inout primitive arrays

Presume this is on the TODO list :)
I'd like to use
@JavaClass("java.nio.ByteBuffer")
open class JavaNIOByteBuffer: JavaNIOBuffer {
...
  @JavaMethod
  open func get(_ arg0: [Int8], _ arg1: Int32, _ arg2: Int32) -> JavaNIOByteBuffer!
...
}

but the projection of byte[] is not inout.

Feel free to close if known issue.

I'd also be happy with a special case for byte buffers that lives within JavaKit (there is precedence, JNI has one).

Issues are good, please keep em coming but I'd like to ask if you could qualify that they're all about "JavaKit" or "Java2Swift" because the same kinds of things need to be done in jextract -- it'll be easier to know which side of conversions the issue is about this way

Note to self: may be possible to use jniGetArrayRegion(). Essentially I'm just trying to bridge java.nio.ByteBuffer to/from Data.

Ah, it's tricky to implement this in Swift without reimplementing a lot of JavaKit. The options are really:

general support for inout parameters in JavaKit
specific ByteBuffer bridge in JavaKit that uses internal API
application-side Java wrapper function that returns a byte[]

To unblock progress (well, I was unblocked, but reading a byte at a time!), I've opted for the third option for now.


Adding ability to pass session tags (AWS provider)

Is your feature request related to a problem? Please describe.
This is not an actual problem, but it would make it easier to control access to your secrets when you use AWS provider with Secrets manager in an external AWS account. Imagine you have numerous services running on your cluster and each service has a number of secrets stored in Secrets Manager. Currently we have one service account in each namespace that refers to an IAM role that ESO can assume to talk to the external account and retrieve secret values.
Without session tags, you need to create one role for each service in each namespace to control which secrets they can use (using conditions with tags or secrets name). But if you could pass session tags, you could limit access by matching session tags to secrets tags and only have one IAM role for all namespaces to be assumed by ESO.
Describe the solution you'd like
It would be great if you could include session tags in your SecretStore object so it can be passed with when using service account's IAM role. For example:
apiVersion: external-secrets.io/v1beta1
kind: SecretStore
metadata:
  name: aws-secretsmanager
spec:
  provider:
    aws:
      service: SecretsManager
      # define a specific role to limit access
      # to certain secrets.
      # role is a optional field that
      # can be omitted for test purposes
      role: arn:aws:iam::123456789012:role/external-secrets
      region: eu-central-1
      auth:
        auth:
          jwt:
            serviceAccountRef:
            name: sa-serviceb
          sessiontags:
            - Key: "namespace"
              Value: <namespace name>

When you pass session tags with your request, you can modify the IAM role on the target account (where Secrets Manager exists) to only allow access to the secrets that has the same tags as the session tags, you can do the same on Secrets Manager using permission policies.
This approach would eliminate the need to having multiple service account roles and multiple IAM roles on the target account (that can be assumed by SA IAM roles).
Describe alternatives you've considered
Currently we have to create one IRSA (IAM role for service account) for each namespace (roughly maps to each service) and have a corresponding IAM role on the external Secrets Manager account to control access to secrets.
Additional context
Information on using session tags
Secrets manager permission policy
aws:RequestTag/tag-key

Hey, thanks for that detailed write-up. As for the feature this sounds like a valuable addition!
For jwt (IRSA) i don't see how to get this to work because the identity provider (Kubernetes in this case) needs to add specific claims to the jwt (see example here). And AFAIK there's no way to add custom claims to JWTs with standard Kubernetes APIs (the TokenRequest API in particular).
For AssumeRole this is just another parameter to pass into the sdk :+1:

@moolen thank you so much for your response. I believe adding sessions tags to assume role SDK call should do fine, but I'm doing more research just to make sure. Give me a day or two and I will get back to you. This would simplify the process of secrets retrieval a lot when you have tons of services running on your cluster and you want finer access control. Thanks again! :pray:

Sounds good!
Now i see how to get it to work with IRSA: by splitting it into two parts. If i understood you correctly, this would be the approach:

To the AssumeRole call (2) we'll need to add SessionTags and that's it. IMO the sessionTags would fit better under spec.provider.aws.
I was thinking if we should apply sessionTags to all assume role calls (when defined) or if they should apply to specific calls :thinking:. With the existing design it is hard to make it explicit, applying them to all calls is easier.
apiVersion: external-secrets.io/v1beta1
kind: SecretStore
metadata:
  name: aws-secretsmanager
spec:
  provider:
    aws:
      service: SecretsManager
      # assume a role in the target account
      role: arn:aws:iam::{target-account}:role/generic-secret-reader

      # note: a user may define a chain of roles that are assumed in order
      # we can add SessionTags here, too.
      additionalRoles:
      - arn:aws:iam::{example}:role/foo
      - arn:aws:iam::{example}:role/bar

      # Each session tag consists of a key name and an associated value.
      # Session tags are added to __ALL__ assumeRole calls: to both `role` and `additionalRoles`.
      sessionTags:
        - key: namespace
          value: foo

      auth: {} # ...omitted for brevity

That is correct. We don’t need to pass tags to IRSA, rather passing them when we assume a role in the target account. However, the architecture I had on my mind was a bit different than yours. I was thinking of using the role reference with service account. So we create an IRSA role on the target account and refer to it in SA definition. similar to this blog post.
Data flow looks like this:

Which is achievable by using EKS Service Account credentials I believe.
So the service account looks like this:
apiVersion: v1
kind: ServiceAccount
metadata:
  annotations:
    eks.amazonaws.com/role-arn: arn:aws:iam::<target account ID>:role/<target account IRSA name>
  name: my-serviceaccount
  namespace: myapp

And SecretStore definition looks like this:
apiVersion: external-secrets.io/v1beta1
kind: SecretStore
metadata:
  name: secretstore-sample
spec:
  provider:
    aws:
      service: SecretsManager
      region: eu-central-1
      auth:
        jwt:
          serviceAccountRef:
            name: my-serviceaccount
      sessionTags:
        - key: namespace
          value: myapp

Regarding adding tags to all sessions, it might be easier to add transitive tags. This way you can pick which tags are persistent through role chaining. So your service account definition can look like this:
apiVersion: external-secrets.io/v1beta1
kind: SecretStore
metadata:
  name: secretstore-sample
spec:
  provider:
    aws:
      service: SecretsManager
      region: eu-central-1
      auth:
        jwt:
          serviceAccountRef:
            name: my-serviceaccount
      sessionTags:
        - key: namespace
          value: foo
      transitiveTags:
        - namespace

I'm not a golang pro but I assume if we change assume role API call to take both Tags and TransitiveTagKeys (when available) we would be able to tag all sessions without adding tags to each session separately.
    // Optional, you can pass tag key-value pairs to your session. These tags are called session tags.
    Tags []*sts.Tag

    // A list of keys for session tags that you want to set as transitive.
    // If you set a tag key as transitive, the corresponding key and value passes to subsequent sessions in a role chain.
    TransitiveTagKeys []*string

Thank you!

Using only a single IRSA-enabled IAM Role is not going to work, i outlined that above https://github.com/external-secrets/external-secrets/issues/2343#issuecomment-1559924373:

For jwt (IRSA) i don't see how to get this to work because the identity provider (Kubernetes in this case) needs to add specific claims to the jwt (see example here). And AFAIK there's no way to add custom claims to JWTs with standard Kubernetes APIs (the TokenRequest API in particular).

Under the hood we do a sts.AssumeRoleWithWebIdentity call when using the jwt auth method. You can not specify SessionTags in that API call. Instead, the jwt must contain specific claims which are read by AWS to assign session tags. Because we have not enough control over the issued jwt (we can not add custom claims), there is no way to pass session tags with just this single API call.
To make it work we need to have another IAM Role that ESO has to assume (sts.AssumeRole) in order to pass SessionTags.
Good suggestion regarding transitive tags :+1:

My bad, I did not completely understood it when you explained it the first time.
Even with one extra IAM role for ESO, adding session tags would save a lot of time in big environments with a lot of clusters/namespaces when it comes to access control.
Thanks again, and please let me know if there is anything else I can provide to help you implement this feature. 🙏

Honestly, I'm not sure if or when we'll be able to squeeze this in because maintenance and going through PRs already eat up a ton of our time.
I totally want to make this happen, but right now we've got more important stuff on our roadmap (sorry). However, I'll add a label on it for new contributors since it seems like a pretty straightforward task.

I understand. I might take a jab at this and submit a PR myself (if I find some time and manage to find my way around ESO). Thanks again for being responsive and for your help, much appreciated!

@nimaft  if you need any help with the code base, tests, etc, feel free to drop a message on #external-secrets-dev on kubernetes slack; or DM me directly there @gusfcarvalho

@gusfcarvalho Thank you so much man, I will get back to you in a few days once I come up with something. I definitely need help because I'm not a golang guy. Thanks again!


Fix circular reference with Reanimated 3

The Reanimated since version 3 captures entire objects to the worklet's closure, instead of capturing just single object property. However, this can cause problems when some objects contain circular references. To avoid issues, it is highly recommended to only pass objects that are as small as possible to the worklet closure.

Thank you so much @piaskowyk, it fixes this error https://github.com/software-mansion/react-native-reanimated/issues/4177 on react-native-draggable-flatlist


Didn't use gpu even 'torch.cuda.is_available()' returns True when I used enn

I followed https://github.com/drorlab/atom3d/blob/master/examples/lba/enn/README.rst, used
cd atom3d/examples/lba/enn
python train.py --target neglog_aff --load
--prefix lba-id30_cutoff-06_maxnumat-600
--datadir $LMDBDIR --format lmdb
--cgprod-bounded
--radius 6 --maxnum 600
--batch-size 1 --num-epoch 150
my terminal and log file show "Beginning training on CUDA/GPU! Device: 0", but nvidia-smi shows No running processes found.
It happened when I tried the lep example. However, at the same virtual env, I tried https://github.com/drorlab/cormorant, python examples/train_qm9.py. It worked well.

Sorry, it actually works. After several minutes of waiting (patient is needed), I think it is preprocessing the data, then it started to use GPU for training.


Installing a 3rd Party App ( from App Source) with CI/CD

I have a small repo, in it the app has a dependency on a 3rd party App Source App (ForNAV in this case)
The build fails, and its related to the 3rd Party App.
I added the 3rd Party App files (3 of) into the installApp settings and it tried to deploy but fails. Assuming this is maybe because its only the symbols?
So, is it possible, can we get it to download app source apps during the CI/CD stage?

Ah, sorted.
I needed to get the runtime packages from ForNAV (you need to be a partner with a partner license).
Once thats done and i specify the license file secret it all works.


Fix ambiguous column name warning on segment_web_sessions.sql

When using this package, I got an ambiguous column name warning message from dbt_packages/segment/models/sessionization/segment_web_sessions.sql line 64 ["partition by blended_user_id"] and line 73 ["left join agg using (blended_user_id)"]
I believe line 64 can be fixed with "partition by sessions.blended_user_id"
... and line 73 can be fixed by joining with 'on' rather than 'using'  - "left join agg on sessions.blended_user_id = agg.blended_user_id"
Thank you!

Thanks for opening this - https://github.com/fleetio/dbt-segment has adopted this package, so I'd recommend transferring this issue there if it is still a problem for you.


Change to not translate unique names

Same as #23964
An incorrect translation has been made in the localized version by machine translation.
※ Machine translation translates property name
Evidence: https://github.com/MicrosoftDocs/azure-docs.ja-jp/blob/live/articles/azure-monitor/platform/data-sources-collectd.md
In the following files, it was made not to make mistranslation by putting proper names in "`".
https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/role-based-access-control/custom-roles.md
This change(enclose property names by "`") has no negative effect on the English version.
Please accept this change so that property names are not mistranslated in each language in each localized version.
🙏

@changeworld : Thanks for your contribution! The author, @mgoedtel, has been notified to review your proposed change.

#sign-off to accept these required changes.


Live Activity Chart doens't populate as it should

Problem:
The live activity only shows the values when I entered the app.
The data that was backfilled or in between data the openings of the app was in the widget.
Without the simulator/NS it works fine (G7 + Dash instead), but I don't understand why it doesn't display the backfilled data aswell. Because the data is in the app so it should also show in the Live activity right?
Smartphone:

iPhone 15 Pro Max
Apple Watch Ultra 2

Settings:

Simulator Pump
Nightscout CGM Source
Backfilled Glucose from nightscout
Live activities branch Merged with Dev_dependencies branch

@Sjoerd-Bo3 , is this still an issue, or can it be closed?


Use double equals when comparing IDs of different types

When you add a new item using a post, it creates a new item in the collection using a number as the ID by default. However, when you update the item using a put, the default URL parser keeps the URL parameter as a string, which causes the ID matcher in the put method to fail.

Ok, maybe a different solution is in order since it failed the linting because of the double equals, but you get the point.

I signed it!


Invite New Members

As a DAO member or funding member, I want to be  able to invite  other members so  that   we can  grow the DAO.

@falkonprods  We don't have funding member! what you mean by that? we only have voting and non-voting members

Smart contract and frontend work. We don't have a frontend design flow for this yet.


[Framework] Random Number on-chain solution

[ ] Simple on-chain Random Number #771
[ ] VRF on-chain

May the verifiable feature is not required unless we have consensus mechanism?

The transaction needs to be synced to another executor or proposer node, so the execution result must be determinate. Maybe we can put the sequencer's transaction witness data in the TxContext, and sync the transaction and witness data together. #771

ZK-VRF please refer:
https://github.com/zkvrf/zkvrf
https://github.com/jae-cuz/zk-draw

A simple solution:

Let the sequencer generate a random seed and add it to TransactionSequenceInfo.
Include the seed in the data of the sequencer signature.
In the future, we can improve the random seed by zkVRF.

pub struct TransactionSequenceInfo {
    /// The tx order
    pub tx_order: u128,
    /// The tx order signature, it is the signature of the sequencer to commit the tx order.
    pub tx_order_signature: Authenticator,
    /// The tx accumulator root after the tx is append to the accumulator.
    pub tx_accumulator_root: H256,
}

Or can we directly use the tx_order_signature as the random seed?

Is the second issue VRF on-chain needing to be resolved?

Is the second issue VRF on-chain needing to be resolved?

Make this TBD


Added dockerfile for sqlite

Added the dockerfile for sqlite database

Thank you, had a great time working on it


Grid Map Editor menu contains unimplemented options

Godot version: v3.0.6

OS/device including version: Arch Linux

Issue description:

The Grid Map Editor menu (the drop-down menu that appears when you click on the text "Grid Map" in the pane that opens when a GridMap node is selected) contains several options that do not appear to be implemented.
The _menu_option method in "godot/modules/gridmap/grid_map_editor_plugin.cpp" does not appear to implement handlers for the following menu items:

Create Area
Create Exterior Connector
Erase Area

Having menu options that don't do anything is confusing for users; it leads them into a goose chase for features that do not exist. I request that the menu options be removed, until the features they correspond to are implemented.

Fixed in #25406


Negative user experience related to copilot-idle-delay

I have copilot-idle-delay set to 1 second, but completions are frequently offered within milliseconds after I type some characters.  This is distracting and causes me to make typos due to the text on the screen changing near where I'm typing.
From reading the code, this seems to happen because:

copilot-idle-delay is the time between when Emacs becomes idle and a request is sent to the server.

The request is delayed using run-with-idle-timer in copilot--post-command, but once run-with-idle-timer is called, the user has copilot-idle-delay seconds (plus the request/response round-trip time) to continue typing, which happens frequently for me.

When the completion arrives from the server, it is displayed immediately, without regard for whether Emacs is idle or if the buffer has changed since the request was sent.

I would prefer that copilot--show-completion does NOT display the completion if the buffer has changed since the request was sent to the server.  Of course, not everyone would prefer this, so maybe this can be disabled by default unless a user-visible variable is set to non-nil?
I'm currently implementing this with advice on copilot--get-completion that saves the current value of (buffer-modified-tick) in a buffer-local variable.  Then, advice on copilot--show-completion checks whether (buffer-modified-tick) is equal to that variable to know if the buffer has changed since the request was sent. If the buffer has changed, the completion is not shown, otherwise it is.
If you don't want to implement this behavior, my advice works for me, but I thought others might like to opt-in to this behavior. Also, I'm willing to implement this (and submit a pull request) if you'd prefer. Let me know.
Thanks for taking the time to read this.
-- Fran

I confirm that this should be considered a bug. I will fix it later.

A related issue is that point can move between the call to run-with-idle-timer and when the response arrives from the server. I can't find any code in *copilot--post-command-debounce (or the functions called from it) to handle that use case, but I could be wrong. I assume the completion should not be shown if point is not in the same place as when run-with-idle-timer was called.

@fpl9000 Can you verify the fix bcc0407? Though I can't distinguish any difference on my end.
The position of the user cursor is checked to ensure the completion is up-to-date, and after this patch, the doc version is checked instead.

Thanks for the fix, @zerolfx! A quick test shows an issue. To reproduce:

Evaluate (setq copilot-idle-delay 5) to set the idle delay to 5 seconds. This makes the issue easier to reproduce, but it also happens with a shorter delay time.
In an empty buffer with major mode emacs-lisp-mode, type: (defun increment (n). Do NOT press ENTER.
Before 5 seconds passes, move point one character to the left.
Wait for the completion to be shown.
Notice the ) is removed when the completion is shown (though there's an extra ')' at the end of the completion, which may be related. See screenshot below.
Accepting the completion does not restore the missing ).

I re-added the verification of the user cursor in commit 15a698e and it should not be removed in my previous fix.


Pasted HTTP (requestJSON) script needs manual attention

When I pasted the script to a new file, the ¶ characters which are in the stored XML get converted to
"
"

a literal carriage return,
but then the script seem to not replace the CR in this line #74 -- Substitute( $responseHeader ; ":" ; ¶ ) (this is my edited version) and as a result Trim ( GetValue ( $responseHeader ; 2 ) ) then fails

Also line #60 has the calculation commented out which it needs otherwise line #65 fails.

I don't see this, can you attach a screen shot that shows the issue?

@rwu2359 will you check the latest version.  See if this has been resolved for you.

This is fixed in the latest version....
the issue I was getting is in screenshot...

excellent


Feat/metadata schema changes

