500 SERVER ERROR when open /admin/general-page

Describe the bug
500 SERVER ERROR when click hostIP /admin/general-page , other pages work normally
Logs

docker yaml
version: '3.4'
services:
speedtest-tracker:
container_name: speedtest-tracker
ports:
- 8765:80
- 8766:443
environment:
- PUID=1000
- PGID=1000
- DB_CONNECTION=sqlite
volumes:
- ./data:/config
- /path/to-custom-ssl-keys:/config/keys
image: lscr.io/linuxserver/speedtest-tracker:latest
restart: unless-stopped

If you're not including custom SSL certs don't include this line in your config - /path/to-custom-ssl-keys:/config/keys.

If you're not including custom SSL certs don't include this line in your config - /path/to-custom-ssl-keys:/config/keys.如果您不包含自定义 SSL 证书，请不要在配置中包含此行 - /path/to-custom-ssl-keys:/config/keys 。

After removing the parameter - /path/to-custom-ssl-keys:/config/keys, it worked for a while, but after testing a few times, the error "500 server error" occurred again.
Full Logs
cURL error 35: OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to www.speedtest.net:443 (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://www.speedtest.net/api/js/servers?engine=js&https_functional=1&limit=20

I've noticed a phenomenon with this issue; every night, a 500 server error occurs, but by the next day, the general-page becomes accessible again.

Can you follow the FAQ for that error to turn on debugging and post the logs? https://docs.speedtest-tracker.dev/help/faqs#other

[1/2] ConnectException
`GuzzleHttp\Exception\ConnectException:
cURL error 35: OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to www.speedtest.net:443  (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://www.speedtest.net/api/js/servers?engine=js&https_functional=1&limit=20
at /app/www/vendor/guzzlehttp/guzzle/src/Handler/CurlFactory.php:210
at GuzzleHttp\Handler\CurlFactory::createRejection()
(/app/www/vendor/guzzlehttp/guzzle/src/Handler/CurlFactory.php:158)
at GuzzleHttp\Handler\CurlFactory::finishError()
(/app/www/vendor/guzzlehttp/guzzle/src/Handler/CurlFactory.php:110)
at GuzzleHttp\Handler\CurlFactory::finish()
(/app/www/vendor/guzzlehttp/guzzle/src/Handler/CurlHandler.php:47)
at GuzzleHttp\Handler\CurlHandler->__invoke()
(/app/www/vendor/guzzlehttp/guzzle/src/Handler/Proxy.php:28)
at GuzzleHttp\Handler\Proxy::GuzzleHttp\Handler{closure}()
(/app/www/vendor/guzzlehttp/guzzle/src/Handler/Proxy.php:48)
at GuzzleHttp\Handler\Proxy::GuzzleHttp\Handler{closure}()
(/app/www/vendor/laravel/framework/src/Illuminate/Http/Client/PendingRequest.php:1252)
at Illuminate\Http\Client\PendingRequest->Illuminate\Http\Client{closure}()
(/app/www/vendor/laravel/framework/src/Illuminate/Http/Client/PendingRequest.php:1218)
at Illuminate\Http\Client\PendingRequest->Illuminate\Http\Client{closure}()
(/app/www/vendor/laravel/framework/src/Illuminate/Http/Client/PendingRequest.php:1204)
at Illuminate\Http\Client\PendingRequest->Illuminate\Http\Client{closure}()
(/app/www/vendor/guzzlehttp/guzzle/src/PrepareBodyMiddleware.php:35)
at GuzzleHttp\PrepareBodyMiddleware->__invoke()
(/app/www/vendor/guzzlehttp/guzzle/src/Middleware.php:38)
at GuzzleHttp\Middleware::GuzzleHttp{closure}()
(/app/www/vendor/guzzlehttp/guzzle/src/RedirectMiddleware.php:71)
at GuzzleHttp\RedirectMiddleware->__invoke()
(/app/www/vendor/guzzlehttp/guzzle/src/Middleware.php:63)
at GuzzleHttp\Middleware::GuzzleHttp{closure}()
(/app/www/vendor/guzzlehttp/guzzle/src/HandlerStack.php:75)
at GuzzleHttp\HandlerStack->__invoke()
(/app/www/vendor/guzzlehttp/guzzle/src/Client.php:333)
at GuzzleHttp\Client->transfer()
(/app/www/vendor/guzzlehttp/guzzle/src/Client.php:169)
at GuzzleHttp\Client->requestAsync()
(/app/www/vendor/guzzlehttp/guzzle/src/Client.php:189)
at GuzzleHttp\Client->request()
(/app/www/vendor/laravel/framework/src/Illuminate/Http/Client/PendingRequest.php:1049)
at Illuminate\Http\Client\PendingRequest->sendRequest()
(/app/www/vendor/laravel/framework/src/Illuminate/Http/Client/PendingRequest.php:894)
at Illuminate\Http\Client\PendingRequest->Illuminate\Http\Client{closure}()
(/app/www/vendor/laravel/framework/src/Illuminate/Support/helpers.php:248)
at retry()
(/app/www/vendor/laravel/framework/src/Illuminate/Http/Client/PendingRequest.php:892)
at Illuminate\Http\Client\PendingRequest->send()
(/app/www/vendor/laravel/framework/src/Illuminate/Http/Client/PendingRequest.php:770)
at Illuminate\Http\Client\PendingRequest->get()
(/app/www/app/Actions/GetOoklaSpeedtestServers.php:25)
at App\Actions\GetOoklaSpeedtestServers->handle()
(/app/www/vendor/lorisleiva/laravel-actions/src/Concerns/AsObject.php:24)
at App\Actions\GetOoklaSpeedtestServers::run()
(/app/www/app/Filament/Pages/Settings/GeneralPage.php:110)
at App\Filament\Pages\Settings\GeneralPage->form()
(/app/www/vendor/filament/spatie-laravel-settings-plugin/src/Pages/SettingsPage.php:184)
at Filament\Pages\SettingsPage->getForms()
(/app/www/vendor/filament/forms/src/Concerns/InteractsWithForms.php:286)
at Filament\Pages\BasePage->cacheForms()
(/app/www/vendor/filament/forms/src/Concerns/InteractsWithForms.php:357)
at Filament\Pages\BasePage->getCachedForms()
(/app/www/vendor/filament/forms/src/Concerns/InteractsWithForms.php:348)
at Filament\Pages\BasePage->getForm()
(/app/www/vendor/filament/support/src/Concerns/ResolvesDynamicLivewireProperties.php:27)
at Filament\Pages\BasePage->__get()
(/app/www/vendor/filament/spatie-laravel-settings-plugin/src/Pages/SettingsPage.php:49)
at Filament\Pages\SettingsPage->fillForm()
(/app/www/vendor/filament/spatie-laravel-settings-plugin/src/Pages/SettingsPage.php:38)
at Filament\Pages\SettingsPage->mount()
(/app/www/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php:36)
at Illuminate\Container\BoundMethod::Illuminate\Container{closure}()
(/app/www/vendor/laravel/framework/src/Illuminate/Container/Util.php:41)
at Illuminate\Container\Util::unwrapIfClosure()
(/app/www/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php:93)
at Illuminate\Container\BoundMethod::callBoundMethod()
(/app/www/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php:35)
at Illuminate\Container\BoundMethod::call()
(/app/www/vendor/livewire/livewire/src/Wrapped.php:23)
at Livewire\Wrapped->__call()
(/app/www/vendor/livewire/livewire/src/Features/SupportLifecycleHooks/SupportLifecycleHooks.php:125)
at Livewire\Features\SupportLifecycleHooks\SupportLifecycleHooks->callHook()
(/app/www/vendor/livewire/livewire/src/Features/SupportLifecycleHooks/SupportLifecycleHooks.php:20)
at Livewire\Features\SupportLifecycleHooks\SupportLifecycleHooks->mount()
(/app/www/vendor/livewire/livewire/src/ComponentHook.php:19)
at Livewire\ComponentHook->callMount()
(/app/www/vendor/livewire/livewire/src/ComponentHookRegistry.php:45)
at Livewire\ComponentHookRegistry::Livewire{closure}()
(/app/www/vendor/livewire/livewire/src/EventBus.php:60)
at Livewire\EventBus->trigger()
(/app/www/vendor/livewire/livewire/src/helpers.php:100)
at Livewire\trigger()
(/app/www/vendor/livewire/livewire/src/Mechanisms/HandleComponents/HandleComponents.php:49)
at Livewire\Mechanisms\HandleComponents\HandleComponents->mount()
(/app/www/vendor/livewire/livewire/src/LivewireManager.php:72)
at Livewire\LivewireManager->mount()
(/app/www/vendor/livewire/livewire/src/Features/SupportPageComponents/HandlesPageComponents.php:17)
at Livewire\Component->Livewire\Features\SupportPageComponents{closure}()
(/app/www/vendor/livewire/livewire/src/Features/SupportPageComponents/SupportPageComponents.php:118)
at Livewire\Features\SupportPageComponents\SupportPageComponents::interceptTheRenderOfTheComponentAndRetreiveTheLayoutConfiguration()
(/app/www/vendor/livewire/livewire/src/Features/SupportPageComponents/HandlesPageComponents.php:14)
at Livewire\Component->__invoke()
(/app/www/vendor/laravel/framework/src/Illuminate/Routing/ControllerDispatcher.php:46)
at Illuminate\Routing\ControllerDispatcher->dispatch()
(/app/www/vendor/laravel/framework/src/Illuminate/Routing/Route.php:259)
at Illuminate\Routing\Route->runController()
(/app/www/vendor/laravel/framework/src/Illuminate/Routing/Route.php:205)
at Illuminate\Routing\Route->run()
(/app/www/vendor/laravel/framework/src/Illuminate/Routing/Router.php:806)
at Illuminate\Routing\Router->Illuminate\Routing{closure}()
(/app/www/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:144)
at Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}()
(/app/www/vendor/filament/filament/src/Http/Middleware/DispatchServingFilamentEvent.php:15)
at Filament\Http\Middleware\DispatchServingFilamentEvent->handle()
(/app/www/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:183)
at Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}()
(/app/www/vendor/filament/filament/src/Http/Middleware/DisableBladeIconComponents.php:14)
at Filament\Http\Middleware\DisableBladeIconComponents->handle()
(/app/www/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:183)
at Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}()
(/app/www/vendor/laravel/framework/src/Illuminate/Routing/Middleware/SubstituteBindings.php:50)
at Illuminate\Routing\Middleware\SubstituteBindings->handle()
(/app/www/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:183)
at Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}()
(/app/www/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/VerifyCsrfToken.php:78)
at Illuminate\Foundation\Http\Middleware\VerifyCsrfToken->handle()
(/app/www/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:183)
at Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}()
(/app/www/vendor/laravel/framework/src/Illuminate/Session/Middleware/AuthenticateSession.php:60)
at Illuminate\Session\Middleware\AuthenticateSession->handle()
(/app/www/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:183)
at Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}()
(/app/www/vendor/laravel/framework/src/Illuminate/Auth/Middleware/Authenticate.php:57)
at Illuminate\Auth\Middleware\Authenticate->handle()
(/app/www/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:183)
at Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}()
(/app/www/vendor/laravel/framework/src/Illuminate/View/Middleware/ShareErrorsFromSession.php:49)
at Illuminate\View\Middleware\ShareErrorsFromSession->handle()
(/app/www/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:183)
at Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}()
(/app/www/vendor/laravel/framework/src/Illuminate/Session/Middleware/StartSession.php:121)
at Illuminate\Session\Middleware\StartSession->handleStatefulRequest()
(/app/www/vendor/laravel/framework/src/Illuminate/Session/Middleware/StartSession.php:64)
at Illuminate\Session\Middleware\StartSession->handle()
(/app/www/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:183)
at Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}()
(/app/www/vendor/laravel/framework/src/Illuminate/Cookie/Middleware/AddQueuedCookiesToResponse.php:37)
at Illuminate\Cookie\Middleware\AddQueuedCookiesToResponse->handle()
(/app/www/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:183)
at Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}()
(/app/www/vendor/laravel/framework/src/Illuminate/Cookie/Middleware/EncryptCookies.php:67)
at Illuminate\Cookie\Middleware\EncryptCookies->handle()
(/app/www/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:183)
at Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}()
(/app/www/vendor/filament/filament/src/Http/Middleware/SetUpPanel.php:19)
at Filament\Http\Middleware\SetUpPanel->handle()
(/app/www/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:183)
at Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}()
(/app/www/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:119)
at Illuminate\Pipeline\Pipeline->then()
(/app/www/vendor/laravel/framework/src/Illuminate/Routing/Router.php:805)
at Illuminate\Routing\Router->runRouteWithinStack()
(/app/www/vendor/laravel/framework/src/Illuminate/Routing/Router.php:784)
at Illuminate\Routing\Router->runRoute()
(/app/www/vendor/laravel/framework/src/Illuminate/Routing/Router.php:748)
at Illuminate\Routing\Router->dispatchToRoute()
(/app/www/vendor/laravel/framework/src/Illuminate/Routing/Router.php:737)
at Illuminate\Routing\Router->dispatch()
(/app/www/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php:200)
at Illuminate\Foundation\Http\Kernel->Illuminate\Foundation\Http{closure}()
(/app/www/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:144)
at Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}()
(/app/www/vendor/livewire/livewire/src/Features/SupportDisablingBackButtonCache/DisableBackButtonCacheMiddleware.php:19)
at Livewire\Features\SupportDisablingBackButtonCache\DisableBackButtonCacheMiddleware->handle()
(/app/www/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:183)
at Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}()
(/app/www/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/TransformsRequest.php:21)
at Illuminate\Foundation\Http\Middleware\TransformsRequest->handle()
(/app/www/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/ConvertEmptyStringsToNull.php:31)
at Illuminate\Foundation\Http\Middleware\ConvertEmptyStringsToNull->handle()
(/app/www/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:183)
at Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}()
(/app/www/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/TransformsRequest.php:21)
at Illuminate\Foundation\Http\Middleware\TransformsRequest->handle()
(/app/www/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/TrimStrings.php:40)
at Illuminate\Foundation\Http\Middleware\TrimStrings->handle()
(/app/www/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:183)
at Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}()
(/app/www/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/ValidatePostSize.php:27)
at Illuminate\Foundation\Http\Middleware\ValidatePostSize->handle()
(/app/www/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:183)
at Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}()
(/app/www/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/PreventRequestsDuringMaintenance.php:99)
at Illuminate\Foundation\Http\Middleware\PreventRequestsDuringMaintenance->handle()
(/app/www/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:183)
at Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}()
(/app/www/vendor/laravel/framework/src/Illuminate/Http/Middleware/HandleCors.php:49)
at Illuminate\Http\Middleware\HandleCors->handle()
(/app/www/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:183)
at Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}()
(/app/www/vendor/laravel/framework/src/Illuminate/Http/Middleware/TrustProxies.php:39)
at Illuminate\Http\Middleware\TrustProxies->handle()
(/app/www/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:183)
at Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}()
(/app/www/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:119)
at Illuminate\Pipeline\Pipeline->then()
(/app/www/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php:175)
at Illuminate\Foundation\Http\Kernel->sendRequestThroughRouter()
(/app/www/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php:144)
at Illuminate\Foundation\Http\Kernel->handle()
(/app/www/public/index.php:51) `
[2/2] ConnectionException
`Illuminate\Http\Client\ConnectionException:
cURL error 35: OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to www.speedtest.net:443  (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://www.speedtest.net/api/js/servers?engine=js&https_functional=1&limit=20
at /app/www/vendor/laravel/framework/src/Illuminate/Http/Client/PendingRequest.php:926
at Illuminate\Http\Client\PendingRequest->Illuminate\Http\Client{closure}()
(/app/www/vendor/laravel/framework/src/Illuminate/Support/helpers.php:248)
at retry()
(/app/www/vendor/laravel/framework/src/Illuminate/Http/Client/PendingRequest.php:892)
at Illuminate\Http\Client\PendingRequest->send()
(/app/www/vendor/laravel/framework/src/Illuminate/Http/Client/PendingRequest.php:770)
at Illuminate\Http\Client\PendingRequest->get()
(/app/www/app/Actions/GetOoklaSpeedtestServers.php:25)
at App\Actions\GetOoklaSpeedtestServers->handle()
(/app/www/vendor/lorisleiva/laravel-actions/src/Concerns/AsObject.php:24)
at App\Actions\GetOoklaSpeedtestServers::run()
(/app/www/app/Filament/Pages/Settings/GeneralPage.php:110)
at App\Filament\Pages\Settings\GeneralPage->form()
(/app/www/vendor/filament/spatie-laravel-settings-plugin/src/Pages/SettingsPage.php:184)
at Filament\Pages\SettingsPage->getForms()
(/app/www/vendor/filament/forms/src/Concerns/InteractsWithForms.php:286)
at Filament\Pages\BasePage->cacheForms()
(/app/www/vendor/filament/forms/src/Concerns/InteractsWithForms.php:357)
at Filament\Pages\BasePage->getCachedForms()
(/app/www/vendor/filament/forms/src/Concerns/InteractsWithForms.php:348)
at Filament\Pages\BasePage->getForm()
(/app/www/vendor/filament/support/src/Concerns/ResolvesDynamicLivewireProperties.php:27)
at Filament\Pages\BasePage->__get()
(/app/www/vendor/filament/spatie-laravel-settings-plugin/src/Pages/SettingsPage.php:49)
at Filament\Pages\SettingsPage->fillForm()
(/app/www/vendor/filament/spatie-laravel-settings-plugin/src/Pages/SettingsPage.php:38)
at Filament\Pages\SettingsPage->mount()
(/app/www/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php:36)
at Illuminate\Container\BoundMethod::Illuminate\Container{closure}()
(/app/www/vendor/laravel/framework/src/Illuminate/Container/Util.php:41)
at Illuminate\Container\Util::unwrapIfClosure()
(/app/www/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php:93)
at Illuminate\Container\BoundMethod::callBoundMethod()
(/app/www/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php:35)
at Illuminate\Container\BoundMethod::call()
(/app/www/vendor/livewire/livewire/src/Wrapped.php:23)
at Livewire\Wrapped->__call()
(/app/www/vendor/livewire/livewire/src/Features/SupportLifecycleHooks/SupportLifecycleHooks.php:125)
at Livewire\Features\SupportLifecycleHooks\SupportLifecycleHooks->callHook()
(/app/www/vendor/livewire/livewire/src/Features/SupportLifecycleHooks/SupportLifecycleHooks.php:20)
at Livewire\Features\SupportLifecycleHooks\SupportLifecycleHooks->mount()
(/app/www/vendor/livewire/livewire/src/ComponentHook.php:19)
at Livewire\ComponentHook->callMount()
(/app/www/vendor/livewire/livewire/src/ComponentHookRegistry.php:45)
at Livewire\ComponentHookRegistry::Livewire{closure}()
(/app/www/vendor/livewire/livewire/src/EventBus.php:60)
at Livewire\EventBus->trigger()
(/app/www/vendor/livewire/livewire/src/helpers.php:100)
at Livewire\trigger()
(/app/www/vendor/livewire/livewire/src/Mechanisms/HandleComponents/HandleComponents.php:49)
at Livewire\Mechanisms\HandleComponents\HandleComponents->mount()
(/app/www/vendor/livewire/livewire/src/LivewireManager.php:72)
at Livewire\LivewireManager->mount()
(/app/www/vendor/livewire/livewire/src/Features/SupportPageComponents/HandlesPageComponents.php:17)
at Livewire\Component->Livewire\Features\SupportPageComponents{closure}()
(/app/www/vendor/livewire/livewire/src/Features/SupportPageComponents/SupportPageComponents.php:118)
at Livewire\Features\SupportPageComponents\SupportPageComponents::interceptTheRenderOfTheComponentAndRetreiveTheLayoutConfiguration()
(/app/www/vendor/livewire/livewire/src/Features/SupportPageComponents/HandlesPageComponents.php:14)
at Livewire\Component->__invoke()
(/app/www/vendor/laravel/framework/src/Illuminate/Routing/ControllerDispatcher.php:46)
at Illuminate\Routing\ControllerDispatcher->dispatch()
(/app/www/vendor/laravel/framework/src/Illuminate/Routing/Route.php:259)
at Illuminate\Routing\Route->runController()
(/app/www/vendor/laravel/framework/src/Illuminate/Routing/Route.php:205)
at Illuminate\Routing\Route->run()
(/app/www/vendor/laravel/framework/src/Illuminate/Routing/Router.php:806)
at Illuminate\Routing\Router->Illuminate\Routing{closure}()
(/app/www/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:144)
at Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}()
(/app/www/vendor/filament/filament/src/Http/Middleware/DispatchServingFilamentEvent.php:15)
at Filament\Http\Middleware\DispatchServingFilamentEvent->handle()
(/app/www/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:183)
at Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}()
(/app/www/vendor/filament/filament/src/Http/Middleware/DisableBladeIconComponents.php:14)
at Filament\Http\Middleware\DisableBladeIconComponents->handle()
(/app/www/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:183)
at Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}()
(/app/www/vendor/laravel/framework/src/Illuminate/Routing/Middleware/SubstituteBindings.php:50)
at Illuminate\Routing\Middleware\SubstituteBindings->handle()
(/app/www/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:183)
at Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}()
(/app/www/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/VerifyCsrfToken.php:78)
at Illuminate\Foundation\Http\Middleware\VerifyCsrfToken->handle()
(/app/www/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:183)
at Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}()
(/app/www/vendor/laravel/framework/src/Illuminate/Session/Middleware/AuthenticateSession.php:60)
at Illuminate\Session\Middleware\AuthenticateSession->handle()
(/app/www/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:183)
at Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}()
(/app/www/vendor/laravel/framework/src/Illuminate/Auth/Middleware/Authenticate.php:57)
at Illuminate\Auth\Middleware\Authenticate->handle()
(/app/www/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:183)
at Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}()
(/app/www/vendor/laravel/framework/src/Illuminate/View/Middleware/ShareErrorsFromSession.php:49)
at Illuminate\View\Middleware\ShareErrorsFromSession->handle()
(/app/www/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:183)
at Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}()
(/app/www/vendor/laravel/framework/src/Illuminate/Session/Middleware/StartSession.php:121)
at Illuminate\Session\Middleware\StartSession->handleStatefulRequest()
(/app/www/vendor/laravel/framework/src/Illuminate/Session/Middleware/StartSession.php:64)
at Illuminate\Session\Middleware\StartSession->handle()
(/app/www/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:183)
at Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}()
(/app/www/vendor/laravel/framework/src/Illuminate/Cookie/Middleware/AddQueuedCookiesToResponse.php:37)
at Illuminate\Cookie\Middleware\AddQueuedCookiesToResponse->handle()
(/app/www/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:183)
at Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}()
(/app/www/vendor/laravel/framework/src/Illuminate/Cookie/Middleware/EncryptCookies.php:67)
at Illuminate\Cookie\Middleware\EncryptCookies->handle()
(/app/www/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:183)
at Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}()
(/app/www/vendor/filament/filament/src/Http/Middleware/SetUpPanel.php:19)
at Filament\Http\Middleware\SetUpPanel->handle()
(/app/www/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:183)
at Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}()
(/app/www/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:119)
at Illuminate\Pipeline\Pipeline->then()
(/app/www/vendor/laravel/framework/src/Illuminate/Routing/Router.php:805)
at Illuminate\Routing\Router->runRouteWithinStack()
(/app/www/vendor/laravel/framework/src/Illuminate/Routing/Router.php:784)
at Illuminate\Routing\Router->runRoute()
(/app/www/vendor/laravel/framework/src/Illuminate/Routing/Router.php:748)
at Illuminate\Routing\Router->dispatchToRoute()
(/app/www/vendor/laravel/framework/src/Illuminate/Routing/Router.php:737)
at Illuminate\Routing\Router->dispatch()
(/app/www/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php:200)
at Illuminate\Foundation\Http\Kernel->Illuminate\Foundation\Http{closure}()
(/app/www/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:144)
at Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}()
(/app/www/vendor/livewire/livewire/src/Features/SupportDisablingBackButtonCache/DisableBackButtonCacheMiddleware.php:19)
at Livewire\Features\SupportDisablingBackButtonCache\DisableBackButtonCacheMiddleware->handle()
(/app/www/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:183)
at Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}()
(/app/www/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/TransformsRequest.php:21)
at Illuminate\Foundation\Http\Middleware\TransformsRequest->handle()
(/app/www/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/ConvertEmptyStringsToNull.php:31)
at Illuminate\Foundation\Http\Middleware\ConvertEmptyStringsToNull->handle()
(/app/www/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:183)
at Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}()
(/app/www/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/TransformsRequest.php:21)
at Illuminate\Foundation\Http\Middleware\TransformsRequest->handle()
(/app/www/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/TrimStrings.php:40)
at Illuminate\Foundation\Http\Middleware\TrimStrings->handle()
(/app/www/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:183)
at Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}()
(/app/www/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/ValidatePostSize.php:27)
at Illuminate\Foundation\Http\Middleware\ValidatePostSize->handle()
(/app/www/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:183)
at Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}()
(/app/www/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/PreventRequestsDuringMaintenance.php:99)
at Illuminate\Foundation\Http\Middleware\PreventRequestsDuringMaintenance->handle()
(/app/www/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:183)
at Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}()
(/app/www/vendor/laravel/framework/src/Illuminate/Http/Middleware/HandleCors.php:49)
at Illuminate\Http\Middleware\HandleCors->handle()
(/app/www/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:183)
at Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}()
(/app/www/vendor/laravel/framework/src/Illuminate/Http/Middleware/TrustProxies.php:39)
at Illuminate\Http\Middleware\TrustProxies->handle()
(/app/www/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:183)
at Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}()
(/app/www/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:119)
at Illuminate\Pipeline\Pipeline->then()
(/app/www/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php:175)
at Illuminate\Foundation\Http\Kernel->sendRequestThroughRouter()
(/app/www/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php:144)
at Illuminate\Foundation\Http\Kernel->handle()
(/app/www/public/index.php:51)                `

It's confirmed that the issue is with my network. I've enabled a network proxy, and the proxy has restricted access to Speedtest.


[opt](invert index) use lowercase by default

Proposed changes
https://github.com/apache/doris/pull/32405

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


An additional application for keys with easy activation via ASF

Has read https://github.com/JustArchi/ArchiSteamFarm/blob/master/.github/CONTRIBUTING.md
Feature request
Purpose
An additional application for keys with easy activation via ASF
Application will be independent of ASF (because activity of people with this app will be more than with asf)
but close integrated with it and will accumulating the data from ASF
Solution
additional key storage application in which the game will be added, whether there are cards, whether the key is activated or not, and which button to activate if there is an ASF enabled
In the same application, you can mark whether cards have been received and keys are activated via ASF
Why currently available solutions are not sufficient?
In principle, there are no current decisions. There is no application that successfully held all the above functions and was integrated with ASF
Does your suggestion fall into ASF scope?
Yes. ASF Have a nice function to activate keys, but not has a management system of this keys
Is your suggestion abiding to Steam guidelines?
Yes. My suggestion does not break the rules
Additional info
I bad speak english
I am QA / UX / Analyst, can make logic and prototype

this suggestion does not fall in ASFs scope. asfs scope is primarily to IDLE games. however you can still code such a tool yourself, publiah it on your github and maintain your close integration with ASF via /Api

An additional application for keys with easy activation via ASF

Does your suggestion fall into ASF scope? Yes

I'm not sure if you have your own definition of what the program's scope is, but your "suggestion" is as far from it as possible to ask. No, creating additional application is not within ASF's application scope.


Is it possible to add aabox data to calculate multiple polygons?

I was looking at the source code and found that there is aabb data for calculating a single and detected element. Can I provide aabb data for calculating certain polygons?
Used to calculate the bounding box of multiple polygons
	/**
	 * get elements bounding box
	 * @param ids element uuid
	 */
	getBoundingBox(ids: string[]) {
		const polygons: Polygon[] = ids.map(id => this.elements.get(id));
		polygons.map(polygon => {
			// do somethings
		});
	}

English is not my native language; please excuse typing errors.

Maybe the typescript definition should expose bvh related attributes to the outside world?

I will try to do that in some automatic way in the meantime see
https://github.com/Prozi/detect-collisions/blob/master/source/modules/BVH.js
also try
$ node

const circle = new (require("detect-collisions").Circle)(0, 0, 100);

console.log(circle._points)

this is an array of [x,y,x,y,x,y,x,y,...]
you propably want to find minx and miny maxx and maxy yourself
I have no idea why you need that :)

