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: flaky test - app history command not printing source in consistent order #17615

Conversation

Mangaal
Copy link
Contributor

@Mangaal Mangaal commented Mar 25, 2024

Description:

This PR addresses the issue of the order of insertion not being preserved in the printApplicationHistoryTable function. I've modified the function to store source URLs in both a map and a slice, ensuring that the order of insertion is preserved when printing the history table.

Changes Made:

Added a slice to store the order of insertion of source URLs.
Modified the logic to populate the map and slice accordingly.
Updated the printing logic to iterate over the slice and print history entries in the order of insertion.

Checklist:

  • Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
  • The title of the PR states what changed and the related issues number (used for the release note).
  • The title of the PR conforms to the Toolchain Guide
  • I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.
  • I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them.
  • Does this PR require documentation updates?
  • I've updated documentation as required by this PR.
  • I have signed off all my commits as required by DCO
  • I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
  • My build is green (troubleshooting builds).
  • My new feature complies with the feature status guidelines.
  • I have added a brief description of why this PR is necessary and/or what this PR solves.
  • Optional. My organization is added to USERS.md.
  • Optional. For bug fixes, I've indicated what older releases this fix should be cherry-picked into (this may or may not happen depending on risk/complexity).

@Mangaal Mangaal requested a review from a team as a code owner March 25, 2024 16:09
@ishitasequeira ishitasequeira changed the title fix: app history command not printing source in consistent order fix: flaky test - app history command not printing source in consistent order Mar 25, 2024
Copy link
Member

@ishitasequeira ishitasequeira left a comment

Choose a reason for hiding this comment

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

LGTM!!

@ishitasequeira ishitasequeira enabled auto-merge (squash) March 25, 2024 16:30
@ishitasequeira ishitasequeira merged commit 8cf0381 into argoproj:master Mar 25, 2024
28 checks passed
lyda pushed a commit to lyda/argo-cd that referenced this pull request Mar 28, 2024
…nt order (argoproj#17615)

* instead if ranging over the map varHistory to print the history, inroduced a string array varHistoryKeys

Signed-off-by: Mangaal <[email protected]>

* update unit test expectation, remove new line in the beginning

Signed-off-by: Mangaal <[email protected]>

---------

Signed-off-by: Mangaal <[email protected]>
Signed-off-by: Kevin Lyda <[email protected]>
mkieweg pushed a commit to mkieweg/argo-cd that referenced this pull request Jun 11, 2024
…nt order (argoproj#17615)

* instead if ranging over the map varHistory to print the history, inroduced a string array varHistoryKeys

Signed-off-by: Mangaal <[email protected]>

* update unit test expectation, remove new line in the beginning

Signed-off-by: Mangaal <[email protected]>

---------

Signed-off-by: Mangaal <[email protected]>
Hariharasuthan99 pushed a commit to AmadeusITGroup/argo-cd that referenced this pull request Jun 16, 2024
…nt order (argoproj#17615)

* instead if ranging over the map varHistory to print the history, inroduced a string array varHistoryKeys

Signed-off-by: Mangaal <[email protected]>

* update unit test expectation, remove new line in the beginning

Signed-off-by: Mangaal <[email protected]>

---------

Signed-off-by: Mangaal <[email protected]>
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.

2 participants