Opening this as there were some lower-level changes I made to get everything working I wanted to make clear versus just pushing to the current open PR at the smart-invoice repo and details getting lost.
Given that all projectAgreements are pushed to IPFS on every detailsUpdate and milestone addition, it seemed like a a repetition to also catch that with the detailsUpdated event and handler. So the mapping runs through the list, creates an Agreement, and pushes it to the projectAgreement field.
Which is all fine, but the main change is given that each Agreement creation isn't linked to an event there's no way to access block.timestamp or a block time method to mark agreement creation. The queries were also returning all the agreements, but out of creation order. So I added a createdAt field on the frontend with Unix timestamp on update of a projectAgreement. So now the query for projectAgreement can be sorted chronologically by that field.
I made the projectAgreement an array in the schema as well (previously just object) for continuity throughout.
With this change a bunch of other type issues came up as well on the Assemblyscript side of things, which I won't bore everyone with here, but if anyone sees something weird and a cleaner and clearer way through definitely let me know
I think everything is fairly straightforward at this point but I wanted to highlight some of these changes before merging it with the other PR against revamp.
One last detail is that before merging into revamp we should maybe have some plan for dealing with old-schema invoices. A new schema invoice will break the old schema subgraph, and vice versa, and the whole thing will come crashing down if not accounted for in some way.

I added a few comments in the file changes. Overall looks good. I figure for your last point, we'd need to keep the old schema and differentiate the two by blocknumber.


Warning: findDOMNode is deprecated in StrictMode

[x] I'm sure this does not appear in the issue list of the repository

Basic Info

Package Name And Version<EMAIL_ADDRESS>Phone Model And Version: pc chrome dev

What is expected?
Warning: findDOMNode is deprecated in StrictMode. findDOMNode was passed an instance of Transition3 which is inside StrictMode. Instead, add a ref directly to the element you want to reference. Learn more about using refs safely here:xxxx
Steps to reproduce
use DatePicker component and use React.StrictMode

Can you provide a minimalist replay demo @zhangjiahao93

@ChelesteWang
https://github.com/zhangjiahao93/arco-mobile-issue

@zhangjiahao93 Now that we know the problem let's look at how do we solve it

@zhangjiahao93 I've located the problem, and it will be fixed in a later version


Block diagram of go-routines.

Picture can say thousand words. Create a block diagram of go-routines, how the interact with application logic and underlying socket. Mostly it is important to trace the execution path and its exceptional cases.

Duplicate of #3


[GitBook] -> [Others]

GitBook
GitBook is a modern documentation platform where teams can document everything from products to internal knowledge-bases and APIs.
Link: https://www.gitbook.com/
Checklist:

[x] I have performed a self-review of submitted resource and its follows the guidelines of the project.

Not related to design. Closing.


Create ResearchMilestoneSummer2023 branches for each version

I'm thinking that we'll want ResearchMilestone branches to be fixed for 0.616. This'll allow version-specific fixes that'll let us focus on framework/mapping changes. It'll also let us normalize approaches (e.g. in 1.14.1 where I did rotation in a totally different way, but there was probably a similar way to how it was done in 1.15.2).
This will let is move forward on the actual production branches, but still maintain the reference-versions for this research project, and even update it independently if we so choose (if some of those posted bugs get fixed and we just want them in, though I'm thinking this lets us avoid that)

[x] Make ResearchMilestoneSummer2023-1.20.1-0.616 branch
[ ] Make ResearchMilestoneSummer2023-1.19.4-0.616 branch
[ ] Make ResearchMilestoneSummer2023-1.18.2-0.616 branch
[ ] Make ResearchMilestoneSummer2023-1.17.1-0.616 branch
[ ] Make ResearchMilestoneSummer2023-1.16.5-0.616 branch
[ ] Make ResearchMilestoneSummer2023-1.15.2-0.616 branch
[ ] Make ResearchMilestoneSummer2023-1.14.1-0.616 branch

Branch ResearchMilestoneSummer2023 1.20 is out

Branch ResearchMilestonesSummer2023 1.19 is out

Branch ResearchMilestonesSummer2023 1.18 is out

Branch ResearchMilestonesSummer2023 1.16 is out

Branch ResearchMilestonesSummer2023 1.15 is out

Branch ResearchMilestonesSummer2023 1.14 is out


Change checkbox to handle lowercase

Handle case where checkbox x is lowercase from user input. Ex: - [x] text

Thank you for the contribution.


feat: implement crd model and Integrated configuration

implement loading model from crd
migrate model into crd
integrate scattered configuration items into 1 configuration file

LGTM

Don't worry, all the problems you mentioned has been corrected by introducing kubebuilder, which is the content of next PR I am going to raise. It has been finished and you will see it in next pr.


HOTFIX: Only measure in nano when producer metadata refresh is required

We added the metadata wait time in total blocked time (https://github.com/apache/kafka/pull/11805). But we added it in the critical path of send which is called per-record, whereas metadata refresh only happens rarely. This way the cost of time.nanos becomes unnecessarily significant as we call it twice per record.
This PR moves the call to inside the waitOnMetadata callee and only when we do need to wait for a metadata refresh round-trip (i.e. we are indeed blocking).
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

cc @rodesai for a quick look.

Hi @cadonna could you please lmk if I can cherry-pick it to 3.2 as well?

@guozhangwang I do not think we need this hotfix on 3.2 since https://github.com/apache/kafka/pull/11805 is not present on the 3.2 branch.

Ah yes :) my bad.


[Question] dubbo+nacos，gateway not success

Question
The client keeps returning：
c.d.s.ShenyuClientURIExecutorSubscriber : host:<IP_ADDRESS>, port:20888 connection failed, will retry
sync and The registry use nacos .

please describe this question with your shenyu version and your debug log.

please describe this question with your shenyu version and your debug log.

shenyu : 2.4.3
shenyu-admin  config :
`shenyu:
register:
registerType: nacos #http #zookeeper #etcd #nacos #consul
serverLists: nacos:8848 #http://localhost:2379 #localhost:8848
registerType: zookeeper #http #zookeeper #etcd #nacos #consul
serverLists: localhost:2181 #http://localhost:2379 #localhost:8848
props:
  sessionTimeout: 5000
  connectionTimeout: 2000
  checked: true
  zombieCheckTimes: 5
  scheduledTime: 10
  nacosNameSpace: 1c10d748-af86-43b9-8265-75f48748517c

sync:
nacos:
url: nacos:8848
namespace: 1c10d748-af86-43b9-8265-75f48748517c
username: nacos
password: nacosshenyu-bootstrap config : shenyu:
sync:
nacos:
url: nacos:8848
namespace: 1c10d748-af86-43b9-8265-75f48748517c
username: nacos
password: nacosclient  config:shenyu:
register:
registerType: nacos #zookeeper #etcd #nacos #consul
serverLists: nacos:8848 #localhost:2181 #http://localhost:2379 #localhost:8848
props:
username: nacos
password: nacos
nacosNameSpace: 1c10d748-af86-43b9-8265-75f48748517c
client:
dubbo:
props:
contextPath: /dubbo
appName: dubbo
dubbo:
application:
name: test-dubbo-service
registry:
protocol: nacos
address: nacos:8848
protocol:
name: dubbo
port: 20889`
request http://localhost:9195/dubbo/findById?id=666    ， response is：
{
code: -106,
message: "Can not find url, please check your configuration!"
}
the admin is reported successfull.

please check nacos exist service？

if nacos is not exist service please check nacos url

do you try shenyu master? I will try test it.

yes ,same result

I changed the synchronization method to websocket and it was successful

The problem is solved. The reason is that the nacos sync package is not import. The master's bootstrap only has nacos without the import of the sync package. Others are import. this https://shenyu.apache.org/zh/docs/deployment/deployment-quick/  package is the same  question .
        <!-- apache shenyu data sync start use nacos-->
        <dependency>
            <groupId>org.apache.shenyu</groupId>
            <artifactId>shenyu-spring-boot-starter-sync-data-nacos</artifactId>
            <version>${project.version}</version>
        </dependency>

do you want to contribute to shenyu? if yes, please fork and contribute to shenyu

The problem is solved. The reason is that the nacos sync package is not import. The master's bootstrap only has nacos without the import of the sync package. Others are import. this https://shenyu.apache.org/zh/docs/deployment/deployment-quick/ package is the same question .
        <!-- apache shenyu data sync start use nacos-->
        <dependency>
            <groupId>org.apache.shenyu</groupId>
            <artifactId>shenyu-spring-boot-starter-sync-data-nacos</artifactId>
            <version>${project.version}</version>
        </dependency>

do you want to contribute to shenyu? if yes, please fork and contribute to shenyu


add garbage collection for ZenFS

This PR adds GC for ZNS. Here's how it works:

We use the statistics interface added in https://github.com/bzbd/zenfs/pull/6, where we can get what size each file occupies in each zone.
We spawn a ZNSGC task in the background, which works like TTLGC. It polls statistics from ZenFS every 10s.
The task will find all full zones with 50% garbage (by default) and mark files in that zone for GC.

Along with ZNS GC, other features are added.

We added zenfs_gc_ratio option in db_bench command.
We fixed a bug where files may be deleted before closed.

Signed-off-by: Alex Chi<EMAIL_ADDRESS>

ping @levisonchen @mm304321141 for review


Git: Option to Close All working-tree files

There should be an option to close all working-tree files , but leaves the other files open.

/duplicate #18651


oss

Search before asking

[X] I had searched in the issues and found no similar issues.

Question
私有化部署，怎么修改文件存储的总容量大小

不清楚具体是什么问题，具体说明一下？


[fix](inverted index) Fix inverted index for MOR unique table

Proposed changes
Issue Number: close #xxx

allow inverted index for key columns for MOR unique table
allow inverted index without parser for value columns for MOR unique table, and do not push down predicate if it may cause wrong result
disallow inverted index with parser for value columns for MOR unique table, due to MATCH without predicate push down is  very slow.

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall


Rename PECO

I wasn't really sure where to open this, it seems to span multiple trackers.
Rename PECO.
From Chris:
You can fix your github repo just with a one line perl
perl -pi -ne 's@PECO@PBECO@g' *.{obo,owl}
But you will have to sync that with SQL updates in your chado and probably codebase changes.... sorry
and re the alignment
Bill is doing a first pass at aligning every single exposure vocabulary we can get our hands on, including the pombase one, no idea how accurate an automated approach will be but we can show you when it's ready

Changes needed:

[ ] Canto test OBO file (https://github.com/pombase/canto/blob/master/t/data/peco_small.obo) and Canto tests
[ ] Canto configuration
[ ] IDs in the Canto database
[ ] .contig files
[ ] PHAF files
[ ] Website docs, there's one mention of PECO here: https://github.com/pombase/website/blob/master/src/docs/documentation/ontology-term-page.md

@matentzn is also interested in following progress

@kimrutherford, I can do my bits pretty much any time with about a day's notice. I'll claim the P(B)ECO file itself, the .contig files, PHAFs, and documentation. Everything Canto is yours ;)

Now that JaponicusDB is a thing, and they're using FYPO, maybe we should change PECO to FYCO or FYECO instead of PBECO. Neither would clash with anything I see on the OBO Foundry list.
Comments, questions, etc.?

Good plan. I don't know which is best. FYECO  maybe?

All this needs is an executive decision to pick a date and do it. Let's schedule it for shortly after Kim gets back from holiday.

Name your day Kim....

ping
just making sure this gets done soon - @kimrutherford pick a day

I just updated the documentation, since there's only one mention of the conditions ontology, and that's at the end of a sorta-longish page. I don't think it'll hurt anything for it to have the new abbreviation a week or two in advance of the rest.
Let me know if you want me to update the contig and/or PHAF files, and if so, when. Pretty much any time is OK, since it's a quick job.

I've just taken the pombe and japonicus Canto instances offline while I attempt to change "PECO:" to "FYECO:".  Hopefully it will be back in an hour or two.
I've taken an extra backup.  :-)

The pombe Canto is back up now.  japonicus shouldn't be long.  Let me know if you spot any problems with conditions.
The changed PECO to FYECO in the Chado loading code and all of the configuration and data files I can find.  I'll check the nightly load on Sunday morning.

I think it (mostly) worked: http://dev.pombase.kmr.nz/term/FYECO:0000268
There 94 fewer annotations then the previous successful load so I'm going to investigate that before updating the main site.

I think that's OK.  It looks like this session went back into approved status which accounted for most of the 94:
https://curation.pombase.org/pombe/curs/d2fab1f2b453d796
PMID:20838651
I've now updated the main site.

hooray!


Change Websocket interface to return commands

Instead of returning reply with frames, or ok, or stop, we should always return {Commands, State}. This way we can easily add more commands, get rid of "stop" which duplicates the close frame, and simplify the code both for the user and for us. This would also get rid of the annoying reply which really means send.
Current reference docs: https://ninenines.eu/docs/en/cowboy/2.0/manual/cowboy_websocket/

Required for #1054.

Done in 8404b1c908ac890925496ce839e5b2b2b407a6f7. Currently experimental/undocumented. It will most likely be documented as part of the 2.6 release.


Dashboard crashes when new user has no payments

Describe the bug
New user doesn't have any payments, the state for 'payments' in the Payment component is undefined, tries to read the length of 'payments' which leads page to crash and show error.
Very similar to bug #171 but introduced for the dashboard payments due to PR #184.
Severity
Major error, cannot open dashboard page
To Reproduce
Steps to reproduce the behavior:

Create a new user
Go to the dashboard
See error - screenshot attached below
See error

Expected behaviour
User should be able to view their dashboard and see no payments.
Actual behaviour
A clear and concise description of what you actually to happened.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment:

OS: Windows 10
Browser: Chrome

Possible solution:
Apply similar fix as #171 (PR#179)
Additional context
Add any other context about the problem here.

Screenshot here


[TW#12721] Self heat stops ble/wifi

Hi , i have a problem with my ESP32 (thing board from sparkfun) , i put it in a HCI continuos listening for BLE ADV packets , after 2 minutes or so it's still working ( printf and GPIO stuff) but BLE stops recieving packets . at first i was connecting also to wifi as station with BLE Wifi Coexists enabled in meuconfig , after ward i stopped the connecion to wifi and just debugged if the BLE will stops also , and in eather ways it STOPs listening. I putted the module in the FREEZER and every thing works absolutly fine for several hours . the module gets hot ( like 70 degrees or some like that) outside the freezer , and i think its drifting something inside the chip or even the crystal it self ... so please any work around to void poutting my module in the freezer while continiously listening to ble and preferrably always connectec to wifi also .
Thanks

Hi @ahmedjouirou , for what it's worth, the Sparkfun ESP32 Thing doesn't seem to have any heat spreading features. You might want to try the same experiment with a board based on the WROOM-32 module, such as the board that Adafruit is selling. If you're looking for a workaround this might be the most expedient route..

well i tried the ESP32-S module , same problem , it stops after 5 of 7 minutes from receiving ble

It might not be because of heat. #618 when I had CONFIG_SW_COEXIST_ENABLE on, Bluetooth would init but wouldn't receive advertisements. Try increasing your scan interval while keeping your window the same or lower.

@ahmedjouirou , ESP32 can bear high temperature.  I'm agree @FHFS . Could you disable the CONFIG_SW_COEXIST_ENABLE, then report the result？Thanks.

Hi @ahmedjouirou, is there any update? Did the above suggestion help you resolve the issue?


LOAD query not working

Hi,
version: 0.9.6 with PR #99 applied
I currently try to load an external file via LOAD query; although the query seems to succeed, the store seems to be empty:
rdfstore.create(function(err, store) {
  if (err) { /* error handling */ }

  // - load remote RDF document
  //   NOTE: timbl-foaf.ttl is a Turtle version of http://dig.csail.mit.edu/2008/webdav/timbl/foaf.rdf
  store.execute('LOAD <https://kindl.io/sw-examples/timbl-foaf.ttl>', function(success, num_triples) {
  	if (!success) { /* error handling */ }

  	/* success = true */
  	/* num_triples = 211 */
  	store.graph(function(err, graph) { console.log(graph); /* empty */});
  });
});

Did I miss a thing?

store.graph('https://kindl.io/sw-examples/timbl-foaf.ttl', function(err, graph) { /*...*/ }); returns the graph with all loaded triples, so I missed a thing ;-)
Anyhow, according to the SPARQL 1.1 Update spec a SPARQL query LOAD query without an INTO clause should populate the default graph -- it seems that this is not the case here..

              var fileString = app.fs.readFileSync(app.dir + '/rdf/imd-rank-education.nt').toString(); 		rdfstore.create(function(err, store) { 			store.load("text/n3", fileString, "<http://example.org/imd>", function(err, loaded) { 				if (err) console.log(err); 				console.log("triples loaded: ", loaded); /***** triples loaded:  194892 ****/ 				store.registeredGraphs(function(err, res){ 					console.log(res); /**** [ { [String: '<http://example.org/imd>']     interfaceName: 'NamedNode',     attributes: [ 'interfaceName', 'nominalValue' ],     nominalValue: '<http://example.org/imd>' } ] ****/ 					store.graph("http://example.org/imd", function(err, res){ 						if (err) console.log("ERR: " + err); 						console.log(res); /**** { triples: [], duplicates: {}, actions: [], length: 0 } ****/ 					}); 				}); 			}); 		});
Here I tried to load rdf from file, 194892 triples loaded and a namedGraph is also created, but when I tried to retrieve the graph to see its content, the graph has no triples. I also tried to run SELECT query, but it still results in an empty array [].
Can anyone help me with this? Thanks.


feat: add support for ipv6 in web.settings.mgmtHostPort stanza

It seems that you can add ipv6 string for web.settings.mgmtHostPort stanza.
Docs: https://docs.splunk.com/Documentation/Splunk/9.0.0/Admin/ConfigureSplunkforIPv6

:tada: This PR is included in version 4.8.0 :tada:
The release is available on:

v4.8.0
GitHub release

Your semantic-release bot :package::rocket:


Feature request: preserve raw error data on exceptions

Because authlib converts exceptions to HTTPException objects that have the error as a serialized string, it is difficult to use error handlers to change the error message format. It would be nice if the raw error data were preserved.
I think the idea was to have standard JSON errors by default. Still, it might be better not to interfere in Flask's standard error handling mechanism if the application uses, say, problem+json, and let the typed exceptions bubble up.

@lepture If you have a general idea of how you would like to see this implemented I would probably be able to do it.

Sorry, you are right. I should have specified I was talking about the ResourceProtector verification mechanism. It calls raise_oauth2_error -> raise_http_exception directly.

Added a raise_error_response on ResourceProtector. Check the latest code.

Great, thanks @lepture!


Refs #31358 -- Change salt measurement from characters to bits of entropy

This commit is in partial service of ticket
https://code.djangoproject.com/ticket/31358
It changes the measurement of the BasePasswordHasher salt
from character length to bits of entropy. Given the current
ascii encoding this code returns a salt with entropy greater than
or equal to the new salt_entropy value which has been set to ~128bits~ 71bits

@darakian Thanks 👍 I wonder if we should add a new paragraph about increasing the salt entropy to the "Password management" in Django docs.

Happy to help. I've restructured the comments as per your suggestions.
As for the documentation; how about we bundle that with the commit which changes the salt entropy value?

As for the documentation; how about we bundle that with the commit which changes the salt entropy value?

We introduce salt_entropy in this PR, so related docs changes should be included here.

Ok. Commit has been updated with some documentation.

I've rebased and reflowed https://github.com/django/django/pull/12553


[Feature] Get the height and width of the rectangle when using series->type:treemap->label:formatter function

What problem does this feature solve?
import * as echarts from 'echarts'
chart = proxy.$echarts.init(document.getElementById('myEcharts'),
2：
treemap
3：
chart.setOption->label->formatter:params
Can't get the height and width of the rectangle when using series->type:treemap->label:formatter function
What does the proposed API look like?
Get the height and width of the rectangle when using series->type:treemap->label:formatter function

I'm afraid you can't have this information. What kind of effect do you want to make?

I’m sorry, but unfortunately, that’s not possible with Apache ECharts.


Updating documentation for certificates

Short description
I had to update the certificates for my laptop and had some problems with it so I updated the documentation with what worked for me. If I missed something, please add it :)

I am wondering if we should change the app signing for development to "automatic code signing", so for local development there is no need to access the current profiles. As we rarely to never build live apps locally, I think this could help us prevent apple struggles. But i am not quite sure if this will work as expected/hoped.


Frida server error

Hello @St3v3nsS ,
I have tried installing the framework on a MAC book M1 processor and installed all the requirements successfully. However when I run the below below got the error
sudo python3 mmsfupdate.py

Hi there,
Looks like the file is not present in your system, could you please verify if the script has downloaded the file in ~/.mmsf/utils?

@kaleemshaik7867 I modified the script to initiate the directories if not exist. Please try again and let me know if this solves the issue.

Hello @St3v3nsS ,
I see a new error; it seems that the apksigner is not installed. I have downloaded the binary and kept in utils folder but still did not fowrk

@St3v3nsS FYI if I am using an alias for apksigner from the Android SDK folder like:
alias apksigner="/Users/<username>/Library/Android/sdk/build-tools/27.0.3/apksigner"

Still, I am getting the same error as the above screenshot shared by @kaleemshaik7867 using Intel MacBook Pro.

Fixed in 648ab7e. Let me know if it works.

Hello @St3v3nsS, I see new errors, and I have moved the zipalign binary to /usr/local/bin still does not work. Also exported it to the PATH.

I'm looking into this issue. Thank for noticing.

Fixed in #bac1943. Try now and see if it works.

Thank you. It worked.


Reproduced scores do not match with paper.

Thank you very much for your excellent work. I attempted to replicate the FID results using the provided demo Jupyter notebook. Following the identical code, I generated 50 images per class (resolutions of 256x256) and utilized the ADM's TensorFlow Evaluation Suite to calculate the scores.
For the VAR-d30 model, I obtained the following scores:
Inception Score: 406.5484
FID: 2.9021
sFID: 8.2664
Precision: 0.8469
Recall: 0.5581

The results for VAR-d12 are:
Inception Score: 337.3990
FID: 9.7795
sFID: 7.8580
Precision: 0.9325
Recall: 0.2679

It appears that the FID is significantly higher than reported in the paper (2.90 compared to 1.97), and the Inception Score is also much higher (406.5 versus 334.7). Could you advise on what might be causing these discrepancies? Could this be due to differences in inference hyperparameters or inherent randomness of FID evaluation? Would it be possible for you to provide the evaluation script so I can reproduce the results more closely?

The visual results on the demo are also noticeably worse than diffusion models like DiT

The visual results on the demo are also noticeably worse than diffusion models like DiT

@darius-lam
Do you mean the images in the dit paper or the actual comparison cases? The current generation model relies on sampling hyperparameters, and you may need to adjust the hyperparameters to get better results

Thank you very much for your excellent work. I attempted to replicate the FID results using the provided demo Jupyter notebook. Following the identical code, I generated 50 images per class (resolutions of 256x256) and utilized the ADM's TensorFlow Evaluation Suite to calculate the scores.
For the VAR-d30 model, I obtained the following scores:
Inception Score: 406.5484
FID: 2.9021
sFID: 8.2664
Precision: 0.8469
Recall: 0.5581

The results for VAR-d12 are:
Inception Score: 337.3990
FID: 9.7795
sFID: 7.8580
Precision: 0.9325
Recall: 0.2679

It appears that the FID is significantly higher than reported in the paper (2.90 compared to 1.97), and the Inception Score is also much higher (406.5 versus 334.7). Could you advise on what might be causing these discrepancies? Could this be due to differences in inference hyperparameters or inherent randomness of FID evaluation? Would it be possible for you to provide the evaluation script so I can reproduce the results more closely?

@YOLO9525
Thanks for your attention
we will check this

@YOLO9525 You used the demo notebook which has too large cfg ratio. Like DiT uses cfg=4.5 or 5 in demo and cfg=1.25 or 1.5 for FID evaluation, we use different cfg in demo and eval too. Large cfg will increase the semantics so you'll observe higher IS and FID.
Full training and evaluation scripts will be released in this week, plz stay tuned.

Thanks @keyu-tian , what size is the default model being used in the demo?

@darius-lam its VAR-d16 (310M)


Initial Preview: Robot controller via web input

Closes #204
Introducing this via pitop.labs, so as to allow us to develop this without having to commit to one particular implementation without better understanding our requirements.
Usage
from pitop import Pitop, DriveController, PanTiltController, Camera
from pitop.labs.webserver import run_webserver

# Create components
robot = Pitop()
drive_controller = DriveController()
pan_tilt = PanTiltController()
camera = Camera()

# Add components to the robot object
robot.add_component(drive_controller)
robot.add_component(pan_tilt)
robot.add_component(camera)

# Run webserver
run_webserver(robot_instance=robot,
              port=8070,
              serve_forever=True)

@jcapona @m-roberts even by reducing the quality of the jpeg like this it's still pretty much unusable on WiFi

@duwudi I think this is fixed by PR #262

I would prefer it if nipplejs.js were minified as part of the build (debian/rules), but this is fine

Really like this, sending the servo angle directly actually works very well - especially since it resets the servos once the user is finished looking which was a problem with the servo speed implementation used before (driving with an offset servo is not easy!).
The reason we might want to implement a servo speed one in future is to have a "pan-follow" drive mechanism, so when the pan servo moves the chassis would move to follow it - essentially this means the user is looking at where they want to steer towards and in steady-state you still get the zero angle pan. However, this implementation is way simpler and has a great UX so nice work!

@jcapona @m-roberts even by reducing the quality of the jpeg like this it's still pretty much unusable on WiFi

@duwudi I think this is fixed by PR #262

@jcapona I noticed this PR is not the same as what was in #262 - are we sure this is fixed as I still have way too much latency, it's more than what is necessary for true FPV driving (I have to be looking at the robot to drive it without crashing)

@jcapona @m-roberts even by reducing the quality of the jpeg like this it's still pretty much unusable on WiFi

@duwudi I think this is fixed by PR #262

@jcapona I noticed this PR is not the same as what was in #262 - are we sure this is fixed as I still have way too much latency, it's more than what is necessary for true FPV driving (I have to be looking at the robot to drive it without crashing)

yeah... I had to revert #262 (cc: @angusjfw ) because the image stream blocks the execution of the app, so joysticks don't work (their commands aren't sent)

yeah... I had to revert #262 (cc: @angusjfw ) because the image stream blocks the execution of the app, so joysticks don't work (their commands aren't sent) ... and adb9455 behaves the same way

Right, of course, I've fixed it to make both systems work now. I've been driving it around with this on my phone and it seems pretty good. Camera direction control brings a lot of life to it.
I also removed the optimize=True flag when converting the camera frames as I measured this was increasing the latency of the video stream. For live video the lost time optimizing outweighs the benefit of sending less data.
Anyway, we should discuss properly how we want to approach concurrency issues like this one we've found with handling camera and joysticks. The use of gevent in this server might complicate the situation for users and other parts of the sdk as it can be tricky to use alongside threads and asyncio, which are probably what users would prefer to work with and/or learn.

Just to add on top of what Angus has put (which I completely agree with), I would also like to think about how we can cover the web stuff with tests, and how we can/if we should combine this with coverage reporting from the Python code.


[feat/LIG-58] refactor dataflow management

Description

apply Dispatcher to manage dataflow submission, termination and cluster status
apply JobManager to manage each dataflow's status

Impact Scope

coordinator dataflow management
worker job management

Test Suggestions
it will be tested in CI
Tag
v1.0.2-alpha

Codecov Report

Merging #22 (d3595d4) into master (83df121) will decrease coverage by 0.07%.
The diff coverage is 45.45%.

@@            Coverage Diff             @@
##           master      #22      +/-   ##
==========================================
- Coverage   72.83%   72.76%   -0.08%
==========================================
  Files          21       21
  Lines        1874     1876       +2
==========================================
  Hits         1365     1365
- Misses        509      511       +2

Impacted Files
Coverage Δ

src/common/src/db.rs
80.00% <ø> (ø)

src/common/src/net/cluster.rs
98.03% <ø> (ø)

src/common/src/types.rs
73.48% <45.45%> (-0.70%)
:arrow_down:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Missing property: minecraft:behavior.look_at_player

The documentation on the property: target_distance
From axolotl

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

ID: 393e1b27-639f-d4bb-1933-d70eaddb7bcc
Version Independent ID: df23824b-714d-b03a-a33a-21575403484c
Content: minecraft:behavior.look_at_player
Content Source: creator/Reference/Content/EntityReference/Examples/EntityGoals/minecraftBehavior_look_at_player.md
Product: gaming
GitHub Login: @v-josjones
Microsoft Alias: v-josjones

This is now live. Thanks!


plug-in does not appear to work.. What did I do wrong?

// vite.config.ts
import { resolve } from 'path'

import reactSWC from '@vitejs/plugin-react-swc'
import { defineConfig } from 'vite'
import { cjsInterop } from 'vite-plugin-cjs-interop'
import vitePluginDts from 'vite-plugin-dts'
import tsconfigPaths from 'vite-tsconfig-paths'

// https://vitejs.dev/config/
export default defineConfig({
  plugins: [
    cjsInterop({
      dependencies: ['@emotion/styled', '@emotion/react'],
    }),
    reactSWC({
      jsxImportSource: '@emotion/react',
    }),
    vitePluginDts({
      insertTypesEntry: true,
    }),
    tsconfigPaths({ root: './' }),
  ],
  build: {
    sourcemap: true,
    lib: {
      entry: resolve(__dirname, 'src/main.ts'),
      name: 'MyLib',
      fileName: 'my-lib,
    },
    rollupOptions: {
      external: [
        '@emotion/react',
        '@emotion/styled',
        '@types/react',
        '@types/react-dom',
        'react',
        'react-dom',
        'typescript',
        'react-beautiful-dnd',
      ],
    },
  },
})

// build result
...
var Xa = Object.defineProperty;
var Ja = (e, t, r) => t in e ? Xa(e, t, { enumerable: !0, configurable: !0, writable: !0, value: r }) : e[t] = r;
var lr = (e, t, r) => (Ja(e, typeof t != "symbol" ? t + "" : t, r), r);
import * as Ln from "react";
import Q, { createContext as Qo, forwardRef as Jr, useContext as ei, createElement as nt, Fragment as Qa, useMemo as we, useCallback as F, useState as Y, useRef as Fe, useEffect as _e, useLayoutEffect as Fn, useImperativeHandle as Qr, PureComponent as ti, Children as es } from "react";
import { css as C, useTheme as en, keyframes as Ge, ThemeProvider as ts } from "@emotion/react";
import c from "@emotion/styled";
import ri, { createPortal as rs } from "react-dom";
import { Draggable as ns, Droppable as os, DragDropContext as is } from "react-beautiful-dnd";
function as(e) {
  if (e.sheet)
    return e.sheet;
  for (var t = 0; t < document.styleSheets.length; t++)
    if (document.styleSheets[t].ownerNode === e)
      return document.styleSheets[t];
}
...

here is my vite.config and build result.
I want to unwrap default imports @emotion by using this plugin.
But Doesn't seem to have applied to the build result.
what did i do wrong??
// pacakge.json
"devDependencies": {
    "vite": "^4.0.0",
    "vite-plugin-cjs-interop": "^0.0.7",
    "vite-plugin-dts": "^1.7.1",
    "vite-tsconfig-paths": "^4.0.3",
    "@vitejs/plugin-react-swc": "^3.0.0",
  },

You're using it in library mode, right?
That's a problem because vite-plugin-cjs-interop only works in SSR build. We could add an option for it to work on the client build too, but it would probably interfere with treeshaking since it will be trying to solve a problem that doesn't exist on the client (the interop issue is caused by Node's interpretation of CJS).
I don't know library mode very well, but I would suggest you do two builds, one for the server and one for the client. Then you can use conditional exports in package.json (or mainandbrowser` fields). Because the interop fix only needs to be applied to the Node build, not to the browser build.
I'll investigate the library mode and come back with more certainty on how to proceed.

thanks you for reply!
I used a because it was introduced in this issue, but I didn't know it was for SSR.
My purpose is to build and distribute react libraries using emotion as vites.
Until now, this library is available in CRA, but when used in next, it will cause an error at runtime.
I think it's because emotion is internally supporting esm and commonjs incorrectly. That's why I needed this plug-in move......
Thank you again for your help. I'll look into it more and come back.

I just release version 0.0.8 that adds a client option to force applying the plugin outside of SSR builds. Setting it to true should force it in the library mode too.
But I think a better option for you is to set build.lib.formats to ["es", "cjs"] and drop this plugin. And then point your package.json main field to the CJS build output and the browser field to the ESM build output. This way users of your lib will use the CJS build in Node (which doesn't require interop) and the the ESM build in the browser (which doesn't require interop either). Alternatively you can use the exports field with the "node" and "browser" conditions.
Hope this helps!


[Alonzo] - update proposals for Alonzo specific parameters does not work

Internal/External
Internal   if an IOHK staff member.
Area
Node CLI    Related to Token Locking (Allegra).
Summary
It is not possible yet to update the Alonzo protocol parameter values through update proposals.
Steps to reproduce
Steps to reproduce the behavior:
details here - https://input-output-rnd.slack.com/archives/C01UFC4QT0T/p1623702198494300
Expected behavior
A clear and concise description of what you expected to happen.
System info (please complete the following information):

alonzo_blue2.0 tag

it seems it is possible to update the protocol param in alonzo era using --alonzo-era


support HTTP Attack on chaosd

Signed-off-by: andrewmatilde<EMAIL_ADDRESS>Please install chaos-tproxy before use the HTTP attack.
usage:
./bin/chaosd attack http abort -h
abort selected HTTP Package

Usage:
  chaosd attack http abort [flags]

Flags:
  -c, --code int32          Code is a rule to select target by http status code in response.
  -h, --help                help for abort
  -m, --method string       HTTP method
      --path string         Mathc path of Uri with wildcard matches.
      --port int32          port is a rule to select server listening on specific port.
  -p, --proxy_ports uints   composed with one of the port of HTTP connection, we will only attack HTTP connection with port inside proxy_ports (default [])
  -t, --target string       HTTP target: Request or Response

Global Flags:
      --log-level string   the log level of chaosd. The value can be 'debug', 'info', 'warn' and 'error'
      --uid string         the experiment ID

./bin/chaosd attack http delay -h
delay selected HTTP Package

Usage:
  chaosd attack http delay [flags]

Flags:
  -c, --code int32          Code is a rule to select target by http status code in response.
  -d, --delay time string   Delay represents the delay of the target request/response.
  -h, --help                help for delay
  -m, --method string       HTTP method
      --path string         Mathc path of Uri with wildcard matches.
      --port int32          port is a rule to select server listening on specific port.
  -p, --proxy_ports uints   composed with one of the port of HTTP connection, we will only attack HTTP connection with port inside proxy_ports (default [])
  -t, --target string       HTTP target: Request or Response

Global Flags:
      --log-level string   the log level of chaosd. The value can be 'debug', 'info', 'warn' and 'error'
      --uid string         the experiment ID

./bin/chaosd attack http file -h
attack with config file

Usage:
  chaosd attack http file [flags]

Flags:
  -p, --file path string   Config file path.
  -h, --help               help for file

Global Flags:
      --log-level string   the log level of chaosd. The value can be 'debug', 'info', 'warn' and 'error'
      --uid string         the experiment ID

PTAL @WangXiangUSTC

@Hexilee PTAL


Add uniforms to starter app

Description

Checklist

[ ] npm test passes
[ ] npm run build works
[ ] tests are included
[ ] documentation is changed or added

Amazing job. Works like dream
Going to extend the model to add some nice uniforms combos etc.


Add process group as arg to FSDP

What does this PR do?
Add process group as arg to FSDP

for hsdp you set:
fsdp_config:
  process_group:
    - set<ReplicaSize>
    - mod<ReplicaSize>

?

for hsdp you set:
fsdp_config:
  process_group:
    - set<ReplicaSize>
    - mod<ReplicaSize>

?

Yep!


Follow HTTP redirect

We currently don't follow HTTP 301 redirects, which means any redirect becomes an error.

:+1:


Send post tags to metasmoke

Ref: Charcoal-SE/metasmoke#283
There is now a field for tags in the MS database; Smokey should send that information to metasmoke. It can be sent as an array in the post creation request; MS will serialize the array and store it.

Do we have post tag information? Trying to remember if the API returns it in a convenient (semicolon-delimited or something) format or if it does something evil.

Haven't the foggiest :)

It's available as an array tags, but only from /question not /posts (that works for us though).

The allspam command doesn’t use either of these routes AFAIK, so we may need to make an extra API request there in order to get the tags.

Would it be better to run the request from metasmoke?

Only if we're sure we don't want to use tags for spam checks

Any tags on spam posts are (almost always) going to just be the suggested tags.

Agree with quartata, since 1-rep folks can't create tags they don't appear to have much signal. I think we should start collecting them first, then build it into Smokey if we see useful patterns.


its possible to add new commands to debugger ?

where/up/down and jump commands ?
Steps to reproduce
for example here 4 functions in separates files:
#222.ps1
function f3 {
  $a = 5
 f2
  #..etc
}

#456.ps1
function f2 {
   $b = 3
  f1
   #..etc
}

#123.ps1
function f1 {
   $e = 44
   $n = 6
  f0
   #....etc
}

#123.ps1
function f0($mypath) {
   $c = 9
   $d = 14
   #...etc
}

to navigate not by line but by frame (function/script)
add new commands where/up/down
#where (w): show the current location in the frame stack for example
[DBG] PS> where

  123.ps1 : line 7  f0 {$mypath}
->123.ps1 : line 66 f1 {}
  456.ps1 : line 7  f2 {}
  222.ps1 : line 3  f3 {}

 [DBG] PS> $c
 [DBG] PS> up
 [DBG] PS> w

->123.ps1 : line 7  f0 {$mypath}
  123.ps1 : line 66 f1 {}
  456.ps1 : line 7  f2 {}
  222.ps1 : line 3  f3 {}

  [DBG] PS> $c; $mypath
  9
  c:/temp
  [DBG] PS> down
  [DBG] PS> down
  [DBG] PS> where

  123.ps1 : line 7  f0 {$mypath}
  123.ps1 : line 66 f1 {}
->456.ps1 : line 7  f2 {}
  222.ps1 : line 3  f3 {}

and add jump command to jump over loop for example:
>>>  $s = 0
>>>  foreach($i in 0..1gb) {
>>>      $s += $i
>>>      $z = 8 + $s
>>>      # etc
>>>      write-host $s -ForegroundColor red
>>>      sleep 1
>>>   }
>>>   $u = 787
>>>   'another statement'

[DBG]: PS C:\>> l

    1:    $s = 0
    2:*   foreach($i in 0..1gb) {
    3:       $s += $i
    4:       $z = 8 + $s
    5:       # etc
    6:       write-host $s -ForegroundColor red
    7:       sleep 1
    8:    }
    9:    $u = 787
   10:    'another statement'

[DBG]: PS> $s
10
[DBG]: PS> $i
4

[DBG]: PS> # and after 20 step :) debugging the loop

[DBG]: PS> jump 9

[DBG]: PS> l

    1:    $s = 0
    2:    foreach($i in 0..1gb) {
    3:       $s += $i
    4:       $z = 8 + $s
    5:       # etc
    6:       write-host $s -ForegroundColor red
    7:       sleep 1
    8:    }
    9:*   $u = 787
   10:    'another statement'

thanks

In theory, you can use the method GetFrameVariables on the objects returned from Get-PSCallStack to implement your hypothetical up - but it would probably require some creativity to get it working exactly like your proposal.
With some additional creativity, you could create some new debugger commands like jump without changing the PowerShell debugger.
These are the currently available commands that can help:
PS C:\Users\jason> gcm -Noun PSBreakpoint,PSCallStack

CommandType     Name                                               Version    Source
-----------     ----                                               -------    ------
Cmdlet          Disable-PSBreakpoint                               <IP_ADDRESS>    Microsoft.PowerShell.Utility
Cmdlet          Enable-PSBreakpoint                                <IP_ADDRESS>    Microsoft.PowerShell.Utility
Cmdlet          Get-PSBreakpoint                                   <IP_ADDRESS>    Microsoft.PowerShell.Utility
Cmdlet          Get-PSCallStack                                    <IP_ADDRESS>    Microsoft.PowerShell.Utility
Cmdlet          Remove-PSBreakpoint                                <IP_ADDRESS>    Microsoft.PowerShell.Utility
Cmdlet          Set-PSBreakpoint                                   <IP_ADDRESS>    Microsoft.PowerShell.Utility

Breakpoints can have custom actions which can conditionally break, see the docs.
You can also utilize the debugger api via $ExecutionContext.Host.Runspace.Debugger.
It probably makes sense to expose other debugger primitives like step over and step into as commands, this would allow some simple customization such as defining your own aliases as well making it easier to implement jump.


Are there plans to make it able to reconstruct the IL?

I know it's a WIP, but is reconstructing the IL one of the planned features for this, or is it out of the scope of the project?

Sorry, I didn't see this issue. Yes, I'm currently rewriting the internals in order to prepare for IL reconstruction.

Any Update?

I do now have an update for this ticket - the new analysis engine is roughly on-par with the old one, so I've enabled it by default. It should allow for IL generation in the (comparatively-)near future.

This is now sort of implemented. There's a new command line option in the dev build, --experimental-enable-il-to-assembly-please, which will ATTEMPT to save the IL back to the DLL. You can change which DLL this runs for with --run-analysis-for-assembly=AssemblyNameWithoutDllExtension.
This will be going live in the next milestone release shortly. Probably going to call it 2021.3.1.

Going to close this now as its basically implemented for everything relevant, all else is covered by other stuff in the roadmap and issues


Upgrading PostgreSQL database for web3signer from 15 to 16 version preventing database loading

Today I've done ./ethd update and my web3signer refused to load.
The problem was, that PostgreSQL for web3signer was updated from 15 to 16 version, because by default we are using
PG_DOCKER_TAG=alpine
in .env file.
PostgresSQL refused to load because of incompability.
2023-09-26 18:30:57.504 UTC [1] FATAL:  database files are incompatible with server 2023-09-26 18:30:57.504 UTC [1] DETAIL:  The data directory was initialized by PostgreSQL version 15, which is not compatible with this version 16.0.
I've fixed this by myself just by changing PG_DOCKER_TAG to latest v15 alpine image (15.4-alpine3.18), but I think we need better solution for this.

Ah so that's what broke it! Thank you. I have since pinned the version to 15-alpine in default.env as well. I agree that there needs to be a way to upgrade the Postgres version, and bring the DB along. Let's keep this issue open for that.

This won't be entirely trivial. Basically we need a container with both 15 and 16, run pg_upgrade, then start 16. See https://github.com/tianon/docker-postgres-upgrade
Need to think a little on how to automate that so that major version upgrades happen automatically, maybe once 16 is on 16.4. This does break the usual UX of users being able to choose a specific tag. I'd need to override that, replace the tag and in the same action do the one-time migration.

Needs to work with arm64 and alpine. There's a repo that adds arm64; asked whether they'd consider a PR for alpine.
https://codeberg.org/pat-s/docker-postgres-upgrade/issues/3

Migrating to bookworm instead, which is the faster PostgreSQL at any rate.
This should land early 2024 with PostgreSQL 16.2.

Migration merged

I've tested migration from 15 to 16, and can confirm it is working.
Thanks for this feature implementation

Glad to hear it! I had run a web3signer on 15 for a month and then tested this, to make sure it would work with a medium-sized DB (1.5 GiB and 10k validators - Holesky). It’s good to get confirmation.
There’s a whole failure handler with dire warnings, because if this fails when the old DB is already removed, there’s a slashing risk. I hope no one ever needs to rely on it, but it’s there.


Support request specific TLS configuration

Adds support for request-specific TLS configuration:
Request(url: "https://webserver.com", tlsConfiguration: .forClient())
https://github.com/apple/swift-nio-ssl/pull/280 must be released, before this can be merged.

@swift-server-bot add to allowlist

@madsodgaard hmm, weird 5.0 compiler warning (that we turn into errors):
[449/452] Compiling Swift Module 'AsyncHTTPClient' (15 sources)
/code/Sources/AsyncHTTPClient/BestEffortHashableTLSConfiguration.swift:16:18: error: result of call to 'bestEffortEquals' is unused
        lhs.base.bestEffortEquals(rhs.base)
                 ^               ~~~~~~~~~~
Build step 'Execute shell' marked build as failure

Also, async-http-client uses automatic format checking with SwiftFormat. If you run SwiftFormat over the source, then the "soundness" part should pass.

@weissi Whoops, forgot a return statement 😅

@madsodgaard also the API breakage checker detected an API breakage:
08:37:54 /* Removed Decls */
08:37:54 Constructor HTTPClient.Request.init(url:method:headers:body:) has been removed

Note that in Swift you cannot just add a new parameter (even if it has a default value) without breaking API. Instead of adding the tlsConfiguration: parameter with a default value, you'll need to add a new init with an extra (non-defaulted) parameter. The existing HTTPClient.Request.init(url:method:headers:body:) should then just call the new init with the extra parameter.


Stackblitz link is broken

Hello. Clicking on the stackblitz link, in the readme or elsewhere, leads to a nonexistent page.

Some examples can be found here:
https://stackblitz.com/edit/angular-vvp849
and here:
https://stackblitz.com/edit/angular-i7ykf5
Daniel's main StackBlitz page is here:
https://stackblitz.com/@DanielYKPan


Assertion in 'do_send' (quicly.c)

Hi,
during some tests I got this error
qperf: /root/qperf/extern/quicly/lib/quicly.c:4346: do_send: Assertion `min_packets_to_send <= s->max_datagrams' failed.

that I solved by setting the min_packets_to_send = 1 instead of min_packets_to_send = 0 . I am pretty sure that it can be fixed also by putting assert(min_packets_to_send < s->max_datagrams)
Can you inspect this error and validate the solution?
Thanks

+1

I had this error come up recently. I tried changing <= to < in assert(min_packets_to_send <= s->max_datagrams) but it didn't seem to work. Still not sure what's up with it.


Yahoo SSP Bid Adapter

The Yahoo SSP Bid Adapter is a new consolidated banner & video adapter intended to replace all legacy adapters: aol, oneMobile, oneDisplay and oneVideo owned previously by AOL / Oath / Verizon Media.
See: https://github.com/prebid/Prebid.js/pull/7522
In this PR we are providing basic integration details with the adapter
as well as notices on old adapters to migrate.
Thanks in advance!
Adam

Hi @patmmccann would it be possible to merge these latest updates please?
Thanks in advance!

We are always waiting for the release to finish and then merge the outstanding pull requests 😊


Fix Spelling Errors

Fixes two words that had misspellings.

@TimCorey : Thanks for your contribution! The author, @CarlRabeler, has been notified to review your proposed change.

#sign-off


Threejs version to show what's in a div

Hi @hiukim, do you know if it's possible to modify the threejs example to show what's on a div instead of a threejs geometry? Basically I have some content in a div on the same page that I want to show in AR.

There is a method addCSSAnchor instead of addAnchor. But I haven't had the chance to add that tutorial/example yet.

How do I use it? I tried this
const anchor = mindarThree.addCSSAnchor(0);
const content = document.getElementsByTagName('canvas')[0];
anchor.group.add(content);

but it didn't work. I keep getting the error
mindar-image-three.prod.js:2 THREE.Object3D.add: object not an instance of THREE.Object3D.
on the line anchor.group.add(content);

Instead of trying to add the canvas object to a threejs object, you will need to create a texture from the canvas, and apply it to a plane (which subclasses Object3D)


fix: #394 & update sub vending module to v1.3.1 from upstream home

Description
This PR fixes #394 and brings in the latest release of the bicep-lz-vending module of v1.3.1 from upstream
Updating an existing module

[x] This is a bug fix:

[x] Someone has opened a bug report issue, and I have included "Closes #{bug_report_issue_number}" in the PR description.
[ ] The bug was found by the module author, and no one has opened an issue to report it yet.

[x] I have run brm validate locally to verify the module files.
[x] I have run deployment tests locally to ensure the module is deployable.
[x] I have read the Updating an existing module section in the contributing guide and updated the version.json file properly:

[ ] The PR contains backwards compatible bug fixes, and I have NOT bumped the MAJOR or MINOR version in version.json.
[x] The PR contains backwards compatible feature updates, and I have bumped the MINOR version in version.json.
[ ] The PR contains breaking changes, and I have bumped the MAJOR version in version.json.

[x] I have updated the examples in README with the latest module version number.

Testing evidence from upstream

https://github.com/Azure/bicep-lz-vending/pull/40

https://github.com/Azure/bicep-lz-vending/actions/runs/5146195469
https://github.com/Azure/bicep-lz-vending/actions/runs/5146195469/jobs/9265312721

@shenglol would appreciate a review/approve and merge of this one so we can get the releases in sync between our repo (upstream) and the registry 👍👍


DESCRIBE produces duplicate statements

(Migrated from https://openrdf.atlassian.net/browse/SES-723)
If the database contains the statement [ ex:a ex:p ex:a ] then the query "DESCRIBE ex:a" returns [ ex:a ex:p ex:a ] twice.

From the spec, "The DESCRIBE form returns a single result RDF graph containing RDF data about resources." CONSTRUCT produces an RDF graph too and doesn't dedup, so if I understand the issue correctly, this should be a "not a bug/wont fix" for the same reasons CONSTRUCT doesn't dedup.

I don't think either the SPARQL or RDF Abstract Model specs specify whether concrete RDF documents should/shall/etc. be deduplicated. The RDF Abstract Model specifies that in abstract terms the final model is a Set, which implies deduplication has occurred at that point, but it doesn't say anything about parsing methods or concrete formats.


Blocked by CSRF Cookie/Header mismatch

see https://github.com/pouchdb/pouchdb/issues/4147

Turns out to be irrelevant


bug(material/autocomplete): Intermittent Scrolling Issue with mat-autocomplete on Mobile Devices

Is this a regression?

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

The previous version in which this bug was not present was
No response
Description
We are experiencing an intermittent but recurring issue with the mat-autocomplete component when accessed via mobile devices. Specifically, when users attempt to scroll through the options presented in the autocomplete dropdown, the scroll action unexpectedly affects the underlying webpage instead of the dropdown list. This behavior disrupts the user's ability to select an option from the autocomplete list and significantly impacts the usability of the component. The issue has been consistently observed across a variety of devices and web browsers, indicating a broader compatibility or event handling problem within the component.
Video Demonstration of the Issue:
https://javamaniac.github.io/angular-autocomplete-example/screen-20240212-143204.mp4
Reproduction
StackBlitz link: https://stackblitz.com/~/github.com/javamaniac/angular-autocomplete-example
The issue with mat-autocomplete scrolling is intermittent and does not have a consistent reproduction sequence. However, it generally involves interactions with the autocomplete component on a mobile device. Below are steps that have sometimes led to the issue, though it may require repeating certain actions or experimenting with the sequence to observe the problem.
Potential Reproduction Sequences:
Basic Interaction:

Open the autocomplete dropdown.
Attempt to scroll through the options.

Extended Interaction:

Open the autocomplete dropdown.
Select any option from the list.
Clear the selected option (erase the choice).
Attempt to scroll through the options again.

External Interaction:

Open the autocomplete dropdown.
Click outside the dropdown to close it.
Re-open the dropdown.
Attempt to scroll through the options.

Note: The issue may not manifest on the first attempt and could require varying the sequence of actions, such as selecting and clearing choices multiple times or opening and closing the dropdown before scrolling attempts are made. The problem appears to be more likely to occur after interacting with the dropdown in some way (selecting options, erasing choices, or clicking outside the dropdown) before attempting to scroll through the options again.
Expected Behavior
Dragging (scrolling) within the mat-autocomplete dropdown should scroll through the autocomplete options.
Actual Behavior
Attempting to scroll through the autocomplete options results in the page itself scrolling.
Environment

Angular: 16, 17 (issue likely affects older versions as well)
CDK/Material: 16, 17
Browser(s): Chrome, Edge, Safari
Operating System (e.g. Windows, macOS, Ubuntu): Android, iOS

Devices tested:

Google Pixel 6 (Chrome, Edge)
iPhone SE (Chrome, Safari)

This is a real problem, since users are unable to select the right options. This only happens on mobile devices,.

It looks like it happens when the keyboard from the device comes into view... when the keyboard is gone, I'm able to scroll

A temp fix for this issue, add interactive-widget to overlays-content in the meta tag

More info:
https://github.com/bramus/viewport-resize-behavior/blob/main/explainer.md#proposal
https://developer.mozilla.org/en-US/docs/Web/HTML/Viewport_meta_tag


Cleanup street_network and import_streets crates

These 2 crates were just moved over from the A/B Street repo. Now that the big transition is done, some smaller cleanup tasks.

[x] Reorganize street_networks/src/lib.rs into more modules
[x] Consistently call an instance of StreetNetwork something -- probably streets. Not raw or map.
[x] Stop re-exporting all the types from raw_map; clean up callers to import from street_network (over on the abstreet side)
[x] Clean up the weird dependency on kml::ExtraShapes for debugging. We should just output GeoJSON instead; don't need the weird wrappers. I'll probably rethink ExtraShapes in general; I made it up early before I knew how to sanely parse geojson in rust.
[x] Update the README in this repo to explain the structure of the crates, and how we'll build multiple wrappers on top of StreetNetwork
[ ] Add error handling to import_streets
[ ] Reconsider import_streets::Options. There's a bunch of A/B Street-isms in there ignored by this repo.
[ ] Slim down the public interface of import_streets. It should mostly just be osm_to_street_network, and over in abstreet, convert_osm should call that.

and @BudgieInWA, now that the 2 crates live over here, please scrutinize them more as you build on top of them. For example, the next big change I want to finish is cutting over to osm2lanes. That'll be a good example of how development in this repo proceeds, because my validation for that cutover will be to make sure there are no unintended consequences downstream in abstreet

and @BudgieInWA, now that the 2 crates live over here, please scrutinize them more as you build on top of them.

Great! I'm looking forward to making more changes directly in street_network rather than on top of it. The next deep dive I do on this project will be familiarising myself with the details of these new crates -- maybe implementing a "Slice" kind of intersection.
This split (and the cleanups that you will continue to do) should make it much easier for me to do so!

With #137 and other recent work, we can call this done, or there are more specific issues/ideas now that take precdence


Warning: getInitialState was defined on Scrollbars

react-custom-scrollbars:
version: "4.1.0"
React:
version: "15.1.0"

fixed in 4.1.1


Add missing QueuePolicy in AWS Playground AppHost

The sample CloudFormation template configures a subscription for the SQS Queue to receive messages from the SNS Topic, but no QueuePolicy is configured which results in: User: arn:aws:iam::111111111111:user/DUB.SQS is not authorized to perform: sqs:sendmessage on resource: arn:aws:sqs:eu-west-1:222222222222:AspireSampleDevResources-ChatMessagesQueue-abcdef123456 because no resource-based policy allows the sqs:sendmessage action.
This pull request adds a QueuePolicy allowing SNS to deliver messages to the ChatMessagesQueue.

@dotnet-policy-service agree


Port TileEntities

Machines:

[ ] FluidTankGC
[ ] TileEntityAdvanced (Base class)
[ ] TEAirlock
[ ] TEAirlockController
[ ]
[ ]
[ ]

Idk why github made 2 issues...


POC: allow project references to be resolved relative to outDir

Fixes #

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: alexeagle sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

To help with PR housekeeping, I'm going to close this draft PR. It's pretty old.


Feature Request: Ability to disable "negative edge" for action buttons

Ability to disable "negative edge" per profile for action buttons (P1-P4, K1-K4).
For reference, definition quoted from Infil's Glossary:
Negative Edge is the act of releasing a button (instead of pressing it) to perform a special move. You might be surprised to learn that, in pretty much all fighting games, you can throw a fireball by first pressing and holding a punch button by itself, then doing your quarter circle input, and finally releasing the button.

Hi @pokeshark ,
We have chatted internally and this is not something we are interested in implementing at this time.

I will further clarify that the definition quoted above is describing game behavior, not input device behavior. We cannot control how a game registers a button press or hold.