fix: fixed frontend warm booting issue and dreamview_sidebar overflow issue #14940
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
fix: adjusted the job count to 80% of the available processing units when building with Bazel fix: fixed frontend hotstart issue and dreamview_sidebar issue fix: fixed dreamview_sidebar issue Revert "fix: adjusted the job count to 80% of the available processing units when building with Bazel" This reverts commit 852cd49.
hanjiayuan236
changed the title
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.
Hello, I have identified two issues that may impact the testing and usability of Dreamview.
While using 'npm install' and 'npm start' for warm booting the frontend, there is an issue caused by Webpack, which is identical to the problem mentioned in Unexpected Token Error eemeli/yaml#394. This can be resolved by specifying the yarn version to be 2.0.1 in the package.json file.
When users click on the layer menu under the sim control mode, the bottom of the perception and map menu may not be displayed due to CSS-related issues. I have introduced additional padding to accommodate screen size variations. The attached images demonstrate the differences before and after implementing the changes.
Before change:
After change: