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

feat(app): mark protocol anlayses as stale if they lack RTP #14763

Merged
merged 4 commits into from
Apr 1, 2024

Conversation

ncdiehl11
Copy link
Collaborator

@ncdiehl11 ncdiehl11 commented Apr 1, 2024

closes AUTH-247

Overview

We currently display a stale anlaysis banner for protocols that are determined to require reanalysis. The current check is for the lack of a liquids key on the analysis output. Now, we also want to check for the lack of a runTimeParmeters key, as all analyses should contain this key, even if its value is an empty list.

Test Plan

  • produce a protocol in the desktop app that does not have a key for runTimeParameters. To do this, you can open the protocol's overflow menu, select 'Show in folder', open the latest analysis, and remove the runTimeParameters key and value if it exists
  • observe the stale analysis banner shows
Screenshot 2024-04-01 at 11 40 47 AM - the banner should disappear after reanalysis

Changelog

  • extend getAnalysisStatus util to check for presence of RTP key
  • add runTimeParameters field to test fixture
  • add tests

Review requests

authorship devs

Risk assessment

low

We currently display a stale anlaysis banner for protocols that are determined to require
reanalysis. The current check is for the lack of a `liquids` key on the analysis output. Now, we
also want to check for the lack of a `runTimeParmeters` key, as all analyses should contain this
key, even if its value is an empty list.
Copy link

codecov bot commented Apr 1, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 67.20%. Comparing base (0fbb4c7) to head (587305b).
Report is 7 commits behind head on edge.

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             edge   #14763      +/-   ##
==========================================
+ Coverage   67.17%   67.20%   +0.02%     
==========================================
  Files        2495     2495              
  Lines       71483    71404      -79     
  Branches     9020     8991      -29     
==========================================
- Hits        48020    47985      -35     
+ Misses      21341    21304      -37     
+ Partials     2122     2115       -7     
Flag Coverage Δ
shared-data 75.93% <ø> (ø)

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

Files Coverage Δ
...shell/src/protocol-analysis/writeFailedAnalysis.ts 100.00% <ø> (ø)
app/src/organisms/ProtocolsLanding/utils.ts 61.53% <ø> (+4.39%) ⬆️

... and 5 files with indirect coverage changes

@ncdiehl11 ncdiehl11 marked this pull request as ready for review April 1, 2024 16:45
@ncdiehl11 ncdiehl11 requested review from a team as code owners April 1, 2024 16:45
@ncdiehl11 ncdiehl11 requested review from mjhuff, koji, shlokamin and jerader and removed request for a team April 1, 2024 16:45
@@ -3936,5 +3936,6 @@
"description": "",
"displayColor": "#b925ff"
}
]
],
"runTimeParameters": []
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚀 yay so cool seeing this key in fixtures!!

Copy link
Collaborator

@jerader jerader left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

woohoo! lgtm 🦒

Copy link
Contributor

@koji koji left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good to me 🎉

@ncdiehl11 ncdiehl11 merged commit c864a99 into edge Apr 1, 2024
44 checks passed
@ncdiehl11 ncdiehl11 deleted the fix_app-stale-analysis-rtp branch April 1, 2024 18:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants