[language][vm] non-recursive serializer/deserializer implementation for SignatureToken

Summary
SignatureToken can be deeply nested, causing the deserializer to overflow its stack. This implements a non-recursive deserializer for SignatureToken, using Vec for memory management, simulating the program stack.
Test Plan
cargo test
Note: Still a WIP. Implementation is complete & tests are passing, but still need to check in the fuzzer artifact and see if it can handle that.

@dariorussi It's complete and I'm doing some final cleanup and debugging right now. (We no longer overflow at 2000 layers, but do at 30K layers. I'm trying to understand what's happening.)

what happened to the nice explanation surrounding the code change : o

@mimoo Too much type theory jargon? I also felt it was a lot more verbose than I initially expected so I agreed with Dario on removing it. Do you find it helpful?
Alternatively I can try to rewrite something in plain language, but not sure if it's gonna be significantly better...

Let me add a line like "... the algorithm works by storing partially constructed types on a stack" followed by the stack transition example.

@bors-libra r=dariorussi

:pushpin: Commit 2811a34 has been approved by dariorussi

:hourglass: Testing commit 2811a34ea1b06569303a609dfe3a448b8a0eeef4 with merge ddf372ae26a704694d5c3fb8f3511e2fa4b4f681...

:sunny: Test successful - checks-actions_land_blocking_test, checks-circle_commit_workflow
Approved by: dariorussi
Pushing ddf372ae26a704694d5c3fb8f3511e2fa4b4f681 to master...

@mimoo Too much type theory jargon? I also felt it was a lot more verbose than I initially expected so I agreed with Dario on removing it. Do you find it helpful?

yes I actually find these really helpful : (


AsterNET .NET Core support

Is there any  plans to port AsterNET and AsterNET.Extensions to .NET Core?

#160 was submitted to address this, but closed by the PR requester.

Can you confirm that #164 solved this issue?

Apologies, I forgot about that one.
This does highlight however that there's not travis support in the current master branch for .net core.

#186

Hi All,
I haven't had any experience with Travis myself, but reading their support forum does This See Sample not resolve the Travis issue?

Only way to know is create a fork with the modified travis file, see if it builds it correctly

#213 says that this works. @brook2006 can you confirm?

I ran it on Net Core 3.0 project, although there is a warning:
I tried to:

CommandAction "pjsip show aors"
get cdr events
ExtensionStateAction
OriginateAction

it works as my expected..
still hoping it purely support Net Core 3.x, so don't get the warning anymore
== warning ===
"Warning		Package 'AsterNET 1.3.0' was restored using '.NETFramework,Version=v4.6.1, .NETFramework,Version=v4.6.2, .NETFramework,Version=v4.7, .NETFramework,Version=v4.7.1, .NETFramework,Version=v4.7.2, .NETFramework,Version=v4.8' instead of the project target framework '.NETCoreApp,Version=v3.0'. This package may not be fully compatible with your project"

#213 says that this works. @brook2006 can you confirm?

I haven't touched this since I last replied. So can't confirm, sorry..


⚠ Bofrost.at has degraded performance

In 9a9aab1, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1180 ms

Resolved: Bofrost.at performance has improved in 57d6db6.


[Feature] Add a onNodeSelected callback

Maybe i am missing something, but i could not find a way to trigger some actions when a node is selected ( In the following example, when by example "Titre 1" is selected)

Here is the example of that
http://azizali.com/react-super-treeview/examples/#checkbox

Is there a way to hide the checkboxes, while keeping the same behavior ?

Something puzzles me. Using your example, if I click anywhere on a node line (starting from the checkbox and ending with the X mark), the callback is fired. In my case, the event is fired only if I click on the check box. The only difference I see is that i set isDeletable to false....

That would be great :)
Le mer. 29 août 2018 à 17:49, Aziz Ali<EMAIL_ADDRESS>a écrit :

Oh so like making the select feature on click of the label and not show the
check box?
This is not currently possible but I can add that in the next version.
On Wed, Aug 29, 2018, 10:03 AM Gervasoni<EMAIL_ADDRESS>wrote:

Is there a way to hide the checkboxes, while keeping the same behavior ?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<
https://github.com/azizali/react-super-treeview/issues/12#issuecomment-416986302
,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/ACfoLKq3bNVf2CqtiXL1l2Z-fd9PLFo5ks5uVq0ugaJpZM4WPvyT
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/azizali/react-super-treeview/issues/12#issuecomment-417001430,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAQztPT6xE2mXmDauAlfVbkmZLhNmMoxks5uVrfzgaJpZM4WPvyT
.

Agreed, I would like this feature as well.

any update on this feature?


Support HTCondor's funky _ schemes

HTCondor will, in some cases, add an _ character into the file transfer scheme.  When this occurs, transfers with the OSDF plugin will fail.
See the following bug report: https://opensciencegrid.atlassian.net/browse/HTCONDOR-1731
Here's how we solved it for HTTP: https://opensciencegrid.atlassian.net/browse/HTCONDOR-1011
It's an ugly solution -- simply "corrects" the URL prior to feeding it to the URL parsing library.  Can we pull the same stunt for OSDF as well?

@CohenQU - can you please take a look at this?

Sure.


[Bug] Stack overflow ved oppdatering av event

Får en stack-overflow feil ved oppdatering av events i produksjon (se bilde). Gjelder oppdatering av arrangementer etter at avmeldingsfrist har gått ut.

