remove elapsedMillisecond hack now that backend is fixed #29
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks :) I'll wait one Sourcegraph version, i.e. when 3.0 is officially released, this'll be merged. This should give folks enough time to update. |
|
Enough time has passed that most instances will have this field working now, merging. There is a separate convo to have about versioning src alongside Sourcegraph |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See https://github.com/sourcegraph/sourcegraph/pull/551 for details. Bad value for elapsedMilliseconds should not be coming back from the server on new versions.
Not sure how releases work so I'll leave that part up to you guys.