handlePlay  promise0xbef39894
2017-12-19 11:49:46.451 [  3] 0 MediaPlayer:handlePlayCalled after validate source and ID
2017-12-19 11:49:46.451 [  3] 0 MediaPlayer:handlePlayCalled after gst_element_get_state
2017-12-19 11:49:46.451 [  3] 0 MediaPlayer:handlePlayCalled after GST_STATE_PLAYING
2017-12-19 11:49:46.451 [  3] 0 MediaPlayer:handlePlayCalled before set state
2017-12-19 11:49:46.451 [  3] 0 MediaPlayer:handlePlay:attemptBuffering=0
Failed to create secure directory (/home/root/.config/pulse): Read-only file system
2017-12-19 11:49:46.487 [  3] 0 MediaPlayer:handlePlay:startingState=PLAYING,stateReturn=ASYNC
OnPadAdded  &promise0xb54f5b44
handlePadAdded  promise0xb54f5b44
2017-12-19 11:49:46.612 [  3] 0 MediaPlayer:callingOnTags
2017-12-19 11:49:46.613 [  3] 0 MediaPlayer:callingOnTags
2017-12-19 11:49:46.618 [  3] 0 MediaPlayer:callingOnPlaybackStarted:currentId=3
2017-12-19 11:49:46.635 [  3] 0 MediaPlayer:callingOnTags
2017-12-19 11:49:49.320 [  3] 0 MediaPlayer:callingOnPlaybackFinished:currentId=3
2017-12-19 11:49:49.320 [  3] 0 MediaPlayer:saveOffsetBeforeTeardown:offset=2688
2017-12-19 11:49:49.338 [  2] E RequiresShutdown:~RequiresShutdownFailed:reason=notShutdown,name=
[       OK ] MediaPlayerTest.testStartPlayWaitForEndStartPlayAgain (5775 ms)
[ RUN      ] MediaPlayerTest.testStopPlay
setObserver  &promise0xbef398d4
2017-12-19 11:49:49.349 [  4] 0 MediaPlayer:handleSetObserverCalled
handlesetObserver  promise0xbef398d4
setSource istream  &promise0xbef39884
2017-12-19 11:49:49.351 [  4] 0 MediaPlayer:handleSetSourceCalled
handlesetsourceCalled  promise0xbef39884
2017-12-19 11:49:49.351 [  4] E MediaPlayer:saveOffsetBeforeTeardown - gst_element_query_position failed
Play  &promise0xbef398bc
2017-12-19 11:49:49.354 [  4] 0 MediaPlayer:handlePlayCalled:idPassed=4,currentId=4
handlePlay  promise0xbef398bc
2017-12-19 11:49:49.354 [  4] 0 MediaPlayer:handlePlayCalled after validate source and ID
2017-12-19 11:49:49.355 [  4] 0 MediaPlayer:handlePlayCalled after gst_element_get_state
2017-12-19 11:49:49.355 [  4] 0 MediaPlayer:handlePlayCalled after GST_STATE_PLAYING
2017-12-19 11:49:49.355 [  4] 0 MediaPlayer:handlePlayCalled before set state
2017-12-19 11:49:49.355 [  4] 0 MediaPlayer:handlePlay:attemptBuffering=0
Failed to create secure directory (/home/root/.config/pulse): Read-only file system
2017-12-19 11:49:49.375 [  4] 0 MediaPlayer:handlePlay:startingState=PLAYING,stateReturn=ASYNC
OnPadAdded  &promise0xb54f5b44
handlePadAdded  promise0xb54f5b44
2017-12-19 11:49:49.491 [  4] 0 MediaPlayer:callingOnTags
2017-12-19 11:49:49.491 [  4] 0 MediaPlayer:callingOnTags
2017-12-19 11:49:49.503 [  4] 0 MediaPlayer:callingOnPlaybackStarted:currentId=4
2017-12-19 11:49:49.505 [  4] 0 MediaPlayer:callingOnTags
Stop  &promise0xbef398bc
2017-12-19 11:49:54.513 [  4] 0 MediaPlayer:handleStopCalled:idPassed=4,currentId=4
handleStop  promise0xbef398bc
2017-12-19 11:49:54.535 [  4] 0 MediaPlayer:callingOnPlaybackStopped:currentId=4
2017-12-19 11:49:54.542 [  4] E MediaPlayer:saveOffsetBeforeTeardown - gst_element_query_position failed
2017-12-19 11:49:54.546 [  2] E RequiresShutdown:~RequiresShutdownFailed:reason=notShutdown,name=
[       OK ] MediaPlayerTest.testStopPlay (5209 ms)
[ RUN      ] MediaPlayerTest.testStartPlayCallAfterStopPlay
setObserver  &promise0xbef398d4
2017-12-19 11:49:54.558 [  5] 0 MediaPlayer:handleSetObserverCalled
handlesetObserver  promise0xbef398d4
setSource istream  &promise0xbef39884
2017-12-19 11:49:54.559 [  5] 0 MediaPlayer:handleSetSourceCalled
handlesetsourceCalled  promise0xbef39884
2017-12-19 11:49:54.559 [  5] E MediaPlayer:saveOffsetBeforeTeardown - gst_element_query_position failed
Play  &promise0xbef398bc
2017-12-19 11:49:54.564 [  5] 0 MediaPlayer:handlePlayCalled:idPassed=5,currentId=5
handlePlay  promise0xbef398bc
2017-12-19 11:49:54.565 [  5] 0 MediaPlayer:handlePlayCalled after validate source and ID
2017-12-19 11:49:54.565 [  5] 0 MediaPlayer:handlePlayCalled after gst_element_get_state
2017-12-19 11:49:54.565 [  5] 0 MediaPlayer:handlePlayCalled after GST_STATE_PLAYING
2017-12-19 11:49:54.565 [  5] 0 MediaPlayer:handlePlayCalled before set state
2017-12-19 11:49:54.565 [  5] 0 MediaPlayer:handlePlay:attemptBuffering=0
Failed to create secure directory (/home/root/.config/pulse): Read-only file system
2017-12-19 11:49:54.601 [  5] 0 MediaPlayer:handlePlay:startingState=PLAYING,stateReturn=ASYNC
OnPadAdded  &promise0xb54f5b44
handlePadAdded  promise0xb54f5b44
2017-12-19 11:49:54.753 [  5] 0 MediaPlayer:callingOnTags
2017-12-19 11:49:54.753 [  5] 0 MediaPlayer:callingOnTags
2017-12-19 11:49:54.759 [  5] 0 MediaPlayer:callingOnPlaybackStarted:currentId=5
2017-12-19 11:49:54.771 [  5] 0 MediaPlayer:callingOnTags
Stop  &promise0xbef398bc
2017-12-19 11:49:56.761 [  5] 0 MediaPlayer:handleStopCalled:idPassed=5,currentId=5
handleStop  promise0xbef398bc
2017-12-19 11:49:56.779 [  5] 0 MediaPlayer:callingOnPlaybackStopped:currentId=5
Play  &promise0xbef398bc
2017-12-19 11:49:56.779 [  5] E MediaPlayer:saveOffsetBeforeTeardown - gst_element_query_position failed
2017-12-19 11:49:56.781 [  5] 0 MediaPlayer:handlePlayCalled:idPassed=5,currentId=0
handlePlay  promise0xbef398bc
2017-12-19 11:49:56.781 [  5] E MediaPlayer:validateSourceAndIdFailed:reason=sourceNotSet
2017-12-19 11:49:56.781 [  5] E MediaPlayer:handlePlayFailed
2017-12-19 11:49:56.784 [  2] E RequiresShutdown:~RequiresShutdownFailed:reason=notShutdown,name=
[       OK ] MediaPlayerTest.testStartPlayCallAfterStopPlay (2237 ms)
[ RUN      ] MediaPlayerTest.testStartPlayCallAfterStopPlayDifferentSource
setObserver  &promise0xbef398d4
2017-12-19 11:49:56.795 [  6] 0 MediaPlayer:handleSetObserverCalled
handlesetObserver  promise0xbef398d4
setSource attachmentreader  &promise0xbef39854
2017-12-19 11:49:56.800 [  6] 0 MediaPlayer:handleSetSourceCalled
handlesetAttachmentReaderSource  promise0xbef39854
2017-12-19 11:49:56.800 [  6] E MediaPlayer:saveOffsetBeforeTeardown - gst_element_query_position failed
Play  &promise0xbef39894
2017-12-19 11:49:56.803 [  6] 0 MediaPlayer:handlePlayCalled:idPassed=6,currentId=6
handlePlay  promise0xbef39894
2017-12-19 11:49:56.803 [  6] 0 MediaPlayer:handlePlayCalled after validate source and ID
2017-12-19 11:49:56.803 [  6] 0 MediaPlayer:handlePlayCalled after gst_element_get_state
2017-12-19 11:49:56.803 [  6] 0 MediaPlayer:handlePlayCalled after GST_STATE_PLAYING
2017-12-19 11:49:56.803 [  6] 0 MediaPlayer:handlePlayCalled before set state
2017-12-19 11:49:56.803 [  6] 0 MediaPlayer:handlePlay:attemptBuffering=0
Failed to create secure directory (/home/root/.config/pulse): Read-only file system
2017-12-19 11:49:56.823 [  6] 0 MediaPlayer:handlePlay:startingState=PLAYING,stateReturn=ASYNC
OnPadAdded  &promise0xb54f5b44
handlePadAdded  promise0xb54f5b44
2017-12-19 11:49:56.942 [  6] 0 MediaPlayer:callingOnTags
2017-12-19 11:49:56.942 [  6] 0 MediaPlayer:callingOnTags
2017-12-19 11:49:56.949 [  6] 0 MediaPlayer:callingOnPlaybackStarted:currentId=6
2017-12-19 11:49:56.954 [  6] 0 MediaPlayer:callingOnTags
Stop  &promise0xbef39894
2017-12-19 11:49:57.961 [  6] 0 MediaPlayer:handleStopCalled:idPassed=6,currentId=6
handleStop  promise0xbef39894
2017-12-19 11:49:57.975 [  6] 0 MediaPlayer:callingOnPlaybackStopped:currentId=6
setSource attachmentreader  &promise0xbef39854
2017-12-19 11:49:57.975 [  6] E MediaPlayer:saveOffsetBeforeTeardown - gst_element_query_position failed
2017-12-19 11:49:57.977 [  6] 0 MediaPlayer:handleSetSourceCalled
handlesetAttachmentReaderSource  promise0xbef39854
2017-12-19 11:49:57.977 [  6] E MediaPlayer:saveOffsetBeforeTeardown - gst_element_query_position failed
Play  &promise0xbef39894
2017-12-19 11:49:57.986 [  6] 0 MediaPlayer:handlePlayCalled:idPassed=7,currentId=7
handlePlay  promise0xbef39894
2017-12-19 11:49:57.986 [  6] 0 MediaPlayer:handlePlayCalled after validate source and ID
2017-12-19 11:49:57.986 [  6] 0 MediaPlayer:handlePlayCalled after gst_element_get_state
2017-12-19 11:49:57.986 [  6] 0 MediaPlayer:handlePlayCalled after GST_STATE_PLAYING
2017-12-19 11:49:57.986 [  6] 0 MediaPlayer:handlePlayCalled before set state
2017-12-19 11:49:57.987 [  6] 0 MediaPlayer:handlePlay:attemptBuffering=0
Failed to create secure directory (/home/root/.config/pulse): Read-only file system
2017-12-19 11:49:58.006 [  6] 0 MediaPlayer:handlePlay:startingState=PLAYING,stateReturn=ASYNC
OnPadAdded  &promise0xb54f5b44
handlePadAdded  promise0xb54f5b44
2017-12-19 11:49:58.127 [  6] 0 MediaPlayer:callingOnTags
2017-12-19 11:49:58.127 [  6] 0 MediaPlayer:callingOnTags
2017-12-19 11:49:58.128 [  6] 0 MediaPlayer:callingOnPlaybackStarted:currentId=7
2017-12-19 11:49:58.143 [  6] 0 MediaPlayer:callingOnTags
Stop  &promise0xbef39894
2017-12-19 11:49:59.142 [  6] 0 MediaPlayer:handleStopCalled:idPassed=7,currentId=7
handleStop  promise0xbef39894
2017-12-19 11:49:59.161 [  6] 0 MediaPlayer:callingOnPlaybackStopped:currentId=7
2017-12-19 11:49:59.162 [  6] E MediaPlayer:saveOffsetBeforeTeardown - gst_element_query_position failed
2017-12-19 11:49:59.168 [  2] E RequiresShutdown:~RequiresShutdownFailed:reason=notShutdown,name=
[       OK ] MediaPlayerTest.testStartPlayCallAfterStopPlayDifferentSource (2384 ms)
[ RUN      ] MediaPlayerTest.testPauseDuringPlay
setObserver  &promise0xbef398d4
2017-12-19 11:49:59.179 [  7] 0 MediaPlayer:handleSetObserverCalled
handlesetObserver  promise0xbef398d4
setSource istream  &promise0xbef39884
2017-12-19 11:49:59.181 [  7] 0 MediaPlayer:handleSetSourceCalled
handlesetsourceCalled  promise0xbef39884
2017-12-19 11:49:59.181 [  7] E MediaPlayer:saveOffsetBeforeTeardown - gst_element_query_position failed
Play  &promise0xbef398bc
2017-12-19 11:49:59.184 [  7] 0 MediaPlayer:handlePlayCalled:idPassed=8,currentId=8
handlePlay  promise0xbef398bc
2017-12-19 11:49:59.184 [  7] 0 MediaPlayer:handlePlayCalled after validate source and ID
2017-12-19 11:49:59.184 [  7] 0 MediaPlayer:handlePlayCalled after gst_element_get_state
2017-12-19 11:49:59.184 [  7] 0 MediaPlayer:handlePlayCalled after GST_STATE_PLAYING
2017-12-19 11:49:59.184 [  7] 0 MediaPlayer:handlePlayCalled before set state
2017-12-19 11:49:59.185 [  7] 0 MediaPlayer:handlePlay:attemptBuffering=0
Failed to create secure directory (/home/root/.config/pulse): Read-only file system
2017-12-19 11:49:59.207 [  7] 0 MediaPlayer:handlePlay:startingState=PLAYING,stateReturn=ASYNC
OnPadAdded  &promise0xb54f5b44
handlePadAdded  promise0xb54f5b44
2017-12-19 11:49:59.338 [  7] 0 MediaPlayer:callingOnTags
2017-12-19 11:49:59.338 [  7] 0 MediaPlayer:callingOnTags
2017-12-19 11:49:59.345 [  7] 0 MediaPlayer:callingOnPlaybackStarted:currentId=8
2017-12-19 11:49:59.356 [  7] 0 MediaPlayer:callingOnTags
pause  &promise0xbef398bc
2017-12-19 11:50:00.346 [  7] 0 MediaPlayer:handlePauseCalled:idPassed=8,currentId=8
handlePause  promise0xbef398bc
2017-12-19 11:50:00.352 [  7] 0 MediaPlayer:callingOnPlaybackPaused:currentId=8
2017-12-19 11:50:00.369 [  2] E RequiresShutdown:~RequiresShutdownFailed:reason=notShutdown,name=
[       OK ] MediaPlayerTest.testPauseDuringPlay (1200 ms)
[ RUN      ] MediaPlayerTest.testResumeAfterPauseThenStop
setObserver  &promise0xbef398d4
2017-12-19 11:50:00.381 [  8] 0 MediaPlayer:handleSetObserverCalled
handlesetObserver  promise0xbef398d4
setSource istream  &promise0xbef39884
2017-12-19 11:50:00.381 [  8] 0 MediaPlayer:handleSetSourceCalled
handlesetsourceCalled  promise0xbef39884
2017-12-19 11:50:00.382 [  8] E MediaPlayer:saveOffsetBeforeTeardown - gst_element_query_position failed
Play  &promise0xbef398bc
2017-12-19 11:50:00.384 [  8] 0 MediaPlayer:handlePlayCalled:idPassed=9,currentId=9
handlePlay  promise0xbef398bc
2017-12-19 11:50:00.384 [  8] 0 MediaPlayer:handlePlayCalled after validate source and ID
2017-12-19 11:50:00.384 [  8] 0 MediaPlayer:handlePlayCalled after gst_element_get_state
2017-12-19 11:50:00.385 [  8] 0 MediaPlayer:handlePlayCalled after GST_STATE_PLAYING
2017-12-19 11:50:00.385 [  8] 0 MediaPlayer:handlePlayCalled before set state
2017-12-19 11:50:00.385 [  8] 0 MediaPlayer:handlePlay:attemptBuffering=0
Failed to create secure directory (/home/root/.config/pulse): Read-only file system
2017-12-19 11:50:00.403 [  8] 0 MediaPlayer:handlePlay:startingState=PLAYING,stateReturn=ASYNC
OnPadAdded  &promise0xb54f5b44
handlePadAdded  promise0xb54f5b44
2017-12-19 11:50:00.534 [  8] 0 MediaPlayer:callingOnTags
2017-12-19 11:50:00.535 [  8] 0 MediaPlayer:callingOnTags
2017-12-19 11:50:00.538 [  8] 0 MediaPlayer:callingOnPlaybackStarted:currentId=9
pause  &promise0xbef398bc
2017-12-19 11:50:00.539 [  8] 0 MediaPlayer:handlePauseCalled:idPassed=9,currentId=9
handlePause  promise0xbef398bc
2017-12-19 11:50:00.540 [  8] 0 MediaPlayer:callingOnPlaybackPaused:currentId=9
resume  &promise0xbef398bc
2017-12-19 11:50:00.541 [  8] 0 MediaPlayer:handleResumeCalled:idPassed=9,currentId=9
handleResume  promise0xbef398bc
2017-12-19 11:50:00.543 [  8] 0 MediaPlayer:callingOnPlaybackResumed:currentId=9
2017-12-19 11:50:00.546 [  8] 0 MediaPlayer:callingOnTags
2017-12-19 11:50:03.106 [  8] 0 MediaPlayer:callingOnPlaybackFinished:currentId=9
2017-12-19 11:50:03.106 [  8] 0 MediaPlayer:saveOffsetBeforeTeardown:offset=2688
2017-12-19 11:50:03.133 [  2] E RequiresShutdown:~RequiresShutdownFailed:reason=notShutdown,name=
[       OK ] MediaPlayerTest.testResumeAfterPauseThenStop (2764 ms)
[ RUN      ] MediaPlayerTest.testStopAfterPause
setObserver  &promise0xbef398d4
2017-12-19 11:50:03.150 [  9] 0 MediaPlayer:handleSetObserverCalled
handlesetObserver  promise0xbef398d4
setSource istream  &promise0xbef39884
2017-12-19 11:50:03.151 [  9] 0 MediaPlayer:handleSetSourceCalled
handlesetsourceCalled  promise0xbef39884
2017-12-19 11:50:03.151 [  9] E MediaPlayer:saveOffsetBeforeTeardown - gst_element_query_position failed
Play  &promise0xbef398bc
2017-12-19 11:50:03.154 [  9] 0 MediaPlayer:handlePlayCalled:idPassed=10,currentId=10
handlePlay  promise0xbef398bc
2017-12-19 11:50:03.155 [  9] 0 MediaPlayer:handlePlayCalled after validate source and ID
2017-12-19 11:50:03.155 [  9] 0 MediaPlayer:handlePlayCalled after gst_element_get_state
2017-12-19 11:50:03.156 [  9] 0 MediaPlayer:handlePlayCalled after GST_STATE_PLAYING
2017-12-19 11:50:03.156 [  9] 0 MediaPlayer:handlePlayCalled before set state
2017-12-19 11:50:03.156 [  9] 0 MediaPlayer:handlePlay:attemptBuffering=0
Failed to create secure directory (/home/root/.config/pulse): Read-only file system
2017-12-19 11:50:03.191 [  9] 0 MediaPlayer:handlePlay:startingState=PLAYING,stateReturn=ASYNC
OnPadAdded  &promise0xb54f5b44
handlePadAdded  promise0xb54f5b44
2017-12-19 11:50:03.350 [  9] 0 MediaPlayer:callingOnTags
2017-12-19 11:50:03.351 [  9] 0 MediaPlayer:callingOnTags
2017-12-19 11:50:03.352 [  9] 0 MediaPlayer:callingOnPlaybackStarted:currentId=10
2017-12-19 11:50:03.367 [  9] 0 MediaPlayer:callingOnTags
pause  &promise0xbef398bc
2017-12-19 11:50:03.576 [  9] 0 MediaPlayer:handlePauseCalled:idPassed=10,currentId=10
handlePause  promise0xbef398bc
2017-12-19 11:50:03.584 [  9] 0 MediaPlayer:callingOnPlaybackPaused:currentId=10
Stop  &promise0xbef398bc
2017-12-19 11:50:03.585 [  9] 0 MediaPlayer:handleStopCalled:idPassed=10,currentId=10
handleStop  promise0xbef398bc
2017-12-19 11:50:03.598 [  9] 0 MediaPlayer:callingOnPlaybackStopped:currentId=10
2017-12-19 11:50:03.603 [  9] E MediaPlayer:saveOffsetBeforeTeardown - gst_element_query_position failed
2017-12-19 11:50:03.607 [  2] E RequiresShutdown:~RequiresShutdownFailed:reason=notShutdown,name=
[       OK ] MediaPlayerTest.testStopAfterPause (475 ms)
[ RUN      ] MediaPlayerTest.testPauseAfterPause
setObserver  &promise0xbef398d4
2017-12-19 11:50:03.616 [  a] 0 MediaPlayer:handleSetObserverCalled
handlesetObserver  promise0xbef398d4
setSource istream  &promise0xbef39884
2017-12-19 11:50:03.617 [  a] 0 MediaPlayer:handleSetSourceCalled
handlesetsourceCalled  promise0xbef39884
2017-12-19 11:50:03.617 [  a] E MediaPlayer:saveOffsetBeforeTeardown - gst_element_query_position failed
Play  &promise0xbef398bc
2017-12-19 11:50:03.620 [  a] 0 MediaPlayer:handlePlayCalled:idPassed=11,currentId=11
handlePlay  promise0xbef398bc
2017-12-19 11:50:03.620 [  a] 0 MediaPlayer:handlePlayCalled after validate source and ID
2017-12-19 11:50:03.620 [  a] 0 MediaPlayer:handlePlayCalled after gst_element_get_state
2017-12-19 11:50:03.620 [  a] 0 MediaPlayer:handlePlayCalled after GST_STATE_PLAYING
2017-12-19 11:50:03.620 [  a] 0 MediaPlayer:handlePlayCalled before set state
2017-12-19 11:50:03.620 [  a] 0 MediaPlayer:handlePlay:attemptBuffering=0
Failed to create secure directory (/home/root/.config/pulse): Read-only file system
2017-12-19 11:50:03.650 [  a] 0 MediaPlayer:handlePlay:startingState=PLAYING,stateReturn=ASYNC
OnPadAdded  &promise0xb54f5b44
handlePadAdded  promise0xb54f5b44
2017-12-19 11:50:03.788 [  a] 0 MediaPlayer:callingOnTags
2017-12-19 11:50:03.789 [  a] 0 MediaPlayer:callingOnTags
2017-12-19 11:50:03.796 [  a] 0 MediaPlayer:callingOnPlaybackStarted:currentId=11
pause  &promise0xbef398bc
2017-12-19 11:50:03.796 [  a] 0 MediaPlayer:handlePauseCalled:idPassed=11,currentId=11
handlePause  promise0xbef398bc
2017-12-19 11:50:03.798 [  a] 0 MediaPlayer:callingOnPlaybackPaused:currentId=11
pause  &promise0xbef398bc
2017-12-19 11:50:03.806 [  a] 0 MediaPlayer:handlePauseCalled:idPassed=11,currentId=11
handlePause  promise0xbef398bc
2017-12-19 11:50:03.806 [  a] E MediaPlayer:handlePauseFailed:reason=noAudioPlaying
Stop  &promise0xbef398bc
2017-12-19 11:50:03.807 [  a] 0 MediaPlayer:handleStopCalled:idPassed=11,currentId=11
handleStop  promise0xbef398bc
2017-12-19 11:50:03.816 [  a] 0 MediaPlayer:callingOnPlaybackStopped:currentId=11
2017-12-19 11:50:03.817 [  a] E MediaPlayer:saveOffsetBeforeTeardown - gst_element_query_position failed
2017-12-19 11:50:03.820 [  2] E RequiresShutdown:~RequiresShutdownFailed:reason=notShutdown,name=
[       OK ] MediaPlayerTest.testPauseAfterPause (213 ms)
[ RUN      ] MediaPlayerTest.testResumeAfterPlay
setObserver  &promise0xbef398d4
2017-12-19 11:50:03.828 [  b] 0 MediaPlayer:handleSetObserverCalled
handlesetObserver  promise0xbef398d4
setSource istream  &promise0xbef39884
2017-12-19 11:50:03.829 [  b] 0 MediaPlayer:handleSetSourceCalled
handlesetsourceCalled  promise0xbef39884
2017-12-19 11:50:03.829 [  b] E MediaPlayer:saveOffsetBeforeTeardown - gst_element_query_position failed
Play  &promise0xbef398bc
2017-12-19 11:50:03.832 [  b] 0 MediaPlayer:handlePlayCalled:idPassed=12,currentId=12
handlePlay  promise0xbef398bc
2017-12-19 11:50:03.832 [  b] 0 MediaPlayer:handlePlayCalled after validate source and ID
2017-12-19 11:50:03.832 [  b] 0 MediaPlayer:handlePlayCalled after gst_element_get_state
2017-12-19 11:50:03.832 [  b] 0 MediaPlayer:handlePlayCalled after GST_STATE_PLAYING
2017-12-19 11:50:03.832 [  b] 0 MediaPlayer:handlePlayCalled before set state
2017-12-19 11:50:03.833 [  b] 0 MediaPlayer:handlePlay:attemptBuffering=0
Failed to create secure directory (/home/root/.config/pulse): Read-only file system
2017-12-19 11:50:03.851 [  b] 0 MediaPlayer:handlePlay:startingState=PLAYING,stateReturn=ASYNC
OnPadAdded  &promise0xb54f5b44
handlePadAdded  promise0xb54f5b44
2017-12-19 11:50:03.971 [  b] 0 MediaPlayer:callingOnTags
2017-12-19 11:50:03.971 [  b] 0 MediaPlayer:callingOnTags
2017-12-19 11:50:03.976 [  b] 0 MediaPlayer:callingOnPlaybackStarted:currentId=12
resume  &promise0xbef398bc
2017-12-19 11:50:03.977 [  b] 0 MediaPlayer:handleResumeCalled:idPassed=12,currentId=12
handleResume  promise0xbef398bc
2017-12-19 11:50:03.977 [  b] E MediaPlayer:handleResumeFailed:reason=alreadyPlaying
Stop  &promise0xbef398bc
2017-12-19 11:50:03.977 [  b] 0 MediaPlayer:handleStopCalled:idPassed=12,currentId=12
handleStop  promise0xbef398bc
2017-12-19 11:50:03.994 [  b] 0 MediaPlayer:callingOnPlaybackStopped:currentId=12
2017-12-19 11:50:03.997 [  b] E MediaPlayer:saveOffsetBeforeTeardown - gst_element_query_position failed
2017-12-19 11:50:04.003 [  2] E RequiresShutdown:~RequiresShutdownFailed:reason=notShutdown,name=
[       OK ] MediaPlayerTest.testResumeAfterPlay (183 ms)
[ RUN      ] MediaPlayerTest.testGetOffsetInMilliseconds
setObserver  &promise0xbef398d4
2017-12-19 11:50:04.018 [  c] 0 MediaPlayer:handleSetObserverCalled
handlesetObserver  promise0xbef398d4
setSource attachmentreader  &promise0xbef39854
2017-12-19 11:50:04.018 [  c] 0 MediaPlayer:handleSetSourceCalled
handlesetAttachmentReaderSource  promise0xbef39854
2017-12-19 11:50:04.019 [  c] E MediaPlayer:saveOffsetBeforeTeardown - gst_element_query_position failed
Play  &promise0xbef39894
2017-12-19 11:50:04.021 [  c] 0 MediaPlayer:handlePlayCalled:idPassed=13,currentId=13
handlePlay  promise0xbef39894
2017-12-19 11:50:04.022 [  c] 0 MediaPlayer:handlePlayCalled after validate source and ID
2017-12-19 11:50:04.022 [  c] 0 MediaPlayer:handlePlayCalled after gst_element_get_state
2017-12-19 11:50:04.022 [  c] 0 MediaPlayer:handlePlayCalled after GST_STATE_PLAYING
2017-12-19 11:50:04.022 [  c] 0 MediaPlayer:handlePlayCalled before set state
2017-12-19 11:50:04.022 [  c] 0 MediaPlayer:handlePlay:attemptBuffering=0
Failed to create secure directory (/home/root/.config/pulse): Read-only file system
2017-12-19 11:50:04.043 [  c] 0 MediaPlayer:handlePlay:startingState=PLAYING,stateReturn=ASYNC
OnPadAdded  &promise0xb54f5b44
handlePadAdded  promise0xb54f5b44
2017-12-19 11:50:04.172 [  c] 0 MediaPlayer:callingOnTags
2017-12-19 11:50:04.172 [  c] 0 MediaPlayer:callingOnTags
2017-12-19 11:50:04.178 [  c] 0 MediaPlayer:callingOnPlaybackStarted:currentId=13
2017-12-19 11:50:04.190 [  c] 0 MediaPlayer:callingOnTags
getOffset  &promise0xbef39894
2017-12-19 11:50:05.186 [  c] 0 MediaPlayer:handleGetOffsetCalled:idPassed=13,currentId=13
handleGetOffset  promise0xbef39894
Stop  &promise0xbef39894
2017-12-19 11:50:05.187 [  c] 0 MediaPlayer:handleStopCalled:idPassed=13,currentId=13
handleStop  promise0xbef39894
2017-12-19 11:50:05.209 [  c] 0 MediaPlayer:callingOnPlaybackStopped:currentId=13
getOffset  &promise0xbef39894
2017-12-19 11:50:05.209 [  c] E MediaPlayer:saveOffsetBeforeTeardown - gst_element_query_position failed
2017-12-19 11:50:05.210 [  c] 0 MediaPlayer:handleGetOffsetCalled:idPassed=13,currentId=0
handleGetOffset  promise0xbef39894
2017-12-19 11:50:05.211 [  c] E MediaPlayer:validateSourceAndIdFailed:reason=sourceNotSet
2017-12-19 11:50:05.218 [  2] E RequiresShutdown:~RequiresShutdownFailed:reason=notShutdown,name=
[       OK ] MediaPlayerTest.testGetOffsetInMilliseconds (1214 ms)
[ RUN      ] MediaPlayerTest.testGetOffsetInMillisecondsNullPipeline
setObserver  &promise0xbef398d4
2017-12-19 11:50:05.230 [  d] 0 MediaPlayer:handleSetObserverCalled
handlesetObserver  promise0xbef398d4
setSource attachmentreader  &promise0xbef39864
2017-12-19 11:50:05.231 [  d] 0 MediaPlayer:handleSetSourceCalled
handlesetAttachmentReaderSource  promise0xbef39864
2017-12-19 11:50:05.231 [  d] E MediaPlayer:saveOffsetBeforeTeardown - gst_element_query_position failed
getOffset  &promise0xbef398a4
2017-12-19 11:50:05.234 [  d] 0 MediaPlayer:handleGetOffsetCalled:idPassed=15,currentId=14
handleGetOffset  promise0xbef398a4
2017-12-19 11:50:05.234 [  d] E MediaPlayer:validateSourceAndIdFailed:reason=sourceIdMismatch
2017-12-19 11:50:05.241 [  2] E RequiresShutdown:~RequiresShutdownFailed:reason=notShutdown,name=
[       OK ] MediaPlayerTest.testGetOffsetInMillisecondsNullPipeline (23 ms)
[ RUN      ] MediaPlayerTest.testGetOffsetWhenStoppedFails
setObserver  &promise0xbef398d4
2017-12-19 11:50:05.253 [  e] 0 MediaPlayer:handleSetObserverCalled
handlesetObserver  promise0xbef398d4
setSource attachmentreader  &promise0xbef3985c
2017-12-19 11:50:05.253 [  e] 0 MediaPlayer:handleSetSourceCalled
handlesetAttachmentReaderSource  promise0xbef3985c
2017-12-19 11:50:05.254 [  e] E MediaPlayer:saveOffsetBeforeTeardown - gst_element_query_position failed
Play  &promise0xbef3989c
2017-12-19 11:50:05.258 [  e] 0 MediaPlayer:handlePlayCalled:idPassed=15,currentId=15
handlePlay  promise0xbef3989c
2017-12-19 11:50:05.258 [  e] 0 MediaPlayer:handlePlayCalled after validate source and ID
2017-12-19 11:50:05.258 [  e] 0 MediaPlayer:handlePlayCalled after gst_element_get_state
2017-12-19 11:50:05.258 [  e] 0 MediaPlayer:handlePlayCalled after GST_STATE_PLAYING
2017-12-19 11:50:05.258 [  e] 0 MediaPlayer:handlePlayCalled before set state
2017-12-19 11:50:05.258 [  e] 0 MediaPlayer:handlePlay:attemptBuffering=0
Failed to create secure directory (/home/root/.config/pulse): Read-only file system
2017-12-19 11:50:05.279 [  e] 0 MediaPlayer:handlePlay:startingState=PLAYING,stateReturn=ASYNC
OnPadAdded  &promise0xb54f5b44
handlePadAdded  promise0xb54f5b44
2017-12-19 11:50:05.425 [  e] 0 MediaPlayer:callingOnTags
2017-12-19 11:50:05.426 [  e] 0 MediaPlayer:callingOnTags
2017-12-19 11:50:05.428 [  e] 0 MediaPlayer:callingOnPlaybackStarted:currentId=15
2017-12-19 11:50:05.437 [  e] 0 MediaPlayer:callingOnTags
Stop  &promise0xbef3989c
2017-12-19 11:50:06.436 [  e] 0 MediaPlayer:handleStopCalled:idPassed=15,currentId=15
handleStop  promise0xbef3989c
2017-12-19 11:50:06.456 [  e] 0 MediaPlayer:callingOnPlaybackStopped:currentId=15
getOffset  &promise0xbef3989c
2017-12-19 11:50:06.457 [  e] E MediaPlayer:saveOffsetBeforeTeardown - gst_element_query_position failed
2017-12-19 11:50:06.458 [  e] 0 MediaPlayer:handleGetOffsetCalled:idPassed=15,currentId=0
handleGetOffset  promise0xbef3989c
2017-12-19 11:50:06.458 [  e] E MediaPlayer:validateSourceAndIdFailed:reason=sourceNotSet
2017-12-19 11:50:06.461 [  2] E RequiresShutdown:~RequiresShutdownFailed:reason=notShutdown,name=
[       OK ] MediaPlayerTest.testGetOffsetWhenStoppedFails (1220 ms)
[ RUN      ] MediaPlayerTest.testGetOffsetWhenPaused
setObserver  &promise0xbef398d4
2017-12-19 11:50:06.469 [  f] 0 MediaPlayer:handleSetObserverCalled
handlesetObserver  promise0xbef398d4
setSource attachmentreader  &promise0xbef3985c
2017-12-19 11:50:06.469 [  f] 0 MediaPlayer:handleSetSourceCalled
handlesetAttachmentReaderSource  promise0xbef3985c
2017-12-19 11:50:06.469 [  f] E MediaPlayer:saveOffsetBeforeTeardown - gst_element_query_position failed
terminate called after throwing an instance of 'std::future_error'
what():  Promise already satisfied
Aborted (core dumped)
root@info3-low:~#
root@info3-low:~#
I can see the same promise being used in multiple methods, though it is stack variable.
You were correct , this is initialization or cleanup issue. Do you know how to cleanup std::promise after being set to true in the case of handlePlay.
I am still struggling to understand this weird issue. is G++ is the culprit here.

