Retry with node selector does not retry only specified step

Pre-requisites

[X] I have double-checked my configuration
[X] I can confirm the issues exists when I tested with :latest
[ ] I'd like to contribute the fix myself (see contributing guide)

What happened/what you expected to happen?
when I run a workflow with two parallel steps, I can't restart only one of them. If I run, for instance,
argo retry greeter-workflow-steps-dev-vx9zf  -n infra-compute  --node-field-selector="id=greeter-workflow-steps-dev-vx9zf-2583895212"

all failed nodes are restarted, despite my node field selector.
Am I running the command wrong?
Version
v3.4.8
Paste a small workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.
we use a helm chart that adds env vars to all containers, so I can only past the "spec" portion.
    spec:
    entrypoint: steps
    templates:
      - name: steps
        steps:
          - - name: step1
              inline:
                container:
                  image: alpine:3.7
                  env: []
                  args: [echo, 'hello inline']
            - name: step2
              template: template-with-input
              arguments:
                parameters: [{name: message, value: 'hello1'}]
            - name: step3
              template: fail
            - name: step4
              template: fail
      - name: container-only
        container:
          env:
            - name: 'KEY'
              value: 'VALUE2'
          image: alpine:3.7
          args: [ echo, '$KEY']
      - name: template-with-input
        inputs:
          parameters:
            - name: message
        container:
          image: alpine:3.7
          args: [echo, 'message is {{inputs.parameters.message}}']
      - name: fail
        container:
          image: alpine:3.7
          args: [exit 1]

or
spec:
    entrypoint: steps
    templates:
      - name: steps
        steps:
          - - name: step1
              inline:
                container:
                  image: alpine:3.7
                  env: []
                  args: [echo, 'hello inline']
            - name: step2
              template: fail
          - - name: step3
              template: template-with-input
              arguments:
                parameters: [{name: message, value: 'hello1'}]
            - name: step4
              template: fail
      - name: container-only
        container:
          env:
            - name: 'KEY'
              value: 'VALUE2'
          image: alpine:3.7
          args: [ echo, '$KEY']
      - name: template-with-input
        inputs:
          parameters:
            - name: message
        container:
          image: alpine:3.7
          args: [echo, 'message is {{inputs.parameters.message}}']
      - name: fail
        container:
          image: alpine:3.7
          args: [exit, '1']

### Logs from the workflow controller

```text
kubectl logs -n argo deploy/workflow-controller | grep ${workflow}

Found 2 pods, using pod/workflows-argo-workflows-workflow-controller-694df9c9b-mkh9t
time="2023-06-29T21:08:11.857Z" level=info msg="Processing workflow" namespace=infra-compute workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:11.896Z" level=info msg="Updated phase  -> Running" namespace=infra-compute workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:11.896Z" level=info msg="Steps node greeter-workflow-steps-dev-wcd48 initialized Running" namespace=infra-compute workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:11.896Z" level=info msg="StepGroup node greeter-workflow-steps-dev-wcd48-3982387348 initialized Running" namespace=infra-compute workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:11.896Z" level=info msg="Pod node greeter-workflow-steps-dev-wcd48-4236060887 initialized Pending" namespace=infra-compute workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:11.927Z" level=info msg="Created pod: greeter-workflow-steps-dev-wcd48[0].step1 (greeter-workflow-steps-dev-wcd48--4236060887)" namespace=infra-compute workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:11.927Z" level=info msg="Pod node greeter-workflow-steps-dev-wcd48-4252838506 initialized Pending" namespace=infra-compute workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:11.946Z" level=info msg="Created pod: greeter-workflow-steps-dev-wcd48[0].step2 (greeter-workflow-steps-dev-wcd48-template-with-input-4252838506)" namespace=infra-compute workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:11.946Z" level=info msg="Pod node greeter-workflow-steps-dev-wcd48-4269616125 initialized Pending" namespace=infra-compute workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:11.966Z" level=info msg="Created pod: greeter-workflow-steps-dev-wcd48[0].step3 (greeter-workflow-steps-dev-wcd48-fail-4269616125)" namespace=infra-compute workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:11.966Z" level=info msg="Pod node greeter-workflow-steps-dev-wcd48-4152172792 initialized Pending" namespace=infra-compute workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:11.986Z" level=info msg="Created pod: greeter-workflow-steps-dev-wcd48[0].step4 (greeter-workflow-steps-dev-wcd48-fail-4152172792)" namespace=infra-compute workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:11.986Z" level=info msg="Workflow step group node greeter-workflow-steps-dev-wcd48-3982387348 not yet completed" namespace=infra-compute workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:11.986Z" level=info msg="TaskSet Reconciliation" namespace=infra-compute workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:11.986Z" level=info msg=reconcileAgentPod namespace=infra-compute workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:11.999Z" level=info msg="Workflow update successful" namespace=infra-compute phase=Running resourceVersion=1112641463 workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:21.927Z" level=info msg="Processing workflow" namespace=infra-compute workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:21.927Z" level=info msg="Task-result reconciliation" namespace=infra-compute numObjs=0 workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:21.927Z" level=info msg="node changed" namespace=infra-compute new.message=PodInitializing new.phase=Pending new.progress=0/1 nodeID=greeter-workflow-steps-dev-wcd48-4269616125 old.message= old.phase=Pending old.progress=0/1 workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:21.927Z" level=info msg="node changed" namespace=infra-compute new.message=PodInitializing new.phase=Pending new.progress=0/1 nodeID=greeter-workflow-steps-dev-wcd48-4236060887 old.message= old.phase=Pending old.progress=0/1 workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:21.927Z" level=info msg="node changed" namespace=infra-compute new.message=PodInitializing new.phase=Pending new.progress=0/1 nodeID=greeter-workflow-steps-dev-wcd48-4152172792 old.message= old.phase=Pending old.progress=0/1 workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:21.927Z" level=info msg="node changed" namespace=infra-compute new.message=PodInitializing new.phase=Pending new.progress=0/1 nodeID=greeter-workflow-steps-dev-wcd48-4252838506 old.message= old.phase=Pending old.progress=0/1 workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:21.928Z" level=info msg="Workflow step group node greeter-workflow-steps-dev-wcd48-3982387348 not yet completed" namespace=infra-compute workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:21.928Z" level=info msg="TaskSet Reconciliation" namespace=infra-compute workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:21.928Z" level=info msg=reconcileAgentPod namespace=infra-compute workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:21.939Z" level=info msg="Workflow update successful" namespace=infra-compute phase=Running resourceVersion=1112641864 workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:31.940Z" level=info msg="Processing workflow" namespace=infra-compute workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:31.940Z" level=info msg="Task-result reconciliation" namespace=infra-compute numObjs=0 workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:31.940Z" level=info msg="node unchanged" namespace=infra-compute nodeID=greeter-workflow-steps-dev-wcd48-4152172792 workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:31.940Z" level=info msg="node unchanged" namespace=infra-compute nodeID=greeter-workflow-steps-dev-wcd48-4252838506 workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:31.940Z" level=info msg="node unchanged" namespace=infra-compute nodeID=greeter-workflow-steps-dev-wcd48-4236060887 workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:31.940Z" level=info msg="node unchanged" namespace=infra-compute nodeID=greeter-workflow-steps-dev-wcd48-4269616125 workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:31.941Z" level=info msg="Workflow step group node greeter-workflow-steps-dev-wcd48-3982387348 not yet completed" namespace=infra-compute workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:31.941Z" level=info msg="TaskSet Reconciliation" namespace=infra-compute workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:31.941Z" level=info msg=reconcileAgentPod namespace=infra-compute workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:56.168Z" level=info msg="Processing workflow" namespace=infra-compute workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:56.168Z" level=info msg="Task-result reconciliation" namespace=infra-compute numObjs=0 workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:56.168Z" level=info msg="node changed" namespace=infra-compute new.message= new.phase=Succeeded new.progress=0/1 nodeID=greeter-workflow-steps-dev-wcd48-4236060887 old.message=PodInitializing old.phase=Pending old.progress=0/1 workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:56.168Z" level=info msg="Pod failed: Error (exit code 64): failed to find name in PATH: exec: \"exit\": executable file not found in $PATH" displayName=step3 namespace=infra-compute pod=greeter-workflow-steps-dev-wcd48-fail-4269616125 templateName=fail workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:56.168Z" level=info msg="node changed" namespace=infra-compute new.message="Error (exit code 64): failed to find name in PATH: exec: \"exit\": executable file not found in $PATH" new.phase=Failed new.progress=0/1 nodeID=greeter-workflow-steps-dev-wcd48-4269616125 old.message=PodInitializing old.phase=Pending old.progress=0/1 workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:56.168Z" level=info msg="node changed" namespace=infra-compute new.message= new.phase=Succeeded new.progress=0/1 nodeID=greeter-workflow-steps-dev-wcd48-4252838506 old.message=PodInitializing old.phase=Pending old.progress=0/1 workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:56.168Z" level=info msg="Pod failed: Error (exit code 64): failed to find name in PATH: exec: \"exit\": executable file not found in $PATH" displayName=step4 namespace=infra-compute pod=greeter-workflow-steps-dev-wcd48-fail-4152172792 templateName=fail workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:56.168Z" level=info msg="node changed" namespace=infra-compute new.message="Error (exit code 64): failed to find name in PATH: exec: \"exit\": executable file not found in $PATH" new.phase=Failed new.progress=0/1 nodeID=greeter-workflow-steps-dev-wcd48-4152172792 old.message=PodInitializing old.phase=Pending old.progress=0/1 workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:56.169Z" level=info msg="Step group node greeter-workflow-steps-dev-wcd48-3982387348 deemed failed: child 'greeter-workflow-steps-dev-wcd48-4269616125' failed" namespace=infra-compute workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:56.169Z" level=info msg="node greeter-workflow-steps-dev-wcd48-3982387348 phase Running -> Failed" namespace=infra-compute workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:56.169Z" level=info msg="node greeter-workflow-steps-dev-wcd48-3982387348 message: child 'greeter-workflow-steps-dev-wcd48-4269616125' failed" namespace=infra-compute workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:56.169Z" level=info msg="node greeter-workflow-steps-dev-wcd48-3982387348 finished: 2023-06-29 21:08:56.169247735 +0000 UTC" namespace=infra-compute workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:56.169Z" level=info msg="step group greeter-workflow-steps-dev-wcd48-3982387348 was unsuccessful: child 'greeter-workflow-steps-dev-wcd48-4269616125' failed" namespace=infra-compute workflowgreeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:56.169Z" level=info msg="Outbound nodes of greeter-workflow-steps-dev-wcd48-4236060887 is [greeter-workflow-steps-dev-wcd48-4236060887]" namespace=infra-compute workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:56.169Z" level=info msg="Outbound nodes of greeter-workflow-steps-dev-wcd48-4252838506 is [greeter-workflow-steps-dev-wcd48-4252838506]" namespace=infra-compute workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:56.169Z" level=info msg="Outbound nodes of greeter-workflow-steps-dev-wcd48-4269616125 is [greeter-workflow-steps-dev-wcd48-4269616125]" namespace=infra-compute workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:56.169Z" level=info msg="Outbound nodes of greeter-workflow-steps-dev-wcd48-4152172792 is [greeter-workflow-steps-dev-wcd48-4152172792]" namespace=infra-compute workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:56.169Z" level=info msg="Outbound nodes of greeter-workflow-steps-dev-wcd48 is [greeter-workflow-steps-dev-wcd48-4236060887 greeter-workflow-steps-dev-wcd48-4252838506 greeter-workflow-steps-dev-wcd48-4269616125 greeter-workflow-steps-dev-wcd48-4152172792]" namespace=infra-compute workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:56.169Z" level=info msg="node greeter-workflow-steps-dev-wcd48 phase Running -> Failed" namespace=infra-compute workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:56.169Z" level=info msg="node greeter-workflow-steps-dev-wcd48 message: child 'greeter-workflow-steps-dev-wcd48-4269616125' failed" namespace=infra-compute workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:56.169Z" level=info msg="node greeter-workflow-steps-dev-wcd48 finished: 2023-06-29 21:08:56.16977965 +0000 UTC" namespace=infra-compute workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:56.169Z" level=info msg="Checking daemoned children of greeter-workflow-steps-dev-wcd48" namespace=infra-compute workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:56.169Z" level=info msg="TaskSet Reconciliation" namespace=infra-compute workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:56.169Z" level=info msg=reconcileAgentPod namespace=infra-compute workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:56.169Z" level=info msg="Updated phase Running -> Failed" namespace=infra-compute workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:56.170Z" level=info msg="Updated message  -> child 'greeter-workflow-steps-dev-wcd48-4269616125' failed" namespace=infra-compute workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:56.170Z" level=info msg="Marking workflow completed" namespace=infra-compute workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:56.170Z" level=info msg="Checking daemoned children of " namespace=infra-compute workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:56.175Z" level=info msg="cleaning up pod" action=deletePod key=infra-compute/greeter-workflow-steps-dev-wcd48-1340600742-agent/deletePod
time="2023-06-29T21:08:56.185Z" level=info msg="Workflow update successful" namespace=infra-compute phase=Failed resourceVersion=1112643153 workflow=greeter-workflow-steps-dev-wcd48
time="2023-06-29T21:08:56.186Z" level=info msg="Queueing Failed workflow infra-compute/greeter-workflow-steps-dev-wcd48 for delete in 5m0s due to TTL"
time="2023-06-29T21:09:01.195Z" level=info msg="cleaning up pod" action=deletePod key=infra-compute/greeter-workflow-steps-dev-wcd48-template-with-input-4252838506/deletePod
time="2023-06-29T21:09:01.195Z" level=info msg="cleaning up pod" action=deletePod key=infra-compute/greeter-workflow-steps-dev-wcd48-fail-4269616125/deletePod
time="2023-06-29T21:09:01.195Z" level=info msg="cleaning up pod" action=deletePod key=infra-compute/greeter-workflow-steps-dev-wcd48-fail-4152172792/deletePod
time="2023-06-29T21:09:01.195Z" level=info msg="cleaning up pod" action=deletePod key=infra-compute/greeter-workflow-steps-dev-wcd48--4236060887/deletePod

### Logs from in your workflow's wait container

```text
N/A

