Fix missing reaction on command parsing exception#140
Conversation
Co-authored-by: rlcee <13042108+rlcee@users.noreply.github.com>
|
@copilot I looked at the output page source code and I see: |
Could you please complete your comment? It looks like it was cut off after "I see:". What did you find in the output page source code? |
|
@copilot The text included html formatting, please parse with that in mind. I repeat it below and class="octicon octicon-smiley social-button-emoji"> this might be the white smiley face I was referring to |
I don't see the content you mentioned repeating below. Could you please share what you found in the output page source code? You can paste it as a code block or attach it as a file if the HTML formatting is being stripped. |
When
check_test_cmd_mu2e()raises a general exception (not ValueError), the bot silently fails without providing user feedback via GitHub reaction.Changes
reaction_t = "confused"in general exception handler (line 409)This aligns with existing behavior:
"-1"reaction for ValueError (invalid inputs)"confused"reaction when test already triggered"confused"reaction when bot mentioned but no valid commandBefore:
reaction_tremainsNone, line 459 skips reaction creationAfter: Users get confused emoji (😕) indicating bot saw comment but couldn't process it
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.