regarding the ubuntu 14.04 , I am having some issue with the setup today for v1.3 version and could not get the logs. so for ubuntu 14.04 m still not sure whether same issue occurs or not.
As previous testing for ubuntu 14.04 was done on v1.1.0 and there I found multiple issues with promise setting which were resolved in v1.3 version.

Hi @dhananjayj29, I have the similar issue porting avs device sdk (version 1.9.0) on an Amlogic board. Could you please share your fix about using std::promises as heap variable. Thanks.


CSS

#CSS
User Story
As a bootcamp student
I want the prework notes to be structured on a webpage
So that I can easily find and read the information
##acceptance criteria
GIVEN a Prework Study Guide Website
WHEN I veiw the study guide
THEN i see a dark blue header and footer, and four boxes with a shadow

revisit! never cracked it ask instructor


Add spinner to SoW upload

As an analyst
I want to see the spinner when I click 'save and import'
So that I know that the system is working on the import
Description:
We need to remove the ability to change the form data while the import happens and show a notification that the system is importing
Acceptance Criteria:
[wireframe 1]

[ ] Acceptance Criteria

[wireframe 2]

[ ] Acceptance Criteria

Implementation Details

Hey team! Please add your planning poker estimate with Zenhub @AntBush @marcellmueller @rafasdc @VB-at-Bis


