-
Notifications
You must be signed in to change notification settings - Fork 283
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
jaeger/1.65.0 package update #39045
jaeger/1.65.0 package update #39045
Conversation
octo-sts
bot
commented
Jan 8, 2025
Signed-off-by: wolfi-bot <121097084+wolfi-bot@users.noreply.github.com>
Please use 👍 or 👎 on this comment to indicate if you agree or disagree with the recommendation. To provide more detailed feedback please comment on the recommendation prefixed with /ai-verify: e.g. /ai-verify partially helpful but I also adde bash to the build environment Gen AI suggestions to solve the build error: Based on the error output, I can provide a specific analysis and fix: • Detected Error: • Error Category: Build/Dependency • Failure Point: UI build step in the jaeger-all-in-one subpackage, specifically in the file • Root Cause Analysis: The build is failing because it's trying to use the • Suggested Fix:
// Change from:
import { LuLoader2 } from 'react-icons/lu';
// To one of these alternatives:
import { AiOutlineLoading } from 'react-icons/ai';
// or
import { CgSpinner } from 'react-icons/cg';
pipeline:
- runs: |
if [[ "${{range.key}}" = "all-in-one" ]]; then
cd jaeger-ui
yarn add react-icons@latest
yarn install --frozen-lockfile
cd packages/jaeger-ui/build
yarn build
fi • Explanation: The error indicates a missing export from the react-icons package. Either the icon name has changed in a newer version, or we need to use a different icon that's definitely available in the current version. • Additional Notes:
• References:
|
Build ID: a6968872-cfe2-4f85-9753-51e621b1c245
Error: failed to build jaeger: building group: pod failed: build failed
did not test because building group: pod failed: build failed looks like issues from infra side, merging main so that CI runs again. |
React Icons seem to be handled differently when using yarn vs npm, yarn issue with react icons |