[TSPS-645] Improve error handling when submitting Teaspoons jobs #5439
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
MatthewBemis
commented
Oct 17, 2025
| fetchData(); | ||
| }, [signal]); | ||
|
|
||
| const handleSubmit = async () => { |
There was a problem hiding this comment.
this function had gotten a bit gnarly- there was some cruft leftover from earlier days of development. i took this opportunity to clean it up and hopefully make a rather complicated sequence of api calls easier to follow
mmorgantaylor
approved these changes
Oct 17, 2025
| notify('error', 'No pipeline selected or pipeline name not found'); | ||
| return; | ||
| } | ||
| const pipelineName = selectedPipeline.pipelineName; |
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Jira Ticket: https://broadworkbench.atlassian.net/browse/TSPS-645
Summary of changes:
What
Screen.Recording.2025-10-17.at.12.35.27.PM.mov
Why
Testing strategy