multiple same tablets in the disk BE storage directory,taking up a lot of disk space.

Load a table, 10 partitions, 900M of data. There are multiple tablets in the disk BE storage directory, and the amount of data gradually increases, occupying a large amount of disk space, up to 150G.
version： 0.12.0-rc03

According to partition and distributed column, it is normally that multiple tablets in the disk.
However, disk space should not be 150G.
Could you please show the disk space by df -h under the data dir


Implement new Orphanet disease-target evidence

Daniel to expand if needed (?)

Some preliminary exploration...
Data and documentation can be found in orphadata portal in section > Genes associated with rare diseases. Dataset here
Monarch also incorporates this data, so it might be an alternative source to make sure we are processing the data correctly:
curl https://archive.monarchinitiative.org/latest/tsv/gene_associations/gene_disease.9606.tsv.gz | gzcat | grep '#orphanet'


Variables not properly injected in Symfony's "bind" feature in dev env ?

Hello,
I recently migrated a Symfony 2.8 app to 3.4 and took advantage of the "bind" feature.
My env parameters are loaded using a .env file
MY_PARAMETER=OK
and a parameters.php which does
$container->setParameter('my_parameter', getenv('MY_PARAMETER'));
parameters.php is imported through config.yml using
imports:
    - { resource: parameters.yml }

