Deploying app with heroku fails (Application error)

After several attempts to deploy magpie backend with heroku, I am still getting an error. I followed the steps for manual deployment in the readme, and the furthest I got on an attempt was managing to create an experiment, but getting an errror when editing it ("Something went wrong")
On my last attempt I can't even access the app anymore. I'm posting the logs here, hopefully someone can figure out what's wrong :)

log
2022-10-19T16:21:18.095928+00:00 app[web.1]: 16:21:18.095 [warning] Description: 'Authenticity is not established by certificate path validation'
2022-10-19T16:21:18.095929+00:00 app[web.1]: Reason: 'Option {verify, verify_peer} and cacertfile/cacerts is missing'
2022-10-19T16:21:18.095930+00:00 app[web.1]:
2022-10-19T16:21:18.103318+00:00 app[web.1]: 16:21:18.103 [warning] Description: 'Authenticity is not established by certificate path validation'
2022-10-19T16:21:18.103319+00:00 app[web.1]: Reason: 'Option {verify, verify_peer} and cacertfile/cacerts is missing'
2022-10-19T16:21:18.103319+00:00 app[web.1]:
2022-10-19T16:21:18.119684+00:00 app[web.1]: 16:21:18.117 [notice] Application magpie exited: Magpie.Application.start(:normal, []) returned an error: shutdown: failed to start child: Magpie.Experiments.ExperimentStatusResetWorker
2022-10-19T16:21:18.119698+00:00 app[web.1]: ** (EXIT) an exception was raised:
2022-10-19T16:21:18.119698+00:00 app[web.1]: ** (Postgrex.Error) ERROR 42P01 (undefined_table) relation "experiment_statuses" does not exist
2022-10-19T16:21:18.119699+00:00 app[web.1]:
2022-10-19T16:21:18.119702+00:00 app[web.1]: query: UPDATE "experiment_statuses" AS e0 SET "status" = $1 WHERE (e0."status" = 1) AND ((e0."last_heartbeat" IS NULL) OR (e0."last_heartbeat" < $2))
2022-10-19T16:21:18.119702+00:00 app[web.1]: (ecto_sql 3.7.2) lib/ecto/adapters/sql.ex:760: Ecto.Adapters.SQL.raise_sql_call_error/1
2022-10-19T16:21:18.119703+00:00 app[web.1]: (ecto_sql 3.7.2) lib/ecto/adapters/sql.ex:693: Ecto.Adapters.SQL.execute/5
2022-10-19T16:21:18.119707+00:00 app[web.1]: (magpie 2.3.4) lib/magpie/experiments/experiment_status_reset_worker.ex:20: Magpie.Experiments.ExperimentStatusResetWorker.init/1
2022-10-19T16:21:18.119707+00:00 app[web.1]: (stdlib 3.17.1) gen_server.erl:423: :gen_server.init_it/2
2022-10-19T16:21:18.119708+00:00 app[web.1]: (stdlib 3.17.1) gen_server.erl:390: :gen_server.init_it/6
2022-10-19T16:21:18.119708+00:00 app[web.1]: (stdlib 3.17.1) proc_lib.erl:226: :proc_lib.init_p_do_apply/3
2022-10-19T16:21:19.660992+00:00 app[web.1]: {"Kernel pid terminated",application_controller,"{application_start_failure,magpie,{{shutdown,{failed_to_start_child,'Elixir.Magpie.Experiments.ExperimentStatusResetWorker',{#{'__exception__' => true,'__struct__' => 'Elixir.Postgrex.Error',connection_id => 2343542,message => nil,postgres => #{code => undefined_table,file => <<\"parse_relation.c\">>,line => <<\"1381\">>,message => <<\"relation \\"experiment_statuses\\" does not exist\">>,pg_code => <<\"42P01\">>,position => <<\"8\">>,routine => <<\"parserOpenTable\">>,severity => <<\"ERROR\">>,unknown => <<\"ERROR\">>},query => <<\"UPDATE \\"experiment_statuses\\" AS e0 SET \\"status\\" = $1 WHERE (e0.\\"status\\" = 1) AND ((e0.\\"last_heartbeat\\" IS NULL) OR (e0.\\"last_heartbeat\\" < $2))\">>},[{'Elixir.Ecto.Adapters.SQL',raise_sql_call_error,1,[{file,\"lib/ecto/adapters/sql.ex\"},{line,760},{error_info,#{module => 'Elixir.Exception'}}]},{'Elixir.Ecto.Adapters.SQL',execute,5,[{file,\"lib/ecto/adapters/sql.ex\"},{line,693}]},{'Elixir.Magpie.Experiments.ExperimentStatusResetWorker',init,1,[{file,\"lib/magpie/experiments/experiment_status_reset_worker.ex\"},{line,20}]},{gen_server,init_it,2,[{file,\"gen_server.erl\"},{line,423}]},{gen_server,init_it,6,[{file,\"gen_server.erl\"},{line,390}]},{proc_lib,init_p_do_apply,3,[{file,\"proc_lib.erl\"},{line,226}]}]}}},{'Elixir.Magpie.Application',start,[normal,[]]}}}"}
2022-10-19T16:21:19.666467+00:00 app[web.1]: Kernel pid terminated (application_controller) ({application_start_failure,magpie,{{shutdown,{failed_to_start_child,'Elixir.Magpie.Experiments.ExperimentStatusResetWorker',{#{'__exception__' => true,'__struct__' => 'Elixir.Postgrex.Error',connection_id => 2343542,message => nil,postgres => #{code => undefined_table,file => <<"parse_relation.c">>,line => <<"1381">>,message => <<"relation \"experiment_statuses\" does not exist">>,pg_code => <<"42P01">>,position => <<"8">>,routine => <<"parserOpenTable">>,severity => <<"ERROR">>,unknown => <<"ERROR">>},query => <<"UPDATE \"experiment_statuses\" AS e0 SET \"status\" = $1 WHERE (e0.\"status\" = 1) AND ((e0.\"last_heartbeat\" IS NULL) OR (e0.\"last_heartbeat\" < $2))">>},[{'Elixir.Ecto.Adapters.SQL',raise_sql_call_error,1,[{file,"lib/ecto/adapters/sql.ex"},{line,760},{error_info,#{module => 'Elixir.Exception'}}]},{'Elixir.Ecto.Adapters.SQL',execute,5,[{file,"lib/ecto/adapters/sql.ex"},{line,693}]},{'Elixir.Magpie.Experiments.ExperimentStatusResetWorker',init,1,[{f
2022-10-19T16:21:19.666600+00:00 app[web.1]:
2022-10-19T16:21:19.827109+00:00 app[web.1]: Crash dump is being written to: erl_crash.dump...done
2022-10-19T16:21:19.989731+00:00 heroku[web.1]: Process exited with status 1
2022-10-19T16:21:20.096866+00:00 heroku[web.1]: State changed from starting to crashed
2022-10-19T16:53:21.926149+00:00 heroku[web.1]: State changed from crashed to starting
2022-10-19T16:53:29.127642+00:00 heroku[web.1]: Starting process with command `_build/prod/rel/magpie/bin/magpie start`
2022-10-19T16:53:51.756944+00:00 app[web.1]: 16:53:51.756 [info] Running Magpie.Endpoint with cowboy 2.9.0 at <IP_ADDRESS>:32327 (http)
2022-10-19T16:53:51.757905+00:00 app[web.1]: 16:53:51.757 [info] Access Magpie.Endpoint at https://moderator-backend.herokuapp.com:32327
2022-10-19T16:53:51.785730+00:00 app[web.1]: 16:53:51.781 [warning] Description: 'Authenticity is not established by certificate path validation'
2022-10-19T16:53:51.785731+00:00 app[web.1]: Reason: 'Option {verify, verify_peer} and cacertfile/cacerts is missing'
2022-10-19T16:53:51.785731+00:00 app[web.1]:
2022-10-19T16:53:51.785732+00:00 app[web.1]: 16:53:51.780 [warning] Description: 'Authenticity is not established by certificate path validation'
2022-10-19T16:53:51.785732+00:00 app[web.1]: Reason: 'Option {verify, verify_peer} and cacertfile/cacerts is missing'
2022-10-19T16:53:51.785732+00:00 app[web.1]:
2022-10-19T16:53:51.785732+00:00 app[web.1]: 16:53:51.781 [warning] Description: 'Authenticity is not established by certificate path validation'
2022-10-19T16:53:51.785733+00:00 app[web.1]: Reason: 'Option {verify, verify_peer} and cacertfile/cacerts is missing'
2022-10-19T16:53:51.785733+00:00 app[web.1]:
2022-10-19T16:53:51.785734+00:00 app[web.1]: 16:53:51.781 [warning] Description: 'Authenticity is not established by certificate path validation'
2022-10-19T16:53:51.785734+00:00 app[web.1]: Reason: 'Option {verify, verify_peer} and cacertfile/cacerts is missing'
2022-10-19T16:53:51.785734+00:00 app[web.1]:
2022-10-19T16:53:51.785734+00:00 app[web.1]: 16:53:51.782 [warning] Description: 'Authenticity is not established by certificate path validation'
2022-10-19T16:53:51.785735+00:00 app[web.1]: Reason: 'Option {verify, verify_peer} and cacertfile/cacerts is missing'
2022-10-19T16:53:51.785735+00:00 app[web.1]:
2022-10-19T16:53:51.785735+00:00 app[web.1]: 16:53:51.782 [warning] Description: 'Authenticity is not established by certificate path validation'
2022-10-19T16:53:51.785735+00:00 app[web.1]: Reason: 'Option {verify, verify_peer} and cacertfile/cacerts is missing'
2022-10-19T16:53:51.785735+00:00 app[web.1]:
2022-10-19T16:53:51.785736+00:00 app[web.1]: 16:53:51.782 [warning] Description: 'Authenticity is not established by certificate path validation'
2022-10-19T16:53:51.785736+00:00 app[web.1]: Reason: 'Option {verify, verify_peer} and cacertfile/cacerts is missing'
2022-10-19T16:53:51.785736+00:00 app[web.1]:
2022-10-19T16:53:51.785736+00:00 app[web.1]: 16:53:51.783 [warning] Description: 'Authenticity is not established by certificate path validation'
2022-10-19T16:53:51.785736+00:00 app[web.1]: Reason: 'Option {verify, verify_peer} and cacertfile/cacerts is missing'
2022-10-19T16:53:51.785736+00:00 app[web.1]:
2022-10-19T16:53:51.785737+00:00 app[web.1]: 16:53:51.783 [warning] Description: 'Authenticity is not established by certificate path validation'
2022-10-19T16:53:51.785737+00:00 app[web.1]: Reason: 'Option {verify, verify_peer} and cacertfile/cacerts is missing'
2022-10-19T16:53:51.785737+00:00 app[web.1]:
2022-10-19T16:53:51.785737+00:00 app[web.1]: 16:53:51.784 [warning] Description: 'Authenticity is not established by certificate path validation'
2022-10-19T16:53:51.785737+00:00 app[web.1]: Reason: 'Option {verify, verify_peer} and cacertfile/cacerts is missing'
2022-10-19T16:53:51.785738+00:00 app[web.1]:
2022-10-19T16:53:51.785738+00:00 app[web.1]: 16:53:51.784 [warning] Description: 'Authenticity is not established by certificate path validation'
2022-10-19T16:53:51.785738+00:00 app[web.1]: Reason: 'Option {verify, verify_peer} and cacertfile/cacerts is missing'
2022-10-19T16:53:51.785738+00:00 app[web.1]:
2022-10-19T16:53:51.813604+00:00 app[web.1]: 16:53:51.784 [warning] Description: 'Authenticity is not established by certificate path validation'
2022-10-19T16:53:51.813606+00:00 app[web.1]: Reason: 'Option {verify, verify_peer} and cacertfile/cacerts is missing'
2022-10-19T16:53:51.813606+00:00 app[web.1]:
2022-10-19T16:53:51.834139+00:00 app[web.1]: 16:53:51.780 [warning] Description: 'Authenticity is not established by certificate path validation'
2022-10-19T16:53:51.834141+00:00 app[web.1]: Reason: 'Option {verify, verify_peer} and cacertfile/cacerts is missing'
2022-10-19T16:53:51.834141+00:00 app[web.1]:
2022-10-19T16:53:51.834142+00:00 app[web.1]: 16:53:51.787 [warning] Description: 'Authenticity is not established by certificate path validation'
2022-10-19T16:53:51.834142+00:00 app[web.1]: Reason: 'Option {verify, verify_peer} and cacertfile/cacerts is missing'
2022-10-19T16:53:51.834142+00:00 app[web.1]:
2022-10-19T16:53:51.834142+00:00 app[web.1]: 16:53:51.787 [warning] Description: 'Authenticity is not established by certificate path validation'
2022-10-19T16:53:51.834143+00:00 app[web.1]: Reason: 'Option {verify, verify_peer} and cacertfile/cacerts is missing'
2022-10-19T16:53:51.834143+00:00 app[web.1]:
2022-10-19T16:53:51.847159+00:00 app[web.1]: 16:53:51.813 [warning] Description: 'Authenticity is not established by certificate path validation'
2022-10-19T16:53:51.847160+00:00 app[web.1]: Reason: 'Option {verify, verify_peer} and cacertfile/cacerts is missing'
2022-10-19T16:53:51.847161+00:00 app[web.1]:
2022-10-19T16:53:51.847161+00:00 app[web.1]: 16:53:51.816 [warning] Description: 'Authenticity is not established by certificate path validation'
2022-10-19T16:53:51.847162+00:00 app[web.1]: Reason: 'Option {verify, verify_peer} and cacertfile/cacerts is missing'
2022-10-19T16:53:51.847162+00:00 app[web.1]:
2022-10-19T16:53:51.859377+00:00 app[web.1]: 16:53:51.844 [warning] Description: 'Authenticity is not established by certificate path validation'
2022-10-19T16:53:51.859378+00:00 app[web.1]: Reason: 'Option {verify, verify_peer} and cacertfile/cacerts is missing'
2022-10-19T16:53:51.859379+00:00 app[web.1]:
2022-10-19T16:53:51.941318+00:00 app[web.1]: 16:53:51.940 [notice] Application magpie exited: Magpie.Application.start(:normal, []) returned an error: shutdown: failed to start child: Magpie.Experiments.ExperimentStatusResetWorker
2022-10-19T16:53:51.941319+00:00 app[web.1]: ** (EXIT) an exception was raised:
2022-10-19T16:53:51.941327+00:00 app[web.1]: ** (Postgrex.Error) ERROR 42P01 (undefined_table) relation "experiment_statuses" does not exist
2022-10-19T16:53:51.941327+00:00 app[web.1]:
2022-10-19T16:53:51.941327+00:00 app[web.1]: query: UPDATE "experiment_statuses" AS e0 SET "status" = $1 WHERE (e0."status" = 1) AND ((e0."last_heartbeat" IS NULL) OR (e0."last_heartbeat" < $2))
2022-10-19T16:53:51.941328+00:00 app[web.1]: (ecto_sql 3.7.2) lib/ecto/adapters/sql.ex:760: Ecto.Adapters.SQL.raise_sql_call_error/1
2022-10-19T16:53:51.941328+00:00 app[web.1]: (ecto_sql 3.7.2) lib/ecto/adapters/sql.ex:693: Ecto.Adapters.SQL.execute/5
2022-10-19T16:53:51.941329+00:00 app[web.1]: (magpie 2.3.4) lib/magpie/experiments/experiment_status_reset_worker.ex:20: Magpie.Experiments.ExperimentStatusResetWorker.init/1
2022-10-19T16:53:51.941329+00:00 app[web.1]: (stdlib 3.17.1) gen_server.erl:423: :gen_server.init_it/2
2022-10-19T16:53:51.941329+00:00 app[web.1]: (stdlib 3.17.1) gen_server.erl:390: :gen_server.init_it/6
2022-10-19T16:53:51.941330+00:00 app[web.1]: (stdlib 3.17.1) proc_lib.erl:226: :proc_lib.init_p_do_apply/3
2022-10-19T16:53:53.599271+00:00 app[web.1]: {"Kernel pid terminated",application_controller,"{application_start_failure,magpie,{{shutdown,{failed_to_start_child,'Elixir.Magpie.Experiments.ExperimentStatusResetWorker',{#{'__exception__' => true,'__struct__' => 'Elixir.Postgrex.Error',connection_id => 2357846,message => nil,postgres => #{code => undefined_table,file => <<\"parse_relation.c\">>,line => <<\"1381\">>,message => <<\"relation \\"experiment_statuses\\" does not exist\">>,pg_code => <<\"42P01\">>,position => <<\"8\">>,routine => <<\"parserOpenTable\">>,severity => <<\"ERROR\">>,unknown => <<\"ERROR\">>},query => <<\"UPDATE \\"experiment_statuses\\" AS e0 SET \\"status\\" = $1 WHERE (e0.\\"status\\" = 1) AND ((e0.\\"last_heartbeat\\" IS NULL) OR (e0.\\"last_heartbeat\\" < $2))\">>},[{'Elixir.Ecto.Adapters.SQL',raise_sql_call_error,1,[{file,\"lib/ecto/adapters/sql.ex\"},{line,760},{error_info,#{module => 'Elixir.Exception'}}]},{'Elixir.Ecto.Adapters.SQL',execute,5,[{file,\"lib/ecto/adapters/sql.ex\"},{line,693}]},{'Elixir.Magpie.Experiments.ExperimentStatusResetWorker',init,1,[{file,\"lib/magpie/experiments/experiment_status_reset_worker.ex\"},{line,20}]},{gen_server,init_it,2,[{file,\"gen_server.erl\"},{line,423}]},{gen_server,init_it,6,[{file,\"gen_server.erl\"},{line,390}]},{proc_lib,init_p_do_apply,3,[{file,\"proc_lib.erl\"},{line,226}]}]}}},{'Elixir.Magpie.Application',start,[normal,[]]}}}"}
2022-10-19T16:53:53.630209+00:00 app[web.1]: Kernel pid terminated (application_controller) ({application_start_failure,magpie,{{shutdown,{failed_to_start_child,'Elixir.Magpie.Experiments.ExperimentStatusResetWorker',{#{'__exception__' => true,'__struct__' => 'Elixir.Postgrex.Error',connection_id => 2357846,message => nil,postgres => #{code => undefined_table,file => <<"parse_relation.c">>,line => <<"1381">>,message => <<"relation \"experiment_statuses\" does not exist">>,pg_code => <<"42P01">>,position => <<"8">>,routine => <<"parserOpenTable">>,severity => <<"ERROR">>,unknown => <<"ERROR">>},query => <<"UPDATE \"experiment_statuses\" AS e0 SET \"status\" = $1 WHERE (e0.\"status\" = 1) AND ((e0.\"last_heartbeat\" IS NULL) OR (e0.\"last_heartbeat\" < $2))">>},[{'Elixir.Ecto.Adapters.SQL',raise_sql_call_error,1,[{file,"lib/ecto/adapters/sql.ex"},{line,760},{error_info,#{module => 'Elixir.Exception'}}]},{'Elixir.Ecto.Adapters.SQL',execute,5,[{file,"lib/ecto/adapters/sql.ex"},{line,693}]},{'Elixir.Magpie.Experiments.ExperimentStatusResetWorker',init,1,[{f
2022-10-19T16:53:53.630569+00:00 app[web.1]:
2022-10-19T16:53:53.820013+00:00 app[web.1]: Crash dump is being written to: erl_crash.dump...done
2022-10-19T16:53:54.019167+00:00 heroku[web.1]: Process exited with status 1
2022-10-19T16:53:54.146807+00:00 heroku[web.1]: State changed from starting to crashed
2022-10-19T17:07:25.876880+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=moderator-backend.herokuapp.com request_id=f43b2522-6e56-444f-9080-86202b11824e fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https
2022-10-19T17:07:37.474367+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=moderator-backend.herokuapp.com request_id=b3e74cad-9628-40ed-b22c-cf15f275fcfc fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https
2022-10-19T17:08:38.060204+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=moderator-backend.herokuapp.com request_id=e431d400-2ab4-468c-9c7d-eaed9e8e80ee fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https
2022-10-19T17:13:17.553217+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=moderator-backend.herokuapp.com request_id=a7be2494-aa36-4fd0-a732-93ad024a0687 fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https

Hey 👋 . It seems that the databases have not been created successfully.
Have you been able to run step 9 in the instructions
heroku addons:create heroku-postgresql:hobby-dev
heroku config:set POOL_SIZE=18

And if so, what was the result?
Thanks!

Great. I should have also refered to step 13 yesterday (sorry, I was away from my computer when I replied):

Run heroku run "_build/prod/rel/magpie/bin/magpie eval 'Magpie.ReleaseTasks.db_migrate()'" (Note the ' in the command.)

Does this work?

Exactly, that also works

Hmm, what's the result then if you now try to access the app?

So now the UI shows up, I can manage my experiments, but when I create a new experiment, I get the message "Something went wrong" (experiments/1/edit endpoint)

And when you say

the furthest I got on an attempt was managing to create an experiment, but getting an errror when editing it ("Something went wrong")

What is the log?

but when I create a new experiment, I get the message "Something went wrong" (experiments/1/edit endpoint)

What's the parameters you input for creating this experiment?

I see there's an error at lib/magpie_web/views/experiment_view.ex:130: Magpie.ExperimentView.get_home_url/0. So the app doesn't know the URL at which it's deployed. Have you run step 8:

Run heroku config:set HOST="[app_name].herokuapp.com" PORT=443 CANONNICAL_URL="https://[app_name].herokuapp.com" where [app_name] is the app name (shown when you first ran heroku create, e.g. mysterious-meadow-6277, or the app name that you set at the previous step, e.g. newname).

The app_name should be moderator-backend here.

I see there's probably a typo in the instruction... Should be CANONICAL_URL instead of CANONNICAL_URL (double N)

oh wow haha that must have been the issue! It's typed correctly in the script, it was just a bit annoying to run it on windows, but next time I'll know!
Thanks a lot :)

No worries! I just fixed the README.  Unfortunately the logs don't seem to contain any information. Could you point me to the frontend you're running? I will test it against an instance I spin up.

Do you mean the repo or the netlify link?

The repo, so that I can edit the URL and point it to the instance I set up and try it out.

Sure

I was able to spin up a new app using the script at http://magpie-magpie-magpie.herokuapp.com/experiments (username and password: test), submit the results and retrieve them correctly. Could you try with a simple experiment on both websites? If it still doesn't work, maybe something was disturbed during the retries to deploy the server. Could you try deleting the app and redeploying it again? Thanks!

Hello again,
after several attempts to redeploy, in the end I managed to do it. Unfortunately I can't say what went wrong, but I suspect it had something to do with the cli I used (I tried both windows command prompt and git bash).
The connection is somewhat unstable, for example I could submit the results if I ran my experiment locally, but not from the deployed version, until I restarted the dynos, and now I still sometimes get an Application error when I try to retrieve the results (even on the app you provided), but refreshing the page a couple of times seems to work.
Thanks a lot for your help!


more than 1000 graphics,become very slow!

After loading more than 1000 graphics, scaling and other operations become very slow, how to solve?

Load less than 1000 graphics?

more than 1000 shape.

Github issues is more for developers with bug reports. For end user questions, please use https://groups.google.com/forum/#!forum/drawio


Uncaught TypeError: Cannot read property 'replace' of undefined

[Enter steps to reproduce:]

...
...

Atom: 1.21.1 ia32
Electron: 1.6.15
OS: Unknown Windows version
Thrown From: script package 3.17.2
Stack Trace
Uncaught TypeError: Cannot read property 'replace' of undefined
At C:\Users\user\.atom\packages\script\lib\runner.js:137

TypeError: Cannot read property 'replace' of undefined
    at Runner.fillVarsInArg (/packages/script/lib/runner.js:137:16)
    at /packages/script/lib/runner.js:154:34
    at Array.map (native)
    at Runner.args (/packages/script/lib/runner.js:154:18)
    at Runner.run (/packages/script/lib/runner.js:26:23)
    at Runtime.execute (/packages/script/lib/runtime.js:78:17)
    at HTMLElement.scriptRun (/packages/script/lib/script.js:98:40)
    at CommandRegistry.handleCommandEvent (~/AppData/Local/atom/app-1.21.1/resources/app/src/command-registry.js:381:36)
    at KeymapManager.module.exports.KeymapManager.dispatchCommandEvent (~/AppData/Local/atom/app-1.21.1/resources/app/node_modules/atom-keymap/lib/keymap-manager.js:621:22)
    at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (~/AppData/Local/atom/app-1.21.1/resources/app/node_modules/atom-keymap/lib/keymap-manager.js:412:28)
    at WindowEventHandler.module.exports.WindowEventHandler.handleDocumentKeyEvent (~/AppData/Local/atom/app-1.21.1/resources/app/src/window-event-handler.js:100:42)
    at HTMLDocument.<anonymous> (~/AppData/Local/atom/app-1.21.1/resources/app/src/window-event-handler.js:3:65)

Commands
     -0:12.3.0 script:run (input.hidden-input)

Non-Core Packages
script 3.17.2

any way to solve this?

i dont know but its annoying.

Same problem just happened to me, any way to solved it?

I used cygwin to compile the c file instead and it worked. I don't know how to fix this in atom

omg, the problem is so annoying

Same problem...

Same problem...

d = don't
l = love
p = problem
I d l p

Try saving the file before compiling and running it.
Hope it helps!

Same problem...

i just got this problem too

do anyone can solve it for us ?

What is the solution to this problem?

Maybe you try to run languages it couldn't support? Like C or C++.

Please help me


Added a PolicyBot for python

Added a bot that takes a policy.
added open_spiel::MakePolicyBot to pyspiel, had to change a few policy unique_ptrs to shared_ptr for this.

Hi @aliyakamercan, I believe your changes also address what is described in https://github.com/deepmind/open_spiel/pull/240. If your PR is merged before https://github.com/deepmind/open_spiel/pull/240, we could add the missing python bindings for MCCFR solvers.

Note that there are python-exposed raw pointers to Policy in function arguments, e.g. here. I'm not completely sure whether the issue described in https://pybind11.readthedocs.io/en/stable/advanced/smart_ptrs.html#std-shared-ptr applies but we should probably check this.

Hi guys, going to be merging #240 in the next hour. Does it affect this PR / overlap?

Hmm, I'm surprised changing this many pointers is necessary for this. @elkhrt , any opinion on this?

Does it affect this PR / overlap?

The reason some constructors were not exposed in https://github.com/deepmind/open_spiel/pull/240 is that they expect Policy via a shared ptr and this PR changes the holder type of Policy from unique to a shared ptr so the two PRs overlap to some extent.

Hi @inejc, @lanctot

Hi @aliyakamercan, I believe your changes also address what is described in #240. If your PR is merged before #240, we could add the missing python bindings for MCCFR solvers. cc @lanctot

I think it addresses some but not all of them. It should be easy to change the rest.

Hmm, I'm surprised changing this many pointers is necessary for this. @elkhrt , any opinion on this?

https://pybind11.readthedocs.io/en/stable/advanced/smart_ptrs.html#std-unique-ptr
It's not possible to use unique pointers as function args.  Changing the signature for MakePolicyBot required all the other changes.

Hey, this looks good to me, but I think julia_test is failing:
ERROR: LoadError: InitError: Unregistered method with key (:function, :new_initial_state, :OpenSpiel, 0x42c9f5e7c174ee9e) requested, maybe you need to precompi
le the Julia module?
Stacktrace:
 [1] error(::String) at ./error.jl:33
 [2] _get_function_pointer(::Tuple{Symbol,Symbol,Symbol,UInt64}) at /usr/local/google/home/finbarrtimbers/.julia/packages/CxxWrap/94t40/src/CxxWrap.jl:376
 [3] initialize_julia_module(::Module) at /usr/local/google/home/finbarrtimbers/.julia/packages/CxxWrap/94t40/src/CxxWrap.jl:414
 [4] __init__() at /usr/local/google/home/finbarrtimbers/tmp/open_spiel/open_spiel/julia/src/OpenSpiel.jl:24
 [5] _include_from_serialized(::String, ::Array{Any,1}) at ./loading.jl:692
 [6] _require_search_from_serialized(::Base.PkgId, ::String) at ./loading.jl:776
 [7] _require(::Base.PkgId) at ./loading.jl:1001
 [8] require(::Base.PkgId) at ./loading.jl:922
 [9] require(::Module, ::Symbol) at ./loading.jl:917
 [10] include at ./boot.jl:328 [inlined]
 [11] include_relative(::Module, ::String) at ./loading.jl:1105
 [12] include(::Module, ::String) at ./Base.jl:31
 [13] include(::String) at ./client.jl:424
 [14] top-level scope at none:6
during initialization of module OpenSpiel
in expression starting at /usr/local/google/home/finbarrtimbers/tmp/open_spiel/open_spiel/julia/test/runtests.jl:1
ERROR: Package OpenSpiel errored during testing
Stacktrace:
 [1] pkgerror(::String, ::Vararg{String,N} where N) at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/Pkg/src/Types.jl:113
 [2] #test#131(::Bool, ::Nothing, ::Cmd, ::Cmd, ::typeof(Pkg.Operations.test), ::Pkg.Types.Context, ::Array{Pkg.Types.PackageSpec,1}) at /buildworker/worker/pa
ckage_linux64/build/usr/share/julia/stdlib/v1.3/Pkg/src/Operations.jl:1372
 [3] #test at ./none:0 [inlined]
 [4] #test#62(::Bool, ::Nothing, ::Cmd, ::Cmd, ::Base.Iterators.Pairs{Union{},Union{},Tuple{},NamedTuple{(),Tuple{}}}, ::typeof(Pkg.API.test), ::Pkg.Types.Cont
ext, ::Array{Pkg.Types.PackageSpec,1}) at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/Pkg/src/API.jl:253
 [5] test(::Pkg.Types.Context, ::Array{Pkg.Types.PackageSpec,1}) at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/Pkg/src/API.jl:239
 [6] #test#58 at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/Pkg/src/API.jl:233 [inlined]
 [7] test() at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/Pkg/src/API.jl:230
 [8] top-level scope at none:1

Hi @finbarrtimbers I think this is unrelated to this PR. I ran into it as well and was able to fix it. I sent you a few messages internally, let me know if it helps.

You were right- it's due to a separate issue. Sorry for the confusion!

The code looks good- I'm merging this, and you'll get a notification in the next few days when it's in. This will most likely be on Monday.


Add support for sending events to HTTPS endpoints in Eventshub

Signing-off by : Rahul Kumar<EMAIL_ADDRESS>Fixes https://github.com/knative/eventing/issues/6840

Add support for sending events to HTTPS endpoints

Release Note

Add support for sending events to HTTPS endpoints

Docs

@pierDipi Let me explain myself whether I understand or not.

step i need to create a function that configure the sender with CA certs.
step is i need to enforce TLS sender would check and enforce TLS regardless of the "is HTTPS sink"
Right and
One question : i have to do both function implementation in sender.go file? Right!

No, I sent you the reference on where to do point 1 (options.go), point 2 is in sender.go

Hi @Rahul-Kumar-prog! Do you need any help, are the requirements clear to you?

Hey @Vishal-Chdhry yes I need help. I will contact with you on slack for some doubts. Please have a look

@Rahul-Kumar-prog do you have any updates on this?

How can we help you?

Hey @pierDipi i have talk to vishal and I got solution just little more time and I will be commit with the solution.

Thank you both!

@pierDipi have a look.

@Rahul-Kumar-prog this is blocking progress on bunch of other tasks, so we need to move forward.
are the task and comments  clear?
by when can we get a solution done?

Sorry @pierDipi i get sick past few days. I understand your comments. Give me some time I will push a comment with the solution/changes.
And again sorry for blocking

@Rahul-Kumar-prog I've sent a PR to your branch https://github.com/Rahul-Kumar-prog/reconciler-test/pull/1, please merge it

/ok-to-test

/lgtm
/approve


[bug] can't run shell/Command Api, it's program not found

Describe the bug
i can't resove my bug when i'm getting start a tauri app and useing shell api.
this is my tauri config info

my code here

i found this error in devTool when i run tauri dev

thanks
I think this may be a very simple bug, but I haven't solved it for a long time. I hope handsome brother can help me!
Reproduction
No response
Expected behavior

Platform and versions
Environment
› OS: Windows 10.0.19044 X64
› Webview2: 104.0.1293.54
› MSVC:
› Node.js: 16.13.1
› npm: 8.1.2
› pnpm: 7.3.0
› yarn: 1.22.19
› rustup: 1.25.1
› rustc: 1.62.0
› cargo: 1.62.0
› Rust toolchain: stable-x86_64-pc-windows-msvc
Packages
› @tauri-apps/cli [NPM]: 1.0.5
› @tauri-apps/api [NPM]: 1.0.2
› tauri [RUST]: 1.0.5,
Stack trace
No response
Additional context
No response

Unlike on Unix systems, on Windows "commands" like echo are no separate programs/binaries and only work inside a terminal. (they do have a special name, but i can't remember it)
In other words, instead of Command::new("echo"), you'll need Command::new("cmd").args(["/C", "echo hello"]) on windows (works on linux too, with sh -c instead of cmd /C, but there it's not needed) and of course you need to adapt the allowlist accordingly.

thanks,this requst maybe windows styterm environment, I'm try to resolve again with your method,but found the Encode Error like this.

However, this question makes me as a developer very confused, can @tauri/apps/shell Command API be compatible with windows at the framework level, makes the Command  makes the Command  API called easy,this is just my little suggestion, but thanks very much for your answer!

你的写法可能有问题，改成这样试试
{
   "scope": [
        {
            "name": "cmd",
            "cmd": "cmd",
            "args": true
          }
      ]
}


Calibre: Change URL to fosshub

FossHub is more stabler and faster than GitHub.

Why to remove hash and checver from github? Files should be identical or not?

FossHub link could use fosshub mode to get hash, and checkver from fosshub to avoid inconsistency of release time between github and fosshub.

Files are identical from all releasing sources.

Could be fosshub hash extract changed to sha1 or md5? This would distinguish fosshub hashmode at first for review. Without specifying hash.mode
My point is that lots of new contributors do not know about checkver and make everything manually (url, hashes, extracts,..) and when you see that there is sha1 or md5 hash inside manifest you know, that user ran checkver and you do not need to download that file and check it while review. (Same as in sourceforge). When you review sourceforge and you see sha256 hash you know, something is wrong.

Yes, it could, the hash extraction regex is https://github.com/lukesampson/scoop/blob/master/lib/autoupdate.ps1#L217 ($Matches.filename+'.*?"sha256":"([a-fA-F0-9]{64})"'), just change it to sth. likes "sha1":"([a-fA-F0-9]{40})" or "md5":"([a-fA-F0-9]{32})".
The hash in html is as follow:
{"n":"calibre-3.41.3.msi","r":"5cba8e83d0a6f00ad7fd0fb5","hash":{"md5":"ec913c8ea7527078c55a5012bf0bf49e","sha1":"08a624eaaccc17168a6545a55758e96dd17f426c","sha256":"727d57b5096ca236113af68a9b69a253af40676985ca63b2f2d1816800aaa022"},"s":false}

If sha1 is preferred for review, I could submit a PR to change it. For daily use, the safety of sha1 and sha256 should be identical.


Add missing reference to CAF unit test library

This PR fixes a bug in the CMake scaffold, preventing master to from compiling.

This one isn't ready to merge. On FreeBSD, I'm still getting errors:
[1/196] Building CXX object libvast/CMakeFiles/libvast.dir/src/system/accountant.cpp.o
FAILED: libvast/CMakeFiles/libvast.dir/src/system/accountant.cpp.o
/usr/bin/c++  -Dlibvast_EXPORTS -Ilibvast -I../libvast -I../aux/date/include -I../aux -isystem /usr/local/include -isystem /home/matthias/caf/libcaf_core -isystem /home/matthias/caf/libcaf_io -isystem /home/matthias/caf/libcaf_openssl -fdiagnostics-color -std=c++17 -Wall -Wextra -pedantic -ftemplate-depth=512 -ftemplate-backtrace-limit=3 -stdlib=libc++ -O2 -g -fno-omit-frame-pointer -fPIC -MD -MT libvast/CMakeFiles/libvast.dir/src/system/accountant.cpp.o -MF libvast/CMakeFiles/libvast.dir/src/system/accountant.cpp.o.d -o libvast/CMakeFiles/libvast.dir/src/system/accountant.cpp.o -c ../libvast/src/system/accountant.cpp
In file included from ../libvast/src/system/accountant.cpp:17:
../libvast/vast/logger.hpp:68:27: error: no member named 'pretty_type_name' in namespace 'caf::detail'
      return caf::detail::pretty_type_name(typeid(value_type));
             ~~~~~~~~~~~~~^
../libvast/vast/logger.hpp:75:27: error: no member named 'pretty_type_name' in namespace 'caf::detail'
      return caf::detail::pretty_type_name(typeid(T));
             ~~~~~~~~~~~~~^
In file included from ../libvast/src/system/accountant.cpp:22:
In file included from ../libvast/vast/concept/printable/vast/filesystem.hpp:16:
In file included from ../libvast/vast/filesystem.hpp:26:
../libvast/vast/expected.hpp:22:32: error: no member named 'no_error' in namespace 'caf'
constexpr auto no_error = caf::no_error;
                          ~~~~~^
3 errors generated.
ninja: build stopped: subcommand failed.

@tobim, our CMake magician, would you mind taking a look how to fix this properly?

The error on FreeBSD looks unrelated to libvast_test. I would still not merge this until the build is fixed though.


JPlayer circle player and bower

Hello
The circle player has been moved to lib and bower has that entire folder ignored. How else can we get at the CirclePlayer prototype ?

Details on the Circle Player are in the demo
The repo is here:
https://github.com/maboa/circleplayer


NuGet Gallery

Can we get this posted to Nuget?  Is it fully functional?

Sure, I can publish it this weekend.  It works fine for me, and I haven't really come across any problems with it.

@phillipsj as you will hopefully notice, this repo has been moved under the cake-contrib organisation.  I will hopefully get an initial release out over the weekend.  Feel free to bug me if you don't see anything going out.

@phillipsj I have pushed the 0.0.3 version to NuGet, just so that we have got a baseline to work from.  We can start updating this from here.


Support /tts (text to speech)

Currently the Discord text to speech function is not supported.

It should be supported

I'm assuming when you send the command. Nothing happens. In that case it probably needs sending via the bot. Will take a look later

Yeah, additionally clients like Riot will get confused with the command /tts, we'll need a new command like !discord_tts
Looks like tts is just a bool in the message object:
https://discordapp.com/developers/docs/resources/channel#create-message


Added support for page size field in php

Also update the resources directory location
Depends on https://github.com/googleapis/gax-php/pull/39

Current coverage is 81.43% (diff: 100%)

Merging #413 into master will increase coverage by 0.01%

@@             master       #413   diff @@
==========================================
  Files           185        185
  Lines          6914       6918     +4
  Methods           0          0
  Messages          0          0
  Branches        896        899     +3
==========================================
+ Hits           5630       5634     +4
  Misses         1015       1015
  Partials        269        269

Powered by Codecov. Last update 94de9f2...b4e2eb9

Fixed build, PTAL

Fixed, PTAL

LGTM


No count by default

This is a backward incompatible change which computes total table size only when Prefer: count=exact is specified. By default postgrest will now get an efficiency boost by no longer performing count(1).
I have opened this PR as a WIP. There are a number of things to consider still

When not counting we don't know the total number of rows hence do not know when to return status 206 rather than 200
RPC endpoints still return an exact count. I have to see if this hurts performance and should be suppressed like the rest or whether it's information we can include for free. Also even if it's free to include should we hide the count for consistency when the Prefer header is absent?
The PATCH verb also includes a count. Similar question to RPC: does it slow things down, should it be included without the Prefer header?
The when ranges are requested and we do not count we are unable to error with 416 when the user requests a range starting beyond the last element because we don't know what the last element is.

Closes #273

i would do it like this.

always return 200 (unless it's count and we know the total)
RPC, i think the cost is free, but still hide it so it's the same as get
PATCH, i think the cost is free, but still hide it so it's the same as get
return 200 with empty array

Currently POST doesn't return a count even if you supply Prefer: count=exact so I'll add that, but not tonight.

I think all the verbs deal with count correctly now. Ready for a last review on this PR.

looks good


Respect substreams datasource startBlock

Fixes https://github.com/graphprotocol/graph-node/issues/5615

Can we merge this? I don't have write access. Thanks in advance.


FFM-6412 - Flags with multiple prerequisites evaluating incorrectly

FFM-6412 - Flags with multiple prerequisites evaluating incorrectly
What
Fix prerequisites loop in the evaluator code
Why
Only the first parent feature is being processed by the evalator due to the loop exiting too early.
Testing
TestEvaluations_ServerSDK
The following tests now pass with this fix
Custom_SDK_:Type=BoolWith2JSON;State=Enabled;On=True;Off=False;Prereq=AlwaysOn;AlwaysOff;Return_False
Custom_SDK:Type=BoolWith2JSON;State=Enabled;On=True;Off=False;Prereq=AlwaysOn;AlwaysOnToo;Return_False
Custom_SDK:Type=BoolWith2Str;State=Enabled;On=True;Off=False;Prereq=AlwaysOn;AlwaysOnToo;Return_False
Custom_SDK:Type=BoolWith2Bool;State=Enabled;On=True;Off=False;Prereq=AlwaysOn;AlwaysOnToo;Return_False
Custom_SDK:Type=JSONWith2Bool;State=Enabled;On=Com;Off=Val;Prereq=AlwaysOn;AlwaysOnToo;Return_Val
Custom_SDK:Type=JSONWith2JSON;State=Enabled;On=Com;Off=Val;Prereq=AlwaysOn;AlwaysOff;Return_Val
Custom_SDK:Type=JSONWith2JSON;State=Enabled;On=Com;Off=Val;Prereq=AlwaysOn;AlwaysOnToo;Return_Val
Custom_SDK:Type=JSONWith2Str;State=Enabled;On=Com;Off=Val;Prereq=AlwaysOn;AlwaysOff;Return_Val
Custom_SDK:Type=JSONWith2Str;State=Enabled;On=Com;Off=Val;Prereq=AlwaysOn;AlwaysOnToo;Return_Val
Custom_SDK:Type=JSONWithJSONBool;State=Enabled;On=Com;Off=Val;Prereq=AlwaysOn;AlwaysOff;Return_Val
Custom_SDK:Type=JSONWithJSONBool;State=Enabled;On=Com;Off=Val;Prereq=AlwaysOn;AlwaysOnToo;Return_Val
Custom_SDK:Type=JSONWithJSONNum;State=Enabled;On=Com;Off=Val;Prereq=AlwaysOn;AlwaysOnToo;Return_Val
Custom_SDK:Type=JSONWithJSONStr;State=Enabled;On=Com;Off=Val;Prereq=AlwaysOn;AlwaysOff;Return_Val
Custom_SDK:Type=JSONWithJSONStr;State=Enabled;On=Com;Off=Val;Prereq=AlwaysOn;AlwaysOnToo;Return_Val
Custom_SDK:Type=NumWith2Bool;State=Enabled;On=2;Off=0.11;Prereq=AlwaysOn;AlwaysOnToo;Return_0.11
Custom_SDK:Type=NumWith2JSON;State=Enabled;On=2;Off=0.11;Prereq=AlwaysOn;AlwaysOff;Return_0.11
Custom_SDK:Type=NumWith2JSON;State=Enabled;On=2;Off=0.11;Prereq=AlwaysOn;AlwaysOnToo;Return_0.11
Custom_SDK:Type=NumWith2Str;State=Enabled;On=2;Off=0.11;Prereq=AlwaysOn;AlwaysOff;Return_0.11
Custom_SDK:Type=NumWithNumBool;State=Enabled;On=2;Off=0.11;Prereq=AlwaysOn;AlwaysOnToo;Return_0.11
Custom_SDK:Type=NumWithNumStr;State=Enabled;On=2;Off=0.11;Prereq=AlwaysOn;AlwaysOff;Return_0.11
Custom_SDK:_Type=NumWithNumStr;State=Enabled;On=2;Off=0.11;Prereq=AlwaysOn;AlwaysOnToo;Return_0.11

Codecov Report
Patch coverage has no change and project coverage change: -0.02 :warning:

Comparison is base (f972833) 60.87% compared to head (783269e) 60.86%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@             Coverage Diff              @@
##               main     #156      +/-   ##
============================================
- Coverage     60.87%   60.86%   -0.02%
- Complexity      355      356       +1
============================================
  Files            31       31
  Lines          1761     1763       +2
  Branches        194      195       +1
============================================
+ Hits           1072     1073       +1
- Misses          539      540       +1
  Partials        150      150

Impacted Files
Coverage Δ

.../main/java/io/harness/cf/client/api/Evaluator.java
85.00% <0.00%> (-0.30%)
:arrow_down:

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Error on login page: relation "public.workspaces" does not exist

I followed the directions to install the project.  On the login page I put username "myname@local" and a password.  I clicked login and got some error indicating my username was invalid.  Then I clicked "Sign up" and received this error on http://myserver:3000/login:

I tried various thing but could not resolve this error.  I wiped out the entire project folder and started over, but still I receive this error whenever the /login URL is visited.  I searched and could not find a similar report.  Any help is appreciated.

I used an unofficial Docker container instead and will not be following up on this issue.   Closing.

Hi, I met with the same problem and am wondering how you solve this problem. Can you share with me some ideas?


Create and integrate common cache service

Can you add a description of what this common cache service would do?

The above comment has been updated with a description.

Migration steps
There is now a single shared cache for Gaffer stores. This replaces the separate caches that were previously used by Named Operations and the Job Tracker. See the Cache README.
If you were previously using the Named Operations and the Job Tracker then there will be a few changes you will need to make:
Replace:
<dependency>
    <groupId>uk.gov.gchq.gaffer</groupId>
    <artifactId>job-tracker-jcs</artifactId>
    <version>gaffer.version</version>
</dependency>

<dependency>
  <groupId>uk.gov.gchq.gaffer</groupId>
  <artifactId>named-operations-library</artifactId>
  <version>${gaffer.version}</version>
</dependency>

with
<dependency>
    <groupId>uk.gov.gchq.gaffer</groupId>
    <artifactId>jcs-cache-service</artifactId>
    <version>gaffer.version</version>
</dependency>

 <dependency>
  <groupId>uk.gov.gchq.gaffer</groupId>
  <artifactId>named-operation-library</artifactId>
  <version>${gaffer.version}</version>
</dependency>

And replace the following properties in you store.properties file:
gaffer.store.job.tracker.class=uk.gov.gchq.gaffer.jobtracker.JcsJobTracker
gaffer.store.job.tracker.config.path=/path/to/config/file

with the new properties:
gaffer.store.job.tracker.enabled=true

gaffer.cache.service.class=uk.gov.gchq.gaffer.cache.impl.JcsCacheService

# Optionally provide custom cache properties
gaffer.cache.config.file=/path/to/config/file

Merged into develop.


wip: feat(ngModel): run formatters / setModelValue

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
feature
What is the current behavior? (You can also link to an open issue here)
There's currently no way to manually run the model -> view pipeline / formatters
What is the new behavior (if this is a feature change)?
An API to run the whole pipeline / the formatters is introduced.
Does this PR introduce a breaking change?
No
Please check if the PR fulfills these requirements

[ ] The commit message follows our guidelines: https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit-message-format
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

Other information:
The PR includes both a $format and a $setModelValue function. I think only one is needed, we just need to decide which one.
$format:

PRO: does the most needed thing, very straightforward: run the formatters and updates the viewValue
CON: developer must run $render manually
CON: empty classes are set even though the DOM is not updated. Could be moved to $render()
CON: no equivalent on the view -> model side (inconsistent API)

$setModelValue

PRO: equivalent to $setViewValue, runs the whole pipeline
CON: unintuitive that the function argument should / must be set to the current $modelValue, so the control does not get out of sync with the scope (same behavior as $setViewValue though)
CON: only runs $render if the viewValue has actually changed.
CON: always runs the validation, even though it might not be necessary

Both methods can handle the basic case, where an app developer wants to run the formatters the view -> model pipeline has been run, see https://github.com/angular/angular.js/issues/3407 or https://github.com/angular/angular.js/pull/5221
I personally tend to introduce $format as it has the smaller surface area and introduces fewer side effects. The full model -> view pipeline is not really needed for most cases.

@jbedard I had to revert the code that was moved to the watchActionFn, because it caused test failures. Specifcally, it caused failures when the model was updated inside ngChange or the model setter - so I think the way it's done is necessary.

What about something like $processModelValue, which is effectively the same as your setModelValue but doesn't take an argument, instead just using whatever is in th current $modelValue?

Hm, that sounds like a good in-between option. It' doesn't have a public equivalent for view -> model but $$parseAndValidate could be exposed if necessary.

Generally I prefer to keep the API consistent (it makes it much easier to wrap your head around), but in this case $processModelValue() sounds like a good idea.
BTW, I agree it makes sense to tie updateEmptyClasses() with the rendering.

Î'll update the PR then. Regarding $$updateEmptyClasses(), I thought about it again, and think it's okay that this is set before $render() is called. It's also more of an issue if we had a $format() function, because that would not have called render.
But $processModelValue calls everything in the pipeline, including $render(), so it's not a big deal that $$updateEmptyClasses() is called right before it.
On the view -> model pipeline it's also only called when the viewValue is committed, so it's also not directly tied to the actual DOM / render value.

Updated.
I left $$format and $$setModelValue as internal functions, and added a PoC autocomplete example to illustrate the use case.


Update verifiers to rely on subset of evidence

Previously the AttributesVerifier and ConfigIdVerifier were being
provided the parent structure and looking up the values themselves from
this parent structure. Now these types are provided the specific piece
of evidence they care about.

Current dependencies on/for this PR:

main

PR #1

PR #2

PR #3

PR #9

PR #10

PR #11

PR #12   👈

PR #4

This comment was auto-generated by Graphite.

With the refactor of #11 this is no longer needed


Numeric Text Nodes

Handle text nodes as part of patch instead of converting to  a string in h.
Existing tests make sure this logic is covered.
-4 bytes

@okwolf I think this will break something else, so like your other PR we'll need a test for that. The problem is I am not sure what "that" is yet.

@JorgeBucaran I've tested this out in some pens and haven't found anywhere this would affect other than the creation of nodes so far. It looked funny that this logic should be happening where it did to me. I understand why the h is responsible for filtering out certain falsey values, but I would think you'd want to pass on through the rest.

Would this also yield a very slight performance improvement from not having to create string copies for each of the numbers in your view? 🤔

@okwolf I think this looks good, let me test a few things.


gdx-freetype failed with some multi-language font

I am working with an app support Chinese, Japanese and English. I found that DroidSansFallback font from Google (systems font on Android) support all those language, mean I can use it on Android and include in iOS because it only 6MB.
But  gdx-freetype failed to display English in this font, because i want use input English and display merge English and other language at the same time, because use more than 1 font in a label not possible.
It can display fine with font NotoSansCJKjp but it cost me 17MB.
I use latest libgdx nightly include freetype: libgdx-nightly-20150129

Are you specifying the character set when generating the fonts? what
characters are you using?
On Fri, Jan 30, 2015 at 11:12 AM, Viet Dzung<EMAIL_ADDRESS>wrote:

I am working with an app support Chinese, Japanese and English. I found
that DroidSansFallback font from Google (systems font on Android) support
all those language, mean I can use it on Android and include in iOS because
it only 6MB.
But gdx-freetype failed to display English in this font, because i want
use input English and display merge English and other language at the same
time, because use more than 1 font in a label not possible.
It can display fine with font NotoSansCJKjp but it cost me 17MB.
I use latest libgdx nightly include freetype: libgdx-nightly-20150129
—
Reply to this email directly or view it on GitHub
https://github.com/libgdx/libgdx/issues/2787.

Yes, below is my code to test:
			fontGen = new FreeTypeFontGenerator(
					Gdx.files.internal("fonts/DroidSansFallback.ttf"));
			fontGenP = new FreeTypeFontParameter();
			fontGenP.size = Gdx.graphics.getWidth() / 20;
			fontGenP.characters = "目前问句:1/20 Clor";
			bmFont = fontGen.generateFont(fontGenP);

Display
		String test= "目前问句:1/20 Color";
		Assets.bmFont.draw(batch, test, Gdx.graphics.getWidth()
				/ 2.0F - Assets.bmFont.getBounds(copyright).width / 2.0F,
				Gdx.graphics.getWidth() / 10.0F);

Font from here: https://github.com/android/platform_frameworks_base/blob/master/data/fonts/DroidSansFallback.ttf
From above comment, if i use font NotoSansCJKjp or NotoSansCJKsc it display fine.

Here is the text drawn using font DroidSansFallback (v 3.00, 5,3mb+):

The font on the link you provided is older - v2.55b and smaller - about 3,3mb and it really have the issues with displaying english.

Because it from master branch of Android https://android.googlesource.com/platform/frameworks/base.git/+/master/data/fonts/ and i can't believe it error with English. Please tell me where you get that 3.0 version? And I tested that font with Word, it does support English.

I used font found by the first link in google:
https://code.google.com/p/galaxy-nexus-khmer/downloads/detail?name=DroidSansFallback.ttf
This fonts looks strange, they might be packed somehow in non-standard way (last commit in the repo from your link shows that the custom packer, e.g. when I open your font it shows English correctly, but not work with gdx-freetype, and moreover my Windows also dislike it - see no english chars at right:

From their git:

The fonts are passed through Noto's identity subsetter at
https://code.google.com/p/noto/source/browse/nototools/subset.py?r=bdd10822706b
which keeps the same functionality, but compresses tables, removes
unreachable glyphs, converts post table to version 3.0, etc.
Additionally, the DroidSansFallback fonts and MotoyaLMaru are passed through
fontcrunch.

This custom processings for font might not be compatible with freetype lib.

Yes, if use that font it will display correct.
But if i use android system font on Lollipop(My nexus 7) i will not display correctly.

fontGen = new FreeTypeFontGenerator(Gdx.files.absolute("/system/fonts/DroidSansFallback.ttf"));

This cost me 5 MB on android if use my own font.

Thats strange, someone familiar with FreeType fonts needed :(
I will try to build gdx-freetype with latest C freetype lib tomorrow and check if it will work with this fonts.

Unfortunatelly, I haven't found a way to make it work.
Just checked - Your font 2 commits behind - seems to work fine - that means the issue appears after they compress and trim their font.
Think the best solution is to post the question/issue at freetype tracker. If it's issue - it's their issue, if not - they might help with some good advice about how correct configuration to resolve it in gdx-freetype..

Four days ago gdx-freetype has been updated with freetype 2.5.5 (it was version 2.4.10 before).
Has anybody checked if this is fixed now?

I don't think it is fixed.

I just tried this again with freetype 2.6.2 and I'm afraid it still doesn't seem to work with that particular version of the font.


🐛 BUG:

Which Cloudflare product(s) does this pertain to?
Pages
What version of Wrangler are you using?
2.10.0
What operating system are you using?
Mac 12.4
Describe the Bug
When attempting to tail logs for "Pages" I receive API errors both in the wrangler command line, raw API and web UI.
Here is an example deployment where I am unable to tail logs using the command npx wrangler pages deployment tail "https://29a19e75.app-waipify-com.pages.dev" --project-name="app-waipify-com".
It is not simply only this deployment but all deployments for this "Page".

When attempting this via web UI I also receive an error:

Using Chrome inspector I collected the error message returned from the endpoint https://dash.cloudflare.com/api/v4/accounts/75461928a2b17b695d1c809221e343ac/pages/projects/app-waipify-com/deployments/6f3c13c3-2ea5-4aef-b1a1-e7c440468540/tails  :
{
  "result": null,
  "success": false,
  "errors": [
    {
      "code": 8000068,
      "message": "workers.api.error.script_not_found"
    }
  ],
  "messages": []
}

This deployment is a Next.js Edge Runtime following deployment instructions on https://developers.cloudflare.com/pages/framework-guides/deploy-a-nextjs-site/
Happy to provide any more details!

I also met

@mydracula as far as I can tell it's because the functions were unable to be run in general. I had this issue with nextjs edge deploys.

“Hi @Incognito! Thanks for flagging this. In an effort to remove stale issues so we can have better signal on current friction points, we’re closing out issues that have not been updated within the last few months. If this is still a problem, please feel free to open a new issue referencing this one. Please be sure to include an updated summary and any additional context and we will review. Thank you!”

Has the tail command been fixed? Still encountering the same error with wrangler 3.22.4.

I'm also running into this issue.

same issue


feat: Add ForkBlockNumber to config

Add ability to fork block number to config
only fork l1 block numbers

Required for https://github.com/ethereum-optimism/mocktimism/issues/8

Current dependencies on/for this PR:

main

PR #69

PR #70

PR #71

PR #74

PR #75

PR #76   👈

This comment was auto-generated by Graphite.


Disallow HTML

Currently it is possible to include malicious code 😨

Actually could just disallow all HTML tags: https://kramdown.gettalong.org/converter/remove_html_tags.html


Javascript code block does not color correctly

Hi all!
I'm using nextra to write my blog posts. There seem to be an issue when it tries to render JS block code.

The color is off. Is there some configs I've missed?

Hey @nazmifeeroz, I noticed @shuding's website has this css file added in his _app.js which should make code readability better.
I'm not sure why the default styling make the js code unreadable... maybe worth fixing.

Hey @phc5 ! That works! Thank you very much!


Handle the case where a sequence_accession is linked to multiple assembly identifiers

This is now the case for NC_003424.3. However, when requesting both ids summaries, one gave an error for the summary:
https://eutils.ncbi.nlm.nih.gov/entrez/eutils/esummary.fcgi?db=assembly&retmode=json&id=22258761,245818

I left a TODO on what to do with the case where more than one assembly id would be returned (not the case in the above example, since one of the ids is wrong anyway). For now, it just takes the first of the list.


Full screen doesn’t work on iOS for Firefox and Safari

Tested Chrome on iPhone and full screen not working either.

Darn! Will need to investigate

I'm experiencing the same! can't see it in project mode. only calibrate

Wow it works!! Thank you ♥♥♥


SNKRX

Project Link
https://github.com/a327ex/SNKRX
Project License
MIT
Steam App Ids

https://steamdb.info/app/915310/

Additional Context

Official engine source code.
https://github.com/a327ex/SNKRX/pull/6

@ToughGuyKunio I don't think this one will be possible as it requires the libsteam so which I can't distribute.
Let me know if there's a alternative way to do this.


custom builder image labels/metadata exceed max allowed size on KinD cluster w/ kubernetes v1.18

Hey kpack folks, Release Integration here
We're running into issues with cf-for-k8s cf pushing an app on our Kind clusters with kubernetes v1.18 (but not with k8s v1.16).
Here's what we're seeing when we describe our app staging pod that's attempting to use the custom builder image:
Failed to pull image "gcr.io/cf-relint-greengrass/cf-workloads/cf-default-builder@sha256:40857aa32d2fe7167c914b63648c4ac0d6f6224e1d73ac6d6148d11c9e12f8c6": rpc error: code = InvalidArgument desc = failed to pull and unpack image "gcr.io/cf-relint-greengrass/cf-workloads/cf-default-builder@sha256:40857aa32d2fe7167c914b63648c4ac0d6f6224e1d73ac6d6148d11c9e12f8c6": failed to prepare extraction snapshot "extract-876130149-3tms sha256:f0dcba2cbeedc3702b4f390963e697b06360502302ec52e0d63bcfa7235220d1": info.Labels: label key and value greater than maximum size (4096 bytes), key: containerd: invalid argument
and when we docker inspect, we can see that these 2 labels are particularly long:
"Labels": {
                "io.buildpacks.builder.metadata":
...
                "io.buildpacks.buildpack.layers" <-- this one is gigantic
...
}

Here's our relevant configuration, which we don't think is particularly crazy and had been working for us until recently: https://github.com/cloudfoundry/cf-for-k8s/blob/d8245bd07135c8d21d771e09571b7f93247b64b8/config/kpack/default-buildpacks.yml

We'd love to hear your feedback on that file and if you have any suggestions for fixes for us here; this is currently a major blocker for us.

cc @jromero

Looking at the error message text I was able to find what I believe is the source producing it and the issue referring to it.

We tried deploying on Kind with K8s v1.16.9 and the same version of cf-for-k8s. When we pushed our test node app to the platform, we were initially surprised to see that the digest for the cf-default-builder image was identical to the one created with K8s v1.18.6, but on reflection, this seems to make sense, given that the builder/stack and store definitions are all identical.
We next tried removing all of the buildpacks, with the exception of the Node JS buildpack that is required for our sample app. For reference, here is the store/stack/builder definitions we deployed:
#@ load("@ytt:data", "data")

---
apiVersion: experimental.kpack.pivotal.io/v1alpha1
kind: Store
metadata:
  name: cf-buildpack-store
spec:
  sources:
  - image: gcr.io/paketo-buildpacks/nodejs@sha256:7110ff41a35ec4d8a0fbb63e7b292c2edc7ef0e072e542cd0a58e5d179ce2605

---
apiVersion: experimental.kpack.pivotal.io/v1alpha1
kind: Stack
metadata:
  name: cflinuxfs3-stack
spec:
  id: "org.cloudfoundry.stacks.cflinuxfs3"
  buildImage:
    image: "gcr.io/paketo-buildpacks/build@sha256:84f7b60192e69036cb363b2fc7d9834cff69dcbcf7aaf8c058d986fdee6941c3"
  runImage:
    image: "gcr.io/paketo-buildpacks/run@sha256:84f7b60192e69036cb363b2fc7d9834cff69dcbcf7aaf8c058d986fdee6941c3"

---
apiVersion: experimental.kpack.pivotal.io/v1alpha1
kind: CustomBuilder
metadata:
  name: cf-default-builder
  namespace: #@ data.values.staging_namespace
spec:
  tag: #@ "{}/cf-default-builder".format(data.values.app_registry.repository_prefix)
  serviceAccount: cc-kpack-registry-service-account
  stack: cflinuxfs3-stack
  store: cf-buildpack-store
  order:
  - group:
    - id: paketo-buildpacks/nodejs

This did result in a new builder image, which had much smaller annotations:
[
    {
        ...
        "Config": {
            ...
            "Labels": {
                "io.buildpacks.builder.metadata": "{\"description\":\"Custom Builder built with kpack\",\"stack\":{\"runImage\":{\"image\":\"gcr.io/paketo-buildpacks/run@sha256:84f7b60192e69036cb363b2fc7d9834cff69dcbcf7aaf8c058d986fdee6941c3\",\"mirrors\":null}},\"lifecycle\":{\"version\":\"0.8.1\",\"api\":{\"buildpack\":\"0.2\",\"platform\":\"0.3\"}},\"createdBy\":{\"name\":\"kpack CustomBuilder\",\"version\":\"v0.0.10 (git sha: 68925eaca94becfeef006c413ebac4fde559e66c)\"},\"buildpacks\":[{\"id\":\"paketo-buildpacks/node-engine\",\"version\":\"0.0.260\",\"homepage\":\"https://github.com/paketo-buildpacks/node-engine\"},{\"id\":\"paketo-buildpacks/yarn-install\",\"version\":\"0.1.86\",\"homepage\":\"https://github.com/paketo-buildpacks/yarn-install\"},{\"id\":\"paketo-buildpacks/npm\",\"version\":\"0.1.79\",\"homepage\":\"https://github.com/paketo-buildpacks/npm\"},{\"id\":\"paketo-buildpacks/nodejs\",\"version\":\"0.0.5\",\"homepage\":\"https://github.com/paketo-buildpacks/nodejs\"}]}",
                "io.buildpacks.buildpack.layers": "{\"paketo-buildpacks/node-engine\":{\"0.0.260\":{\"api\":\"0.2\",\"layerDiffID\":\"sha256:7d57d604f4efbf533639810fc3d590b2c334382097f4cdd4c3d5bcfaf8b1bd15\",\"stacks\":[{\"id\":\"io.buildpacks.stacks.bionic\"},{\"id\":\"org.cloudfoundry.stacks.cflinuxfs3\"}],\"homepage\":\"https://github.com/paketo-buildpacks/node-engine\"}},\"paketo-buildpacks/nodejs\":{\"0.0.5\":{\"api\":\"0.2\",\"layerDiffID\":\"sha256:71dd90c6ed436af5fd5027789c76ef7bc19d71ea2b46ec602dbdbe0c6e7ee9af\",\"order\":[{\"group\":[{\"id\":\"paketo-buildpacks/node-engine\",\"version\":\"0.0.260\"},{\"id\":\"paketo-buildpacks/yarn-install\",\"version\":\"0.1.86\"}]},{\"group\":[{\"id\":\"paketo-buildpacks/node-engine\",\"version\":\"0.0.260\"},{\"id\":\"paketo-buildpacks/npm\",\"version\":\"0.1.79\"}]}],\"homepage\":\"https://github.com/paketo-buildpacks/nodejs\"}},\"paketo-buildpacks/npm\":{\"0.1.79\":{\"api\":\"0.2\",\"layerDiffID\":\"sha256:687909d9abefc647892cbe213a425cf37097f5cd96eb79987f5fab4eb8b6af18\",\"stacks\":[{\"id\":\"org.cloudfoundry.stacks.cflinuxfs3\"},{\"id\":\"io.buildpacks.stacks.bionic\"}],\"homepage\":\"https://github.com/paketo-buildpacks/npm\"}},\"paketo-buildpacks/yarn-install\":{\"0.1.86\":{\"api\":\"0.2\",\"layerDiffID\":\"sha256:25eefd03f95bf374fa44cadd0fc7a9c7ef943ba1a7faa0fc90379786e0c07b21\",\"stacks\":[{\"id\":\"org.cloudfoundry.stacks.cflinuxfs3\"},{\"id\":\"io.buildpacks.stacks.bionic\"}],\"homepage\":\"https://github.com/paketo-buildpacks/yarn-install\"}}}",
                "io.buildpacks.buildpack.order": "[{\"group\":[{\"id\":\"paketo-buildpacks/nodejs\",\"version\":\"0.0.5\"}]}]",
                "io.buildpacks.stack.id": "org.cloudfoundry.stacks.cflinuxfs3"
            }
        },
        "Architecture": "amd64",
        "Os": "linux",
        "Size":<PHONE_NUMBER>,
        "VirtualSize":<PHONE_NUMBER>,
        "GraphDriver": {
            "Data": {
                "LowerDir": "/var/lib/docker/overlay2/ed68aeaecb6b741619bb19701aaa44de0ffec69b0c9ae506925df5885fcf89db/diff:/var/lib/docker/overlay2/c0d8b46fab8cc1bd50fafb8c488bff78dfded88e7fdac52fbf3d03a6f61dc5bd/diff:/var/lib/docker/overlay2/c055453ec8328a06aea7e48fa15532749c111b36b9de976263bf51ca351451d2/diff:/var/lib/docker/overlay2/edd6efe0267833bbce1f84157c7ec0cac1cdac63e51a6d825793c84d6bd3d328/diff:/var/lib/docker/overlay2/14b725c618f9984cdbd685ca3b475ee39cad8598a5dd246411bb1db5d97ddad3/diff:/var/lib/docker/overlay2/d1999b90d1a3b57d9c63e0167e1602ed090ec4e05d9e3642fbc8961a67be3a35/diff:/var/lib/docker/overlay2/4616983ec5476539812eab442d439f404364f9c8e70c7278f9958542159ea939/diff:/var/lib/docker/overlay2/1cc6f315cab22e27897441b185a7d637764766565c7f719c702a9c780b3cc18d/diff",
                "MergedDir": "/var/lib/docker/overlay2/36d812a5c093893dfc5308adb9433af8d977568e342c5f4b509b7a6a77008f39/merged",
                "UpperDir": "/var/lib/docker/overlay2/36d812a5c093893dfc5308adb9433af8d977568e342c5f4b509b7a6a77008f39/diff",
                "WorkDir": "/var/lib/docker/overlay2/36d812a5c093893dfc5308adb9433af8d977568e342c5f4b509b7a6a77008f39/work"
            },
            "Name": "overlay2"
        },
        "RootFS": {
            "Type": "layers",
            "Layers": [
                "sha256:f0dcba2cbeedc3702b4f390963e697b06360502302ec52e0d63bcfa7235220d1",
                "sha256:7755b972f0b4f49de73ef5114fb3ba9c69d80f217e80da99f56f0d0a5dcb3d70",
                "sha256:c33cb7212a62bb159674eae50b7ace60bb7c73c70ea6f8597c72fff10189d78f",
                "sha256:7d57d604f4efbf533639810fc3d590b2c334382097f4cdd4c3d5bcfaf8b1bd15",
                "sha256:25eefd03f95bf374fa44cadd0fc7a9c7ef943ba1a7faa0fc90379786e0c07b21",
                "sha256:687909d9abefc647892cbe213a425cf37097f5cd96eb79987f5fab4eb8b6af18",
                "sha256:71dd90c6ed436af5fd5027789c76ef7bc19d71ea2b46ec602dbdbe0c6e7ee9af",
                "sha256:3ae93fd59e3e53f9d0cbea42625e12139a7fb8a59915dc23b0219a01a44e018f",
                "sha256:a7ce12a420636d1b1726e67e67055a3ead31453018be5c32019420cb9e3786ba"
            ]
        },
        "Metadata": {
            "LastTagTime": "0001-01-01T00:00:00Z"
        }
    }
]

We're not sure how this information helps, given that we are still unsure as to exactly which part of the image containerd is complaining about.

We were able to isolate the problem to Kind/containerd by pushing the cf-default-builder image to our public dockerhub repository and creating a simple deployment:

kubectl create deployment test --image relintdockerhubpushbot/cf-default-builder-test

When we inspect the resulting pod, we see the following events:
Events:
  Type     Reason     Age   From                         Message
  ----     ------     ----  ----                         -------
  Normal   Scheduled  13s   default-scheduler            Successfully assigned default/test-5dd6b896f8-6g459 to kind-control-plane
  Normal   Pulling    12s   kubelet, kind-control-plane  Pulling image "relintdockerhubpushbot/cf-default-builder-test"
  Warning  Failed     11s   kubelet, kind-control-plane  Failed to pull image "relintdockerhubpushbot/cf-default-builder-test": rpc error: code = InvalidArgument desc = failed to pull and unpack image "docker.io/relintdockerhubpushbot/cf-default-builder-test:latest": failed to prepare extraction snapshot "extract-345901367-cGhX sha256:ac0538e4e603b4d6027dabc72660256eafd203fac1be9e1ca15c7f3f2ce837d5": info.Labels: label key and value greater than maximum size (4096 bytes), key: containerd: invalid argument
  Warning  Failed     11s   kubelet, kind-control-plane  Error: ErrImagePull
  Normal   BackOff    11s   kubelet, kind-control-plane  Back-off pulling image "relintdockerhubpushbot/cf-default-builder-test"
  Warning  Failed     11s   kubelet, kind-control-plane  Error: ImagePullBackOff

We will leave the public image available for y'all to test with. It was created with this set of store/stack/builder definitions.

One last test we ran before "end of day" was to reduce the size of the annotations on the cf-default-builder image by removing the ruby buildpack from the store/builder lists, leaving the other seven buildpacks, which allowed us to successfully push an app. When we pulled and inspected the builder image, we saw that the two keys mentioned in the original issue description were shorter, but were still much longer than the 4096-byte limit mentioned in the error message.
We're not sure what that means, but it leads me to speculate that it is not the annotations we can see that is causing the problem, and that K8s/Kind/Containerd is manipulating them in some way that is pushing us over the limit.

One last test we ran before "end of day" was to reduce the size of the annotations on the cf-default-builder image by removing the ruby buildpack from the store/builder lists, leaving the other seven buildpacks, which allowed us to successfully push an app. When we pulled and inspected the builder image, we saw that the two keys mentioned in the original issue description were shorter, but were still much longer than the 4096-byte limit mentioned in the error message.
We're not sure what that means, but it leads me to speculate that it is not the annotations we can see that is causing the problem, and that K8s/Kind/Containerd is manipulating them in some way that is pushing us over the limit.

@jromero @matthewmcnew Any updates here?

Hey @jamespollard8, I don't think I have the necessary experience within the internals of k8s to understand further what is going on. I did look at the release notes between v1.18.2 and v1.18.4 and couldn't find anything that should have caused this change in behaviour. I wonder if it's worth reaching out to the k8s community devs for better understanding.

Yeah that makes sense - I think the change here is some sort of creep in number/length of labels that's not really related to v1.18.2 vs v1.18.4.
We're wondering if maybe this is more of a pack or buildpack concern. @matthewmcnew Do you think that may be the case? If so, could you help us escalate this to the proper folks?

x-linking a slack thread to this:
https://vmware.slack.com/archives/CU3LBH422/p1599843114109100

Running v1.18.2, or any earlier minor version of K8s does not exhibit this problem, even with the full store/stack/builder definition currently in cf-for-k8s.

for anyone landing here searching about 1.19.x:

yep, 1.19.1 (on Kind) does exhibit the same behavior

We found a pretty great workaround for now - details in https://github.com/cloudfoundry/cf-for-k8s/issues/444
Thanks y'all!
James

@jamespollard8 should we suggest somewhere in this repository that folks trying kpack out on kind should create their clusters w/ that configuration?
it's pretty cool that people following cf-for-k8s' instructions will have a good time (https://github.com/cloudfoundry/cf-for-k8s/commit/2079080aaaa1c75d1253c7336378b15dda715d1a), but I imagine we still should provide a good experience for those other outside cf using kpack 😁
wdyt?
thx!

I suspect our use case was fairly special, and even for our special case we were right on the borderline for having issues with this.

One last test we ran before "end of day" was to reduce the size of the annotations on the cf-default-builder image by removing the ruby buildpack from the store/builder lists, leaving the other seven buildpacks, which allowed us to successfully push an app.

Given that, I'd suspect that having an issue logged here is good enough. If people hit the info.Labels: label key and value greater than maximum size (4096 bytes), key: containerd: invalid argument error, they'll be able to find a workaround here.
But also, the fixes for KinD are already in the pipe and I'd imagine they'll get released within a few weeks.


Visual Studio 2019 Integration

Unlike show at Avalonia website, there is no option to create a UserControl in the options of Visual Studio 2019 (File -> Add -> New File).
Either there is no option to edit or view the form created, the preview stay blank.
I don't know if it is related of version VS 2019 or any other configuration.

In vs 2019 If I right click in my project and select 'add new item' I can go to Avalonia and select UserControl


immediate segfault + [OPENCL]:CL ERROR:CL_OUT_OF_RESOURCES

with master HEAD:
https://github.com/nginnever/zogminer/commit/3501698a206470da7e427e59d0227f00e27365dc
./src/zcash-miner -G
Running the test miner
[OPENCL]:Found suitable OpenCL device [GeForce GTX 960] with<PHONE_NUMBER> bytes of GPU memory
[OPENCL]:Using platform: NVIDIA CUDA
[OPENCL]:Using device: GeForce GTX 960(OpenCL 1.2 CUDA)
[OPENCL]:Printing program log
[OPENCL]:
Solving nonce<PHONE_NUMBER>000000000000000000000000000000000000000000000000000000
[OPENCL]:CL ERROR:CL_OUT_OF_RESOURCES
Solutions: 486565743
Segmentation fault (core dumped)

same here with 3501698a206470da7e427e59d0227f00e27365dc and i get also a /opt/nvidia/cuda/lib64/libOpenCL.so.1: no version information available
/src/zcash-miner: /opt/nvidia/cuda/lib64/libOpenCL.so.1: no version information available (required by ./src/zcash-miner)
./src/zcash-miner: /opt/nvidia/cuda/lib64/libOpenCL.so.1: no version information available (required by ./src/zcash-miner)
Running the test miner
[OPENCL]:Found suitable OpenCL device [GRID K520] with<PHONE_NUMBER> bytes of GPU memory
[OPENCL]:Using platform: NVIDIA CUDA
[OPENCL]:Using device: GRID K520(OpenCL 1.2 CUDA)
[OPENCL]:Printing program log
[OPENCL]:
Solving nonce<PHONE_NUMBER>000000000000000000000000000000000000000000000000000000
[OPENCL]:CL ERROR:CL_OUT_OF_RESOURCES
Solutions:<PHONE_NUMBER>
Segmentation fault (core dumped)

I get the same error also with earlier commits. Kernel is 4.4.19-29.55.amzn1.x86_64 with libnvidia-opencl.so.352.99.

nvidia-370 drivers Ubuntu 16.04 x64
[OPENCL]:Found suitable OpenCL device [GeForce GTX 1080] with<PHONE_NUMBER> bytes of GPU memory
[OPENCL]:Using platform: NVIDIA CUDA
[OPENCL]:Using device: GeForce GTX 1080(OpenCL 1.2 CUDA)
[OPENCL]:Printing program log
[OPENCL]:

[OPENCL]:CL ERROR:CL_OUT_OF_RESOURCES

Same here with Tesla K80 (12GB RAM). Looks like an Nvidia-related problem. I am running Ubuntu 14.04 x64. Here is Debugging info:
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `./src/zcash-miner -G'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007f71da0b2b47 in GPUSolver::GPUSolve200_9(unsigned char*, unsigned long, unsigned long, std::function<bool (std::vector<unsigned char, std::allocator<unsigned char> >)>, std::function<bool (GPUSolverCancelCheck)>, crypto_generichash_blake2b_state) (this=this@entry=0x7f71da8c7a00, header=header@entry=0x7f71db3c4d70 "\004",
    header_len=header_len@entry=108, nonce=nonce@entry=0, validBlock=..., cancelled=..., base_state=...) at libzogminer/gpusolver.cpp:212
212                     index_vector[i] = indices->values[s-1][i];

Thank you

Same here (GeForce GTX 970):
[OPENCL]:Using device: GeForce GTX 970(OpenCL 1.2 CUDA)
[New Thread 0x7ffff3e77700 (LWP 7261)]
[New Thread 0x7fffeb3ff700 (LWP 7262)]
[New Thread 0x7fffea9b3700 (LWP 7263)]
[New Thread 0x7fffea1b2700 (LWP 7264)]
[New Thread 0x7fffe99b1700 (LWP 7265)]
[New Thread 0x7fffe91b0700 (LWP 7266)]
[New Thread 0x7fffe89af700 (LWP 7267)]
[OPENCL]:Printing program log
[OPENCL]:
[OPENCL]:CL ERROR:CL_OUT_OF_RESOURCES
Thread 1 "zcash-miner" received signal SIGSEGV, Segmentation fault.
0x00005555557a9bd8 in GPUSolver::GPUSolve200_9(unsigned char*, unsigned long, unsigned long, std::function<bool (std::vector<unsigned char, std::allocator >)>, std::function<bool (GPUSolverCancelCheck)>, crypto_generichash_blake2b_state) (
this=this@entry=0x555555aa64a0, header=header@entry=0x55555650aeb0 "\004", header_len=header_len@entry=108, nonce=nonce@entry=0,
validBlock=..., cancelled=..., base_state=...) at libzogminer/gpusolver.cpp:212
212                     index_vector[i] = indices->values[s-1][i];

zogminer does not support nvidia


How to run 'step' in background?

Hi, I'm trying to duplicate a YAML build from Circle CI to Azure DevOps and am stuck on how to replicate the ability to run steps in the background. They have a simple background: true flag. https://circleci.com/docs/2.0/configuration-reference/#background-commands
The use case is being able to start a server, then run tests from another process against this server.
I was looking at the reference for bash commends here: https://docs.microsoft.com/en-us/azure/devops/pipelines/yaml-schema?view=azure-devops&tabs=schema#bash
Does ADO allow running steps in the background (child process started, and build continues)?
If so how?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 7458d5b2-1bb7-7d87-7ce6-2b0c430b0155
Version Independent ID: edf5bbd3-a3f0-5426-e985-31290f8afd05
Content: YAML schema - Azure Pipelines
Content Source: docs/pipelines/yaml-schema.md
Product: devops
Technology: devops-cicd
GitHub Login: @vtbassmatt
Microsoft Alias: macoope

Can we please get this burning feature supported?

@mattmazzola Were you able to get the background process running in Azure DevOps in any way ? I have the same issue and want to do this

@wejeel did you find any solution? I also need the ability to start a server in the background and close it when other tasks are done

On Azure DevOps, it gets stuck on first attempt to start the bot. I have this:

add & at the end, you will get:
``` and the process will be running.


add kamaji version 0.2.0

add kamaji version 0.2.0

Why this version isn't available under Rancher Extension Updates. And why this extension can't be installed?

@stfast because that version is not compliant with Rancher 2.10. https://github.com/rancher/partner-extensions/blob/main/index.yaml#L10
Extension needs to be migrated in order to be Vue3/Rancher 2.10 compliant, as per https://extensions.rancher.io/extensions/next/rancher-2.10-support

@stfast because that version is not compliant with Rancher 2.10. https://github.com/rancher/partner-extensions/blob/main/index.yaml#L10
Extension needs to be migrated in order to be Vue3/Rancher 2.10 compliant, as per https://extensions.rancher.io/extensions/next/rancher-2.10-support

Understand. Thank you!


Expression with same name as helper fails

If you have an expression that has the same name as a helper you've registered it blows chunks.
var Handlebars = require('handlebars');

Handlebars.registerHelper("coolHelper", function(options) {
  return "cool-->" + options.fn(this) + "<--cool";
});

Handlebars.registerHelper("title", function(options) {
  return options.fn(this);
});

var tmpl = Handlebars.compile("{{#coolHelper}}{{title}}{{/coolHelper}}");
console.log(tmpl({title:'Michael'}));

And the exceptions is...
/Users//il/tmpl/testbug.js:8
  return options.fn(this);
		 ^
TypeError: Object #<Object> has no method 'fn'
at Object.<anonymous> (/Users//il/tmpl/testbug.js:8:22)
at Object.eval (eval at <anonymous> (/Users//il/tmpl/node_modules/handlebars/dist/cjs/handlebars/compiler/javascript-compiler.js:171:23), <anonymous>:3:182)
at Object.prog [as fn] (/Users//il/tmpl/node_modules/handlebars/dist/cjs/handlebars/runtime.js:168:15)
at Object.console.log.tmpl.title (/Users//il/tmpl/testbug.js:4:34)
at Object.eval (eval at <anonymous> (/Users//il/tmpl/node_modules/handlebars/dist/cjs/handlebars/compiler/javascript-compiler.js:171:23), <anonymous>:3:278)
at ret (/Users//il/tmpl/node_modules/handlebars/dist/cjs/handlebars/runtime.js:137:30)
at ret (/Users//il/tmpl/node_modules/handlebars/dist/cjs/handlebars/compiler/compiler.js:422:21)
at Object.<anonymous> (/Users//il/tmpl/testbug.js:12:17)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)

...but, if you remove the "title" helper you get
cool-->Hello World<--cool

Helpers have precedence. If you would like to reference a context value that has the same name as a helper, then you need to use a scoped reference, i.e. {{./title}}.

Thanks Kevin. Much appreciated.


why do we both as_dict and to_dict in the base model?

What is the expected enhancement?
https://github.com/Qiskit/qiskit-terra/blob/459a6f3192fb5e1d29dde23e44edda58ac5c8bc0/qiskit/validation/base.py#L356

The short answer is a combination of backwards compatibility and (probably) inability to agree on the preferred one at the point of time it was introduced. Going back in time, the first version of the Qobj (~ 0.6) concept included as_dict, and if memory serves, shortly after some other constructs that preferred to_foo instead where introduced - and when the models were generalised, we went with providing both for compatibility.
It would be nice indeed to settle on one and deprecate the other - I don't really have a strong preference over the name as long as we are consistent (might be worth doing a round of similar purpose methods and use them as a decision point).

I agree lets choose one. I prefer to_dict. @ajavadia what about you.

Yes to_dict() is fine, and it seems it has already superseded as_dict() for the most part.

ok cool lets deprecate the as_dict


Optimize load times by defaulting object types to zip segment

In practice, the vast majority of AFF4 objects are zip segments.  This PR adds an optimization where by default AFF4_TYPE properties are assumed to be AFF4_ZIP_SEGMENT_TYPE if no other type is defined.  This prevents a map insertion for every single zip segment, which can drastically speed up image loading when dealing with images with large numbers of segments

I think this is reasonable but should we also have a fatal check when loading an RDF document if an object has no type attribute?  Zip segments are never written into RDF and this change requires everything else to always have a type (which it should anyway).

That's not a bad idea, but an extra check like that might slow things down which would defeat the purpose.  Like you said, for standards compliant images, all objects in the RDF MUST have a type.

The check would only apply on objects which are stored in the RDF (Zip segments are not) so there are not many of them. I am just worried about things getting confused by feeding in an invalid RDF.
On second thoughts it might not be an issue because even if we think something is a zip segment we wont be able to do anything with it because we dont have a zip info struct for it (which can only be populated from reading the CD).


Consider having a consistent naming of http headers

Would probably make it easier to access them in an environment that doesn't honor the case-insensitive semantics of HTTP headers by default, e.g. scalyr log parsers?

I am bit conflicted. We already "fake" the request URI but it would be nice to stick to what we got from the header.

I think I agree. I basically prefer the upper title case variant, i.e. If-Modified-Since rather than the lower case version if-modified-since. But it's impossible to reliably transform lower case to upper e.g. x-flow-id could be X-Flow-Id or X-Flow-ID.
I guess we just drop this one.


pluginhook to receive branches different than master

I need an option to receive multiple versions of the same application in an easy for the developer way (so branches instead of remotes). This patch allows me to do this:
#!/bin/bash

reference_app=$1
refname=$3
newrev=$2
APP=${refname/*\//}.$reference_app

if [[ ! -d "$DOKKU_ROOT/$APP" ]]; then
  REFERENCE_REPO="$DOKKU_ROOT/$reference_app
  git clone --bare --shared --reference "$REFERENCE_REPO" "$REFERENCE_REPO" "$DOKKU_ROOT/$APP" > /dev/null
fi
pluginhook receive-app $APP $newrev

I would leave the warning in the code but I don’t know how to check if any plugin handled the event. I’d use the same approach as with DOKKU_NOT_IMPLEMENTED_EXIT, but it’s too much hassle.

FWIW -1 on this
This represents a serious breakage of the contract provided by the deployment interface to me.

@alessio, it doesn’t change anything by default. My script is just an example. If it doesn’t fit your point of view, you don’t have to use it, that’s the beauty of pluginhooks :)

I wonder, can we provide a fallback pluginhook that provides the current output?

you could do something like
if test -f /var/lib/dokku/plugins/enabled/*/receive-branch; then
  pluginhook receive-branch $APP $newrev $refname
else
  echo $'\e[1G\e[K'"-----> WARNING: deploy did not complete, you must push to master."
  echo $'\e[1G\e[K'"-----> for example, try 'git push <dokku> ${refname/refs\/heads\/}:master'"
fi

@mlebkowski mind updating your PR with @michaelshobbs suggestion? I'm a fan of that :)

I’ve updated the patch with @michaelshobbs suggestion

Can you restart your tests?

This might need to be rebased to get tests to pass....

@michaelshobbs, yeah, I just realised that…

@mlebkowski will you add this plugin hook to the docs?


cargo run arguments

When running cargo run -- [arguments], the arguments after the -- are not being sent to the binary application.
For example, if my application expects a -h argument, I think I'm supposed to type cargo run -- -h. But when I do, cargo prints out the help information as if I typed cargo run -h.
But if I run something such as cargo run -- sometext the argument is passed to the binary as expected.
I tried looking through any existing issues and Issue #2213 looks like it may be related to my problem, but it's over a year old.

Just found #2898.


Call refresh on addthis after directive is loaded

Fixes AddThis panel not loading if user views landing page first.

:+1:


Different message from vscode and terminal

I have installed tlint globally and tighten-lint for vscode. I setup tlint.json in the project root. But it seems the plugin not reading tlint.json, for example I prefer to disabled the SpaceAfterSoleNotOperator. my code looks something like this
if(!$this->auth->userid()){       return redirect('logout');     }
in vscode at problems tabs showing "tighten-lint: ! No parenthesis on empty instantiations (NoParensEmptyInstantiations)" but if I run via terminal there is no error which is correct that I ignore that specific rule.
I'm missing something ?

@shafarizkyf could you open this issue on https://github.com/d9705996/vscode-tighten-lint ?

ah sure, I was searching for that plugin repo but didn't find it.


Introduce public API to call type coercion

Which issue does this PR close?

Closes https://github.com/apache/arrow-datafusion/issues/3708
Rationale for this change
See https://github.com/apache/arrow-datafusion/issues/3708
What changes are included in this PR?

Add a public coerce_expr function and a basic test

Note I plan to add better documentation / examples via https://github.com/apache/arrow-datafusion/issues/3740 / https://github.com/apache/arrow-datafusion/pull/3741
Are there any user-facing changes?
New API

labeler CI failure is unrelated https://github.com/apache/arrow-datafusion/issues/3743

I have had some thoughts about this API and want to try something different

Closing in favor of https://github.com/apache/arrow-datafusion/pull/3758


The WAR failed to start in Tomcat

I build the WAR from source code. When I try to deploy the WAR through brooklyn, it started but I can not connect to the broker. I checked the tomcat startup log, there is errors. Then I tried to deploy the WAR in a local tomcat directly, there is also errors. The log is as follows. My environment is jdk1.8 and tomcat 8.
12-Nov-2015 11:27:34.092 INFO [main] org.apache.catalina.core.AprLifecycleListener.initializeSSL OpenSSL successfully initialized (OpenSSL 1.0.1m 19 Mar 2015)
12-Nov-2015 11:27:34.378 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-apr-8080"]
12-Nov-2015 11:27:34.407 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["ajp-apr-8009"]
12-Nov-2015 11:27:34.412 INFO [main] org.apache.catalina.startup.Catalina.load Initialization processed in 2481 ms
12-Nov-2015 11:27:34.467 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service Catalina
12-Nov-2015 11:27:34.468 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet Engine: Apache Tomcat/8.0.26
12-Nov-2015 11:27:34.540 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployWAR Deploying web application archive D:\workspace\apache-tomcat-8.0.26\webapps\brooklyn-service-broker.war
12-Nov-2015 11:27:50.037 INFO [localhost-startStop-1] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
12-Nov-2015 11:27:50.085 SEVERE [localhost-startStop-1] org.apache.catalina.core.ContainerBase.addChildInternal ContainerBase.addChild: start:
 org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/brooklyn-service-broker]]
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
	at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:725)
	at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:701)
	at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:717)
	at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:945)
	at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1768)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.NullPointerException
	at org.eclipse.jetty.websocket.jsr356.server.deploy.WebSocketServerContainerInitializer.isEnabled(WebSocketServerContainerInitializer.java:122)
	at org.eclipse.jetty.websocket.jsr356.server.deploy.WebSocketServerContainerInitializer.onStartup(WebSocketServerContainerInitializer.java:137)
	at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5156)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
	... 10 more

12-Nov-2015 11:27:50.088 SEVERE [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployWAR Error deploying web application archive D:\workspace\apache-tomcat-8.0.26\webapps\brooklyn-service-broker.war
 java.lang.IllegalStateException: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/brooklyn-service-broker]]
	at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:729)
	at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:701)
	at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:717)
	at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:945)
	at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1768)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)

12-Nov-2015 11:27:50.094 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployWAR Deployment of web application archive D:\workspace\apache-tomcat-8.0.26\webapps\brooklyn-service-broker.war has finished in 15,553 ms
12-Nov-2015 11:27:50.101 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory D:\workspace\apache-tomcat-8.0.26\webapps\docs

Is there any suggestion about this error?
Thanks.

I succeed to deploy the WAR through cloudfoundry using cf push command and register the broker to cloudfoundry. But there is still error when deploying from brooklyn using blueprint. Tomcat start with error above.

That log isn't very helpful, I'm afraid, it could be for any number of reasons.  The recommended approach is to deploy to CF, but I'm just taking a look at deploying it with Brooklyn now.  First thing I can see is that Brooklyn is installing Java 1.6, so that won't work, I'll dig deeper and see if I can get it working then share what I did.

incidentally, it comes with a built in jetty application server so you can run:
java -jar brooklyn-service-broker.war

putting your properties in application.properties

I found the issue:  Since it comes with an embedded server you need to specify in build.gradle that it is a provided dependency.
providedRuntime("org.springframework.boot:spring-boot-starter-jetty:1.2.5.RELEASE")

rather than
compile("org.springframework.boot:spring-boot-starter-jetty:1.2.5.RELEASE")

providedRuntime is supposed to allow it to work in both settings, but it seems in this case it doesn't, which is why it has been left as compile.


[🐞] Error Boundary Issue

Which component is affected?
Qwik Runtime
Describe the bug
Using ErrorBoundary (which is not documented) leads to symbol not found error:

Reproduction
https://github.com/tzdesign/qwik-error-boundary-issue
Steps to reproduce
pnpm install && pnpm preview
System Info
System:
    OS: macOS 14.5
    CPU: (14) arm64 Apple M3 Max
    Memory: 4.50 GB / 36.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.12.2 - /usr/local/bin/node
    Yarn: 1.22.22 - ~/Library/pnpm/yarn
    npm: 10.5.0 - /usr/local/bin/npm
    pnpm: 9.0.5 - ~/Library/pnpm/pnpm
  Browsers:
    Chrome: 124.0.6367.207
    Edge: 124.0.2478.105
    Safari: 17.5
  npmPackages:
    @builder.io/qwik: ^1.5.4 => 1.5.4
    @builder.io/qwik-city: ^1.5.4 => 1.5.4
    typescript: 5.4.5 => 5.4.5
    undici: * => 6.16.1
    vite: ^5.2.10 => 5.2.11

Additional Information
It's also odd that qwik has a component ErrorBoundary created by Manu, but does not export it.
If I have time a bit this week, I might write docs about the error boundary.

@PatrickJS @wmertens you know if we are able to use useErrorBoundery in the future?
I might listen to qerror for now. I read the code, but I probably don't understand the issue with the log.
Still remains in 1.9.1

@Varixo does the errorboundary work in v2?

I have this warning in dev mode but it's working fine in dev and preview with v2.
QWIK WARN You are trying to add an event "onError-boundary$" using `useOn` hook, but a node to which you can add an event is not found. Please make sure that the component has a valid element node.

v2 will be release soon so I marked this issue with STATUS-3: solved by V2, thanks.