@StringKe

@Prozi
I just saw that the _bvh parameter corresponds to the bounding box. I want to avoid calculating it again in other places and save CPU calculations.

after version 3 this is done in body.updateAABB()

but actually you should do
system.updateBody(body);

which removes body from rbush, updates aabb, then inserts it back

but to answer you original question:
Can I provide aabb data for calculating certain polygons?

Used to calculate the bounding box of multiple polygons

@StringKe I think that is not possible, each polygon has its own separate aabb :(
closing the issue and feel free to reopen if you have more comments, or if I misunderstood somethin


tests: obj_tracing: Enhance object tracing test

Enhance object tracing test to improve code coverage of
all kernel object's SYS_TRACING_OBJ_INIT() API.
Signed-off-by: Spoorthi K<EMAIL_ADDRESS>

@nashif, @ramakrishnapallala @andrewboie @andyross : Would you please review and suggest changes if required to get it merged?


Clarify compatible and dependencies

Hello
On https://github.com/input-output-hk/cardano-graphql/releases/tag/5.1.0 it states:

Compatible with:
cardano-node: 1.29.0
cardano-ogmios: v4.0.0-beta.9
cardano-db-sync: 11.0.0 - Note: The database must be recreated using the new version.
hasura/graphql-engine: 1.3.3

However, the docker-compose.yml file does not use any version of cardano-node.  See https://github.com/input-output-hk/cardano-graphql/blob/5.1.0/docker-compose.yml.
It is using something called cardano-ogmios.
Should the docker-compose file also contain an instance of cardano-node? If not, what, in docker-compose, is replacing it?

cardano-ogmios runs on top of cardano-node and therefore contains cardano-node.

Thanks for the reply @CyberCyclone
Based on https://github.com/CardanoSolutions/ogmios/blob/v4.0.0-beta.9/docker-compose.yml it seems that cardano-node and cardano-ogmios are two separate containers.

Correct. cardano-node is still used regardless, but the communication to it from graphql is handled by ogmios.

Yeah, so to clarify my confusion (forgive me, I'm growing old...),
the docker-compose file in this repo does no include the cardano-node. But in the ogmios repo, there are two separate containers, and one is the cardano-node.
Does this mean, the docker-compose file in this repo is using a vastly different version and build of ogmious that has the cardano-node embedded in it?

I'm not sure what you mean. cardano-graphql and ogmios are different projects.
Basically cardano-node is used for all data extraction, but ogmios is an "API standard" to make it easier to communicate.
The docker-compose file in graphql references / imports ogmios, and then uses that to communicate with cardano-node.

Ah, cardanosolutions/cardano-node-ogmios contains both cardano-node and `ogmios, encapsulated in the one image.

Ah, cardanosolutions/cardano-node-ogmios contains both cardano-node and ogmios, encapsulated in the one image.

Yes, more info here: https://ogmios.dev/getting-started/docker/. The docker-compose.json in the Ogmios repo is there for the multi-container use-case, which suits internal development.


[SPARK-22371][CORE] Return None instead of throwing an exception when an accumulator is garbage collected.

What changes were proposed in this pull request?
There's a period of time when an accumulator has been garbage collected, but hasn't been removed from AccumulatorContext.originals by ContextCleaner. When an update is received for such accumulator it will throw an exception and kill the whole job. This can happen when a stage completes, but there're still running tasks from other attempts, speculation etc. Since AccumulatorContext.get() returns an option we can just return None in such case.
How was this patch tested?
Unit test.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Yes, this is correct.

cc @cloud-fan

this behavior change LGTM, but the test is over complicated and seems has limited value.

Test build #90577 has started for PR 21114 at commit 8b30733.

I may miss something. It's weak reference, so if we have a long-running job and the memory pressure is high, we can reproduce it?

Test build #90577 has finished for PR 21114 at commit 8b30733.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/90577/
Test FAILed.

can we do this?
var acc = ...
... // launch a long running job
val accId = acc.getId
acc = null
gc
... // job finished

accumulator is created by users so we have to be prepared for any situations. That's why we use weak reference at the first place.

There's "get accum" test which does this, it was updated for new behavior.

Test build #90623 has started for PR 21114 at commit 1b1b1fa.

Test build #90623 has finished for PR 21114 at commit 1b1b1fa.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/90623/
Test FAILed.

retest this please

Test build #90629 has finished for PR 21114 at commit 1b1b1fa.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/90629/
Test FAILed.

Merged build finished. Test FAILed.

retest this please

retest this please

Test build #90703 has started for PR 21114 at commit 1b1b1fa.

Test build #90703 has finished for PR 21114 at commit 1b1b1fa.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/90703/
Test PASSed.

Merged build finished. Test PASSed.

thanks, merging to master!

backported to 2.3


element-{web,desktop}: 1.11.46 -> 1.11.47

Description of changes
ChangeLog web: https://github.com/vector-im/element-web/releases/tag/v1.11.47
ChangeLog desktop: https://github.com/vector-im/element-desktop/releases/tag/v1.11.47

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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

[ ] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 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

[x] Fits CONTRIBUTING.md.

the x86 build timed out but it passed nixpkgs-review here. I am tempted to merge but will let @Ma27 do it.


Update docs for CDN cache node configuration for OpenWRT

Small devices will have problems when trying to store in limited tmp areas. NGINX on OpenWRT will not run without this setting. There's really no reason not to have this setting on cloud CDN nodes also, however it needs to be tested.
Also note that on openwrt the /var path used maps to /tmp. This won't be a good place to put cache files on a router device with limited memory. You'll want to use the external root method to map an overlay external USB drive if you can. Then you can use /overlay instead of /var prefix to cache your files.
You'll also need to reduce the shared memory zone sizes. Here's an example file that works for me on a TP-LINK OpenWRT device:
nginx.conf.txt
More updates to come because this thing is slow and needs to be tuned.

Another update to cut down on buffer usage.


Benchmarks wired to plutus-tx output

Currently, our benchmarks are checked into the repo - which is good for reproducibility, but may mean they are not benchmarking current/sensible things.
For that reason, we should (in line with Michael's suggestion) create a separate cabal library for benchmarks and have it depend on plutus-tx, plutus-use-cases, etc.

We've got some now.


Replace Ring and Rustls with mbedTLS

Requested feature
Our use of Ring and Rustls should be replaced with mbedTLS.

This is implemented by #472 and #476.

Closing this because of #472 and #476.


nginx work process using 100% cpu

the VOD doesn't work randomly
work process use 100% cpu in top
no error log
use perf top -p 8560 can see :
76.06%  nginx     [.] ngx_rtmp_mp4_parse
  23.70%  nginx     [.] ngx_rtmp_mp4_parse_trak

mp4 file 2.6GB and duration is 03:46:23

By randomly you mean one file and it sometimes work and sometimes not, or a
single file work all the time, but other doesn't?
Are those .mp4 files produced by nginx or you upload them yourself (or
users upload them)?
śr., 17.04.2019, 11:47 użytkownik Wang Jingkai<EMAIL_ADDRESS>napisał:

the VOD doesn't work randomly
work process use 100% cpu in top
no error log
use perf top -p 8560 can see :
76.06%  nginx     [.] ngx_rtmp_mp4_parse
23.70%  nginx     [.] ngx_rtmp_mp4_parse_trak
mp4 file 2.6GB and duration is 03:46:23
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/arut/nginx-rtmp-module/issues/1405, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AAbp9n37nZak-B-5aaDOrs5ew4N9PE4Wks5vhu3DgaJpZM4c0pME
.

By randomly you mean one file and it sometimes work and sometimes not, or a single file work all the time, but other doesn't? Are those .mp4 files produced by nginx or you upload them yourself (or users upload them)? śr., 17.04.2019, 11:47 użytkownik Wang Jingkai<EMAIL_ADDRESS>napisał:
…
the VOD doesn't work randomly work process use 100% cpu in top no error log use perf top -p 8560 can see : 76.06% nginx [.] ngx_rtmp_mp4_parse 23.70% nginx [.] ngx_rtmp_mp4_parse_trak mp4 file 2.6GB and duration is 03:46:23 — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#1405>, or mute the thread https://github.com/notifications/unsubscribe-auth/AAbp9n37nZak-B-5aaDOrs5ew4N9PE4Wks5vhu3DgaJpZM4c0pME .

random means I don't know how to hit this 'bug',
but I compiled a nginx with debug log, now it has worked more than 24hours without error.
The mp4(h.264 + aac ) file is upload by myself.

Okay, so it's working good with the same file and sometimes exactly same
file hangs nginx worker. So my guesses were wrong.
Is it possible there was disk failure (like your server provider had some
maintenance on storage, or just disk failed)?
pt., 19.04.2019, 09:24 użytkownik Wang Jingkai<EMAIL_ADDRESS>napisał:

By randomly you mean one file and it sometimes work and sometimes not, or
a single file work all the time, but other doesn't? Are those .mp4 files
produced by nginx or you upload them yourself (or users upload them)? śr.,
17.04.2019, 11:47 użytkownik Wang Jingkai<EMAIL_ADDRESS>napisał:
… <#m_-7352691258426947309_>
the VOD doesn't work randomly work process use 100% cpu in top no error
log use perf top -p 8560 can see : 76.06% nginx [.] ngx_rtmp_mp4_parse
23.70% nginx [.] ngx_rtmp_mp4_parse_trak mp4 file 2.6GB and duration is
03:46:23 — You are receiving this because you are subscribed to this
thread. Reply to this email directly, view it on GitHub <#1405
https://github.com/arut/nginx-rtmp-module/issues/1405>, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AAbp9n37nZak-B-5aaDOrs5ew4N9PE4Wks5vhu3DgaJpZM4c0pME
.
random means I don't know how to hit this 'bug',
but I compiled a nginx with debug log, now it has worked more than 24hours
without error.
The mp4(h.264 + aac ) file is upload by myself.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/arut/nginx-rtmp-module/issues/1405#issuecomment-484790933,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADOT5VXMDKIJNAGJDBA6ELPRFXUPANCNFSM4HGSSMCA
.

Next time this happens try to dump process memory and maybe try to connect
with some debugger (eg. gdb) and see where it is looping.
sob., 20.04.2019, 10:38 użytkownik Michał<EMAIL_ADDRESS>napisał:

Okay, so it's working good with the same file and sometimes exactly same
file hangs nginx worker. So my guesses were wrong.
Is it possible there was disk failure (like your server provider had some
maintenance on storage, or just disk failed)?
pt., 19.04.2019, 09:24 użytkownik Wang Jingkai<EMAIL_ADDRESS>napisał:

By randomly you mean one file and it sometimes work and sometimes not, or
a single file work all the time, but other doesn't? Are those .mp4 files
produced by nginx or you upload them yourself (or users upload them)? śr.,
17.04.2019, 11:47 użytkownik Wang Jingkai<EMAIL_ADDRESS>napisał:
… <#m_-7352691258426947309_>
the VOD doesn't work randomly work process use 100% cpu in top no error
log use perf top -p 8560 can see : 76.06% nginx [.] ngx_rtmp_mp4_parse
23.70% nginx [.] ngx_rtmp_mp4_parse_trak mp4 file 2.6GB and duration is
03:46:23 — You are receiving this because you are subscribed to this
thread. Reply to this email directly, view it on GitHub <#1405
https://github.com/arut/nginx-rtmp-module/issues/1405>, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AAbp9n37nZak-B-5aaDOrs5ew4N9PE4Wks5vhu3DgaJpZM4c0pME
.
random means I don't know how to hit this 'bug',
but I compiled a nginx with debug log, now it has worked more than
24hours without error.
The mp4(h.264 + aac ) file is upload by myself.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/arut/nginx-rtmp-module/issues/1405#issuecomment-484790933,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADOT5VXMDKIJNAGJDBA6ELPRFXUPANCNFSM4HGSSMCA
.

Next time this happens try to dump process memory and maybe try to connect with some debugger (eg. gdb) and see where it is looping. sob., 20.04.2019, 10:38 użytkownik Michał<EMAIL_ADDRESS>napisał:
…
Okay, so it's working good with the same file and sometimes exactly same file hangs nginx worker. So my guesses were wrong. Is it possible there was disk failure (like your server provider had some maintenance on storage, or just disk failed)? pt., 19.04.2019, 09:24 użytkownik Wang Jingkai @.> napisał: > By randomly you mean one file and it sometimes work and sometimes not, or > a single file work all the time, but other doesn't? Are those .mp4 files > produced by nginx or you upload them yourself (or users upload them)? śr., > 17.04.2019, 11:47 użytkownik Wang Jingkai @. > napisał: > … <#m_-7352691258426947309_> > the VOD doesn't work randomly work process use 100% cpu in top no error > log use perf top -p 8560 can see : 76.06% nginx [.] ngx_rtmp_mp4_parse > 23.70% nginx [.] ngx_rtmp_mp4_parse_trak mp4 file 2.6GB and duration is > 03:46:23 — You are receiving this because you are subscribed to this > thread. Reply to this email directly, view it on GitHub <#1405 > <#1405>>, or mute the > thread > https://github.com/notifications/unsubscribe-auth/AAbp9n37nZak-B-5aaDOrs5ew4N9PE4Wks5vhu3DgaJpZM4c0pME > . > > random means I don't know how to hit this 'bug', > but I compiled a nginx with debug log, now it has worked more than > 24hours without error. > > The mp4(h.264 + aac ) file is upload by myself. > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <#1405 (comment)>, > or mute the thread > https://github.com/notifications/unsubscribe-auth/AADOT5VXMDKIJNAGJDBA6ELPRFXUPANCNFSM4HGSSMCA > . >

May be I have no ability to do these?
It happen today.
I check the debug log and found which file cause the problem.
The mp4 file has just a video stream and no audio stream.
The debug log:
2019/04/20 15:18:07 [debug] 21771#0: *74 read: 10, 00007FFDDD60C5D0, 8, 32
2019/04/20 15:18:07 [debug] 21771#0: *74 mp4: found moov box
2019/04/20 15:18:07 [debug] 21771#0: *74 mp4: box unhandled 'mvhd'
2019/04/20 15:18:07 [debug] 21771#0: *74 mp4: box 'trak'
2019/04/20 15:18:07 [debug] 21771#0: *74 mp4: trying track 0
2019/04/20 15:18:07 [debug] 21771#0: *74 mp4: too small box: size=-8
2019/04/20 15:18:07 [debug] 21771#0: *74 mp4: box 'trak'
2019/04/20 15:18:07 [debug] 21771#0: *74 mp4: box 'trak'
2019/04/20 15:18:07 [debug] 21771#0: *74 mp4: box 'trak'
2019/04/20 15:18:07 [debug] 21771#0: *74 mp4: box 'trak'
2019/04/20 15:18:07 [debug] 21771#0: *74 mp4: box 'trak'
2019/04/20 15:18:07 [debug] 21771#0: *74 mp4: box 'trak'
2019/04/20 15:18:07 [debug] 21771#0: *74 mp4: box 'trak'
2019/04/20 15:18:07 [debug] 21771#0: *74 mp4: box 'trak'
2019/04/20 15:18:07 [debug] 21771#0: *74 mp4: box 'trak'
2019/04/20 15:18:07 [debug] 21771#0: *74 mp4: box 'trak'
2019/04/20 15:18:07 [debug] 21771#0: *74 mp4: box 'trak'
2019/04/20 15:18:07 [debug] 21771#0: *74 mp4: box 'trak'
2019/04/20 15:18:07 [debug] 21771#0: *74 mp4: box 'trak'
2019/04/20 15:18:07 [debug] 21771#0: *74 mp4: box 'trak'
2019/04/20 15:18:07 [debug] 21771#0: *74 mp4: box 'trak'
2019/04/20 15:18:07 [debug] 21771#0: *74 mp4: box 'trak'
2019/04/20 15:18:07 [debug] 21771#0: *74 mp4: box 'trak'
2019/04/20 15:18:07 [debug] 21771#0: *74 mp4: box 'trak'
2019/04/20 15:18:07 [debug] 21771#0: *74 mp4: box 'trak'
2019/04/20 15:18:07 [debug] 21771#0: *74 mp4: box 'trak'
2019/04/20 15:18:07 [debug] 21771#0: *74 mp4: box 'trak'
2019/04/20 15:18:07 [debug] 21771#0: *74 mp4: box 'trak'

2019/04/20 15:18:07 [debug] 21771#0: *74 mp4: box 'trak' loop forever
I modify the function "ngx_rtmp_mp4_parse" in "ngx_rtmp_mp4_module.c"
change
uint32_t                   *hdr, tag;
    size_t                      size, nboxes;
    ngx_uint_t                  n;
    ngx_rtmp_mp4_box_t         *b;

    while (pos != last) {
        if (pos + 8 > last) {
            ngx_log_debug1(NGX_LOG_DEBUG_RTMP, s->connection->log, 0,
                           "mp4: too small box: size=%i", last - pos);
            return NGX_ERROR;
        }

        hdr = (uint32_t *) pos;
        size = ngx_rtmp_r32(hdr[0]);
        tag  = hdr[1];

to
uint32_t                   *hdr, tag;
    size_t                      size, nboxes;
    ngx_uint_t                  n;
    ngx_rtmp_mp4_box_t         *b;

    while (pos != last) {
        if (pos + 8 > last) {
            ngx_log_debug1(NGX_LOG_DEBUG_RTMP, s->connection->log, 0,
                           "mp4: too small box: size=%i", last - pos);
            return NGX_ERROR;
        }

        hdr = (uint32_t *) pos;
        size = ngx_rtmp_r32(hdr[0]);
        if(0 == size) return NGX_ERROR;
        tag  = hdr[1];

then it seems work.


4.x - Improve AppFactory & ServerRequestCreatorFactory Automatic Decoration

AppFactory's New Behavior
AppFactory will attempt to decorate ResponseFactory instances passed via AppFactory::create() or set via AppFactory::setResponseFactory() given that a StreamFactoryInterface has been set via AppFactory::setStreamFactory() given that Slim\Http is present.
Note that the AppFactory setters will override any of the PSR-17 factory provider automatically detected implementations.
<?php
use Slim\Factory\AppFactory;
use Your\Psr7\CustomResponseFactory;
use Your\Psr7\CustomStreamFactory;

// Set your custom StreamFactory first
$myStreamFactory = new CustomStreamFactory();
AppFactory::setStreamFactory($myStreamFactory);

// You can use a setter for your ResponseFactory
$myCustomResponseFactory = new CustomResponseFactory();
AppFactory::setResponseFactory($myCustomResponseFactory);
$app = AppFactory::create();

// Or you can use the AppFactory::create() constructor parameter
$app = AppFactory::create($myCustomResponseFactory);

ServerRequestCreatorFactory's New Behavior
Similarly to AppFactory you can set a default ServerRequestCreator which implements ServerRequestCreatorInterface that will override the automatically detected server request creators present in the PSR-17 factory provider.
<?php
use Slim\Factory\AppFactory;
use Slim\Factory\ServerRequestCreatorFactory;
use Your\Psr7\CustomServerRequestCreator;

$myCustomServerRequestCreator = new CustomServerRequestCreator();
ServerRequestCreatorFactory::setServerRequestCreator($myCustomServerRequestCreator);

$app = AppFactory::create();
$app->run();

This PR effectively closes #2709, #2710, #2712  and #2713

Coverage remained the same at 100.0% when pulling 22f7157470e67e9267c5ad2ac7862507ef1f8cb3 on l0gicgate:4.x-ImproveAutomaticDecoration into 8dfa32d8fd49c2349d03e61a7619d15debb2b7a2 on slimphp:4.x.

Cool.


Detailed Specification for AOT Inference-only ATen Tracer Function

Added in https://github.com/pytorch/pytorch/issues/108079#issuecomment-1710887979


Non-intuitive plotting range when combining EC and MS data

When combining .tsv  and .mpt files in any ECMSMeasurement object it will plot from when EC data starts (when the potential column starts), contrary to what is ususally the case when reading in pure .tsv data (all data from time=0 until whenever .tsv file time stamp runs out. Would be nice if the format of plotting range, vs time of the ECMS object had the same time range as the pure MS object. This would also make sense as backgrounds are are somewhat easier defined prior any EC data collection, i.e. not having to define a new time range fro the plot (could of course be done using  tspan=[0,np.max(full_ECMS_data.grab("time/s"))] or similar in the ECMS plotting command).

This depends on the workflow.
When doing EC-MS I and, I think, my colleagues here at ICL, start recording MS data while setting up and leaving MS data acquisition running until we go home. During the day we then run one or more EC measurements, which we think of as the actual experiments. When analizying data, we'll often have something like the following:
ms = Measurement.read(...)  # all the MS data
ec_1 = Measurement.read(...)   # experiment 1, with sample A
ec_2 = Measurement.read(...)   # experiment 2, with sample B
ecms_1 = ec_1 + ms
ecms_2 = ec_2 + ms
ecms_1.plot()   # plot 1
ecms_2.plot()   # plot 2

If we used the tspan of the full data, then plot 1 and plot 2 have the same range and identical top panels. Yes, they show different ec data, but the part of the experiment I actually want to look at might be too small to resolve.
I've now updated the plotting function to accept the following strings as tspan specification:
"ec": use the timespan of the EC data (this will remain the default)
"ms": use the timespan of the MS data
"all": use a timespan containing all of the data.
So if you want the whole MS data plotted, you'll be able to just call ecms_1.plot(tspan="all"). Hope this is satisfactory?
The change is here: https://github.com/ixdat/ixdat/commit/8ced531ae42ecd844c28260b2fd5681ff3184b2d
I'll open the PR with it now, and hopefully soon distribute in ixdat 0.2.4


Use context in mixins/Animated

Now that parent-tree contexts are landing in 0.13, we should test them out for the animations.
There's a patch:
https://github.com/facebook/react/issues/2112#issuecomment-75418472
And would require modifications to the ./mixins/Animated.js file to remove the use of AnimateStore and switch to contexts.

This has landed


[CHALLENGE SUBMISSION] OmegaMadLab - Challenge 4

What is your name? (First, Last)
Marco Obinu
Where is your GitHub Repo ?(With your challenge solution)
https://github.com/OmegaMadLab/TerraformOnAzure-Challenge4
the browsable web app is available at http://db105718c5064356b1f8.westeurope.aksapp.io/
What Challenge is this for? (Challenge number between 1 and 5)
Challenge 4
(Optional) Anything else we should know? e.g., language used, location, blog post?
I'm quite a newbie here; I really appreciate the challenge: it allows me to go more in-depth on topics I should work more with

Thanks for participating in the #TerraformOnAzure coding challenges!
We have attached your very special Astronaut Badger background, for you to use in all your upcoming video calls!
And to recognize you for your learning, you can collect your digital Azure Heroes badge on your mobile (you may need to install the Enjin wallet to collect it). Make sure to collect it today!
https://beam.enjin.io/claim/d32599695c8c28cfc24820492080fac0
Keep on learning and sharing!
Greetings from the #TerraformOnAzure team,
Suzanne, Floor, Erik & Nick


Performance-Info in Systemtray/Taskleiste

Description of the new feature / enhancement
Please let me show my system Performances e.g. CPU Usage %, GPU Temp., RAM Usage % etc. in my Systemtray.
Thanks :)
Scenario when this would be used?
Always and everywhere!
Supporting information
Thank you very much! Powertoys is great!

/dup #8756


Run tests for SKA-Low for SKA DC3

Using ObservationLong, design the simulation for SKADC3.

@kenfus Hello

@rohitcbscient Is this still an open issue?

stale


Adding code anywhere around class

Is there a way to use this syntax: defined( 'MYVAR') or die('bla bla');
One of these ways is acceptable :) :

Injecting a string with the code at given point in the file.
Creating a construct for conditions

Thanks.

I solved the problem by using custom file templates:
$prettyPrinter->addTemplatePath(DIR.'/my_templates');

That's good to know, thanks for coming back with your solution :)


Allow 773/774 fields to have institution identifier prefix before MMS ID

Current indexing
https://github.com/pulibrary/bibdata/blob/main/marc_to_solr/lib/princeton_marc.rb#L820 only accepts 773 and 774 fields that have $w that starts with 99 and ends with 6421.
Desired Indexing
To allow our records to follow the MARC format (see https://www.loc.gov/marc/bibliographic/bd760787.html for $w), we need to add in Alma the prefix (NjP) to all 773 and 774 $w.
(important:)This will break the current indexing routine unless we support
valid_linked_fields to accept a $w that may or may not start with (NjP) as long as there is a valid MMS ID that ends the subfield.
Examples:
773  __ $w (NjP)9923506421
773 __ $w<PHONE_NUMBER>
This will allow both ways to work while we remediate the bib records.
Acceptance criteria

[ ] 773 and 774 linkages work (important:) with or without the presence of the (NjP) prefix -

Implementation Notes
From @christinach on slack:
The index will accept 773 and 774 with a $w that may or may not start with (NjP) as long as there is a valid MMS ID that ends the subfield. When NJP is there and the mms_id is valid we will index Njp and the mmsid When Njp is not there and the mms_id is valid we will index the mmsid only.

Closed by #2422


Please help me to install youtube-dl to my server

I'm new to python if anyone know to youtube-dl write php ? please help me

https://github.com/rg3/youtube-dl/blob/master/CONTRIBUTING.md
Also, this is an issue tracker. Not some kind of support forum.

Thanks @Hrxn. This should help, too: https://github.com/rg3/youtube-dl/blob/master/README.md#installation


Inference results v4.1 repo download support in CM

Merged https://github.com/GATEOverflow/cm4mlops/pull/107.


Unable to perform call on iOS

Hi,
I'm unable to perform a call on iOS. I always get an exception sayin the NSString couldnt be parsed.
I also tried removed whitespaces and signs like "+" from the number but nothing worked.
Any ideas?

Smmm, strange.  Here's the snippet from the sample project PCL to make a phone call.
public static void MakeSamplePhoneCall(this IPhoneCallTask phoneCall)
{
    if (phoneCall.CanMakePhoneCall)
    {
        phoneCall.MakePhoneCall("+272193343499", "Xamarin Demo User");
    }
}

Pending further feedback this issue is now closed


Schema Validation is not working as expected using match and contains keywords

IMPORTANT: If you have a general question please use Stack Overflow instead where Karate has a dedicated "tag": https://stackoverflow.com/questions/tagged/karate
If you are sure you have found a bug, please make sure you follow the instructions here: https://github.com/intuit/karate/wiki/How-to-Submit-an-Issue

Here is my Schema file : {
"consentGroups": [
{
"type": '#string',
"consents": [
{
"id": '#string',
"consentProfileId": '#string',
"consentTypeId": '#string',
"consentTypeVersion": '#string',
"name": '#string',
"agreeText": '#string',
"url": '#string',
"value": '#boolean',
"mandatory": '#boolean'
}
]
}
]
}
Response
{
"consentGroups" : [ {
"type" : "consent",
"consents" : [ {
"id" : "TOS1",
"consentProfileId" : "bfd9cb4b-4159-432c-a0da-a0fd135de395",
"consentTypeId" : "TOS-group1",
"consentTypeVersion" : "1.1",
"name" : "Terms of service",
"agreeText" : "Terms and Conditions",
"url" : "htttps://valami.hu",
"value" : true,
"mandatory" : true
}, {
"id" : "GDPR1",
"consentProfileId" : "79912122-f90d-4ea2-9f11-f15ac7794ef8",
"consentTypeId" : "GDPR-group1",
"consentTypeVersion" : "1.0",
"name" : "Data collection statement    ",
"agreeText" : "I have read and agreed to the collection of personal data.",
"url" : "htttps://valami.hu",
"value" : true,
"mandatory" : true
}, {
"id" : "GDPR2",
"consentProfileId" : "79912122-f90d-4ea2-9f11-f15ac7794ef8",
"consentTypeId" : "GDPR-group1",
"consentTypeVersion" : "1.0",
"name" : "Personalized Content",
"agreeText" : "I agree to receive personalized content through the application.",
"value" : true,
"mandatory" : false
} ]
}, {
"type" : "notifications",
"consents" : [ {
"id" : "PNF1",
"consentProfileId" : "578274af-4135-41c1-9237-bad1ec0c9e77",
"consentTypeId" : "PNF-group1",
"consentTypeVersion" : "2.0",
"name" : "Bill notifications",
"description" : "Get notified when the bill is generated, ready to be payed, overdue, and fulfilled.",
"value" : true,
"mandatory" : false
}]
} ]
}
Both my schema and response is correct and include all keys, still I am getting silly error : reason: no key-values matched
There is some issue in match and assert keyword.

closing as you haven't followed the instructions:
https://github.com/intuit/karate/wiki/How-to-Submit-an-Issue


swing animation doesn't work any more

For some reason, the swing animation stop working.
view.animate(.swing(repeatCount: 1))

Just tried in the animation playground, seems working as expected, what's broken?

I am silly when I tested .swing with a circle. Can't see it that time. I close it now.


Cannot find show links

Keep getting this:
D:\>anime-dl -i "http://www.crunchyroll.com/parasyte-the-maxim-" -u xxxxx -p xxxxx Trying to login... Logged in successfully... Could not find the show links. Report on https://github.com/Xonshiz/anime-dl/issues/new
Error log as follows:
DEBUG: You have successfully set the Debugging On. DEBUG: Arguments Provided : Namespace(input=['http://www.crunchyroll.com/gate'], language='Japanese', password=['xxxxx'], range='All', resolution='720p', skip=False, username=['xxxxx'], verbose=True, version=False) DEBUG: Operating System : Windows - 8.1 - 6.3.9600 DEBUG: Python Version : 2.7.13 (32bit) DEBUG: Starting new HTTPS connection (1): www.crunchyroll.com DEBUG: https://www.crunchyroll.com:443 "GET /login HTTP/1.1" 503 None DEBUG: Resetting dropped connection: www.crunchyroll.com DEBUG: https://www.crunchyroll.com:443 "GET /cdn-cgi/l/chk_jschl?jschl_answer=5&jschl_vc=xxxxx&pass=xxxxx HTTP/1.1" 302 165 DEBUG: https://www.crunchyroll.com:443 "GET /login HTTP/1.1" 200 None DEBUG: https://www.crunchyroll.com:443 "POST /login HTTP/1.1" 302 None DEBUG: https://www.crunchyroll.com:443 "GET / HTTP/1.1" 200 None DEBUG: Starting new HTTP connection (1): www.crunchyroll.com DEBUG: http://www.crunchyroll.com:80 "GET /gate HTTP/1.1" 200 None DEBUG: Starting new HTTP connection (1): www.crunchyroll.com DEBUG: http://www.crunchyroll.com:80 "GET /gate HTTP/1.1" 200 None
Any ideas?  If I do the episodes individually by copying each episode's website and pasting it into anime-dl, then it grabs the file fine.

Disregard.  I forgot my premium doesn't exist anymore.


AfPO_0000285 resource URL contains non-ASCII character

I've encountered an error when trying to parse the latest hancestro.owl via the Python package, pronto. Please see
https://github.com/fastobo/fastobo-py/issues/343
Would HANCESTRO consider replacing the resource URL https://en.wikipedia.org/wiki/Efé_people with the URL-safe version, https://en.wikipedia.org/wiki/Efé_people?

@jggatter Thank you for raising this issue and sorry to hear our latest release is causing you parsing issues. As the property in question originates from AfPO rather than HANCESTRO, I've asked the AfPO team to look into implementing the fix.

Hi @jggatter, haven't you had a problem with two dbpedia classes: https://dbpedia.org/page/Réunion and https://dbpedia.org/page/São_Tomé_and_Príncipe?
After fixing the issue in AfPO, I tested parsing using fastobo and got an error on the Réunion class. Then, I found issues with São Tomé and Príncipe, which are defined in HANCESTRO.

Thanks @daniwelter!
Hi @anitacaron, it seems like those two classes you mention appear in the hancestro.owl file before Efé people. From my original attempt, pronto errored out on me for Efé people and was unable to continue. I suppose the parsing might not happen in a linear order of file start to file end (probably parses as a tree). In any case, it doesn't surprise me that these other resources that contain non-ASCII characters caused the same issue.
In the fastobo issue I linked, the maintainer replies saying that they will add UTF-8 support. Not sure when this would be. Even still, they advise that ontologies use the ASCII character set to better assure support across operating systems.
I've had our organization revert to using a previous HANCESTRO version for now, so we're not blocked. I look forward to eventually upgrading to include the AfPO contributions!
Thanks,
James


Simplified the code of the RedirectToPreferredLocale listener

Some minor changes after the merge of #199.
@voronkovich could you please review that this simplifications don't break your code? Thanks!

@javiereguiluz, please remove the not needed quotes from the service definitions (I forgot to do it). See https://github.com/symfony/symfony-demo/blob/master/app/config/services.yml#L34


GEOMESA-1514 Standardizing tools output/logging

Note: stacks on top of #1222
Signed-off-by: Emilio Lahr-Vivaz<EMAIL_ADDRESS>

rebased on master


promote pre-minio-removal in release-dev workflow too

Addresses an issue where the workflow running on main would fail during the "download embedded-cluster" step: https://github.com/replicatedhq/embedded-cluster/actions/runs/8194465936/job/22441201694

yep that would do it
would you consider adding error message reporting to the pull script?


do recursive merging for the config file.

so that if the custom yaml override some property but not all property of a nested object, the missing property would be fetch from the default.yaml config file

A merging system where,
A:
x:
- y: abc

and B:
x:
- y: pqr

when merged give:
x:
- y: abc
- y: pqr

Might be useful if we want to merge test_accounts

A merging system where,
A:
x:
- y: abc

and B:
x:
- y: pqr

when merged give:
x:
- y: abc
- y: pqr

Might be useful if we want to merge test_accounts

is this a question?
what you describe is what should happen.
but if you have :
x:
 y: a

merged with
x:
 y: b

then you would have
{x: y: {b}}

A merging system where,
A:
x:
- y: abc

and B:
x:
- y: pqr

when merged give:
x:
- y: abc
- y: pqr

Might be useful if we want to merge test_accounts

is this a question?

A suggestion

what you describe is what should happen.

Nope, that does not happen with this PR. I just tested it locally. We get this:
// merged
x:
  - y: pqr

But we don't want that for the test_accounts data structure at least, because each entry there would be a separate account.


Indexing from scratch always detects gaps and stops

Indexing from scratch always detects gaps, this seems to happen with all latest releases of ordinals-api. I've tried v2.1.1 , v2.2.0, v3.0.0, and getting the same result at block height near 810k+-:
{
  "level": "error",
  "time": "2024-03-01T13:19:21.676Z",
  "pid": 7,
  "hostname": "bb4e651ca4a9",
  "name": "chainhook-client",
  "err": {
    "type": "BadPayloadRequestError",
    "message": "Block inscription gap detected: Attempting to insert #35144998 (810988) but current max is #35144902. Chain tip is at 810985.",
    "stack": "BadPayloadRequestError: Block inscription gap detected: Attempting to insert #35144998 (810988) but current max is #35144902. Chain tip is at 810985.\n    at assertNoBlockInscriptionGap (/app/dist/src/pg/helpers.js:23:19)\n    at /app/dist/src/pg/pg-store.js:85:59\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n    at async scope (/app/node_modules/postgres/cjs/src/index.js:226:18)\n    at async Function.begin (/app/node_modules/postgres/cjs/src/index.js:213:14)\n    at async PgStore.updateInscriptions (/app/dist/src/pg/pg-store.js:52:9)\n    at async /app/dist/src/ordhook/server.js:57:9\n    at async Object.<anonymous> (/app/node_modules/@hirosystems/chainhook-client/dist/server.js:177:17)",
    "name": "BadPayloadRequestError"
  },
  "msg": "ChainhookEventObserver bad payload"
}
{
  "level": "info",
  "time": "2024-03-01T13:19:21.677Z",
  "pid": 7,
  "hostname": "bb4e651ca4a9",
  "name": "chainhook-client",
  "reqId": "req-51",
  "res": {
    "statusCode": 400
  },
  "responseTime":<PHONE_NUMBER>9609375,
  "msg": "request completed"
}

{
  "level": "error",
  "time": "2024-03-01T13:19:21.676Z",
  "pid": 7,
  "hostname": "bb4e651ca4a9",
  "name": "chainhook-client",
  "err": {
    "type": "BadPayloadRequestError",
    "message": "Block inscription gap detected: Attempting to insert #35144998 (810988) but current max is #35144902. Chain tip is at 810985.",
    "stack": "BadPayloadRequestError: Block inscription gap detected: Attempting to insert #35144998 (810988) but current max is #35144902. Chain tip is at 810985.\n    at assertNoBlockInscriptionGap (/app/dist/src/pg/helpers.js:23:19)\n    at /app/dist/src/pg/pg-store.js:85:59\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n    at async scope (/app/node_modules/postgres/cjs/src/index.js:226:18)\n    at async Function.begin (/app/node_modules/postgres/cjs/src/index.js:213:14)\n    at async PgStore.updateInscriptions (/app/dist/src/pg/pg-store.js:52:9)\n    at async /app/dist/src/ordhook/server.js:57:9\n    at async Object.<anonymous> (/app/node_modules/@hirosystems/chainhook-client/dist/server.js:177:17)",
    "name": "BadPayloadRequestError"
  },
  "msg": "ChainhookEventObserver bad payload"
}
{
  "level": "info",
  "time": "2024-03-01T13:19:21.677Z",
  "pid": 7,
  "hostname": "bb4e651ca4a9",
  "name": "chainhook-client",
  "reqId": "req-51",
  "res": {
    "statusCode": 400
  },
  "responseTime":<PHONE_NUMBER>9609375,
  "msg": "request completed"
}

@alexqrid can you share more details about the ordhook setup you have? there could be a version mismatch between the two

Closing this, please reopen if you have any more questions


[NVGPU] Allow async dots in an additional case.

[NVGPU] Allow async dots in an additional case.
Previously a dot could be async if the only use of its value from iteration i-1
was an async or sync dot.
We relax this to allow arbitrary uses of the value from iteration i-1 so long
as those uses come after a synchronous dot.  This better matches the original
code before I rewrote it in https://github.com/openai/triton/pull/3097.
To make this easier to reason about, I convert all MMAv3 dots to dot_async.
The synchronous dots just have a wait immediately after.
While we're here, we also thread dependencies properly through dot_wait ops.
Now that all MMAv3 dots are dot_async, this is a lot easier to do.
PR chain

👉 #3327 👈 YOU ARE HERE

@ThomasRaoux apologies for asking you to re-review code I just rewrote.

Huh, I could have sworn I had the lit tests working.  Anyway, fixed, I think.


typings: command not found

Errors during npm install
npm install ionic-hockeyapp --save

<EMAIL_ADDRESS>postinstall /Users/pbondt/Documents/node-work/inttime/node_modules/ionic-hockeyapp
typings install

sh: typings: command not found

Solved after installing typings
npm install typings -g

This issue has been resolved in v0.1.5. If still experience this issue on v0.1.5 or greater please create an issue.


[Enhancement] adjust configs for cloud star cache

Why I'm doing:
What I'm doing:

add starlet_star_cache_async_init
make starlet_star_cache_mem_size_percent and starlet_star_cache_mem_size_bytes dynamic
collect cloud star cache memory usage in daemon

Fixes #issue
What type of PR is this:

[x] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[ ] Yes, this PR will result in a change in behavior.
[x] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

[ ] This is a backport pr

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[x] 3.2
[x] 3.1
[ ] 3.0
[ ] 2.5

@mergify backport branch-3.1

@mergify backport branch-3.2

https://github.com/StarRocks/starrocks/pull/43377


how close bn when run demo in cpu?

Thank you for your great work!
How can I close close the bn when run demo in cpu?
ValueError: SyncBatchNorm expected input tensor to be on GPU

You can use substitute 'SyncBN' with 'BN'.


TTL support (and a few enhancements)

Introduce an extensible Options struct as a param for NewStream, which includes a TTL param. TTL leverages Redis Streams MINID param to expire old stream entries.
Also:

a constant for NoExpiration when TTL isn't desired
add RevRange method to Stream
support time.Time and time.Duration for ser/de
new Metadata field type for generic structured data
updated README

Hi @dranikpg - I have a few enhancements to your package that I've been using from my fork, but I thought I'd see if you're interested in merging them back into your original package. Let me know what you think of these, thanks!


Fixes to get the simulation to work with the current HEAD

The changes are outlined in https://github.com/US-JOET/base-camp/issues/153#issuecomment-2161931501

After creating the PR, re-ran the command again and then charged again.
Got the same results as https://github.com/US-JOET/everest-demo/pull/4/commits/11a1a909df7247fedd2cdb30a2ef024a1959678e

Testing done:

Modified demo-iso15118-2-ac-plus-ocpp.sh to copy instead of clone
bash demo-iso15118-2-ac-plus-ocpp.sh -r .../everest-demo -3
Selected AC ISO 15118; worked
Selected AC ISO 15118 PnC; worked

However, the detailed ISO logging isn't showing up. fixing that...

Fixed. Now tried to call setChargingProfile, which failed with the following error. it looks like @louisg1337 fixed MaEVe 😄
Fixing this in the patch for now and will ask @louisg1337 to test by removing the patch tomorrow.
2024-06-13 03:38:11.473557 [ERRO] ocpp:OCPP201    void ocpp::v201::from_json(const json&, SetChargingProfileRequest&) :: In the message class, parsing from JSON: {"ChargingProfile":{"chargingProfileKind":"Absolute","chargingProfilePurpose":"TxDefaultProfile","chargingSchedule":[{"chargingRateUnit":"A","chargingSchedulePeriod":[{"limit":20,"numberPhases":1,"startPeriod":0}],"duration":86400,"id":0,"minChargingRate":0,"startSchedule":"2024-06-12T00:00:00.000Z"}],"id":1,"recurrencyKind":"Daily","stackLevel":1},"EvseId":0}
2024-06-13 03:38:11.473955 [ERRO] ocpp:OCPP201    void ocpp::v201::ChargePoint::message_callback(const std::string&) :: JSON exception during handling of message: [json.exception.out_of_range.403] key 'ChargingProfileType' not found

Everything seems to work now. @louisg1337 can you pull from this branch, run and verify that you get the same results? I can then merge this to the charin-e2e-demo branch so that AFS can build on it. Then finally, we can start removing the patches one by one by incorporating the changes into the actual code 😄
Testing done:

Plugged in the car and got a charge delivery of 22kW with a 230V and 32 A
[DEBG] iso15118_car    pybind11_init_everestpy(pybind11::module_&)::<lambda(const std::string&)> :: Decoded message (ns=urn:iso:15118:2:2013:MsgDef): {"V2G_Message":{"Header":{"SessionID":"67634FE7DDFF935F"}
"Body":{"ChargeParameterDiscoveryRes":{"ResponseCode":"OK"
"EVSEProcessing":"Finished"
"SAScheduleList":{"SAScheduleTuple":[{"SAScheduleTupleID":1
"PMaxSchedule":{"PMaxScheduleEntry":[{"RelativeTimeInterval":{"start":0
"duration":86400}
"PMax":{"Multiplier":0
"Unit":"W"
"Value":22080}}]}}]}
"AC_EVSEChargeParameter":{"AC_EVSEStatus":{"NotificationMaxDelay":0
"EVSENotification":"None"
"RCD":false}
"EVSENominalVoltage":{"Multiplier":-1
"Unit":"V"
"Value":2300}
"EVSEMaxCurrent":{"Multiplier":-1
"Unit":"A"
"Value":320}}}}}}

Unplugged the car, and set a profile that was valid starting `2024-06-13T00:00:00.000Z` and a limit of 20 A (the file is attached)
2024-06-13 03:52:58.408417 [ERRO] ocpp:OCPP201    void ocpp::v201::ChargePoint::handle_set_charging_profile_req(ocpp::Call<ocpp::v201::SetChargingProfileRequest>) :: Received SetChargingProfile: {
    "chargingProfile": {
        "chargingProfileKind": "Absolute",
        "chargingProfilePurpose": "TxDefaultProfile",
        "chargingSchedule": [
            {
                "chargingRateUnit": "A",
                "chargingSchedulePeriod": [
                    {
                        "limit": 20.0,
                        "numberPhases": 1,
                        "startPeriod": 0
                    }
                ],
                "duration": 86400,
                "id": 0,
                "minChargingRate": 0.0,
                "startSchedule": "2024-06-13T00:00:00.000Z"
            }
        ],
        "id": 1,
        "recurrencyKind": "Daily",
        "stackLevel": 1
    },
    "evseId": 1
}
with messageId: 2b9f7b12-ac9b-46b8-88a3-72327a66928b
2024-06-13 03:52:58.409520 [WARN] ocpp:OCPP201    module::OCPP201::ready()::<lambda()> :: Received a new Charging Schedules from the CSMS or another actor.
2024-06-13 03:52:58.409682 [INFO] ocpp:OCPP201     :: ProfileId #1 Kind: Absolute
2024-06-13 03:52:58.409723 [INFO] ocpp:OCPP201     :: #1 find_period_at> 2024-06-13T00:00:00.000Z
2024-06-13 03:52:58.409765 [INFO] ocpp:OCPP201     ::    find_period_at>        start_time> 2024-06-13T03:52:58.409Z
2024-06-13 03:52:58.409794 [INFO] ocpp:OCPP201     ::    find_period_at> period_start_time> 2024-06-13T00:00:00.000Z
2024-06-13 03:52:58.409821 [INFO] ocpp:OCPP201     ::    find_period_at>   period_end_time> 2024-06-14T00:00:00.000Z
2024-06-13 03:52:58.409929 [INFO] ocpp:OCPP201     :: PeriodDateTimePair>  period: {
    "limit": 20.0,
    "numberPhases": 1,
    "startPeriod": 0
} end_time: 2024-06-14T00:00:00.000Z
2024-06-13 03:52:58.409998 [INFO] ocpp:OCPP201     :: period.has_value() limit = 4600
2024-06-13 03:52:58.410040 [INFO] ocpp:OCPP201     :: period.has_value() stackLevel = 4600
2024-06-13 03:52:58.453739 [ERRO] ocpp:OCPP201    void ocpp::v201::ChargePoint::handle_set_charging_profile_req(ocpp::Call<ocpp::v201::SetChargingProfileRequest>) :: Received profile validity: Validsetting response to {
    "status": "Accepted"
}

Plugged in the car again, and got max power of 4600 W, with 230V and 6.6A
[DEBG] iso15118_car    pybind11_init_everestpy(pybind11::module_&)::<lambda(const std::string&)> :: Decoded message (ns=urn:iso:15118:2:2013:MsgDef): {"V2G_Message":{"Header":{"SessionID":"6F6CE6DFFD1F6169"}
"Body":{"ChargeParameterDiscoveryRes":{"ResponseCode":"OK"
"EVSEProcessing":"Finished"
"SAScheduleList":{"SAScheduleTuple":[{"SAScheduleTupleID":1
"PMaxSchedule":{"PMaxScheduleEntry":[{"RelativeTimeInterval":{"start":0
"duration":86400}
"PMax":{"Multiplier":0
"Unit":"W"
"Value":4600}}]}}]}
"AC_EVSEChargeParameter":{"AC_EVSEStatus":{"NotificationMaxDelay":0
"EVSENotification":"None"
"RCD":false}
"EVSENominalVoltage":{"Multiplier":-1
"Unit":"V"
"Value":2300}
"EVSEMaxCurrent":{"Multiplier":-1
"Unit":"A"
"Value":66}}}}}}

TXProfile_1.json

To do my testing, I clone the US-JOET/everest-demo repo and checked out charin-e2e-demo-last-min-hacks. I then deleted all previous docker containers I had and ran bash demo-iso15118-2-ac-plus-ocpp.sh -3.

Plugged in the car and got a charge delivery of 22kW with a 230V and 32 A

Got the same result when plugging in the car normally.
2024-06-13 15:03:56.582203 [DEBG] iso15118_car    pybind11_init_everestpy(pybind11::module_&)::<lambda(const std::string&)> :: Decoded message (ns=urn:iso:15118:2:2013:MsgDef): {"V2G_Message":{"Header":{"SessionID":"9FAA4FDD3FEFBD3F"},
"Body":{"ChargeParameterDiscoveryRes":{"ResponseCode":"OK",
"EVSEProcessing":"Finished",
"SAScheduleList":{"SAScheduleTuple":[{"SAScheduleTupleID":1,
"PMaxSchedule":{"PMaxScheduleEntry":[{"RelativeTimeInterval":{"start":0,
"duration":86400},
"PMax":{"Multiplier":0,
"Unit":"W",
"Value":22080}}]}}]},
"AC_EVSEChargeParameter":{"AC_EVSEStatus":{"NotificationMaxDelay":0,
"EVSENotification":"None",
"RCD":false},
"EVSENominalVoltage":{"Multiplier":-1,
"Unit":"V",
"Value":2300},
"EVSEMaxCurrent":{"Multiplier":-1,
"Unit":"A",
"Value":320}}}}}}

Unplugged the car, and set a profile that was valid starting 2024-06-13T00:00:00.000Z and a limit of 20 A (the file is attached)

I unfortunately was not able to reproduce the setChargingProfile working properly. I ran the setChargingProfile script we have with the JSON file, but there weren't any EVerest logs that indicated we received a new profile. I did check the OCPP logs, however, and I found the setChargingProfile requests there, but with the typical "Unknown" response we have always gotten.

I'm not sure if I am doing something wrong, or if I don't have an updated version of EVerest with the new chargingProfile implementation. I'll keep on messing around with it to see what I am doing wrong that i am not getting the same results.

Plugged in the car again, and got max power of 4600 W, with 230V and 6.6A

Unable to reproduce because of the above.

Updated Testing
As I said in the edit section above, I was running the script without pointing it to my local directory, so I wasn't getting any of the patches. Now that I have the patches, things are working as expected.

Plugged in the car and got a charge delivery of 22kW with a 230V and 32 A

Same as the comment above.

Unplugged the car, and set a profile that was valid starting 2024-06-13T00:00:00.000Z and a limit of 20 A (the file is attached)

Got the same response after setChargingProfile API call
2024-06-13 16:28:32.924613 [ERRO] ocpp:OCPP201    void ocpp::v201::ChargePoint::handle_set_charging_profile_req(ocpp::Call<ocpp::v201::SetChargingProfileRequest>) :: Received SetChargingProfile: {
    "chargingProfile": {
        "chargingProfileKind": "Absolute",
        "chargingProfilePurpose": "TxDefaultProfile",
        "chargingSchedule": [
            {
                "chargingRateUnit": "A",
                "chargingSchedulePeriod": [
                    {
                        "limit": 20.0,
                        "numberPhases": 1,
                        "startPeriod": 0
                    }
                ],
                "duration": 86400,
                "id": 0,
                "minChargingRate": 0.0,
                "startSchedule": "2024-06-13T00:00:00.000Z"
            }
        ],
        "id": 1,
        "recurrencyKind": "Daily",
        "stackLevel": 1
    },
    "evseId": 1
}
with messageId: 197d7fa0-8aba-4135-bb0f-9fcbe3c2d280
2024-06-13 16:28:32.926104 [WARN] ocpp:OCPP201    module::OCPP201::ready()::<lambda()> :: Received a new Charging Schedules from the CSMS or another actor.
2024-06-13 16:28:32.926363 [INFO] ocpp:OCPP201     :: ProfileId #1 Kind: Absolute
2024-06-13 16:28:32.926639 [INFO] ocpp:OCPP201     :: #1 find_period_at> 2024-06-13T00:00:00.000Z
2024-06-13 16:28:32.926950 [INFO] ocpp:OCPP201     ::    find_period_at>        start_time> 2024-06-13T16:28:32.926Z
2024-06-13 16:28:32.927014 [INFO] ocpp:OCPP201     ::    find_period_at> period_start_time> 2024-06-13T00:00:00.000Z
2024-06-13 16:28:32.927057 [INFO] ocpp:OCPP201     ::    find_period_at>   period_end_time> 2024-06-14T00:00:00.000Z
2024-06-13 16:28:32.927286 [INFO] ocpp:OCPP201     :: PeriodDateTimePair>  period: {
    "limit": 20.0,
    "numberPhases": 1,
    "startPeriod": 0
} end_time: 2024-06-14T00:00:00.000Z
2024-06-13 16:28:32.927585 [INFO] ocpp:OCPP201     :: period.has_value() limit = 4600
2024-06-13 16:28:32.927671 [INFO] ocpp:OCPP201     :: period.has_value() stackLevel = 4600
2024-06-13 16:28:33.018306 [ERRO] ocpp:OCPP201    void ocpp::v201::ChargePoint::handle_set_charging_profile_req(ocpp::Call<ocpp::v201::SetChargingProfileRequest>) :: Received profile validity: Validsetting response to {
    "status": "Accepted"
}

Plugged in the car again, and got max power of 4600 W, with 230V and 6.6A

Got the same result once started charging using new profile
2024-06-13 16:33:53.809243 [DEBG] iso15118_car    pybind11_init_everestpy(pybind11::module_&)::<lambda(const std::string&)> :: Decoded message (ns=urn:iso:15118:2:2013:MsgDef): {"V2G_Message":{"Header":{"SessionID":"E8875BBEF62E2EFF"},
"Body":{"ChargeParameterDiscoveryRes":{"ResponseCode":"OK",
"EVSEProcessing":"Finished",
"SAScheduleList":{"SAScheduleTuple":[{"SAScheduleTupleID":1,
"PMaxSchedule":{"PMaxScheduleEntry":[{"RelativeTimeInterval":{"start":0,
"duration":86400},
"PMax":{"Multiplier":0,
"Unit":"W",
"Value":4600}}]}}]},
"AC_EVSEChargeParameter":{"AC_EVSEStatus":{"NotificationMaxDelay":0,
"EVSENotification":"None",
"RCD":false},
"EVSENominalVoltage":{"Multiplier":-1,
"Unit":"V",
"Value":2300},
"EVSEMaxCurrent":{"Multiplier":-1,
"Unit":"A",
"Value":66}}}}}}


Migrate Pipeline environment tasks to Node20

Task name:
Tasks with build config Node20_229_2 :
"AzureAppServiceManageV0","AzureAppServiceSettingsV1","AzureCLIV1","AzureCLIV2","AzureFileCopyV2","AzureFileCopyV3","AzureFileCopyV4","AzureFileCopyV5","AzureFunctionAppContainerV1","AzureFunctionOnKubernetesV0","AzureFunctionOnKubernetesV1","AzureKeyVaultV1","AzureKeyVaultV2","AzureMysqlDeploymentV1","AzureNLBManagementV1","AzureRmWebAppDeploymentV3","AzureRmWebAppDeploymentV4","AzureWebAppV1", "AzureWebAppContainerV1","ContainerBuildV0","DockerV0","DockerV1","DockerComposeV0","DockerInstallerV0","DotNetCoreCLIV2"
Tasks with build config Node20_229_3:
"DotNetCoreInstallerV0","DotNetCoreInstallerV1","DownloadBuildArtifactsV0","DownloadFileshareArtifactsV1","DownloadGitHubNpmPackageV1","DownloadGitHubNugetPackageV1","DownloadGitHubReleaseV0","DuffleInstallerV0","FileTransformV1","FileTransformV2","FuncToolsInstallerV0","GitHubReleaseV0","GitHubReleaseV1","GoV0","GoToolV0","HelmDeployV0","HelmInstallerV0","HelmInstallerV1","IISWebAppDeploymentOnMachineGroupV0","JenkinsDownloadArtifactsV1","KubectlInstallerV0","KubernetesV1","KubernetesManifestV0","MysqlDeploymentOnMachineGroupV1","UseDotNetV2"
Description: Migrate 50 tasks owned by pipeline environments team to Node20.
Splitting them into two task groups: Node20_229_2 and Node20_229_3.
@vsebesta   @rvairavelu  @manolerazvan  @pipeline-environment-team
Documentation changes required: (Y/N)
Added unit tests: (Y/N)
Attached related issue: (Y/N)
Checklist:

[x] Task version was bumped - please check instruction how to do it
[x] Checked that applied changes work as expected

@manolerazvan @rvairavelu Here's tasks migration PR that your team owns, could you please review and approve it? Thank you

@qianz2 I believe that files inside Tests/task outputs are generated by unit tests and should not be presented in the repo

hi @qianz2 may i know the use case of the file PreJobExecutionAzureFileCopy.ts under Tasks/AzureFileCopyV4 & Tasks/AzureFileCopyV5 and also as @DmitriiBobreshev suggested i hope the files under Tests/task is not required in repo.

@qianz2 I believe that files inside Tests/task outputs are generated by unit tests and should not be presented in the repo

test outputs are removed. Thanks for catching it.

hi @qianz2 may i know the use case of the file PreJobExecutionAzureFileCopy.ts under Tasks/AzureFileCopyV4 & Tasks/AzureFileCopyV5 and also as @DmitriiBobreshev suggested i hope the files under Tests/task is not required in repo.

Hi @PhilipsonJoseph I added PreJobExecutionAzureFileCopy.ts from AzureFileCopyV2/AzureFileCopyV3 for testing purpose, looks that it's working w/o this file, so removing it from AzureFileCopyV4/AzureFileCopyV5, thanks!

hi @qianz2 may i know the use case of the file PreJobExecutionAzureFileCopy.ts under Tasks/AzureFileCopyV4 & Tasks/AzureFileCopyV5 and also as @DmitriiBobreshev suggested i hope the files under Tests/task is not required in repo.

Hi @PhilipsonJoseph I added PreJobExecutionAzureFileCopy.ts from AzureFileCopyV2/AzureFileCopyV3 for testing purpose, looks that it's working w/o this file, so removing it from AzureFileCopyV4/AzureFileCopyV5, thanks!

Actually taking another look into it, this file is required to be node handler execution file we put in task.json and task.loc.json, we will need it to build node20 tasks.
"prejobexecution": {         "Node10": {           "target": "PreJobExecutionAzureFileCopy.js"         },         "Node16": {           "target": "PreJobExecutionAzureFileCopy.js",           "argumentFormat": ""         }     },

/azp run

hi @qianz2 may i know the use case of the file PreJobExecutionAzureFileCopy.ts under Tasks/AzureFileCopyV4 & Tasks/AzureFileCopyV5 and also as @DmitriiBobreshev suggested i hope the files under Tests/task is not required in repo.

Hi @PhilipsonJoseph I added PreJobExecutionAzureFileCopy.ts from AzureFileCopyV2/AzureFileCopyV3 for testing purpose, looks that it's working w/o this file, so removing it from AzureFileCopyV4/AzureFileCopyV5, thanks!

Actually taking another look into it, this file is required to be node handler execution file we put in task.json and task.loc.json, we will need it to build node20 tasks. "prejobexecution": { "Node10": { "target": "PreJobExecutionAzureFileCopy.js" }, "Node16": { "target": "PreJobExecutionAzureFileCopy.js", "argumentFormat": "" } },

@qianz2 but if I'm not wrong, AzureFileCopyV4 and AzureFileCopyV5 not node tasks but PowerShell, so why we need to use node execution handler is unclear for me

hi @qianz2 may i know the use case of the file PreJobExecutionAzureFileCopy.ts under Tasks/AzureFileCopyV4 & Tasks/AzureFileCopyV5 and also as @DmitriiBobreshev suggested i hope the files under Tests/task is not required in repo.

Hi @PhilipsonJoseph I added PreJobExecutionAzureFileCopy.ts from AzureFileCopyV2/AzureFileCopyV3 for testing purpose, looks that it's working w/o this file, so removing it from AzureFileCopyV4/AzureFileCopyV5, thanks!

Actually taking another look into it, this file is required to be node handler execution file we put in task.json and task.loc.json, we will need it to build node20 tasks. "prejobexecution": { "Node10": { "target": "PreJobExecutionAzureFileCopy.js" }, "Node16": { "target": "PreJobExecutionAzureFileCopy.js", "argumentFormat": "" } },

@qianz2 but if I'm not wrong, AzureFileCopyV4 and AzureFileCopyV5 not node tasks but PowerShell, so why we need to use node execution handler is unclear for me
UPD. It seems they were in V2 & V3 tasks but has gone after that. Could removing PrejobExecution be the real reason for new tasks? If so, I'm not sure it's worth returning them in this PR

Hi @KonstantinTyukalov , AzureFileCopy tasks are written in Powershell, and we use nodejs to build and test it. I've tried to build it first time without PreJobExecutionAzureFileCopy.js file in it or without specifying it in task.json/task.loc.json files, and it failed.  Once they were built successfully and migrated tasks files are generated under _generated folder, we don't need this PreJobExecutionAzureFileCopy.js file in subsequential builds and test runs. So I'm okay to either remove it or keep it.


Use cargo embed instead of cargo-embed

Replaces dash with whitespace since the version if the dash is not working.

:warning: Warning :warning:

Pull requests are usually filed against the master branch for this repo, but this one is against rewrite. Please double check that you specified the right target!

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @jamesmunns (or someone else) soon.
Please see the contribution instructions for more information.


[_50] request build() before up() in project (4-2-stable)

This step results in a rebuild of the image to be run if the
Dockerfile dependency has changed.  Note, this can happen due
to a switch between git branches.

So, there's no logic here to detect anything - it will always run the build() step... but usually, it will all be cached and quick.
Is that correct?

Yes, the build command uses cache by default (with an option for --no-cache). We can possibly expose this option in the future should we desire the ability to forego the cached images.

In fact, up() has an option called do_build that I considered suggesting as an alternative to this implementation, but that would require importing an enumeration called BuildAction and further entrench us in the Docker implementation. This, too, could be an improvement added as part of the abstraction effort of #8

Sold.   I vote to # it up.

Yes, I saw the do_build option too. Six, half dozen, I believe. (Ok, my 2 cents are in.)


Tutorial on passwords and git

This issue is about ways to avoid plain passwords in scripts & git repository.


Separated documentation into multiple files

This is awesome! Thanks for cleaning up the docs a bit. The application links to certain anchors in the documentation and these links would be broken now. Would you mind correcting the links in the following files?

https://github.com/SecretiveShell/hass-workstation-service/blob/master/UserInterface/Views/AddCommandDialog.axaml.cs
https://github.com/SecretiveShell/hass-workstation-service/blob/master/UserInterface/Views/AddSensorDialog.axaml.cs

Sure! I will take a look now

Please let me know if there are any other changes that need to be made!


Integrate GitHub histories

A simple link to the history would help people evaluate what had changed without requiring authors to detail it.

Moving away from GitHub.


Attempt at a monitor pipeline refactor

That makes sense. I am going to go ahead and close this pull request.


Have a look at http://pitest.org/

PIT is definitely the best mutation tester out there. Add every feature, mutator and idea in the issue tracker.

Has a configuration file -> we do not need that
A lot of additional arguments -> Lots of Java specific arguments as well as additional filtering (e.g. filter for certain classes/functions); Arguments to fail at a certain point (e.g. if mutation score < x)
Integration into build systems e.g. Ant and Maven
"Off by one"-mutators -> #23
Mutates the byte code itself -> would be nice
Lots of reporting for mutation runs e.g. out of memory and time out -> would be nice
Incremental run -> would be very nice


CPU usage become very high when using the incorrect interval param.

When I use this command './profiler.sh -d 15 -i 10.1ms -o collapsed 2121155' to profile a java process, the cpu of the user process rise to more than 3000%. I guess, maybe the interval param should be long type but here we set to a decimal type caused this problem. So would it be better to check before execution?

10.1ms is not a valid value for the interval argument. Use 10100us instead.
Profiler treated it as just 10 (nanoseconds), which obviously causes too big performance overhead. I fixed the parser to print error in such cases.


HBASE-23953 SimpleBalancer bug when second pass to fill up to min

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 10s
Docker mode activated.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
5m 41s
the patch passed

-0 :warning:
checkstyle
1m 17s
hbase-server: The patch generated 7 new + 154 unchanged - 0 fixed = 161 total (was 154)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
18m 20s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

-1 :x:
findbugs
3m 16s
hbase-server in the patch failed.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
7m  8s
the patch passed

+1 :green_heart:
compile
1m 12s
the patch passed

+1 :green_heart:
javac
1m 12s
the patch passed

+1 :green_heart:
shadedjars
5m 28s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 40s
hbase-server in the patch failed.

_ Other Tests _

+1 :green_heart:
unit
81m 44s
hbase-server in the patch passed.

114m 24s

Subsystem
Report/Notes

Docker
Client=19.03.7 Server=19.03.7 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1262/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1262

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux cc8683b5615a 4.15.0-74-generic #84-Ubuntu SMP Thu Dec 19 08:06:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 31484f007f

Default Java
2020-01-14

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1262/1/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-server.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1262/1/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-server.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1262/1/testReport/

Max. process+thread count
5727 (vs. ulimit of 10000)

modules
C: hbase-server U: hbase-server

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1262/1/console

versions
git=2.17.1 maven=2018-06-17T18:33:14Z)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.


Bump to v2.2.4

coverage: 91.144% (+0.01%) from 91.133%
when pulling 9e9d3e62e15fe8dfff9ba45d646521959239eab1 on bump_v224
into 75a2d85e6d17aadb03ee26f7491e368fc1700a8e on master.


"Getting started gce" deadlink

modify for kubernetes/website link

remove unnecessary .md link

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
For 1.11 Features: set Milestone to 1.11 and Base Branch to release-1.11
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
NOTE: After opening the PR, please un-check and re-check the "Allow edits from maintainers" box so that maintainers can work on your patch and speed up the review process. This is a temporary workaround to address a known issue with GitHub.>
Please delete this note before submitting the pull request.

@justinsb
Thank you for your review.
I think it same, so I modify the link from github.com to kubernetes.io
Best,

I heard from mistyhacks, HUGO migration is checked by you.
Thank you for your help!
/assign @steveperry-53
/assign @Bradamant3

@MasayaAoyama we don't accept PRs against old blog posts (take a look at the date ;) ). The change you made to the other file is useful, though. Could you please remove the blog post file and resubmit for the other change? Thanks!

@Bradamant3 Hello, Thank you for your review.
I modified for your suggestion.

/lgtm
/approve


Fix file not found when delete a cached image.

Everywhere else the uniqueId is used instead of creating a new one and in this case the file extension was not being considered, thus the previously cached file was not being found.

Thanks for the fix. Merging it.