These are then bind in services.yml using :
services:
    _defaults:
        autowire: true
        autoconfigure: true
        public: false
        bind:
            $myParameter: '%my_parameter%'

Somehow the autowired services that have $myParameter as a constructor's argument receive the 'ok' value properly in production environment (app.php), as soon as I switch to dev or add app_dev.php to url the injected value becomes empty ''
Any idea ?

After more testing, it's never injected when using app_dev.php and app.php only works after warming up the cache with bin/console cache:clear --env=prod

I guess this is because symfony is caching stuff? Sorry, I don't use Symfony.


Example of sending an entire file

Hello!
I' trying to send a file to a SOAP service that seem to only accept content-type of multipart/related and I am wondering what is the best way to do it...
Should I make a loop, read a few bytes and use w.CreatePart() at every iteration? Kind of like in the README.md? This doesn't seem very efficient. Isn't there a way to use io.Copy()?
Thanks for your help!

Hey Gujie,
As mentioned in the README.md a multipart/related contains multiple components/files which are related to each other. Usually, each part represents a file. For example, you’re going to upload an images with metadata(like tags, categories, etc) formatted in json. The image would be part 1 and the metadata would be part 2.
Thus, you need to iterate over your content(image, metadata) and copy each into a part. Unfortunately, this package doesn’t support media type sniffing so you need to set your content-type explicitly.
image_header := textproto.MIMEHeader{}
image_header.Add("Content-Type", "images/jpeg")
image_part, _ := w.CreatePart("", image_header)
io.Copy(image_part, image_file)

json_header := textproto.MIMEHeader{}
json_header.Add("Content-Type", "application/json")
json_part, _ := w.CreatePart("", json_header )
io.Copy(json_part , json_output)

Thanks, it's working now!


i18n(zh-cn): Update dev-toolbar-app-reference.mdx

Description (required)
Update dev-toolbar-app-reference.mdx
Related issues & labels (optional)

#9240
Suggested label: i18n

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

File
Note

zh-cn/reference/dev-toolbar-app-reference.mdx
Localization changed, will be marked as complete.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.


enable_async_write_back = true

I am using shared-data mode and trying to create a table with enable_async_write_back true.
CREATE TABLE cloud_db.example (
	id BIGINT NOT NULL,
        date DATE
)
PRIMARY KEY(id)
DISTRIBUTED BY HASH(id)
ORDER BY (id)
PROPERTIES ("enable_async_write_back" = "true");

: Unexpected exception: enable_async_write_back is disabled since version 3.1.4

This feature is not tested very well, so we disable it now.
Do you mind telling us the background that you need this feature? Let me help you if there is another workaround for your scenario.

I am trying to speed up broker load ingestion. I am doing some transformation there and I just want to make sure I utilize everything for speed. I read about disk_spill to reduce memory as well, does it effect broker loads?

Thanks for your explanation.
disk_spill won't help broker loads.
It can only be used when there are join, aggregate operators in the execution trees.

I see, is there anyway to utilize disk/memory to improve load times?


replace caddr_t with char*

overriding my old pr to source from a proper issue branch for issue 1447
Replaces old 'caddr_t' type with generic 'char*'
EDIT: Fixes #1447

 test


[extractor/instagram] Fix error reporting with failed post extraction

Description of pull request and other information
Enhances the instagram post extractor error reporting.
Fixes #4532
Before submitting a pull request make sure you have:

[x] At least skimmed through contributing guidelines including yt-dlp coding conventions
[x] Searched the bugtracker for similar pull requests
[x] Checked the code with flake8 and ran relevant tests

In order to be accepted and merged into yt-dlp each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[x] Fix or improvement to an extractor (Make sure to add/update tests)
[ ] New extractor (Piracy websites will not be accepted)
[ ] Core bug fix/improvement
[ ] New feature (It is strongly recommended to open an issue first)

Why do not merge? it fixes the problem with error notes when the extraction fails

Because the new error message is wrong. The videos open in browser without login. So raising a login_required is incorrect

No this error is general purpose error and would be shown if anyhow extraction fails.

You think "login required" is a general purpose error and shouldn't just be used when login is required??

So what we tell the user if the extraction fails or we just show them the traceback caused due to unwanted code execution?

Raise login_reqiored only when it's actually login issue. There is no need to "fix" the current error message, because the extraction is broken. But, if you think you can provide a better error message, raise an ExtractorError. You can hint the user that login can workaround the issue, but not that lack of login is the issue

Also, the PR title/desc no longer reflects what it does?


how to run multiple instance?

I have run bleno sucessfully on MacOS, but Id like to know how to run multi instances on the same server? Does it support?

@slixin have you tried just running multiple node apps? Let us know if this doesn't work.

Even running multiple node apps, it does not work. If I run a second node app, it will override the advertisement of the service in the first node app. Is this a bug or bleno really doesn't support this yet?

I'm currently using this fork of bleno because the "official" version does not support the latest versions of Node: https://github.com/abandonware/bleno
However, I believe that this issue applies to both versions. I'm using the "startAdvertisingIBeacon" to simulate an iBeacon, but I'm only able to run one instance of my application that does it. As soon as I run another instance the previous one stops advertising.
Is this something that can be done at the Node.js/bleno level. Or is it some inherent limitation of BlueZ or perhaps even an hardware limitation? For instance, on certain Android phones I'm able to advertise multiple iBeacon signals concurrently on an app such as this one: https://play.google.com/store/apps/details?id=net.alea.beaconsimulator&hl=en


How do I insert data into the table in the module installation process?

Hello good afternoon
All good my friend
I created a new extension using your module
Where a table was set up in the database
I would like to offer this new module but with pre-existing data in this table
What is the correct way to do this process?

@cerebrumgit Sorry, for the late response. I've been putting this on hold for a while. Unfortunately there is no way to prefill your table with data using the UMC. But it sounds like a good idea for a feature. Until I implement this, I can recommend you this dummy data generator: http://www.generatedata.com/ you should be able to setup your dummy data in a few minutes.


Paper Equation 7 Typo

Hi, thanks for the awesome library and writeup!
I noticed that in Equation 7, there is a minus sign before gamma^{-2}. Is this a typo -- I would assume it should be the following one (with the leading negative sign removed)?

Hi, thanks for noticing that. You're right, the negative signs from inside the exponent in the prior and from the fact that L is the negative log-posterior, cancel.

Got it -- thanks for the confirmation!


Consider switching the build system.

Qbs is being deprecated, so switching to another build system might be needed at some point.
Thunder could follow the Qt project itself and switch to using CMake?
I've managed to cobble a CMake project that seems to work a little bit, so at least it's not impossible :smile:

Hi, yes I know about this sad news =( They will not going to introduce new features but qbs will not disappear immediately. At this moment it's doing all we need to build a project and natively supported by Qt Creator. It's much faster and flexible then QMake btw QMake is also not growing. CMake is also in my field of view but when I used it in my previous project, I faced a lot of problems like frameworks version conflicts (when you have several Qt versions or several OpenSSL versions and etc) it peeks the version with internal logic and it was hard to do it right with undocumented variables. But anyway thanks for your proposal. I will think about this.

Just wanted to add. Thunder is using qbs as an internal build tool. To build your game project WorldEditor will use Builder tool which packs your resources and build your binaries. It uses qbs in the last step. I mean, switch to CMake will require to modify this logic. But yes, it's not impossible.

I've managed to cobble a CMake project that seems to work a little bit, so at least it's not impossible.
Does it mean you are ready to do this for ThunderEngine?

I guess this issue can be closed now


Exclude a repository from the list if there are 0 issues with label good-first-issues

Hi @gomzyakov I was just taking a look at this and I thought it was interesting and I might be able to assist.

My understanding is that on /Generator.php line 42 or before there could a condition that tests if there is an issue >0 with the label good first issue.
I was looking at this part below in the REST API.
https://docs.github.com/en/rest/issues/labels?apiVersion=2022-11-28 Get a label

I am just trying to piece this together, does this sound like I am on the right track?
Thanks.

@joshhazelhurst123 Hello!
Yes, you are on the right track!

Okay so based on what the API tells me here.

https://docs.github.com/en/search-github/searching-on-github/searching-for-repositories#search-based-on-number-of-issues-with-good-first-issue-or-help-wanted-labels

I can search based on number of issues with good first issue or help wanted labels. Below I have a condition that searches for good first issues that have the label 'good-first-issue' occurring 2 times or more.

https://github.com/search?utf8=✓&q=good-first-issues%3A>2&type=repositories

I can search for 'good-first-issue' to occur 0 times or more

https://github.com/search?utf8=✓&q=good-first-issues%3A>0&type=repositories

So to run a search where there are 0 issues with the label 'good-first-issue' I would search like below.

https://github.com/search?utf8=✓&q=good-first-issues%3A<1&type=repositories

Which return 138m results.
Pseudocode would be, create a function that searches through the repositories to see if there is >1 'good-first-issue' then put that into a list, array, basically store that list. Then have another list that searches through the repositories that looks to see if there is <1 'good-first-issue' then discard those repositories.
So I basically have no idea how to code this, any tips would really help.

@joshhazelhurst123
Thanks for the excellent research work!
Based on your link:
https://docs.github.com/en/search-github/searching-on-github/searching-for-repositories#search-based-on-number-of-issues-with-good-first-issue-or-help-wanted-labels
I looked at the API documentation:
https://docs.github.com/en/rest/search/search?apiVersion=2022-11-28#search-repositories
After that I thought: Maybe we should give up the repositories.json file?
You can simply take repositories from the API that have more than 2 labels good first issues and show them.
You can think in this direction and make a PR, or I will do this in a couple of weeks, and you will review my edits ;)

Hi @gomzyakov thanks for reviewing what I have done and taking at look at the research that I put forward as shown above. Yes, I think giving up on the respositories.json file is a good idea. I got a bit confused with how to piece this together and code it.

I like what you have written here. "You can simply take repositories from the API that have more than 2 labels good first issues and show them." Based on what I have posted here. Reference below

joshhazelhurst123 commented last week

I can search based on number of issues with good first issue or help wanted labels. Below I have a condition that searches for good first issues that have the label 'good-first-issue' occurring 2 times or more.

https://github.com/search?utf8=%E2%9C%93&q=good-first-issues%3A>2&type=repositories

gomzyakov commented 4 hours ago

"You can think in this direction and make a PR, or I will do this in a couple of weeks, and you will review my edits".

I would like to do a PR and code this, I am still quite unsure how to code this and put it all together. I think the logical place to put this function is in

https://github.com/good-first-issues.github.io/tree/main/src/Renderer.php
And, AND OR
https://github.com/good-first-issues/good-first-issues.github.io/tree/main/src/Generator.php

