Skip to content
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

fix: improve trial log request cancelling #8787

Merged
merged 1 commit into from
Feb 2, 2024

Conversation

ashtonG
Copy link
Contributor

@ashtonG ashtonG commented Feb 1, 2024

Description

this fixes an issue where resetting the filter settings on trials with logs that take a long time to respond (over 500 ms) can cause the catch up log request to get cancelled. To fix, we skip aborting the request when handling filter changes if the filter is being updated to an empty object. This is because the request was already reset when the filter was reset. We also ensure that old requests don't stick around by merging the outer abort controller with the one that the stream config gives us.

Test Plan

  • on a trial logs page, use devtools to throttle the network to GPRS levels
  • apply a filter and wait for the logs to appear.
  • click reset filters
  • the full logs should appear

Commentary (optional)

Checklist

  • Changes have been manually QA'd
  • User-facing API changes need the "User-facing API Change" label.
  • Release notes should be added as a separate file under docs/release-notes/.
    See Release Note for details.
  • Licenses should be included for new code which was copied and/or modified from any external code.

Ticket

WEB-1964

this fixes an issue where resetting the filter settings on trials with
logs that take a long time to respond (over 500 ms) can cause the catch
up log request to get cancelled. To fix, we skip aborting the request
when handling filter changes if the filter is being updated to an empty
object. This is because the request was already reset when the filter
was reset. We also ensure that old requests don't stick around by
merging the outer abort controller with the one that the stream config
gives us.
@ashtonG ashtonG requested a review from a team as a code owner February 1, 2024 21:35
@cla-bot cla-bot bot added the cla-signed label Feb 1, 2024
Copy link

netlify bot commented Feb 1, 2024

Deploy Preview for determined-ui ready!

Name Link
🔨 Latest commit 3e31406
🔍 Latest deploy log https://app.netlify.com/sites/determined-ui/deploys/65bc0eba6ea5ef0008f5826f
😎 Deploy Preview https://deploy-preview-8787--determined-ui.netlify.app/
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link

codecov bot commented Feb 1, 2024

Codecov Report

Attention: 19 lines in your changes are missing coverage. Please review.

Comparison is base (36a2e29) 47.69% compared to head (3e31406) 42.69%.
Report is 2 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #8787      +/-   ##
==========================================
- Coverage   47.69%   42.69%   -5.01%     
==========================================
  Files        1049      732     -317     
  Lines      167230   128569   -38661     
  Branches     2239     2239              
==========================================
- Hits        79766    54888   -24878     
+ Misses      87306    73523   -13783     
  Partials      158      158              
Flag Coverage Δ
harness ?
web 42.54% <9.52%> (-0.01%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Coverage Δ
.../react/src/pages/TrialDetails/TrialDetailsLogs.tsx 14.61% <9.52%> (-0.47%) ⬇️

... and 317 files with indirect coverage changes

@ashtonG ashtonG added the to-cherry-pick Pull requests that need to be cherry-picked into the current release label Feb 1, 2024
@ashtonG ashtonG merged commit bb88b01 into main Feb 2, 2024
82 of 93 checks passed
@ashtonG ashtonG deleted the fix/WEB-1964/reset-log-settings-fix branch February 2, 2024 17:59
dai-release bot pushed a commit that referenced this pull request Feb 2, 2024
this fixes an issue where resetting the filter settings on trials with
logs that take a long time to respond (over 500 ms) can cause the catch
up log request to get cancelled. To fix, we skip aborting the request
when handling filter changes if the filter is being updated to an empty
object. This is because the request was already reset when the filter
was reset. We also ensure that old requests don't stick around by
merging the outer abort controller with the one that the stream config
gives us.

(cherry picked from commit bb88b01)
maxrussell pushed a commit that referenced this pull request Mar 21, 2024
this fixes an issue where resetting the filter settings on trials with
logs that take a long time to respond (over 500 ms) can cause the catch
up log request to get cancelled. To fix, we skip aborting the request
when handling filter changes if the filter is being updated to an empty
object. This is because the request was already reset when the filter
was reset. We also ensure that old requests don't stick around by
merging the outer abort controller with the one that the stream config
gives us.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla-signed to-cherry-pick Pull requests that need to be cherry-picked into the current release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants