CI: Disable the failed macOS Builds

Summary
This PR disables the failed macOS Builds from CI Checks sim-02 and sim-03, so that the macOS CI Checks will complete successfully in the NuttX Mirror Repo:

sim:libcxxtest: macOS doesn't support cxxabi.h

sim:lua: macOS doesn't support pipe2()

sim:note: macOS doesn't support ld --wrap

sim:quickjs: macOS fails to patch quickjs-libc.c

sim:rpproxy_virtio: macOS fails at uintmax_t unsigned long long vs unsigned long

sim:rpserver_virtio: macOS fails at uintmax_t unsigned long long vs unsigned long

Impact
With this PR, macOS CI Checks will complete successfully in the NuttX Mirror Repo.
Testing
The macOS CI Checks completed successfully in our Test Repo:
https://github.com/lupyuen5/label-nuttx/actions/runs/11828738112

[Experimental Bot, please feedback here]
Yes, this PR appears to meet the NuttX requirements, though some sections could be more explicitly filled out.  Here's a breakdown:
Strengths:

Clear Summary: The summary explains the "why" (failed macOS builds), "what" (disabling specific tests), and "how" (by excluding them from the CI).
Impact is Addressed:  The impact on the user, build process, hardware, documentation, security, and compatibility is adequately addressed, albeit briefly. The main impact is a positive one: fixing the broken CI.
Testing Provided:  A link to a successful test run is provided, which demonstrates the effectiveness of the change.

Areas for Improvement (While Minor, Worth Considering):

Explicitly State "No Impact" Where Applicable:  Instead of just implying no impact, explicitly state "NO" for each impact category where there's no change.  For example:  "Impact on user: NO".  This improves readability and clarity.
More Detailed Testing Logs (If Feasible): While the link to the successful run is good, including snippets of relevant log output directly in the PR would further strengthen it.  Show a "before" (failing builds) and "after" (successful builds) example, even if brief.
Mention Specific CI Config Files Changed: If possible, mention the specific CI configuration files that were modified to disable the tests. This adds transparency.
Consider Upstream Solutions (Long-Term): While disabling the tests is a practical short-term fix, mention (if applicable) whether upstream fixes for these macOS issues are being explored.  This shows that the disabled tests are not intended to be a permanent solution.

Despite the minor suggestions, the PR provides sufficient information to understand the change, its impact, and the verification process.  It generally meets the requirements.


Provide a way to override global env properties in a test ConnectionProviderBuilder

Hey 😃
We are using this ConnectionProviderBuilder in Search tests and in those cases, we usually have database settings coming from a Junit extension, which may be too late as Environment.getProperties() are already initialized. These changes would allow us to pass the settings from an extension into this builder.
Let me know if it makes sense to apply this, or if maybe you have other suggestions on how we can address the problem at hand 😃.

hi @beikov  😃 (since GH suggests I ping you for the review 😃 🙈)
I was looking to see whether there was anything pending for Search as Steve was asking about 6.5 release, and I noticed this old PR.
There's no urgency about this one; it would just be nice to get it in at some point so that we can remove the workaround in Search. Thanks!


about rnn tutorial

I can't figure out the role of prepare network. It seems the prepare network copies the last hidden status and cell status to the input of the LSTM after every sample is trained. But the next training sample is not what following the previous sequence in the text, so can't make use of the hidden and cell status. Is its purpose just to make the initial hidden and cell status random? Could I replace the prepare network with a random tensor filler?

Hi @breadbread1984,
This could be a bug in my code. I should take a closer look.
Do you see the same thing happen in the original Caffe2 tutorial in char_rnn.py?

I am afraid that I am really not good at understanding Python code. That's why I am stick to your C++ model helper. :-P


how to shut down a service?

Thank you.
It works very well.
But I still have a few questions.
The first is， how to shut down a service?
The second is ，how to enable the second service when the first service is running？

you can run service  in docker  ，and  run two docker

@yhfwww you can shutdown the service by killing the process? Use ctrl-c to send the int signal or docker stop the container.


Chevereto API

Hey @DeadNews
I noticed that this project supports ImgBB API. Did you know that imgbb is based on Chevereto? If you support Chevereto there will be a lot of potential users for this repo.
To support the Chevereto API is easy as change the URL (enable the user to provide the URL). Everything else is already made, the API is compatible.
Here, check the docs: https://v4-docs.chevereto.com/developer/api/api-v1.html

How many working instances are there with an open api, is there a list? I only found one:

def imgsco_upload(img: bytes) -> str:
    key = "fhadliajlfaddfFdadfidjfladfIfjlakd"

    response = post(
        url="https://imgs.co/api/1/upload",
        data={"key": key},
        files={"source": img},
    )
    if not response.ok:
        raise UploadError(response.json())

    return response.json()["image"]["url"]

If you can't get the link when image loaded correctly == the api doesn't work.

{'status_code': 400, 'error': {'message': 'Duplicated upload', 'code': 101}, 'status_txt': 'Bad Request'}

In this case the existing link should be displayed. For example:
https://github.com/DeadNews/images-upload-cli/blob/b57dae3190fddedbdc85b160ee6cd69065950036/src/images_upload_cli/upload.py#L229-L233

None. Is up to each instance if the API is public or not. We don't keep a registry.

Duplicated upload is triggered by IP + time basis. In any case, for us duplicated content doesn't mean duplicated tenency. We won't return existing files as we consider each upload unique.

I won't add hosts that don't return links.

Filo, metete tu wea en la raja


Backup failure: Download shard n failed copy backup to file

Steps to reproduce:
Execute a backup command like this:
influxd backup -database mydb -portable -since 2018-01-01T00:00:00Z backup_$(date +%Y%m%d_%H%M%S)
Expected behavior:
Get a backup written to files.
Actual behavior:
Fails to generate a backup. Console output is as follows.
2020/02/05 14:40:47 backing up db=mydb
2020/02/05 14:40:47 backing up db=mydb rp=my_rp shard=122 to backup_20200205_144047/mydb.my_rp.00122.00 since 2018-01-01T00:00:00Z
2020/02/05 14:40:47 Download shard 122 failed copy backup to file: err=<nil>, n=0.  Waiting 2s and retrying (0)...
2020/02/05 14:40:49 Download shard 122 failed copy backup to file: err=<nil>, n=0.  Waiting 2s and retrying (1)...
2020/02/05 14:40:52 Download shard 122 failed copy backup to file: err=<nil>, n=0.  Waiting 2s and retrying (2)...
2020/02/05 14:40:54 Download shard 122 failed copy backup to file: err=<nil>, n=0.  Waiting 2s and retrying (3)...
2020/02/05 14:40:56 Download shard 122 failed copy backup to file: err=<nil>, n=0.  Waiting 2s and retrying (4)...
2020/02/05 14:40:58 Download shard 122 failed copy backup to file: err=<nil>, n=0.  Waiting 2s and retrying (5)...
2020/02/05 14:41:01 Download shard 122 failed copy backup to file: err=<nil>, n=0.  Waiting 3.01s and retrying (6)...
2020/02/05 14:41:04 Download shard 122 failed copy backup to file: err=<nil>, n=0.  Waiting 11.441s and retrying (7)...
2020/02/05 14:41:15 Download shard 122 failed copy backup to file: err=<nil>, n=0.  Waiting 43.477s and retrying (8)...
2020/02/05 14:41:59 Download shard 122 failed copy backup to file: err=<nil>, n=0.  Waiting 2m45.216s and retrying (9)...
2020/02/05 14:44:44 error (copy backup to file: err=<nil>, n=0) when backing up db: mydb, rp my_rp, shard 122. continuing backup on remaining shards
2020/02/05 14:44:44 backup failed: copy backup to file: err=<nil>, n=0
backup: copy backup to file: err=<nil>, n=0

Only once have I gotten a backup, and that was when the database was newly-created.

The directory that contains the shard noted in the output above contained hundreds of empty temp directories. Deleting those directories didn't change anything with the backup failure.
Of the 132 shards, one has 8 tsm files, the problem shard has one tsm file and the others have one tsm file.
Running influx_inspect commands verify and inspect show no issues.

Environment info:

System info: Linux 4.15.0-1066-azure x86_64
InfluxDB version: InfluxDB v1.7.0 (git: 1.7 dac4c6f571662c63dc0d73346787b8c7f113222a)
Other relevant environment details:
Influx instance is running on a pod in a AKS cluster. Database files are on a mounted Azure File share.

Config:
Non-default configs are
reporting-disabled = true
bind-address = "<IP_ADDRESS>:8088"
auth-enabled = true

@gholmes thanks for opening this. Have you tried with the latest 1.7.9 influxdb? Also, where are you running the backup command? is it from inside your k8s cluster or remote?

Yes, I tried with 1.7.9 and got the same results. I ran the backup command locally, from another container in the cluster, and from a host outside the k8s cluster. I did learn that part of the problem is that I was mounting Azure file shares, which don't support hard links. Failures creating hard links leave the temp directories to accumulate, which seems to be at least part of the issue with backing up. I have since switched to mounting Azure Disk and I'm now able to run a backup and the temp directories don't accumulate. I think the problem that needs to be addressed is that the temp directories aren't cleaned up after the failure to create a hard link. I'm also wondering why the hard links are created at all.

@gholmes

Hello
did you solve this problem. I have the same problem
Thank you

Hi, same here with the problem (influx v1.7.9) with azure, any news about it?
Command
influxd backup -portable -database 'myDB' 'myDB_bkp'
2020/04/27 16:52:04 backing up metastore to myDB_bkp/meta.00
2020/04/27 16:52:05 backing up db=myDB
2020/04/27 16:52:06 backing up db=myDB rp=autogen shard=681 to myDB_bkp/myDB.autogen.00681.00 since 0001-01-01T00:00:00Z
2020/04/27 16:52:07 Download shard 681 failed copy backup to file: err=<nil>, n=0.  Waiting 2s and retrying (0)...
2020/04/27 16:52:11 Download shard 681 failed copy backup to file: err=<nil>, n=0.  Waiting 2s and retrying (1)...

Log
ts=2020-04-27T20:52:13.824530Z lvl=info msg="error creating tsm hard link: \"link /var/lib/influxdb/data/myDB/autogen/681/000000023-000000002.tsm /var/lib/influxdb/data/myDB/autogen/681/14.tmp/000000023-000000002.tsm: operation not supported\"" log_id=0MRIgTX0000 service=snapshot

Thanks!

Hey,
you should add "bind-address =": 8088 "" in the influxdb.conf on the two
Influxdb hosts
then it should work
if not contact me 😉
Am Mo., 27. Apr. 2020 um 22:56 Uhr schrieb palbornozl <
<EMAIL_ADDRESS>
Hi, same here with the problem (influx v1.7.9) with azure, any news about
it?
Command
influxd backup -portable -database 'myDB' 'myDB_bkp'
2020/04/27 16:52:04 backing up metastore to myDB_bkp/meta.00
2020/04/27 16:52:05 backing up db=myDB
2020/04/27 16:52:06 backing up db=myDB rp=autogen shard=681 to myDB_bkp/myDB.autogen.00681.00 since 0001-01-01T00:00:00Z
2020/04/27 16:52:07 Download shard 681 failed copy backup to file: err=, n=0.  Waiting 2s and retrying (0)...
2020/04/27 16:52:11 Download shard 681 failed copy backup to file: err=, n=0.  Waiting 2s and retrying (1)...
Log
ts=2020-04-27T20:52:13.824530Z lvl=info msg="error creating tsm hard link: "link /var/lib/influxdb/data/myDB/autogen/681/000000023-000000002.tsm /var/lib/influxdb/data/myDB/autogen/681/14.tmp/000000023-000000002.tsm: operation not supported"" log_id=0MRIgTX0000 service=snapshot
Thanks!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/influxdata/influxdb/issues/16739#issuecomment-620229856,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOYZBVJWA675JAYSR7NEVGTROXWRPANCNFSM4KQQKCYQ
.