2021-08-17T17:43:31.914Z ERROR - Container for lepton-prod-api_web_0_7dda0781 site lepton-prod-api is unhealthy, Stopping site.
2021-08-17T17:43:31.915Z INFO  - Stopping site lepton-prod-api because it is not healthy.
2021-08-17T17:43:29.454381835Z Fatal Python error: Cannot recover from stack overflow.
2021-08-17T17:43:29.455172436Z
2021-08-17T17:43:29.455816836Z Current thread 0x00007fd4e0cbc700 (most recent call first):
2021-08-17T17:43:29.461549139Z   File "/usr/local/lib/python3.6/collections/__init__.py", line 609 in update
2021-08-17T17:43:29.466965742Z   File "/usr/local/lib/python3.6/collections/__init__.py", line 535 in __init__
2021-08-17T17:43:29.471692044Z   File "/usr/local/lib/python3.6/site-packages/django/db/models/sql/query.py", line 2357 in __init__
2021-08-17T17:43:29.476727747Z   File "/usr/local/lib/python3.6/site-packages/django/db/models/sql/query.py", line 1377 in _add_q
2021-08-17T17:43:29.481674649Z   File "/usr/local/lib/python3.6/site-packages/django/db/models/sql/query.py", line 1360 in add_q
2021-08-17T17:43:29.485125151Z   File "/usr/local/lib/python3.6/site-packages/django/db/models/query.py", line 969 in _filter_or_exclude_inplace
2021-08-17T17:43:29.489913753Z   File "/usr/local/lib/python3.6/site-packages/django/db/models/query.py", line 962 in _filter_or_exclude
2021-08-17T17:43:29.493500155Z   File "/usr/local/lib/python3.6/site-packages/django/db/models/query.py", line 942 in filter
2021-08-17T17:43:29.500854058Z   File "/usr/local/lib/python3.6/site-packages/django/db/models/base.py", line 906 in _do_update
2021-08-17T17:43:29.501852859Z   File "/usr/local/lib/python3.6/site-packages/django/db/models/base.py", line 873 in _save_table
2021-08-17T17:43:29.510048763Z   File "/usr/local/lib/python3.6/site-packages/django/db/models/base.py", line 792 in save_base
2021-08-17T17:43:29.512935764Z   File "/usr/local/lib/python3.6/site-packages/django/db/models/base.py", line 754 in save
2021-08-17T17:43:29.515912566Z   File "/usr/src/app/content/signals.py", line 27 in run_celery_tasks_for_event
2021-08-17T17:43:29.519411568Z   File "/usr/src/app/content/signals.py", line 20 in send_event_reminders
2021-08-17T17:43:29.522178969Z   File "/usr/src/app/util/utils.py", line 41 in wrapper
2021-08-17T17:43:29.527567472Z   File "/usr/local/lib/python3.6/site-packages/django/dispatch/dispatcher.py", line 179 in <listcomp>
2021-08-17T17:43:29.531942274Z   File "/usr/local/lib/python3.6/site-packages/django/dispatch/dispatcher.py", line 179 in send
2021-08-17T17:43:29.535790176Z   File "/usr/local/lib/python3.6/site-packages/django/db/models/base.py", line 803 in save_base
2021-08-17T17:43:29.537905677Z   File "/usr/local/lib/python3.6/site-packages/django/db/models/base.py", line 754 in save
2021-08-17T17:43:29.541549279Z   File "/usr/src/app/content/signals.py", line 27 in run_celery_tasks_for_event
2021-08-17T17:43:29.544551080Z   File "/usr/src/app/content/signals.py", line 20 in send_event_reminders
2021-08-17T17:43:29.546340081Z   File "/usr/src/app/util/utils.py", line 41 in wrapper
2021-08-17T17:43:29.552834584Z   File "/usr/local/lib/python3.6/site-packages/django/dispatch/dispatcher.py", line 179 in <listcomp>
2021-08-17T17:43:29.558527987Z   File "/usr/local/lib/python3.6/site-packages/django/dispatch/dispatcher.py", line 179 in send
2021-08-17T17:43:29.561422888Z   File "/usr/local/lib/python3.6/site-packages/django/db/models/base.py", line 803 in save_base
2021-08-17T17:43:29.568127492Z   File "/usr/local/lib/python3.6/site-packages/django/db/models/base.py", line 754 in save
2021-08-17T17:43:29.571595893Z   File "/usr/src/app/content/signals.py", line 27 in run_celery_tasks_for_event
2021-08-17T17:43:29.575411095Z   File "/usr/src/app/content/signals.py", line 20 in send_event_reminders
2021-08-17T17:43:29.576618796Z   File "/usr/src/app/util/utils.py", line 41 in wrapper
2021-08-17T17:43:29.581282898Z   File "/usr/local/lib/python3.6/site-packages/django/dispatch/dispatcher.py", line 179 in <listcomp>
2021-08-17T17:43:29.585027100Z   File "/usr/local/lib/python3.6/site-packages/django/dispatch/dispatcher.py", line 179 in send
2021-08-17T17:43:29.589524602Z   File "/usr/local/lib/python3.6/site-packages/django/db/models/base.py", line 803 in save_base
2021-08-17T17:43:29.595221105Z   File "/usr/local/lib/python3.6/site-packages/django/db/models/base.py", line 754 in save
2021-08-17T17:43:29.595235505Z   File "/usr/src/app/content/signals.py", line 27 in run_celery_tasks_for_event
2021-08-17T17:43:29.600494108Z   File "/usr/src/app/content/signals.py", line 20 in send_event_reminders
2021-08-17T17:43:29.600508508Z   File "/usr/src/app/util/utils.py", line 41 in wrapper
2021-08-17T17:43:29.603996609Z   File "/usr/local/lib/python3.6/site-packages/django/dispatch/dispatcher.py", line 179 in <listcomp>
2021-08-17T17:43:29.608158311Z   File "/usr/local/lib/python3.6/site-packages/django/dispatch/dispatcher.py", line 179 in send
2021-08-17T17:43:29.613186614Z   File "/usr/local/lib/python3.6/site-packages/django/db/models/base.py", line 803 in save_base
2021-08-17T17:43:29.618646617Z   File "/usr/local/lib/python3.6/site-packages/django/db/models/base.py", line 754 in save
2021-08-17T17:43:29.623141019Z   File "/usr/src/app/content/signals.py", line 27 in run_celery_tasks_for_event
2021-08-17T17:43:29.627186721Z   File "/usr/src/app/content/signals.py", line 20 in send_event_reminders
2021-08-17T17:43:29.629246922Z   File "/usr/src/app/util/utils.py", line 41 in wrapper
2021-08-17T17:43:29.635402425Z   File "/usr/local/lib/python3.6/site-packages/django/dispatch/dispatcher.py", line 179 in <listcomp>
2021-08-17T17:43:29.639421027Z   File "/usr/local/lib/python3.6/site-packages/django/dispatch/dispatcher.py", line 179 in send
2021-08-17T17:43:29.645464530Z   File "/usr/local/lib/python3.6/site-packages/django/db/models/base.py", line 803 in save_base
2021-08-17T17:43:29.649879632Z   File "/usr/local/lib/python3.6/site-packages/django/db/models/base.py", line 754 in save
2021-08-17T17:43:29.653018834Z   File "/usr/src/app/content/signals.py", line 27 in run_celery_tasks_for_event
2021-08-17T17:43:29.657666336Z   File "/usr/src/app/content/signals.py", line 20 in send_event_reminders
2021-08-17T17:43:29.659185937Z   File "/usr/src/app/util/utils.py", line 41 in wrapper
2021-08-17T17:43:29.664006739Z   File "/usr/local/lib/python3.6/site-packages/django/dispatch/dispatcher.py", line 179 in <listcomp>
2021-08-17T17:43:29.669262242Z   File "/usr/local/lib/python3.6/site-packages/django/dispatch/dispatcher.py", line 179 in send
2021-08-17T17:43:29.674159844Z   File "/usr/local/lib/python3.6/site-packages/django/db/models/base.py", line 803 in save_base
2021-08-17T17:43:29.679786747Z   File "/usr/local/lib/python3.6/site-packages/django/db/models/base.py", line 754 in save
2021-08-17T17:43:29.681994448Z   File "/usr/src/app/content/signals.py", line 27 in run_celery_tasks_for_event
2021-08-17T17:43:29.686586150Z   File "/usr/src/app/content/signals.py", line 20 in send_event_reminders
2021-08-17T17:43:29.689826852Z   File "/usr/src/app/util/utils.py", line 41 in wrapper
2021-08-17T17:43:29.695855755Z   File "/usr/local/lib/python3.6/site-packages/django/dispatch/dispatcher.py", line 179 in <listcomp>
2021-08-17T17:43:29.700006457Z   File "/usr/local/lib/python3.6/site-packages/django/dispatch/dispatcher.py", line 179 in send
2021-08-17T17:43:29.707553960Z   File "/usr/local/lib/python3.6/site-packages/django/db/models/base.py", line 803 in save_base
2021-08-17T17:43:29.711625262Z   File "/usr/local/lib/python3.6/site-packages/django/db/models/base.py", line 754 in save
2021-08-17T17:43:29.716572465Z   File "/usr/src/app/content/signals.py", line 27 in run_celery_tasks_for_event
2021-08-17T17:43:29.720218267Z   File "/usr/src/app/content/signals.py", line 20 in send_event_reminders
2021-08-17T17:43:29.722082068Z   File "/usr/src/app/util/utils.py", line 41 in wrapper
2021-08-17T17:43:29.730507772Z   File "/usr/local/lib/python3.6/site-packages/django/dispatch/dispatcher.py", line 179 in <listcomp>
2021-08-17T17:43:29.735680974Z   File "/usr/local/lib/python3.6/site-packages/django/dispatch/dispatcher.py", line 179 in send
2021-08-17T17:43:29.740280177Z   File "/usr/local/lib/python3.6/site-packages/django/db/models/base.py", line 803 in save_base
2021-08-17T17:43:29.745597679Z   File "/usr/local/lib/python3.6/site-packages/django/db/models/base.py", line 754 in save
2021-08-17T17:43:29.751814882Z   File "/usr/src/app/content/signals.py", line 27 in run_celery_tasks_for_event
2021-08-17T17:43:29.754562284Z   File "/usr/src/app/content/signals.py", line 20 in send_event_reminders
2021-08-17T17:43:29.757757385Z   File "/usr/src/app/util/utils.py", line 41 in wrapper
2021-08-17T17:43:29.762808588Z   File "/usr/local/lib/python3.6/site-packages/django/dispatch/dispatcher.py", line 179 in <listcomp>
2021-08-17T17:43:29.768215090Z   File "/usr/local/lib/python3.6/site-packages/django/dispatch/dispatcher.py", line 179 in send
2021-08-17T17:43:29.772934793Z   File "/usr/local/lib/python3.6/site-packages/django/db/models/base.py", line 803 in save_base
2021-08-17T17:43:29.779067796Z   File "/usr/local/lib/python3.6/site-packages/django/db/models/base.py", line 754 in save
2021-08-17T17:43:29.786224299Z   File "/usr/src/app/content/signals.py", line 27 in run_celery_tasks_for_event
2021-08-17T17:43:29.786241199Z   File "/usr/src/app/content/signals.py", line 20 in send_event_reminders
2021-08-17T17:43:29.809133911Z   File "/usr/src/app/util/utils.py", line 41 in wrapper
2021-08-17T17:43:29.809148211Z   File "/usr/local/lib/python3.6/site-packages/django/dispatch/dispatcher.py", line 179 in <listcomp>
2021-08-17T17:43:29.809153111Z   File "/usr/local/lib/python3.6/site-packages/django/dispatch/dispatcher.py", line 179 in send
2021-08-17T17:43:29.809156511Z   File "/usr/local/lib/python3.6/site-packages/django/db/models/base.py", line 803 in save_base
2021-08-17T17:43:29.809159911Z   File "/usr/local/lib/python3.6/site-packages/django/db/models/base.py", line 754 in save
2021-08-17T17:43:29.809163011Z   File "/usr/src/app/content/signals.py", line 27 in run_celery_tasks_for_event
2021-08-17T17:43:29.809166211Z   File "/usr/src/app/content/signals.py", line 20 in send_event_reminders
2021-08-17T17:43:29.813883713Z   File "/usr/src/app/util/utils.py", line 41 in wrapper
2021-08-17T17:43:29.820392416Z   File "/usr/local/lib/python3.6/site-packages/django/dispatch/dispatcher.py", line 179 in <listcomp>
2021-08-17T17:43:29.826831919Z   File "/usr/local/lib/python3.6/site-packages/django/dispatch/dispatcher.py", line 179 in send
2021-08-17T17:43:29.832257522Z   File "/usr/local/lib/python3.6/site-packages/django/db/models/base.py", line 803 in save_base
2021-08-17T17:43:29.836804624Z   File "/usr/local/lib/python3.6/site-packages/django/db/models/base.py", line 754 in save
2021-08-17T17:43:29.842046327Z   File "/usr/src/app/content/signals.py", line 27 in run_celery_tasks_for_event
2021-08-17T17:43:29.844885128Z   File "/usr/src/app/content/signals.py", line 20 in send_event_reminders
2021-08-17T17:43:29.846611029Z   File "/usr/src/app/util/utils.py", line 41 in wrapper
2021-08-17T17:43:29.853324432Z   File "/usr/local/lib/python3.6/site-packages/django/dispatch/dispatcher.py", line 179 in <listcomp>
2021-08-17T17:43:29.858704235Z   File "/usr/local/lib/python3.6/site-packages/django/dispatch/dispatcher.py", line 179 in send
2021-08-17T17:43:29.858720735Z   File "/usr/local/lib/python3.6/site-packages/django/db/models/base.py", line 803 in save_base
2021-08-17T17:43:29.862975937Z   File "/usr/local/lib/python3.6/site-packages/django/db/models/base.py", line 754 in save
2021-08-17T17:43:29.868976240Z   File "/usr/src/app/content/signals.py", line 27 in run_celery_tasks_for_event
2021-08-17T17:43:29.868991340Z   File "/usr/src/app/content/signals.py", line 20 in send_event_reminders
2021-08-17T17:43:29.873245942Z   File "/usr/src/app/util/utils.py", line 41 in wrapper
2021-08-17T17:43:29.879585145Z   File "/usr/local/lib/python3.6/site-packages/django/dispatch/dispatcher.py", line 179 in <listcomp>
2021-08-17T17:43:29.879600545Z   ...
2021-08-17T17:43:29.879604745Z
2021-08-17T17:43:29.879607945Z Thread 0x00007fd4dbfff700 (most recent call first):
2021-08-17T17:43:29.884162648Z   File "/usr/local/lib/python3.6/threading.py", line 295 in wait
2021-08-17T17:43:29.889779950Z   File "/usr/local/lib/python3.6/site-packages/sentry_sdk/_queue.py", line 180 in get
2021-08-17T17:43:29.893387252Z   File "/usr/local/lib/python3.6/site-packages/sentry_sdk/worker.py", line 123 in _target
2021-08-17T17:43:29.895945554Z   File "/usr/local/lib/python3.6/threading.py", line 864 in run
2021-08-17T17:43:29.902521557Z   File "/usr/local/lib/python3.6/site-packages/sentry_sdk/integrations/threading.py", line 67 in run
2021-08-17T17:43:29.906775959Z   File "/usr/local/lib/python3.6/threading.py", line 916 in _bootstrap_inner
2021-08-17T17:43:29.913867162Z   File "/usr/local/lib/python3.6/threading.py", line 884 in _bootstrap
2021-08-17T17:43:29.913883762Z
2021-08-17T17:43:29.913927162Z Thread 0x00007fd4e8e99700 (most recent call first):
2021-08-17T17:43:29.913935962Z   File "/usr/local/lib/python3.6/selectors.py", line 376 in select
2021-08-17T17:43:29.917720464Z   File "/usr/local/lib/python3.6/socketserver.py", line 236 in serve_forever
2021-08-17T17:43:29.921294566Z   File "/usr/local/lib/python3.6/site-packages/django/core/servers/basehttp.py", line 216 in run
2021-08-17T17:43:29.928022069Z   File "/usr/local/lib/python3.6/site-packages/django/core/management/commands/runserver.py", line 140 in inner_run
2021-08-17T17:43:29.931447171Z   File "/usr/local/lib/python3.6/site-packages/django/utils/autoreload.py", line 53 in wrapper
2021-08-17T17:43:29.933838972Z   File "/usr/local/lib/python3.6/threading.py", line 864 in run
2021-08-17T17:43:29.939782475Z   File "/usr/local/lib/python3.6/site-packages/sentry_sdk/integrations/threading.py", line 67 in run
2021-08-17T17:43:29.940792976Z   File "/usr/local/lib/python3.6/threading.py", line 916 in _bootstrap_inner
2021-08-17T17:43:29.949566280Z   File "/usr/local/lib/python3.6/threading.py", line 884 in _bootstrap
2021-08-17T17:43:29.949590280Z
2021-08-17T17:43:29.949595580Z Thread 0x00007fd4ef79a740 (most recent call first):
2021-08-17T17:43:29.949599480Z   File "/usr/local/lib/python3.6/pathlib.py", line 387 in wrapped
2021-08-17T17:43:29.949603280Z   File "/usr/local/lib/python3.6/pathlib.py", line 1158 in stat
2021-08-17T17:43:29.964998188Z   File "/usr/local/lib/python3.6/site-packages/django/utils/autoreload.py", line 384 in snapshot_files
2021-08-17T17:43:29.965013088Z   File "/usr/local/lib/python3.6/site-packages/django/utils/autoreload.py", line 364 in tick
2021-08-17T17:43:29.965018088Z   File "/usr/local/lib/python3.6/site-packages/django/utils/autoreload.py", line 324 in run_loop
2021-08-17T17:43:29.965021888Z   File "/usr/local/lib/python3.6/site-packages/django/utils/autoreload.py", line 318 in run
2021-08-17T17:43:29.965025488Z   File "/usr/local/lib/python3.6/site-packages/django/utils/autoreload.py", line 603 in start_django
2021-08-17T17:43:29.965029088Z   File "/usr/local/lib/python3.6/site-packages/django/utils/autoreload.py", line 618 in run_with_reloader
2021-08-17T17:43:29.965032588Z   File "/usr/local/lib/python3.6/site-packages/django/core/management/commands/runserver.py", line 103 in run
2021-08-17T17:43:29.965046388Z   File "/usr/local/lib/python3.6/site-packages/django/core/management/commands/runserver.py", line 96 in handle
2021-08-17T17:43:29.965051188Z   File "/usr/local/lib/python3.6/site-packages/django/core/management/base.py", line 371 in execute
2021-08-17T17:43:29.965054588Z   File "/usr/local/lib/python3.6/site-packages/django/core/management/commands/runserver.py", line 61 in execute
2021-08-17T17:43:29.965058188Z   File "/usr/local/lib/python3.6/site-packages/django/core/management/base.py", line 330 in run_from_argv
2021-08-17T17:43:29.965061588Z   File "/usr/local/lib/python3.6/site-packages/django/core/management/__init__.py", line 395 in execute
2021-08-17T17:43:29.965065088Z   File "/usr/local/lib/python3.6/site-packages/django/core/management/__init__.py", line 401 in execute_from_command_line
2021-08-17T17:43:29.965068788Z   File "manage.py", line 19 in <module>
2021-08-17T17:43:37.713Z INFO  - Starting multi-container app..