How to get involved in argo workflows for the contribution.

Relevant code is here. Would anyone like to take a look? https://github.com/argoproj/argo-workflows/blob/master/workflow/util/util.go#L804

I think this relates to https://github.com/argoproj/argo-workflows/issues/10675 where the possible key/values for node selector are very hard to know

I think this relates to #10675 where the possible key/values for node selector are very hard to know

@tooptoop4 Are you saying it might just be an issue with my CLI command? If so, that would be great.

If this is indeed a bug, I may be able to justify some time toward this in the next couple of months. We're evaluating Argo Workflows right now as a DAG solution. We still have a lot of work to do toward that end, but being able to retry only specific failed nodes is a requested feature of any solution we go with.

the trouble is we don't have an enum of available values, so we could be sending argument of step(0).abc when it really expects step-0.template.abc or something else! we just don't know

any luck @sstaley-hioscar ?

any luck @sstaley-hioscar ?
So far no one's requested the feature on our end

Seems like this has been superseded by #12543 which has had a decent bit of activity


May rowkey be duplicated in different db?

[ ] I have searched the issues of this repository and believe that this is not a duplicate.

Ⅰ. Issue Description
As I know, in AT mode. The global lock key is getRowKey(rowLock.getResourceId(), rowLock.getTableName(), rowLock.getPk()));
There are two totally different db, may their lockkey be the same? Because the resourceId may be the same?
在AT模式中，全局锁的key是resourceId+tablename+pk。有没可能两个完全不相关的db，他们的锁key是一样的，因为resourceid可能是一样，比如jdbc里的地址是虚地址？ 这会导致两个无关的应用抢同一个锁。
请问seata是如何考虑这个问题的，或者我理解有误。谢谢
Ⅱ. Describe what happened
If there is an exception, please attach the exception trace:
Just paste your stack trace here!

Ⅲ. Describe what you expected to happen
Ⅳ. How to reproduce it (as minimally and precisely as possible)

xxx
xxx
xxx

Ⅴ. Anything else we need to know?
Ⅵ. Environment:

JDK version :
Seata version:
OS :
Others:

jdbc:mysql://<IP_ADDRESS>:3306/seata-order^^^order^^^2188
你觉得ip+dbname会出现相同mysqlip上有2个dbname一样几率大吗？


Runtime: Support DuckDB exports using COPY TO

Closed by https://github.com/rilldata/rill/pull/2870