Thanks @ronaldoo9 to reply, but is it necessary to add "bind-address =": 8088 " if by default has set 8088?
So, where do I need to add it? HTTP section o a new section?
Thanks!

you need add it a new section !  just like on picture
Am Di., 5. Mai 2020 um 15:28 Uhr schrieb Patricia Albornoz L <
<EMAIL_ADDRESS>
Thanks @ronaldoo9 https://github.com/ronaldoo9 to reply, but is it
necessary to add "bind-address =": 8088 " if by default has set 8088?
So, where do I need to add it? HTTP section o a new section?
Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/influxdata/influxdb/issues/16739#issuecomment-624055239,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOYZBVI4L2SHHR2GNNWTVQ3RQAIBHANCNFSM4KQQKCYQ
.

you should also restart the container so that it can accept the new
configuration 😉
Am Di., 5. Mai 2020 um 16:01 Uhr schrieb Rozad Khalaf<EMAIL_ADDRESS>
you need add it a new section !  just like on picture
Am Di., 5. Mai 2020 um 15:28 Uhr schrieb Patricia Albornoz L <
<EMAIL_ADDRESS>
Thanks @ronaldoo9 https://github.com/ronaldoo9 to reply, but is it
necessary to add "bind-address =": 8088 " if by default has set 8088?
So, where do I need to add it? HTTP section o a new section?
Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/influxdata/influxdb/issues/16739#issuecomment-624055239,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOYZBVI4L2SHHR2GNNWTVQ3RQAIBHANCNFSM4KQQKCYQ
.

Hello, do you have any update for this issue?
I also have the same issue.
I tried to use "bind-address =": 8088 ", but it doesn't work.
This backup command is executed from a pod on kubernetes (minikube).

version information

# influx --version
InfluxDB shell version: 1.8.0

command and result

# influxd backup -portable -database telegraf /tmp/mysnapshot
2020/06/02 06:10:12 backing up metastore to /tmp/mysnapshot/meta.00
2020/06/02 06:10:12 backing up db=telegraf
2020/06/02 06:10:12 backing up db=telegraf rp=autogen shard=2 to /tmp/mysnapshot/telegraf.autogen.00002.00 since 0001-01-01T00:00:00Z
2020/06/02 06:10:12 Download shard 2 failed copy backup to file: err=<nil>, n=0.  Waiting 2s and retrying (0)...
2020/06/02 06:10:14 Download shard 2 failed copy backup to file: err=<nil>, n=0.  Waiting 2s and retrying (1)...
2020/06/02 06:10:16 Download shard 2 failed copy backup to file: err=<nil>, n=0.  Waiting 2s and retrying (2)...
^C

Some files were created.

# ls -l /tmp/mysnapshot/
total 4
-rw-r--r-- 1 root root 212 Jun  2 06:10 20200602T061012Z.meta
-rw-r--r-- 1 root root   0 Jun  2 06:10 telegraf.autogen.00002.00.pending

InfluxDB container logs.

ts=2020-06-02T06:10:12.915378Z lvl=info msg="Cache snapshot (start)" log_id=0N8tfNjG000 engine=tsm1 trace_id=0N8vGuCl000 op_name=tsm1_cache_snapshot op_event=start
ts=2020-06-02T06:10:12.928475Z lvl=info msg="Snapshot for path written" log_id=0N8tfNjG000 engine=tsm1 trace_id=0N8vGuCl000 op_name=tsm1_cache_snapshot path=/var/lib/influxdb/data/telegraf/autogen/2 duration=13.112ms
ts=2020-06-02T06:10:12.928510Z lvl=info msg="Cache snapshot (end)" log_id=0N8tfNjG000 engine=tsm1 trace_id=0N8vGuCl000 op_name=tsm1_cache_snapshot op_event=end op_elapsed=13.146ms
ts=2020-06-02T06:10:12.930983Z lvl=info msg="error creating tsm hard link: \"link /var/lib/influxdb/data/telegraf/autogen/2/000000005-000000002.tsm /var/lib/influxdb/data/telegraf/autogen/2/14.tmp/000000005-000000002.tsm: operation not permitted\"" log_id=0N8tfNjG000 service=snapshot
ts=2020-06-02T06:10:14.932404Z lvl=info msg="Cache snapshot (start)" log_id=0N8tfNjG000 engine=tsm1 trace_id=0N8vH150000 op_name=tsm1_cache_snapshot op_event=start
ts=2020-06-02T06:10:14.935146Z lvl=info msg="Snapshot for path written" log_id=0N8tfNjG000 engine=tsm1 trace_id=0N8vH150000 op_name=tsm1_cache_snapshot path=/var/lib/influxdb/data/telegraf/autogen/2 duration=2.758ms
ts=2020-06-02T06:10:14.935172Z lvl=info msg="Cache snapshot (end)" log_id=0N8tfNjG000 engine=tsm1 trace_id=0N8vH150000 op_name=tsm1_cache_snapshot op_event=end op_elapsed=2.782ms
ts=2020-06-02T06:10:14.937766Z lvl=info msg="error creating tsm hard link: \"link /var/lib/influxdb/data/telegraf/autogen/2/000000005-000000002.tsm /var/lib/influxdb/data/telegraf/autogen/2/15.tmp/000000005-000000002.tsm: operation not permitted\"" log_id=0N8tfNjG000 service=snapshot
ts=2020-06-02T06:10:16.939496Z lvl=info msg="Cache snapshot (start)" log_id=0N8tfNjG000 engine=tsm1 trace_id=0N8vH8vl000 op_name=tsm1_cache_snapshot op_event=start
ts=2020-06-02T06:10:16.940931Z lvl=info msg="Snapshot for path written" log_id=0N8tfNjG000 engine=tsm1 trace_id=0N8vH8vl000 op_name=tsm1_cache_snapshot path=/var/lib/influxdb/data/telegraf/autogen/2 duration=1.450ms
ts=2020-06-02T06:10:16.941095Z lvl=info msg="Cache snapshot (end)" log_id=0N8tfNjG000 engine=tsm1 trace_id=0N8vH8vl000 op_name=tsm1_cache_snapshot op_event=end op_elapsed=1.612ms
ts=2020-06-02T06:10:16.942620Z lvl=info msg="error creating tsm hard link: \"link /var/lib/influxdb/data/telegraf/autogen/2/000000005-000000002.tsm /var/lib/influxdb/data/telegraf/autogen/2/16.tmp/000000005-000000002.tsm: operation not permitted\"" log_id=0N8tfNjG000 service=snapshot

Hello,
The two containers should be able to see each other or there should be a
connection between the two
like this
[image: image.png]
If you only have one POD, you still have to add this parameter
"bind-address =": 8088 "in the config file and restart the pod
[image: image.png]
Am Di., 2. Juni 2020 um 08:21 Uhr schrieb yyy-opt<EMAIL_ADDRESS>
:

Hello, do you have any update for this issue?
I also have the same issue.
I tried to use "bind-address =": 8088 ", but it doesn't work.
This backup command is executed from a pod on kubernetes (minikube).

version information

influx --version
InfluxDB shell version: 1.8.0

command and result

influxd backup -portable -database telegraf /tmp/mysnapshot
2020/06/02 06:10:12 backing up metastore to /tmp/mysnapshot/meta.00
2020/06/02 06:10:12 backing up db=telegraf
2020/06/02 06:10:12 backing up db=telegraf rp=autogen shard=2 to /tmp/mysnapshot/telegraf.autogen.00002.00 since 0001-01-01T00:00:00Z
2020/06/02 06:10:12 Download shard 2 failed copy backup to file: err=, n=0.  Waiting 2s and retrying (0)...
2020/06/02 06:10:14 Download shard 2 failed copy backup to file: err=, n=0.  Waiting 2s and retrying (1)...
2020/06/02 06:10:16 Download shard 2 failed copy backup to file: err=, n=0.  Waiting 2s and retrying (2)...
^C

Some files were created.

ls -l /tmp/mysnapshot/
total 4
-rw-r--r-- 1 root root 212 Jun  2 06:10 20200602T061012Z.meta
-rw-r--r-- 1 root root   0 Jun  2 06:10 telegraf.autogen.00002.00.pending

InfluxDB container logs.

ts=2020-06-02T06:10:12.915378Z lvl=info msg="Cache snapshot (start)" log_id=0N8tfNjG000 engine=tsm1 trace_id=0N8vGuCl000 op_name=tsm1_cache_snapshot op_event=start
ts=2020-06-02T06:10:12.928475Z lvl=info msg="Snapshot for path written" log_id=0N8tfNjG000 engine=tsm1 trace_id=0N8vGuCl000 op_name=tsm1_cache_snapshot path=/var/lib/influxdb/data/telegraf/autogen/2 duration=13.112ms
ts=2020-06-02T06:10:12.928510Z lvl=info msg="Cache snapshot (end)" log_id=0N8tfNjG000 engine=tsm1 trace_id=0N8vGuCl000 op_name=tsm1_cache_snapshot op_event=end op_elapsed=13.146ms
ts=2020-06-02T06:10:12.930983Z lvl=info msg="error creating tsm hard link: "link /var/lib/influxdb/data/telegraf/autogen/2/000000005-000000002.tsm /var/lib/influxdb/data/telegraf/autogen/2/14.tmp/000000005-000000002.tsm: operation not permitted"" log_id=0N8tfNjG000 service=snapshot
ts=2020-06-02T06:10:14.932404Z lvl=info msg="Cache snapshot (start)" log_id=0N8tfNjG000 engine=tsm1 trace_id=0N8vH150000 op_name=tsm1_cache_snapshot op_event=start
ts=2020-06-02T06:10:14.935146Z lvl=info msg="Snapshot for path written" log_id=0N8tfNjG000 engine=tsm1 trace_id=0N8vH150000 op_name=tsm1_cache_snapshot path=/var/lib/influxdb/data/telegraf/autogen/2 duration=2.758ms
ts=2020-06-02T06:10:14.935172Z lvl=info msg="Cache snapshot (end)" log_id=0N8tfNjG000 engine=tsm1 trace_id=0N8vH150000 op_name=tsm1_cache_snapshot op_event=end op_elapsed=2.782ms
ts=2020-06-02T06:10:14.937766Z lvl=info msg="error creating tsm hard link: "link /var/lib/influxdb/data/telegraf/autogen/2/000000005-000000002.tsm /var/lib/influxdb/data/telegraf/autogen/2/15.tmp/000000005-000000002.tsm: operation not permitted"" log_id=0N8tfNjG000 service=snapshot
ts=2020-06-02T06:10:16.939496Z lvl=info msg="Cache snapshot (start)" log_id=0N8tfNjG000 engine=tsm1 trace_id=0N8vH8vl000 op_name=tsm1_cache_snapshot op_event=start
ts=2020-06-02T06:10:16.940931Z lvl=info msg="Snapshot for path written" log_id=0N8tfNjG000 engine=tsm1 trace_id=0N8vH8vl000 op_name=tsm1_cache_snapshot path=/var/lib/influxdb/data/telegraf/autogen/2 duration=1.450ms
ts=2020-06-02T06:10:16.941095Z lvl=info msg="Cache snapshot (end)" log_id=0N8tfNjG000 engine=tsm1 trace_id=0N8vH8vl000 op_name=tsm1_cache_snapshot op_event=end op_elapsed=1.612ms
ts=2020-06-02T06:10:16.942620Z lvl=info msg="error creating tsm hard link: "link /var/lib/influxdb/data/telegraf/autogen/2/000000005-000000002.tsm /var/lib/influxdb/data/telegraf/autogen/2/16.tmp/000000005-000000002.tsm: operation not permitted"" log_id=0N8tfNjG000 service=snapshot
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/influxdata/influxdb/issues/16739#issuecomment-637304470,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOYZBVLIUKZCLLVR53XLH6DRUSK47ANCNFSM4KQQKCYQ
.