https://stackoverflow.com/questions/7375875/django-post-save-signals-on-update
https://stackoverflow.com/questions/10840030/django-post-save-preventing-recursion-without-overriding-model-save


Support lazy configuration for mainClass and jvmFlags properties of ContainerParameters

This is a fix for #3927. I tried to follow the changes for similar issues applied in https://github.com/GoogleContainerTools/jib/pull/3242 and https://github.com/GoogleContainerTools/jib/pull/3709 as suggested in https://github.com/GoogleContainerTools/jib/issues/3927#issuecomment-1428027692.
If there is anything that needs to be changed before this PR can be accepted then please just let me know and I will amend it as necessary.
Before filing a pull request, make sure to do the following:

[x] Create a new issue at https://github.com/GoogleContainerTools/jib/issues/new/choose.
[x] Ensure that your implementation plan is approved by the team.
[x] Verify that integration tests and unit tests are passing after the change.
[x] Address all checkstyle issues. Refer to the style guide.

This helps to reduce the chance of having a pull request rejected.

Are there plans to review this PR in the near future, please?

Regarding the kokoro failures - they don't look related to the changes in this PR, and should be resolved by updating the branch against main to include fixes from https://github.com/GoogleContainerTools/jib/pull/3965. Thanks!

Regarding the kokoro failures - they don't look related to the changes in this PR, and should be resolved by updating the branch against main to include fixes from #3965. Thanks!

That's done, thanks.

could you help add a note on this enhancement in the README.md as well?

I've added notes to README.md about the properties now being lazily configurable similarly to the notes added in #3709.

I believe that all comments have been addressed so back to you, @emmileaf.

Thanks @emmileaf. I've registered for notifications from #3978 and #3979 so when they get merged/resolved I will pull main into this branch. Hopefully this will make it easier for you.

Latest master, which includes https://github.com/GoogleContainerTools/jib/pull/3979, has been merged into this branch now so this is ready for another run of checks, @emmileaf.

Thanks again @erdi!

And thank you for reviewing and merging, @emmileaf!


[SVE] Add support for scalable data type strings

This commit adds support for representing scalable vectors using the string data type format. For example, "float32xvscalex4" may be used to represent the following scalable type: DataType(kDLFloat, 32, /*lanes=*/4, /*is_scalable=*/true).
Co-authored-by: Elen Kalda<EMAIL_ADDRESS>Co-authored-by: Neil Hickey<EMAIL_ADDRESS>

@tvm-bot rerun

Thanks @lhutton1!

there is a regression due to concurrent merge, cc @Lunderberg

thanks for raising @tqchen, I'm taking a look now

Apologies for missing this previously, I've uploaded #16649 which I'd expect to fix the failing test case

Any idea why the CI didn't catch this?

CI was last run on the patch yesterday (26th Feb) while the PR that caught the issue was merged a week ago https://github.com/apache/tvm/pull/16563. I didn't rebase before pushing, but had expected CI to do this automatically.
I think it might have something to do with a missing call to merge_with_main()(link) in the unity_jenkinsfile.groovy file since the other jenkinsfiles used in CI make calls to this, which presumably updates the PR branch before CI is run


[Swift] various dead code cleanups, simplifications and phpdoc fixes.

I don't know why the tests suite ends up with a segfault on PHP 5.3. On my machine (PHP 5.6.12), the test suite also segfaults when I run unit tests after a fresh checkout of the repository + composer install command.

PHP 5.3 is pretty dead on TravisCi, and try disabling the gc as used in https://github.com/symfony/phpunit-bridge/blob/2.7/bootstrap.php#L11-L15

@stof also any reasons why the build matrix allows failures for PHP 5.6? Shouldn't we officially support PHP5.6 with Swiftmailer?

@hhamon no idea

So we can add PHP 5.6 to the list of supported versions I guess.

Probably because 5.6 did not work back then. It should indeed be re-integrated into the main matrix, and hopefully PHP7 as well.

Thank you @hhamon.


SYSLOG Server in AZS Endpoits #705

Close missing outbound endpoint for SYSLOG, see #705

@jbpaux : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#in-progress


Warning: DOMDocument::loadHTML(): Unexpected end tag : a in Entity, line: 25

Hello Developers,
so I gradually go through all Pico CMS plugins and install some. Now I am at the TOC and has installed it. On the page at http://picocms.wpzweinull.ch/sub/datenschutz these warnings are displayed.
Warning: DOMDocument::loadHTML(): Unexpected end tag : a in Entity, line: 25 in /xxxxx/picocms.wpzweinull.ch/plugins/mcb_TableOfContent.php on line 79

Warning: DOMDocument::loadHTML(): Unexpected end tag : a in Entity, line: 27 in /xxxxx/picocms.wpzweinull.ch/plugins/mcb_TableOfContent.php on line 79

Warning: DOMDocument::loadHTML(): Unexpected end tag : a in Entity, line: 36 in /xxxx/picocms.wpzweinull.ch/plugins/mcb_TableOfContent.php on line 79

Warning: DOMDocument::loadHTML(): Unexpected end tag : a in Entity, line: 37 in /xxxxx/picocms.wpzweinull.ch/plugins/mcb_TableOfContent.php on line 79

Warning: DOMDocument::loadHTML(): Unexpected end tag : a in Entity, line: 40 in /xxxx/picocms.wpzweinull.ch/plugins/mcb_TableOfContent.php on line 79

How can I fix it?
Thanks in advance.
I use the last Pico CMS version.

You have to check your template. You have closing  tag, but no open one in your template.
Try also  https://validator.w3.org when this plugin is disabled to find the invalid html code.
best regards from Austria

Check this out; I think this will solve your problem.

for dirty code in content, you "can`t" clean, put this:
libxml_use_internal_errors(true);

in line:79 of the mcb_TableOfContent.php, before the $dom->loadHTML line:
https://github.com/mcbSolutions/Pico-Plugins/blob/master/mcb_TableOfContent/mcb_TableOfContent.php#L79
found here: https://stackoverflow.com/a/11819635/8110291


feature: add basic + sync operation on information_schema, tested on …

Description

add some schema operation. like show_database, show tables.
update macros/seeds.sql, now it  works properly when tableexists
test cases (these test are not unit tests) :

default_catalog + seed as kafka ===> seed twice, data duplicate.  we cannot drop kafka data by flink
hive catalog + minio ===> seed twice, one data
hive catalog + iceberg ===> seed twice, one data

Resolves https://github.com/getindata/dbt-flink-adapter/issues/55
PR Checklist

[ ] Tests added. (not unit tests, dont know how to deal with these code )

As for tests I still didnt found time to add test framework. What I have in mind are two types of tests:

mocked sql client so we can test all the macro generation and interaction with Flink sql gateway using that mock
end to end test with Flink and Kafka and maybe some DB running as containers in test.

@zqWu you should be able to run all checks on your machine using pre-commit run -a


fix: fixed broken dialog when using maxWidth="xs" and custom breakpoint unit

[x] I have followed (at least) the PR section of the contributing guide.

@jguddas Thanks for working on this ~
Please provide a before/after reproduction so we can verify if it's indeed a bug and then test it.
Also, for the future, it's better to open an issue describing the problem first 🙂
PS: You can use this template for a reproduction: https://mui.com/r/issue-template-latest

Resolves https://github.com/mui/material-ui/issues/37241.

Wow, that's true speed.


Make scipy.ndimage.map_coordinates fail when coordinates is rank 1

This will fix the just raised issue:
https://github.com/google/jax/issues/5685

Based on https://github.com/google/jax/issues/5685#issuecomment-776883676, let's close this for now.


Exclude setting in vitest config doesn't work with file paths that contain parentheses/brackets

Describe the bug
Hello, I noticed that the exclude-option in vitest.config.ts doesn't work for file paths that contain parentheses/brackets, e.g. file paths like src/(test)/file.spec.ts. Normally, this wouldn't be an issue as parentheses/brackets in are rarely used for file paths, but in Next13/14, folders in parentheses/brackets are used for route grouping. At the moment, tests in route groups can't be disabled.
Reproduction
I created an example repo here.
// vitest.config.ts
import react from '@vitejs/plugin-react';
import { defineConfig } from 'vitest/config';
import { configDefaults } from 'vitest/config';

export default defineConfig({
  plugins: [react()],
  test: {
    exclude: [
      ...configDefaults.exclude,
      'src/tests/(with-parentheses)/test.spec.ts', // is not excluded
      'src/tests/without-parentheses/test.spec.ts', // is excluded
    ],
  },
});

When running vitest via npm run test "src/tests/(with-parentheses)/test.spec.ts" is still executed, even tho it is disabled, while "src/tests/without-parentheses/test.spec.ts" is not executed, which is intended.
System Info
vitest: 1.1.3,
node: 20

Used Package Manager
pnpm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

It might not be documented properly but Vitest uses fast-glob/micromatch and it looks like they support double backslash \\ to escape special characters.

https://github.com/mrmlnc/fast-glob?tab=readme-ov-file#advanced-syntax

I tested this on stackblitz https://stackblitz.com/edit/github-4hjjeo?file=vitest.config.ts

Hello, that seems to be the fix. Thanks!

It might not be documented properly but Vitest uses fast-glob/micromatch

I am not sure how it can be more obvious (from the docs):

Files to exclude from the test run, using glob pattern.

Do we need to add a link to how glob pattern works?

Does Vitest doc mention exact library it uses (namely fast-glob and micromatch)? I was kinda comparing with Vite documentation, which explicitly mentions picomatch with a link to picomatch's README in a few places, for example https://vitejs.dev/config/server-options.html#server-fs-deny

Does Vitest doc mention exact library it uses

No, we don't mention what library is used. And I'd say it is a bad idea to mention implementation details like that. Glob pattern is a standard and it shouldn't depend on what implementation we use.

Perhaps a small hint like, "Please be aware, that certain characters like () need to be escaped" would suffice?


[WIP] Add a new JavaFX provider for authentication on JBR

Closes #237.
Please do not merge yet, we're waiting for the dependency libraries to update.

Depends on:

https://github.com/microsoft/oauth2-useragent/pull/47
https://github.com/microsoft/vsts-authentication-library-for-java/pull/23

After the pull requests are merged, we'll have to wait for publication of the new versions of these libraries.

We have decided to migrate to the Microsoft Authentication Library for Java, so I'm closing this pull request.


[Impeller] Scene is getting compiled into binary even if IMPELLER_ENABLE_3D is false.

We should not do this for now, only add it in if the define is set.
@bdero fyi

Can you please paste the validation log you are getting? SceneContext uploads a texture on construction, but it doesn't render anything. It sounds to me like there might be a bug in the Vulkan backend.

Ah, I see it's the pipeline formation as you pointed out here: https://github.com/flutter/flutter/issues/133194


Training is too slow

Hi, I use all the default configs, but only train 50 epochs (total 300) in 12h. Is that normal?
My envs:
pytorch1.0 + cuda9.0 + P100 * 2

Yes. You could also try other schedule and parameters.


Added support for JSON files

Added support for JSON files

Not working for me, is there a thing I do wrong ?


Implement RESSEL ensemble algorithm

A reliable ensemble based approach to semi-supervised learning

Added on https://github.com/dpr1005/Semisupervised-learning-and-instance-selection-methods/commit/2e355a73bfedfc9d40563a75045569c8802e8888


Fix install failure when .bashrc does not exists

All users do not have a .bashrc.
PR76 adds lines to bashrc but causes install failure if the file does not exist.
Solution: allow bashrc file creation if it does not exist.

Thanks!


hook for initialisation scripts

it'd be great to have a hook in entrypoint.sh for running some pre-startup init scripts, for configuring db users etc
like in the PostgreSQL one here:
https://github.com/docker-library/postgres/blob/cd294bf8dfdf4a74b2077aa6413fa579f9bf07de/9.3/docker-entrypoint.sh#L76
I'm happy to make a pull request based on above if you agree the approach?

There is a entrypoint.sh for mongodb. Refer this
https://github.com/docker-library/mongo/tree/14bbc085ef419c141b10595b04fe48c924a8c45e/3.1

@anilkun yes the point is build a hook into that entrypoint script file
otherwise you have to copy and paste the entrypoint script into your project and work out how to write your own hook code
see my PR, they do the same thing in the Postgres image

+1, the initdb.d approach is nice. mysql does the same thing as postgres mentioned above https://github.com/docker-library/mysql/blob/f7a67d7634a68d319988ad6f99729bfeaa84ceb2/5.6/docker-entrypoint.sh#L107-L115


Copy the text to the vscode editor will change the character t to the chinese character seven

Issue Type: Bug
-- coding:utf-8 --
def useproxy(proxy_addr,url):
impor七urllib.reques七
proxy= urllib.reques七.ProxyHandler({'h七tp':proxy—addr})
opener = urllib.request.build_opener(proxy, urllib.request.HTTPHandler)
urllib.reques七.ins七all_opener(opener)
da七a = urllib . reques 七. urlopen (url) . read () . decode ('u七f-8')
re七urn data
proxy_addr="<IP_ADDRESS>:7777"
data=use_proxy(proxy_addr,"h七tp://www.baidu.com")
print(len(da七a))
VS Code version: Code 1.26.1 (493869ee8e8a846b0855873886fc79d480d342de, 2018-08-16T18:38:57.434Z)
OS version: Windows_NT x64 6.1.7601

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz (4 x 2394)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: unavailable_softwarevideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabled

Memory (System)
7.91GB (4.64GB free)

Process Argv
C:\Users\Icarus\AppData\Local\Programs\Microsoft VS Code\Code.exe C:\Users\Icarus\Desktop

Screen Reader
no

VM
0%

Extensions (4)

Extension
Author (truncated)
Version

code-runner
for
0.9.4

vscode-language-pack-zh-hans
MS-
1.26.3

python
ms-
2018.7.1

vscode-icons
rob
7.25.0

(1 theme extensions excluded)

Here are my vscode plugin

This text's copy should be like this

But it sounds like wrong with this

And I don't know if this is related to the Chinese display plugin(Chinese Language Pack), or others

Today, the first thing that I think it related to Chinese language pack,so, I uninstall the pack and restart it.
The result of what i see is it doesn't work like that

and Now, I think it isn't the Chinese Language Pack's fault, it maybe the editor's self.
Here are my userseting.json, I do not think it would be wrong set

@JYG-V Do you mean you have a problem when opening a certain file? Can you attach the file with the problem? The text you have pasted contains this funny character and does not contain two t's
In other words, what are the steps you do, what do you expect to happen vs. what happens?

That's interesting question and answer, I mean I copy the example code or the demo, other than open, it isn't Encoding's Proplem, I know reEncoding GBK will be good support for Chinese language ,and then paste it to the vscode editor, it was amazing and fantastic editor,i love it.and because of i'm chinese, i wish it could be better support for chinese to program or code, i'm learing Python Spider and Regulation Expression, I copy the sample code from the pdf file and just want to test it and figure it out what can it doing or can do something else. And you see, i met this problem, and it makes me not convenient to code any more, this pdf file are too larger 43MB size, maybe will upload failed,and my network isn't good

Yet, the github's regulation is no more than 10MB file, i upload failed!

Now, I'm trying to reappear the situation that i met.
First, i open the pdf file 精通Python网络爬虫 核心技术框架与项目实战 韦玮.pdf

Then i go to the character5 regulation expression proxy setup,and i copy the sample code

Then i open the vscode editor and new a file choose to python and save as a test.py

Please trust me, i do not have any other bad habits,, what happen is what you see.

I wish vscode editor could fix that problem, yet,, althought it's too small to negelect it, and not important than others, i think it isn't only i met this problem.Why does the vscode editor happen to t otherwise any other characters?i present think it's a vscode colorful eggs(amazing),but it is not friendly to me, thank you for your answer.

@JYG-V I believe the PDF itself contains 七 instead of t. What happens if you copy from the PDF and paste in another software, like e.g. Notepad ?

I'm so sorry to hear that, It seems that you still don't believe me.

emmm, I have write a email to your email address, attach a larger attachment PDF file which contains 七 instead of t, Please Check it out,  and i'm glad to hear your good news, good luck, Thank you!

It seems that actually the pdf file's character t instead of the chinese character 七, but the pdf file's author have no way to do that, because when you type import ,it can't be typed as 七, it isn't convenient, but the stranger thing is that, you will see the pdf file clearly that t is t,not 七
Actually, VSCode Editor has been added picture viewer,then there is a question, why not add a plugin such as edge PDF viewers?All in one, plugin is everything, can create anything.That's why I like to use vscode.

And why do it only change t to 七？why other characters not changed?I have no way to type t as 七

@JYG-V From your previous screenshot where you show Notepad, it looks like when you paste in Notepad you also get the 七 character and not the latin t character. I can therefore conclude this is not a problem with VS Code, but rather a problem with the PDF you are copying from.
Here, select the following text and paste it to VS Code or Notepad:
this is a sentence that uses t a lot
Are the characters pasted as t or as 七?
If the characters are pasted as t you have further proof that this is a problem with the PDF.

Okay, thank you very much, I misunderstand the editor, it's my fault.


[WIP] Fix/typo : Tutorials improvements

See issue #383.
Note that the changes made have been tested with mkdocs version 1.1.2.

Can one of the admins verify this patch?

ok to test


Retry Throttling errors in CloudFormation waiters.

This is a cherry-pick commit from https://github.com/acquia/aws-sdk-ruby/tree/v2.9.5-acquia1 branch which is currently used in worker.
Current worker version: v2.9.5-acquia1
Current API version: v2.11.3-acquia
Once this PR is merged, would like to update both repos to use v2.11.3-acquia

The motivation behind this change is, with the current version in worker we cannot specify tags to create_snapshot aws call.


Extend time issue when current time is days

Extend time issue when current time is days
theres an issue on extending time if your current time is > 24 hour

perform a hotfix for v2.1.1

closing issue since already in latest push


encrypt.so and encrypt.dll or encrypt_64.dll aren't included with the download

Where do I find these files on the internet? any links I follow show me a page about legalities in Australia, and the files that come from it don't do anything.....

Try the manual installation: https://github.com/PokemonGoF/PokemonGo-Bot/blob/dev/docs/manual_installation.md

Please direct issues with installing the bot to the slack #help page.


luci-app-commands public links wrong

Using the luci-app-command part of luci works well for the most part. However, there is an error in the links for public commands.
When hitting the “Link” button on the dashboard page, it returns a link in the form below:
“Access command with http://<IP_ADDRESS>/cgi-bin/luci/admin/system/commandscommand/cfg089944”
It should read:
“Access command with http://<IP_ADDRESS>/cgi-bin/luci/command/cfg089944”
The error appears to be in /usr/lib/lua/luci/view/commands.htm at line 113
var link = location.protocol + '//' + location.hostname +                    (location.port ? ':' + location.port : '') +                    location.pathname.split(';')[0] + 'command/' +                    id + (args ? '/' + args : '');
It perhaps should read (and please pardon my lack of programming ability...)
var link = location.protocol + '//' + location.hostname +                    (location.port ? ':' + location.port : '') +                    location.pathname.split('luci/')[0] + 'luci/command/' +                    id + (args ? '/' + args : '');

@muddyfeet Does this PR (https://github.com/openwrt/luci/pull/768) also resolve the issue (along with the main purpose of allowing text viewing instead of have to download the output).

Sorry for the delay responding - no, the code in PR (#768) doesn't fix the URI as you've already determined.  However, the changes proposed are a great improvement in other areas.

Fixed by e4f77ac


Patching DOM elements loses img src attribute values

I'm having a html similar to this:

After some user interaction I will perform a request to the server which returns new innerHTML for main. Since most of that innerHTML is the same then I decided to give Virtual DOM a try to avoid changing too much. Here's how I tried to do it:
fetch("/new-content")
  .then(response => response.text())
  .then(html => {
    var newContentEl = document.querySelector("main").cloneNode(false)
    newContentEl.innerHTML = html
    patch(toVNode(document.querySelector("main")), toVNode(newContentEl))
  })

It will result in html similar to like this:

Notice that both img tag src attributes have been removed although I can see them being there in the html variable got from fetch. All other seems to be in place, the only problem seems to be img elements src attributes which will change after each fetch.
If I don't use Virtual DOM then everything works as expected:
fetch("/new-content")
  .then(response => response.text())
  .then(html => {
    var newContentEl = document.querySelector("main")
    newContentEl.innerHTML = html
  })

What am I doing wrong?

This test fails because toVNode does not capture the src property from the original dom element.
it("can process img src attributes", function () {
  const prevElm = document.createElement("img");
  const newElm = document.createElement("img");
  prevElm.src = "http://other/";
  newElm.src = "http://localhost/";

  const vnode2 = toVNode(newElm)

  // test passes, when the below line is un-commented
  // vnode2.data.props = { src: "http://localhost/" }

  elm = patch(toVNode(prevElm), vnode2).elm;
  assert.strictEqual(elm.src, "http://localhost/");
});

This issue seems to touch a number of overlapping things,
Currently, the below test incorrectly nests img inside another empty vnode,
it("can patch img vnode attributes", function () {
  const vnode1 = toVNode((e => (
    e = document.createElement("img"),
    e.src = "http://other/",
    toVNode(e)
  ))())
  const vnode2 = toVNode((e => (
    e = document.createElement("img"),
    e.src = "http://localhost/",
    toVNode(e)
  ))())

  elm = patch(vnode1, vnode2).elm.elm;

  assert.strictEqual(elm.src, "http://localhost/");
});

the empty vnode returned from the patch above looks like this
{
  sel: '',
  data: {},
  children: [],
  elm: {
    sel: 'img',
    data: [Object],
    children: [],
    elm: 'HTMLImageElement: ',
    text: undefined,
    key: undefined
  },
  text: undefined,
  key: undefined
}

also, if we create "img" vnodes and call the patch function with those, no element is returned in the patch
it("should patch img vnodes", function () {
  const vnode1 = h("img", { props: { src: "http://other/" } })
  const vnode2 = h("img", { props: { src: "http://localhost/" } })

  const vnode = patch(vnode1, vnode2))
  assert.strictEqual(vnode.data.props.src, "http://localhost/")
  assert.strictEqual(vnode.elm.src,  "http://localhost/") // fail: element is undefined
});

pre-existing tests using patch around other vnode tags such as "i" return a dom element, for example this pre-existing test passes,
it("changes the elements classes", function () {
  const vnode1 = h("i", { class: { i: true, am: true, horse: true } });
  const vnode2 = h("i", { class: { i: true, am: true, horse: false } });
  patch(vnode0, vnode1);
  elm = patch(vnode1, vnode2).elm;
  assert(elm.classList.contains("i"));
  assert(elm.classList.contains("am"));
  assert(!elm.classList.contains("horse"));
})

The test using the "i" element starts the patch sequence with vnode0; that is way it returns the dom element...

Testing patches around the 'img' tag specifically is not possible using the master branch because of the same issues described in https://github.com/snabbdom/snabbdom/issues/972 and https://github.com/snabbdom/snabbdom/issues/971
Because of that, this issue should be handled after https://github.com/snabbdom/snabbdom/pull/1062 has been merged. https://github.com/snabbdom/snabbdom/pull/1062 is updated to include the test case above so that it will be ready for this issue.
it("can patch single img element", function () {
  const prevElm = document.createElement("img");
  const newElm = document.createElement("img");
  prevElm.src = "http://other/";
  newElm.src = "http://localhost/";

  const vnode1 = toVNode(prevElm)
  const vnode2 = toVNode(newElm)

  // test fails, when the below line is un-commented, but should pass
  // https://github.com/snabbdom/snabbdom/issues/958
  vnode2.data.props = { src: "http://localhost/" }

  patch(vnode0, vnode1);
  elm = patch(vnode1, vnode2).elm;
  assert.strictEqual(elm.src, "http://localhost/");
})

Closing due to the discussion at https://github.com/snabbdom/snabbdom/pull/1066


Stop updating latest message text in subscription frame when it is text selected

This helps the user copy and paste the text or in general do what they want to do.

It's too difficult to accomplish and they can use the log popup


Implement versioning strategy

Currently, WarpSQL's versioning lacks a proper structure. It would be nice to formalize this process to alert users of breaking changes etc.

Proposal
I am proposing the following versioning strategy for the WarpSQL codebase, using the SemVer Specification.
MAJOR Version (v1.x.x):
For incompatible backward changes.
Examples:

Increment an extension to MAJORversions
Features causing backward incompatibility

MINOR Version (vx.4.x):
For non-breaking feature additions.
Examples:

Increment an extension to MINOR/PATCHversions
Addition of an extension
Upgrades maintaining backward compatibility

PATCH Version (vx.x.1):
For bug fixes that are backward compatible.
Using this strategy, we can guarantee that upgrading to a MINOR/PATCHversion of WarpSQL will ensure backward compatibility.

How do we handle test/alpha releases?


[DownloadPipelineArtifact@2] Unclear error Input string was not in a correct format

Required Information
Type: Bug/Feature
Enter Task Name: DownloadPipelineArtifact
Issue Description
Using this task, I get an error Input string was not in a correct format which doesn't indicate which field exactly is wrong, I tried changing the pipelineId to be with quotes (not sure where should I get the pipelineId from too) but it doesn't solve it.
I would prefer if there was a clearer error message about what's wrong in my configuration. To be able to solve this error.
- task: DownloadPipelineArtifact@2
  inputs:
    buildType: 'specific'
    project: '284k8d13-4263-4e3e-bca1-bf4744fb3dc6'
    pipelineId: 1819
    artifactName: 'bin_Linux'
    buildVersionToDownload: 'latestFromBranch'
    branchName: 'master'
    targetPath: '$(Pipeline.Workspace)'

(I changed the IDs in this snippet to not expose certain data)
Task logs
##[debug]Evaluating condition for step: 'DownloadPipelineArtifact'
##[debug]Evaluating: SucceededNode()
##[debug]Evaluating SucceededNode:
##[debug]=> True
##[debug]Result: True
Starting: DownloadPipelineArtifact
==============================================================================
Task         : Download Pipeline Artifacts
Description  : Download build and pipeline artifacts
Version      : 2.1.1
Author       : Microsoft Corporation
Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/download-pipeline-artifact
==============================================================================
##[error]Input string was not in a correct format.
##[debug]Processed: ##vso[task.logissue type=error;]Input string was not in a correct format.
##[debug]Processed: ##vso[task.complete result=Failed;]
##[debug]   at System.Number.StringToNumber(ReadOnlySpan`1 str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
   at System.Number.ParseInt32(ReadOnlySpan`1 s, NumberStyles style, NumberFormatInfo info)
   at Agent.Plugins.PipelineArtifact.DownloadPipelineArtifactTaskV2_0_0.GetPipelineIdAsync(AgentTaskPluginExecutionContext context, String pipelineDefinition, String pipelineVersionToDownload, String project, String[] tagFilters, String branchName)
   at Agent.Plugins.PipelineArtifact.DownloadPipelineArtifactTaskV2_0_0.ProcessCommandInternalAsync(AgentTaskPluginExecutionContext context, CancellationToken token)
   at Agent.PluginHost.Program.Main(String[] args)
Finishing: DownloadPipelineArtifact

@jahsu-MSFT

@sharno Thanks for the feedback. From looking at your yaml schema, I think the pipelineId there is redundant since you already selected to use the "latest from branch".
The pipeline should work by using the below schema -

task: DownloadPipelineArtifact@2
inputs:
buildType: 'specific'
project: '284k8d13-4263-4e3e-bca1-bf4744fb3dc6'
artifactName: 'bin_Linux'
buildVersionToDownload: 'latestFromBranch'
branchName: 'master'
targetPath: '$(Pipeline.Workspace)'

@jahsu-MSFT
Thanks for your reply
I found out that pipelineId should actually be just pipeline and this worked correctly
seems like the documentation is contradicting between the examples and the YAML snippet:
https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/utility/download-pipeline-artifact?view=azure-devops

Thanks for the update. @sharno  and sorry I deleted the previous reply since it's not exactly correct.
There are actually pipeline input field and pipelineId input field. The old name for the "pipeline" input field was "definition". We are going to update the documentation to avoid confusion. And we'll also be improving our error messages.
Thanks,

@jahsu-MSFT No worries, thanks for taking care of the issue


Image resize not working for some images

I'm getting this error "Cannot resize: Reading image failed" for a few images and I can't find any documentation on why this would happen.

"Cannot resize: Reading image failed" means that the original image was corrupted, for example, the image doesn't have the number of pixels which was claimed in the metadata.


Implement Elchemy/XDecoder.elm and  Elchemy/XEncoder.elm

Blocked by #125

Since it was moved out of elm-core in the newest release (0.19) it can be closed for now as it will be a separate project


feature basic functions for map datatype

Proposed changes
Issue Number: close #xxx
Problem summary
basic functions for map datatype:

MAP<K, V> map(K k1, V v1, ...)
BIGINT map_size(MAP<K, V> m)
BOOL map_contains_key(MAP<K, V> m, K k1)
BOOL map_contains_value(MAP<K, V> m, V v1)
ARRAY< K> map_keys(MAP<K, V> m)
ARRAY< V> map_values(MAP<K, V> m)

Checklist(Required)

[ ] Does it affect the original behavior
[ ] Has unit tests been added
[ ] Has document been added or modified
[ ] Does it need to update dependencies
[ ] Is this PR support rollback (If NO, please explain WHY)

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

run buildall

run buildall

run buildall

run buildall

run buildall

run buildall

run beut

run buildall

LGTM

run buildall

run buildall


BBC example no longer applicable with OpenDyslexic

Firefox 60.0.1 on FreeBSD-CURRENT:

$ pkg info firefox | grep Version
Version        : 60.0.1_3,1
$ date ; uname -v
Fri  1 Jun 2018 16:10:30 BST
FreeBSD 12.0-CURRENT #3 r334382: Thu May 31 01:37:12 BST 2018     root@momh167-gjp4-hpelitebook8570p-freebsd:/usr/obj/usr/src/amd64.amd64/sys/GENERIC

With Mobile Dyslexic in lieu of OpenDyslexic:

Any ideas?
Cheers

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Im currently working on this.
We have a firefox repo too. https://github.com/OpenDyslexic/firefox-extension

Thank you 👍
(I was in the other repo a few days ago for https://github.com/OpenDyslexic/firefox-extension/issues/1; apologies for the misplacement here.)

Hey @grahamperrin this is sorted and released now

Fix confirmed. Thanks 👍


Unhashable type SpdxNoAssertion

Hi there, if any relationships contain a NOASSERTION relationship, represented by the object SpdxNoAssertion(), then there will be a failure to write to file
  File "path/to/lib/spdx_tools/spdx/writer/tagvalue/tagvalue_writer_helper_functions.py", line 89, in scan_relationships
    and relationship.related_spdx_element_id in files_by_spdx_id.keys()
TypeError: unhashable type: 'SpdxNoAssertion'

The current work around I found is changing the if statements in scan_relationships to the following (lines 87-89)
        if (
            relationship.relationship_type == RelationshipType.CONTAINS
            and relationship.spdx_element_id in packages_spdx_ids
            and str(relationship.related_spdx_element_id) in files_by_spdx_id.keys()
        ):

Alternatively for a user side fix, replace your SpdxNoAssertion with "NOASSERTION" in any relationship or str(SpdxNoAssertion())
Also, I just want to voice some disappointment in the complete lack of  backwards compatibility in the 0.7.1->0.8.0 upgrade. I appreciate this very useful tool and the work the developers do, but when it takes as much time to fix my old script that was working as it would to just manually write and SPDX document by hand, it is very frustrating for me as a user. I hope you consider more backwards compatibility in future major patches. Thanks!

Hi @nathanjacobiOXOS, thanks for using the spdx-tools!
The issue you describe has been fixed in #778. Unfortunately, we didn't have a release since then. It's high time for a new release, it seems! :)
Regarding your disappointment, we are truly sorry for the inconvenience. The decision to drop backwards compatibility was not made lighthearted, but ultimately the hope was to have a stronger foundation in the code base going forward with the tools.


HSEARCH-2961 Downgrade the version of the MariaDB plugin

https://hibernate.atlassian.net//browse/HSEARCH-2961

merged


Support sending an image file to TagoIO Server

Dear Developers
I want to send an image file to TagoIO Server by modifying the repository made by you (Zephyr/samples/net/cloud/tagoio_http_post).
The following function "tagoio_http_push" can only send the text data to tagoio server.
Function: tagoio_http_push
**int tagoio_http_push(struct tagoio_context *ctx, http_response_cb_t resp_cb)
{
struct http_request req;
int ret;
memset(&req, 0, sizeof(req));
long int res = collect_data();
const char *image_path = data.txt;

req.method = HTTP_POST;
req.host = TAGOIO_SERVER;
req.port = HTTP_PORT;
req.url = TAGOIO_URL;
req.header_fields = tagoio_http_headers;
req.protocol = "HTTP/1.1";
req.response = resp_cb;
req.payload		= data.txt;
req.payload_len		= res;
req.recv_buf		= ctx->resp;
req.recv_buf_len	= sizeof(ctx->resp);

ret = http_client_req(ctx->sock, &req,
		      CONFIG_TAGOIO_HTTP_CONN_TIMEOUT * MSEC_PER_SEC,
		      ctx);

close(ctx->sock);
ctx->sock = -1;

return ret;

}**
The function for ctx-> payload is as follows:
**Function:
static int collect_data(void)
{
#define lower 20000
#define upper 100000
#define base  1000.00f
float temp;

/* Generate a temperature between 20 and 100 celsius degree */
temp = ((sys_rand32_get() % (upper - lower + 1)) + lower);
temp /= base;

(void)snprintf(ctx.payload, sizeof(ctx.payload),
	       "{\"variable\": \"temperature\","
	       "\"unit\": \"c\",\"value\": %f}",
	       (double)temp);

/* LOG doesn't print float #18351 */
LOG_INF("Temp: %f", (float) temp);

return 0;

}**
But I want to send the image file to TagoIo Server.
Can you please suggest the required changes that can I made to send the image file to TagoIo Server.
Is there any separate function is required to push the image.
Thanks in advance.

Hi @SinghKarminder ,
You can find all information about how to use device send data at Tago.IO documentation. The explanation is there about the API and their endpoints. I recommend you look for Arduino samples which are quite simple and easy to follow. You can find more info about HTTP here, for instance. The current application sends simple raw data to some endpoint and I don't want to change that. You are free to submit another PR based the current implementation which shows how to submit an image. I think it is better not mix topics.
If you dedicate your effort to develop using a PC to cloud the process it will be easy to figure out all needs. Once you understood all details and how your application should like it won't be difficult to replicate on Zephyr.

Hi @nandojve,
Thanks for your response. I will try to follow your instructions.
Thanks once again for giving time to my problem.


Add instructions for configuring a running instance

It isn't obvious that you need to set the --output-broker so that should be made clear.
The rest of the details can be copied from the C++ version.

I made it not required and defaulted to localhost:9092 so that the C++ codebase system tests could be run without any changes. Now that we have been making changes to the system tests we can remove the default, make it required and update the system test run configs as necessary.


Support for multiplatform container imege (amd64 and arm64)

/kind feature
I'd like to support multiplatform container image (amd64 and arm64), same as https://github.com/kubeflow/katib/issues/1900 so that users can run on arm machines such as NVIDIA DGX Server with Grace CPU.
ref: https://docs.docker.com/desktop/multi-arch/

Ref: https://github.com/kubeflow/training-operator/pull/1674
@tenzen-y Should we add ARCH as param like in Katib?

I will work on this before the next feature freeze date.


Some reviseion on bin/dotbot

See here:
https://github.com/hongyi-zhao/dotbot/commit/a5bc597a53ed170c9f439ec3b57e69c507ad63b7

What does this change accomplish? I see that in the patched version, PYTHONPATH is being modified if it is already set. For this program, though, does it matter whether we are updating it or replacing it entirely with just the path to this project's directory?

May be I just want to not touch the original stuff.
Anther thing is that I changed the function inject to path_insert, which may be more meaningful.

I think unless the current behavior is buggy, let's leave it as-is. Thanks for taking the time to propose this.


[Task] Add Dinky task to better support the development and execution of FlinkSQL

Purpose of the pull request
Add Dinky task to better support the development and execution of FlinkSQL.

close #10444
Brief change log

Verify this pull request

This pull request is code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:

demo-get-dinky-task-id(../../../../img/tasks/demo/dinky_task_id.png)
At present, Dinky is not internationalized, and English pictures will be added later.

Codecov Report

Merging #10640 (464ac6e) into dev (719a9d4) will decrease coverage by 0.04%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##                dev   #10640      +/-   ##
============================================
- Coverage     40.94%   40.90%   -0.05%
+ Complexity     4876     4830      -46
============================================
  Files           895      897       +2
  Lines         36212    36158      -54
  Branches       3987     4006      +19
============================================
- Hits          14826    14789      -37
+ Misses        19921    19898      -23
- Partials       1465     1471       +6

Impacted Files
Coverage Δ

...inscheduler/server/master/config/MasterConfig.java
35.00% <0.00%> (-41.75%)
:arrow_down:

...inscheduler/server/worker/config/WorkerConfig.java
52.38% <0.00%> (-24.09%)
:arrow_down:

.../dolphinscheduler/common/utils/ParameterUtils.java
58.53% <0.00%> (-14.60%)
:arrow_down:

...cheduler/plugin/task/api/TaskExecutionContext.java
93.87% <0.00%> (-5.38%)
:arrow_down:

...ache/impl/ProcessInstanceExecCacheManagerImpl.java
83.33% <0.00%> (-1.29%)
:arrow_down:

...heduler/server/master/service/FailoverService.java
63.80% <0.00%> (-1.10%)
:arrow_down:

...he/dolphinscheduler/server/utils/ProcessUtils.java
28.23% <0.00%> (-1.04%)
:arrow_down:

...olphinscheduler/plugin/alert/email/MailSender.java
51.03% <0.00%> (-0.36%)
:arrow_down:

...r/api/service/impl/WorkFlowLineageServiceImpl.java
33.01% <0.00%> (-0.32%)
:arrow_down:

...nscheduler/service/process/ProcessServiceImpl.java
30.28% <0.00%> (-0.30%)
:arrow_down:

... and 34 more

Continue to review full report at Codecov.

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

Hi. Please review the new code. thx. @Amy0104

@zhongjiajie PTAL.

Thanks for bringing this up


angora::bind_cpu::find_free_cpus incompatible with cpuset

when using docker run with parameter --cpuset-cpus 7, angora-fuzzer crashes in angora::bind_cpu::find_free_cpus.
Could you provide a environment variable for disable find_free_cpus?
When using cpuset, you can read this file for usable cpu: /sys/fs/cgroup/cpuset/cpuset.cpus
 INFO  angora::bind_cpu    > Found 1 cores.
thread 'main' panicked at 'index out of bounds: the len is 1 but the index is 7', /rustc/2aa4c46cfdd726e97360c2734835aa3515e8c858/src/libcore/slice/mod.rs:2461:14
stack backtrace:
   0: std::sys::unix::backtrace::tracing::imp::unwind_backtrace
             at src/libstd/sys/unix/backtrace/tracing/gcc_s.rs:39
   1: std::sys_common::backtrace::_print
             at src/libstd/sys_common/backtrace.rs:70
   2: std::panicking::default_hook::{{closure}}
             at src/libstd/sys_common/backtrace.rs:58
             at src/libstd/panicking.rs:200
   3: std::panicking::default_hook
             at src/libstd/panicking.rs:215
   4: std::panicking::rust_panic_with_hook
             at src/libstd/panicking.rs:478
   5: std::panicking::continue_panic_fmt
             at src/libstd/panicking.rs:385
   6: rust_begin_unwind
             at src/libstd/panicking.rs:312
   7: core::panicking::panic_fmt
             at src/libcore/panicking.rs:85
   8: core::panicking::panic_bounds_check
             at src/libcore/panicking.rs:61
   9: angora::bind_cpu::find_free_cpus
  10: angora::fuzz_main::fuzz_main
  11: fuzzer::main
  12: std::rt::lang_start::{{closure}}
  13: std::panicking::try::do_call
             at src/libstd/rt.rs:49
             at src/libstd/panicking.rs:297
  14: __rust_maybe_catch_panic
             at src/libpanic_unwind/lib.rs:92
  15: std::rt::lang_start_internal
             at src/libstd/panicking.rs:276
             at src/libstd/panic.rs:388
             at src/libstd/rt.rs:48
  16: main
  17: __libc_start_main
  18: _start
 INFO  angora::depot::dump > dump constraints and chart..

Hi @zjuchenyuan. Thanks for you feedback. We have provided environment variable ANGORA_DISABLE_CPU_BINDING for this case. Please update to newest version.

thanks


dfc: 3.0.4 -> 3.0.5

Cc maintainers: @qknight
Successfully built locally.

thanks for your contribution.


 Don't emit any log. Don't time out also. Don't show any nottification as v1.8.0
Steps to reproduce
Steps to reproduce the behavior:
After entering the password the extension start to running the connection, but never complete.
Expected behavior
Connect (I never did it before)
Screenshots
If applicable, add screenshots to help explain your problem.

Environment (please complete the following information):
Client OS: Windows 10 Enterprise 22H2
Extension version:  v1.9.0 (also tried on v. 1.8.0)
SAS version: 9.04.01M7P08062020
Additional context
I usually use SAS Enterprise Guide with the IOM connection.

duplicate to #964, it will be fixed in v1.10

it will be fixed in v1.10

What will be fixed, connection or the log?

it will be fixed in v1.10

What will be fixed, connection or the log?

Both. Or say, they're single issue.


image/jpeg: Decode incorrectly complains about missing SOF marker

http://play.golang.org/p/qUNLzBVraB
The image was generated using ImageMagick and libjpeg's cjpeg and is a valid image with a SOF0 marker, but Decode() complains about invalid JPEG format: missing SOF marker.

If I dump your jpg array to file and then try to decode it I get
$ djpeg ~/Desktop/imm.jpg
Corrupt JPEG data: 3 extraneous bytes before marker 0xc4
Invalid JPEG file structure: SOS before SOF

Are you sure you are using a valid JPEG image?

@ALTree Oops. Something went wrong. Closing the issue as invalid.

For the record, I stumbled across this issue while debugging an image resizer, I had some images that wasn't resized and the error message was the same as this issue, so I tried to get the type of the file and turns out to be png and I forgot to import the png and also gif decoders to my app.
just to save some time for other people who gets here.


Emit compiler diagnostics

Check for error,warning,note and remark in a format compatible with clang and swiftc, see: https://github.com/apple/swift/blob/main/docs/Diagnostics.md
Motivation:
Emit compiler diagnostics, normally redirected to output, now consumable by libSwiftPM users. https://bugs.swift.org/browse/SR-15479

@swift-ci please smoke test

Could you please add a test for this?

this is a nice improvement, thanks for putting the PR together @krzyzanowskim. we need a couple of tests, and one thing to confirm is this won't print errors/warnings multiple times now since I think we were printing the compiler output before? cc @abertelrud

this is a nice improvement, thanks for putting the PR together @krzyzanowskim. we need a couple of tests, and one thing to confirm is this won't print errors/warnings multiple times now since I think we are printing the compiler output in L609?
cc @abertelrud

That's a really good point — I hadn't noticed that.  It does look as if the message would be emitted twice.  For other IDEs I've worked on the pattern is usually to try to recognize it as a diagnostics and if that fails to just print it.
Either way, a unit test would show for sure whether it's printed once or twice now.

I think we are printing the compiler output in L609?

writing to output is parallel to diagnostics. emitting diagnostics is derived from the output as we parse the output. I use it as library and it's handy to have it in diagnostics and in the output stream. Does the SPM CLI print diagnostics too?

I think we are printing the compiler output in L609?

writing to output is parallel to diagnostics. emitting diagnostics is derived from the output as we parse the output. I use it as library and it's handy to have it in diagnostics and in the output stream. Does the SPM CLI print diagnostics too?

Yes, it looks like the SwiftToolObservability struct prints any emitted diagnostics (and I think all observability events emitted during the build reach up to that level).

Yes, it looks like the SwiftToolObservability struct prints any emitted diagnostics (and I think all observability events emitted during the build reach up to that level).

An alternative is to either emit diagnostic or write to the output stream, but not both? while it would work for SwiftToolObservability, not so much for everyone else, am I right? If I'd like to get a build output and save it to eg. a file, I need to merge output stream and diagnostics into a single stream to get it all. Thoughts?

Yes, it looks like the SwiftToolObservability struct prints any emitted diagnostics (and I think all observability events emitted during the build reach up to that level).

An alternative is to either emit diagnostic or write to the output stream, but not both? while it would work for SwiftToolObservability, not so much for everyone else, am I right? If I'd like to get a build output and save it to eg. a file, I need to merge output stream and diagnostics into a single stream to get it all. Thoughts?

Right, that doesn't seem like a great solution.
Another option would be to use the new ability to associate metadata with diagnostics (this is a new feature of ObservabilityScope) to indicate that it was derived by parsing the output text.  Then an observer who is printing text anyway can ignore those diagnostics, while an observer who isn't printing the text can emit them.

Yes, it looks like the SwiftToolObservability struct prints any emitted diagnostics (and I think all observability events emitted during the build reach up to that level).

An alternative is to either emit diagnostic or write to the output stream, but not both? while it would work for SwiftToolObservability, not so much for everyone else, am I right? If I'd like to get a build output and save it to eg. a file, I need to merge output stream and diagnostics into a single stream to get it all. Thoughts?

Right, that doesn't seem like a great solution.
Another option would be to use the new ability to associate metadata with diagnostics (this is a new feature of ObservabilityScope) to indicate that it was derived by parsing the output text. Then an observer who is printing text anyway can ignore those diagnostics, while an observer who isn't printing the text can emit them.

It would be clearer in this case if it were the observer that printed regular output text too — I guess in this case the SwiftTool observer will have to rely no line 609 to have already emitted the output, and just not print diagnostics that are tagged as having been parsed from output text.

Yes, it looks like the SwiftToolObservability struct prints any emitted diagnostics (and I think all observability events emitted during the build reach up to that level).

An alternative is to either emit diagnostic or write to the output stream, but not both? while it would work for SwiftToolObservability, not so much for everyone else, am I right? If I'd like to get a build output and save it to eg. a file, I need to merge output stream and diagnostics into a single stream to get it all. Thoughts?

Right, that doesn't seem like a great solution.
Another option would be to use the new ability to associate metadata with diagnostics (this is a new feature of ObservabilityScope) to indicate that it was derived by parsing the output text. Then an observer who is printing text anyway can ignore those diagnostics, while an observer who isn't printing the text can emit them.

It would be clearer in this case if it were the observer that printed regular output text too — I guess in this case the SwiftTool observer will have to rely no line 609 to have already emitted the output, and just not print diagnostics that are tagged as having been parsed from output text.

lets take a step back here. @krzyzanowskim I assume in your use case are setting a BuildOperationBuildSystemDelegateHandler and it has an outputStream set? if so, where is that pointing?

@tomerd  I use outputStream as a "raw" build log, and in my case, it goes to the file or to the console, depends on what I need. I treat OutputByteStream as raw data without semantic meaning whatsoever, in contrary to Diagnostics that provide useful information.

thanks for the additional info @krzyzanowskim, so in your case it sounds the console output is treated as optional and the diagnostics are the critical part.
@abertelrud iiuc the delegate here was designed to pipe the build-system output to the provided stream, to give users information about the build status, etc. is there any important information expected to be included in this beyond what we consider diagnostics? iow,  should the entire thing be parsed(*) into diagnostics instead of being printed to the stream as-is?

with some failure mode protection in which we fall back to dumping it into the stream

Yes, it looks to me as if it would be better to just use a single sequence of delegate calls here (and no text stream).  Each line of text could really be broken into an info or debug diagnostic if needed — I don't think a fallback is necessary.  I don't know how this evolved but I suspect that it started as just a text stream and then some delegate callbacks were added on top to show the animated progress, but that the text stream wasn't removed.
I think the key would be to get rid of the parallel streams, either by making non-issues become info diagnostics or having separate didSeePlainText and didSeeDiagnostic calls (as in the recent plugin changes).

I guess I didn't really answer the key question there.  Yes, I think the delegate calls about starting and ending certain steps are important because it affects what clients show in terms of status.  We can also model those as debug or info diagnostics (perhaps carrying specific metadata) but it seems cleaner to keep a delegate for such build events.

So the other approach would then be to have a delegate call to handle the diagnostic in-order with the other calls, but that seems at odds with using ObservabilityScope.emit for diagnostics.

Having looked at this a bit more, my specific suggestion for this PR is to:

remove the separate outputStream from BuildOperation
instead send each line of output through the observabilityScope

those that are recognized as errors or warnings have that severity
the others get sent as info

That keeps all the output in order, and everything only gets reported once.
I think the only change compared with what you have here would be to send each line of non-matching output as info.
@krzyzanowskim is that something you'd be willing to take on as part of this?

Having looked at this a bit more, my specific suggestion for this PR

thank you for that. I wasn't sure what's the output of the discussion here was.

@krzyzanowskim is that something you'd be willing to take on as part of this?

yes. I put it on my todo

Having looked at this a bit more, my specific suggestion for this PR

thank you for that. I wasn't sure what's the output of the discussion here was.

Yes, sorry about that — I was exploring ideas out loud, but of course that's not very helpful for the PR author.

@krzyzanowskim is that something you'd be willing to take on as part of this?

yes. I put it on my todo

Great, thanks! Please do ping me here if there are problems or ambiguities and I'll try to be more specific with any recommendations.


(1318) Create and allocate a placement request on assessment approval

This PR adds the concept of placement requests. These objects are created when an assessment has been accepted, and allocated to a Matcher. The matching "algorithm" (such as it is) is pretty naive, but enough to be going on with.
As it stands, the criteria that a placement request has does not directly map to room characteristics, but we've judged that this is OK for now, as we won't (yet) allow searching by the characteristics, and leave it up to the matcher to use their own judgement to find the most applicable place.

As it stands, the criteria that a placement request has does not directly map to room characteristics, but we've judged that this is OK for now, as we won't (yet) allow searching by the characteristics, and leave it up to the matcher to use their own judgement to find the most applicable place.

Are we sure on this?  Adam's doc from the call this morning has "Preloading of Application" section which would suggest prepopulating a search is MVP?


Cannot connect to Bitcoin Core server

Hello, I compiled bitcoin core and am running it via a container image.  The blockchain is fully synchronized.  I can netcat to port 8442 on the same machine I am running Sparrow without issue.  I can also curl it with no issue.  When I try to connect with Sparrow, I see the following error message in the Sparrow log:
2024-02-01 16:14:37,106 ERROR [JavaFX Application Thread] c.s.s.p.ServerPreferencesController [null:-1] Connection error
java.lang.IllegalStateException: I/O error during request processing
	at simple.json.rpc.client@1.3/com.github.arteam.simplejsonrpc.client.builder.ObjectApiBuilder.execute(Unknown Source)
	at simple.json.rpc.client@1.3/com.github.arteam.simplejsonrpc.client.builder.ObjectApiBuilder.invoke(Unknown Source)
	at jdk.proxy2/jdk.proxy2.$Proxy17.getNetworkInfo(Unknown Source)
	at com.sparrowwallet.sparrow@1.8.2/com.sparrowwallet.sparrow.net.cormorant.bitcoind.BitcoindClient.initialize(Unknown Source)
	at com.sparrowwallet.sparrow@1.8.2/com.sparrowwallet.sparrow.net.cormorant.Cormorant.start(Unknown Source)
	at com.sparrowwallet.sparrow@1.8.2/com.sparrowwallet.sparrow.net.ElectrumServer$ConnectionService$1.call(Unknown Source)
	at com.sparrowwallet.sparrow@1.8.2/com.sparrowwallet.sparrow.net.ElectrumServer$ConnectionService$1.call(Unknown Source)
	at javafx.graphics@18/javafx.concurrent.Task$TaskCallable.call(Unknown Source)
	at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
	at javafx.graphics@18/javafx.concurrent.Service.lambda$executeTask$6(Unknown Source)
	at java.base/java.security.AccessController.doPrivileged(Unknown Source)
	at javafx.graphics@18/javafx.concurrent.Service.lambda$executeTask$7(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.base/java.lang.Thread.run(Unknown Source)
Caused by: java.io.FileNotFoundException: http://bitcoind:8332/wallet/cormorant
	at java.base/jdk.internal.reflect.DirectConstructorHandleAccessor.newInstance(Unknown Source)
	at java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Unknown Source)
	at java.base/java.lang.reflect.Constructor.newInstance(Unknown Source)
	at java.base/sun.net.www.protocol.http.HttpURLConnection$10.run(Unknown Source)
	at java.base/sun.net.www.protocol.http.HttpURLConnection$10.run(Unknown Source)
	at java.base/java.security.AccessController.doPrivileged(Unknown Source)
	at java.base/sun.net.www.protocol.http.HttpURLConnection.getChainedException(Unknown Source)
	at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream0(Unknown Source)
	at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
	at com.sparrowwallet.sparrow@1.8.2/com.sparrowwallet.sparrow.net.cormorant.bitcoind.BitcoindTransport.pass(Unknown Source)
	... 15 common frames omitted
Caused by: java.io.FileNotFoundException: http://bitcoind:8332/wallet/cormorant
	at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream0(Unknown Source)
	at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
	at java.base/java.net.HttpURLConnection.getResponseCode(Unknown Source)
	... 16 common frames omitted

The host, bitcoind is exposed over tailscale.  When I curl the URL it tries to hit (http://bitcoind:8332/wallet/cormorant), I receive a 404 HTTP error.
Any clue what might be going on?  I am running Sparrow v1.8.2, Bitcoin Core v26.0

Did you compile Bitcoin Core with wallet support? There may be a previous error in the sparrow log that is relevant.
Closing as it is not a feature or bug report.

@craigraw that is the entirety of the log. Here is how I compiled bitcoin core:
./autogen.sh
./configure --with-gui=no
make

As far as I can tell, this would produce a build with wallet support wouldn't it?

You can also disable wallets with disablewallet=1 in bitcoin.conf.
That said, it may be more of a network configuration issue. Can you try running bitcoin-cli on the machine running Sparrow, configured to talk to your host?

bitcoin-cli seems to work (rpcconnect, rpcport, rpcuser, and rpcpassword are set appropriately in the .conf file referenced, bitcoin-cli running on the the same machine as sparrow):
./bitcoin-cli -conf=/var/home/comminutus/Downloads/bitcoin-26.0-x86_64-linux-gnu/bitcoin-26.0/bitcoin.conf getblockchaininfo
{
  "chain": "main",
  "blocks": 828730,
  "headers": 828730,
  "bestblockhash": "000000000000000000011dc7d7a93e128a9185c7cc855b8c334127b78abcbbbd",
  "difficulty":<PHONE_NUMBER>3893.72,
  "time":<PHONE_NUMBER>,
  "mediantime":<PHONE_NUMBER>,
  "verificationprogress": 0.9999992937843648,
  "initialblockdownload": false,
  "chainwork": "0000000000000000000000000000000000000000687d817cf16da11ee8d358e0",
  "size_on_disk":<PHONE_NUMBER>78,
  "pruned": false,
  "warnings": ""
}

Does Sparrow support Bitcoin Core v26.0?

Yes.
It may be possible that bitcoind is not resolving properly in Sparrow to an IP address. Can you try an IP address instead?

Is this value somehow cached?

I don't think so, but it does seem related to your bitcoind config. Asking the obvious here, you have server=1? It also looks like bitcoind sends a 404 with incorrect user credentials, so that's something to check you have correct in Sparrow as well.

server=1 is indeed set, I don't think bitcoin-cli would work otherwise, right?  I tried changing the password to something very simple thinking perhaps it has something to do with character encoding but I get the same error.
Here's the entirety of the config:
estimatefee=1
printtoconsole=1
minrelaytxfee=0.00001
rpcallowip=<IP_ADDRESS>/8
rpcallowip=<IP_ADDRESS>/12
rpcallowip=<IP_ADDRESS>/16
rpcallowip=<IP_ADDRESS>/10
rpcbind=<IP_ADDRESS>
rpcuser=bitcoin
rpcpassword=<omitted>
server=1
txindex=1
zmqpubrawblock=tcp://<IP_ADDRESS>:28332
zmqpubrawtx=tcp://<IP_ADDRESS>:28332
zmqpubsequence=tcp://<IP_ADDRESS>:28332

If you use curl without the /wallet/cormorant path do you still get a 404?

No, it returns a 405:
curl -s http://<IP_ADDRESS>:8332
JSONRPC server handles only POST requests

curl -w "%{http_code}" -o /dev/null -s http://<IP_ADDRESS>:8332
405

Ok - and do you get the same results if you perform these commands on the machine with Bitcoin Core running, talking to localhost? Apologies if you already covered this above.

Here's where my install is different - I get a 405 response for any wallet, including one to an imaginary wallet:
curl -w "%{http_code}" -o /dev/null -s http://localhost:8332/wallet/justmadethisup
405

So it looks like the problem is either with your install of Bitcoin Core, or the configuration of it. Are you able to interact with the wallet features - for example using bitcoin-cli createwallet?


Bug on compiling code-cracker commit dc6c8d5daa9ede05c1f9e59db2889eba5d4a9fba

Yes, HEAD is at RTM now, you are using VS 2015. Update and it will compile. :)

Thanks it worked!!!


Feature Request: Log Commands in Execute Shell to Audit Log or External Service

Requesting the ability to log all commands executed within a running container via the Execute Shell method in the Rancher UI or CLI. In addition to the Audit Log, this would give a full picture of how authorized users are interacting with running containers and stacks.
If Rancher is between a user and a container, logging the stream to an external service would be beneficial in keeping a history of all activity within an environment and avoid tampering.
Justification
While it's considered an anit-pattern to shell into a running container, if there is an unknown bad-actor in an organization with access to an environment, they could disrupt a stack by running commands via Execute Shell.
Rancher Version:
v1.1.4
Docker Version:
v1.10.3
OS and where are the hosts located? (cloud, bare metal, etc):
RancherOS
Setup Details: (single node rancher vs. HA rancher, internal DB vs. external DB)
Rancher using AWS RDS external DB
Environment Type: (Cattle/Kubernetes/Swarm/Mesos)
Cattle
Steps to Reproduce:
Results:
Expected:

This isn't very practical as it's just a TTY.  The best you could do is get the equivalent of a keystroke recorder, with no context.  Or record both sides and play it back as a TTY, like iTerm can do, but that's considerably more complicated.
I feel like something simpler such as a taintedByMeatbags: true flag on containers that gets automatically set if a shell is ever opened on a container could be almost as effective.

With the release of Rancher 2.0, development on v1.6 is only limited to critical bug fixes and security patches.


Why do I still need to know the id of the vertixes while I use "where" to find the vertixes

The code is just like this:
UPSERT VERTEX 111 SET player.name = "Dwight Howard", player.age = $^.player.age + 11 WHEN $^.player.name == "Ben Simmons" && $^.player.age > 20 YIELD $^.player.name AS Name, $^.player.age AS Age;

please  raise issue in https://github.com/vesoft-inc/nebula-graph

and remember to build index


[firebase_messaging] use _firebaseMessaging.configure in two different places in one application?

I installed _firebaseMessaging.configure in two different places in one application. the first in the root home class, and the second in the chat class. here's my code:
home.dart
....
HomeBodyState({Key key});

@override
  void initState() {
    super.initState();
    _firebaseMessaging.configure(...);
}
....

and chat.dart
....
class ChatBuilderState extends State<ChatBuilder> with AfterLayoutMixin<ChatBuilder> {

@override
  void initState() {
    super.initState();
    _firebaseMessaging.configure(...);
  }
....

the condition is when I receive a message from the cloud, what works is only the configuration in home.dart, while in chat.dart nothing happens. why did it happen?, is there anyone who can help to answer?
thank you,
Best Regards,

abstract your code to configure the firebase messaging only once and attach listeners to your pages where you need them. Make an Inherited Widget above the Widget Tree and initialize firebase there and create stream for the notifications. In the pages where you need to listen for notifications get the inherited widget and listen for the stream there.

Hi @DenisMrGnusa
does @mariogorki94 proposed solution solves your issue?
thank you

As @mariogorki94 pointed out, this is by design. Your code should be setup to use handle the events from a single point of truth.
Will close, but this generally will be documented.


augment the json output to include a unique id for each rule content

this enables external systems to track specific rules and their versions.
probably derive the id from the content of the rule, perhaps via md5(content) or uuid3(content).

https://docs.python.org/3/library/uuid.html#uuid.uuid3

this is no longer needed in the external context, but might still be useful for other users.

closing since nobody needs this feature right now. reopen if the situation changes.


Increase code coverage (2)

As a developer
I'd like to be confident my tests can detect refactoring issues
So I can easily make code changes
Acceptance criteria
Code coverage should be at least 80%
Below is a list of classes which could benefit from some extra testing and should be the focus of this ticket. They are arranged (more or less) in increasing test complexity:
ValidationError
FederatedMetaStore
PrimaryMetaStore
MetastoreUnavailableException
TunnelableFactorySupplier
TunnelingMetaStoreClientFactory
NotifyingFederationService
AdvancedPropertyUtils
PrefixBasedDatabaseMappingService
WaggleDanceConfiguration
YamlStorageConfiguration (trivial)
MonitoringConfiguration
FederatedHMSHandlerFactory
FederatedHMSHandler

@massdosage ValidationError test PR: https://github.com/HotelsDotCom/waggle-dance/pull/104

@massdosage I updated #104 with the tests for FederatedMetaStore and PrimaryMetaStore.

@massdosage Thank you for the feedback so far!
I added a test to NotifyingFederationService to get 100% coverage, but I will need to continue on Thursday (or later today) with TunnelingMetaStoreClientFactory because there are some private and final classes that can't be mocked with the current configuration. I'll spend more time with it and try different strategies and hopefully I can get that to 100% 😄

@courtsVII I updated #104 with the tests for TunnelingMetaStoreClientFactory :)

@massdosage I added tests for AdvancedPropertyUtils and PrefixBasedDatabaseMappingService but they're not at 100% coverage because some of the cases are not testable (unmockable or defensive programming code).
There are also now tests for WaggleDanceConfiguration and YamlStorageConfiguration :)

FederatedHMSHandler will not have any tests added for this issue. The tests that are not covered will be added as part of another issue.


fix conditional comment for meta tag in skeleton

<!--[if !mso]><!-- --> will be parsed as a comment with a text content of [if !mso]><!--
This PR changes the conditional comment in the skeleton to matches the other instances of conditional outlook tags in conditionalTag.js
https://github.com/mjmlio/mjml/blob/604a9f2d2c19a224590814615fda8666fe1fd4e4/packages/mjml-core/src/helpers/conditionalTag.js#L4-L5

@kmcb777 can you test this one ? This seems like a small patch and might fix post process from some ESP

It doesn't seem to cause any problems 👍


Song preview lists "Unknown Song - Unknown Artist"

Checklist:

[X] I have checked that there are no issues with similar or the same content
YOU SHOULD CHECK CLOSED ISSUES AS WELL

[X] I have checked the FAQ (https://github.com/MarshallOfSound/Google-Play-Music-Desktop-Player-UNOFFICIAL-/wiki/FAQ) and the answer I am looking for is not there

[X] I have double checked and can reproduce the issue

OS: Windows 10
GPMDP Version: 4.7.1
Issue Descriptions: On the hover-over of the taskbar icon, the window lists "Unknown Song - Unknown Artist". This also seems to modify what my music-display app SMG can read, as all it can detect is the same unknown message.
Steps to Reproduce: N/A, I'm simply using the YouTube Music app. Issue persisted after a reinstall.

debug_info.zip

See #3888


HideExpression with Nested fields and Default values not working

@aitboudad A Very Happy New Year to you.
I have this following scenario that I am trying to put together and for some reason I am not able to get it to work.
Some details around setup is
I am using the latest version of the formly software
I am using a .ts file to store my filed config which is then imported into the component.

if I try to do hide expression at the key: "mqttv5" level it does not work
If I comment out key: "mqttv5" and set hide expression at field level  key: "sessexpinterval"
a. and comment out its default value, it works and it is added to model when I enter a value.
b. v/s uncomment its default value the field is hidden in the form, but is present in the model with the set default value.

Ideally I would like the hide to work at the higher level (i.e: key: "mqttv5") and some default values for the nested fields be set.
Will appreciate your help in getting this to work.
Thanks
export const SandboxMqttFields: FormlyFieldConfig[] = [
  {
    fieldGroupClassName: "row",
    fieldGroup: [
      {
        type: "select",
        key: "mqttprotover",
        className: "col-12 col-md-3",
        templateOptions: {
          label: "MQTT Version",
          placeholder: " Select MQTT Version",
          options: [
            { label: "V3", value: "3" },
            { label: "V3.1.1", value: "4" },
            { label: "V5", value: "5" },
          ],
          // disabled: true,
        },
      },
     ]
   },
  {
    // key: "mqttv5",
    // hideExpression: 'model.mqttprotover != "5"',   <--- for some reason hide expression does not work at this level
    fieldGroupClassName: "row",
    fieldGroup: [
      {
        type: "input",
        key: "sessexpinterval",
        className: "col-12 col-md-3",
        // defaultValue: 100,                       <-- if default value is uncommented, then field is always present in model
        templateOptions: {
          label: "Session Expiry Interval",
          placeholder: "1000",
          type: "number",
        },
        hideExpression: 'model.mqttprotover != "5"',  <!-- hide expression works here
      },
     // .... I have more fields here that are omitted
     ]
}
]

Happy New Year, check my comment https://github.com/ngx-formly/ngx-formly/issues/704#issuecomment-364661614

Happy New Year, check my comment https://github.com/ngx-formly/ngx-formly/issues/704#issuecomment-364661614

@aitboudad I am having hide expression issue when passing nested object value through json schema, these are the changes I have made here https://stackblitz.com/angular/eyoexxxgvpg?file=src%2Fapp%2Fapp.component.ts in nested.json schema
"hideExpression": "field.parent.model.title === 'test'" => this also I have tried, Am I missing something, please suggest me it will resolve my lot of issues related to disable or hide conditionally

@BhagyashreeCH , I encountered the same issue. Did you eventually find a solution?


added gitUrl to analytics scan

You cannot test this until you have the latest analytics plugin https://github.com/fabric8io/openshift-jenkins-s2i-config/pull/177 merged right ?
Let's hold on merging unless we have the new plugin merged is that ok ?

@sthaha yes it provides the github url..
from my logs "Git URL is git@github.com:yzainee/hellovertx11.git" . As for your query on https vs git@github, I had asked Sam for the format and he was fine with this format. Hence i kept it like this.

@yzainee https://help.github.com/articles/which-remote-url-should-i-use/#cloning-with-https-urls-recommended in case you didn't know