Conversation
jameskerr
approved these changes
Aug 19, 2023
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.
I figured this one out by running
yarn install --inline-buildson Zui commitcb746afandcd'ing to the tmp directory it showed for where it cloned the Brimcap repo. By doinggit diffwhile it was building I could see the following output:So it looks like the changes from #306 to
package.jsonare simplified during the build process and that's enough to render the build artifacts as "dirty".Here's verification that the
-dirtygoes away when using the Brimcap based on this fix branch.Sadly, even with this change in place, it looks like
brimcap -versionbroke in some other way again with the Monorepo changes in brimdata/zui#2818, but I'm game to fix these problems one layer at a time.Fixes brimdata/zui#2840