Thanks @gomzyakov hope that makes sense. If you can you guide me on how to code this I will do a PR with you or I am happy to wait to see what you will add in a couple of weeks.

@joshhazelhurst123 Hi!
I implemented the idea described above in PR https://github.com/good-first-issues/good-first-issues.github.io/pull/188
At the basic level, everything works, but periodically there is a problem with exhausting the GitHub API limits.
But, that's a completely different task (you can think about it if you have time). I think the current task can be closed)

NOTE: This repository is no longer supported or updated by @gomzyakov . If you wish to continue to develop this code yourself, we recommend you fork it.


Make Canvas Renderer functional again.

fix sprite texture square (#1778)
fix missing export in CanvasGraphics (#1790)

Closing, managed to get these changes into dev.

Not 100% sure why this works - I'm not that saavy with pixi internals yet :)
Sent from my iPhone

On May 14, 2015, at 03:57, Chad Engler<EMAIL_ADDRESS>wrote:
Closing, managed to get these changes into dev.
—
Reply to this email directly or view it on GitHub.


Added Scroll to top button

Related Issue
https://github.com/anmode/grabtern-frontend/issues/528

I have added scroll to top button
Closes: #[528]
Description of Changes

Checklist:

[ x] My code adheres to the established style guidelines of this project.
[ x] I have conducted a self-review of my code.
[ x] I have included comments in areas that may be difficult to understand.
[ x] I have made corresponding updates to the project documentation.
[ x] My changes have not introduced any new warnings.

what's your scrren resolution?? 100% or not? yeh site aisi aa rhi h? like as you show in pic
and one more thing increase z-index of scroll buttoon

in full screen: 100% zoom

in full screen: 100% zoom

oh no it's a bug then!

sorry @anmode sir, I didn't got to understand what is the bug here ?

Its looking fine everywhere. What is the bug ?

sorry @anmode sir, I didn't got to understand what is the bug here ?

oh okk, My bad. it's not on your side. may be viewport needs to fixed. that I will see.
please see my suggestion / review comments

I have already updated the z index after it @anmode sir

I have already updated the z index after it @anmode sir

oh no! these comments: https://github.com/anmode/grabtern-frontend/pull/539/files/8c43e0b50121f28281002c052bcaf2e4c16672c8

@anmode check it now

Cool thanks @akanksha984

Cool thanks @akanksha984

My pleasure @anmode


Corpus generator colab notebook

I have refactored the colab notebook and fixed some of the non-working code snippets, so now everything flows very well
you can check it out here: https://colab.research.google.com/drive/1Hsp2508TXMR0ihYOLjKYOzWm9byqg9ue

Hello!
It seems like your colab notebook is private only. Can you open it?

@Kepler-br sorry. Try again

Now it works


Stablish a admin password

Hi, is it possibly to stablish and admin password for login to web page ?
Thanks.

Hello,
Sorry for the late reply.
Of course, you can add a login into the website.
There are so many tutorials about how to make it to your website.


[release-0.24] Upgrade to latest dependencies

bumping webhooks -dprotaso
/cc knative/serving-writers knative/eventing-writers
/assign knative/serving-writers knative/eventing-writers
Produced by: knative-sandbox/knobots/actions/update-deps
Details:

closing - this is a noop


GDPR - Group Number inconsistent

The group file for GDPR checks identifies its GROUP_NUMBER as '8.0' rather than '9.0'
https://github.com/toniblyx/prowler/blob/3212b0db551d72f9673d5d6c69ec613a74dd0119/groups/group9_gdpr#L15

my bad, I'm going to fix it now. I have to add more checks to complete the group, I'll find some time later this week.
Thanks!


complex data in gmsh

Hi,
I am trying import a grid with data from a gmsh file. The problem is that the data ara complex numbers, and the importer does not read it. It should be easily implemented, since in the new version of numpy (1.18), the function fromfile() can read complex numbers.

As always, we need a mesh file to reproduce the issue.

No problem, Please find it attached.
dataWithMesh.msh.zip

When trying to open this in gmsh, the geometry loads but not the data. Instead, I get
Could not read data in msh file

Something is off.

And by the way you can get much better-quality sphere meshes with https://github.com/nschloe/meshzoo#sphere-surface and optimesh. https://github.com/nschloe/optimesh#surface-mesh-smoothing

Closing for lack of response. Feel free to reopen at any time.


Similarities with paralleldrive/cuid2

I am looking around to what opitons there are other than uuids within Go and stumbled across this package. I just wanted to know is this pretty much a 1:1 with the JS package

Yes that's what it is.
There's an issue with some discussions about this Go port : https://github.com/paralleldrive/cuid2/issues/33
Looks like someone else gave a shot at this recently though :sweat_smile: : https://github.com/paralleldrive/cuid2/issues/52 (I haven't looked at it yet)


File to import not found or unreadable: envb_mixins.

Added gem to new Rails project
application.css manifest file looks like:
 *
 *= require_tree .
 *= require envb
 *= require_self
 */

Rails server starts just fine. Hitting http://localhost:3000 throws the above error.

@ramanbuttar wow, sorry I didn’t even see this issue get posted. I assume you’re still getting this error. Could you let me know which version of Rails you were using and I’ll see if I can figure out the problem?

@joedynamite Still getting the error. Using Rails 4.2 and Ruby 2.3.1

Updating https://github.com/joedynamite/envb-rails/blob/ea0e62e6651d6740b74224194ebbf65608bb68d7/app/assets/stylesheets/envb.css.scss.erb#L3 to read
@import 'envb_mixins.css.scss'; worked for me.


Running cypress test on docker image locally, and the test fails because of contentWindow of null

Hi Team, some help is appreciated. I am running cypress in docker container locally, I use the following command
Docker run -it -v $PWD:/e2e -w /e2e —entrypoint=cypress cypress/included:5.5.0 run
When I run this command , I get the following issue.
TypeError: Cannot read property ‘contentWindow’ of null
I don’t have any code related to iframes, please let me know what are the possible issues.

Try https://on.cypress.io/debugging and paste screenshots / logs here. Or the best - create a reproducible example, otherwise we have nothing to go on. This is the closest issue we see - is there shadow dom? https://github.com/cypress-io/cypress/issues/4156#issuecomment-491755310

@bahmutov  I see there is a docIframe being added while I am trying to load the application in cypress, is this could be the issue?

can you paste your support file? What are the things you load there?

import "./commands";
Cypress.on("uncaught:exception", () => {
return false;
});
Cypress.on("window:load", (window) => {
// Get webApp iframe
const docIframe = window.parent.document.getElementById("Your App: 'my app mane'");
const webAppWindow = docIframe.contentWindow;
// Get current cypress server thats started
const server = Cypress.state().server;
if (server) {
// bind server to our webApp window
server.bindTo(webAppWindow);
}
});

Where is this code in your support file coming from?

I believe we have added it to execute the test suites in ci pipeline back then when we were trying multiple different things!

I think you can comment those out if you don't need them, and I have no idea what that code is supposed to do

As soon as I commented out I see this issue.
http://localhost:3000/
We attempted to make an http request to this URL but the request failed without a response.
We received this error at the network level:

Error: connect ECONNREFUSED <IP_ADDRESS>:3000

Common situations why this would fail:

you don't have internet access
you forgot to run / boot your web server
your web server isn't accessible
you have weird network configuration settings on your computer

is the webserver accessible from inside the Docker container? Like it seems Cypress is requesting localhost:3000 where the app is running, but it is not there. Maybe you need to use Docker settings to determine the accessible URL?

Is there a way I can tell the docker to run the application, all I see from https://www.cypress.io/blog/2019/05/02/run-cypress-with-a-single-docker-command/ is to run the application with the single command, i tried executing the same, and it server is not able to load.

Well because I don’t know how you run and start the app, and how you configure the Docker networking I’m not sure how to help you. Make sure the test container can access the web app url, it is probably different from localhost url since localhost in the container running cypress tests is not the localhost outside (where you app is probably running)
Sent from my iPhone

On Nov 2, 2020, at 13:05, AB1519<EMAIL_ADDRESS>wrote:

Is there a way I can tell the docker to run the application, all I see from https://www.cypress.io/blog/2019/05/02/run-cypress-with-a-single-docker-command/ is to run the application with the single command, i tried executing the same, and it server is not able to load.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Thank @bahmutov


Deleting Feature of Saved Project Missing

Currently we have no option available to delete a saved Project.

Hey, @opticod How to import the android project in android studio?

it is not getting imported by simply using the import project option

Hi @nehaPolo , make sure you import or open the source-code folder. and after that you have to fix plugin version and sync the project .
Make this changes to build.gradle
buildscript {
    repositories {
        jcenter()
        mavenCentral()
    }
    dependencies {
        classpath 'com.android.tools.build:gradle:1.5.0'

        // NOTE: Do not place your application dependencies here; they belong
        // in the individual module build.gradle files
    }
}

Hope this helps.


Experimental: Downloadable Formats API testing

Summary | Résumé
This PR contains some early/experimental code related to #2793:

Wires up the Download button on the Responses page to the new Downloadable Formats API endpoint
Adds additional buttons for downloading other formats (csv, zip)
Adds a prop to the handleDownload method to toggle between "html", "zip" and "csv" formats
Updates the response handler for HTML to loop over the json data, extract the html, and generate the rendered document for downloading
Adds a 200ms delay to the above loop to make downloading large numbers of individual responses more consistent

closing superseded by #2828


Context menu automatically gets triggered

VSCode Version: 1.30.1
OS Version: Ubuntu 16.04

It's hard to open context menu (in new design) by clicking mouse right button, because it closes immediately or trigger first point "go to definition". It seems double click triggered. I opened context menu in file system (folder, terminal) and it worked correctly. Probably it's not mouse bug.

@razor09 I have this same problem, it started once the window styling was switched around from native to custom. Try to set window.titleBarStyle back to native, it seems to have fixed it for me.

@reishapira return to window.titleBarStyle: 'native' solves this problem. Thanks a lot.

don't think it has anything do to with zoom? happens @ zoom = 1  too

Rather than trying to fix the math, maybe require at least X pixels of mouse movement in order for any of the menu items becoming clickable?

The menu only comes up when releasing the mouse, so this appears to be fixed.


Do not instrument abstract doCall methods of Closures

It makes no sense and breaks valid classes.
Fixes #28389

@bot-gradle test this

I've triggered the following builds for you. Click here to see all build failures.

PullRequestFeedback build

The merge queue build has started. Click here to see all failures if any.


Improve error handling logic for effectively once

Motivation
As a part of solving #5218
Modifications
When there are BK write errors we need to fence the topic and reset highestSequencedPushed -> highestSequencedPersisted

rerun cpp tests

rerun cpp tests

run integration tests

What if the client produces [M1, seq:1],[M2, seq:2],[M3, seq:3] asynchronously. M1 succeeds, M2 fails with a BK error, the managed ledger recovers from the error, then M3 hits the broker and is persisted. At this point, M2 can retry, but the message is lost because seq:2 is lower than seq:3.

The current guard against this scenario is that managed ledger will reject all the writes for a period of 10sec. In practical terms, this should avoid all races between threads (for non-blocking ops), though of course it does not give 100% proof.
The next step is to have managed ledger to stay in "error mode" after write failure, until we manually set it back into normal mode, after all the pending ops are done and we got the chance of resetting the topic.

rerun integration tests

rerun integration tests

rerun integration tests

What if the client produces [M1, seq:1],[M2, seq:2],[M3, seq:3] asynchronously. M1 succeeds, M2 fails with a BK error, the managed ledger recovers from the error, then M3 hits the broker and is persisted. At this point, M2 can retry, but the message is lost because seq:2 is lower than seq:3.

The current guard against this scenario is that managed ledger will reject all the writes for a period of 10sec. In practical terms, this should avoid all races between threads (for non-blocking ops), though of course it does not give 100% proof.
The next step is to have managed ledger to stay in "error mode" after write failure, until we manually set it back into normal mode, after all the pending ops are done and we got the chance of resetting the topic.

Maybe we need to rebrand our "exactly-once" again from "effectively-once" to "probably-once".
I think there needs to be some cooperation with the client w.r.t. failures. A client could have a write pending during the time that the error occurs on a previous write and that error being handled, so when the write hits the broker it proceeds as normal, losing the previous write forever.
Maybe we should have some sort of epoch to represent the client <-> producer relationship? When an error occurs on a write, all subsequent writes from that epoch should fail. The error should be kicked back to the client, which should then have to reestablish it's current position before preceeding.

In this PR, the sequence of handling errors will be:

Get a write error
"fence" topic
disconnect all producers

Producers will fail to reconnect because of the topic state
This will discard any other publish request in the pipe

Wait until all pending write ops are completed (with failure)
"un-fence" the topic

rerun integration tests

rerun integration tests

rerun integration tests

rerun integration tests

rerun integration tests

rerun integration tests

rerun integration tests

rerun integration tests


fix: adjust exceptionhandling for encryption

Description
Exception-handling was added to the CryptoHelper to properly map the System-exceptions that are thrown by the Aes-classes to Configuration resp. ConflictExceptions
Why
To handle the exceptions thrown by the cryptoHandler to handle the failing process steps correctly
Issue
N/A
Checklist

[x] I have followed the contributing guidelines
[x] I have performed IP checks for added or updated 3rd party libraries
[x] I have created and linked IP issues or requested their creation by a committer
[x] I have performed a self-review of my own code
[x] I have successfully tested my changes locally
[x] I have added tests that prove my changes work
[x] I have checked that new and existing tests pass locally with my changes
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have added copyright and license headers, footers (for .md files) or files (for images)

 Quality Gate failed
Failed conditions  76.5% Coverage on New Code (required ≥ 80%)
See analysis details on SonarCloud

test coverage results will be ignored as they appear to be faulty: supposedly 12 changed lines without coverage - at the same time sonar shows it as if the new lines are all covered...


Every time an user installs an app update, a new installation is registered in his profile.

When an user install an App update from the store, the next time he opens the app, a new installation is registered in his "Persons" profile, so, as it shows in the picture below, the user now has 2 installations, and when i send a push notification to that user email, the infobip is sending 2 pushes, one for both installations, but the older one always throws the following error: Expired pushRegistrationId (code 8001).
How do i prevent this behavior? i don't want to register a new installation for every app update. Our user base on "Persons" module is ful of garbage installations because of this.

Package version:
"infobip-mobile-messaging-react-native-plugin": "8.4"
SDK Initialization on index.js:
mobileMessaging.supportedEvents.forEach(event => {
    mobileMessaging.subscribe(event, handleMobileMessagingEvent);
});

mobileMessaging.init(
    {
        applicationCode: app_settings.infobip.appCode,
        ios: { notificationTypes: ['alert', 'badge', 'sound'] },
    },
    () => {},
    error => {
        console.log('MobileMessaging error: ', error?.description);
    }
);
...
AppRegistry.registerRunnable(appName, props => {
    AppRegistry.registerComponent(appName, () => App);
    TrackPlayer.registerPlaybackService(() => Player);
    AppRegistry.runApplication(appName, props);
});

After user login:
mobileMessaging.personalize(
            {
                userIdentity: {
                    emails: [email],
                    externalUserId: id
                },
                userAttributes: {
                    firstName: first_name,
                    lastName: last_name,
                    customAttributes,
                },
                forceDepersonalize: true,
            },
            user => console.log('infobip user personalized', { user }),
            error => console.error('infobip user personalized error', { error })
);

Hello,

App updates should not create new registrations, you should check your implementation thoroughly. If app storage is cleaned - if someone cleans the data on Android for example, then the new registration will be created. From analysing few registrations I was able to find successful updates without reissuing registration id (person profile ids 14854, 31861, event - Push contact changed, property: app version, from: 3.5.2, to: 3.6.0).

There are a lot of personalize/depersonalize calls. If your app has user sessions, it is better to perform personalize/depersonalize only on login/logout, as described here - https://github.com/infobip/mobile-messaging-react-native-plugin/wiki/Personalization-implementation-for-mobile-apps-with-authorization

In case you need additional support or help with handling any sensitive private account data, please forward your request to<EMAIL_ADDRESS>

Closing the issue because no additional questions or comments appeared for a long time.


Any update for Python 3.9?

Is there any update or alternative for Python 3.9?

Hi All,
We are waiting for feedback

Hello, maybe PyAudioWPatch is for you. Available for Windows x64/x32 Python 3.{7-11}
Everything is based on the latest releases of PyAudio and PortAudio. Loopback support is now more canonical.

Yep, PyAudioWatch works like a charm. THANK YOU! I did a sample using PyAudioWatch on Python 3.10.10 and worked good!

I get an empty 1KB recording file after running the pawp_record_wasapi_loopback.py
Am I missing something?


Cherry pick for API_LEVEL_14

Description
Cherry picks from:

#465 Update workflow to be able to build some apps on Stax
#468 Add Eth app in the list of apps to build on Stax target
#474 [nbgl] PIC some addr
#475 lib_ux/include/ux.h: Fix LNX and LNSP version of UX_WAIT_DISPLAYED()
#476 workflows/build_all_apps.yml: Remove apps repos that are archived
#481 Fix nbgl_getTextMaxLenInNbLines() computing wrong len for non wrappable text
#477 Makefile.rules_generic: Stop allowing app custom SCRIPT_LD
#472 Rework install_parameters generation
#473 ledger_assert: add LEDGER_ASSERT macro with debug capacities
#487 Fix ledger assert compatibility with DISABLE_UI

Changes include

[ ] Bugfix (non-breaking change that solves an issue)
[x] New feature (non-breaking change that adds functionality)
[x] Breaking change (change that is not backwards-compatible and/or changes current functionality)
[ ] Tests
[ ] Documentation
[ ] Other (for changes that might not fit in any category)

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

:exclamation: No coverage uploaded for pull request base (API_LEVEL_14@deb22a5). Click here to learn what that means.

Additional details and impacted files
@@               Coverage Diff               @@
##             API_LEVEL_14     #484   +/-   ##
===============================================
  Coverage                ?   59.44%
===============================================
  Files                   ?       12
  Lines                   ?     1684
  Branches                ?        0
===============================================
  Hits                    ?     1001
  Misses                  ?      683
  Partials                ?        0

Flag
Coverage Δ

unittests
59.44% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


STM32CubeIDE Usage Statistics

STM32CubeIDE by default sends usage-statistics to ST to "improve its products". You can opt-out of the usage-statistics in the preferences, which is not very intuitive and easy to miss.
When usage statistics is on, this domain is requested via DNS: stmicroelectronics.d3.sc.omtrdc.net (as seen in Wireshark)
The omtrdc.net is known as an analytics and tracking platform from Adobe.
Can you please add stmicroelectronics.d3.sc.omtrdc.net to the blocklist?

Thank you for this Ethan @nandlab.
This is added in commit bdf4bafb and will reflect online soon.
Closing.


Add Iglu Server mirrors to CI/CD process

@jbeemster can we list all servers here? I know only of

com-iglucentral-eu1-prod.iglu.snplow.net


MapViewStateDraw's updateGlowTimer can be simplified

MapViewStateDraw.cpp's updateGlowTimer can be simplified using std::chrono and a single call to std::sin.
Simplifying it removes all the Conversion from 'int' to 'uint8_t'; possible loss of data. warnings present in drawResourceInfo.
Using std::sin will remove the need for a branch. With no branch prediction, the code will run faster. Using const and constexpr variables will allow the optimizer to combine all the variables into a single value, thus reducing the whole function to a single addition, a single multiplication, and a single call to std::sin.
Using std::chrono removes the ambiguity as to what GLOW_TIMER.accumulator >= 10 does and what it represents. I suspected it was meant to be

When the delta time is greater than or equal to 10 milliseconds, advance the GLOW_STEP by +/-20 units towards 255 or 0. i.e. a frequency of 26 times per second or a period of 0.38 seconds.

Simplifying it to a time-based function it becomes:

Interpolate from 0 to 255 and back over a period of 0.38 seconds.

The new code as refactored becomes:
//...Includes and Globals
#include <chrono>
#include <cmath>

Timer GLOW_TIMER;
uint8_t GLOW_STEP = 0;

//...Function
static void updateGlowTimer()
{
	constexpr auto maxGlowSeconds = std::chrono::duration<float>{0.38f};
	const std::chrono::duration<float> accumulatorSeconds = std::chrono::duration<float, std::milli>{GLOW_TIMER.accumulator()};
	const auto t = accumulatorSeconds / maxGlowSeconds;
	// Adjust amplitude from [-1.0, 1.0] to [0, 255]
	GLOW_STEP = static_cast<uint8_t>((1.0f + std::sin(t)) * 0.5f * 255.0f);
}

//...Initial declaration and Usage
uint8_t glowColor = shouldCommonMetalsGlow ? GLOW_STEP : 255;
r.drawText(*MAIN_FONT, string_format("%i", mPlayerResources.commonMetals()), initialXPosition + margin, textY, 255, glowColor, glowColor);

r.drawSubImage(mUiIcons, x + offsetX, y, 80, 16, constants::RESOURCE_ICON_SIZE, constants::RESOURCE_ICON_SIZE);
bool shouldRareMetalsGlow = mPlayerResources.rareMetals() <= 10;
glowColor = shouldRareMetalsGlow ? GLOW_STEP : 255;
r.drawText(*MAIN_FONT, string_format("%i", mPlayerResources.rareMetals()), (x + offsetX) + margin, textY, 255, glowColor, glowColor);

Using std::sin will remove the need for a branch. With no branch prediction, the code will run faster.

This is false. The std::sin function is quite a heavy operation. Internally it will use lots of branching and looping. There's no way that's going to be faster than a simple branch.

I suppose the real question here is what kind of smoothing do we want. Do we want simple linear smoothing, or do we want smooth sin smoothing. There are other options too. For reference, we may want to examine CSS easings:
https://easings.net/en
Questions about the style of transition we want probably trump concerns over performance. Performance is not exactly a big concern for this simple use case.
Do we want linear transitions, as we currently have, to do the pulsed transition of colors, or do we want a more smooth transition? I think it might be fun to experiment with more smooth transitions, such as polynomial interpolation, Bézier curves, or sin/cos curves. Quite likely, we can do the transition using lighter weight interpolations other than sin, which can produce results so similar that we are unlikely to notice the difference.

For some code examples, I found this:
https://gist.github.com/gre/1650294

I would be amicable to easing functions: https://www.youtube.com/watch?v=mr5xkf6zSzk

Adding reference to #285, which updated the updateGlowTimer() method (and renamed it to calcGlowIntensity()).

Looking back at this, I'm not sure we actually want to tackle this at this time. The idea of having easing functions available is kind of nice, and I would support using such functions. However, it's more of a neat thing than something that is in any real immediate need.
I recommend we close this for now, as not a priority, with possibility that it be re-opened in the future if we have more pressing need for it.


Instruments Learning Feature

Hi there! Thanks for opening this issue. We appreciate your contribution to this open-source project. We aim to respond or assign your issue as soon as possible.

Assign this issue to me.

Hello .I am intrested in contributing for this task .Please assign me this under GSSOC'24

Hey Vaibhav , assign this issue to me


Multiple Sequences Not Handled correctly in upload_sample_status

The function runs an upsert, so if there is an existing sequence for a sample it will just override it.
We could switch the upsert to an insert, but I think upserting is still useful in cases where it makes sense and we could get left with a bunch of duplicate sequences.
Current suggestion is to take in the fluidX ID as input, compare this with any existing sequences for the sample, and if it's a match, update, otherwise insert.

Donzo https://github.com/populationgenomics/sample-metadata/pull/320


visualize fMRI with pycortex

Your work is inspiring. Could you share the code for visualizing the nsd 2D brain using pycortex? It has been troubling me for a long time.

Hi,
Apologies for the delayed response. I'm planning on significantly cleaning up this repo soon and adding plotting code.
Are you referencing plotting pycortex using NSD?
If so I am using the exact command here:
https://github.com/ariaaay/NSD/blob/b5307511fd14307484262b414b3059b8ff3e44e7/code/make_pc_tree.py#L302
Except I am not setting the mask parameter (it is optional, I recommend you mask first by setting vol[mask] = np.nan).

Hi,
Apologies for the delayed response. I'm planning on significantly cleaning up this repo soon and adding plotting code.
Are you referencing plotting pycortex using NSD?
If so I am using the exact command here:
https://github.com/ariaaay/NSD/blob/b5307511fd14307484262b414b3059b8ff3e44e7/code/make_pc_tree.py#L302
Except I am not setting the mask parameter (it is optional, I recommend you mask first by setting vol[mask] = np.nan).


hadoop/spark

This tutorial seems to be well out of date. I managed to get it running by folking the elasticluster repo and making a lot of changes. I seem to have a few issues actually running the hadoop cluster, which I'm still working through, I expect some changes to the ansible playbooks might have cause issue with the hadoop/spark cluster.

Hi there,
Thanks for letting us know, and sorry there were issues with the tutorial!
I will have a look through and make fixes where necessary.
Kind regards,
Sonia

All good. I also had to run elasticluster from a python3.7 virtual environment. It didn't work from 3.8.

hey @skiptoniam We've had a couple of tickets come through recently about this. I've been trying to make this work with at least Python 3.10 and I've fixed up a few things.
We're trying to work out if we can continue to support this tutorial, as it does feel like upstream aren't really maintaining it.
Maybe with the work you've done here and my work fixing some of the newer Python issues, we can keep it going. Are you going to be using Elasticluster longish term?


suggestion: easier citation of the package

Right now, citation('raincloudplots') returns:
To cite package ‘raincloudplots’ in publications use:

  person) (NA). raincloudplots: The easy way to create raincloud plots. R package version 0.2.0.
  https://github.com/jorvlan/raincloudplots

A BibTeX entry for LaTeX users is

  @Manual{,
    title = {raincloudplots: The easy way to create raincloud plots},
    author = {{person)}},
    note = {R package version 0.2.0},
    url = {https://github.com/jorvlan/raincloudplots},
  }

ATTENTION: This citation information has been auto-generated from the package DESCRIPTION file and may
need manual editing, see ‘help("citation")’.

Warning messages:
1: In citation("raincloudplots") :
  no date field in DESCRIPTION file of package ‘raincloudplots’
2: In citation("raincloudplots") :
  could not determine year for ‘raincloudplots’ from package DESCRIPTION file

Adding a CITATION file would make it easier to cite the package (here is an example from ggplot2, and here is the doc about CITATION files).

Thank you for providing us with your feedback.
We will implement this in the next release.


finalize coveralls integration

Coverage remained the same at 68.675% when pulling f94397523dd618b96634064474bc68329f73b84d on muzir:master into e647b3475c58350000133c70d30d3e9dc2bcf71d on iyzico:master.


⚠ Bofrost.be has degraded performance

In 209efeb, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 2528 ms

Resolved: Bofrost.be performance has improved in 9c2ac96.


printer_width is None

Hey team, I could be wrong but v2.0.0 may accidentally set dbt flags.PRINTER_WIDTH to None and this breaks other dbt packages that I am using in my environment.

Looking at the dbt code (and in particular this comment), it seems it should be fairly safe to set printer_width to default to 80.

Have you tried setting printer_width manually? I.e. via an environment variable? I'm curious what happens then.
Maybe this could be hiding an underlying bug somewhere else, but it seems like a quick and easy fix to work with other packages. Happy to set the default while we investigate a bit further.

Yeah tried setting it manually but does not work. I think you need to set the default 80 in this line

Yup, that's what I'm doing (see linked PR). It should be set-able though, so wanted to investigate further...

Will merge the PR regardless, thanks for your input!

Thanks @tomasfarias !


cert manager API showing error -  "x509: certificate has expired or is not yet valid"

Describe the bug:
[root@ocp-svc cert-issue]# cmctl check api
Not ready: Internal error occurred: failed calling webhook "webhook.cert-manager.io": failed to call webhook: Post "[https://cert-manager-webhook.openshift-cert-manager.svc:443/mutate?timeout=10s":](https://cert-manager-webhook.openshift-cert-manager.svc/mutate?timeout=10s%22:) x509: certificate has expired or is not yet valid: current time 2023-03-03T08:18:27Z is before 2023-03-03T14:51:52Z
[root@ocp-svc cert-issue]#

Expected behaviour:
cert manager API should be in functional state.
Steps to reproduce the bug:

Install cert-manager on OCP or K8s platform
reboot workers
run -- cmctl check api on master or bastion.

Anything else we need to know?:
[root@r7515-166-con6 ~]# kubectl logs -n cert-manager  cert-manager-webhook-8bc4ff568-qqc8g
W0309 16:57:06.368572       1 client_config.go:615] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
W0309 16:57:06.369361       1 client_config.go:615] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I0309 16:57:06.369593       1 webhook.go:69] cert-manager/webhook "msg"="using dynamic certificate generating using CA stored in Secret resource"  "secret_name"="cert-manager-webhook-ca" "secret_namespace"="cert-manager"
I0309 16:57:06.369781       1 server.go:150] cert-manager/webhook "msg"="listening for insecure healthz connections"  "address"=":6080"
I0309 16:57:06.369810       1 server.go:163] cert-manager/webhook "msg"="listening for secure connections"  "address"=":10250"
I0309 16:57:06.369849       1 server.go:189] cert-manager/webhook "msg"="registered pprof handlers"
I0309 16:57:06.370848       1 reflector.go:219] Starting reflector *v1.Secret (1m0s) from external/io_k8s_client_go/tools/cache/reflector.go:167
I0309 16:57:07.399197       1 dynamic_source.go:199] cert-manager/webhook "msg"="Updated serving TLS certificate"
I0309 09:40:48.427941       1 logs.go:58] http: TLS handshake error from <IP_ADDRESS>:7439: remote error: tls: bad certificate
I0309 09:40:50.463251       1 logs.go:58] http: TLS handshake error from <IP_ADDRESS>:6653: remote error: tls: bad certificate
.
.
.
I0309 09:57:19.680624       1 logs.go:58] http: TLS handshake error from <IP_ADDRESS>:38715: remote error: tls: bad certificate
I0309 09:57:42.501928       1 dynamic_source.go:135] cert-manager/webhook "msg"="Detected root CA rotation - regenerating serving certificates"
I0309 09:57:42.529025       1 dynamic_source.go:199] cert-manager/webhook "msg"="Updated serving TLS certificate"
I0309 09:57:46.546170       1 logs.go:58] http: TLS handshake error from <IP_ADDRESS>:59324: EOF

