operator-sdk up local: The ansible_python_interpreter variable is missing from the generated inventory

Bug Report
I created my first operator using Ansible as explained here:
https://github.com/operator-framework/operator-sdk/blob/master/doc/ansible/user-guide.md
What did you do?
After having installed the operator-sdk, Ansible, ansible-runner, the openshift module and the ansible-runner-http plugin.
brew install operator-sdk ansible
brew link --overwrite ansible
/usr/local/Cellar/ansible/2.7.10/libexec/bin/pip install ansible-runner-http openshift
ln -s /usr/local/Cellar/ansible/2.7.10/libexec/bin/ansible-runner /usr/local/bin/ansible-runner

Having scaffolded the operator structure:
operator-sdk new hello-world --type=ansible --generate-playbook --api-version itix.fr/v1alpha1 --kind HelloWorld

Having written some code:
cat <<EOF > roles/helloworld/defaults/main.yml
# NOTE: meta.name(space) comes from CR metadata when run with Ansible Operator
# deploy/crds has an example CR for reference
name: "{{ meta.name | default('hello-world') }}"
namespace: "{{ meta.namespace | default('hello-world') }}"
image: docker.io/ansibleplaybookbundle/hello-world:latest

# To uninstall from the cluster
# state: absent
state: present

# The size of the hello-world deployment
size: 1
EOF

cat <<EOF > roles/helloworld/tasks/main.yml
---

- name: "Get information about the cluster"
  set_fact:
    api_groups: "{{ lookup('k8s', cluster_info='api_groups') }}"

- name: 'Set hello-world objects state={{ state }}'
  k8s:
    state: '{{ state }}'
    definition: "{{ lookup('template', item.name) | from_yaml }}"
  when: item.api_exists | default(True)
  loop:
    - name: deployment.yml.j2
    - name: service.yml.j2
    - name: route.yml.j2
      api_exists: "{{ 'route.openshift.io' in api_groups }}"
EOF

cat <<EOF > roles/helloworld/templates/deployment.yml.j2
---

{% if 'apps.openshift.io' in api_groups %}
apiVersion: apps.openshift.io/v1
kind: DeploymentConfig
{% else %}
apiVersion: apps/v1
kind: Deployment
{% endif %}
metadata:
  name: {{ name }}
  namespace: {{ namespace }}
  labels:
    app: {{ name }}
    service: {{ name }}
spec:
  replicas: {{ size }}
{% if 'apps.openshift.io' in api_groups %}
  selector:
    app: {{ name }}
    service: {{ name }}
{% else %}
  selector:
    matchLabels:
      app: {{ name }}
      service: {{ name }}
{% endif %}
  template:
    metadata:
      labels:
        app: {{ name }}
        service: {{ name }}
    spec:
      containers:
      - image: {{ image }}
        name: hello-world
        ports:
        - containerPort: 8080
          protocol: TCP
EOF

cat <<EOF > roles/helloworld/templates/service.yml.j2
---

apiVersion: v1
kind: Service
metadata:
  name: {{ name }}
  namespace: {{ namespace }}
  labels:
    app: {{ name }}
    service: {{ name }}
spec:
  ports:
  - name: web
    port: 8080
    protocol: TCP
    targetPort: 8080
  selector:
    app: {{ name }}
    service: {{ name }}
EOF

cat <<EOF > roles/helloworld/templates/route.yml.j2
---

apiVersion: route.openshift.io/v1
kind: Route
metadata:
  name: {{ name }}
  namespace: {{ namespace }}
  labels:
    app: {{ name }}
    service: {{ name }}
spec:
  port:
    targetPort: web
  to:
    kind: Service
    name: {{ name }}
EOF

Having tested it manually:
oc new-project test-operator
ansible-playbook playbook.yml -e '{"meta":{"name":"hello-nicolas","namespace":"test-operator"}}'

I wanted to test it locally within the operator framework.
So, I prepared my environment:
oc create -f deploy/crds/*_crd.yaml
oc create -f - <<EOF
apiVersion: itix.fr/v1alpha1
kind: HelloWorld
metadata:
  name: example-helloworld
spec:
  # Add fields here
  size: 3
EOF
perl -pi -e 's|^  playbook:.*|  playbook: $ENV{PWD}/playbook.yml|' watches.yaml

And ran the operator-sdk up local command:
operator-sdk up local --namespace=test-operator

What did you expect to see?
I expected the operator to run smoothly since I tested the playbook manually before and it worked perfectly.
What did you see instead? Under which circumstances?
But the operator failed with a strange error message (This module requires the OpenShift Python client. Try 'pip install openshift'):
INFO[0000] Running the operator locally.
INFO[0000] Using namespace test-operator.
{"level":"info","ts":1558017137.075559,"logger":"cmd","msg":"Go Version: go1.12.4"}
{"level":"info","ts":1558017137.075617,"logger":"cmd","msg":"Go OS/Arch: darwin/amd64"}
{"level":"info","ts":1558017137.075627,"logger":"cmd","msg":"Version of operator-sdk: v0.7.0"}
{"level":"info","ts":1558017137.07586,"logger":"cmd","msg":"Watching namespace.","Namespace":"test-operator"}
{"level":"info","ts":1558017138.215403,"logger":"leader","msg":"Trying to become the leader."}
{"level":"info","ts":1558017138.215489,"logger":"leader","msg":"Skipping leader election; not running in a cluster."}
{"level":"info","ts":1558017138.2160451,"logger":"proxy","msg":"Starting to serve","Address":"<IP_ADDRESS>:8888"}
{"level":"info","ts":1558017138.216366,"logger":"manager","msg":"Using default value for workers 1"}
{"level":"info","ts":1558017138.216394,"logger":"ansible-controller","msg":"Watching resource","Options.Group":"itix.fr","Options.Version":"v1alpha1","Options.Kind":"HelloWorld"}
{"level":"info","ts":1558017138.216649,"logger":"kubebuilder.controller","msg":"Starting EventSource","controller":"helloworld-controller","source":"kind source: itix.fr/v1alpha1, Kind=HelloWorld"}
{"level":"info","ts":1558017138.321085,"logger":"kubebuilder.controller","msg":"Starting Controller","controller":"helloworld-controller"}
{"level":"info","ts":1558017138.42496,"logger":"kubebuilder.controller","msg":"Starting workers","controller":"helloworld-controller","worker count":1}
{"level":"info","ts":1558017140.246912,"logger":"logging_event_handler","msg":"[playbook task]","name":"example-helloworld","namespace":"test-operator","gvk":"itix.fr/v1alpha1, Kind=HelloWorld","event_type":"playbook_on_task_start","job":"2585521572816551866","EventData.Name":"helloworld : Set hello-world objects state=present"}
{"level":"error","ts":1558017141.009769,"logger":"logging_event_handler","msg":"","name":"example-helloworld","namespace":"test-operator","gvk":"itix.fr/v1alpha1, Kind=HelloWorld","event_type":"runner_on_failed","job":"2585521572816551866","EventData.Task":"Set hello-world objects state={{ state }}","EventData.TaskArgs":"","EventData.FailedTaskPath":"/Users/nmasse/tmp/hello-world/roles/helloworld/tasks/main.yml:7","error":"[playbook task failed]","stacktrace":"github.com/operator-framework/operator-sdk/vendor/github.com/go-logr/zapr.(*zapLogger).Error\n\tsrc/github.com/operator-framework/operator-sdk/vendor/github.com/go-logr/zapr/zapr.go:128\ngithub.com/operator-framework/operator-sdk/pkg/ansible/events.loggingEventHandler.Handle\n\tsrc/github.com/operator-framework/operator-sdk/pkg/ansible/events/log_events.go:84"}
{"level":"error","ts":1558017141.219702,"logger":"runner","msg":"\u001b[0;34mansible-playbook 2.7.10\u001b[0m\r\n\u001b[0;34m  config file = /etc/ansible/ansible.cfg\u001b[0m\r\n\u001b[0;34m  configured module search path = ['/Users/nmasse/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']\u001b[0m\r\n\u001b[0;34m  ansible python module location = /usr/local/Cellar/ansible/2.7.10/libexec/lib/python3.7/site-packages/ansible\u001b[0m\r\n\u001b[0;34m  executable location = /usr/local/bin/ansible-playbook\u001b[0m\r\n\u001b[0;34m  python version = 3.7.3 (default, Mar 27 2019, 09:23:39) [Clang 10.0.0 (clang-1<IP_ADDRESS>)]\u001b[0m\r\n\u001b[0;34mUsing /etc/ansible/ansible.cfg as config file\u001b[0m\r\n\u001b[0;34m/tmp/ansible-operator/runner/itix.fr/v1alpha1/HelloWorld/test-operator/example-helloworld/inventory/hosts did not meet host_list requirements, check plugin documentation if this is unexpected\u001b[0m\r\n\u001b[0;34m/tmp/ansible-operator/runner/itix.fr/v1alpha1/HelloWorld/test-operator/example-helloworld/inventory/hosts did not meet script requirements, check plugin documentation if this is unexpected\u001b[0m\r\n\r\nPLAYBOOK: playbook.yml *********************************************************\n\u001b[0;34m1 plays in /Users/nmasse/tmp/hello-world/playbook.yml\u001b[0m\n\u001b[1;35m [WARNING]: Found variable using reserved name: name\u001b[0m\r\n\u001b[1;35m\u001b[0m\n\r\nPLAY [localhost] ***************************************************************\n\u001b[0;34mMETA: ran handlers\u001b[0m\n\r\nTASK [helloworld : Get information about the cluster] **************************\r\n\u001b[1;30mtask path: /Users/nmasse/tmp/hello-world/roles/helloworld/tasks/main.yml:3\u001b[0m\n/usr/local/Cellar/ansible/2.7.10/libexec/lib/python3.7/site-packages/kubernetes/config/kube_config.py:496: YAMLLoadWarning: calling yaml.load() without Loader=... is deprecated, as the default Loader is unsafe. Please read https://msg.pyyaml.org/load for full details.\r\n  config_dict=yaml.load(f),\r\n\u001b[0;32mok: [localhost] => {\"ansible_facts\": {\"api_groups\": [\"apiregistration.k8s.io\", \"extensions\", \"apps\", \"events.k8s.io\", \"authentication.k8s.io\", \"authorization.k8s.io\", \"autoscaling\", \"batch\", \"certificates.k8s.io\", \"networking.k8s.io\", \"policy\", \"authorization.openshift.io\", \"rbac.authorization.k8s.io\", \"storage.k8s.io\", \"admissionregistration.k8s.io\", \"apiextensions.k8s.io\", \"scheduling.k8s.io\", \"apps.openshift.io\", \"build.openshift.io\", \"image.openshift.io\", \"network.openshift.io\", \"oauth.openshift.io\", \"project.openshift.io\", \"quota.openshift.io\", \"route.openshift.io\", \"security.openshift.io\", \"template.openshift.io\", \"user.openshift.io\", \"monitoring.coreos.com\", \"automationbroker.io\", \"itix.fr\", \"microcks.github.io\", \"servicecatalog.k8s.io\"]}, \"changed\": false}\u001b[0m\n\r\nTASK [helloworld : Set hello-world objects state=present] **********************\r\n\u001b[1;30mtask path: /Users/nmasse/tmp/hello-world/roles/helloworld/tasks/main.yml:7\u001b[0m\n\u001b[0;31mfailed: [localhost] (item={'name': 'deployment.yml.j2'}) => {\"changed\": false, \"item\": {\"name\": \"deployment.yml.j2\"}, \"msg\": \"This module requires the OpenShift Python client. Try `pip install openshift`\"}\u001b[0m\n\u001b[0;31mfailed: [localhost] (item={'name': 'service.yml.j2'}) => {\"changed\": false, \"item\": {\"name\": \"service.yml.j2\"}, \"msg\": \"This module requires the OpenShift Python client. Try `pip install openshift`\"}\u001b[0m\n\u001b[0;31mfailed: [localhost] (item={'name': 'route.yml.j2', 'api_exists': True}) => {\"changed\": false, \"item\": {\"api_exists\": true, \"name\": \"route.yml.j2\"}, \"msg\": \"This module requires the OpenShift Python client. Try `pip install openshift`\"}\u001b[0m\n\r\nPLAY RECAP *********************************************************************\r\n\u001b[0;31mlocalhost\u001b[0m                  : \u001b[0;32mok=1   \u001b[0m changed=0    unreachable=0    \u001b[0;31mfailed=1   \u001b[0m\r\n\n","job":"2585521572816551866","name":"example-helloworld","namespace":"test-operator","error":"exit status 2","stacktrace":"github.com/operator-framework/operator-sdk/vendor/github.com/go-logr/zapr.(*zapLogger).Error\n\tsrc/github.com/operator-framework/operator-sdk/vendor/github.com/go-logr/zapr/zapr.go:128\ngithub.com/operator-framework/operator-sdk/pkg/ansible/runner.(*runner).Run.func1\n\tsrc/github.com/operator-framework/operator-sdk/pkg/ansible/runner/runner.go:289"}

Environment

operator-sdk version:

operator-sdk version v0.7.0

Kubernetes version information:

$ oc version
oc v3.11.0+0cbc58b
kubernetes v1.11.0+d4cacc0
features: Basic-Auth

Server https://openshift.itix.fr:8443
openshift v3.11.98
kubernetes v1.11.0+d4cacc0

Kubernetes cluster kind: OpenShift all-in-one node

Are you writing your operator in ansible, helm, or go? Ansible

Possible Solution
The operator-sdk generates an inventory file for the ansible-runner. But this inventory file do not match the implicit localhost entry (see https://docs.ansible.com/ansible/latest/inventory/implicit_localhost.html).
$ cat /tmp/ansible-operator/runner/itix.fr/v1alpha1/HelloWorld/test-operator/example-helloworld/inventory/hosts
localhost ansible_connection=local

This lead to ansible/ansible#56510.
Proposed solution
The generated inventory file includes the ansible_python_interpreter variable as described in the link above.
localhost ansible_connection=local ansible_python_interpreter="{{ansible_playbook_python}}"

Hi @nmasse-itix,
It is solved in the master branch:
$ brew install operator-sdk ansible
Updating Homebrew...
==> Auto-updated Homebrew!
Updated 1 tap (homebrew/cask).
No changes to formulae.
....
See: https://docs.brew.sh/Homebrew-and-Python
camilamacedo@Camilas-MacBook-Pro ~/go/src/github.com $ brew link --overwrite ansible
Linking /usr/local/Cellar/ansible/2.8.5... 19 symlinks created
camilamacedo@Camilas-MacBook-Pro ~/go/src/github.com $

In this way, I am closing this one. However, please feel free to re-open if you need.


Update the Android Template with new test cases design convention

What happened 🤔
Resolve #73 : Improve test case design convention by applying the Method B: Create multiple test functions that each of them will have a specific description message and one assertion for each observer used per test function - the most-voted option by the team 💪
Insight 👀

Add more detailed descriptions for all existing test functions for correctly reflecting what is being tested in each function.
Split some test functions that have multiple assertions into each function per assertion.
Add some small refactors to clean up some warnings.
Update build_gradle_version to latest existing version: 4.2.0-rc01

PoW (a.k.a Proof Of Work)💪
The template and all the updated tests are built and running successfully 👌

@minhnimble conflict 😢

@luongvo no worries, I will update this PR accordingly since you modified the tests a bit. Let me update your new tests to match our new convention as well 🙏


AttributeError: 'NoneType' object has no attribute '_fixed_uid' & ValueError: No radiological volume for {xy}

First off, thank you very much for providing this tool as an open-source solution.
I am a radiologist and must admit that i have little programming knowledge regarding python. Thats why i am struggeling a bit trying to set this up. I already progressed getting the tool to run (didnt want to start segmenting in the beginning) but with this issue i dont seem to make any progress:
Describe the bug
When running the Reporting tool using direct DICOM import of T1, T2, FLAIR and T1-ce i get an error message (see below Nr 1)
When running it with compressed niftii (even the ones provided as test data) i get a different error message (see below Nr 2)
Computer settings (please complete the following information):

Operating System : Windows 10
CPU: Ryzen 5 3600
GPU: Nvidia RTX 2060

Scanner-Data

Siemens Espree / Skyra 1.5T/3.0T
Syngo MR BR19/  VB30C

Error message 1
20/11/2023 15.50 ; root ; INFO ; LOG: Pipeline - Registration from T1w (T0) to T1CE (T0) - Runtime: 43.97487211227417 seconds.
20/11/2023 15.50 ; root ; INFO ; LOG: Pipeline - Registration from T1w (T0) to T1CE (T0) - End (5/15)
20/11/2023 15.50 ; root ; INFO ; LOG: Pipeline - Apply registration from T1w (T0) to T1CE (T0) - Begin (6/15)
20/11/2023 15.50 ; root ; ERROR ; [RegistrationDeployerStep] Step setup failed with: Traceback (most recent call last):
File "raidionicsrads\Pipelines\RegistrationDeployerStep.py", line 52, in setup
AttributeError: 'NoneType' object has no attribute '_fixed_uid'
Error message 2
20/11/2023 16.42 ; root ; ERROR ; [SegmentationStep] setup failed with: Traceback (most recent call last):
File "raidionicsrads\Pipelines\SegmentationStep.py", line 71, in setup
ValueError: No radiological volume for {'timestamp': 0, 'sequence': 'T1-w', 'labels': None, 'space': {'timestamp': 0, 'sequence': 'T1-w'}}.
my assumption
I assume this is an issue with the DICOM headers but i wasnt really able to trace it down to what.
Thank you very much.
LS

Closed due to accidental duplicate of https://github.com/raidionics/Raidionics/issues/65.


Getting connectors work

There is still an issue during installation of the spool-dir-connector that has the OpaTransformer added. (spool-dir-connector-masking-config)
"Connector configuration is invalid and contains the following 2 error(s):\nInvalid value com.opencredo.opasmt.OpaTransformer for configuration transforms.opa.type: Class com.opencredo.opasmt.OpaTransformer could not be found."
This seems to be an issue either with classpath or plugin.path, or there is something wrong with how maven plugin packaged the fat jar.


[HPC] Proposal: Offer long, guaranteed benchmark stability

Introduction:
After collecting feedback from engineers, clients, and press, NVIDIA presented a list of proposals that aim to improve the popularity of the MLPerf HPC benchmark suite. Please see our slide deck for more information on our feedback gathering process and insights.
Proposal: Offer long, guaranteed benchmark stability (guarantees submission longevity)
Slide 13 in proposals slide deck.
We propose to offer guaranteed benchmark stability for some agreed-upon duration:

First appearance of benchmark labeled "beta": A beta benchmark may or may not change by the next submission round.
Second submission round drops the beta status and freezes the benchmark for X years. We guarantee that code and dataset will not be modified at all during the guaranteed lifespan.
Since benchmark is guaranteed stable, this proposal allows carrying results from prior rounds.

This proposal aims to improve the popularity of the MLPerf HPC benchmark suite by improving on the following aspects:

High submission overhead and cost [Affects participation and competition]
Enables prioritizing of MLPerf-HPC for new systems [Affects participation and competition]

Discussion
Pros:

Carrying prior results reduces overhead for participation
Guaranteed benchmark lifespan reduces effective submission overhead/cost since one submission will be valid for the next X years
Improves prioritizing MLPerf HPC for new systems, if it is designed to be more stable than MLPerf Training

Cons:

Bugs in model code and dataset will not be corrected if they are identified after beta status drops

I support making benchmark stability a goal. However, I don't think we've actually had any problems yet where someone couldn't reuse results that wanted to, have we? If not, or even if very rarely, is it necessary to formalize this? Without formalizing it, we give ourselves the flexibility to maximize stability when possible but to decide as a group on the rare cases whether to allow for improvements or bugfixes.

Yes, I think for now this can be decided based on group consensus.

Since we haven't had an issue with it, why not  formalize it? Sounds like we just need to add a paragraph in the policies document.
I think a formal guarantee that a benchmark will not change will be a strong motivator for submitters who are concerned about their "return on investment" (investment would be the total engineer/machine hours needed for submissions, return will be longevity of results). We don't have to guarantee stability for centuries. Perhaps 2-3 years? We have to retire benchmarks after a few years anyway (not a focus yet, but it will unavoidably become one over time).
The flexibility and ensuring stability argument is fair. There may be ways to remain flexible under this proposal: Off the top of my head we can, when absolutely necessary, create a fork of some benchmark that in turn has a guaranteed lifespan. So if for example we find a bug in cosmoflow during its guaranteed lifetime (ideally we won't - that's why the first year's beta status is there for), we can create a "cosmoflow 2.0" benchmark while keeping cosmoflow 1.0 still intact. Perhaps in this case, we no longer allow 1.0 submissions moving forward?


support pipe2 on BSD

Right now it's only available in the notbsd subtree, but it looks like the BSD's support it?
https://www.freebsd.org/cgi/man.cgi?query=pipe&sektion=2
http://netbsd.gw.com/cgi-bin/man-cgi?pipe2+2+NetBSD-current
http://man.openbsd.org/pipe.2
I might try moving it up to src/unix/mod.rs in a PR just to see what happens. Maybe Apple doesn't support it? Let me know if there's an easy way to figure this out without just seeing what breaks :)

Yep, it breaks on OSX. Would the right thing to do be to individually add it to the other BSD flavors?

Related question: nix currently hardcodes the platforms that support this call, https://github.com/nix-rust/nix/blob/master/src/unistd.rs#L617-L619. If we add more platforms, nix will want to update those lines. Is there a way for nix to avoid this kind of hardcoding?

AFAIK there's no way to avoid hardcoding down the road, but yeah you can just add it to the BSD modules

Closing since #502 has landed.


fixed segfault when only white space in input, protected add history

minishell PR message template and checklist.
Please fill in/check all the items below and PR!

Brief one-line summary of the fix
(Please write a short one-line summary/title of your fix here).

Main loop changed
small fix in parsing.c
change the parameter of process_input

Detailed description of the fix
(Please write more details about your fix here)
-Changed the loop for the shell prompt : added an history with add_history only if the prompt is not empty, and break to stop the prompt incase of a ctrl-d (which returns NULL)
-Fixed segfault when only white space in input, by adding "!*tokens" in parsing_tree function

I changed the process input parameter, because if we dont collect NULL, we dont have a way to stop the prompt, and also we can readline the prompt with readline and then give it to process_input.

Other questions
(Feel free to write any questions you have, things you noticed along the way, or anything else you want to share).

Tell if that dont modify the work you did, and if its okay for you like this.

What's Next

I'm doing the built-in after understanding of all the parsing
Starting to recreate the cd and env fct.

CheckList

[x] Check and follow the rules stated above
[x] You have completed the necessary tests and verified that the functionality works properly.
[x] You have written the code according to norminette.

keep a checklist and a summary of what features you've implemented

As I labeled it, your branch is conflicted ,so that needs to be resolved before i can review it


⚠ Roblox has degraded performance

In 02bc753, Roblox (https://www.roblox.com) experienced degraded performance:

HTTP code: 200
Response time: 869 ms

Resolved: Roblox performance has improved in 3e06db8.


How to defined RUNNER_LABELS in docker-compose file?

HI , i have create a docker-compose.yaml and try to run the runner with RUNNER_LABELS environment variable, but it doesn't work as expected.
here is my docker-compose.yaml file
version: "3.7"

services:
    runner:
      image: tcardonne/github-runner:latest
      environment:
        RUNNER_NAME: "my-runner"
        RUNNER_REPOSITORY_URL: ${RUNNER_REPOSITORY_URL}
        #RUNNER_ORGANIZATION_URL: ${RUNNER_ORGANIZATION_URL}
        GITHUB_ACCESS_TOKEN: ${GITHUB_ACCESS_TOKEN}
        RUNNER_LABELS: "my-runner"
      volumes:
        - /var/run/docker.sock:/var/run/docker.sock

after i docker-compose up, the runner did run successfully but without "my-runner" label attached.
Can you help me with this?
regards
dawnseeker8

What you did should work.
https://github.com/tcardonne/docker-github-runner/blob/21400f71b894946de9b75127ba0353807cde1135/docker/entrypoint.sh#L36

Actually after i switch the image from tcardonne/github-runner:latest to tcardonne/github-runner:ubuntu-20.04. then the label start working, but it didnt work for latest tag which use debian for so reason.


Add 'license' field to the index

Add licensing information to the Solr index.
Note: There may be an issue for this in the NCEAS metacat repo but I haven't found it yet.
TODO:

[ ] determine source elements from all supported document types
[ ] update necessary Spring application-context files
[ ] update unit tests

Metaadata dialects to implement this for:

[ ] Datacite
[ ] Dublin Core
[ ] Dryad
[ ] EML
[ ] FGDC
[ ] ISO
[ ] JSON-LD

@mbjones Some SoSo licenses have just a string, and some have both a name and a URL. I'm making the Solr field just a string (maybe it could be multiple strings, since multiple license are possible?) - in the latter case, do we want the name, the URL, or both?

I think we want both, and they can be multivalued (e.g., more than one license is applied to a given dataset). I'd definitely like the URLs indexed so that we can automate some search behaviors. For common license names like CC-0 and CC-BY, I wonder if we can supplement the name with a URL accurately if the URL is not provided. See the table https://github.com/ESIPFed/science-on-schema.org/blob/master/guides/Dataset.md#license that lists some common ones we might expect.

@nein09 I created a branch for you to work against on this feature: feature-2-add-license. Please commit your changes there and we can merge into develop via PR when you are ready for review and testing. Thanks!

A Dublin Core question: how does http://ns.dataone.org/metadata/schema/onedcx/v1.0 relate to this? Will those metadata documents ever have rights / license information?

Also, it looks like everything that's published on Dryad is CC0 by default: https://blog.datadryad.org/2011/10/05/why-does-dryad-use-cc0/ - should I account for that and just set everything that comes out of Dryad as CC0, regardless of how else it may be marked?

I'm not sure that FGDC even has much of a notion of rights or licensing. It looks like ISO allows (suggests?) licensing information in Abstract_Citation.

look at the XSDs in here for dublin core and everything else: https://github.com/NCEAS/metacat/tree/main/lib/schema
Dryad is using DataCite and schema.org so don't worry about Dryad because it's going to go away. It's worth grabbing a couple schema.org records from here https://so.test.dataone.org/mnTestDRYAD/v2/ and looking at them to see whether we're supporting that, and perhaps putting them in our tests, though.
FGDC doesn't seem to have the concept of licensing.
ISO: look at all these https://def.isotc211.org/ontologies/iso19115/
The XSD files are the way to go for this though, they'll show exactly what we are expecting.

In ISO, look under gmd (geospatial metadata)

ISO xpaths:
/*/metadataConstraints/MD_LegalConstraints/accessConstraints/MD_RestrictionCode/text()[normalize-space()] |
        /*/metadataConstraints/MD_LegalConstraints/useConstraints/MD_RestrictionCode/text()[normalize-space()] |
        /*/metadataConstraints/MD_LegalConstraints/otherConstraints/MD_RestrictionCode/text()[normalize-space()]

here's a one-size-fits-all license checker; it's worth double-checking whether what I came up with is the same as the paths in here:
https://github.com/NCEAS/metadig-checks/blob/main/src/checks/metadata.license.present.xml

What about license identifiers, like SPDX?

There are already some dryad-specific JSON-LD tests with license fields, so I think we're good on that front.

Make sure completed work has all been merged
If any remaining work to be done, open a new ticket (eg Dublin core, ISO?)

verified dublin core & iso have been merged (#45). Closing this issue


Script-Windows-10

Just pull request , for fix this error on this line at sudo su && wget https://kali.sh/xfce4.sh && cat xfce4.sh && sudo sh xfce4.sh && apt-get dist-upgrade -y --force-yes
Too sudo and adding sudo <-i>

Problem resolved


Spawn settings are wonky with the validation

Commands to reproduce:
/mvm set monsters false
/mvi 3
/mvm add spider monsters
/mvi 3

The result should be that monsters are, in fact enabled, at least in Bukkit. Multiverse should be false
If the Bukkit Setting is false no monsters will even attempt to spawn, and we can't filter them out.

That picture should never be possible, it should always be one of these:
False
True
spider

Result: Only spiders can spawn
OR
True
True
spider

Result: Anything except spiders can spawn
OR
True
True
''

Result: Anything can spawn
OR
False
False
''

Result: Nothing can spawn

Closing as fixed.


Tests: Add test cases using comments within SQL and JS statements

@seut discovered we did not have a single test case using SQL comments. This patch adds two corresponding test cases.

Can we also have a comment within an SQL statement?

Good idea. 01c153dc483437 adds a corresponding SQL statement.


[TT-523] Added Sepolia L2 Networks

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (a915f62) 31.07% compared to head (7054656) 31.13%.
Report is 2 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #779      +/-   ##
==========================================
+ Coverage   31.07%   31.13%   +0.05%
==========================================
  Files          41       41
  Lines        5352     5361       +9
==========================================
+ Hits         1663     1669       +6
- Misses       3510     3512       +2
- Partials      179      180       +1

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


transpiler reusing variables that should be unique

I have a custom node that takes json text and then outputs a whole bunch of different prompts for different purposes, scene, detailer, upscale, etc. the transpiler however uses the same variable for each of the outputs of the node:
Transpiler generates this:
string, string, _, _, _, _, string, string = PromptBuilder(string, 1910, 'realistic photo', 'hallway', 'woman', 'Lisa', '', 'lab coat', 'standing', 'looking down', 'tiled floor, mri machine', '', 'long shot, wide angle', '4K', '', '', 'glasses, gloves, carpet')
but each of those "string" is used in a different ksampler.

Could you share the workflow?

_simple_pdb.json
becomes:
image, _, positive, _, _, _, _, _, _, , filename, _ = SDPromptReader('ComfyUIxxy_00002.png', 0)
positive, positive, positive, positive, _, _, positive, positive = PromptBuilder(positive, 1529, '', '', '', '', '', '', '', '', '', '', '', '', '', '', '')
_, _, _ = SDPromptSaver(image, filename, positive, r'New\Deliberate_v4.safetensors', 'clearvae_main.safetensors',<PHONE_NUMBER>80631, 20, 8, 'euler', 'normal', None, 1, 1, positive, '', 'png', True, True, True, 100, '%Y-%m-%d', '%H%M%S', False, '')

Sorry for this late reply. Another one reported a similar bug with SplitSigmasDenoise today. It's now fixed. I can't find the Prompt Builder in your workflow to test, but they are very likely to be the same issue. Feel free to reopen this issue if it's still not fixed.


[FEATURE REQUEST] Upgrade Ansible to the latest version in V2.0.x

Is your feature request related to a problem? Please describe.
The current version of Ansible has a bunch of security issues:

CVE-2022-3697 High severity
CVE-2022-3697 High severity
CVE-2023-5115 Moderate severity
CVE-2023-5115 Moderate severity

Describe the solution you'd like
Upgrade Ansible to the latest version.
Describe alternatives you've considered
None
Additional context
None

DoD checklist

Changelog

[ ] updated
[ ] not needed

COMPONENTS.md

[ ] updated
[ ] not needed

Schema

[ ] updated
[ ] not needed

Backport tasks

[ ] created
[ ] not needed

Documentation

[ ] added
[ ] updated
[ ] not needed

[ ] Feature has automated tests
[ ] Automated tests passed (QA pipelines)

[ ] apply
[ ] upgrade
[ ] backup/restore

[ ] Idempotency tested
[ ] All conversations in PR resolved
[ ] Solution meets requirements and is done according to design doc
[ ] Usage compliant with license

ansible-core 2.17 (ansible 10.x) is incompatible with RHEL 8 (due to Python 3.6 dnf bindings).
We have the following options:

Upgrade to Ansible 9 instead of 10 (ansible-core 2.16 works with Python 3.6)
Use unofficial packages to provide dnf bindings for Python 3.11 - they were created by a RedHat employee but hard to say if they will be updated and continuously available.

https://github.com/ktdreyer/python-311-copr
https://copr.fedorainfracloud.org/coprs/ktdreyer/python3.11/packages/

Release two versions of Epiphany: for Ubuntu with Ansible 10, for RHEL with Ansible 9
Upgrade RHEL from 8 to 9

More info here:
https://github.com/ansible/ansible/issues/83357#issuecomment-2150254754
https://www.jeffgeerling.com/blog/2024/newer-versions-ansible-dont-work-rhel-8
We decided to choose option 1.

Option 1 will fix all open CV issues and while the main Ansible package is EOL from November 2024, ansible-core will be supported till EOL Epiphany in May 2025

Fixed with #3469


Add passes to replace uses of AMD extensions

Some extensions have become obsolete because they have equivalent functionality in new versions of spir-v.  For portability developers may want to change their spir-v module to remove the extensions.
For this issue we specifically want a pass to replaces uses of three extensions:

VK_AMD_shader_ballot
VK_AMD_gcn_shader
VK_AMD_shader_trinary_minmax

There are still two issues that need to be addressed for the three extension.  We cannot replace TimeAMD instructions because the Vulkan extension that enables SPV_KHR_shader_clock has not been released yet.
Also, the extension that allows OpGroup* instructions to work on 16-bit integers has not been release, as far as I know.


Added feature to export user data to csv file

Resolves #124
Changes made in this PR:

Added a button on user dashboard (left sidebar) to allow admins to export user data into csv file.
Added basic styles to the button.

Changes will be added

[ ]  Restrict feature to only super admin (depending on what Abdullah wants).
[ ]  Currently the extracted fields are hardcoded. May want to make it so that it works well with the config file (in #108).

Due to the way allusers is structured, swag data and all data that are not saved in allusers doc will now temporarily be removed from csv export.

Closed in favor of #188


High CVE in containerd/containerd & docker/docker

Even the latest version of https://github.com/helm/helm/releases/tag/v3.11.3 brings in the following versions
The High CVE's are found by aquasec scan are
- github.com/containerd/containerd: v1.6.15
"CVE-2023-25173--high
CVE-2023-25153--medium"
- github.com/docker/docker:  v20.10.21+incompatible
"CVE-2022-41720--high
CVE-2022-41716--high
CVE-2022-41721--high
CVE-2022-23471--medium
CVE-2022-41717--medium
CVE-2023-28840--
CVE-2023-28842--
CVE-2023-28841--"
They are fixed in versions

github.com/containerd/containerd:1.5.18, 1.6.18
github.com/docker/docker: "
20.10.22, 23.0.0-rc.1
20.10.22, 23.0.0-rc.4
23.0.0-rc.3
20.10.22, 23.0.0rc1
20.10.24, 23.0.3"

Please upgrade the  2 libraries in the next release of Helm.

Thanks for the report. Is the tool here simply reporting via the helm source dependency graph? Or is there further analysis to show that helm is impacted by there CVEs? (if the former, I suspect the urgency to fix here is low)
Since helm is a tool invoked via the cli, generally the scope/impact of such CVEs (in the helm cli context) is low. If you could kindly check the existing PRs for dependabot bumps. Or, submit PRs yourself, that would be greatly appreciated!

Please note, we do have scanning enabled for this repo: see https://github.com/helm/helm/security/code-scanning

Closing this. We use dependabot. You can view the security tab to see details.
If you're finding security issues not listed, they're probably a false positive from the security tool you're using.


RUM-3455 Cleanup SR code

What does this PR do?
This PR performs some cleanup in our Session Replay code

Use dependency injection instead of relying of default constructors for internal classes
Use interface instead of tight coupling with objects
Improves detection of background color based on drawables

Motivation
Originally, it was to better handle the mask layer in Ripple Drawables + the color of gradients when using tint (which resolves to a color filter).
And then I just tried to make the code cleaner and it impacted more in the end 😅

Codecov Report

Merging #1910 (a5ca09d) into develop (f46eb76) will increase coverage by 0.00%.
Report is 6 commits behind head on develop.
The diff coverage is 90.32%.

Additional details and impacted files
@@            Coverage Diff            @@
##           develop    #1910    +/-   ##
=========================================
  Coverage    83.38%   83.38%
=========================================
  Files          477      480     +3
  Lines        16922    17159   +237
  Branches      2514     2534    +20
=========================================
+ Hits         14109    14307   +198
- Misses        2120     2154    +34
- Partials       693      698     +5

Files
Coverage Δ

...m/datadog/android/core/internal/utils/NumberExt.kt
0.00% <ø> (ø)

...essionreplay/material/MaskSliderWireframeMapper.kt
100.00% <100.00%> (ø)

...d/sessionreplay/material/MaskTabWireframeMapper.kt
100.00% <100.00%> (ø)

...sessionreplay/material/MaterialExtensionSupport.kt
100.00% <100.00%> (ø)

...id/sessionreplay/material/SliderWireframeMapper.kt
97.47% <100.00%> (-0.03%)
:arrow_down:

...droid/sessionreplay/material/TabWireframeMapper.kt
98.33% <100.00%> (+0.22%)
:arrow_up:

...adog/android/sessionreplay/SessionReplayPrivacy.kt
100.00% <100.00%> (ø)

...dog/android/sessionreplay/SessionReplayRecorder.kt
96.15% <100.00%> (+1.03%)
:arrow_up:

.../sessionreplay/internal/recorder/MappingContext.kt
100.00% <100.00%> (ø)

...essionreplay/internal/recorder/SnapshotProducer.kt
88.24% <100.00%> (+0.36%)
:arrow_up:

... and 46 more

... and 26 files with indirect coverage changes


build: Add bazel wrapper

This wrapper is a simple shell script that handles downloading bazel.
This ensures that all developers are using the same supported version of
bazel, as well as keeping it in lockstep with CI. This also means
developers who aren't already using bazel don't have to figure out how
to install it on their system globally.
Signed-off-by: Keith Smiley<EMAIL_ADDRESS>

LGTM overall, but CI is failing:

line 1: ./bazelw: No such file or directory


feat(papi-v2): allow dispense liquid to a tiprack

Overview
Before 2.11, I was able to define a custom "tip_isolator", fill it with water and "park" reusable tips there. Now I cannot fill it with water and I have to do it manually
    # Define tip_isolator and water reservoir
    tip_isolator = ctx.load_labware(tiprack_type[tip_type], 11, 'Tip Isolator')
    res2 = ctx.load_labware('nest_12_reservoir_15ml', 2)

    # Add 300 uL of Water to each well in tip isolator
    ctx.comment('''Transferring 300 uL of water to
                each well in the tip isolator''')
    m300.pick_up_tip()
    m300.transfer(300, [well for well in res2.wells()[9:12]
                        for _ in range(4)][:cols],
                  tip_isolator.rows()[0][:cols], new_tip='never')
    m300.drop_tip()

Steps to reproduce
    # Define tip_isolator
    tip_isolator = ctx.load_labware(tiprack_type[tip_type], 11, 'Tip Isolator')

    # Add 300 uL of Water to each well in tip isolator
    ctx.comment('''Transferring 300 uL of water to
                each well in the tip isolator''')
    pick_up(m300, tip_isolator['A1'])
    m300.transfer(300, [well for well in res2.wells()[9:12]
                        for _ in range(4)][:cols],
                  tip_isolator.rows()[0][:cols], new_tip='never')
    m300.drop_tip(_drop(m300))

Current behavior
Error pops out
RuntimeError [line 426]: Cannot dispense to a tiprack

Expected behavior
I would like to be able to dispense water into my custom tipracks if I need to

Dispensing liquid to a tip rack is an error in a majority of protocols (see #7552), so I've reclassified this as a "feature request" rather than a bug. Disallowing aspirates/dispenses with tip-racks is fully intended behavior of the Protocol API.
We'll have to consider this idea of a "hybrid" labware that can be a receptacle for both liquids and tips a little carefully. In the mean time, you have a few options for workarounds:

Keep your protocol locked to the PAPI version you noted (2.10)

This has the downside of locking you out of unrelated bug fixes in future PAPI versions

Strip the labware information from the dispense location to bypass the tip-rack check

This may not work in some future PAPI version, but should hold up for now

This little snippet shows you how to strip labware information from a given well location:
from opentrons import types

...
tip_well = tip_rack.wells()[0]
tip_well_dispense_location = types.Location(
    point=tip_well.bottom(z=pipette.well_bottom_clearance.dispense).point,
    labware=None,
)
...

pipette.dispense(volume=20, location=tip_well_dispense_location)

Maybe a solution would be to throw an error when the tiprack is an Opentrons tiprack, but only throw a warning when the tiprack is custom?
Thank you for the workarounds you proposed. I didn't want to be stuck with version 2.10, but the second option seems good


Add an .editorconfig

I think it'd be a good idea to add an .editorconfig to the projects root for contributors to easily see the code-formatting style. I imagine the file would be something like this:
# https://editorconfig.org

root = true

[*]
charset = utf-8
end_of_line = lf
indent_size = 2
indent_style = space
trim_trailing_whitespace = true

[*.go]
indent_size = 8
indent_style = tab

[*.js]
insert_final_newline = true

[*.md]
trim_trailing_whitespace = false

Ref: https://editorconfig.org/. Let me know what you think, I'd be happy to open a PR for this.

Somebody familiar with the codebase should write down the requirements and check if the code is ready for this before "just" adding it. I broke a project recently with an activity like this :)
Other than this :+1:


Unable to assign NSG flow logs to custom defined network watcher

In the scenario where I define a network watcher as per below
network_watchers = {
    nwaue = {
        name = "aue"
        resource_group_key = "network"
        region             = "primary"
    }
}

When I attempt to link the NSG flow logs to a network watcher resource using  (network_watcher_key, network_watcher_rg_key), I find it does not work.
flow_logs = {
      version = 2
      enabled = true
      # we pick the default network watcher inside #NetworkWatcherRG
      # we use the network watcher in the current region (created by default)
      # this can be overwritten by specifying the following fields:
      network_watcher_key = "nwaue"
      network_watcher_rg_key = "network"

The NSG flows module always tries to link to a network watcher which uses the default resource group name (NetworkWatcherRG) and naming convention (in my case "NetworkWatcher_australiaeast"). Therefore I get this error on terraform apply
(Network Watcher "NetworkWatcher_australiaeast" / Resource Group "NetworkWatcherRG"): network.WatchersClient#SetFlowLogConfiguration: Failure sending request: StatusCode=0 -- Original Error: Code="ResourceNotFound" Message="The Resource 'Microsoft.Network/networkWatchers/NetworkWatcher_australiaeast' under resource group 'NetworkWatcherRG' was not found. For more details please go to https://aka.ms/ARMResourceNotFoundFix"
Looking at the code I believe the following is contributing to the issue.

The network watcher flow log module uses the network_watcher_rg_key to lookup the network watcher resource group, however
I think the first lookup will always fail as it is using the network_watchers list rather than the resource groups list to retrieve
the RG name.

https://github.com/aztfmod/terraform-azurerm-caf/blob/b7572e34382340d7dc4f33be70b342865d0c7e78/modules/networking/virtual_network/nsg/flow_logs/flow_logs.tf#L6

network_watchers variable is not passed from the virtual network module to the nsg module therefore defaults to empty

https://github.com/aztfmod/terraform-azurerm-caf/blob/b7572e34382340d7dc4f33be70b342865d0c7e78/modules/networking/virtual_network/module.tf#L62

Thanks @swilkodev for the detailed analysis. do you have a fix and want to try a PR or should we push further for triage and fix with the core team?

@arnaudlh sorry for the delay, tried to fix the issue, but no luck..
I found the network_watchers collection also seems to be keyed by the landing zone.  I also noticed the virtual network module contains two variables - network_watchers and netwatcher. I'm not familiar with the code base so best if the core team triages.

@swilkodev - no problem we are working on it - @SergioMiyama

Closing as integrated into 5.4.2


Error when call start_owner! with multiple repos

Elixir version
1.14.2
Database and Version
PostgreSQL 14.2
Ecto Versions
3.9.5
Database Adapter and Versions (postgrex, myxql, etc)
0.16.5
Current behavior
I’m using 2 repo in my project.
For testing some logic that uses both repos (ex. MyApp.Repo1, MyApp.Repo2), I tried to use sandbox mode with both repos.
defmodule MyApp.DataCase do
  ...
  setup tags do
    repos = tags[:repos] || [MyApp.Repo1]

    pids =
      repos
      |> Enum.map(fn repo ->
        Ecto.Adapters.SQL.Sandbox.start_owner!(repo, shared: not tags[:async])
      end)

    on_exit(fn ->
      pids
      |> Enum.map(fn pid ->
        Ecto.Adapters.SQL.Sandbox.stop_owner(pid)
      end)
    end)

    :ok
  end
  ...
end

But when I set repos option [MyApp.Repo1, MyApp.Repo2], an error occurs.
defmodule MyApp.SampleTest do
  use MyApp.DataCase, async: true

  @moduletag repos: [MyApp.Repo1, MyApp.Repo2]

  ...
end

23:49:07.982 mfa=DBConnection.Connection.disconnect/2 [error] Postgrex.Protocol (#PID<0.1735.0>) disconnected: ** (DBConnection.ConnectionError) client #PID<0.1845.0> timed out because it queued and checked out the connection for longer than 30000ms

Client #PID<0.1845.0> is still using a connection from owner at location:

    :prim_inet.recv0/3
    (postgrex 0.16.5) lib/postgrex/protocol.ex:3171: Postgrex.Protocol.msg_recv/4
    (postgrex 0.16.5) lib/postgrex/protocol.ex:2201: Postgrex.Protocol.recv_bind/3
    (postgrex 0.16.5) lib/postgrex/protocol.ex:2126: Postgrex.Protocol.bind_execute/4
    (ecto_sql 3.9.2) lib/ecto/adapters/sql/sandbox.ex:375: Ecto.Adapters.SQL.Sandbox.Connection.proxy/3
    (db_connection 2.4.3) lib/db_connection/holder.ex:354: DBConnection.Holder.holder_apply/4
    (db_connection 2.4.3) lib/db_connection.ex:1413: DBConnection.run_execute/5
    (db_connection 2.4.3) lib/db_connection.ex:1508: DBConnection.run/6
    (db_connection 2.4.3) lib/db_connection.ex:644: DBConnection.parsed_prepare_execute/5
    (db_connection 2.4.3) lib/db_connection.ex:636: DBConnection.prepare_execute/4
    (postgrex 0.16.5) lib/postgrex.ex:340: Postgrex.query/4
    (ecto_sql 3.9.2) lib/ecto/adapters/sql.ex:955: Ecto.Adapters.SQL.struct/10
    (ecto 3.9.5) lib/ecto/repo/schema.ex:756: Ecto.Repo.Schema.apply/4
    (ecto 3.9.5) lib/ecto/repo/schema.ex:369: anonymous fn/15 in Ecto.Repo.Schema.do_insert/4
    (ecto 3.9.5) lib/ecto/repo/schema.ex:265: Ecto.Repo.Schema.insert!/4
    test/my_app/sample_test.exs:14: MyApp.SampleTest.__ex_unit_setup_0_0/1
    MyApp.SampleTest.__ex_unit_describe_0/1
    (ex_unit 1.14.2) lib/ex_unit/runner.ex:505: ExUnit.Runner.exec_test_setup/2
    (ex_unit 1.14.2) lib/ex_unit/runner.ex:464: anonymous fn/2 in ExUnit.Runner.spawn_test_monitor/4
    (stdlib 4.1.1) timer.erl:235: :timer.tc/1

The connection itself was checked out by #PID<0.1845.0> at location:

    (postgrex 0.16.5) lib/postgrex.ex:340: Postgrex.query/4
    (ecto_sql 3.9.2) lib/ecto/adapters/sql.ex:955: Ecto.Adapters.SQL.struct/10
    (ecto 3.9.5) lib/ecto/repo/schema.ex:756: Ecto.Repo.Schema.apply/4
    (ecto 3.9.5) lib/ecto/repo/schema.ex:369: anonymous fn/15 in Ecto.Repo.Schema.do_insert/4
    (ecto 3.9.5) lib/ecto/repo/schema.ex:265: Ecto.Repo.Schema.insert!/4
    test/my_app/sample_test.exs:14: MyApp.SampleTest.__ex_unit_setup_0_0/1
    MyApp.SampleTest.__ex_unit_describe_0/1
    (ex_unit 1.14.2) lib/ex_unit/runner.ex:505: ExUnit.Runner.exec_test_setup/2
    (ex_unit 1.14.2) lib/ex_unit/runner.ex:464: anonymous fn/2 in ExUnit.Runner.spawn_test_monitor/4
    (stdlib 4.1.1) timer.erl:235: :timer.tc/1
    (ex_unit 1.14.2) lib/ex_unit/runner.ex:463: anonymous fn/4 in ExUnit.Runner.spawn_test_monitor/4

...
  1) test sample (MyApp.SampleTest)
     ...
     ** (DBConnection.ConnectionError) tcp send: closed (the connection was closed by the pool, possibly due to a timeout or because the pool has been terminated)
    stacktrace:
       (ecto_sql 3.9.2) lib/ecto/adapters/sql.ex:913: Ecto.Adapters.SQL.raise_sql_call_error/1
       (ecto 3.9.5) lib/ecto/repo/schema.ex:756: Ecto.Repo.Schema.apply/4
       (ecto 3.9.5) lib/ecto/repo/schema.ex:369: anonymous fn/15 in Ecto.Repo.Schema.do_insert/4
       (ecto 3.9.5) lib/ecto/repo/schema.ex:265: Ecto.Repo.Schema.insert!/4
       test/my_app/sample_test.exs:14: MyApp.SampleTest.__ex_unit_setup_0_0/1
       MyApp.SampleTest.__ex_unit_describe_0/1

Expected behavior
no errors

I asked about it in elixir forum, but there were no answers, so I posted it here.
https://elixirforum.com/t/error-when-call-start-owner-with-multiple-repos/55137

Hi,
I believe there should be no issue with it in principle. I wrote a simple test that passes: https://github.com/greg-rychlewski/ecto_sql/commit/d449f9875cd60a7bfac88f54725b7eeb3770fae6
From your error message something is timing out so it's probably related to the details of your situation. Are you able to post a minimal reproducible example?

Hi @nallwhy ,
Just wanted to check in. Did you resolve the issue reported here?

@greg-rychlewski Sorry! I failed to reproduce it. It was my fault.


autocomplete not working in mobile safari

Framework7 version: 4.4.3
Platform and Target: ios 12.2 mobile safari
Live Link or JSFiddle: https://jsfiddle.net/145ngkea/

Describe the bug
-1
i am using autocomplete for two input field which take the values from an array , if we select one the other change automatically  as you can see here in this website and it’s working on windows , mac and android but not on safari mobile as you can see in this video you can find my code here

i dig more in the problem .... it seams that the on: change event is not triggering on safari mobile  but work perfectly in all other platforms


HACS integration not working

I get the error below after a restart:
HTTP error occurred: 404 Client Error: Not Found for url: https://www.mijnafvalwijzer.nl/error
what could be the problem?
after installing the afvalwijzer in HACS, he created the folders himself in custom_components -> waste guide
after the restart of HA i added the following config:
sensor:
platform: afvalwijzer
provider: mijnafvalwijzer
postal_code: 0000XX
street_number: X
suffix: A.
include_date_today: false
default_label: None
after this another reboot

I get the error below after a restart:
HTTP error occurred: 404 Client Error: Not Found for url: https://www.mijnafvalwijzer.nl/error
what could be the problem?
after installing the afvalwijzer in HACS, he created the folders himself in custom_components -> waste guide
after the restart of HA i added the following config:
sensor:
platform: afvalwijzer
provider: mijnafvalwijzer
postal_code: 0000XX
street_number: X
suffix: A.
include_date_today: false
default_label: None
after this another reboot

maybe I miss something, or did I do something wrong?

After the suffix, I see an A, but behind it I see a dot, hence the error 404 not found.
The page you're trying to access doesn't exist with the street number, postal code and suffix provided, and most probabaly that's related to the dot.

thanks for your comment. i adjusted it but still get the same error. (see screenshot)

Im 100% sure this has nothing to do with the component itself, this is a config error. Ill help you out further through the hass community.

You could also set it to debug so you can actually see how the URL is parsed. This has to be put in your configuration.yaml
logger:
  default: info
  logs:
    custom_components.afvalwijzer: debug


[WIP DO NOT MERGE] api: instance and template details are free text

Problem: Users don't know what keys/values to enter for template and VM details.
Root Cause: The feature does not exist that can list possible details and options.
Solution: Based on the possible VM and template details handled by the
codebase, those details were refactored and a list API is introduced
that can return users those details along with possible values. When
users add details now, they will be presented with a list of key details
and their possible options if any.
Introduces a new API:
listDetailOptions: Lists all possible details and their options for a resource type such as a VM or a template
Required params: resourcetype,
API Params               Type     Description
==========               ====     ===========
resourceid               string   the UUID of the resource (optional)
resourcetype             string   the resource type such as UserVm, Template etc.

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] New feature (non-breaking change which adds functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

Screenshots (if appropriate):

@blueorangutan package

@borisstoyanov a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

@rhtyd there's some build failures with this one, can you have a look?
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ cloud-plugin-network-vcs ---
[INFO] Deleting /jenkins/workspace/acs-pr-centos6-pkg-builder/dist/rpmbuild/BUILD/cloudstack-<IP_ADDRESS>-SNAPSHOT/plugins/network-elements/brocade-vcs (includes = [target, dist], excludes = [])
[INFO]
[INFO] --- maven-checkstyle-plugin:3.0.0:check (cloudstack-checkstyle) @ cloud-plugin-network-vcs ---
/opt/rh/maven30/root/usr/bin/mvn: line 9:  2041 Killed                  $M2_HOME/bin/mvn "$@"
error: Bad exit status from /var/tmp/rpm-tmp.ozlF7H (%build)

RPM build errors:
    Bad exit status from /var/tmp/rpm-tmp.ozlF7H (%build)
+ '[' 1 -ne 0 ']'
+ '[' false == true ']'
+ echo 'RPM Build Failed '
RPM Build Failed
+ exit 3
Build step 'Execute shell' marked build as failure
Stopping all containers
Finished: FAILURE

Packaging result: ✖centos6 ✔centos7 ✔debian. JID-2653

@borisstoyanov looks like an env issue, let's try again
@blueorangutan package

@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: ✔centos6 ✔centos7 ✔debian. JID-2657

@blueorangutan test

@borisstoyanov a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

Trillian test result (tid-3458)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 37191 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr3240-t3458-kvm-centos7.zip
Intermittent failure detected: /marvin/tests/smoke/test_privategw_acl.py
Intermittent failure detected: /marvin/tests/smoke/test_vpc_redundant.py
Smoke tests completed. 69 look OK, 1 have error(s)
Only failed tests results shown below:

Test
Result
Time (s)
Test File

test_04_rvpc_privategw_static_routes
Failure
966.29
test_privategw_acl.py

Thanks for reporting the issue @borisstoyanov - the issue was missing role permission/authorization for the new API. I've fixed it.
@blueorangutan package

@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: ✔centos6 ✔centos7 ✔debian. JID-2676

@blueorangutan test

@rhtyd a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

Trillian test result (tid-3469)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 33155 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr3240-t3469-kvm-centos7.zip
Intermittent failure detected: /marvin/tests/smoke/test_vpc_redundant.py
Smoke tests completed. 69 look OK, 1 have error(s)
Only failed tests results shown below:

Test
Result
Time (s)
Test File

test_05_rvpc_multi_tiers
Failure
413.21
test_vpc_redundant.py

test_05_rvpc_multi_tiers
Error
440.47
test_vpc_redundant.py

With https://github.com/apache/cloudstack/pull/3213, users won't be able to see the details admin decides to block. However, it's a presentation limitation only. With this FR, the user is only allowed a set of details that I thought can be allowed in most/all cases. (we can discuss/add/remove the details we want to export or not)
WIth https://github.com/apache/cloudstack/pull/3244, users will alway see the tab and that some details may always be shown to the user but not allowed to edit. This again is a presentation limitation, a smart use can still use the API/cmk.

@blueorangutan package

@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: ✔centos6 ✔centos7 ✔debian. JID-2813

@blueorangutan test

@rhtyd a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

Trillian test result (tid-3614)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 31444 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr3240-t3614-kvm-centos7.zip
Smoke tests completed. 70 look OK, 0 have error(s)
Only failed tests results shown below:

Test
Result
Time (s)
Test File

@rhtyd do you plan to address the comments?

@borisstoyanov the comments are asking for refactoring, no changes in functionality. Yes, I'll try to address them.

@borisstoyanov due to codebase limitations that will require a rather new set of refactorings, I'm not going to address the comments.
There is no easy way to centralise all the details and their options without hardcoding them in current design. Even if I write an interface that the sub-systems will implement, those options will partly spread in the sub-systems where they would be hard-coded. We can go with the hardcoded option values for now, and maybe address them in future.

Thanks @rhtyd, proceeding with testing this as is.

@blueorangutan package

@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: ✖centos6 ✖centos7 ✖debian. JID-2889

@blueorangutan package

@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: ✔centos6 ✔centos7 ✔debian. JID-2890

@blueorangutan test

@rhtyd a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

@blueorangutan package

@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: ✔centos6 ✔centos7 ✔debian. JID-2892

Trillian test result (tid-3694)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 28402 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr3240-t3694-kvm-centos7.zip
Smoke tests completed. 71 look OK, 0 have error(s)
Only failed tests results shown below:

Test
Result
Time (s)
Test File

@blueorangutan package

@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: ✔centos6 ✖centos7 ✔debian.  I'll keep you posted as I make progress.

Packaging result: ✔centos6 ✔centos7 ✔debian. JID-2904

Last change is UI only change to show all possible drop down options while editing an existing detail. No smoketests needed.

@blueorangutan package

@PaulAngus a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: ✔centos6 ✔centos7 ✔debian. JID-2914

@blueorangutan package

@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Fixed few minor issues cc @borisstoyanov @andrijapanic - Kindly kick packaging and build new Trillian env to review. Thanks.

@blueorangutan package

@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

@blueorangutan package

@borisstoyanov a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

@blueorangutan package

@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: ✔centos6 ✔centos7 ✔debian. JID-14

@blueorangutan test

@rhtyd a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

Trillian test result (tid-16)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 30315 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr3240-t16-kvm-centos7.zip
Intermittent failure detected: /marvin/tests/smoke/test_privategw_acl.py
Smoke tests completed. 71 look OK, 0 have error(s)
Only failed tests results shown below:

Test
Result
Time (s)
Test File

Lgtm received from @andrijapanic - can you confirm on the PR. I'll merge this based on testing and review.

LGTM


OnCopyFromItemOnAfterCheck Event in Purchase Line missing Call by Reference

Hello there,
in BC19 the Event "OnCopyFromItemOnAfterCheck" in the Purchase Line has the Record "PurchaseLine" not as call by reference.
In the Event "OnCopyFromItemOnAfterCheck" from the Sales Line, it is call by reference.
Is there a way, you could add it in the upcoming versions? It's kind of misleading.
Thanks in advance

wrong repo, you want https://github.com/microsoft/AlAppExtensions/issues

Sorry :(
Is there a way to move it?

Thanks for the feedback. And yes, you'll want the https://github.com/microsoft/AlAppExtensions/issues repo instead. Unfortunately, we don't have an automatic way of moving this.

It looks like this was requested/claimed to be fixed in https://github.com/microsoft/ALAppExtensions/issues/7312 but evidently didn't take...


The padding of Conv2d and Pool22 not support SAME_UPPER, SAME_LOWER

Now the singa's padding is, we assign a value, and it adds the amount of value's padding at both sides of head and tail.
However, according to the onnx doc, there are four types of padding method, which are NOTSET, SAME_UPPER, SAME_LOWER or VALID. Singa cannot support SAME_UPPER, SAME_LOWER yet.

SAME_UPPER or SAME_LOWER mean pad the input so that the output spatial size match the input. In case of an odd number add the extra padding at the end for SAME_UPPER and at the beginning for SAME_LOWER.

For example, the input is 32*32, the stride is 1, the kernel is 4*4, and output is same, we need to add (3,3) zeros totally, each side is 3/2 = 1.5, cannot work basing on the current setting of singa.

@joddiy Has the issues been fixed?

yes, by PR #612


Reduce cardinality

towards https://github.com/giantswarm/giantswarm/issues/30422

If PR is ok, let's deploy it on viking only and see how it goes


azure-mgmt-advisor returns invalid resource ID

I received a resource ID from the Advisor Recommendations - list method which failed validation/parsing by the functions in msrest.tools.
Here is the resource ID which failed validation with identifying information removed. I did nothing but access the id attribute of the returned recommendation object:
/subscriptions/<uuid>/resourceGroups/<rg>/providers/Microsoft.Compute//providers/Microsoft.Advisor/recommendations/<recommendation_id>

I don't think the /providers/Microsoft.Compute/ segment should be present in this string. Normally these resources only have /providers/Microsoft.Advisor/recommendations/ present.
Here are the relevant packages installed:
azure-common==1.1.16
azure-mgmt-advisor==2.0.1
msrestazure==0.6.1

Hi @wesley-smith thank you for reporting this, someone from our team is going to take a look at this


Missing translations

Is your feature request related to a problem? Please describe.
Some parts of the website are not translated (code-wise)
Describe the solution you'd like
Add the parts of the website to translation.json so they can be translated
Additional context
Here are the missing translations I could find :

Dates in the explore rooms card

The currently listening card ("listener", "leave")

Debug audio button

Sounds

App names in the programmed rooms reminder dropdown
That's all I could find

Missing translations for the "with" in the room view


Should we default to long for integer types?

Spec doesn't define that integer type is int32 .

Blocked by https://github.com/Azure/autorest.modelerfour/issues/288

From https://github.com/Azure/autorest.modelerfour/issues/288#issuecomment-649063965 -

I just read back over the initial conversation that @pakrym linked in the issue description. It sounds like there isn't anything actionable to do in AutoRest/Modelerfour at this moment, correct?

@johanste's proposal was mainly to add a linting rule (which @lmazuel filed a request for) and gradually get all service Swaggers to explicitly specify the format for each usage of integer. I got the impression that we want to hold off on making int64 the default for now since that might be an unexpected change for service teams (and SDK library users).


Release v1.28.1+k3s1 isn't marked as latest

Not sure if this is intentional, but the release v1.28.1+k3s1 isn't marked as latest. This results in our update script not being able to catch it automatically:
K3S_VERSION=$(curl -fsSL -o /dev/null -w %{url_effective} https://github.com/k3s-io/k3s/releases/latest | rev | cut -d / -f 1 | rev)

Not a big problem though, just a friendly reminder to you guys.

Nope. We don't want it marked as latest, due to the init container issue called out in the release notes. We'll mark v1.28.2 latest, after it is released by upstream next week.


Fix a display problem when entering text after the size of TextEdit extends off the screen on the web

If you enter a large number of line breaks where the height of TextEdit exceeds the height of the browser window, and then enter more non-line breaks, the egui screen will be driven out of the client area
Also, since scrolling is currently disabled in a browser itself, there doesn't seem to be much benefit in changing the position of the text_agent
I apologize for my terrible English

@emilk
I'd like to hear what @n2 thinks, but for now, I've reverted the previous wrong code and added the code to restrict the position of the text agent to within the client area.
I've also checked the IME position tracking. There is a subtle difference in the IME position tracking compared to the browser native text input, but it seems to be a practical problem.

Note: For some reason the CI test was failing, so I rebased to the latest master branch. When I did that, the old commits you had linked to the review comments disappeared.

As mentioned in the comments, move_text_cursor() is used to move IME candidate window following egui's cursor. It is better to constrain the position within the canvas, rather than just delete the function. I think your newly submitted code is suitable. Thank you for fixing the overlooked part of my code. @sumibi-yakitori


Fix the return values for sadd, srem, smove, persist, hset, and hsetnx

This change fixes the return values for sadd, srem, smove, persist, hset, and hsetnx so that redis-rb properly returns true / false for those calls.

Thanks for your fixes!!! I will release a new version soon with your changes.
I've added you as collaborator, you can now commit directly to the project or you can continue working in your repository and later merge your changes here.

Thanks for making me a collaborator :)  The gem is getting closer and closer to being a simple drop-in replacement.


Avro message deserialization error

I tried to deserialize the Avro message and I got back this error:
ERRO[0011] a panic occurred during JS execution: runtime error: invalid memory address or nil pointer dereference.

Hey @takdan01,
Please provide me with an example script, as I won't be able to reproduce this based on this log message.

Hello @mostafa,
I would like to get the Avro schema from schema-registry and deserialize the Kafka message with Avro schema.
`import {
Reader,
Connection,
SchemaRegistry,
SCHEMA_TYPE_AVRO,
} from "k6/x/kafka";
export function deserialization(message){
const schemaRegistry = new SchemaRegistry({
url: KAFKA.SCHEMA_REGISTRY_URL
});
if(typeof(message) != "undefined" ){
let deserializedValue = schemaRegistry.deserialize({
data: message,
schemaType: SCHEMA_TYPE_AVRO,
});
return deserializedValue;
}
else {
return null
}
}`

@takdan01
You are not passing the schema to deserialize method, which is why it is not working. Please have a look at this example script and use the getSchema method to get the schema from Schema Registry.

I wrote this small code what it tries to get schema from Schema Registry and I got same error what mentioned before.
ERRO[0010] panic: runtime error: invalid memory address or nil pointer dereference
export function getSchema(schemaSubject){     console.log(schemaSubject)     let valueSchema = schemaRegistry.getSchema(schemaSubject);     console.log(valueSchema);     return valueSchema; }

Try this instead:
export function getValueSchema(schemaSubject){
    console.log(schemaSubject)
    // 0 means the latest version of the schema.
    let valueSchema = schemaRegistry.getSchema({version: 0, subject: schemaSubject});
    console.log(valueSchema);
    return valueSchema;
}

Thanks your help. Now the code is working.


ERROR Can't find stylesheet to import when I have @use in my scss files

TBH I am new in esbuild area and tried to move my current webpack configuration to esbuild. Here is my esbuild configuration file.
import {sassPlugin} from 'esbuild-sass-plugin'
import path from 'path'
import { fileURLToPath } from 'url';

const __filename = fileURLToPath(import.meta.url);
const __dirname = path.dirname(__filename);

await esbuild.build({
    entryPoints: [
        { out: 'frontend', in: './resources/ts/frontend/index.ts'},
        { out: 'block-editor', in: './resources/ts/block-editor/index.ts'},
        { out: 'global', in: './resources/ts/global/index.ts'},
    ],
    bundle: true,
    minify: true,
    outdir: 'assets',
    plugins: [
        sassPlugin(),
    ],
}).catch(() => process.exit(1));

So when running npm run build I am getting the following errors pointing that unable to find the stylesheet to import.

Any ideas how can I fix the issue?

I have been successfully using @use in my SCSS files with this plugin for a couple of months.
However, on the way I did note #136 where using @ in the paths was causing an error.
Perhaps use a different path prefix?  #136 has a  good description and response to this problem.
I am just revisiting the issue as  I have changed my path structure and need to rewrite my importmapper.


Two instances launch, as many of us use it

Could it be possible to put in --config parameters in commande line, two config files ?
Or another way coud be to add another ASSET in config.watch when using the same configuration for those two assets.

You want to watch 2 markets at the same time (with the same config / strategy?)
--
You have to run 2 gekkos for that..
Something that makes this trivial is being worked on (just got back from a holiday, will pick it up soon) in the web-wrapper branch:
https://github.com/askmike/gekko/blob/web-wrapper/core/workers/pipeline/parent.js
With that you could create a simple script like:
// helper
var _ = require('lodash');

// load the helper
var pipeline = require('core/workers/pipeline/parent.js');

// first config is your json file
var config1 = require('your-config.json');

// copy it for second config
var config2 =_._.cloneDeep(config1);

// change the asset
config2.watch.asset = 'your-second-asset';

// start 2 gekkos
pipeline('realtime', config1, () => console.log);
pipeline('realtime', config2, () => console.log);

--
Your only goal is to listen to two different markets on the same exchange? Or do you want to create a strategy that uses two markets as input?

listen 2 market in same xchange but cant launch 2 gekko because old bug :
{ Error: SQLITE_BUSY: database is locked
at Error (native) errno: 5, code: 'SQLITE_BUSY' }

@tinyrobot yes a PR sound great! Did you implement postgres as a different adapter?

I've implemented the datastore in such a way that you are able to add an adapter (that exposes a Reader and a Writer object). You can then configure and set your adapter in the config. But there is no documentation yet.. Let me know if you run into anything.

I've made a simple PR #446 to resolve multi instance, WAL is working

I'm sorry WAL isnt working in our case your rigth

You can run it in docker and volume mount in a unique config file for each instance.

This is old, but:
I have two gekkos running now, one that inserts data into a DB and one that retrieves this data. This way you can have 1 watcher and potentially 100 different leechers (strats). Read more here.

I've disabled WAL and now we can finally use this :)

You want to watch 2 markets at the same time (with the same config / strategy?)
You have to run 2 gekkos for that..
Something that makes this trivial is being worked on (just got back from a holiday, will pick it up soon) in the web-wrapper branch:
https://github.com/askmike/gekko/blob/web-wrapper/core/workers/pipeline/parent.js
With that you could create a simple script like:
// helper
var _ = require('lodash');

// load the helper
var pipeline = require('core/workers/pipeline/parent.js');

// first config is your json file
var config1 = require('your-config.json');

// copy it for second config
var config2 =_._.cloneDeep(config1);

// change the asset
config2.watch.asset = 'your-second-asset';

// start 2 gekkos
pipeline('realtime', config1, () => console.log);
pipeline('realtime', config2, () => console.log);

Your only goal is to listen to two different markets on the same exchange? Or do you want to create a strategy that uses two markets as input?

Thank you for the tip.
Anyway to get output/error output with that code ? I get no log from () => console.log ... But if I start the "your-config.json" alone I have error.


cannot evaluate unversioned components from central.sonatype.com

Describe the bug
recent "unversioned" urls were recently added to central.sonatype.com
they can't be evaluated by the extension version 2.10.7
To Reproduce
see for example https://central.sonatype.com/artifact/commons-io/commons-io/overview
Expected behavior
given latest version is displayed at this url, the browser extension should extract that version and evaluate
Screenshots

:tada: This issue has been resolved in version 2.11.0 :tada:
The release is available on:

Chrome Web Store
v2.11.0
GitHub release

Your semantic-release bot :package::rocket:


Python 3 compatibility issue in from_url() parsing logic

Today I ran into the following issue in redis==2.10.6; it appears there is some occasional incompatibility between this bit of URL-handling code and Python 3 which is throwing an exception back to my client code. I did some searching but didn't see anyone else that ran into this yet.
> .../venv/lib/python3.6/site-packages/redis/connection.py(839)from_url()
--> 839         if '?' in url.path and not url.query:
    840             # chop the querystring including the ? off the end of the url

ipdb> url
ParseResultBytes(scheme=b'', netloc=b'', path=b'', params=b'', query=b'', fragment=b'')
ipdb> '?' in url.path
*** TypeError: a bytes-like object is required, not 'str'
ipdb>

This same issue just popped up for me out of the blue. Not sure what could have changed.

I just migrated a project from python 3.5 to 3.6 and looks like the newer version is more strict

hi @megahall
Piece of code causing the issue (and the line if '?' in url.path and not url.query: in particular) was removed
I believe the problem is not present since version 3.0

Yes, this was fixed as part of 3.0. Sorry for not commenting about it in this issue when 3.0 was released.


Why not upstream?

Given you're able to shave so many seconds setting up Go, any reason the hack isn't upstreamed to actions/setup-go?

I hope this does eventually get pulled into actions/setup-go in some form.
It's been just 8 days since the first commit to this project. I don't expect the setup-go maintainers to be interested in pulling this in just yet.
I'm afraid the biggest performance improvement would be a breaking change too. Most of the improvement to Windows installs comes from installing to RUNNER_WORKSPACE instead of RUNNER_TOOL_CACHE, and there are probably some users of setup/go who expect it to end up in RUNNER_TOOL_CACHE.
🤞 for this eventually becoming actions/setup-go@v3

I hope this does eventually get pulled into actions/setup-go in some form.
It's been just 8 days since the first commit to this project. I don't expect the setup-go maintainers to be interested in pulling this in just yet.
I'm afraid the biggest performance improvement would be a breaking change too. Most of the improvement to Windows installs comes from installing to RUNNER_WORKSPACE instead of RUNNER_TOOL_CACHE, and there are probably some users of setup/go who expect it to end up in RUNNER_TOOL_CACHE.
🤞 for this eventually becoming actions/setup-go@v3


[Error] Compact Tension Example: DimensionMismatch

name: Compact Tension Example: DimensionMismatch
about: File an issue
title: '[Error] < Compact Tension Example: DimensionMismatch  >'
labels: Error
assignees: ''

Current Behavior:

Example fails at the beginning of the verlet solver ⭕
Expected Behavior:

Successful run of the example as in previous tests.
Steps To Reproduce:

julia> PeriLab.main("examples/Compact_Tension/CompactTension.yaml")
PeriLab Version: 1.0.6
┌ Warning: No current git info.
└ @ PeriLab ~/.julia/packages/PeriLab/pZpHW/src/PeriLab.jl:210
[ Info: Read input file examples/Compact_Tension/CompactTension.yaml
[ Info: Read mesh file examples/Compact_Tension/CompactTension.txt
[ Info: Read node sets
[ Info: 2d problem assumed, please define plane stress or plane strain if needed in Physics
[ Info: Init Neighborhoodlist
[ Info: Finished init Neighborhoodlist
[ Info: Apply bond filters
[ Info: Finished applying bond filters
[ Info: Start distribution
[ Info: Finished distribution
[ Info: Create Overlap
[ Info: Finished Overlap
[ Info: Mesh input overview
[ Info: -------------------
[ Info: Number of nodes: 9996
[ Info: Geometrical degrees of freedoms: 2
[ Info: -------------------
[ Info: Synchronize data over cores
[ Info: Get node sets
[ Info: FEM option is set to false
[ Info: Finish init data
[ Info: Init solver
[ Info: Read properties
[ Info: Init models
[ Info: Init damage models
[ Info: Init material models
[ Info: Init pre calculation models
[ Info: Init Boundary Conditions
[ Info: Init Verlet
[ Info: =======================
[ Info: ==== Verlet Solver ====
[ Info: =======================
[ Info: Initial time: 0.0 [s]
[ Info: Final time: 0.0002 [s]
[ Info: Minimal time increment: 3.715470789352762e-7 [s]
[ Info: Safety Factor: 0.95
[ Info: Time increment: 3.527336860670194e-7 [s]
[ Info: Number of steps: 567
[ Info: Numerical Damping 5.0e-6
[ Info: Finished Init Solver
[ Info: Init write results
[ Info: Create output examples/Compact_Tension/CompactTension_Output1.e
[ Info: Create output examples/Compact_Tension/CompactTension_Output2.e
[ Info: Run Verlet Solver
0.0%┣                                                                                ┫ 0/568 [00:00<00:00, -0s/it]
ERROR: DimensionMismatch: arrays could not be broadcast to a common size; got a dimension with lengths 28 and 56
Stacktrace:
[1] _bcs1
@ ./broadcast.jl:555 [inlined]
[2] _bcs
@ ./broadcast.jl:549 [inlined]
[3] broadcast_shape
@ ./broadcast.jl:543 [inlined]
[4] combine_axes
@ ./broadcast.jl:524 [inlined]
[5] _axes
@ ./broadcast.jl:236 [inlined]
[6] axes
@ ./broadcast.jl:234 [inlined]
[7] combine_axes
@ ./broadcast.jl:524 [inlined]
[8] _axes
@ ./broadcast.jl:236 [inlined]
[9] axes
@ ./broadcast.jl:234 [inlined]
[10] combine_axes
@ ./broadcast.jl:524 [inlined]
[11] _axes
@ ./broadcast.jl:236 [inlined]
[12] axes
@ ./broadcast.jl:234 [inlined]
[13] combine_axes
@ ./broadcast.jl:524 [inlined]
[14] _axes
@ ./broadcast.jl:236 [inlined]
[15] axes
@ ./broadcast.jl:234 [inlined]
[16] combine_axes
@ ./broadcast.jl:524 [inlined]
[17] instantiate
@ ./broadcast.jl:306 [inlined]
[18] materialize
@ ./broadcast.jl:903 [inlined]
[19] compute_weighted_volume(nodes::SubArray{…}, nlist::SubArray{…}, undeformed_bond::SubArray{…}, bond_damage::SubArray{…}, omega::SubArray{…}, volume::SubArray{…})
 Use show(err) to see complete types.

It has to do with the anisotropic damage. If you use the correspondence material it should work. For the PD solid we will make a fix and a test on Monday.

Perfect. I will give it a try early next week. Thank you @CWillberg !!


React

I am not an expert about React or Angular, so my question maybe can be silly: I would like to know if AdminLTE can be used with React.
Thanks
Armando

Yes, it can be... you can componentize the admin-lte using react pretty easily, here is a basic app
https://github.com/rafakwolf/curso-reactjs/tree/master/my-money-app/frontend


Dependency error - GiftedSpinner

Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: undefined. Check the render method of GiftedSpinner.

I got the same error, is there something wrong?

@sunkehappy This error is fixed in 9b8d939e0feadd728e44fe865c36c524ff6a3a77

Is this released? How would I fix this on my local?

@sunkehappy It's not yet published on the npm yet. We'll do so once upgraded in ES6 syntax.
Meanwhile, you can npm uninstall the existing repo, and instead install using
npm install https://github.com/FaridSafi/react-native-gifted-listview.git. Your code remains the same, just the repo source is changed.
You can also make manual change in node_modules as a temporary solution, but would not recommend that.


⚠ Fortnite has degraded performance

In bec7dd7, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 200
Response time: 1505 ms

Resolved: Fortnite performance has improved in 657e8f5.


Publish the package

Publish it on pip

Resolved https://github.com/tusharmakkar08/Facebook_Graph_Search_Images/commit/20ec313e7022b1e716a29ff92392ca3cf0e05e3b


change a text in lb_fullwidth_details_overview

can you please help me to know how can I change the text below the poster in leanback details view content?
I added this text to lb_fullwidth_details_overview.xml file but I couldn’t understand how can I change it!
thank you in advance.

See https://stackoverflow.com/questions/67804830/change-leanback-details-view-content-fragment


AMM Unit tests: rounding down of equal asset deposit LPToken calculation

High Level Overview of Change
This PR exercises a specific portion of the AMMHelpers.cpp file. It triggers a downward rounding of LPTokens in adjustLPTokens function in the AMMHelpers.cpp file.

Context of Change

Type of Change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Refactor (non-breaking change that only restructures code)
[ ] Performance (increase or change in throughput and/or latency)
[x] Tests (you added tests for code that already exists, or your new feature included in this PR)
[ ] Documentation update
[ ] Chore (no impact to binary, e.g. .gitignore, formatting, dropping support for older tooling)
[ ] Release

API Impact

[ ] Public API: New feature (new methods and/or new fields)
[ ] Public API: Breaking change (in general, breaking changes should only impact the next api_version)
[ ] libxrpl change (any change that may affect libxrpl or dependents of libxrpl)
[ ] Peer protocol change (must be backward compatible or bump the peer protocol version)
No impact on performance. No change to APIs

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 76.11%. Comparing base (4bcbf70) to head (2db3500).
Report is 7 commits behind head on develop.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #4982      +/-   ##
===========================================
- Coverage    76.98%   76.11%   -0.87%
===========================================
  Files         1129     1129
  Lines       131872   129479    -2393
  Branches     39549    39554       +5
===========================================
- Hits        101517    98559    -2958
- Misses       24392    24860     +468
- Partials      5963     6060      +97

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

This looks good to me.  But I was hoping it would hit these lines: https://app.codecov.io/gh/XRPLF/rippled/pull/4982/blob/src/ripple/app/misc/impl/AMMHelpers.cpp#L171. And I don't have a good explanation as to why it didn't.  Nevertheless, this looks like a good addition to me.

@HowardHinnant  I have updated the numbers so that the execution hits the necessary lines.
I expected 10'000.1 to be rounded down to 10'000 and consequently hit the said line. I think my debugger is malfunctioning.


Introduce IValueObserver interface

Summary and Histogram could have more generic interface to contain the single method:
Observe(double value)
Extension methods for convenient way to measure duration of actions/functions execution would be helpful as well.

Implemented


Move default case to bottom of all switch statements

A thing of beauty is a joy forever.
A thing of consistency is a joy for as long as it remains consistent.

@mattnibs: Didn't find one with a quick search.


SSR error (Gatsby)

When using SSR in Gatsby, the build stage throws the following error:
 ERROR #95313

Building static HTML failed for path "/"

See our docs page for more info on this error: https://gatsby.dev/debug-html

  72 |         };
  73 |     }, [autoPlay, hlsConfig, playerRef, src]);
> 74 |     if (Hls.isSupported())
     |         ^
  75 |         return React.createElement("video", __assign({ ref: playerRef }, props));
  76 |     return React.createElement("video", __assign({ ref: playerRef, src: src, autoPlay: autoPlay }, props));
  77 | }

It appears to be coming from hls.js. The problem is that any reference to window or document will throw an error during SSR, although this appears to have been rectified in subsequent versions of hls.js (the latest version doesn't seem to mention either window or document). Might be worth bumping the version in your package.json.
For anyone stumbling across this issue, a quick fix is to conditionally render your <ReactHlsPlayer /> component, dependant on whether or not window is defined:
import React from "react";
import ReactHlsPlayer from 'react-hls-player';

const MyVideoComponent = (props) => {
  return (
    typeof window !== "undefined" ?
      <ReactHlsPlayer src={src} />
    : null
  );
};
export default MyVideoComponent;

Cheers.

Hey @lewisdonovan , thanks for the quick fix!
As for an actual fix, it should be as simple as using ssr-window, or implementing it manually (super small package). It's my personal go-to for SSR-friendly code.
Also refactoring the package code with optional chaining, really helps prevent further bugs.


[Enhancement] Automatic execution of LongTapCommand

Hello,
If I use the LongTap command, it will only be executed if it is held down for some time and then released.
As a user, I would find it better if I only have to hold down for a while and then the command is executed automatically.
What do you mean?

I experienced the same issue.
In my case, I have a view wich I attach two commands:

Tap: to navigate to another page;
LongTap: to display an action sheet;

When I tap the view, it navigates to another page as expected. If I long press the view, it navigates to the page (behavior wich is expected in a single short tap) and when I release the action sheet is displayed (the behavior expectd in a long tap).
Additional info:
Xamarin.Forms on Android
Xamarin.Forms version: <IP_ADDRESS>1221


Create  Validate Stack Sequences.py

Related Issue
Closes: #763
Describe the changes you've made
added new file
Describe if there is any unusual behaviour of your code(Write NA if there isn't)
NA
Language used for coding
Python
Checklist:

[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have documented the code.
[x] New and existing unit tests pass locally with my changes.

All some more and effective comments.


chore: move unused jsonwebtoken to devDependencies

This moves amplify-appsync-simulator unused runtime dependency jsonwebtoken to devDependencies

@panva  could you please resolve the conflicts in this PR


NetworkPolicy denies communication with EKS Pod Identity Agent

Is there an existing issue for this?

[X] I have searched the existing issues

Version
equal or higher than v1.14.13 and lower than v1.15.0
What happened?
When NetworkPolicies configured, pods can't communicate with EKS Pod Identity Agent on http://<IP_ADDRESS>/v1/credentials
<IP_ADDRESS>:80 is actually port on the daemon set with hostNetwork: true:

https://docs.aws.amazon.com/eks/latest/userguide/pod-identities.html#pod-id-considerations

Everything works with network policy like:
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  name: test-policy
spec:
  egress:
  - {}
  podSelector:
    matchLabels:
      component: my-pod
  policyTypes:
  - Egress

But it stops working when any egress rule is added, for example:
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  name: test-policy
spec:
  egress:
  - to:
    - ipBlock:
        cidr: <IP_ADDRESS>/0
  podSelector:
    matchLabels:
      component: my-pod
  policyTypes:
  - Egress

Hubble reports following:
my-test-pod:38762 (ID:97997) <> <IP_ADDRESS>:80 (host) policy-verdict:none EGRESS DENIED (TCP Flags: SYN)

How can we reproduce the issue?

Install cilium helm
Install EKS Pod Identity helm
Create network policy like:

apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  name: test-policy
spec:
  egress:
  - to:
    - ipBlock:
        cidr: <IP_ADDRESS>/0
  podSelector:
    matchLabels:
      component: my-pod
  policyTypes:
  - Egress

Start a pod
Try calling an http://<IP_ADDRESS>/v1/credentials endpoint

kubectl debug test-pod --image curlimages/curl  -it -- curl http://<IP_ADDRESS>/v1/credentials --connect-timeout  7 -I

Cilium Version
v1.14.13
Kernel Version
Linux my-bottlerocket-node 6.1.77 #1 SMP PREEMPT_DYNAMIC Fri Feb 23 02:26:25 UTC 2024 x86_64 Linux

Kubernetes Version
1.28
Regression
No response
Sysdump
No response
Relevant log output
Aug 14 18:05:59.638: taras-test-pod:54768 (ID:97997) <> <IP_ADDRESS>:80 (host) policy-verdict:none EGRESS DENIED (TCP Flags: SYN)
Aug 14 18:05:59.638: taras-test-pod:54768 (ID:97997) <> <IP_ADDRESS>:80 (host) Policy denied DROPPED (TCP Flags: SYN)
Aug 14 18:06:00.686: taras-test-pod:54768 (ID:97997) <> <IP_ADDRESS>:80 (host) policy-verdict:none EGRESS DENIED (TCP Flags: SYN)
Aug 14 18:06:00.686: taras-test-pod:54768 (ID:97997) <> <IP_ADDRESS>:80 (host) Policy denied DROPPED (TCP Flags: SYN)
Aug 14 18:06:02.756: taras-test-pod:54768 (ID:97997) <> <IP_ADDRESS>:80 (host) policy-verdict:none EGRESS DENIED (TCP Flags: SYN)
Aug 14 18:06:02.756: taras-test-pod:54768 (ID:97997) <> <IP_ADDRESS>:80 (host) Policy denied DROPPED (TCP Flags: SYN)

### Anything else?

_No response_

### Cilium Users Document

- [ ] Are you a user of Cilium? Please add yourself to the [Users doc](https://github.com/cilium/cilium/blob/main/USERS.md)

### Code of Conduct

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

Thanks for this issue @taraspos.
In this case, the NetworkPolicy objects you've given are working as directed - they're blocking all egress from the pods, full stop. This will include IPs on the local machine. For this to work, you'll need to flip to using allow policies, and allowlisting the traffic you want - Cilium will deny any traffic that does not match a policy in that case.
More information is available in the Network Policy reference section of the Cilium documentation at https://docs.cilium.io/en/stable/security/policy/.
Please let us know if you need to know more.

It seems like this issue might be related to the:

https://github.com/cilium/cilium/issues/20550

🤦 Yes, you're right.
However, I also agree that nodes being excluded from ipBlock would actually produce the outcome I was talking about. Is it possible for you to upgrade and see if 1.15 and see if that helps?

Yes, I can confirm this works fine with Cilium 1.15

Okay, it does seem likely that nodes being excluded from ipBlock produces the outcome you're looking for, and that changes in 1.15 remove that issue. Given that, what would you like for next steps to be?

I believe we should be OK to resolve this then. If other users face the same problem, they should be able to find this issue.

Just as an addition, we use the following CNP successfully for External Secrets Operator using Pod Identity. The traffic to the mentioned IP is recognised as host traffic by Cilium 1.16 and the two ports are from the EKS Pod Identity docs:
apiVersion: cilium.io/v2
kind: CiliumNetworkPolicy
metadata:
  name: aws
spec:
  endpointSelector: {}
  ingress:
    - {}
  egress:
    - toFQDNs:
        - matchName: sts.{{ $.Values.awsSecretsmanager.region }}.amazonaws.com
        - matchName: secretsmanager.{{ $.Values.awsSecretsmanager.region }}.amazonaws.com
        - matchName: api.ecr.{{ $.Values.awsSecretsmanager.region }}.amazonaws.com
      toPorts:
        - ports:
            - port: "443"
    - toEntities:
        - host
      toPorts:
        - ports:
            - port: "80"
            - port: "2703"


Some unrecognized flags as of May 26, 2016

Here are a few flags I ran into that WLLVM didn't recognize:
WARNING:Did not recognize the compiler flag "-pedantic"
WARNING:Did not recognize the compiler flag "-print-prog-name=ld"
WARNING:Did not recognize the compiler flag "-pie"
WARNING:Did not recognize the compiler flag "--shared"
WARNING:Did not recognize the compiler flag "debian/libcolord2/usr/lib/x86_64-linux-gnu/libcolord.so.2"
WARNING:Did not recognize the compiler flag "debian/libcolord2/usr/lib/x86_64-linux-gnu/libcolordprivate.so.2"
WARNING:Did not recognize the compiler flag "debian/libcolorhug2/usr/lib/x86_64-linux-gnu/libcolorhug.so.2"

If you need more info for the "debian" flags, just let me know.

The - style flags are not that important. The .so.N are important. I fixed the .so (but not the .so.N)
in SRI's fork. I will also fix the .so.N is SRI's fork.

We (@BrunoDutertre and I) did the port to the mac. We use it on both mac and linux most weeks.
Like last week I did gmp, yices, and libpoly using it.
I doubt that I will push up again since my last push is still sitting there getting lonely. My guess
is Tristan doesn't use the mac version so doesn't care that his version is broken.

@travitch, @ianamason fixed this issue in a fork and explained in a discussion related to his commit why the fork: https://github.com/SRI-CSL/whole-program-llvm/commit/17f2e850defb10f2a0eb3263041e618793125870#commitcomment-17641358
Would you consider cherry-picking that commit and putting it here upstream?
Even better, would you guys consider merging the repos? I'm sure everyone involved would benefit from it.