jquery error when posting tickets as user

while creating a ticket as user the window doesn't close after clicking add
I checked the console and it throws a jquery error
jquery-3.4.1.min.js:2 POST http://<IP_ADDRESS>:8000/tickets 500 (Internal Server Error)
send @ jquery-3.4.1.min.js:2
ajax @ jquery-3.4.1.min.js:2
ajax_form_submit @ create:380
(anonymous) @ create:361
dispatch @ jquery-3.4.1.min.js:2
v.handle @ jquery-3.4.1.min.js:2

hello @vasilejianu,
The HTTP error 500 error you're getting is generated in Laravel and not in jquery itself.
In PanicHD there are some e-mail notifications active by default, but if you don't have all email parameters correctly filled up in your Laravel app or PanicHD or they don't work, when you add a new ticket you will get the error you have specified.
You may even check you Laravel log to view that error traceback. Do check this, please follow these steps:

Execute the action that causes this error in your app
Open storage\logs in your Laravel app and open today's assigned log file
Errors details start with date and time. Look for the instant when you have got the error.
Copy these error details in a new comment in this issue

[2021-06-23 12:08:35] local.ERROR: Attempt to read property "id" on null {"userId":1,"exception":"[object] (ErrorException(code: 0): Attempt to read property "id" on null at F:\dev\apex-windows\vendor\panichd\panichd\src\Models\Ticket.php:835)
[stacktrace]
#0 F:\dev\apex-windows\vendor\panichd\panichd\src\Models\Ticket.php(835): Illuminate\Foundation\Bootstrap\HandleExceptions->handleError(2, 'Attempt to read...', 'F:\\dev\\apex-win...', 835)
#1 F:\dev\apex-windows\vendor\panichd\panichd\src\Controllers\TicketsController.php(1578): PanicHD\PanicHD\Models\Ticket->autoSelectAgent()
#2 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Routing\Controller.php(54): PanicHD\PanicHD\Controllers\TicketsController->store(Object(Illuminate\Http\Request))
#3 F:\dev\apex-windows\vendor\panichd\panichd\src\Controllers\TicketsController.php(64): Illuminate\Routing\Controller->callAction('store', Array)
#4 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Routing\ControllerDispatcher.php(45): PanicHD\PanicHD\Controllers\TicketsController->callAction('store', Array)
#5 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Routing\Route.php(254): Illuminate\Routing\ControllerDispatcher->dispatch(Object(Illuminate\Routing\Route), Object(PanicHD\PanicHD\Controllers\TicketsController), 'store')
#6 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Routing\Route.php(197): Illuminate\Routing\Route->runController()
#7 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Routing\Router.php(695): Illuminate\Routing\Route->run()
#8 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(128): Illuminate\Routing\Router->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#9 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Routing\Middleware\SubstituteBindings.php(50): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#10 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(167): Illuminate\Routing\Middleware\SubstituteBindings->handle(Object(Illuminate\Http\Request), Object(Closure))
#11 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Auth\Middleware\Authenticate.php(44): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#12 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(167): Illuminate\Auth\Middleware\Authenticate->handle(Object(Illuminate\Http\Request), Object(Closure))
#13 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Foundation\Http\Middleware\VerifyCsrfToken.php(78): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#14 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(167): Illuminate\Foundation\Http\Middleware\VerifyCsrfToken->handle(Object(Illuminate\Http\Request), Object(Closure))
#15 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\View\Middleware\ShareErrorsFromSession.php(49): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#16 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(167): Illuminate\View\Middleware\ShareErrorsFromSession->handle(Object(Illuminate\Http\Request), Object(Closure))
#17 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Session\Middleware\StartSession.php(121): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#18 F:\dev\apex-windows\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))
#19 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(167): Illuminate\Session\Middleware\StartSession->handle(Object(Illuminate\Http\Request), Object(Closure))
#20 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Cookie\Middleware\AddQueuedCookiesToResponse.php(37): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#21 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(167): Illuminate\Cookie\Middleware\AddQueuedCookiesToResponse->handle(Object(Illuminate\Http\Request), Object(Closure))
#22 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Cookie\Middleware\EncryptCookies.php(67): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#23 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(167): Illuminate\Cookie\Middleware\EncryptCookies->handle(Object(Illuminate\Http\Request), Object(Closure))
#24 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(103): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#25 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Routing\Router.php(697): Illuminate\Pipeline\Pipeline->then(Object(Closure))
#26 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Routing\Router.php(672): Illuminate\Routing\Router->runRouteWithinStack(Object(Illuminate\Routing\Route), Object(Illuminate\Http\Request))
#27 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Routing\Router.php(636): Illuminate\Routing\Router->runRoute(Object(Illuminate\Http\Request), Object(Illuminate\Routing\Route))
#28 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Routing\Router.php(625): Illuminate\Routing\Router->dispatchToRoute(Object(Illuminate\Http\Request))
#29 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Foundation\Http\Kernel.php(166): Illuminate\Routing\Router->dispatch(Object(Illuminate\Http\Request))
#30 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(128): Illuminate\Foundation\Http\Kernel->Illuminate\Foundation\Http\{closure}(Object(Illuminate\Http\Request))
#31 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Foundation\Http\Middleware\TransformsRequest.php(21): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#32 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Foundation\Http\Middleware\ConvertEmptyStringsToNull.php(31): Illuminate\Foundation\Http\Middleware\TransformsRequest->handle(Object(Illuminate\Http\Request), Object(Closure))
#33 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(167): Illuminate\Foundation\Http\Middleware\ConvertEmptyStringsToNull->handle(Object(Illuminate\Http\Request), Object(Closure))
#34 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Foundation\Http\Middleware\TransformsRequest.php(21): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#35 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Foundation\Http\Middleware\TrimStrings.php(40): Illuminate\Foundation\Http\Middleware\TransformsRequest->handle(Object(Illuminate\Http\Request), Object(Closure))
#36 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(167): Illuminate\Foundation\Http\Middleware\TrimStrings->handle(Object(Illuminate\Http\Request), Object(Closure))
#37 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Foundation\Http\Middleware\ValidatePostSize.php(27): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#38 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(167): Illuminate\Foundation\Http\Middleware\ValidatePostSize->handle(Object(Illuminate\Http\Request), Object(Closure))
#39 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Foundation\Http\Middleware\PreventRequestsDuringMaintenance.php(86): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#40 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(167): Illuminate\Foundation\Http\Middleware\PreventRequestsDuringMaintenance->handle(Object(Illuminate\Http\Request), Object(Closure))
#41 F:\dev\apex-windows\vendor\fruitcake\laravel-cors\src\HandleCors.php(37): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#42 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(167): Fruitcake\Cors\HandleCors->handle(Object(Illuminate\Http\Request), Object(Closure))
#43 F:\dev\apex-windows\vendor\fideloper\proxy\src\TrustProxies.php(57): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#44 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(167): Fideloper\Proxy\TrustProxies->handle(Object(Illuminate\Http\Request), Object(Closure))
#45 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(103): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#46 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Foundation\Http\Kernel.php(141): Illuminate\Pipeline\Pipeline->then(Object(Closure))
#47 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Foundation\Http\Kernel.php(110): Illuminate\Foundation\Http\Kernel->sendRequestThroughRouter(Object(Illuminate\Http\Request))
#48 F:\dev\apex-windows\public\index.php(52): Illuminate\Foundation\Http\Kernel->handle(Object(Illuminate\Http\Request))
#49 F:\dev\apex-windows\server.php(21): require_once('F:\\dev\\apex-win...')
#50 {main}
"}
[2021-06-23 12:08:35] local.ERROR: Attempt to read property "id" on null {"userId":1,"exception":"[object] (ErrorException(code: 0): Attempt to read property "id" on null at F:\dev\apex-windows\vendor\panichd\panichd\src\Models\Ticket.php:835)
[stacktrace]
#0 F:\dev\apex-windows\vendor\panichd\panichd\src\Models\Ticket.php(835): Illuminate\Foundation\Bootstrap\HandleExceptions->handleError(2, 'Attempt to read...', 'F:\\dev\\apex-win...', 835)
#1 F:\dev\apex-windows\vendor\panichd\panichd\src\Controllers\TicketsController.php(1578): PanicHD\PanicHD\Models\Ticket->autoSelectAgent()
#2 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Routing\Controller.php(54): PanicHD\PanicHD\Controllers\TicketsController->store(Object(Illuminate\Http\Request))
#3 F:\dev\apex-windows\vendor\panichd\panichd\src\Controllers\TicketsController.php(64): Illuminate\Routing\Controller->callAction('store', Array)
#4 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Routing\ControllerDispatcher.php(45): PanicHD\PanicHD\Controllers\TicketsController->callAction('store', Array)
#5 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Routing\Route.php(254): Illuminate\Routing\ControllerDispatcher->dispatch(Object(Illuminate\Routing\Route), Object(PanicHD\PanicHD\Controllers\TicketsController), 'store')
#6 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Routing\Route.php(197): Illuminate\Routing\Route->runController()
#7 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Routing\Router.php(695): Illuminate\Routing\Route->run()
#8 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(128): Illuminate\Routing\Router->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#9 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Routing\Middleware\SubstituteBindings.php(50): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#10 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(167): Illuminate\Routing\Middleware\SubstituteBindings->handle(Object(Illuminate\Http\Request), Object(Closure))
#11 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Auth\Middleware\Authenticate.php(44): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#12 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(167): Illuminate\Auth\Middleware\Authenticate->handle(Object(Illuminate\Http\Request), Object(Closure))
#13 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Foundation\Http\Middleware\VerifyCsrfToken.php(78): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#14 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(167): Illuminate\Foundation\Http\Middleware\VerifyCsrfToken->handle(Object(Illuminate\Http\Request), Object(Closure))
#15 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\View\Middleware\ShareErrorsFromSession.php(49): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#16 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(167): Illuminate\View\Middleware\ShareErrorsFromSession->handle(Object(Illuminate\Http\Request), Object(Closure))
#17 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Session\Middleware\StartSession.php(121): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#18 F:\dev\apex-windows\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))
#19 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(167): Illuminate\Session\Middleware\StartSession->handle(Object(Illuminate\Http\Request), Object(Closure))
#20 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Cookie\Middleware\AddQueuedCookiesToResponse.php(37): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#21 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(167): Illuminate\Cookie\Middleware\AddQueuedCookiesToResponse->handle(Object(Illuminate\Http\Request), Object(Closure))
#22 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Cookie\Middleware\EncryptCookies.php(67): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#23 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(167): Illuminate\Cookie\Middleware\EncryptCookies->handle(Object(Illuminate\Http\Request), Object(Closure))
#24 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(103): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#25 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Routing\Router.php(697): Illuminate\Pipeline\Pipeline->then(Object(Closure))
#26 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Routing\Router.php(672): Illuminate\Routing\Router->runRouteWithinStack(Object(Illuminate\Routing\Route), Object(Illuminate\Http\Request))
#27 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Routing\Router.php(636): Illuminate\Routing\Router->runRoute(Object(Illuminate\Http\Request), Object(Illuminate\Routing\Route))
#28 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Routing\Router.php(625): Illuminate\Routing\Router->dispatchToRoute(Object(Illuminate\Http\Request))
#29 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Foundation\Http\Kernel.php(166): Illuminate\Routing\Router->dispatch(Object(Illuminate\Http\Request))
#30 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(128): Illuminate\Foundation\Http\Kernel->Illuminate\Foundation\Http\{closure}(Object(Illuminate\Http\Request))
#31 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Foundation\Http\Middleware\TransformsRequest.php(21): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#32 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Foundation\Http\Middleware\ConvertEmptyStringsToNull.php(31): Illuminate\Foundation\Http\Middleware\TransformsRequest->handle(Object(Illuminate\Http\Request), Object(Closure))
#33 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(167): Illuminate\Foundation\Http\Middleware\ConvertEmptyStringsToNull->handle(Object(Illuminate\Http\Request), Object(Closure))
#34 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Foundation\Http\Middleware\TransformsRequest.php(21): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#35 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Foundation\Http\Middleware\TrimStrings.php(40): Illuminate\Foundation\Http\Middleware\TransformsRequest->handle(Object(Illuminate\Http\Request), Object(Closure))
#36 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(167): Illuminate\Foundation\Http\Middleware\TrimStrings->handle(Object(Illuminate\Http\Request), Object(Closure))
#37 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Foundation\Http\Middleware\ValidatePostSize.php(27): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#38 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(167): Illuminate\Foundation\Http\Middleware\ValidatePostSize->handle(Object(Illuminate\Http\Request), Object(Closure))
#39 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Foundation\Http\Middleware\PreventRequestsDuringMaintenance.php(86): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#40 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(167): Illuminate\Foundation\Http\Middleware\PreventRequestsDuringMaintenance->handle(Object(Illuminate\Http\Request), Object(Closure))
#41 F:\dev\apex-windows\vendor\fruitcake\laravel-cors\src\HandleCors.php(37): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#42 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(167): Fruitcake\Cors\HandleCors->handle(Object(Illuminate\Http\Request), Object(Closure))
#43 F:\dev\apex-windows\vendor\fideloper\proxy\src\TrustProxies.php(57): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#44 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(167): Fideloper\Proxy\TrustProxies->handle(Object(Illuminate\Http\Request), Object(Closure))
#45 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(103): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#46 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Foundation\Http\Kernel.php(141): Illuminate\Pipeline\Pipeline->then(Object(Closure))
#47 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Foundation\Http\Kernel.php(110): Illuminate\Foundation\Http\Kernel->sendRequestThroughRouter(Object(Illuminate\Http\Request))
#48 F:\dev\apex-windows\public\index.php(52): Illuminate\Foundation\Http\Kernel->handle(Object(Illuminate\Http\Request))
#49 F:\dev\apex-windows\server.php(21): require_once('F:\\dev\\apex-win...')
#50 {main}
"}

Hi @vasilejianu,
As you may see at the beginning of your error traceback, it starts in "panichd\src\Models\Ticket.php" at line 835. This line contains:
$selected_agent_id = $first_admin->id;
You may use Laravel tinker to check what do you get in your Laravel app when executing this code:
\PanicHDMember::admins()->first();
If you have PanicHD correctly configured, you should get at least one member account instance. If I do this in my local app I get:

Please share here what do you get with it. If  you get null result, you should review your Laravel users table in your database, and check if your admin account has "panichd_admin" field value "1"

ok that makes sense now , its my fault
Due to testing this in dev and not prod i though ill cheat my way of adding a new user and modified my and only account in db with the flags 0 for admin and agent so no admins were available :)
Thank you very much sir for your help

Hi @vasilejianu,
I'm glad I could help you. Thanks for your quick response

i think now im facing the email problem you mentioned above
disabling the notifications from options menu solves the issue but would like to get this setup properly
any help in pointing me in the right direction on how to get this working? thanks
[2021-06-24 18:04:15] local.ERROR: Address in mailbox given [] does not comply with RFC 2822, 3.6.2. {"userId":24,"exception":"[object] (Swift_RfcComplianceException(code: 0): Address in mailbox given [] does not comply with RFC 2822, 3.6.2. at F:\dev\apex-windows\vendor\swiftmailer\swiftmailer\lib\classes\Swift\Mime\Headers\MailboxHeader.php:355)
[stacktrace]
#0 F:\dev\apex-windows\vendor\swiftmailer\swiftmailer\lib\classes\Swift\Mime\Headers\MailboxHeader.php(272): Swift_Mime_Headers_MailboxHeader->assertValidAddress('')
#1 F:\dev\apex-windows\vendor\swiftmailer\swiftmailer\lib\classes\Swift\Mime\Headers\MailboxHeader.php(117): Swift_Mime_Headers_MailboxHeader->normalizeMailboxes(Array)
#2 F:\dev\apex-windows\vendor\swiftmailer\swiftmailer\lib\classes\Swift\Mime\Headers\MailboxHeader.php(74): Swift_Mime_Headers_MailboxHeader->setNameAddresses(Array)
#3 F:\dev\apex-windows\vendor\swiftmailer\swiftmailer\lib\classes\Swift\Mime\SimpleMimeEntity.php(600): Swift_Mime_Headers_MailboxHeader->setFieldBodyModel(Array)
#4 F:\dev\apex-windows\vendor\swiftmailer\swiftmailer\lib\classes\Swift\Mime\SimpleMessage.php(213): Swift_Mime_SimpleMimeEntity->setHeaderFieldModel('From', Array)
#5 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Mail\Message.php(50): Swift_Mime_SimpleMessage->setFrom(Array, 'Laravel')
#6 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Mail\Mailable.php(355): Illuminate\Mail\Message->from(NULL, 'Laravel')
#7 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Mail\Mailable.php(181): Illuminate\Mail\Mailable->buildFrom(Object(Illuminate\Mail\Message))
#8 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Mail\Mailer.php(271): Illuminate\Mail\Mailable->Illuminate\Mail\{closure}(Object(Illuminate\Mail\Message))
#9 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Mail\Mailable.php(186): Illuminate\Mail\Mailer->send('panichd::emails...', Array, Object(Closure))
#10 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Support\Traits\Localizable.php(19): Illuminate\Mail\Mailable->Illuminate\Mail\{closure}()
#11 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Mail\Mailable.php(187): Illuminate\Mail\Mailable->withLocale(NULL, Object(Closure))
#12 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Mail\Mailer.php(304): Illuminate\Mail\Mailable->send(Object(Illuminate\Mail\Mailer))
#13 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Mail\Mailer.php(258): Illuminate\Mail\Mailer->sendMailable(Object(PanicHD\PanicHD\Mail\PanicHDNotification))
#14 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Mail\PendingMail.php(121): Illuminate\Mail\Mailer->send(Object(PanicHD\PanicHD\Mail\PanicHDNotification))
#15 F:\dev\apex-windows\vendor\panichd\panichd\src\Controllers\NotificationsController.php(434): Illuminate\Mail\PendingMail->send(Object(PanicHD\PanicHD\Mail\PanicHDNotification))
#16 F:\dev\apex-windows\vendor\panichd\panichd\src\Controllers\NotificationsController.php(225): PanicHD\PanicHD\Controllers\NotificationsController->sendNotification(Array, Array)
#17 F:\dev\apex-windows\vendor\panichd\panichd\src\PanicHDServiceProvider.php(269): PanicHD\PanicHD\Controllers\NotificationsController->newComment(Object(PanicHD\PanicHD\Models\Comment), Object(Illuminate\Http\Request))
#18 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Events\Dispatcher.php(392): PanicHD\PanicHD\PanicHDServiceProvider->PanicHD\PanicHD\{closure}(Object(PanicHD\PanicHD\Events\CommentCreated))
#19 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Events\Dispatcher.php(237): Illuminate\Events\Dispatcher->Illuminate\Events\{closure}('PanicHD\\PanicHD...', Array)
#20 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Foundation\helpers.php(450): Illuminate\Events\Dispatcher->dispatch('PanicHD\\PanicHD...')
#21 F:\dev\apex-windows\vendor\panichd\panichd\src\Controllers\CommentsController.php(217): event(Object(PanicHD\PanicHD\Events\CommentCreated))
#22 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Routing\Controller.php(54): PanicHD\PanicHD\Controllers\CommentsController->store(Object(Illuminate\Http\Request))
#23 F:\dev\apex-windows\vendor\panichd\panichd\src\Controllers\CommentsController.php(36): Illuminate\Routing\Controller->callAction('store', Array)
#24 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Routing\ControllerDispatcher.php(45): PanicHD\PanicHD\Controllers\CommentsController->callAction('store', Array)
#25 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Routing\Route.php(254): Illuminate\Routing\ControllerDispatcher->dispatch(Object(Illuminate\Routing\Route), Object(PanicHD\PanicHD\Controllers\CommentsController), 'store')
#26 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Routing\Route.php(197): Illuminate\Routing\Route->runController()
#27 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Routing\Router.php(695): Illuminate\Routing\Route->run()
#28 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(128): Illuminate\Routing\Router->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#29 F:\dev\apex-windows\vendor\panichd\panichd\src\Middleware\UserAccessMiddleware.php(35): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#30 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(167): PanicHD\PanicHD\Middleware\UserAccessMiddleware->handle(Object(Illuminate\Http\Request), Object(Closure))
#31 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Routing\Middleware\SubstituteBindings.php(50): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#32 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(167): Illuminate\Routing\Middleware\SubstituteBindings->handle(Object(Illuminate\Http\Request), Object(Closure))
#33 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Auth\Middleware\Authenticate.php(44): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#34 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(167): Illuminate\Auth\Middleware\Authenticate->handle(Object(Illuminate\Http\Request), Object(Closure))
#35 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Foundation\Http\Middleware\VerifyCsrfToken.php(78): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#36 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(167): Illuminate\Foundation\Http\Middleware\VerifyCsrfToken->handle(Object(Illuminate\Http\Request), Object(Closure))
#37 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\View\Middleware\ShareErrorsFromSession.php(49): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#38 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(167): Illuminate\View\Middleware\ShareErrorsFromSession->handle(Object(Illuminate\Http\Request), Object(Closure))
#39 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Session\Middleware\StartSession.php(121): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#40 F:\dev\apex-windows\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))
#41 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(167): Illuminate\Session\Middleware\StartSession->handle(Object(Illuminate\Http\Request), Object(Closure))
#42 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Cookie\Middleware\AddQueuedCookiesToResponse.php(37): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#43 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(167): Illuminate\Cookie\Middleware\AddQueuedCookiesToResponse->handle(Object(Illuminate\Http\Request), Object(Closure))
#44 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Cookie\Middleware\EncryptCookies.php(67): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#45 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(167): Illuminate\Cookie\Middleware\EncryptCookies->handle(Object(Illuminate\Http\Request), Object(Closure))
#46 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(103): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#47 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Routing\Router.php(697): Illuminate\Pipeline\Pipeline->then(Object(Closure))
#48 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Routing\Router.php(672): Illuminate\Routing\Router->runRouteWithinStack(Object(Illuminate\Routing\Route), Object(Illuminate\Http\Request))
#49 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Routing\Router.php(636): Illuminate\Routing\Router->runRoute(Object(Illuminate\Http\Request), Object(Illuminate\Routing\Route))
#50 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Routing\Router.php(625): Illuminate\Routing\Router->dispatchToRoute(Object(Illuminate\Http\Request))
#51 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Foundation\Http\Kernel.php(166): Illuminate\Routing\Router->dispatch(Object(Illuminate\Http\Request))
#52 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(128): Illuminate\Foundation\Http\Kernel->Illuminate\Foundation\Http\{closure}(Object(Illuminate\Http\Request))
#53 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Foundation\Http\Middleware\TransformsRequest.php(21): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#54 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Foundation\Http\Middleware\ConvertEmptyStringsToNull.php(31): Illuminate\Foundation\Http\Middleware\TransformsRequest->handle(Object(Illuminate\Http\Request), Object(Closure))
#55 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(167): Illuminate\Foundation\Http\Middleware\ConvertEmptyStringsToNull->handle(Object(Illuminate\Http\Request), Object(Closure))
#56 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Foundation\Http\Middleware\TransformsRequest.php(21): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#57 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Foundation\Http\Middleware\TrimStrings.php(40): Illuminate\Foundation\Http\Middleware\TransformsRequest->handle(Object(Illuminate\Http\Request), Object(Closure))
#58 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(167): Illuminate\Foundation\Http\Middleware\TrimStrings->handle(Object(Illuminate\Http\Request), Object(Closure))
#59 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Foundation\Http\Middleware\ValidatePostSize.php(27): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#60 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(167): Illuminate\Foundation\Http\Middleware\ValidatePostSize->handle(Object(Illuminate\Http\Request), Object(Closure))
#61 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Foundation\Http\Middleware\PreventRequestsDuringMaintenance.php(86): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#62 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(167): Illuminate\Foundation\Http\Middleware\PreventRequestsDuringMaintenance->handle(Object(Illuminate\Http\Request), Object(Closure))
#63 F:\dev\apex-windows\vendor\fruitcake\laravel-cors\src\HandleCors.php(37): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#64 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(167): Fruitcake\Cors\HandleCors->handle(Object(Illuminate\Http\Request), Object(Closure))
#65 F:\dev\apex-windows\vendor\fideloper\proxy\src\TrustProxies.php(57): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#66 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(167): Fideloper\Proxy\TrustProxies->handle(Object(Illuminate\Http\Request), Object(Closure))
#67 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Pipeline\Pipeline.php(103): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#68 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Foundation\Http\Kernel.php(141): Illuminate\Pipeline\Pipeline->then(Object(Closure))
#69 F:\dev\apex-windows\vendor\laravel\framework\src\Illuminate\Foundation\Http\Kernel.php(110): Illuminate\Foundation\Http\Kernel->sendRequestThroughRouter(Object(Illuminate\Http\Request))
#70 F:\dev\apex-windows\public\index.php(52): Illuminate\Foundation\Http\Kernel->handle(Object(Illuminate\Http\Request))
#71 F:\dev\apex-windows\server.php(21): require_once('F:\\dev\\apex-win...')
#72 {main}
"}


Apply line caps

Here's one example where the strokes on this path don't join up.

They should probably be closed, but that's the file wrong I think
So I think they normally just overlap, but may need a specific line cap to reach the next edge, and I know I haven't implemented line caps.
Does unity's vector API support different line caps?

studio5logo.pretty.json

Done in #11


Remove batchnorm in DeepLabV3 ASPPPooling module

DeepLabV3 failed to perform training with an error:
ValueError: Expected more than 1 value per channel when training, got input size torch.Size([1, 256, 1, 1])
PyTorch Batch Normalization 2D layer does not support input with spatial shape 1x1, but AdaptiveAvgPool2d(1) here always produce tensors with such shape.
torch version: 1.2.0

Codecov Report

Merging #1667 into master will decrease coverage by 66.02%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #1667       +/-   ##
==========================================
- Coverage   66.02%      0%   -66.03%
==========================================
  Files          92      92
  Lines        7331    7331
  Branches     1107    1107
==========================================
- Hits         4840       0     -4840
- Misses       2175    7331     +5156
+ Partials      316       0      -316

Impacted Files
Coverage Δ

torchvision/models/segmentation/deeplabv3.py
0% <ø> (-100%)
:arrow_down:

torchvision/models/quantization/__init__.py
0% <0%> (-100%)
:arrow_down:

torchvision/ops/boxes.py
0% <0%> (-100%)
:arrow_down:

torchvision/datasets/samplers/__init__.py
0% <0%> (-100%)
:arrow_down:

torchvision/ops/_register_onnx_ops.py
0% <0%> (-100%)
:arrow_down:

torchvision/models/__init__.py
0% <0%> (-100%)
:arrow_down:

torchvision/io/__init__.py
0% <0%> (-100%)
:arrow_down:

torchvision/models/segmentation/fcn.py
0% <0%> (-100%)
:arrow_down:

torchvision/ops/__init__.py
0% <0%> (-100%)
:arrow_down:

torchvision/models/segmentation/__init__.py
0% <0%> (-100%)
:arrow_down:

... and 83 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2d7c066...44bde87. Read the comment docs.


Document how to delete an artifact and a transform

This needs to go through reticulate.
In Python, for a transform record:
transform = ln.Transform.get(uid="...")
transform.delete()

Updated the title to make this about documentation.


chore/bump-kfm version to kfm prod version

Closing, need to create this change on stage branch directly to avoid breaking dev env!


snapTo Menu

http://www.garagegames.com/community/resources/view/5880/2#comment-195821
Credit to Paul Weston

Very useful for a lot stuff like modular levels... If anyone need a video of how it work, I can do it.


Create stv.md

Add doc for new stv adapter

For https://github.com/prebid/Prebid.js/pull/3737

released with 2.11


fix(25622): fix bug with compact table

See https://hivemq.kanbanize.com/ctrl_board/57/cards/25622/details/
The fix prevents the RJSC registry, which contains templates and widgets, to be permanently modified for the overrides needed by the compact table

Not fixing the problem, creating others. Discarded


pipenv shell should have envvar option to block bare pip usage

Problem
pipenv shell currently allows bare pip commands to be executed inside the shell, which means that you can pip install foo and have package foo available to your Python code, but not have foo present in the Pipfile or Pipfile.lock.
In practice, that means that a developer's tests will pass locally, but not once the code is pushed to a CI test suite.
Proposed solution
Provide an environment variable to be passed to pipenv shell which will block bare pip access, or at least output a warning when it's used.
Describe alternatives you've considered
Another possibility would be for pipenv shell to warn the user when it detects packages that are in the virtualenv, but aren't in the Pipfile. However, this would only trigger when new shells are launched.
Additional context
Versions:
Python 3.9.1
pipenv, version 2020.11.15

Note: not running pipenv --support here because it has nonpublic information and isn't relevant to this feature request.
Apologies if this is a known issue - it's hard to search the issues list for this particular problem.

@vaughnkoch I don't believe we want to block pip usage -- for myself, I often want to pip install something for use in my own virtualenv in the project space but not check that in to the project in the Pipfile and Pipfile.lock  and I believe other users do similar.
I believe it is better to just take more time reviewing the command being entered.


feat: remove asyncapi new projectalias

Removing asyncapi new project alias since is doing exactly the same like asyncapi new glee.
Related issue(s)
Resolves #913

/rtm


Add support for vector in/out for LSTM

Hello,
it would be great to be able to be able to train LSTM on the 2D vector in -> 2D vector out basis, like is e.g. OCRopus or in Pybrain.
I am not able to easily reproduce this with Keras right now, since LSTM wants 3D array. I couldn't figure out how to simply transfer matrix, where rows are vectors of integers in specific timestep to this 3D format.
Thank you

You need to use the constructor argument return_sequences=True. I believe the documentation covers all of this.


POW(x,n) USING JAVA

Hi Dear @Tanushree-Ghosh
Great code
Thanks for your contribution......
Show your support on my youtube channel web Pixar(The institute of coding)
like , share , subscribe
youtube - https://youtu.be/5qnQjgdpFPg
telegram-channel - https://t.me/WebPixar
join our telegram channel for more goodies , swag packs


feat: #2067 - code cleaning

Impacted file:

personalized_ranking_page.dart: code cleaning

What

There were several open options regarding the new UI.
Now that one of them was chosen, it was time to get rid of the other options' code

Part of

#2067

Codecov Report

Merging #2182 (1da37ff) into develop (2ea0da3) will decrease coverage by 0.96%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           develop   #2182      +/-   ##
==========================================
- Coverage     8.86%   7.90%   -0.97%
==========================================
  Files          161     176      +15
  Lines         6623    8630    +2007
==========================================
+ Hits           587     682      +95
- Misses        6036    7948    +1912

Impacted Files
Coverage Δ

...kages/smooth_app/lib/widgets/attribute_button.dart
0.00% <0.00%> (-92.00%)
:arrow_down:

packages/smooth_app/lib/themes/smooth_theme.dart
53.48% <0.00%> (-29.50%)
:arrow_down:

...s/smooth_app/lib/data_models/user_preferences.dart
11.11% <0.00%> (-21.20%)
:arrow_down:

...p/lib/generic_lib/dialogs/smooth_alert_dialog.dart
19.23% <0.00%> (-14.98%)
:arrow_down:

...mooth_app/lib/data_models/product_preferences.dart
26.47% <0.00%> (-4.96%)
:arrow_down:

.../smooth_app/lib/pages/onboarding/welcome_page.dart
0.00% <0.00%> (-3.13%)
:arrow_down:

.../smooth_app/lib/pages/onboarding/scan_example.dart
0.00% <0.00%> (-2.28%)
:arrow_down:

packages/smooth_app/lib/main.dart
15.74% <0.00%> (-2.16%)
:arrow_down:

...s/smooth_app/lib/pages/onboarding/next_button.dart
2.22% <0.00%> (-1.78%)
:arrow_down:

...p/lib/pages/onboarding/consent_analytics_page.dart
0.00% <0.00%> (-1.57%)
:arrow_down:

... and 162 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9cedfb7...1da37ff. Read the comment docs.


probability_two_random_records_match shouldn't have a default value

What happens?
I've been using splink for a bit, and I just realized I hadn't ever been fitting probability_two_random_records_match. Everything happily works and there are no warnings, even though the default value of 1/10_000 is almost definitely wrong. If I understand correctly, this parameter determines the "prior", which all of the probabilities use as a starting point, so all my final match probabilities are also incorrect.
I think there should be a warning when you try to .predict() if you haven't fit this param, similar to when you haven't fit a particular m or u parameter. (BTW, I love that splink does these warnings, really helps with keeping you from shooting yourself in the foot)
To Reproduce
Never call Linker.estimate_probability_two_random_records_match(), then call .predict()
OS:
all
Splink version:
3.6.0
Have you tried this on the latest master branch?

[X] I agree

Have you tried the steps to reproduce? Do they include all relevant data and configuration? Does the issue you report still appear there?

[X] I agree

I agree there should definitely being a warning if you try and predict() without having fitted this param.
Just for background info: There are various reasons we use defaults for the various params:

They're needed as starting values for the iterative EM estimation process.
In some cases, a particular param cannot be estimated from the data because the scenario never occurs in the data.  This really only applies to m and u probabilities.  It's not great to have a default values, but it prevents the predict() step failing e.g. on new data where that scenario does occur.
m values are hard to estimate.  In many simple use cases, the user could get away with not bothering to train the m values at all, and just use the defaults.  So long as the prior and the u probabilities were trained (which doesn't require EM), the model would probably give quite good predictions.

Some expert practitioners I've spoken to actually don't use this parameter of the model at all.  If you 'don't use it' (by which they mean setting the prior to 0.5, or 50% probability), then the interpretation of the model changes.  The interpretation of the final prediction (match weight) becomes more like "does the information in the columns add or subtract evidence about whether it's a match".
Part of their rationale is that, since the conditional independence assumption behind the fellegi sunter model is almost always false, the 'match probabilities' produced are no reliable probabilities.  So you might as well just use match weight as an arbitrary ordinal score.
Personally I disagree with this because i think in well specified models, the match probabilities get fairly close to true probabilities in many cases (enough for them to be interesting).  And also that setting the prior correctly makes EM estimation converge more reliably.


CORS issue

Some days ago, our users report problems with the branch links, when we check the issue, we could identify that we are presenting a problem of 'CORS' that was not presented before, no changes have been generated in the site.
We use branch some months ago without any trouble, but this new issue is terrible for our application performance.
Thank you for your prompt cooperation.
This is the browser console message:
[Error] Origin https://w.pingpro.com is not allowed by Access-Control-Allow-Origin.
[Error] Failed to load resource: Origin https://w.pingpro.com is not allowed by Access-Control-Allow-Origin. (open, line 0)
[Error] XMLHttpRequest cannot load https://api.branch.io/v1/open due to access control checks.

Having same issue locally and on production server
(index):1 XMLHttpRequest cannot load https://api.branch.io/v1/open. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://localhost:3000' is therefore not allowed access. The response had HTTP status code 400.


Doc showing data from old commit after refresh.

Affected repo: https://godoc.org/github.com/jmoiron/sqlx
Earlier this morning the doc appeared to be correct.  A merge was performed adding a new method a short while ago (jmoiron/sqlx@3564e3a). After refreshing the godoc and a hard reload in the browser, the doc shows outdated info.
I'm unsure of which commit this data represents, but it is old enough to be missing not just the method added today, but also more recent functions and methods which receive context.Context.

I can confirm, this looks like a problem.
I'm not sure if it's a bug in the code, or an operations issue (or both).

One hunch to look into. The func that was added recently is inside a .go file with // +build go1.8.
We should confirm that godoc.org is using a Go 1.8+ build context.

@stephenmw Could you take a look? This works fine with my own deployment.

I've confirmed my hunch was right.
I created a package for debugging this issue at https://github.com/shurcooL/play/commit/11633f2cd8c683fe0a40444edad2896038055f5a.
godoc.org displays "1.7":
https://godoc.org/github.com/shurcooL/play/219

That confirms it's using the Go 1.7 build context, but it should be updated to use Go 1.8.

Thanks @shurcooL , yeah it seems to be an operations issue. I just did a new deployment and it seems work fine now.


Replaced block height with timestamps

Description
This PR replaces all the usages of block heights inside the Post module with timestamps in RFC3339 format (using time.Time). Closes #62.
TODO:

[ ] Modify the migrate command to accept the genesis time and block interval that should be considered when converting posts creation time from using block heights to using timestamps

Checklist

[x] Targeted PR against correct branch.
[x] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[x] Wrote tests.
[x] Added an entry to the CHANGELOG.md file.
[ ] Re-reviewed Files changed in the Github PR explorer.

Codecov Report

Merging #71 into master will decrease coverage by 0.42%.
The diff coverage is 78.57%.

@@            Coverage Diff             @@
##           master      #71      +/-   ##
==========================================
- Coverage   77.37%   76.95%   -0.43%
==========================================
  Files          18       18
  Lines         831      833       +2
==========================================
- Hits          643      641       -2
- Misses        174      176       +2
- Partials       14       16       +2

Impacted Files
Coverage Δ

x/posts/internal/types/querier.go
0% <0%> (ø)
:arrow_up:

x/posts/internal/keeper/keeper.go
98.21% <100%> (ø)
:arrow_up:

x/posts/internal/keeper/handler.go
94.89% <100%> (ø)
:arrow_up:

x/posts/internal/types/reaction.go
82.85% <100%> (-1.76%)
:arrow_down:

x/posts/internal/types/post.go
95.91% <100%> (ø)
:arrow_up:

x/posts/internal/types/msgs.go
95.74% <63.63%> (-4.26%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4a45ac9...31eefde. Read the comment docs.


Unable to download PDFs #2

A year later this problem still persists.
See https://github.com/duckduckgo/Android/issues/1533#issuecomment-1438324172

Duplicate of https://github.com/duckduckgo/Android/issues/3028


Add cleanup routine in AtomDB adapters

Cleanup tasks so far:

Remove atom types not present in the AtomDB

Closing as not-planned because clean-ups are supposed to be performed by a special agent using multiple components such as cache, AttentionBroker and Homeostatic controller. This will be planned/designed later.


Update Makefile

Why we need this PR

The current Makefile needs update for

adding mandatory annotation to OKD bundle
update golang version
update tools

adding the mandatory annotation, I also noted an issue in CI which I decided to fix here, see the first change in the next section.
Changes made

Fix tag version in release document created by CI
Bump golang to version 1.22
Add OCP annotation to OKD bundle
Bump kustomize to version v5.4.2
Fix verify-unchanged script log
Bump controller-gen and envtest versions
Bump ginkgo version to v2.19.0
vendoring due to ginkgo version bump
Bump goimports, opm and sort-imports versions
Bump operator-sdk version to v1.35
Bump envtest k8s version to 1.30

Which issue(s) this PR fixes

Test plan

/test 4.16-openshift-e2e

Dropping last commit, as it is already included in https://github.com/medik8s/fence-agents-remediation/pull/150

superseded by #152


feat: #683 allow arbitrary extensions on graphql type defs

Closes #683

pr release made:
 { distTag: 'pr.684', version: '0.0.0-pr.684.1.187f285' }

I just discovered an edge case which seems to be not working yet.
I have an interface A and some objectType B that implements interface A. I would like to modify the implemented field that is part of interface A (via modify method) within objectType B and also set the extension for the field there.

I have an interface A and some objectType B that implements interface A. I would like to modify the implemented field that is part of interface A (via modify method) within objectType B and also set the extension for the field there.

Cool, will look into supporting this

@benjixx added a failing test for that case.


User Found action violates strictActionSerializability NgRx 8 runtime check

Describe the bug
The OidcUser payload violates the new strictActionSerializability check in NgRx 8
export class UserFound implements Action {
  readonly type = OidcActionTypes.UserFound;

  constructor(public payload: OidcUser) {}
}

To Reproduce
Steps to reproduce the behavior:

Update to NgRx 8
Enable runtime  checks

@NgModule({
  imports: [
    StoreModule.forRoot(reducers, {
      runtimeChecks: {
        strictStateImmutability: true,
        strictActionImmutability: true,
        strictStateSerializability: true,
        strictActionSerializability: true,
      },
    }),
  ],
})

Login and call this.oidcFacade.getOidcUser();
Console log shows error
core.js:5847 ERROR Error: Detected unserializable action at "payload"

Expected behavior
[Oidc] User found action should complete without runtime error
Desktop (please complete the following information):

Windows 10
Browser chrome
Version 74

Thanks for reporting the issue. Will try to update NgRx within the next couple weeks.

Any progress on this?

@mvanderlee
This has been implemented in the latest version.
Let me know if you still have any issues.


Add Blue Waters Documentation

Documentation for how to install UCVM on Blue Waters is still required.

Finally got around to doing this. As part of the most recent check-in to dev. Will be merged into master.


Add live option to getCards()

This PR adds new options to the getCards() API that allows the search to be live as well as to return live cards. The cards from the search are actually provided via CardResource.
In this approach I follow a similar pattern to how we get or create realm resources from the realm service, only instead of realm resources I'm operating with card resources, which takes advantage of an identity map for all the cards it deals with.
Probably a future refactor is to retire the CardService.search(). i don't think it really does what we want since it is not live, and the cards that it returns are not live and does not leverage the identity map from CardResource, so it may create duplicative instances of cards when it deserializes the results.

I have tested and confirm that new cards inside of the search are being indexed and re-rendered!
HOWEVER, the invalidations are still being ignored inside of the card resource (at least inside of the work tracker). Particularly, when I create a new card, I can see that a new card is appearing (with empty vals). Following that, it's typical that I try to edit the fields of that new card (inside edit mode), BUT, the invalidation of that newly created card is ignored bcos of clientRequestIds in the card service as stated here. But, this is the problem of the card resource and not the search itself


Updated "README.md", made it more precise, emojified, short and engaging!

If you are reading this, you are amazing!

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Ans: Just update "README.md" docs because I felt, why not upgrade it a bit?

Why was this change needed? (You can also link to an open issue here)
Ans: The README.md before looks a bit boring honestly, and I thought why not make it fun, short, precise and emojify it a bit!

Other information:
Ans: Thanks!:)

Just make changes here please docs/README.md, remove changes in CODE_OF_CONDUCT.md. Thank you!

@dartpain updated and apologises for any confusion!
Thanks and regards,
Armaan.


Investigate Audio.Create = nil error in Tests

see https://github.com/Limit-Theory-Redux/ltheory/commit/1fcc49458cc630a10fba0bc08b3845ba656f5ff4

I hit this problem as well, and I assumed it's because the LTheoryRedux object is the "App" object for LTheoryRedux, but when we run a different app like PhysicsTest, LTheoryRedux will be an empty table? Should the audio not be passed in to GameView at startup ideally?

I hit this problem as well, and I assumed it's because the LTheoryRedux object is the "App" object for LTheoryRedux, but when we run a different app like PhysicsTest, LTheoryRedux will be an empty table? Should the audio not be passed in to GameView at startup ideally?

LTheoryRedux really is just LTheoryRedux = require('States.Application') same as PhysicsTest = require('States.Application') so it should be the same. That is what bugs me out.


(PDB-2508) Update release notes for 4.0.0

Refer to this link for build results (access rights to CI server needed):
http://jenkins-enterprise.delivery.puppetlabs.net/job/enterprise_puppetdb_init-multijob_githubpr-master/580/
Test FAILed.


fix: Unable to run saveNativeModel for VWRegressionModel #1364

/azp run

Codecov Report

Merging #1366 (cd54085) into master (be49658) will decrease coverage by 5.22%.
The diff coverage is 70.00%.

@@            Coverage Diff             @@
##           master    #1366      +/-   ##
==========================================
- Coverage   84.77%   79.55%   -5.23%
==========================================
  Files         287      287
  Lines       14230    14230
  Branches      732      731       -1
==========================================
- Hits        12064    11320     -744
- Misses       2166     2910     +744

Impacted Files
Coverage Δ

...spark/ml/source/image/PatchedImageFileFormat.scala
88.88% <57.14%> (ø)

.../azure/synapse/ml/io/binary/BinaryFileFormat.scala
98.86% <100.00%> (ø)

...ft/azure/synapse/ml/vw/VowpalWabbitBaseModel.scala
100.00% <100.00%> (ø)

...synapse/ml/cognitive/TextAnalyticsSDKSchemas.scala
0.00% <0.00%> (-81.20%)
:arrow_down:

...e/synapse/ml/cognitive/FormRecognizerSchemas.scala
7.69% <0.00%> (-76.93%)
:arrow_down:

...ure/synapse/ml/cognitive/FormOntologyLearner.scala
14.89% <0.00%> (-72.35%)
:arrow_down:

.../synapse/ml/cognitive/AnomalyDetectorSchemas.scala
33.33% <0.00%> (-66.67%)
:arrow_down:

.../azure/synapse/ml/cognitive/TextAnalyticsSDK.scala
23.77% <0.00%> (-63.64%)
:arrow_down:

...oft/azure/synapse/ml/cognitive/TextAnalytics.scala
34.48% <0.00%> (-54.03%)
:arrow_down:

...ft/azure/synapse/ml/cognitive/TextTranslator.scala
33.08% <0.00%> (-48.13%)
:arrow_down:

... and 11 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update be49658...cd54085. Read the comment docs.

VW changes look good to me. Assume this ran through a unit test?

yes. The function is covered by unit test and gets run in CI build.

/azp run

/azp run

@eisber Markus, the merge is blocked because it requires Mark's approval as well and he's out of office. Can you force merge?

unfortunately I cannot. maybe @serena-ruan  can help?


failure to link 3rdparty/rijndael/librijndael.a (only in the clang specific builds)

FAILED: 3rdparty/rijndael/librijndael.a
cmd.exe /C "cd . && "C:\Program Files\CMake\bin\cmake.exe" -E rm -f 3rdparty\rijndael\librijndael.a && C:\ProgramData\chocolatey\lib\winlibs\tools\mingw64\bin\llvm-ar.exe qc 3rdparty\rijndael\librijndael.a  @CMakeFiles\rijndael.rsp && C:\ProgramData\chocolatey\lib\winlibs\tools\mingw64\bin\llvm-ranlib.exe 3rdparty\rijndael\librijndael.a && cd ."
C:\ProgramData\chocolatey\lib\winlibs\tools\mingw64\bin\llvm-ar.exe: error: unable to open '3rdparty\rijndael\librijndael.a': No such file or directory
[97/494] Building CXX object 3rdparty/vulkan/CMakeFiles/spirv-tools_obj.dir/source/binary.cpp.obj
ninja: build stopped: subcommand failed.
this might be related to the build tools i have and not be an issue of the emulator per se. clang-cl from winlibs was used.

llvm-ar.exe from winlibs is broken. It can be replaced with ar.exe from mingw
The bug is fixed in recent versions of llvm. But winlibs is slightly outdated.

thank you for the response. works as intended. closing...


SVN support removed

Hello all,
This is my first time using capistrano. Lucky or unlucky, capistrano 3 just released. I think I found a bug, maybe not. The capistrano removed svn support. I set scm to svn or subversion, but neither worked. In the gem installed folder, I can find a git.rb, but nothing related to subversion.
Can anyone help me?
cannot load such file -- capistrano/subversion.rb
/Users/Bill/.rvm/gems/ruby-2.0.0-p247/gems/capistrano-3.0.0/lib/capistrano/setup.rb:14:in load' /Users/Bill/.rvm/gems/ruby-2.0.0-p247/gems/capistrano-3.0.0/lib/capistrano/setup.rb:14:in block (2 levels) in <top (required)>'
/Users/Bill/.rvm/gems/ruby-2.0.0-p247/gems/capistrano-3.0.0/lib/capistrano/application.rb:12:in run' /Users/Bill/.rvm/gems/ruby-2.0.0-p247/gems/capistrano-3.0.0/bin/cap:3:in <top (required)>'
/Users/Bill/.rvm/gems/ruby-2.0.0-p247/bin/cap:23:in load' /Users/Bill/.rvm/gems/ruby-2.0.0-p247/bin/cap:23:in '
Tasks: TOP => production

Were these fixes included? I seem to be running into the same issues, and the latest release was after these comments. Is there a different build I should be using?
Thank you.

A slightly old technology but still in use in several places, so I figured out a way to use Subversion with Capistrano overcoming the problems with authentication to the SVN server the following way:
In file lib/capistrano/svn.rb I modified line 19 from:
to the following:
Did the same with the other methods and got a working SVN with authentication, adding the variables :svn_username and :svn_password to the deployment file.
If there is interest and the way it is done is considered fine, I can create a pull request with the changes.

Please do!
On 21 Mar 2015 5:32 pm, "Damian Serrano Thode"<EMAIL_ADDRESS>wrote:

A slightly old technology but still in use in several places, so I figured
out a way to use Subversion with Capistrano overcoming the problems with
authentication to the SVN server the following way:
In file lib/capistrano/svn.rb I modified line 19 from:
to the following:
Did the same with the other methods and got a working SVN with
authentication, adding the variables :svn_username and :svn_password to the
deployment file.
If there is interest and the way it is done is considered fine, I can
create a pull request with the changes.
—
Reply to this email directly or view it on GitHub
https://github.com/capistrano/capistrano/issues/752#issuecomment-84387523
.

Great! Added PR #1402
Made a slight change to not specify the parameters in each class method, but instead push them to the args array in the svn method if :svn_username and :svn_password are defined in the deployment file


Could not load existing sourcemap of "node_modules/paper/dist/paper-full.js".

I was trying to run it on my mac and getting this error. "Could not load existing sourcemap of "node_modules/paper/dist/paper-full.js"."

Ok. Solve it by open the
package.json, go to the watch line and change it to:
"watch": "cross-env NODE_ENV=development parcel index.html --no-hmr --open",
After --open add  "--no-source-maps". Now run
yarn
yarn watch
Fixed.


Update ItemStatPlugin with Moons of Peril items

Added Moonlight moths, Moonlight potions, cooked bream and cooked moss lizard

Duplicate of https://github.com/runelite/runelite/pull/17607

Added in https://github.com/runelite/runelite/commit/a12fec482e34693926006473d80846389b3ca51e, https://github.com/runelite/runelite/commit/d6001c3f6f8a10b505622ca1e4b6ed6294e3e607, https://github.com/runelite/runelite/commit/e791d0854b3d36371ed371830b4a60488fc2f083, https://github.com/runelite/runelite/commit/bfe21caa2f6592b1ecc75977dc5ffddc0b3f82f3


Connection is not closed by calling close()

Seems like on Chrome connection is not closed after calling close().
Chrome still shows in developer tools: "CAUTION: request is not finished yet!"  for "cancelled" request.
Google Chrome Version 60.0.3112.90
May be related to #82

Found the answer - fetch cannot be cancelled.

I'm curious - why are you using the polyfill in Chrome? It's got a native EventSource.
Can we close this issue?

@VadimDez Is it using fetch as a transport? Looks like I'm having same problem. I'm using this polyfill because of headers support that I need for authentication. Have you found a way to fix this or maybe some workaround?


Upgrade from version 1.2.1 to 1.11.1

I have upgraded the player from 1.2.1 to 1.11.1. There's an issue when trying to play Youtube videos, it instead plays Vimeo videos.
I expect all Youtube and Vimeo vidos to play depending on the url.
On the current version 1.2.1, I get a 404 error on the network tab using Chrome for this 'https://vimeo.com/api/oembed.json?url=https%3A%2F%2Fvimeo.com%2F127250231&autopause=false&autoplay=false&byline=false&portrait=false&title=false&url=https%3A%2F%2Fvimeo.com%2F127250231&loop=false'

There's an issue when trying to play Youtube videos, it instead plays Vimeo videos.

What URL are you trying to play? What props are you using? Can you recreate the problem in a forked jsFiddle? https://jsfiddle.net/sv5x3ug1

I get a 404 error on the network tab using Chrome

This looks like an issue with vimeo/player.js rather than this library. The error is from vimeo.com/... – ReactPlayer has no control over what the Vimeo player API requests.

@cookPete The issue is the preload set to true was breaking Youtube videos playing. I've recreated the issue on https://jsfiddle.net/m2yv8L4s/3/

@CookPete to give context, I'm dynamically passing urls from a server so in config I've got preload for both Youtube and Vimeo videos. In this case when loading Youtube videos, the preload video for Vimeo is also loading.

I've just noticed something that may be related. In updating from 1.11.0 to 1.11.1, I suddenly start seeing a (distorted and pixellated) soundcloud player where I'd expect a youtube player.
@eTheMan80 : Have you tried version 1.11.0 instead?


prove: Return delHashes in RemoveTargets()

The responsibility of removing the deleted hashes was on the caller
since RemoveTargets() would only remove the targets from the proof.
RemoveTargets() has enough information to also return the modified
delHashes so the function signature is changed to do so.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

38 of 48 (79.17%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.1%) to 77.584%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

prove.go
38
48
79.17%

Totals

Change from base Build<PHONE_NUMBER>:
0.1%

Covered Lines:
1509

Relevant Lines:
1945

💛  - Coveralls


Added blog for instrumentation of Apache Http Server

Introductory blog on how to instrument Apache Http Server using OpenTelemetry

Thanks @svrnm @cartermp. I have incorporated the changes as per review comments. This PR is available for review again

@DebajitDas, thanks for going through this, overall it looks good to me now!

@open-telemetry/blog-approvers Requesting to review and merge this PR.


Translation of messages with authorization errors

Backend login not translated authorization error messages:

This commit makes the messages available for translation.

Thanks for your interest in contributing to Winter CMS!
This has been discussed a few times before but it boils down to this:

Detailed authentication messages are not meant for general usage consumption; hence why they are only visible when app.debug = true. Displaying them anyways in production is a bad idea for security as it reveals vital information to attackers about the state of the user database and how close they are to getting in
The Storm library cannot reference language keys provided by the Backend module, that is coupling the separate codebases in the wrong direction and would cause issues
If we were to even consider implementing this it would need to be by first implementing more specific AuthenticationException classes and throwing them when applicable and then in the backend module catching each specific exception class to provide the translated error message for that specific exception class.

I'm going to close this and related PRs for now, but feel free to post your thoughts in response to this message and we can continue the discussion and reopen the PRs if necessary.


🌐 Add Chinese translation for docs/advanced/response-headers.md

As title

It seems this was translated at some point in another PR. So I'll close this one, but thanks for the effort! ☕


Changelog is wrong

Something went wrong in the changelog regarding 2.0.0

shouldn't it be PDF on the left hand side? And not Pdf?

thanks, fixed in 2.0.1


Can this work for Godot 4+ games with multiplayer and open world chunks?

Test chunks link: https://github.com/WithinAmnesia/ARPG/discussions/15
I'm trying to find a way to seamless load and unload chunks for a 2D multiplayer game project to make an open world with a working server using Godot 4.2.1.NET.
How can this work for multiplayer and what is needed for this to potentially work? What options can be used for chunk loading and unloading seamlessly in Godot 4.2.1.NET? Please give feedback.

GitHub issues is not the place to ask questions, help, or advertise your own project. GitHub issues is for reporting issues and feature requests for the current repository (in this instance Minedot). Your comment is not related to this repository, this means it is spam.
You should be using the Godot forum.


plumbing: istio routing for new microservices

@scanalesespinoza thinking this for url paths:
/ms/deppkg - POST -> dep-pkg-cud container
/ms/deppkg - GET -> dep-pkg-r container
Open to suggestions on this.

@sbtaylor15 works fine, I test it with:
  http:
  - match:
    - method:
          exact: POST
    redirect:
      uri: /dmadminweb/Home

And got a nice 301
[scanales@scanales-t470s ortelius-istio]$ curl -X POST -v http://<IP_ADDRESS>:30208/
*   Trying <IP_ADDRESS>...
* TCP_NODELAY set
* Connected to <IP_ADDRESS> (<IP_ADDRESS>) port 30208 (#0)
> POST / HTTP/1.1
> Host: <IP_ADDRESS>:30208
> User-Agent: curl/7.59.0
> Accept: */*
>
< HTTP/1.1 301 Moved Permanently
< location: http://<IP_ADDRESS>:30208/dmadminweb/Home
< date: Tue, 13 Apr 2021 12:46:11 GMT
< server: istio-envoy
< content-length: 0
<
* Connection #0 to host <IP_ADDRESS> left intact

I only have running the monolith, so need to deploy the other MS, thats why I ask for the meeting with you, want to check all the deployment we have

@sbtaylor15 do you think we can close this one with the quickstart video? Prob we can open a new one with the implementation of the new microservices, to having a more specific use case

Removing isto


Add min-height to collapsed v2 timeslider

This is pretty minor but I think also easy to fix.
currently when I collapse the timeslider there's a slight different in height between the collapse button and the date readout:

Adding a min-height:40px; seems to fix this issue:

Tested in FF, Chrome, and Safari

Done.


SDK improve add asset method

The add_asset method is always doing a get_asset before returning. This is not required and it should be avoided.
This is done in order to ensure that the get_asset and the add_asset methods return the same objects (or similar objects).
For instance an add_method could return a object with a pkhash field and a get_asset method could return an object with a key field. This kind of behaviour makes it very difficult to handle Timeout exceptions (if the add_asset method timeout, we retry on till the object exist using the get_asset method). That's one of the reason why a get_asset has been added at the end of the add_asset method. It is also good to have consistent responses for get/add methods.
We should investigate more to identify the assets that are really different and fix the problem at the source: in the backend or in the chaincode and update the required responses.

This would be a good idea, would be reopen when it will be needed. This issue is clearly visible and commented in the source code.


Rust highlighting doesn't support current inner-attribute syntax

(Original issue 972 created by eridius on 2014-04-09T00:03:54.385424+00:00)
The Rust language changed its inner-attribut syntax from #[attr]; to #![attr]. Pygments doesn't seem to handle this and marks up the leading # in #![attr] as an error.
I realize that Rust is still in development and having highlighting get a bit out of date is to be expected, but the obvious error markup for #![attr] is rather unfortunate. Most language changes don't get flagged as errors by syntax highlighters.

(Original comment by tshatch on 2014-04-15T17:20:40.374442+00:00)
Please see Pull Request 320, let me know if that's valid.
https://bitbucket.org/birkenfeld/pygments-main/pull-request/320/include-new-attribute-syntax-for-rust/diff

(Original comment by eridius on 2014-04-17T13:15:06.458358+00:00)
The semicolon for inner attributes should be removed. It's still valid at the moment (though not in conjunction with the "!") but it will be going away at some point.

(Original comment by tshatch on 2014-04-23T19:51:41.981117+00:00)
I don't speak rust; can you give me a syntactically valid example for what "inner" and "outer" mean?

(Original comment by eridius on 2014-04-24T07:36:00.425252+00:00)
An "outer" attribute is one that modifies the item that directly follows it in the source. An item may be a module, a type definition, a function, etc. An "inner" attribute is one that modifies the item that the attribute is contained within (and the inner attribute must be the first thing inside of the item).
For example, the following demonstrates an outer attribute for a function:
#[inline]
pub fn foo(x: int) {
    println!("foo: {}", x);
}

Whereas the following is the same function using an inner attribute:
pub fn foo(x: int) {
    #![inline]
    println!("foo: {}", x);
}

(Original comment by birkenfeld on 2014-10-07T13:25:25.138092+00:00)
Closes #972: accept "inner attribute" syntax for Rust.
→ <<cset 43c74f79c17b>>


Configurable the daemon resource requirements

What type of PR is this?

/kind feature
What this PR does / why we need it:
It makes configurable the daemon resource requirements. This is useful when the daemon requires different resource requirements due to the cluster size (e.g. number of pods is watching for).
Which issue(s) this PR fixes:

Does this PR have test?

Special notes for your reviewer:
Does this PR introduce a user-facing change?

Make the daemon resource requirements configurable.

/assign @saschagrunert

Codecov Report

Merging #1291 (c58de75) into main (e87e953) will decrease coverage by 0.02%.
The diff coverage is 0.00%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1291      +/-   ##
==========================================
- Coverage   44.80%   44.77%   -0.03%
==========================================
  Files          48       48
  Lines        5406     5409       +3
==========================================
  Hits         2422     2422
- Misses       2864     2867       +3
  Partials      120      120

It would be nice to document the new options. I'm on the fence about a test, ideally we should have everything tested (and e.g. we do have tests for webhook label changes), but the patch "just" adds a public kube type, so..shrug.
By the way, thanks a lot for doing this performance and scalability work!

It would be nice to document the new options. I'm on the fence about a test, ideally we should have everything tested (and e.g. we do have tests for webhook label changes), but the patch "just" adds a public kube type, so..shrug.

I'll add some docs and tests.

@jhrozek @pjbgf I think that I addressed all your remarks. I added some documentation and an e2e test.

/test all


netstandard1.3 support

Is there a reason the latest version (v2.0.0) dropped netstandard1.3 support? The github page still mentions netstandard1.3 support.

@Jaap-van-Hengstum I intended to have it support as many platforms as possible. Is there a particular use case where netstandard2.0 support isn't working for you?

Did you ever pull my changes in from the last build?  It should have support for the latest Core & Standard.    Is there a reason why your project is unable to upgrade its .NET framework?
I can repack it in 2 secs if needed..  but @ternerdo still hasn't pulled in my last release I believe.
Build configurations were updated and intended to break appveyor.. no surprise!

@tonerdo:  Request to change authors/owners metadata attributes!   (community vs personalized)???

@tonerdo
The reason for netstandard1.3 is that I'm still using .NET Framework 4.6.2 with VS2015.
I'm not sure if you can use netstandard2 packages with that configuration, but it doesn't work out-of-the-box. I get the following message trying to install from NuGet:

Could not install package 'ReadLine 2.0.0'. You are trying to install this package into a project that targets '.NETFramework,Version=v4.6.2', but the package does not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author.

@Jaap-van-Hengstum:  I added the v4.5 to the package last night.
Can you use the package found here and retry it?

Fixed!!!
@Jaap-van-Hengstum:
I had dropped Standard v1.3, since it has been replaced by v2.0.
Framework v4.7.x requires Windows 10 (creators or fall season) build v1703 and newer.
For backwards compatibility, Framework v4.5 / v4.6.2 & Standard v1.3 added into this build.
Requests to sustain anything older than that will be rejected!!!
References:
Issue #34

Net Standard does not work in that way.
Net Standard is like an interface and a newer standard includes older ones. So you should use the lower Net standard which fits with your requirements: older standards are not really "older", but they only have fewer classes.
That is also the best practice recommendation from Microsoft.

Closing this for it's a stale issue.


work with PyPy?

Thank you for building this amazing library. Does newspaper work with PyPy?

Good question. I suppose it depends on the requirements (Pillow, lxml).

pypy3 currently supports Python 3.2 only, and the latest version requires 3.4+.
Maybe it'll work on the python-2-head branch. Did you try?


Powerless Patch

Expanded Power should probably make windows require the glass-like quartz.

Added to TODO. Closing


Link to default child is not highlighted when another child is active

Version
3.0.3
Reproduction link
https://jsfiddle.net/3svnktq2/1/
Steps to reproduce
The setup is that 'parent' is a menu item. When you go to that item, you are redirected to the child state with default parameters. Within that child state you can modify your parameters which should result in keeping the menu item highlighted.

Click on the parent link
-> Redirected to child state with type parameter 'type1' and parent is highlighted as active state
Click on 'go to child with type2'

What is expected?
You stay in the same child state with a different parameter, keeping the parent link highlighted as the active state.
What is actually happening?
'Parent' is no longer highlighted as the active state. It is only highlighted when the type parameter is 'type1'.

This happens since version 3.0.3 of vue-router. If you change the loaded version of vue-router to 3.0.2, the behaviour is as expected. More history on this issue: https://github.com/vuejs/vue-router/issues/2717.

Despite the warning, you need to reference the parent route to get it highlighted.
  <router-link :to="{name:'parent'}">/parent</router-link> (but link doesn't work) or use the link /parent which will make the link work correctly

Referencing the parent route (and adding a redirect to the empty child) also results in no highlight when going to the child with a different parameter (https://jsfiddle.net/a5doLpvh/).
So from version 3.0.3 referencing the parent route through name is not possible? I have to reference it through the link?

if you used a named link, you are explicitly referencing the child, so it makes sense not to highlight the link if the child is not being displayed

In https://jsfiddle.net/a5doLpvh/ I am explicitly referencing the parent which has a redirect to its child. I would expect that the link stays highlighted for the same child state but with a different parameter.
Also according to the documentation found in https://router.vuejs.org/api/#exact, I would expect that any route which starts with /parent should make the 'parent' link active. Unless this is only the case with a reference to a path and not to a route name.

I'm revisiting this. What happens is that the link points to a redirected url, so it's never active. Activating such behaviour needs a bit more thinking and is part of an RFC. If you have any input for that, it will be highly appreciated once the RFC is out :)
This is a working version with no redirect: https://jsfiddle.net/o59bxs3m/
You could do the redirect manually in the created hook or the beforeEnter guard

Same happening to me. Works correctly with ver 3.0.1.

I'm marking this as a bug, the child should be indeed marked as active, whether there is a redirect or not. Playground for myself or anybody who wants to give this issue a shot: https://jsfiddle.net/posva/fj7ywzxv/

@posva Same for parent redirect, i guess: https://codesandbox.io/s/vue-router-issue-redirect-0jqwm?fontsize=14&module=%2Fsrc%2Fplugins%2Frouter%2Findex.js

@maxim-usikov the redirect should go on a child (see #2717). A route record with both component and redirect is not allowed because redirect means that the route is never reached, therefore its component is never reached. For routes with children, because we are redirecting to a child route, it can work, but the right declaration of the redirect will be on an empty child { path: '', redirect: {...} }
FYI the fix hasn't been released yet

@posva ahhh, thank you for explanation.


fix for using feathers-sequelize

This is probably a logic error?
I think you want to convert number to string?
When using the feathers-sequelize adapter, I get the error: .includes is not a function.

File is not used, will close this PR.


PK-Chunking support + Better handling of batched jobs  + surfacing errors

Making it possible to pass options into Bulk.query (to utilize PKChunking comfortably)
Surfacing errors from Bulk.prototype.query
Lazy loading query streams from job batches in order to avoid timeouts from idle open connections
Credit: some parts of this PR were copied over from MixMaxHQ's PR (https://github.com/mixmaxhq/jsforce/commit/78349443154e2228db9070ae9ee70c3360363746)
PK-Chunking Usage Sample (credit to @iyobo for the sample)
conn.bulk.query(soql, {pkChunking: {
   chunkSize: ...,
   parent:...,
   startRow: ...
}})

Hi @wearhere!
Glad you liked it :)
The portions of code you commented on were actually the ones i copied over from mixmaxhq's PR.
I'll do my best to respond, but i'm CC'ing the original author(s) so that they can respond as well.
CC @ghmeier @leonicolas

@wearhere I've made changes in accordance to your comments, though i was not sure how to simulate the relevant flow.
@ghmeier @leonicolas, because i made the changes, the comments @wearhere made are now hidden; here are the links:
https://github.com/jsforce/jsforce/pull/780#discussion_r204219083
https://github.com/jsforce/jsforce/pull/780#discussion_r204219139
https://github.com/jsforce/jsforce/pull/780#discussion_r204219203

Thats exactly right @iyobo

@david0673 There is actually something wrong with this branch.
This used to work, but now it doesn't.
sfconn.bulk.query(soql)
                .stream()
                .on('error', function (e) {
                    errHandler(e, this);
                })
                .pipe(myStream)
                .on('end', function () {
                    console.log('This ends now!')

                });

Now it just hangs and never ends. This is the case with or without the new options params.
This might also be why CI is still waiting for status to be reported.
How was this tested?

@iyobo thanks for pointing that out, this was because when conn.bulk.load receives a non Object value for options, it assumes that the value was meant to be the soql, & essentially truncates the option parameter.
I've now submitted a fix for this issue.
it is possible this is why the status from CI is not yet reported, but i'd like to believe there is a timeout set & it would've failing by now on that scenario
Previously I've tested these only by running selected flows, but now i ran:

npm run test:browser - no tests seem to run
npm run node - many successful tests but overall failed

If you look at the main branch you can see that the build is failing regardless of this branch, so i'm not sure what more i can do (within reason)

@david0673 Thanks for being awesome!
Now I'm curious if we aren't bubbling up errors as we should if the null options caused the earlier stall. That error seemed to have been swallowed.

@iyobo thanks for being flattering! 😄
that is definitely possible; one step at a time 😛

@david0673
I've seen that you added my changes in this PR.
We are near to have the PK Chunking support in JSForce :)

@leonicolas, yes, i did, as a subset of the things copied from this PR: https://github.com/mixmaxhq/jsforce/commit/78349443154e2228db9070ae9ee70c3360363746
Though i was having timeout issues related to holding the batch result streams open too early, which is why i changed it to "lazy-load" those batch result streams

@leonicolas hows it going?
@stomita anything i can do to help get this PR merged?

Hi Guys,
Any plans to merge this any time soon?
Thanks!
Josh

Hey Guys,
Any chance this makes it in soon? We are doing a pretty big migration and have to manually export the files with Data Loader as the bulk.query is troublesome with objects over 2 mil.
Thanks!
Brandon Mikeska

Hello Brandon, I have a family issue right now and cannot continue, thanks for
All your assistance.
Mamie
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10

From: Brandon Mikeska<EMAIL_ADDRESS>Sent: Thursday, April 25, 2019 2:19:08 PM
To: jsforce/jsforce
Cc: Subscribed
Subject: Re: [jsforce/jsforce] PK-Chunking support + Better handling of batched jobs + surfacing errors (#780)
Hey Guys,
Any chance this makes it in soon? We are doing a pretty big migration and have to manually export the files with Data Loader as the bulk.query is troublesome with objects over 2 mil.
Thanks!
Brandon Mikeska
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/jsforce/jsforce/pull/780#issuecomment-486804139, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AKCLYOQ44I2NI2R474I74G3PSH72ZANCNFSM4FLG5NIA.

Hello, any updates on getting this into the release?

closing this now that v1 is deprecated.
we suggest to use bulk v2 as it has handles pkchunking automatically, see: https://github.com/jsforce/jsforce/discussions/1433#discussioncomment-10063833


Make 'style' target silent

This is a short follow-up to https://github.com/dlang/phobos/pull/5199 and this PR sets calls and echos in the style target to silent as Andrei requested. A message(s) will only be printed in case of an error.
However, I am not so convinced that this is a good idea because (a) it might make debugging more difficult and (b) there will be no visual feedback for 10-15s.
Anyways here are the potential changes.
(I opened this PR because I am fine with both ways.)

ping @wilzbach
Merge conflict; please rebase.  This has been sitting here for far too long; let's get it merged!

Hmm I never really cared about this target and as no one pushed for this, I am just going to close it.
These greps were never planned to be permanent anyways and the few time I have left I want to invest in finally managing to get proper DScanner plugins merged :)


Optimization

Removed code duplication
Reworked selection system

Previous selection method worked the following way: user selects item and then file has been reselected programmatically. This patch fixes that.
Use of FileList.SelectedItem replaced with SelectedItems as we use "Extended" selection mode (look at microsoft docs)
BaseLayout.SelectedItem is just first element of BaseLayout.SelectedItems
Moved some functions to UI abstract methods
Removed code duplication
Removed cast to BaseLayout as ContentPage is typeof BaseLayout

@duke7553 I think BaseLayout should contain only UI-related code. Intercation should contain functions like copy, paste, pin item and other.
We have to decide what we will do with this PR, because if you merge this, you (or someone else) will have to port this changes to optimization branch to get merge back to master without conflicts.

@tsvietOK Would you like to join the UWP Discord so we can collaborate on Files UWP outside of issues and pull requests? https://discord.gg/Km25JR

@yaichenbaum Joined

@duke7553 Do we want to merge this pull request or should we wait?

@yaichenbaum  I like these changes a lot. But we should wait until #827 is merged to prevent conflicts with his work.


Reduce batch size to fit T5 paper

One of the things we want to understand is why does out model seem to underperform?
One thing we noticed is that learning rate/learning rate schedule is extracted from the t5 paper, but we've update the batch size to fit with Meg-DS (ie 2048 instead of 128)?
Typically learning rate is constant for the first 1e4 steps, however since t5 starts decaying at 128 * 1e4 * 512 = 655M tokens whereas we start decaying at 2048 * 1e4 * 512 = 10B tokens (which is about 1/3 of the entire training data). Can this explain the poor performances? If so, what do we so? Reduce batch size to 128? Tune the learning_rate_scheduler.warmup_steps to be 1e4 / (2048 / 128) = 6250 . I'd be in favor of reducing batch size to mimick T5 paper.
In this PR I suggest reducing the batch size back to the original paper.

I would suggest reverting this change - a batch size of 2048 should work fine (it's what we used for the final T5 models). Adafactor is roughly invariant to batch size.

Reverted in bb34fda312455b774d5ca1d38783ad37d88b4a6b

Re applied the change as we've seen promising results with this modification.


fix(modgpt): prevent out-of-scope topics

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


Error (Xcode): Framework not found audioplayers

Checklist

[X] I read the troubleshooting guide before raising this issue
[X] I made sure that the issue I am raising doesn't already exist

Current bug behaviour
I'm getting this error even when upgrading the package to the latest version and even deleting the package
Expected behaviour
No response
Steps to reproduce

Execute flutter run on the code sample
...
...

Code sample

Code sample
void main() {
}

Affected platforms
iOS
Platform details
No response
AudioPlayers Version
audioplayers: ^3.0.1
Build mode
No response
Audio Files/URLs/Sources
No response
Screenshots
No response
Logs

my relevant logs

Full Logs

my full logs or a link to a gist

Flutter doctor:
Output of: flutter doctor -v

Related issues / more information
No response
Working on PR
no way

I have added audioplayers dependency in pubspec.yaml but its adding audioplayers_darwin in generatedpluginregistrant and when i try to play using xcode then I am getting "Module 'audioplayers_darwin' not found"

Did you try a flutter clean and flutter pub cache clean and flutter pub get before running the app?

Tried but again the same issue is there
OUTPUT OF  flutter build ios
Building .......... for device (ios-release)...
Automatically signing iOS for device deployment using specified development team in Xcode project: XXXXXXXXXX
Running pod install...                                             443ms
Running Xcode build...
└─Compiling, linking and signing...                        649ms
Xcode build done.                                           27.9s
Failed to build iOS app
Parse Issue (Xcode): Module 'audioplayers_darwin' not found
................................/ios/Runner/GeneratedPluginRegistrant.m:11:8
Encountered error while building for device.

same for me

Did you try a flutter clean and flutter pub cache clean and flutter pub get before running the app?

yes, but it didn't work

FYI If you create a new flutter project, add audioplayers and try to build it in xcode, you see that error.
Latest flutter, latest xcode

FYI, moving back to XCode 14.2, it works. The issue I guess comes from XCode 14.3

Did you try this https://github.com/flutter/flutter/issues/53573#issuecomment-680265617 ?
Plz state what you have yet tried. Did you once run it from XCode and in the ios folder. Did you do a pod update ?

XCode 14.2 worked for me but now with latest flutter version, everything works on latest xcode

Same problem here:
Xcode build done.                                           18.0s
Failed to build iOS app
Error (Xcode): Framework not found audioplayers

Error (Xcode): Linker command failed with exit code 1 (use -v to see invocation)

Found the solution for this.

Open your Xcode project.
Navigate to the "Build Settings" tab.
Select the "Linking" category.
Look for the "Other Linker Flags" setting and expand it.
Find the flag that includes "audioplayers". and also remove the "-framework", before it
Remove the flag by clicking on it and pressing the delete key, or by right-clicking and selecting "Delete".
Save your changes and rebuild your project.

Should work after that, it might be because they have changed for ios.

I have the same issue. I can build and run on any physical device I have both from flutter and Xcode (14.3), but the build fails on any simulator device I tried.
Message from Xcode:
/Users/lukasnevosad/Projects/Yomio/scholis/scholis/ios/Runner/GeneratedPluginRegistrant.m:12:9: Module 'audioplayers_darwin' not found

Message when building from flutter:
Launching lib/main.dart on iPad Pro (12.9-inch) (6th generation) in debug mode...
main.dart:1
Xcode build done.                                            2.3s
Failed to build iOS app
Error output from Xcode build:
↳
    2023-05-29 08:42:23.450 xcodebuild[43714:13960633] DVTCoreDeviceEnabledState: DVTCoreDeviceEnabledState_Disabled set via user default (DVTEnableCoreDevice=disabled)
    xcodebuild: error: Unable to find a destination matching the provided destination specifier:
    		{ id:272FF786-7F03-4103-B72A-504974A814BD }
    	Available destinations for the "prod" scheme:
    		{ platform:macOS, arch:arm64, variant:Designed for [iPad,iPhone], id:00008103-000428101132001E }
    		{ platform:iOS, id:dvtdevice-DVTiPhonePlaceholder-iphoneos:placeholder, name:Any iOS Device }
Xcode's output:
↳
    Writing result bundle at path:
    	/var/folders/bx/lkj2g27x5491t9zy48cwrslr0000gn/T/flutter_tools.7pqIkG/flutter_ios_build_temp_dirEubjAX/temporary_xcresult_bundle
Could not build the application for the simulator.
Error launching application on iPad Pro (12.9-inch) (6th generation).
Exited

Regarding the solutions mentioned above, there is no mention of "audioplayers" in my project.pbxproj and flutter clean did not work either.


Fix Shader::has_uniform() always returning false

This commit fixes #64467. Note that Shader::has_param() in Godot 3.x still has the same issue.

Superseded by https://github.com/godotengine/godot/pull/64092.


Result with "greater" or "less than" is displayed wrongly, should be with < or > - signs

Example: https://github.com/hl7-be/hl7-be-fhir-laboratory-report/blob/master/testing/Macsys/815333049/81365677998_815333049_11.json

Issue made on visualiser github


Documentation usability feedback for run.md

https://github.com/GoogleContainerTools/kpt/blob/master/docs/fn/run.md

Caveats section is very long since it's explaining multiple concepts. It's probably worth creating subsection for each
Need to use verbatim code style in many instances. e.g. metadata.annotations.[config.kubernetes.io/function]. Otherwise, it's hard to read.
Config Functions -> KPT Functions ?
We should simplify number of ways to invoke functions declarativey. Or at least, emphasize one approach in docs so user doesn't get overwhelmed.
It's ambiguous whether functions directory is required or just a convention used (functions dir is in fact a special dir recognized by kpt).
Also note that the implicit pattern is currently broken: #188

This will be addressed with the docs revamp (and pipeline implementation) targeted for v1.0


update zh-CN docs

I think this modification is helpful in reading.
@Lapis-Apple please review it.

Wow..
Thanks. Really.