[#120] Moderation page href added on dashboard moderation widget

Link added to widget using BookmarkablePageLink component.

:+1: Thanks!


More Clarification on the Dataflows Limitations

Could you provide clarification on the statement that Dataflows feature is not supported for Multi-Geo:

Is it that dataflows are disabled?
Is it that dataflows are supported, but data storage and metadata all reside in the Home Tenant location?

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

ID: 2e1ae590-933f-bf65-888e-03dbf0ddc252
Version Independent ID: ae8f54bb-5fdb-a071-528d-169b4b766be6
Content: Multi-Geo support for Power BI Premium - Power BI
Content Source: powerbi-docs/admin/service-admin-premium-multi-geo.md
Service: powerbi
Sub-service: powerbi-admin
GitHub Login: @davidiseminger
Microsoft Alias: davidi

Thanks for the question, @olyamusok. I'm assigning this issue to the author to look into providing that clarification.

@davidiseminger @kfollis
Adding to the above question. After testing with capacity in remote region I am able to

create dataflows
create and publish reports based on dataflows stored in a different capacity located in home region
This by itself brings a whole list of questions on where the data is actually stored in these cases?

On another note on something else I do not see mentioned anywhere in documentation:
For new capacities in remote regions dataflows workload can not be disabled at all, see on the screenshot the toggle is greyed out to on by default, which calls for explanation:

TIA

We've updated all the dataflows documentation to address issues.

@Davidseminger Could you please point me to the articles that have the updates related to dataflow storage and in particular its relation to Mult-Geo. I do not see any changes or clarifications in the article text: Multi-Geo support for Power BI Premium - Power BI
Do I need to look at a different doc? Thank you

@olyamusok  - I don't think this article has the info you need, but the updated dataflow documentation is located in this section: https://docs.microsoft.com/en-us/power-bi/transform-model/dataflows/dataflows-introduction-self-service


Question related to your "CSGO cheating dataset" on Kaggle

Hi @LaihoE , I came across your dataset on Kaggle (https://www.kaggle.com/datasets/emstatsl/csgo-cheating-dataset/data?selectedOnly=true) and wanted to know if this parser was used to collect that data? I noticed that the parser can output a host of helpful fields and since the Kaggle dataset is a minimal version of this, I was curious as to 1) how it was curated and 2) how the labeling of "cheater" and "legit" players was performed?
I have been using that dataset for my own side project (a comparative analysis between manual coding and an AI assisted approach) and I am working on a short blog post which is why I wanted to know more about how you built that dataset.
Thanks,
Mehnaaz

Hi @MehnaazAsad! Markus parser was used to collect the data https://github.com/markus-wa/demoinfocs-golang. This library only works for CS2.
As for the labeling, websites like faceit used to have a list of banned players and then the most recent game of said player would be labeled as "cheating" data. This would mean that some of the data may not have been labeled correctly. As for the "legit" players I dont think anything special was done, just anyone who didnt have a ban was used.
Despite the data possibly having some incorrectly labeled data, I got a model made https://github.com/LaihoE/DLAC. I dont have any numbers on how well it worked as it was also hard to even know if a false positive really was a false positive or if a "legit" player really was a cheater. That being said I got the false positive rate very low and the model could have been used as a filter.
This parser exposes a bunch of new stuff that could be interesting. Things like aim punch angles, button presses, local viewangles and so on could be added among many more.

Thanks for all the info @LaihoE!! Definitely a wealth of information here!


Version 2.4.0 not available in Chef Supermarket?

For some reason https://supermarket.chef.io/cookbooks/openssh still shows 2.3.1 as the latest one, causing Berks to fail. Is this something you guys can fix? Or is this how it should be and I'm missing something?
Cheers!

Looks like the push failed. I pushed it up again. Sorry about that


SMD_671 - Integrate PF mappings extraction into pipeline

Ticket
SMD_671 - Integrate PF mappings extraction into pipeline
Summary of changes

Renamed extraction tags in test spreadsheets (and reference spreadsheet on SharePoint) to clearly separate "User" and "Control" tables, reflected change in code
Added control table extraction and control mapping creation to ingest function in ingest.py module. As a quick explainer, control mappings are lookup tables (dicts) that can be used in cross-table validation or transformation, and obtaining them involves extracting the tables as DataFrames from the spreadsheet (via extract_process_validate_tables) and then processing those DataFrames into dicts (via create_control_mappings)
Changing interface of extract_process_validate_tables such that it returns a dictionary of DataFrames not Tables. It seems to make more sense as the only reason the Table wrapper exists around a DataFrame is to support extraction and error messaging during validation, so once extraction and validation has taken place we should strip it away
Adding basic column validation to control table extraction config - this was added because having an empty dictionary for validate doesn't work with the current extraction / validation code, because _check_columns inside TableValidator throws an error when it sees that the schema doesn't match the table
Removing standard output and outcome extraction from control table extraction config - standard outputs and outcomes are just lists of possible values, not mapping tables, and because we pass the entire output of this control table extraction into the create_control_mappings function, it simplifies things to make sure that all tables in this output are mapping tables. An alternative could be to extract all control tables but then only pass the mapping tables to create_control_mappings. This would allow us to do things like checking outputs against a defined list in cross-table validation

Hey @cyrusdobbs I've added a docstring to the create_control_mapping function and also done a small refactor as per our conversation over Slack. The user data and control data config dictionaries have been combined into a single config dictionary, and this gets passed into extract_process_validate_tables. Inside that we will call cross_validate (I guess the callable will be injected) such that it has access to the Table objects for error messaging but we can keep a clean interface for extract_process_validate_tables of DataFrame dictionary in, DataFrame dictionary out. It can access the control data mappings by calling create_control_mappings and passing in the extracted tables from the merged config, which will include the control data tables necessary to create the mappings. Then downstream in transformation, we will call create_control_mappings again. So it's duplication but with the benefit of removing the need to inject control_mappings as a dependency or pass Table objects around at the level of the ingest module.
This means the actual integration of mapping extraction via a call to create_control_mappings will now be shifted to the PR I will shortly open for transformation integration, and we'll also need that call in the cross-validation PR you're working on.


Add a new state given by celery in rare occasions

Fixes #545
Add a new state given by celery on rare occasions
Check:
https://github.com/repository-service-tuf/repository-service-tuf-worker/blob/63c77974a402b80f618aecb9f124a6466d61149b/app.py#L118

Rebased on top of the latest main changes. Ready for approval again @kairoaraujo.


Trajectory Semantic Clustering

Hi,
Thank you for your research and for publishing this code. I'm reproducing your experiment on the Foursquare dataset and have some questions (not technical ones):

The output of your model is the next location. What changes should I make to output clusters of user trajectory movement semantically? For example, two users do not necessarily have to be in the same physical trajectory to be in the same cluster, but rather in the same semantic context (home, work, etc.).
Instead of next-location prediction, do you have any idea of using a seq2seq autoencoder to encode trajectory features, and then cluster them using K-MEANS or something?

I would appreciate your help with this.

Hi, Thanks for your interest in the research. I provide the answers below (according to the best of my understanding):

A straightforward adoption is to change the location embedding to an activity embedding, and instead of the location identifier, you input the activity label of each record. This will arguably simplify the model, and you might want to reduce the model's capacity (e.g., layers, heads)
You might want to check out works with the keywords trajectory embedding. For the MHSA network, you can take the vector given in the last layer (the one before softmax) and regard it as a trajectory representation, just that the representation is optimized for next location prediction and not for, e.g., user profiling.


FIX: Block Manifest of the compatibility class Object and lean on the compatibility auto loader

On PHP 7.2 initial dev/build of a SilverStripe 3.7.1 site can throw a Fatal error: Cannot use 'Object' as class name as it is reserved, I experienced this on SilverStripe Platform causing the deployment to fail and rollback.
This pull request simply adds a manifest exclude file in core/compat which causes the framework to lean on the auto loader defined in model/fieldtypes/compat/autoload.php instead.

Will this make it into the upcoming 3.7.3 release? or will it need to wait until 3.7.4? Trying to plan ahead with one of our projects that's moving to SilverStripe Platform on a stack that's currently configured for PHP 7.2, but without this pull being merged would need to be downgraded to PHP 7.1.


The deployment is continuously failing on OKD 3.11.

Hello,
following the install instructions for the  cluster wide case:
oc apply -fhttps://raw.githubusercontent.com/tnozicka/openshift-acme/master/deploy/cluster-wide/{clusterrole,serviceaccount,issuer-letsencrypt-live,deployment}.yaml
 oc create clusterrolebinding openshift-acme --clusterrole=openshift-acme --serviceaccount="$( oc project -q ):openshift-acme" --dry-run -o yaml | oc apply -f -

we are getting error with 2 hanging pods:
openshift-acme-68f96bc4cf-bctsm
Error: container has runAsNonRoot and image will run as root
8 times in the last

What kind of ssc one should set for the service account in order to start the openshift-acme deployment?
Thanks,
Arman.

I did deploy it on OKD 3.11 and it works - I went in cluster wide option.


Support RP's user agent in mgmt plane lro

Description
Fix #1588
Currently we use the user agent azsdk-net-ResourceManager in all the mgmt plane SDK, this PR aims to modify the user agent according to the RP SDK info.
Checklist
To ensure a quick review and merge, please ensure:

[ ] The PR has a understandable title and description explaining the why and what.
[ ] The PR is opened in draft if not ready for review yet.

If opened in draft, please allocate sufficient time (24 hours) after moving out of draft for review

[ ] The branch is recent enough to not have merge conflicts upon creation.

Ready to Land?

[ ] Build is completely green

Submissions with test failures require tracking issue and approval of a CODEOWNER

[ ] At least one +1 review by a CODEOWNER
[ ] All -1 reviews are confirmed resolved by the reviewer

Override/Marking reviews stale must be discussed with CODEOWNERS first

Can we use a class, instead of a Dictionary?


PostCSS plugin tailwindcss-jit requires PostCSS 8

What version of @tailwindcss/jit are you using?
v0.1.6
What version of Node.js are you using?
v14.15.1
What browser are you using?
firefox, Chrome
What operating system are you using?
macOS
Reproduction repository
https://github.com/MuttakinHasib/cloudsbay
Create React App
http://localhost:3000/

Hey! Yep this project requires PostCSS v8 as the error mentions. You have an error in your postcss.config.js file as well, you don't need tailwindcss and @tailwindcss/jit, just @tailwindcss/jit as mentioned in the instructions 👍🏻

how can i use @tailwindcss/jit in this project ?

Create React App unfortunately uses an old version of PostCSS and isn't kept up to date, so you will have to wait until CRA updates their version of PostCSS or use a different tool.
Personally I would recommend Vite as an alternative for anyone who likes CRA — it's a great experience for building CRA-style projects.


Create Package, precompiled header files

Using vc17  i have created a project that doesn't use precompiled headers. The project compiles and executes successfully, But when i try create a store app package the build process fails with the message
"unexpected end of file while looking for precompiled header. did you forget to add #include stdafx.h to your source?"
no, i didn't forget to add it. i don't use precompliled headers  but the create package process refuses to acknowledge that.
can anyone provide a work around for this?

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

ID: e9d1c88d-24b1-0eda-b458-105db02dca36
Version Independent ID: c5d1634a-0ead-f68a-e5be-89acf0eef0a6
Content: Packaging UWP apps - Windows UWP applications
Content Source: windows-apps-src/packaging/packaging-uwp-apps.md
Product: uwp
GitHub Login: @mcleanbyron
Microsoft Alias: mcleans

Hi @timhirrel - Unfortunately, this docs repo is not a support channel. Please see this page for your support options. You might also try the following resources:

Our MSIX and packaging forums.
Our general Windows development forums
StackOverflow


Broken wiki Images in golang/go/wiki/Mobile

I'm reading the Go Mobile docs, and some images is not found

Deploying app bundle
https://camo.githubusercontent.com/fbc28cc15ba04a995fe26925658557d8be5565fe/68747470733a2f2f676f6f676c6564726976652e636f6d2f686f73742f30427966536a64505673394d5a626b686a6555684d597a52546545452f676f77696b692f676f6d6f62696c652d696f732d6465706c6f792e706e67

Xcode project layout with hello.framework
https://camo.githubusercontent.com/ca8480d267fa6fba06cd69ddbd7a157083a7dab9/68747470733a2f2f676f6f676c6564726976652e636f6d2f686f73742f30427966536a64505673394d5a626b686a6555684d597a52546545452f676f77696b692f676f6d6f62696c652d696d706f72742d616e64726f696473747564696f2e706e67

Drag and drop Hello.framework
https://camo.githubusercontent.com/4056086ee93aa86233588f92a7e180374d11807d/68747470733a2f2f676f6f676c6564726976652e636f6d2f686f73742f30427966536a64505673394d5a626b686a6555684d597a52546545452f676f77696b692f676f6d6f62696c652d62696e642d696f73647261672e706e67

Xcode project layout with Hello.framework
https://camo.githubusercontent.com/158aaea172021b5c38d1cf2fcccfa39336384a77/68747470733a2f2f676f6f676c6564726976652e636f6d2f686f73742f30427966536a64505673394d5a626b686a6555684d597a52546545452f676f77696b692f676f6d6f62696c652d62696e642d696f732e706e67

Should this be reported here? If I know which image should be there I can send a fix, but as I am a begginer looking for how to start to work with go, I'm not familiar with this documentation yet.

The wiki is editable by anyone but if you're not sure how to fix the link reporting the problem here is the right thing to do, thanks.

Images are missing (404) and I can't find the proper URLs.
The missing images:

https://googledrive.com/host/0ByfSjdPVs9MZbkhjeUhMYzRTeEE/gowiki/gomobile-ios-deploy.png
https://googledrive.com/host/0ByfSjdPVs9MZbkhjeUhMYzRTeEE/gowiki/gomobile-import-androidstudio.png
https://googledrive.com/host/0ByfSjdPVs9MZbkhjeUhMYzRTeEE/gowiki/gomobile-bind-iosdrag.png
https://googledrive.com/host/0ByfSjdPVs9MZbkhjeUhMYzRTeEE/gowiki/gomobile-bind-ios.png

Maybe @rakyll knows where these images are (some of the commits including these screenshots came from her).

Fixed them all.


Register groupIds with Sonartype

https://central.sonatype.org/publish/publish-guide/

Either rename this repository to jct, change the groupId to com.github.java-compiler-testing, or move into the groupId into com.github.ascopes. In the latter case, we would want to rename the examples projects to something like java-compiler-testing-examples for consistency, even if they do not get deployed.

Register the desired groupId and com.github.ascopes with Sonartype to allow publishing to Maven Central by creating a JIRA at https://issues.sonatype.org/secure/CreateIssue.jspa?issuetype=21&pid=10134

Renamed repository to jct for consistency.

Global GID JIRA: https://issues.sonatype.org/browse/OSSRH-80456

JCT GID JIRA: https://issues.sonatype.org/browse/OSSRH-80457

Need to use the io.github GID rather than com.github

Both GIDs registered 🎉


Deadlock at loss.backward()

Hello, thank you for sharing your impressive work!
However, I got an issue on running your code.
Deadlock always occurs at loss.backward() of second iteration(batch index 1).
I think this is multiprocessing issue, isn't it?
My torch version is 0.4.1 and python version is 3.6.1
I hope this issue be resolved soon!

The issue may occur when the machine is out of GPU memory.   You can reduce the input size and try again.


Merge dev/release/2.1 into master

cc: @weshaggard @dagood @crummel @dleeapho

Comparing dev/release/2.1 to the merge commit, my git client tells me:
diff --git a/clean.sh b/clean.sh
old mode 100755
new mode 100644

Can you make sure the script keeps the right permissions?

Fixed :)

I just merged a few PRs into dev/release/2.1 that were waiting for RTM. I think this PR is mergeable (make sure not to squash), then I'll submit more for the new commits.

Could you please update the ReadMe to match netci.groovy?  We're not building ARM right now and we've added the tarball legs, I think you'll get those but the ReadMe doesn't look like it changed.

@dotnet-bot test CentOS7.1 Release please


alc and gex header fix

Did some minor modifications, so that Aarhus Workbench can read the xyz-data and alc-file written with libaarhus.dump(...)
Might be a bit ugly but is working. Feel free to change the coding to be more "pythonic" ;-).
Did the following modifications:

all channel/gate related information in .alc file must end on Gate_Ch01_45 not Gate_Ch01_[44].
the first gate channel must be numbered with 01 not 00 (like Gate_Ch01_01 instead of Gate_Ch01_[00]).
The xyz file must only have 1 header line, when input to AarhusWorkbench, so data['model_info'] must be skipped and not written to file.

A bit sceptical to including 9999 verbatim as a NaN value... Isn't this specified in a header in many xyz files? Possibly better to filter in the dataframe rather than in parsing maybe?


Egress controllers not passing pagination constraints

A GET request on /Users with pagination constraints does not pass the constraints to the egress handler.
Here's my setup
app.ts
SCIMMY.Resources.declare(SCIMMY.Resources.User)
    .ingress(UserController.ingress)
    .egress(UserController.egress)
    .degress((resource: any) => {
        console.log(`Request to delete user ${resource}`);
    });

users.controller.ts
export async function egress(resource: UserResource) {
    console.dir(resource, {depth: null});
    const {handle} = findUserQuery;
    return handle({filter: mappedFilters});
}

The resource is passed as-is to the controller and when I log the values in resource, I see an empty constraints object
Request

User { constraints: {} }

I expect the resource in the controller to contain a startIndex and count keys. This works well for filter and attributes.

Hi @always-akshat,

I expect the resource in the controller to contain a startIndex and count keys. This works well for filter and attributes.

Your expectation is correct, and the observed behaviour is indeed unexpected!
The underlying issue appears to be with how query string parameters are handled by express - as there's nothing to identify the type of query string parameters, they are all parsed into strings. When the string values of the startIndex and count parameters are passed to the resource at instantiation, they are discarded, as they are expected to be positive integers as defined by the SCIM protocol.
The solution to this issue involves adding a new route handler to the SCIMMYRouters stack to cast the startIndex and count parameters to integers. Casting should only occur for each parameter on condition that they are defined, their value is a string, and that the string is a valid integer when it has been cast.
In the interim the new route handler method (or at least a version compatible with TypeScript) will be as follows, and can safely be inserted in the chain where you call app.use, just prior to where you instantiate the SCIMMYRouters class:
(req, res, next) => {
    const {query} = req as any;

    // Cast pagination query parameters from strings to numbers...
    for (let param of ["startIndex", "count"]) {
        // ...but only if they were defined, were strings, and are valid as numbers
        if (!!query[param] && typeof query[param] === "string" && !Number.isNaN(+query[param])) {
            query[param] = +query[param];
        }
    }

    next();
}

Thanks,
Sam

Hi @always-akshat,
I've added the new route handler to the SCIMMYRouters stack and published v1.0.1 to NPM including the change, which should resolve the issue.
Thanks,
Sam


hop-node: handle rpc errors when checking if recipient is receivable

Handles non-revert errors in getIsRecipientReceivable().
Handles #336

@miguelmota back to you

@shanefontaine LGTM :+1:


Error

node:events:505
throw er; // Unhandled 'error' event
^
Error: [Poru Connection] you have to Provide guildId

Fixed

when i run bot i have a problems
`node:events:505
throw er; // Unhandled 'error' event
^
TypeError: Cannot read properties of undefined (reading 'get')
at module.exports.run (D:\Downloads\poru-example-main_2\poru-example-main\events\interactionCreate.js:5:34)and i changedconst command = client.slash.get(interaction.commandName);in interactionCreate.js toconst command = client.commands.get(interaction.commandName); the error has been fixed but it appears 1 more error that isconst resolve = await client.poru.resolve(args.join(' '));
^
TypeError: Cannot read properties of undefined (reading 'join')
at Object.run (D:\Downloads\poru-example-main_2\poru-example-main\commands\Music\play.js:15:52)
at module.exports.run (D:\Downloads\poru-example-main_2\poru-example-main\events\interactionCreate.js:35:15)`

Again fixed

you forger change slashCommands in handler/slash.js to slash :v

D:\Downloads\poru-example-main_3\poru-example-main\events\voiceStateUpdate.js:5
if (!newVoice.guild.me.voice.channel) {
-------------------------^
TypeError: Cannot read properties of undefined (reading 'voice')
:v

Try now we fixed all issues


UX pull-from-upstream

Description
I got a PR for pull-from-upstream
https://src.fedoraproject.org/rpms/python-ibm-cloud-sdk-core/pull-request/5
and there is a comment
Logs and details of the syncing: Packit dashboard
when I open the link to dashboard I see
Status
rawhide with green check mark
My initial impression is "the scratch/copr build passed", but this is status of import to dist-git fork. The build itself failed.
Please change the title "Status" to "Dist-git Import Status".
Benefit
user is not confused
Importance
No response
Workaround

[X] There is an existing workaround that can be used until this feature is implemented.

Participation

[ ] I am willing to submit a pull request for this issue. (Packit team is happy to help!)

Fixed by #382


ReferenceError: URL is not defined (webtorrent-cli)

bashflix "westworld s03e01 1080p" en

UNEXPECTED ERROR: If this is a bug in WebTorrent, report it!
OPEN AN ISSUE: https://github.com/webtorrent/webtorrent-cli/issues

DEBUG INFO: webtorrent-cli 3.0.5, webtorrent 0.108.1, node v8.17.0, linux x64, exit 1
/home/user/npm/lib/node_modules/webtorrent-cli/node_modules/webtorrent/lib/server.js:79
    const pathname = new URL(req.url, 'http://example.com').pathname
                     ^

ReferenceError: URL is not defined
    at Server.onRequest (/home/user/npm/lib/node_modules/webtorrent-cli/node_modules/webtorrent/lib/server.js:79:22)
    at emitTwo (events.js:126:13)
    at Server.emit (events.js:214:7)
    at parserOnIncoming (_http_server.js:660:12)
    at HTTPParser.parserOnHeadersComplete (_http_common.js:119:17)

https://github.com/webtorrent/webtorrent-cli/issues/117
Upgrading Node v10 LTS worked.
I also had to set PATH=$HOME/npm/bin:$PATH in $HOME/.bashrc


Revert "DOTCOM-118347" as it is not verified and has issues

Revert "DOTCOM-118347" as it is not verified and has issues

Verified the revert pr  :
https://revert-274-dotcom-118347--cc--adobecom.hlx.page/products/premiere-rush

https://revert-274-dotcom-118347--cc--adobecom.hlx.page/creativecloud/business/enterprise/design-to-development-workflow


Update global.json so .Net Core example builds from command line

@sbohlen
This fixes the problem with "dotnet restore" and "dotnet build" when I run it on my local machine.  Hopefully it will address yours as well.
Thanks,
Brant

Thanks -- I tested and this does indeed resolve it for me on my local system as well.  Nice catch to add the paths to the global.json.
Its frustratingly inconsistent that this was required for dotnet to pick up the projects in /example/ but not required for it to pick up the projects in /src/.   I theorize that this is indeed b/c the projects are located outside the /examples/ folder hierarchy (where the examples .sln file is located), but its a bit of a bizarre inconsistency that dotnet restore was happy to find the projects without the explicit declaration of the /src/ folder in project.json.
Its a bit of a sad commentary on the overall state of the almost criminal (and ultimately adoption-limiting) lack of documentation around all-things-.NET-Core that this seems to be the entire extent of the documentation around global.json that can be found anywhere other than years-outdated blog posts.  But I guess such is  just the sorry state of how we as an ecosystem have completely acquiesced to the steady degradation of the meaning of 'done' for so long that "builds without error" has now literally become almost the only requirement for us to accept a formal "release" of an effort like .NET Core :(
In any case, enough of my soapbox :)  I'll merge this and then add a call in the build script to invoke dotnet restore from the root of the entire repo at the same we're manually invoking nuget.exe to restore the non-.NET Core packages that might be needed for build.
Thanks for taking the time to dig into this for us!


Update Prometheus helm charts

Add support for pod update strategy due to configmap changes, and tolerations for node-exporter
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve

/lgtm


Automatic error report from BioJulia/GenomicFeatures.jl

[err]
Repo: BioJulia/GenomicFeatures.jl
Run URL: https://github.com/BioJulia/GenomicFeatures.jl/actions/runs/91463436
Image ID: sha256:4243bc6e6e3949ce7db921d21b64b0448307c021b8e45906f47d200b5491e23e
Stacktrace:
Traceback (most recent call last):
  File "/root/tagbot/action/__main__.py", line 55, in <module>
    versions = repo.new_versions()
  File "/root/tagbot/action/repo.py", line 249, in new_versions
    old = self._versions(min_age=self._lookback)
  File "/root/tagbot/action/repo.py", line 181, in _versions
    kwargs["ref"] = commit.commit.sha
  File "/usr/local/lib/python3.8/site-packages/github/GitCommit.py", line 91, in sha
    self._completeIfNotSet(self._sha)
  File "/usr/local/lib/python3.8/site-packages/github/GithubObject.py", line 299, in _completeIfNotSet
    self._completeIfNeeded()
  File "/usr/local/lib/python3.8/site-packages/github/GithubObject.py", line 303, in _completeIfNeeded
    self.__complete()
  File "/usr/local/lib/python3.8/site-packages/github/GithubObject.py", line 310, in __complete
    headers, data = self._requester.requestJsonAndCheck("GET", self._url.value)
  File "/usr/local/lib/python3.8/site-packages/github/Requester.py", line 317, in requestJsonAndCheck
    return self.__check(
  File "/usr/local/lib/python3.8/site-packages/github/Requester.py", line 342, in __check
    raise self.__createException(status, responseHeaders, output)
github.GithubException.BadCredentialsException: 401 {"message": "Bad credentials", "documentation_url": "https://developer.github.com/v3"}

#140


scheduler: use high priority for the hot region related operators

What problem does this PR solve?
Hot region related operators should be the high priority.
What is changed and how it works?
This PR does the thing mentioned above.
Check List
Tests

Unit test

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@c0c07dc). Click here to learn what that means.
The diff coverage is 55.55%.

@@           Coverage Diff            @@
##             master   #1492   +/-   ##
========================================
  Coverage          ?   67.3%
========================================
  Files             ?     158
  Lines             ?   15465
  Branches          ?       0
========================================
  Hits              ?   10409
  Misses            ?    4104
  Partials          ?     952

Impacted Files
Coverage Δ

server/config.go
82.35% <100%> (ø)

server/schedulers/hot_region.go
76.83% <50%> (ø)

Continue to review full report at Codecov.

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


What is the code to make popsplits easier?

HI can anybody please help me to make popsplits easier thank you :)

Please look through the other issues as there is no point repeating this the 100th time

Fantasy

