Crash while loading cluster overview view.

Describe the bug
Switched from one cluster (while inspecting a node instance) to another cluster. Recieved this crash while switching. Occurs intermittantly. (Restart allows the Overview to load normally.) Have seen this crash twice.
=== crash details in-app ===
App crash at /events
To help us improve the product please report bugs to Slack community or Github issues tracker.
Component stack:

    at virtual_list_VirtualList (http://a3d00c6b51780c5d5303bef80e905ed2.localhost:52286/build/Lens.js:496164:9)
    at div
    at LogList (http://a3d00c6b51780c5d5303bef80e905ed2.localhost:52286/build/Lens.js:529464:9)
    at div
    at Logs (http://a3d00c6b51780c5d5303bef80e905ed2.localhost:52286/build/Lens.js:529896:9)
    at div
    at div
    at Dock (http://a3d00c6b51780c5d5303bef80e905ed2.localhost:52286/build/Lens.js:530308:9)
    at div
    at div
    at MainLayout (http://a3d00c6b51780c5d5303bef80e905ed2.localhost:52286/build/Lens.js:475494:9)
    at ErrorBoundary (http://a3d00c6b51780c5d5303bef80e905ed2.localhost:52286/build/Lens.js:475037:9)
    at Router (http://a3d00c6b51780c5d5303bef80e905ed2.localhost:52286/build/Lens.js:18291:30)
    at App (http://a3d00c6b51780c5d5303bef80e905ed2.localhost:52286/build/Lens.js:531386:9)
    at ThemeProvider (http://a3d00c6b51780c5d5303bef80e905ed2.localhost:52286/build/Lens.js:556003:24)

Error stack:

TypeError: Cannot read property 'resetAfterIndex' of null
    at virtual_list_VirtualList.componentDidUpdate (http://a3d00c6b51780c5d5303bef80e905ed2.localhost:52286/build/Lens.js:496215:34)
    at Yi (http://a3d00c6b51780c5d5303bef80e905ed2.localhost:52286/build/Lens.js:442399:502)
    at dk (http://a3d00c6b51780c5d5303bef80e905ed2.localhost:52286/build/Lens.js:442439:160)
    at exports.unstable_runWithPriority (http://a3d00c6b51780c5d5303bef80e905ed2.localhost:52286/build/Lens.js:442514:343)
    at gg (http://a3d00c6b51780c5d5303bef80e905ed2.localhost:52286/build/Lens.js:442302:325)
    at Uj (http://a3d00c6b51780c5d5303bef80e905ed2.localhost:52286/build/Lens.js:442432:279)
    at Lj (http://a3d00c6b51780c5d5303bef80e905ed2.localhost:52286/build/Lens.js:442423:371)
    at http://a3d00c6b51780c5d5303bef80e905ed2.localhost:52286/build/Lens.js:442303:115
    at exports.unstable_runWithPriority (http://a3d00c6b51780c5d5303bef80e905ed2.localhost:52286/build/Lens.js:442514:343)
    at gg (http://a3d00c6b51780c5d5303bef80e905ed2.localhost:52286/build/Lens.js:442302:325)
    at jg (http://a3d00c6b51780c5d5303bef80e905ed2.localhost:52286/build/Lens.js:442303:61)
    at ig (http://a3d00c6b51780c5d5303bef80e905ed2.localhost:52286/build/Lens.js:442302:428)
    at Wj (http://a3d00c6b51780c5d5303bef80e905ed2.localhost:52286/build/Lens.js:442424:190)
    at reactionScheduler (http://a3d00c6b51780c5d5303bef80e905ed2.localhost:52286/build/Lens.js:2536:12)
    at http://a3d00c6b51780c5d5303bef80e905ed2.localhost:52286/build/Lens.js:2537:14
    at Hh (/Applications/Lens.app/Contents/Resources/extensions/lenscloud-lens-extension/dist/renderer.js:306:141185)

To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
Normal load of cluster overview.
Screenshots

Environment (please complete the following information):
Lens: 5.0.0-latest.20210629.3
Electron: 9.4.4
Chrome: 83.0.4103.122
Node: 12.14.1
Install via website download.
Logs:
No logs available.
Kubeconfig:
Rather not post. Generated using aws eks update-kubeconfig.
Additional context
Nothing usual that I can think of.

fixed by #3230


[GitHub template] Update "areas" for bug-issue template (explorer-previews)

Description of the new feature / enhancement
We have a number of rather specific "preview elements" in the list of "Areas with issue" when opening a new GitHub issue for a bug. We don't need to name all current possibilities and now Monaco is included, we're obviously not gonna name 150 items here. Maybe split previews and miniatures, but I'd probably just use one list-item myself.

Scenario when this would be used?
Filing issue with Explorer preview.
Supporting information
No response

Same would make sense for mouse utilities

I don't think we should do this.  This is focusing on a "us" thing, not who would file the bug.  I'd rather focus making sure we get enough data to help get what we need to solve bugs

I don't follow both of the comments.

I misunderstood the main topic of the issue. So my comment is obsolete.
Reading the text helps a lot to understand things. I should do this. 😅


How can I get updated frames/dicoms and POST them?

Describe the Bug
I need to change frames in a dicom file and then get the updated file to send to the backend.
I can't find examples or articles on this topic(
Perhaps you can tell me? The logic is as follows: I changed the file using tools (for example, RectangleROITool) and then on Submit I have to send the changed dicom to the database via POST request
Steps to Reproduce
--
The current behavior
--
The expected behavior
--
OS
--
Node version
--
Browser
--

you can make use of the dicomn SR, for that you can look into how OHIF is handling that https://github.com/OHIF/Viewers/


Telecine refuse to stop recording when lunched

Expected behavior
App should record screen activities, store the recorded activity, and user should be able to stop the recording when they are done.
Actual behavior
When the application is lunched to start recording the app only stops when it want to stop recording, It sometimes freezes the screen and makes it difficult to navigate the screen.
How to reproduce
Download Telecine from play store here, launch it the app, try to stop the recording.
•	Operating system: Android Version 7.0
•	Device used: Tecno Boom J8
•	App Version: 1.6.2
Recording Of The Bug
https://youtu.be/D1ibwCpvRtg
Posted on Utopian.io -  Rewarding Open Source Contributors

In that video, AZ Screen Recorder is using the media projection APIs which prevents Telecine from launching. This is evidenced by the fact that the overlay for Telecine never displays and as a result it never actually starts recording.

I was able to fix this bug by going to permission setting and enabling "show pop up window" option. Maybe, you forgot to ask for "DRAW OVER OTHER APPS" permission.


ARM64 for apple silicon

Hi. I`m build your app and runing well but is Intel64 bit. How to compile your app with go for arm64 ?? Thank you so much for any help.
When I try to build on arm got this message but is no app in build folder
go build -o pacman main.go
# github.com/hajimehoshi/oto
../../../go/pkg/mod/github.com/hajimehoshi/oto@v0.3.3/driver_openal.go:36:22: warning: 'alcOpenDevice' is deprecated: first deprecated in macOS 10.15 - OpenAL is deprecated in favor of AVAudioEngine [-Wdeprecated-declarations]
/Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk/System/Library/Frameworks/OpenAL.framework/Headers/alc.h:209:38: note: 'alcOpenDevice' has been explicitly marked deprecated here
../../../go/pkg/mod/github.com/hajimehoshi/oto@v0.3.3/driver_openal.go:40:11: warning: 'alcCloseDevice' is deprecated: first deprecated in macOS 10.15 - OpenAL is deprecated in favor of AVAudioEngine [-Wdeprecated-declarations]
/Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk/System/Library/Frameworks/OpenAL.framework/Headers/alc.h:211:38: note: 'alcCloseDevice' has been explicitly marked deprecated here
../../../go/pkg/mod/github.com/hajimehoshi/oto@v0.3.3/driver_openal.go:44:22: warning: 'alcCreateContext' is deprecated: first deprecated in macOS 10.15 - OpenAL is deprecated in favor of AVAudioEngine [-Wdeprecated-declarations]
/Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk/System/Library/Frameworks/OpenAL.framework/Headers/alc.h:191:38: note: 'alcCreateContext' has been explicitly marked deprecated here
../../../go/pkg/mod/github.com/hajimehoshi/oto@v0.3.3/driver_openal.go:48:11: warning: 'alcGetError' is deprecated: first deprecated in macOS 10.15 - OpenAL is deprecated in favor of AVAudioEngine [-Wdeprecated-declarations]
/Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk/System/Library/Frameworks/OpenAL.framework/Headers/alc.h:218:38: note: 'alcGetError' has been explicitly marked deprecated here
../../../go/pkg/mod/github.com/hajimehoshi/oto@v0.3.3/driver_openal.go:52:4: warning: 'alcMakeContextCurrent' is deprecated: first deprecated in macOS 10.15 - OpenAL is deprecated in favor of AVAudioEngine [-Wdeprecated-declarations]
/Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk/System/Library/Frameworks/OpenAL.framework/Headers/alc.h:193:38: note: 'alcMakeContextCurrent' has been explicitly marked deprecated here
../../../go/pkg/mod/github.com/hajimehoshi/oto@v0.3.3/driver_openal.go:56:4: warning: 'alcDestroyContext' is deprecated: first deprecated in macOS 10.15 - OpenAL is deprecated in favor of AVAudioEngine [-Wdeprecated-declarations]
/Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk/System/Library/Frameworks/OpenAL.framework/Headers/alc.h:199:38: note: 'alcDestroyContext' has been explicitly marked deprecated here
cgo-gcc-prolog:152:2: warning: 'alBufferData' is deprecated: first deprecated in macOS 10.15 - OpenAL is deprecated in favor of AVAudioEngine [-Wdeprecated-declarations]
/Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk/System/Library/Frameworks/OpenAL.framework/Headers/al.h:601:25: note: 'alBufferData' has been explicitly marked deprecated here
cgo-gcc-prolog:166:2: warning: 'alDeleteBuffers' is deprecated: first deprecated in macOS 10.15 - OpenAL is deprecated in favor of AVAudioEngine [-Wdeprecated-declarations]
/Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk/System/Library/Frameworks/OpenAL.framework/Headers/al.h:595:25: note: 'alDeleteBuffers' has been explicitly marked deprecated here
cgo-gcc-prolog:180:2: warning: 'alDeleteSources' is deprecated: first deprecated in macOS 10.15 - OpenAL is deprecated in favor of AVAudioEngine [-Wdeprecated-declarations]
/Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk/System/Library/Frameworks/OpenAL.framework/Headers/al.h:501:25: note: 'alDeleteSources' has been explicitly marked deprecated here
cgo-gcc-prolog:194:2: warning: 'alGenBuffers' is deprecated: first deprecated in macOS 10.15 - OpenAL is deprecated in favor of AVAudioEngine [-Wdeprecated-declarations]
/Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk/System/Library/Frameworks/OpenAL.framework/Headers/al.h:592:25: note: 'alGenBuffers' has been explicitly marked deprecated here
cgo-gcc-prolog:208:2: warning: 'alGenSources' is deprecated: first deprecated in macOS 10.15 - OpenAL is deprecated in favor of AVAudioEngine [-Wdeprecated-declarations]
/Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk/System/Library/Frameworks/OpenAL.framework/Headers/al.h:498:25: note: 'alGenSources' has been explicitly marked deprecated here
cgo-gcc-prolog:222:2: warning: 'alGetSourcei' is deprecated: first deprecated in macOS 10.15 - OpenAL is deprecated in favor of AVAudioEngine [-Wdeprecated-declarations]
/Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk/System/Library/Frameworks/OpenAL.framework/Headers/al.h:530:25: note: 'alGetSourcei' has been explicitly marked deprecated here
cgo-gcc-prolog:238:35: warning: 'alGetString' is deprecated: first deprecated in macOS 10.15 - OpenAL is deprecated in favor of AVAudioEngine [-Wdeprecated-declarations]
/Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk/System/Library/Frameworks/OpenAL.framework/Headers/al.h:382:34: note: 'alGetString' has been explicitly marked deprecated here
cgo-gcc-prolog:254:2: warning: 'alSourcePlay' is deprecated: first deprecated in macOS 10.15 - OpenAL is deprecated in favor of AVAudioEngine [-Wdeprecated-declarations]
/Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk/System/Library/Frameworks/OpenAL.framework/Headers/al.h:558:25: note: 'alSourcePlay' has been explicitly marked deprecated here
cgo-gcc-prolog:268:2: warning: 'alSourceQueueBuffers' is deprecated: first deprecated in macOS 10.15 - OpenAL is deprecated in favor of AVAudioEngine [-Wdeprecated-declarations]
/Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk/System/Library/Frameworks/OpenAL.framework/Headers/al.h:572:25: note: 'alSourceQueueBuffers' has been explicitly marked deprecated here
cgo-gcc-prolog:281:2: warning: 'alSourceRewind' is deprecated: first deprecated in macOS 10.15 - OpenAL is deprecated in favor of AVAudioEngine [-Wdeprecated-declarations]
/Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk/System/Library/Frameworks/OpenAL.framework/Headers/al.h:564:25: note: 'alSourceRewind' has been explicitly marked deprecated here
cgo-gcc-prolog:294:2: warning: 'alSourceStop' is deprecated: first deprecated in macOS 10.15 - OpenAL is deprecated in favor of AVAudioEngine [-Wdeprecated-declarations]
/Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk/System/Library/Frameworks/OpenAL.framework/Headers/al.h:561:25: note: 'alSourceStop' has been explicitly marked deprecated here
cgo-gcc-prolog:308:2: warning: 'alSourceUnqueueBuffers' is deprecated: first deprecated in macOS 10.15 - OpenAL is deprecated in favor of AVAudioEngine [-Wdeprecated-declarations]
/Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk/System/Library/Frameworks/OpenAL.framework/Headers/al.h:574:25: note: 'alSourceUnqueueBuffers' has been explicitly marked deprecated here
# github.com/hajimehoshi/ebiten/internal/graphicsdriver/metal/mtl
In file included from mtl.m:18:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk/System/Library/Frameworks/Metal.framework/Headers/Metal.h:9:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk/System/Library/Frameworks/Metal.framework/Headers/MTLTypes.h:8:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk/System/Library/Frameworks/Foundation.framework/Headers/Foundation.h:6:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk/System/Library/Frameworks/CoreFoundation.framework/Headers/CoreFoundation.h:60:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk/System/Library/Frameworks/CoreFoundation.framework/Headers/CFPropertyList.h:17:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk/System/Library/Frameworks/CoreFoundation.framework/Headers/CFStream.h:20:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk/usr/include/dispatch/dispatch.h:63:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk/usr/include/os/object.h:111:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk/usr/include/objc/NSObject.h:10:
/Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk/usr/include/objc/objc.h:78:18: error: typedef redefinition with different types ('bool' vs 'signed char')
../../../go/pkg/mod/github.com/hajimehoshi/ebiten@v1.9.3/internal/graphicsdriver/metal/mtl/mtl.h:19:21: note: previous definition is here
# github.com/go-gl/glfw/v3.2/glfw
In file included from ../../../go/pkg/mod/github.com/go-gl/glfw@v0.0.0-20181213070059-819e8ce5125f/v3.2/glfw/c_glfw_darwin.go:8:
../../../go/pkg/mod/github.com/go-gl/glfw@v0.0.0-20181213070059-819e8ce5125f/v3.2/glfw/glfw/src/cocoa_window.m:989:9: warning: multiple methods named 'center' found [-Wobjc-multiple-method-names]
/Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk/System/Library/Frameworks/AppKit.framework/Headers/NSCollectionViewCompositionalLayout.h:604:19: note: using
/Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk/System/Library/Frameworks/AppKit.framework/Headers/NSWindow.h:340:1: note: also found

Hi @naymapl sorry for late reply, I'll look into this issue.

@skatiyar - do you have any news about arm64 build issue ?
I have one more question to you. How to change scale of game on hdpi system ? Game is super cool but little bit to small. Scale 1.5x or 2x will be much better on HDPi screen.
I found this code:
func (g *Game) Run() error {
	return ebiten.Run(func(screen *ebiten.Image) error {
		return g.update(screen)
	}, 712, 1220, 0.5, "PACMAN") // scale is kept to 0.5, for good rendering in retina.
}

So when I try to change it for code below this will be bigger window ??
func (g *Game) Run() error {
	return ebiten.Run(func(screen *ebiten.Image) error {
		return g.update(screen)
	}, 934, 1600, 0.5, "PACMAN") // scale is kept to 0.5, for good rendering in retina.
}

Thanks a lot for help and hope so you van fix it for arm64.

Problem is when i doing go get ./... on arm64
go get ./...                                                                                 2 ✘  16:00:28 
# github.com/hajimehoshi/oto
/Users/naymapl/go/pkg/mod/github.com/hajimehoshi/oto@v0.3.3/driver_openal.go:36:22: warning: 'alcOpenDevice' is deprecated: first deprecated in macOS 10.15 - OpenAL is deprecated in favor of AVAudioEngine [-Wdeprecated-declarations]
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/OpenAL.framework/Headers/alc.h:209:38: note: 'alcOpenDevice' has been explicitly marked deprecated here
/Users/naymapl/go/pkg/mod/github.com/hajimehoshi/oto@v0.3.3/driver_openal.go:40:11: warning: 'alcCloseDevice' is deprecated: first deprecated in macOS 10.15 - OpenAL is deprecated in favor of AVAudioEngine [-Wdeprecated-declarations]
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/OpenAL.framework/Headers/alc.h:211:38: note: 'alcCloseDevice' has been explicitly marked deprecated here
/Users/naymapl/go/pkg/mod/github.com/hajimehoshi/oto@v0.3.3/driver_openal.go:44:22: warning: 'alcCreateContext' is deprecated: first deprecated in macOS 10.15 - OpenAL is deprecated in favor of AVAudioEngine [-Wdeprecated-declarations]
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/OpenAL.framework/Headers/alc.h:191:38: note: 'alcCreateContext' has been explicitly marked deprecated here
/Users/naymapl/go/pkg/mod/github.com/hajimehoshi/oto@v0.3.3/driver_openal.go:48:11: warning: 'alcGetError' is deprecated: first deprecated in macOS 10.15 - OpenAL is deprecated in favor of AVAudioEngine [-Wdeprecated-declarations]
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/OpenAL.framework/Headers/alc.h:218:38: note: 'alcGetError' has been explicitly marked deprecated here
/Users/naymapl/go/pkg/mod/github.com/hajimehoshi/oto@v0.3.3/driver_openal.go:52:4: warning: 'alcMakeContextCurrent' is deprecated: first deprecated in macOS 10.15 - OpenAL is deprecated in favor of AVAudioEngine [-Wdeprecated-declarations]
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/OpenAL.framework/Headers/alc.h:193:38: note: 'alcMakeContextCurrent' has been explicitly marked deprecated here
/Users/naymapl/go/pkg/mod/github.com/hajimehoshi/oto@v0.3.3/driver_openal.go:56:4: warning: 'alcDestroyContext' is deprecated: first deprecated in macOS 10.15 - OpenAL is deprecated in favor of AVAudioEngine [-Wdeprecated-declarations]
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/OpenAL.framework/Headers/alc.h:199:38: note: 'alcDestroyContext' has been explicitly marked deprecated here
cgo-gcc-prolog:152:2: warning: 'alBufferData' is deprecated: first deprecated in macOS 10.15 - OpenAL is deprecated in favor of AVAudioEngine [-Wdeprecated-declarations]
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/OpenAL.framework/Headers/al.h:601:25: note: 'alBufferData' has been explicitly marked deprecated here
cgo-gcc-prolog:166:2: warning: 'alDeleteBuffers' is deprecated: first deprecated in macOS 10.15 - OpenAL is deprecated in favor of AVAudioEngine [-Wdeprecated-declarations]
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/OpenAL.framework/Headers/al.h:595:25: note: 'alDeleteBuffers' has been explicitly marked deprecated here
cgo-gcc-prolog:180:2: warning: 'alDeleteSources' is deprecated: first deprecated in macOS 10.15 - OpenAL is deprecated in favor of AVAudioEngine [-Wdeprecated-declarations]
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/OpenAL.framework/Headers/al.h:501:25: note: 'alDeleteSources' has been explicitly marked deprecated here
cgo-gcc-prolog:194:2: warning: 'alGenBuffers' is deprecated: first deprecated in macOS 10.15 - OpenAL is deprecated in favor of AVAudioEngine [-Wdeprecated-declarations]
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/OpenAL.framework/Headers/al.h:592:25: note: 'alGenBuffers' has been explicitly marked deprecated here
cgo-gcc-prolog:208:2: warning: 'alGenSources' is deprecated: first deprecated in macOS 10.15 - OpenAL is deprecated in favor of AVAudioEngine [-Wdeprecated-declarations]
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/OpenAL.framework/Headers/al.h:498:25: note: 'alGenSources' has been explicitly marked deprecated here
cgo-gcc-prolog:222:2: warning: 'alGetSourcei' is deprecated: first deprecated in macOS 10.15 - OpenAL is deprecated in favor of AVAudioEngine [-Wdeprecated-declarations]
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/OpenAL.framework/Headers/al.h:530:25: note: 'alGetSourcei' has been explicitly marked deprecated here
cgo-gcc-prolog:238:35: warning: 'alGetString' is deprecated: first deprecated in macOS 10.15 - OpenAL is deprecated in favor of AVAudioEngine [-Wdeprecated-declarations]
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/OpenAL.framework/Headers/al.h:382:34: note: 'alGetString' has been explicitly marked deprecated here
cgo-gcc-prolog:254:2: warning: 'alSourcePlay' is deprecated: first deprecated in macOS 10.15 - OpenAL is deprecated in favor of AVAudioEngine [-Wdeprecated-declarations]
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/OpenAL.framework/Headers/al.h:558:25: note: 'alSourcePlay' has been explicitly marked deprecated here
cgo-gcc-prolog:268:2: warning: 'alSourceQueueBuffers' is deprecated: first deprecated in macOS 10.15 - OpenAL is deprecated in favor of AVAudioEngine [-Wdeprecated-declarations]
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/OpenAL.framework/Headers/al.h:572:25: note: 'alSourceQueueBuffers' has been explicitly marked deprecated here
cgo-gcc-prolog:281:2: warning: 'alSourceRewind' is deprecated: first deprecated in macOS 10.15 - OpenAL is deprecated in favor of AVAudioEngine [-Wdeprecated-declarations]
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/OpenAL.framework/Headers/al.h:564:25: note: 'alSourceRewind' has been explicitly marked deprecated here
cgo-gcc-prolog:294:2: warning: 'alSourceStop' is deprecated: first deprecated in macOS 10.15 - OpenAL is deprecated in favor of AVAudioEngine [-Wdeprecated-declarations]
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/OpenAL.framework/Headers/al.h:561:25: note: 'alSourceStop' has been explicitly marked deprecated here
cgo-gcc-prolog:308:2: warning: 'alSourceUnqueueBuffers' is deprecated: first deprecated in macOS 10.15 - OpenAL is deprecated in favor of AVAudioEngine [-Wdeprecated-declarations]
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/OpenAL.framework/Headers/al.h:574:25: note: 'alSourceUnqueueBuffers' has been explicitly marked deprecated here
# github.com/go-gl/glfw/v3.2/glfw
In file included from /Users/naymapl/go/pkg/mod/github.com/go-gl/glfw@v0.0.0-20181213070059-819e8ce5125f/v3.2/glfw/c_glfw_darwin.go:8:
/Users/naymapl/go/pkg/mod/github.com/go-gl/glfw@v0.0.0-20181213070059-819e8ce5125f/v3.2/glfw/glfw/src/cocoa_window.m:989:9: warning: multiple methods named 'center' found [-Wobjc-multiple-method-names]
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/AppKit.framework/Headers/NSCollectionViewCompositionalLayout.h:604:19: note: using
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/AppKit.framework/Headers/NSWindow.h:340:1: note: also found
# github.com/hajimehoshi/ebiten/internal/graphicsdriver/metal/mtl
In file included from mtl.m:18:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/Metal.framework/Headers/Metal.h:9:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/Metal.framework/Headers/MTLTypes.h:8:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/Foundation.framework/Headers/Foundation.h:6:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/CoreFoundation.framework/Headers/CoreFoundation.h:60:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/CoreFoundation.framework/Headers/CFPropertyList.h:17:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/CoreFoundation.framework/Headers/CFStream.h:20:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/dispatch/dispatch.h:63:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/os/object.h:111:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/objc/NSObject.h:10:
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/objc/objc.h:78:18: error: typedef redefinition with different types ('bool' vs 'signed char')
/Users/naymapl/go/pkg/mod/github.com/hajimehoshi/ebiten@v1.9.3/internal/graphicsdriver/metal/mtl/mtl.h:19:21: note: previous definition is here


Harmony Hubs - Unavailable - 94.4

Version: 94.4
Component: Harmony Hub
Hub Version: 4.15.250
Throughout the day, my hubs randomly go to a status of unavailable.   I have been reading online that some folks have a workaround of syncing the hubs through an automation which bring them back online, but this doesn't work for me.   I have a ping sensor setup to also see if I can communicate with the hubs, and they never go offline.
The only way for me to get the hubs "online" is to restart Home Assistant.

Did it work before 0.94.4 and started happening with 0.94.4?

	I want to say it has been happening since the new websocket connection vs the XMPP method.   I saw that it was fixed in .85, but wasn’t paying attention to it enough to see if it was doing it.  I do know it has been disconnecting since a minimum of .90.

On Mon, Jul 8, 2019 at 7:43 AM -0700, "ehendrix23"<EMAIL_ADDRESS>wrote:
Did it work before 0.94.4 and started happening with 0.94.4?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I don't have the problems anymore since the fix was implemented a while ago, running stable here

Hello,  I have been watching this daily, and I am still having the issue up to the latest version.   I monitor the Harmony Hub with the ping service in HA, when the Hub goes to unavailable I am seeing that HA can still continuously ping the hub itself.  Restarting HA resolves the hub from being unavailable.

Hello, I have been watching this daily, and I am still having the issue up to the latest version. I monitor the Harmony Hub with the ping service in HA, when the Hub goes to unavailable I am seeing that HA can still continuously ping the hub itself. Restarting HA resolves the hub from being unavailable.

Can you enable debug logging in Home Assistant for following components:
aioharmony.hubconnector
aioharmony.harmonyclient
through the logger configuration
Thx.

home-assistant.log
Good morning,
Attached are the logs you requested.  I had 2 hubs go offline yesterday, the screenshots show the time, both on 08-05.

Looking in the log files it shows that the Web Socket is being closed (not by us) and then we start to reconnect again.
Do you use HASS.IO? Linux? Windows? Mac?
The issues we saw before were on HASS.IO and had to do with sockets not being closed automatically by the OS.

Hi!
It is running Hass.io in a docker environment w/ a Ubuntu 16 host.

The ping you have setup. Is that from Ununtu host then or from within the docker environment (I'm thinking the host but wanting to confirm).
Do you know how to setup a custom component?

	I believe it is from hass.io as I am using the ping component within.   I can setup a custom component.

On Tue, Sep 3, 2019 at 11:38 AM -0700, "ehendrix23"<EMAIL_ADDRESS>wrote:
The ping you have setup. Is that from Ununtu host then or from within the docker environment (I'm thinking the host but wanting to confirm).
Do you know how to setup a custom component?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

If you can setup a custom component for harmony (folder harmony in folder custom_components). Copy the existing files from the harmony component over and then update the manifest.json file, changing the aioharmony version from 0.1.11 to 0.1.13.
That would then already make it that you run with the latest non-XMPP version of aioharmony. Since 0.1.11 it includes some fixes around debug logging for connections and also a force cleanup of closed sockets upon closure.
Hopefully this will fix it, and if not at least provides some more debug information on why it is unable to reconnect.

I have modified the custom component and verified it is in use.  I'll let you know if/when it hiccups.  Thanks for your help!

This morning when I checked, all the hubs went offline around 6PM my time
home-assistant.log

Looking at the log files I can see that the connection is being closed (not by us but other end). Then a reconnect occurs which often is successful but sometimes fails. However during that timeframe the connection is only established for less then a minute and then it is closed again.
It seems that overall the network connection itself is not stable to the Hub resulting in this behavior.
When I Googled there seem to be a number of potential issues with Docker and network connections. Your connection is going from HASS through your docker container into your host, and from your host to your Hub over your router/switch. If any of these drops then you might end up with result you see.
I would see to use a network packet capture (i.e. WireShark) to trace the network between your host and your Hub, and also between your Docker container and your host and to look at what is being stated there in the packets when the issue occurs.
Feel free to provide the packet trace here and I can help looking into it. :-)
As a note, one of the things that was changed as well when going to Web Socket from XMPP is that when the connection is lost than the state is set to unavailable. Before the state in HASS would never be set to unavailable even if connection was lost. Hence now when there are connection issues it is actually being reported in HASS through the unavailable state whereas before with the XMPP implementation it was not.

	The confusing part, is my pings never stop or go offline from hassio to the hub, and once the hub goes unavailable in hassio, it never seems to come back until I restart hassio.   Does the component stop trying once going unavailable?

On Wed, Sep 4, 2019 at 1:03 PM -0700, "ehendrix23"<EMAIL_ADDRESS>wrote:
Looking at the log files I can see that the connection is being closed (not by us but other end). Then a reconnect occurs which often is successful but sometimes fails. However during that timeframe the connection is only established for less then a minute and then it is closed again.
It seems that overall the network connection itself is not stable to the Hub resulting in this behavior.
When I Googled there seem to be a number of potential issues with Docker and network connections. Your connection is going from HASS through your docker container into your host, and from your host to your Hub over your router/switch. If any of these drops then you might end up with result you see.
I would see to use a network packet capture (i.e. WireShark) to trace the network between your host and your Hub, and also between your Docker container and your host and to look at what is being stated there in the packets when the issue occurs.
Feel free to provide the packet trace here and I can help looking into it. :-)
As a note, one of the things that was changed as well when going to Web Socket from XMPP is that when the connection is lost than the state is set to unavailable. Before the state in HASS would never be set to unavailable even if connection was lost. Hence now when there are connection issues it is actually being reported in HASS through the unavailable state whereas before with the XMPP implementation it was not.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Ping itself uses a different protocol. Further, ping is not constantly connected but just does it on a regular basis.
Here is for example some entries from the log file showing the disconnect, reconnect, then disconnect again, and reconnect again:
`
2019-09-03 17:45:00 DEBUG (MainThread) [aioharmony.hubconnector] <IP_ADDRESS>: Response payload: None
2019-09-03 17:45:00 DEBUG (MainThread) [aioharmony.hubconnector] <IP_ADDRESS>: Web socket closed
2019-09-03 17:45:00 DEBUG (MainThread) [aioharmony.hubconnector] <IP_ADDRESS>: Listener stopped.
2019-09-03 17:45:00 DEBUG (MainThread) [aioharmony.hubconnector] <IP_ADDRESS>: Connection closed, reconnecting
2019-09-03 17:45:00 DEBUG (MainThread) [aioharmony.hubconnector] <IP_ADDRESS>: Closing sessions
2019-09-03 17:45:01 DEBUG (MainThread) [aioharmony.hubconnector] <IP_ADDRESS>: Starting connect.
2019-09-03 17:45:01 DEBUG (MainThread) [aioharmony.hubconnector] <IP_ADDRESS>: Connecting for hub 12313977
2019-09-03 17:45:01 DEBUG (MainThread) [aioharmony.hubconnector] <IP_ADDRESS>: Connected to hub 12313977
2019-09-03 17:45:01 DEBUG (MainThread) [aioharmony.hubconnector] <IP_ADDRESS>: Listener started
2019-09-03 17:45:29 DEBUG (MainThread) [aioharmony.hubconnector] <IP_ADDRESS>: Response payload: None
2019-09-03 17:45:29 DEBUG (MainThread) [aioharmony.hubconnector] <IP_ADDRESS>: Web socket closed
2019-09-03 17:45:29 DEBUG (MainThread) [aioharmony.hubconnector] <IP_ADDRESS>: Listener stopped.
2019-09-03 17:45:29 DEBUG (MainThread) [aioharmony.hubconnector] <IP_ADDRESS>: Connection closed, reconnecting
2019-09-03 17:45:29 DEBUG (MainThread) [aioharmony.hubconnector] <IP_ADDRESS>: Closing sessions
2019-09-03 17:45:30 DEBUG (MainThread) [aioharmony.hubconnector] <IP_ADDRESS>: Starting connect.
2019-09-03 17:45:30 DEBUG (MainThread) [aioharmony.hubconnector] <IP_ADDRESS>: Connecting for hub 12313977
`
First we receive something but there was no payload (None).
Next the Web socket is closed (that line is only put out if something else closed the web socket), and then the listener is stopped (as we're not connected anymore).
Then you see that we're going to go for reconnecting. We first ensure everything is cleaned up and then start the connect (Starting connect) and "Connecting for hub ...".
Then you can see we're connected and listener is started again. Back in business.
Then at 14:45:29 we again get the Response payload None. And we go back through the same thing.
Hence we loose the connection, go for reconnect which is successful, but then less then 30 seconds later the connection is dropped again.
Starting at 18:01 you can see that this is starting to happen for the Hubs with IP 41 and 42 as well.
If you for example look starting at 18:02:29 for hub with IP 41 you can just see a whole list of the same thing happening over and over again. Connection is lost, reconnect is initiated and successful, then about 30 seconds later the connection is dropped again.
At 18:06:28 you for example see a failure trying to establish the connection, here the connection is reset by peer.
And at 18:06:34 thee is a time out when trying to establish the connection.
However, irrespective we keep on trying to connect back to Hub and there is no limit on how many times we try.
But because the connection is dropped so quickly again, the state is not set back to available each time and hence it might seem like it stays unavailable.
Upon reconnect, what happens is that we 1st wait for 1 second after the connection is lost. If it fails then we wait for a second again before re-trying. After that we keep on doubling how long we wait with a maximum of 30 seconds. Thus if 1st reconnect fails then it is: 1 second, 2, 4, 8, 16, 30 seconds between each. After that it is always 30 seconds between retries.


[task] default yes in destroy task

What does this PR do?
Default destroy without asking for confirmation on destroy task
Which scenarios this will impact?
All
Motivation
Personally I always want to destroy the stack I have in my state, no need to confirm
Additional Notes

/merge


commands in terminal plugin only return echo + spinning gear

Darwin 1.0 RC
When I enter a command in the terminal plugin, I get a return of my command + spinning gear, but nothing else happens

Fixed in #276


Simplemde dependency not loaded when bundle is used inside app

Shall we include this package (including CSS) in the dependencies and bundle it? If it is big, maybe a second bundle or some other way to import it (to prevent importing it by default) would be nice.
E.g.
// without editor
import "@eox/storytelling

// with editor
import @eox/storytelling/dist/storytelling-editor.js
import "@eox/storytelling

// or
import @eox/storytelling/dist/storytelling-editor.js

I think as we have to relatively separate functions, one only for rendering and one if you want to provide an editor, having separate packages to make the "rendering" only version lighter makes sense to me.
Not sure how much effort this change would mean though.


🐞 When typing Chinese, sometimes pressing a key will get several more letters

Description
When typing Chinese, sometimes pressing a key will get several more letters,For example, pressing one m will get two m's,When you press the Delete key, text is added instead of deleted
To Reproduce

Change the input method to Chinese
Slowly type the text, press one m, then another m, and you will find that three m's appear
Press the Delete key and you will find that you are adding text instead of deleting text

Expected Behavior
In the case of Chinese input method, input a few words to get a few words, press the delete key can be deleted normally
Version Information
CodeEdit: [V0.1.0]
macOS: [14.5]
Xcode: [15.4]
Additional Context
No response
Screenshots
No response

This may possibly be related to this...

https://github.com/CodeEditApp/CodeEditTextView/issues/36


Repalce async on neo-async

Before filing issues, please check the following points first:

[x] Have a look at https://github.com/wycats/handlebars.js/blob/master/CONTRIBUTING.md
[x] Read the FAQ at https://github.com/wycats/handlebars.js/blob/master/FAQ.md
[x] Use the jsfiddle-template at https://jsfiddle.net/9D88g/47/ to reproduce problems or bugs

It is will improve perf. I can do PR :+1:

I know you opened this issue a long while ago. I somehow had the impression that neo-async was working with newer NodeJS version only, so it would be a breaking change to include it.
But it seems like I was wrong. At least I wasn't able to find a "const" keyword in the source.
Thank you for this issue, I have made a branch now.


Bump Node from v16 to v20

Description

Increased Node from v16 > v20 to address deprecation warning.

Related Issue

Fix #103

Motivation and Context

Node 16 has reached its end of life, prompting us to initiate its deprecation process for GitHub Actions. Our plan is to transition all actions to run on Node 20 by Spring 2024. We will actively monitor the migration's progress and gather community feedback before finalizing the transition date. Starting October 23rd, workflows containing actions running on Node 16 will display a warning to alert users about the upcoming migration.

How Has This Been Tested?

Tested with AsBuiltReport.Veeam.VB365 release workflow

https://github.com/AsBuiltReport/AsBuiltReport.Veeam.VB365/blob/d0ea9a1076d92c12d0f3129c2514cfdac1967d27/.github/workflows/Release.yml#L40
Log:

job-logs.txt

Screenshots (if appropriate):
Pre Changes:

Post Changes:

Twitter/X message:

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.

Thanks for the PR, but it needs a bit more work to bump node 20.
I just released the v2 of this action:

test: https://x.com/ManuEomm/status/1794648059990737188
https://github.com/Eomm/why-don-t-you-tweet/releases/tag/v2.0.0
https://github.com/Eomm/why-don-t-you-tweet/actions/runs/9241920083/job/25424055254

Thanks for pushing it


The spectrum ids in the mzIdentML file are not correct Thermo ids

Hi,
I was trying to build a library in Skyline and received an error. Their support people say that the spectrum ids in the mzIdentML file are not correct Thermo ids: "scan=1234".
It is listed under issue ID 648 on Skyline support page.
Can you check this? Are you able to create a spectrum library from results from MetaMorpheus?
Thanks,
Yishai

thanks for creating this issue. I hope that we can look at it today. Here is a link to skyline issue https://skyline.ms/issues/home/issues/details.view?issueId=648

Ok, I think I understand the problem. The Thermo scan IDs in the mzID file are not formatted properly, I guess.
Instead of: "scan=1234"
We should use: "controllerType=1 controllerNumber=0 scan=1234"
This scan ID is correct in our written mzML files but not our mzID files, apparently. I'll test to see if I can fix this and get back to you, hopefully today.

I got Skyline to read our mzID with the following steps:

Change .mzID to .mzid
Find+Replace:
Find: spectrumID="scan=
Replace with: spectrumID="controllerType=0 controllerNumber=1 scan=
Put the .mzML file into the same directory as the .mzID file

I'll see about correcting our scan headers so you don't have to do step 2.

Thanks for your patience. I've fixed this in #1685 and it will be in the next release


[Dialog] Element with tabIndex -1 is not automatically focused

Bug report
The Dialog ARIA pattern linked from the radix docs recommends setting tabIndex="-1" on static elements in some scenarios. For example:

If content is large enough that focusing the first interactive element could cause the beginning of content to scroll out of view, it is advisable to add tabindex="-1" to a static element at the top of the dialog, such as the dialog title or first paragraph, and initially focus that element.

However, the autofocus behavior of the dialog component excludes elements with tabindex="-1".
Current Behavior

The first keyboard focusable element receives focus on dialog open.
Expected behavior

The first focusable element receives focus on dialog open, including those with tabIndex={-1}.
Reproducible example
https://codesandbox.io/s/strange-paper-pxoh8l?file=/src/App.tsx
Suggested solution

Update FocusScope to allow elements with tabindex="-1" for this use case.
Additional context

Overriding this behavior via onOpenAutoFocus isn't ideal because it disables the default focus behavior, which may still be desired for some instances. The override may be simple enough when using radix dialog directly in an app, but it adds some complexity when using radix dialog in a shared component library.
Your environment

Software
Name(s)
Version

Radix Package(s)
@radix-ui/react-dialog
1.0.3

React
n/a
17.0.2

Browser
Chrome
111.0.5563.64

Assistive tech

Node
n/a

npm/yarn
yarn
1.22.19

Operating System
Mac OS
12.6

If content is large enough that focusing the first interactive element could cause the beginning of content to scroll out of view, it is advisable to add tabindex="-1" to a static element at the top of the dialog, such as the dialog title or first paragraph, and initially focus that element.

This is a suggestions made for authors in general, and isn't something that can be achieved at the library level, because it requires case-by-case attention.
The reason they advise tabIndex="-1" is specifically so it's not "tabbable" but is "focusable" programatically for the purpose of accessibility.
Hence, what Radix does by default is the expected behaviour.
Overriding on a case by case basis using onOpenAutoFocus is the correct solution here.


Is it possible to add the "all sizes" button too?

Hi,
Google removes "view image" button but "size" button too. Is it possible to add the "All sizes" button too?
Thank you.

Seems resolved in #44.


confusing search tags

It's just me or the tag list looks like a main menu?
I would like two share two alternatives if you don't mind

Remove the tags from there and show them in the search-box when the there is no query.
or
Make it clear that those links are search tags. Something like this:

Hmm, some analytics:

tag searches are about 30% of sessions and about 25% of all searches
most popular search terms heavily influenced by the tags:

layout
button
form
paper
toolbar
calendar
paper-
routing
iron
emoji

I'd be curious to see what 1. looks like, do you want to try it out @pdgago?

cool, i'll do! 😄


Add proper markdown to 'main'

What:
I have changed "main" to main.
Why:
Below the 'main' section, in the 'master' section, master is used, not "master".

@a2br Thanks so much for opening a PR! I'll get this triaged for review 💖

Still waiting for review.

@a2br Thanks for your patience! Our small team is working our way through reviewing all of the amazing contributions ✨

Ok! I can still revert the commits on the translation files.

Ok! I can still revert the commits on the translation files.

I hadn't noticed that they were in separate commits. That would be great. Many thanks.

Done! ✅

@a2br 👋🏻 Bonjour 😄
Since I merged your pull request, I've been getting email notifications about Actions workflow failures in your fork. This puzzled me. I looked into it.
I think you enabled Actions in the settings for your fork. The failing workflow synchronizes the docs repository with our internal systems. It uses a token that your fork does not have access to. To avoid using up your Actions minutes, you should turn off actions in your fork of the docs repo (Disabling or limiting GitHub Actions for a repository).
I raised this with the docs engineering team and they will update the synchronization workflow so that it does not run on forks.  The work is not scheduled yet, so it would be good to turn off actions for this repository.

Actions are now disabled in my fork ☑

💐 Thank you. I hope that this hasn't cause problems for you in your fork.
We usually create a feature branch from main with the changes we want to merge into the main branch of the docs repository. This would also help avoid problems like this in any future changes you propose to the docs repository.

Yes, that's what I usually do. Since the change here was very small, I thought i'd just delete my fork and re-fork if needed in the future. Thanks for the reminder though.

That makes sense. Some of the contributors to this repository are just starting out with git and GitHub, so I thought I should mention it. It's great to hear that you already knew.
Have a great weekend 👋🏻


add username claim to token used for testing

What does this pull request do?
add username claim to token used for testing
What is the intent behind these changes?
ensures that the username claim is available to the backend when running pact tests.

Most annoying thing ever, but is it a username, or the user's name? If the first, I'd suggest all lowercase, but if it's the second I'd say camel case (like you've done).

hmm. well it is the former. but the claim is named user_name in the real tokens ...


Command PhaseScriptExecution failed with a nonzero exit code

Description
Getting this issue only when building to real devices using Xcode 15.1 and any version of iOS 17. Works with no issues when building to simulators.
Steps to reproduce

yarn install
run Xcode start to a targeted device

React Native Version
0.73.1
Affected Platforms
Runtime - iOS
Output of npx react-native info
System:
  OS: macOS 13.6.3
  CPU: (8) x64 Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
  Memory: 299.42 MB / 16.00 GB
  Shell:
    version: 3.2.57
    path: /bin/bash
Binaries:
  Node:
    version: 18.18.2
    path: /usr/local/bin/node
  Yarn:
    version: 1.22.17
    path: /usr/local/bin/yarn
  npm:
    version: 9.2.0
    path: ~/.npm-packages/bin/npm
  Watchman: Not Found
Managers:
  CocoaPods:
    version: 1.12.1
    path: /usr/local/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 23.2
      - iOS 17.2
      - macOS 14.2
      - tvOS 17.2
      - watchOS 10.2
  Android SDK: Not Found
IDEs:
  Android Studio: 2023.1 AI-231.9392.1.2311.11076708
  Xcode:
    version: 15.1/15C65
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: <IP_ADDRESS>
    path: /usr/bin/javac
  Ruby:
    version: 2.6.10
    path: /usr/bin/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.2.0
    wanted: 18.2.0
  react-native:
    installed: 0.73.1
    wanted: 0.73.1
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: true
  newArchEnabled: false

Stacktrace or Logs
No logs, only Command PhaseScriptExecution failed with a nonzero exit code issue.

Reproducer
Brand new RN project
Screenshots and Videos
No response

I used the following code to diagnose the error on the node_modules/react-native/scripts/react-native-xcode.sh
err_report() {
    echo "Error on line $1"
}

trap 'err_report $LINENO' ERR

The function err_report noticed to me that the error was found on the for num in 0 1 2 3 4 5 6 7 8.
This for was created to get the local ip address of the metro server.
As you can see below, I commented the entire for and replaced with the new command, and my build is working fine now.
IP=$(ifconfig | grep -E "([0-9]{1,3}\.){3}[0-9]{1,3}" | grep -v <IP_ADDRESS> | head -1 | awk '{ print $2 }')
  # for num in 0 1 2 3 4 5 6 7 8; do
  #   IP=$(ipconfig getifaddr en${num})
  #   if [ ! -z "$IP" ]; then
  #     break
  #   fi
  # done

Thanks @rafaels-dev, it turns out that my entry file was causing the issue (index.tsx). Bundling in RN only considers index.js. That was my issue, appreciate you taking your time trying to help!


BUG: Fix Windows install paths

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Fixes #1

File paths on Windows need to be $PREFIX/Library.
cmake targets contain incorrect paths which needs to be patched for Windows

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found some lint.
Here's what I've got...
For recipe/meta.yaml:

❌ Selectors are suggested to take a <two spaces>#<one space>[<expression>] form. See lines [31, 32, 33, 34, 35]

For recipe/meta.yaml:

ℹ It looks like the 'libcudss-commlayer-nccl' output doesn't have any tests.
ℹ It looks like the 'libcudss-commlayer-mpi' output doesn't have any tests.
ℹ The recipe is not parsable by parser conda-souschef (grayskull). Your recipe may not receive automatic updates and/or may not be compatible with conda-forge's infrastructure. Please check the logs for more information and ensure your recipe can be parsed.

This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12303936871. Examine the logs at this URL for more detail.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.


⚠ Samsung has degraded performance

In 3f139fb, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2744 ms

Resolved: Samsung performance has improved in 3d16c21.


How about support for verbs/commands?

Hi.
I like this library a lot! But one thing I'm missing is support for "verbs". Like when the first argument on command line is a verb which then has options specific to that verb. Similar to git commit -m "message".
I put the code below together as a proof of concept. Though, looking at it now I think I would have preferred to have the Option attribute assigned to parameters of the method instead of a dedicated class, but that would require some more intrusive changes. Is this something you would be interested in exploring or is totally out of scope for this library?
using System;
using System.Linq;
using System.Reflection;

using CommandLine;

namespace SampleApp
{
    public class VerbProgram
    {
        private static void Main(string[] args)
        {
            //MyVerbs.FooOptions options = new MyVerbs.FooOptions();
            //if (!CommandLineParser.Default.ParseArguments(
            //    new[] { "--flag" }, options))
            //{
            //    Environment.Exit(1);
            //}

            MyVerbs verbs = new MyVerbs();
            if (!VerbParser.Default.ParseArguments(
                new[] { "foo", "--flag" }, verbs))
            {
                Environment.Exit(1);
            }

            Environment.Exit(0);
        }
    }

    internal class MyVerbs
    {
        internal class FooOptions : CommandLineOptionsBase
        {
            [Option("f", "flag", Required = true)]
            public bool Flag { get; set; }
        }

        [Verb]
        public void Foo(FooOptions options)
        {
            Console.WriteLine(options.Flag);
        }
    }

    public class VerbAttribute : Attribute
    {
        /// <summary>
        /// By default the name of the verb is a lowercase version of the
        /// method name, set this property to override.
        /// </summary>
        public string Name { get; set; }

        public string HelpText { get; set; }
    }

    internal class VerbParser
    {
        public static VerbParser Default = new VerbParser();
        internal ICommandLineParser ArgumentParser = CommandLineParser.Default;

        public bool ParseArguments(string[] args, object verbs)
        {
            // store name of verb and remove it from args
            var verbName = args[0];
            args = args.Skip(1).ToArray();

            // find verb method
            Pair<MethodInfo, VerbAttribute> verb = null;
            foreach (Pair<MethodInfo, VerbAttribute> pair in
                ReflectionUtil.RetrieveMethods<VerbAttribute>(verbs))
            {
                string name = pair.Right.Name;
                if (string.IsNullOrEmpty(name))
                {
                    name = pair.Left.Name.ToLower();
                }
                if (verbName.Equals(name))
                {
                    verb = pair;
                    break;
                }
            }
            if (verb == null)
            {
                return false; // verb not found
            }

            object options = Activator.CreateInstance(
                verb.Left.GetParameters()[0].ParameterType);
            if (!ArgumentParser.ParseArguments(args, options))
            {
                return false; // couldnt parse verb arguments
            }

            verb.Left.Invoke(verbs, new[] {options});
            return true;
        }
    }
}

@DriverEntry may be you're quoting at stable-1.9.*? Some time passed... Now I don't remember the whole story and why that route was favored. The interesting thing of having source code is forking for PR or forking for private use or whatever you want, isn't it? Also my absence to the project was not determinant since someone else can fork and maintain it...
Backing to the problem. If you look at 2.0 (which as I said is an attempt to simplify all inside/out) you define X normal types for parsing and the parser will give you the instance associated with the correct verb.
Why this architecture in 2.0 pre-rel? Because apps that uses verbs are similar to the one which not use one, making things easy.
Hope all this, helped! And thank you for your interest in this project and for comments that ALWAYS help.
R. Giacomo


eth_getBalance returns 0 balance instead of 1

Describe the bug
Currently the rpc-compat hive test for eth_getBalance/get-balance-blockhash fails, returning the incorrect balance:
>>  {"jsonrpc":"2.0","id":1,"method":"eth_getBalance","params":["0xaa00000000000000000000000000000000000000","0x898753d8fdd8d92c1907ca21e68c7970abd290c647a202091181deec3f30a0b2"]}
<<  {"jsonrpc":"2.0","result":"0x0","id":1}
response differs from expected:
 {
   "id": 1,
   "jsonrpc": "2.0",
-  "result": "0x0"
+  "result": "0x1"
 }

Steps to reproduce
Run hive:
./hive --client reth --sim ethereum/rpc-compat --sim.limit "/eth_getBalance"

Node logs
No response
Platform(s)
No response
What version/commit are you on?
No response
Code of Conduct

[X] I agree to follow the Code of Conduct

Did some debugging, and we the call is failing here, returning Ok(None):
https://github.com/paradigmxyz/reth/blob/2ce72c51e10640e28def1dc8a51a01ac9021fe23/crates/storage/provider/src/providers/state/historical.rs#L43-L51
custom traces:
2023-03-24T00:34:40.422816Z TRACE connection{remote_addr=<IP_ADDRESS>:58894 conn_id=1}:method_call{method="eth_getBalance"}: Serving eth_getBalance address=0xaa00000000000000000000000000000000000000 block_number=Some(Hash(BlockHash { block_hash: 0x898753d8fdd8d92c1907ca21e68c7970abd290c647a202091181deec3f30a0b2, require_canonical: None }))
2023-03-24T00:34:40.422846Z TRACE connection{remote_addr=<IP_ADDRESS>:58894 conn_id=1}:method_call{method="eth_getBalance"}: Getting balance for address address=0xaa00000000000000000000000000000000000000
2023-03-24T00:34:40.422857Z TRACE connection{remote_addr=<IP_ADDRESS>:58894 conn_id=1}:method_call{method="eth_getBalance"}: Getting basic account information address=0xaa00000000000000000000000000000000000000
2023-03-24T00:34:40.422860Z TRACE connection{remote_addr=<IP_ADDRESS>:58894 conn_id=1}:method_call{method="eth_getBalance"}: Using history key history_key=ShardedKey { key: 0xaa00000000000000000000000000000000000000, highest_transition_id: 1 }
2023-03-24T00:34:40.422874Z TRACE connection{remote_addr=<IP_ADDRESS>:58894 conn_id=1}:method_call{method="eth_getBalance"}: Could not find account info


Water Drinking Appliance 6320882A (425) 无法正常工作

HA版本
2024.3.3
集成版本
0.3.18
设备类型及型号
Water Drinking Appliance 6320882A (425)
使用的App
美的美居
问题详细描述
所有额外传感器都不可用。

The logs
7021372841026] Status update: {'available': False}
2024-03-25 15:29:05.580 DEBUG (净水机) [custom_components.midea_ac_lan.midea.core.device] [177021372841026] Connecting to <IP_ADDRESS>:6444
2024-03-25 15:29:05.591 DEBUG (净水机) [custom_components.midea_ac_lan.midea.core.device] [177021372841026] Connected
2024-03-25 15:29:05.591 DEBUG (净水机) [custom_components.midea_ac_lan.midea.core.device] [177021372841026] Handshaking
2024-03-25 15:29:05.648 DEBUG (净水机) [custom_components.midea_ac_lan.midea.core.device] [177021372841026] Authentication success
2024-03-25 15:29:05.649 DEBUG (净水机) [custom_components.midea_ac_lan.midea.core.device] [177021372841026] Sending: {'header': 'aa0ced00000000000003', 'body': '0001', 'message type': '03', 'body type': '00'}
2024-03-25 15:29:15.662 DEBUG (净水机) [custom_components.midea_ac_lan.midea.core.device] [177021372841026] Does not supports the protocol MessageQuery, ignored
2024-03-25 15:29:15.663 DEBUG (净水机) [custom_components.midea_ac_lan.midea.core.device] [177021372841026] Refresh status is timed out
2024-03-25 15:29:15.663 DEBUG (净水机) [custom_components.midea_ac_lan.midea.core.device] [177021372841026] Status update: {'available': False}

+1

2024-08-11 23:02:22.378 ERROR (净水机) [custom_components.midea_ac_lan.midea.core.device] [210006729982883] Unknown error :/config/custom_components/midea_ac_lan/midea/core/device.py, 348, RefreshFailed()

2024-08-11 23:01:42.730 WARNING (MainThread) [homeassistant.helpers.frame] Detected code that calls async_forward_entry_setup for integration midea_ac_lan with title: 净水机 and entry_id: xxx, during setup without awaiting async_forward_entry_setup, which can cause the setup lock to be released before the setup is done. This will stop working in Home Assistant 2025.1. Please report this issue.
Stack (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in _run_code
File "/usr/src/homeassistant/homeassistant/main.py", line 223, in
sys.exit(main())
File "/usr/src/homeassistant/homeassistant/main.py", line 209, in main
exit_code = runner.run(runtime_conf)
File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run
return loop.run_until_complete(setup_and_run_hass(runtime_config))
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 674, in run_until_complete
self.run_forever()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 641, in run_forever
self._run_once()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1990, in _run_once
handle._run()
File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
self._context.run(self._callback, *self._args)
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2161, in async_forward_entry_setup
_report_non_awaited_platform_forwards(entry, "async_forward_entry_setup")
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1201, in _report_non_awaited_platform_forwards
report(
File "/usr/src/homeassistant/homeassistant/helpers/frame.py", line 151, in report
_LOGGER.warning(msg, stack_info=True)


Adding Jupyter Notebooks

Some Todos for adding Jupyter Notebooks to the Site:

Clean up the exported file from nbconvert! My tiny notebooks don't need 5000 lines of CSS Code
Custom CSS for the Exported HTML Docs that integrate notebooks with the current theme of the website
Easily Cloneable Article Page that just needs a new link to be dropped in each time to post an article

Update 3/5/24

Markdown Files are now working with a combination of react-markdown, remark-math, rehype-katex, and highlight.js
Custom CSS can be found in the CodeBlock.css and MdArticles.module.css files


SeLinux error

Bug Report
Following error found:
time->Thu Aug 25 14:55:11 2022
type=AVC msg=audit(1661435711.300:4401): avc:  denied  { read } for  pid=70032 comm="tar" name="preloaded-images-k8s-v17-v1.23.3-docker-overlay2-amd64.tar.lz4" dev="dm-0" ino=25573826 scontext=system_u:system_r:container_t:s0:c330,c807 tcontext=unconfined_u:object_r:user_home_t:s0 tclass=file permissive=0

Current Behavior
On a newly built Fedora system I see the above error when run make quickstart in audit log
Possible Solution
Standard solution resolves this issue:
ausearch -c 'tar' --raw | audit2allow -M my-tar
semodule -X 300 -i my-tar.pp

Steps to Reproduce
With newly build Fedora 36 run make quickstart
Build will take a while and fail with Kyverno.

Confirmed this caused by minikube


Issue 1300

Adresses this issue : https://github.com/mc-server/MCServer/issues/1300

Again, why aren't we doing the calculation on each tick? This way we present information that is almost always wrong. Was there a performance problem with a per-tick calculation? I have a feeling that the chrono methods you use eat up way more CPU than the simple calculation would have.
Also, your solution hides the GetSpeed() and SetSpeed() functions from cEntity, which is rather unfortunate, especially when it comes to plugins - they expect consistent behavior.
Not to mention that your calculation is wrong, you're doing abs() on the difference in positions (and an integral one), thus mis-representing the speed vector.

@papatwika Any updates on this?

This is totally outdated. Closing for now


Building Spark-TSNE Behind Corporate Firewall

Hi,
I am unable to download plugins etc from behind the firewall but I am very interested in looking at this code. Is it possible to provide an assembled jar? I am unable to convince our IT here to open up access to all the sites the build process is using.
Thank you for your help!

Maybe you can build an assembly jar on your personal laptop or on an AWS instance? That'd give you flexibility if you need to make any changes to the code.

Unfortunately I am not allowed to get anything into the company like that either. Just to get your code I had to go through a unit which looked your github site, checked out license and downloaded it and made it available on an internal site which I then I downloaded from.
Sent from my iPhone
On Jan 14, 2017, at 9:50 PM, Forest Fang <notifications<EMAIL_ADDRESS>wrote:
Maybe you can build an assembly jar on your personal laptop or on an AWS instance? That'd give you flexibility if you need to make any changes to the code.

You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/saurfang/spark-tsne/issues/6#issuecomment-272669668, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AJ4kyG6kUekgX3DpAzozaDVB9kkvD3F1ks5rSYl4gaJpZM4Lh5Xo.


Bump fog version

fixes #69

I just realized i have merge permissions here.
Can i go ahead and merge this?
cc/ @chrisroberts @slyness @agoddard

This is an attribute which you can override with a role or your own recipe. Not really any need to rush a merge on something like this. I will be looking at going through open issues and PRs this Friday.

if this is a requirement of fog-aws, why is not enforcing minimum required fogorfog-core`?

fog is a meta gem for all providers. fog-aws depends on fog-core which does not depend on fog at all.
There is a relation from fog to fog-aws but there is none from fog-aws to fog.
Force core versions isn't really a good idea since we have a lot of providers that aren't much of active. If each provider force a specific version of fog-core, fog will just break.
This scenario give us 2 possible solutions:

Depend only of fog-aws (which we already have an open PR #67)
Bump fog version from time to time. (this PR)

As long as it's an AWS-specific feature I think we should depend on fog-aws or if we want to get rid of it, migrate to aws-sdk

@slyness  , I get error when I try to override fog version in role:
[2015-11-16T08:44:44-08:00] INFO: package[libxslt-dev] is a virtual package, actually acting on package[libxslt1-dev]

================================================================================
Error executing action `install` on resource 'chef_gem[fog]'
================================================================================

Mixlib::ShellOut::ShellCommandFailed
------------------------------------
Expected process to exit with [0], but received '1'
---- Begin output of /opt/chef/embedded/bin/gem install fog -q --no-rdoc --no-ri -v "1.30" ----
STDOUT:
STDERR: ERROR:  Error installing fog:
	fog-google requires Ruby version >= 2.0.
---- End output of /opt/chef/embedded/bin/gem install fog -q --no-rdoc --no-ri -v "1.30" ----
Ran /opt/chef/embedded/bin/gem install fog -q --no-rdoc --no-ri -v "1.30" returned 1

Resource Declaration:
---------------------
# In /tmp/chef-solo/site-cookbooks/route53/recipes/default.rb

 22: chef_gem "fog" do
 23:   action :install
 24:   version node['route53']['fog_version']
 25: end
 26:

Compiled Resource:
------------------
# Declared in /tmp/chef-solo/site-cookbooks/route53/recipes/default.rb:22:in `from_file'

chef_gem("fog") do
  provider Chef::Provider::Package::Rubygems
  action [:install]
  retries 0
  retry_delay 2
  guard_interpreter :default
  package_name "fog"
  version "1.30"
  timeout 900
  gem_binary "/opt/chef/embedded/bin/gem"
  cookbook_name :route53
  recipe_name "default"
end

================================================================================
Recipe Compile Error in /tmp/chef-solo/site-cookbooks/route53/recipes/default.rb
================================================================================

Mixlib::ShellOut::ShellCommandFailed
------------------------------------
chef_gem[fog] (route53::default line 22) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '1'
---- Begin output of /opt/chef/embedded/bin/gem install fog -q --no-rdoc --no-ri -v "1.30" ----
STDOUT:
STDERR: ERROR:  Error installing fog:
	fog-google requires Ruby version >= 2.0.
---- End output of /opt/chef/embedded/bin/gem install fog -q --no-rdoc --no-ri -v "1.30" ----
Ran /opt/chef/embedded/bin/gem install fog -q --no-rdoc --no-ri -v "1.30" returned 1

Cookbook Trace:
---------------
  /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/mixlib-shellout-1.6.1/lib/mixlib/shellout.rb:272:in `invalid!'
  /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/mixlib-shellout-1.6.1/lib/mixlib/shellout.rb:259:in `error!'
  /opt/chef/embedded/apps/chef/lib/chef/mixin/shell_out.rb:43:in `shell_out!'
  /opt/chef/embedded/apps/chef/lib/chef/provider/package/rubygems.rb:538:in `install_via_gem_command'
  /opt/chef/embedded/apps/chef/lib/chef/provider/package/rubygems.rb:522:in `install_package'
  /opt/chef/embedded/apps/chef/lib/chef/provider/package.rb:82:in `block in action_install'
  /opt/chef/embedded/apps/chef/lib/chef/mixin/why_run.rb:52:in `call'
  /opt/chef/embedded/apps/chef/lib/chef/mixin/why_run.rb:52:in `add_action'
  /opt/chef/embedded/apps/chef/lib/chef/provider.rb:156:in `converge_by'
  /opt/chef/embedded/apps/chef/lib/chef/provider/package.rb:80:in `action_install'
  /opt/chef/embedded/apps/chef/lib/chef/provider.rb:121:in `run_action'
  /opt/chef/embedded/apps/chef/lib/chef/resource.rb:648:in `run_action'
  /opt/chef/embedded/apps/chef/lib/chef/resource/chef_gem.rb:48:in `block in after_created'
  /opt/chef/embedded/apps/chef/lib/chef/resource/chef_gem.rb:47:in `each'
  /opt/chef/embedded/apps/chef/lib/chef/resource/chef_gem.rb:47:in `after_created'
  /opt/chef/embedded/apps/chef/lib/chef/dsl/recipe.rb:139:in `build_resource'
  /opt/chef/embedded/apps/chef/lib/chef/dsl/recipe.rb:85:in `declare_resource'
  /opt/chef/embedded/apps/chef/lib/chef/dsl/recipe.rb:41:in `method_missing'
  /tmp/chef-solo/site-cookbooks/route53/recipes/default.rb:22:in `from_file'
  /opt/chef/embedded/apps/chef/lib/chef/mixin/from_file.rb:30:in `instance_eval'
  /opt/chef/embedded/apps/chef/lib/chef/mixin/from_file.rb:30:in `from_file'
  /opt/chef/embedded/apps/chef/lib/chef/cookbook_version.rb:234:in `load_recipe'
  /opt/chef/embedded/apps/chef/lib/chef/run_context.rb:166:in `load_recipe'
  /opt/chef/embedded/apps/chef/lib/chef/run_context/cookbook_compiler.rb:140:in `block in compile_recipes'
  /opt/chef/embedded/apps/chef/lib/chef/run_context/cookbook_compiler.rb:138:in `each'
  /opt/chef/embedded/apps/chef/lib/chef/run_context/cookbook_compiler.rb:138:in `compile_recipes'
  /opt/chef/embedded/apps/chef/lib/chef/run_context/cookbook_compiler.rb:75:in `compile'
  /opt/chef/embedded/apps/chef/lib/chef/run_context.rb:89:in `load'
  /opt/chef/embedded/apps/chef/lib/chef/policy_builder/expand_node_object.rb:73:in `setup_run_context'
  /opt/chef/embedded/apps/chef/lib/chef/client.rb:265:in `setup_run_context'
  /opt/chef/embedded/apps/chef/lib/chef/client.rb:429:in `do_run'
  /opt/chef/embedded/apps/chef/lib/chef/client.rb:213:in `block in run'
  /opt/chef/embedded/apps/chef/lib/chef/client.rb:207:in `fork'
  /opt/chef/embedded/apps/chef/lib/chef/client.rb:207:in `run'
  /opt/chef/embedded/apps/chef/lib/chef/application.rb:236:in `run_chef_client'
  /opt/chef/embedded/apps/chef/lib/chef/application/solo.rb:226:in `block in run_application'
  /opt/chef/embedded/apps/chef/lib/chef/application/solo.rb:218:in `loop'
  /opt/chef/embedded/apps/chef/lib/chef/application/solo.rb:218:in `run_application'
  /opt/chef/embedded/apps/chef/lib/chef/application.rb:55:in `run'
  /opt/chef/embedded/apps/chef/bin/chef-solo:25:in `<top (required)>'
  /usr/bin/chef-solo:38:in `load'
  /usr/bin/chef-solo:38:in `<main>'

Relevant File Content:
----------------------
/opt/chef/embedded/lib/ruby/gems/1.9.1/gems/mixlib-shellout-1.6.1/lib/mixlib/shellout.rb:

265:      # +msg+:  A String to use as the basis of the exception message. The
266:      # default explanation is very generic, providing a more informative message
267:      # is highly encouraged.
268:      # === Raises
269:      # ShellCommandFailed  always
270:      def invalid!(msg=nil)
271:        msg ||= "Command produced unexpected results"
272>>       raise ShellCommandFailed, msg + "\n" + format_for_exception
273:      end
274:
275:      def inspect
276:        "<#{self.class.name}##{object_id}: command: '#@command' process_status<EMAIL_ADDRESS>" +
277:        "stdout: '#{stdout.strip}' stderr: '#{stderr.strip}' child_pid<EMAIL_ADDRESS>" +
278:        "environment<EMAIL_ADDRESS>timeout: #{timeout} user: #@user group: #@group working_dir: #@cwd >"
279:      end
280:
281:      private

[2015-11-16T08:44:48-08:00] ERROR: Running exception handlers
[2015-11-16T08:44:48-08:00] ERROR: Exception handlers complete
[2015-11-16T08:44:48-08:00] FATAL: Stacktrace dumped to /tmp/chef-solo/cache/chef-stacktrace.out
[2015-11-16T08:44:48-08:00] ERROR: chef_gem[fog] (route53::default line 22) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '1'
---- Begin output of /opt/chef/embedded/bin/gem install fog -q --no-rdoc --no-ri -v "1.30" ----
STDOUT:
STDERR: ERROR:  Error installing fog:
	fog-google requires Ruby version >= 2.0.
---- End output of /opt/chef/embedded/bin/gem install fog -q --no-rdoc --no-ri -v "1.30" ----
Ran /opt/chef/embedded/bin/gem install fog -q --no-rdoc --no-ri -v "1.30" returned 1
[2015-11-16T08:44:48-08:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)

FAILED: chef-solo could not finish configuring the node

As i understand the issue is in ruby version, but how it can be changed?

The issue lies here:
fog-google requires Ruby version >= 2.0.
and here:
/opt/chef/embedded/lib/ruby/gems/1.9.1/gems/
So it seems you are not using version 2.2.2 after all.

@plribeiro3000 , seem like
I use ubuntu 14.04 and when I after installing chef (fix -d -y node:host_name deploy_chef:version=11.18.12) it uses 1.9.1 ruby, and did not find how to change it :(

At this point 1.30 is not current. I'll go ahead and bump to '1.37.0' in #85 and close this PR. Thank you for contributing.

Awesome. Thank you!
Em sex, 4 de mar de 2016 10:05, Aaron Baer<EMAIL_ADDRESS>escreveu:

At this point 1.30 is not current. I'll go ahead and bump to '1.37.0' in
#85 https://github.com/hw-cookbooks/route53/pull/85 and close this PR.
Thank you for contributing.
—
Reply to this email directly or view it on GitHub
https://github.com/hw-cookbooks/route53/pull/75#issuecomment-192386143.


Issue rendering cylinders

When i add cylinders to my robot model, it seems they cannot handle decimal values.
Decimal values do work correctly with boxes.
This line works

This line shows a black cylinder (0 height)

This line become invisible

These lines show exact same shape

It seems to be locale related. Using commas as decimal points in the urdf file solves the issue  (my locale is fr_FR). But that's not a solution. Simply launch rviz2 without a locale defined
LANG= rviz2

Just starting using ros2, can't help more at the moment. But what a fantastic framework.

Oh, this was solved in URDF quite a while ago.
Because of that, I'm going to assume that this is fixed, and close this issue.  If this is not the case, please feel free to reopen.


Unsupported URL scheme http+docker with Python 3.12.2

I'm trying to update some of my molecule-based projects to Python 3.12.2 and am getting the following error:

Error connecting: Error while fetching server API version: Not supported URL scheme http+docker

Has the Molecule Docker plugin been tested and verified working with Python 3.12.x?

it was added in https://github.com/ansible-community/molecule-plugins/pull/207 but the CI has been broken for a while.
hopefully https://github.com/ansible-community/molecule-plugins/pull/260 will be merged soon, but this repository seems to be pretty dormant.

and a note regarding http+docker https://github.com/ansible-collections/community.docker/issues/860

I am running molecule-plugins 23.5.3 with python 3.12.7 and run into a similar issue.
Error searching for image molecule_local/instance - Not supported URL scheme http+docker

I also try to update an old Molecule test which used to work. And is still working in my old virtual environment.


⚠ Bofrost.at has degraded performance

In 312a62d, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2347 ms

Resolved: Bofrost.at performance has improved in df6c1a5 after 7 minutes.


Loading messages

Should include cool loading mechanisms, examples: promoting new podcasts, episodes, app tips, hot topics?

Ideas:
New shows
App tips
Synonym suggestions
Hot topics
Link to github


[WIP][EXPERIMENTAL] Upmerging xen-tools to xen 4.17.2

This is an experimental change and it is not expected to be merged. We can even move to 4.18 when it comes out. It has QEMU 8.0.2

I had to build ninja from source since Alpine dropped as support for it in 3.8

FIXME:

Rebase CPU pinning patches

Highlights:

QEMU 7.0.0
libgcc instead of musl

Looking at XEN release page  at https://downloads.xenproject.org/release/xen/ I would expect XEN 4.18.0 in December this year. It will contain 8.x.y QEMU version. FYI @OhmSpectator , @rouming

I also like the fact libgc is used here, not muscle. It would be useful, particularly for the CPU pinning feature.

failing test is expected. I did not modify them so they expect stuff I've removed from the template

@christoph-zededa also mentioned the following changes:
./xen-tools/Dockerfile:ENV XEN_VERSION 4.15.0
./xen/Dockerfile:ENV XEN_VERSION 4.15.0

I've switched to my personal GH account @rucoder and closing this PR in favor of https://github.com/lf-edge/eve/pull/3534


Sharedsock for NAT traversal

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


fix(bug): Nested nil field will cause panic.

I'll have to think about this one a bit. My gut feeling is that it's not a good idea to auto-initialize fields  since they might be strange side effects. On the other hand I already did a similar thing with big.Ints in the encoder, so...
Either way, the codec is the wrong place for this check, it should be done in the encoder similar to big ints, otherwise the asymmetric API (if it survives 😅 ) would not get fixed.

I generally agree with you on both fronts here, maybe a way to error more gracefully? Though I must say I do prefer the hashing api surface here over fastssz

I have a much more involved solution for this that's also avoid allocating most of the time + I have a bunch of tests, but it's based on top of of the monolith rework, and it would be a PITA to rebased on master, and then break for monoliths. So I'll close this PR but will ship the fix together with the monoliths.


Custom theme on ThemeProvider is not being assigned when testing

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Steps to reproduce 🕹
Link to live example: https://codesandbox.io/s/solitary-monad-2sbfr5?file=/src/App.spec.js
Steps:

Create a custom theme and assign it to a ThemeProvider
Render a component wrapping it with the ThemeProvider
Run test

Current behavior 😯
When trying to use a custom color for a button while testing, the tests fail because of an error "Cannot read properties of undefined (reading 'dark')"
If I use a default color from the base theme, it works as expected.
Expected behavior 🤔
The custom theme should be available when using a ThemeProvider while testing
Context 🔦
Like the following comment: https://github.com/mui/material-ui/issues/29136#issuecomment-1146784282, I cannot use custom properties from a custom theme while testing.
Your environment 🌎
As setup on the codesandbox

The problem is that you are importing ThemeProvider from '@mui/styles' instead of '@mui/material/styles'. Since v5, @mui/styles is a standalone package that has different styling solution & them context compared to the one used in @mui/material. This setup should work: https://codesandbox.io/s/old-dawn-wn0blw?file=/src/App.spec.js


Module Installation fails on Github Actions workflow

Hi, I'm incredibly bad at weird errors, and am not even sure if this is the right place to be posting it, but here I go:
I created a Github Actions Workflow to test builds of my project which makes use of the rawpy library, and as such, needed to run pip install rawpy, however, when running and installing, it fails. This was after multiple attempts to get it working, which only succeeded after manually specifying that numpy & cython should be installed. This error doesn't occur on my desktop rig as far as I'm concerned.
Very interested if you're familiar with this error and if you're able to help me resolve it. Thanks.
Latest Failed Build Attempt
Full Raw Log File

You use an old rawpy version (0.13.1, see https://github.com/Xevion/phototag/blob/master/requirements.txt) which didn't come with Python 3.8 wheels yet. Simply switch to 0.14.0, then everything is fine.
Note that from 0.14.0 onwards I'm no longer publishing the source distribution to PyPI as it was too brittle and caused more trouble than it was worth. This means, either you get a working wheel or nothing at all, and you don't need to have Cython installed.


[Adaptive] [Teams] Add adaptive support for TeamsActivityHandler

https://github.com/microsoft/botbuilder-dotnet/blob/master/libraries/Microsoft.Bot.Builder/Teams/TeamsActivityHandler.cs

See composer ticket - https://github.com/microsoft/BotFramework-Composer/issues/1958


Fixed several issues of SystemClock.

As an Android developer I was very happy to use SystemClock in the shared code for a media playing app which heavily relies on timers. Unfortunately I ran into the following issues:

The iOS implementation of elapsedRealtime() is not monotonic, as the used systemUptime does not take sleep time into account.
The issue was hard to find, since it works in many cases and I was blind, knowing the contract of the Android's API ;)
elapsedRealtimeNanos() returns the same value during the lifetime of a process, since it only returns the actual boot time of the system. But as the SO post below describes, even this fixed time can change, if the user/system changes the OS time.
The implementation of elapsedRealtimeNanos() actually has another issue: the returned value contains a timestamp in microseconds.

In my change I took the code of elapsedRealtimeNanos() to get the boot time in microseconds and used it to calculate the actual uptime based on this SO post: http://stackoverflow.com/q/12488481/1394330
I also took the warning of a race condition into account. elapsedRealtimeNanos() still uses the microseconds multiplied by 1000 to calculate the nanoseconds. This may be improved by using other APIs (?), but for now I'm ok with this ;)

I signed it!


feature request: loadByCompositeKeyAsync

https://github.com/expo/universe/pull/10823/files#r1020707597

Previously discussed in https://github.com/expo/entity/pull/123#issuecomment-847502513


Automated Package Upgrade

:tada: This PR is included in version 13.0.46 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


java.lang.ClassNotFoundException: com.google.auth.CredentialTypeForMetrics | v1.28.0

Environment details

Specify the API at the beginning of the title. For example, "BigQuery: ...").
General, Core, and Other are also allowed as types
OS type and version: MacOS Sequoia 15.0
Java version: 21
version(s): 1.28.0

Steps to reproduce

Use the version 1.28.0 in your pom
Try to connect to a service (Google Drive in my case) and execute a  query

Code example
            val query = "mimeType = 'application/vnd.google-apps.folder'"
            val result: FileList = when (nextPageToken) {
                null -> buildSharedDrive()
                    .setQ(query)
                    .setFields("nextPageToken, files(id, name)")
                    .execute()

Stack trace
Caused by: java.io.IOException: Unexpected error refreshing access token
	at com.google.auth.oauth2.OAuth2Credentials.unwrapDirectFuture(OAuth2Credentials.java:325)
	at com.google.auth.oauth2.OAuth2Credentials.getRequestMetadata(OAuth2Credentials.java:183)
	at com.google.auth.oauth2.ServiceAccountCredentials.getRequestMetadataForGdu(ServiceAccountCredentials.java:1038)
	at com.google.auth.oauth2.ServiceAccountCredentials.getRequestMetadata(ServiceAccountCredentials.java:1016)
	at com.google.auth.http.HttpCredentialsAdapter.initialize(HttpCredentialsAdapter.java:96)
	at com.google.api.client.http.HttpRequestFactory.buildRequest(HttpRequestFactory.java:91)
	at com.google.api.client.googleapis.services.AbstractGoogleClientRequest.buildHttpRequest(AbstractGoogleClientRequest.java:455)
	at com.google.api.client.googleapis.services.AbstractGoogleClientRequest.executeUnparsed(AbstractGoogleClientRequest.java:565)
	at com.google.api.client.googleapis.services.AbstractGoogleClientRequest.executeUnparsed(AbstractGoogleClientRequest.java:506)
	at com.google.api.client.googleapis.services.AbstractGoogleClientRequest.execute(AbstractGoogleClientRequest.java:616)
        at ...
	at org.springframework.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:258)
	at org.springframework.context.annotation.ConfigurationClassEnhancer$BeanMethodInterceptor.intercept(ConfigurationClassEnhancer.java:348)
	at ...
	at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(Unknown Source)
	at java.base/java.lang.reflect.Method.invoke(Unknown Source)
	at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:146)
	... 78 common frames omitted
Caused by: java.lang.NoClassDefFoundError: com/google/auth/CredentialTypeForMetrics
	at com.google.auth.oauth2.ServiceAccountCredentials.getMetricsCredentialType(ServiceAccountCredentials.java:1024)
	at com.google.auth.oauth2.ServiceAccountCredentials.refreshAccessToken(ServiceAccountCredentials.java:512)
	at com.google.auth.oauth2.OAuth2Credentials$1.call(OAuth2Credentials.java:270)
	at com.google.auth.oauth2.OAuth2Credentials$1.call(OAuth2Credentials.java:267)
	at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
	at com.google.auth.oauth2.OAuth2Credentials$RefreshTask.run(OAuth2Credentials.java:635)
	at com.google.common.util.concurrent.DirectExecutor.execute(DirectExecutor.java:31)
	at com.google.auth.oauth2.OAuth2Credentials$AsyncRefreshResult.executeIfNew(OAuth2Credentials.java:582)
	at com.google.auth.oauth2.OAuth2Credentials.asyncFetch(OAuth2Credentials.java:233)
	... 98 common frames omitted

Any additional information below
It's a spring boot microservice using
        <dependency>
            <groupId>com.google.auth</groupId>
            <artifactId>google-auth-library-oauth2-http</artifactId>
            <version>1.28.0</version>
        </dependency>

This CredentialTypeForMetrics is a class newly introduced in 1.28.0 for google-auth-library-credentials.
You will also need to have
        <dependency>
            <groupId>com.google.auth</groupId>
            <artifactId>google-auth-library-credentials</artifactId>
            <version>1.28.0</version>
        </dependency>

On second thought, google-auth-library-oauth2-http:1.28.0 should bring in dependency google-auth-library-credentials:1.28.0 by default. e.g.
[INFO] org.example:test:jar:1.0-SNAPSHOT
[INFO] \- com.google.auth:google-auth-library-oauth2-http:jar:1.28.0:compile
[INFO]    \- com.google.auth:google-auth-library-credentials:jar:1.28.0:compile

Are you overriding the google-auth-library-credentials version specifically? If not, can you share your dependency tree? I am curious where your project is getting the google-auth-library-credentials version from.

It seems that in our case spring-cloud-gcp and googlea-oi-services-sqladmin is still using 1.27.

Could we see your Maven pom.xml or gradle file? I think it would be helpful if we could see the output of mvn dependency:tree or the gradle equivalent.
I believe the latest version of spring-cloud-gcp is pulling in libraries-bom v26.48.0 which pulls in Auth-Library v1.27.0.
Until a new version of spring-cloud-gcp is released with the updated libraries-bom (v26.49.0), you may need to explicitly pull in v1.28.0 of the auth-library-http and auth-library-credentials

@MoritzHorch
spring-cloud-gcp-starter will release a new version likely this week that ships with auth libraries v1.28.0.
Your screenshot is helpful. A few things I noticed:

in your screenshot, there are both google-auth-library-credentials and google-auth-library-oauth2-http brought in by goog-api-client but with inconsistent versions.

mvn dependency:tree shows
for google-api-services-sqladmin

[INFO] \- com.google.apis:google-api-services-sqladmin:jar:v1-rev20241004-2.0.0:compile
[INFO]    \- com.google.api-client:google-api-client:jar:2.7.0:compile
[INFO]       +- com.google.auth:google-auth-library-credentials:jar:1.23.0:compile
[INFO]       \- com.google.auth:google-auth-library-oauth2-http:jar:1.23.0:compile

for spring-cloud-gcp-starter:
[INFO] \- com.google.cloud:spring-cloud-gcp-starter:jar:5.7.0:compile
[INFO]    \- com.google.cloud:spring-cloud-gcp-core:jar:5.7.0:compile
[INFO]       \- com.google.cloud:google-cloud-core:jar:2.44.1:compile
[INFO]          +- com.google.api:gax:jar:2.54.1:compile
[INFO]          +- com.google.auth:google-auth-library-credentials:jar:1.27.0:compile
[INFO]          \- com.google.auth:google-auth-library-oauth2-http:jar:1.27.0:compile

In your pom file, are you specifying google-auth-library-oauth2-http version to 1.28.0? what about google-auth-library-credentials version?
Likely you need to specify versions for both of these if you choose to override.

@zhumin8, I encountered an issue today where I was referencing only google-auth-library-oauth2-http. Based on your last note:

On second thought, google-auth-library-oauth2-http:1.28.0 should bring in dependency google-auth-library-credentials:1.28.0 by default

This doesn’t seem to be the case.

@kessiler  Hmm, can we see your pom.xml or gradle file? There is a reference to the credentials module in the deps section of the pom.xml here. I'm not sure why it wouldn't be bringing it in.

Sure, here’s the pom.xml and the output from the mvn dependency:tree command. There’s a reference to the credentials module in the dependencies section, but it doesn't seem to be resolving as expected.
pom.xml:

mvn dependency:tree:

Can I see the full pom.xml so I can run the mvn dependency:tree locally?  google-auth-library-credentials may be brought in above if it's being omitted here.
Can you run mvn dependency:tree -Dverbose to see if it's being omitted? Or mvn dependency:tree -Dincludes=com.google.auth:google-auth-library-credentials to filter specifically for it?

This looks like google-auth-library-credentials is being pulled in by the kms jar. I'm guessing it's due to how the deps are ordered in the maven pom.xml file (auth-credentials is probably at the same depth for both kms and auth-http), so the first occurrence wins.
Can you try and use either the libraries-bom (preferably) or auth-bom to manage these versions?

I was already using libraries-bom for the KMS dependency, as shown below. Initially, I thought that adding google-auth-library-oauth2-http would bring in all necessary dependencies automatically:
<dependencyManagement>
    <dependencies>
        <dependency>
            <groupId>com.google.cloud</groupId>
            <artifactId>libraries-bom</artifactId>
            <version>26.48.0</version>
            <type>pom</type>
            <scope>import</scope>
        </dependency>
    </dependencies>
</dependencyManagement>

<dependency>
    <groupId>com.google.cloud</groupId>
    <artifactId>google-cloud-kms</artifactId>
</dependency>
<dependency>
    <groupId>com.google.auth</groupId>
    <artifactId>google-auth-library-oauth2-http</artifactId>
    <version>1.28.0</version>
</dependency>

The simple fix turned out to be explicitly adding google-auth-library-credentials:

<dependency>
    <groupId>com.google.auth</groupId>
    <artifactId>google-auth-library-credentials</artifactId>
    <version>1.28.0</version>
</dependency>

Thank you!

Going to close this issue. Feel free to re-open if anything else comes up.


Reintroduce PercentileDataArray to fix older icclims

Setup Information

Xclim version: 0.40
Python version: all
Operating System: all

Description
#1236 broke icclim by removing the PercentileDataArray class. cerfacs-globc/icclim#251 did fix icclim, but there was no release since and installing icclim is still broken.
Steps To Reproduce
pip install icclim
python -c "import icclim"

Additional context
Xclim will make no use of the class, but at least older icclim will still work.
Contribution

[X] I would be willing/able to open a Pull Request to address this bug.

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Is it a temporary fix for a few days or do you intent to keep this for a while ?
Just my opinion, but I think this should be addressed on icclim not on xclim.
We (icc) didn't strongly pin xclim version in the past versions of icclim, it's unfortunate because now all icclim's published version on pipy and conda-forge are unusable.
However, I think until xclim reaches a 1.0.0, xclim's "contract of use" should be something like "there will be breaking changes between minor versions, you must be able to deal with it."
I would suggest to patch icclim latest with a pin to xclim==0.39 to fix this issue (I'm working on it).

It is to be a temporary fix indeed. We had a discussion this morning with Christian and this seemed a good short-term fix.
The thing is, we're not 100% sure we will ever have a version 1.0. Packages around us are not following this scheme (xarray, dask, etc) and we fear the maintenance and development burden might be too heavy?
If icclim depends so strongly on xclim, indeed a good method would be to pin it. We do this for finch, for example.

The 0ver versioning strategy!
Jokes aside, I understand how tempting it is, but to limit burden on maintenance you can clearly state in xclim documentation that only latest major version is maintained no ?

If icclim depends so strongly on xclim, indeed a good method would be to pin it. [...]

Yeah I should have done that for the past versions, I didn't realize it could lead to this situation. It will be fixed in icclim 6.2.0.

Haha, I think we were mainly thinking of the Calendar versioning strategy ;)
We haven't thought of this much, but IMO the maintenance burden is more in all the workarounds one would do to avoid breaking xclim in a minor version update, when it is not "worth" a major update.

I personally prefer semver, but I would be happy to see xclim adopt calver !

We haven't thought of this much, but IMO the maintenance burden is more in all the workarounds one would do to avoid breaking xclim in a minor version update, when it is not "worth" a major update.

I agree, I had the issue in icc and I updated the minor even when there was some (minor) breaking changes a few times ...
I think we should normalize incrementing the major number though.
As for the original issue, icclim 6.2 is available on pipy and will be very soon on conda-forge so this issue can be closed IMO, ping @pagecp.

Closing as this was fixed on icclim. Feel free to reopen if needed.


Cleans up various bits of old code

@randall Would you mind squashing this into one commit? It makes it easier for cherry-picking to the LTS branches, and it's generally how we do things (unless you have strong reasons why you need the commits broken up).

@zwoop Done.
This is safe for 8.0.x (not sure if we want these sort of changes brought over)

I think we should cherry pick as much as possible of cleanup changes that are safe. The point of branching early is to stabilize things, and avoid dangerous commmits to sneak in. This one is not dangerous IMO.

Cherry-picked to 8.0.x


Corona tracker slide

Very quick hack but:
A slide that displays the danish corona stats as seen on https://www.dr.dk/nyheder/indland/status-paa-coronavirus-lige-nu
I thought it would be relevant with the increase in covid cases
The code references a few online JS files. I don't know if it preferable to have them locally instead. I think other places in the code does that too, so I don't imagine it's much of a priority.

Jeg kigger lige på det, men der er noget i gang :)


Implementing Bigtable list_column_families().

In the process, also upgrading the column family factor on the
Table class and adding a ColumnFamily.name property for
comparison with the retrieved protobuf.

LGTM


Change background color for deprecated feature.

What type of PR is this?
/kind documentation
/kind cleanup

What this PR does / why we need it:
Change background color for deprecated feature.
Which issue(s) this PR fixes:

Part of #2256
Special notes for your reviewer:

Does this PR introduce a user-facing change?

NONE

/cc @alculquicondor

@alculquicondor @mimowo WDYT?

@alculquicondor @mimowo WDYT?

+1

/lgtm
/approve
/cherry-pick website


Modify title per input from Geert van Teylingen

Adding "with Azure NetApp Files" to the ReadMe title

What type of PR is this?

Uncomment only one  /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:
/kind api-change
/kind bug
/kind cleanup
/kind design
/kind documentation
/kind failing-test
/kind feature
/kind flake

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Release note:
none

#sign-off

#sign-off