ork/exec /opt/bootstrap: permission denied when using Layers

I am using Bref for building serverless PHP applications using layers.
All works with layers when deployed using sam. But on local I get
Error: fork/exec /opt/bootstrap: permission denied
Work env.
aws --version
aws-cli/1.16.103 Python/3.6.0 Windows/10 botocore/1.12.93
sam --version
SAM CLI, version 0.11.0
Docker desktop Version <IP_ADDRESS>
I debugged on it seems SAM have issue with custom layers
Can you please help.
The template I use
template.yaml
AWSTemplateFormatVersion: '2010-09-09'
Transform: AWS::Serverless-2016-10-31
Description: ''
Globals:
Function:
Environment:
Variables:
Laravel environment variables
APP_STORAGE: '/tmp'
Resources:
MyFunction:
Type: AWS::Serverless::Function
Properties:
FunctionName: 'my-function'
Description: ''
CodeUri: .
Handler: index.php
Timeout: 30 # in seconds (API Gateway has a timeout of 30 seconds)
Runtime: provided
Layers:

'arn:aws:lambda:eu-west-1:209497400698:layer:php-72-fpm:1'
Events:

The function will match all HTTP URLs
HttpRoot:
Type: Api
Properties:
Path: /
Method: ANY
HttpSubPaths:
Type: Api
Properties:
Path: /{proxy+}
Method: ANY
All works on Prod correctly when deployed only local showing this error

Have seen this issue crop up on a bad installation of docker, have you tried it on another windows computer to see if this is repeatable?

Same for me

Same here with these versions:

Docker Desktop <IP_ADDRESS> (31259)
aws-cli/1.16.117 Python/3.6.5 Windows/10 botocore/1.12.107
SAM CLI, version 0.12.0

Same error

Same here:
Docker Desktop <IP_ADDRESS> (31088)
Docker version 18.09.1, build 4c52b90
aws-cli/1.16.169 Python/2.7.16 Windows/10 botocore/1.12.160
SAM CLI, version 0.16.1

Have you tried setting permissions on the codeuri and layer folders as well, and re-tried it?


chore(ci): add changelog automation

Summary
Add changelog automation tool(implemented by GitHub workflow) to generate changelog file automatically based on the PR title.
PR title is not always qualified to be the changelog. For example, https://github.com/Kong/kong/pull/11427 (feat(http-log): add allow list for logged headers), the user facing changelog should be more detailed by including the added fields.
message: "**HTTP-Log**: add `enable_logged_headers_allow_list` and `logged_headers_allow_list` fields in HTTP Log plugin."
type: feature
scope: Plugin
prs:
  - 11427

Therefore, I add a changelog form in PULL_REQUEST_TEMPLATE.md to allow contributors and reviewers to override it:
### Changelog

message:
type:
scope:
prs:
issues:

Once the changelog form is updated, people can easily re-generate changelog by leaving a comment( /update-changelog )

https://github.com/Kong/kong/pull/11514


not show list commands Admin

i'm use $command->isAdminCommand() in help command but nothing show in list
or !$command->isSystemCommand() && $command->isEnabled() not show list commands Admin
however set  $telegram->enableAdmin(['123456']); for Admin in file hook.php

Your admin ID should be set as an integer, not string!
 $telegram->enableAdmin(123456);

thanx

You're welcome.
Just a reminder to check the readme first 😉


4.0.1 websocket WsListener onHttpUpgrade and onOpen use different instance

Environment Details

Helidon Version: 4.0.1
Helidon SE
JDK version: jdk21
OS: windows

Problem Description
when use WsRouting.Builder.endpoint(String path, Supplier listener)
the WsListener instance is different in function onHttpUpgrade and onOpen、this is the code screenshot

