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

Remove duplicate route for /simulations (#1952) #1955

Merged
merged 1 commit into from
Nov 8, 2024

Conversation

mikesmit
Copy link
Collaborator

@mikesmit mikesmit commented Nov 7, 2024

The flask app defines the same GET operation on /simulations twice. This change simply removes one of them.

Copy link
Collaborator

@anth-volk anth-volk left a comment

Choose a reason for hiding this comment

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

Thanks for your work on this @mikesmit! Unfortunately, this change causes tests to fail; could you look into why that is? If you're unable to, I could also do so, just give me the word.

Also, please open an issue in the repo for this, then begin your top comment with "Fixes #ISSUE NUMBER". This helps us better track changes.

@@ -0,0 +1,4 @@
bump: patch
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
bump: patch
- bump: patch

This is required due to how this file's parsed by yaml-changelog

Copy link
Collaborator Author

@mikesmit mikesmit Nov 7, 2024

Choose a reason for hiding this comment

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

Question: I was going to write that in the commit title ("FIXES #issue") , but I looked at your commit log and the convention seemed to actually be "thing I did (#issue)" (for instance Fix error debugging (https://github.com/PolicyEngine/policyengine-api/pull/1943) which was why I wrote the commit message that way (intended to reference #1952)

Is there some automation that replaces the title and/or am I misunderstanding what you are asking for there?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

With regard to the tests... I can't actually run them locally at all at the moment because of this issue although that is failing with a different root cause. I'll eyeball the logs and see what I can see though.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Right, I did see your comment in Slack on #1954. Weirdly, I tried responding last night, but my message doesn't appear as of today, though I see Nikhil ended up giving some context. If nothing becomes apparent, feel free to let me know. I can run locally and see if I can figure out what's going on.

Fixes #1952

The flask app defines the same GET operation on /simulations twice. This
change simply removes one of them.
@anth-volk
Copy link
Collaborator

And of course for some reason, the tests passed upon your force push. Maybe the failure was either a fluke or old code. Thanks for this @mikesmit, approving.

@anth-volk anth-volk self-requested a review November 8, 2024 23:37
@anth-volk anth-volk merged commit d85e818 into master Nov 8, 2024
4 checks passed
@anth-volk anth-volk deleted the 1952-remove-duplicate-routes branch November 8, 2024 23:37
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