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(deadline): bad file path for Repository when using VersionQuery #252

Merged
merged 1 commit into from
Nov 26, 2020

Conversation

ddneilson
Copy link
Contributor

Fixes: #251


By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

@ddneilson ddneilson added the contribution/core This is a PR that came from AWS. label Nov 25, 2020
Copy link
Contributor

@horsmand horsmand left a comment

Choose a reason for hiding this comment

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

This looks fine to me, but I think we may want to re-evaluate if it makes sense to leave these VersionQuery fields like majorVersion as numbers when we need to jump through hoops any time we need to use them. It might make more sense to just make them strings.

@jusiskin jusiskin changed the title fix(deadline): Bad filepath for Repository when using VersionQuery fix(deadline): bad file path for Repository when using VersionQuery Nov 26, 2020
@jusiskin jusiskin merged commit 84a20de into aws:mainline Nov 26, 2020
@ddneilson ddneilson deleted the fix_bad_repo_token branch March 17, 2021 15:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
contribution/core This is a PR that came from AWS.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Bad filepath in Repository when using VersionQuery
3 participants