Adds a simple method to print startup diagnostic information#192
Merged
Conversation
This was referenced Aug 13, 2021
Closed
Closed
Member
Not sure if this is how it works, but couldn't the framework theoretically have been built at a different time and cargo just used an "old" version when compiling the actual operator (theroretically even with a different version of rustc?)? |
This file contains hidden or 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
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.
This is related to stackabletech/issues#19
I don't think we can include the full
bultinoperator-rsbecause it auto-generates a file at build time (using abuild.rsscript) and if we include this in operator-rs we'd get the information ofoperator-rsand not of the using library.See stackabletech/spark-operator#118 for an example on how to use it.