@koda Change your config to this:
`# MultiOgar configurations file
Lines starting with number sign (#) are comments
[NOTE]
MultiOgar uses cell size instead of cell mass to improve performance!
In order to get the cell size from mass value, you need to calculate using this formula:
size = SQRT( mass * 100 )

For example, to set start mass = 43:
size = SQRT( 43 * 100 ) = SQRT( 4300 ) = 65.57
Set playerStartSize = 66

Also, you can use the following syntax to specify mass:
playerStartSize = massToSize(43)
It will be automatically converted to 66
[LOGGING]
logVerbosity: Console log level (0=NONE; 1=FATAL; 2=ERROR; 3=WARN; 4=INFO; 5=DEBUG)
logFileVerbosity: File log level
logVerbosity = 4
logFileVerbosity = 5
[SERVER]
serverTimeout: Seconds to keep connection alive for non-responding client
serverWsModule: WebSocket module: 'ws' or 'uws' (install npm package before using uws)
serverPort: Server port which will be used to listen for incoming connections
serverBind: Server network interface which will be used to listen for incoming connections (<IP_ADDRESS> for all IPv4 interfaces)
serverTracker: Set to 1 if you want to show your server on the tracker http://ogar.mivabe.nl/master (check that your server port is opened for external connections before setting it to 1)
serverGamemode: 0 = FFA, 1 = Teams, 2 = Experimental, 3 = Rainbow, 4 = Last Man Standing
serverBots: Number of player bots to spawn (Experimental)
serverViewBase: Base view distance of players. Warning: high values may cause lag! Min value is 1920x1080
serverMinScale: Min scale for player (low value leads to lags due to large visible area for big cell)
serverSpectatorScale: Scale (field of view) used for free roam spectators (low value leads to lags, vanilla=0.4, old vanilla=0.25)
serverStatsPort: Port for the stats server. Having a negative number will disable the stats server.
serverStatsUpdate: Update interval of server stats in seconds
serverMaxLB: Controls the maximum players displayed on the leaderboard.
serverChat: Allows the usage of server chat. 0 = no chat, 1 = use chat.
serverName: Server name, for example "My great server"
serverWelcome1: First server welcome message
serverWelcome2: Second server welcome message (optional, for info, etc)
serverTimeout = 300
serverWsModule = "ws"
serverMaxConnections = 128
serverPort = 443
serverBind = "<IP_ADDRESS>"
serverTracker = 0
serverGamemode = 0
serverBots = 0
serverViewBaseX = 1920
serverViewBaseY = 1080
serverMinScale = 0.15
serverSpectatorScale = 0.4
serverStatsPort = 88
serverStatsUpdate = 60
[CLIENT]
serverMaxLB = 10
serverChat = 1
serverChatAscii = 1
serverName = "MultiOgar-Edited #1"
serverWelcome1 = "Welcome to MultiOgar-Edited!"
serverWelcome2 = ""
[ANTI-BOT]
serverIpLimit: Controls the maximum connections from single IP (use 0 to disable)
serverMinionIgnoreTime: minion detection disable time on server startup [seconds]
serverMinionThreshold: max connections within serverMinionInterval time period, which will not be marked as minion
serverMinionInterval: minion detection interval [milliseconds]
serverScrambleLevel: Toggles scrambling of coordinates. 0 = No scrambling, 1 = lightweight scrambling. 2 = full scrambling (also known as scramble minimap), 3 - high level scrambling (no border)
playerBotGrow: Cells greater than 625 mass cannot grow from cells under 17 mass (set to 1 to disable)
serverIpLimit = 4
serverMinionIgnoreTime = 30
serverMinionThreshold = 10
serverMinionInterval = 1000
serverScrambleLevel = 0
playerBotGrow = 0
[BORDER]
Border size (vanilla 14142.135623730952)
borderWidth = 14142.135623730952
borderHeight = 14142.135623730952
[FOODS]
Each interval is 1 tick (40 ms)
foodMinSize: vanilla 10 (mass = 10*10/100 = 1)
foodMaxSize: vanilla 20 (mass = 20*20/100 = 4)
foodMinSize = 10
foodMaxSize = 20
foodMinAmount = 1000
foodMaxAmount = 2000
foodSpawnAmount = 30
foodMassGrow = 1
spawnInterval = 20
[VIRUSES]
virusMinSize: vanilla 100 (mass = 100*100/100 = 100)
virusMaxSize: vanilla 140 (mass = 140*140/100 = 196)
virusMinSize = 100
virusMaxSize = 140
virusMinAmount = 50
virusMaxAmount = 100
[EJECTED MASS]
ejectSize: vanilla 37 (mass = 37*37/100 = 13.69)
ejectSizeLoss: Eject size which will be substracted from player cell (vanilla 43?)
ejectCooldown: Tick count until a player can eject mass again (1 tick = 40 ms)
ejectSpawnPercent: Chance for a player to spawn from ejected mass. 0.5 = 50% (set to 0 to disable)
ejectSize = 38
ejectSizeLoss = 43
ejectCooldown = 3
ejectSpawnPercent = 0.5
[PLAYERS]
Reminder: MultiOgar uses cell size instead of mass!
playerStartMass replaced with playerStartSize

playerMinSize: vanilla 32 (mass = 32*32/100 = 10.24)
playerMaxSize: vanilla 1500 (mass = 1500*1500/100 = 22500)
playerMinSplitSize: vanilla 60 (mass = 60*60/100 = 36)
playerStartSize: Start size of the player cell (mass = 32*32/100 = 10.24)
playerSpeed: Player speed multiplier (1=normal speed, 2=twice faster)
playerRecombineTime: Base time in seconds before a cell is allowed to recombine
playerDecayRate: Amount of size lost per second
playerDisconnectTime: Time in seconds before a disconnected player's cell is removed (Set to -1 to never remove)
playerMinSize = 66
playerMaxSize = 2500
playerMinSplitSize = 60
playerStartSize = 66
playerMaxCells = 512
playerSpeed = 1
playerDecayRate = .002
playerRecombineTime = 30
playerMaxNickLength = 15
playerDisconnectTime = 60
[MINIONS]
Custom minion settings
minionStartSize: Start size of minions (mass = 32*32/100 = 10.24)
minionMaxStartSize: Maximum value of random start size for minions (set value higher than minionStartSize to enable)
disableERTP: Whether or not to disable ERTP controls for minions. (must use ERTPcontrol script in /scripts) (Set to 0 to enable)
disableQ: Whether or not to disable Q controls for minions. (Set 0 to enable)
serverMinions: Amount of minions each player gets once they spawn
defaultName: Default name for all minions if name is not specified using command (put  before the name for random skins!)
collectPellets: Enable collect pellets mode for minions. To use, use the ERTPcontrol script and press "P"
minionStartSize = 64
minionMaxStartSize = 32
disableERTP = 0
disableQ = 1
serverMinions = 0
defaultName = "minion"
collectPellets = 1
[LAST MAN STANDING]
When it starts/ends is decided randomly just like vanilla, based on the values below
lastManStandingShortest: Shortest amount of time possible before LMS happens in minutes
lastManStandingLongest: Longest amount of time possible before LMS happens in minutes
lastManStandingKickShortest: Shortest amount of minutes till kicking time
lastManStandingKickLongest: Longest amount of minutes till kicking time
lastManStandingShortest = 60
lastManStandingLongest = 120
lastManStandingKickShortest = 30
lastManStandingKickLongest = 60
`

Now you 360 NO SCOPE HAX POPSPLIT EVERYONE (NOTCLICKBAIT)

if you want 16 split back use OgarUl

wtf is this


proxy_feedback_fix

proxy feedback was (incorrectly) loading feedback after the calculation of the quantile cutoffs
does not affect output in a very noticeable way, but logically this is the correct thing to do

LGTM


render_form.html & object_create hidden field printing on html

Environment

Nautobot version (Docker tag too if applicable): 1.6
Python version: 3.11
Database platform, version: psql
Middleware(s):

Steps to Reproduce

Create model
Create model from NautobotModelForm
Do not create a template
Add hidden_fields = ["_custom_field_data"]

Expected Behavior
field to be hidden

Observed Behavior
field is show, and get random printouts of the hidden_field data

I think this is because of
https://github.com/nautobot/nautobot/blob/1d372e4040a0a4d6f95d688843a76b4194283bf1/nautobot/core/templates/utilities/render_form.html#L2
and
https://github.com/nautobot/nautobot/blob/1d372e4040a0a4d6f95d688843a76b4194283bf1/nautobot/core/templates/generic/object_create.html#L8-L10

This feels like a misuse/misunderstanding of the Forms API - normally form.hidden_fields() is a method which automatically returns a list of the fields for which is_hidden = True. Overriding it to be a static list of strings seems incorrect to me. https://docs.djangoproject.com/en/3.2/topics/forms/#looping-over-hidden-and-visible-fields

ok, thanks for your explanation!!


Add TypeDoc generation to docs site

Similar to docs sites for Misk, OkHttp, Barber
Use TypeDoc and this plugin to output to Markdown: https://github.com/tgreyuk/typedoc-plugin-markdown

https://typedoc.org/


bump beorn7/perks v1.0.1

full diff: https://github.com/beorn7/perks/compare/e7f67b54abbeac9c40a31de0f81159e4cafebd6a...v1.0.1

Add go module support
Create v1.0.0 (to play better with go modules)
Lower Go requirement in go.mod

ping @dperny ptal

LT (Look Taken)


chore: version info in Makefile

we can add a script to check the version when we release new version.
here is an example of APISIX: https://github.com/apache/apisix/blob/master/utils/check-version.sh

we can add a script to check the version when we release new version.
here is an example of APISIX: https://github.com/apache/apisix/blob/master/utils/check-version.sh

@membphis OK, will check it out.

@membphis OK, will check it out.


Support straight line dial for angle setting

Use the code from the Inchworm project.

Need to refactor Inchworm code first.

2.13.0 supports this feature now


bindgen doesn't always generate accessors for bitfields

https://gist.github.com/db48x/ac5185816f1b921bb8ca804883165e17
No particular arguments needed.
I expected there to be an impl glyph_row with accessor methods for the bitfield in this struct.

Actually, I made a slight error. I had an old version of bindgen installed, and with the new one this testcase does not fail. It does still fail on the full code base, but just not on this partially-reduced testcase.


runtime: document MemStats better

The current runtime.MemStats documentation is terse and impenetrable. Questions about the meanings of these fields come up not infrequently. We should improve its documentation so that it actually explains what the fields mean as well as enough of the allocation model to understand their meanings and apply them to debugging.
/cc @RLH @hyangah

additionally, would be nice if the documentation explains how they relate (or not relate) to pprof heap profile result.

one example among many: from looking through mheap.go, it looks like none of the counters are decremented when memory is released to the system. Specifically, HeapIdle looks like it really should, and HeapSys may or may not depending on whether it's supposed to be "total memory obtained from the system", or "current mem ...".

Postponing to 1.8.

additionally, would be nice if the documentation explains how they relate (or not relate) to pprof heap profile result.

I'm not sure where to put this that would make sense and people would see it. We do document in runtime/pprof that profiles are as of the most recently completed GC. I've added a blurb to ReadMemStats to clarify that it's instantaneous and to contrast it with profiles, but I don't know if it'll do any good.


fontawesome version used?

Is this implemented with fontawesome 5+ ?

I assume this is version 4.7.0 based on the file structure, you can find it here.
https://fontawesome.com/v4.7.0/get-started/
I'll be honest though, I have yet to even get this solution working. I'm working on it as well. :)

Oh. The nativescript-fonticon is working?

I couldn't get it to work in the current version of NativeScript Vue. This link here is the only thing I can find that works.
https://www.gitmemory.com/issue/NathanWalker/nativescript-fonticon/14/493559957
incase the link doesn't work...
Starting from scratch. .. From Official Guide
cd ~
vue init nativescript-vue/vue-cli-template delete_me
? Project name delete_me
? Project description A native application built with NativeScript-Vue
? Application name NativeScript-Vue Application
? Unique application identifier org.nativescript.application
? Project version 1.0.0
? Author
? License MIT
? Select the programming language javascript
? Select a preset (more coming soon) Simple
? Install vuex? (state management) No
? Install vue-devtools? No
? Color scheme none
cd delete_me
npm install
Then I installed nativescript-fonticon Official guide
npm install nativescript-fonticon --save
Then I visited the page Hosting Font Awesome Yourself and downloaded the zip.
Extracted, I copied webfonts/fa-solid-900.ttf into my project's folder app/fonts. Then I renamed as Font Awesome Free 5 Solid.ttf, because on IOS font file name must match font full name. And this is is how Apple's Font Book identifies my font, it's the full name of the font.
I then copied css/fontawesome.css into my project as app/fontawesome.css.
I modified app/components/app.vue as follows
<template>
    <Page>
        <GridLayout columns="*" rows="*">
            <Label class="message fa" text.decode="" col="0" row="0"/>
        </GridLayout>
    </Page>
