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

Fixes 2938: Add Errata tab to snapshot details #235

Merged
merged 13 commits into from
Apr 26, 2024

Conversation

Andrewgdewar
Copy link
Member

@Andrewgdewar Andrewgdewar commented Mar 22, 2024

Summary

  • Adds a query to retrieve snapshot errata
  • Adds an Errata tab to SnapshotDetails modal to list snapshot errata
  • Supports filtering by name / synopsis, type, and severity
  • Dependent on these PRs: backend, tang

Testing steps

  • Add a repository with package errata and let it snapshot
  • Click View all snapshots from the kebab on the Repositories page
  • Click the Errata count to route to the Errata (Advisories) tab in the SnapshotDetails modal
  • You should see all the errata for this snapshot displayed, with additional info for each errata displayed when clicking the expandable icon
  • Filtering on name / synopsis, type, severity should only display errata with those filters

@jlsherrill
Copy link
Member

@swadeley
Copy link
Member

swadeley commented Apr 8, 2024

/retest

1 similar comment
@swadeley
Copy link
Member

/retest

@swadeley
Copy link
Member

Hi

I added repo:
https://jlsherrill.fedorapeople.org/fake-repos/needed-errata/

I clicked kebab, View all snapshots, clicked on the errata count "4",
"Snapshot detail" table was displayed but the lines were blank.

Table closed and the follow error was displayed:

Unable to find errata with the given UUID.
Bad Request

@swadeley
Copy link
Member

/retest

1 similar comment
@swadeley
Copy link
Member

/retest

@xbhouse
Copy link
Contributor

xbhouse commented Apr 16, 2024

sorry just seeing this @swadeley. i wonder if the errors you're seeing are because the backend requires a new tang release. the tang PR will likely need to be merged in first before this can be tested properly, otherwise you'd need to reference a local clone of that tang PR in the backend

@Andrewgdewar
Copy link
Member Author

✅ Ack on the code changes from me!
Feel free to ack this if you are good with the other changes @xbhouse!
Thanks for the help 🙇‍♂️

Copy link
Contributor

Choose a reason for hiding this comment

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

The JIRA card says to include a link to the advisory page in the description, but I don't see it here. Should that be added or has the requirement changed?

image

Copy link
Contributor

Choose a reason for hiding this comment

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

cc @Andrewgdewar, similar question as above

Copy link
Member

Choose a reason for hiding this comment

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

we might need some funny logic that checks if the errata starts with RH and add a link if so

@swadeley
Copy link
Member

/retest

@swadeley
Copy link
Member

/retest

1 similar comment
@swadeley
Copy link
Member

/retest

@swadeley
Copy link
Member

swadeley commented Apr 22, 2024

Hi

looks good:

image

image

image

@xbhouse
Copy link
Contributor

xbhouse commented Apr 23, 2024

ack on @Andrewgdewar's code changes!

@jlsherrill
Copy link
Member

I would make the default sort be done in descending order of date (so most recent errata first). Thats generally what users are more interested in.

@rverdile
Copy link
Contributor

I agree with justin's comment, otherwise looks good to me

@jlsherrill
Copy link
Member

Checking an epel errata, theres some formatting issues, for example:
image

@jlsherrill
Copy link
Member

otherwise everything else looks great!

@xbhouse
Copy link
Contributor

xbhouse commented Apr 23, 2024

oh that doesn't look good at all :) there's no formatting being done on the description right now, i'll see what i can do there. which repo was that @jlsherrill ?

EDIT: i see it's epel9, no other errata in repos i've checked have a description with a changelog like that :/ i'm not sure how best to handle that

@xbhouse
Copy link
Contributor

xbhouse commented Apr 23, 2024

for the sorting on date, i think we'd have to make a change in the api to support that. i can open a bug? correct me if i'm wrong @Andrewgdewar

@jlsherrill
Copy link
Member

We probably just need to adjust the default order here: https://github.com/content-services/tang/blob/main/pkg/tangy/rpm.go#L313

as right now its not configurable, which i think is okay for now

@jlsherrill
Copy link
Member

and yeah, that can be a followup ticket

@xbhouse
Copy link
Contributor

xbhouse commented Apr 25, 2024

sort order changed thanks to @Andrewgdewar ! and here's that epel errata description with the latest push @jlsherrill. thoughts?

Screenshot 2024-04-25 at 3 27 53 PM

@swadeley
Copy link
Member

/retest

1 similar comment
@swadeley
Copy link
Member

/retest

@swadeley swadeley merged commit f76dd22 into content-services:main Apr 26, 2024
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants