Confusing wording about environment variables

File: engine/reference/builder.md
Regarding the paragraph "The ENV instruction has two forms. The first form, ENV  , will set a single variable to a value. The entire string after the first space will be treated as the  - including characters such as spaces and quotes."
I suggest to consider the variant "The entire string after the second space will be treated as the  ..." as the proper one.

I got this one.

On it!

@urbantom i raised a PR(https://github.com/docker/docker.github.io/pull/2849) to merge in docker:v1.13 as this file not present in master branch

Thanks in behalf of all newbies. ;-)


Check if for R1CS, a single gate can contain more than one degree-2 multiplication

See https://github.com/noir-lang/acvm/pull/77#discussion_r1098543036 for more information

don't think r1cs supports higher degree if I remember correctly

Great catch, made a mistake in the title. Should have said, more than one degree-2 multiplication


Error on Kubernetes Contributor Course

On Section 1 of Contributor Course, page 9, about how K8s community organized it states four group but shows only three.
I believe details about User Group is missing.

Thanks, it was intentional^^;;
User groups are slated to be removed as a form of kubernetes groups - we opted to removed it from the course while we were working on it as it'd be one less thing for us to update when they are officially removed.
/close

I'd accept a PR to change the “four” to “three”, FWIW. However, please note our policy on trivial edits. Usually, bigger updates than one word are the right thing to do.
I'd make an exception here because readers will look for the missing 4th item.


Multicore convolution

Convolutions currently target a single AIE core. This is because targetting multiple cores results in
error: 'aie.memtile_dma' op could not find and assign a valid BD id

See https://github.com/nod-ai/iree-amd-aie/pull/789
This task is to make the required changes to be able to compile to multiple AIE cores.

Update:
I can use a full column of 4 AIE cores with (for conv2d)
 tileSizeLevel0 = {1, 1, OW, 4*OC, 0, 0, 0};
 tileSizeLevel1 = {1, 1, OW, OC, 0, 0, 0};

The above error message is then observed when this is extended to multiple columns:
 tileSizeLevel0 = {1, 2, OW, 4*OC, 0, 0, 0};
 tileSizeLevel1 = {1, 1, OW, OC, 0, 0, 0};

Update:
The problem is that there are these dma start ops which have "index" gte 6:
  %13 = aie.dma_start(S2MM, 7, ^bb40, ^bb42)

They are created in lower-to-aie.


Parsing issue for intrinsic function Fn::Sub.

If the value for the intrinsic function Fn::Sub does not contain a variable to be replaced, starting with "${" ending with "}", then parsing fails.
"Description": {           "Fn::Sub": "Some value without a variable to be replaced"         }
Error occurs at this line of code: delimited(tag("${"), take_until("}"), take(1usize))
fn inner_resolver(str: &str) -> IResult<&str, SubValue> {
    let ir = alt((
        map(
            delimited(tag("${"), take_until("}"), take(1usize)),
            |var: &str| SubValue::Variable(var.to_string()),
        ),
        map(take_until("${"), |static_str: &str| {
            SubValue::String(static_str.to_string())
        }),
    ))(str);

    let (remaining, res) = ir?;
    IResult::Ok((remaining, res))
}

Note, I'm not actually able to reproduce the issue you are having. I am adding this test:
#[test]
fn test_parse_tree_sub_str_no_replacements() {
    let a = serde_json::json!({
        "LogicalResource": {
            "Type": "AWS::IAM::Role",
            "Properties": {
                "RoleName": {
                    "Fn::Sub": "bobs-roleio"
                }
            }
        }
    });

    let resource = ResourceParseTree {
        name: "LogicalResource".into(),
        condition: Option::None,
        metadata: Option::None,
        update_policy: Option::None,
        deletion_policy: Option::None,
        dependencies: vec![],
        resource_type: "AWS::IAM::Role".into(),
        properties: map! {
            "RoleName" => ResourceValue::Sub(vec![ResourceValue::String("bobs-roleio".into())])
        },
    };
    assert_resource_equal(a, resource);
}

which essentially has a Sub with no variable to be replaced. Nothing bad occurs though and the test passes. Can you send a sample resource that matches the issue described?

Oh wait, the parse tree only happens during IR output. Let me create a better test.

Finally reproed:
    #[test]
    fn test_no_substitution() -> Result<(), TransmuteError> {
        let v = sub_parse_tree("NoSubstitution")?;
        assert_eq!(
            v,
            vec![
                SubValue::String(String::from("NoSubstitution"))
            ]
        );

        Ok(())
    }

Time to fix :)

Fixed! Closing, thanks for the heads up of the bug.


Add major, minor, makedev functions

Only for Linux and Android currently, though they also exist on BSDs

Wow I had no idea the identifiers major and minor were macros in C...
@bors: r+

:pushpin: Commit dbdce80 has been approved by alexcrichton

:hourglass: Testing commit dbdce80 with merge 25b6092...

@bors: retry

:hourglass: Testing commit dbdce80 with merge 44805ff...

:sunny: Test successful - status-appveyor, status-travis
Approved by: alexcrichton
Pushing 44805ffd03a9088b2fd75c03d9162fa5744f67c5 to master...


publish<EMAIL_ADDRESS>

Requested by: @lforst
Merge target: deno-publish-test
Quick links:

View changes
View check runs

Assign the accepted label to this issue to approve the release.
Leave the #retract comment under this issue to retract the release (original issuer only).
Targets

[ ] npm[@sentry/types]
[ ] npm[@sentry/utils]
[ ] npm[@sentry/core]
[ ] npm[@sentry-internal/tracing]
[ ] npm[@sentry/replay]
[ ] npm[@sentry/opentelemetry]
[ ] npm[@sentry/browser]
[ ] npm[@sentry/node]
[ ] npm[@sentry/angular-ivy]
[ ] npm[@sentry/angular]
[ ] npm[@sentry/ember]
[ ] npm[@sentry/react]
[ ] npm[@sentry/svelte]
[ ] npm[@sentry/vue]
[ ] npm[@sentry/wasm]
[ ] npm[@sentry/integrations]
[ ] npm[@sentry/vercel-edge]
[ ] npm[@sentry/deno]
[ ] commit-on-git-repository
[x] npm[@sentry/types]
[x] npm[@sentry/utils]
[x] npm[@sentry/core]
[x] npm[@sentry-internal/tracing]
[x] npm[@sentry/replay]
[x] npm[@sentry/opentelemetry]
[x] npm[@sentry/browser]
[x] npm[@sentry/node]
[x] npm[@sentry/angular-ivy]
[x] npm[@sentry/angular]
[x] npm[@sentry/ember]
[x] npm[@sentry/react]
[x] npm[@sentry/svelte]
[x] npm[@sentry/vue]
[x] npm[@sentry/wasm]
[x] npm[@sentry/integrations]
[x] npm[@sentry/vercel-edge]
[x] npm[@sentry/deno]
[ ] npm[@sentry/serverless]
[ ] npm[@sentry/opentelemetry-node]
[ ] npm[@sentry/bun]
[ ] npm[@sentry/nextjs]
[ ] npm[@sentry/remix]
[ ] npm[@sentry/sveltekit]
[ ] npm[@sentry/gatsby]
[ ] npm[@sentry/astro]
[ ] npm[@sentry-internal/typescript]
[ ] npm[@sentry-internal/eslint-plugin-sdk]
[ ] npm[@sentry-internal/eslint-config-sdk]
[ ] npm[@sentry/hub]
[ ] npm[@sentry/tracing]
[ ] npm[@sentry/node-experimental]
[ ] aws-lambda-layer
[ ] gcs[browser-cdn-bundles]
[ ] github
[ ] registry

Targets marked with a checkbox have already been executed.  Administrators can manually tick a checkbox to force craft to skip it.

#retract


Why: I noticed that we're actually shipping everything under content/ to everyone due to the way webpack is bundling up our dynamic require statements.

How: No time to chat right now. Still a WIP. Take a look if you're interested!
A few requirements of this approach:

Static export builds of the website for every locale (with the LOCALE environment variable set)
Move most of the content from .js files to .md files. The babel plugin that I've written can handle both!
Use import statements (can't do require) and the import source must include content to be transpiled. These limitations could be worked on, but I think this is alright for now.

Things are busted all over, but the /examples page should be working :)

I'm getting very close on this one! If I could get a few reviewers on it that would be wonderful!

Check it out! These are static (crazy fast) and autoscaled for free!
https://en-ghdsoalvem.now.sh/
https://fr-ayvcehlqpw.now.sh
https://es-zzavqyjmew.now.sh/
Boo yah!

I'm going to update contributing docs, then I'm going to go ahead and merge this so we can get things going elsewhere. Let's fail forward! I'm so much happier with this stuff!

🎉🎉🎉 Obviously the language selection is busted on those, but it should sort itself out on the rc, right?

Obviously the language selection is busted on those, but it should sort itself out on the rc, right?

Yes! I had considered making it work, but decided it probably wouldn't be worth it right now...

Woo! I hope the master deploy works. That bit can't easily be tested 😅

We'll know soon enough. 😀

It works! (after a few extra commits 😅)

Should all of the content of the components need to be changed to markdown?
Something like tdeschryver/glamorous-website/ component-content-md

Yeah, we could do that. For some reason I thought it would be nice to support both, but probably no real reason to do that. Feel free to open that as a PR :) Thanks!


getting rid of svn, making sure we cache npm install api

So basically yarn is a pain on circleci for the moment (issues for node-gyp, mocha, phantomjs), but I figured that we could already save 3-4 minutes by making sure we cache the result of api> npm install on circleci instead of rebuilding the api every time we want to run the e2e tests :-)


CI is broken without changing anything

CI is now failing, but was completely green two weeks ago
On the same commit, attempt 1

Attempt 2:

Here is the error

We merged a PR recently, but the CI succeeded: https://github.com/meilisearch/meilisearch-symfony/pull/329
If someone has any clue.
@norkunas if you are around 😇

This is because Symfony Serializer has a bug, nothing we can do about it, and people should add conflicts in their projects with that version :)

Should be fixed now with Symfony 7.0.7.


[Wait For #580] [CS/Refactor] Migrate to MVP style

This patch layouts Customshortcut refactor. It is being migrated
Model-View-Presenter pattern for clarity.
Changes proposed in this PR:

Add presenter_* to main presenter function
Add util_* to data for utility function
Some static function residing in view.c has exposed
Strict segregation between view and data change

Resolves #577
Self evaluation:

Build test: [X]Passed [ ]Failed [ ]Skipped
Run test: [X]Passed [ ]Failed [ ]Skipped

Signed-off-by: Jihoon Lee<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.4.20191203. Thank you for submitting PR #586. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://nnsuite.mooo.com/.

:octocat: cibot: @zhoonit, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnsuite.mooo.com/nntrainer/ci/repo-workers/pr-checker/586-202009231156360.009782075881958-3cf838810652d30e4773516b9cad4fd1fc9ca404/.

semantics:
** view handles view only **
creating, setting views are done. (controlling views are done in edje)
callback only related to view is registered inside view/view
** data handles data only **
data is changed at data_* only. (except very simple data like ad->tried`
** presenter manipulates data and view **
callback that invovles changing data is registered at main/presenter
presenter has view and data
reposition:
data/data_parse_route -> data/util_parse_route
data/data_get_resource_path -> data/util_get_resource_path
view/process_train_result -> data/data_update_train_result
view/on_draw_proceed_infer_  -> main/presenter_on_canvas_submit_inference
view/on_draw_proceed_training_  -> main/presenter_on_canvas_submit_training
view/train -> presenter/train_ (facade)
view/create_canvas_ -> view/view_init_canvas
new methods:
data_update_draw_target
data_handle_path_data (page spsecific data initiation)
presenter/init_page_ (page specific view initiataion, facade)
rearranged :
view/on_routes_to_ + view/routes_to -> main/presenter_on_routes_request + presenter/routes_to_(facade)
view/set_draw_texts_ + view/canvas_erase_all_ -> view/view_set_canvas_clean


Modbus TCP: "PortNotOpenError: Port Not Open"

I'm submitting a ...
Problem

(x) unexpected behavior

Current behavior

My device doesn't maintain permanent TCP connection and close after 1.5 second or so. Single FC 3 request rise the list of errors:
TypeError: Cannot read property 'getMachineState' of undefined
PortNotOpenError: Port Not Open
FSM Reset On State [object Object]
Client -> try to reconnect by init in 100 ms TCP@<IP_ADDRESS>:502 default Unit-Id: 1
Client -> try to reconnect by init in 100 ms TCP@<IP_ADDRESS>:502 default Unit-Id: 1
FSM Reset On State [object Object]
Client -> try to reconnect by init in 100 ms TCP@<IP_ADDRESS>:502 default Unit-Id: 1
Client -> reconnect in 100 ms TCP@<IP_ADDRESS>:502 default Unit-Id: 1
Client -> reconnect in 100 ms TCP@<IP_ADDRESS>:502 default Unit-Id: 1
Client -> reconnect in 100 ms TCP@<IP_ADDRESS>:502 default Unit-Id: 1
and log from console:
5 Dec 09:08:04 - [error] [modbus-flex-getter:Shtyl] TypeError: Cannot read property 'getMachineState' of undefined
    at Object._inputCallback (/data/node_modules/node-red-contrib-modbus/modbus/maps/modbus-flex-getter.js:123:61)
    at Object.Node._emitInput (/usr/src/node-red/node_modules/@node-red/runtime/lib/nodes/Node.js:199:18)
    at Immediate._onImmediate (/usr/src/node-red/node_modules/@node-red/runtime/lib/nodes/Node.js:179:33)
    at runCallback (timers.js:705:18)
    at tryOnImmediate (timers.js:676:5)
    at processImmediate (timers.js:658:5)
5 Dec 09:08:04 - [error] [modbus-flex-getter:Shtyl] PortNotOpenError: Port Not Open
    at ModbusRTU.writeFC4 (/data/node_modules/modbus-serial/index.js:501:24)
    at ModbusRTU.writeFC3 (/data/node_modules/modbus-serial/index.js:487:10)
    at /data/node_modules/modbus-serial/apis/promise.js:48:31
    at new Promise (<anonymous>)
    at ModbusRTU.readHoldingRegisters (/data/node_modules/modbus-serial/apis/promise.js:39:27)
    at Object.noneCommandSent [as callModbus] (/data/node_modules/node-red-contrib-modbus/modbus/maps/modbus-client.js:550:7)
    at Object.sequentialDequeueCommand (/data/node_modules/node-red-contrib-modbus/modbus/maps/modbus-client.js:140:13)
    at Timeout.r.dequeueCommand [as _onTimeout] (/data/node_modules/node-red-contrib-modbus/modbus/maps/modbus-client.js:172:14)
    at ontimeout (timers.js:436:11)
    at tryOnTimeout (timers.js:300:5)
    at listOnTimeout (timers.js:263:5)
    at Timer.processTimers (timers.js:223:10)
5 Dec 09:08:04 - [warn] [modbus-flex-getter:Shtyl] FSM Reset On State [object Object]
5 Dec 09:08:04 - [warn] [modbus-client:Shtyl-dacha] Client -> try to reconnect by init in 100 ms TCP@<IP_ADDRESS>:502 default Unit-Id: 1
5 Dec 09:08:04 - [warn] [modbus-flex-getter:Shtyl] FSM Reset On State [object Object]
5 Dec 09:08:04 - [warn] [modbus-client:Shtyl-dacha] Client -> try to reconnect by init in 100 ms TCP@<IP_ADDRESS>:502 default Unit-Id: 1
5 Dec 09:08:05 - [warn] [modbus-client:Shtyl-dacha] Client -> reconnect in 100 ms TCP@<IP_ADDRESS>:502 default Unit-Id: 1
5 Dec 09:08:05 - [warn] [modbus-client:Shtyl-dacha] Client -> reconnect in 100 ms TCP@<IP_ADDRESS>:502 default Unit-Id: 1
5 Dec 09:08:05 - [warn] [modbus-client:Shtyl-dacha] Client -> reconnect in 100 ms TCP@<IP_ADDRESS>:502 default Unit-Id: 1
no response for request, request is lost. The only workaround, constantly send requests, in that case only first one is lost.
Expected behavior

Process a request. If port is closed, should open connection and process a request.
Minimal reproduction of the problem with instructions

Create simple flow with Getter or FlexGetter node with TCP connection.
Device should close connection.
Send FC 3 request
in result list of errors and no response.

Your Environment
Please tell us about your environment:

(x) I am using just the Node-RED package and got modbus-serial package installed with it

( ) I have installed modbus-serial package global from source (using git clone)

( ) I have installed modbus-serial as a global package (using npm i -g)

node-red-contrib-modbus version: 5.1.0

Node: (min. 6.x)
node --version = v10.17.0
Node-RED 1.0.3 docker on raspberry PI

I tried the fix, doesn't help. List of errors and no answer to request.
Log after d0d3b23 commit:
7 Dec 12:08:55 - [error] [modbus-flex-getter:Shtyl] PortNotOpenError: Port Not Open
    at ModbusRTU.writeFC4 (/data/node_modules/modbus-serial/index.js:501:24)
    at ModbusRTU.writeFC3 (/data/node_modules/modbus-serial/index.js:487:10)
    at /data/node_modules/modbus-serial/apis/promise.js:48:31
    at new Promise (<anonymous>)
    at ModbusRTU.converted [as readHoldingRegisters] (/data/node_modules/modbus-serial/apis/promise.js:39:27)
    at Object.ModbusClientNode.node.readModbus [as callModbus] (/data/node_modules/node-red-contrib-modbus/modbus/modbus-client.js:571:25)
    at ModbusClientNode.node.sequentialDequeueCommand (/data/node_modules/node-red-contrib-modbus/modbus/modbus-client.js:141:21)
    at Timeout.ModbusClientNode.node.dequeueCommand [as _onTimeout] (/data/node_modules/node-red-contrib-modbus/modbus/modbus-client.js:172:14)
    at ontimeout (timers.js:436:11)
    at tryOnTimeout (timers.js:300:5)
    at listOnTimeout (timers.js:263:5)
    at Timer.processTimers (timers.js:223:10)
7 Dec 12:08:55 - [warn] [modbus-flex-getter:Shtyl] FSM Reset On State [object Object]
7 Dec 12:08:55 - [warn] [modbus-client:Shtyl-dacha] Client -> try to reconnect by init in 100 ms TCP@<IP_ADDRESS>:502 default Unit-Id: 1
7 Dec 12:08:55 - [warn] [modbus-flex-getter:Shtyl] FSM Reset On State [object Object]
7 Dec 12:08:55 - [warn] [modbus-client:Shtyl-dacha] Client -> try to reconnect by init in 100 ms TCP@<IP_ADDRESS>:502 default Unit-Id: 1
7 Dec 12:08:55 - [warn] [modbus-client:Shtyl-dacha] Client -> reconnect in 100 ms TCP@<IP_ADDRESS>:502 default Unit-Id: 1
7 Dec 12:08:55 - [warn] [modbus-client:Shtyl-dacha] Client -> reconnect in 100 ms TCP@<IP_ADDRESS>:502 default Unit-Id: 1
7 Dec 12:08:55 - [warn] [modbus-client:Shtyl-dacha] Client -> reconnect in 100 ms TCP@<IP_ADDRESS>:502 default Unit-Id: 1

I'll give a fix to that in the next few days. That is a bug with the new state machine and it was not to see by testing. I have to add more tests here to take care about that problems with the FSM.

Same error with previous FSM, readModbus should catch PortNotOpenError

@mikeS7 could you add some logs, please? https://github.com/BiancoRoyal/node-red-contrib-modbus/wiki/DEBUG
DEBUG=contribModbus*,modbus-serial

@biancode done:
2019-12-07T10:22:18.090Z contribModbus:core:client Client -> new
2019-12-07T10:22:18.093Z contribModbus:core:client Client -> initialized
2019-12-07T10:22:19.200Z contribModbus:core:client Client -> init
7 Dec 13:22:19 - [warn] [modbus-client:Shtyl-dacha] Client -> reconnect in 100 ms TCP@<IP_ADDRESS>:502 default Unit-Id: 1
7 Dec 13:22:19 - [info] Started flows
2019-12-07T10:22:19.823Z contribModbus:core:client Client -> TCP port TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-07T10:22:19.917Z modbus-serial TCP port: signal connect
2019-12-07T10:22:19.921Z contribModbus:core:client Client -> connected TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-07T10:22:19.923Z contribModbus:core:client Client -> activated TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-07T10:22:19.924Z contribModbus:core:client Client -> queueing TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-07T10:22:19.964Z contribModbus:core:client Client -> {"state":"queueing","message":"dequeue command tcp","delay":1} TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-07T10:22:19.967Z contribModbus:core:client Client -> {"type":"queue check is not a unit","unitid":null} TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-07T10:22:19.968Z contribModbus:core:client Client -> empty TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-07T10:22:21.392Z modbus-serial TCP port: signal close: false
2019-12-07T10:23:00.294Z contribModbus:core:client Client -> {"info":"push to Queue by Unit-Id","message":{"unitid":1,"fc":3,"address":501,"quantity":1,"messageId":"5deb7d8403d2563971aee44a"},"unit":1} TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-07T10:23:00.295Z contribModbus:core:client Client -> queueing TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-07T10:23:00.297Z contribModbus:core:client Client -> {"info":"queue read msg","message":{"unitid":1,"fc":3,"address":501,"quantity":1,"messageId":"5deb7d8403d2563971aee44a"},"state":"empty","queueLength":1} TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-07T10:23:00.299Z contribModbus:core:client Client -> {"state":"queueing","message":"dequeue command tcp","delay":1} TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-07T10:23:00.300Z contribModbus:core:client Client -> {"type":"queue check","unitid":1,"sendAllowed":true,"queueLength":1} TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-07T10:23:00.301Z contribModbus:core:client Client -> {"type":"serial sending and wait","unitid":1,"queueLength":0,"sendAllowedForNext":false,"delay":1} TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-07T10:23:00.305Z contribModbus:core:client Client -> {"info":"read msg","message":{"unitid":1,"fc":3,"address":501,"quantity":1,"messageId":"5deb7d8403d2563971aee44a"},"unitid":1,"timeout":1000,"state":"queueing"} TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-07T10:23:00.314Z contribModbus:core:client Client -> {"info":"queue response activate sending","message":{"unitid":1,"fc":3,"address":501,"quantity":1,"messageId":"5deb7d8403d2563971aee44a"}} TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-07T10:23:00.315Z contribModbus:core:client Client -> activated TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-07T10:23:00.316Z contribModbus:core:client Client -> queueing TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-07T10:23:00.318Z contribModbus:flex:getter Port Not Open
7 Dec 13:23:00 - [error] [modbus-flex-getter:Shtyl] PortNotOpenError: Port Not Open
at ModbusRTU.writeFC4 (/data/node_modules/modbus-serial/index.js:501:24)
at ModbusRTU.writeFC3 (/data/node_modules/modbus-serial/index.js:487:10)
at /data/node_modules/modbus-serial/apis/promise.js:48:31
at new Promise ()
at ModbusRTU.converted [as readHoldingRegisters] (/data/node_modules/modbus-serial/apis/promise.js:39:27)
at Object.ModbusClientNode.node.readModbus [as callModbus] (/data/node_modules/node-red-contrib-modbus/modbus/modbus-client.js:571:25)
at ModbusClientNode.node.sequentialDequeueCommand (/data/node_modules/node-red-contrib-modbus/modbus/modbus-client.js:141:21)
at Timeout.ModbusClientNode.node.dequeueCommand [as _onTimeout] (/data/node_modules/node-red-contrib-modbus/modbus/modbus-client.js:172:14)
at ontimeout (timers.js:436:11)
at tryOnTimeout (timers.js:300:5)
at listOnTimeout (timers.js:263:5)
at Timer.processTimers (timers.js:223:10)
2019-12-07T10:23:00.353Z contribModbus:core:client Client -> failed TCP@<IP_ADDRESS>:502 default Unit-Id: 1
7 Dec 13:23:00 - [warn] [modbus-flex-getter:Shtyl] FSM Reset On State [object Object]
2019-12-07T10:23:00.357Z contribModbus:core:client Client -> broken TCP@<IP_ADDRESS>:502 default Unit-Id: 1
7 Dec 13:23:00 - [warn] [modbus-client:Shtyl-dacha] Client -> try to reconnect by init in 100 ms TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-07T10:23:00.360Z contribModbus:core:client Client -> closed TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-07T10:23:00.362Z contribModbus:core:client Client -> broken TCP@<IP_ADDRESS>:502 default Unit-Id: 1
7 Dec 13:23:00 - [warn] [modbus-client:Shtyl-dacha] Client -> try to reconnect by init in 100 ms TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-07T10:23:00.371Z modbus-serial modbusErrorHandling:Port Not Open
2019-12-07T10:23:00.372Z contribModbus:core:client Client -> failed TCP@<IP_ADDRESS>:502 default Unit-Id: 1
7 Dec 13:23:00 - [warn] [modbus-flex-getter:Shtyl] FSM Reset On State [object Object]
2019-12-07T10:23:00.374Z contribModbus:core:client Client -> broken TCP@<IP_ADDRESS>:502 default Unit-Id: 1
7 Dec 13:23:00 - [warn] [modbus-client:Shtyl-dacha] Client -> try to reconnect by init in 100 ms TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-07T10:23:00.377Z contribModbus:core:client Client -> {"state":"broken","message":"dequeue command disallowed state","delay":1} TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-07T10:23:00.460Z contribModbus:core:client Client -> init TCP@<IP_ADDRESS>:502 default Unit-Id: 1
7 Dec 13:23:00 - [warn] [modbus-client:Shtyl-dacha] Client -> reconnect in 100 ms TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-07T10:23:00.467Z contribModbus:core:client Client -> init TCP@<IP_ADDRESS>:502 default Unit-Id: 1
7 Dec 13:23:00 - [warn] [modbus-client:Shtyl-dacha] Client -> reconnect in 100 ms TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-07T10:23:00.476Z contribModbus:core:client Client -> init TCP@<IP_ADDRESS>:502 default Unit-Id: 1
7 Dec 13:23:00 - [warn] [modbus-client:Shtyl-dacha] Client -> reconnect in 100 ms TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-07T10:23:00.564Z contribModbus:core:client Client -> TCP port TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-07T10:23:00.573Z contribModbus:core:client Client -> TCP port TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-07T10:23:00.579Z contribModbus:core:client Client -> TCP port TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-07T10:23:00.741Z modbus-serial TCP port: signal connect
2019-12-07T10:23:00.742Z contribModbus:core:client Client -> connection closed TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-07T10:23:00.955Z modbus-serial TCP port: signal close: false
2019-12-07T10:23:00.998Z modbus-serial TCP port: signal connect
2019-12-07T10:23:00.999Z contribModbus:core:client Client -> connection closed TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-07T10:23:01.235Z modbus-serial TCP port: signal close: false
2019-12-07T10:23:01.694Z modbus-serial TCP port: signal connect
2019-12-07T10:23:01.696Z contribModbus:core:client Client -> connected TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-07T10:23:01.697Z contribModbus:core:client Client -> activated TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-07T10:23:01.698Z contribModbus:core:client Client -> queueing TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-07T10:23:01.699Z contribModbus:core:client Client -> {"state":"queueing","message":"dequeue command tcp","delay":1} TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-07T10:23:01.700Z contribModbus:core:client Client -> {"type":"queue check is not a unit","unitid":null} TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-07T10:23:01.701Z contribModbus:core:client Client -> empty TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-07T10:23:03.216Z modbus-serial TCP port: signal close: false

From the log, it should be OK to reconnect on the first request after connection gets lost, but if it gets no answer while timeout, then it reconnects again. It looks like your port is not ready to connect. What is the timeout value?

Timeout 1 sec, tried 2 sec without success

Unfortunately issue is not  solved in 5.2.0. Tomorrow will provide logs and working example with modbus-serial logger.

Please, check the port settings in docker and firewall
hint:
sudo usermod -a -G tty $username
sudo usermod -a -G dailout $username

sudo usermod -a -G tty $username
sudo usermod -a -G dailout $username

What is relation to TCP?

I modified logger.js example a bit to add timing to console output:
/* eslint-disable no-console, spaced-comment */

// create an empty modbus client
var ModbusRTU = require("modbus-serial");
// var ModbusRTU = require("../index");
var client = new ModbusRTU();
var timeoutRunRef = null;
var timeoutConnectRef = null;

var networkErrors = [
    "ESOCKETTIMEDOUT",
    "ETIMEDOUT",
    "ECONNRESET",
    "ECONNREFUSED",
    "EHOSTUNREACH",
    "ENETRESET",
    "ECONNABORTED",
    "ENETUNREACH",
    "ENOTCONN",
    "ESHUTDOWN",
    "EHOSTDOWN",
    "ENETDOWN",
    "EWOULDBLOCK",
    "EAGAIN"
];

// check error, and reconnect if needed
function checkError(e) {
    if(e.errno && networkErrors.includes(e.errno)) {
        console.log(new Date().toISOString(), "we have to reconnect");

        // close port
        client.close();

        // re open client
        client = new ModbusRTU();
        timeoutConnectRef = setTimeout(connect, 0);
    }
}

// open connection to a serial port
function connect() {
    // clear pending timeouts
    clearTimeout(timeoutConnectRef);

    // if client already open, just run
    if (client.isOpen) {
        run();
    }

    // if client closed, open a new connection
    client.connectTCP("<IP_ADDRESS>", { port: 502 })
        .then(setClient)
        .then(function() {
            console.log(new Date().toISOString(), "Connected"); })
        .catch(function(e) {
            checkError(e);
            console.log(new Date().toISOString(), e.message); });
}

function setClient() {
    // set the client's unit id
    // set a timout for requests default is null (no timeout)
    client.setID(1);
    client.setTimeout(1000);

    // run program
    run();
}

function run() {
    // clear pending timeouts
    clearTimeout(timeoutRunRef);

    // read the 4 registers starting at address 5
    client.readHoldingRegisters(200, 7)
        .then(function(d) {
            console.log(new Date().toISOString(), "Receive:", d.data);
            })
        .then(function() {
            timeoutRunRef = setTimeout(run, 1000); })
        .catch(function(e) {
            checkError(e);
            console.log(new Date().toISOString(), e.message); });
}

// connect and start logging
connect();

Output with 1000 msec timeout:
/usr/src/app # node logger.js
2019-12-09T18:05:12.832Z Connected
2019-12-09T18:05:13.027Z Receive: [ 2375, 2381, 2393, 9, 8, 8, 501 ]
2019-12-09T18:05:14.215Z Receive: [ 2374, 2380, 2394, 9, 9, 8, 501 ]
2019-12-09T18:05:15.377Z Receive: [ 2374, 2383, 2395, 9, 9, 8, 501 ]
2019-12-09T18:05:16.545Z Receive: [ 2376, 2383, 2395, 9, 9, 8, 501 ]
2019-12-09T18:05:17.697Z Receive: [ 2373, 2380, 2392, 9, 9, 8, 501 ]
2019-12-09T18:05:18.864Z Receive: [ 2373, 2380, 2391, 9, 9, 8, 501 ]
2019-12-09T18:05:20.024Z Receive: [ 2373, 2380, 2391, 9, 9, 8, 501 ]
2019-12-09T18:05:21.176Z Receive: [ 2375, 2382, 2393, 9, 9, 8, 501 ]
2019-12-09T18:05:22.340Z Receive: [ 2371, 2375, 2387, 9, 9, 8, 501 ]
2019-12-09T18:05:23.504Z Receive: [ 2371, 2377, 2386, 9, 9, 8, 501 ]
2019-12-09T18:05:24.641Z Receive: [ 2368, 2376, 2387, 9, 9, 8, 501 ]
2019-12-09T18:05:25.790Z Receive: [ 2368, 2376, 2389, 9, 9, 8, 501 ]
2019-12-09T18:05:26.936Z Receive: [ 2371, 2383, 2392, 8, 8, 8, 501 ]
2019-12-09T18:05:28.028Z Receive: [ 2370, 2383, 2390, 8, 8, 8, 501 ]
2019-12-09T18:05:29.205Z Receive: [ 2373, 2386, 2394, 8, 8, 7, 501 ]
2019-12-09T18:05:30.360Z Receive: [ 2369, 2380, 2388, 8, 8, 7, 501 ]
2019-12-09T18:05:31.496Z Receive: [ 2372, 2382, 2390, 8, 8, 7, 501 ]
2019-12-09T18:05:32.656Z Receive: [ 2369, 2381, 2389, 8, 8, 7, 501 ]
2019-12-09T18:05:33.740Z Receive: [ 2372, 2381, 2390, 8, 8, 7, 501 ]
2019-12-09T18:05:34.890Z Receive: [ 2372, 2381, 2390, 8, 8, 7, 501 ]
2019-12-09T18:05:36.029Z Receive: [ 2371, 2383, 2391, 8, 8, 7, 501 ]
2019-12-09T18:05:37.177Z Receive: [ 2377, 2379, 2390, 8, 8, 7, 501 ]
2019-12-09T18:05:38.365Z Receive: [ 2379, 2380, 2393, 8, 8, 7, 501 ]
2019-12-09T18:05:39.446Z Receive: [ 2376, 2370, 2401, 8, 8, 7, 501 ]
2019-12-09T18:05:40.596Z Receive: [ 2378, 2369, 2402, 8, 8, 7, 501 ]
2019-12-09T18:05:41.602Z we have to reconnect
2019-12-09T18:05:41.606Z Port Not Open
2019-12-09T18:05:41.648Z Connected
2019-12-09T18:05:41.877Z Receive: [ 2376, 2369, 2401, 8, 8, 7, 501 ]
2019-12-09T18:05:43.040Z Receive: [ 2376, 2368, 2399, 8, 8, 7, 501 ]
2019-12-09T18:05:44.177Z Receive: [ 2377, 2368, 2399, 8, 8, 7, 501 ]
2019-12-09T18:05:45.348Z Receive: [ 2381, 2377, 2386, 8, 8, 7, 501 ]
2019-12-09T18:05:46.514Z Receive: [ 2379, 2375, 2394, 8, 8, 7, 501 ]
2019-12-09T18:05:47.669Z Receive: [ 2378, 2377, 2395, 8, 8, 7, 501 ]
2019-12-09T18:05:48.838Z Receive: [ 2381, 2377, 2397, 8, 8, 7, 501 ]
2019-12-09T18:05:50.000Z Receive: [ 2381, 2377, 2397, 8, 8, 7, 501 ]

2000 msec timeout:
/usr/src/app # node logger.js
2019-12-09T18:08:00.678Z Connected
2019-12-09T18:08:00.874Z Receive: [ 2377, 2372, 2402, 8, 8, 7, 501 ]
2019-12-09T18:08:02.905Z we have to reconnect
2019-12-09T18:08:02.910Z Port Not Open
2019-12-09T18:08:02.982Z Connected
2019-12-09T18:08:03.241Z Receive: [ 2375, 2371, 2397, 8, 8, 7, 501 ]
2019-12-09T18:08:05.246Z we have to reconnect
2019-12-09T18:08:05.247Z Port Not Open
2019-12-09T18:08:05.291Z Connected
2019-12-09T18:08:05.529Z Receive: [ 2371, 2369, 2395, 8, 8, 7, 501 ]
2019-12-09T18:08:07.533Z we have to reconnect
2019-12-09T18:08:07.534Z Port Not Open
2019-12-09T18:08:07.592Z Connected
2019-12-09T18:08:07.794Z Receive: [ 2369, 2366, 2392, 8, 8, 7, 501 ]

Node-Red settings:

simple payload:
{
    "fc": 3,
    "unitid": 1,
    "address": 200,
    "quantity": 7
}

I've got the following without actual response:
9 Dec 21:20:28 - [info] Stopping modified flows
9 Dec 21:20:28 - [warn] [modbus-flex-getter:Shtyl] FSM Reset On State {"value":"failed","actions":[],"changed":true}
9 Dec 21:20:28 - [warn] [modbus-client:Shtyl] Client -> try to reconnect by init in 2000 ms TCP@<IP_ADDRESS>:502 default Unit-Id: 1
9 Dec 21:20:28 - [info] Stopped modified flows
9 Dec 21:20:28 - [info] Starting modified flows
9 Dec 21:20:28 - [warn] [modbus-client:Shtyl] Client -> reconnect in 2000 ms TCP@<IP_ADDRESS>:502 default Unit-Id: 1
9 Dec 21:20:28 - [info] Started modified flows
9 Dec 21:20:32 - [error] [modbus-flex-getter:Shtyl] PortNotOpenError: Port Not Open
    at ModbusRTU.writeFC4 (/data/node_modules/modbus-serial/index.js:501:24)
    at ModbusRTU.writeFC3 (/data/node_modules/modbus-serial/index.js:487:10)
    at /data/node_modules/modbus-serial/apis/promise.js:48:31
    at new Promise (<anonymous>)
    at ModbusRTU.readHoldingRegisters (/data/node_modules/modbus-serial/apis/promise.js:39:27)
    at Object.callModbus (/data/node_modules/node-red-contrib-modbus/modbus/maps/core/core/modbus-client-core.js:68:16)
    at Object.sendDataInParallel (/data/node_modules/node-red-contrib-modbus/modbus/maps/core/core/modbus-queue-core.js:76:15)
    at Object.sequentialDequeueCommand (/data/node_modules/node-red-contrib-modbus/modbus/maps/core/core/modbus-queue-core.js:32:4)
    at Object.dequeueCommand (/data/node_modules/node-red-contrib-modbus/modbus/maps/core/core/modbus-queue-core.js:146:10)
    at Timeout._onTimeout (/data/node_modules/node-red-contrib-modbus/modbus/maps/modbus-client.js:162:10)
    at ontimeout (timers.js:436:11)
    at tryOnTimeout (timers.js:300:5)
    at listOnTimeout (timers.js:263:5)
    at Timer.processTimers (timers.js:223:10)
9 Dec 21:20:32 - [warn] [modbus-flex-getter:Shtyl] FSM Reset On State {"value":"failed","actions":[],"changed":true}
9 Dec 21:20:32 - [warn] [modbus-client:Shtyl] Client -> try to reconnect by init in 2000 ms TCP@<IP_ADDRESS>:502 default Unit-Id: 1
9 Dec 21:20:32 - [warn] [modbus-flex-getter:Shtyl] FSM Reset On State {"value":"failed","actions":[],"changed":true}
9 Dec 21:20:32 - [warn] [modbus-client:Shtyl] Client -> try to reconnect by init in 2000 ms TCP@<IP_ADDRESS>:502 default Unit-Id: 1
9 Dec 21:20:34 - [warn] [modbus-client:Shtyl] Client -> reconnect in 2000 ms TCP@<IP_ADDRESS>:502 default Unit-Id: 1
9 Dec 21:20:34 - [warn] [modbus-client:Shtyl] Client -> reconnect in 2000 ms TCP@<IP_ADDRESS>:502 default Unit-Id: 1

single request with DEBUG=contribModbus*,modbus-serial:
9 Dec 21:31:49 - [warn] [modbus-client:Shtyl] Client -> try to reconnect by init in 2000 ms TCP@<IP_ADDRESS>:502 default Unit-Id: 1                                                                                [20/1959]
2019-12-09T18:31:49.811Z contribModbus:core:client Client -> closed TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-09T18:31:49.812Z contribModbus:core:client Client -> broken TCP@<IP_ADDRESS>:502 default Unit-Id: 1
9 Dec 21:31:49 - [warn] [modbus-client:Shtyl] Client -> try to reconnect by init in 2000 ms TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-09T18:31:49.814Z contribModbus:core:client Client -> stopped TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-09T18:31:49.815Z contribModbus:core:client Client -> close node TCP@<IP_ADDRESS>:502 default Unit-Id: 1
9 Dec 21:31:49 - [info] Stopped modified flows
9 Dec 21:31:49 - [info] Starting modified flows
2019-12-09T18:31:49.834Z contribModbus:core:client Client -> new
2019-12-09T18:31:49.836Z contribModbus:core:client Client -> initialized
2019-12-09T18:31:49.863Z contribModbus:core:client Client -> init
9 Dec 21:31:49 - [warn] [modbus-client:Shtyl] Client -> reconnect in 2000 ms TCP@<IP_ADDRESS>:502 default Unit-Id: 1
9 Dec 21:31:49 - [info] Started modified flows
2019-12-09T18:31:50.365Z contribModbus:core:client Client -> TCP port TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-09T18:31:50.418Z modbus-serial TCP port: signal connect
2019-12-09T18:31:50.420Z contribModbus:core:client Client -> connected TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-09T18:31:50.423Z contribModbus:core:client Client -> activated TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-09T18:31:50.424Z contribModbus:core:client Client -> queueing TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-09T18:31:50.427Z contribModbus:core:client Client -> {"state":"queueing","message":"dequeue command tcp","delay":1} TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-09T18:31:50.428Z contribModbus:core:client Client -> {"type":"queue check is not a unit","unitid":null} TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-09T18:31:50.429Z contribModbus:core:client Client -> empty TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-09T18:31:51.812Z contribModbus:core:client Client -> stopped TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-09T18:31:51.815Z contribModbus:core:client Client -> stopped TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-09T18:31:51.918Z modbus-serial TCP port: signal close: false
2019-12-09T18:31:53.090Z contribModbus:core:client Client -> {"info":"push to Queue by Unit-Id","message":{"unitid":1,"fc":3,"address":200,"quantity":7,"messageId":"5dee9319876ec0aedcbb8f5c"},"unit":1,"sendingListLength":0} TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-09T18:31:53.092Z contribModbus:core:client Client -> queueing TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-09T18:31:53.094Z contribModbus:core:client Client -> {"info":"queue read msg","message":{"unitid":1,"fc":3,"address":200,"quantity":7,"messageId":"5dee9319876ec0aedcbb8f5c"},"state":"empty","queueLength":1} TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-09T18:31:53.095Z contribModbus:core:client Client -> {"state":"queueing","message":"dequeue command tcp","delay":1} TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-09T18:31:53.098Z contribModbus:core:client Client -> {"type":"queue check","unitid":1,"sendAllowed":true,"queueLength":1} TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-09T18:31:53.099Z contribModbus:core:client Client -> {"type":"serial sending and wait per unitid","unitid":1,"queueLength":0,"sendAllowedForNext":false,"delay":1} TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-09T18:31:53.103Z contribModbus:core:client Client -> {"info":"read msg","message":{"unitid":1,"fc":3,"address":200,"quantity":7,"messageId":"5dee9319876ec0aedcbb8f5c"},"unitid":1,"timeout":1000,"state":"queueing"} TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-09T18:31:53.111Z contribModbus:core:client Client -> {"info":"queue response activate sending","message":{"unitid":1,"fc":3,"address":200,"quantity":7,"messageId":"5dee9319876ec0aedcbb8f5c"}} TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-09T18:31:53.112Z contribModbus:core:client Client -> activated TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-09T18:31:53.113Z contribModbus:core:client Client -> queueing TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-09T18:31:53.115Z contribModbus:flex:getter Port Not Open
9 Dec 21:31:53 - [error] [modbus-flex-getter:Shtyl] PortNotOpenError: Port Not Open
    at ModbusRTU.writeFC4 (/data/node_modules/modbus-serial/index.js:501:24)
    at ModbusRTU.writeFC3 (/data/node_modules/modbus-serial/index.js:487:10)
    at /data/node_modules/modbus-serial/apis/promise.js:48:31
    at new Promise (<anonymous>)
    at ModbusRTU.readHoldingRegisters (/data/node_modules/modbus-serial/apis/promise.js:39:27)
    at Object.callModbus (/data/node_modules/node-red-contrib-modbus/modbus/maps/core/core/modbus-client-core.js:68:16)
    at Object.sendDataInParallel (/data/node_modules/node-red-contrib-modbus/modbus/maps/core/core/modbus-queue-core.js:76:15)
    at Object.sequentialDequeueCommand (/data/node_modules/node-red-contrib-modbus/modbus/maps/core/core/modbus-queue-core.js:32:4)
    at Object.dequeueCommand (/data/node_modules/node-red-contrib-modbus/modbus/maps/core/core/modbus-queue-core.js:146:10)
    at Timeout._onTimeout (/data/node_modules/node-red-contrib-modbus/modbus/maps/modbus-client.js:162:10)
    at ontimeout (timers.js:436:11)
    at tryOnTimeout (timers.js:300:5)
    at listOnTimeout (timers.js:263:5)
    at Timer.processTimers (timers.js:223:10)
9 Dec 21:31:53 - [warn] [modbus-flex-getter:Shtyl] FSM Reset On State {"value":"failed","actions":[],"changed":true}
9 Dec 21:31:53 - [warn] [modbus-client:Shtyl] Client -> try to reconnect by init in 2000 ms TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-09T18:31:53.568Z contribModbus:core:client Client -> failed TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-09T18:31:53.570Z contribModbus:core:client Client -> broken TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-09T18:31:53.573Z contribModbus:core:client Client -> closed TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-09T18:31:53.574Z contribModbus:core:client Client -> broken TCP@<IP_ADDRESS>:502 default Unit-Id: 1
9 Dec 21:31:53 - [warn] [modbus-client:Shtyl] Client -> try to reconnect by init in 2000 ms TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-09T18:31:53.577Z modbus-serial modbusErrorHandling:Port Not Open
2019-12-09T18:31:53.578Z contribModbus:core:client Client -> failed TCP@<IP_ADDRESS>:502 default Unit-Id: 1
9 Dec 21:31:53 - [warn] [modbus-flex-getter:Shtyl] FSM Reset On State {"value":"failed","actions":[],"changed":true}
2019-12-09T18:31:53.580Z contribModbus:core:client Client -> broken TCP@<IP_ADDRESS>:502 default Unit-Id: 1
9 Dec 21:31:53 - [warn] [modbus-client:Shtyl] Client -> try to reconnect by init in 2000 ms TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-09T18:31:53.583Z contribModbus:core:client Client -> {"state":"broken","message":"dequeue command disallowed state","delay":1} TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-09T18:31:55.573Z contribModbus:core:client Client -> init TCP@<IP_ADDRESS>:502 default Unit-Id: 1
9 Dec 21:31:55 - [warn] [modbus-client:Shtyl] Client -> reconnect in 2000 ms TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-09T18:31:55.580Z contribModbus:core:client Client -> init TCP@<IP_ADDRESS>:502 default Unit-Id: 1
9 Dec 21:31:55 - [warn] [modbus-client:Shtyl] Client -> reconnect in 2000 ms TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-09T18:31:55.587Z contribModbus:core:client Client -> init TCP@<IP_ADDRESS>:502 default Unit-Id: 1
9 Dec 21:31:55 - [warn] [modbus-client:Shtyl] Client -> reconnect in 2000 ms TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-09T18:31:57.577Z contribModbus:core:client Client -> TCP port TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-09T18:31:57.585Z contribModbus:core:client Client -> TCP port TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-09T18:31:57.591Z contribModbus:core:client Client -> TCP port TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-09T18:31:57.629Z modbus-serial TCP port: signal connect
2019-12-09T18:31:57.631Z contribModbus:core:client Client -> connection closed TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-09T18:31:57.871Z modbus-serial TCP port: signal close: false
2019-12-09T18:31:57.914Z modbus-serial TCP port: signal connect
2019-12-09T18:31:57.915Z contribModbus:core:client Client -> connection closed TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-09T18:31:58.131Z modbus-serial TCP port: signal close: false
2019-12-09T18:31:58.665Z modbus-serial TCP port: signal connect
2019-12-09T18:31:58.667Z contribModbus:core:client Client -> connected TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-09T18:31:58.668Z contribModbus:core:client Client -> activated TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-09T18:31:58.670Z contribModbus:core:client Client -> queueing TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-09T18:31:58.672Z contribModbus:core:client Client -> {"state":"queueing","message":"dequeue command tcp","delay":1} TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-09T18:31:58.674Z contribModbus:core:client Client -> {"type":"queue check is not a unit","unitid":null} TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-09T18:31:58.675Z contribModbus:core:client Client -> empty TCP@<IP_ADDRESS>:502 default Unit-Id: 1
2019-12-09T18:32:00.179Z modbus-serial TCP port: signal close: false

I'm ready to test any other cases

@yaacov what do you think?

Please, test v5.4.0 and reopen with new information if the problem is not fixed.

Hello, I am a new guy at here with the same issue.  I try to connect the modbus device with FC 3 but It is not connected . Can I get any help here .

have same issue (using TCP connection not TTY), current version of node-red-contrib-modbus is 5.10.1
After some period of time ( maybe 2-4 hours ) of work it suddenly stops to connect to Modbus TCP Server, claiming what "Modbus Failure On State sending Get More About It By Logging" and after 'Port Not Open'

@tjunussov try v5.13.2 or above, please

I am on v5.13.2 and I get  "Modbus Failure On State sending Get More About It By Logging" and after 'Port Not Open'. Strangely if I just open a webpage to nodered and trigger the modbus write from my webpage(mqtt into nodered) again then it will work. An hour later the port not open issue appears again.

Hi,
same Problem ModBus TCP, V 5.21.2
is it better to use a few modbus write nodes?

Hi, some devices will close the Port if the communication is to slow. Why should the queue work with a delay per message of 1 sec. ?  Please, check the Modbus Specs or the information of the responding Modbus device in those cases.

Hi,
same Problem ModBus TCP, V 5.21.2
is it better to use a few modbus write nodes?

I use one read and one write if the device has enough possible connections for TCP.

hi, I am also getting a port not found error on the TCP connection.
actually, we are fetching plc data every 1 minute. the issue is  coming  after 6-8 hours. I am getting port not found error .
and after node server restart it starts again !
is there any solution for this?
i am on version   8.0.5
@biancode  please help


Product of Array Except Self-Leetcode

AIM
Want to add solution the "Product of array except self".
Kindly assign me this problem I want to add solution to this problem in C++.
Link To the problem:-https://leetcode.com/problems/product-of-array-except-self/
DETAILS
Given an integer array nums, return an array answer such that answer[i] is equal to the product of all the elements of nums except nums[i].
Example 1:
Input: nums = [1,2,3,4]
Output: [24,12,8,6]
Example 2:
Input: nums = [-1,1,0,-3,3]
Output: [0,0,9,0,0]
Programming language

[ ] C
[ ] C++
[ ] Java
[ ] Python

Please assign me this issue under LGM-SOC'21


Error when running Backport docker container

Hi
I'm having trouble running the backport docker container.
When initialising a container from the 'sqren/backport' image, I get the following error:
Invalid option "branches"

So, I have built the docker image locally from main, but when I run that, I get:
/entrypoint.sh: line 10: backport: command not found

I am running it like in backport-alias.sh:
docker run -it --rm -v $(pwd):/app:ro -v $BACKPORT_FOLDER:/root/.backport -v $GITCONFIG:/etc/gitconfig sqren/backport "$@"

My .backport.json looks something like this:
{
  "fork": false,
  "upstream": "x",
  "targetBranchChoices": [
    "xx-SNAPSHOT",
    "xx-RELEASE"
  ],
  "targetPRLabels": ["something", "something-else"]
}

I hope you can help with this.
Thanks
BR
Thomas Jensen

Hey there,
I just released 7.3.2 and updated the command:
https://github.com/sqren/backport/blob/bcd6235b868665a65c29ec2b153ca5d39e37900b/docker/backport-alias.sh#L11
Can you give it a try and let me know if it works?

Hey there,
I just released 7.3.2 and updated the command:
https://github.com/sqren/backport/blob/bcd6235b868665a65c29ec2b153ca5d39e37900b/docker/backport-alias.sh#L11
Can you give it a try and let me know if it works?

Hi
That was fast.
I tried the new code with the updated command. Unfortunately, I get:
docker: Error response from daemon: OCI runtime create failed: container_linux.go:370: starting container process caused: exec: "./entrypoint.sh": stat ./entrypoint.sh: no such file or directory: unknown.

This dockerfile works for me:
FROM node:latest

COPY ./entrypoint.sh ./entrypoint.sh

RUN mkdir /app
WORKDIR /app

RUN npm install backport -g
ENTRYPOINT ["/entrypoint.sh"]
CMD []

Hey there,
I forget to get back to you but I did update the docker setup:
https://github.com/sqren/backport/tree/main/docker
I'm able to make it work like:
./backport.sh --repo backport-org/backport-demo --no-fork

Can you give it a try?

Hi again
I tried pulling the newest image and I ran it as before, i.e.
docker run -it --rm -v $PURE_BASE_PATH:/app:ro -v $BACKPORT_FOLDER:/root/.backport -v $GITCONFIG:/etc/gitconfig sqren/backport "$@"
I still get the same error message as before:
Invalid option "branches"

Okay, I think the problem was that I hadn't published the image to docker hub. Try running this now:
docker run -it --rm -v $(pwd):/app:ro -v ~/.backport:/root/.backport sqren/backport "$@"

Note: you might have to change $(pwd) and ~/.backport if you are on Windows.

There does still seem to be something with the build.
When I run your command above, I get
WARNING: The requested image's platform (linux/arm64/v8) does not match the detected host platform (linux/amd64) and no specific platform was requested
standard_init_linux.go:219: exec user process caused: exec format error

When I add a --platform parameter, i.e.
docker run -it --rm -v $(pwd):/app:ro -v ~/.backport:/root/.backport --platform linux/arm64/v8 sqren/backport "$@"

I still get the last error:
standard_init_linux.go:219: exec user process caused: exec format error

I'm on Linux (Ubuntu 20.04.2 LTS)

Thanks for all the feedback.
I finally bit the bullet and added automation for publishing docker images. This also takes care of multiple platforms (linux/amd64,linux/arm64).
From what I can tell it should work but I'd be very happy if you can try it out

It works now 🙂
Thanks for the update


bloc common states fileds fixed

🗃 Github Issue Or Explanation for this PR. (What is it supposed to do and Why is needed)
✅ Checklist

[x] Github issue details are up to date for people to QA.
[x] I have tested all my changes.

🕵♂ Notes for Code Reviewer
Frequent fields of a bloc state are standardized.
Now the following structure is proposed for bloc state clases:
class SomeState extends Equatable {
  final PageState pageState;
  final PageCommand? pageCommand;
  final String? errorMessage;
  ... The rest of the states of this bloc

👯♀ Paired with
"nobody"

Thanks @RaulUrtecho


Check manual_tracking

Hey @SamHawkens2,
I split the mask_list_src() into 2 similar fcts, namely one for returning segmentation mask and the other to return tracked mask. Can you make sure that I haven't messed up the manual tracking, please.
Thanks

Corrected and its working again.


ES5 Experiment

I decided to spend a couple of hours today experimenting with moving the code to ES5. Here are some things I have found.

Using _.extend and _.create for inheritance is not that bad. The code doesn't look that far off from ES6 classes.
Modules are better in ES6.
I had to combine the registry and primitives into one file because of circular redundancy with require.
Tests run in 0.5 seconds and it's so nice
Errors are for the right line numbers

Thoughts @danielgtaylor?

Also, just a note, we need to talk about and decide on this route first. For the time being, this should not be merged.

Did a test and ES6 classes still work as before:
import { StringType } from './lib/minim';

class MyString extends StringType {
  foo() {
    return 'bar';
  }
}

let test = new MyString('Hello World!');

console.log(test.primitive()); // string
console.log(test.toValue()); // Hello World!
console.log(test.foo()); // bar

@smizell overall I think this looks fine. Do you know if super still works as expected from ES6 (both in constructors and other methods)?


Integrate doc creation into CI process

Integrate doc building into CI, failing CI if there are issues.

Closed by #487


Issue 4283 allow phpdoc summary to end with colon

The changes here address #4283.

I am against this change, reason given in my comment on the issue


Added separate_job experiment option to batch experiments

One half of #920.
When set to True, circuits coming from different sub-experiments are routed to different jobs. Default value is False.

@nkanazawa1989 Thanks a lot for the review. CI is not passing because of tox issues. But I addressed your comments and will appreciate if you can re-review.
@haggaila You can try the current version (with the fixes following Naoki's review) on your use case.


bump version in package.json to v2.24.5

release version v2.24.5

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


[SPARK-27725][EXAMPLES] Add an example discovery Script for GPU resources

What changes were proposed in this pull request?
Example GPU resource discovery script that can be used with Nvidia GPUs and passed into SPARK via spark.{driver/executor}.resource.gpu.discoveryScript
For example:
./bin/spark-shell --master yarn --deploy-mode client --driver-memory 1g  --conf spark.yarn.am.memory=3g --num-executors 1 --executor-memory 1g  --conf spark.driver.resource.gpu.count=2  --executor-cores 1 --conf spark.driver.resource.gpu.discoveryScript=/home/tgraves/workspace/tgravescs-spark/examples/src/main/resources/getGpusResources.sh  --conf spark.executor.resource.gpu.count=1 --conf spark.task.resource.gpu.count=1 --conf spark.executor.resource.gpu.discoveryScript=/home/tgraves/workspace/tgravescs-spark/examples/src/main/resources/getGpusResources.sh
How was this patch tested?
Manually tested local cluster mode and yarn mode. Tested on a node with 8 GPUs and one with 2 GPUs.

Test build #105874 has started for PR 24731 at commit 1e41b2e.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/11131/
Test PASSed.

Test build #105874 has finished for PR 24731 at commit 1e41b2e.

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

Merged build finished. Test PASSed.

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

@felixcheung . We can make src/main/sh(?), but it's more natural to consider this as a resource or configuration, isn't it?

Yeah I didn't want to put it into the top level main directory since everything else has a subdirectory there. We already have python/r/scala but those are really spark programming languages and this isn't so that is why I put it under resources.
I could create a scripts directory there, thoughts on that?

@felixcheung  are you ok with the scripts directory? If so I'll file another jira and move it

script sounds good

https://github.com/apache/spark/pull/24754 to move


moved transaction-related react files to transactions subdirectory

(╯°□°）╯︵ ┻━┻
I have NO idea what I am doing. Seriously.
I do think we need the component files for each model in individual directories, but I can't make the connection between the application and the transaction. Halp.

I am merging so I can pull it and see the code in action.


[1.x] Lazily resolves the database connection

This is an alternative to #42. The connection and all configuration is now lazily resolved allowing for better multi-tennant support.
This allows the configuration to be changed at runtime and the correct values will be used within the drivers.
This is technically a breaking change to the DatabaseDriver's constructor signature, however I believe we can take the risk as it is still very early days for the package.
Additionally, this PR fixes an issue where stores were not configurable. Now multiple database stores may exist at once and be configured on an individual basis.

love it man thanks for this one

This sort of awkward lazy resolution is only necessary because we are forcing the Pennant manager into the Illuminate\Support\Manager model.
I have opened a new PR that drops that class extension all together and is a totally custom, multi-driver manager - modeled like the current Laravel CacheManager which also does not extend Illuminate\Support\Manager.
PR: https://github.com/laravel/pennant/pull/44


blend file does import but will not render materials/textures correctly

Tested versions
reproducable on macos 14.5 (23F79) godot stable v4.3
System information
macos 14.5 (23F79) godot stable v4.3
Issue description
When I drag a blend file into godot, it imports correctly.
However the materials or textures are not rendered correctly.

Steps to reproduce
Simply drag and drop a blend file into godot.
Minimal reproduction project (MRP)
https://github.com/drewpotter/testgame

There are error messages in your log, are they related? If so please add them to your report

These messages appear:
  Source and destination path are equal.
  Source and destination path are equal.
  editor/import/3d/scene_import_settings.cpp:227 - Condition "p_material != material_data.material" is true.
  editor/import/3d/scene_import_settings.cpp:227 - Condition "p_material != material_data.material" is true.
  editor/import/3d/scene_import_settings.cpp:227 - Condition "p_material != material_data.material" is true.
  scene/resources/3d/importer_mesh.cpp:521 - Ignoring face with non-finite normal in LOD generation.

That sounds pretty relevant

These errors appear to be because you have linked multiple blend files together, not sure godot has much in the way to handle that, but the errors do seem harmless in testing your files.
editor/import/3d/scene_import_settings.cpp:227 - Condition "p_material != material_data.material" is true.

As for the weird rendering, it's because the current importer has issues with lighting spec, see https://github.com/godotengine/godot/issues/92168 and https://github.com/godotengine/godot/issues/73624 as a temporary fix you can disable "Punctual Lights" in the import settings.


docs: fix setup documentation link

Updated Expo documentation link to include local build environment parameter so that EAS is turned off by default when you click the link.

Merge activity

Nov 18, 2:31 PM EST: A user started a stack merge that includes this pull request via Graphite.


[Tsa] fix typo in compilers

Fix colon in tsa compilers.
I dont know what the consequences this change might trigger, since I dont know if the previous yaml was compliant and accepted by syntax

launch jenkins --tsa

launch jenkins all --tsa


Account status - Working

Hello,
Awesome app!
Quick question, if I have multiple accounts going, is there a way for me to see if they are all working?
I mean, the app is working and updating etc, but I have like 7 accounts added, and I'm not sure if it tells you if a specific account isn't working (banned...wrong password)
Any insight into this?
Thanks!

I think the only way to know if something is wrong with an specific worker is in the console. If there is an account witch the app cannot log to, or if it is finding 0 pokemons, 0pokestops and 0 gyms... It's likely something is not working well with that worker. After that, you should check it yourself logging in with said account.

How can I view the console?
I'm pretty sure if I could see what was going on in the background with the raw data I could figure it out myself.

Tools>Toogle Developer Tools.
There, you have to search for the console tab. Be aware that the console "calls" the accounts as search-worker-number, so first of all you should see which account is assigned to which search-worker-number (In the console, filtering by the name of the account should do to see the line where the search-worker tries to log with a given name)

That is exactly what I was looking for.
Turns out, in fact, I did typo one password for one account haha.
Thanks!


Fixes for integrating sympy based solvers with CoreNEURON

Install newton solver and related header dependencies
Build libraries and prepare headers in CMAKE_BINARY_DIR

Ignoring Jenkins as its down.


Change edit_view Save and continue url

Fixes #2183.
When using flask_admin behind reverse proxy, working in the edit view, the Save and continue button uses request.url which is missing the prefix.
This works ok in the create_view, We need to use the self.get_url('.edit_view') so the correct url is returned.

@mrjoes @briancappello Can you review this?

@ulgens Can you review this?

Looks good and makes sense to me.

@ulgens Thanks.
Any plans for new release of flask_admin? I can see there's been some fixes, besides this one.

Any plans for new release of flask_admin? I can see there's been some fixes, besides this one.

Not sure if the question was for me, but I will try my best to push for a new release after couple other fixes.


Debouncing resizes?

Hi, 👋
What would you think of adding possibility to debounce resizes? I'm experiencing slowdown and flickering of renderings if continuously resizing a window (or a paned layout).
Try it out on this established example. Just resize the panel underneath the view.
The question is if the ResizeObserver callback should be the one to debounce, or the rendering itself 🤔. Or both?
What do you think of this feature?

debounce where the last frame is guaranteed to fire would be ok with me. could i interest you into that pr? i would also put it into the resize hook in canvas.tsx, makes sense.

I can look into it, definitely. Not used to TypeScript though so maybe could get a hand for that. But I'll start somwhere!

it's in. will publish it next version:
<Canvas resize={{ scroll: true, debounce: { scroll: 50, resize: 0 } }}>

it is using this lib internally and just forwards the config: https://github.com/react-spring/react-use-measure

Awesome, thanks a lot! Sorry haven't looked into it really due to time and not being fluent in TS 😺


[Enhancement]: Searchbar AutoSuggestion while typing

PR Description 📜
I have added auto suggestion in search bar and clicking on that it opens the project my issue #3354 is closed by the PA bcoz of 2 issues at a time can you pls assign me these one
Fixes #3354

Mark the task you have completed ✅

[✅ ] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[ ✅] I have performed a self-review of my own code or work.
[ ✅] I have commented my code, particularly in hard-to-understand areas.
[ ✅] My changes generates no new warnings.
[ ✅] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE

Add your screenshots(Optional) 📸

Thank you soo much for contributing to our repository 💗

Thank you @Pratik2401 ,for creating the PR and contributing to our GameZone 💗
Review team will review the PR and will reach out to you soon! 😇
Make sure that you have marked all the tasks that you are done with ✅.
Thank you for your patience! 😀

Thank you  @Pratik2401 , for your valuable time and contribution in our GameZone 💗.
It’s our GameZone, so Let’s build this GameZone altogether !!🤝
Hoping to see you soon with another PR again 😇
Wishing you all the best for your journey into Open Source🚀


[BUG] Toolbar dialog background in Dark Mode

Hi author.
In dark mode, when I click toolbar button, and show dialog, the background color is white, and the font color is also white.
Currently, I tried setting alertDialog background color, it was work. If there is any other methods can change the background of dialog?

Hi, try setting dialogBackgroundColor in your theme and it should follow that color.


creating guild role facing method not allowed

Dear, maintainer.
I found some issue related with createGuildRole it said: 405 Method not Allowed.
Here the full log:
[Lib]: Making request to PUT https://discord.com/api/v10/guilds/1026152036317790288/roles
    size: 121, reason: ""
[Lib]: Got response.
/mnt/c/Users/kelts/Programming/vel/src/vel.nim(198) vel
/usr/lib/nim/lib/pure/asyncdispatch.nim(1961) waitFor
/usr/lib/nim/lib/pure/asyncdispatch.nim(1653) poll
/usr/lib/nim/lib/pure/asyncdispatch.nim(1394) runOnce
/usr/lib/nim/lib/pure/asyncdispatch.nim(234) processPendingCallbacks
/usr/lib/nim/lib/pure/asyncmacro.nim(28) requestNimAsyncContinue
/root/.nimble/pkgs/dimscord-1.4.0/dimscord/restapi/requester.nim(266) requestIter
[[reraised from:
/mnt/c/Users/kelts/Programming/vel/src/vel.nim(198) vel
/usr/lib/nim/lib/pure/asyncdispatch.nim(1961) waitFor
/usr/lib/nim/lib/pure/asyncdispatch.nim(1653) poll
/usr/lib/nim/lib/pure/asyncdispatch.nim(1394) runOnce
/usr/lib/nim/lib/pure/asyncdispatch.nim(234) processPendingCallbacks
/usr/lib/nim/lib/pure/asyncmacro.nim(28) requestNimAsyncContinue
/usr/lib/nim/lib/system/excpt.nim(144) requestIter
]]
[[reraised from:
/mnt/c/Users/kelts/Programming/vel/src/vel.nim(198) vel
/usr/lib/nim/lib/pure/asyncdispatch.nim(1961) waitFor
/usr/lib/nim/lib/pure/asyncdispatch.nim(1653) poll
/usr/lib/nim/lib/pure/asyncdispatch.nim(1394) runOnce
/usr/lib/nim/lib/pure/asyncdispatch.nim(234) processPendingCallbacks
/usr/lib/nim/lib/pure/asyncmacro.nim(28) createGuildRoleNimAsyncContinue
/usr/lib/nim/lib/pure/asyncmacro.nim(131) createGuildRoleIter
/usr/lib/nim/lib/pure/asyncfutures.nim(389) read
]]
[[reraised from:
/mnt/c/Users/kelts/Programming/vel/src/vel.nim(198) vel
/usr/lib/nim/lib/pure/asyncdispatch.nim(1961) waitFor
/usr/lib/nim/lib/pure/asyncdispatch.nim(1653) poll
/usr/lib/nim/lib/pure/asyncdispatch.nim(1394) runOnce
/usr/lib/nim/lib/pure/asyncdispatch.nim(234) processPendingCallbacks
/usr/lib/nim/lib/pure/asyncmacro.nim(28) anonymousNimAsyncContinue
/usr/lib/nim/lib/pure/asyncmacro.nim(131) anonymousIter
/usr/lib/nim/lib/pure/asyncfutures.nim(389) read
]]
[[reraised from:
/mnt/c/Users/kelts/Programming/vel/src/vel.nim(198) vel
/usr/lib/nim/lib/pure/asyncdispatch.nim(1961) waitFor
/usr/lib/nim/lib/pure/asyncdispatch.nim(1653) poll
/usr/lib/nim/lib/pure/asyncdispatch.nim(1394) runOnce
/usr/lib/nim/lib/pure/asyncdispatch.nim(234) processPendingCallbacks
/usr/lib/nim/lib/pure/asyncfutures.nim(437) asyncCheckCallback
]]
Error: unhandled exception: [405] Unknown error

 - [DiscordError]:: 405: Method Not Allowed (0)
Async traceback:
  /mnt/c/Users/kelts/Programming/vel/src/vel.nim(198)                   vel
  /usr/lib/nim/lib/pure/asyncdispatch.nim(1961)                         waitFor
  /usr/lib/nim/lib/pure/asyncdispatch.nim(1653)                         poll
  /usr/lib/nim/lib/pure/asyncdispatch.nim(1394)                         runOnce
  /usr/lib/nim/lib/pure/asyncdispatch.nim(234)                          processPendingCallbacks
  /usr/lib/nim/lib/pure/asyncmacro.nim(28)                              requestNimAsyncContinue
  /root/.nimble/pkgs/dimscord-1.4.0/dimscord/restapi/requester.nim(266) requestIter
  #[
    /mnt/c/Users/kelts/Programming/vel/src/vel.nim(198)                   vel
    /usr/lib/nim/lib/pure/asyncdispatch.nim(1961)                         waitFor
    /usr/lib/nim/lib/pure/asyncdispatch.nim(1653)                         poll
    /usr/lib/nim/lib/pure/asyncdispatch.nim(1394)                         runOnce
    /usr/lib/nim/lib/pure/asyncdispatch.nim(234)                          processPendingCallbacks
    /usr/lib/nim/lib/pure/asyncmacro.nim(28)                              requestNimAsyncContinue
    /usr/lib/nim/lib/system/excpt.nim(144)                                requestIter
  ]#
  #[
    /mnt/c/Users/kelts/Programming/vel/src/vel.nim(198)                   vel
    /usr/lib/nim/lib/pure/asyncdispatch.nim(1961)                         waitFor
    /usr/lib/nim/lib/pure/asyncdispatch.nim(1653)                         poll
    /usr/lib/nim/lib/pure/asyncdispatch.nim(1394)                         runOnce
    /usr/lib/nim/lib/pure/asyncdispatch.nim(234)                          processPendingCallbacks
    /usr/lib/nim/lib/pure/asyncmacro.nim(28)                              createGuildRoleNimAsyncContinue
    /usr/lib/nim/lib/pure/asyncmacro.nim(131)                             createGuildRoleIter
    /usr/lib/nim/lib/pure/asyncfutures.nim(389)                           read
  ]#
  #[
    /mnt/c/Users/kelts/Programming/vel/src/vel.nim(198)                   vel
    /usr/lib/nim/lib/pure/asyncdispatch.nim(1961)                         waitFor
    /usr/lib/nim/lib/pure/asyncdispatch.nim(1653)                         poll
    /usr/lib/nim/lib/pure/asyncdispatch.nim(1394)                         runOnce
    /usr/lib/nim/lib/pure/asyncdispatch.nim(234)                          processPendingCallbacks
    /usr/lib/nim/lib/pure/asyncmacro.nim(28)                              anonymousNimAsyncContinue
    /usr/lib/nim/lib/pure/asyncmacro.nim(131)                             anonymousIter
    /usr/lib/nim/lib/pure/asyncfutures.nim(389)                           read
  ]#
Exception message: [405] Unknown error

 - [DiscordError]:: 405: Method Not Allowed (0)

I had figure the cause that the PUT changed to POST verb, reference.
Can you assign this to me ? PR ongoing.

I've merged the PR, thanks for letting me know 👍.


Replace broken link for commit guidelines

Motivation
The contribution guidelines suggest that contributors
Ensure your commit messages are well-written.
The medium link redirects to an expired domain.
Solution
This PR replaces the broken link with the latest version saved by archive.org: https://web.archive.org/web/20160316232453/https://medium.com/brigade-engineering/the-secrets-to-great-commit-messages-106fc0a92a25
I'm opening PRs to make this fix in these repos: rosetta-specifications, rosetta-cli, rosetta-sdk-go and rosetta-bitcoin.

If Heimdall is stuck, please click the following link: https://heimdall-public.cbhq.net/v1/pull_request/stuck?pr_number=151&repository=coinbase/rosetta-cli

@KNWR Looks like you'll need to sign your commit before I can review 😢

On it 👍


quotes are replaced by -, bump to 1.1.4

FIX #17

test_cyrillic_text is failling, but I don't understand why any letter in 'Компьютер' should match a quote, is it normal ?

(компьютер) is first converted to (komp'yuter), and you can see why it is matching a quote.

Ok thanks. It is meaningfull in this language to replace the quote by a
dash ?
--
/*
** "What do you despise? By this you are truly known."
**	from Manual of Muad'Dib by the Princess Irulan.
*/
On Fri, Sep 18, 2015 at 9:55 PM, Val Neekman<EMAIL_ADDRESS>wrote:

(компьютер) is first converted to (komp'yuter), and you can see why it is
matching a quote.
—
Reply to this email directly or view it on GitHub
https://github.com/un33k/python-slugify/pull/18#issuecomment-141551226.

Don't speak Russian, but I know it doesn't make sense to have a computer written as comp-uter. Same goes for Kompyuter vs. Komp-yuter.
I suggest that users of slugify pre-process the text as per their locale prior to calling slugify.

So I grabbed a Russian and the comma is a phonic (not sure it's the right word...) accent.
Maybe an option could be given when creating the slugify object, retrocompatibility would be respected and us froggies would have our dash?

I am closing this one to replace it by #20

https://github.com/un33k/python-slugify/issues/17

Available in version 1.2.0.


Validator Sign up: !gjacksonh74#2387

Bio:
halo, I'm defi&WEB3&Layer 1,2 & Node operator degen ape student. validator server from Ukraine. I have some experience of Node operating somethin like Namada Trusted setup / Sui, Aptos / Aleo / Starknet / Esperessosys / obol network / Kyve cosmos
etc.
I want to be a more contributor of Anoma, Namada ser.
Socials:
Mail<EMAIL_ADDRESS>GitHub: https://github.com/zssbecker
Twitter: https://twitter.com/777_Earth2
Discord: !gjacksonh74#2387
Ty, Happy Namada!

merged zssbecker.toml manually into public-testnet-3


[python3] Build error on<EMAIL_ADDRESS>

Host Environment
Host: arm64-osx
Compiler: AppleClang <IP_ADDRESS>00026
Installing 32/33<EMAIL_ADDRESS>Building<EMAIL_ADDRESS>CMake Warning at ports/python3/portfile.cmake:7 (message):
Call Stack (most recent call first):
  scripts/ports.cmake:192 (include)

-- Using cached python-cpython-v3.11.8.tar.gz.
-- Cleaning sources at
-- Applying patch 0001-only-build-required-projects.patch
-- Applying patch 0003-use-vcpkg-zlib.patch
-- Applying patch 0004-devendor-external-dependencies.patch
-- Applying patch 0005-dont-copy-vcruntime.patch
-- Applying patch 0008-python.pc.patch
-- Applying patch 0010-dont-skip-rpath.patch
-- Applying patch 0012-force-disable-modules.patch
-- Applying patch 0014-fix-get-python-inc-output.patch
-- Applying patch 0015-dont-use-WINDOWS-def.patch
-- Applying patch 0016-undup-ffi-symbols.patch
-- Applying patch 0018-fix-sysconfig-include.patch
-- Applying patch 0002-static-library.patch

-- Getting CMake variables for x64-osx-dbg
-- Getting CMake variables for x64-osx-rel
-- Generating configure for x64-osx
-- Finished generating configure for x64-osx
-- Configuring x64-osx-dbg
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:127 (message):
    Command failed: /opt/homebrew/bin/bash -c "V=1 ./../src/v3.11.8-31d17ab840.clean/configure --host=x86_64-apple-darwin \"--with-openssl=`workfolder`/vcpkg_installed/x64-osx\" \"--without-ensurepip\" \"--with-suffix=\" \"--with-system-expat\" \"--without-readline\" \"--disable-test-modules\" \"LIBS=-liconv -lintl\" \"--with-build-python=`workfolder`/vcpkg_installed/arm64-osx/tools/python3/python3.11\" \"--disable-silent-rules\" \"--verbose\" \"--disable-shared\" \"--enable-static\" \"--with-pydebug\" \"vcpkg_rpath=`workfolder`/vcpkg_installed/x64-osx/debug/lib\" \"--prefix=`workfolder`/vcpkg_installed/x64-osx/debug\" \"--bindir=\\${prefix}/../tools/python3/debug/bin\" \"--sbindir=\\${prefix}/../tools/python3/debug/sbin\" \"--libdir=\\${prefix}/lib\" \"--includedir=\\${prefix}/../include\" \"--datarootdir=\\${prefix}/share/python3\""
    Working Directory: `workfolder`VCPKG/buildtrees/python3/x64-osx-dbg
    Error code: 1

Call Stack (most recent call first):
  scripts/cmake/vcpkg_configure_make.cmake:866 (vcpkg_execute_required_process)
  ports/python3/portfile.cmake:274 (vcpkg_configure_make)
  scripts/ports.cmake:192 (include)

i try to install the miss package , but it doesnt work.
Also i try to install it without manifest mode, which leads the same result.
here i have provide the install script that i use.
vcpkg.json
{
  "name": "app",
  "version-string": "0.1.0",
  "dependencies": [
      "glfw3",
      "glad" ,
      "opengl-registry",
      "implot",
      "python3",
      "pybind11",

    {
      "name": "imgui",
      "features": ["glfw-binding", "opengl3-binding"]
    }
  ]

install.sh
#!/usr/bin/env bash

VCPKG_TARGET_TRIPLET="x64-osx"
VCPKG_DIR="$PWD/VCPKG"
INSTALLED_SHARED_DIR="$PWD/vcpkg_installed"  # Replace with actual path

# Check if dependencies are already installed
if [ ! -d "$INSTALLED_SHARED_DIR" ]; then
    rm -rf "$INSTALLED_SHARED_DIR"

    echo "Dependencies not installed. Installing..."

    # Define the path to the vcpkg executable
    pushd "$VCPKG_DIR" || exit

    # Run vcpkg install command
    ./vcpkg install --triplet="$VCPKG_TARGET_TRIPLET"

    # Check the result of the installation
    if [ $? -ne 0 ]; then
        echo "Failed to install dependencies with Vcpkg."
        exit 1
    fi

    popd || exit
fi

exit 0

I have reproduced this issue locally.

Duplicate of https://github.com/microsoft/vcpkg/issues/41055.


As a CIF project coordinator, I want parts of the project long id to be generated, so that I can ensure consistency on all the related forms and documents

Description:
The project RFP should not be a free-form field, but a complex widget that populates automatically depending on the selected RFP year, stream, and operator. Only the three-digit part should be editable directly
The long id format is <year>-RFP-<stream_id>-<random_digits>-<operator_code>
To allow CIF users to input existing projects in the system, the random_digits part should be editable (later, an option should be added to generate those digits). The other parts should be read-only and depend on the selected RFP year, stream, and operator
Acceptance Criteria:
Given I am logged in as a CIF user
When I create a new project
Then the year, stream_id and operator_code parts of the long id should be automatically generated
Development Checklist:

[ ] The year is derived from the form_change row for the funding_stream_rfp table
[ ] The stream_id is derived from the form_change row for the funding_stream table
[ ] The operator_code is derived from the form_change row for the operator table
[ ] The generated portions of the long ID are shown in the form as read-only
[ ] The random_digits part of the long ID is editable by the cif user

Personas:

Operations Team

Hey team! Please add your planning poker estimate with ZenHub @AlexZorkin @matthieu-foucault @pbastia

Thanks @dleard! Works as expected.


scrollbarSlider.background isn't applied to scrollbar

It seems that the "scrollbarSlider" color options (when define a theme) are not applied to the scrollbar, but only the minimap. I'm sorry if this is expected.
monaco-editor version: Latest
Browser: All
OS: Mac
Playground code that reproduces the issue:
monaco.editor.defineTheme('myTheme', {
    base: 'vs',
    inherit: true,
    colors: {
        'scrollbarSlider.background': '#FF0000',
        'scrollbarSlider.hoverBackground': '#FF0000',
        'scrollbarSlider.activeBackground': '#FF0000',
    },
    rules: {}
});
monaco.editor.setTheme('myTheme');

monaco.editor.create(document.getElementById("container"), {
	value: "Hello\n".repeat(100),
	language: "text/plain"
});

Expected: the slider in scrollbar should be red
Actual: the slider in minimal is red, the slider in scrollbar is still gray

The following works as a workaround: https://github.com/microsoft/monaco-editor/issues/908#issuecomment-433739458.
FYI this looks like a duplicate of https://github.com/microsoft/monaco-editor/issues/1551.

Reopening due to #2997.