</template>

I edit my app.scss file as follows
@import 'fontawesome.css';

.fa,
.fas {
  font-family: "Font Awesome Free 5 Solid";
}

tns debug ios or tns debug android

I'm not a big fan of this solution because of the text.decode and using unicode... but I don't know how else to fix it. I did notice the other ways work, however, only when I close the app and reopen it. It's very weird.

Yeah. Thanks for the heads up. Maybe a workaround for the text.decoode and unicode is to map it.

Anyways the version is answered. Closing this ticket.


fix: use a proper endpoint for DirectPath tests

Hi @ko3a4ok: Just had one question. Why are we setting the endpoint to wrenchworks-nonprod? Is it because this endpoint receives SpanFE releases early, and we would want to catch issues early on in the release cycle?

Hi @ko3a4ok: Just had one question. Why are we setting the endpoint to wrenchworks-nonprod? Is it because this endpoint receives SpanFE releases early, and we would want to catch issues early on in the release cycle?

@rajatbhatta this is a canary endpoint for prod SpanFE servers. It receives the binary release earlier than the rest of prod Spanner frontend servers. We're using a different set of probers to detect any regressions for DirectPath on the server side. This endpoint(wrenchworks-nonprod) will help us to detect regressions on the client side(Spanner lib, or grpc, rls, xds etc). So, technically, we can use any Spanner endpoint. But spanner.googleapis.com isn't available publicly with DirectPath, but wrenchworks-nonprod.googleapis.com has been setup and tested with DirectPath for a while

Hi @ko3a4ok: Just had one question. Why are we setting the endpoint to wrenchworks-nonprod? Is it because this endpoint receives SpanFE releases early, and we would want to catch issues early on in the release cycle?

@rajatbhatta this is a canary endpoint for prod SpanFE servers. It receives the binary release earlier than the rest of prod Spanner frontend servers. We're using a different set of probers to detect any regressions for DirectPath on the server side. This endpoint(wrenchworks-nonprod) will help us to detect regressions on the client side(Spanner lib, or grpc, rls, xds etc). So, technically, we can use any Spanner endpoint. But spanner.googleapis.com isn't available publicly with DirectPath, but wrenchworks-nonprod.googleapis.com has been setup and tested with DirectPath for a while

Thanks for clarifying! LGTM.


Pattern.quote input strings in PatternMatchingCommandElement

