-
Notifications
You must be signed in to change notification settings - Fork 69
Automatically add a testcase via a comment #231
Comments
Also it should be possible to update an ice, but using |
So, we have to serve and manage glacier-bot like rustbot(triagebot)? If so, I'm not sure but it may be a burden to the members (particularly infra team). |
Can you explain the "serve and manage" part a little bit more? I never developed a github bot, nor looked I at the source of rustbot/triagebot/bors. I do not know how much effort it is to develop such bot. But we can aggree, that it will be a burden to somebody. But it will be increase the awareness and the usefulness of this repository. Nobody needs to open a PR anymore, nobody needs to approve it (well, if we go for the It's up to you to decide wether it's worth the effort to develop (and maintain (?)) such a bot. |
I would be happy to accept a patch that includes this functionality into triagebot, but I don't think we need a separate bot for this. |
Should this issue be transfered to the https://github.com/rust-lang/triagebot/ repo then? |
I would imagine that tracking it here makes more sense, but feel free to reopen there if needed. |
Sounds good, I agree with that! |
rust-lang/triagebot#526 landed, so this should probably be closed? |
We should test it out first :) |
Should we have a dummy ICE PR? Or do we want to wait until we have an ICE with MCVE ready? |
I tried in rust-lang/rust#72554 and we should have enabled |
Hm, I tried with rust-lang/rust#72554 (comment) but there is no response for about an hour. |
cc @Elinvynia |
I see where the issue could possibly be, I parse the URL like so: If only team members are supposed to use this, then I guess we could allow any URL that resolves into text. @LeSeulArtichaut the above thing aside, it still should have created a PR, albeit with the wrong content. Do you see any potential issue with how I've done the octocrab side of things? |
It's possible that octocrab could have failed e.g. to parse a GitHub response. If that's the case the error should have been logged, cc @Mark-Simulacrum. |
|
Error comes from Octocrab, cc @XAMPPRocky |
The error is with this model, I can make a fix for this later, but if someone else wants to please go ahead. https://github.com/XAMPPRocky/octocrab/blob/96e9413c921078463e249078ac0cc5956ac80d1a/src/models.rs#L786 |
I've published a fix for this in |
Is this fixed by rust-lang/triagebot#580 ? |
I'm not sure, let me check it... |
It... doesn't still work well? rust-lang/rust#74120 (comment) |
Are you a team member (as per rustbot) ? |
@Mark-Simulacrum is there something in the logs ? |
https://gist.github.com/Mark-Simulacrum/bcb29951de2a15b94c4a761d06515d35 is the log for the event -- looks like maybe a bug in octocrab? |
|
IIRC octocrab is only used for |
The backtrace clearly indicates that the error happens as a result of this line: https://github.com/rust-lang/triagebot/blob/e03ad06feda31ff2d832db8f4d61b795ca8bbcbc/src/handlers/glacier.rs#L52 |
The error is that See https://docs.github.com/en/rest/reference/repos#create-or-update-file-contents |
Thank you for the report! If someone wants to make a PR to octocrab to make those fields optional I would accept a PR and put out a patch release, otherwise I can make the change later. |
I don't think that any field should be made optional. I think it should be a whole different struct. I'll open a PR if I get some time to fix it. |
The fix has now been published as part of |
Does it work now ? Btw is there any reason only team members can use this command ? |
Still doesn't look like it's working? rust-lang/rust#74120 (comment) |
Unfortunately, I don't know what reference already exists. Maybe this is enough though; happy to deploy more logging or whatever. I would prefer to limit commands that cause triagebot to take noisy action (e.g., opening PRs or pushing commits) to team members just for safety even if we believe them to be relatively secure. |
The cause is that rustbot fork repo has the same name branch already, I think it was created in the previous time. https://github.com/rustbot/glacier/tree/triagebot-ice-74120 |
And getting the raw rust code didn't worked: cc @Elinvynia |
@kellda Thanks, I'll have a look! |
Hitting the main GitHub URL would let one scrape the button and then follow the raw link, however, more simply, given a gist e.g. https://api.github.com/gists/fa3a4448239b08769f0c581dd1588f36 |
This was implemented in triagebot as the
Make sure to include "/rust-play/" in the URL or it won't work. |
Does it work now ? |
Yes: see #551 for an example. |
Does this still work? I tried it on rust-lang/rust#109146 but don't see a PR. |
It requires gists associated with @rust-play, the bot user that runs the Rust Playground. |
Just like
@rustbot
can be pinged, why not using the same with@rust-lang-glacier-bot
?I would suggest something like this:
Hey, I found a mcve for this ICE. With this mcve it works.
@rust-lang-glacier-bot add ICE https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=34dc5c9d1e14ff10ff8be22be265e7ef
Then the bot can try the playgroundand see if it ICEs and automatically adds it.
If we don't want an automatism, something like
@rust-lang-glacier-bot +r
can be used, similar to@bors
.What do you think?
The text was updated successfully, but these errors were encountered: