macos console output: Class WebSwapCGLLayer is implemented in both ...

kubernetes-sigs / kui

A hybrid command-line/UI development experience for cloud-native development

Apache License 2.0

2.82k stars 183 forks source link

macos console output: Class WebSwapCGLLayer is implemented in both ... #8860

Closed starpit closed 1 year ago

starpit commented 2 years ago

Greetings visitors: this is an innocuous message that does not affect the way Kui interacts with your cluster.

upstream bug: https://github.com/electron/electron/issues/33685

objc[70843]: Class WebSwapCGLLayer is implemented in both /System/Library/Frameworks/WebKit.framework/Versions/A/Frameworks/WebCore.framework/Versions/A/Frameworks/libANGLE-shared.dylib (0x7ffa4b892318) and /Users/nickm/git/whisk/nickm/kui/node_modules/electron/dist/Electron.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Libraries/libGLESv2.dylib (0x10c3ea9c8). One of the two will be used. Which one is undefined.

starpit commented 2 years ago

the underlying bug in chromium is still not resolved. we may release a version of kui, anyway?

k8s-triage-robot commented 2 years ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue or PR as fresh with /remove-lifecycle stale
Mark this issue or PR as rotten with /lifecycle rotten
Close this issue or PR with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 1 year ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue or PR as fresh with /remove-lifecycle stale
Mark this issue or PR as rotten with /lifecycle rotten
Close this issue or PR with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

starpit commented 1 year ago

/remove-lifecycle stale

starpit commented 1 year ago

note: actually closed by #9214 not #9200