text:
Update info about using Siri to turn on / off switch control

What does this PR do?
In some newer iOS versions, it is working fine to use Siri to turn on or off switch control. I could not find iOS release notes on information in which iOS version this was added, but it's working in iOS 17.6.1. Since this makes turning on and off switch control immensely easier, I would like to add it to the docs even though it might not be working for some users with lower iOS version.
How do you test this PR?
Test link: https://appt.org/en/docs/ios/features/switch-control#enable-switch-control and https://appt.org/en/docs/ios/features/switch-control#disable-switch-control

This doesn't work on iOS 17.5.1. Currently updating to 17.6.1.

It doesn't work for me on iOS 17.6.1, both in Dutch and English.
Can you make a video showcasing that how it works on your device, @fbernutz ? Thanks!

It doesn't work for me on iOS 17.6.1, both in Dutch and English.
Can you make a video showcasing that how it works on your device, @fbernutz ? Thanks!

I press the power button to use Siri and say "Turn on Switch Control", later I say "Turn off Switch Control":
https://github.com/user-attachments/assets/218a8e92-53e2-4c9c-a74e-45943020a43e
My phone is set to English language + region is Germany, Siri language is set to English (UK). I have an iPhone 13 Pro with iOS 17.6.1. Switch Control scanning style is auto, control mode is "Item Mode", I have setup one switch with Full Screen to select item.

Thanks for sharing @fbernutz
Maybe you can use that shortcut because you have an accessibility shortcut sets for Switch Control. Or maybe I can't use it because Switch Control hasn't been set-up properly or something.
I'm going to update to iOS 18 later today and will give it another try. But considering it works on your device, either way it's a good addition to the article.

Hi @fbernutz , it still doesn't work for me - but I think it's good info to have for those that can use it. Just merged.

authors: JJdeGroot fbernutz

repo: appt-org/appt-website


text:
Numbered map pins

Thanks for this lib! Is there any way to have numbered map pins for easy identification? I'll typically be showing 30 - 60 pins at a time

@myleftshoe We do not plan on adding a lot of features to this plugin. Our development efforts are focused on https://github.com/apptreesoftware/flutter_map which would allow you to place any Widget on a map. This approach would let you cluster items.

source: gharchive/issue

authors: matthewtsmith myleftshoe

license: MIT

license_type: permissive

license_source: github-api


text:
Bug : When I try deploy a function it doesn't work

Hello,
I create a gitpod with appwrite integration
After I download and initialize the CLI appwrite
I link my project
I create a deployment command from dasboard
I deploy with the CLI
Expect in dashboard  the function deployment is ready.
Result:
The deployment is always processing

Thanks @Gi972. Try again with the latest 0.14.x release and reopen if you still have issues

repo: appwrite/integration-for-gitpod


text:
Save forecastData in a separate table

With #714, we start fetching forecast data to make them available through latest_data.
However, this was a temporary solution. This data is ephemeral and should not be saved in the time_series table. Instead, we should create a new table called forecast_data to store this data, including lead_time.

Create a new table called forecast_data
Point the hourly WindWave data updates to this table and store the next 6 hours of values
Add a new endpoint to get forecast_data for the wind and wave card
In the wind/wave card, use spotter data when available and less than 12 hours old, otherwise use forecast_data
Delete forecast_data from the time-series table

@echaidemenos actually, instead of using the forecast endpoint like we do now, let's use the hindcast endpoint for these to get the latest available forecast in the past. This endpoint is a lot faster and should have the info we need.
All the other changes still apply but we will only have one datapoint of old forecast data in the table

repo: aqualinkorg/aqualink-app


text:
scan locally a repository

It will be nice to use the chain-bench in local mode, for example
chain-bench --local .

Hi,
This is a duplicated issue - https://github.com/aquasecurity/chain-bench/issues/54

repo: aquasecurity/chain-bench


text:
Missing asset in release v0.1.8

It appears that the go binary was not published as part of the release v0.1.8.   The container build fails on step 4/6 as a result.   Can't revert to previous releases as they point at invalid urls now.

looking at the release.yml workflow (GitHub Actions), it appears that it is still pointing at the old tfsec repo url, which may explain why the release failed....thus leading to the issue above.

https://github.com/aquasecurity/tfsec-pr-commenter-action/blob/main/.goreleaser.yml
I think its still referencing the old repo and trying to create the binary artifact in the wrong location.

#22 is the same as this. Anyway to workaround? I tried to reference
aquasecurity/tfsec-pr-commenter-action@v0.1.7
But it didn't make any difference

I forked the code and made the change i Suggested and have no issues creating a release with artifacts.
https://github.com/mc-benchmarkcorp/tfsec-pr-commenter-action/blob/31b67c15509e4633f74949d8fdcd87cca237b844/.goreleaser.yml#L29
https://github.com/mc-benchmarkcorp/tfsec-pr-commenter-action
https://github.com/mc-benchmarkcorp/tfsec-pr-commenter-action/releases/tag/v0.1.9
as you can see it uploads both artifacts under the release.  If you need a fix until this is corrected  fork a version and make the change.

This has been fixed - the issues came about when we moved to aquasec and missed the deployer change. Apologies for the inconvenience caused

Thanks! Working fine for me.

authors: cr-benchmarkcorp mc-benchmarkcorp olympus-fergus owenrumney

repo: aquasecurity/tfsec-pr-commenter-action


text:
Trivy Action times out since today

Until ths morning everything worked well. In all our GitHub Actions Workflows the Trivy Image Scanning worked normal and took around 30 seconds.
Since some hours now, the scanning times out. Even increasing the timeout to 15 minutes and disabling the secret scanning does not help. Maybe something is wrong with the trivy database?
Please see our output:
Run aquasecurity/trivy-action@master
Running trivy with options: trivy image  --format sarif --vuln-type  os,library --severity  UNKNOWN,LOW,MEDIUM,HIGH,CRITICAL --output  trivy-results.sarif --ignore-policy  ./trivy_ignore.rego  xxxxxxxxxxxxx.dkr.ecr.eu-central-1.amazonaws.com/cccs/centraladdresssearchservice:qa
Global options:
2023-01-12T11:03:15.708Z	INFO	Need to update DB
2023-01-12T11:03:15.708Z	INFO	DB Repository: ghcr.io/aquasecurity/trivy-db
2023-01-12T11:03:15.708Z	INFO	Downloading DB...
27.06 MiB / 36.04 MiB [--------------------------------------------->_______________] 75.09% ? p/s ?36.04 MiB / 36.04 MiB [----------------------------------------------------------->] 100.00% ? p/s ?36.04 MiB / 36.04 MiB [----------------------------------------------------------->] 100.00% ? p/s ?36.04 MiB / 36.04 MiB [---------------------------------------------->] 100.00% 14.94 MiB p/s ETA 0s36.04 MiB / 36.04 MiB [---------------------------------------------->] 100.00% 14.94 MiB p/s ETA 0s36.04 MiB / 36.04 MiB [---------------------------------------------->] 100.00% 14.94 MiB p/s ETA 0s36.04 MiB / 36.04 MiB [---------------------------------------------->] 100.00% 13.98 MiB p/s ETA 0s36.04 MiB / 36.04 MiB [---------------------------------------------->] 100.00% 13.98 MiB p/s ETA 0s36.04 MiB / 36.04 MiB [---------------------------------------------->] 100.00% 13.98 MiB p/s ETA 0s36.04 MiB / 36.04 MiB [-------------------------------------------------] 100.00% 22.16 MiB p/s 1.8s2023-01-12T11:03:18.536Z	INFO	Vulnerability scanning is enabled
2023-01-12T11:03:18.536Z	INFO	Secret scanning is enabled
2023-01-12T11:03:18.536Z	INFO	If your scanning is slow, please try '--security-checks vuln' to disable secret scanning
2023-01-12T11:03:18.536Z	INFO	Please see also https://aquasecurity.github.io/trivy/v0.34/docs/secret/scanning/#recommendation for faster secret detection
2023-01-12T11:08:15.773Z	WARN	Increase --timeout value
2023-01-12T11:08:15.773Z	FATAL	image scan error: scan error: scan failed: failed analysis: analyze error: timeout: context deadline exceeded

I believe this is not our issue. GitHub Container Registry distributing Trivy DB was slow and it caused timeout in my environment. Others saw timeout with search.maven.org. If you are scanning images with JAR/WAR files, it is worth trying --offline-scan. You can set it via trivy.yaml.
https://aquasecurity.github.io/trivy/v0.36/docs/references/customization/config-file/

This worked for me, which should be the same as @knqyf263 comment.
- name: Run Trivy
  uses: aquasecurity/trivy-action@master
  env:
    TRIVY_OFFLINE_SCAN: true
...

That is working for me as well

gonna add a me-too post to keep track ... seems to really affect java projects only. Node / Go projects seem to be running fast as ever 🤷🏻

we've just released a new version of trivy action (https://github.com/aquasecurity/trivy-action/releases/tag/0.9.0) please give it a shot and see if the problem still persists.

It still fails here for OSS DataHub project https://github.com/datahub-project/datahub/actions/runs/4070080489/jobs/7020725786. Started happening 2 days ago.

We currently use aquasecurity/trivy-action@master in our tags. Is using aquasecurity/trivy-action@0.9.0 instead recommended?

This had happened a few weeks ago and we added https://github.com/datahub-project/datahub/pull/7050/files this environment variables based on the github discussions in the issues. But seems that stopped working on 31st-Jan-2023.

aquasecurity/trivy-action@master is using v0.9.0 since today and it is using Trivy v0.37.1 - and it has stopped working with this environment variable for us as well. We changed our pipeline to aquasecurity/trivy-action@0.8.0 and it is working again.

Thanks for the feedback. We’ll another look at it.

I am facing same issue with the @master tag. and getting below error
FATAL	image scan error: scan error: unable to initialize a scanner:
unable to initialize a docker scanner: failed to parse the image name: could not parse reference:
${REGISTRY}/${REPOSITORY}:${IMAGE_TAG}

@b44rawat Your error is something different. The variable is not evaluated well.

repo: aquasecurity/trivy-action


text:
Fix github cron workflow

The Makefile targets were renamed in this PR https://github.com/aquasecurity/trivy-db/pull/65 but the github cron workflow is trying to call the old one and failing.
fixes #87

oops. Thank you so much!

No problemo, trivy has been absolute pleasure to use, thanks for your work!

source: gharchive/pull-request

repo: aquasecurity/trivy-db


text:
Updated project to exclude LinqArray project

Removed Ara3d.LinqArray
Removed Ara3d.LinqArray (which is mission from the repository) is removed from csproj.

The repo currently doesn't have the project, its causing problems when loading the project. So my suggestion would be to leave it out of the repo until the project is accessible by others.


text:
Weekday not Adjusted

This is to fix the [issue #1] (https://github.com/arabiaweather/hijri-date/issues/1)

fixed #1

repo: arabiaweather/hijri-date

license: mit

license_source: bigquery


text:
UPDATE edge._from value throws "document not found (while executing)"

my environment running ArangoDB
I'm using the latest ArangoDB of the respective release series:

3.1

Mode:

Single-Server

Storage-Engine:

mmfiles

On this operating system:

Windows, version: 10

this is an AQL-related issue:
I'm using graph features
I'm issuing AQL via web interface with this browser: Chrome     running on this OS: Win10
The AQL query in question is:
FOR n IN UpgradesToClientGroup
     FOR v,e,p IN 1 OUTBOUND n._from
     HasClientGroup,HasClient
UPDATE e WITH {_from:n._to} IN HasClientGroup

This statement should take all clients from a clientGroup (the edge HasClient) and adds them to another clientGroup by following the UpgradesToClientGroup edge.
The issue can be reproduced using this dataset:
Collections.zip
The following problem occurs: Error Query: document not found (while executing)
Instead I would be expecting: That all clients move to the next client group

Note: was able to reproduce this in 3.1 after renaming the "Clients" collection to "Client" ("Collections.zip" suggests that there should be a collection named "Clients" - instead it must be named "Client").

It seems that the problem is caused by the UPDATE statement referring to collection HasClientGroup.
However, the documents that will be updated are from collection HasClient.
This can be seen by changing the UPDATE part of the query to a simple RETURN statement:
FOR n IN UpgradesToClientGroup
  FOR v,e,p IN 1 OUTBOUND n._from HasClientGroup,HasClient RETURN e

This produces:
[
  {
    "_key" : "6803448",
    "_id" : "HasClient/6803448",
    "_from" : "ClientGroup/6803291",
    "_to" : "Client/6803443",
    "_rev" : "_Vh3mHXy--_",
    "isActive" : true,
    "paysFor" : false
  },
  {
    "_key" : "6803418",
    "_id" : "HasClient/6803418",
    "_from" : "ClientGroup/6803261",
    "_to" : "Client/6803413",
    "_rev" : "_Vh3mHXy--D",
    "isActive" : true,
    "paysFor" : false
  },
  {
    "_key" : "6803428",
    "_id" : "HasClient/6803428",
    "_from" : "ClientGroup/6803276",
    "_to" : "Client/6803423",
    "_rev" : "_Vh3mHXy--C",
    "isActive" : true,
    "paysFor" : false
  }
]

All documents produced are from collection HasClient, but the UPDATE statement will look for them in collection HasClientGroup and won't find them there.
Changing the UPDATE part of the query to update the documents in collection HasClient instead will work:
FOR n IN UpgradesToClientGroup
  FOR v,e,p IN 1 OUTBOUND n._from HasClientGroup,HasClient
  UPDATE e WITH {_from:n._to} IN HasClient

So I think it works as expected.

Sorry I was the mistake:
 FOR n IN UpgradesToClientGroup
     FOR v,e,p IN 1 OUTBOUND n._from
     HasClientGroup,HasClient
 UPDATE e WITH {_from:n._to} IN HasClient

The IN HasClientGroup needs to be a IN HasClient

authors: jsteemann konsultaner

repo: arangodb/arangodb


text:
Coordinator: giving up waiting for unused V8 context when under load

my environment running ArangoDB
I'm using the latest ArangoDB of the respective release series:

[x] 3.2

Mode:

[x] Cluster

Storage-Engine:

[x] rocksdb

On this operating system:

[x] Linux

[x] docker - official docker library
[x] other: I've also used a custom self-built Arango docker image (using the official .deb packages under the hood) but can reproduce this issue with both the official version and the custom build

Hello,
I've been running some load tests against a three node (an instance of agency, coordinator and primary on each) cluster. This is done using an application reading and writing into arango (using the Java driver) rather than arangobench. As part of the load test a few operations are performed - to the best of my knowledge it's two documents being created, one of them being read and subsequently also updated. This cycle is performed concurrently by many application threads and the end goal of the test is to get to 1mln documents in two collections (1mln documents in each one of them). So far we've been having much better results with the 3.2 series using RocksDB but we're currently running into an issue every few hours where the coordinator node stops responding.
At the time the coordinator starts acting up we start seeing messages like these in the logs:
arangodb-coordinator_1          | 2017-09-19T23:59:48Z [16] WARNING {memory} process is near the maximum number of memory mappings. current: 64507, maximum: 65530
arangodb-coordinator_1          | 2017-09-20T00:00:08Z [16] WARNING {memory} process is near the maximum number of memory mappings. current: 64551, maximum: 65530
arangodb-coordinator_1          | 2017-09-20T00:00:18Z [16] WARNING {memory} process is near the maximum number of memory mappings. current: 64539, maximum: 65530
arangodb-coordinator_1          | 2017-09-20T00:00:28Z [16] WARNING {memory} process is near the maximum number of memory mappings. current: 64539, maximum: 65530
arangodb-coordinator_1          | 2017-09-20T00:00:38Z [16] WARNING {memory} process is near the maximum number of memory mappings. current: 64539, maximum: 65530
arangodb-coordinator_1          | 2017-09-20T00:00:49Z [16] WARNING {memory} process is near the maximum number of memory mappings. current: 64539, maximum: 65530
arangodb-coordinator_1          | 2017-09-20T00:00:59Z [16] WARNING {memory} process is near the maximum number of memory mappings. current: 64539, maximum: 65530
arangodb-coordinator_1          | 2017-09-20T00:01:08Z [16] WARNING {v8} giving up waiting for unused V8 context after 60.000000 s
arangodb-coordinator_1          | 2017-09-20T00:01:08Z [16] WARNING {v8} giving up waiting for unused V8 context after 60.000000 s
arangodb-coordinator_1          | 2017-09-20T00:01:08Z [16] WARNING {v8} giving up waiting for unused V8 context after 60.000000 s
arangodb-coordinator_1          | 2017-09-20T00:01:08Z [16] WARNING {v8} giving up waiting for unused V8 context after 60.000000 s
arangodb-coordinator_1          | 2017-09-20T00:01:09Z [16] WARNING {memory} process is near the maximum number of memory mappings. current: 64540, maximum: 65530
arangodb-coordinator_1          | 2017-09-20T00:01:09Z [16] WARNING {v8} giving up waiting for unused V8 context after 60.000000 s
arangodb-coordinator_1          | 2017-09-20T00:01:09Z [16] WARNING {v8} giving up waiting for unused V8 context after 60.000000 s
arangodb-coordinator_1          | 2017-09-20T00:01:09Z [16] WARNING {v8} giving up waiting for unused V8 context after 60.000000 s
arangodb-coordinator_1          | 2017-09-20T00:01:09Z [16] WARNING {v8} giving up waiting for unused V8 context after 60.000000 s
arangodb-coordinator_1          | 2017-09-20T00:01:09Z [16] WARNING {v8} giving up waiting for unused V8 context after 60.000000 s
arangodb-coordinator_1          | 2017-09-20T00:01:09Z [16] WARNING {v8} giving up waiting for unused V8 context after 60.000000 s
arangodb-coordinator_1          | 2017-09-20T00:01:09Z [16] WARNING {v8} giving up waiting for unused V8 context after 60.000000 s

This looks very similar to #2324 so I've added some v8 tweaks on the command line:
--javascript.v8-contexts 5 --javascript.v8-max-heap 3072
but unfortunately this doesn't seem to make much difference. This issue usually starts occurring after 5-6 hours of testing and the v8 flags don't seem to influence this timing much.
Here's what the memory usage looks like for this particular coordinator node:

Here's the CPU usage:

(the above are container metrics obtained using cAdvisor)
Here's the HTTP requests served by the server nodes:

(these are obtained from the Arango API - different colours are different HTTP verbs)
As you can see there's a very slight jump in CPU usage at the same time http requests stop being forwarded to the server and afterwards the memory usage starts growing. I'm happy to share the full Grafana dashboard privately if this helps!
After restarting the affected coordinator node the load test goes straight back to normal - the application picks another coordinator node and continues processing.

sorry - the enter key seems to have created an issue instead of a newline! updating the contents now.

We recently found that it may help in this context to increase the value of a kernel parameter, as specified here.
The Linux default value for /proc/sys/vm/max_map_count seems to be rather low for a powerful server with many cores and many parallel threads, so increasing it may allow a process (i.e. arangod) to use more memory mappings than the default 64K.
Additionally, the number of V8 contexts (--javascript.v8-contexts) may need to be increased a bit. It seems you set it 5, but this will mean that if there are more than 5 threads in parallel that require the usage of V8, the other threads will block.
Can you try the adjusted settings to see if that fixes the problem?

I had the same issue. Increasing max_map_count, v8-contexts, threads and the frequency of V8 GC it seems solved.
This doesn't happen to us with 3.1.X or prior versions, it started when we migrated to 3.2. Also happened to us in a clean installation.

It took a lot of time but one of our coordinators get the same issue.
2017-09-23T09:01:13Z [1] WARNING {memory} process is near the maximum number of memory mappings. current: 255044, maximum: 256000
2017-09-23T09:01:23Z [1] WARNING {memory} process is near the maximum number of memory mappings. current: 255046, maximum: 256000
2017-09-23T09:05:59Z [1] WARNING {memory} process is near the maximum number of memory mappings. current: 255001, maximum: 256000
2017-09-23T09:06:09Z [1] WARNING {memory} process is near the maximum number of memory mappings. current: 255009, maximum: 256000
2017-09-23T09:06:19Z [1] WARNING {memory} process is near the maximum number of memory mappings. current: 255014, maximum: 256000
2017-09-23T09:06:29Z [1] WARNING {memory} process is near the maximum number of memory mappings. current: 255017, maximum: 256000
2017-09-23T09:06:39Z [1] WARNING {memory} process is near the maximum number of memory mappings. current: 255021, maximum: 256000
2017-09-23T09:06:49Z [1] WARNING {memory} process is near the maximum number of memory mappings. current: 255022, maximum: 256000
2017-09-23T09:06:59Z [1] WARNING {memory} process is near the maximum number of memory mappings. current: 255022, maximum: 256000
2017-09-23T09:07:11Z [1] WARNING {memory} process is near the maximum number of memory mappings. current: 255022, maximum: 256000
2017-09-23T09:07:25Z [1] WARNING {memory} process is near the maximum number of memory mappings. current: 255022, maximum: 256000
2017-09-23T09:07:36Z [1] WARNING {memory} process is near the maximum number of memory mappings. current: 255024, maximum: 256000
2017-09-23T09:07:49Z [1] WARNING {memory} process is near the maximum number of memory mappings. current: 255024, maximum: 256000
2017-09-23T09:08:00Z [1] WARNING {memory} process is near the maximum number of memory mappings. current: 255024, maximum: 256000
2017-09-23T09:08:10Z [1] WARNING {memory} process is near the maximum number of memory mappings. current: 255021, maximum: 256000
2017-09-23T09:08:20Z [1] WARNING {memory} process is near the maximum number of memory mappings. current: 255026, maximum: 256000
2017-09-23T09:08:30Z [1] WARNING {memory} process is near the maximum number of memory mappings. current: 255026, maximum: 256000
2017-09-23T09:09:35Z [1] WARNING {memory} process is near the maximum number of memory mappings. current: 255026, maximum: 256000
2017-09-23T09:09:45Z [1] WARNING {memory} process is near the maximum number of memory mappings. current: 255030, maximum: 256000
2017-09-23T09:09:55Z [1] WARNING {memory} process is near the maximum number of memory mappings. current: 255031, maximum: 256000

In this case the config of the coordinator is:
[server]
authentication = true
endpoint = tcp://[::]:8529
threads = 16
jwt-secret = ***
[log]
level = info
[javascript]
v8-contexts = 32
gc-frequency = 10
gc-interval = 128
[database]
index-threads = 4

Thanks @jsteemann - running more tests now after increasing max_map_count (as well as doubling v8 contexts). So far so good but it usually takes about 6hrs before I hit this issue so I'll report once the test is complete later on.
I've read through all the tuning recommendations that you've linked (as well as implemented all of them before re-testing) and I have a couple of questions:

The docs specify a rule of thumb for calculating the max_map_count value - when I follow this the resulting value is lower than the default as I'm running tests on a 2-core system (but with 15G of ram and very fast storage). I've resorted to making it 262144 as this seems to be a very common tweak for Elasticsearch as well and that's the value a lot of articles seem to recommend. Should 256k be the de-facto recommended value regardless of the number of cores?
There seems to be a bit of a discrepancy in the overcommit_memory setting - the docs specify this should be 0 however looking at the logs of the server and coordinator nodes I get this message:
WARNING {memory} /proc/sys/vm/overcommit_memory is set to '0'. It is recommended to set it to a value of 2
Which one is correct?

Thanks for coming back. I have created a PR to change the documentation and to increase the recommended default values.

Thanks @jsteemann! I can confirm now that the load test has finished successfully and I believe max_map_count is what solved the issue here. I'm running a higher throughput test now to verify again but things are looking good.

I can definitely confirm that this problem has been resolved for me now. Thanks for your help @jsteemann!

Ok, Thanks a lot for confirming.

@dothebart in our case logs have disappeared, the process just finish when the map limit is reached (checked with pmap). Should I open other issue? Is the same case :S

You need to increase the available mappings. The current way jemalloc handles this isn't the best way - we're working on analysing whether we find a better way of doing this.
Eventually you may want to start more coordinators to better distribute the mappings across more processes. Please report back if neither of both solves the issue.

@dothebart the mappings allowed in our systems is around 2.5 millions, it take some hours due to the volume of queries we have to reach that value.
The current config is the suggested:
sudo bash -c "echo madvise >/sys/kernel/mm/transparent_hugepage/enabled"
sudo bash -c "echo madvise >/sys/kernel/mm/transparent_hugepage/defrag"
sudo bash -c "echo 0 >/proc/sys/vm/overcommit_memory"
sudo bash -c "echo 0 >/proc/sys/vm/zone_reclaim_mode"
sudo bash -c "sysctl -w 'vm.max_map_count=2500000'"
export GLIBCXX_FORCE_NEW=1

All the config is permanent. Also we have tested with echo 2 >/proc/sys/vm/overcommit_memory and it usually resist more hours. Also we tried with numactl --interleave=all even when our system isn't NUMA enabled, no improvements found with this change.
Currently we have 9 coordinators working, so load balancing between them are the only way to not suffer this bug.
Thanks for all your efforts, I'm pretty sure you will fix it in an elegant way and soon 😃

You should be able to increase the max mapping count even more.
We're currently adding monitoring for this to collectd: https://github.com/collectd/collectd/pull/2454
so we can trace it a bit better throughout loadtests.

That's perfect! I will check it this afternoon :) Thanks

I have a configuration where I have 8 nodes with 8 coordinators and 8 db servers and 3 agents. After reading the above discussion I had set the value of max mapping count = 848000 = 256000.
After 14 days, the memory mapping limit was reached.
I understand that I can increase the memory mappings to a higher value but looks like the problem will then occur at a later time, but definitely occur : O.
Is there a fix for this coming out in 3.3?
Thanks!

Hi,
we recently learned, that the V8 engine included in 3.2 has a memory leak.
We're currently working on 3.2.7 with a fixed version of V8.

3.2.7 is out today, I see that we have increased the number of initial V8 contexts,but I did not see a memory fix for the V8 engine, is that covered? Did I miss anything?

Hi,
Yes the V8 engine has also been upgraded.

authors: choppedpork dashdeep13 dothebart javiergarmon jsteemann


text:
Databases should be able to have their own defaults

At the moment defaults are set in config files/ command options.
But databases might have their specific needs in defaults and changing some default server-wide might introduce an issue in a database, if for example journal size is changed in the global  scope, it might affect a specific database's collection journal.
Same might happen with wait_for_sync or other default values that are inherited further down the database level.
Therefore it would be good for Databases to have their own default values, that can be picked up by any database objects. Only in the event where a database default is not set, it would mean to use the server default.
What do you think?

at the time being there are defaults for replication factor and sharding on per database basis.

authors: dothebart frankmayer


text:
Bug fix 3.7/internal issue #762

Scope & Purpose
(Please describe the changes in this PR for reviewers)

[ ] :hankey: Bugfix
[ ] :pizza: New feature
[ ] :hammer: Refactoring
[ ] :book: CHANGELOG entry made
[ ] :muscle: The behavior in this PR was manually tested
[ ] :computer: The behavior change can be verified via automatic tests

Backports:

[ ] No backports required
[ ] Backports required for: (Please specify versions)

Related Information
(Please reference tickets / specification etc)

[ ] Docs PR:
[ ] Enterprise PR:
[ ] GitHub issue / Jira ticket number:
[ ] Design document:

Testing & Verification
(Please pick either of the following options)

[ ] This change is a trivial rework / code cleanup without any test coverage.
[ ] This change is already covered by existing tests, such as (please describe tests).
[ ] This PR adds tests that were used to verify all changes:

[ ] Added Regression Tests
[ ] Added new C++ Unit Tests
[ ] Added new integration tests (i.e. in shell_server / shell_server_aql)
[ ] Added new resilience tests (only if the feature is impacted by failovers)

Additionally:

[ ] There are tests in an external testing repository:
[ ] I ensured this code runs with ASan / TSan or other static verification tools

(Include link to Jenkins run etc)
Documentation

All new Features should be accompanied by corresponding documentation.
Bugs and features should furthermore be documented in the changelog so that
developers and users have a concise overview.

[ ] Added a Changelog Entry (referencing the corresponding public or internal issue number)
[ ] Added entry to Release Notes
[ ] Added a new section in the Manual
[ ] Added a new section in the HTTP API
[ ] Added Swagger examples for the HTTP API
[ ] Updated license information in LICENSES-OTHER-COMPONENTS.md for 3rd party libraries

External contributors / CLA Note
Please note that for legal reasons we require you to sign the Contributor Agreement
before we can accept your pull requests.

Closed in favor of https://github.com/arangodb/arangodb/pull/13146 which covers this issue too.


text:
Small cleanup of caching code

Scope & Purpose
Address some TODOs that were raised in handover of caching code.

[ ] :hankey: Bugfix (requires CHANGELOG entry)
[ ] :pizza: New feature (requires CHANGELOG entry, feature documentation and release notes)
[ ] :fire: Performance improvement
[x] :hammer: Refactoring/simplification
[ ] :book: CHANGELOG entry made

Testing & Verification
Link to Jenkins PR run: https://jenkins.arangodb.biz/view/PR/job/arangodb-matrix-pr/13326/ (all blue)

https://jenkins.arangodb.biz/view/PR/job/arangodb-matrix-pr/13330/

https://jenkins.arangodb.biz/view/PR/job/arangodb-matrix-pr/13339/


text:
[CINFRA-612] Handle shard creation errors

Scope & Purpose
When a collection is created, we start creating the corresponding replicated state, which in turn starts creating the core. The core is responsible for creating the shard, but for that, it needs to look up the collection properties in the agency. There is a slight race in there, because the collection could get removed, before the core gets to look up the properties, in which case it will find nothing.
Currently we crash the server with an error message. This PR makes getCollectionPlan return a ResultT. The DocumentCore checks the value and throws and exception in case something went wrong. This would get caught by UpdateReplicatedStateAction.

[ ] :hankey: Bugfix
[x] :pizza: New feature
[ ] :fire: Performance improvement
[ ] :hammer: Refactoring/simplification

This is a valid solution. I wonder though, would it be possible to pass on that information? What I mean is, when the creation of the state is being triggered, I suppose we already have some version of the Plan in hand. Could the collection properties be taken from there and passed down to the Core constructor, so we use the same "snapshot", so this kind of error can't occur? Or is that infeasible?

I suppose we already have some version of the Plan in hand. Could the collection properties be taken from there and passed down to the Core constructor, so we use the same "snapshot", so this kind of error can't occur? Or is that infeasible?

This might be possible. When we pass down the collection ID to the core, we have access to the ClusterCollectionCreationInfo structure. Among a few other member variables, this contains a velocypack::Slice json. I will check that out, maybe it contains the plan information for the collection. I have to investigate this a bit further and see whether it's feasible.

This PR is currently waiting for #17679, since there's been a refactoring of the shard creation code in there.

Due to a current refactoring, this PR is no longer relevant. The core is no longer responsible for creating the shard. This is done by the maintenance on the leader, which write a CreateShard entry into the log.

authors: apetenchea goedderz


text:
fix windows warnings / compile errors

fix compiler warnings / errors on windows

http://jenkins01.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/4786/

Can you try to include this commit from 3.4?
4982ca6
Fixed the issue there.

Ok just checked the source for above commit is not present in devel, so will not help either.
@fceller and me suspect some misconfiguration now, we did trigger a rerun.
https://jenkins.arangodb.biz/view/PR/job/arangodb-matrix-pr/4798/

Ok latest jenkins is green.
Thank you!!!

authors: dothebart mchacki


text:
Realisation relationship not allowed between Technology artifact and Application Data Object

I have tried in both Archi 4.0.0 beta3 and 4 to create a realisation relationship between an artifact and data object and it is not allowed... although I believe it should. Could you help me out?

Is the relationship in the matrix in the ArchiMate 3 spec? Or is it one for the list @jbsarrodie ?

It is already on @jbsarrodie  list.
@pannema - temporarily you can allow it if you edit relationships.xml file inside model plugin and add allowance for this and other missing relationships

Thanks both Phillipus and pjjv! The workaround works as a charm :-)

authors: Phillipus pannema pjjv

repo: archimatetool/archi


text:
Update LangVersion. Consolidate styling and conventions.

Closes #342, Closes #343. This was a tedious job, but it had to be done.

Updated C# version to 11.
Consolidated project files (.csproj)
Consolidated test project files and updated report generation.
Updated pipelines - use NET 7 SDK (we need it for C#11), fix docker files, etc.
Updated .editorconfig and applied the styling.
Manually updated all inconsistencies (the usage of this and all other details).
Added config to ignore some warnings related to missing XML comments (it was polluting the output, and we were missing more important stuff). Ignored the following warning:

1591 Missing XML comment for publicly visible type or member 'Type_or_Member'
1573 Parameter 'parameter' has no matching param tag in the XML comment for 'parameter'
1712 Type parameter 'type parameter' has no matching typeparam tag in the XML comment on 'type'

Other fixes and cleanup.

Note: @ardalis the 2-space indent is making the code hard to read (e.g. check this file). I do understand that you like that style, but if you change your mind let me know :)

Hide whitespaces while reviewing, otherwise it's overwhelming.

This was... big. :)

authors: ardalis fiseni

repo: ardalis/Specification


text:
Implement Rate Limiting on Requests

To enhance the stability and performance of our load balancer, we need to introduce a rate limiting feature that restricts the number of requests sent to each backend service to a specified limit per second. This implementation will provide a default global limit, with the ability to override this limit for individual backends.
Requirements:

Global Rate Limit: Define a default global rate limit for requests per second across all backends.

Override for Individual Backends: Allow each backend to specify its own rate limit, overriding the global setting.

Configuration Options:

A global configuration option (e.g., global_requests_per_second) for the default rate limit.
Backend-specific configuration (e.g., backend_requests_per_second) to set individual limits.

