text:
[Bug]: Error: Call to undefined method DateTime::isoFormat()

What happened?
Call to undefined method DateTime::isoFormat() when opening reservation.
log shows ->

2022-08-18 12:52:13
Error: Call to undefined method DateTime::isoFormat()in /customers/c/c/2/photobella.nl/httpd.www/tast/extensions/igniter/reservation/components/Booking.php:257Stack trace:#0 /customers/c/c/2/photobella.nl/httpd.www/tast/extensions/igniter/reservation/components/Booking.php(309): Igniter\Reservation\Components\Booking->getTimeSlots()#1 /customers/c/c/2/photobella.nl/httpd.www/tast/extensions/igniter/reservation/components/Booking.php(134): Igniter\Reservation\Components\Booking->processPickerForm()#2 /customers/c/c/2/photobella.nl/httpd.www/tast/app/main/classes/MainController.php(743): Igniter\Reservation\Components\Booking->initialize()#3 /customers/c/c/2/photobella.nl/httpd.www/tast/app/main/classes/MainController.php(571): Main\Classes\MainController->addComponent('booking', 'booking', Array)#4 /customers/c/c/2/photobella.nl/httpd.www/tast/app/main/classes/MainController.php(244): Main\Classes\MainController->initializeComponents()#5 /customers/c/c/2/photobella.nl/httpd.www/tast/app/main/classes/MainController.php(201): Main\Classes\MainController->runPage(Object(Main\Template\Page))#6 /customers/c/c/2/photobella.nl/httpd.www/tast/app/system/classes/Controller.php(97): Main\Classes\MainController->remap('default/reserva...')#7 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Routing/Controller.php(54): System\Classes\Controller->run('default/reserva...')#8 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Routing/ControllerDispatcher.php(45): Illuminate\Routing\Controller->callAction('run', Array)#9 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Routing/Route.php(262): Illuminate\Routing\ControllerDispatcher->dispatch(Object(Illuminate\Routing\Route), Object(System\Classes\Controller), 'run')#10 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Routing/Route.php(205): Illuminate\Routing\Route->runController()#11 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Routing/Router.php(721): Illuminate\Routing\Route->run()#12 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(128): Illuminate\Routing\Router->Illuminate\Routing{closure}(Object(Illuminate\Http\Request))#13 /customers/c/c/2/photobella.nl/httpd.www/tast/extensions/igniter/user/middleware/ThrottleRequests.php(20): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}(Object(Illuminate\Http\Request))#14 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(167): Igniter\User\Middleware\ThrottleRequests->handle(Object(Illuminate\Http\Request), Object(Closure))#15 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/tastyigniter/flame/src/Translation/Middleware/Localization.php(27): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}(Object(Illuminate\Http\Request))#16 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(167): Igniter\Flame\Translation\Middleware\Localization->handle(Object(Illuminate\Http\Request), Object(Closure))#17 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Routing/Middleware/SubstituteBindings.php(50): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}(Object(Illuminate\Http\Request))#18 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(167): Illuminate\Routing\Middleware\SubstituteBindings->handle(Object(Illuminate\Http\Request), Object(Closure))#19 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/View/Middleware/ShareErrorsFromSession.php(49): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}(Object(Illuminate\Http\Request))#20 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(167): Illuminate\View\Middleware\ShareErrorsFromSession->handle(Object(Illuminate\Http\Request), Object(Closure))#21 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Session/Middleware/StartSession.php(121): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}(Object(Illuminate\Http\Request))#22 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Session/Middleware/StartSession.php(64): Illuminate\Session\Middleware\StartSession->handleStatefulRequest(Object(Illuminate\Http\Request), Object(Illuminate\Session\Store), Object(Closure))#23 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(167): Illuminate\Session\Middleware\StartSession->handle(Object(Illuminate\Http\Request), Object(Closure))#24 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Cookie/Middleware/AddQueuedCookiesToResponse.php(37): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}(Object(Illuminate\Http\Request))#25 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(167): Illuminate\Cookie\Middleware\AddQueuedCookiesToResponse->handle(Object(Illuminate\Http\Request), Object(Closure))#26 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Cookie/Middleware/EncryptCookies.php(67): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}(Object(Illuminate\Http\Request))#27 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(167): Illuminate\Cookie\Middleware\EncryptCookies->handle(Object(Illuminate\Http\Request), Object(Closure))#28 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(103): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}(Object(Illuminate\Http\Request))#29 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Routing/Router.php(723): Illuminate\Pipeline\Pipeline->then(Object(Closure))#30 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Routing/Router.php(698): Illuminate\Routing\Router->runRouteWithinStack(Object(Illuminate\Routing\Route), Object(Illuminate\Http\Request))#31 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Routing/Router.php(662): Illuminate\Routing\Router->runRoute(Object(Illuminate\Http\Request), Object(Illuminate\Routing\Route))#32 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/tastyigniter/flame/src/Router/CoreRouter.php(22): Illuminate\Routing\Router->dispatchToRoute(Object(Illuminate\Http\Request))#33 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(167): Igniter\Flame\Router\CoreRouter->dispatch(Object(Illuminate\Http\Request))#34 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(128): Illuminate\Foundation\Http\Kernel->Illuminate\Foundation\Http{closure}(Object(Illuminate\Http\Request))#35 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/tastyigniter/flame/src/Setting/Middleware/SaveSetting.php(27): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}(Object(Illuminate\Http\Request))#36 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(167): Igniter\Flame\Setting\Middleware\SaveSetting->handle(Object(Illuminate\Http\Request), Object(Closure))#37 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/TransformsRequest.php(21): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}(Object(Illuminate\Http\Request))#38 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/TrimStrings.php(40): Illuminate\Foundation\Http\Middleware\TransformsRequest->handle(Object(Illuminate\Http\Request), Object(Closure))#39 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(167): Illuminate\Foundation\Http\Middleware\TrimStrings->handle(Object(Illuminate\Http\Request), Object(Closure))#40 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/ValidatePostSize.php(27): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}(Object(Illuminate\Http\Request))#41 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(167): Illuminate\Foundation\Http\Middleware\ValidatePostSize->handle(Object(Illuminate\Http\Request), Object(Closure))#42 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/PreventRequestsDuringMaintenance.php(86): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}(Object(Illuminate\Http\Request))#43 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(167): Illuminate\Foundation\Http\Middleware\PreventRequestsDuringMaintenance->handle(Object(Illuminate\Http\Request), Object(Closure))#44 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/fruitcake/laravel-cors/src/HandleCors.php(38): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}(Object(Illuminate\Http\Request))#45 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(167): Fruitcake\Cors\HandleCors->handle(Object(Illuminate\Http\Request), Object(Closure))#46 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/fideloper/proxy/src/TrustProxies.php(57): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}(Object(Illuminate\Http\Request))#47 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(167): Fideloper\Proxy\TrustProxies->handle(Object(Illuminate\Http\Request), Object(Closure))#48 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(103): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}(Object(Illuminate\Http\Request))#49 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(142): Illuminate\Pipeline\Pipeline->then(Object(Closure))#50 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(111): Illuminate\Foundation\Http\Kernel->sendRequestThroughRouter(Object(Illuminate\Http\Request))#51 /customers/c/c/2/photobella.nl/httpd.www/tast/index.php(53): Illuminate\Foundation\Http\Kernel->handle(Object(Illuminate\Http\Request))#52 {main}