you need add it a new section ! just like on picture Am Di., 5. Mai 2020 um 15:28 Uhr schrieb Patricia Albornoz L <<EMAIL_ADDRESS>…
Thanks @ronaldoo9 https://github.com/ronaldoo9 to reply, but is it necessary to add "bind-address =": 8088 " if by default has set 8088? So, where do I need to add it? HTTP section o a new section? Thanks! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#16739 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOYZBVI4L2SHHR2GNNWTVQ3RQAIBHANCNFSM4KQQKCYQ .

Sorry for my delay, but which picture are you refer to?
Thanks

I refer to both ! 😀
the "bind-address =": 8088 "must always be entered to enable backup
say how many pods do you have?
And what exactly do you want to do?
Am Mi., 3. Juni 2020 um 04:24 Uhr schrieb Patricia Albornoz L <
<EMAIL_ADDRESS>
you need add it a new section ! just like on picture Am Di., 5. Mai 2020
um 15:28 Uhr schrieb Patricia Albornoz L <<EMAIL_ADDRESS>… <#m_7858053573103901810_>
Thanks @ronaldoo9 https://github.com/ronaldoo9
https://github.com/ronaldoo9 to reply, but is it necessary to add
"bind-address =": 8088 " if by default has set 8088? So, where do I need to
add it? HTTP section o a new section? Thanks! — You are receiving this
because you were mentioned. Reply to this email directly, view it on GitHub
<#16739 (comment)
https://github.com/influxdata/influxdb/issues/16739#issuecomment-624055239>,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOYZBVI4L2SHHR2GNNWTVQ3RQAIBHANCNFSM4KQQKCYQ
.
Sorry for my delay, but which picture are you refer to?
Thanks
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/influxdata/influxdb/issues/16739#issuecomment-637914229,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOYZBVO7PS4B5ZTERGFN34TRUWX6LANCNFSM4KQQKCYQ
.

I have encoutered the same issue.Does someone can help?

I backup the the influxdb database from a machine which installs v1.7.8  to a machine that install influxdb-v1.8.5.

I have this same problem on 1.8.2 influx.
Am not running under kubernetes.
Am running the backup command directly on the same host as the database.
Many shard files are successfully backed up before reaching the problem shard, so its not a port 8088/binding issue as the transfers worked up to the point it fails as in the last screenshots above.
err= isn't a helpful message, no matter what the underlying problem, the tool should be doing better to explain what the problem is (in addition to please fixing whatever the underlying problem is here, clearly its beein around since v1.7 at least).

It seems to be related to #9923: if there was no free space on the device, then InfluxDB stops saving data to disk for some metrics and will not restore even if space was freed. In that state, the backup functionality will not work until the service restart. After the restart, some data become lost, but the backup functionality starts working again. At least it was so in my case.

Stuck into the same problem.
I got this message when I looked up the log from influxdb:
2020-12-11T02:36:39.335325Z	info	error creating tsm hard link: "link /var/lib/influxdb/data/....../autogen/2/000000001-000000001.tsm /var/lib/influxdb/data/..../autogen/2/1.tmp/000000001-000000001.tsm: operation not permitted"	{"log_id": "0Q~vJQ0W000", "service": "snapshot"}
Can anyone give any suggestion as to solve the problem?Thx!

Same problem here with 1.8.2 version. The problem always appears when trying to backup the last shard even if it doesn't contain data of the period indicated by start and end.

Same problem here with 1.8.2 version. The problem always appears when trying to backup the last shard even if it doesn't contain data of the period indicated by start and end.

Agree, same problem with 1.8.2 version on Ubuntu 16.04.

Same problem here with 1.8.2 version. The problem always appears when trying to backup the last shard even if it doesn't contain data of the period indicated by start and end.

Agree, same problem with 1.8.2 version on Ubuntu 16.04.

Anyone looking into this?
Facing the same issue on version 1.8.2 on centos 1.7

#9923

I am also facing the same issue, where restarting influxdb helped out, but this behaviour is not ideal, please fix this issue.

After some checks it seems that is related to the ingestion traffic, as I wrote before. After restarting the influxdb daemon the issue persist, but after cloning the machine and starting it without external traffic I was able to do the backup.

I have got the same problem with 1.7.7 version connected to http://localhost:8086. In my case there was simply no data in the influx shard. When i started our datalogger service on Win10 and tried this command again after it started
>influxd backup -portable -database M-02263C -shard 124 D:\XChange\Influx_TestBackup_M_2263C_Shard24
all was fine. The backup did what it should do.

Summary:
https://github.com/influxdata/influxdb/issues/16739#issuecomment-620229856 - I think this is the important part.
Download shard 122 failed copy backup to file: err=<nil>, n=0.  Waiting 2s and retrying (0)... - this means there was no explicit error but we did not get any data while trying to get a snapshot of the shard to back up.
For some users the error happens when trying to create a hard link to download the snapshot from: ts=2020-04-27T20:52:13.824530Z lvl=info msg="error creating tsm hard link: \"link /var/lib/influxdb/data/myDB/autogen/681/000000023-000000002.tsm /var/lib/influxdb/data/myDB/autogen/681/14.tmp/000000023-000000002.tsm: operation not supported\"" log_id=0MRIgTX0000 service=snapshot.

I did learn that part of the problem is that I was mounting Azure file shares, which don't support hard links

That explains that part. The hardlinks are created so that the backup process on the server can download the files.
So the resolution should be that we properly return an error to the backup cli when hardlinks are not supported, instead of saying 'error=nil' .

See also https://github.com/influxdata/influxdb/issues/22446 for 2.x issue

@lesam  - we could generalize the fix for https://github.com/influxdata/influxdb/issues/16289 to support operating systems without hard links.  GOOS or compile-time equivalents won't tell us in all cases whether we need to copy or link.  Perhaps a onfiguration flag, or maybe we can have smart detection of the problem.

I like smart detection

https://github.com/influxdata/influxdb/issues/16739#issuecomment-925354005 is a great idea, thanks for agreeing to make it reality @davidby-influx !

I made a preliminary attempt. In my own version, I found that the permissions of the data directory have been changed to root

I made a preliminary attempt. In my own version, I found that the permissions of the data directory have been changed to root。 i revert the permissions。 it is running

I had a similar backup problem in v2.6.1, where after a few shards been backed up it suddenly abends with:
Error: failed to backup bucket data: failed to download snapshot of shard 21: unexpected EOF
Eyecatcher in the log suggesting backup hit a limit:
msg="internal error not returned to client" log_id=0g9AhmQG000 handler=error_logger error="write tcp xx.xx.xx.xx:8086->yy.yy.yy.yy:50886: i/o timeout"
In this case it was because backup hit the http-write-timeout limit, removing this from config.toml solved the problem.


add support for manage_home = false

add support for manage_home = false.
Description
Trying to add users without copying /etc/skel.
Issues Resolved
#403
Check List

[ ] All tests pass. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/TESTING.MD
[ ] New functionality includes testing.

Testing is not my strong suite, help?

[x] New functionality has been documented in the README if applicable
[x] All commits have been signed for the Developer Certificate of Origin. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/CONTRIBUTING.MD

Ok, did try to run the tests
Testing currently fails on freebsd.
     ∅  shell should eq "/bin/bash"

     expected: "/bin/bash"
          got: "/bin/sh"

     (compared using ==)

macosx failed cause I didn't have vmware_fusion installed, so osx wasn't tested.
opensuse failed cause the groups wasn't sorted
     ∅  groups should eq ["test_user", "testgroup", "nfsgroup"]

     expected: ["test_user", "testgroup", "nfsgroup"]
          got: ["users", "testgroup", "nfsgroup"]

     (compared using ==)

Should perhaps be a .sort somewhere so the groups are always sorted.
This is the exception output of chef exec kitchen test
>>>>>> ------Exception-------
>>>>>> Class: Kitchen::ActionFailed
>>>>>> Message: 5 actions failed.
>>>>>>     Verify failed on instance <default-freebsd-103>.  Please see .kitchen/logs/default-freebsd-103.log for more details
>>>>>>     Verify failed on instance <default-freebsd-110>.  Please see .kitchen/logs/default-freebsd-110.log for more details
>>>>>>     Failed to complete #create action: [Expected process to exit with [0], but received '1'
---- Begin output of vagrant up --no-provision --provider vmware_fusion ----
STDOUT:
STDERR: The provider 'vmware_fusion' could not be found, but was requested to
back the machine 'default'. Please use a provider that exists.
---- End output of vagrant up --no-provision --provider vmware_fusion ----
Ran vagrant up --no-provision --provider vmware_fusion returned 1] on default-macosx-1011
>>>>>>     Verify failed on instance <default-opensuse-132>.  Please see .kitchen/logs/default-opensuse-132.log for more details
>>>>>>     Verify failed on instance <default-opensuse-leap-422>.  Please see .kitchen/logs/default-opensuse-leap-422.log for more details
>>>>>> ----------------------
>>>>>> Please see .kitchen/logs/kitchen.log for more details
>>>>>> Also try running `kitchen diagnose --all` for configuration

Also ran delivery local all
Chef Delivery
Running Every Stage
Running Lint Phase
Inspecting 15 files
...............