debug the code i found the WsRoute.listener() will be call twice、maybe it`s the reason

Duplicate of https://github.com/helidon-io/helidon/issues/8039

Closing as a duplicate


Add php

[ ] install multiple php version and switch using brew/not
[ ] install hhvm
[ ] install c plugins like phalcon

I think it's better to use https://github.com/phpbrew/phpbrew

but find it hard to install phalcon using phpbrew ... e ... sucks

need to brew install autoconf ... have to manually run the command in cphalcon directory, the error for phpbrew tells nothing ...


Do all filesystem operations via the executor

We want to do all filesystem operations via the executor. This actually has two reasons:

They may take some time, for example when listing a large directory, or listing a NFS share. Running them via the executor means we get to do this in the background.
The worker nodes may not have the same filesystem as the API server or dask.distributed Client

In the first iteration, this means we make sure Context.load(...) pushes the dataset load operation into the cluster, including the check_valid() call. The web API basically needs the same changes.
The next step would be to update the web API to also do directory listing / existence checks etc. via functions pushed into the cluster.
This is highly related to #154 which also may need to do more work on dataset initialization. Also related is #186 as listing a directory and opening files should take priority over another job that may take a while to finish.

[x] add ability to run simpler functions via the executor
[x] update Context and DataSetDetailHandler to  do load and check_valid via executor
[x] test connecting via Context to a remote dask scheduler
[x] update DataSetDetectHandler
[x] update LocalFSBrowseHandler
[x] test starting the web client with a connection to a remote dask scheduler

As of ad09ac8798ca72b13bf5ab67c603e5d38eeacd0c it is possible to spawn a dask cluster on a remote host, connect to it (for example by starting a LiberTEM server locally, and then connecting via GUI) and work with the files on the remote system.
Currently, this is a bit brittle, as certain methods on the dataset need to make sure they don't access the filesystem (they are used on the client to calculate partitioning etc.), and that the initialization function is called. If I get an idea how to structure this better, maybe it can be made more robust.

Tested with the async Digital Micrograph prototype with processing on moellenstedt. It ROCKS! 👍 👍 👍


[BUG] unix/cmath.rs does not exist

Bug Report
When building rust-src for the riscv32im-risc0-zkvm-elf target I get a file not found error due to this wrong path:

master: https://github.com/rust-lang/rust/blob/ff24ef91fc848832a8dab483d3b17097cbead5a8/library/std/src/sys/pal/zkvm/mod.rs#L15
tag 1.77.1: https://github.com/rust-lang/rust/blob/7cf61ebde7b22796c69757901dd346d0fe70bd97/library/std/src/sys/pal/zkvm/mod.rs#L15

cmath.rs is not located in the unix directory, rather in the sys directory at the same level as pal here:

master : https://github.com/rust-lang/rust/blob/master/library/std/src/sys/cmath.rs
tag 1.77.1: https://github.com/rust-lang/rust/tree/1.77.1/library/std/src/sys/cmath

Steps to Reproduce

Fetch the template
go to methods/guest
run cargo build -Z build-std --target riscv32im-risc0-zkvm-elf

error: couldn't read /nix/store/mhzd2fna42zfxdpdn0kr1zcnmrcck17p-rust-default-1.77.1/lib/rustlib/src/rust/library/std/src/sys/pal/zkvm/../unix/cmath.rs: No such file or directory (os error 2)
  --> /nix/store/mhzd2fna42zfxdpdn0kr1zcnmrcck17p-rust-default-1.77.1/lib/rustlib/src/rust/library/std/src/sys/pal/zkvm/mod.rs:16:1
   |
16 | pub mod cmath;

Expected behavior

Your Environment

risc0-zkvm version: 0.21.0
Rust version: 1.77.1
Platform/OS: Linux

I craeted a PR, I wonder whether it would be better to remove all the relative paths https://github.com/rust-lang/rust/pull/123858

Thanks for the report: I actually have a patch that addresses this. I see you fixed the cmath thing but there's another one so I'll follow up with that

@SchmErik how do you keep track of regressions for the zkvm target?

we maintain a fork of the upstream rust repo and once upstream releases, I update our fork to build the rust binaries and deal with regressions then. There are much better way of finding regressions than my current process though. Since my patch got merged, I'm going to close this. Thanks for the report!


RFP - Compressonator

Checklist

[x] The package I am requesting does not already exist on https://chocolatey.org/packages;
[x] There is no open issue for this package;
[x] The issue title starts with 'RFP - ';
[x] The download URL is public and not locked behind a paywall / login;

Package Details
Software project URL : https://gpuopen.com/compressonator/
Direct download URL for the software / installer :https://github.com/GPUOpen-Tools/compressonator/releases/download/V4.0.4855/CompressonatorCLI_x64_4.0.4855.exe
Software summary / short description:
Compressonator is a set of tools to allow artists and developers to more easily work with compressed assets and easily visualize the quality impact of various compression technologies.
It consists of a GUI application, a command line application, and an SDK for easy integration into a developer toolchain.

I had provided an incorrect link to the executable in question. The correct one is
https://github.com/GPUOpen-Tools/compressonator/releases/download/V4.0.4855/CompressonatorCLI_x64_4.0.4855.exe

I will take a look into that package

https://chocolatey.org/packages/compressonator-cli/4.0.4855

@AdmiringWorm , this package as been approved.
So this issue can be closed.
Thank you


New Contribution

Contributor: Nuelty
SSH Public key: ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAINXMMzn6hl6n83FewMiy8OsSAdpEXccXbo+FzQWqikIk
Attestation: [any form of attestation for contribution (e.g., signature) - Optional]

Okay
I'm ready
Lfg


*Error while setting up rpi_gpio_pwm platform for light

Hi,
My HA is 2023.7.2
I installed as expected in the read.me with Manual installation.
Setting up rpi_gpio_pwm in configuration.yaml
# add Bernard

switch:
  - platform: rpi_gpio
    switches:
      - port: 17
        name: "Fan Office"
        unique_id: "fan_office_switch_port_17"

sensor:
  - platform: command_line
    name: "X CPU Temp"
    command: "cat /sys/class/thermal/thermal_zone0/temp"
    unit_of_measurement: "°C"
    value_template: "{{ value | multiply(0.001) | round(1)  }}"
    scan_interval: 10

  - platform: time_date
    display_options:
      - 'time'
      - 'date'
      - 'date_time'
      - 'date_time_utc'
      - 'date_time_iso'
      - 'time_date'
      - 'time_utc'
      - 'beat'

light:
  - platform: rpi_gpio_pwm
    leds:
      - name: RPI Cooling Fan
        pin: 18

climate:
  - platform: generic_thermostat
    name: RPI Cooling Fan Controller
    unique_id: rpi_cooling_fan_controller
    heater: light.rpi_cooling_fan
    target_sensor: sensor.X_CPU_Temp
    min_temp: 30
    max_temp: 70
    ac_mode: true
    target_temp: 30
    cold_tolerance: 0.1
    hot_tolerance: 0.1
    min_cycle_duration:
      seconds: 30
    keep_alive:
      minutes: 1
    initial_hvac_mode: "cool"

2023-07-26 14:34:25.382 ERROR (MainThread) [homeassistant.components.light] Error while setting up rpi_gpio_pwm platform for light
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 353, in _async_setup_platform
    await asyncio.shield(task)
  File "/usr/local/lib/python3.11/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/ha-rpi_gpio_pwm/light.py", line 70, in setup_platform
    opt_args["pin_factory"] = PiGPIOFactory(host=led_conf[CONF_HOST], port= led_conf[CONF_PORT])
                              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/gpiozero/pins/pigpio.py", line 101, in __init__
    raise IOError('failed to connect to %s:%s' % (host, port))
OSError: failed to connect to localhost:8888

Have you an idea to solve this issue.
BR
Bernard

same here

same here,
ha 2023.10.1
Error while setting up rpi_gpio_pwm platform for light
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 359, in _async_setup_platform
    await asyncio.shield(task)
  File "/usr/local/lib/python3.11/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/rpi_gpio_pwm/light.py", line 70, in setup_platform
    opt_args["pin_factory"] = PiGPIOFactory(host=led_conf[CONF_HOST], port= led_conf[CONF_PORT])
                              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/gpiozero/pins/pigpio.py", line 101, in __init__
    raise IOError('failed to connect to %s:%s' % (host, port))
OSError: failed to connect to localhost:8888

Try changing default port to 8123 (or at least that's the port I connect to home assistant http://<IP_ADDRESS>:8123)

Could have multiple reasons:

remote GPIO disabled on the pi
gpiod service not running
if using a custom docker setup, try using networkmode host


progress bars on project details and list pages are now hooked up

Did you want to change this in the PR as well?

Works for me by manually changing my data.
Do we want a color change when we get close to the quote total?

I guess we can ask @cydoval about that one but this will be a start


[Bug] [Cdc] checkpoint is always increment

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
wait checkpoint completed: 1
.....
wait checkpoint completed: 204
wait checkpoint completed: 205
.....
and so on.
The bellow is some detailed msg:
2023-07-26 13:48:12,148 DEBUG org.apache.seatunnel.engine.server.service.slot.DefaultSlotService - start send heartbeat to resource manager, this address: [ds01]:5801
2023-07-26 13:48:12,148 DEBUG org.apache.seatunnel.engine.server.resourcemanager.AbstractResourceManager - received worker heartbeat from: [ds01]:5801
2023-07-26 13:48:15,960 INFO  com.hazelcast.client.impl.protocol.task.AuthenticationMessageTask - [ds01]:5801 [seatunnel] [5.1] Received auth from Connection[id=2, /<IP_ADDRESS>:5801->/<IP_ADDRESS>:43203, qualifier=null, endpoint=[<IP_ADDRESS>]:43203, remoteUuid=93bb2f95-0e06-4af3-9a3a-3e3b797c2bbb, alive=true, connectionType=JVM, planeIndex=-1], successfully authenticated, clientUuid: 93bb2f95-0e06-4af3-9a3a-3e3b797c2bbb, client name: hz.client_1, client version: 5.1
2023-07-26 13:48:17,024 INFO  org.apache.seatunnel.engine.server.master.JobMaster - Init JobMaster for Job SeaTunnel_Job<PHONE_NUMBER>58592257)
2023-07-26 13:48:17,024 INFO  org.apache.seatunnel.engine.server.master.JobMaster - Job SeaTunnel_Job<PHONE_NUMBER>58592257) needed jar urls [file:/seatunnel/connector-cdc-mysql-2.3.3-SNAPSHOT.jar]
2023-07-26 13:48:17,055 DEBUG org.apache.seatunnel.engine.server.dag.execution.ExecutionPlanGenerator - Generate execution plan using logical plan:
2023-07-26 13:48:17,055 DEBUG org.apache.seatunnel.engine.server.dag.execution.ExecutionPlanGenerator - Phase 1: generate execution edge list [ExecutionEdge(leftVertex=ExecutionVertex(vertexId=1, action=org.apache.seatunnel.engine.core.dag.actions.SourceAction@2a502f47, parallelism=1), rightVertex=ExecutionVertex(vertexId=2, action=org.apache.seatunnel.engine.core.dag.actions.SinkAction@54d7c7e8, parallelism=1), leftVertexId=1, rightVertexId=2)]
2023-07-26 13:48:17,055 DEBUG org.apache.seatunnel.engine.server.dag.execution.ExecutionPlanGenerator - Phase 2: generate shuffle edge list [ExecutionEdge(leftVertex=ExecutionVertex(vertexId=1, action=org.apache.seatunnel.engine.core.dag.actions.SourceAction@2a502f47, parallelism=1), rightVertex=ExecutionVertex(vertexId=2, action=org.apache.seatunnel.engine.core.dag.actions.SinkAction@54d7c7e8, parallelism=1), leftVertexId=1, rightVertexId=2)]
2023-07-26 13:48:17,055 DEBUG org.apache.seatunnel.engine.server.dag.execution.ExecutionPlanGenerator - Phase 3: generate transform chain edge list [ExecutionEdge(leftVertex=ExecutionVertex(vertexId=1, action=org.apache.seatunnel.engine.core.dag.actions.SourceAction@2a502f47, parallelism=1), rightVertex=ExecutionVertex(vertexId=2, action=org.apache.seatunnel.engine.core.dag.actions.SinkAction@54d7c7e8, parallelism=1), leftVertexId=1, rightVertexId=2)]
2023-07-26 13:48:17,055 DEBUG org.apache.seatunnel.engine.server.dag.execution.ExecutionPlanGenerator - Phase 4: generate pipeline list [org.apache.seatunnel.engine.server.dag.execution.Pipeline@35024291]
2023-07-26 13:48:17,055 DEBUG org.apache.seatunnel.engine.server.dag.execution.ExecutionPlanGenerator - Phase 5: generate execution plan: org.apache.seatunnel.engine.server.dag.execution.ExecutionPlan@a22fef3
2023-07-26 13:48:17,064 INFO  org.apache.seatunnel.engine.checkpoint.storage.hdfs.HdfsStorage - Path /tmp/seatunnel/checkpoint_snapshot/736459787658592257 is not a directory
2023-07-26 13:48:17,064 INFO  org.apache.seatunnel.engine.checkpoint.storage.hdfs.HdfsStorage - No checkpoint found for job, job id is:<PHONE_NUMBER>58592257
2023-07-26 13:48:17,064 INFO  org.apache.seatunnel.engine.server.dag.physical.PhysicalVertex - The task Job SeaTunnel_Job<PHONE_NUMBER>58592257), Pipeline: [(1/1)], task: [pipeline-1 [Source[0]-MySQL-CDC-test_1_shared]-SourceTask (1/1)], taskGroupLocation: [TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=30000}] is in state CREATED when init state future
2023-07-26 13:48:17,064 INFO  org.apache.seatunnel.engine.server.dag.physical.PhysicalVertex - The task Job SeaTunnel_Job<PHONE_NUMBER>58592257), Pipeline: [(1/1)], task: [pipeline-1 [Source[0]-MySQL-CDC-test_1_shared]-SplitEnumerator (1/1)], taskGroupLocation: [TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=1}] is in state CREATED when init state future
2023-07-26 13:48:17,065 INFO  org.apache.seatunnel.engine.server.master.JobMaster - Job Job SeaTunnel_Job<PHONE_NUMBER>58592257) waiting for scheduler finished
2023-07-26 13:48:17,065 INFO  org.apache.seatunnel.engine.server.dag.physical.PhysicalPlan - Job SeaTunnel_Job<PHONE_NUMBER>58592257) turn from state CREATED to SCHEDULED.
2023-07-26 13:48:17,066 INFO  org.apache.seatunnel.engine.server.dag.physical.SubPlan - Job SeaTunnel_Job<PHONE_NUMBER>58592257), Pipeline: [(1/1)] turn from state CREATED to SCHEDULED.
2023-07-26 13:48:17,066 DEBUG org.apache.seatunnel.engine.server.dag.physical.PhysicalVertex - Try to update the task Job SeaTunnel_Job<PHONE_NUMBER>58592257), Pipeline: [(1/1)], task: [pipeline-1 [Source[0]-MySQL-CDC-test_1_shared]-SplitEnumerator (1/1)], taskGroupLocation: [TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=1}] state from CREATED to SCHEDULED
2023-07-26 13:48:17,067 INFO  org.apache.seatunnel.engine.server.dag.physical.PhysicalVertex - Job SeaTunnel_Job<PHONE_NUMBER>58592257), Pipeline: [(1/1)], task: [pipeline-1 [Source[0]-MySQL-CDC-test_1_shared]-SplitEnumerator (1/1)], taskGroupLocation: [TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=1}] turn from state CREATED to SCHEDULED.
2023-07-26 13:48:17,067 DEBUG org.apache.seatunnel.engine.server.dag.physical.PhysicalVertex - Try to update the task Job SeaTunnel_Job<PHONE_NUMBER>58592257), Pipeline: [(1/1)], task: [pipeline-1 [Source[0]-MySQL-CDC-test_1_shared]-SourceTask (1/1)], taskGroupLocation: [TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=30000}] state from CREATED to SCHEDULED
2023-07-26 13:48:17,067 DEBUG org.apache.seatunnel.engine.server.service.slot.DefaultSlotService - received slot request, jobID:<PHONE_NUMBER>58592257, resource profile: ResourceProfile{cpu=CPU{core=0}, heapMemory=Memory{bytes=0}}, return: SlotProfile{worker=[ds01]:5801, slotID=3, ownerJobID=736459787658592257, assigned=true, resourceProfile=ResourceProfile{cpu=CPU{core=0}, heapMemory=Memory{bytes=0}}, sequence='f39eac91-0fc0-4dc9-bcaf-64f8d55dee79'}
2023-07-26 13:48:17,067 INFO  org.apache.seatunnel.engine.server.dag.physical.PhysicalVertex - Job SeaTunnel_Job<PHONE_NUMBER>58592257), Pipeline: [(1/1)], task: [pipeline-1 [Source[0]-MySQL-CDC-test_1_shared]-SourceTask (1/1)], taskGroupLocation: [TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=30000}] turn from state CREATED to SCHEDULED.
2023-07-26 13:48:17,068 DEBUG org.apache.seatunnel.engine.server.service.slot.DefaultSlotService - received slot request, jobID:<PHONE_NUMBER>58592257, resource profile: ResourceProfile{cpu=CPU{core=0}, heapMemory=Memory{bytes=0}}, return: SlotProfile{worker=[ds01]:5801, slotID=4, ownerJobID=736459787658592257, assigned=true, resourceProfile=ResourceProfile{cpu=CPU{core=0}, heapMemory=Memory{bytes=0}}, sequence='f39eac91-0fc0-4dc9-bcaf-64f8d55dee79'}
2023-07-26 13:48:17,068 DEBUG org.apache.seatunnel.engine.server.resourcemanager.AbstractResourceManager - received worker heartbeat from: [ds01]:5801
2023-07-26 13:48:17,068 DEBUG org.apache.seatunnel.engine.server.resourcemanager.AbstractResourceManager - received worker heartbeat from: [ds01]:5801
2023-07-26 13:48:17,068 DEBUG org.apache.seatunnel.engine.server.scheduler.PipelineBaseScheduler - slotProfiles: {TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=1}=SlotProfile{worker=[ds01]:5801, slotID=3, ownerJobID=736459787658592257, assigned=true, resourceProfile=ResourceProfile{cpu=CPU{core=0}, heapMemory=Memory{bytes=0}}, sequence='f39eac91-0fc0-4dc9-bcaf-64f8d55dee79'}, TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=30000}=SlotProfile{worker=[ds01]:5801, slotID=4, ownerJobID=736459787658592257, assigned=true, resourceProfile=ResourceProfile{cpu=CPU{core=0}, heapMemory=Memory{bytes=0}}, sequence='f39eac91-0fc0-4dc9-bcaf-64f8d55dee79'}}, PipelineLocation: PipelineLocation(jobId=736459787658592257, pipelineId=1)
2023-07-26 13:48:17,075 INFO  org.apache.seatunnel.engine.server.dag.physical.SubPlan - Job SeaTunnel_Job<PHONE_NUMBER>58592257), Pipeline: [(1/1)] turn from state SCHEDULED to DEPLOYING.
2023-07-26 13:48:17,076 DEBUG org.apache.seatunnel.engine.server.dag.physical.PhysicalVertex - Try to update the task Job SeaTunnel_Job<PHONE_NUMBER>58592257), Pipeline: [(1/1)], task: [pipeline-1 [Source[0]-MySQL-CDC-test_1_shared]-SplitEnumerator (1/1)], taskGroupLocation: [TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=1}] state from SCHEDULED to DEPLOYING
2023-07-26 13:48:17,077 INFO  org.apache.seatunnel.engine.server.dag.physical.PhysicalVertex - Job SeaTunnel_Job<PHONE_NUMBER>58592257), Pipeline: [(1/1)], task: [pipeline-1 [Source[0]-MySQL-CDC-test_1_shared]-SplitEnumerator (1/1)], taskGroupLocation: [TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=1}] turn from state SCHEDULED to DEPLOYING.
2023-07-26 13:48:17,077 DEBUG org.apache.seatunnel.engine.server.dag.physical.PhysicalVertex - Try to update the task Job SeaTunnel_Job<PHONE_NUMBER>58592257), Pipeline: [(1/1)], task: [pipeline-1 [Source[0]-MySQL-CDC-test_1_shared]-SourceTask (1/1)], taskGroupLocation: [TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=30000}] state from SCHEDULED to DEPLOYING
2023-07-26 13:48:17,077 INFO  org.apache.seatunnel.engine.server.dag.physical.PhysicalVertex - Job SeaTunnel_Job<PHONE_NUMBER>58592257), Pipeline: [(1/1)], task: [pipeline-1 [Source[0]-MySQL-CDC-test_1_shared]-SourceTask (1/1)], taskGroupLocation: [TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=30000}] turn from state SCHEDULED to DEPLOYING.
2023-07-26 13:48:17,078 INFO  org.apache.seatunnel.engine.server.TaskExecutionService - [ds01]:5801 [seatunnel] [5.1] received deploying task executionId [736459461644124161]
2023-07-26 13:48:17,079 INFO  org.apache.seatunnel.engine.server.TaskExecutionService - [ds01]:5801 [seatunnel] [5.1] received deploying task executionId [736459461644189697]
2023-07-26 13:48:17,116 INFO  org.apache.seatunnel.engine.server.TaskExecutionService - [ds01]:5801 [seatunnel] [5.1] deploying task TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=1}, executionId [736459461644124161]
2023-07-26 13:48:17,116 INFO  org.apache.seatunnel.engine.server.TaskExecutionService - [ds01]:5801 [seatunnel] [5.1] deploying TaskGroup TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=1} init success
2023-07-26 13:48:17,117 INFO  org.apache.seatunnel.engine.server.task.SourceSplitEnumeratorTask - starting seatunnel source split enumerator task, source name: pipeline-1 [Source[0]-MySQL-CDC-test_1_shared]
2023-07-26 13:48:17,118 INFO  org.apache.seatunnel.engine.server.TaskExecutionService - [ds01]:5801 [seatunnel] [5.1] deploying TaskGroup TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=1} success
2023-07-26 13:48:17,118 DEBUG org.apache.seatunnel.engine.server.dag.physical.PhysicalVertex - Try to update the task Job SeaTunnel_Job<PHONE_NUMBER>58592257), Pipeline: [(1/1)], task: [pipeline-1 [Source[0]-MySQL-CDC-test_1_shared]-SplitEnumerator (1/1)], taskGroupLocation: [TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=1}] state from DEPLOYING to RUNNING
2023-07-26 13:48:17,118 INFO  org.apache.seatunnel.engine.server.dag.physical.PhysicalVertex - Job SeaTunnel_Job<PHONE_NUMBER>58592257), Pipeline: [(1/1)], task: [pipeline-1 [Source[0]-MySQL-CDC-test_1_shared]-SplitEnumerator (1/1)], taskGroupLocation: [TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=1}] turn from state DEPLOYING to RUNNING.
2023-07-26 13:48:17,124 DEBUG org.apache.seatunnel.engine.server.checkpoint.CheckpointManager - reported task(20000) status WAITING_RESTORE
2023-07-26 13:48:17,125 DEBUG org.apache.seatunnel.engine.server.checkpoint.CheckpointManager - Sead Operation : NotifyTaskRestoreOperation to [ds01]:5801 for task group:TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=1}
2023-07-26 13:48:17,125 DEBUG org.apache.seatunnel.engine.server.checkpoint.operation.NotifyTaskRestoreOperation - NotifyTaskRestoreOperation TaskLocation{taskGroupLocation=TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=1}, taskID=20000, index=0}
2023-07-26 13:48:17,125 DEBUG org.apache.seatunnel.engine.server.TaskExecutionService - [ds01]:5801 [seatunnel] [5.1] accept async execute function from TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=1} with id 45c7e733-54f0-49c9-bb58-fb79c07df71e
2023-07-26 13:48:17,125 DEBUG org.apache.seatunnel.engine.server.checkpoint.operation.NotifyTaskRestoreOperation - NotifyTaskRestoreOperation.restoreState []
2023-07-26 13:48:17,125 DEBUG org.apache.seatunnel.engine.server.task.SourceSplitEnumeratorTask - restoreState for split enumerator [[]]
2023-07-26 13:48:17,128 INFO  org.apache.seatunnel.engine.server.TaskExecutionService - [ds01]:5801 [seatunnel] [5.1] deploying task TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=30000}, executionId [736459461644189697]
2023-07-26 13:48:17,128 INFO  org.apache.seatunnel.engine.server.TaskExecutionService - [ds01]:5801 [seatunnel] [5.1] deploying TaskGroup TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=30000} init success
2023-07-26 13:48:17,135 INFO  org.apache.seatunnel.engine.server.TaskExecutionService - [ds01]:5801 [seatunnel] [5.1] deploying TaskGroup TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=30000} success
2023-07-26 13:48:17,135 DEBUG org.apache.seatunnel.engine.server.dag.physical.PhysicalVertex - Try to update the task Job SeaTunnel_Job<PHONE_NUMBER>58592257), Pipeline: [(1/1)], task: [pipeline-1 [Source[0]-MySQL-CDC-test_1_shared]-SourceTask (1/1)], taskGroupLocation: [TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=30000}] state from DEPLOYING to RUNNING
2023-07-26 13:48:17,136 INFO  org.apache.seatunnel.engine.server.task.TransformSeaTunnelTask - starting seatunnel transform task, index 0
2023-07-26 13:48:17,143 DEBUG org.apache.seatunnel.engine.server.checkpoint.CheckpointManager - reported task(50000) status WAITING_RESTORE
2023-07-26 13:48:17,143 DEBUG org.apache.seatunnel.engine.server.checkpoint.CheckpointManager - Sead Operation : NotifyTaskRestoreOperation to [ds01]:5801 for task group:TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=30000}
2023-07-26 13:48:17,144 DEBUG org.apache.seatunnel.engine.server.checkpoint.operation.NotifyTaskRestoreOperation - NotifyTaskRestoreOperation TaskLocation{taskGroupLocation=TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=30000}, taskID=50000, index=0}
2023-07-26 13:48:17,144 DEBUG org.apache.seatunnel.engine.server.TaskExecutionService - [ds01]:5801 [seatunnel] [5.1] accept async execute function from TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=30000} with id 991487d5-4230-43b7-99bd-3a2d7db36a4f
2023-07-26 13:48:17,144 DEBUG org.apache.seatunnel.engine.server.checkpoint.operation.NotifyTaskRestoreOperation - NotifyTaskRestoreOperation.restoreState []
2023-07-26 13:48:17,144 DEBUG org.apache.seatunnel.engine.server.task.SeaTunnelTask - restoreState for SeaTunnelTask[[]]
2023-07-26 13:48:17,145 INFO  org.apache.seatunnel.engine.server.dag.physical.PhysicalVertex - Job SeaTunnel_Job<PHONE_NUMBER>58592257), Pipeline: [(1/1)], task: [pipeline-1 [Source[0]-MySQL-CDC-test_1_shared]-SourceTask (1/1)], taskGroupLocation: [TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=30000}] turn from state DEPLOYING to RUNNING.
2023-07-26 13:48:17,145 INFO  org.apache.seatunnel.engine.server.dag.physical.SubPlan - Job SeaTunnel_Job<PHONE_NUMBER>58592257), Pipeline: [(1/1)] turn from state DEPLOYING to RUNNING.
2023-07-26 13:48:17,146 INFO  org.apache.seatunnel.engine.server.dag.physical.PhysicalPlan - Job SeaTunnel_Job<PHONE_NUMBER>58592257) turn from state SCHEDULED to RUNNING.
2023-07-26 13:48:17,148 INFO  org.apache.seatunnel.engine.server.master.JobMaster - Job SeaTunnel_Job<PHONE_NUMBER>58592257) scheduler finished
2023-07-26 13:48:17,151 DEBUG org.apache.seatunnel.engine.server.service.slot.DefaultSlotService - start send heartbeat to resource manager, this address: [ds01]:5801
2023-07-26 13:48:17,151 DEBUG org.apache.seatunnel.engine.server.resourcemanager.AbstractResourceManager - received worker heartbeat from: [ds01]:5801
2023-07-26 13:48:17,162 DEBUG org.apache.seatunnel.engine.server.task.SeaTunnelTask - restoreState for SeaTunnelTask finished, actionStateList: []
2023-07-26 13:48:17,162 DEBUG org.apache.seatunnel.engine.server.checkpoint.operation.NotifyTaskRestoreOperation - NotifyTaskRestoreOperation.finished []
2023-07-26 13:48:17,162 DEBUG org.apache.seatunnel.engine.server.TaskExecutionService - [ds01]:5801 [seatunnel] [5.1] remove async execute function from TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=30000} with id 991487d5-4230-43b7-99bd-3a2d7db36a4f
2023-07-26 13:48:17,189 INFO  org.apache.seatunnel.engine.server.task.SourceSeaTunnelTask - starting seatunnel source task, index 0
2023-07-26 13:48:17,190 DEBUG org.apache.seatunnel.engine.server.checkpoint.CheckpointManager - reported task(40000) status WAITING_RESTORE
2023-07-26 13:48:17,190 DEBUG org.apache.seatunnel.engine.server.checkpoint.CheckpointManager - Sead Operation : NotifyTaskRestoreOperation to [ds01]:5801 for task group:TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=30000}
2023-07-26 13:48:17,190 DEBUG org.apache.seatunnel.engine.server.checkpoint.operation.NotifyTaskRestoreOperation - NotifyTaskRestoreOperation TaskLocation{taskGroupLocation=TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=30000}, taskID=40000, index=0}
2023-07-26 13:48:17,190 DEBUG org.apache.seatunnel.engine.server.TaskExecutionService - [ds01]:5801 [seatunnel] [5.1] accept async execute function from TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=30000} with id d8f7052c-2e02-4872-a164-52609b82df3a
2023-07-26 13:48:17,191 INFO  com.zaxxer.hikari.HikariDataSource - connection-pool-<IP_ADDRESS>:33306 - Starting...
2023-07-26 13:48:17,192 DEBUG org.apache.seatunnel.engine.server.checkpoint.operation.NotifyTaskRestoreOperation - NotifyTaskRestoreOperation.restoreState []
2023-07-26 13:48:17,192 DEBUG org.apache.seatunnel.engine.server.task.SeaTunnelTask - restoreState for SeaTunnelTask[[]]
2023-07-26 13:48:17,192 DEBUG org.apache.seatunnel.engine.server.task.SeaTunnelTask - restoreState for SeaTunnelTask finished, actionStateList: []
2023-07-26 13:48:17,192 DEBUG org.apache.seatunnel.engine.server.checkpoint.operation.NotifyTaskRestoreOperation - NotifyTaskRestoreOperation.finished []
2023-07-26 13:48:17,192 DEBUG org.apache.seatunnel.engine.server.TaskExecutionService - [ds01]:5801 [seatunnel] [5.1] remove async execute function from TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=30000} with id d8f7052c-2e02-4872-a164-52609b82df3a
2023-07-26 13:48:17,244 DEBUG org.apache.seatunnel.engine.server.checkpoint.CheckpointManager - reported task(50000) status READY_START
2023-07-26 13:48:17,291 INFO  org.apache.seatunnel.connectors.seatunnel.common.source.reader.SourceReaderBase - Open Source Reader.
2023-07-26 13:48:17,291 DEBUG org.apache.seatunnel.engine.server.TaskExecutionService - [ds01]:5801 [seatunnel] [5.1] accept async execute function from TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=1} with id 2fc2402a-ecbe-4b5b-a850-1e1ca2620b99
2023-07-26 13:48:17,291 INFO  org.apache.seatunnel.engine.server.task.SourceSplitEnumeratorTask - received reader register, readerID: TaskLocation{taskGroupLocation=TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=30000}, taskID=40000, index=0}
2023-07-26 13:48:17,294 DEBUG org.apache.seatunnel.engine.server.checkpoint.CheckpointManager - reported task(40000) status READY_START
2023-07-26 13:48:17,319 INFO  com.zaxxer.hikari.HikariDataSource - connection-pool-<IP_ADDRESS>:33306 - Start completed.
2023-07-26 13:48:17,343 INFO  org.apache.seatunnel.connectors.seatunnel.cdc.mysql.utils.TableDiscoveryUtils - Read list of available databases
2023-07-26 13:48:17,364 INFO  org.apache.seatunnel.connectors.seatunnel.cdc.mysql.utils.TableDiscoveryUtils -    list of available databases is: [information_schema, cdc_test]
2023-07-26 13:48:17,364 INFO  org.apache.seatunnel.connectors.seatunnel.cdc.mysql.utils.TableDiscoveryUtils - Read list of available tables in each database
2023-07-26 13:48:17,378 INFO  io.debezium.jdbc.JdbcConnection - Connection gracefully closed
2023-07-26 13:48:17,389 INFO  io.debezium.jdbc.JdbcConnection - Connection gracefully closed
2023-07-26 13:48:17,392 DEBUG org.apache.seatunnel.engine.server.task.SourceSplitEnumeratorTask - restoreState split enumerator [[]] finished
2023-07-26 13:48:17,392 DEBUG org.apache.seatunnel.engine.server.checkpoint.operation.NotifyTaskRestoreOperation - NotifyTaskRestoreOperation.finished []
2023-07-26 13:48:17,392 DEBUG org.apache.seatunnel.engine.server.TaskExecutionService - [ds01]:5801 [seatunnel] [5.1] remove async execute function from TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=1} with id 45c7e733-54f0-49c9-bb58-fb79c07df71e
2023-07-26 13:48:17,398 DEBUG org.apache.seatunnel.engine.server.task.SourceSplitEnumeratorTask - reader register complete, current task size 1
2023-07-26 13:48:17,398 DEBUG org.apache.seatunnel.engine.server.TaskExecutionService - [ds01]:5801 [seatunnel] [5.1] remove async execute function from TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=1} with id 2fc2402a-ecbe-4b5b-a850-1e1ca2620b99
2023-07-26 13:48:17,425 DEBUG org.apache.seatunnel.engine.server.checkpoint.CheckpointManager - reported task(20000) status READY_START
2023-07-26 13:48:17,425 DEBUG org.apache.seatunnel.engine.server.checkpoint.CheckpointManager - Sead Operation : NotifyTaskStartOperation to [ds01]:5801 for task group:TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=30000}
2023-07-26 13:48:17,426 DEBUG org.apache.seatunnel.engine.server.checkpoint.CheckpointManager - Sead Operation : NotifyTaskStartOperation to [ds01]:5801 for task group:TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=30000}
2023-07-26 13:48:17,426 DEBUG org.apache.seatunnel.engine.server.checkpoint.CheckpointManager - Sead Operation : NotifyTaskStartOperation to [ds01]:5801 for task group:TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=1}
2023-07-26 13:48:17,526 INFO  org.apache.seatunnel.engine.server.task.SourceSplitEnumeratorTask - received enough reader, starting enumerator...
2023-07-26 13:48:17,527 INFO  org.apache.seatunnel.connectors.seatunnel.cdc.mysql.source.eumerator.MySqlChunkSplitter - Start splitting table cdc_test.test_1 into chunks...
2023-07-26 13:48:17,546 INFO  io.debezium.jdbc.JdbcConnection - Connection gracefully closed
2023-07-26 13:48:17,566 WARN  io.debezium.relational.history.DatabaseHistoryMetrics - Unable to register the MBean 'debezium.mysql:type=connector-metrics,context=schema-history,server=mysql_binlog_source': debezium.mysql:type=connector-metrics,context=schema-history,server=mysql_binlog_source
2023-07-26 13:48:18,122 INFO  org.apache.seatunnel.connectors.seatunnel.cdc.mysql.source.eumerator.MySqlChunkSplitter - The distribution factor of table cdc_test.test_1 is 1.0 according to the min split key 1, max split key 2 and approximate row count 2
2023-07-26 13:48:18,122 INFO  org.apache.seatunnel.connectors.seatunnel.cdc.mysql.source.eumerator.MySqlChunkSplitter - Use evenly-sized chunk optimization for table cdc_test.test_1, the approximate row count is 2, the chunk size is 8096, the dynamic chunk size is 8096
2023-07-26 13:48:18,123 INFO  org.apache.seatunnel.connectors.seatunnel.cdc.mysql.source.eumerator.MySqlChunkSplitter - Split table cdc_test.test_1 into 1 chunks, time cost: 595ms.
2023-07-26 13:48:18,123 INFO  io.debezium.jdbc.JdbcConnection - Connection gracefully closed
2023-07-26 13:48:18,132 INFO  org.apache.seatunnel.connectors.seatunnel.common.source.reader.fetcher.SplitFetcher - Starting split fetcher 0
2023-07-26 13:48:18,162 WARN  io.debezium.connector.mysql.MySqlConnection - Database configuration option 'serverTimezone' is set but is obsolete, please use 'connectionTimeZone' instead
2023-07-26 13:48:18,186 INFO  com.zaxxer.hikari.HikariDataSource - connection-pool-<IP_ADDRESS>:33306 - Starting...
2023-07-26 13:48:18,192 WARN  com.zaxxer.hikari.util.DriverDataSource - Registered driver with driverClassName=com.mysql.cj.jdbc.Driver was not found, trying direct instantiation.
2023-07-26 13:48:18,214 INFO  com.zaxxer.hikari.HikariDataSource - connection-pool-<IP_ADDRESS>:33306 - Start completed.
2023-07-26 13:48:18,228 INFO  io.debezium.jdbc.JdbcConnection - Connection gracefully closed
2023-07-26 13:48:18,252 WARN  io.debezium.relational.history.DatabaseHistoryMetrics - Unable to register the MBean 'debezium.mysql:type=connector-metrics,context=schema-history,server=mysql_binlog_source': debezium.mysql:type=connector-metrics,context=schema-history,server=mysql_binlog_source
2023-07-26 13:48:18,949 WARN  io.debezium.relational.history.DatabaseHistoryMetrics - Unable to register the MBean 'debezium.mysql:type=connector-metrics,context=schema-history,server=mysql_binlog_source': debezium.mysql:type=connector-metrics,context=schema-history,server=mysql_binlog_source
2023-07-26 13:48:18,950 INFO  io.debezium.relational.history.DatabaseHistoryMetrics - Started database history recovery
2023-07-26 13:48:18,950 INFO  io.debezium.relational.history.DatabaseHistoryMetrics - Finished database history recovery of 0 change(s) in 0 ms
2023-07-26 13:48:19,461 INFO  org.apache.seatunnel.connectors.seatunnel.common.source.reader.fetcher.SplitFetcher - Finished reading from splits [cdc_test.test_1:0]
2023-07-26 13:48:19,499 INFO  org.apache.seatunnel.connectors.seatunnel.common.source.reader.SourceReaderBase - Finished reading split(s) [cdc_test.test_1:0]
2023-07-26 13:48:19,503 INFO  org.apache.seatunnel.connectors.cdc.base.source.enumerator.SnapshotSplitAssigner - Snapshot split assigner received all splits completed and the job parallelism is 1, snapshot split assigner is turn into completed status.
2023-07-26 13:48:19,509 INFO  org.apache.seatunnel.connectors.cdc.base.source.reader.IncrementalSourceSplitReader - It's turn to read incremental split, close current snapshot fetcher.
2023-07-26 13:48:19,511 INFO  io.debezium.jdbc.JdbcConnection - Connection gracefully closed
2023-07-26 13:48:19,512 WARN  io.debezium.connector.mysql.MySqlConnection - Database configuration option 'serverTimezone' is set but is obsolete, please use 'connectionTimeZone' instead
2023-07-26 13:48:19,513 INFO  org.apache.seatunnel.connectors.cdc.base.source.reader.IncrementalSourceSplitReader - Stream fetcher is created.
2023-07-26 13:48:19,530 WARN  io.debezium.relational.history.DatabaseHistoryMetrics - Unable to register the MBean 'debezium.mysql:type=connector-metrics,context=schema-history,server=mysql_binlog_source': debezium.mysql:type=connector-metrics,context=schema-history,server=mysql_binlog_source
2023-07-26 13:48:19,531 INFO  org.apache.seatunnel.connectors.seatunnel.cdc.mysql.source.reader.fetch.MySqlSourceFetchTaskContext - MySQL has the binlog file 'mysql-bin.000001' required by the connector
2023-07-26 13:48:19,531 INFO  io.debezium.relational.history.DatabaseHistoryMetrics - Started database history recovery
2023-07-26 13:48:19,531 INFO  io.debezium.relational.history.DatabaseHistoryMetrics - Finished database history recovery of 0 change(s) in 0 ms
2023-07-26 13:48:19,538 INFO  io.debezium.util.Threads - Requested thread factory for connector MySqlConnector, id = mysql_binlog_source named = binlog-client
2023-07-26 13:48:19,551 INFO  org.apache.seatunnel.connectors.seatunnel.jdbc.internal.executor.FieldNamedPreparedStatement - PrepareStatement sql is:
INSERT INTO `cdc_test`.`test_1_target` (`id`, `name`) VALUES (?, ?)

2023-07-26 13:48:19,558 INFO  io.debezium.util.Threads - Creating thread debezium-mysqlconnector-mysql_binlog_source-binlog-client
2023-07-26 13:48:19,561 INFO  io.debezium.util.Threads - Creating thread debezium-mysqlconnector-mysql_binlog_source-binlog-client
2023-07-26 13:48:19,569 INFO  io.debezium.util.Threads - Creating thread debezium-mysqlconnector-mysql_binlog_source-binlog-client
2023-07-26 13:48:22,142 DEBUG org.apache.seatunnel.engine.server.TaskExecutionService - [ds01]:5801 [seatunnel] [5.1]
***********************************************
    TaskExecutionServer Thread Pool Status
***********************************************
activeCount               :                   4
threadShareTaskQueueSize  :                   0
completedTaskCount        :                  37
taskCount                 :                  41
***********************************************

2023-07-26 13:48:22,148 DEBUG org.apache.seatunnel.engine.server.service.slot.DefaultSlotService - start send heartbeat to resource manager, this address: [ds01]:5801
2023-07-26 13:48:22,148 DEBUG org.apache.seatunnel.engine.server.resourcemanager.AbstractResourceManager - received worker heartbeat from: [ds01]:5801
2023-07-26 13:48:22,151 INFO  org.apache.seatunnel.engine.server.CoordinatorService - [ds01]:5801 [seatunnel] [5.1]
***********************************************
     CoordinatorService Thread Pool Status
***********************************************
activeCount               :                   1
corePoolSize              :                   0
maximumPoolSize           :<PHONE_NUMBER>
poolSize                  :                   6
completedTaskCount        :                  68
taskCount                 :                  69
***********************************************

2023-07-26 13:48:22,152 INFO  org.apache.seatunnel.engine.server.CoordinatorService - [ds01]:5801 [seatunnel] [5.1]
***********************************************
                Job info detail
***********************************************
createdJobCount           :                   0
scheduledJobCount         :                   0
runningJobCount           :                   1
failingJobCount           :                   0
failedJobCount            :                   0
cancellingJobCount        :                   0
canceledJobCount          :                   0
finishedJobCount          :                   0
restartingJobCount        :                   0
suspendedJobCount         :                   0
reconcilingJobCount       :                   0
***********************************************

2023-07-26 13:48:27,148 DEBUG org.apache.seatunnel.engine.server.service.slot.DefaultSlotService - start send heartbeat to resource manager, this address: [ds01]:5801
2023-07-26 13:48:27,148 DEBUG org.apache.seatunnel.engine.server.resourcemanager.AbstractResourceManager - received worker heartbeat from: [ds01]:5801
2023-07-26 13:48:32,141 DEBUG org.apache.seatunnel.engine.server.TaskExecutionService - [ds01]:5801 [seatunnel] [5.1]
***********************************************
    TaskExecutionServer Thread Pool Status
***********************************************
activeCount               :                   4
threadShareTaskQueueSize  :                   0
completedTaskCount        :                  37
taskCount                 :                  41
***********************************************

2023-07-26 13:48:32,148 DEBUG org.apache.seatunnel.engine.server.service.slot.DefaultSlotService - start send heartbeat to resource manager, this address: [ds01]:5801
2023-07-26 13:48:32,148 DEBUG org.apache.seatunnel.engine.server.resourcemanager.AbstractResourceManager - received worker heartbeat from: [ds01]:5801
2023-07-26 13:48:32,427 INFO  org.apache.seatunnel.engine.server.checkpoint.CheckpointCoordinator - wait checkpoint completed: 1
2023-07-26 13:48:32,427 DEBUG org.apache.seatunnel.engine.server.checkpoint.CheckpointCoordinator - trigger checkpoint barrier<PHONE_NUMBER>58592257/1/1, CHECKPOINT_TYPE
2023-07-26 13:48:32,428 DEBUG org.apache.seatunnel.engine.server.checkpoint.CheckpointManager - Sead Operation : CheckpointBarrierTriggerOperation to [ds01]:5801 for task group:TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=1}
2023-07-26 13:48:32,428 DEBUG org.apache.seatunnel.engine.server.checkpoint.CheckpointCoordinator - Start a scheduled task to prevent checkpoint timeouts for barrier<PHONE_NUMBER>58592257/1/1, CHECKPOINT_TYPE
2023-07-26 13:48:32,428 DEBUG org.apache.seatunnel.engine.server.TaskExecutionService - [ds01]:5801 [seatunnel] [5.1] accept async execute function from TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=1} with id 45e2811f-81a1-4984-9657-0ae58264b6d1
2023-07-26 13:48:32,428 DEBUG org.apache.seatunnel.engine.server.checkpoint.operation.CheckpointBarrierTriggerOperation - CheckpointBarrierTriggerOperation [TaskLocation{taskGroupLocation=TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=1}, taskID=20000, index=0}]
2023-07-26 13:48:32,428 DEBUG org.apache.seatunnel.engine.server.task.SourceSplitEnumeratorTask - split enumer trigger barrier [CheckpointBarrier 1 @<PHONE_NUMBER>427 Options: CHECKPOINT_TYPE]
2023-07-26 13:48:32,430 DEBUG org.apache.seatunnel.engine.server.task.SourceSplitEnumeratorTask - source split enumerator send state [HybridPendingSplitsState(snapshotPhaseState=SnapshotPhaseState(remainingTables=[], alreadyProcessedTables=[cdc_test.test_1], remainingSplits=[], assignedSplits={cdc_test.test_1:0=org.apache.seatunnel.connectors.cdc.base.source.split.SnapshotSplit@f041ba98}, splitCompletedOffsets={cdc_test.test_1:0={ts_sec=0, file=mysql-bin.000001, pos=12566283, gtids=209753da-221a-11ee-9983-76b78ab3e808:1-51705, row=0, event=0}}, isAssignerCompleted=true, isTableIdCaseSensitive=false, isRemainingTablesCheckpointed=true), incrementalPhaseState=IncrementalPhaseState())] to master
2023-07-26 13:48:32,430 DEBUG org.apache.seatunnel.engine.server.task.SourceSplitEnumeratorTask - split enumerator send to read--size: 1, location: TaskLocation{taskGroupLocation=TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=30000}, taskID=40000, index=0}, address: [ds01]:5801
2023-07-26 13:48:32,430 DEBUG org.apache.seatunnel.engine.server.TaskExecutionService - [ds01]:5801 [seatunnel] [5.1] accept async execute function from TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=30000} with id 8ddaf358-db77-401f-a336-992f4398ea7c
2023-07-26 13:48:32,430 DEBUG org.apache.seatunnel.engine.server.task.operation.checkpoint.BarrierFlowOperation - CheckpointBarrierTriggerOperation [TaskLocation{taskGroupLocation=TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=30000}, taskID=40000, index=0}]
2023-07-26 13:48:32,430 DEBUG org.apache.seatunnel.engine.server.task.flow.SourceFlowLifeCycle - source trigger barrier [CheckpointBarrier 1 @<PHONE_NUMBER>427 Options: CHECKPOINT_TYPE]
2023-07-26 13:48:32,430 DEBUG org.apache.seatunnel.engine.server.checkpoint.operation.TaskAcknowledgeOperation - TaskAcknowledgeOperation TaskLocation{taskGroupLocation=TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=1}, taskID=20000, index=0}
2023-07-26 13:48:32,431 DEBUG org.apache.seatunnel.engine.server.checkpoint.CheckpointManager - checkpoint manager received ack TaskLocation{taskGroupLocation=TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=1}, taskID=20000, index=0}
2023-07-26 13:48:32,431 DEBUG org.apache.seatunnel.engine.server.checkpoint.CheckpointCoordinator - task[20000](1/736459787658592257) ack. CheckpointBarrier 1 @<PHONE_NUMBER>427 Options: CHECKPOINT_TYPE
2023-07-26 13:48:32,431 DEBUG org.apache.seatunnel.engine.server.checkpoint.PendingCheckpoint - acknowledgeTask states [[ActionSubtaskState(stateKey=ActionStateKey(name=ActionStateKey - pipeline-1 [Source[0]-MySQL-CDC-test_1_shared]), index=-1, state=[[B@dc476b7])]]
2023-07-26 13:48:32,431 DEBUG org.apache.seatunnel.engine.server.checkpoint.operation.TaskAcknowledgeOperation - task ack finished TaskLocation{taskGroupLocation=TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=1}, taskID=20000, index=0}
2023-07-26 13:48:32,431 DEBUG org.apache.seatunnel.engine.server.TaskExecutionService - [ds01]:5801 [seatunnel] [5.1] remove async execute function from TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=1} with id 45e2811f-81a1-4984-9657-0ae58264b6d1
2023-07-26 13:48:32,431 DEBUG org.apache.seatunnel.engine.server.task.SeaTunnelTask - seatunnel task ack barrier[TaskLocation{taskGroupLocation=TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=30000}, taskID=40000, index=0}]
2023-07-26 13:48:32,431 DEBUG org.apache.seatunnel.engine.server.task.flow.SourceFlowLifeCycle - source ack barrier finished, taskId: [40000]
2023-07-26 13:48:32,431 DEBUG org.apache.seatunnel.engine.server.task.SeaTunnelTask - seatunnel task ack barrier[TaskLocation{taskGroupLocation=TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=30000}, taskID=40000, index=0}]
2023-07-26 13:48:32,431 DEBUG org.apache.seatunnel.engine.server.checkpoint.operation.TaskAcknowledgeOperation - TaskAcknowledgeOperation TaskLocation{taskGroupLocation=TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=30000}, taskID=40000, index=0}
2023-07-26 13:48:32,431 DEBUG org.apache.seatunnel.engine.server.checkpoint.CheckpointManager - checkpoint manager received ack TaskLocation{taskGroupLocation=TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=30000}, taskID=40000, index=0}
2023-07-26 13:48:32,431 DEBUG org.apache.seatunnel.engine.server.checkpoint.CheckpointCoordinator - task[40000](1/736459787658592257) ack. CheckpointBarrier 1 @<PHONE_NUMBER>427 Options: CHECKPOINT_TYPE
2023-07-26 13:48:32,431 DEBUG org.apache.seatunnel.engine.server.checkpoint.PendingCheckpoint - acknowledgeTask states [[ActionSubtaskState(stateKey=ActionStateKey(name=ActionStateKey - pipeline-1 [Source[0]-MySQL-CDC-test_1_shared]), index=0, state=[[B@79f1a229])]]
2023-07-26 13:48:32,432 DEBUG org.apache.seatunnel.engine.server.checkpoint.operation.TaskAcknowledgeOperation - task ack finished TaskLocation{taskGroupLocation=TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=30000}, taskID=40000, index=0}
2023-07-26 13:48:32,432 DEBUG org.apache.seatunnel.engine.server.task.flow.SourceFlowLifeCycle - send record to next finished, taskId: [40000]
2023-07-26 13:48:32,432 DEBUG org.apache.seatunnel.engine.server.task.SeaTunnelTask - seatunnel task ack barrier[TaskLocation{taskGroupLocation=TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=30000}, taskID=50000, index=0}]
2023-07-26 13:48:32,432 DEBUG org.apache.seatunnel.engine.server.TaskExecutionService - [ds01]:5801 [seatunnel] [5.1] remove async execute function from TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=30000} with id 8ddaf358-db77-401f-a336-992f4398ea7c
2023-07-26 13:48:32,432 DEBUG org.apache.seatunnel.engine.server.task.SeaTunnelTask - seatunnel task ack barrier[TaskLocation{taskGroupLocation=TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=30000}, taskID=50000, index=0}]
2023-07-26 13:48:32,432 DEBUG org.apache.seatunnel.engine.server.checkpoint.operation.TaskAcknowledgeOperation - TaskAcknowledgeOperation TaskLocation{taskGroupLocation=TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=30000}, taskID=50000, index=0}
2023-07-26 13:48:32,432 DEBUG org.apache.seatunnel.engine.server.checkpoint.CheckpointManager - checkpoint manager received ack TaskLocation{taskGroupLocation=TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=30000}, taskID=50000, index=0}
2023-07-26 13:48:32,432 DEBUG org.apache.seatunnel.engine.server.checkpoint.CheckpointCoordinator - task[50000](1/736459787658592257) ack. CheckpointBarrier 1 @<PHONE_NUMBER>427 Options: CHECKPOINT_TYPE
2023-07-26 13:48:32,432 DEBUG org.apache.seatunnel.engine.server.checkpoint.PendingCheckpoint - acknowledgeTask states [[ActionSubtaskState(stateKey=ActionStateKey(name=ActionStateKey - pipeline-1 [Sink[0]-jdbc-cdc_test.test_1]), index=0, state=[])]]
2023-07-26 13:48:32,432 DEBUG org.apache.seatunnel.engine.server.checkpoint.PendingCheckpoint - checkpoint is full ack!
2023-07-26 13:48:32,432 DEBUG org.apache.seatunnel.engine.server.checkpoint.operation.TaskAcknowledgeOperation - task ack finished TaskLocation{taskGroupLocation=TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=30000}, taskID=50000, index=0}
2023-07-26 13:48:32,432 DEBUG org.apache.seatunnel.engine.server.checkpoint.CheckpointCoordinator - pending checkpoint(1/1@736459787658592257) completed! cost: 5, trigger:<PHONE_NUMBER>427, completed:<PHONE_NUMBER>432
2023-07-26 13:48:32,473 INFO  org.apache.seatunnel.engine.server.checkpoint.CheckpointCoordinator - pending checkpoint(1/1@736459787658592257) notify finished!
2023-07-26 13:48:32,474 INFO  org.apache.seatunnel.engine.server.checkpoint.CheckpointCoordinator - start notify checkpoint completed, checkpoint:CompletedCheckpoint(jobId=736459787658592257, pipelineId=1, checkpointId=1, triggerTimestamp=1690350512427, checkpointType=CHECKPOINT_TYPE, completedTimestamp=1690350512432, taskStates={ActionStateKey(name=ActionStateKey - pipeline-1 [Sink[0]-jdbc-cdc_test.test_1])=ActionState(stateKey=ActionStateKey(name=ActionStateKey - pipeline-1 [Sink[0]-jdbc-cdc_test.test_1]), subtaskStates=[ActionSubtaskState(stateKey=ActionStateKey(name=ActionStateKey - pipeline-1 [Sink[0]-jdbc-cdc_test.test_1]), index=0, state=[])], coordinatorState=null, parallelism=1), ActionStateKey(name=ActionStateKey - pipeline-1 [Source[0]-MySQL-CDC-test_1_shared])=ActionState(stateKey=ActionStateKey(name=ActionStateKey - pipeline-1 [Source[0]-MySQL-CDC-test_1_shared]), subtaskStates=[ActionSubtaskState(stateKey=ActionStateKey(name=ActionStateKey - pipeline-1 [Source[0]-MySQL-CDC-test_1_shared]), index=0, state=[[B@79f1a229])], coordinatorState=ActionSubtaskState(stateKey=ActionStateKey(name=ActionStateKey - pipeline-1 [Source[0]-MySQL-CDC-test_1_shared]), index=-1, state=[[B@dc476b7]), parallelism=1)}, taskStatistics={2=TaskStatistics(jobVertexId=2, subtaskStats=[SubtaskStatistics(subtaskIndex=0, ackTimestamp=1690350512431, stateSize=1, subtaskStatus=RUNNING)], subtaskCompleted=[false], numAcknowledgedSubtasks=1, latestAckedSubtaskStatistics=null), 4=TaskStatistics(jobVertexId=4, subtaskStats=[SubtaskStatistics(subtaskIndex=0, ackTimestamp=1690350512432, stateSize=1, subtaskStatus=RUNNING)], subtaskCompleted=[false], numAcknowledgedSubtasks=1, latestAckedSubtaskStatistics=null), 5=TaskStatistics(jobVertexId=5, subtaskStats=[SubtaskStatistics(subtaskIndex=0, ackTimestamp=1690350512432, stateSize=0, subtaskStatus=RUNNING)], subtaskCompleted=[false], numAcknowledgedSubtasks=1, latestAckedSubtaskStatistics=null)})
2023-07-26 13:48:32,475 DEBUG org.apache.seatunnel.engine.server.checkpoint.CheckpointManager - Sead Operation : CheckpointFinishedOperation to [ds01]:5801 for task group:TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=30000}
2023-07-26 13:48:32,477 DEBUG org.apache.seatunnel.engine.server.checkpoint.CheckpointManager - Sead Operation : CheckpointFinishedOperation to [ds01]:5801 for task group:TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=30000}
2023-07-26 13:48:32,477 DEBUG org.apache.seatunnel.engine.server.checkpoint.CheckpointManager - Sead Operation : CheckpointFinishedOperation to [ds01]:5801 for task group:TaskGroupLocation{jobId=736459787658592257, pipelineId=1, taskGroupId=1}
2023-07-26 13:48:37,148 DEBUG org.apache.seatunnel.engine.server.service.slot.DefaultSlotService - start send heartbeat to resource manager, this address: [ds01]:5801
2023-07-26 13:48:37,148 DEBUG org.apache.seatunnel.engine.server.resourcemanager.AbstractResourceManager - received worker heartbeat from: [ds01]:5801
2023-07-26 13:48:42,140 DEBUG org.apache.seatunnel.engine.server.TaskExecutionService - [ds01]:5801 [seatunnel] [5.1]
***********************************************
    TaskExecutionServer Thread Pool Status
***********************************************
activeCount               :                   4
threadShareTaskQueueSize  :                   0
completedTaskCount        :                  39
taskCount                 :                  43
***********************************************

2023-07-26 13:48:42,148 DEBUG org.apache.seatunnel.engine.server.service.slot.DefaultSlotService - start send heartbeat to resource manager, this address: [ds01]:5801
2023-07-26 13:48:42,148 DEBUG org.apache.seatunnel.engine.server.resourcemanager.AbstractResourceManager - received worker heartbeat from: [ds01]:5801
2023-07-26 13:48:47,148 DEBUG org.apache.seatunnel.engine.server.service.slot.DefaultSlotService - start send heartbeat to resource manager, this address: [ds01]:5801
2023-07-26 13:48:47,148 DEBUG org.apache.seatunnel.engine.server.resourcemanager.AbstractResourceManager - received worker heartbeat from: [ds01]:5801
2023-07-26 13:48:47,428 INFO  org.apache.seatunnel.engine.server.checkpoint.CheckpointCoordinator - wait checkpoint completed: 2

SeaTunnel Version
2.3.2
SeaTunnel Config
seatunnel:
  engine:
    backup-count: 1
    queue-type: blockingqueue
    print-execution-info-interval: 60
    print-job-metrics-info-interval: 60
    slot-service:
      dynamic-slot: true
    checkpoint:
      interval: 10000
      timeout: 60000
      max-concurrent: 1
      tolerable-failure: 2
      storage:
        type: hdfs
        max-retained: 3
        plugin-config:
          namespace: /tmp/seatunnel/checkpoint_snapshot
          storage.type: hdfs
          fs.defaultFS: file:///tmp

Running Command
./bin/seatunnel-cluster.sh -d

Error Exception
Nothing

Flink or Spark Version
No response
Java or Scala Version
1.8.0_191
Screenshots
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

it's normal,but you should apply a pathch # 5054

it's normal,but you should apply a patch #5054


Laravel 10 Compatibility?

Is this package already Laravel 10 compatible? I just tried it on a completely new project and it does not look like, as I got this error:
Object of class Illuminate\\Database\\Query\\Expression could not be converted to string at /var/www/l10/vendor/coroowicaksono/chart-js-integration/src/api/TotalRecordsController.php:174
To Reproduce
Steps to reproduce the behavior:

Create new Laravel 10 Project
Install Nova 4 and coroo/nova-chartjs
migrate and add some users
Add the Code for a Simple Stacked Chart with Laravel Model to the Main Dashboard:

class Main extends Dashboard
{
    /**
     * Get the cards for the dashboard.
     *
     * @return array
     */
    public function cards()
    {
        return [
              (new StackedChart())
                ->title('Revenue')
                ->model('\App\Models\User') // Use Your Model Here
                ->width('2/3'),
        ];
    }
}

@ndberg  just add ->col_xaxis('created_at') after ->model('\App\Models\User') .
The issue is when we don't provide col_xaxis it takes reference from DB::raw($tableName . '.created_at') which creates an issue here.


Ticket/369

Clarified / handled timezones properly in the organizer-facing interface.

Resolves #369.


docs: remove module-metadata.json and commitlint.config.js

/run pipeline

@akocbek can you resolve conflicts please?


Increase snapshot creation interval

Current snapshots are pretty old. That's bad (especially on busy networks) bcs it can lead to running into RPC rate limits right at the beginning.
We have a pretty good pipeline for snapshot creation and should make the little (?) extra effort to automate more frequent updates.

cronjob was disabled. Is not on again with 1 month interval.
Running on sentinel@buck-1


timerMs corrupts readings

Reads 25MHz with timerMs = 1000 and 100. Other values corrupts the value of frequency.
#include "FreqCountESP.h"
void setup()
{
int inputPin = 14;
int timerMs = 100;
FreqCountESP.begin(inputPin, timerMs);
Serial.begin(115200);
}
void loop()
{
if (FreqCountESP.available())
{
uint32_t frequency = FreqCountESP.read();
Serial.println(frequency);
// Do something with the frequency...
}
}

I have a similar problem.
If I keep reading a stable frequency source, the reading varies slightly  on successive reads.
I had the same problem with Arduino ATmega328 device.
Arduino delay() statement uses Timer0 which causes interrupts every 10ms(?).  I had to stop Timer0 interrupts during the frequency count, using a register write, that worked!  How can I do that for the ESP32?  I am using Arduino IDE.

davidllpz,
timerMs is the gate for the frequency counter.  I have tried different values it works fine.  timerMs=100 gives you the frequency to 10Hz resolution, 1000 gives you 1Hz resolution.  If you used something like 500, you will need to multiply the result to see the frequency in 1Hz (with only 2Hz resolution.  Also, be aware that the crystal is not exactly 40MHz and there is no way to correct it, so the accuracy in not 100%.

I added some 'correction' code so any integer works for timerMs
''' #include "FreqCountESP.h"
int inputPin = 14;
int timerMs = 250;  // how many milliseconds to count, the longer the more accurate
// slight mod so that any number can be used for timerMs, the original library only shows hz when it is set to 1000
int correction = 1000 / timerMs;
int corrected = 0;
void setup()
{
Serial.begin(9600);
FreqCountESP.begin(inputPin, timerMs);
}
void loop()
{
if (FreqCountESP.available())
{
uint32_t frequency = FreqCountESP.read();
corrected = frequency * correction;
Serial.println(corrected);

}
}'''

If you guys are reading a stable signal, you should be seeing my problem.  Set your signal generator to something like 10.0000MHz.
You might get a reading of 10.0001 or 10.0009 or something.  That would be due to the crystal not being exact, etc. and YES,
you can correct for that.
BUT, you should get a very stable reading, maybe +/-1LSB.
ESP32 can not do that for me.   Readings are much more variable +/-MANY counts, different with each count.
I attribute that to the built in real time multi-tasking operating system that you can not stop during
the frequency count.  There SHOULD be a way but I can't find it, help would be appreciated.   Gary WB6OGD


Remove sender from update_last_login

I can't see the attribute "sender" in update_last_login being used anywhere in this file nor is it returned so another object could use it.

I don't see any downside (or much benefit for that matter) but if we're going to remove unused arguments from this receiver, I'd think we should remove unused arguments from all receivers.


FIxed ReadMe.md formatting and added NPM publishing action

corrected markdown

@sstur your formatting was a touch off in the readme so I cleaned it up while I was writing you an NPM Publishing action so we can get this package consumable.
Generate and add two tokens to your repo secrets to use:
PUBLISH_GITHUB_TOKEN
PUBLISH_NPM_TOKEN
When a new Release tag is created in GitHub it will automatically build and generate a new NPM package and deploy it to both NPM and GitHub registries.

I have a legacy project that still utilizes it in production.


Chinese is not supported

It seems that Chinese is not supported. As long as the code file contains Chinese, it will fail.

pull request welcomed


"Cannot read property previousSibling of null" error when selecting cells

Create new Notebook
Add two text cells
Click to select one, then click back and forth to select the other one multiple times

I'm seeing a bunch of these errors in the console.
ERR Cannot read property 'previousSibling' of null: TypeError: Cannot read property 'previousSibling' of null
    at c.getNodeIndex (vscode-file://vscode-app/c:/Users/chgagnon/AppData/Local/Programs/Azure%20Data%20Studio%20-%20RC1/resources/app/out/vs/workbench/workbench.desktop.main.js:3267:155338)
    at vscode-file://vscode-app/c:/Users/chgagnon/AppData/Local/Programs/Azure%20Data%20Studio%20-%20RC1/resources/app/out/vs/workbench/workbench.desktop.main.js:3267:154761
    at i.fire (vscode-file://vscode-app/c:/Users/chgagnon/AppData/Local/Programs/Azure%20Data%20Studio%20-%20RC1/resources/app/out/vs/workbench/workbench.desktop.main.js:129:1712)
    at S.doModeUpdates (vscode-file://vscode-app/c:/Users/chgagnon/AppData/Local/Programs/Azure%20Data%20Studio%20-%20RC1/resources/app/out/vs/workbench/workbench.desktop.main.js:997:12838)
    at S.set showMarkdown [as showMarkdown] (vscode-file://vscode-app/c:/Users/chgagnon/AppData/Local/Programs/Azure%20Data%20Studio%20-%20RC1/resources/app/out/vs/workbench/workbench.desktop.main.js:997:12591)
    at c.toggleEditMode (vscode-file://vscode-app/c:/Users/chgagnon/AppData/Local/Programs/Azure%20Data%20Studio%20-%20RC1/resources/app/out/vs/workbench/workbench.desktop.main.js:3267:158341)
    at c.ngOnChanges (vscode-file://vscode-app/c:/Users/chgagnon/AppData/Local/Programs/Azure%20Data%20Studio%20-%20RC1/resources/app/out/vs/workbench/workbench.desktop.main.js:3267:155280)

I've seen this multiple times in previous releases. Moving out.


Incompatibility with latest HLS.js versions

On the provided demo, the error e.parsing is undefined is thrown. Same goes for my implementation.
Has there been an update to HLS.js that broke this project?
Update: Works if I target<EMAIL_ADDRESS>

@MeguminSama What is the version of hls.js that does not work?

I've only tested with the latest, but I think it's broken because of a major release.

@MeguminSama Could you provide some more stack trace/logs from the error output?

Upon visiting https://moshisushi.github.io/ipfs_hls_example.html
Firstly:
Uncaught (in promise) TypeError: e.parsing is undefined
    loadsuccess https://cdn.jsdelivr.net/npm/hls.js@latest:1
    loadInternal https://cdn.jsdelivr.net/npm/hlsjs-ipfs-loader@latest/dist/index.js:254
hls.js@latest:1:100225
    loadsuccess hls.js@latest:1
    <anonymous> self-hosted:1178
    loadInternal index.js:115

Secondly:
Uncaught (in promise) TypeError: e.parsing is undefined
    loadsuccess hls.js@latest:1
    loadInternal index.js:115
    promise callback*loadInternal index.js:110
    load index.js:40
    load hls.js@latest:1
    onManifestLoading hls.js@latest:1
    emit hls.js@latest:1
    emit hls.js@latest:1
    trigger hls.js@latest:1
    loadSource hls.js@latest:1
    handleInit ipfs_hls_example.html:28
    <anonymous> ipfs_hls_example.html:14
    async* ipfs_hls_example.html:35
hls.js@latest:1:100225

@vaultec81 , it is an awesome loader, can you update to support stable hls player?


Change the logger name for kestrel http server

Any reason why we do this way in Kestrel.

Duplicate: https://github.com/aspnet/KestrelHttpServer/issues/775


Angular Translate IE 10/11 language detection

I am using angular translate for my project and I see that language detection fails for IE 10/11 when we do determinePreferredLanguage(). It never returns my preferred language and always defaults to en-US which is second in my preference order. Is this a known issue? Any workarounds?

Please see #1094 . Closing this as a duplicate.


[5.4] Added strict comparison to integers and strings

Added strict comparison to safe integer and string comparison. On projects with a high load, any help is welcome.

It's hard to merge such big changes right now and review each file so close to release. If there is a specific check that could be a bug we would be glad to merge fixes related to that.


Add explanation how to use metadata repository locally

What does this PR do?
Extends Readme file with the explanation of how to test your project or local changes of this repo, locally.

Good idea, any way we can avoid running the entire gate when we're updating the docs?

Yes, good point. I would try to prevent running the tests when only documentation is changed.


Thoughts on persistant caching

I made a loader called dynohot which implements hot module reloading in nodejs as an experimental loader.
One of the requirements of the loader is a code transformation written using Babel. Like all Babel transformations there is a good bit of overhead involved. I wanted to add a file cache to avoid the transformation in the common case where most source files are unchanged since the last invocation. This raised a bunch of questions and ad-hoc solutions that I'd like to share here.
How do we know what previous loaders are doing?
The result of nextLoad may change depending on what loaders are defined before us in the chain. If we want to be able to cache a result then it is necessary to ask each loader for a cache key.
The ad-hoc solution for this is a resolve hook. Cache-aware loaders will define a resolver for "loader:cache-key" and add their cache key to the payload blob. A cache provider will resolve this cache key and use it as a "namespace" while caching.
// `settings` could be anything. I've been defining loader settings in query strings:
// --loader "dynohot?ignore=pattern"
const self = new URL(import.meta.url);
const ignoreString = self.searchParams.get("ignore");
const ignorePattern = ignoreString === null ? /[/\\]node_modules[/\\]/ : new RegExp(ignoreString);

const settings = { ignore: ignoreString };
const cacheKey = JSON.stringify({ name: "dynohot", version: 1, settings });

export const resolve: NodeResolve = async (specifier, context, nextResolve) => {
	if (specifier === "loader:cache-key") {
		const previous = await async function() {
			try {
				const previous = await nextResolve(specifier, context);
				const url = new URL(previous.url);
				return url.searchParams.get("payload");
			} catch {}
		}();
		const payload = `${previous};${cacheKey}`;
		return {
			shortCircuit: true,
			url: `loader:cache-key?payload=${encodeURIComponent(payload)}`,
		};
	}();
	return nextResolve(specifier, context)
};

A cache provider then only needs to do const cacheKey = import.meta.resolve("loader:cache-key") (with try/catch) to build a cache key for the active loader chain.
How do we know all the source dependencies for the previous loader and resolvers?
A load hook can use information from multiple sources to generate a single underlying module source text blob. For example a TypeScript loader would use the settings in tsconfig.json to determine whether or not it should omit type-only imports. This has a material impact on the resulting source payload.
Resolve hooks run into the same issue. package.json, and the absence of package.json in traversed directories, affects the way a specifier is resolved to a module URL.
The ad-hoc solution is to pass forward arbitrary information in the result object but this isn't something that is officially documented and seems subject to the whims of the implementation:
export const load: NodeLoad = async (urlString, context, nextLoad) => {
	const previous = nextLoad(urlString, context);
	const tsconfigURL = new URL("tsconfig.json", urlString);
	const tsconfig = JSON.parse(await fs.readFile(tsconfigURL, "utf8"));
	const result = await transform(previous.source, {
		tsconfigRaw: tsconfig,
	});

	return {
		...previous,
		sourceURLs: [ ...previous.sourceURLs ?? [], tsconfigURL ],
		source: result.code,
	};
};

This would inform a cache provider about which files it needs to stat before returning a cached response. It also would have benefits to other loaders, for example, it would tell dynohot which files it needs to watch for updates.
What is a cache provider?
This led to my final question about whose job it is to cache? No loader should make any presumptions about its position in the loader chain. Multiple loaders implementing different forms of caching would lead to inconsistent caching, less than optimal performance, and duplicated code. Therefore I think terminating your loading chain with a caching loader makes the most sense.
The most simple caching loader would take in the result of nextLoad and save a persistent cache entry for the given moduleURL, sourceURLs, and active chain cache-key. It would be up to the user, and not the earlier loaders, whether or not and how they want to cache.
Another example of a caching loader would be one which JIIT-bundles arbitrary packages under node_modules. I think it's absolutely deranged that packages in the npm ecosystem distribute minified single-file build artifacts from rollup. But of course there's very real benefits to loading and parsing, so I understand why they do this. If this was implemented as a loader it would encourage package authors to distribute plain source files and let the user decide how to manage caching for their project.
Do we standardize this?
I proposed 2 ad-hoc solutions here: loader:cache-key resolution specifier, and sourceURLs array on the result of resolve and load. By asking loaders to provide this information we unlock the possibility of caching / watching loaders. Is this something we want to encourage? I think the cache key solution would be better represented as an export on the loader, but this isn't possible without support in the host environment. sourceURLs I think is pretty close to ideal and is only missing an implementation from the default loaders.

I wanted to add a file cache to avoid the transformation in the common case where most source files are unchanged since the last invocation.

Here's how I would do it:
import { createReadStream } from 'node:fs';
import { createHash } from 'node:crypto';

export async function resolve(specifier, context, next) {
  const result = await next(specifier, context);
  const url = new URL(result.url);
  if (url.protocol !== 'file:') return result; // for e.g. data: URLs
  const hashChunks = createReadStream(url).pipe(createHash('sha256')).toArray();
  url.search.set(
    import.meta.url, // An almost certainly unique key
    Buffer.concat(hashChunks).toString('base64url')
  );
  return { ...result, url };
}

By adding the hash to the resolved URL, you are guaranteed per spec that it won't be load more than once, you don't need to implement your own cache.
What is the purpose of your custom loader: scheme? I'm not sure I see why you would need a special scheme.

This led to my final question about whose job it is to cache?

According to the current ES spec, there can be only one module per URL. IIRC it's also a limitation of V8, trying to load more than one module on the same URL would lead to undefined behavior. For this reason, Node.js has an internal module cache which loaders cannot access but can rely upon.
With the addition of import attributes, this is slightly more complicated (the module cache is now Map<SerializedKey, ModuleNamespace> with SerializedKey is a serialization of the URL string with the import attributes), but the principle still holds.
So loaders are of course free to add an additional cache layer if they see fit, but I'd expect that wouldn't be necessary for most use cases.

I'm sorry but none of this is true.

current ES spec, there can be only one module per URL

The resolution process is not specified by es262 at all.

ecma262 defines a [[LoadedModules]] structure that maps a [[Specifier]] to a [[Module]]. It turns out in Node.js we use the absolute URL returned by the resolve hook as [[Specifier]], not sure if that's required in this spec or if it's taken from another spec.

HostLoadImportedModule is host-defined and can be anything.

Sure but it must be stable: "If this operation is called multiple times with the same (referrer, specifier) pair […] then it must perform FinishLoadingImportedModule(referrer, specifier, payload, result) with the same result each time."  But we're getting off topic, a loader doesn't have to comply with the ES spec anyway.

I am talking about a persistent file cache for caching the results of transformations between different runs of nodejs, not an in-memory cache for caching instances of modules within a single process

I completely missed that, sorry for the confusion.

ecma262 doesn't have any requirements on the specifier except that it's a string; HTML is what requires they be URLs. node is free to make whatever choice it wants here, since it's not a web browser.

I proposed 2 ad-hoc solutions here: loader:cache-key resolution specifier, and sourceURLs array on the result of resolve and load.

Could we create a cache based on the resolved URL and a hash (like a shasum) of the source returned by nextLoad? Then maybe the cache wouldn't need to know anything about the other hooks in the chain? It would be the same problem as designing a cache for loading files from disk, where the resolved URL is like the filename and nextLoad is like readFile.

Could we create a cache based on the resolved URL and a hash (like a shasum) of the source returned by nextLoad?

Ideally you wouldn't need to call nextLoad at all if you don't want to.
Imagine a generalized Babel loader that transforms your source based on the contents of babelrc. You invoke nodejs with something like: node --loader babel --loader transform-cache exotic-script.xyz.
Invocation 1 (fresh):

transform-cache looks for a cache entry for exotic-script.xyz, finds nothing
transform-cache invokes nextLoad

babel invokes nextLoad

default load invokes fs.readFile

babel runs transform, returns result

transform-cache saves a cache entry to .cache or wherever. The cache entry includes the source file's mtime, size, and transformed text
Script executes, nodejs exits

Invocation 2 (afterward):

transform-cache looks for a cache entry for exotic-script.xyz, finds previous entry
transform-cache stats the underlying moduleURL and compares mtime, and size. Finds that they are the same, so it returns the previously transformed source text
Script executes, nodejs exits

What I'm suggesting is a cache scheme which allows us to elide the invocation to nextLoad entirely. With the scheme you suggested you will need to read the original source text in addition to the cached source text, each time.

Ideally you wouldn't need to call nextLoad at all if you don't want to.

That's fine. I guess what this illuminates though is that there can be varying goals for creating a cache: avoiding file reads (the goal you cited) or avoiding processing. Like for example if your loader is the one that does the transpilation, you could use the approach I suggested to load transpiled output from cache rather than doing the transpilation work again.

Yeah I didn't mean to say that either case is more valid than the other. Studying both is great.
Thinking about good "best practices" for caching would really benefit the ecosystem. Right now my intuition is that caching should live in dedicated loader. If each loader implements their own caching mechanism then you might actually run into very poor performance on first load, because cache misses aren't free.


mysql instructions?

in branch v4.1.4, using node 6.14.5 or 8.11.14, atempt to run node . fails with:
 node .
Config from /home/matt/src/jsbin-git/lib/config.local.json
/home/matt/src/jsbin-git/lib/store.js:5
    throw new Error(`${options.adapter} is not supported, only mysql as of v4.`);
    ^

Error: sqlite is not supported, only mysql as of v4.
    at new Store (/home/matt/src/jsbin-git/lib/store.js:5:11)
    at createStore (/home/matt/src/jsbin-git/lib/store.js:93:10)
    at Object.<anonymous> (/home/matt/src/jsbin-git/lib/app.js:16:37)
    at Module._compile (module.js:577:32)
    at Object.Module._extensions..js (module.js:586:10)
    at Module.load (module.js:494:32)
    at tryModuleLoad (module.js:453:12)
    at Function.Module._load (module.js:445:3)
    at Module.runMain (module.js:611:10)
    at run (bootstrap_node.js:387:7)

Are there instructions for using mysql somewhere? thanks!

closing, I see i have to change config.local.json to mysql.


Pin worker to a release and add renovate regex template

This will allow Renovate to bump the worker block reference to point to the latest GitHub tag.
Change-type: patch
Signed-off-by: Kyle Harding<EMAIL_ADDRESS>

@balena-ci I self-certify!


Six apps manifests need to be re-published

Background:
There are five app manifests on staging (and possibly production) that aren't published via yarn publish-manifests.  These are:

[ ] Akaunting
[ ] MediaWiki
[ ] Mibew
[ ] vTiger CRM
[ ] Wallabag
[ ] Zimbra

The reason for the republish is so that they get their "cost" flag set to free, paid, or both, depending on how their editions have prices. Re-publishing will set them accordingly. Probably, they are all 'free', so their records could be edited directly to add a "cost": "free" to their records.
Example from Echo Server:
{
    "_id" : "01ERDKZ8DS3197DG2JRF61NVWZ",
    "name" : "Echo Server",
    "package" : "@provisioner/appengine",
    "description" : "Ever want to meet an server that is a good listener? Look no further, connect with your inner narcissist and buy echo server today!",
    "summary" : "Echo server just replies back what you sent it.",
    "category" : "dev-tools",
    "keywords" : [
        "Developer",
        "Tools"
    ],
    "repo" : "https://github.com/robblovell/echo-server",
    "license" : "https://www.apache.org/licenses/LICENSE-2.0.html",
    "support" : "https://github.com/robblovell/echo-server/issues",
    "provisioner" : {
        "repo" : "https://github.com/robblovell/echo-server",
        "support" : "https://github.com/robblovell/echo-server/issues"
    },
    "namespace" : "echoserver",
    "cost" : "both",
    "updatedOn" : ISODate("2020-12-23T05:51:25.362Z")
}

All of these were deprecated / removed out of source.  Typically they had unmet dependencies which we could satisfy in the short term.


scib doesn't install with python 3.8 anymore

Due to the github actions PR and the changed dependenices, scIB does not install with Python 3.8 anymore.
scGen requires tensorflow 1.15 which is not available for python 3.8.
Do we need to have the integration tools as required dependencies?
Or would it be possible to have those as optional dependencies?

Please move to optional. We should definitely not have these as required. This might entail moving import statements into functions in integration.py though.


Feature/ted 604

Codecov Report
Base: 98.70% // Head: 98.77% // Increases project coverage by +0.07% :tada:

Coverage data is based on head (bac1a15) compared to base (acd8e43).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #271      +/-   ##
==========================================
+ Coverage   98.70%   98.77%   +0.07%
==========================================
  Files         113      113
  Lines        5164     5306     +142
==========================================
+ Hits         5097     5241     +144
+ Misses         67       65       -2

Impacted Files
Coverage Δ

ted_sws/core/adapters/cmd_runner.py
100.00% <100.00%> (ø)

ted_sws/core/model/manifestation.py
100.00% <100.00%> (ø)

...sws/event_manager/adapters/event_handler_config.py
100.00% <100.00%> (ø)

ted_sws/event_manager/services/log.py
100.00% <100.00%> (ø)

..._sws/event_manager/services/logger_from_context.py
100.00% <100.00%> (ø)

ted_sws/mapping_suite_processor/__init__.py
100.00% <100.00%> (ø)

...cessor/adapters/mapping_suite_structure_checker.py
100.00% <100.00%> (ø)

...sor/entrypoints/cli/cmd_mapping_suite_processor.py
100.00% <100.00%> (ø)

...sor/entrypoints/cli/cmd_mapping_suite_validator.py
100.00% <100.00%> (ø)

...rocessor/entrypoints/cli/cmd_resources_injector.py
100.00% <100.00%> (ø)

... and 11 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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


Get or make sprites for the ants

This would also involve making the ants face the correct direction along their motion.

I'm pretty sure that Dylan did this.


Add test for incorrect max_past_epochs value

We noticed that there was an issue with the max_past_epochs flag being respected in the MlsGroupCreateConfig. Members of the group joining from a Welcome would see the specified value, but the group creator would always have a max_past_epochs set to 0.
This is because when the MlsGroupBuilder::build method is run, it uses the max_past_epochs flag from the builder instead of the MlsGroupCreateConfig
This is how we fixed it in our fork, but you may want to handle differently. Is the max_past_epochs flag on the MlsGroupBuilder even necessary with the group create config. From my cursory look, it seems to be always None.

Merged in #1664


Don't intermingle targets between packages

When loading targets to compile, be sure to use the targets from the package
that's being passed down to the compilation step, not the one that was passed in
which is overridden.
Closes #1404

r? @wycats
(rust_highfive has picked a reviewer for you, use r? to override)

@bors: r=wycats

 @bors r=wycats 350bd8d

:hourglass: Testing commit 350bd8d with merge 6cb51cc...

:sunny: Test successful - cargo-linux-32, cargo-linux-64, cargo-mac-32, cargo-mac-64, cargo-win-32, cargo-win-64


Warn when derating is present when calling write_timing_model

Describe the bug
The SDC used in Openlane contains various derating parameters:
https://github.com/The-OpenROAD-Project/OpenLane/blob/master/scripts/base.sdc
This SDC is used to create liberty timing models, which means we apply derating to both the timing model and the top level integration.
Expected Behavior
Print a warning so the user is aware that the timing model has been derated.
Environment
Git commit: e41b1dcc4510b1a7dda30f4c7db7de4e60050579
os: Fedora Linux 36 (Workstation Edition)
cmake version 3.25.1
gcc (GCC) 12.2.1 20221121 (Red Hat 12.2.1-4)
clang version 14.0.5 (Fedora 14.0.5-2.fc36)

To Reproduce
N/A
Relevant log output
No response
Screenshots
No response
Additional Context
No response

Openlane also adds external capacitance to outputs via the set_load command. This has an impact on the liberty model. The output tables are indexed by capacitance, so it seems adding a capacitance on top of that is bad.
Should this be a warning too?

I think it is really wrong that openlane writes liberty models by default in the flow and has no mechanism to override all of the sdc that it adds to a design.


Bump @itwin/object-storage pkgs to address GHSA-jchw-25xp-jwwc

Addresses Vulnerability: https://github.com/advisories/GHSA-jchw-25xp-jwwc

@mergifyio backport release/4.3.x


[tools revamp] add date options for scatter

allow setting date options in the url for scatter stat vars
update subject page proto so that stat var spec takes a date

thanks for the review!


Added --data-raw support

Raw data support

Hi @mkp95 - happy new year and thanks for the pull request!
Can you please narrow the changes to just the support for --data-raw - I'm uncomfortable with disabling HTTPS verification as a default. See #5 for more discussion on that.

Hi @mkp95 - happy new year and thanks for the pull request!
Can you please narrow the changes to just the support for --data-raw - I'm uncomfortable with disabling HTTPS verification as a default. See #5 for more discussion on that.

@mkp95
@incarnate said correct, please remove detect https from your code. I need just data-row support for now.
It's been about 3 months; Can you do that or think of something else?

@mkp95
@incarnate said correct, please remove detect https from your code. I need just data-row support for now.
It's been about 3 months; Can you do that or think of something else?

I think I have to edit the whole file again will do it by 1st April..

now you can approve the pull request .. i removed all alterations and added data raw support only


How to train PN network to use different ways in training and testing

I try to modify the dataset and basemodel in their init function.
But it's a pity that I can't use these hyperparameters like val_ways train_ways.
How to modify the code to implement this function? I haven't used Lighting torch before.

Since the training and testing are separated, a simple method is to use any number of ways in the config file for training, and then use another number of ways in the config file for testing. Any further questions are welcome.

This method is indeed feasible, but if the number of classes used in training exceeds the number of classes in all val, an error will be reported.
For example, in a MiniImagenet dataset, an error will be reported if ways=20 is set.

Hi, I have changed all the code to make it possible to separate ways in train, val and test. Now please find three different hyperparameters train_way, val_way and test_way in the config file (I mainly modified base_module.py and few_shot_datamodule.py). Please see if this meets your requirement.

Closed after one month of inactivity.


Sensitive information when APP_DEBUG is false

Even if APP_DEBUG is false, exceptions or errors with file and line numbers appear.
It should display a generic error message instead when not in debug mode.
Also, would like to see the callstack, but it's ok since I can see it in the /storage/logs.

i have same Problem! any idea?


Godot Language Server throws nonexistent errors on Line:1 Col:1 saying Error(test)

Godot version
4.1.3.stable.official [f06b6836a]
System information
Godot v4.1.3.stable - Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce MX110 (NVIDIA; <IP_ADDRESS>92) - Intel(R) Core(TM) i5-8265U CPU @ 1.60GHz (8 Threads)
Issue description
Godot's Language Server is not behaving like I'd expect it to. It keeps throwing errors that read "Error (test)" on top of the file (@ line1:col1, the extends NODETYPE part) but my code works just fine when I run the project. It's also inconsistent since it doesn't throw the same error on my Player.gd file. I do not understand what is happening and I don't think it's related to my code, since this happens in every project I have in my folders, including premade games, etc. I have dropped images of the errors below. If you need any other resources such as screenshots or code I can drop them too.
I should also note that I am having the same issue on Godot v4.1.2.stable.mono.official [399c9dc39] too.
Mainscene.gd:

Boulder.gd:

Player.gd:

Steps to reproduce
Just create a new project in Godot 4.1.3 and make a basic 2D project that involves RigidBody2D's and CharacterBody2D's. Attach scripts to them and open the scripts in VSCode with the Godot VSCode extension. I suppose you will see the same effect.
Minimal reproduction project
N/A

Well, I kinda fixed it I guess, let me tell.
There was a warning in the script saying the delta parameter in _physics_process was never used and advised me to prefix it with an underscore like _delta. No big deal, right? And I put the underscore in there to make the warning go away, and it just worked. I achieved the same effect by using the delta variable basically anywhere, it doesn't matter.

Same issue for me.
It seems that the errors could appear when some glint issues are present in the file.
Fixing the warnings can remove the errors.
Just a remark:
This error is very annoying when coding using VSCode.
That's due to Gdlint issues that may not be reported when using glint on the terminal or with an add on in Godot Editor.
It could be caused by the presence of a .gdlinrc file at the root of the project.
I'm not sure that this file is used by default when coding in VScode .
So the issues reported by the linter could be not be the same between Godot / GdLint and Vscode


Change Snyk Actions

Feature or Bugfix

Detail

Change GitHub Action step from using snyk/actions/python-3.9@master to snyk/actions/setup@master

snyk/actions/setup@master will just install Snyk CLI and we add step to explicitly call snyk test ... with our arguments
Changed because snyk/actions/python-3.9@master was setting up some virtual env and not finding the installed dependencies from make install (leading to Snyk skipping over the checks on requirements.txt)

Alternatives Explored

Specifying package-manager to pip rather than poetry (Poetry shell was being created that did not carry over installed deps from before using snyk/actions/python-3.9@master)

But not supported with all-projects flag

Adding configuration to pyproject.toml to prevent venv creation (could not find a working solution)
Using venvs and exporting PATH env variable to be used later by Snyk action step (could not find a working solution)

Relates

https://github.com/data-dot-all/dataall/pull/1708

Security
Please answer the questions below briefly where applicable, or write N/A. Based on
OWASP 10.

Does this PR introduce or modify any input fields or queries - this includes
fetching data from storage outside the application (e.g. a database, an S3 bucket)?

Is the input sanitized?
What precautions are you taking before deserializing the data you consume?
Is injection prevented by parametrizing queries?
Have you ensured no eval or similar functions are used?

Does this PR introduce any functionality or component that requires authorization?

How have you ensured it respects the existing AuthN/AuthZ mechanisms?
Are you logging failed auth attempts?

Are you using or adding any cryptographic features?

Do you use a standard proven implementations?
Are the used keys controlled by the customer? Where are they stored?

Are you introducing any new policies/roles/users?

Have you used the least-privilege principle? How?

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Tested in a forked repo the same GitHub Action - Snyk workflow successful with output: Tested 8 projects, no vulnerable paths were found. (link to GH forked repo run)

@petrkalos @dlpzx @SofiaSazonova - take a look when you have some time
Github Action's of Snyk running into some issues not reproducible locally but this PR changes to resolve and ultimately close the loop on Snyk setup


Run integration tests by re-using the CI build results

This changeset attempts to re-use the CI build result of Build under Ubuntu when running the integration-tests workflow.
It appends the Ubuntu-based CI build with a step uploading the whole working folder of the repository as a workflow artifact. The subsequent integration-tests workflow downloads it and unpacks.
Note: to download the artifact conveniently, a custom action is used.
Restrictions:

The dependant workflow is only executed according to the .yml file which resides in the default branch (master) in our case. So any modifications made to integration-tests.yml in scope of PRs have no value until they are merged.

According to the docs, the tests should also be executed from the default (master) branch. However, as this PR has not been merged yet, I am not able to verify it.

@alexander-yevsyukov FYI.


How do you capture the RAW data?

Would you be able to write a small list of steps required to actually capture the data sent from the Little Printer bridge? I'm trying to establish whether it's possible to actually do away with the bridge and send data directly to the LP. That would make it a lot more useful!

@flyte I know it's been 8 years ;) but wondering if you're still using your Little Printer and every got it to work without the bridge.
I've snooped some of the data (.logicdata file is over at https://discord.com/channels/709148447927697410/751522892184944652/793465458161352755) but haven't been able to make much sense if it yet. Maybe I should just get some USB zigbee module and try to replay it.


Tweaks to the FluentValidation solution

Hi
This pull request contains two commits.

Define official NuGet package source in NuGet.config, instead of falling back to what's configured in Visual Studio.
Make use of EditorConfig to define indentation rules. EditorConfig are used in many other OSS projects, including CoreCLR.

Andreas

Looks good, thanks!


Fix possible memory leaks in cups-browsed daemon

Hi Till,
I found several other possible memory leaks in cupsAddOption() calls - using strdup as parameter of cupsAddOption() results in losing the allocated pointer, because cupsAddOption() allocates the memory by itself and since the pointer allocated by strdup is not saved anywhere, it leaks.
Plus I assigned NULL into response pointer too, because it is in the loop and the garbage after freeing can confuse the conditional when getting new response fails.
I tested it in Fedora rawhide and I was able to see remote print queues and print to one of them.
Would you mind adding the fix into the project?
Thank you in advance,
Zdenek

Merged. Thank you very much for your contribution.


typo: Double word "get"

@nschonni : Thanks for your contribution! The author, @darrelmiller, has been notified to review your proposed change.

Verified the update.


Is it possible to get running on M1 MacBooks?

Unfortunately MuJoCo doesn't currently provide an ARM binary. You could try and ask Roboti for this. (dm_control itself is pure Python so it should work on any platform.)

Roboti is the weak point of the research in reinforcement learning.

Looks like these guys have it working? https://github.com/openai/gym/issues/2114

This is another related thread: https://www.reddit.com/r/reinforcementlearning/comments/kd6j0o/installing_openai_gym_on_an_m1_macbook/