What did you expect to happen?
Reservation not opening
Version
3.5.x
What browser are you seeing the problem on?
Firefox, Chrome, Safari
Relevant log output
2022-08-18 12:52:13	Error: Call to undefined method DateTime::isoFormat()
in /customers/c/c/2/photobella.nl/httpd.www/tast/extensions/igniter/reservation/components/Booking.php:257
Stack trace:
#0 /customers/c/c/2/photobella.nl/httpd.www/tast/extensions/igniter/reservation/components/Booking.php(309): Igniter\Reservation\Components\Booking->getTimeSlots()
#1 /customers/c/c/2/photobella.nl/httpd.www/tast/extensions/igniter/reservation/components/Booking.php(134): Igniter\Reservation\Components\Booking->processPickerForm()
#2 /customers/c/c/2/photobella.nl/httpd.www/tast/app/main/classes/MainController.php(743): Igniter\Reservation\Components\Booking->initialize()
#3 /customers/c/c/2/photobella.nl/httpd.www/tast/app/main/classes/MainController.php(571): Main\Classes\MainController->addComponent('booking', 'booking', Array)
#4 /customers/c/c/2/photobella.nl/httpd.www/tast/app/main/classes/MainController.php(244): Main\Classes\MainController->initializeComponents()
#5 /customers/c/c/2/photobella.nl/httpd.www/tast/app/main/classes/MainController.php(201): Main\Classes\MainController->runPage(Object(Main\Template\Page))
#6 /customers/c/c/2/photobella.nl/httpd.www/tast/app/system/classes/Controller.php(97): Main\Classes\MainController->remap('default/reserva...')
#7 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Routing/Controller.php(54): System\Classes\Controller->run('default/reserva...')
#8 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Routing/ControllerDispatcher.php(45): Illuminate\Routing\Controller->callAction('run', Array)
#9 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Routing/Route.php(262): Illuminate\Routing\ControllerDispatcher->dispatch(Object(Illuminate\Routing\Route), Object(System\Classes\Controller), 'run')
#10 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Routing/Route.php(205): Illuminate\Routing\Route->runController()
#11 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Routing/Router.php(721): Illuminate\Routing\Route->run()
#12 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(128): Illuminate\Routing\Router->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#13 /customers/c/c/2/photobella.nl/httpd.www/tast/extensions/igniter/user/middleware/ThrottleRequests.php(20): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#14 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(167): Igniter\User\Middleware\ThrottleRequests->handle(Object(Illuminate\Http\Request), Object(Closure))
#15 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/tastyigniter/flame/src/Translation/Middleware/Localization.php(27): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#16 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(167): Igniter\Flame\Translation\Middleware\Localization->handle(Object(Illuminate\Http\Request), Object(Closure))
#17 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Routing/Middleware/SubstituteBindings.php(50): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#18 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(167): Illuminate\Routing\Middleware\SubstituteBindings->handle(Object(Illuminate\Http\Request), Object(Closure))
#19 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/View/Middleware/ShareErrorsFromSession.php(49): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#20 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(167): Illuminate\View\Middleware\ShareErrorsFromSession->handle(Object(Illuminate\Http\Request), Object(Closure))
#21 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Session/Middleware/StartSession.php(121): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#22 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Session/Middleware/StartSession.php(64): Illuminate\Session\Middleware\StartSession->handleStatefulRequest(Object(Illuminate\Http\Request), Object(Illuminate\Session\Store), Object(Closure))
#23 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(167): Illuminate\Session\Middleware\StartSession->handle(Object(Illuminate\Http\Request), Object(Closure))
#24 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Cookie/Middleware/AddQueuedCookiesToResponse.php(37): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#25 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(167): Illuminate\Cookie\Middleware\AddQueuedCookiesToResponse->handle(Object(Illuminate\Http\Request), Object(Closure))
#26 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Cookie/Middleware/EncryptCookies.php(67): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#27 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(167): Illuminate\Cookie\Middleware\EncryptCookies->handle(Object(Illuminate\Http\Request), Object(Closure))
#28 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(103): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#29 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Routing/Router.php(723): Illuminate\Pipeline\Pipeline->then(Object(Closure))
#30 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Routing/Router.php(698): Illuminate\Routing\Router->runRouteWithinStack(Object(Illuminate\Routing\Route), Object(Illuminate\Http\Request))
#31 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Routing/Router.php(662): Illuminate\Routing\Router->runRoute(Object(Illuminate\Http\Request), Object(Illuminate\Routing\Route))
#32 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/tastyigniter/flame/src/Router/CoreRouter.php(22): Illuminate\Routing\Router->dispatchToRoute(Object(Illuminate\Http\Request))
#33 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(167): Igniter\Flame\Router\CoreRouter->dispatch(Object(Illuminate\Http\Request))
#34 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(128): Illuminate\Foundation\Http\Kernel->Illuminate\Foundation\Http\{closure}(Object(Illuminate\Http\Request))
#35 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/tastyigniter/flame/src/Setting/Middleware/SaveSetting.php(27): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#36 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(167): Igniter\Flame\Setting\Middleware\SaveSetting->handle(Object(Illuminate\Http\Request), Object(Closure))
#37 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/TransformsRequest.php(21): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#38 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/TrimStrings.php(40): Illuminate\Foundation\Http\Middleware\TransformsRequest->handle(Object(Illuminate\Http\Request), Object(Closure))
#39 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(167): Illuminate\Foundation\Http\Middleware\TrimStrings->handle(Object(Illuminate\Http\Request), Object(Closure))
#40 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/ValidatePostSize.php(27): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#41 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(167): Illuminate\Foundation\Http\Middleware\ValidatePostSize->handle(Object(Illuminate\Http\Request), Object(Closure))
#42 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/PreventRequestsDuringMaintenance.php(86): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#43 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(167): Illuminate\Foundation\Http\Middleware\PreventRequestsDuringMaintenance->handle(Object(Illuminate\Http\Request), Object(Closure))
#44 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/fruitcake/laravel-cors/src/HandleCors.php(38): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#45 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(167): Fruitcake\Cors\HandleCors->handle(Object(Illuminate\Http\Request), Object(Closure))
#46 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/fideloper/proxy/src/TrustProxies.php(57): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#47 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(167): Fideloper\Proxy\TrustProxies->handle(Object(Illuminate\Http\Request), Object(Closure))
#48 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(103): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#49 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(142): Illuminate\Pipeline\Pipeline->then(Object(Closure))
#50 /customers/c/c/2/photobella.nl/httpd.www/tast/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(111): Illuminate\Foundation\Http\Kernel->sendRequestThroughRouter(Object(Illuminate\Http\Request))
#51 /customers/c/c/2/photobella.nl/httpd.www/tast/index.php(53): Illuminate\Foundation\Http\Kernel->handle(Object(Illuminate\Http\Request))
#52 {main}

Fixed in v3.5.4

Thanks Sam but unfortunately i still can't access the reservation even after the update to V 3.5.4 and i'm having the same error.
do you mind sharing correction and i can try to fix it manually. thanks

authors: iva-system sampoyigi

repo: tastyigniter/TastyIgniter


text:
Directory.EnumerateDirectories ignore case on directory #134

EnumerateDirectories was fixed

Fixing issue #134

Hi @ericnewton76
Test Move_DirectoryExistsWithDifferentCase_DirectorySuccessfullyMoved was changed to be less specific

Will be published to NuGet within a few minutes. Thanks.

source: gharchive/pull-request

authors: borismod tathamoddie

license: MIT

license_type: permissive

license_source: github-api


text:
Roave

Adds RoaveBC for backward-compatibility break detection

Pull Request Test Coverage Report for Build 839662019

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 83.019%

Totals

Change from base Build 839659763:
0.0%

Covered Lines:
44

Relevant Lines:
53

💛  - Coveralls

authors: MGatner coveralls


text:
fix(updater): windows field is none by default

Fix #1015
Also fixes installerArgs not working in tauri config files

Not sure why it can't pick up installer_args if windows field is Option<WindowsConfig>, WindowsConfig works though

Strange, cargo test --bin app-updater on my machine succeed

repo: tauri-apps/plugins-workspace


text:
fix: build on windows when system-tray feature is not enabled

What kind of change does this PR introduce? (check at least one)