15 files inspected, no offenses detected
Running Syntax Phase
FC003: Check whether you are running with chef server before using server-specific features: ./resources/manage.rb:36
FC003: Check whether you are running with chef server before using server-specific features: ./resources/manage.rb:174
FC005: Avoid repetition of resource declarations: ./spec/recipes/home_dir_spec.rb:48
FC011: Missing README in markdown format: spec/README.md:1
FC016: LWRP does not declare a default action: ./resources/manage.rb:1
FC031: Cookbook without metadata file: spec/metadata.rb:1
FC045: Metadata does not contain cookbook name: spec/metadata.rb:1
Running Unit Phase
/Users/raboo/.rvm/rubies/ruby-2.2.0/lib/ruby/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require': cannot load such file -- chefspec (LoadError)
	from /Users/raboo/.rvm/rubies/ruby-2.2.0/lib/ruby/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
	from /Users/raboo/repos/users/spec/spec_helper.rb:1:in `<top (required)>'
	from /Users/raboo/.rvm/rubies/ruby-2.2.0/lib/ruby/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
	from /Users/raboo/.rvm/rubies/ruby-2.2.0/lib/ruby/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
	from /Users/raboo/repos/users/spec/recipes/home_dir_spec.rb:1:in `<top (required)>'
	from /Users/raboo/.rvm/gems/ruby-2.2.0/gems/rspec-core-3.5.1/lib/rspec/core/configuration.rb:1435:in `load'
	from /Users/raboo/.rvm/gems/ruby-2.2.0/gems/rspec-core-3.5.1/lib/rspec/core/configuration.rb:1435:in `block in load_spec_files'
	from /Users/raboo/.rvm/gems/ruby-2.2.0/gems/rspec-core-3.5.1/lib/rspec/core/configuration.rb:1433:in `each'
	from /Users/raboo/.rvm/gems/ruby-2.2.0/gems/rspec-core-3.5.1/lib/rspec/core/configuration.rb:1433:in `load_spec_files'
	from /Users/raboo/.rvm/gems/ruby-2.2.0/gems/rspec-core-3.5.1/lib/rspec/core/runner.rb:100:in `setup'
	from /Users/raboo/.rvm/gems/ruby-2.2.0/gems/rspec-core-3.5.1/lib/rspec/core/runner.rb:86:in `run'
	from /Users/raboo/.rvm/gems/ruby-2.2.0/gems/rspec-core-3.5.1/lib/rspec/core/runner.rb:71:in `run'
	from /Users/raboo/.rvm/gems/ruby-2.2.0/gems/rspec-core-3.5.1/lib/rspec/core/runner.rb:45:in `invoke'
	from /Users/raboo/.rvm/gems/ruby-2.2.0/gems/rspec-core-3.5.1/exe/rspec:4:in `<top (required)>'
	from /Users/raboo/.rvm/gems/ruby-2.2.0/bin/rspec:23:in `load'
	from /Users/raboo/.rvm/gems/ruby-2.2.0/bin/rspec:23:in `<main>'
	from /Users/raboo/.rvm/gems/ruby-2.2.0/bin/ruby_executable_hooks:15:in `eval'
	from /Users/raboo/.rvm/gems/ruby-2.2.0/bin/ruby_executable_hooks:15:in `<main>'
Phase failed with exit code (1)!

I followed instructions, so I don't know why chefspec is missing.
How do I proceed from here?

closing this one as it has stalled..


chore: import repository https://github.com/cns-ubiwhere/golang-test4.git

this commit will trigger a pipeline to generate the CI/CD configuration which will create a second commit on this Pull Request before it auto merges

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign
You can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Update documentation

The documentation does not mention all the steps necessary to run the project localy. As we also need to add the migrations to the database and then run them so changing it might be helpful for faster setup of new contributers.

I will rewrite the documentation soon and try to make the installation a bit simpler. In the meantime, if you face any issues please list them here.

I'd love to see minimum and recommended hardware requirements in the documentation.

Also the docs reference a branch configured for vercel... but I'm not seeing it - is that outdated info?

Also the docs reference a branch configured for vercel... but I'm not seeing it - is that outdated info?

Yes, the deployment is done directly from the main branch now.

I'd love to see minimum and recommended hardware requirements in the documentation.

I have no idea what the "minimum" requirements should be. My dev instance takes up barely 100M or so of RAM including the SQL server. It should pretty much run on everything.


Getting warnings after updated to react-native 0.54

I updated the react native version to 0.54. After update i m getting multiple warning like below:

#1665


Define Host Path

Is it possible to define Local Host Path as VOLUMERIZE_TARGET?

Docker Volumes are pathes on the host.
If you want to access a specific path on the host you cant mount any path with the Docker volumes option -v.


Use sops --in-place encryption

This prevents the possibility of unencrypted secrets left
in our current working checkout. .gitignore prevents these
from being committed, but it's nice to not have those lying
around regardless.
Relies on https://github.com/2i2c-org/infrastructure/pull/1097 to
prevent unencrypted files from being committed.

What do you think of this, @sgibson91?

@sgibson91 I was hoping https://github.com/2i2c-org/infrastructure/pull/1097 will mean we don't have to keep unencrypted data on our local disks, even if they're encrypted in git. So --in-place will mean that the unencrypted copy is less likely to lie around, compared to using --output.
And yeah, the logic for erroring out in the deployer doesn't need enc- I think.

To be clear, I think I'm happy with any naming convention that allows us to be strict about checking secret files for encryption. My personal worry is that it'll be janky for me to rely on the pre-commit hook solely to do this.

@sgibson91 yeah, given the high stakes nature of this, I'm happy for us to have both the pre-commit hook as well as the enc- convention + gitignore in place.

I will approve a PR that adds the use of the pre-commit hook to the docs as a complementary method for ensuring secrets are encrypted

@sgibson91 https://github.com/2i2c-org/infrastructure/pull/1097 is that PR I think? It only adds the pre-commit hook, doesn't touch anything that already exists.

I meant documenting it's use in the files we were changing here. So adding a section to this page describing the hook, how to install/use it and where it's maintained https://infrastructure.2i2c.org/en/latest/topic/secrets.html


Unable to reproduce model on GPU using 'gpu_hist', but works with 'hist'

Dear everyone,
I have read all discussions on https://github.com/dmlc/xgboost/issues/5023 and the related issues, but do not seem to find a solution that works.
My problem is that my merror differs between runs, but only when running 'gpu_hist' for the tree method.
Code (including dataset):
#!/home/user/miniconda/envs/xgboost-1.0.2-cuda-10.1/bin/python
import xgboost as xgb
import numpy as np
from sklearn.datasets import fetch_covtype
from sklearn.model_selection import train_test_split
import time
import random

# Fetch dataset using sklearn
cov = fetch_covtype()
X = cov.data
y = cov.target

np.random.seed(0)
random.seed(0) # Python general seed

# Create 0.75/0.25 train/test split
X_train, X_test, y_train, y_test = train_test_split(X, y, test_size=0.25, train_size=0.75, random_state=0)

# Leave most parameters as default
param = {'objective': 'multi:softmax',
         'num_class': 8,
         'seed': 0,
        # 'single_precision_histogram': True
         }

# Convert input data from numpy to XGBoost format
dtrain = xgb.DMatrix(X_train, label=y_train)
dtest = xgb.DMatrix(X_test, label=y_test)

# Specify sufficient boosting iterations to reach a minimum
num_round = 100

# GPU Training
param['tree_method'] = 'gpu_hist'
gpu_res = {}
tmp = time.time()
xgb.train(param, dtrain, num_round, evals=[(dtest, 'test')], evals_result=gpu_res)
print("GPU Training Time: %s seconds" % (str(time.time() - tmp)))

I have set the numpy seed, the python random seed, the train test split seed and the XGBoost seed. Furthermore, I tried the single_precision_histogram.
It is reproducible using the 'hist' tree_method.
My environment:
Docker container based on Cuda 10.1, python 3.7 and the following environment:
name: xgboost-1.0.2-cuda-10.1
channels:
    - conda-forge
    - defaults
dependencies:
    - defaults::cudatoolkit=10.1
    - conda-forge::graphviz=2.40.1
    - conda-forge::python-graphviz=0.13.2
    - conda-forge::scikit-learn==0.22.1
    - pip
    - pip:
      - xgboost==1.0.2

I hope that I am not replicating an already existing issue or am overseeing something trivial.
Thank you very much!

Right now you need master branch for reproducible GPU hist.

So I need to wait for the next release or install the current master branch manually?

Yes.  See: https://github.com/dmlc/xgboost/issues/5337

All right. Thank you for your swift help.


pip installation has conflicts (conda on windows)

Describe the bug
Following the quspin website instructions to install pip produces warnings from conda terminal (see below for error messages). The installation finishes, but importing quspin functionality in e.g. jupyter immediately leads to error messages.
To Reproduce
These errors appeared following installation of the latest version of conda on a clean computer, then executing pip install quspin. Within jupyter, importing standard quspin functionality via
from quspin.operators import hamiltonian  # Hamiltonians and operators
from quspin.basis import spin_basis_1d  # Hilbert space spin basis
import numpy as np  # generic math functions

then leads to the error messages reported below.
Expected behavior
I expected quspin to install without conflicts, or to report package conflicts via pip. Unfortunately it seems that pip is confused or something deeper is going on, as pip is citing an irreconcilable conflict between package versions.
Desktop (please complete the following information):
This was installed on a windows 11 PC with no prior python installs of any kind. I used the current (Python 3.12) conda distribution to get started.
Additional context
Here I will report the exact error messages mentioned earlier in this post. First, upon grabbing quspin with pip, the following conflicts were reported in the conda terminal:

ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
pywavelets 1.5.0 requires numpy<2.0,>=1.22.4, but you have numpy 2.0.2 which is incompatible.
streamlit 1.32.0 requires numpy<2,>=1.19.3, but you have numpy 2.0.2 which is incompatible.

Next, after importing quspin functionality with the commands mentioned earlier, the following errors appeared:

ValueError Traceback (most recent call last)
Cell In[1], line 1
----> 1 from quspin.operators import hamiltonian # Hamiltonians and operators
2 from quspin.basis import spin_basis_1d # Hilbert space spin basis
3 import numpy as np
File ~\anaconda3\Lib\site-packages\quspin_init_.py:3
1 # local modules
2 import numpy, dill
----> 3 from . import operators
4 from . import basis
5 from . import tools
File ~\anaconda3\Lib\site-packages\quspin\operators_init_.py:55
1 """
2 ==========================================
3 Operators module (:mod:quspin.operators)
(...)
52
53 """
---> 55 from .quantum_operator_core import *
56 from .quantum_LinearOperator_core import *
57 from .hamiltonian_core import *
File ~\anaconda3\Lib\site-packages\quspin\operators\quantum_operator_core.py:1
----> 1 from quspin.basis import spin_basis_1d as _default_basis
2 from quspin.basis import isbasis as _isbasis
4 # from quspin.operators._oputils import _get_matvec_function, matvec as _matvec
File ~\anaconda3\Lib\site-packages\quspin\basis_init_.py:132
1 """
2 ==================================
3 Basis module (:mod:quspin.basis)
(...)
129
130 """
--> 132 from .basis_1d import *
133 from .basis_general import *
134 from .base import *
File ~\anaconda3\Lib\site-packages\quspin\basis\basis_1d_init_.py:1
----> 1 from .spin import spin_basis_1d
2 from .boson import boson_basis_1d
3 from .fermion import spinless_fermion_basis_1d, spinful_fermion_basis_1d
File ~\anaconda3\Lib\site-packages\quspin\basis\basis_1d\spin.py:1
----> 1 from quspin_extensions.basis.basis_1d._basis_1d_core import hcp_basis, hcp_ops
2 from quspin_extensions.basis.basis_1d._basis_1d_core import boson_basis, boson_ops
3 from quspin.basis.basis_1d.base_1d import basis_1d
File ~\anaconda3\Lib\site-packages\quspin_extensions\basis\basis_1d_basis_1d_core_init_.py:1
----> 1 from . import hcp_basis, hcp_ops
2 from . import boson_basis, boson_ops
3 from . import spf_basis, spf_ops
File src\quspin_extensions\basis\basis_1d_basis_1d_core\hcp_basis.pyx:18, in init quspin_extensions.basis.basis_1d._basis_1d_core.hcp_basis()
File ~\anaconda3\Lib\site-packages\scipy\special_init_.py:777
773 import warnings
775 from ._sf_error import SpecialFunctionWarning, SpecialFunctionError
--> 777 from . import _ufuncs
778 from ._ufuncs import *
780 # Replace some function definitions from _ufuncs to add Array API support
File ~\anaconda3\Lib\site-packages\scipy\special_ufuncs.pyx:1, in init scipy.special._ufuncs()
ValueError: numpy.dtype size changed, may indicate binary incompatibility. Expected 96 from C header, got 88 from PyObject

Unfortunately The c++ extensions are not compatible with numpy 1.0.0 I assume that the other packages should be working towards upgrading to numpy 2.0

Hi, just wondering if there is any guidance about how to manage this? pip installation would be super convenient but as it stands I'm not sure where these bugs are coming from so I'll probably go back to the old method of installation. That said, if you know a simple fix for the pip installation I'd be interested to try it, thanks.

It seems to be an issue with pywavelets not supporting the numpy 2.0 I would check to see if they have resolved this issue on their side


CLI support for creating a document

./outline document create documentFromCli 633e497f-8a41-482a-937e-0d00ee326963 --server [URL] --key [KEY]

See:

Currently I don't make use of any optional parameters.
This will be discussed in https://github.com/ioki-mobility/go-outline/discussions/58
The discussion affects also other CLI calls. So we can merge this (if we are fine with that) without waiting of the discussion outcome 👍

@StefMa please resolve conflicts.

@rsjethani rebased ✅


Inbound metrics missing for ingress gateway

(NOTE: This is used to report product bugs:
To report a security vulnerability, please visit https://istio.io/about/security-vulnerabilities
To ask questions about how to use Istio, please visit https://discuss.istio.io)
Bug description
Currently, ingress metrics are missing for ingress gateway (we don't have metrics with reporter=destination)
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[X] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[X] User Experience
[ ] Developer Infrastructure
[ ] Upgrade
Expected behavior
Inbound metrics present for ingress gateway
Steps to reproduce the bug
Check metrics emitted by endpoint :15090/stats/prometheus. Metrics with tag reporter=destination will be missing.
Version (include the output of istioctl version --remote and kubectl version --short and helm version --short if you used Helm)
istioctl version client version: 1.8.0 control plane version: 1.8.0 data plane version: 1.8.0
kubectl version --short Client Version: v1.18.3 Server Version: v1.18.4
helm version --short v3.4.1+gc4e7485
How was Istio installed?
Helm
Environment where the bug was observed (cloud vendor, OS, etc)
Additionally, please consider running istioctl bug-report and attach the generated cluster-state tarball to this issue.
Refer cluster state archive for more details.

Is this by design or a bug? Can we add some configuration to enable inbound metrics for ingress gateway?

Ingressgateway request metrics are reported as client metrics. Close as this works as expected. Thanks!

@bianpengyuan  is this in roadmap to add these metrics. We will require these metrics to monitor if there is some issue and compare the inbound and outbound metrics.

We will require these metrics to monitor if there is some issue and compare the inbound and outbound metrics.

What exactly do you want to monitor? All request go through ingress are tracked as outbound metrics at ingress proxy, and requests from ingress to applications are tracked as inbound metrics at application sidecar proxy.

@bianpengyuan for requests which are dropped at ingress gateway due to some reasons like cluster not present or any other reason, having inbound metrics helps. With that we could see what % of requests actually go through ingress gateway and what gets dropped at it.

Any requests that are processed by ingress will be tracked with the inbound request metrics. There is no forwarding inside the ingress gateway (i.e. an inbound listener forward to an outbound listener). There is just one listener, and one filter chain deals with any ingress requests.


[feature request] allow to choose what results (folder) to download and allow to download results from previous model run

currently all files in "results" folder get downloaded,
there is a use case from SUMMA that the model execution step generates a lot of model outputs files,
but most of the time, user just want to know  some statistical indices, such as averaged data.
so this kind of statistical indices  or processed results are calculated in the post-processing step, and get saved to "results" folder.
However, there are some cases users want to get all the raw model outputs back (probably in a separate step) to further analyze the model outputs on jupyter.
So there should be a way to allow user to choose what subfolder(s) in the "results" to download, and allow user to choose to download  other subfolder(s) in "results" in a separate step without re-running the model or submitting a job

I believe the first part is satisfied by https://github.com/cybergis/cybergis-compute-hello-world/blob/main/manifest.json#L38, but needs documentation on the SDK site.
The second part was implemented in v2.1


Modified base plate to fit SMA antennas

Adds extensions and holes to allow users to add SMA antennas. Looks better, works better too.
These are small wifi antennas that work fine:
https://www.amazon.com/gp/product/B07111BNBB/ref=ppx_yo_dt_b_asin_title_o01_s00?ie=UTF8&psc=1
Here's a picture of a beta version:

JetRacerV2.zip

Hi Chris,
Thanks for sharing, this looks awesome!
Do you have a fork that you're working out of with these changes?
Best,
John

No, but I can do that if it's easier for you to pull from a fork. I figured you'd want to modify the original CAD file rather than using my janky hack ;-)
BTW, if you want to lower the center of mass for better handling, I've used 15mm standoffs, not the 20mm specified, and it works well. It does requires the motor controller to be moved a bit closer to the edge of the baseplate to give it enough room. So if you're redesigning the plate for antennas, you might want to consider doing that, too

Hi Chris,
Thank you for letting us know the cool trick to lower the center of mass.
And we will definitely consider adding the SMA antenna fork for the next revision of STL file, BoM and hardware assembly manual.

Hi Chris,
We just introduce JetRacer - Tamiya version, added the separate BoM and Hardware Setup doc for it.
https://github.com/NVIDIA-AI-IOT/jetracer/blob/master/docs/tamiya/bill_of_materials.md
https://github.com/NVIDIA-AI-IOT/jetracer/blob/master/docs/tamiya/hardware_setup.md
We included the SMA antenna connector mount holes on its 3d-printed chassis.
It was a great idea! Thank you again.


Distribution map has no corrlectly colors

the expected result does not correspond to the actual one
https://explorer.dev.grid.tf/nodes
actual res
status - offline

ex:res
the card must be red

Version v1.4.2
Deployed on Testnet
No.177 - Test case: TC226

@VenyaPanou sorry, I meant you

@rkhamis , Hi , on the picture in the test case map has red color when nodes - offline


Optimize code

Codecov Report
Patch coverage: 100.00% and project coverage change: -0.24% :warning:

Comparison is base (6067937) 85.66% compared to head (93f63f7) 85.43%.
Report is 3 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #16      +/-   ##
==========================================
- Coverage   85.66%   85.43%   -0.24%
==========================================
  Files           4        4
  Lines         307      302       -5
==========================================
- Hits          263      258       -5
  Misses         44       44

Files Changed
Coverage Δ

contracts/halo-farm/src/contract.rs
87.72% <100.00%> (-0.33%)
:arrow_down:

contracts/halo-farm/src/formulas.rs
100.00% <100.00%> (ø)

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

close #15


Simpler custom commands

What problem does this solve or what need does it fill?
Custom commands are cumbersome and bulky to work with. See book draft for current design.
What solution would you like?
impl Command for <impl FnOnce(&mut World)>
This could be used for simple one-off use-cases where the whole struct + trait extension pattern is too heavy.
What alternative(s) have you considered?
Running systems as commands has similar effects, see #2234. However, it has higher overhead and is not well-suited to reusing custom entity spawning / other archetype modifying logic (unless we use it to insert new exclusive systems).
Additional context
Idea credit @TheRawMeatball.

I see no harm in implementing Command for functions / support this. But I wouldn't recommend it for any "structured / reusable" command, especially those with inputs. Extension methods are 100% optional, so in practice this is the difference:
// Struct with no inputs
struct Foo;
impl Command for Foo {
    fn write(self, world: &mut World) {
        /* do thing */
    }
}
commands.add(Foo);

// Struct with inputs
struct Bar {
    baz: usize,
}

impl Command for Bar {
    fn write(self, world: &mut World) {
        /* do thing */
    }
}
commands.add(Bar { baz: 42 };

// Floating functions with no inputs
fn foo(world: &mut World) {
    /* do thing */
}

commands.add(foo);

// Floating function with inputs
fn bar(baz: usize) -> impl FnOnce(&mut World) {
    move |world: &mut World| {
        /* do thing with baz */
    }
}

commands.add(bar(42));

I think functions will be most useful for one-off system-specific capture closure commands. Traits seems way clearer for reusable commands (both on the definition and consumption side).

// Floating function with inputs
fn bar(baz: usize) -> impl FnOnce(&mut World) {
    move |world: &mut World| {
        /* do thing with baz */
    }
}

commands.add(bar(42));

Why don't we just make a macro to convert a standard function into that special format?

You could go one further, and even make the extension trait with a macro 🤔
// Creates a storage data struct and extends the Command trait.
#[command]
fn do_stuff(world: &mut World, param1: Param1) {
   // Does things
}

// Usage
commands.do_stuff(param1);

Sure, but a macro doesn't seem very practical here, or very bevy-ish. But, I'd say floating fn with inputs personally looks pretty clean, though that's more so a style thing.

Yeah, my preference is for the floating fn personally; I think it's nice for simple one-off uses.
That plus proper docs on how to do custom commands the Proper Way should be plenty.

Wouldn't a floating fn with input be a system? So #2234 would fix this?

Chances are if you're writing a custom command it's because you need direct world access, so, probably not.

Does #2234 work with exclusive systems @mockersf?

Even if it did, getting all the system stuff feels like unnecessary complexity.


Added Norwegian Nynorsk

Data for Norwegian Nynorsk (Norway has two written languages, Nynorsk (nn) and Bokmål (nb)).

Thank you for the PR. I will try to incorporate it soon, but I first need to get the tests working again.

I've changed from Travis to Github workflow testing. I'll test on my local host...

Great, thanks for merging :) :+1:

On Tue, Oct 13, 2020 at 02:13 Eskild Hustvedt<EMAIL_ADDRESS>wrote:

Great, thanks for merging :) 👍

You are most welcome, you made it very easy to do!


test: combine prql-compiler test binaries, test_each_file

Followup for #3715
This PR does two things:

combines prqlc/prql-compiler/tests/integration and prqlc/prql-compiler/tests/sql into a single test binary,
replaces insta::glob! with test_each_file::test_each_path!, which is a macro that generates separate tests:

prql-compiler::integration:
    bad_error_messages::array_instead_of_tuple
    bad_error_messages::empty_interpolations
...
    error_messages::test_ambiguous
    error_messages::test_ambiguous_inference
...
    parser::check_invalid_version
    parser::check_valid_version
...
    queries::compile::aggregation   <-- all of these used to be a single test
    queries::compile::arithmetic
    queries::compile::cast
    queries::compile::constants_only
    queries::compile::distinct
    queries::compile::distinct_on
    queries::compile::genre_counts
    queries::compile::group_all
    queries::compile::group_sort
    queries::compile::invoice_totals
    queries::compile::loop_01
    queries::compile::pipelines
    queries::compile::read_csv
    queries::compile::set_ops_remove
    queries::compile::sort
    queries::compile::switch
    queries::compile::window
    queries::fmt::aggregation
    queries::fmt::arithmetic
    queries::fmt::cast
    queries::fmt::constants_only
    queries::fmt::distinct
    queries::fmt::distinct_on
    queries::fmt::genre_counts
    queries::fmt::group_all
    queries::fmt::group_sort
    queries::fmt::invoice_to
...

This means that when a test panics:

it is easy to see which test file panicked,
other tests will run regardless.

I've also started using cargo-nextest, which has nicer printout and cuts run time of all tests from 7.5sec to 4.8sec. Not much, but it's something.

replaces insta::glob! with test_each_file::test_each_path!, which is a macro that generates separate tests:

Yeah, it's a shame that glob! doesn't show enough detail; I agree it's annoying when the test doesn't immediately & obviously show what's wrong. FWIW I think it used to — I wouldn't have switched that back unless I had thought it did, with the description field etc.
I put https://github.com/mitsuhiko/insta/issues/424 in, but haven't got to even starting on it.
So +1 for the change given our constraints, thanks...

Making glob! report more details would be hard. That's because when a test panics, you would have to catch that panic, recover, print the panic message and continue with other tests.
This same logic is already implemented by the Rust's #[test] macro (or some other internal machinery), so test_each_file! takes advantage of that:
test_each_path! { in "./prqlc/prql-compiler/tests/integration/queries" as compile => run }

fn run(prql_path: &Path) {
    ...
}

... will expand to:
mod compile {
    #[test]
    fn arithmentic() {
        run(PathBuf::new("./prqlc/prql-compiler/tests/integration/queries/arithmentic.prql));
    }

    #[test]
    fn group() {
        run(PathBuf::new("./prqlc/prql-compiler/tests/integration/queries/group.prql));
    }

    ...
}

Is this different to the other tests though? Insta achieves this for non-glob tests, I think?

It does not, I think. That's why I was splitting the tests. It just doesn't panic on non-matching snapshots.

it has its own macro, it can avoid panicking until the end...

Macros are just a fancy way to write plain Rust code. Try running cargo expand --test=integration queries

It just doesn't panic on non-matching snapshots.

It doesn't panic per se, but it does exit with a non-zero exit code.
And with --check (which is default in CI), it shows the full output rather than proposing a snapshot change:
cargo insta test -p prqlc-parser --check
    Blocking waiting for file lock on build directory
    Finished test [unoptimized + debuginfo] target(s) in 2.45s
     Running unittests src/lib.rs (target/debug/deps/prqlc_parser-653f00769a9839a4)

running 4 tests
test lexer::numbers ... ok
test interpolation::parse_interpolate ... ok
test lexer::test_line_wrap ... ok
test lexer::quotes ... FAILED

failures:

---- lexer::quotes stdout ----
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Snapshot Summary ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Snapshot: quotes
Source: prqlc/prqlc-parser/src/lexer.rs:601
──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
Expression: quoted_string(false).parse(r#"'aou'"#).unwrap()
──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
-old snapshot
+new results
────────────┬─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
    0       │-aoeu
          0 │+aou
────────────┴─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
Stopped on the first failure. Run `cargo insta test` to run all snapshots.
thread 'lexer::quotes' panicked at 'snapshot assertion for 'quotes' failed in line 601', /Users/maximilian/.cargo/registry/src/index.crates.io-6f17d22bba15001f/insta-1.34.0/src/runtime.rs:563:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

failures:
    lexer::quotes

test result: FAILED. 3 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.06s

error: test failed, to rerun pass `-p prqlc-parser --lib`
error: 1 target failed:
    `-p prqlc-parser --lib`
info: no snapshots to review

I'm not following. What have you discovered?

Sorry.
What was wrong with using insta, if you remember?
I had thought that using insta::glob didn't give enough context on what file & dialect was failing, since I saw that myself recently.
But then I tested that just now, and found that it did show these details. But it sounds like you had issues too — do you remember what were your reasons for moving away from insta::glob?

Now that we have one #[test] per query file, a panic would:

print which file caused the panic :white_check_mark:, but not which connection (dialect)  :x:
allow other files and connections to be tested with --no-fail-fast :white_check_mark:

Non-matching snapshot error contains info about which file caused the error. :white_check_mark:
with_duplicates! error does contain info about which dialect was not matching. :white_check_mark:

Perfect!

with_duplicates! error did not contain info about which dialect was not matching. ❌

Thanks — this is what I was seeing, then.

a panic would:
* not print which file or connection (dialect) caused the panic, ❌

Ah, this is what you meant about panics — I see now. I was confusing the discussion for a panic caused by an assert vs. a panic from running our code.

(I'm quite impressed you remember all the context of what works where!)


CI pre-commit check

Type of changes

[ ] Bug fix
[ ] New feature
[ ] Documentation / docstrings
[ ] Tests
[x] Other (CI)

Checklist

[x] I've run the latest black with default args on new code.
[ ] I've updated CHANGELOG.md and CONTRIBUTORS.md where appropriate.
[ ] I've added tests for new code.
[x] I accept that @willmcgugan may be pedantic in the code review.

Description
The contributing guidelines suggest that pre-commit should be used when committing (Contributing/pre-commit). This PR adds a workflow to run pre-commit for all files for each PR. It also updates instances where pre-commit has not been run before committing (mainly end of file fixes and isort) so that the workflow will initially pass.

https://github.com/Textualize/rich/issues/2849


Upload image files.

Upload to the chart releases an asset containing all the container images used in the chart.
Fix https://github.com/kubewarden/kubewarden-controller/issues/343

This generates one txt file per chart which contains the images for this specific chart. It would be great to have one txt file will the images from all charts. That way the user just needs to execute the airgap script once with all the images in the same txt file.

Where do you want to store this file? Should we copy it in all chart releases?

This generates one txt file per chart which contains the images for this specific chart. It would be great to have one txt file will the images from all charts. That way the user just needs to execute the airgap script once with all the images in the same txt file.

@raulcabello, where do you want to store this file? Should we duplicate it in all chart releases?

Ok, let me document here what we discussed in the kuberwarden-dev channel in the Kubernetes Slack.
We agreed to change the current approach to have a unified file with all container images. This file will use the name suggested by @viccuad , kubewarden-crds-${{crd-chart-version}}_kubewarden-controller-${{controller version}}_kubewarden-defaults-${{defaults version}}_images.txt. The file will be upload to all chart releases.

I've updated the PR to add a file in the helm chart tarball to store the image used in the chart. Besides that, I've created another file with all images used in all charts. This unified file is attached in the releases of the kubewarden-controller and kubewarden-defaults charts. The goal of the unified file is to be used with the rancher script to load container images in a air gap environment.


james/newtutorials

FYI; Please ignore this branch/PR. It's a test for our new tutorials experience and I'll be closing it out once I'm done.

Closing this test of the new tutorials content type


Add Arabic translation

Arabic (RTL).
Hope there is progress on https://github.com/CloudCannon/pagefind/pull/453#issuecomment-1760668025 .

@bglw should this page be updated for Arabic UI Translations?  I can open a PR at https://github.com/CloudCannon/pagefind/blob/main/docs/content/docs/multilingual.md if needed.
Thanks for merging ❤


#5354 Port Resnet50 to TTNN

I added the call to downsample directly inside of ttnn.Conv2d, so you don't need to expose this op

Thanks I will ping you for more info.

@shwetankTT nit-picking: can you replace all Bottol with Bottle :)

Would it make sense to duplicate this functional version and go ahead and add them both to https://github.com/tenstorrent-metal/tt-metal/blob/main/tests/scripts/run_performance.sh?   The idea is that as progress as made we would all see the performance improving daily.

Already merged with mainline.


using first() in a dashboard caused the UI triangle to appear

message is
Index 1 out of bounds for length 1
assume first is 1 based, array is 0 based ?

happens for any() too


Use version provided via sys prop & remove org name

Until we provide a better way to display FQN of a module, we have removed displaying it in left column in API docs. Furthermore, to fix version used in standard library doc generation, we have to honor a system prop if module version is empty.
Check List

[X] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@dda2eec). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master   #20244   +/-   ##
=========================================
  Coverage          ?   19.79%
=========================================
  Files             ?       55
  Lines             ?     1470
  Branches          ?      227
=========================================
  Hits              ?      291
  Misses            ?     1163
  Partials          ?       16

Continue to review full report at Codecov.

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


Add automation workflows

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@3428077). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main       #2   +/-   ##
=======================================
  Coverage        ?   86.64%
=======================================
  Files           ?       37
  Lines           ?     3676
  Branches        ?        0
=======================================
  Hits            ?     3185
  Misses          ?      491
  Partials        ?        0

Continue to review full report at Codecov.

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


how I use to jsonb in postgresql

How I use jsonb in postgresql.
or will this feature be added for in future?
thank you for making kotysa!
:)

Hi again @boojongmin ,
Thanks for your feedbacks !
To be honest this issue will probably not be done soon as it is a quite special SQL type


Inconsistent typedef rules

#13 introduced multiple inconsistencies for me (examples seen below). It is not possible to create code that has no lint errors. (Or maybe I am doing something wrong?)
As @sindresorhus already pointed out variable-declaration was annoying this clearly has been used and I am not sure why the problems I am pointing out were not found / removed? Do I miss something obvious?
As a fix I would remove the typedef requirement for the ones I pointed out below. Or maybe there is a better solution?
Because of this I checked the other typedef requirements and think they are still useful:

call-signature
arrow-call-signature
property-declaration
member-variable-declaration

Examples
arrow-parameter
import test, {ExecutionContext} from 'ava';

test('1', t => {
	t.pass();
});

test('2', (t: ExecutionContext) => {
	t.pass();
});

error messages:
ERROR: 3:11   typedef                         expected arrow-parameter: 't' to have a typedef
ERROR: 7:13   no-unnecessary-type-annotation  type annotation is redundant

parameter
function meh(foo: string = 'bar', bar = 'foo'): string {
	return foo + bar;
}

error messages:
ERROR: 1:19   no-inferrable-types             Type string trivially inferred from a string literal, remove type annotation
ERROR: 1:35   typedef                         expected parameter: 'bar' to have a typedef

object-destructuring
const testObj = {paramA: 'test', paramB: 15};

function caseA(): string {
	const {paramA, paramB} = testObj;
	return paramA + String(paramB);
}

function caseB(): string {
	const {paramA, paramB}: {paramA: string; paramB: number; } = testObj;
	return paramA + String(paramB);
}

error messages:
ERROR: 4:8    typedef                         expected object-destructuring: '{paramA, paramB}' to have a typedef
ERROR: 9:24   no-unnecessary-type-annotation  type annotation is redundant

array-destructuring
const testArr = [1, 2, 3];

function caseA(): number {
	const [first, second, third] = testArr;
	return first + second + third;
}

function caseB(): number {
	const [first, second, third]: number[] = testArr;
	return first + second + third;
}

error messages:
ERROR: 4:8    typedef                         expected array-destructuring: '[first, second, third]' to have a typedef
ERROR: 9:30   no-unnecessary-type-annotation  type annotation is redundant

I'm having a similar issue when using the map operator on an array:
['foo'].map((s: string, i: number): string => `${i}${s.toUpperCase()}`);

Errors:
ERROR: 1:26  no-unnecessary-type-annotation  type annotation is redundant

Errors when removing the type for s and i:
ERROR: 1:14  typedef                         expected arrow-parameter: 's' to have a typedef
ERROR: 1:17  typedef                         expected arrow-parameter: 'i' to have a typedef

Sorry for the inconvenience. I should have tested this better. I didn't hit this in one project as TSLint was not working correctly and in the other project I used for dogfooding this, it was so many errors for typedef that I disabled it until I would have a chance to go through it.

arrow-parameter

I think it would be nice to be explicit about parameter types here, but I tihnk the rule needs an option to not have to type functions in arrow parameters (callbacks).

parameter

I think the typedef rule should have an option to not require types for parameters with default argument literals.

I really think these two rules should have been one rule with various options to customize it. Please open issues on TSLint if you agree.

I read through a bunch of issues for TSLint regarding typedef (why haven't I done this earlier?) and in most cases the TS compiler option noImplicitAny does this job already perfectly fine.
I tried all of the above code and did not get any false positives while having errors with tsc for correctly detected missing types. 👍
This may break some builds but as you are requiring lint and build to work I don't think it's worse than having a lint error.
--noImplicitAny  Raise error on expressions and declarations with an implied 'any' type.


azure-wi-webhook-controller-manager brokes aks upgrade because of pdb

Our attempt to upgrade AKS failed after a hour and put whole cluster in failed state 🤷♂
Failed to save Kubernetes service 'capybara002-aks-eun-dev'.

Error: Drain of aks-infra002-17497433-vmss00000y did not complete:

Too many req pod azure-wi-webhook-controller-manager-749b9d5cc8-2chl9 on node aks-infra002-17497433-vmss00000y:

azure-workload-identity-system/azure-wi-webhook-controller-manager-749b9d5cc8-2chl9 blocked by pdb azure-wi-webhook-controller-manager with unready pods [].

See http://aka.ms/aks/debugdrainfailures

Imagine how bad and scarry it was :) thankfully it was not production but development
In AKS upgrade docs there is mention about this:

Ensure that any PodDisruptionBudgets (PDBs) allow for at least 1 pod replica to be moved at a time otherwise the drain/evict operation will fail. If the drain operation fails, the upgrade operation will fail by design to ensure that the applications are not disrupted. Please correct what caused the operation to stop (incorrect PDBs, lack of quota, and so on) and re-try the operation.

But this budgets are hidden inside chart and not configurable and/or mentioned anywhere in docs (to be fair I did not even know that we have one in our cluster)
As a workaround I have manually replaced minAvailable to maxUnavailable and with help of az cli rerun node pool upgrade and then whole cluster - it helped and cluster healthy again
The problem here: if we leave this as is - it will mean that we can not upgrade, and even worse, enable auto upgrade because it will be always failing exactly because of this deployment
So I am wondering if there some other workarounds we may use or may be at least make this part of chart configurable

Meanwhile the workaround is
before making an upgrade run
kubectl -n azure-workload-identity-system patch pdb azure-wi-webhook-controller-manager --type=json -p='[{"op": "remove", "path": "/spec/minAvailable"},{"op": "add", "path": "/spec/maxUnavailable", "value": 1}]'

after upgrade
kubectl -n azure-workload-identity-system patch pdb azure-wi-webhook-controller-manager --type=json -p='[{"op": "remove", "path": "/spec/maxUnavailable"},{"op": "add", "path": "/spec/minAvailable", "value": 1}]'

but this is applicable only for manual upgrades

Another possible workaround is to configure rolling update in a such a way that it will guarantee that at least one instance will be always running, yes, for a short period of time there may be two instances while things moving, but it will allow to get rid of pdb at all
https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#max-unavailable
# ...
spec:
  strategy:
    rollingUpdate:
      maxSurge: 1
      maxUnavailable: 1
    type: RollingUpdate
# ...

which means that rolling update will try add new instance before removing old one, there will be always at least one instance, and in case of upgrades, for a short period there may be two instances
with this in place we may add flag to disable pdb at all


[openssl-windows] Make sure ninja is available on our path

vcpkg_test_cmake uses ninja by default, make sure we install it and have it on our path, fixes #5713. Normally ninja would be installed by vcpkg_configure_cmake but openssl doesn't use cmake for compilation of itself

Can someone from Microsoft add the check failure log?

Hi @jwillemsen , here are some errors:
    fizz                          **regression**                Fail vs Pass
    wangle                                                      Skip vs Pass

fizz and wangle depends on openssl-windows, plz check to install them correctly.
Thanks.

@JackBoosY openssl did work a few weeks back without ninja installed, seems something within vcpkg was changed without updating openssl. Has someone from the vcpkg team identified the breaking change?
It would really help when the logs would be automatically linked to the PR.

Looks this is very likely the breaking change https://github.com/Microsoft/vcpkg/commit/bdc5d538a59e4983ab184d65963bac2678d35947

fizz and wangle depend on folly which seems broken, see #5759

Looks other changes broken openssl and much more, this PR fixes the issue for openssl, maybe get this in, it improved things a little bit.

vcpkg_test_cmake() has been disabled by https://github.com/Microsoft/vcpkg/commit/c2ad1baafccc91bf7e9e60a390eb91cf4e130062 while we rework it to address the common issues that keep coming up.  With that change openssl-windows will build so I am closing this PR for now.  If there is still an issue I am unaware of then please open the PR again.


Update documentation screenshots for Wagtail 5.0

Updates all screenshots of the UI in the dev docs. There isn’t much to see here so I’ll merge right away.
The main changes are:

Switching the TableBlock screenshot to use one of the instances of the RecipePage model we recently added to bakerydemo, and changing the format of the image so it’s easier to automate.
Using the correct amount of progress in the tutorial for the tutorial_8 screenshot.

The RTD build failure is unrelated to the changes here, will attempt to fix it in #10408.


Security Vest and Helmet Resprite

About the PR
 Resprites the default Security vest and helmet.
Why / Balance
 The old variations were old and were beginning to fall behind the rest of the art style, plus I want to see usage of the vest and helmet as they have been mostly unused by anyone except cadets.
Technical details

Media

New:

Old:

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog

:cl:

tweak: Security Vest Resprited
tweak: Security Helmet Resprited

Whoops, messed up the old icon previews

I don't like the flatness of the previous resprite for the helmet, but these changes don't look right, mainly the vest itself.

Let's make them look less evil not more

Let's make them look less evil not more

Please explain what makes you say that?

The vest looks like shit, can't exactly pinpoint what, it's better then the original.

I'd like feedback on what does or doesn't work, it's fine to not like it, just tell me why in a way that I can work on.

Extremely stiff, I understand you were trying to do velcro straps on the sides as well but it just doesn't visually work.

I feel like there isn’t enough depth(?) to the inventory sprite. Like with the shading and the shoulders, it’s very clear the old one is a representation of a physical object, while the new one has almost none of that, and looks closer to a painted cardboard cutout

It’s too dark for one, and the form feels off

Alrighty, this should be enough feedback. I'll keep the helmet design and completely rework the vest.
It will remain a relatively dark color to keep with the slim vest that most officers use, this is so that you can use the helmet with either vest and look good.

I think the glass visor looks a little weird. I think I'd rather it get removed from the icon than added to the clothing sprites.


UnicodeDecodeError in posixpath on ipython==5.1.0

I have run pip-compile with python 2.7 and it failed with the above error:
pip-compile -o base.txt base.in
No handlers could be found for logger "pip.req.req_install"
Traceback (most recent call last):
  File "/usr/local/bin/pip-compile", line 11, in <module>
    sys.exit(cli())
  File "/usr/local/lib/python2.7/dist-packages/click/core.py", line 722, in __call__
    return self.main(*args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/click/core.py", line 697, in main
    rv = self.invoke(ctx)
  File "/usr/local/lib/python2.7/dist-packages/click/core.py", line 895, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/usr/local/lib/python2.7/dist-packages/click/core.py", line 535, in invoke
    return callback(*args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/piptools/scripts/compile.py", line 185, in cli
    results = resolver.resolve()
  File "/usr/local/lib/python2.7/dist-packages/piptools/resolver.py", line 109, in resolve
    has_changed, best_matches = self._resolve_one_round()
  File "/usr/local/lib/python2.7/dist-packages/piptools/resolver.py", line 191, in _resolve_one_round
    for best_match in best_matches
  File "/usr/local/lib/python2.7/dist-packages/piptools/resolver.py", line 192, in <genexpr>
    for dep in self._iter_dependencies(best_match))
  File "/usr/local/lib/python2.7/dist-packages/piptools/resolver.py", line 261, in _iter_dependencies
    dependencies = self.repository.get_dependencies(ireq)
  File "/usr/local/lib/python2.7/dist-packages/piptools/repositories/local.py", line 68, in get_dependencies
    return self.repository.get_dependencies(ireq)
  File "/usr/local/lib/python2.7/dist-packages/piptools/repositories/pypi.py", line 135, in get_dependencies
    dependencies = reqset._prepare_file(self.finder, ireq)
  File "/usr/local/lib/python2.7/dist-packages/pip/req/req_set.py", line 620, in _prepare_file
    session=self.session, hashes=hashes)
  File "/usr/local/lib/python2.7/dist-packages/pip/download.py", line 821, in unpack_url
    hashes=hashes
  File "/usr/local/lib/python2.7/dist-packages/pip/download.py", line 663, in unpack_http_url
    unpack_file(from_path, location, content_type, link)
  File "/usr/local/lib/python2.7/dist-packages/pip/utils/__init__.py", line 599, in unpack_file
    flatten=not filename.endswith('.whl')
  File "/usr/local/lib/python2.7/dist-packages/pip/utils/__init__.py", line 492, in unzip_file
    fn = os.path.join(location, fn)
  File "/usr/lib/python2.7/posixpath.py", line 80, in join
    path += '/' + b
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc6 in position 27: ordinal not in range(128)

the base.in file looks like:
...
django-bootstrap3==7.0.1
Django==1.10.5
djangorestframework-jwt==1.8.0
djangorestframework==3.4.6
icalendar==3.10
ipython==5.1.0
...

Any ideas?

This looks very much like a duplicate of #433

@byjott It does look similar, but your fix for #433 isn't working (at least in our fork)

Should be fixed by #568, closing.


Add section on test suite structure

As per a discussion on discord, this PR adds a section on suggested test suite structure.  Also fixes a couple of other random things.

@carver Just found this old PR sitting around.  Still have any concerns?


[decompiler] say what object file is currently being worked on

Often times the decompiler will crash without warning but with no indication of the cause or even which file it crashed on. Makes it very difficult to debug quickly.

sticking a print in for_each_obj does the job but also spams the console ridiculously hard... need something more elegant

#890 will send this info to the decompiler.log file in a much more elegant fashion, if it is too verbose we can always log it to a separate file

fixed(?) in #895


New version: ExpressLRS.ExpressLRS-Configurator version 1.5.1

Result: Installation Failed

Manifest
Add/Remove Programs

Name
ExpressLRS Configurator

Version
1.5.1

Publisher
ExpressLRS Configurator Contributors

ProductCode

Auto-updated by vedantmgoyal2009/winget-pkgs-automation in workflow run 3507
Microsoft Reviewers: Open in CodeFlow

@wingetbot run


Add analytics

Hey everyone, I just noted that we don't have any analytics in this project, so there is no way to get information about how the user is handling with our app.
What do you think about add analytics in order to get more data about our user? 💃
That could be added for v1.4

According to about privacy policy you are misinformed.

@rancidfrog I believe this is referring to the store analytics on iTunes and Google Play Store, which can be fairly limited. This issue relates to more specific information, such as device model, location, etc. that isn't reported by iTunes or Google Play Store Analytics.

That is not what is written.
Read it.

device and platform version, region and referrer...

It would be thoughtful for an opt-out settings.
Especially if you plan on going full on creep mode and collect all data possible.

@rancidfrog The idea here is understand what features are more used by our user. I'm no intent to get user data, only tracks navigation, clicks and etc... 😄

I understand.
But, would it be better to use only one analytics library; I.E. crashlytics or another.
Instead of using google, iTunes, and whatever allows for good feedback?

Appreciate the discussion on this folks, and thank you for opening this @jouderianjr.
So the Google Play Console and iTunes Connect do provide analytics out of the box and as limited as they are, they actually provide more than I thought they would:
iTunes Connect

We're also seeing a greater number of crashes this past week with our most recent release:

Play Console

Similarly, more crashes with our most recent release (most likely due to markdown rendering if I'm not mistaken)

Overall the analytics provided isn't extensive (clicks, navigation, etc...). I would definitely be interested in exploring a separate library to get more insightful data without violating our anonymity protocol as mentioned in pur privacy policy.
Moreover I think it's important that we find a way that people in the organization here have complete access to view analytics and it's not just me :sweat_smile:


Fix temporary embed JS in IE

In IE8, the Javascript used to set up the embedded iframes (HowTo and USA) doesn't update as it does in Chrome.
To reproduce, go to http://ringdev.measuredvoice.com/usagov/embed-example.html in IE8.
Expected: The embedded verification form should appear under the header.
Current: An "oops" page from USA.gov is displayed.

Fixed this by changing the Javascript used to set the iframe URL.


feat: Port path api to js

What kind of change does this PR introduce? (check at least one)

[ ] Bugfix
[x] Feature
[ ] New Binding Issue #___
[ ] Code style update
[ ] Refactor
[ ] Build-related changes
[ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

[ ] Yes. Issue #___
[x] No

The PR fulfills these requirements:

[x] When resolving a specific issue, it's referenced in the PR's title (e.g. fix: #xxx[,#xxx], where "xxx" is the issue number)
[x] A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.

If adding a new feature, the PR's description includes:

[x] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

Would you please give some context behind the purpose of this PR and if it's related to prior discussion or an issue?

The purpose it to make accessing these directories available from js side. I think it can ease the development for tauri users a bit, since they won't have to write this by themselves.
No, this is not related to prior discussion but I think there is an issue open #929 .

I pushed new changes but I am not sure if I named the endpoints and methods correctly. If you have some better names or other comments, let me know.


feat: Implement LockfileResourceLocker

This closes #324.
However, I have not had time to make it fully work. There is still an error somewhere in the recursive recall when there is another lock on the file and a second lock is requested.
I also have not been able to mimic the internal error in the release function of the external library in the unit test.

Closing for now; we can take it up later.


fix: remove beta statement

:tada: This PR is included in version 1.0.3 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


DM cluster can't start while -hostname use FQDN

What did you do?

use FQDN in -hostname area
deploy DM cluster
try to start dm cluster

What did you expect to see?
DM cluster can start as expect.
What did you see instead?
start dm cluster failed
Versions of the cluster
DM version (run dmctl -V or dm-worker -V or dm-master -V):
v6.1.0

Upstream MySQL/MariaDB server version:
(paste upstream MySQL/MariaDB server version here)

Downstream TiDB cluster version (execute SELECT tidb_version(); in a MySQL client):
(paste TiDB cluster version here)

How did you deploy DM: tiup or manually?
(leave TiUP or manually here)

Other interesting information (system version, hardware config, etc):
>
>

current status of DM cluster (execute query-status <task-name> in dmctl)
(paste current status of DM cluster here)

yaml file:
global:
user: "tidb"
ssh_port: 22
deploy_dir: "/dm-deploy"
data_dir: "/dm_data"
master_servers:

host: tiup-peer
port: 8261
peer_port: 8291
worker_servers:
host: tiup-peer
port: 8262
monitoring_servers:
host: tiup-peer
grafana_servers:
host: tiup-peer

maybe this is a TiUP bug? what's the error

While use FQDN, below error reported
[2022/05/30 16:11:35.757 +08:00] [ERROR] [main.go:71] ["fail to start dm-master"] [error="[code=38037:class=dm-master:scope=internal:level=high], Message: fail to validate embed etcd config, RawCause: expected IP in URL for binding (http://tiup-peer:8291/), Workaround: Please check configs in master configuration file."] errorVerbose="[code=38037:class=dm-master:scope=internal:level=high], Message: fail to validate embed etcd config, RawCause: expected IP in URL for binding (http://tiup-peer:8291/), Workaround: Please check configs in master configuration file.[ngithub.com/pingcap/tiflow/dm/pkg/terror.(*Error).Delegate\n\tgithub.com/pingcap/tiflow/dm/pkg/terror/terror.go:315\ngithub.com/pingcap/tiflow/dm/pkg/terror.(*Error).AnnotateDelegate\n\tgithub.com/pingcap/tiflow/dm/pkg/terror/terror.go:324\ngithub.com/pingcap/tiflow/dm/dm/master.(*Config).genEmbedEtcdConfig\n\tgithub.com/pingcap/tiflow/dm/dm/master/config.go:392\ngithub.com/pingcap/tiflow/dm/dm/master.(*Server).Start\n\tgithub.com/pingcap/tiflow/dm/dm/master/server.go:169\nmain.main\n\tgithub.com/pingcap/tiflow/dm/cmd/dm-master/main.go:69\nruntime.main\n\truntime/proc.go:250\nruntime.goexit\n\truntime/asm_amd64.s:1571"]

etct listen addr must be ip
see https://github.com/etcd-io/etcd/issues/9575

--peer-urls="{{.Scheme}}://{{.IP}}:{{.PeerPort}}" I think the right template in tiup-dm should be --peer-urls="{{.Scheme}}://<IP_ADDRESS>:{{.PeerPort}}"


How to set min open and max open with flow variable?

Hi how I can set the min and max open or close time with flow variable? it works for the offset but not for the the min and max.
The idea it is to do the setup from HOME ASSISTANT.
Thanks

This is currently not possible I will think about to implement this in a later version.

What can be done is to setup a rule with a minimum or a maximum Blind level:

In the meantime there is a possibility to overwrite the most of the settings by message object.
I can't think of an elegant way to use context data for this type of data. The problem here is that there is no mechanism in Node-Red to react to changes in the context of stored data.
Assuming that data from the context is used here, there is a problem with the trigger as to when it should be updated. The initial values are then also a problem. These settings are initially processed during flow. At this point in time, however, the data in the context may not yet be set.
For these reasons, the option of the setting by msg.topic and msg.payload should be sufficient for the time being. So these data needs to be send once short after flow start and if the data has changed in HOME ASSISTANT.

Thanks for the change 👍
I still don't quite get it.
Currently, I'm using 8 Blind Controllers, like in the screenshot:

The only difference between those 8 blind controllers are the window top/bottom/azimuth start/azimuth end and the floor length.
My goal is to use just one blind controller which is controlled by an input object with those settings. Something like this:
msg = {
  "settings": {
    "windowTop": 210,
    "windowBottom": 10
 }
}

Is this not possible?
With this implementation it is hard to set multiple values at once. I need to send X messages to set multiple settings, which generates X output messages to control the blind.

Test and example code of "Rolladensteuerung Parameter setzen" node
var windowSize = "small" //big
var windowDirection = "east"
var settingsToSet = [
    "setSettingsTopic",
    "setSunDataTopic",
    "setBlindSettingsTopic",
    "setWindowSettingsTop",
    "setWindowSettingsBottom",
    "setWindowSettingsAzimuthStart",
    "setWindowSettingsAzimuthEnd",
    "setSunDataFloorLength"
]

var messages = [];
for(var setting of settingsToSet)
{
    var payload;
    var topic = setting;

    if(setting == "setSettingsTopic" || setting == "setSunDataTopic" || setting == "setBlindSettingsTopic")
    {
        if(windowDirection == "north") payload = "Norden";
        else if(windowDirection == "east") payload = "Osten";
        else if(windowDirection == "south") payload = "Süden";
        else if(windowDirection == "west") payload = "Westen";
    }
    else if(setting == "setWindowSettingsAzimuthStart")
    {
        if(windowDirection == "north") payload = 285;
        else if(windowDirection == "east") payload = 0;
        else if(windowDirection == "south") payload = 70;
        else if(windowDirection == "west") payload = 160;

    }
    else if(setting == "setWindowSettingsAzimuthEnd")
    {
        if(windowDirection == "north") payload = 360;
        else if(windowDirection == "east") payload = 160;
        else if(windowDirection == "south") payload = 250;
        else if(windowDirection == "west") payload = 340;
    }
    else if(setting == "setWindowSettingsTop")
    {
        if(windowSize == "small") payload = 210;
        else if(windowSize == "big") payload = 210;
    }
    else if(setting == "setWindowSettingsBottom")
    {
        if(windowSize == "small") payload = 100;
        else if(windowSize == "big") payload = 10;
    }
    else if(setting == "setSunDataFloorLength")
    {
        if(windowSize == "small") payload = 80;
        else if(windowSize == "big") payload = 40;
    }

    var message = {};
    message.topic = topic;
    message.payload = payload;
    messages.push(message);

}
return [messages];

Ok ich werde versuchen für diese Werte, das man hier auch anstelle fester Werte flow/global/env wählen kann:

Als Eingabeparameter die zum Blindcontroller Node im Message Objekt geschickt werden klappt das nicht? Eigtl. so wie du es mit den Eingabeparameter reset, position, priority oder expire gemacht hast.

Es gibt noch einen anderen Wunsch: Die Node soll mehr zu SubFlows kompatibel werden. Das lässt sich damit auch besser realisieren.
Der Aufwand ist nicht höher als wenn ich es so umbauen würde das es sich so wie die anderen parameter verhalten.  Dann kann man es auch als message property übergeben.
Ich muss dazu mir erst mal ansehen wie ich das am besten implementiere.

Is integrated in the 2.0.0-beta and can be installed and tested. See Releases Information on how to install the beta version.


The coda daemon is crashed.

The crash log is attached.
coda_crash_report_2019-12-20_03-42-53.197754.tar.gz

Closing this issue as it is stale for a long time.


[instrumentation-document-load] trace parent behaviour not as expected

What version of OpenTelemetry are you using?
"@opentelemetry/core": "^1.25.0"
"@opentelemetry/instrumentation-document-load": "^0.39.0"
"@opentelemetry/api": "^1.9.0"
What version of Node are you using?
N/A (browser)
What did you do?
As per the readme:

Because the browser does not send a trace context header for the initial page navigation, the server needs to fake a trace context header in a middleware and then send that trace context header back to the client as a meta tag traceparent .

I followed this pattern on the backend when generating the page HTML:
<head>
  <!--
    https://www.w3.org/TR/trace-context/
    Set the `traceparent` in the server's HTML template code. It should be
    dynamically generated server side to have the server's request trace Id,
    a parent span Id that was set on the server's request span, and the trace
    flags to indicate the server's sampling decision
    (01 = sampled, 00 = notsampled).
    '{version}-{traceId}-{spanId}-{sampleDecision}'
  -->
  <meta name="traceparent" content="00-ab42124a3c573678d4d8b21ba52df3bf-d21f7bc17caa5aba-01">
</head>

I used the span ID here as the parent span ID for the server.
What did you expect to see?
The browser uses the span ID I provided and becomes the parent of the server span.
What did you see instead?
The browser uses the span ID as its own parent span ID, creates a new random span ID, and becomes the sibling of the server span. Both spans now refer to a nonexistent span ID.
Additional context

I looked at this some time ago and noticed that this was incorrectly implemented right from the beginning - see https://github.com/open-telemetry/opentelemetry-js-contrib/commit/4f48357b7d1dea246a67ef1a0e071fc64aa10e26 - the test case only checks for the server-sent trace id on the root span, but not the span id.
In fact, I don't think the trace api provides a way to specify the span id when starting a span. The idea mentioned in the html comment is hard to implement.


📝 SSE docstring updates

Update docstrings on sse endpoints

@cl0ete we can update / rename this and move these docstring changes to Waypoint

included in PR 1118