Handle Exceeding Limits: Ensure that appropriate responses are returned when the defined limit is exceeded (e.g., HTTP 429 Too Many Requests).

Hi @ardatosun
I can pick this up if that is okay ?

You are on fire @ohyesgocool, sure 😄

authors: ardatosun ohyesgocool

repo: ardatosun/loadbalancer


text:
Update URL of "ArreyExt"

Companion to https://github.com/arduino/library-registry/pull/1265

Made pointless by library maintainer shenanigans: https://github.com/arduino/library-registry/pull/1268

repo: arduino/library-registry


text:
Copy config files after compilation

Motivation

After compilation, the developer should be able to start any project without additional effort. At this moment, to start IPC project or to configure logging, after compilation with cmake, the developer needs manually create config subdirectory and copy log.init and router.init files in the folder of binaries. For example, compiling with msvc and make automatically do this action.
make under Linux compiles and creates binaries with extension .out and msvc compiles binaries with extension .exe.
Both, make and msvc compile with incremental build, which is much faster and does not require to recompile all projects.

What to do

After compilation of binaries with cmake, create config subfolder in the binary output folder bin (i.e. in bin/config) if it is not existing, and copy files log.init used by logging and router.init used for IPC.
When compile under Linux, add .out extension to executable binaries, i.e. the mcrouter is mcrouter.out. No need to make this change for Windows, because the compiler automatically adds extension .exe.
Support incremental build with cmake at least for Debug configuration, so that there will be no need to rebuild all projects after each small change.

Hi @Ali-Nasrolahi,
I'll be very thankful if you extend cmake support: copy config files, change binary extensions and make build incremental.
FYI, probably it helps. In the Makefile of areg project, written by @biwiki, at the end there are scripts:
@mkdir -p $(AREG_OUTPUT_BIN)/config
@cp $(areg_BASE)/resources/log.init $(areg_BASE)/resources/router.init $(AREG_OUTPUT_BIN)/config/

Many thanks in advance!

Hello @aregtech,
I understood the first two TODOs , however the third one (incremental build) is little bit vague to me.
Could you explain/reference a more detailed description?
Thanks a lot!

The incremental compiler

Quite naturally, whereas ordinary compilers make a so-called clean build, that is, (re)build all program modules, an incremental compiler recompiles only modified portions of a program.

It means that the compiler checks the timestamp of source and compiled file, and compiles only if source has been changed. It also checks the dependencies, i.e. if file a.hpp is included in a.cpp and b.cpp, and not included in c.cpp, the modification of a.hpp will cause re-build of a.cpp and b.cpp, but not c.cpp.
The expectation is that when in areg framework, compiled as shared library, make modifications not related with examples, the examples are not compiled. Or if make changes only in an example project, it will not require compilation of all entire codes, but only that particular project.
I know how to enable / disable in MSVS, but don't know how to do that in CMake. Might be possible, it is a compiler specific option.
Maybe @biwiki helps / gives a hint when finds a little time 🙂 He implemented that for make and it works.

Thanks, I will look into it.

authors: Ali-Nasrolahi aregtech

repo: aregtech/areg-sdk


text:
License update

I'm submitting a ...

[x] feature request

Expected Behavior
There should be a LICENSE file that covers the entire repository.
Actual Behavior
Currently, there is no License file covering the whole repository.
My uncertainty with which License to give this repository is that other Moltres projects had LGPL Licenses, which are viral. This appears to be something that interacts with Moltres, but I can't ascertain if it is a direct derivative of the original program.
How can this issue be closed?
First, a determination has to be made about the type of License under which to cover this repository.
Second, that License should then be added through a pull request to this repository.
Side Tangent
I tried to add this issue to the meta repository. The only projects that show up for this repository are Cyder, Moltres, i2cner, and Fuel Cycles. Also, the labels are not consistent with the rest of the organization.

This is mostly a paper directory. I don't think there's much code (double check). So, CC-BY.

repo: arfc/moltres-init


text:
[FEATURE]Auto-annotation of Repeated Tokens

Is your feature request related to a problem? Please describe.
There are situations when same bigrams,trigrams, etc appear multiple times in a text being annotated. The annotator has to repeatedly annotate the n-grams, else the tokens will be labelled as "0" under IOB scheme by default.
Describe the solution you'd like
Currently, Argilla UI enables us to annotate/label tokens in a text with an easy-to-use interface. However, I've identified a use case where an additional feature could enhance efficiency:
Sample claim text:
The method of claim 1 that includes the step of locating said pillow directly between a tympanic membrane and a round window membrane, but without contacting the round window membrane to block the approach of the tympanic membrane into close proximity to said round window membrane.

Assume we have labels like: ["method of use", "product", "machine", "system"]
Here first occurrence of token tympanic membrane is labelled as product by annotator. Since there are multiple instances of the tympanic membrane, the annotator must annotate each instance appropriately, else the system implicitly annotates them as 'O' per the IOB scheme to each token of the bigram. This makes it harder for the model to learn that "tympanic membrane" is a product and shouldn't be treated as two different tokens "tympanic" and "membrane".
Proposed Improvement
When an annotator labels a token (e.g., "tympanic membrane" as "product"), the system could automatically identify and suggest the same label for all exact matches of that token in the text. This would:
Reduce repetitive labeling actions
Save significant time, especially in longer texts with recurring terms
Ensure consistency in labeling across the document
Prevent accidental omissions that could lead to incorrect 'O' labels in the IOB scheme

@nataliaElv, seems like an interesting feature that has some overlap with bulk for span questions.

@frascuchon would this be easier now that we have the advanced queries included.

repo: argilla-io/argilla


text:
WIP: Support mas login

Add support to login to MAS with mas login --appleId <apple_id> --password <password>
You can install this version of mas with
brew install cybertk/formulae/mas --HEAD --env=std

Current TODOs:

[ ] Prettify execution log
[ ] Updated usage guide
[ ] Give better instructions to enable Accessibility Permission

Just saw this. I'm not comfortable including arbitrary AppleScript in the app at the moment. Have you checked whether this can be done in the SDK directly? If not is there a way to perform the accessibility commands directly from Cocoa instead of embedded AppleScript?

I spent a long time to find how to login with API in CommerceKit and StoreFoundation, but no progress.
What do you mean is there a way to perform the accessibility commands directly from Cocoa

I cannot find a CLI way to grant mas Accessibility Permission on El Capitan. I tried jacobsalmela/tccutil with tccutil -i /path/to/mas, but it does not work.
I also observed that

When running mas in Terminal.app, grant Accessibility Permission to Terminal.app is worked
When running mas in Xcode(Debug),  grant Accessibility Permission to Xcode.app is worked

I am referring to this API https://developer.apple.com/library/mac/documentation/ApplicationServices/Reference/AXUIElement_header_reference/ instead of using AppleScript.

Did you update the headers to see the API that I trimmed from the PrivateHeaders in the repository? If you pull the latest master (I had to fix something) and call script/update_headers you will see a lot more header files.
I have identified some headers which are worth exploration:
mas-cli/PrivateHeaders/CommerceKit/CKAccountAuthentication.h
mas-cli/PrivateHeaders/StoreFoundation/ISAccountService-Protocol.h
mas-cli/PrivateHeaders/StoreFoundation/ISAuthenticationChallenge.h
mas-cli/PrivateHeaders/StoreFoundation/ISSignInPrompt.h
mas-cli/PrivateHeaders/StoreFoundation/ISStoreAuthenticationChallenge.h

There should be enough API's to perform a sign in without showing any UI as that is the full API that the App Store app uses.

I agree with you @argon. After some experiments I found it's not some direct APIs calls to implement login, it more like some of these APIs are depended on the others. If we can know how Apple's MAS using those APIs, there would be easier to understanding the login flow.

I have added this command here d80ad6e866378504c11aeb2e47692977954bd05d.
It is included in v1.1.0 which is available from Homebrew

You are aaaaaawesome. How can you find find the login flow? I'm very curious about that.

I spent a couple of hours exploring StoreFoundation.framework (and friends) with a debugger and experimenting with the different code paths I found. It took a lot of trial and error before I noticed that the demo mode override was triggered before any other UI and it worked perfectly

authors: argon cybertk

repo: argon/mas


text:
Fixed potential insufficient samples due to num_files is not divisible by comm.size

This might cause hang, an alternative solution to #198

I get that error message:
Set the environment variable HYDRA_FULL_ERROR=1 for a complete stack trace.
Traceback (most recent call last):
  File "/root/measure/storage/dlio_benchmark/dlio_benchmark/main.py", line 394, in main
    benchmark.run()
  File "/usr/local/lib/python3.10/dist-packages/dlio_profiler/logger.py", line 183, in wrapper
    x = func(*args, **kwargs)
  File "/root/measure/storage/dlio_benchmark/dlio_benchmark/main.py", line 333, in run
    self.framework.get_loader(dataset_type=DatasetType.TRAIN).read()
  File "/usr/local/lib/python3.10/dist-packages/dlio_profiler/logger.py", line 183, in wrapper
    x = func(*args, **kwargs)
  File "/root/measure/storage/dlio_benchmark/dlio_benchmark/data_loader/tf_data_loader.py", line 98, in read
    epoch_number=0).next()
  File "/usr/local/lib/python3.10/dist-packages/dlio_profiler/logger.py", line 183, in wrapper
    x = func(*args, **kwargs)
  File "/root/measure/storage/dlio_benchmark/dlio_benchmark/reader/tf_reader.py", line 110, in next
    total = math.float(len(self._file_list)/self._args.comm_size / self.batch_size * self._args.num_samples_per_file)
AttributeError: module 'math' has no attribute 'float'

Set the environment variable HYDRA_FULL_ERROR=1 for a complete stack trace.

If I replace math.float with float i get that:
Set the environment variable HYDRA_FULL_ERROR=1 for a complete stack trace.
Traceback (most recent call last):
  File "/root/measure/storage/dlio_benchmark/dlio_benchmark/main.py", line 394, in main
    benchmark.run()
  File "/usr/local/lib/python3.10/dist-packages/dlio_profiler/logger.py", line 183, in wrapper
    x = func(*args, **kwargs)
  File "/root/measure/storage/dlio_benchmark/dlio_benchmark/main.py", line 333, in run
    self.framework.get_loader(dataset_type=DatasetType.TRAIN).read()
  File "/usr/local/lib/python3.10/dist-packages/dlio_profiler/logger.py", line 183, in wrapper
    x = func(*args, **kwargs)
  File "/root/measure/storage/dlio_benchmark/dlio_benchmark/data_loader/tf_data_loader.py", line 98, in read
    epoch_number=0).next()
  File "/usr/local/lib/python3.10/dist-packages/dlio_profiler/logger.py", line 183, in wrapper
    x = func(*args, **kwargs)
  File "/root/measure/storage/dlio_benchmark/dlio_benchmark/reader/tf_reader.py", line 111, in next
    return self._dataset.take(total*self._args.epochs).prefetch(buffer_size=self._args.prefetch_size)
  File "/usr/local/lib/python3.10/dist-packages/tensorflow/python/data/ops/dataset_ops.py", line 1561, in take
    return take_op._take(self, count, name=name)
  File "/usr/local/lib/python3.10/dist-packages/tensorflow/python/data/ops/take_op.py", line 24, in _take
    return _TakeDataset(self, count, name=name)
  File "/usr/local/lib/python3.10/dist-packages/tensorflow/python/data/ops/take_op.py", line 33, in __init__
    self._count = ops.convert_to_tensor(count, dtype=dtypes.int64, name="count")
  File "/usr/local/lib/python3.10/dist-packages/tensorflow/python/profiler/trace.py", line 183, in wrapped
    return func(*args, **kwargs)
  File "/usr/local/lib/python3.10/dist-packages/tensorflow/python/framework/ops.py", line 696, in convert_to_tensor
    return tensor_conversion_registry.convert(
  File "/usr/local/lib/python3.10/dist-packages/tensorflow/python/framework/tensor_conversion_registry.py", line 234, in convert
    ret = conversion_func(value, dtype=dtype, name=name, as_ref=as_ref)
  File "/usr/local/lib/python3.10/dist-packages/tensorflow/python/framework/constant_op.py", line 335, in _constant_tensor_conversion_function
    return constant(v, dtype=dtype, name=name)
  File "/usr/local/lib/python3.10/dist-packages/tensorflow/python/ops/weak_tensor_ops.py", line 142, in wrapper
    return op(*args, **kwargs)
  File "/usr/local/lib/python3.10/dist-packages/tensorflow/python/framework/constant_op.py", line 271, in constant
    return _constant_impl(value, dtype, shape, name, verify_shape=False,
  File "/usr/local/lib/python3.10/dist-packages/tensorflow/python/framework/constant_op.py", line 284, in _constant_impl
    return _constant_eager_impl(ctx, value, dtype, shape, verify_shape)
  File "/usr/local/lib/python3.10/dist-packages/tensorflow/python/framework/constant_op.py", line 296, in _constant_eager_impl
    t = convert_to_eager_tensor(value, ctx, dtype)
  File "/usr/local/lib/python3.10/dist-packages/tensorflow/python/framework/constant_op.py", line 103, in convert_to_eager_tensor
    return ops.EagerTensor(value, ctx.device_name, dtype)
TypeError: Cannot convert 39.09375 to EagerTensor of dtype int64

Set the environment variable HYDRA_FULL_ERROR=1 for a complete stack trace.

It seems to work now:
./benchmark.sh run --hosts myhost --workload resnet50 --param reader.read_threads=4 --accelerator-type h100 --num-accelerators 8  --results-dir fakeres --param dataset.num_files_train=100 --param dataset.data_folder=/mnt/nfs_clientshare/resnet50

With the PR (1 epochs)
[INFO] Averaged metric over all epochs
[METRIC] ==========================================================
[METRIC] Number of Simulated Accelerators: 8
[METRIC] Training Accelerator Utilization [AU] (%): 98.6350 (0.2730)
[METRIC] Training Throughput (samples/second): 13967.4690 (104.5302)
[METRIC] Training I/O Throughput (MB/second): 1527.3199 (11.4302)
[METRIC] train_au_meet_expectation: success
[METRIC] ==========================================================
 [/root/measure/storage/dlio_benchmark/dlio_benchmark/utils/statscounter.py:185]

With main:
[INFO] 2024-06-07T08:27:18.153579 Maximum number of steps reached [/root/measure/storage/dlio_benchmark/dlio_benchmark/main.py:290]
[INFO] 2024-06-07T08:27:18.153864 Ending block 1 - 39 steps completed in 9.07 s [/root/measure/storage/dlio_benchmark/dlio_benchmark/utils/statscounter.py:282]
[INFO] 2024-06-07T08:27:18.154736 Epoch 1 - Block 1 [Training] Accelerator Utilization [AU] (%): 97.3939 [/root/measure/storage/dlio_benchmark/dlio_benchmark/utils/statscounter.py:285]
[INFO] 2024-06-07T08:27:18.154918 Epoch 1 - Block 1 [Training] Throughput (samples/second): 13756.4333 [/root/measure/storage/dlio_benchmark/dlio_benchmark/utils/statscounter.py:286]

(hangs)


text:
Doesn't handle different registry structures well?

Describe the bug
If registry in the source spec and the desired target registry have different structures it seems to mix and match them (or something).
For example my annotations might be this:
annotations:
    argocd-image-updater.argoproj.io/image-alias.force-update: "true"
    argocd-image-updater.argoproj.io/image-alias.kustomize.image-name: registry.gitlab.com/my/group/fluent-bit:1.5.2
    argocd-image-updater.argoproj.io/image-list: image-alias=registry-1.docker.io/fluent/fluent-bit:1.5
    argocd-image-updater.argoproj.io/write-back-method: git:secret:argocd/git-creds

where registry.gitlab.com/my/group/fluent-bit:1.5.2 is whats there in the repo which Id like to be replaced/updated
and registry-1.docker.io/fluent/fluent-bit:1.5 is just a simple docker hub reference for testing as a proof of concept
but this results in trying to list tags at: https://registry.gitlab.com/my/group/v2/fluent/fluent-bit
Why is it trying to do a Get at "https://registry.gitlab.com/my/group/v2/fluent/fluent-bit"?
fluent/fluent-bit is from the image-alias.kustomize.image-name annotation, but its appending that to:  registry.gitlab.com/my/group, which I provided with the image and tag directly "fluent-bit:1.5.2" (so theres no fluent/fluent-bit to be found there)
so I can't tell exactly how its building these paths but it looks like its mixing and matching them wrongfully.
To Reproduce
In your annotations have 2 registries that have differing paths:
argocd-image-updater.argoproj.io/image-alias.kustomize.image-name: registry.gitlab.com/path/one/image:tag
argocd-image-updater.argoproj.io/image-list: image-alias=registry-1.docker.io/pathtwo/image:tag
and it will try to do a get using the first annotation but it will use the path from the second, which it will not find.
Or perhaps something else is going on but I cannot figure it out.
Expected behavior
I'm not sure which registry the Get call is trying to figure out (if its for the original or replacemnt) but If its trying to do a get at https://registry.gitlab.com/my/group/v2/fluent/fluent-bit/tags/list
then it should have done https://registry.gitlab.com/my/group/v2/fluent-bit/tags/list (without the fluent).
Or it could be the opposite it should have taken the fluent/fluent-bit and looked for it at docker hub.
Additional context
ive also tried docker.io/fluent/fluent-bit:1.5 or nothing (just fluent/fluent-bit:1.5, assuming its claim that it has docker hub by default), and it still tries to find the tags at https://registry.gitlab.com/my/group/v2/fluent/fluent-bit/tags/list
Is it the case that this tool expects two different registries to have identical structure/pathing? for example in the docs it uses 2 different registries, but both have the same argoproj/argocd path.
Version
I used latest as of this morning which appears to be v0.9.5
Logs
Get "https://registry.gitlab.com/my/group/v2/fluent/fluent-bit/tags/list\": http: non-successful response (status=404 body="404 page not found\n")" alias=image-alias application=fluentbit-es image_name=my/group/fluent-bit image_tag=1.5.2 registry=registry.gitlab.com

As an update, i only seem to be having this issue with kustomize. That attempt to "GET" seems to be at the root of the issue.
I was able to accomplish the same with helm using image updater, these annotations which mirror the same goal worked:
argocd-image-updater.argoproj.io/image-list: jaeger-alias=docker.io/jaegertracing/jaeger-operator:1.21.2
argocd-image-updater.argoproj.io/jaeger-alias.helm.image-name: image.repository
argocd-image-updater.argoproj.io/jaeger-alias.helm.image-tag: image.tag
argocd-image-updater.argoproj.io/write-back-method: git:secret:argocd/writeback-creds
argocd-image-updater.argoproj.io/jaeger-alias.force-update: "true"

main difference is that I don't have to specify registry.gitlab.com/my/group/image:tag, which is what its provided in the actual values.yaml, so this successfully overrode it with the public docker image. and it never tried to do a GET for jaegertracing/jaeger-operator:1.21.2 at registry.gitlab.com/my/group (which wouldn't be there).
I was able to get the kustomize functionality I wanted but I had to forgo the image-updater and put the logic directly into the app object with param overrides:
kustomize:
      images:
      - registry.gitlab.com/my/group/fluent/fluent-bit:1.5.2=fluent/fluent-bit:1.5.2

So I feel like this should be doable with the image updater.
I feel like its first trying to check for tags in the repo I'm trying to swap out, but I don't know why its checking there.

Fix in #253 (released in v0.10.3) should have fixed that

authors: jannfis perezjasonr

repo: argoproj-labs/argocd-image-updater


text:
Label workflows with updator

Summary

I'd like to see an updator label we can see who updated a workflow.

Ref(creator): https://github.com/argoproj/argo-workflows/pull/3440

the label will be like this: workflow.WorkflowFullName + "/updator.resumed": "admin"

Use Cases

To audit who suspended/stopped/resumed/etc a workflow
Pseudo-approval process for Intermediate Parameter, with condition creator != updator.

Message from the maintainers:
Love this enhancement proposal? Give it a 👍. We prioritise the proposals with the most 👍.

@toyamagu-2021 is this done?

Not done. #11763 implements insert some information in Node, but not label.

repo: argoproj/argo-workflows


text:
Proposal: DAG-based (dependency) model of workflow execution

This issue is to document a proposal and facilitate discussion on having an alternative model of workflow execution using a bottoms-up DAG dependency based approach vs. our current model of a top-down steps-based approach. We would still continue to support the steps-based execution model, but provide the option to execute workflows using the DAG-based model.
The idea behind a dependency approach is similar in concept to a Makefile, where you have a target, that target has dependencies, which in turn have their own dependencies. The execution engine would figure out a resolution order in order to reach the desired target, and run the nodes in the most optimal way possible (essentially when all of a target's dependencies have been satisfied).
Consider the following run-of-the-mill diamond workflow pattern which fans out and fans back in:
     ONE
    /   \
  TWO  THREE
    \   /
    FOUR

The following is how it might be represented in our workflow yaml by declaring dependencies between targets (aka nodes):
apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
  generateName: diamond-dag-
spec:
  target: four
  templates:
  - name: whalesay
    inputs:
      parameters:
      - name: message
    container:
      image: docker/whalesay:latest
      command: [cowsay]
      args: ["{{inputs.parameters.message}}"]

  targets:
  - name: one
    template: whalesay
    arguments:
      parameters: [{name: message, value: one}]
  - name: two
    dependencies:
    - one
    template: whalesay
    arguments:
      parameters: [{name: message, value: two}]
  - name: three
    dependencies:
    - one
    template: whalesay
    arguments:
      parameters: [{name: message, value: three}]
  - name: four
    dependencies:
    - two
    - three
    template: whalesay
    arguments:
      parameters: [{name: message, value: four}]

This is how we are able to achieve the same functionality today:
apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
  generateName: diamond-steps-
spec:
  entrypoint: diamond
  templates:
  - name: whalesay
    inputs:
      parameters:
      - name: message
    container:
      image: docker/whalesay:latest
      command: [cowsay]
      args: ["{{inputs.parameters.message}}"]

  - name: diamond
    steps:
    - - name: one
        template: whalesay
        arguments:
          parameters: [{name: message, value: one}]
    - - name: two
        template: whalesay
        arguments:
          parameters: [{name: message, value: two}]
      - name: three
        template: whalesay
        arguments:
          parameters: [{name: message, value: three}]
    - - name: four
        template: whalesay
        arguments:
          parameters: [{name: message, value: four}]

Below are some of the key benefits of the DAG model which I will attempt to outline:

Highly optimized target execution. Execution of the nodes in the DAG will be highly optimized because we would be able to execute nodes as soon as its dependencies have been satisfied.

Flexibility in control flow. With today's steps based model, we can approximate a DAG, but never truly achieve the same level of functionality.

However, there are some key drawbacks for DAG workflows

Difficult mental model. The bottoms up approach of building dependencies can be somewhat of an unnatural way to think of some workflows. The top down approach would feel more natural for workflows which are more closer to a script than a DAG. It may also be harder to understand and express branching in a DAG.

Dynamic workflows would be difficult to achieve. Consider the coinflip-recursive.yaml example, which is an example of a dynamic workflow which recursively runs a template until it reaches a desired outcome. With DAGs, targets are typically pre-defined at submission and dynamically injecting new targets on the fly, set up relationships between them for something like a recursive workflow would be difficult. I also do not believe we would want to allow something like circular dependency of targets.

CLI rendering. Our steps-based workflow is easily represented as a tree with a single root. Each node has a predictable pattern (every template is either a leaf, or a node which fans out and fans back in). Due  of this, we are able to render the tree quite easily in the CLI. But since DAGs are completely free-form in their relationships between nodes, I do not think it will be feasible to render a free-form DAG from the CLI.

In the end, my belief is that users may still end up preferring a steps-based approximation because of its simpler mental model.

Here is a simple, concrete example of a DAG, which does not have a good approximation using a steps-based execution (node dependencies goes downward):
    A   B
   / \ /
  C   D

The closest approximation of this using steps would be something like:
    *
   / \
  A   B
   \ /
    *
   / \
  C   D
   \ /
    *

As you can see, C's execution gets delayed since it waits on B unnecessarily.

After discussion the decision is to make dag a new template type, which defines a list of tasks from within that overall encompassing step. Example below:
# The following workflow executes a multi-root workflow
#
#   A   B
#  / \ /
# C   D
apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
  generateName: diamond-dag-
spec:
  entrypoint: multiroot
  templates:
  - name: echo
    inputs:
      parameters:
      - name: message
    container:
      image: alpine:3.7
      command: [echo, "{{inputs.parameters.message}}"]
  - name: multiroot
    dag:
      tasks:
      - name: A
        template: echo
        arguments:
          parameters: [{name: message, value: A}]
      - name: B
        dependencies:
        template: echo
        arguments:
          parameters: [{name: message, value: B}]
      - name: C
        dependencies: [A]
        template: echo
        arguments:
          parameters: [{name: message, value: C}]
      - name: D
        dependencies: [A, B]
        template: echo
        arguments:
          parameters: [{name: message, value: D}]

What do you think about actor model?

@bhack i'm unfamiliar with that concept. Is there a framework that uses this pattern that you could point to so I can understand further?

Take a look to this specific Go presentation

Another quite popular Go project is https://github.com/AsynkronIT/protoactor-go

Also for scientific workflows. There is also a related video

Thanks for the links -- I watched the video. Based on what I've learned, actor models seem more of a programming paradigm requiring a framework/SDK to handle the plumbing and messaging between nodes and their actors. This issue is more about how to support a traditional dependency based DAG definition within an container-based workflow. It's definitely an interesting model which we may draw concepts from in the future, but seems be orthogonal to the issue at hand, which is defining a DAG in k8s yaml.

Yes it is a little bit orthogonal to this issue cause the message passing component of the actor model pattern doesn't exist on the shelf in K8 core. But could be an interesting workflow execution paradigm cause could include explicit data exchange definition in the workflow execution model.

@jlewi FYI

This is great!
I think this will make it easier to replace Airflow with Argo since Airflow offers the ability to do arbitrary DAGS.
I think in some ways specifying the dependencies is much easier than trying to manually flatten the graph into the current representation.
My general expectation though is that for really complicated graphs you'd want to use higher level tooling to generate them and not write them by hand.

Yes, we also think higher level tooling is needed for complex workflows.
We're also experimenting with invoking Airflow workflows from Argo workflows. This would let users mix and match existing Airflow operators/DAGs with container based workflows and leverage the huge catalog of existing container images.

DAG support is now in master and will be available as part of the upcoming v2.1 release

authors: bhack edlee2121 jessesuen jlewi

repo: argoproj/argo


text:
Parameterize imagePullSecrets for private authenticated repositories

Is this a BUG REPORT or FEATURE REQUEST?:
FEATURE REQUEST
What happened:
Attempted to install argo in an offline environment against an authenticated private repository and had to edit the deployments manually for it to work.
Additionally, attempting to run a workflow pulling containers from an authenticated repository does not appear to work. Specifying imagePullSecret in the template does not appear to be respected.
What you expected to happen:
Allow for a flag to supply a imagePullSecrets name to properly pull from the Docker registry at installation time. Workflows should also respect imagePullSecret in the template.
How to reproduce it (as minimally and precisely as possible):

Set up a private repository that requires authentication (Harbor, etc.)
Run the following command pointing to the private repo:
argo install --controller-image private-registry.io/argo/workflow-controller:latest  --executor-image private-registry.io/argo/argoexec:latest --ui-image private-registry.io/argo/argoui:latest --ui-base-href /argo/ --enable-web-console -n argo

Anything else we need to know?:
Environment:

Argo version:

$ argo version
argo: v2.1.0
  BuildDate: 2018-05-01T20:04:30Z
  GitCommit: 9379638189cc194f1b34ff7295f0832eac1c1651
  GitTreeState: clean
  GitTag: v2.1.0
  GoVersion: go1.9.3
  Compiler: gc
  Platform: linux/amd64

Kubernetes version :

$ kubectl version -o yaml
clientVersion:
  buildDate: 2018-04-12T14:26:04Z
  compiler: gc
  gitCommit: d4ab47518836c750f9949b9e0d387f20fb92260b
  gitTreeState: clean
  gitVersion: v1.10.1
  goVersion: go1.9.3
  major: "1"
  minor: "10"
  platform: linux/amd64
serverVersion:
  buildDate: 2018-04-12T14:14:26Z
  compiler: gc
  gitCommit: d4ab47518836c750f9949b9e0d387f20fb92260b
  gitTreeState: clean
  gitVersion: v1.10.1
  goVersion: go1.9.3
  major: "1"
  minor: "10"
  platform: linux/amd64

Specifying imagePullSecret in the template does not appear to be respected

ImagePullSecrets is actually at the workflow spec, and no the template level. So if you specify spec.imagePullSecrets, it will be carried forward to the pod.
Additionally, I believe kubernetes provides ways to supply image pull secrets at a namespace level, so that you don't have to always specify imagePullSecrets per pod.
Do the above techniques work for you?

Additionally, I believe kubernetes provides ways to supply image pull secrets at a namespace level, so that you don't have to always specify imagePullSecrets per pod.

Correction -- it is at a service account level, not namespace. But you can attach it to the default service account in a namespace such that the default behavior is that the pods in that namespace will have the image pull secret:
https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/#add-imagepullsecrets-to-a-service-account

Closing this since imagePullSecrets is already in the workflow sepc at the spec.imagePullSecrets level (not a template level).

@jessesuen Thank you for the pointer in the right direction. This works for us. Really enjoying working with argo!

authors: jessesuen patrickstjohn


text:
Minor changes of website

[ ] A Umbenennung von "Archiv" in "Alle"
[ ] B Umsortierung der Menüunterpunkte im Reiter "Rekonstruktionen", nämlich 1. Alle, 2. Tags, 3. Neuste, sodass beim Klick auf Rekonstruktionen zunächst alle Beiträge erscheinen
[ ] C Auf Unterseite Tags: keine Überschrift "Tags"
[ ] D Auf Unterseite "Alle": keine Überschrift "Alle"
[ ] E Betitelung der Beiträge auf Unterseite Archiv nach "Überschrift - Datum" (bisher: "Datum - Überschrift")

All das sollte aber nochmals diskutiert werden, um Inkonsistenzen zu vermeiden.

ad E: Vorschlag: Vereinheitlichung der Überschriften zu "Nachname, Vorname - Stichwort" (wo es Nach- und Vorname gibt; Anselm bleibt Anselm)

authors: davidloewenstein ggbetz


text:
Little bugs in aria-Extract_tutorial.ipynb

Recently, I went through ariaExtract_turotial notebook, and I found something that the authors may want to correct or add.
1. Extract incidence Angle with shapefile
In the Extract incidence Angle with shapefile, we use OSMnx python library to create a shapefile from the OpenStreetMap dataset. In the tutorial, there is no guidance or a cell of codes of doing that. Perhaps adding a remark of installing OSMnx by running:
conda install -c conda-forge osmnx.
Then we can run the following to download the polygon of the Big Island:
import osmnx as ox city = ox.gdf_from_place('Big Island, Hawaii') ox.save_gdf_shapefile(city) ox.plot_shape(ox.project_gdf(city))
Then, we need to rename the downloaded files to "Big_Island.something" and put them into the folder under ./support_docs/Big_Island which is not created by default. So, we also need to create that folder.
With that done, we can run GDAL's orginfo to verify the contents of our shapefile.
2. Application 1. ENU conversion factors
Here we need to create a "results" folder in order to put 3-band enu files generating by GDAL. So, again, we need to do mkdir results. Otherwise, we will have an issue later on:

RuntimeError: Attempt to create file `results/20180502_20180408_enu' failed.

3. Application 2. Computing displacement map
The conversion from interferometric phase, 𝜑, to line‐of‐sight displacement, d, is written as:
𝑑 = ( 4𝜋 / 𝜆 ) 𝜑
Howerver, I think it should be the following instead:
𝑑 [𝑐𝑚] = ( 𝜆 [𝑐𝑚] / 4𝜋 [𝑟𝑎𝑑] ) 𝜑 [𝑟𝑎𝑑]
These are some little things I found. Thank you.

@Yuankailiu thanks for these findings and especially the detailed instructions.
The latest pull request solves points 2 and 3.
In regards to point 1, we provide the Big Island shapefile in the support_docs; as long as you clone the directory as suggested in the installation instruction you will have them in your repo.

repo: aria-tools/ARIA-tools-docs


text:
issue when running ariaDownload.py -h

Hi,
I am trying to install and run Aria-tools on an Ubuntu 21.04 VM (Windows 10 Host).
I followed the steps mentioned in the ReadMe file:

clone git repo
create new environment with anaconda using environment.yml
activate new environment
install all the dependencies
build and installing using setup.py file
saving to PYTHONPATH and PATH

The problem I encounter is that when I run on a Jupyter Notebook:
!ariaDownload.py -h
I get the error;
Traceback (most recent call last):
File "/usr/local/bin/ariaDownload.py", line 19, in
import matplotlib as mpl
ModuleNotFoundError: No module named 'matplotlib'
However, I am sure matplotlib is install in such environment because I can import it in another cell.
Additionally, if I try to import ARIAtools directly I get the error:
ModuleNotFoundError: No module named 'ARIAtools'
Thanks

hi @ulloa18, you need to install to the created conda environment and use it. File "/usr/local/bin/ariaDownload.py", line 19 indicates a problem in your conda setup

We have not tested ARIA-tools on Windows.

If you are setup.py with build and install, then there should be no need to set the python path and path.
If you are using setup.py with just build, then you would need to add the PATH and PYTHON PATH

Can you provide additional information on how you are installing perhaps with the command you use?

closing it as no additional details provided. Can be re-opened if needed

I am using GIT BASH in windows, having the same problem though i save the path and python path the jupyter notebook. please can someone confirm the way of saving path and python path i feel i might have made a mistake there.

please can someone explain how to do the second half of this paragraph

repo: aria-tools/ARIA-tools


text:
In aria.DomEvent, on Edge, isGecko was incorrectly true

This PR changes the value of the isGecko variable in aria.DomEvent, which was incorrectly true on Edge. This fixes several regressions introduced on Edge after changing isSpecialKey in commit e631660e271afe9352ddc36aa2c53873dc372a98.

Looks good, you can integrate it when the build passes

@ymeine Thank you for your review.

authors: divdavem ymeine

repo: ariatemplates/ariatemplates


text:
Batchprocessing/multiplefiles

process multiple files

process multiple files


text:
Support schema inspect for Mysql table with column "Timestamp/Datetime default on update"

We have a column that is in Datetime type and has the default on update definition. For example:
CREATE TABLE `foo` (
 `id`			INT,
 `update_time`	DATETIME(6)  NOT NULL DEFAULT CURRENT_TIMESTAMP(6) ON UPDATE CURRENT_TIMESTAMP(6)

  PRIMARY KEY (`id`),
)

When I try to inspect the schema, I got the following error:
atlas schema inspect -d "mysql://root:secret@tcp(localhost:12334)/my_database"
Error: mysql: unknown attribute "on update current_timestamp(6)"

Mysql version: 5.7.35
Atlas version:
atlas CLI version v0.3.1
https://github.com/ariga/atlas/releases/tag/v0.3.1

Hey @mindbergh, thank you for reaching out to us and reporting this. I will have a look at this :-)

@mindbergh Please try the latest master and let me know if there still is an issue.

Thanks for the quick fix, it works now. I'm able to inspect the column for the default current_timestamp(6). But it still doesn't give the on update current_timestamp(6) attribute. I guess it will be addressed together in #472?

@masseelch Thanks for the quick fix, it works now. I'm able to inspect the column for the default current_timestamp(6). But it still doesn't give the on update current_timestamp(6) attribute. I guess it will be addressed together in #472?

@mindbergh An oversight on my sight. I'll add the field to the rendered HCL.

@mindbergh I just added the on_update field to the column definition in HCL. Closing again, but please let me know if there are more issues.

authors: masseelch mindbergh

repo: ariga/atlas


text:
LL(1) parser friendliness

Over the weekend I was looking into various types of parsing techniques.  Turns out most of the parsers I've implemented are recursive descent with single token / character look-ahead (LL(1)).
The way we currently have annotations (and to a lesser extent colons) means that the JCR ABNF is not LL(1) compatible.  It may be necessary to parse any annotations and back-track up to four times.  Parslet does this very well, but the C++ Boost::Spirit library (which is more XML SAX like in that it fires off events as it parses input) used naively would potentially quadruple up the annotations identified on a rule.  Not only is this less efficient it also requires more work from the developer.  I figure the easier the grammar is to implement, the more implementations there will be, and the more success JCR will have.
Thus this was troubling me, so I looked to see if the grammar could be de-conflicted.  Alas it can be, but at the loss of clarity in the ABNF, and also the potential for introducing errors.
So I propose we leave the grammar as it is and accept that it is not LL(1) friendly. If anyone brings it up we can say we know, but we decided it's not that big-a-deal.  Although the grammar allows annotations, they are a typically rare (so the inefficiency won't occur) and typical scenarios where JCR is used are not likely to be performance critical.
I thought I'd capture this suggestion here to act as a record of the rationale for not changing the grammar to address this.  Naturally if you disagree with the approach let me know.  But if you're happy to go with it then feel free to close it thus 'logging' it as a resolved issue.

I'm happy to go forward with it, but shouldn't this be on the JCR draft project. We could definitely put some text in the draft discussing our decision.

Oh, and thanks for taking the time to look at it.

I'll copy it to the JCR project with a note to put something in the draft, and close it here

repo: arineng/jcrvalidator

license: isc


text:
Add support for multiple custom_structured_configuration prefixes

Change Summary

Allow multi layered custom_structured_configuration and more flexible naming.
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes)
[X] Documentation content changes
[ ] Other (please describe):

Related Issue(s)

Component(s) name
eos_l3ls_evpn
Proposed changes

custom_structured_configuration_prefix allows the user to customize the prefix for Custom Structured Configuration variables.
Default value is custom_structured_configuration_.	Default value is custom_structured_configuration_. Remember to include any delimiter like the last _ in this case.
It is possible to specify a list of prefixes, which will all be merged one by one. The order of merge will start from beginning of the list, which means that keys defined in the later prefixes will be able to override keys defined in previous ones.
custom_structured_configuration_prefix: < variable_prefix, default -> "custom_structured_configuration_" >	custom_structured_configuration_prefix: < variable_prefix, default -> "custom_structured_configuration_" >
#or
custom_structured_configuration_prefix: [ < variable_prefix_1 > , < variable_prefix_2 > , < variable_prefix_3 > ]

Example using multiple prefixes:
custom_structured_configuration_prefix: [ my_dci_ , my_special_dci_ ]

my_special_dci_ethernet_interfaces:
  Ethernet4000:
    ip_address: 10.3.2.1/21

my_dci_ethernet_interfaces:
  Ethernet4000:
    description: My test
    ip_address: 10.1.2.3/12
    shutdown: false
    type: routed
    mtu: 1500
    peer: MY-own-peer
    peer_interface: Ethernet123
    peer_type: my_precious

In this example  Ethernet4000 will be added to the ethernet_interfaces dictionary in the Structured Configuration and the ip_address will be 10.3.2.1/21 since ip_adddress was overridden on the later custom_scructured_configuration_prefix
How to test

Tested with my test repo: https://github.com/ClausHolbechArista/claus-l3ls-dev/commits/superspine-alternative
Following commits show each test scenario.

[x] Test without custom config
[x] Test with default prefix and custom config
[x] Test with 1 custom prefix but no matching config
[x] Test with 1 custom prefix and both matching and non-matching custom config (non-matching is just ignored)
[x] Test with multiple custom prefixes. One using the default name and others using custom names. Also including overrides.

Checklist:

[X] My code has been rebased from devel before I start
[X] I have read the CONTRIBUTING document.
[X] My change requires a change to the documentation.
[X] I have updated the documentation accordingly.
[x] I have updated molecule CI testing accordingly
[ ] All new and existing tests passed (pre-commit, make linting and make sanity-lint).

Rebased and refreshed CI artifacts

Rebased and refreshed CI artifacts

repo: aristanetworks/ansible-avd


text:
Parsing query strings with keys of the same name

The browser behavior (and standard if I can dig up the forms spec) of HTML forms with array-like values is to include a query string with repeated keys.
This multi-select:
<select name="colors" multiple>
  <option value="orange">orange</option>
  <option value="purple">purple</option>
</select>

Will result in ?colors=orange&colors=purple if both options are selected. Instead of parsing this as a list, parseQuery ignores the second value. Furthermore, the query is represented as a lookup map of bytestrings, so has no notion of multiple values per key.
The reason I bring this issue up is this use case: basic HTML form with a multi-select and no JS and a haskell backend using http-types. The http-types Query type and parsers fail that use case.

Fair point. How about this?
We leave Query and QueryItem as is, but make a generic Query-like type that allows putting in Maybe or [], and we just use a generic "append" operation that either replaces or adds an element.
I would most welcome pull requests for this! :-)

To clarify: The parseQuery function would always work in terms of the generic type.

authors: alexmingoia aristidb

repo: aristidb/http-types


text:
The resource object with key 'DateHumanize_MultipleHoursAgo' was not found

Please check all of the platforms you are having the issue on (if platform is not listed, it is not supported)

[] iOS
[X] Android
[] UWP
[X] NET Standard 2.0

Version of OS(s) listed above with issue (if android - please include version of Xamarin.Android.Support.* you are using)
Version of ACR UserDialogs Library
2.6.2
Expected Behaviour
Actual Behavior
For one user we are getting a System.ArgumentException: The resource object with key 'DateHumanize_MultipleHoursAgo' was not found Parameter name: resourceKey
The user is having his UI set to Polish
Code of Conduct

No Library Update Requests - THIS ESPECIALLY MEANS ANDROID SUPPORT LIBRARIES
No Timeline Requests
Please read through the documentation and FAQs
Please be respectful of my time. I put a lot of effort into my libraries.  I try to support the issue requests within a day.  I'm not psychic, so please take the time to fill out the above form as complete as possible

This library has never had a v2.6.2 and has no key or error like that

authors: aritchie jemunk

repo: aritchie/userdialogs


text:
[Feature] self-cleaning

Implement trash note
now you can move note to trash after 28 will auto delete also you can delete and restore+
Uploading bandicam 2023-10-17 00-33-33-747.mp4…

Can you please fix the ktlint checks @salmanA169.

repo: aritra-tech/Notify


text:
Longest Increasing Subsequence and Coin Change problem

The solution to two popular DP problems written in an easy way.

Hey thanks for your contribution ❗. Keep up the good job and leave a star if you liked the repo .
Happy hacking 😉

authors: Sagnikban aritrakrbasu

repo: aritrakrbasu/Hacktoberfest-Hack-Codes


text:
sqlite: Split SelectSweepableRounds into several smaller queries

Rework the SelectSweepableRounds SQL query. The current implementation was using a lot of LEFT JOIN making GetSweepableRounds stuck the main thread.
@altafan please review

Although this probably improves current situation I would say NACK to it cause we need to revamp db layer a bit.
Here is a problem:
Our domain Round is aggregating whole DB:
type Round struct {
	Id                string
	StartingTimestamp int64
	EndingTimestamp   int64
	Stage             Stage
	TxRequests        map[string]TxRequest
	Txid              string
	UnsignedTx        string
	ForfeitTxs        []string
	VtxoTree          tree.VtxoTree
	Connectors        []string
	ConnectorAddress  string
	DustAmount        uint64
	Version           uint
	Swept             bool // true if all the vtxos are vtxo.Swept or vtxo.Redeemed
	changes           []RoundEvent
}

Bellow is one of problematic queries and rows count in comment:
SELECT count(*)
FROM round
         LEFT OUTER JOIN round_request_vw ON round.id=round_request_vw.round_id
         LEFT OUTER JOIN round_tx_vw ON round.id=round_tx_vw.round_id
         LEFT OUTER JOIN request_receiver_vw ON round_request_vw.id=request_receiver_vw.request_id
         LEFT OUTER JOIN request_vtxo_vw ON round_request_vw.id=request_vtxo_vw.request_id
WHERE round.swept = false AND round.ended = true AND round.failed = false; --11 010 322

select count(*) from round; --147
select count(*) from round_request_vw; -- 2111
select count(*) from round_tx_vw; --88258
select count(*) from request_receiver_vw; --4125
select count(*) from request_vtxo_vw; --3249

SelectSweptRounds results in massive result set that takes more than 40 GB of RAM.
We need to be careful with what we fetch for db, and we should never fetch data to populate all Rounds with all its properties(basically whole DB).
For eg. bellow code needs sweepable tx ids:
func (s *covenantlessService) restoreWatchingVtxos() error {
	sweepableRounds, err := s.repoManager.Rounds().GetSweepableRounds(context.Background())
	if err != nil {
		return err
	}

	vtxos := make([]domain.Vtxo, 0)

	for _, round := range sweepableRounds {
		fromRound, err := s.repoManager.Vtxos().GetVtxosForRound(
			context.Background(), round.Txid,
		)
		if err != nil {
			log.WithError(err).Warnf("failed to retrieve vtxos for round %s", round.Txid)
			continue
		}
		for _, v := range fromRound {
			if !v.Swept && !v.Redeemed {
				vtxos = append(vtxos, v)
			}
		}
	}

	if len(vtxos) <= 0 {
		return nil
	}

	if err := s.startWatchingVtxos(vtxos); err != nil {
		return err
	}

	log.Debugf("restored watching %d vtxos", len(vtxos))
	return nil
}

We could use bellow query:
select count(*)
from round r inner join tx t on r.id = t.round_id
WHERE r.swept = false AND r.ended = true AND r.failed = false; — 83507

100% we should rework the interface to return more granular data.
but this must be done for all methods I would say and it will require change in the application layer, this is an hotfix at least to make the server work before a better solution.

also the method is also used to get VtxoTree and I think the trees are what make the dataset so big. We can probably gain by only selecting the trees but I'd still split the queries into smaller ones instead of a lot of JOIN.

closed in favor of #399

authors: altafan louisinger sekulicd

repo: ark-network/ark


text:
Backstage code review

Hey, I just made a Pull Request!

:heavy_check_mark: Checklist

[x]  ChangeSets done:

'/thin-geese-brush.md' added extra parameter for testing purposes. (GkeClusterLocator.test.ts)
'/eleven-bags-flash.md' added extra parameter in the config settings (GkeClusterLocator.ts)
(more info)

[x] Before login BUG UI issue:

[x] After login BUG UI fixed:

[ ] All commits have a Signed-off-by line in the message.
(more info)

approved ✅


text:
docs(k8s-agent): refactor intro bullet points

request from Stu to revamp intro bullet points based on marketing release plan
changed top level bullet points to match marketing categories
incorporated a bit more functionality into the existing bullet points

@aimeeu Looks good to me! Thanks!

authors: aimeeu stuposluns

repo: armory/docs


text:
Excluding namespaces

When running a cluster with v1.0..88 and using the flag --exclude-namepaces "kube-system,kube-public" the scan results are still showing this namespaces under the [control: Network policies] section.
kubescape scan framework --exclude-namespaces "kube-system,kube-public" \  -t 80 \ -o cluster-scan.log nsa

@Daniel-GrunbergerCA How is this possible? What is the Kubernetes object the rego returns when running this control?

@Daniel-GrunbergerCA I found the issue. Should be fixed next release.

@Daniel-GrunbergerCA  Thanks for the quick response of this.  Just to clarify I was seeing this mainly in the Network policy control.
`[control: Network policies] failed
[control: Network policies] failed
Namespace - kube-system
Namespace - default
Namespace - kube-public
Namespace - kube-node-lease
Namespace - gatekeeper-system

`

@alfrye Yes, we filtered out the namespace based on metadata.namespace so when the failed object was a namespace we did not filter it out (since we did not check the metadata.name).
This fix is waiting to be released, I will update the issue tag to fixed after it is released.
Have a nice day and thank you for your feedback :)

ApiVersion:
Kind: ServiceAccount
Name: statefulset-controller
Namespace: kube-system

Controls: 9 (Failed: 1, Excluded: 0)

+----------+------------------+------------------------------------+-----------------------------------------+
| SEVERITY |   CONTROL NAME   |                DOCS                |          ASSISTANT REMEDIATION          |
+----------+------------------+------------------------------------+-----------------------------------------+
| Critical | Data Destruction | https://hub.armo.cloud/docs/c-0007 | relatedObjects[1].rules[4].resources[0] |
|          |                  |                                    | relatedObjects[1].rules[4].verbs[1]     |
|          |                  |                                    | relatedObjects[1].rules[4].apiGroups[0] |
|          |                  |                                    | relatedObjects[0].subjects[0]           |
|          |                  |                                    | relatedObjects[0].roleRef.name          |
+----------+------------------+------------------------------------+-----------------------------------------+

with the command
kubescape scan framework nsa,mitre,armobest,devopsbest --exclude-namespaces kube-system,kube-public
looks like it is also not filtering service accounts

Hi, is this Issue still open, please guide me how to work on this, Thank you and kudos to your team.

authors: alfrye danieljkemp dwertent iamhardikat11

repo: armosec/kubescape


text:
🛑 NWTFV is down

In e85a6b1, NWTFV (https://nwtfv.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: NWTFV is back up in c4b9864.

repo: arnef/status


text:
🛑 NWTFV is down

In 24736cf, NWTFV (https://nwtfv.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: NWTFV is back up in 60324c1.


text:
iOS Pods Error

Hi, i've got an error when i build my project in Xcode. Here is my errors:

Diff:/../Podfile.lock: No such file or directory
Diff:/../Manifest.lock: No such file or directory
The sandbox is not in sync with the Podfile.lock. Run 'pod install' or update your CocoaPods installation

I already install cocoapods and follow this tutorial https://firebase.google.com/docs/ios/setup , but still not working.
Same for the 3rd error, i already trys 'pod install' and update my cocoapods but still got the same 3 error
Can someone help me to resolve this error pls?
Thank you

@cincaw Can you tell us that how you resolved this issue. As I am also having the same error.

@ansaries  Did you fix this issue man? Can you share it to me how? Thanks

authors: ansaries cincaw minto5050

repo: arnesson/cordova-plugin-firebase


text:
Comparison with cookiecutters ?

https://github.com/pydanny/cookiecutter-django

Hi,
Cookie cutter is also a project starter but with a different philosophy. Edge uses the standard django-admin template parameter approach to customize your project as much as possible, while CookieCutter has a separate command which uses a Q&A interface to provide more customization.
Cookie cutter offers plenty of starter templates and Edge offers just one. Hence we strive towards a more general starter template. If you have clearly known specialized needs then you might find a cookiecutter suited for you.
I would also add that Edge is more oriented towards a simpler set of requirements especially if you are starting out in development (for e.g. uses SQLlite rather than PostgreSQL). This is intended to make it more beginner-friendly.

repo: arocks/edge


text:
Added missing favicon

🛠 Fixes Issue
[OTHER] Missing favicon
Closes #202
👨💻 Changes proposed
Added missing favicon in the base HTML and login page using static files by creating a new URL for favicons.
✔ Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

📷 Screenshots

@singhmansi25 @raghavTinker


text:
Revamped the Engineers Copied frontend template

Description
Inserted the logo of website , added information in form of cards , modified the form page , created a footer, revamped the About Us page , added line below texts .
Fixes:  #442

Type of change

[x] New feature (non-breaking change which adds functionality)

Checklist:

[x] I have made this from my own

[x] I have taken help from some online resourses

[x] My code follows the style guidelines of this project

[x] I have performed a self-review of my own code

[x] My changes generate no new warnings

ATTACH SCREEN-SHOTS / DEPLOYMENT LINK
Images.before.after.zip
here are the images before n after @VidhiBhatt01

Images before after .zip
Here are the before after images which you requested .

@IshitaGarg-01 kindly add images for mobile view also so that we can check if its responsible or not.

@IshitaGarg-01 kindly add images for mobile view also so that we can check if its responsible or not.

@DEEPIKA-SUK Ma'am the website isn't responsive !

@IshitaGarg-01 If possible try to make it responsive.

@IshitaGarg-01 If possible try to make it responsive.

ma'am can't it be accepted without making responsive?

ok

@IshitaGarg-01 delete all the .DS store files

@IshitaGarg-01 delete all the .DS store files

@arpit456jain Done !

@IshitaGarg-01  solve merge conflicts

@IshitaGarg-01 solve merge conflicts

Ok sir

@IshitaGarg-01 solve merge conflicts

@arpit456jain I have tried solving all the merge conflicts. Can you please check ?

@IshitaGarg-01 i can't do thing anything in this i suggest you to make a new PR after updating ur branch
take help from mentors


text:
Store doesn't reset between launches.

Using freezer in a React Native Android app, the store doesn't completely reset between launches.
I have a store that has an object called projects
projects: {}.
When I launch the app for the very first time (fresh install) and print out all projects I get an empty object as expected. I then fill the project object with, say, 10 projects, where the object key is the project ID and the value is some project object.
If I now kill and restart the app (no reinstall), and print out all projects as the first action, I get an object with 10 projects, with their keys ranging from 0 - 10, rather than being the project IDs I used to originally save those projects.
Shouldn't the store be deleted on an app restart?

Hi @Billydubb
I am not a react native expert, but it looks to me like the context of the app is not really killed when you close it. To be honest I have no idea about how Android closes the apps, but if it doesn't clean the JS context automatically, maybe you can use some android signal to the app (some event when the app get closed or open) and clean it yourself. That way you will be sure that you will get a fresh store on opening.

Issue can be closed. It is indeed reset between launches. I overlooked that I loaded the projects from persistent database on startup and put them into the storage without giving them their IDs as keys.
Stupid mistake.

authors: Billydubb arqex

repo: arqex/freezer


text:
how can i get the normal of planes for each frame extracted from /scene_id/scene_id.sens?

hello! thanks for your impressive work of this project.
after running parse.py, i got three files:
annotation/segmentation/ *.png : the planr segmentation of each frame
annotation/planes.npy : the global normal for all the planes in the scene
annotation/planes.ply : the 3D mesh model of the scene, and i can open it with meshlab
I think these files should be the correct output of parse.py .
for now, i want to get the normal of planes of each frame extracted from /scene_id/scene_id.sens using the official reader,
but i have saw the document of both PlaneNet and PlaneRcnn, i can`t figure out it.
could you tell me how to solve it ?
thank a lot.
By the way : welcome to contact me at im_huiyao@163.com , if anyone wanna dicuss problems of PlaneNet and PlaneRcnn.

hello! thanks for your impressive work of this project.
after running parse.py, i got three files:
annotation/segmentation/ *.png : the planr segmentation of each frame
annotation/planes.npy : the global normal for all the planes in the scene
annotation/planes.ply : the 3D mesh model of the scene, and i can open it with meshlab
I think these files should be the correct output of parse.py .
for now, i want to get the normal of planes of each frame extracted from /scene_id/scene_id.sens using the official reader,
but i have saw the document of both PlaneNet and PlaneRcnn, i can`t figure out it.
could you tell me how to solve it ?
thank a lot.
By the way : welcome to contact me at im_huiyao@163.com , if anyone wanna dicuss problems of PlaneNet and PlaneRcnn.

Hav u solved problem? Depressing meet same confusion as urs.
Appreciate a lot for sharing!

for network output it can be inferred from P_i. But where in data preparation phase?

authors: Hui-Yao wwryidiosyncraster

repo: art-programmer/PlaneNet


text:
An option to prevent just the .sidr-class prefix from being added

Is there an option to prevent this from happening? Classes are not unique and don't need a  prefix to validate the HTML. They can be easily differentiated by using a descending selector. I just want to prevent class renaming, not the ID.
Thank you!

artberri: thanks dear it's working :+1:

Hello,
I think there is still an issue with this solution : defining renaming to false doesn't rename classes, ok, but it doesn't rename ids either !
We sometimes need to keep classes but we MUST rename ids because they must be unique.
You should create renamingClasses and renamingIds options, or add keepClasses option to renaming option.

instead of using the id, can you put the id into a class? you can still make your calls accrding to a unique class.

No, I don't talk about the whole menu ID. Every UL in my source menu has got an id to use Bootstrap3 Collapse features, target identified with data-target="#id". So I don't want to rename ul classes like btn, collapse, ... but all the IDs MUST be renamed to be unique.

authors: jesserosenfield santonum santoshverma001 schmelik

repo: artberri/sidr