[x] Bugfix
[ ] Feature
[ ] Code style update
[ ] Refactor
[ ] Documentation
[ ] Build-related changes
[ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

[ ] Yes. Issue #___
[ ] No

The PR fulfills these requirements:

[ ] When resolving a specific issue, it's referenced in the PR's title (e.g. fix: #xxx[,#xxx], where "xxx" is the issue number)
[ ] A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.

If adding a new feature, the PR's description includes:

[ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

Oops! So sorry!
I’ll add a CI test no-featurs on windows and mac too I think, we should be able to catch this.

authors: lemarier lucasfernog

repo: tauri-apps/tao


text:
document supported versions

We should document what versions of our dependencies we support.

I know this should be implementrd over at tauri-docs but let’s discuss this here first.

OS

macOS: >= 10.15
window: >= win10
linux: ???

Other

Node.js: >= 12.13.0 (Should this be raised to 12.22.0 to support  napi 8? )
Rustc: >= 1.56.0 (edition 2021)
Cargo: >= 1.56.0 (edition 2021)

macos

I'm really fine with 10.15. But we could add a note that reportedly >=10.13 works too, and that we won't provide support for it or something like this.

windows

>= win7 -> webview2 supports it, it's still too widespread, and it has some extended support for security fixes for enterprise versions. In general we don't have to invest too much time to support it anyway, or at least not enough to justify potentially loosing the enterprise audience.

linux

That's really difficult. So far it's just "as long as it has webkit2gtk". centos7 (oldest linux that still got lts support) still got webkit1gtk, causing some problems. So for now it's something like >= ubuntu 18.04 or equivalent.
This might change if we need webkit2gtk >= 2.36 for the fixed header thingies.
But with linux being linux we can't rely on that until quite some time after its release (of provide some kind of fallback)...

Rust

>= 1.57 -> already done in the audit repo. Even if not i'd defend that with all i got haha. Multiple users (including me) reported that compiling on 1.56 produced broken release binaries on windows.

Node.js

Might as well raise this to >= 12.20, which is used in the js cli right now. 1.22 is only 4 months younger than 1.20, so 1.22 would be fine imo too, if it adds something valuable.
-> this should be discussed together with the potential napi/esbuild-like changes i guess.

We also need to add a note saying that window.print is only supported on macOS 11+

source: gharchive/issue

authors: FabianLars JonasKruckenberg lucasfernog

repo: tauri-apps/tauri


text:
[bug] wrong language code in allowlist for msi bundle

Describe the bug
Legitimate BCP 47 Code for Korean is ko-KR.
but ko-KO is specified in the file which is used as allowlist.
https://github.com/tauri-apps/tauri/blob/6650e5d6720c215530ca1fdccd19bd2948dd6ca3/tooling/bundler/src/bundle/windows/msi/languages.json#L70
So, bundling Windows msi fails when tauri.bundle.windows.wix.language in tauri.conf.json is ko-KR.
thread '<unnamed>' panicked at 'Language ko-KR not found. It must be one of et-EE, he-IL, hr-HR, tr-TR, de-DE, pl-PL, sr-Latn-CS, it-IT, eu-ES, da-DK, hu-HU, jp-JP, fi-FI, en-US, es-ES, ca-ES, sk-SK, ro-RO, zh-TW, lt-LT, ru-RU, sv-SE, th-TH, ar-SA, uk-UA, nb-NO, zh-CN, bg-BG, nl-NL, ko-KO, el-GR, sl-SI, vi-VN, lv-LV, cs-CZ, pt-PT, fr-FR, pt-BR', D:\a\tauri\tauri\tooling\bundler\src\bundle\windows\msi\wix.rs:636:7

Reproduction
No response
Expected behavior
ko-KR should be valid language code for the config
Platform and versions
GitHub Actions

Stack trace
No response
Additional context
No response

I want to fix it and make a PR and It will be a breaking change. But I have no idea that it is okay or not.

thank you, and since it never worked in the first place, it is a bugfix and not a breaking change, so I'd love to see a PR

authors: amrbashir dolsup


text:
[bug] Can't run the examples

Describe the bug
I'm trying tauri for the first days and everything runs fine with create-tauri-app, but I want to know a little deeper about it and I'm trying to run the examples. I started with the examples/api and follow the readme.md but the example doesn't start.
I'm trying to run with different ways in dev, latest, next and 1.x branches without success until now.
I'm using WSL2 on Windows 11 and started following these v1 instructions, then quick start and now I'm stucked in the example with the error bellow:
$ yarn tauri dev
yarn run v1.22.21
warning package.json: No license field
$ node ../../tooling/cli/node/tauri.js dev
     Running BeforeDevCommand (`yarn dev`)
warning package.json: No license field
$ vite --clearScreen false --port 5173

  vite v2.9.16 dev server running at:

  > Local: http://localhost:5173/
  > Network: use `--host` to expose

  ready in 629ms.

        Info Watching /home/lucascampelo/projetos/lucascampelo/tauri/examples/api/src-tauri for changes...
    Updating crates.io index
error: failed to select a version for `nix`.
    ... required by package `wl-clipboard-rs v0.8.0`
    ... which satisfies dependency `wl-clipboard-rs = "^0.8"` of package `arboard v3.3.0`
    ... which satisfies dependency `arboard = "^3"` (locked to 3.3.0) of package `tauri-runtime-wry v0.14.4 (/home/lucascampelo/projetos/lucascampelo/tauri/core/tauri-runtime-wry)`
    ... which satisfies path dependency `tauri-runtime-wry` of package `api v0.1.0 (/home/lucascampelo/projetos/lucascampelo/tauri/examples/api/src-tauri)`
versions that meet the requirements `^0.26.4` are: 0.26.4

all possible versions conflict with previously selected packages.

  previously selected package `nix v0.26.2`
    ... which satisfies dependency `nix = "^0.26.0"` (locked to 0.26.2) of package `tauri v1.6.0 (/home/lucascampelo/projetos/lucascampelo/tauri/core/tauri)`
    ... which satisfies path dependency `tauri` of package `api v0.1.0 (/home/lucascampelo/projetos/lucascampelo/tauri/examples/api/src-tauri)`

failed to select a version for `nix` which could resolve this conflict
error Command failed with exit code 101.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Reproduction
Try to run the examples/api in a new environment.
Expected behavior
To start the example app.
Full tauri info output
[✔] Environment
    - OS: Ubuntu 20.04 X64
    ✔ webkit2gtk-4.0: 2.38.6
    ✔ rsvg2: 2.48.9
    ✔ rustc: 1.76.0 (07dca489a 2024-02-04)
    ✔ cargo: 1.76.0 (c84b36747 2024-01-18)
    ✔ rustup: 1.26.0 (5af9b9484 2023-04-05)
    ✔ Rust toolchain: stable-x86_64-unknown-linux-gnu (default)
    - node: 20.10.0
    - yarn: 1.22.21
    - npm: 10.2.3

[-] Packages
    - tauri [RUST]: 1.5.3
    - tauri-build [RUST]: 1.5.0
    - wry [RUST]: 0.24.6
    - tao [RUST]: 0.16.2
    - tauri-cli [RUST]: 1.5.10
    - @tauri-apps/api [NPM]: 1.5.3
    - @tauri-apps/cli [NPM]: 1.5.10

[-] App
    - build-type: bundle
    - CSP: img-src 'self' asset: https://asset.localhost blob: data:; default-src 'self' customprotocol: asset:; font-src https://fonts.gstatic.com; style-src 'unsafe-inline' 'self' https://fonts.googleapis.com
    - distDir: ../dist
    - devPath: http://localhost:5173/
    - framework: Svelte
    - bundler: Vite

Stack trace
error: failed to select a version for `nix`.
    ... required by package `wl-clipboard-rs v0.8.0`
    ... which satisfies dependency `wl-clipboard-rs = "^0.8"` of package `arboard v3.3.0`
    ... which satisfies dependency `arboard = "^3"` (locked to 3.3.0) of package `tauri-runtime-wry v0.14.4 (/home/lucascampelo/projetos/lucascampelo/tauri/core/tauri-runtime-wry)`
    ... which satisfies path dependency `tauri-runtime-wry` of package `api v0.1.0 (/home/lucascampelo/projetos/lucascampelo/tauri/examples/api/src-tauri)`
versions that meet the requirements `^0.26.4` are: 0.26.4

all possible versions conflict with previously selected packages.

  previously selected package `nix v0.26.2`
    ... which satisfies dependency `nix = "^0.26.0"` (locked to 0.26.2) of package `tauri v1.6.0 (/home/lucascampelo/projetos/lucascampelo/tauri/core/tauri)`
    ... which satisfies path dependency `tauri` of package `api v0.1.0 (/home/lucascampelo/projetos/lucascampelo/tauri/examples/api/src-tauri)`

failed to select a version for `nix` which could resolve this conflict
error Command failed with exit code 101.

Additional context
No response

After the update, keep the same error.
Just for feedback:
$ cargo update
    Updating crates.io index
    Updating addr2line v0.20.0 -> v0.21.0
    Updating anyhow v1.0.79 -> v1.0.80
    Updating arboard v3.2.1 -> v3.3.1
    Updating async-channel v1.9.0 -> v2.2.0
    Updating async-executor v1.5.1 -> v1.8.0
      Adding async-io v2.3.1
      Adding async-lock v3.3.0
    Updating async-process v1.7.0 -> v1.8.1
      Adding async-signal v0.2.5
    Updating backtrace v0.3.68 -> v0.3.69
    Updating blocking v1.4.1 -> v1.5.1
    Updating bstr v1.6.2 -> v1.9.0
    Updating bumpalo v3.14.0 -> v3.15.0
    Updating cargo_toml v0.15.2 -> v0.15.3
    Updating cfg-expr v0.15.4 -> v0.15.7
    Updating clipboard-win v4.5.0 -> v5.1.0
    Updating colored v2.0.2 -> v2.1.0
      Adding core-graphics v0.23.1
    Updating crossbeam-channel v0.5.8 -> v0.5.11
      Adding crossbeam-deque v0.8.5
      Adding crossbeam-epoch v0.9.18
    Updating crossbeam-utils v0.8.16 -> v0.8.19
    Removing cty v0.2.2
    Updating darling v0.20.5 -> v0.20.6
    Updating darling_core v0.20.5 -> v0.20.6
    Updating darling_macro v0.20.5 -> v0.20.6
      Adding deranged v0.3.11
      Adding dlib v0.5.2
    Updating embed-resource v2.3.0 -> v2.4.1
      Adding equivalent v1.0.1
    Updating error-code v2.3.1 -> v3.0.0
      Adding event-listener v3.1.0
      Adding event-listener v4.0.3
      Adding event-listener v5.1.0
      Adding event-listener-strategy v0.4.0
      Adding event-listener-strategy v0.5.0
    Updating flate2 v1.0.26 -> v1.0.28
      Adding foreign-types v0.5.0
      Adding foreign-types-macros v0.2.3
      Adding foreign-types-shared v0.3.1
      Adding futures-lite v2.2.0
    Updating gethostname v0.2.3 -> v0.4.3
    Updating gimli v0.27.3 -> v0.28.1
    Updating globset v0.4.13 -> v0.4.14
    Updating h2 v0.3.20 -> v0.3.24
      Adding hashbrown v0.14.3
    Updating ignore v0.4.18 -> v0.4.22
    Updating image v0.24.4 -> v0.24.8
      Adding indexmap v2.2.3
    Removing is-terminal v0.4.7
    Updating jpeg-decoder v0.2.6 -> v0.3.1
      Adding libloading v0.8.1
      Adding linux-raw-sys v0.4.13
    Updating memchr v2.6.2 -> v2.7.1
    Removing memoffset v0.6.5
    Removing nix v0.24.3
      Adding num-conv v0.1.0
    Removing num-integer v0.1.46
    Removing num-rational v0.4.1
    Removing num_threads v0.1.6
    Updating object v0.31.1 -> v0.32.2
    Updating os_str_bytes v6.5.1 -> v6.6.1
    Updating petgraph v0.6.3 -> v0.6.4
    Updating pkg-config v0.3.29 -> v0.3.30
    Updating plist v1.5.1 -> v1.6.0
    Updating png v0.17.11 -> v0.17.13
      Adding polling v3.5.0
      Adding powerfmt v0.2.0
    Updating proptest v1.2.0 -> v1.4.0
      Adding quick-xml v0.31.0
    Updating raw-window-handle v0.5.0 -> v0.5.2
    Removing redox_syscall v0.3.5
    Updating regex v1.9.6 -> v1.10.3
    Updating regex-automata v0.3.9 -> v0.4.5
    Updating regex-syntax v0.7.5 -> v0.8.2
    Updating reqwest v0.11.18 -> v0.11.24
      Adding rustix v0.38.31
      Adding rustls-pemfile v1.0.4
    Updating ryu v1.0.16 -> v1.0.17
    Updating semver v1.0.21 -> v1.0.22
    Updating serde_json v1.0.97 -> v1.0.113
    Updating serde_spanned v0.6.1 -> v0.6.5
    Updating serde_with v3.0.0 -> v3.6.1
    Updating serde_with_macros v3.0.0 -> v3.6.1
    Removing signal-hook v0.3.17
      Adding socket2 v0.5.5
    Removing str-buf v1.0.6
    Updating syn v2.0.48 -> v2.0.49
      Adding sync_wrapper v0.1.2
      Adding system-configuration v0.5.1
      Adding system-configuration-sys v0.5.0
    Updating system-deps v6.1.1 -> v6.2.0
    Updating tar v0.4.39 -> v0.4.40
    Updating tempfile v3.6.0 -> v3.10.0
    Updating textwrap v0.16.0 -> v0.16.1
    Updating tiff v0.7.4 -> v0.9.1
    Updating time v0.3.15 -> v0.3.34
      Adding time-core v0.1.2
    Updating time-macros v0.2.4 -> v0.2.17
    Updating tokio v1.29.0 -> v1.36.0
    Updating tokio-macros v2.1.0 -> v2.2.0
    Removing toml v0.7.3
      Adding toml v0.7.8
      Adding toml v0.8.10
    Updating toml_datetime v0.6.1 -> v0.6.5
    Removing toml_edit v0.19.8
      Adding toml_edit v0.19.15
      Adding toml_edit v0.22.6
    Updating wasm-streams v0.2.3 -> v0.4.0
      Adding wayland-backend v0.3.3
    Updating wayland-client v0.29.5 -> v0.31.2
    Removing wayland-commons v0.29.5
    Updating wayland-protocols v0.29.5 -> v0.31.2
      Adding wayland-protocols-wlr v0.2.0
    Updating wayland-scanner v0.29.5 -> v0.31.1
    Updating wayland-sys v0.29.5 -> v0.31.1
    Removing winapi-wsapoll v0.1.1
      Adding windows-core v0.52.0
    Removing winnow v0.4.1
      Adding winnow v0.5.40
      Adding winnow v0.6.1
    Updating winreg v0.10.1 -> v0.50.0
    Updating wl-clipboard-rs v0.7.0 -> v0.8.0
    Updating x11rb v0.10.1 -> v0.13.0
    Updating x11rb-protocol v0.10.0 -> v0.13.0
    Updating xattr v0.2.3 -> v1.3.1
    Removing xml-rs v0.8.19
    Updating zbus v3.13.0 -> v3.15.0
    Updating zbus_macros v3.13.0 -> v3.15.0
    Updating zbus_names v2.5.0 -> v2.6.0
    Updating zvariant v3.13.0 -> v3.15.0
    Updating zvariant_derive v3.13.0 -> v3.15.0
    Updating zvariant_utils v1.0.0 -> v1.0.1

The same version works fine on Mac OS, but doesn't work on WSL2 running Ubuntu.

The current version of dev branch is targeting the v2-beta of tauri. Looking deeper I found the required dependency libwebkit2gtk-4.1-dev isn't available on Ubuntu 20.04 (which is the version I was running). After to run on Ubuntu 22.04, works pretty fine.
Maybe tauri v2 will not be compatible with Ubuntu 20.04 due the this dependency change.

Maybe tauri v2 will not be compatible with Ubuntu 20.04 due the this dependency change.

Correct. At least as long as we're using webkitgtk :)

authors: FabianLars lucascampelo


text:
Arch Linux package (AUR)

kerl is there, so why not kiex?

No one has written a package for it I guess. 🤷🏻
Would you like to contribute to the repo with a PR @radrow?

authors: radrow taylor

repo: taylor/kiex

license: mit

license_source: bigquery


text:
Update README.md

Fix CDN link

That change was in reference to the next version 7.0.0. Sorry the readme was changed before the release. It should be correct now.

authors: sergeyzharko taylorhakes

repo: taylorhakes/promise-polyfill


text:
memory issues with hetkmers.py

I run hetkmers.py on 1.3G genome, cca 30x.
The script allocated 750Gbp of memory at the point of generating the graph G. I killed the process in this moment.
The graph is very efficient implementation in terms on number of lines, but it does not scale well for bigger genomes. The computation was long, but not super long (2 days for the calculation of pairs distant exactly 1). Speeding up would be useful, but not necessary, the memory is issue here.
Any ideas @tbenavi1 ?

Fixed with b49d6bf939a821a07174eb13bb1285e00e154656. The code now converts kmers to ints as it loads, dramatically reducing the memory. It no longer requires pandas or networkx. It also uses multiple processes to speed up the analysis.


text:
🛑 RocketChat is down

In 8ac690a, RocketChat (https://rocket.etna.io) was down:

HTTP code: 0
Response time: 0 ms

Resolved: RocketChat is back up in eb55365.

repo: tbobm/etna-uptime


text:
Ability to import mid-season data, and then overwrite the same season data later on

This should just check for the season number/ID and update the stats for each player based on the player ID

This should work

repo: tbrittain/SmbExplorerCompanion


text:
Possible forward-compatibility issue in Intl.Locale.prototype.timeZones?

get Intl.Locale.prototype.timeZones is spec'ed to return IANA names, so if we ever extend Intl.Locale to support the "tz" Unicode extension, I have to assume that get Intl.Locale.prototype.timeZone will also return the resolved IANA name instead of the "tz" value. For example new Intl.Locale("en-u-tz-usnyc").timeZones will then return ["America/New_York"]. And following that line of thought, I assume new Intl.Locale("en-u-tz-usnyc").timeZone (so singular "timeZone") will then also return "America/New_York", to keep things consistent.
Do we expect that this will cause any issues for users who want to access the actual value "usnyc"?

I suggest one of the following:

timeZoneIds can return IANA names and is consistent with the .timeZoneId getter on Temporal objects

It return an Array - which is an object, therefore, it cannot be a getter. but a function. We have discussed this early this year. It must be a getXXX function. I do not think we should go back to rediscuss this again.

getTimeZones() could be a function returning upgraded Temporal.TimeZone instances

I think that should be done in a proposal which allow the Intl.DateTimeFormat to take Temporal.TimeZone as parameter for the timeZone option bag instead of in the Intl Locale Info API proposal.

I agree it would be nice to not take the name timeZones when there is a BCP-47 tag of the same name with different semantics

But Intl.DateTimeFormat constructor and Intl.DateTimeFormat.prototype.resolvedOptons() ALREADY take the name "timeZone" YEARS ago.

a BCP-47 tag of the same name with different semantics
This is not true. the name for BCP-47 tz name is "Short Identifier" not "Time Zone Identifier", as mentioned in the UTS 35.

timeZoneIds can return IANA names and is consistent with the .timeZoneId getter on Temporal objects

It return an Array - which is an object, therefore, it cannot be a getter. but a function. We have discussed this early this year. It must be a getXXX function. I do not think we should go back to rediscuss this again.

Makes sense. getTimeZoneIds() would be fine, assuming that the result is an array of IANA IDs and not CLDR short codes. I would not support getTimeZones() because it seems too similar with Temporal.ZonedDateTime's getTimeZone() method that returns a Temporal.TimeZone object.

I think that should be done in a proposal which allow the Intl.DateTimeFormat to take Temporal.TimeZone as parameter for the timeZone option bag instead of in the Intl Locale Info API proposal.

FWIW, this case is already supported, because if timeZone is an Object, then it's coerced to a String, which returns the id of the TimeZone. I guess there could be an improvement that adds a fast path to avoid the observable Get. But if the goal is simply to support TimeZone objects in DTF, then there's no action needed beyond the current spec.

+1 on getTimeZoneIds()
I think the precedent of the Intl.DateTimeFormat field called timeZone is not very strong because we are taking an approach that this option coerces its inputs to a better form, such as calling ToString on the Temporal.TimeZone type. However, this getter on Intl.Locale will only ever return exactly one format (IANA names as strings).

@anba what is your view about changing it to getTimeZoneIds() since you are the one who filed this issue.

I am not quite sure how would renaming this to getTimeZoneIds() will address the forward-compatibility issue @anba is filing about.
In that world, if one day we do support let loc = new Intl.Locale("en-u-tz-usnyc")
then
a. what getter will return "usnyc" ? and
b. what getter will return "America/New_York"?

Yeah, I'm convinced that if/when we add wupport for Unicode-style time zone IDs, we should give them a very clearly unique namespace, such as unicodeShortTimeZone or timeZoneBcp47Id or similar.

Agree, separate names seems like the way to go.

I'll note that this issue was opened by @anba (an implementer). There is also new information since this reached Stage 3, which is that Temporal only recently decided to go with timeZoneId.
I think the only real options are getTimeZones() and getTimeZoneIds(). They have pros and cons:

Advantages of getTimeZones():

Consistency with Intl.DateTimeFormat's timeZone option
Consistency with Intl.supportedValuesOf("timeZone")
Current state of the Stage 3 proposal

Advantages of getTimeZoneIds():

Consistency with Temporal
More clear that this function is returning time zone IDs, not Temporal.TimeZone objects
Leaves the getTimeZones() name open for future proposals

The point @anba made while filing this bug is not about getTimeZones vs getTimeZoneIds but how to deal with "tz" Unicode extension in the future and that issue exist regardless how we name this function between getTimeZones and getTimeZoneIds, right?

getTimeZoneIds() is consistent with timeZoneId in Temporal which is defined as an IANA time zone, leaving getTimeZones() open if we wanted to make it either BCP-47 or Temporal.TimeZone objects.
I think there's probably room for -u-tz to change the content of the returned list like we do for Collations and Calendars and others.

@anba what is your view about changing it to getTimeZoneIds() since you are the one who filed this issue.

Changing getTimeZones() to getTimeZoneIds() based on Temporal kind of ignores Intl.Locale.prototype.getCalendars() and calendarId in Temporal.
The following advantages for getTimeZoneIds() were mentioned:

It's consistent with timeZoneId in Temporal and allows to add Intl.Locale.prototype.getTimeZones() which returns an array of Temporal.TimeZone objects. (https://github.com/tc39/proposal-intl-locale-info/issues/73#issuecomment-1629379836)
getTimeZones() is too similar to Temporal.ZonedDateTime.prototype.getTimeZone(). (https://github.com/tc39/proposal-intl-locale-info/issues/73#issuecomment-1629596052)

But these points all also apply to Intl.Locale.prototype.getCalendars(). (The only difference is that we already have Intl.Locale.prototype.calendar, which returns a String value.)

We discussed this in 2023-09-07 TG2, and attendees supprt keeping the current spec text with getTimeZones() and getCalendars() without changing it to Ids() suffix.

TG2 notes: https://github.com/tc39/ecma402/blob/master/meetings/notes-2023-09-07.md#possible-forward-compatibility-issue-in-intllocaleprototypegettimezones-73

authors: FrankYFTang anba justingrant sffc


text:
Update README.md

As far as I see the A-Index is the value from the predicted fredricksburg a-index.

Yeah, the a-index points to the "/json/predicted_fredericksburg_a_index.json" endpoint. I agree with this change in documentation and am happy to make it.
If there's a better endpoint to point a-index at let me know, I can also make that change and add an endpoint for predicted fredericksburg like pred_a_fred ... 3d ... etc.


text:
info_trivial has been fixed?

README.md says "(currently info_trivial is broken)" but it appears that it has been fixed. Should we remove that note?

Just removed the note, thanks for pointing that out!

authors: anton-trunov tchajed

repo: tchajed/coq-tricks


text:
🛑 Hayward Community Garden Forums is down

In 132734f, Hayward Community Garden Forums (https://forums.haywardcommunitygarden.org/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Hayward Community Garden Forums is back up in 42a3217.


text:
Fix broken link to Rust homepage.

Unfortunately, the site requires 'www' with HTTPS at the moment.

Ah, I see. LGTM! :+1:

authors: frewsxcv tdfischer

repo: tdfischer/pto


text:
Reduce compiled tdlib size

I've noticed that the libtdjni.so lib compiled in my Android Studio project is slightly bigger than the prebuilt/TGX one (4MB less). Is there any way to optimize even more my build? Here's the CMake flags I'm currently using (took from Issue #77):
string(APPEND CMAKE_CXX_FLAGS "-std=c++14 -fno-omit-frame-pointer -ffunction-sections -fdata-sections -fno-exceptions -fno-rtti")
string(APPEND CMAKE_SHARED_LINKER_FLAGS "-Wl,--gc-sections -Wl,--exclude-libs,ALL")
# ...
add_custom_command(TARGET tdjni POST_BUILD
  COMMAND ${CMAKE_STRIP} --strip-debug --strip-unneeded $<TARGET_FILE:tdjni>)

build.gradle:
externalNativeBuild {
    cmake {
        version '3.18.1'
        targets "tdjni"
        arguments '-DCMAKE_BUILD_TYPE=MinSizeRel'
    }
}

You need to use
string(APPEND CMAKE_CXX_FLAGS_RELWITHDEBINFO " -flto=thin -Oz")

Also, the prebuilt version links libc++ dynamically, so it still be slighly less even after the change, but the total size of libtdjni and libc++ should be bigger after that.

These flags had no effect unfortunately, I've also just noticed this warning during the build
> Task :app:stripDebugDebugSymbols
Unable to strip the following libraries, packaging them as they are: libtdjni.so.

CMakeOutput.log
CMakeError.log
The warning won't appear with no CMAKE flags+custom strip command set in the CMakeLists file

So I managed to fix the app:stripDebugDebugSymbols error, for some strange reason I also had to add ndkVersion in my app module. unfortunately the two new flags you suggested still have no effect.

Could you recheck that the flags are appended to CMAKE_CXX_FLAGS_MINSIZEREL? I don't see them in CMake logs.

I can see those flags in these files:
build.ninja
compile_commands.json
I noticed that the flags that actually shrink the lib are the SHARED_LINKER ones, CMAKE_CXX_FLAGS have no effect on the lib size. By adding ndkVersion in the app module I could remove the strip custom_command in CMake since it is now done at compile time via gradle with app:stripDebugDebugSymbols

No, the output confirms that there are was no flags added.  You need to add the line string(APPEND CMAKE_CXX_FLAGS_RELWITHDEBINFO " -flto=thin -Oz") before add_subdirectory(td).

You meant CMAKE_CXX_FLAGS_MINSIZEREL right? I've moved the MinSizeRel flags before the add_subdirectory(td) and now the lib size has finally been reduced. Thank you again for your help, hoping I won't be bothering you again like I already did😅

repo: tdlib/td


text:
how to imitate method messages.getDialogs using tdlib?

Hi, I'm new to tdlib and wondering how to get the same result as using method messages.getDialogs
I'm interested in online user information especialy actual online status UserStatus
I tried getChats + getChat but I get stale information...
Thanks!

See https://core.telegram.org/tdlib/getting-started for the way to fetch chat list.
You can't fetch a user's status from the server using TDLib. It is updated whenever appropriate.

I got desired data by listening to UpdateUserStatus event, thanks for hint!
    clientBuilder.addUpdateHandler(TdApi.UpdateUserStatus.class, this::onUpdateNewMessage);
    //
    private void onUpdateNewMessage(TdApi.UpdateUserStatus update) {
        logger.info("{}: {}", update.userId, update.status);
    }

(I'm using tdlight-java version 3.3.1+td.1.8.25)


text:
thumbnail seems not to work with inputMessageDocument

I got problems to set a thumbnail for inputMessageDocument. I'm really not sure what I'm doing wrong. Thats how my json looks like:
{                   '@type': 'sendMessage',
                    'chat_id': chat_id,
                    'input_message_content': {
                        '@type': 'inputMessageDocument',
                        'document': {'@type': 'inputFileLocal', 'path': path},
                        'thumbnail': {'@type':'inputThumbnail', 'thumbnail': {'@type': 'inputFileLocal', 'path': thumbnail_path}, 'width':103, 'height':73},
                        'caption': {'@type':'formattedText', 'text':text}
                    }}

The path var seems to be right because otherwise I would get an error from tdlib, but I don't get any.
The image I use as thumb:
JPG | size: 8,9KB | width: 103 | height: 73
Like I said I don't get any errors and the file is sent successfully but there is no thumbnail set.

If thumbnail fails to load, the file will be still send successfully without thumbnail. You can find what has happened in the TDLib's log.

authors: MalteToenjes levlam


text:
amazon2csv.py unable to generate output.csv with data extracting from Amazon

Hi author/ tducret,
I download all your files and attempted to run python setup.py install. Next, i  tried running amazon2csv.py followed your instruction steps found in https://github.com/tducret/amazon-scraper-python which says " You can also pass a search url (if you added complex filters for example), and save it to a file ".
However, on Windows command prompt windows session when i run this command   "  amazon2csv.py --url="https://www.amazon.com/s/ref=nb_sb_noss_2?url=search-alias%3Daps&field-keywords=python+scraping" > output.csv ", my output.csv file is generated however there's no data found inside the output.csv file.  Any advise what steps have i missed out which resulted to the output.csv file being empty (ie: no data extracting from url = https://www.amazon.com/s/ref=nb_sb_noss_2?url=search-alias%3Daps&field-keywords=python+scraping" ) ?
See below screenshot as a proof / reference

Hi @clementks
Sorry about that, but Amazon is definitely stronger than me. It's very hard to keep pace with their anti-scraping protections.
I'd really appreciate if somebody wanted to update the code though.

Hi tducret,
Thanks for your advice/response, in other words, u are implying that your amazon scraping program upon you upload to github, back then it works fine and able to export into csv file.
Pardon me as i'm not proficient in OO in Python, may i ask you if i were to perform web scrapping on another website (ie: https://www.walmart.com/), what product attributes does it need/require so that i can get your advice on what  to modify init.py, client.py etc ? I learnt a great deal on OO in Python from your program, which i would like to use it for my other project development. Hence, thanks a lot for your sharing by uploading into github

authors: clementks tducret

repo: tducret/amazon-scraper-python


text:
Use term name as label name

We currently use the local name of a term (e.g. in the quick reference guide, such as scientificNameAuthorship), which is a bit of a weird concept. It would be better to use the label, which is a concept that is part of the standard. The current labels use spaces (e.g. Scientific Name Authorship), which was a 2011 decision:

The label for all terms have been changed to words in English rather than lower camel case term names. This will facilitate discovery with search engines and is consistent with Dublin Core.

In my experience, those labels are not used for Darwin Core (they are also not in the quick reference guide). People refer to terms by their local name, which are also in English. I therefore propose to update the labels to what is currently the local name and start using the labels. If someone still wants a space separated version, that is fairly easy to generate.
In this pull request I have update the label column with the last element of the term_iri, e.g.:
http://rs.tdwg.org/dwc/terms/associatedReferences -> label: associatedReferences
Note 1
I kept the capitalization of the IRI. For some terms this has changed over time, e.g.:

Class: http://digir.net/schema/conceptual/darwin/2003/1.0/Class (superseded)
Class: http://digir.net/schema/conceptual/darwin/2003/1.0/Class (deprecated)
Class: http://rs.tdwg.org/dwc/dwcore/Class (deprecated)
class: http://rs.tdwg.org/dwc/terms/class (superseded)
class: http://rs.tdwg.org/dwc/terms/class (recommended)

Note 2
This transformation didn't change any label names (except for removing spaces and different capitalization) except for:

old label
new label
term_iri

Darwin Core Type
DwCType
http://rs.tdwg.org/dwc/terms/DwCType

Event Attribute
EventAttributeValue
http://rs.tdwg.org/dwc/terms/EventAttributeValue

Sample Attribute ID
SamplingAttributeID
http://rs.tdwg.org/dwc/terms/SamplingAttributeID

Sample Attribute Type
SamplingAttributeType
http://rs.tdwg.org/dwc/terms/SamplingAttributeType

But I think all of these are correct updates.

What we are proposing to do here is to change the metadata of the terms (that is, the terms as a continuing entity).  Any time you change the metadata of a term, you are generating a new version of that term.  So we should not be changing the labels of term versions issued in 2009 or 2015.  We should be generating new term versions that have an issued date of 2017-10-02.  For example:
Existing line:
Country Code,2009-04-24,recommended,http://rs.tdwg.org/dwc/terms/countryCode,http://rs.tdwg.org/dwc/terms/version/countryCode-2009-04-24,,http://www.w3.org/1999/02/22-rdf-syntax-ns#Property,The standard code for the country in which the Location occurs.
Added line:
countryCode,2017-10-02,recommended,http://rs.tdwg.org/dwc/terms/countryCode,http://rs.tdwg.org/dwc/terms/version/countryCode-2017-10-02,,http://www.w3.org/1999/02/22-rdf-syntax-ns#Property,The standard code for the country in which the Location occurs.
We should never change any existing line in the table - only add lines.  Otherwise we are changing history.

Oh, and we should only be doing this for terms whose most recent versions have the status "recommended" (the other versions are dead and can't change).  Actually, this also changes the status of the previously recommended version to "superseded", so the changed existing line and the new line should look like this:
Country Code,2009-04-24,superseded,http://rs.tdwg.org/dwc/terms/countryCode,http://rs.tdwg.org/dwc/terms/version/countryCode-2009-04-24,,http://www.w3.org/1999/02/22-rdf-syntax-ns#Property,The standard code for the country in which the Location occurs.
countryCode,2017-10-02,recommended,http://rs.tdwg.org/dwc/terms/countryCode,http://rs.tdwg.org/dwc/terms/version/countryCode-2017-10-02,,http://www.w3.org/1999/02/22-rdf-syntax-ns#Property,The standard code for the country in which the Location occurs.
So what I said before wasn't exactly true.  You can change a preciously existing term version in one way: changing its status from "recommended" to "superseded".

Fair enough, I can implement it that way. Any feedback on the proposed change?

Good catch, Steve. Since there are a large number of changes where the
recommendations got pulled out and into comments, which are no longer in
the term metadata, it's not a bad idea to go ahead and use the opportunity
to change all terms (because of the label change).
With the term local name as the preferred label, we solve having a metadata
element that gives us a standard field name (column header, etc.) and begs
that english labels go with labels in every other language. That seems like
a good thing to me.
On Mon, Oct 2, 2017 at 1:57 PM, Peter Desmet notifications@github.com
wrote:

Fair enough, I can implement it that way. Any feedback on the proposed
change?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/tdwg/dwc/pull/156#issuecomment-333662815, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAcP6-L532qv46fMCET9MlQKctZEYZ8Sks5soU4wgaJpZM4PrGGm
.

We need to do this differently and will make a new pull request.

authors: baskaufs peterdesmet tucotuco

repo: tdwg/dwc


text:
Make properties for the font of the title available

The documentation mentions the following font related properties:

fontsize
fontcolor
fontfamily
fontstyle

Necessary code for the html string :
title: {
        fontFamily: 'Algerian',
	fontSize: 16 ,
	fontColor: 'rgb(255, 99, 132)',
	fontStyle: 'italic bold'
},

Released with version 2.21.05

repo: team-moeller/better-access-charts


text:
Club portal

Added menu section modified some features in the body section added some files

Noted with thanks
On Sat, Nov 13, 2021 at 9:01 PM Chalie Wizz @.***>
wrote:

@.**** requested changes on this pull request.
Kindly follow the folder structure, firebase won't detect anything outside
the public folder.
Place all your images inside "public/img" and maybe you can create sub
folders in there according to the respective HTML files where the images
are to be displayed,
do the same for the css files, place all your CSS files inside
"public/css".
Make sure you also check on the naming convention, if a css file belongs
to display.html, it should be named display.css, the same case applies to
js if you'll use an external file.
If a js file belongs to display.html, name it display.js and place it
inside the "pu
blic/js" folder.
For the images, to avoid name conflicts, you can place them in sub-folders
inside the img folder, for instance, if you have images that should be
displayed on the display.html file, place them in "public/img/display" that
will make the work clean and leave no room for errors and image naming
conflicts.
Please take your time to work on the changes, otherwise, you've done an
impressive job, keep it up.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/teau-ict-club/club-website/pull/23#pullrequestreview-805390428,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AL7PZ5PHFSRCSF6L4C5NEIDUL2RX7ANCNFSM5H3LPYZQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

repo: teau-ict-club/club-website


text:
Integrated TransformContext

Add new Canvas component (derived from LayerCake) which handles scaleCanvas() globally and supports scale/translate transforms
[GeoPath] Respect strokeWidth prop within Svg context (not just stroke-width attribute) to align with Canvas context usage
Integrate Transform into Chart () and expose as transformContext(). Renamed to TransformContext and removed direct SVG control (now handled by Svg and Canvas components)

#166  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @techniq and the rest of your teammates on  Graphite

repo: techniq/layerchart


text:
Build process and output

Need to rethink the build process and output.

I had an idea for this that I would be happy to PR!
One of the thoughts I had was the use the Handlebar's templating library to make the template more dynamic. So instead of manually specifying each button, it could render every type of button using just this:
{{#each people}}
    {{this.text}}

{{/each}}

Then you could pass in an array of values that looks something like:
[
    {
        id: "github",
        link: "https://github.com/",
        alt: "GitHub Logo"
    },
    {
        id: "my_custom_website",
        link: "https://somewhere.com",
        alt: "Website Logo",
        imageLink: "https://cdn.com/img.png"
    }
]

My thought is that the express file can compile the handlebars code and output it to index.html just as it is doing now!
Thoughts?

Hey, thank you!  This issues was to address the js build step, but happy to discuss your feature here.  I like this!  I am thinking about making to change to how this works (a v2 really) and will ping you when it's ready so that you can open a PR against that!  Thank you!

Hey, thank you!  This issues was to address the js build step, but happy to discuss your feature here.  I like this!  I am thinking about making to change to how this works (a v2 really) and will ping you when it's ready so that you can open a PR against that!  Thank you!

Sounds good!
There's lots of options depending on how simple/complex you want it to be to be honest.
The same thing can be done in a similar fashion in React which I think I saw you mention?
Either way, happy to help where I can, just drop me a ping 😄

repo: techno-tim/littlelink-server


text:
package needs a function to post prediction model result to other service

currently planned as a Redis in memory DB that handles all the RW to the DB

Possible package https://github.com/richfitz/redux

repo: technologiestiftung/fhpredict


text:
RuntimeError: CUDA error: invalid device function

Hi there, thank you very much for this library- it has worked great for one of the problems I've encountered in research, at least on CPU. Now I am trying to get it to run on GPU; I have installed it from a git clone of this library and then python setup.py install. However, I'm running into this stack trace. Like others, I've tried to use the spearmanr example from the main README.md.
I tried to look for other closed issues involving this to see if anyone else had run into it, but I haven't found any (or maybe I missed them?)
     34 def spearmanr(pred, target, **kw):
---> 35     pred = torchsort.soft_rank(pred, **kw)
     36     target = torchsort.soft_rank(target, **kw)
     37     pred = pred - pred.mean()

~/envs/pytorch1938/lib/python3.8/site-packages/torchsort-0.1.5-py3.8-linux-x86_64.egg/torchsort/ops.py in soft_rank(values, regularization, regularization_strength)
     38     if regularization not in ["l2", "kl"]:
     39         raise ValueError(f"'regularization' should be a 'l2' or 'kl'")
---> 40     return SoftRank.apply(values, regularization, regularization_strength)
     41
     42

~/envs/pytorch1938/lib/python3.8/site-packages/torchsort-0.1.5-py3.8-linux-x86_64.egg/torchsort/ops.py in forward(ctx, tensor, regularization, regularization_strength)
     94         if ctx.regularization == "l2":
     95             dual_sol = isotonic_l2[s.device.type](s - w)
---> 96             ret = (s - dual_sol).gather(1, inv_permutation)
     97             factor = torch.tensor(1.0, device=s.device)
     98         else:

RuntimeError: CUDA error: invalid device function
CUDA kernel errors might be asynchronously reported at some other API call,so the stacktrace below might be incorrect.
For debugging consider passing CUDA_LAUNCH_BLOCKING=1.

Here is my system information:
$ uname -a
Linux xxx.xxx.ucl.ac.uk 4.15.0-143-generic #147-Ubuntu SMP Wed Apr 14 16:10:11 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Here is my Python information (I am running anaconda - so this is an excerpt from conda info)
         python version : 3.8.10.final.0
       virtual packages : __cuda=11.2=0
                          __linux=4.15.0=0
                          __glibc=2.27=0
                          __unix=0=0
                          __archspec=1=x86_64

Many thanks!

I've sorted myself out- It was because:
The version of nvcc on the machine I built, was cuda 10.0. The driver was 11.2
In case anyone else runs into this, all that was required was to upgrade the nvcc (by installing cuda 11.2 toolkit, to match the cuda 11.2 driver), and do the following
python setup.py clean --all
python setup.py install

Hi @rekcahpassyla, glad you got this sorted out! Thanks for sharing your solution :)

authors: rekcahpassyla teddykoker

repo: teddykoker/torchsort


text:
encode() confuses the data being hashed, with the hash digest

The multihash.encode() function takes a parameter digest at first it's treated as data to hashed (hashfn.update(digest) is called). However immediately after that len(digest) is used as the length to encode in the multihash - rather than len(hashfn.digest()).
The appearance of encoded = encode('testing', SHA1) in the docstring suggests the function takes data, rather than an existing hash digest. Is this the case?

I have a PR in progress for this and #2

repo: tehmaze/python-multihash


text:
Missing .env File: Defined in pubspec.yaml but Not Found in Repository

The .env file defined under flutter -> assets in pubspec.yaml appears to be missing from the repository. Is it necessary to create this file manually?
..........

flutter:
  uses-material-design: true
  assets:
    - .env

..........

yes, this file should contain your open weather map API key.
just create a .env file at the root of your project and assign your api key to API_KEY.
it should look something like this -
API_KEY=

Thank you very much for your reply.

repo: tejasbadone/EasyWeather


text:
Scope remote_desktop_client.xml to non-main window

This is a proposed enhancement for #632
I didn't test other remote desktops apps, only Microsoft Remote Desktop.
It should not do any harm for users of other rdp clients: window name would be different.
Potentially, other REMOTEDESKTOPCONNECTION (and maybe VIRTUALMACHINE) can benefit from it with including their own Main window in Remote_Desktop_Main_Window .

I think this issue is solved by <bundleidentifieroverridedef> since Karabiner 10.18.7.
https://github.com/tekezo/Karabiner/issues/632#issuecomment-219480124
Please confirm the latest beta version.

Great!

authors: tekezo vors

repo: tekezo/Karabiner

license: unlicense


text:
Warning You may reach API Hard limit

This app iterate over all files under specified directory path to create following output
Code Review:
Positive Points:
- The code is well-structured and easy to read.
- All the properties are declared with the appropriate data type.
- The code is using the latest version of .NET (EF Core).
- All the properties are declared with nullable reference types (NRTs).

Improvement Areas:
- The code could be improved by adding more comments to explain the purpose of each property and its usage.
- The code could be improved by using more descriptive names for the properties and variables.

Positive Points:

- The code is well organized and easy to read.
- The code is using System, so all the necessary components are included.
- The code is using nullable reference types, which will help ensure that data is not lost due to null values.
- The code is using partial classes, which allows for easier maintenance and scalability.
- The code is using meaningful variable names, which will help with readability.

Improvement Areas:

- The code could be improved by using more descriptive comments to explain the purpose of each line of code.
- The code could be improved by adding more validation checks to ensure that data is not lost due to incorrect input.
- The code could be improved by adding more logging to track changes and errors.

if there are lot of files you will quickly end up burning many API calls, essentially may also hit API usage hard limit. So be very careful.

Hi Yash, to manage it flexibility is provided in the code to provide the custom path as parameter ".\codeanalyser.ai  ".
Also provision to exclude files in appsettings.json which are not required.

we don't want to put any restriction from our end for the user on number of files they want to analyze.  User can take a decision which files they want to analyze and which one to skip.

authors: tekspry yashodhank

repo: tekspry/openai-code-analyser


text:
Adding tektoncd wide default SECURITY.md

Add a default SECURITY.md with instruction regarding how to report
security issues safely.
Signed-off-by: Andrea Frittoli andrea.frittoli@gmail.com

Thanks @afrittoli looks great to me. 3 working days feels like a reasonable timeline - i assume that between all of us we can make sure someone is always available. i wonder if we want to do a bit more coordination to make sure that's the case, just in case we all go on holidays at once or something? (or maybe the build captain can be part of it somehow 🤔 )

Note that you don't need to restrict the vulnerability management/reporting to just the governing board. It should be a relatively small list of people from different organizations, but feel free to solicit help from others.
I'd be happy to help out here, for example :)

Note that you don't need to restrict the vulnerability management/reporting to just the governing board. It should be a relatively small list of people from different organizations, but feel free to solicit help from others.
I'd be happy to help out here, for example :)

Thanks @dlorenc 🎉
This wasn't meant to be restricted to the GB members, it was just an initial list to get started.
I'll add you to the DL.

Thanks @afrittoli looks great to me. 3 working days feels like a reasonable timeline - i assume that between all of us we can make sure someone is always available. i wonder if we want to do a bit more coordination to make sure that's the case, just in case we all go on holidays at once or something? (or maybe the build captain can be part of it somehow 🤔 )

@bobcatfish That's a good point. I think the most important part of this is to let people know how to report vulnerabilities, perhaps we don't need to commit to the 3 days; I think the wording allows for a "we're looking into this" kind of reply still, that could be used in case 3 days are not enough to decide whether an issue is considered a security vulnerability by the Tekton SVM team.
+1 we'll need some way to coordinate. I'd suggest we can use the DL to let other know if someone is looking into an issue or to ask for help. GithHub provides tooling to discuss and work on private patches which is a great help: https://docs.github.com/en/code-security/security-advisories/about-github-security-advisories

authors: afrittoli bobcatfish dlorenc


text:
Feature flags to trim tekton results EOF newlines

Feature request
Related https://github.com/tektoncd/pipeline/issues/2936
Some of our users have pre-defined container that doesn't trim the outputs. It is quite troublesome to ask everyone to fix and rebuild their container especially when we are building a pipeline that's depended on each other's work. Is it possible to add a feature flag for Tekton to handle it? Thank you in advance.
Here is an example to reproduce this:
apiVersion: tekton.dev/v1beta1
kind: PipelineRun
metadata:
  name: test-params
spec:
  params:
  - name: project_name
    value: 'a-project'
  - name: notebook_name
    value: 'a-notebook'
  pipelineSpec:
    params:
    - name: project_name
    - name: notebook_name
    tasks:
    - name: find-project
      params:
      - name: project_name
        value: $(params.project_name)
      taskSpec:
        params:
        - name: project_name
        results:
        - description: /tmp/outputs/project/data
          name: project
        steps:
        - command:
          - sh
          - -ex
          - -c
          - "echo \"$0\" > \"$1\""
          - $(inputs.params.project_name)
          - $(results.project.path)
          image: alpine:3.12
          name: main
    - name: find-asset
      params:
      - name: find-project-project
        value: $(tasks.find-project.results.project)
      - name: notebook_name
        value: $(params.notebook_name)
      taskSpec:
        params:
        - name: find-project-project
        - name: notebook_name
        steps:
        - command:
          - sh
          - -ex
          - -c
          - "echo \"'$0'\"\n echo \"'$1'\""
          - $(inputs.params.find-project-project)
          - $(inputs.params.notebook_name)
          image: alpine:3.12
          name: main

Tracking issue on our repo: https://github.com/kubeflow/kfp-tekton/issues/273
/cc @pritidesai @animeshsingh

Use case

Thanks for the issue report.  This has also recently come up in the context of stdout / stderr capture (comment thread here).
I agree I think this would be useful.  Here's the way it might work:
# in a TaskSpec
results:
- name: my-result
  description: Foo bar result description.
  trimWhitespace: true

I hesitate to add yet more flags to the entrypoint binary so I think right now my preference would be that the Tekton Controller is responsible for performing the trimming after the result is sent back to it but that's an implementation detail.  I'll write a TEP for it.

Has anybody taken this one? If not, I'm interested in working on it :)
/assign @XinruZhang

In summary the feedback on this feature's TEP boiled down to the fact that working around this problem is quite easy for users. Removing trailing spaces can be done in the Task directly or by adding a Task to their pipeline to perform string trimming.  Therefore it doesn't seem like this is a feature the Pipelines project should pursue.  That doesn't preclude this being something the Pipelines project takes on in future when a clear need presents itself that users are unable to work around, but right now we don't see evidence of that kind of problem.
/close

authors: Tomcli XinruZhang sbwsg

repo: tektoncd/pipeline


text:
Test refactor: separate Task validation tests for propagation

To support propagated parameters in inline Task specs, validation of variable usage is skipped for inline Task specs and performed only for referenced Tasks. This commit refactors TestTaskSpecValidateError to split out the test cases which rely on this validation logic from test cases that rely on validation logic that is always performed. Since validation logic for usage of declared variables should always be performed when a Task is created directly (but not always for a Task spec), it updates these tests to validate a Task rather than a Task spec. This refactoring will make cleanup for propagated parameters easier. No functional changes.
/kind cleanup
Partially addresses https://github.com/tektoncd/pipeline/issues/6647
Submitter Checklist
As the author of this PR, please check off the items in this checklist:

n/a Has Docs if any changes are user facing, including updates to minimum requirements e.g. Kubernetes version bumps
[x] Has Tests included if any functionality added or changed
[x] Follows the commit message standard
[x] Meets the Tekton contributor standards (including functionality, content, code)
[x] Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
n/a Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings). See some examples of good release notes.
n/a Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes
NONE

/retest


text:
cluster-reslover: add support for StepAction

Changes
This adds support for StepAction in the cluster resolver.
Signed-off-by: Vincent Demeester vdemeest@redhat.com
/kind feature
/wip

[ ] Needs updated docs
[ ] Needs some unit tests

Submitter Checklist
As the author of this PR, please check off the items in this checklist:

[ ] Has Docs if any changes are user facing, including updates to minimum requirements e.g. Kubernetes version bumps
[ ] Has Tests included if any functionality added or changed
[x] pre-commit Passed
[x] Follows the commit message standard
[x] Meets the Tekton contributor standards (including functionality, content, code)
[x] Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
[x] Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings). See some examples of good release notes.
[ ] Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes
StepAction are now supported to a refered via the cluster resolver.

/retest

authors: chitrangpatel vdemeester


text:
chore(package): update tap to version 10.1.2

Closes #86
https://greenkeeper.io/

Coverage remained the same at 100.0% when pulling 46d692b34e9a350dbb900761324ecbb047e8e376 on greenkeeper/tap-10.1.2 into f99888eb649d1369fffab85a09de2788a6da6405 on master.

authors: coveralls cybermelmac

repo: telemark/roy


text:
Create SoC Zephyr Skeleton for TL321x

Add new SoC Telink TLx (telink_tlx) based on Telink B9x (telink_b9x).
Add new board tl3218x based on tlsr9528a.
Add Zephyr driver and DTS files for TLx SoC.
Add tl3218x.conf and tl3218x.overlay in ot-cli samples to apply uart.
Update hal_telink to match tl321x driver skeleton.

Known issue: usb driver does not work.

The following west manifest projects have been modified in this Pull Request:

Name
Old Revision
New Revision
Diff

hal_telink
https://github.com/telink-semi/hal_telink/commit/36283106d9b0b1d5fb3025a98be5a58007ac3d77 (develop,telink_tl321x)
https://github.com/telink-semi/hal_telink/commit/17c4cedd1038aec6f432cf76357d477e1c5d7672 (tl321x_skeleton)
telink-semi/hal_telink@36283106..17c4cedd

Note: This message is automatically posted and updated by the Manifest GitHub Action.

@s07641069
Could you take a quick look and see if there is any improvement needed?
Andy

Adopt pinctrl and uart driver
- update pinctrl driver.
- update uart driver to enable serial output.

repo: telink-semi/zephyr


text:
Staker Status for Dataserver is provided to all connected Miners

When you set up a separate dataserver and specify a public/private key, the status of that public address is provided for all the miners connected to the datasever.
https://github.com/tellor-io/telliot/blob/13ab4c229e8a8f2f5b50bd8a400e5569e994e248/cmd/telliot/main.go#L297
It looks like the disputeKey is only set for the 1 public address that the data server is using. So, other miners with different public addresses are dependant on the data server's public address being staked.

Thanks for the report, can you also add steps to reproduce so we can replicate easier.

Make a datasever with a unstaked miner public address
Make a miner with a staked miner public address connected to the dataserver

Expected: miner starts up and dataserver serves it
Actual: miner never starts up because dataserver public address is unstaked

authors: krasi-georgiev mikeghen

repo: tellor-io/telliot


text:
Meeting participant shall select layout

Participants that don't register any modules must select which layout they will join.

Implemented in release 1.6.0.


text:
EPG Update

telly release with the issue:

Last working telly release (if known):
Operating environment (Docker/Windows/Linux/QNAP, etc.):

Description of problem:
EPG doesn't update automattacly in Plex. I'm not sure if this is a telly or Plex issue. I have telly update the EPG and it didn't pull anything. I restarted telly which redownload the epg from the provider then stuff showed up. Should I just have telly reboot every night to download the new EPG?
Contents of telly.config.toml [if you're using a version above 1.1]:

REMEMBER TO DELETE ANY CREDENTIALS IN CONFIG FILES OR COMMAND LINES

Command line used to run telly [if applicable]:

REMEMBER TO DELETE ANY CREDENTIALS IN CONFIG FILES OR COMMAND LINES

Docker run command used to run telly [if applicable]:

REMEMBER TO DELETE ANY CREDENTIALS IN CONFIG FILES OR COMMAND LINES

telly or docker log:

Additional information:

Closing since this seems to be sorted.

repo: tellytv/telly


text:
🛑 QRCODE VIEWER is down

In 4f5d55f, QRCODE VIEWER (https://qrcode-viewer.onrender.com/qrcode-viewer/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: QRCODE VIEWER is back up in 8f8cf93 after 13 minutes.

repo: templain/mywatcher


text:
修复创建会话后类型不提示的问题

解决DirectMessageGuild特性不会提示问题

是的，因为创建私信会话的类型提示丢失了
---Original---
From: @.>
Date: Mon, May 9, 2022 20:55 PM
To: @.>;
Cc: @.@.>;
Subject: Re: [tencent-connect/botpy] 修复创建会话后类型不提示的问题 (PR #62)
这个pr的目的是主要增加一个参数类型注释吗？
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

repo: tencent-connect/botpy


text:
Enable installation through brew on macOS

Fix the installation steps in here: https://github.com/tendermint/homebrew-tendermint

Does this belong to this repo? Or the other repo? Sounds like a job for Greg :)

close? there are recent updates to the tap in the homebrew repo

authors: adrianbrink ethanfrey zramsay

repo: tendermint/basecoin


text:
🛑 Beeldoverleg Website is down

In 7579ea2, Beeldoverleg Website (https://beeldoverleg.nl) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Beeldoverleg Website is back up in b0b8988 after 6 minutes.

repo: tendsgn/upptime


text:
2019-12-20 Typo in error message for aurc_all

As of 5ca1f6efa4 the error messages for the aurc_all function give messages with "Error in aucr_all: instead of aurc_all. This appears to affect all instances of the phrase aurc_all in the aurc_all.R file.

This issue was addressed in e681d9c.

repo: tensfeldt/openNCA


text:
[ar] How to show the titles in Arabic for already translated tutorials in the side navigation menu?

When I choose the Arabic language, for a given tutorial, like this one: https://www.tensorflow.org/tutorials/keras/classification?hl=ar, I was expecting to see the title of this already translated tutorial in Arabic in the right side navigation menu, but it's showing in English as you can see in the following picture:

Showing the translated tutorials' title in Arabic for already translated tutorial can be useful to reader as a visual identification of what is already in Arabic.
@lamberta
Could you explain whether it's something I can configure myself with a PR or it requires extra development?
Thanks.

Hi @mohamed-ali
The site navigation is displayed using YAML files, for example, here's the English source for the tutorials: site/en/tutorials/_toc.yaml.
Unfortunately, these are out-of-scope for community translations. In the past we've allowed this, but they quickly fall out of sync with the source material—and the cost is very high, since users will miss entire documents (sometimes sections). These were added to the Do not translate list.
Some languages on tensorflow.org are "officially" supported, meaning we use an internal process to translate the navigation. But, at this time, Arabic is still "unofficial" and not part of this internal process. Occasionally new languages are added to the "official" list, but that depends on a number of things. Will keep Arabic in mind, though, especially as the ML community grows.

authors: lamberta mohamed-ali


text:
Fixed assertion error during tfds subsplit()

The line "splits = tfds.Split.ALL.subsplit(weighted=(80, 10, 10))" was causing "**AssertionError: Unrecognized instruction format: NamedSplitAll()(tfds.percent[0:80])**" during tfds.load().
Issue is fixed by using "split=['train[:80%]', 'train[80%:90%]', 'train[90%:]"

@googlebot I signed it!

Thanks @jintolonappan,
It looks like your editor changed the notebook formatting. Can you run the tensorflow/docs nbfmt script on it? That makes the history cleaner, and makes everything easier to review.
https://raw.githubusercontent.com/tensorflow/docs/master/tools/nbfmt.py
$ curl https://raw.githubusercontent.com/tensorflow/docs/master/tools/nbfmt.py
$ python nbfmt tflite_c04_exercise_convert_model_to_tflite_solution.ipynb
$ git add tflite_c04_exercise_convert_model_to_tflite_solution.ipynb
$ git commit -m "nbfmt"

Thanks @jintolonappan,
It looks like your editor changed the notebook formatting. Can you run the tensorflow/docs nbfmt script on it? That makes the history cleaner, and makes everything easier to review.
https://raw.githubusercontent.com/tensorflow/docs/master/tools/nbfmt.py
$ curl https://raw.githubusercontent.com/tensorflow/docs/master/tools/nbfmt.py
$ python nbfmt tflite_c04_exercise_convert_model_to_tflite_solution.ipynb
$ git add tflite_c04_exercise_convert_model_to_tflite_solution.ipynb
$ git commit -m "nbfmt"

Thanks for the feedback. I fixed it.

authors: MarkDaoust jintolonappan

repo: tensorflow/examples


text:
CoLab MusicVAE 16 Mel Seq Reconstruction issue

Hi Adam
I am sorry to be a pain...
In the 16-bar Melody Models, the extracted melodies would not be converted into the start or end seq reconstruction. (I tried print start_mel out and it won't match ns from the last cell) It is fine in the 2 bar mode. Thanks very much. I uploaded a video to youtube to demonstrate.
https://youtu.be/-K9CcmfkxYU

This is simply a limitation of the model due to the variational bottleneck. There is a tradeoff when we train: the more we limit information flow through the bottleneck, the worse the reconstructions; the less we limit information flow, the worse the sampling.  Or if you're an optimist: the more we limit information flow through the bottleneck, the better the sampling; the less we limit information flow, the worse the reconstructions.  This tradeoff is more pronounced for longer sequences, although the hierarchical models help to overcome it somewhat vs flat models.
In some cases we have a lokl and hikl model. The lokl model has a tight bottleneck and hikl has a loose bottleneck.

Based on the examples you sent me offline and watching the video, it does seem like there is a regression somewhere.

It looks like there was a regression between 1.3.1 and 1.3.2.

@iansimon https://github.com/tensorflow/magenta/commit/8899becceaa1be6267ba8971c1f578b2b55b7685 appears to be the culprit

It looks like someone already sent in a PR for this (#1709) but it was never merged for some reason. We are merging it now and then I'll update the pip package.

Thanks very much Adam! The only last thing is different before the meltdown is the midi download... It only downloads the mean sequence rather than the whole progression. Thanks very much!!

Thanks very much Adam!!! It is just so hard to search in Colab. Got it!!!

authors: Z-QIAO adarob

repo: tensorflow/magenta


text:
More than just piano?

Is it possible using any of the models (except for the NSynth model, because it doesn't use MIDI), to generate MIDI files with more than 1 MIDI instrument?

if you want to generate midi files with more instruments,maybe you should edit the code by yourself,becaulse  I traced the code "melody_rnn_generate" and know that beforing generating midi file,you should refer a certain instrument. and so as other model in my opinion.

I understand that I can change piano to another instrument, but I'm asking if the music models could use multiple instruments at once.

I was playing around with a variant on Performance RNN that handles multiple instruments.  Code is here but not sure it's in a great state; that said, it should be fairly straightforward to modify the Performance RNN representation to handle instrument change events.
Of course, stuffing all instruments into a single stream might very well not be the best way to handle multiple instrument generation...

Thanks! I'll try that out!

Any related news? @iansimon @Programmerino

There is also MusicVAE which supports Trio models with multiple instruments as well as the Multi-Track model.

authors: Calvin-Shen SkyrisBactera adarob iansimon nodiz


text:
FailedPreconditionError HashTable has different value for same key. Key  has 1 and trying to add value 4

the code from example:
nmt/scripts/wmt16_en_de.sh /tmp/wmt16
python -m nmt.nmt
--src=de --tgt=en
--hparams_path=nmt/standard_hparams/wmt16_gnmt_4_layer.json
--out_dir=/tmp/deen_gnmt
--vocab_prefix=/tmp/wmt16/vocab.bpe.32000
--train_prefix=/tmp/wmt16/train.tok.clean.bpe.32000
--dev_prefix=/tmp/wmt16/newstest2013.tok.bpe.32000
--test_prefix=/tmp/wmt16/newstest2015.tok.bpe.32000
it caused error like this:
FailedPreconditionError (see above for traceback): HashTable has different value for same key. Key  has 1 and trying to add value 4
[[Node: string_to_index/hash_table/table_init = InitializeTableFromTextFileV2[delimiter="\t", key_index=-2, value_index=-1, vocab_size=-1, _device="/job:localhost/replica:0/task:0/device:CPU:0"](string_to_index/hash_table, string_to_index/hash_table/table_init/asset_filepath)]]
[[Node: string_to_index/hash_table/table_init/_10 = _Recvclient_terminated=false, recv_device="/job:localhost/replica:0/task:0/device:GPU:0", send_device="/job:localhost/replica:0/task:0/device:CPU:0", send_device_incarnation=1, tensor_name="edge_6_string_to_index/hash_table/table_init", tensor_type=DT_FLOAT, _device="/job:localhost/replica:0/task:0/device:GPU:0"]]
what makes this happen?how can i slove it?could someone help?

I have the same problem. Could you please tell me how you fixed this?

check the vocab file ,maybe contains two same values like ,delete one.

check the vocab file ,if the file has two same values like '',delete one,keep one.

authors: KaqiKaqi SuperYm

repo: tensorflow/nmt


text:
Is it possible to get the distance between two samples?

Suppose I train the model like this.
I'm trying to figure out if I could pass two new samples to the model and not retrieve the closest items, but to the distance between them so I can say whether they are the same or not (for that I'd also need to know the mean distance between the clusters and withing samples of the cluster, to find a good threshold), as can be seen here, under Visualize the predictions.

You can certainly do this using the following steps:

Call model.predict() on a list of examples.
Call tf.stack() on the list of predictions.
Pass the stacked predictions to the same tensorflow_similarity.distances function used during training.
This will produce a symmetric, pairwise distance matrix.

Alternatively, you can directly train a siamese network that computes the contrastive loss on the distance between two examples. This is not too hard, but will require writing a custom gradient.tape function. You can see something similar with the self-supervised model in the development branch.

authors: owenvallis paulaceccon

repo: tensorflow/similarity


text:
t2t_decoder not working for model trained with bfloat16

I trained a transformer model with bfloat16 (weights and activations). when i try to decode from file I am getting type mismatch errors in various places. the same procedure works fine for a float32 model.
t2t-decoder --data_dir=$DATA_DIR --problem=translate_ende_wmt32k --model=transformer --hparams_set=transformer_tpu --output_dir=$OUT_DIR --decode_hparams="beam_size=$BEAM_SIZE,alpha=$ALPHA" --decode_from_file=text.en --decode_to_file=translation.de

i got the decoder working by using for the decoder:
hparams.activation_dtype = "float32"
hparams.weight_dtype = "bfloat16"

on wmt14 en-de i can use batches as large as 18432

Ah, gotcha, don't think WMT eval sets are that large, so that's during training right?
Have you tried measuring the speedup before and after using t2t-decoder for, say, batch size 32?

i was referring to training

have you measured any stats while decoding? How does performance and inference speed compare to float32?

authors: eyaler s-xie zxie


text:
matmul back-propagation quadratic memory consumption

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Windows 7
TensorFlow installed from (source or binary): binary
TensorFlow version (use command below): 1.3.0
Python version: 3.6.3
CUDA/cuDNN version: using CPU only

Describe the problem
tf.matmul in back-propagation has memory consumption quadratic in the number of records of data. Test case and discussion here:
https://stackoverflow.com/questions/47991747/back-propagation-exhibiting-quadratic-memory-consumption
One answer at time of writing suggests a workaround using mini-batches, appears to confirm quadratic memory consumption is not expected. I've also tried using tf.tensordot(a,b,1) which seems to be a synonym of tf.matmul(a,b) and does not use as much memory. This despite the existence of another discussion indicating tf.matmul should be more efficient:
https://stackoverflow.com/questions/43100679/tensorflow-einsum-vs-matmul-vs-tensordot

It turns out to be again the problem of shape. Using matmul the way I did there, generates output of shape (n,1). Using that in a context where shape (n,) was expected, silently generates quadratic blowup. This is arguably at least a usability bug, but that has already been posted elsewhere, so this one can be closed.

repo: tensorflow/tensorflow


text:
Tensorboard Error 404, path /[[_dataImageSrc]] not found

I am using the object detection API
and training a new ssd_mobilenet from scratch with my dataset.
I already did a successful retraining, but now i want to try a complete new training without checkpoint.
The training and evaluation job seem to run normal, but when i start tensorboard and open port 6006 in my browser,  the terminal where its running shows following error:
W0213 11:04:23.869396 Thread-2 application.py:273] path /[[_dataImageSrc]] not found, sending 404
and no scalars, except of the learning rate, are visualized in tensorboard.
In contrast to that Evaluation images, the graph, distributions and histogram are all shown correctly.

although the error is still shown, now everything works and is displayed as it should.
Idk what was the reason but doesn't seem to be really problematic.
Thanks, closing!