-
Notifications
You must be signed in to change notification settings - Fork 13
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
state publish
#2951
state publish
#2951
Conversation
This came from DX-1754.
Test failures are not due to this PR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice find!
It's needed for identifying languages to install. Without it, we'd get a "Unsupported platform: Windows -1 10.0.17134.1" error. Also fix some nil pointer exceptions.
@MDrakos please re-review. I found another set of integration test failures that are fixed with: 021913e Note that the whole method is getting messy and is slated for refactor in https://activestatef.atlassian.net/browse/DX-1897. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm good to merge but I did add a comment that is worth considering.
Comment is here btw: 021913e#r135121863
I guess because it's on a commit it doesn't show up here?
Okay, I've added comments: ca2dc45 |
6d5aa3a
to
ca2dc45
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Works for me!
Try again.
This was the problem: 049d1aa. I'm honestly not sure why the tests were passing before vs. after this change. Perhaps something on the platform side changed with regards to typing.
strfmt.DateTime
appears to be equivalent totime.Time
from Go's perspective, but perhaps serialization changes in some way. Anyway, I'm seeing some recent, unrelated test failures that are due to platform changes, indicating some flux that could be causing trouble here. I'll file tickets to investigate those.