Some input strings can cause PatternSyntaxException's to be thrown when compiling the regex pattern due to them containing certain characters.
For example, compiling the user input for a blockstate minecraft:stone[ fails due to the open bracket: log snippet
Pattern.quote()'ing the input string resolves this in my tests.

Wrapping the input in Pattern.quote defeats the whole point of the PatternMatchingCommandElement which is to allow matching results by regex. A better solution would be to try to parse the input as regex, and only if that fails Pattern.quote the input and parse the quoted input -- that way a valid regex can still be interpreted as a regex.

The problem arises in edge cases when a valid regex is also a valid literal, but the regex would give a different answer. Taking the example above with block states, one example is minecraft:stone[variant=granite]. Trying to parse it as a regex means that the user in question can't get the entry in question unless they know the argument is a regex and know to escape the first [.
Worse, let's consider minecraft:stone[variant=smooth_granite]. Again - this is a valid regex, but I imagine it will match (after addition of the initial caret), minecraft:stone_slab because of the underscore - and would require a user to know that the argument is a regex and that they again, have to escape the first [. It might match other things, right now, just working from the top of my head!
My concern is that, given the above, most server owners do not expect that the argument parses like this and getting a literal should be easier than inputting the regex. I don't think we can expect players to have to catch these edge cases themselves, telling them to type in minecraft:stone\[variant=smooth_granite\] in order to avoid getting stone steps. The majority of server owners simply expect that they can put in the start of some ID, or name, and that it'll match the literal.
I'm honestly not sure how to solve this in the best way. My initial thoughts were to parse the literal first, then parse the regex if that turned up nothing, and then allow for an r: token at the beginning of the argument to indicate you wish to parse a regex straight off the bat. It's probably not the best way, but parsing the regex first when many players (and developers) will not expect the argument to be a regex (or know what a regex is) is just going to end up in confusion.

How about something like this:
private static Pattern getFormattedPattern(String input) {
    String literal = ".*?" + Pattern.quote(input) + ".*?";

    if (!input.startsWith("^")) {
        input = "^" + input;
    }

    try {
        return Pattern.compile(input + "|" + literal, Pattern.CASE_INSENSITIVE);
    } catch (PatternSyntaxException e) {
        return Pattern.compile(literal, Pattern.CASE_INSENSITIVE);
    }
}

So if the input is valid regex, match using the expression or by finding the literal somewhere within the string.
Otherwise only match if the literal is somewhere within the string.

The problem with that is that you aren't prioritising one over the other, which means you get the results from the regex and the literal. Like my previous example above, take an argument that selects block states. Again, let's select minecraft:stone[variant=smooth_granite], that'll get us this block as expected (from the literal), and also all the minecraft:stone_slab block state variants (from the regex) - probably not expected in this case.
I also don't think being able to select the literal from anywhere in the string is a particularly good idea. The expectation is currently that whatever you type into the argument forms the start of the string, we should keep it that way.
This issue is more complex than it is on the surface, because we're moving into the realms of potentially breaking the current behaviour - however unexpected it might be for some. Currently, the argument is set up to accept a regex only, but ideally, I think we should be doing the simpler check of comparing literal strings by default, and optionally turning on regex (somehow) for those that need/want it.

If the unformatted string matches an element exactly then only that result is returned:
https://github.com/SpongePowered/SpongeAPI/blob/bleeding/src/main/java/org/spongepowered/api/command/args/PatternMatchingCommandElement.java#L58
I must've been stuck tab-completing with vanilla commands for too long, thought that was the norm in Sponge as well.
Maybe the CommandElement for CatalogTypes just needs to not extend this class and handle parsing/tab-completing itself.

I had missed that for exact matches, good point, thanks. It certainly allays most of my concerns - I should have tested it, I was mostly commenting from work!

I must've been stuck tab-completing with vanilla commands for too long, thought that was the norm in Sponge as well.

Not with this argument type, as it currently always anchors the pattern to the start, and I think that needs to continue.
For the most part, I think extending this argument type for catalog types is OK because I see why regex can be useful, it's mostly block states that cause the issue as they contain square brackets.

I'm not sure about the regex thing at all. First of all most players habe no clue about it especially its syntax requirements.
Lets disassemble it a bit:
Who would type something like .*stone.*\[variant=mossy\] in chat just to find a mossy cobblestone wall? I hope nobody.
If i use skele i would like to get skeleton, wither skeleton and skeleton horse. Dont just skip the wither because it doesnt start with skeleton.
If i use variant=stone, direction=NORTH i would like to also find entries where the order is reversed or there is no space in between both.
Regex can DDos your server.
Can somebody give me a usecase where a regex is useful for players to specify a single element/value?

Essentials on Bukkit had this behavior, and it was confusing for some users, others relied entirely upon it.
e.g. banning a user that's currently online, but has a hard to type username that ends in 64? /ban *64
but this was also able to target multiple people simultaneously.
Noting that this was pre selectors, nowadays I think you would struggle to find someone who expects a command to affect multiple targets without explicitly targeting them using some form of selector.

Just as a reminder, this is blocked pending our 1.13 update.

Closing this PR as the Commands Re-write PR will change all of this. Regardless, I want to thank @dags- for his contribution here.


Deploy

Prepare and deploy to public (website & on-chain):

Set up hosting for front end on Vercel
Update contract and web3 to point to Polygon
Deploy to polygon mumbai and ensure functionality
Deploy to polygon mainnet

Testnet deployment on Ropsten.
@TODO complete changes for polygon deployment


Attendance Count Breakdown for Training Events

Context: When entering attendance for instructor training events I often use the attendance number to confirm all trainees were added. However, I have to count the individual tasks to verify those recorded as an open seat or under a membership.
Current Status: Currently the attendance field shows the total number of learners for the event and a question mark icon. Hovering the mouse over the question mark icon reveals a pop up that shows a breakdown of the total attendance number. The current breakdown includes the number of Manual entered attendance and counted learner tasks (see screenshot)

Question: What is the purpose of the manual entered attendance? For example, if the event total was 22 (Manual entered attendance: 0, Learner Tasks: 22).  We then edit the event and add 5 into the manual attendance field and then submit those changes. The total attendance number does not increase, it remains at 22 but the breakdown shows Manual entered attendance: 5 and Learner Tasks: 22, which should mean the total goes to 27. So this is confusing. I'm also not sure how we would use this information but if we want to keep it, can we update the math so this calculates appropriately?
@sheraaronhurt & @maneesha - What do you think? Do we need manual attendance included in the breakdown?
Ask: What would be helpful right now is to have a breakdown of the attendance number by Open seats and Member Seats.
The breakdown would include:

Total Counted Learner Tasks:
Open Seats:
Member Seats:

@maneesha @sheraaronhurt  - The Member Seat count would include all seats via membership, a-la-carte, or sponsored so maybe we want to come up with a different label  or should we split this up to look like:

Total Counted Learner Tasks:
Open Seats:
Member Seats:
A la Carte Seats:
Sponsored Seats:

Priority: Not Urgent. Feel free to do this in conjunction with the membership infrastructure project if it aligns or push off to later.

The manual attendance is a vestige from when we collected attendance numbers from workshops.  In @sheraaronhurt 's current workflows, we do not collect attendance so that is not really used.  I think we should revisit how that is used with her.
For the count of learner tasks for instructor training events, @Talishask  you are right that this should fit into the membership infrastructure project.  We'll keep this open here to consider as features of that project are implemented.

For counts of learner tasks for instructor training: There are still a few things to work out about memberships, public/inhouse seats, etc.  That part should stay open here for now.
For counts of learner tasks for workshops: The workshop admin team will be considering how we handle attendance. So that should also stay open here for now.

I will be taking this back for discussion with the various teams.


Bot measurements

@andrea-pasquale or @stavros11 could we made the bot measure T1 and RB single qubit apart from assigment fidelity ?

Possible solution: use bot to run runcard and upload report + show link in the message.

Possible solution: use bot to run runcard and upload report + show link in the message.

That's a good plan, I would just still keep the very basic information (platform name, run time, assignment fidelities and potentially T1, T2) in the bot message, so that it is visible without opening the report. I am mainly thinking the lab where we need to change the cluster address to open the reports (due to being in the same network). But for sure we should also append the uploaded link for more details.

Yeah, I can do the message, the upload I'm not so sure about.

For some reason RB routines, maybe due to several connections or something takes way longer than expected on the bot. I have no clue what it could be the solution.

The GitHub bot most likely will need to be reviewed completely, since quite some time has passed.
Let's close this, and reopen a new one whenever someone will need the bot again.


Cannot render email | TypeError: undefined is not an object (evaluating 'Object.hasOwn(Z,"renderToReadableStream")')

Describe the Bug
I am getting this error when sending email from bun@latest.
TypeError: undefined is not an object (evaluating 'Object.hasOwn(Z,"renderToReadableStream")')
at hasOwn (native:1:1)
at /node_modules/@react-email/render/dist/node/index.mjs:99:14
at G (/node_modules/@react-email/render/dist/node/index.mjs:21:24)
at processTicksAndRejections (native:7:39)

My code sample

import * as React from "react";
import { render } from "@react-email/render";
import { Resend } from "resend";
import MedTravelBooking, {
  MedTravelBookingSubject,
  MedtravelProps,
} from "./emails/medtravel-submission";

export async function sendMedtravelEmailToAdmin(
  email: string,
  data: MedtravelProps,
): Promise<any> {
  try {
    await resend.emails.send({
      from: FROM_EMAIL,
      to: email,
      subject: MedTravelBookingSubject,
      html: await render(<MedTravelBooking data={data} />, {
        pretty: true,
      }),
    });
  } catch (error) {
    console.error(error);
  }
  return true;
}

Which package is affected (leave empty if unsure)
@react-email/render
Link to the code that reproduces this issue

To Reproduce

import * as React from "react";
import { render } from "@react-email/render";
import { Resend } from "resend";
import MedTravelBooking, {
  MedTravelBookingSubject,
  MedtravelProps,
} from "./emails/medtravel-submission";

export async function sendMedtravelEmailToAdmin(
  email: string,
  data: MedtravelProps,
): Promise<any> {
  try {
    await resend.emails.send({
      from: FROM_EMAIL,
      to: email,
      subject: MedTravelBookingSubject,
      html: await render(<MedTravelBooking data={data} />, {
        pretty: true,
      }),
    });
  } catch (error) {
    console.error(error);
  }
  return true;
}

Expected Behavior
--
What's your node version? (if relevant)
No response

Have been having the same problem in Bun. Downgrading to 0.0.20 fixed the problem for me. Seems to have been introduced at some point after that.

Tried it myself on a blank project that just plain console logs a simple email rendered and got no error. Can you share a minimal repo that reproduces the error? @amjed-ali-k

I couldn't reproduce it locally either, happened in the oven/bun:2.0.0 docker image for me

+1 on this, getting same error on bun, ubuntu vps

after a bit of research bun add react@canary react-dom@canary seems to fix my issue
Bun Guide

Reproduction of this issue.
@gabrielmfern  You can find the reprod here.
Run bundled version using bun run start and it will throw the error.
https://github.com/amjed-ali-k/react-email-bun-bundler-bug
here is the screenshot

Should be fixed on the latest canaries!

bun add react@canary react-dom@canary

@gabrielmfern this fixed it for me. Tried all canaries from you guys and didn't fix the issue :)

@thisislvca your problem must be something else then, since it did work just fine in the original problem for this issue
here's the repro that it worked for https://github.com/amjed-ali-k/react-email-bun-bundler-bug


WaveForm.js:36 Uncaught TypeError: this.wavesurfer.enableDragSelection is not a function

while using this function ,its throwing error in latest 3.2.0 version,while using 1.1.2 its working
this.wavesurfer.on('ready', () => {
this.wavesurfer.enableDragSelection({ loop: true });
});
is there any change in new updates related this function

i got the function in the latest version after adding regions  plugin.


Accessibility errors cross default backstage pages

My team start using backstage to build an internal application, because the application will be widely used by all developers in my company, I would like it to be accesisble and follow AA standard.
Current I did a accessibility scan with axe tool on backstage default pages, I foud some error appears those errors are critical and serious. Below are a list of errors that I found. I can also provide csv files for full error report if needed.
Catalog page
1 critical: missing aria-label
8 serious: button inside button
Filter component
7 critical:
Missing aria-label
Missing aria parent, menu, menu item
Form label are missing
API doc page
11 critical, icon button missing aria-label
14 serious,

color contrast
Missing aria-label
Button in button

Documentation
1 critical, missing aria-label
2 serious, color contrast, missing aria-label
Create a new component page
Filter error, similar as above
New Service Form
Missing aria-label, 2

Hey :wave: we'd happily accept some of these as contributions, is this something you'd like to take on?

@benjdlambert yes, I would like to contribute this as I am doing accessibility scan.

Assigned! @linzhaoken!

Hi,
We ran some accessibility scanning and testing and found some additional areas for improvement, including:

The SUPPORT button in upper right hand corner of the Software Catalog -- when clicked -- launches a popover with some moderate accessibility concerns:

On smaller screens, the filter FILTERS in the software catalog launch a left side drawer has similar accessibility issues concerning lack of landmarks (or content outside of landmarks)

The OAuthRequestDialog component from @backstage\core-components ( it is created as a Dialogue ) does not usearia-modal:"true", and instead uses aria-hidden:true to hide layers underneath when the dialogue has focus.  This triggers some landmark warnings.

Could changes to address these be included in this work?  Thanks.

@mhaley37 I think this work has gone stale, so maybe you would like to contribute some of these issues? :pray:

HI @benjdlambert, sure!  I discussed this with our team and we'd be happy to contribute to making a more accessible platform.  You can assign to me and I should have some bandwidth soon and can contribute some work.  Thanks

Done!

https://github.com/backstage/backstage/pull/11591 fixes a number of accessibility issues in the catalog and component pages by disabling draggability on table columns.


dividing_into_modules-creating_folders

Created new folders so that there is a division in accordance with the descriptions presented in the file Readme.md
A timer class has been created that will count the time for benchmarks
Fixed Readme.md

The following changes have been made:

added a constructor and destructor to make the class match the RAII
some examples of using the Timer are written in Timer.hpp
written  4 calls of include_directories in CMakeLists.txt

@IzmaylovI please update master and resolve conflicts

Tell me, please, for what reason do conflicts arise?


Make it possible to turn off SSO on certain environments

E.g. turn off Nodes SSO on production. Should this be in nodes-sso or in the admin panel? Not sure.

Not relevant anymore - re-open if needed.


runtime: TestGdbPythonCgo is flaky on linux-mips64le-rtrk builder

2020-03-10T16:25:09-9f74f0a/linux-mips64le-rtrk
2020-02-01T06:01:05-866920a/linux-mips64le-rtrk
2019-11-27T16:41:28-b11d02e/linux-mips64le-rtrk
2019-11-19T02:41:53-2d8c199/linux-mips64le-rtrk
2019-11-15T18:31:19-398f9e1/linux-mips64le-rtrk
2019-11-13T15:52:21-bf49905/linux-mips64le-rtrk
2019-11-12T22:30:48-995ade8/linux-mips64le-rtrk
CC @ianlancetaylor @bogojevic @milanknezevic
##### GOMAXPROCS=2 runtime -cpu=1,2,4 -quick
--- FAIL: TestGdbPythonCgo (6.02s)
    runtime-gdb_test.go:69: gdb version 8.2
    runtime-gdb_test.go:236: gdb output: Loading Go Runtime support.
        Loading Go Runtime support.
        Breakpoint 1 at 0x1200ad4b4: file /tmp/gobuilder-mips64le/tmp/go-build883242937/main.go, line 15.
        Couldn't get registers: No such process.
        BEGIN info goroutines
        Traceback (most recent call last):
          File "/tmp/gobuilder-mips64le/go/src/runtime/runtime-gdb.py", line 442, in invoke
            for ptr in SliceValue(gdb.parse_and_eval("'runtime.allgs'")):
          File "/tmp/gobuilder-mips64le/go/src/runtime/runtime-gdb.py", line 91, in __getitem__
            if i < 0 or i >= self.len:
          File "/tmp/gobuilder-mips64le/go/src/runtime/runtime-gdb.py", line 84, in len
            return int(self.val['len'])
        gdb.MemoryError: Cannot access memory at address 0x120193958
        Error occurred in Python command: Cannot access memory at address 0x120193958
        END
        BEGIN print mapvar
        No symbol "mapvar" in current context.
        END
        BEGIN print strvar
        No symbol "strvar" in current context.
        END
        BEGIN info locals
        No frame selected.
        END
        BEGIN goroutine 1 bt
        Traceback (most recent call last):
          File "/tmp/gobuilder-mips64le/go/src/runtime/runtime-gdb.py", line 536, in invoke
            self.invoke_per_goid(goid, cmd)
          File "/tmp/gobuilder-mips64le/go/src/runtime/runtime-gdb.py", line 539, in invoke_per_goid
            pc, sp = find_goroutine(goid)
          File "/tmp/gobuilder-mips64le/go/src/runtime/runtime-gdb.py", line 467, in find_goroutine
            for ptr in SliceValue(gdb.parse_and_eval("'runtime.allgs'")):
          File "/tmp/gobuilder-mips64le/go/src/runtime/runtime-gdb.py", line 91, in __getitem__
            if i < 0 or i >= self.len:
          File "/tmp/gobuilder-mips64le/go/src/runtime/runtime-gdb.py", line 84, in len
            return int(self.val['len'])
        gdb.MemoryError: Cannot access memory at address 0x120193958
        Error occurred in Python command: Cannot access memory at address 0x120193958
        END
        BEGIN goroutine 2 bt
        Traceback (most recent call last):
          File "/tmp/gobuilder-mips64le/go/src/runtime/runtime-gdb.py", line 536, in invoke
            self.invoke_per_goid(goid, cmd)
          File "/tmp/gobuilder-mips64le/go/src/runtime/runtime-gdb.py", line 539, in invoke_per_goid
            pc, sp = find_goroutine(goid)
          File "/tmp/gobuilder-mips64le/go/src/runtime/runtime-gdb.py", line 467, in find_goroutine
            for ptr in SliceValue(gdb.parse_and_eval("'runtime.allgs'")):
          File "/tmp/gobuilder-mips64le/go/src/runtime/runtime-gdb.py", line 91, in __getitem__
            if i < 0 or i >= self.len:
          File "/tmp/gobuilder-mips64le/go/src/runtime/runtime-gdb.py", line 84, in len
            return int(self.val['len'])
        gdb.MemoryError: Cannot access memory at address 0x120193958
        Error occurred in Python command: Cannot access memory at address 0x120193958
        END
        BEGIN goroutine all bt
        Traceback (most recent call last):
          File "/tmp/gobuilder-mips64le/go/src/runtime/runtime-gdb.py", line 530, in invoke
            for ptr in SliceValue(gdb.parse_and_eval("'runtime.allgs'")):
          File "/tmp/gobuilder-mips64le/go/src/runtime/runtime-gdb.py", line 91, in __getitem__
            if i < 0 or i >= self.len:
          File "/tmp/gobuilder-mips64le/go/src/runtime/runtime-gdb.py", line 84, in len
            return int(self.val['len'])
        gdb.MemoryError: Cannot access memory at address 0x120193958
        Error occurred in Python command: Cannot access memory at address 0x120193958
        END
        Breakpoint 2 at 0x1200ad55c: file /tmp/gobuilder-mips64le/tmp/go-build883242937/main.go, line 20.
        Cannot execute this command while the selected thread is running.
        BEGIN goroutine 1 bt at the end
        Traceback (most recent call last):
          File "/tmp/gobuilder-mips64le/go/src/runtime/runtime-gdb.py", line 536, in invoke
            self.invoke_per_goid(goid, cmd)
          File "/tmp/gobuilder-mips64le/go/src/runtime/runtime-gdb.py", line 539, in invoke_per_goid
            pc, sp = find_goroutine(goid)
          File "/tmp/gobuilder-mips64le/go/src/runtime/runtime-gdb.py", line 467, in find_goroutine
            for ptr in SliceValue(gdb.parse_and_eval("'runtime.allgs'")):
          File "/tmp/gobuilder-mips64le/go/src/runtime/runtime-gdb.py", line 91, in __getitem__
            if i < 0 or i >= self.len:
          File "/tmp/gobuilder-mips64le/go/src/runtime/runtime-gdb.py", line 84, in len
            return int(self.val['len'])
        gdb.MemoryError: Cannot access memory at address 0x120193958
        Error occurred in Python command: Cannot access memory at address 0x120193958
        END

    runtime-gdb_test.go:265: info goroutines failed: Traceback (most recent call last):
          File "/tmp/gobuilder-mips64le/go/src/runtime/runtime-gdb.py", line 442, in invoke
            for ptr in SliceValue(gdb.parse_and_eval("'runtime.allgs'")):
          File "/tmp/gobuilder-mips64le/go/src/runtime/runtime-gdb.py", line 91, in __getitem__
            if i < 0 or i >= self.len:
          File "/tmp/gobuilder-mips64le/go/src/runtime/runtime-gdb.py", line 84, in len
            return int(self.val['len'])
        gdb.MemoryError: Cannot access memory at address 0x120193958
        Error occurred in Python command: Cannot access memory at address 0x120193958
FAIL
FAIL	runtime	177.962s

See also #35743, #20821.

2020-09-15T14:51:32-f1c400a/linux-mips64le-rtrk
2020-08-28T20:01:41-54e18f1/linux-mips64le-rtrk
2020-03-25T20:14:03-e8be350/linux-mips64le-rtrk

greplogs --dashboard -md -l -e '(?ms)FAIL: TestGdbPythonCgo .*Cannot access memory at address' --since=2020-09-17
2022-01-07T18:20:24-ade5488/linux-mips64le-rtrk
2021-12-20T15:13:56-7c94355/linux-mips64le-rtrk
2021-12-07T21:54:30-cf1ec17/linux-mips64le-rtrk
2021-11-13T00:23:16-39bc666/linux-mips64le-rtrk
2021-09-17T21:29:32-3fa7dbe/linux-mips64le-rtrk
2021-05-26T22:43:54-1d5298d/linux-mips64le-rtrk
2021-04-02T01:13:58-41e8a9f/linux-mips64le-rtrk
2021-03-23T05:11:39-e7aa0f9/linux-mips64le-rtrk

This test is still flaking regularly, creating noise in the dashboard and potentially masking other issues.
@bogojevic, @milanknezevic: is this a known bug for the gdb version installed on this builder? Is the gdb binary current, and if not can it be upgraded to see whether the underlying problem has been fixed?

There is already a skip on this builder for mipsle and mips64 due to #18784. 😠


CARBON-15674 fix

Please get this reviewed

All the methods (GET, POST, PUT, DELETE, OPTIONS, HEAD, PATCH) supported by synapse are now included for tenants with this fix.

+1 please proceed.


Fix GroundPrimitive clipping issue

Fixes #3706.
Removes the OBB optimization for better culling. The bounding volume was
pulling the far plane closer to the camera and causing the shadow volume
to be clipped.

I can confirm the issue is fixed.  I also wrote up #3710, which is most likely unrelated.

@bagnell if I'm following you correctly, the bounding volume was smaller than the shadow volume so the shadow volume was getting clipped, right?
I'm fine with this change for now since we have bigger fillrate improvements to make here, but two questions:

Why doesn't depth clamping clamp the clipped volume to the near/far plane?
Wouldn't it be more efficient to just also make the shadow volume smaller instead of making the bounding volume big?  Is that just too ugly?

Why doesn't depth clamping clamp the clipped volume to the near/far plane?

I forgot about the near/far plane clipping. The volume doesn't need to be clipped to the near plane. It should be getting clipped to the far plane though so I'll look into it.

Wouldn't it be more efficient to just also make the shadow volume smaller instead of making the bounding volume big?

Yes, I wish we could. Most likely, we would need support from the terrain server to get the max/min height of the terrain over an area.

Wouldn't it be more efficient to just also make the shadow volume smaller instead of making the bounding volume big?

Yes, I wish we could. Most likely, we would need support from the terrain server to get the max/min height of the terrain over an area.

In the general case, I agree.  In this case, don't we know the max height of the smaller OBB?  Couldn't we use that?

In this case, don't we know the max height of the smaller OBB?

Which OBB? We compute the one for the primitive based on the volume. For the terrain tile, we would have to go through the quadtree. The volume might overlap more than one tile. We can't use the parent tiles either. The min and max height of the tiles are for the quantized mesh so the min/ max heights of the parent aren't guaranteed to bound those of the children.

In the quantized mesh format, at least the one produced by STK Terrain Server and at least when I wrote it, the min/max heights of a tile very intentionally represent the the min/max height of that tile and all its descendants.

That would be great. We might be able to do something client side in the short term to shrink the volumes. I had an offline discussion with Alex where he said that was not the case. Maybe something changed? CC @abwood

Looking at the code, this is not the case (I can see how maybe it was intended).  From what I see, min height and max height are set during refinement, meaning only vertices that are INSERTED into the tile contribute to minheight and max height.  What that means is that if you have a tileset with leaf nodes at level 9, and then add a higher resolution raster data to that tileset into level 12, simplification could cull out the minimum and maximum values that are defined in level 12 by the time those vertices are propagated up to level 9.
I'm not sure how common that case is, but looking at the code we can just make it behave as kevin says (I've been thinking of this since Dan and I spoke).  The only thing that could be impacted would be the precision we have to work with when quantizing the heights, but it shouldn't be that big of a deal.  Will backup with unit tests.

@bagnell is there anything you want to do in the short-term or should we merge this?

@pjcozzi I think we should merge this.


Io -> Lua. Lang change not working, buggy and Inconsistent

I cannot figure this out.
I cannot change from Io to Lua.
Io by the way is not working.
It's inconsistent no matter what I do.
It's also pretty hard to explain.
Io wasn't changing back to Lua even after browser and code reload
So I'm confused to as what to do

write your full code

Not supporting Io any more.


Cloudflare Worker / "client-side" usage?

First of all, thanks for making this library!
I was interested in using it in a Cloudflare Worker, but realized it relies on Node.js' crypto module. Not sure how I could sanely add in support for Web Crypto. https://developers.cloudflare.com/workers/runtime-apis/web-crypto/#constructors
Might create a PR myself if I figure it out in a reasonable amount of time.

Yes, it does use Node's crypto.  But feel free to give it a shot.  If you feel like you are 80% there, let me know and perhaps I can help close the gap.

@Manouchehri - Thought on this a bit.  Where I'm confused is that SNS aways does a POST.  How are you setup that you can handle a POST client side?
Perhaps this is a Cloudflare thing.  I'm used to just good old React / Angular / Solid routing which only handles GET's unless you are doing SSR.
Let me know if you can provide more info, as my curiosity is now peaked. 😄

Sorry, I put "client-side" in quotes, because Cloudflare Workers are still server-side. =P It's just that they use a pretty vanilla V8 runtime, so it's easier to think of compatibility as if it was running "client-side".

OK, cause my next thought was that it is using Node's https library.  Perhaps we might want to create a different library for Cloudfare, using the same principles but with the methods available in Cloudfare Workers.
Feel free to keep working on a PR if you want.  I'm pretty stacked the next couple days, but I might set myself up with a Cloudfare account this weekend and see what's what.

I ended up rewriting most of it, not sure if a PR really makes sense anymore.
https://gist.github.com/Manouchehri/5eac5fdf02b159e479e07c1c90f903a7

Well done.  Yeah, as I thought, this is probably a totally different module.  If you have what you need, glad I could give you the inspiration.  If you want to work together to create a new module so we can have test coverage, documentation, etc.. let me know.

Closing due to being out of scope of this module.  Will perhaps hit it up in the next couple weeks.

@Manouchehri  - TL;DR - If you still have a need, checkout https://github.com/devinstewart/sns-cloudflare-validator/
I had someone else hit me up about Cloudflare.  As you saw in your gist, the "key" is extracting the Public Key from the x509 Certificate.  I didn't want to include any of the huge modules that do that kind of stuff in a module I am maintaining, so I adapted only the needed  code from node-forge, and of course attributed them at the top of the file.
After that was the challenge of testing a Cloudflare Worker (ESM) that makes a fetch call that needs to be intercepted.
Feel free to check it out and give it for a spin.


hide "create repo" option if limit is reaced

we currently show:

and

but it would be better if this menue option do disapear if the limit is reached

Not disappear, disable

I think we need to tell them user somehow why he can't create a repo

That's why I meant disable.
That way, we can display a tooltip

typo in the title: reaced -> reached

Hi, can I take this up?

@Manish-Giri Hi, sure :)

Hi, if this issue if open, can I contribute?

if you need help just tell us here or via matrix/discord :)

@6543 Sorry for the delay, took a while to get caught up with templates in Go!

I've managed to locate and temporarily disable the "New Repository" link as below.

This is currently set to disabled always just to get a screenshot, but to disable it conditionally, the head_navbar template here will need access to the CanCreateRepo data - similar to how the repo/create template here is assigned that info -
https://github.com/go-gitea/gitea/blob/6352114a77cb67e8797f2c8552328f684092c42d/routers/web/repo/repo.go#L179
Any suggestions on where the head_navbar template is normally assigned all its data, so I can look to pass the CanCreateRepo info too?

Does a tooltip also need to be added with a short message on why it's disabled? If so, will a static message like this be sufficient?

If static message is allowed, any preference on the tooltip text? I can add the new text to the locale file then.
Thank you!

@denyskon / @6543 Any thoughts?

Hey @delvh
Can i take this up (cc/ @Manish-Giri -- let me if you are looking forward to work on this)

@hrshkshri sure.

I added my fix here https://github.com/go-gitea/gitea/pull/31818. Let me know if it needs any adjustments.

The problem is more complicated than it looks. There are more logics for "creating repositories in an org"


Minor edits to contributing doc

Minor fixes, edits to contributing doc to make it more relevant.
Signed-off-by: ravisantoshgudimetla<EMAIL_ADDRESS>

Is there a way to skip CI for some PRs? I think changes like this won't need fully blown tests to run.

Hi @ravisantoshgudimetla thanks for the fixes. I added [skip ci] but it does not seem to be working well. I'll look at this soon.


Node: Fix node exports

fixes: #2334

Duplicated naming found between node/src/GlideClient.ts and node/src/GlideClusterClient.ts, including:
enum PubSubChannelModes
interface PubSubSubscriptions
Might need to rename the Cluster one, as they are actually not the same.
Please comment if it's fine to make such change in this PR, or a new PR.