Workaround:
[root@r7515-166-con6 cert-issue]# kubectl delete secrets -n cert-manager cert-manager-webhook-ca
secret "cert-manager-webhook-ca" deleted <<<
[root@r7515-166-con6 cert-issue]# kubectl get secrets -n cert-manager
NAME                      TYPE     DATA   AGE
cert-manager-webhook-ca   Opaque   3      11s

[root@r7515-166-con6 cert-issue]# cmctl check api
The cert-manager API is ready

Environment details:

Kubernetes version:1.24.6
cert-manager version: 1.11
Install method: openshift-operator/static
All nodes are NTP synced, same zone and time

/kind bug

current time 2023-03-03T08:18:27Z is before 2023-03-03T14:51:52Z

That seems like the cert might have been issued with a wrong NotBefore. I wonder if it's an issue with time on the worker nodes. Perhaps you want to check the NotBefore on the serving cert and on the node to which webhook is allocated.

I double checked (on GKE, with cert-manager v1.11.0) that cert-manager installation recovers successfully after rebooting worker node.

We have already verified time on all master and worker nodes, all are having same time. Time mismatch doesn't seems to be an issue here. What other settings or logs we should check?

Is this happening every time you restart the worker nodes? Or only sometimes?

Is this happening every time you restart the worker nodes? Or only sometimes?

