-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrong Order of Start Errors #22
Comments
We are having problems with the order of errors of start command. The first error displayed is "This task does not reflect a business priority at the moment...", but should be "No price label is set to calculate the duration". 1 Footnotes
|
/annotate |
Curious to know how much information you seeded your database with before we are testing this |
actually only this issue is on database, lol. |
@shiv810 I think we need to either open source our production database or you should provide instructions for your scraper. Otherwise we can't really QA this stuff |
One time we we working on a fix where the price label should be the first thing that start command checks for and throws an error for 1 Footnotes
|
/annotate |
I suppose it would make sense to transfer it to @ubiquity-os and also make a note of it in the vector embeddings readme. |
We are having problems with the order of errors of start command. The first error displayed is "This task does not reflect a business priority at the moment...", but should be "No price label is set to calculate the duration". 1 Footnotes
|
/annotate #22 (comment) global |
/help |
/annotate ubiquity-os/plugins-wishlist#66 (comment) global |
Sorry, my kernel is off, I will turn it on |
That was a test to see if it would have permissions problems on other repositories, organizations, and such. It should due to different JWT based on the GitHub app installation ID |
/annotate ubiquity-os/plugins-wishlist#66 (comment) global |
! Not Found - https://docs.github.com/rest/issues/comments#get-an-issue-comment |
But either way I can't seem to get the plugin to work. Can you fix? |
I suppose we eventually should throw a specific and clear error saying that this is out of the current organization and it does not have permissions to annotate it. |
I think the problem here is that the the bot only gets the comment id of the link, and supposes that the comment is from the same org and repo from the annotate command, so if you try to annotate a command from another repo, it will break |
I didnt get the org and repo from the url cause I thought this wouldnt be necessary, it doesnt make much sense the user wanting to annotate a comment from another issue in the issue that his making comments |
When user comments /start, at least the first error should say that there is no price label so this can't be started.
The text was updated successfully, but these errors were encountered: