Use expressions for the constraints used in the disjunctions

https://jump.dev/JuMP.jl/stable/manual/expressions/
This is probably a better approach for the internals of this package. This way, constraints are not modified, but the expressions are reformulated and then added as constraints.

This may not be the best option since expressions don't have operators (<=, >=, ==). Thus you would need to have the expressions in canonical form (<= 0) to properly do the reformulation.
A pro of using expressions, is that for the nonlinear case, you can name them, which you can't do with nonlinear-constraints


Ore dict resolution crash with tinkers construct slime grass

1.06 version of the mod
1.12.2 minecraft
2503 forge
I was randomly swinging around with an instant dig pickaxe and got this crash:
https://pastebin.com/Ur69wvAe
I think I traced it to the tconstruct block that corresponds to the slime fern.  Not 100% sure
Maybe change it so the oreswapper method only runs on blocks and not tile entities?

I can't reproduce this crash but I'm pretty sure I know what's causing this, please try using this version to see if that fixes it https://github.com/RCXcrafter/AOBDorechunks/releases/download/1.0.6-maybefix/AOBDOC-1.12.2-1.0.6.jar

Thanks, I'll try that as soon as I get back on my home computer.

Seems to be when I veinminer slime dirt from tinkers construct, and the grasses and ferns on top break.

okay, I was able to reproduce the crash with veinminer and I fixed it. I will upload it to curse soon.

Thanks!


 For example, the Button component needs to customize the ripple to hide overflow and round corners as you want to do in your example. Checking here and here might be helpful :)

$button-border-radius: 2 * $unit;
.rippleWrapper {
border-radius: 2 * $unit;
}
Thanks for the help, I solve this problem

Great, glad to read!!


p5.Oscillator's phase() method doesn't work

https://processing.github.io/p5.js-sound/examples/outOfPhase

@allocinit Thanks for opening this issue. I went through the link provided by you. I was wondering if you could just add a little bit of more description about the issue, making it much easier to understand the problem and fix it early.


UIAlertView deprecated in iOS 9

I guess with the new XCode new depreciations... any ideas how to fixed this one?
'UIAlertView' was deprecated in iOS 9.0: UIAlertView is deprecated. Use UIAlertController with a preferredStyle of UIAlertControllerStyleAlert instead
@fethica @analogcode
again, thanks in advance!

I'm closing this issue. Reason: The project has been updated.


CIV-14829 dismiss case dashboard notification except editing tasks

JIRA link (if applicable)
CIV-14829
Change description
Changes for all ACs except the modification of tasks
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[X] No

This was closed as it was covered in https://tools.hmcts.net/jira/browse/CIV-15165


Prepare for Gradle Plugin release 2.1.0

Current dependencies on/for this PR:

main

PR #76

PR #77   👈

This comment was auto-generated by Graphite.


OLS-103 - Completed basic retriever

Description
This is the code for basic retriever as described in
https://issues.redhat.com/secure/RapidBoard.jspa?rapidView=18820&projectKey=OLS&view=detail&selectedIssue=[OLS-103](https://issues.redhat.com//browse/OLS-103)
Type of change

[ ] Refactor
[ X] New feature
[ ] Bug fix
[ ] CVE fix
[ ] Optimization
[ ] Documentation Update
[ ] Configuration Update
[ ] Bump-up dependent library

Related Tickets & Documents

Related Issue #
Closes #

Checklist before requesting a review

[X ] I have performed a self-review of my code.
[ ] PR has passed all pre-merge test jobs.
[ ] If it is a core feature, I have added thorough tests.

Testing

Please provide detailed steps to perform tests related to this code change.
unit test/integration test included
How were the fix/results from this change verified? Please provide relevant screenshots or results.

@bparees his implementation is a generic implementation of VectorStoreRetriever that will work with most vector dbs.
It will work with most common vector db

There are various tuning option that is provided within the this retriever.

The various tuning options have been covered as part tests and docs.

The search by vectors are still not implemented by langchain for this generic interface
https://github.com/langchain-ai/langchain/blob/master/libs/core/langchain_core/vectorstores.py#L386
Once we decide upon a vector db for OLS we can extend this class to implment search by vector methods

As an example this is the code for FAISS(VectorStore)

https://github.com/langchain-ai/langchain/blob/master/libs/community/langchain_community/vectorstores/faiss.py#L272

From the ADR it seems like no vector db has been chosen yet
https://docs.google.com/document/d/1ChhHpmB-EZZ0hQXVbBuWbN6Fa0XAngQTDIMPyNF0SII/edit#heading=h.66y4kqbj468a
Lastly it is sufficiently modular to allow tuning at this point.

@tisnik @bparees when I run make verify on my local it passes.

on local

black . --check
All done! ✨ 🍰 ✨
61 files would be left unchanged.
ruff . --per-file-ignores=tests/*:S101

```, but it is failing on CI. Any recommendation?

/retest

@tisnik @bparees when I run make verify on my local it passes.
* on local

black . --check
All done! ✨ 🍰 ✨
61 files would be left unchanged.
ruff . --per-file-ignores=tests/*:S101

```,
 but it is failing on CI. Any recommendation?

Do you happen to have the latest version of black? Also is everything commit into this PR?

@asamal4 Very good point. The vector store index will be specific to vector store and embeddings will depend on the model with which you create those.. Refer ADR, both langchain and llamaindex is in consideration.

@asamal4 llamaindex and langchain are two libraries that can be both used for RAG searches and both are in consideration. if you look into some docs Langchain is preferred over llamaindex for chats(conversation). I am not trying to debate langchain over llamaindex here as they are both in consideration as per ADR. The existing code has to be looked as a POC and several elements of it is addressed in JIRA issue. One such example is that of QuestionAnswer Validator. This is anyhow a basic retriever not to obtain necessarily a best response but to be tunable as per JIRA description

@bparees all the comments have been addressed. So you can merge it at your convenience. In case you still see any issues let me know.

i'll give it an approval as it establishes the right structure, i'll let @asamal4 and @onmete finalize their reviews though, before we merge it
/approve


Add tests for keyless auth to Azure Search vector store

Add test validating DefaultAzureCredential can be used with the Azure Search vector store
Fix filter tests on Windows due to differences in checked-in newlines vs. platform-specific newline.
Adds dependencies on azure-core, azure-identity, and azure-json packages

much appreciated!  See comment above.

thanks, i'll check it

thanks, i'll check it

LGTM


import autocomplete list tuneup

Most people use the syntax of
import rhinoscriptsyntax

and there is no need to confuse them with the "rhinoscript" package which is essentially the same thing but in a "package" form.  Remove this from the autocomplete in the UI.
There are also a lot of other modules/packages not showing up in the autocomplete list.  These should get added if they make sense.

not an issue anymore


Apache dashboard

JSON looks good. I've added two small comments.
Also when you take the screenshot of the dashboards, could you change the time range so it shows data on the whole graph?
But besides that, everything looks great. Thanks 👍

The shortest it appears that I can go is 30 minutes, but yeah it's no problem.

Looks good 👍


Bug#950_Jumping_profile_page

Changes in this Pull Request:

add script for scroll page to top
use in Profile page already created elements

Mandatory checks:

[ ] Branch is up to date (latest changes were fetched from the upstream branch before creating this PR)
[x] Changes were tested manually
[ ] Java code changes are unit tested
[ ] Webtests are successful

To be checked by the reviewer:

[ ] Clean Java code and unit tested changes
[ ] UI customizablity is preserved: No hard-coded styling and URL references in JSF views

To be checked by the pull request owner:

[ ] .MASTER/job/BES_MASTER_IT/
[ ] .MASTER/job/OSCM_WS_Tests_INTERNAL/
[ ] .MASTER/job/OSCM_WS_Tests_OIDC/
[ ] .MASTER/job/OSCM_Integration_Tests_INTERNAL/
[ ] .MASTER/job/OSCM_Integration_Tests_OIDC/

Cross repository and core changes:

[ ] Interdependent changes have been communicated to the team (if applicable)
[ ] This pull request includes high risk modifications or core changes (e.g API, datamodel, authentication...). Mandatory reviewers: @goebell or @kowalczyka.

OSCM Build References:

ci11

Screenshot (if applicable):

This change is

oscm-portal/WebContent/marketplace/playground/account/profile.xhtml, line 109 at r1 (raw file):
Previously, GoebelL (Lorenz Goebel) wrote…
I'd like to have some vertical alignment of the input fields on this page. The locale combo is a bit short.

Done.


PR: Set parent for Variable Explorer windows so Spyder closes properly, and improve tests

Fix #5696 .
Currently, any window launched from the Variable Explorer (Dataframe Editor, Collections Editor, etc) will cause Spyder to stay open even if the main window is closed, leading to extra resources and cluter, user confusion and general sub-optimal Ux. Therefore, this PR sets that properly to fix it, and additionally adds a specific test for this as well as improves the existing ones to make them less brittle (as this change broke one of them, my own). Also, updated file/section headers to the consistent standard and did a few bits of minor cleanup around lines that were changed.

@CAM-Gerlach, now this one needs a rebase :-)

@ccordoba12 Done. FYI, test_elapsed_time failed several times on the Python 3.6 builds of both AppVeyor and Travis; the AppVeyor build eventually passed while the Travis one failed all three times and I had to restart it, whence it eventually succeeded. Should I submit a PR to play with the timeouts, etc or if necessary just skip it on Py3.6, or do you have a better fix in mind?

I think increasing the timeouts should be enough. Thanks!

I think increasing the timeouts should be enough. Thanks!

@ccordoba12 Done, as a separate PR of course ( #6714 ). Did so on the two tests that were causing issues, along with related tweaks to a few other tests known to be flaky on Linux locally per you and jitseniesen .
Is there anything you need me to change/do on this one, or is it ready to merge?


Add https support

Communications via https would be beneficial.
Jetty and Karaf are fully capable of supporting HTTPs; sorting out SSL certificates without requiring anything of the casual user could require some careful scripting.

In the branch issues/83, https is enabled for the jetty server.
A key will have to be generated. I used this command:
keytool -genkey -keyalg RSA -alias selfsigned -keystore keystore.jks -storepass 123456 -validity 360 -keysize 2048

The following line will have to be pointed to the generated key, and CyREST will have to be built locally for it to work: https://github.com/cytoscape/cyREST/blob/d026681e3da5f29edeefcdc49fd67b0fb1469781/src/main/java/org/cytoscape/rest/internal/task/OSGiJAXRSManager.java#L174
From there, the gentlest, non-root version of getting the https to work without warnings on Chrome was to access this url: chrome://flags/#allow-insecure-localhost
Mind you, this is ONLY for local browser access; how it interacts with other https services is yet to be seen.

This appears to be a good resource to do things programmatically:
https://www.humankode.com/asp-net-core/develop-locally-with-https-self-signed-certificates-and-asp-net-core

Regarding the last comment, at least the linux method works. The downside is that certutil is part of a package that requires sudo to install.
There was a suggestion that some of this can be solved by having a sudo/admin query in install4j. Still not a total solution.
Maybe if there's a way to get a CA to recognize localhost keys?

WebKit (Safari) has re-opened the bug, but it isn't resolved: https://bugs.webkit.org/show_bug.cgi?id=171934


Rename ethermintd.service.template to cronosd.service.template

To align with the docs
https://cronos.crypto.org/docs/getting-started/cronos-mainnet.html#step-3-run-everything

/staging


what's the cb argument to patch() ?

The patch() function accepts a fourth argument, cb, which appears to be unused and gets immediately overwritten in a while-loop inside the function.
This argument also doesn't figure in documentation or in the Typescript declaration file.
What's it for?

@mindplay-dk It's not in the declarations file because it's for private use. It's just a local variable.
https://github.com/picodom/picodom/blob/ca5aa34026d5ef366b0a411e550cb976c4589370/src/patch.js#L13-L16
We could var cb right above the while loop just as well.


Allow for renaming param nuisances

Can change the name of "param" type nuisances (changes name inside workspace) using
nuisance edit rename oldname newname
Also checks for correct syntax with using new option

Issue resolved


group_vars/all.yml doesn't appear to have been called

I'm following along with the readme but my all.yml doesn't seem to be called:
 grep kube_cert_group inventory/group_vars/all.yml
kube_cert_group: kube-cert

ansible-playbook -i muskateers.cfg cluster.yml -u root
PLAY ***************************************************************************

TASK [setup] *******************************************************************
ok: [aramis]
ok: [athos]
ok: [dartagnan]
ok: [porthos]

TASK [adduser : User | Create User Group] **************************************
fatal: [athos]: FAILED! => {"failed": true, "msg": "ERROR! ERROR! ERROR! 'kube_cert_group' is undefined"}
fatal: [porthos]: FAILED! => {"failed": true, "msg": "ERROR! ERROR! ERROR! 'kube_cert_group' is undefined"}
fatal: [aramis]: FAILED! => {"failed": true, "msg": "ERROR! ERROR! ERROR! 'kube_cert_group' is undefined"}
fatal: [dartagnan]: FAILED! => {"failed": true, "msg": "ERROR! ERROR! ERROR! 'kube_cert_group' is undefined"}

Hi @joshuacox could you please paste your inventory ?
What is your Ansible version ?

Well it was ansible 2.1.0, I just pulled in 2.2.0 though.  Is there something fresh in 2.2.0 that auto finds that all.yml?
I 'fixed' with the PR just referenced, this may or may not be the correct way to go about that.  I'd be happy to continue debugging for you.
inventory here (all muskateer aliases are defined elsewhere, and otherwise work fine):
[kube-master]
athos
porthos
aramis

[etcd]
athos
porthos
aramis

[kube-node]
athos
porthos
aramis
dartagnan

[paris]
athos
porthos local_as=xxxxxxxx
aramis local_as=xxxxxxxx

[new-york]
dartagnan local_as=xxxxxxxx

[k8s-cluster:children]
kube-node
kube-master

Thanks for the PR but i'm pretty sure that's not the cause of your issue.
Where is located your muskateers.cfg when you run the ansible-playbook command.
Btw, do you really need two sites and the bgp peeriing ?
In not you should remove the following sections from your inventory:
[paris]
athos
porthos local_as=xxxxxxxx
aramis local_as=xxxxxxxx

[new-york]
dartagnan local_as=xxxxxxxx

Another test is to test the connectivity with your remote servers
ansible -m ping -i inventory/muskateers.cfg all

Following one of the examples I placed it in a dev directory inside inventory, but that should work?  ping works  great (I'll past at bottom), now I'm getting some strange errors:
TASK [setup] *******************************************************************
<<IP_ADDRESS>> ESTABLISH SSH CONNECTION FOR USER: root
<<IP_ADDRESS>> ESTABLISH SSH CONNECTION FOR USER: root
<<IP_ADDRESS>> ESTABLISH SSH CONNECTION FOR USER: root
<<IP_ADDRESS>> ESTABLISH SSH CONNECTION FOR USER: root
<<IP_ADDRESS>> SSH: EXEC ssh -C -vvv -o ControlMaster=auto -o ControlPersist=60s -o StrictHostKeyChecking=no -o Port=16222 -o 'IdentityFile="/home/thoth/.ssh/id_ecdsa"' -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o User=root -o ConnectTimeout=10 -o ControlPath=/home/thoth/.ansible/cp/ansible-ssh-%h-%p-%r <IP_ADDRESS> '/bin/sh -c '"'"'LANG=en_US.UTF-8 LC_ALL=en_US.UTF-8 LC_MESSAGES=en_US.UTF-8 /usr/bin/python && sleep 0'"'"''
<<IP_ADDRESS>> SSH: EXEC ssh -C -vvv -o ControlMaster=auto -o ControlPersist=60s -o StrictHostKeyChecking=no -o Port=16222 -o 'IdentityFile="/home/thoth/.ssh/id_ecdsa"' -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o User=root -o ConnectTimeout=10 -o ControlPath=/home/thoth/.ansible/cp/ansible-ssh-%h-%p-%r <IP_ADDRESS> '/bin/sh -c '"'"'LANG=en_US.UTF-8 LC_ALL=en_US.UTF-8 LC_MESSAGES=en_US.UTF-8 /usr/bin/python && sleep 0'"'"''
<<IP_ADDRESS>> SSH: EXEC ssh -C -vvv -o ControlMaster=auto -o ControlPersist=60s -o StrictHostKeyChecking=no -o Port=16222 -o 'IdentityFile="/home/thoth/.ssh/id_ecdsa"' -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o User=root -o ConnectTimeout=10 -o ControlPath=/home/thoth/.ansible/cp/ansible-ssh-%h-%p-%r <IP_ADDRESS> '/bin/sh -c '"'"'LANG=en_US.UTF-8 LC_ALL=en_US.UTF-8 LC_MESSAGES=en_US.UTF-8 /usr/bin/python && sleep 0'"'"''
<<IP_ADDRESS>> SSH: EXEC ssh -C -vvv -o ControlMaster=auto -o ControlPersist=60s -o StrictHostKeyChecking=no -o Port=16222 -o 'IdentityFile="/home/thoth/.ssh/id_ecdsa"' -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o User=root -o ConnectTimeout=10 -o ControlPath=/home/thoth/.ansible/cp/ansible-ssh-%h-%p-%r <IP_ADDRESS> '/bin/sh -c '"'"'LANG=en_US.UTF-8 LC_ALL=en_US.UTF-8 LC_MESSAGES=en_US.UTF-8 /usr/bin/python && sleep 0'"'"''
fatal: [porthos]: FAILED! => {"changed": false, "failed": true, "invocation": {"module_args": {"gather_subset": "all"}, "module_name": "setup"}, "msg": "unsupported parameter for module: gather_subset"}
fatal: [dartagnan]: FAILED! => {"changed": false, "failed": true, "invocation": {"module_args": {"gather_subset": "all"}, "module_name": "setup"}, "msg": "unsupported parameter for module: gather_subset"}
fatal: [athos]: FAILED! => {"changed": false, "failed": true, "invocation": {"module_args": {"gather_subset": "all"}, "module_name": "setup"}, "msg": "unsupported parameter for module: gather_subset"}
fatal: [aramis]: FAILED! => {"changed": false, "failed": true, "invocation": {"module_args": {"gather_subset": "all"}, "module_name": "setup"}, "msg": "unsupported parameter for module: gather_subset"}

I reverted back to ansible 2.1 rc4 and same, I'll provision some fresh hosts to try on as these may be silly after deving on them all night.
ansible -m ping -i inventory/dev/muskateers.cfg all                                                                                ⏎ [22h6m] ✭
porthos | SUCCESS => {
    "changed": false,
    "ping": "pong"
}
athos | SUCCESS => {
    "changed": false,
    "ping": "pong"
}
dartagnan | SUCCESS => {
    "changed": false,
    "ping": "pong"
}
aramis | SUCCESS => {
    "changed": false,
    "ping": "pong"
}

ok on four fresh ubuntu trusty hosts:
ansible-playbook -i inventory/dev/vipers.cfg cluster.yml -u root

PLAY [k8s-cluster] *************************************************************

TASK [setup] *******************************************************************
fatal: [cobra]: FAILED! => {"changed": false, "failed": true, "msg": "unsupported parameter for module: gather_subset"}
fatal: [rattlesnake]: FAILED! => {"changed": false, "failed": true, "msg": "unsupported parameter for module: gather_subset"}
fatal: [asp]: FAILED! => {"changed": false, "failed": true, "msg": "unsupported parameter for module: gather_subset"}
fatal: [blackmamba]: FAILED! => {"changed": false, "failed": true, "msg": "unsupported parameter for module: gather_subset"}

NO MORE HOSTS LEFT *************************************************************
        to retry, use: --limit @cluster.retry

PLAY RECAP *********************************************************************
asp                        : ok=0    changed=0    unreachable=0    failed=1
blackmamba                 : ok=0    changed=0    unreachable=0    failed=1
cobra                      : ok=0    changed=0    unreachable=0    failed=1
rattlesnake                : ok=0    changed=0    unreachable=0    failed=1

new inventory:
[kube-master]
rattlesnake
blackmamba
cobra

[etcd]
rattlesnake
blackmamba
cobra

[kube-node]
rattlesnake
blackmamba
cobra
asp

[k8s-cluster:children]
kube-node
kube-master

ping is great:
ansible -m ping -i inventory/dev/vipers.cfg all                                                                                [23h4m] ✭
cobra | SUCCESS => {
    "changed": false,
    "ping": "pong"
}
rattlesnake | SUCCESS => {
    "changed": false,
    "ping": "pong"
}
asp | SUCCESS => {
    "changed": false,
    "ping": "pong"
}
blackmamba | SUCCESS => {
    "changed": false,
    "ping": "pong"
}

I'm not using my PR checked out commit ab05
commit ab0581e114983810d18c732d13407b311ac54d73
Merge: cb92b30 6880853
Author: Smaine Kahlouch<EMAIL_ADDRESS>Date:   Tue May 31 20:16:01 2016 +0200

    Merge pull request #276 from mattymo/patch-1

    Fix order in restart kubelet to fix systemd reload

And ansible is 2.1 rc4
ansible --version
ansible <IP_ADDRESS> (detached HEAD 9e622dcf31) last updated 2016/06/01 11:10:20 (GMT -500)
  lib/ansible/modules/core: (detached HEAD 002028748f) last updated 2016/01/04 08:45:02 (GMT -500)
  lib/ansible/modules/extras: (detached HEAD f6a7b6dd1f) last updated 2016/01/04 08:45:10 (GMT -500)
  config file = /mnt/xyliss/git/kargo/ansible.cfg
  configured module search path = Default w/o overrides

rolling ansible back to 2.0.2 git checkout v<IP_ADDRESS>-1:
 ansible --version
ansible <IP_ADDRESS> (detached HEAD 24d9e5e0b4) last updated 2016/06/01 13:10:26 (GMT -500)
  lib/ansible/modules/core: (detached HEAD 002028748f) last updated 2016/01/04 08:45:02 (GMT -500)
  lib/ansible/modules/extras: (detached HEAD f6a7b6dd1f) last updated 2016/01/04 08:45:10 (GMT -500)
  config file =
  configured module search path = Default w/o overrides

produces the old error, leading me to believe I was 2.0.1 and 2.1 like I assumed earlier previous to my checkout of 2.2.0.  What ansible version is kargo to be used with?
5494 ± : ansible-playbook -i inventory/dev/vipers.cfg cluster.yml -u root                                                                           [23h54m] ✭

PLAY [k8s-cluster] *************************************************************

TASK [setup] *******************************************************************
ok: [cobra]
ok: [rattlesnake]
ok: [asp]
ok: [blackmamba]

TASK [adduser : User | Create User Group] **************************************
fatal: [blackmamba]: FAILED! => {"failed": true, "msg": "'kube_cert_group' is undefined"}
fatal: [cobra]: FAILED! => {"failed": true, "msg": "'kube_cert_group' is undefined"}
fatal: [asp]: FAILED! => {"failed": true, "msg": "'kube_cert_group' is undefined"}
fatal: [rattlesnake]: FAILED! => {"failed": true, "msg": "'kube_cert_group' is undefined"}

NO MORE HOSTS LEFT *************************************************************
        to retry, use: --limit @cluster.retry

PLAY RECAP *********************************************************************
asp                        : ok=1    changed=0    unreachable=0    failed=1
blackmamba                 : ok=1    changed=0    unreachable=0    failed=1
cobra                      : ok=1    changed=0    unreachable=0    failed=1
rattlesnake                : ok=1    changed=0    unreachable=0    failed=1

stealth 福 ~/git/kargo ➤ ab0581e|ab0581e⚡
5498 ± : ansible --version                                                                                ⏎ [23h54m] ✭
ansible <IP_ADDRESS> (detached HEAD 24d9e5e0b4) last updated 2016/06/01 13:10:26 (GMT -500)
  lib/ansible/modules/core: (detached HEAD 002028748f) last updated 2016/01/04 08:45:02 (GMT -500)
  lib/ansible/modules/extras: (detached HEAD f6a7b6dd1f) last updated 2016/01/04 08:45:10 (GMT -500)
  config file = /mnt/xyliss/git/kargo/ansible.cfg
  configured module search path = Default w/o overrides

Well strange we've never had this issue.
The ansible versions supported for sure are 2.2.0 and 2.1 and above.
We'll try to find out what's going on from your side but in the mean time did you consider using kargo-cli ?
sudo pip2 install kargo
kargo prepare --nodes cobra[ansible_ssh_host=x.x.x.x] asp[ansible_ssh_host=x.x.x.x] ...
kargo deploy [--gce|--aws]

What's the output of tree -L 3 -Ap inventory ?

here is the tree:
tree -L 3 -Ap inventory                                                                                [23h55m] ✭
inventory
├── [drwxr-xr-x]  dev
│   ├── [-rw-r--r--]  muskateers.cfg
│   ├── [-rw-r--r--]  muskateers-cities.cfg
│   ├── [-rw-r--r--]  vipers.cfg
│   └── [-rw-r--r--]  vipersf.cfg
├── [drwxr-xr-x]  group_vars
│   ├── [-rw-r--r--]  all.yml
│   ├── [-rw-r--r--]  new-york.yml
│   └── [-rw-r--r--]  paris.yml
├── [-rw-r--r--]  inventory.example
└── [-rw-r--r--]  local-tests.cfg

Same errors with kargo:
kargo prepare --nodes rattlesnake[ansible_host=<IP_ADDRESS>,ansible_ssh_private_key_file=~/.ssh/id_ecdsa,ansible_port=16222,ansible_ssh_user=root] blackmamba[ansible_host=<IP_ADDRESS>,ansible_ssh_private_key_file=~/.ssh/id_ecdsa,ansible_port=16222,ansible_ssh_user=root] asp[ansible_host=<IP_ADDRESS>,ansible_ssh_private_key_file=~/.ssh/id_ecdsa,ansible_port=16222,ansible_ssh_user=root] cobra[ansible_host=<IP_ADDRESS>,ansible_ssh_private_key_file=~/.ssh/id_ecdsa,ansible_port=16222,ansible_ssh_user=root]
kargo deploy
Identity added: /home/thoth/.ssh/id_ecdsa (/home/thoth/.ssh/id_ecdsa)

CHECKING SSH CONNECTIONS *******************************************************
cobra | SUCCESS => {
    "changed": false,
    "ping": "pong"
}
rattlesnake | SUCCESS => {
    "changed": false,
    "ping": "pong"
}
blackmamba | SUCCESS => {
    "changed": false,
    "ping": "pong"
}
asp | SUCCESS => {
    "changed": false,
    "ping": "pong"
}
All hosts are reachable
/mnt/xyliss/git/ansible/bin/ansible-playbook --ssh-extra-args -o StrictHostKeyChecking=no -e kube_network_plugin=flannel -u thoth -b --become-user=root -i /home/thoth/kargo/inventory/inventory.cfg /home/thoth/kargo/cluster.yml
Run kubernetes cluster deployment with the above command ? [Y/n] Y

RUN PLAYBOOK *******************************************************************

PLAY [k8s-cluster] *************************************************************

TASK [setup] *******************************************************************
fatal: [rattlesnake]: FAILED! => {"changed": false, "failed": true, "msg": "unsupported parameter for module: gather_subset"}
fatal: [blackmamba]: FAILED! => {"changed": false, "failed": true, "msg": "unsupported parameter for module: gather_subset"}
fatal: [cobra]: FAILED! => {"changed": false, "failed": true, "msg": "unsupported parameter for module: gather_subset"}
fatal: [asp]: FAILED! => {"changed": false, "failed": true, "msg": "unsupported parameter for module: gather_subset"}

NO MORE HOSTS LEFT *************************************************************
        to retry, use: --limit @/home/thoth/kargo/cluster.retry

PLAY RECAP *********************************************************************
asp                        : ok=0    changed=0    unreachable=0    failed=1
blackmamba                 : ok=0    changed=0    unreachable=0    failed=1
cobra                      : ok=0    changed=0    unreachable=0    failed=1
rattlesnake                : ok=0    changed=0    unreachable=0    failed=1

debug version: http://sprunge.us/GMEW
captured using:
ansible-playbook -vvvvv -e kube_network_plugin=flannel -u thoth -b --become-user=root -i /home/thoth/kargo/inventory/inventory.cfg /home/thoth/kargo/cluster.yml|sprunge

perhaps more interesting is the fact that my pipe did not include the errors:
Using /home/thoth/kargo/ansible.cfg as config file
ERROR! the playbook: StrictHostKeyChecking=no could not be found
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  8471  100    23  100  8448      3   1344  0:00:07  0:00:06  0:00:01  1344

especially the
ERROR! the playbook: StrictHostKeyChecking=no could not be found

i had to eliminate that when I copied from kargo's output to make that line work, or to be clear this line failed:
ansible-playbook -vvvvvvvv --ssh-extra-args -o StrictHostKeyChecking=no -e kube_network_plugin=flannel -u thoth -b --become-user=root -i /home/thoth/kargo/inventory/inventory.cfg /home/thoth/kargo/cluster.yml
Using /home/thoth/kargo/ansible.cfg as config file
ERROR! the playbook: StrictHostKeyChecking=no could not be found

is perhaps my ssh the issue?
ssh -V
OpenSSH_7.2p2 Debian-5, OpenSSL 1.0.2h  3 May 2016

which got me to try:
ANSIBLE_SCP_IF_SSH=y

before my ansible-playbook command.  just becaue I ran into that recently elsewhere. But still the same error about gather_subset

just to test if it was because I was using debian stretch I tested from dartagnan (a ubuntu trusty host)
after cloning the ansible repo and checkout out the 2.1 stable branch, I get the missing kube_cert_group again, which can be fixed with my PR, but I digress and would rather this work as intended:
http://sprunge.us/FVjX

So I spun up a group of 4 centos machines this morning one to act as ansible controller, and it appears to have gotten past the addusers step just fine.  So is this an issue with ubuntu trusty hosts?

Sorry we dropped the ci tests for trusty.
do you want to keep this issue openned ?

well I added the viper hosts to inventory and it works fine.
[kube-master]
doberman
dachsund
rattlesnake

[all]
doberman        ansible_host=<IP_ADDRESS> ansible_ssh_private_key_file=~/.ssh/id_ecdsa ansible_ssh_user=root
dachsund        ansible_host=<IP_ADDRESS> ansible_ssh_private_key_file=~/.ssh/id_ecdsa ansible_ssh_user=root
spaniel         ansible_host=<IP_ADDRESS> ansible_ssh_private_key_file=~/.ssh/id_ecdsa ansible_ssh_user=root
rattlesnake     ansible_host=<IP_ADDRESS> ansible_ssh_private_key_file=~/.ssh/id_ecdsa ansible_port=16222 ansible_ssh_user=root
blackmamba      ansible_host=<IP_ADDRESS> ansible_ssh_private_key_file=~/.ssh/id_ecdsa ansible_port=16222 ansible_ssh_user=root
asp             ansible_host=<IP_ADDRESS> ansible_ssh_private_key_file=~/.ssh/id_ecdsa ansible_port=16222 ansible_ssh_user=root
cobra           ansible_host=<IP_ADDRESS> ansible_ssh_private_key_file=~/.ssh/id_ecdsa ansible_port=16222 ansible_ssh_user=root

[k8s-cluster:children]
kube-node
kube-master

[kube-node]
doberman
dachsund
spaniel
rattlesnake
blackmamba
asp
cobra

[etcd]
doberman
dachsund
spaniel
blackmamba
rattlesnake

there is something else at play here, as I'm on debian stretch (which fails with the above errors when trying spin up trusty or centos7 hosts)
trusty also fails with the same errors
yet trusty is working as a host IF controlled by centos.
as for keeping the issue open I would definitely like to be able to use debian as I prefer to not use redhat based distros (alway seem broken by design to drive you nuts so you'll be forced to hire a RHCE),  I'm not even certain what is causing the failure

module mismatch was the issue:
git submodule update --init --recursive  in the ansible after checking out 2.1 stable cleaned up all issues here


fix: allow empty test bodies

In jest/jasmine, if you don't provide a test body for an it statement, it should just mark the test as skipped. This is a very simple way to write out a bunch of scenarios and then incrementally add the test cases for each.
Example:
it('should return a string');

When you try and run a test suite using the above syntax you get the following error:
TypeError: Cannot read property 'length' of undefined
      at wrapTestInZone (node_modules/jest-zone-patch/index.js:46:18)

This PR should fix this problem.

Thank you for taking care of this, super appreciated!
In this case testBody should be undefined, right? Can you make the check more explicit?

Check adjusted to only look for undefined values as requested

Thanks! Would love a patch release on npm when you get a chance.

Just published 15 minutes ago or so ;)


update python device sdk to the latest version

Updating to the latest Python device SDK.

Do we need to test any tools that have dependency on this python device sdk version?

@cindydeng1998 samples in the IoT SDK for Python include implementations that utilize aspects added since 2.3.0. They replace features that are deprecated in the same version. Templates should align to this change.


Looking forward to get involved and contribute to the community 🎉

First Name
Bhavesh
Last Name
Goyal
Discord Username (if applicable)
Bhavesh Goyal#5292
Let us understand your motive.
I am following up Siddharth since HackOn.
I want to serve the community in any way possible to the best of my ability.

Hey @bhaveshgoyal182 👋🏻
Thanks for requesting an invite! Welcome to SidHacks Community 🎉
Before going ahead, I would want you to complete the below To-Do list.
Your To-Do List ✔

Accept the invitation sent to you via mail.
Change the appearance of this organization to "Public" from the people list here.
Join our Discord Server here.

Accept the Rules from #📓〡rules channel.
Introduce yourself to our community in 👋〡introduction channel.

Feel free to share your excitement on socials with #SidHacksCommunity. You can also tag me @siddharth_hacks.

Close this issue once you complete all the above points.

Looking forward to interacting with you in our community! Welcome once again! 🤓

Thanks Sid!


WIP POC - Framework builds on el8

I am closing this one in favor of https://github.com/oamg/leapp/pull/717 - I have rebased it recently and it already handles more problems we discovered in the past.


Would Urho.Net follow the new community U3D or Urho3D

With the current split of Urho3D and U3D.  Which path would you continue to support?
Urho.Net is a wonderful code-first type of engine and as a hobby game programmer, I love working with it. Please continue to keep this alive and give me hope for near future :-)
BTW, I did the sample games of
Urho.Net-2D-Map-of-Doom
Urho.Net_CardGame_Example

Urho3D is shutting down its Discourse forum by the end of this week.
I don't see a bright future for it.
The future of U3D remains to be seen.
I will continue to support Urho.Net regardless of the future states of Urho3D and U3D.
Currently, I am very busy with my own projects.
Once my workload decreases, I plan to release new versions this year and possibly NuGET packages.
Keep having fun and making cool projects with it.


Ducky's Wallpapers update

Ducky's Wallpapers
https://github.com/Casquall/Steam-Deck-Themes
Checklist
Failure to complete this checklist or deleting boxes from the checklist will result in the closing of your pull request. Please write any comments regarding this checklist at the bottom of your pull request.
Check every box.

[X] I am the original author of this theme or have permission from the original author to make this pull request.
[X] All copyright of this theme's contents belong to the listed author or is cited in the repository linked above.
[X] This theme's target has been marked appropriately and only styles said target.
[X] This theme works properly on the latest versions of SteamOS for Steam Deck, decky-loader and SDH-CssLoader.
[X] This theme only uses * or !important if absolutely necessary.
[X] This theme is under 10MB in size and uses the least disk space possible.
[X] This theme's preview image does not include text unless it is necessary to describe changes that can be made.
[X] This theme is safe for work and does not contain any sexual, drug-related, or profane content.

Check one box.

[ ] I am not bundling a part of another theme with this theme to encourage mixing and matching themes.
[X] Themes included with this theme are toggleable using a patch.

Check one box.

[ ] This is a keyboard theme applied to the default keyboard.
[ ] This is a system-wide theme applied to the default keyboard. The keyboard is toggleable using a patch.
[X] This theme does not target the keyboard.

Please rebase your repository


v4.50.3 Update Fails

Describe The Bug
Clicking the update button on the web for 4.50.3 and it is failing.
Logs
CMD: npm install -g<EMAIL_ADDRESS>
npm ERR! process terminated
npm ERR! signal SIGTERM

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/homebridge/.npm/_logs/2023-05-12T13_35_33_771Z-debug-0.log

Cleaning up npm cache, please wait...
npm cache cleared, please try updating homebridge-config-ui-x again.

Operation failed. Please review log for details.

2110 verbose stack Error: process terminated
2110 verbose stack     at /opt/homebridge/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/reify.js:200:39
2110 verbose stack     at process.<anonymous> (/opt/homebridge/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/signal-handling.js:53:5)
2110 verbose stack     at process.emit (node:events:525:35)

Config
No response
Homebridge UI Version
4.50.2
Homebridge Version
1.6.1
Node.js Version
16.14.0
Operating System
Raspberry Pi OS / Raspbian
Environment Info

[ ] Using Docker?
[ ] Using Hyper-V?
[ ] Using hb-service?

Raspberry Pi Model
Raspberry Pi Zero W

Yes , i click update and can not access homebridge over local web .

Yes , i click update and can not access homebridge over local web .

My homebridge install is still functional. The update just fails to complete.

This homebridge-config-ui-x update also took down my Homebridge instance. Currently trying to uninstall/reinstall the homebridge-config-ui-x, but has not worked so far.

This homebridge-config-ui-x update also took down my Homebridge instance. Currently trying to uninstall/reinstall the homebridge-config-ui-x, but has not worked so far.

Yes , i need uninstall and reinstall from fresh

Yes , i need uninstall and reinstall from fresh

@hlong0712 what uninstall & install command(s) (in which OS) did you use? Was it just for homebridge-config-ui-x?

@petebocken the working theory for why the install failed for you was that your RPI may have been low of memory needed to run the install process.  How much free ram does the dashboard show before you attempt the upgrade.

@petebocken the working theory for why the install failed for you was that your RPI may have been low of memory needed to run the install process. How much free ram does the dashboard show before you attempt the upgrade.

0.42 GB Total
0.23 GB Available
I did already try restarting the Pi and performing the update again.

@petebocken just to confirm that the issue is environmental and not the release packaging could you install the previous version?
You can select alternate versions to install with the wrench icon on the homebridge-config-ui-x plugin widget

@NorthernMan54 so you are the new main contributor for this project? Do you also plan to update the docker version?

@Staubgeborener All the homebridge collaborators are now contributing to the ongoing maintenance and support of this package and several other core packages, including the docker image.
I just happen to have the been person to hit the release button at this time, so I’m also taking the lead on post release support.
Once this release has settled into the community the plan is to also update all the packages like the docker include that include this.  As I wanted to reduce the release risk, I’m staggering the packages.

@petebocken just to confirm that the issue is environmental and not the release packaging could you install the previous version?

Downgraded from 4.50.2 to 4.50.1 just fine.
Upgraded from 4.50.1 to 4.50.2 just fine.
Upgrade from 4.50.2 to 4.50.3 fails with same error.

@petebocken Tks let me take a deeper dive into this.

If you use the homebridge terminal to try to update to the new version of the ui
npm install -g<EMAIL_ADDRESS>
does this complete or result in the same error: ?
npm ERR! process terminated
npm ERR! signal SIGTERM

If you use the homebridge terminal to try to update to the new version of the ui
npm install -g<EMAIL_ADDRESS>
does this complete or result in the same error: ?

Here's what I got. I see it needs a newer version of node. I tried updating it, but not sure I'm doing it correctly. Can't get it to update. I got npm updated to 9.6.6.
$ sudo npm install -g<EMAIL_ADDRESS>npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package<EMAIL_ADDRESS>npm WARN EBADENGINE   required: { node: '>=16.20.0', homebridge: '>=1.6.0' },
npm WARN EBADENGINE   current: { node: 'v16.14.0', npm: '8.6.0' }
npm WARN EBADENGINE }
npm notice
npm notice New major version of npm available! 8.6.0 -> 9.6.6
npm notice Changelog: https://github.com/npm/cli/releases/tag/v9.6.6
npm notice Run npm install -g<EMAIL_ADDRESS>to update!
npm notice
npm ERR! code ENOTEMPTY
npm ERR! syscall rename
npm ERR! path /usr/local/lib/node_modules/homebridge-config-ui-x
npm ERR! dest /usr/local/lib/node_modules/.homebridge-config-ui-x-3gtnOIj4
npm ERR! errno -39
npm ERR! ENOTEMPTY: directory not empty, rename '/usr/local/lib/node_modules/homebridge-config-ui-x' -> '/usr/local/lib/node_modules/.homebridge-config-ui-x-3gtnOIj4'

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2023-05-12T21_54_47_961Z-debug-0.log

In this case I would try this:
rm -rf /usr/local/lib/node_modules/homebridge-config-ui-x

(if you get permission issues then maybe try with sudo at the beginning)
and then (without restarting homebridge in between) install the plugin
npm install -g homebridge-config-ui-x

Your version of node (although you are getting warnings) I don't think is important for the install of the ui plugin.
Once you have config-ui-x running again on the latest version, you could consider using the hb-service tool to update your node to the latest 18.x version

I've tried deleting the directory and reinstalling (as mentioned previously), but I am still unable to get the UI to load.

sorry i didn’t see you mentioned earlier about deleting the directory

i feel like maybe different users may have slightly different things going on and/or issues why the ui isn’t updating properly

@bwp91 deleting the dir and reinstalling appears to have completed fine?  However, the web still shows I'm on 4.50.2.
$ sudo rm -rf /usr/local/lib/node_modules/homebridge-config-ui-x
pi@web:/usr/local/lib/node_modules $ sudo npm install -g homebridge-config-ui-x
/usr/local/bin/homebridge-config-ui-x -> /usr/local/lib/node_modules/homebridge-config-ui-x/dist/bin/standalone.js
/usr/local/bin/hb-service -> /usr/local/lib/node_modules/homebridge-config-ui-x/dist/bin/hb-service.js

><EMAIL_ADDRESS>install /usr/local/lib/node_modules/homebridge-config-ui-x/node_modules/node-pty-prebuilt-multiarch
> node scripts/check-prebuild.js || prebuild-install || node scripts/install.js

Prebuild binary exists: /usr/local/lib/node_modules/homebridge-config-ui-x/node_modules/node-pty-prebuilt-multiarch/prebuilds/linux-arm/node.abi67.node

><EMAIL_ADDRESS>postinstall /usr/local/lib/node_modules/homebridge-config-ui-x/node_modules/core-js-pure
> node -e "try{require('./postinstall')}catch(e){}"

><EMAIL_ADDRESS>postinstall /usr/local/lib/node_modules/homebridge-config-ui-x/node_modules/@nestjs/core
> opencollective || exit 0

><EMAIL_ADDRESS>postinstall /usr/local/lib/node_modules/homebridge-config-ui-x/node_modules/node-pty-prebuilt-multiarch
> node scripts/post-install.js

npm WARN<EMAIL_ADDRESS>requires a peer of cache-manager@* but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.

+<EMAIL_ADDRESS>added 346 packages from 398 contributors in 377.732s

@petebocken Could you try one more thing for us, we packaged the release again and published it as version 4.50.4.   We found the issue with the packaging of 4.50.3, and believe this will resolve the issue.
PS You may want to remove this version - sudo rm -rf /usr/local/lib/node_modules/homebridge-config-ui-x

For people watching this, low powered/low resource devices, like a api w or a rpi 2 use an alternate method of plugin installation that requires the GitHub release package to include a artifact bundle that includes the distributed package, and that step was missed with 4.50.3.

Updating to 4.50.4 worked. 👍 thanks!

Just wanted to follow-up in case this is still an issue for anyone else. I tried deleting and downgrading the UI version -- did not work. I then tried deleting and installing the just released 4.50.4 version, still did not work. I finally thought to reinstall the homebridge user, and that got the UI working:
sudo hb-service install --user homebridge
Now I'm having to reinstall plugins.

@jca2112 I think your issue may have been different than the one reported by @petebocken, in his case the install of version homebridge-config-ui-x 4.50.3 did not succeed and he was able to recover manually.
In your case I think the install corrupted homebridge-config-ui-x, and one method of recovery would be to try these steps.
sudo hb-shell
npm install -g homebridge-config-ui-x

The homebridge apt package creates its own location for the installation of homebridge-config-ui-x in /opt/homebridge/lib/node_modules/homebridge-config-ui-x.  And by using the hb-shell it set's the environment settings needed.


Enable MPI support

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Closes #21

creates low-priority variants for MPI enabled versions using MPICH and OpenMPI (non-MPI version is installed by default)
does not add MPI support for OSX on ARM

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe:

License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

Documentation on acceptable licenses can be found here.

@awvwgk thanks a lot!!! I had a question on one line (added in the review). Can you also explain how to choose the version that will be installed (nompi/openmpi/mpich) or point me to a documentation page where this is discussed? Thanks again

The conda-forge knowledge base is quite detailed on this topic: https://conda-forge.org/docs/maintainer/knowledge_base.html#message-passing-interface-mpi
The mpi package on conda-forge is a virtual package which makes MPICH and OpenMPI mutually exclusive. With the build variants of conda-build defined in conda_build_config.yaml in the recipe directory we create three variants (nompi, mpich, openmpi), where only the MPI variants depend on MPI. To make the selection straight-forward for conda install, we increase the build number for the non-MPI build to be always preferred over the MPI variants.
The user has to explicitly install the MPI variant (see https://dftbplus-recipes.readthedocs.io/en/latest/introduction.html#installing-from-conda-forge)
conda install plumed  # always non-MPI version of plumed
conda install 'plumed=*=mpi_*'  # some MPI version of plumed
conda install mpich 'plumed=*=mpi_*'  # MPICH version of plumed

The conda-forge knowledge base is quite detailed on this topic: https://conda-forge.org/docs/maintainer/knowledge_base.html#message-passing-interface-mpi
The mpi package on conda-forge is a virtual package which makes MPICH and OpenMPI mutually exclusive. With the build variants of conda-build defined in conda_build_config.yaml in the recipe directory we create three variants (nompi, mpich, openmpi), where only the MPI variants depend on the mpi metapackage. To make the selection straight-forward for conda install, we increase the build number for the non-MPI build to be always preferred over the MPI variants.
The user has to explicitly install the MPI variant:
conda install plumed  # always non-MPI version of plumed
conda install 'plumed=*=mpi_*'  # some MPI version of plumed
conda install mpich 'plumed=*=mpi_*'  # MPICH version of plumed

Amazing... thanks a lot!

@awvwgk sorry for coming back to this, I have a little doubt. In the documentation you pointed to there are also these lines:
{% if mpi == 'nompi' %}
# prioritize nompi variant via build number
{% set build = build + 100 %}
{% endif %}

These are not present in the plumed recipe. Could you explain how the priority of nompi is controlled?
Thanks!
Giovanni

My bad, I forgot to add those lines to recipe, sorry about that. I just checked and an unspecified install will pick some plumed version and maybe even install some MPI in the same environment, unless there is a constraint present which prefers one of the three available versions.
Adding those three lines to the recipe would properly prioritize the non-MPI version. I can submit a patch to fix it.


Allow chaining of Router.addRoute() calls

Existing interface is a bit annoying when writing new router:
router.addRoute({
  ...
});

router.addRoute({
  ...
});

// +100500 route.addRoute calls

I suppose to return router instance from addRoute to allow chaining:
router
    .addRoute({
     ...
    })
    .addRoute({
      ...
    });

Only a bit of sugar, no anything more..

May be add new method: pushRoute, appendRoute or ...
Because returning an instance of created route can be useful and I don't want to break backwards compatibility.


The ocds:Award url does not work

When I put in a browser http://data.tbfy.eu/ontology/ocds#Award redirects me to http://<IP_ADDRESS>:7200/ontology/ocds#Award and the message 'Cannot connect' appears

Please, Brian/Ahmet, can you check this? I think it is redirecting to old URIs.

Was fixed a long time ago. URL redirects to https://raw.githubusercontent.com/TBFY/ocds-ontology/master/model/ocds.ttl#Award

Was fixed a long time ago. URL redirects to https://raw.githubusercontent.com/TBFY/ocds-ontology/master/model/ocds.ttl#Award


feat: Improve Error Handling by Adding Display Implementations

This pull request aims to improve the error-handling mechanism of the codebase by providing more descriptive error messages. It involves changes across multiple files (cell.rs, log.rs) to add implementations for the fmt::Display trait for InitError.
Key Changes:

Consistent Formatting: Replaced std::fmt with fmt to maintain consistency in the code.

File: btreemap.rs

Enhanced Error Messages for InitError in cell.rs:

Describes errors related to incompatible versions and value sizes.

Detailed Error Messages for InitError in log.rs:

Explains issues with incompatible data and index versions, as well as invalid indices.

Why this is important:
Better error messages enhance the debugging experience and allow developers to understand the issues quickly, thereby saving time and effort.
Files Changed:

src/btreemap.rs
src/cell.rs
src/log.rs

Types of changes:

[x] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update (if none of the other choices apply)

@b3hr4d I think you need to sign the CLA for us to be able to merge this commit.

@b3hr4d I think you need to sign the CLA for us to be able to merge this commit.

I, b3hr4d, hereby agree to the DFINITY Foundation's CLA.


Update kong-connection-distribution dashboard

This PR

update kong-connection-distribution dashboard to work with newer versions of kong
removes node aggregation panel because it doesn't work

Checklist

[x] Update changelog in CHANGELOG.md in an end-user friendly language.

@mcharriere It's identical. Except for removing the panel that no longer worked. I only had to adjust the Variables and queries.


Error in schemas/domain.yml file or ruamel.yaml

Rasa Core version: 0.8.3
Python version:  3.5
Operating system (windows, osx, ...): Ubuntu
Issue: Error in schemas/domain.yml file or ruamel.yaml.
When I only kept the 1st line in domain.yml file, the error disappeared
policies=[MemoizationPolicy(), ChatbotPolicy()])

File "/usr/local/lib/python3.5/dist-packages/rasa_core/agent.py", line 42, in init
self.domain = self._create_domain(domain)
File "/usr/local/lib/python3.5/dist-packages/rasa_core/agent.py", line 237, in _create_domain
return TemplateDomain.load(domain)
File "/usr/local/lib/python3.5/dist-packages/rasa_core/domain.py", line 429, in load
cls.validate_domain_yaml(filename)
File "/usr/local/lib/python3.5/dist-packages/rasa_core/domain.py", line 463, in validate_domain_yaml
schema_files=[schema_file])
File "/usr/local/lib/python3.5/dist-packages/pykwalify/core.py", line 90, in init
data = yaml.safe_load(stream)
File "/usr/local/lib/python3.5/dist-packages/ruamel/yaml/main.py", line 668, in safe_load
return load(stream, SafeLoader, version)
File "/usr/local/lib/python3.5/dist-packages/ruamel/yaml/main.py", line 639, in load
return loader._constructor.get_single_data()  # type: ignore
File "/usr/local/lib/python3.5/dist-packages/ruamel/yaml/constructor.py", line 104, in get_single_data
return self.construct_document(node)
File "/usr/local/lib/python3.5/dist-packages/ruamel/yaml/constructor.py", line 114, in construct_document
for dummy in generator:
File "/usr/local/lib/python3.5/dist-packages/ruamel/yaml/constructor.py", line 611, in construct_yaml_map
value = self.construct_mapping(node)
File "/usr/local/lib/python3.5/dist-packages/ruamel/yaml/constructor.py", line 356, in construct_mapping
return BaseConstructor.construct_mapping(self, node, deep=deep)
File "/usr/local/lib/python3.5/dist-packages/ruamel/yaml/constructor.py", line 236, in construct_mapping
value = self.construct_object(value_node, deep=deep)
File "/usr/local/lib/python3.5/dist-packages/ruamel/yaml/constructor.py", line 159, in construct_object
data = constructor(self, node)
File "/usr/local/lib/python3.5/dist-packages/ruamel/yaml/constructor.py", line 631, in construct_undefined
node.start_mark)
ruamel.yaml.constructor.ConstructorError: could not determine a constructor for the tag 'tag:yaml.org,2002:python/str'
in "/usr/local/lib/python3.5/dist-packages/rasa_core/schemas/domain.yml", line 4, column 11

This is an issue we encountered just now as well, you need to downgrade pykwalify to 1.6.0 (they just released 1.6.1 which broke compatibility...)

Thanks @tmbo . it worked for me when using pykwalify==1.6.0

I've created an issue on their repository, https://github.com/Grokzen/pykwalify/issues/124.
I'll look if there is a way to fix this without breaking backward compatibility for rasa core, but for now I am going to pin the version in setup.py.


Release of version <IP_ADDRESS> of xPSDesiredStateConfiguration

Releasing version <IP_ADDRESS>

This change is

Codecov Report

Merging #635 into master will increase coverage by <1%.
The diff coverage is 90%.

@@          Coverage Diff           @@
##           master   #635    +/-   ##
======================================
+ Coverage      75%    75%   +<1%
======================================
  Files          28     28
  Lines        4187   4195     +8
  Branches        4      4
======================================
+ Hits         3147   3155     +8
  Misses       1036   1036
  Partials        4      4


<= character breaks parser

Describe the bug
This issue was described in the previous bug:
https://github.com/mjmlio/mjml/issues/485
I dont think that it was fixed as expected. For example using something like this.
<mj-raw>var isNewInSale = property.DaysInSale <= 15;</mj-raw> --- Will break PARSER and output var isNewInSale = property.DaysInSale <= 15;</mj-raw>.... anything else from here will not be parsed and we will get mjml code.
<mj-raw>var isNewInSale = 15 >= property.DaysInSale;</mj-raw> --- Will work as expected
So seams like < symbol breaking parser while > is working fine

Well situation now is still way better than #485 but yes, there's still some small cases like that where htmlparser2 thinks that's an opening tag, it's sad because some special tag as script support this feature in htmlparser2 (https://github.com/fb55/htmlparser2/issues/72) but as the author said, it's not really an option.
I don't think there's a proper fix about this one @kmcb777 can we still check if we can do something on this, but I bet the tag is still considered as open for the rest of the file :(

Hi @julius-spudvilas if you can juste use < instead of <=, this will work because htmlparser doesn't consider it as a tag.
So if you're comparing integers this workaround should be ok.
Unfortunately i made a few attempts and it turns out that being able to detect on our side that <= is not really a tag and make htmlparser ignore it would require to do really hacky things on the parser and i don't think it's safe.

Well as i mentioned it is always possible to reverse the comparison :)
1<2  is same as 2>1  and secon one always works ;)

Maybe we should take a look at https://www.npmjs.com/package/parse5  there's a compatibility mode with htmlparser2 don't think we'll be able to try out soon but if someone have time to spare. I guess parse5 might have other issues and maybe no way to handle the line number as we do for linting errors.
I'm closing for now because I think we can't do better for now


When calling from the same selection, hide the current blame

First, thanks again for writing this, I had to go through a bunch of old code today and this made it way easier to see who/when things were added. The only thing I thought would be nice is if I could use the keyboard shortcut to toggle hiding the blame once I had read it. I took a shot at making the change myself, and it seems to be working for me. Its pretty much the first python I've ever written, so no hard feelings if something needs to change.

Thanks, will release this in the next release!


Not All Flags after Installation

I installed the reporter according to the instructions.
However grafana-reporter is not added to path and i have to run it from ~/GOPATH/bin via ./grafana-reporter
if i type ./grafana-reporter --help only 3 Flags are shown. The other Flags are unknown to the reporter. I need to set the other flags and run the reporter as cmd. Do you have any idea how to solve this issue ?
/home/go/bin# ./grafana-reporter --help
Usage of ./grafana-reporter:
-ip string
Grafana IP and port (default "localhost:3000")
-port string
Port to serve on (default ":8686")
-proto string
Grafana Protocol. Change to 'https://' if Grafana is using https. Reporter will still serve http. (default "http://")
-templates string
Directory for custom TeX templates (default "templates/")

However grafana-reporter is not added to path and i have to run it from ~/GOPATH/bin via ./grafana-reporter

This is the expected behaviour. You can copy the grafana-reporter binary to your system path or add GOPATH/bin to your system path of you want.

if i type ./grafana-reporter --help only 3 Flags are shown. The other Flags are unknown to the reporter. I need to set the other flags and run the reporter as cmd. Do you have any idea how to solve this issue ?

This is bisarre. I have never seen this. The only possible explanation I can imagine is that you have somehow checked out an old version from github. I have tested the latest release and the flags are definitely there.


NameError: name 'args' is not defined

`ubuntu@ubuntu:~/permasigner$`` sudo python3 main.py
IPA Permasigner | Version main-2a4362e
Program created by Nebula | Original scripts created by zhuowei | CoreTrust bypass by Linus Henze
Traceback (most recent call last):
File "/home/ubuntu/permasigner/main.py", line 311, in
main(args)
File "/home/ubuntu/permasigner/main.py", line 61, in main
if not LdidHash.check_linux_64():
File "/home/ubuntu/permasigner/utils/hash.py", line 26, in check_linux_64
if args.debug:
NameError: name 'args' is not defined
`

Will be fixing this, hold on!

Thanks, let me know then

Could you please run git pull and try again?

Looks like it works now, thanks!


Does github.event.inputs work for workflow_call: as well?

For the workflow_dispatch version of the docker-test.yml, inputs.directory doesn't work but I think github.event.inputs.directory will, but the question is, will github.event.inputs.directory work for workflow_call:?

Nope it doesn't work for both, so I will have to create a separate manual dispatch one.

Will need to merge this to test.


Create/Delete/Update secret using Keptn API/CLI

Please see discussion for more context info:  https://github.com/keptn/keptn/discussions/2829
API

Add a /secret endpoint to the api-service to create/delete/update a secret

Is the api-service the right place?

A secret is represented by a unique secret name and a key-value-map
If the secret is already available, the POST endpoint returns the user message: The secret xyz is already available, please use another name.

CLI new CLI commands for:

keptn create secret xyz --from-literal="key1=value1" --from-literal="key2=value2": If the secret has a unique name (not already available and the key-value pairs are valid, the secret will be created.
keptn delete secret xyz: If the secret is available, it will be deleted.
keptn update secret xyz --from-literal="key1=value1" --from-literal="key3=value3": If the secret is available, the key-value pairs are updated (i.e., key1) or added (i.e., key3).

Example, the command:
kubectl -n keptn create secret generic dynatrace --from-literal="DT_API_TOKEN=$DT_API_TOKEN" --from-literal="DT_TENANT=$DT_TENANT" --from-literal="KEPTN_API_URL=$KEPTN_API_URL" --from-literal="KEPTN_API_TOKEN=$KEPTN_API_TOKEN"

can be replaced with:
keptn create secrete dynatrace -from-literal="DT_API_TOKEN=$DT_API_TOKEN" --from-literal="DT_TENANT=$DT_TENANT" --from-literal="KEPTN_API_URL=$KEPTN_API_URL" --from-literal="KEPTN_API_TOKEN=$KEPTN_API_TOKEN"

Backend

Based on the research from #3463, implement the secret management with K8s secrets.
To be clarified: Can we use RBAC to restrict the read access? (does it conflict with updating?)
A secret is created in the namespace in which Keptn is installed
Component test: Run the secret service, use (to create/update/delete) the service, check the result (on K8s): https://github.com/testcontainers/testcontainers-go

Definition of Done

[x] Clean Swagger UI (param definition, description)
[ ] Docu for CLI is updated on keptn.sh/docs
[ ] By using the Keptn API or CLI, I can create/delete/update a secret
[ ] Component test validate the behavior of the service

Integration test still TBD


Add checkpoint functionality

When scanning big tables a checkpoint can be used to store the last position of the scan.

store the last sequence number back to dynamo checkpoint table
update Reamde with instructions

this has been merged in


Update Scala versions

About this change - What it does
Updates the Scala version.
Why this way
Not done by Scala steward because it doesn't regenerate sbt-github-actions

So the PR is failing because it appears that scalafix isn't working with latest scala version yet


Winmd2ObjC binary update:

Replace [NSAutorelease alloc] with @autoreleasepool blocks

@mukhole I don't know why this is necessary. We are bumping hundreds of binaries for an unnecessary change.

We are making this change to avoid allocating NSAutorelease objects each time we dispatch a runtime call or invoke a callback.


New Service Template

#42  The issue is mentioned here.
Note, the development approach is similar to how the "current template" and "gRPC LabVIEW support" is linked and developed. Below is the dependency diagram.

Please build and install the "LabVIEW gRPC Servicer" to use the "Client Server Template New". The package that is linked here (rename the extension from .txt to .vop and install the package or build it using the build spec in the source)
ni_lib_labview_grpc_servicer-<IP_ADDRESS>.txt
,

@ccifra  Committed the template components alone. Once this is reviewed and signed off, we can create an issue for the scripting tool that generates the template from one or more proto files.

This issue is mentioned here #16
Before this change:
When the proto file package name has a "dot" in it. For example: Package.V1.
During creation of server code, we get the server code created with issues in RPC methods

During creation of client code, we get an below error and client code is not created

This issue is fixed by doing changes in two VIs:
"Translate gRPC Method FullName" VI is changed to consider a "dot" in the package name.
From:

To:

"Create LV RPC Method Name" VI is changed to consider a package name with dot and replace it with underscore to create a Method Name.
From:

To:

Test Cases:
Tested both code generation of server and client code, and basic functionality of server and client for all the below cases,

Proto file with no package name
Proto file with package name and DOT
Proto file with package name and no DOT

Some comments on the overall structure:
End RPC Call.vi is under the RPC Messages folder.  Is there a reason for that?  It is only needed when implementing a server and I think it should be part of the server class.  I am not sure we even need it since it is just a simple wrapper around the end call VI in the LV Support library.
For the messages, do we need to add _Data to the typedef of the message or can it be just be package_templatemessage.ctl
Given the path length issues do we need to have a folder per service method?  I think it would be better to just have a single folder for all methods with a messaging and registration folder under that, but all of the method VIs would be in the same folder.
What is the purpose of "RPC Method package_service_method logic.vi"

@ccifra
#1 I am good with removing it, since like you mentioned it is a wrapper. All the messages contain the "set" API which closes the RPC call themselves. If we are planning to make the "end call" VI public for developers, then we can remove them.
#2 I dont see any naming spacing concerns for the message to have a _Data with it. It came from legacy template. I will remove that as well.
#3 I have them flat in file explorer, and only on the project made some virtual folders. I will probably have only a virtual folder for each method and not have many nest under it. But the files in disk are flat under RPC methods

#4 Given the business logic are written in the event structure, and the logic should be repliacted in Sync & Async engine and it is upto developers to create VIs to modularize them - I have created a VI for it. This VI will be dropped in the event structure of sync and Async for their respective events. So, developers need not go to sync or async engines, rather just add their service logic in this VI and both sync/async will work well.  Also, when there are changes to service in proto file, the events will break but if the logic is in this VI, we could avoid disturbing the logic.
This is the idea. Please let me know your thoughts.

@ccifra I was recommending folks to create a VI under event structure for the logic, and this VI will help that. But maybe we need not have this for version 1, and look at it in future if this comes up. Less development now :)
Its easy to tell people to code here,

Rather than code here,

That does not work as well for the streaming case or when the method changes what is being stream.  I think we should think about this aspect a little more before moving forward.

Sure @ccifra . I was thinking about streaming and imagining will that be a blocking call or Asynchronous implementation. I guess if its in event structure case it will be a blocking call (even in VI) for other events. The logic should be implemented outside the event case for server streaming, if it should allow for other event calls meanwhile. I guess I will wait to look at the APIs and decide. For now, Will not build any placeholders for logic - It will be open.

@ccifra Made changes mentioned above.

This was resolved by PR #46 which included these changes.


Embed platform fields in Image spec

Carries #777 + adds other platform fields
Closes #777

(not a maintainer) I'm +1 on this, but I think it's probably worth at least mentioning pros/cons of including all the platform fields vs deprecating existing fields and adding a full proper platform object instead. :innocent:

Major con I can see with that is builders will need to set both the old fields and the new platform field to maintain backwards compatibility.
Also requires allocating another object, but 🤷

@cyphar any comments here?
ping @opencontainers/image-spec-maintainers
It seems this would warrant a bump in a minor or micro release, nothing breaks here (optional field)

I think a platform object would be a nicer solution, but :shrug: from my side too.

Updated.

Ping

ping @opencontainers/image-spec-maintainers

You could poke some folks in the weekly meeting (today) if you want to get some activity.

Thanks.  I wanted to join for a long time but the time is tough (11PM in my time zone).  Maybe, I'll make it once to push this issue forward :)

# cd .; git clone https://github.com/opencontainerd/image-spec /home/runner/work/image-spec/image-spec/go/src/github.com/opencontainerd/image-spec
Cloning into '/home/runner/work/image-spec/image-spec/go/src/github.com/opencontainerd/image-spec'...
fatal: could not read Username for 'https://github.com': terminal prompts disabled
package github.com/opencontainerd/image-spec/specs-go/v1: exit status 128

@cpuguy83 hrm. Is that a go.mod issue?

Looks like a network fluke in CI that probably just needs a restart to me 😅

/me kicked the jobs

All green now.

@cyphar Does this LGTY? I made the adjustments you'd requested before. Merging is currently blocked due to prior review.
Thanks!


SMTPSendFailedException

runtime: java17
env: standard
instance_class: F2
We are getting a SMTPSendFailedException error 530-5.7.0 authentication required.

We have followed below Google Workspace email configuration in app.yaml file
SMTP_ENABLE_STARTTLS: 'True'
SMTP_PORT: '587'
SMTP_SECRET: projects/xxxxxxxxxx/secrets/jitaccess-smtp/versions/2
SMTP_SENDER_ADDRESS<EMAIL_ADDRESS>SMTP_SENDER_NAME: jitaccess
https://googlecloudplatform.github.io/jit-access/configure-multi-party-approval/
Do you have any idea what the problem could be? Is it "app password" problem?

Recent obervation:
2024-02-06 16:37:59.968
The mail could not be delivered caused by AuthenticationFailedException: 534-5.7.9 Please log in with your web browser and then try again. For more
534-5.7.9 information, go to

On the App passwords page, use the following settings:
Select app: Select Mail
Select device: Select Other and enter a name such as JIT Access
There is no option for me to select app and the device for setting app password in the above picture

The error might be related to licensing: Could you verify that the user jitaccess-notifications@ has a Workspace license assigned and can access https://mail.google.com/?

We have a license with Google Workspace. I don't know the root cause of this problem.
We configured it with a Microsoft 365 email account to solve the problem, and now the email is working.

Thank you for confirming that this works now.
I guess there isn't anything to follow up on on the JIT Access side, so I'll close this issue.


Micropython Plasma module doesn't expose stop

Would be very useful to be able to stop the updating to allow painting without updating, and then re-starting.
I see there is a stop method in ws2812 - its just not exposed in the plasma micropython module.
A method to read an LED would be useful too, this would enable a 2nd strip to be created as an off screen buffer, make use of the set_hsv, set_rgb methods, and then copy it to the strip that is being displayed.
Taking that one step further, the option to set an LED with another LED would be nice too.
Is there any guidance on cross compiling etc.. - I'd be happy to have a go at this myself and submit a PR

Cross-compiling is something of a hassle but the steps to accomplish it are laid out in - https://github.com/pimoroni/pimoroni-pico/blob/v0.3.3/.github/workflows/micropython.yml
I've got an open issue reminding me to document this in a more human-readable way.
I just added the update() function, I wish I'd seen this Issue before I merged that. Hindsight is 20/20, eh.
If you fancy having a go, though, it's a succinct example of what and where you need to change to bind a new method in MicroPython: https://github.com/pimoroni/pimoroni-pico/pull/237/files
Getting colours is more of an issue, since there's only a back buffer and the colours are mangled through gamma correction and not recoverable. I have an outstanding Issue to look into double-buffering Plasma to solve this problem and make working with the LEDs generally nicer: https://github.com/pimoroni/pimoroni-pico/issues/239


🔧Fix: broken link

This Pull Request is...

[X] Edit typos or links
[ ] Inaccurate information
[ ] New Resources

Description
🔧Fix: broken link
https://github.com/h5bp/Front-end-Developer-Interview-Questions/tree/master/Translations/Korean
to
https://h5bp.org/Front-end-Developer-Interview-Questions/translations/korean/

항상 감사합니다! 😄


tests/dns: add tests for task 7018 - v1

Add tests for earlier raw stream reassembly for dns
Also related to
Bug #7004
Ticket
Redmine ticket:
https://redmine.openinfosecfoundation.org/issues/7018

Failed to add version-check to protect 6.0.x

Failed to add version-check to protect 6.0.x

It seems that what's missing for 6.0.x for tests task-7018-ips-stream-rule and its ids counter-part are the fields related to TCP max_regions. Are those somehow also connected to stream reassembly, somehow?

My observation was incomplete. The dns-keyword tests were passing for that test because they're 8.0.x.
Followed by: https://github.com/OISF/suricata-verify/pull/1902


bug(Overlay): OverlayRef.detach not working when using ZonelessChangeDetection (v18.2.6)

Is this a regression?

[x] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
no very sure, but around 18.2.x
Description

The overlay content has not been removed.
Reproduction
StackBlitz link:
Steps to reproduce:

git clone https://github.com/keatkeat87/ng-mat-overlay-detach-issue.git
ng serve
click open and then close.

if use ZoneChangeDetection, then no problem.
export const appConfig: ApplicationConfig = {
  providers: [provideZoneChangeDetection({ eventCoalescing: true }), provideAnimations()] // work
  // providers: [provideExperimentalZonelessChangeDetection(), provideAnimations()] // no work
};

only ZonelessChangeDetection have the problem.
if we manual call detectChanges(), then it work.
export class ModalContainerComponent {
  private readonly overlayRef = inject(OverlayRef);
  private cdk = inject(ChangeDetectorRef);

  close() {
    this.overlayRef.detach();
    this.cdk.detectChanges(); // manual detectChanges will work
    // this.cdk.detectChanges(); // without detectChanges no work
  }
}

Expected Behavior
The overlay content should be removed.
Actual Behavior
The overlay content has not been removed.
Environment
Angular CLI: 18.2.7
Node: 20.11.1
Package Manager: yarn 1.22.19
OS: win32 x64
Angular: 18.2.7
... animations, cli, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router
Package                         Version
@angular-devkit/architect       0.1802.7
@angular-devkit/build-angular   18.2.7
@angular-devkit/core            18.2.7
@angular-devkit/schematics      18.2.7
@angular/cdk                    18.2.6
@angular/material               18.2.6
@schematics/angular             18.2.7
rxjs                            7.8.1
typescript                      5.5.4
zone.js                         0.14.10

This looks like a framework issue. The combination of zoneless and one of the animations modules (either enabled or noop) prevents the element from being removed until the next change detection. I've isolated it in the following Stackblitz: https://stackblitz.com/edit/stackblitz-starters-9p2rdd?file=src%2Fmain.ts


iOS App v1.3(50)

Issues to check:

[x] https://github.com/phetsims/phet-ios-app/issues/544
[x] https://github.com/phetsims/phet-ios-app/issues/543
[ ] https://github.com/phetsims/phet-ios-app/issues/542
[ ] https://github.com/phetsims/phet-ios-app/issues/539
[x] https://github.com/phetsims/phet-ios-app/issues/538
[x] https://github.com/phetsims/phet-ios-app/issues/531
[x] https://github.com/phetsims/phet-ios-app/issues/525
[ ] https://github.com/phetsims/phet-ios-app/issues/487
[x] _https://github.com/phetsims/phet-ios-app/issues/450_

For 51:

[ ] https://github.com/phetsims/phet-ios-app/issues/507
[ ] https://github.com/phetsims/phet-ios-app/issues/487

For 52:

[ ] https://github.com/phetsims/phet-ios-app/issues/550
[ ] https://github.com/phetsims/phet-ios-app/issues/549
[ ] https://github.com/phetsims/phet-ios-app/issues/548
[ ] https://github.com/phetsims/phet-ios-app/issues/530

For 53:

[ ] https://github.com/phetsims/phet-ios-app/issues/551
[ ] https://github.com/phetsims/phet-ios-app/issues/550
[ ] https://github.com/phetsims/phet-ios-app/issues/549
[ ] https://github.com/phetsims/phet-ios-app/issues/548
[ ] https://github.com/phetsims/phet-ios-app/issues/539
[ ] https://github.com/phetsims/phet-ios-app/issues/530

Closing and moving to a new issue


Parsing bug

In the following code
var moment = require("moment-jalaali")
const userInput = "01/01/1395";
moment(userInput, 'jYYYY/jM/jD').isValid();//true
moment(userInput, 'jYYYY/jM/jD').format('jYYYY/jM/jD');//"0001/1/13"

As you can see , I want to parse jYYYY/jM/jD format but user input is different and the result is wrong, it must not parse it
When we have multiple format :
var moment = require("moment-jalaali")
moment("01/01/1395", ['jYYYY/jM/jD','jM/jD/jYYYY']).format('jYYYY/jM/jD');//"0001/1/13"
moment("01/01/1395", ['jM/jD/jYYYY','jYYYY/jM/jD']).format('jYYYY/jM/jD');//"1395/1/1"

As you can see the result is changed when we change order of format

@733amir @aaghamohammadi @alisinabh @alitaheri @behrang @mousavian @novid
Reply please

Use the Boolean strict parameter in constructor:
moment(userInput, 'jYYYY/jM/jD', true).isValid();

@behrang  your paser is different from momentjs parser
https://momentjs.com/docs/#/parsing/string-format/

Why? Any sample code?

@behrang Sorry,I think I make mistake

Ok.

@behrang I found that there is an issue in strict mode
var moment = require("moment-jalaali")

moment.utc("1397-01-01",'jYYYY-jMM-jDD').toDate();//Wed Mar 21 2018 03:30:00 GMT+0330 (Iran Standard Time)

moment.utc("1397-01-01",'jYYYY-jMM-jDD',true).toDate();//Wed Mar 21 2018 00:00:00 GMT+0330 (Iran Standard Time)

As you can see in strick mode we loose time zone offset

In momentjs we have
var moment = require("moment")

moment.utc("2018-12-01",'YYYY-MM-DD').toDate();//Sat Dec 01 2018 03:30:00 GMT+0330 (Iran Standard Time)
moment.utc("2018-12-01",'YYYY-MM-DD',true).toDate();//Sat Dec 01 2018 03:30:00 GMT+0330 (Iran Standard Time)

I open https://github.com/jalaali/moment-jalaali/issues/161


gitops run: replace the promptui library for Weave GitOps

User Story:
As a Weave GitOps developer,
I want to replace the promptui library with a more reliable and actively maintained alternative so that I can avoid race conditions and ensure the stability and maintainability of the WG OSS project.
Acceptance Criteria

Identify a suitable alternative library that is actively maintained and does not have known race condition issues.
The new library should provide similar functionality to the promptui library, especially the user prompts functionalities.
Replace all instances of the promptui library in the Weave GitOps project with the new library. Also in the go.mod.
Confirm that Weave GitOps continues to function as expected, with no loss of functionality, and without race conditions.

Investigated the issue. The best option looks like replacing promptui with the survey library (which is used in GitHub CLI). But more testing concerning binary size and investigation on how how to replace some hardcoded colors in survey with system colors is needed.
Closes as a low-priority issue which would require too much effort right now.


Where does it generate the nu get package and how to consume it

perhaps this is a nice place to document where it creates the nuget package and what the license settings needs to work

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 1490ea17-1bce-6eb1-0a78-1b8159b82e4e
Version Independent ID: 4350b38b-6f06-16b6-da75-4d85c6c43909
Content: Assembly Information Dialog Box - Visual Studio
Content Source: docs/ide/reference/assembly-information-dialog-box.md
Product: visual-studio-windows
Technology: vs-ide-general
GitHub Login: @gewarren
Microsoft Alias: gewarren

Comment to trigger priority label.

I think we're better off linking to NuGet docs from here. I'll update.