Yes everytime.

I keep running into this error too.
My setup is:

argocd
cert-manager v1.11.0

Helm Output (manual)
[Mon 20 Mar 10:11:14 GMT 2023] simon@symphony ~/src/github.com/****/**** helm upgrade *** charts/**** -n ****
Error: UPGRADE FAILED: cannot patch "****" with kind Certificate: Internal error occurred: failed calling webhook "webhook.cert-manager.io": failed to call webhook: Post "https://cert-manager-webhook.cert-manager.svc:443/mutate?timeout=10s": x509: certificate has expired or is not yet valid: current time 2023-03-20T10:11:17Z is after 2023-03-16T11:32:41Z && cannot patch "****" with kind Issuer: Internal error occurred: failed calling webhook "webhook.cert-manager.io": failed to call webhook: Post "https://cert-manager-webhook.cert-manager.svc:443/mutate?timeout=10s": x509: certificate has expired or is not yet valid: current time 2023-03-20T10:11:17Z is after 2023-03-16T11:32:41Z && cannot patch "****" with kind Issuer: Internal error occurred: failed calling webhook "webhook.cert-manager.io": failed to call webhook: Post "https://cert-manager-webhook.cert-manager.svc:443/mutate?timeout=10s": x509: certificate has expired or is not yet valid: current time 2023-03-20T10:11:17Z is after 2023-03-16T11:32:41Z

ArgoCD Application
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  creationTimestamp: "2023-02-24T15:48:57Z"
  generation: 2112
  name: cert-manager
  namespace: argocd
  resourceVersion: "4257972"
  uid: 5f089033-6658-4d9e-ba14-6794f16dbeff
spec:
  destination:
    name: in-cluster
    namespace: cert-manager
  project: default
  source:
    chart: cert-manager
    helm:
      parameters:
      - name: installCRDs
        value: "true"
      releaseName: cert-manager
    repoURL: https://charts.jetstack.io
    targetRevision: v1.11.0
  syncPolicy:
    automated:
      selfHeal: true
    syncOptions:
    - CreateNamespace=true

The Secret...
[Mon 20 Mar 10:10:34 GMT 2023] simon@symphony ~/src/github.com/***/*** openssl x509 -in cert -noout -text
Certificate:
    Data:
        Version: 3 (0x2)
        Serial Number:
            a3:22:72:17:d3:d5:d1:0f:a9:97:76:29:55:aa:c7:1a
        Signature Algorithm: ecdsa-with-SHA384
        Issuer: CN = cert-manager-webhook-ca
        Validity
            Not Before: Jan 30 10:36:44 2023 GMT
            Not After : Jan 30 10:36:44 2024 GMT
        Subject: CN = cert-manager-webhook-ca
        Subject Public Key Info:
            Public Key Algorithm: id-ecPublicKey
                Public-Key: (384 bit)
                pub:
                    04:8a:7c:e4:af:9d:09:ff:1d:0a:35:51:06:fe:db:
                    1f:19:40:65:55:02:ea:80:e9:a1:84:b0:ce:31:07:
                    03:55:17:1e:b9:de:60:fe:39:72:7b:4c:2a:df:a7:
                    a7:b1:8e:29:4f:14:a6:93:8d:ae:96:eb:d7:48:1c:
                    4c:83:ff:c2:3b:b9:13:c7:ad:ff:5b:b7:c9:5d:25:
                    c5:30:11:c9:0c:40:f5:4e:bf:70:be:da:6d:e1:dc:
                    f7:8e:b5:e4:02:61:fb
                ASN1 OID: secp384r1
                NIST CURVE: P-384
        X509v3 extensions:
            X509v3 Key Usage: critical
                Digital Signature, Key Encipherment, Certificate Sign
            X509v3 Basic Constraints: critical
                CA:TRUE
            X509v3 Subject Key Identifier:
                49:E4:EF:9E:C2:CE:65:FF:1B:F0:9C:CE:51:08:55:79:DF:53:FC:75
    Signature Algorithm: ecdsa-with-SHA384
    Signature Value:
        30:66:02:31:00:9f:79:aa:aa:ce:0e:14:ca:92:9f:9b:b1:59:
        f4:58:9f:68:8e:2e:da:d3:b6:68:b8:67:9c:e0:74:fe:4b:fc:
        60:70:90:42:d1:d1:d5:a5:e7:57:69:64:a0:9f:47:b8:61:02:
        31:00:d7:8c:12:86:09:23:19:32:0e:9f:45:f5:84:93:e9:fe:
        df:2e:1b:ea:93:97:35:16:6a:df:cc:0d:82:2a:cd:89:80:d5:
        1d:a0:ca:ab:b0:86:9e:ac:2b:ed:f8:51:db:39

So what I'm hypothesizing is....

Cert has been rotated
Webhook doesn't pick up the change, for some reason (here's where your input comes in!)
A restart of the webhook pod solves the issue, thus adding some weight to the hypothesis

Now this is running on my laptop, which is -- for burn out reasons -- not on during the weekend, I dunno if that's going to have some bearing on the situation, but you never know.

@irbekrm What specific NotBefore stamp should be checked and steps for timing confirmation. (other than running timedatectl over host)?

Can you please elaborate on how to check this?

@irbekrm What specific NotBefore stamp should be checked and steps for timing confirmation. (other than running timedatectl over host)?

Can you please provide some information on this query?

current time 2023-03-03T08:18:27Z is before 2023-03-03T14:51:52Z

That seems like the cert might have been issued with a wrong NotBefore. I wonder if it's an issue with time on the worker nodes. Perhaps you want to check the NotBefore on the serving cert and on the node to which webhook is allocated.

Hi @irbekrm ,
We have checked the timesync on the worker and master nodes where the cert pods are relying. (using timedatectl command). So all the nodes are in timesync with same timezone too.
Can you please let us know how to check the NotBefore time or time inside the pods?

facing  the exact same issue with kind, argoCD and cert-manager v1.15.3:
>  k logs -n cert-manager cert-manager-9647b459d-r76bs
I0829 00:05:12.780155       1 sync.go:62] "Error initializing issuer: Get \"https://acme-v02.api.letsencrypt.org/directory\": tls: failed to verify certificate: x509: certificate has expired or is not yet valid: current time 2024-08-29T00:05:12Z is after 2022-06-22T20:05:55Z" logger="cert-manager.controller" resource_name="letsencrypt-prod" resource_namespace="cert-manager" resource_kind="Issuer" resource_version="v1"
E0829 00:05:12.780493       1 controller.go:162] "re-queuing item due to error processing" err="Get \"https://acme-v02.api.letsencrypt.org/directory\": tls: failed to verify certificate: x509: certificate has expired or is not yet valid: current time 2024-08-29T00:05:12Z is after 2022-06-22T20:05:55Z" logger="cert-manager.controller" key="cert-manager/letsencrypt-prod"


Revision TH

Additionally to what I've already mentioned in the issues below, I've added a paragraph about large systems to the manuscript. I'm not sure if this is the way to go but I also didn't know where else to put this information. @brookehus
fixes #138
fixes #140
adds some information about why feature selection / dimension reduction are important (#147)

fixes #139

I'd be happy if somebody could have a look at the feature_tic_correlation for the di-alanine. I've added some code on how one could do a more systematic search for a correlating feature in order to understand the TICA projection, but I'm not sure if that conveys the message.

Thanks very much for the review!

All requested changes above were incorporated (hope I didn't miss anything). Major refactoring of the manuscript section about large systems was done with @cwehmeyer. I'd be happy if @brookehus could have a look especially at the manuscript. Thanks again.

After reading #155 I have a question about some of the CK test discussed in this PR, more for my personal understanding than for any manuscript changes. If I am reading correctly it seems like, if a CK test is failing, then maybe we should try a CK test with a different number of metastable states (e.g. line 143 in notebook 03). However, when is this number of metastable states actually used later in analysis? What does it mean if a CK test for 3 metastable states is bad but a CK test for 4 metastable states is good?

Important question. In principle, the CK-test as conducted in Pyemma requires the additional assumption of the number of macrostates. So the Markovianity assumption is tested by comparing the long time predictions of the current model with new estimates, both with the additional layer of coarse graining. If it fails with, say, 3 states, the model with this number of states cannot predict future transition probabilities. One could also say that this particular coarse graining does not yield a partitioning into Markov states. If the test passes with 4 states, those states are actually Markovian, i.e. knowledge of the current macrostate is enough to predict the future behavior. Don't know if that's a good explanation, we can also discuss this later.


remove deprecated action

kubernetes-sigs/release-actions/setup-publish-release is inside the kubernetes-sigs/release-actions/publish-release

Thanks!


Vertical filtering on inserts

For insertions, the docs talk about using Prefer: return=representation to get the inserted object back. Moreover they also talk about applying vertical filtering to it, e.g., ?select=foo.
Where would one specify the select=foo part in the POST request of an insert operation?

Yeah, that's a bug reported in https://github.com/begriffs/postgrest/issues/1087, this will be fixed on the next release.


gecode_6: add patch fixing clang build

Description of changes
ZHF: #172160
https://github.com/Gecode/gecode/pull/74
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[x] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 173940 run on aarch64-darwin 1

1 package marked as broken and skipped:

gecode


Generate string literals instead of enums

Hi! Big fan this library. One thing I'd like to configure but can't find in the docs is switching the enums used for inputs to string literals. Our team don't use enums in typescript at all, we find there isn't really value in them given you can achieve the same type safety by using string literals, without having to import something extra, and without having any ambiguity about how typescript will compile to js.
So basically it'd be great to change the generate type for this example input type:
export enum IssueState {
  CLOSED = 'CLOSED',
  OPEN = 'OPEN',
}

/** Filter by IssueState */
export interface IssueStateInput {
  eq: IssueState
}

To:
export type IssueState = 'CLOSED' | 'OPEN'

/** Filter by IssueState */
export interface IssueStateInput {
  eq: IssueState
}

I think at runtime they'd be identical, but no need to import anything extra to specify an IssueState.

We have an option enumsAsStrings in gqty.config.js, you may try that.

@mmkal Feel free to reopen if the option above doesn't work.

Perfect, thank you! Not sure how I didn't find that in the docs. Actually enumsAsConst is even better, since it allows for either usage.


feat(metabase): upgrade to version 50.18

Hi @Ant0wan, I'm glad to see you along with other peoples to contribute. However, contributions on PR #126 (this PR) and #127 #128 #129 #130 #131 #132 #133 #134 #135 #136 #137 you're doing it wrong  ... about versioning, and it really not necessary to update appVersion for every metabase releases, you can always deploy with your version of choice by overriding value image.tag during helm installation.
Sorry I have to /close #126 #127 #128 #129 #130 #131 #132 #133 #134 #135 #136 #137


[pugixml] Build error on x64-windows

Package<EMAIL_ADDRESS>
**Host Environment**

- Host: x64-windows
- Compiler: MSVC 19.41.34120.0
-    vcpkg-tool version: 2024-08-01-fd884a0d390d12783076341bd43d77c3a6a15658
    vcpkg-scripts version: ee2d2a100 2024-09-10 (5 hours ago)

**To Reproduce**

`vcpkg install pugixml:x64-windows`

**Failure logs**

-- Downloading https://github.com/zeux/pugixml/archive/v1.14.tar.gz -> zeux-pugixml-v1.14.tar.gz...

CMake Error at scripts/cmake/vcpkg_download_distfile.cmake:32 (message):

      Failed to download file with error: no such file or directory
      If you are using a proxy, please check your proxy setting. Possible causes are:

      1. You are actually using an HTTP proxy, but setting HTTPS_PROXY variable
         to `https://address:port`. This is not correct, because `https://` prefix
         claims the proxy is an HTTPS proxy, while your proxy (v2ray, shadowsocksr
         , etc..) is an HTTP proxy. Try setting `http://address:port` to both
         HTTP_PROXY and HTTPS_PROXY instead.

      2. If you are using Windows, vcpkg will automatically use your Windows IE Proxy Settings
         set by your proxy software. See https://github.com/microsoft/vcpkg-tool/pull/77
         The value set by your proxy might be wrong, or have same `https://` prefix issue.

      3. Your proxy's remote server is out of service.

      If you've tried directly download the link, and believe this is not a temporary
      download server failure, please submit an issue at https://github.com/Microsoft/vcpkg/issues
      to report this upstream download server failure.

Call Stack (most recent call first):
  scripts/cmake/vcpkg_download_distfile.cmake:270 (z_vcpkg_download_distfile_show_proxy_and_fail)
  scripts/cmake/vcpkg_from_github.cmake:106 (vcpkg_download_distfile)
  ports/pugixml/portfile.cmake:1 (vcpkg_from_github)
  scripts/ports.cmake:192 (include)

How can I do for it?

Thanks for posting this issue, could you work around this issue as following steps:

Download https://github.com/zeux/pugixml/archive/v1.14.tar.gz manually.
Rename it to zeux-pugixml-v1.14.tar.gz, and put it to .\vcpkg\downloads\
Try to build again.

Thanks for posting this issue. Please reopen this issue if this is still a problem for you.


Specifying $emits for automatic documentation and validation

What problem does this feature solve?
As it is, we can specify the props, their name, type, a validator, all that jazz. Some documenting tools take advantage of this in order to create documentation of the component. To make documentation more useful, I think adding an optional 'emits' specification would help better specify the ins and the outs of the component. I suppose that, validation could be added to this specification to ensure that $emit events don't emit payloads in an unspecified format, which would protect the parent from getting screwy data.
What does the proposed API look like?
emits: {
  formCompleted: {
    payload: {
      type: 'object',
      properties: {
        name: 'string',
        age: 'number',
        gunch: {
          type: 'number',
          validator: function(value) {
            return value < 5;
          }
        }
      }
    }
  },
  nameEntered: {
    payload: {
      type: 'string'
    }
  },
  buttonClicked: 'string' // or null since it doesn't have a payload?
}

More or less dup of #6040
Closing because of the comment https://github.com/vuejs/vue/issues/6040#issuecomment-313658773
About payload checks, That is something that can and should be handled with typings like Typescript


Metadata plugin: Brain region label shown as "undefined" if the same brain region @id appears twice on the same resource

In some cases, we have resources with the same brain region information in

brainLocation.brainRegion
neuriteFeature.projectionBrainRegion

In those cases, the Metadata plugin is sometimes showing "undefined" as Brain Region (since the label only appears once in the resource graph)
This behaviour could potentially be avoided by fetching the /source endpoint of the resource

@annakristinkaufmann could you provide a couple of examples so that we can fix it? if possible a project where you have many resources with that specific path

Hey team! Please add your planning poker estimate with ZenHub @adulbrich @imsdu @nicwells @smitfire @wwajerowicz


Add ability to generate tokens

I wrote some code to be able to generate tokens in cdk.
The tricky thing with tokens is that they have to be created new every time they are deployed, this is because we cannot return the actual token_value from a request to the databricks api (I assume this is for safety reasons).
The implementation can be found here:
https://github.com/godatadriven/databricks-cdk/pull/808

fixed in: https://github.com/godatadriven/databricks-cdk/pull/808


make all-homebrew fails during mkdir scripts/ppx_gen_flowlibs

Flow version: 0.105.2
Expected behavior
Build to complete successfully on mac when using make all-homebrew.
Actual behavior
Fails with the following error:
+ mkdir scripts/ppx_gen_flowlibs
mkdir: scripts/ppx_gen_flowlibs: File exists
Command exited with code 1.
Failure:
  Error during command "mkdir scripts/ppx_gen_flowlibs": Ocamlbuild_pack.My_std.Exit_with_code(10).

See this homebrew-core pull-request.

Link to Try-Flow or Github repo: No link possible the issue is about building flow on mac.

/cc @mroch

@Moisan do you have the full logs? can't repro locally and the tests on the PR seem gone.

Here is the full log from the Homebrew CI on mojave.


Hydra updates

This PR combines changes from #157072, #152427, and a further update to a hydra commit from last week.
TODOs:

[ ] Decide whether to keep the refactoring, or continue to provide for multiple versions of hydra. I'm leaning towards keeping the refactor in spite of the code churn it causes. The prospect of another version of hydra being reintroduced seems unlikely.
[ ] Remove multi-versioning from the hydra NixOS tests
[ ] Potentially clean up commits (some changes, such as the maintainership changes, should probably not be rolled into the commits they currently lie in)

cc @Mindavi @dasJ who have agreed to be co-maintainers, @lovesegfault who opened the refactoring PR.
Closes #157072, closes #152427.

Gonna try and run this for a bit to see if it works as expected, ping me if you'd like to hear how it went :).
I'm in favor of removing the multi-versioning, so :+1: from me on that one. IMO the commit history is clean enough, and I think this could be acceptable wrt the policy (but I'd recommend to check it if you don't have it fresh in your mind).

Finally got this building (was having some issues with something nvidia related, not sure why it started building fine all of a sudden).
Everything seems to be fine on first glance, started a rebuild of something and that seemed to work fine. No obvious issues otherwise. Will keep this running for a while and report back if I see anything problematic.

There's a merge conflict that should be solved.

Started rebasing: https://github.com/Mindavi/nixpkgs/tree/hydra-updates-2.
Time's up for now, might look at this for a bit this evening.


Started translation of 'Using the Effect Hook' section (WIP)

WIP

Hey, @Kurzdor 👋
Any progress on fixing #58, #73 and #74 PRs?

@klymenkoo Sorry, I was busy last two weeks, I think that tommorow I will finish this PR and start other section.

@Kurzdor any progress with #74?

@Kurzdor please let us know if you need any help with #74.

ну шо там?)) є якийсь прогрес?