feat: add vite to bundle

What does it do?
This PR does a few things:

Adds vite as the bundler for the packages
Moves the testing infrastructure outside the packages so it can be used for the repo as a whole
Consolidates deps / devDeps e.g. there were some devDeps in deps & some devDeps we weren't using in certain areas or at all

Ideally, I'd like to lift out storybook into it's own docs folder and make that isolated from the packages so we have to import { Select } from '@strapi/design-system' so that

we can be sure the public facing package works as intended
remove unnecessary devDeps from the design-system package and keep it tidier in the long run.

This would require moving all the stories around and I want to get the opinion on it before actioning.
Why is it needed?
Because moving to vite decreases bundle size by ~70-80% and therefore allows better tree shaking in other applications.
Keeping the packages tidy as possible to ensure we're not adding additional overheads where not required i.e. when people install our package imo they shouldn't be installing all the unneccessary devDeps for our storybook etc.

Because of the changes to type:module in the package.json, #741 needs to be merged first.

NOTE: it also might be worth releasing a beta of this prior to stable to ensure it correctly works with cloud and cms.
Therefore, we could set up a beta branch – thoughts?

I think in terms of merge/ release I'd prefer if we'd release 1.26 asap followed by a 1.3 alpha/ beta release, so that both (cloud and cms) can pull it in to see if that works well.

What do you think?

I agree, I'll try to get 1.2.6 released today as there's bits for relations that we need, then when people are happy with this PR we should do a beta release of 1.3 👍🏼 check it works across cloud and admin then release stable.


Fix for issue #258

Fix javascript errors when using Colorpicker datatype. The solution is the same as the existing hack for the fileupload datatype by adding a validation property to the model.

Thank you for this, I'll review and test when I get a chance! :+1:

This will likely get pulled in but I may merge the two similar if statements. Target release will be the January patch update.

Thanks!

I made it a tiny bit more DRY, but thank you nonetheless!


Your web app is running and waiting for your content

Hello,
As far as I can tell I've successfully installed everything according to the instructions. When I visit the configuration page I am met with a generic Azure page with the message "Your web app is running and waiting for your content".
I don't see anything wrong that I can troubleshoot. I've also verified that the config app has admin consent. Any suggestions?
Thanks

你好，请问你解决了吗？


Mobile friendly

Make this website mobile friendly. It's not currently 100% mobile friendly.

I'll give it a crack! Forking now.

Sounds like a task that I can handle. Forking!


Update to YAMT guide as files no longer need to be saved

Removed the last part about not deleting files as it no longer applies to Ensō users

This would be fixed with #179

Fixed: #179


No SOURCES given to target: zstd_static

fails to build

had to clone with recusive

:D

I will think about including submodule update part in the Build instructions in readme, thanks.

@mapron downloading the source from the release page has the same problem so maybe include a script to clone the repos manually for people who do that

downloading the source from the release page has the same problem
well, source balls made by github, I do not control them. Did not notice GH does not include submodules there, that's unfortunate.

I will create an issue to think about it, as I planing to add 1 more submodule anyway.

#16 created I will think how to improve it


WIP - use for deploying concat

This changes the install script to install a binary mcnode from a github release, and changes most of the branding from OpenBazaar to Mediachain.  There's a few stray OB1 references around though, so we should clean that up before we merge.
We'll need to run a very simple CORS proxy on the domain we serve this from.  The code tries to GET http://deploy.mediachain.io/cors/status/${dropletIP} which should return the string READY when the install completes.  The droplet is running a lighttpd server that will serve up the deployment status at http://${dropletIP}:9010/state, so that's what the proxy should try to resolve
Update: the CORS proxy isn't needed if we add  "Access-Control-Allow-Origin" => "*" to the lighttpd config.  This seems safe since we're exposing so little.  With that, we can just request the status directly from the node without a proxy.
TODO (see #1, #2 and #4):

[ ] finish the rebranding, remove refs to OpenBazaar (howto videos, etc)
[X] run the CORS proxy
[x] deploy this project somewhere
[ ] add docs for how to use mcclient over SSH to control your node
[ ] add docs (and copy/paste shell command?) for fetching your node's keypair over SSH
[ ] change the digital ocean referral code :)

Should def leave a shout to OBZ team in the UI, BTW

yeah, great call

going to merge this; we can update the referral code and add some more docs in a second pass


feat: add support for overriding the initCode for an account

Pull Request Checklist

[x] Did you add new tests and confirm existing tests pass? (yarn test)
[x] Did you update relevant docs? (docs are found in the site folder, see guidleines below)
[x] Do your commits follow the Conventional Commits standard?
[x] Does your PR title also follow the Conventional Commits standard?
[x] If you have a breaking change, is it [correctly reflected in your commit message](https://www.conventionalcommits.org/en/v1.0.0/#examples? (e.g. feat!: breaking change)
[x] Did you run lint (yarn lint:check) and fix any issues? (yarn lint:fix)
[x] Is the base branch you're merging into development and not main?

PR-Codex overview
Detailed summary

Added an optional override for the account address in the createBaseSmartAccountParamsSchema function.
Added an optional override for the account init code in the createBaseSmartAccountParamsSchema function.
Updated the tests to use the new account init code override.
Added a new property accountInitCode in the BaseSmartContractAccount class.
Updated the getAccountInitCode method to return the value of accountInitCode if it exists.
Updated the getAddress method to use the _getAccountInitCode private method.
Added the _getAccountInitCode private method to return the value of accountInitCode if it exists.
Added the create6492Signature private method to handle signature creation for deployed and non-deployed accounts.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

@moldy530
q1: what was the context around needing this feature? This feature is for deployed accounts only or could be also used for non-deployed accounts?
q2: should we add some validations on when these optional parameters should be passed in so that devs can catch when incorrect set of parameters are passed in? (runtime validation using zod) cc: @avasisht23

Q1: context around this is to support the case where a developer wants to snapshot the initCode that generated a given counterfactual. This is useful to protect against the case where the counterfactual might change before a user eventually sends a UO and deploys their account. with this, a dev can make sure that when a UO is finally sent, they deploy the account the user has been using the counterfactual of, even if the default factory address or account impl changes down the line
Q2: I've added validations to Zod around passing this in already here. However, beyond that we can't do much else to enforce that a dev SHOULD pass them. it's opt-in if they want to override these params

Current dependencies on/for this PR:

development

PR #197   👈

This stack of pull requests is managed by Graphite.


Non-existence proof verification failed

We can verify the non-existence proof with another proof spec because the left or right leaf's key and value are hashed in Sparse Merkle Tree.
However, we cannot switch the proof spec in the IBC client module. The proof spec is used for both the existence and non-existence proof verification.

The proof and the verification work well, however, sparse-merkle-tree(SMT) isn't compatible with the current IBC integration. We need to replace the Merkle tree implementation.
The problem is that the non-existence proof-verification requires a different proof spec from that of the existence proof verification.
IBC VP couldn't verify the receipt absence on the counterparty chain (when packet-timeout) because IBC VP (ibc-rs and cosmos(ibc-go)) uses the same proof spec for the existence and non-existence proof verification. It is set in an IBC client state.

Proof spec of the leaf for the existence proof

LeafOp {
    hash: H::hash_op().into(),
    prehash_key: H::hash_op().into(),
    prehash_value: H::hash_op().into(),
    length: LengthOp::NoPrefix.into(),
    prefix: H256::zero().as_slice().to_vec(),
}

Proof spec of the leaf for the non-existence proof

LeafOp {
    hash: hash_op.into(),
    prehash_key: HashOp::NoHash.into(),
    prehash_value: HashOp::NoHash.into(),
    length: LengthOp::NoPrefix.into(),
    prefix: H256::zero().as_slice().to_vec(),
}

The non-existence proof needs a different proof spec because sparse-merkle-tree (SMT) returns the proof with the hashed key and value of neighbors in SMT.
For the existence proof, we can replace the key and value in the proof generated by SMT with a non-hashed(original) key and value to verify it with ICS23 verification which checks if the key and value are equal to the target key and value. So, the proof spec's LeafOp (it says how to calculate the leaf hash) should set the prehash_key and prehash_value with the hash operation (Sha256 in this case) to calculate their hashes after the comparison.
pub struct ExistenceProof {
    #[prost(bytes = "vec", tag = "1")]
    pub key: ::prost::alloc::vec::Vec<u8>,
    #[prost(bytes = "vec", tag = "2")]
    pub value: ::prost::alloc::vec::Vec<u8>,
    #[prost(message, optional, tag = "3")]
    pub leaf: ::core::option::Option<LeafOp>,
    #[prost(message, repeated, tag = "4")]
    pub path: ::prost::alloc::vec::Vec<InnerOp>,
}

Replace the hashed key and value
https://github.com/anoma/anoma/blob/8eeab64ca0765950cef4c8a0c1f5b9de6a672b90/shared/src/ledger/storage/merkle_tree.rs#L251-L261

ICS23 checks the key and value (called by ibc-rs verification)
https://github.com/confio/ics23/blob/8ea0b239740068dd004fe4a42a1d861cd607611c/rust/src/verify.rs#L22-L23

We want to replace the hashed key and value for the non-existence proof, but we cannot. That's because they are hashed and we don't know the original key and value of the neighbors (we know only the target key at that time).
The non-existence proof has existence proofs of the neighbors. ICS23 verification checks the existence proofs. These existence proofs have the hashed key and value. We can verify the proof with the spec which sets the prehash_key and prehash_value with NoHash because they have been already hashed. (ICS23 verification doesn't compare that key to the given key in the non-existence proof verification.) However, ibc-rs/cosmos uses the same proof spec for the existence and non-existence proof.
pub struct NonExistenceProof {
    #[prost(bytes = "vec", tag = "1")]
    pub key: ::prost::alloc::vec::Vec<u8>,
    #[prost(message, optional, tag = "2")]
    pub left: ::core::option::Option<ExistenceProof>,
    #[prost(message, optional, tag = "3")]
    pub right: ::core::option::Option<ExistenceProof>,
}

I tried to modify SMT to have the original key and value in each leaf and to get the proof with them. But ICS23 refused the proof. ICS23 verification checks also the key order for the non-existence proof. The original keys order is not the same as hashed keys' order in the tree. That's why it failed.

The proof and the verification work well, however, sparse-merkle-tree(SMT) isn't compatible with the current IBC integration. We need to replace the Merkle tree implementation.
The problem is that the non-existence proof-verification requires a different proof spec from that of the existence proof verification.
IBC VP couldn't verify the receipt absence on the counterparty chain (when packet-timeout) because IBC VP (ibc-rs and cosmos(ibc-go)) uses the same proof spec for the existence and non-existence proof verification. It is set in an IBC client state.

Proof spec of the leaf for the existence proof

LeafOp {
    hash: H::hash_op().into(),
    prehash_key: H::hash_op().into(),
    prehash_value: H::hash_op().into(),
    length: LengthOp::NoPrefix.into(),
    prefix: H256::zero().as_slice().to_vec(),
}

Proof spec of the leaf for the non-existence proof

LeafOp {
    hash: hash_op.into(),
    prehash_key: HashOp::NoHash.into(),
    prehash_value: HashOp::NoHash.into(),
    length: LengthOp::NoPrefix.into(),
    prefix: H256::zero().as_slice().to_vec(),
}

The non-existence proof needs a different proof spec because sparse-merkle-tree (SMT) returns the proof with the hashed key and value of neighbors in SMT.
For the existence proof, we can replace the key and value in the proof generated by SMT with a non-hashed(original) key and value to verify it with ICS23 verification which checks if the key and value are equal to the target key and value. So, the proof spec's LeafOp (it says how to calculate the leaf hash) should set the prehash_key and prehash_value with the hash operation (Sha256 in this case) to calculate their hashes after the comparison.
pub struct ExistenceProof {
    #[prost(bytes = "vec", tag = "1")]
    pub key: ::prost::alloc::vec::Vec<u8>,
    #[prost(bytes = "vec", tag = "2")]
    pub value: ::prost::alloc::vec::Vec<u8>,
    #[prost(message, optional, tag = "3")]
    pub leaf: ::core::option::Option<LeafOp>,
    #[prost(message, repeated, tag = "4")]
    pub path: ::prost::alloc::vec::Vec<InnerOp>,
}

Replace the hashed key and value
https://github.com/anoma/anoma/blob/8eeab64ca0765950cef4c8a0c1f5b9de6a672b90/shared/src/ledger/storage/merkle_tree.rs#L251-L261

ICS23 checks the key and value (called by ibc-rs verification)
https://github.com/confio/ics23/blob/8ea0b239740068dd004fe4a42a1d861cd607611c/rust/src/verify.rs#L22-L23

We want to replace the hashed key and value for the non-existence proof, but we cannot. That's because they are hashed and we don't know the original key and value of the neighbors (we know only the target key at that time).
The non-existence proof has existence proofs of the neighbors. ICS23 verification checks the existence proofs. These existence proofs have the hashed key and value. We can verify the proof with the spec which sets the prehash_key and prehash_value with NoHash because they have been already hashed. (ICS23 verification doesn't compare that key to the given key in the non-existence proof verification.) However, ibc-rs/cosmos uses the same proof spec for the existence and non-existence proof.
pub struct NonExistenceProof {
    #[prost(bytes = "vec", tag = "1")]
    pub key: ::prost::alloc::vec::Vec<u8>,
    #[prost(message, optional, tag = "2")]
    pub left: ::core::option::Option<ExistenceProof>,
    #[prost(message, optional, tag = "3")]
    pub right: ::core::option::Option<ExistenceProof>,
}

I tried to modify SMT to have the original key and value in each leaf and to get the proof with them. But ICS23 refused the proof. ICS23 verification checks also the key order for the non-existence proof. The original keys order is not the same as hashed keys' order in the tree. That's why it failed.

because sparse-merkle-tree (SMT) returns the proof with the hashed key and value of neighbors in SMT.

Returns specifically the non-existence-proof with the hashed key and value of neighbors?

We want to replace the hashed key and value for the non-existence proof, but we cannot. That's because they are hashed and we don't know the original key and value of the neighbors (we know only the target key at that time).

Hmm, we must be storing the key and value of the neighbors in the tree somewhere, right? Can we look them up in order to produce the proofs?

I tried to modify SMT to have the original key and value in each leaf and to get the proof with them. But ICS23 refused the proof. ICS23 verification checks also the key order for the non-existence proof. The original keys order is not the same as hashed keys' order in the tree. That's why it failed.

Hmm, I don't quite follow - if you have the original key and value in each leaf, why would the key order be different? Are some intermediate values still being hashed an extra time, compared to what ICS23 expects?

Our SMT provides functions to make ICS23 proofs from the tree.
The ICS23 proofs can be verified in our tests.


[ZEPPELIN-1312] Hotfix - consistent getNoteRevision in websocket call

What is this PR for?
This pr fixes inconsistency on websocket call of getNoteRevision method on frontend, since backend waits for Revision but front sends RevisionId.  This is the simplest fix without api change.
What type of PR is it?
Hot Fix
Todos

[x] - RevisionId -> Revision

What is the Jira issue?
Zeppelin-1312
How should this be tested?
CI pass
Screenshots (if appropriate)
Questions:

Does the licenses files need update? no
Is there breaking changes for older versions? no
Does this needs documentation? no

/cc @corneadoug @bzz for review

Looks good to me.
@khalidhuseynov fix for version is not set in JIRA (neither it is assigned yet) - merging only to master, in case there is no further discussion

@bzz added fix version to issue. merging into master sounds good

CI is green, so merging as a hotfix


In the plugin, set up static route for multicast

Fixes #1752

I added an option to disable, matching #1741.

This looks fine, but I haven't tested it locally due to the rigmarole of setting up a cluster store - will do so once this is rebased on mesh moad. We should also extent test/195_no_multicast_route_1_test.sh to include this...

Rebased and added test


Size mismatch in class function TNetData.ExtractHeaderInfo in UNetProtocol.pas

In:
class function TNetData.ExtractHeaderInfo(buffer : TExtendedStream; var HeaderData : TNetHeaderData; DataBuffer : TExtendedStream; var IsValidHeaderButNeedMoreData : Boolean) : Boolean;
Following line has a size mismatch:
	buffer.Read( HeaderData.error_code, 2);

In reality error_code is integer which is size 4 !
Not reading all 4 bytes could potentially cause garbage in (higher bytes?) of this error code.

 HeaderData.error_code type is 4 bytes lenght, but is initialized to 0 so reading only 2 bytes does not produce a bug
But, totally agree with you that better is to change  HeaderData.error_code type to Word or similar


Redis bibdata qa

resolves https://github.com/pulibrary/bibdata/security/dependabot/67
related Pr: https://github.com/pulibrary/princeton_ansible/pull/4267

Do the following on bibdata-staging unless this one is resolved first https://github.com/pulibrary/princeton_ansible/issues/4355


Teal interpreter

TEAL Interpreter for arithmatic and arg opcodes

execute(..) to process each logic object
Added opcode class for len, +, -, /, *, arg_0, arg_1, arg_2, arg_3.
Added TealError (took reference from BuilderError).
Added tests for stack, len, Add, arg_[N]. (Will be adding more tests for arithmatic opcodes)

Few Points (would like to hear suggestions) :-

Max stack capacity is 1000.
I have used BigInt instead of regular int/number because TEAL supports uint64 and max integer value for js is 2^53 - 1.
Arguments as considered to be an array of (string | number). Should this be array of Uint8Array[]?

Max stack capacity is 1000.

Yes - we need to make an error if the stack will grow beyond 1000. So you need to check the stack after each operation.

I have used BigInt instead of regular int/number because TEAL supports uint64 and max integer value for js is 2^53 - 1.

Very good. Please also check for overflows. so after each operation we need to check if the value is not bigger than 2^64.

Arguments as considered to be an array of (string | number). Should this be array of Uint8Array[]?

No, let's define a type for that:
type StackElem = string | number;
let stack: StackElem[]

I think we should never use number in the stack. Since we must operate on uint64 numbers, and Node.js can't handle them, then all values must be string. So, the stack must be Stack<string>.
While executing operations we will need to parse stack elements and check if they are correct, example:
class Add {
  const op = "add"
  ...
  execute ( ... ) {
  let a = parseNum(this.op, stack.pop());  // this function will return BigInt
  let b = parseNum(this.op, stack.pop());
  ...
  }
 }

I think we should never use number in the stack. Since we must operate on uint64 numbers, and Node.js can't handle them, then all values must be string. So, the stack must be Stack<string>.
While executing operations we will need to parse stack elements and check if they are correct, example:
class Add {
  const op = "add"
  ...
  execute ( ... ) {
  let a = parseNum(this.op, stack.pop());  // this function will return BigInt
  let b = parseNum(this.op, stack.pop());
  ...
  }
 }

@robert-zaremba by the current design the stack stores - stack<string | bigint>, so we're operating on bigint and not number. Although i agree that keeping just string in stack would be better, but this will create some complications. Eg.
args = [ "123", 123 ] // arg[0] = string "123", arg[1] = number 123

Now if we load agrs into stack, it looks like (with string) :-
stack = [ "123", "123" ]

consider opcode + on this stack (both will pe parsed and added, but it should have panicked)
consider opcode ==, we will compare two string and return true, but it should have panicked.

OK, you are right. But when creating BigInt we should never use number. Only strings.

Ok, understood. Updating..


Fix gettext arm build

HAVE_STRDUP implies using of strdup, which is deprecated, and produces warnings as errors.
If I specify to undefine HAVE_STRDUP, gettext uses it's own manual implementation of strdup.
Another approach would be to replace using of strdup to strdup_s, which IMO needs more efforts regarding to patches and so on.

You can also add #define _CRT_NONSTDC_NO_WARNINGS to disable such warnings. That would work for x86/x64-uwp too.

BTW the gettext fix is not enogh. When compilation succedes, linking fails:
         langprefs.obj : error LNK2019: unresolved external symbol RegOpenKeyExA referenced in function _nl_language_preferences_win32_95 [G:\dev\vcpkg-dev\buildtrees\gettext\arm-uwp-rel\gettext-runtime\libintl.vcxproj]
         langprefs.obj : error LNK2019: unresolved external symbol RegQueryValueExA referenced in function _nl_language_preferences_win32_95 [G:\dev\vcpkg-dev\buildtrees\gettext\arm-uwp-rel\gettext-runtime\libintl.vcxproj]
         langprefs.obj : error LNK2019: unresolved external symbol RegCloseKey referenced in function _nl_language_preferences_win32_95 [G:\dev\vcpkg-dev\buildtrees\gettext\arm-uwp-rel\gettext-runtime\libintl.vcxproj]
         langprefs.obj : error LNK2019: unresolved external symbol EnumResourceLanguages referenced in function _nl_language_preferences_default [G:\dev\vcpkg-dev\buildtrees\gettext\arm-uwp-rel\gettext-runtime\libintl.vcxproj]
         langprefs.obj : error LNK2019: unresolved external symbol GetModuleHandle referenced in function _nl_language_preferences_default [G:\dev\vcpkg-dev\buildtrees\gettext\arm-uwp-rel\gettext-runtime\libintl.vcxproj]
         localename.obj : error LNK2019: unresolved external symbol GetThreadLocale referenced in function _nl_locale_name [G:\dev\vcpkg-dev\buildtrees\gettext\arm-uwp-rel\gettext-runtime\libintl.vcxproj]
         G:\dev\vcpkg-dev\buildtrees\gettext\arm-uwp-rel\gettext-runtime\Release\libintl.dll : fatal error LNK1120: 6 unresolved externals [G:\dev\vcpkg-dev\buildtrees\gettext\arm-uwp-rel\gettext-runtime\libintl.vcxproj]

BTW the gettext fix is not enogh. When compilation succedes, linking fails:

Odd, my local build ends with:

Installing package gettext:arm-uwp... done

About _CRT_NONSTDC_NO_WARNINGS, I'll repush fix

Yep, I've messed with my local buildtree copy.

Add missing patch

Thanks for the PR! It works great 🥇


Document RBAC kinds required for different use cases

We need to document that someone who is working with collections (activating, upgrading, etc) will require RBAC authority to create/modify the kind Collection. Likewise, someone wanting to configure a Kabanero instance will need access to the Kind Kabanero.

@kyleschlosser Kyle, is this still needed or has it been covered with existing doc?

@mingcyu WRT Kind Collection, I believe we've decided that these should be manipulated either by the Kab operator directly, or with the Kabanero CLI (which uses a Git login).  I don't think any documentation is required for this part.
WRT Kind Kabanero, I believe the install instructions say to run as cluster-admin.  However there's no reason why this step could not be done as someone with a lower level of access.  I can update this as I go thru the documentation for 0.3.0.  Please leave this open for now.

@kaczyns Hi Tim, so for the second paragraph do you require ID support/resources to review?  If so can you point us to where you might be working?

@mingcyu I'm working in kabanero-io/docs#194


New Mudi Firmware 4.3.9 wich includes important Securtiy Updates

There is a new Firmware that fixes various vulnerability the most problematic  https://nvd.nist.gov/vuln/detail/CVE-2023-46454
I tested blue-merle on with a Mudi 750 V2 on 4.3.9. Besides the Firmware Version check that fails for a fully automated install it works as expected (Tested: Button, Webinterface, ClI) added a fix for the firmware check in this PR #28

hello, i have difficulties installing blue merle on the latest version... Maybe you could explain how to install it without fully automated install?

works for me
root@GL-E750:/tmp# opkg install blue-merle*.ipk
Installing blue-merle (2.0.0-0) to root...
Installing coreutils (9.0-2) to root...
Downloading https://fw.gl-inet.com/releases/v22.03.4/packages-4.2/ath79/packages/coreutils_9.0-2_mips_24kc.ipk
Installing coreutils-shred (9.0-2) to root...
Downloading https://fw.gl-inet.com/releases/v22.03.4/packages-4.2/ath79/packages/coreutils-shred_9.0-2_mips_24kc.ipk
Installing libpython3-3.10 (3.10.9-1) to root...
Downloading https://fw.gl-inet.com/releases/v22.03.4/packages-4.2/ath79/packages/libpython3-3.10_3.10.9-1_mips_24kc.ipk
Installing python3-base (3.10.9-1) to root...
Downloading https://fw.gl-inet.com/releases/v22.03.4/packages-4.2/ath79/packages/python3-base_3.10.9-1_mips_24kc.ipk
Installing libffi (3.4.2-2) to root...
Downloading https://fw.gl-inet.com/releases/v22.03.4/packages-4.2/ath79/packages/libffi_3.4.2-2_mips_24kc.ipk
Installing libbz2-1.0 (1.0.8-1) to root...
Downloading https://fw.gl-inet.com/releases/v22.03.4/packages-4.2/ath79/packages/libbz2-1.0_1.0.8-1_mips_24kc.ipk
Installing python3-light (3.10.9-1) to root...
Downloading https://fw.gl-inet.com/releases/v22.03.4/packages-4.2/ath79/packages/python3-light_3.10.9-1_mips_24kc.ipk
Installing python3-pyserial (3.4-2) to root...
Downloading https://fw.gl-inet.com/releases/v22.03.4/packages-4.2/ath79/packages/python3-pyserial_3.4-2_mips_24kc.ipk
Version 4.3.9 is *probably* supported

You have a GL.iNet GL-E750, running firmware version 4.3.9.
blue-merle has only been tested with GL-E750 Mudi Version 4.3.8.
The device or firmware version you are using have not been verified to work with blue-merle.
Would you like to continue on your own risk? (y/N): y

So blue merel works with the v2? What card is being used or did u uses that it worked on?

Why is this closed? I asked a question

Yes. This is exactly why the issue was closed.
Please read the friendly manual.

It is not giving me the message at the end "Would you like to continue on your own risk? (y/N): "

are u using the mudiv2 @dzigitaz


Claim Trades

Hello, these are the last two bugs that I found then I think the GTS will work perfectly

Tax is not applied
In Claim Trades menu, the pokemon is not refresh.

Video : https://drive.google.com/file/d/1JyNXFa87U0zrynya2l2Nfk0TAoo01QrY/view?usp=sharing
If I did not understand the principle of the tax, it should be applied as soon as it goes on sale to prevent players from putting anything on the GTS and not on purchase.
thanks for your jobs.

Fixed in latest


Support for Generics

Hey, wondering if generics are supported in this library and if not if there are plans to support this.
Right now when I try to do:
static interfaces: InterfaceDeclarationStructure[] = [
    {
      name: 'ISegment<T>',
      methods: [
        {
          name: 'loadRawSegment<T>',
          parameters: [
            {
              name: 'segment',
              type: 'TRawSegment'
            }
          ],
          returnType: 'T'
        }
      ],
      isExported: true
    }
  ];

I get a cryptic error:
Could not find file: 'tsSimpleAstTempFile.ts'
Thanks!

I have to look into that tsSimpleAstTempFile.ts bug (opened #135). I've seen that too when things go wrong.
Use the typeParameters property. A name doesn't include the type parameters:
name: 'ISegment',
typeParameters: [{ name: "T" }]

Great thanks, that worked perfectly.


Integrate NAO v6

NAO v6 uses the Naoqi v2.8 that is backward compatible with NAO v5 using Naoqi v2.1.4. Therefore we do not have to make changes in the HAL. However, for successful integration we have to modify the following:

[x] NAO-USB program:

[x] Set the environment variables while running the user's created program
[x] Modify the update process of the HAL (separate the HAL for NAO v5 and v6)

[ ] Modify the NAO Client:

[ ] Remove the monkey patch for the NAO v6,
[ ] Modify the update process of the HAL (separate the HAL for NAO v5 and v6)

[x] Modify the server to accepts different versions of naoqi for the update process of the HAL

We would need to split the NAO client this one into two, one for V5 with all needed libraries and the other one for V6 that would be small and build a release for two different versions, because in the app store it is possible to download the app for specific NAO version and it would be nice to make the app not contain unneeded files. We can have two branches for two versions.


Relative view to current buffer

Is it possible to view the current directory when opening :Vaffle like vim-vinegar or vim-dirvish?
I've tried (unsuccessfully):
let g:vaffle_auto_cd = 1

Btw fantastic plugin, great work and thanks :heart:

I've just figured out that I could do `:Vaffle %e' as a shortcut.


Add tooltip to truncated bookmark titles

Fixes #606
This is what it looks like with a custom hover over a link that has an overly long title.

Light theme.

Thank you!


explicit secrets removed from jobs

Changes

Let jobs use the inherited environment and secrets from calling workflows

should be merged before knative-sandbox/.github/pull/174

/lgtm
/approve

/check-cla

/approve

something is going on with GitHub/tide - it's not happy with my override.
Fabian will make a new PR


Architecturecraft Architect's Sawbench is slightly harder to acquire than intended

Version 0.9.4-beta
Despite being unlocked in the questbook upon acquisition of iron, the Architect's Sawbench cannot be crafted immediately because of the wooden pressure plate in its recipe. Ironwood currently cannot be turned into a wooden pressure plate, so access is artificially barred until other wood types are available.

already resolved for next update


Can't start server because of permission denied

I use the following command to create the server:
docker run -d \
   --name=7d2d \
   -e PUID=1000 \
   -e PGID=100 \
   -e TZ=Europe/Zurich \
   -v /sharedfolders/docker/config/7d2d/steam:/steamcmd/7dtd \
   -v /sharedfolders/docker/config/7d2d/game:/app/.local/share/7DaysToDie \
   -p 26900-26902:26900-26902 \
   -p 26900-26902:26900-26902/udp \
   didstopia/7dtd-server

This leads to creation of two folders game and steam. The game folder has the right user permissions, while the steam folder has root:root. This leads to the error:

/app/start.sh: line 116: /steamcmd/7dtd/7DaysToDieServer.x86_64: Permission denied

Both volumes need to be set to the same user id (PUID) and group id (PGID).

Yes they are. But still the same error

Just to be sure, did your run chown -R to apply the permissions recursively?
I'll be deploying a potential fix upstream to the base images, which should fix this automagically. I'll let you know when the fix is live.

Okay, can you pull the latest version and give that one a go? It should now always fix the permissions on startup, so long as you're not using any custom container paths, outside of /steamcmd and /app.

I will try it tonight. Thanks

Hmm, I still have the same error. Is there any way to get more error information? I am trying to run it on an OMV host.

Could you try deleting the volumes/folders again? Both game and steam should now be under the non-root user, and the permissions are set whenever the container starts. Additionally, could you try running the container as root, if the previous attempt fails? Just sudo docker run ... should do, just to rule out anything else.

I will try it tonight. Sorry for the late reply.

So I tried it again tonight. First I deleted everything.

Have you tried without creating the folders manually? Because Docker should ideally be in charge of creating them, as then it could also set the permissions accordingly.

I might have found the issue. cat /etc/mtab gives me:
/dev/md0 /home/steam/7d2d/server ext4 rw,noexec,relatime,stripe=384,jqfmt=vfsv0,usrjquota=aquota.user,grpjquota=aquota.group 0 0 /dev/md0 /home/steam/7d2d/save ext4 rw,noexec,relatime,stripe=384,jqfmt=vfsv0,usrjquota=aquota.user,grpjquota=aquota.group 0 0
I think the problem is noexec

It's possible, but then noexec should be coming from the filesystem/partition mount flags and there's not much Docker can do about it.

Yeah, OMV does this for the data partition. So I guess it's my error. Sorry.

No worries! As a last resort, you could try again, but this time with PUID=0 and PGID=0, which would effectively run the container as root again.


Parallel Python execution for tool completion

Pull Request Summary
with some sample data (1000 prompts). on my devbox (96 CPU cores), but since i used threadpool to start subprocess i think it still might be slowed down by GIL to start processes, probably not high util for the 96 cores
467s total, 283s tool use
vs
without this change 862s total, 687s tool use
Test Plan and Usage Guide
How did you validate that your PR works correctly? How do you run or demo the code? Provide enough detail so a reviewer can reasonably reproduce the testing procedure. Paste example command line invocations if applicable.

took a bit more look into this @Georgepu1 15/1000 output texts have changed, i manually checked 5 of them and i don't think python code execution results are different. the differences appear to be some randomness in sampling that sentences in both cases made sense to me


Special-case Vec when returning from a script

When a vector is returned from a script, instead of using retd to return the stuct Vec itself (which will be disallowed soon anyways because Vec will contain a raw_ptr - see https://github.com/FuelLabs/sway/issues/2551), use retd to return the actual data that lives on the heap.

So https://github.com/FuelLabs/sway/pull/3288 (combined with https://github.com/FuelLabs/fuels-rs/pull/743) covers the basic uses case of returning heap data from a script. There are certainly more complex cases that we would like to support such as returning a tuple with two vectors, etc. However, for now, we don't need to worry about them I think so I will close this issue.


[WIP] add option for sorting iterator by the last added to the db.

@mafintosh this is just a quick stab at sorting the stream by latest added node.
This is not super efficient at the moment, as for each pop it is sorting the worker's stack. This could and should be optimised by checking if a sort is needed when pushing a new value to the stack - and only sorting if its needed. I started implementing this optimisation but it requires quite a lot of changes to deal with pending. So figured its best to check with you first, to gage if this method of sorting is heading in the right direction.

@mafintosh so this is an optimised version that actually works.
I have included two options. One built on top of your iterator and the other as an external operator.
Both are laboriously slow on large datasets For example - 10,000 keys split over two feeds, with 2000 overlapping keys - takes 20s approximately on the version built on top of your iterator, and 24 seconds using my older iteration method. By comparison sorting by hash takes just 5.6s.
This is the test I was using to benchmark
tape('iterator sorted via latest (large set)', (t) => {
  const expected = []
  const db1Keys = []
  const db2Keys = []

  for (var i = 0; i < 10000; i++) {
    var key = i.toString()
    if (i < 6000) {
      db1Keys.push(key)
    }
    if (i > 4000) {
      db2Keys.push(key)
    }
    expected.push(key)
  }

  create.two(function (db1, db2, replicate) {
    console.time('iteration')
    run(
      cb => put(db1, db1Keys, cb),
      replicate,
      cb => put(db2, db2Keys, cb),
      replicate,
      cb => testIteratorOrder(t, db1.iterator({ latest: true }), expected, 'latest', cb),
      // cb => testIteratorOrder(t, db2.iterator({ latest: true }), expected, 'latest', cb),
      () => {
        console.timeEnd('iteration')
        t.end()
      }
    )
  })
})

What are your thoughts? What do you think is the best way to approach this? Are the changes needed to implement it as an option of the default iterator too complex - is it worth breaking it into its own iterator? Any thoughts on possible ways to speed it up?

I am slow moving on this one - but will look at rewriting these to be more inline with @mafintosh's https://gist.github.com/mafintosh/08c29ff876f0444b7270cf8335cbf650


[FIX] Treat vfwe as an array of floats for KDA

Closes #361
ref #350, #343

Changes proposed in this pull request:

change vfwe array to float

I'll link to the relevant failed test in #343 when it's available.

The change looks good to me, but do you want to add a test or something to cover this situation? I think a simple data type check for the relevant maps would be good. Probably for all of the CBMA estimators though.

added one test for the KDA cbma estimator, and #343 (and extensions from that pull request) will catch these errors, at least, that pull request is how I found this issue.
(p.s., can this pull request also count for hacktoberfest? 🥺)

Merge commits mess up the codecov step in CI, but this PR looks good so I'm going to merge.


Add functionality to whitelist and blacklist commands

Previously, the whitelist and blacklist commands could only whitelist/blacklist clients. Now, their functionality has been extended to all users to also list out all whitelisted/blacklisted clients through these commands.
Fixes #151
Fixes #149

Closes #151

LGTM


Fixes and improvements to Static API

Adds AwaStaticClient_GetResrouceInstanceValue implementation which gets the pointer to a resource instance.
Adds tests for AwaStaticClient_GetResrouceInstanceValue.
Moves Static API tests out into separate files.
Fixes invalid read in when observe does a read.

Can one of the admins verify this patch?


Implement rolling skew and rolling kurtosis methods

pandas has implementations for rolling skew and rolling kurtosis. The implementations can be seen here.

Done


Update main.js

Why ya Delate the scratch follower messenger?

Hey, it is because the Scratch Team does not allow Follower Messengers. Sorry for not asking you first.

Okay. Can we make somethibg else? Like a stats website or A Api that allows
you to find more information or a search engie
On Sep 10, 2017 8:03 PM, "csf30816"<EMAIL_ADDRESS>wrote:

Hey, it is because the Scratch Team does not allow Follower Messengers.
Sorry for not asking you first.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ScratchFun/scratcher-info/pull/1#issuecomment-328384256,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AUBvYYFW-_cm1rxDeH2SQ2wB7VGjS2Elks5shHjQgaJpZM4PSdxl
.

Can i join Scratchfun


Handle rawTerm wrapper from the simplifier

The LLVM backend has added a new way of handling non-symbol terms across API boundaries; previously when doing so we added a spurious injection into KItem to non-symbol terms when returning them to callers. This could be worked around, but was not completely sound.
Clients that call backend binding APIs that use the new rawTerm symbol must be aware of it when deserializing or parsing binary or textual KORE. For the Python bindings, the deserialization logic is implemented here directly in C++.
The intended semantics are to perform the following rewrite unconditionally during parsing or deserialization:
rawTerm{}(inj{S, SortKItem{}}(X)) → X

where the sort variable S is the real sort of the term X.
Blocking: https://github.com/runtimeverification/llvm-backend/pull/931
Related:

https://github.com/runtimeverification/llvm-backend/pull/907
https://github.com/runtimeverification/llvm-backend/pull/905

Further discussion on Slack: https://runtimeverification.slack.com/archives/CC360GUTG/p1702578768476599

@gtrepta to send some additional context over to @jberthold

You can reproduce the failure introduced by the rawTerm wrapper by doing the following:

Build K on the latest develop branch, but with the simplify_rawTerm branch checked out in the llvm-backend submodule (llvm-backend/src/main/native/llvm-backend)
add k-distribution/bin to your PATH
in hs-backend-booster/src/main/native/hs-backend-booster run stack test :llvm-integration

You can also build with kup by doing kup install k --override llvm-backend 77f6e98. But, I'm not sure how to run the booster's llvm integration tests with it. I get a glibc linking error when I try it because the interpreter library gets built against the nix environment, and stack tries to use it against the host environment.

Thanks @gtrepta .
Preparing the booster code in advance means that I have to make two PRs, one to handle the newly returned rawTerm value and another to clean up the previous workaround once the LLVM change is present in K master. But that's fine.


Run 'yarn upgrade'

📦 Pull Request
Run yarn upgrade
🗜 Versioning
(Check one!)

[x] Patch: Bug Fix?
[ ] Minor: New Feature?
[ ] Major: Breaking Change?

✅ Fixed Issues

No associated issue (chore)

🚨 Test instructions
None
⚠ Update CHANGELOG.md

[x] I have updated the Upcoming Changes section of CHANGELOG.md with context related to this Pull Request.

:rocket: PR was released in<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>:rocket:


Adding troubleshooting guide

This is initial version for troubleshooting guide, issue: #331
It is expected to be iteratively improved in the future.

Thanks for the review @javaducky! :raised_hands:


Make none dialog changing state type

When state doesn't have new choices, inherit choices from previous state

Solved in editor ( json export will have them hardcoded )


[Google Chat] Add support for Performance Alerts

Implement support for Performance Alerts: https://firebase.google.com/docs/functions/beta/alert-events#handle-performance-alerts

Request for information!
Need sample data from app distribution events to see what kind of information is set in e.g. subject and data


Move usage doc from README to wiki

FYI: Build failed because of report submission to Coveralls API failed with HTTP status 500


matching and tmatching trigger a ton of styleCheck hints

/cc @haxscramper
tests/tmatching.nim(1874, 11) Hint: 'doASsert' should be: 'doAssert' [Name]
a fix for this issue should also include this change:
switch("styleCheck", "hint")
=>
switch("styleCheck", "error")

in tests/config.nims

done

Using error not possible - stdlib fails.
  Compiling /home/runner/work/fusion/fusion/fusion/tests/tmatching (from package fusion) using c backend
Error: /home/runner/work/fusion/fusion/nim/lib/std/private/underscored_calls.nim(43, 21) Error: 'nnkArgList' should be: 'nnkArglist'
       Tip: 5 messages have been suppressed, use --verbose to show them.

https://github.com/nim-lang/fusion/pull/77/checks?check_run_id=2205625601#step:7:58

thanks!

Using error not possible - stdlib fails.

that's nasty, and relates to: https://github.com/nim-lang/Nim/pull/16176#issuecomment-737442088
IMO we should do the suggested fix there, and special-case stylecheck to allow both nnkArgList and nnkArglist, given that these are canonical:
nnkStmtList
nnkStmtListExpr
nnkStmtListType
nnkRecList
nkArgList (one n)

=> https://github.com/nim-lang/Nim/pull/17529

reopening, i did the mistake of writing unblocks nim-lang/fusion#77 which will fix nim-lang/fusion#82 so it aut-closed this unintendedly


why after add new modules ,windows service will change the path to my computer localhost

Please provide some repro steps. This doesn't look like it's related to Orchard.


Error when using without full install (unplugin or components)

Installation:
`
import { AnuComponentResolver } from 'anu-vue'
Components({
extensions: ['vue'],
include: [/.vue$/, /.vue?vue/],
dts: 'src/types/components.d.ts',
resolvers: [
AnuComponentResolver(),
],
}),
`
Error with components ABtn, ASelect and may be others

If install as full thats problems dosnt have

Can you run anu this repo: https://github.com/jd-solanki/anu-demo ?

Can you run anu this repo: https://github.com/jd-solanki/anu-demo ?

https://github.com/evdevru/anu-demo
Check demo repo

Can you please share your repo?

I will check this tonight!
Thanks for reporting ☺

Hi 👋🏻
Sorry for being late. Actually, I forgot to update the docs. When you use unplugin-vue-component, you shouldn't remove the anu plugin registration.
Please use below code:
createApp(App)
    .use(anu)
    .mount('#app')

I have updated the anu-demo repo, please checkout this commit.
Thanks for reporting.


xenops-increase-size changes forgotten after reveal

Currently, I can use xenops-increase-size to make the size of the rendered TeX bigger, and it works quite well. The problem is, if I enter a snippet and reveal it to reveal the math command, when it renders again it goes back to the default size, not the increased size. I have to do "xenops-increase-size" followed by "xenops-decrease-size" to restore all the snippets back to their usual size.
Is this a known bug? Is something just configured wrong for revealing?

Hi @JoeyEremondi. As a meta comment -- I'd love to do more work on Xenops but recently I haven't been writing any math (I made it for myself when I was taking time out to study) -- and so it has been a bit hard to justify the time.
If I remember correctly, this was a known bug. Basically here
https://github.com/dandavison/xenops/blob/4d75c1cd5ee7afba62af3a39a1f43432b295c29c/lisp/xenops-math.el#L356-L366
this function takes in the factor by which to change size, but I think what was needed was some sort of global/default factor which would be honored on each render automatically; and then the xenops-increase-size function would mutate the global factor variable, or something along those lines. So this would give a uniform multiplicative display scaling of all images over and above whatever the default size would be based on the latex source.
If you have the slighted temptation to look into fixing it, that would be fantastic, and I can offer you my claim that the code is fairly clean and that it's fun to do xenops development, and obviously that I'd be happy to discuss it.

Or perhaps the problem is the image caching? That when we change size, we need to invalidate the entries in emacs's image cache so that they are re-rendered with the new size.


Update pyodide to 0.23.0

https://blog.pyodide.org/posts/0.23-release/

Codecov Report

Merging #520 (c8bbda1) into main (1276e37) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head c8bbda1 differs from pull request most recent head b294ddf. Consider uploading reports for the commit b294ddf to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #520   +/-   ##
=======================================
  Coverage   94.80%   94.80%
=======================================
  Files          93       93
  Lines       12259    12259
  Branches       25       25
=======================================
  Hits        11622    11622
  Misses        630      630
  Partials        7        7

Continue to review full report in Codecov by Sentry.

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


Fix embed code in examples

Fixes #149
Found this was a problem in each of the examples I tested.
I explored modifying the parameters sent to elm make to see if there was a way to compile a Elm module as a library (so that we could write var Elm = require('./src/Main.elm') rather than having to use a property of the import var Elm = require('./src/Main.elm').Elm), but I was unable to find any such option.

I'd love to see this get merged. The current examples are broken for Elm 0.19, and if this project supports 0.19 its examples should be up-to-date.


checkout: optimize lost hardlink search

Speeds up checkout for 30K files from 6sec to 3.5sec
Signed-off-by: Ruslan Kuprieiev<EMAIL_ADDRESS>

Hm, something is wrong with the windows, will investigate in the morning.

Closing for now, need to use fileID instead of inodes on windows.


Changing names of months

Hey,
is there a feature to easily change the names of the months to use this amazing tools with in a other language.
Thx :)

I have the same problem!

Hey, is there a feature to easily change the names of the months to use this amazing tools with in a other language.
Thx :)

You can change the locale for the language, like this:
import React, { useState } from 'react';
import DtPicker from 'react-datepicker';
import pt from 'date-fns/locale/pt-BR';

const DatePicker = () => {
  const [startDate, setStartDate] = useState(new Date());
  return (
    <DatePicker
      selected={startDate}
      onChange={(date) => setStartDate(date)}
      locale={pt}
     />
  );
};

But for me, I'd like to capitalize the month names, usually in portuguese we write alone month names capitalized, it bugs me a little bit.


Support refresh in ES 5.y.z

https://www.elastic.co/guide/en/elasticsearch/reference/5.0/docs-refresh.html#docs-refresh
This is a nice new option in ES that allows you to customize how fast results appear in ElasticSearch queries. Please expose the ability to configure passing ?refresh=X when adding/updating documents to indexes

Setting refresh to true will put more load on the Elasticsearch server. Is that acceptable in your use case? Or were you hoping to go the other direction, defer indexing to reduce ES load?

After a bit more research and though, it looks like this probably isn't something that makes sense for the connector. As noted in the description of the IMMEDIATE refresh policy:

This refresh policy does not scale for high indexing or search throughput
but is useful to present a consistent view to for indices with very low traffic.

If the goal is to minimize the time between when a document is written to Couchbase and when it is searchable in Elasticsearch, then forcing a refresh after every write does not help in the long run. Even though the first batch of documents might be searchable more quickly, subsequent batches actually take longer to appear in search results just because the forced refresh acts as a bottleneck that significantly delays future indexing.
If the goal is to have consistent search results (that is, to write a document in Couchbase and then make an Elasticsearch query that returns the document), forcing a refresh doesn't solve that problem either. The time between when a document is written to Couchbase and when the document reaches the connector to be indexed can vary based on the current replication load. The best guarantee the connector can offer is that the document will appear in Elasticsearch "eventually." Making it visible in search results a little bit sooner ("eventually - 1") doesn't offer stronger consistency.
tldr; Forcing a refresh is the solution to a different problem.

Sorry, I should have closed this one. We had some record discrepancies where XDCR didn’t have the current records in couchbase yet on UPDATE. We built a system that kept track of the changes made in the UPDATES and merged ES results with up to date records from couchbase.


Need route for times a resource is clicked

When the front end is created, we're going to track the popularity of a resource by tracking how many times people click the link to open that resource. Eventually, we're also going to track who specifically clicks on the resource so that we don't increment times_clicked if they have already clicked the resource in the past, but that is beyond the scope of this issue.
The route should be PUT api/v1/resources/<id>/times_clicked and it should return the updated resource with the times_clicked value incremented. Please write a test for this in test_routes.py.

Closed via #125


fix: SafeTransferLib tests

Overview
In SafeTransferLib's tests, we don't currently exclude the hardhat console or vm addresses from the non-contract tests. As pointed out in #119, this can sometimes cause the fuzz tests to fail.
Solution
Exclude the hardhat console or vm addresses from the non-contract tests. Bonus points for replacing the parameter restrictions with vm.assume so we get full advantage of all fuzz runs.

This issue also affects testFuzzTransferETH(...).
Failing tests:
Encountered 1 failing test in test/utils/SafeTransferLib.t.sol:SafeTransferLibTest
[FAIL. Reason: ETHTransferFailed() Counterexample: calldata=0xb91b6ee7000000000000000000000000000000000000000000636f6e736f6c652e6c6f670000000000000000000000000000000000000000000000000000000000000492000000000000000000000000000000000000000000000000000000000000006000000000000000000000000000000000000000000000000000000000000000200000000000000000000000000000000000000000000000000000000000000a0a, args=[0x000000000000000000636F6e736F6c652e6c6f67, 1170, 0x0000000000000000000000000000000000000000000000000000000000000a0a]] testFuzzTransferETH(address,uint256,bytes) (runs: 179, μ: 41692, ~: 43294)


Is there an interface in dreamview plus that can display the vehicle SOC on the page?

I want to display the vehicle soc value on the dreamview plus page, is there an interface in dreamview plus that can display the vehicle SOC on the page?

do you mean Vehicle Security Operations Center? Dreamview already has an event monitor to display multi-level messages about the module, like warning, error, delay so on.
we're adding more functional security monitor, and maybe you can explain your requirements in detail, or give a design document

I mean soc(State-of-Charge) value of vehicle battery, it can be read on the chassis via canbus,  I want to display it on dreamview plus page, is there an interface I can use? Looking forward to your reply.

do you mean Vehicle Security Operations Center? Dreamview already has an event monitor to display multi-level messages about the module, like warning, error, delay so on.
we're adding more functional security monitor, and maybe you can explain your requirements in detail, or give a design document

I mean soc(State-of-Charge) value of vehicle battery, it can be read on the chassis via canbus,  I want to display it on dreamview plus page, is there an interface I can use? Looking forward to your reply.

do you mean Vehicle Security Operations Center? Dreamview already has an event monitor to display multi-level messages about the module, like warning, error, delay so on.
we're adding more functional security monitor, and maybe you can explain your requirements in detail, or give a design document

autoDrivingCar
Vehicle related information is in autoDrivingCar, which is a Object message, the proto type you can find in https://github.com/ApolloAuto/apollo/blob/0026d7ee9ebdb772818c741e6b9220f9412a94ff/modules/common_msgs/dreamview_msgs/simulation_world.proto#L77
how to get the battery_percentage

Here is an example about how to get speed.
https://github.com/ApolloAuto/apollo/blob/0026d7ee9ebdb772818c741e6b9220f9412a94ff/modules/dreamview_plus/frontend/packages/dreamview-core/src/components/panels/DashBoard/index.tsx#L71-L77

so you can add below method to get battery_percentage,
            <SignalAndGear
                color={dashBoardState?.trafficSignal?.currentSignal}
                gearPosition={dashBoardState?.autoDrivingCar?.gearLocation}
                batteryPercentage={dashBoardState?.autoDrivingCar?.batteryPercentage}  #-------> add
            />

Next, display info in below code
https://github.com/ApolloAuto/apollo/blob/0026d7ee9ebdb772818c741e6b9220f9412a94ff/modules/dreamview_plus/frontend/packages/dreamview-core/src/components/panels/DashBoard/SignalAndGear/index.tsx#L12-L21

    <div className={classes['dash-board-signal-gear']}>
        <Signal signal={props?.color as SignalEnum} />
        <Gear gearPosition={props?.gearPosition} />
        <Battery percentage={props?.batteryPercentage} />  #-------> add
    </div>

Thanks for your reply! I will try it in my project.

Thanks for your reply! I will try it in my project.

您好，请问您改完以后有生效吗，我刷新了网页后还是和原来一样

Thanks for your reply! I will try it in my project.

您好，请问您改完以后有生效吗，我刷新了网页后还是和原来一样

最近在忙别的事，按我的理解改完需要编译dreamview_plus的前端代码才会生效

Thanks for your reply! I will try it in my project.

您好，请问您改完以后有生效吗，我刷新了网页后还是和原来一样

最近在忙别的事，按我的理解改完需要编译dreamview_plus的前端代码才会生效

我这边已经显示出来了，除了上述的修改，还需要新建两个对应的文件 以及需要去看懂前端的dreamview_proto_bundle 就可以去把他显现出来


Fix feature gates that don't match the code (KEP-4192)

Ref: https://github.com/kubernetes/enhancements/issues/4192
PR - https://github.com/kubernetes/kubernetes/pull/123344
Follows up on: https://github.com/kubernetes/website/pull/45757#discussion_r1548110247
/cc @nilekhc @deads2k @jpbetz @enj
/milestone 1.30
/sig docs
/sig api-machinery

/lgtm

Thanks for the fix!
/approve


Suppress EntityFramework false positives.

Fixes Issue
Fixes: https://github.com/jeremylong/DependencyCheck/issues/90#issuecomment-278581196 which I saw in my own scans.
Description of Change
Suppress EntityFramework false positives.
Have test cases been added to cover the new functionality?
No.

Thanks!


Snapshots that require life-cycle methods for HOC

I am using enzyme for testing after making a change from react-test-renderer.
Initially I want to snapshot test (pure-html) all components and once complete move onto more detailed tests.
My issue is mount is going to be great for more detailed testing but I do not see why render which returns the html does not also use the life-cycle methods as these are needed with HOC or with redux to properly render a component.
Related to #42
&
#1050

I'm not sure I understand your issue perfectly.
Are you saying that when you mount your component, your lifecycle methods are not called? It sounds like an Enzyme issue, enzyme-to-json is literally just converting Enzyme wrappers to a format compatible with Jest snapshots so if the lifecyle methods are not called on mount or setState it is probably an Enzyme issue.


Phone doesn't connect and gets forced into charging mode

After connecting the phone (Xiaomi POCO F2 Pro) to the Mac (M1 Max) I immediately set it to file transfer mode and then refresh OpenMTP. After clicking the refresh button in open MTP, the file transfer mode directly switches to charging mode on the phone and openMTP gives an error. The list of internal storage files never appears and if I press refresh again the same thing happens.
Process:

connect phone to Mac through USB
set phone to file transfer mode
open openMTP
press refresh button
file transfer mode immediately jumps to charging mode on phone without pressing anything, it's like openMTP is forcing the phone to charging mode over and over again.

This process repeats over and over again and I can never access the internal storage.
This never happened to me on previous versions.
If you need more info please let me know so I can provide it, thanks.

Any feedback on this?

What version of OpenMTP are you using?
Could you try a good quality usb cable?(Imp)
Could you try these steps : https://github.com/ganeshrvel/openmtp/issues/276#issue-1447067326

Lastest public, 3.2.10.

Quitting the preview app fixed it seems. Thx!

Closing this issue

Would like to reopen this issue because it's still happening even after trying the steps in276.


Add generator-create-redux-app into the starter kits list

generator-create-redux-app

Hello @jonidelv!
As that page is no longer present in the docs I will close this PR as outdated.
Thank you!


what does these different values actually mean?

What system policy?  Where do I set it?
How can the Revoked event have an argument with a value of Resumed? Can the application be stopped without receiving the Revoked event, and then first when it is restarted it is told about it??

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

ID: b57334b4-96d1-4285-bb3a-d0197cb3a0b6
Version Independent ID: c3e46f1d-ff41-f213-10d8-b5ca414413dc
Content: ExtendedExecutionForegroundRevokedReason Enum (Windows.ApplicationModel.ExtendedExecution.Foreground) - Windows UWP applications
Content Source: https://cpubwin.visualstudio.com/DefaultCollection/windows-uwp/_git/winrt-api-build?path=%2fwinrt-api-build%2fwindows.applicationmodel.extendedexecution.foreground.extendedexecutionforegroundrevokedreason.yml&version=GBlive&_a=contents
Product: uwp
Technology: winrt-reference
Git Login: knicholasa
Microsoft Alias: nichola

Thanks for reaching out. Those are good questions. To get the fastest answer, I recommend that you ask on our forums or StackOverflow. Otherwise, please see the developer support page for your support options.

Ok,could you please provide the location/source/site/documentation where users in the forums and on StackOverflow get their information from?

https://docs.microsoft.com/ is the primary place to go for documentation. The people on the forums will search the docs, but if they can’t find a solution and are Microsoft staff, they may reach out to the feature teams responsible and ask them directly. If you need a different level of support, you can check out the options on the support page.
I should also say that we do use the feedback here to update our docs - I'm providing these other links because we aren't a direct support channel.


Upgrade bitcoincore-rpc dependency

This PR is basically just noise, really only useful only to highlight the rust-bitcoincore-rcp branch with the upgrade on it case you want to use it locally.
ref: https://github.com/rust-bitcoin/rust-bitcoincore-rpc/pull/311
No changes required to this crate, done while attempting to upgrade to rust-bitcoin v0.31.0-rc1 in miniscript and bdk.

@tcharding I went ahead with #146 so that you find the crate already published with that, hope you are happy with that instead of roundtripping on this

Yeah man, legend. Thanks for the heads up!


Re-enable parsing of query string in URL

Since the last upgrade of AngularJS, the part of the URL to the right of the hash has been prefixed with a slash. The library used to parse the URL considers the slash as part of the name of the parameter and thus the name needs to be updated when accessing it.
With this change, the URL is again successfully parsed.
This is a hack to re-enable the functionality lost with the AngularJS upgrade. This will all be replaced with an AngularJS implementation of the prefix list page.
Fixes #1115
Fixes #1089

This is a really hackish workaround. I just started working on an AngularJS implementation of the prefix list page which will render this obsolete, but it'd be great to have this workaround in place until it's ready to merge...


Problem with rs-convert to PLY

Required Info

Camera Model
L515

Firmware Version
<IP_ADDRESS>

Operating System & Version
Windows 10

Platform
PC

SDK Version
2.36.0

Issue Description
Hi,
I recorded the streams as videos with RealSense Viewer and I obtained a .bag file. I tried to extract the frames with the rs-convert tool. The tool works for all formats except PLY: the process seems to run fine to the 100% PLY convert, but in the output folder there is no files saved. How can I resolve?
Thank you,
Maria Teresa

Hi @marteresagh
Sorry for the delay, are you still having issues with producing PLY files from RealSense Viewer recordings?
I used on my Windows machine the following command line and was able to get generated PLY files:
C:\Program Files (x86)\Intel RealSense SDK 2.0\tools>rs-convert.exe -l test -i C:\temp\20200813_111127.bag
This was based on the 2.36.0 version of SDK using the rs-convert built executable.
*If we don’t hear from you in 7 days, this issue will be closed

Hi,
yes, I still can't get the PLY files. I used the same tool, but in the folder I not find the files.
Thanks,
Maria Teresa

Hi @marteresagh
Can you outline the steps in RealSense Viewer you are taking to record the bag files?  How about streams you have turned on or off prior to hitting the record button within the Viewer?  Can you provide screen captures of your Viewer setup?
Thanks

I think I found the problem. I noticed that the .bag file, recording with only depth sensor activated, does not generate PLY files, I have to activate the rgb camera too.
Thank you

Sounds good.  Glad you were able to figure out the need for the rgb stream to be activated to get the PLY.


Ability to cycle sorting mode to 'off' on table column

Currently once you click a table column the sorting is always 'on' with no way of turning it off.
Proposed solution:
Cycle though ascending, descending and then "off"

Issue resolved in release v0.6.1-alpha


:art: most advanced code

Image dose not load. Otherwise looks nice.

That is the image ;D
nftstorage.link/ipfs/bafkreidvb2my5vj6jgpbrwa7dfw55tryhfk7um5inuxnz7y7khqse2thjq

uh, okay let's goo we will make design for that
cc @exezbcz

@yangwao what is needed 👀

what is needed 👀

Image dose not load. Otherwise looks nice.

This is the current link for the form. Wao wants to make it nicer


Tanstack Query for Svelte 5 does not rerender when adding a dependency variable

Describe the bug
Issue Description:
Problem:
When utilizing the createInfiniteQuery client to manage infinite queries, there is an issue with updating the query despite the addition of a dependency variable in the query key.
Steps to Reproduce:
Initialize a query using createInfiniteQuery.
Define a queryKey that includes generic variables.
Implement the queryFn function to handle data retrieval based on certain conditions.
Attempt to update the query based on changes in the dependency variable within the queryKey.
Actual Behavior:
Despite adding the dependency variable to the queryKey, the query does not update as expected when the variable changes.
Code Snippet:
javascript
let query = createInfiniteQuery({
  queryKey: ['Resource', dependencyVariable],
  queryFn: async ({ pageParam }) => {
    // Implementation omitted for brevity
  },
  getNextPageParam(lastPage) {
    // Implementation omitted for brevity
  },
  initialPageParam: null as string | null | undefined,
  initialDataUpdatedAt: () => Date.now(),
});

Environment:
Framework/Libraries: SVELTE 5
Possible Solutions:
Review the implementation of createInfiniteQuery to ensure proper handling of dependency variables.
Check for any inconsistencies or errors in the query key setup.
Consider alternative approaches for managing infinite queries that may better accommodate dynamic updates.
Your minimal, reproducible example
I have added an example code below
Steps to reproduce
Steps to Reproduce:
Initialize a query using createInfiniteQuery.
Define a queryKey that includes generic variables.
Implement the queryFn function to handle data retrieval based on certain conditions.
Attempt to update the query based on changes in the dependency variable within the queryKey.
Expected Behavior:
The query should update accordingly when there are changes in the dependency variable included in the queryKey.
Expected behavior
Expected Behavior:
The query should update accordingly when there are changes in the dependency variable included in the queryKey.
How often does this bug happen?
Every time
Screenshots or Videos
test
Platform
Any platform
Tanstack Query adapter
None
TanStack Query version
@tanstack/svelte-query
TypeScript version
5.4.3
Additional context
Additional Context:
This issue impacts the ability to dynamically update queries based on changing dependency variables, hindering the functionality of the application.

I have the same issue, I would expect infinite query to refetch page 0 with different parameters (or do anything at all) when part of the array key changes

I have added an example code below

Please show a minimal reproduction with codesandbox or stackblitz

To my knowledge, Tanstack Query has yet to support Svelte 5 runes, so directly feeding $state (assuming dependencyVariable is $state) won't yield the desired results.
The Tanstack Query 5 documentation mentions you can pass options as a Svelte Store to make it reactive.
While not very ergonomic, it is workable.
Alternatives like Svelte 4 reactive statements or re-creating the query in a $effect won't work because svelte's context becomes unavailable after the component initialization is complete. (this accidentally did work in early versions of svelte 5)
To make it a bit more ergnomic you can simplify the creation of a reactive store from your runes with a function like:
const toReadable = (cb) => readable(cb(), set => $effect.pre(() => set(cb())));

and then do something like:
let dependency = $state("something");
const query = createQuery(toReadable(() => ({
  queryKey: ["Resource", dependency],
  queryFn: () => getSomething(dependency)
})));

However, note that the above example is for createQuery.
For createInfiniteQuery, it's appears to be bit trickier. You might expect something like this to work:
let dependencyVariable = writable("whatever");
let query = createInfiniteQuery(
  derived(dependencyVariable, ($dependencyVariable) => ({
    queryKey: ["Resource", $dependencyVariable],
    queryFn: async ({ pageParam }) => {
      // Implementation omitted for brevity
    },
    getNextPageParam(lastPage) {
      // Implementation omitted for brevity
    },
    initialPageParam: null as string | null | undefined,
    initialDataUpdatedAt: () => Date.now(),
  }))
);

However, this gives me a lot of type errors, suggesting it is not the way to do it.

An additional example in the documentation specifically demonstrating how to use createInfiniteQuery reactively would be very helpful.

Can you please create a stackblitz reproduction?

I'm using svelte 5 and I tried wrapping the createQuery in a $derived because I needed one of the variables to be derived but I would then get an error when the $derived rune would run, because createQuery uses getContext under the hood and you can only call getContext on mount.
The example @nicksulkers provides wasn't working for me eitherr as I was getting an error:
"$effect() can only be used as an expression statement"
I ended up creating an abstraction using a readable and queryClient.ensureQueryData which works very similarly but doesn't require it to be in a context so it doesn't break in svelte 5's runes and re-rendering. the downside is that I don't have state data anymore it's just the data I want or null. but it's all I could whip up in the little time I have to code ouotside of work
import queryClient from "$lib/utilities/tanstack/queryClient";
import type { DefaultError, EnsureQueryDataOptions, QueryKey } from "@tanstack/svelte-query";
import { readable, type Readable } from "svelte/store";

export const ensureQuery = <TQueryFnData, TError = DefaultError, TData = TQueryFnData, TQueryKey extends QueryKey = QueryKey>(options: EnsureQueryDataOptions<TQueryFnData, TError, TData, TQueryKey>): Readable<TData | null> => {
  return readable<TData | null>(null, (set) => {
    queryClient.ensureQueryData(options).then(set)
  })
}

I then use it like this:
const ensuredQuery = $derived(
  ensureQuery({
    queryKey: ["Resource", dependency],
    queryFn: () => getSomething(dependency)
  })
);

@SaintPepsi here's the function as I'm actually using it:
export const reactiveQueryArgs = <T>(cb: () => T) => {
	const store = writable<T>();
	$effect.pre(() => {
		store.set(cb());
	});
	return store;
};

Usage could then be something like:
let {search}: {search: string} = $props();

const query = createQuery(reactiveQueryArgs(() => ({
	queryKey: ["users", `search:${search}`],
	queryFn: () => fetch(`/users?search=${encodeURIComponent(search)}`)
})));

@nicksulkers is reactiveQueryArgs in a .svelte.ts file?

I was just reading through the source code and realised I can also just pass queryClient as second parameter to createQuery

export const reactiveQueryArgs = <T>(cb: () => T) => {
	const store = writable<T>();
	$effect.pre(() => {
		store.set(cb());
	});
	return store;
};

What do you mean?

I was just reading through the source code and realised I can also just pass queryClient as second parameter to createQuery

What do you mean?

I was just reading through the source code and realised I can also just pass queryClient as second parameter to createQuery

What do you mean?

For exam I have my query client defined in $lib/utilities/tanstack/queryClient
You can pass your queryClient to your createQuery:
const query = createQuery({
        ...your query options,
    },
    queryClient <<<
)

Check the type of createQuery 😊

Hopefully fixed by #6981

@nicksulkers I'm using your amazing trick for quite some time now.
Today I got brutal error in my app:
Cannot read properties of undefined (reading 'teamId')

The code is this:
import { readable } from "svelte/store";

export const reactiveQueryArgs = <T>(cb: () => T) => {
  return readable(cb(), (set) => {
    $effect.pre(() => {
      set(cb());
    });
  });
};

const playerStore = createQuery(
  reactiveQueryArgs(() => ({
    queryKey: ["player", player_id],
    queryFn: getPlayer(player_id),
  }))
);

let { data, error, isLoading } = $derived($playerStore);

const teamStore = createQuery(
  reactiveQueryArgs(() => ({
    queryKey: ["team", data!.teamId],
    queryFn: getTeam(data!.teamId),
    enabled: !!data?.teamId,
  }))
);

I'm using data! because of the typescript error:
'data' is possibly 'null' or 'undefined'. ts(18049)

What do you think?

@frederikhors what does !. do?
MDN doesn't show any information on it: https://developer.mozilla.org/en-US/search?q=!.

@frederikhors what does !. do? MDN doesn't show any information on it: https://developer.mozilla.org/en-US/search?q=!.

Is to shut-up typescript, telling it that I know data is there because I'm using enabled: !!data?.teamId.

Oh true! 🤦
Technically speaking, even if data is null or undefined and you're checking that in enabled the value itself can still be null or undefined, which is why typescript complains.
const data = null

queryKey: ["team", data!.teamId],
queryFn: getTeam(data!.teamId),
enabled: !!data?.teamId,

Is equivelent to:
const data = null

queryKey: ["team", null.teamId],
queryFn: getTeam(null.teamId),
enabled: false,

so you'd probably have to do something like this:
queryKey: ["team", data?.teamId],
queryFn: getTeam(data?.teamId),
enabled: !!data?.teamId,

@frederikhors Your error is likely due to
queryFn: getTeam(data!.teamId),

where getTeam (and specifically it's parameter) is executed immediately, before data contains a meaningful value.
You probably intended to do something like this:
queryFn: () => getTeam(data!.teamId),

where getTeam only gets called after the queryFn is triggered and we are certain data is valid because of the "enabled" property.
You'll probably want to do the same thing for your "getPlayer".

If I use this code:
const teamStore = createQuery(
  reactiveQueryArgs(() => ({
    queryKey: ["team", data!.teamId],
    queryFn: () => getTeam(data!.teamId),
    enabled: !!data?.teamId,
  }))
);

let { data: teamData } = $derived($teamStore);

let { players } = $derived(teamData);

I get this error:
Property 'players' does not exist on type '(() => Promise<{ __typename?: "Team" | undefined; updatedAt?: Date | null | undefined; ... 21 more ...; }) | und...'. ts(2339)

@frederikhors  Please reference my comment to why that might be happening
Destructuring from undefined doesn't work, Imagine if your query hasn't run yet. that means teamData in let { data: teamData } will be undefined.
imagine it like this:
let { players } = $derived(undefined);

You'd probably use a Nullish coalescing operator in that line
let { players } = $derived(teamData ?? {});

Oh true! 🤦
Technically speaking, even if data is null or undefined and you're checking that in enabled the value itself can still be null or undefined, which is why typescript complains.
const data = null

queryKey: ["team", data!.teamId],
queryFn: getTeam(data!.teamId),
enabled: !!data?.teamId,

Is equivelent to:
const data = null

queryKey: ["team", null.teamId],
queryFn: getTeam(null.teamId),
enabled: false,

so you'd probably have to do something like this:
queryKey: ["team", data?.teamId],
queryFn: getTeam(data?.teamId),
enabled: !!data?.teamId,

Why is noone using this:
const query = $derived(createQuery({
  queryKey: ['posts', postId]
})):


INT-1613 Module to wrap Intercom API

Implemented basic functions to access Intercom.io's API

This change is

Reviewed 6 of 6 files at r1.
Review status: all files reviewed at latest revision, 2 unresolved discussions.

README.md, line 11 [r1] (raw file):

getUsers(<lastNumDays>, callback);

getUsers returns a list of users. Expects an integer for lastNumDays and a callback - lastNumDays limits the return results to only users created in the last lastNumDays days, omit this parameter to get all users ever created.

:+1:

lib/index.js, line 17 [r1] (raw file):

 * @param {object} options Options object for the HTTP request
 * @param {function} callback Callback function to call if error or successful return
 * @return {void}

:+1:

Comments from Reviewable


Webview!

I would like the Webview from 6.1.1 back. This may sound petty but hey, it was a nice feature!

We'll look into the possibility of bringing it back in a separate module, sorry for the inconvenience.


Improve binding to member functions

Improve logic when binding to member functions. This may include, but is not limited to:

requiring explicit base::Unretained() when binding to raw pointers
better interoperability (and easier to maintain code) when binding to base::WeakPtrs
potentially allow binding to std::shared_ptr<T> (as a replacement of scoped_refptr<T>)
consider also other adapters - both for class pointer and also for arguments (e.g. like base::Owned)

Done. For argument adapters - created separate issue (#15).


warning: manifest_maker: standard file '-c' not found

I have recently noticed the following strange warning in one of my projects after switching from distutils to setuptools:
warning: manifest_maker: standard file '-c' not found
Google shows me this warning is very common in multiple Python packages - usually present as a distraction to a real installation error.
The string -c is clearly not intended to be a real filename, my guess is something using the Python command line argument -c is wrongly being interpreted?

I believe this message comes from here:
https://github.com/pypa/setuptools/blob/v36.0.1/setuptools/command/py36compat.py#L76
        def _add_defaults_standards(self):
            standards = [self.READMES, self.distribution.script_name]
            for fn in standards:
                if isinstance(fn, tuple):
                    ...
                else:
                    if self._cs_path_exists(fn):
                        self.filelist.append(fn)
                    else:
                        self.warn("standard file '%s' not found" % fn)

The list of expected README file is defined here:
https://github.com/pypa/setuptools/blob/v36.0.1/setuptools/command/sdist.py#L40
class sdist(sdist_add_defaults, orig.sdist):
    """Smart sdist that finds anything supported by revision control"""
    ...
    READMES = 'README', 'README.rst', 'README.txt'

Meanwhile self.distribution.script_name would appear to usually be setup.py, so I am puzzled as to where the -c string comes from.

-c really looks like the value of sys.argv[0] when one does something like python -c "from setuptools import setup; setup(), which pip is doing (using a subprocess) if I recall correctly.

That's what I was wondering - but any idea where/how?

It's probably pip's invocation of setuptools.


Feature request: support "http(s) request" from raw requests file

From https://httpie.io/docs#offline-mode,

Generating raw requests that can be sent with any other client:
▶ RUN# 1. save a raw request to a file:
$ http --offline POST httpbin.org/post hello=world > request.http
▶ RUN# 2. send it over the wire with, for example, the fantastic netcat tool:
$ nc httpbin.org 80 < request.http

Expected
one can run http < request.http or https < request.https to reproduce some results.

So something along the line of batch requests from a file? I see what you're thinking here, and it would be nice to have an automated way to make a lot of requests efficiently. I suppose this would also require a directory as an argument to have somewhere to store all the output because printing to stdout would probably be a bad idea with batch requests.

So something along the line of batch requests from a file? I see what you're thinking here, and it would be nice to have an automated way to make a lot of requests efficiently. I suppose this would also require a directory as an argument to have somewhere to store all the output because printing to stdout would probably be a bad idea with batch requests.

Actually duplicates #758

i would be willing to work on this if no is already working on it

Bonus for ability to add assertion capabilities so that entire test suites could be defined in .http files.


Next permutation

Enter your question -
Implement next permutation, which rearranges numbers into the lexicographically next greater permutation of numbers.
If such an arrangement is not possible, it must rearrange it as the lowest possible order (i.e., sorted in ascending order).
Enter link to the question(if question belongs to any online platform) -
I had this question in my university exam.
Tags for the question(eg - Array

Can you assign this to me, so that i can solve it.

@RAshid602,
Kindly add your solution to "Number Theory" folder.
Deadline - 04/10/2021


Add SUM and AVG functions

Fixes #37
I decided to implement summing and averaging with one trait. If the Money DB type is implemented in the future, you can disable averaging for them by passing in () as the Avg type.

Wow, thanks for the thorough and well done PR.

This is missing a changelog entry. I'll add it.


Deprecate this package in favour of @loopback/sequelize

Is your feature request related to a problem? Please describe.
Since all of the necessary features are now being provided by the official package @loopback/sequelize
This package can safely be marked as deprecated.
Describe the solution you'd like

[x] Add deprecation notice in README file.
[ ] Run following deprecation command. (to be run by @samarpan-b sir's npm account.)
npm deprecate loopback4-sequelize "<message>"
Replace message with <message> "This package has been deprecated in favour of @loopback/sequelize."

Describe alternatives you've considered
__
Additional context
__

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Failure to open PDF created by Xerox WorkCentre 7225 scanner

Attempting to read a PDF generated by a Xerox WorkCentre 7225 scanner results in the following error:
Error reading the pdf: Read failed.: dereferenceObject: problem dereferencing object 6: pdfFilterPipeline: Expected DecodeParms Array corrupt

I've attached a pdf of a blank page.
To reproduce the error, I basically do this:
        cfg := pdfcpu.NewDefaultConfiguration()
        ctx, err := api.Read("Scanned.pdf", cfg)
        if err != nil {
                fmt.Printf("Error reading the pdf: %v\n", err)
        }

Eh, forgot the attachment of course. :-/
Xerox-blank-scan.pdf

Thanks for reporting this!
It will be fixed with the upcoming release next week.

fixed by 0.1.15


Websocket client: input sequence, continuous in memory

A simplified version of my websocket-client looks like following
boost::beast::multi_buffer b;

for (;;) {
  ws.read(b);

  // Copy a range of bytes
  // (asio::buffers_begin(b.data()), asio::buffers_begin(b.data()) + b.size())

  b.consume(b.size())
}

My question is whether the range that I copy inside for-loop above constitutes a
continuous piece of memory and how a user can access a pointer to it to avoid extra coping inside?
Since I know the maximum size of a websocket message, is there any way to ask beast library
to use a single buffer so that it will be guaranteed that the range above is a continuous piece
of memory?
Thank you very much for such a great library. This is a great job.

is there any way to ask beast library to use a single buffer

Yes, that is very easy. Instead of using multi_buffer, use a flat buffer:
Using dynamic allocation:
http://www.boost.org/doc/libs/master/libs/beast/doc/html/beast/ref/boost__beast__flat_buffer.html
Example:
boost::beast::flat_buffer b;
...
ws.read(b);
boost::asio::const_buffer cb = boost::beast::buffers_front(b.data));
std::cout << boost::beast::string_view(
    reinterpret_cast<char const*>(cb.data()), cb.size()) << "\n";

Or if you are guaranteed to know the maximum message size you can use a static flat buffer:
http://www.boost.org/doc/libs/master/libs/beast/doc/html/beast/ref/boost__beast__flat_static_buffer.html
Example:
// Message is guaranteed to be 2,000 bytes or less
boost::beast::flat_static_buffer<2000> b;
...
ws.read(b);
boost::asio::const_buffer cb = boost::beast::buffers_front(b.data));
std::cout << boost::beast::string_view(
    reinterpret_cast<char const*>(cb.data()), cb.size()) << "\n";

Hope this helps!

Hope this helps!

Definitely! Thank you very much for such a prompt response.
Your answer covers my questions completely.
Thanks again.


Added cell level passing into getCellIDs Util function

The library’s util has a function which lets api users get the cell ids in a specific region.
After a trial and test, I found out that although cell level 15 is used to getMapObjects, any cell level can be used.
By increasing the cell level, more data can be retrieved, and potentially decrease api calls due to scanning all level 15 cells.

I vaguely remember something about there being a limit of how much data you can request from the API in one call which is why level 15 was chosen. I might be wrong though. If none of the other contributors see any reason against this change I'll gladly merge.

API always returns level 15 cells. It can handle most cell levels in requests afaik.

I think there was some discussion on the PogoDev discord that revealed that this change doesn't actually do anything to the data you receive, but I'm not sure I'm remembering that right. Can anyone confirm?

Still, scanning in level 17 means that you are jumping at a shorter distance because the cells are smaller. you are getting more info in wild_pokemons/catchable_pokemons because it's in the range.


[SPARK-13577] [yarn] Allow Spark jar to be multiple jars, archive.

In preparation for the demise of assemblies, this change allows the
YARN backend to use multiple jars and globs as the "Spark jar". The
config option has been renamed to "spark.yarn.jars" to reflect that.
A second option "spark.yarn.archive" was also added; if set, this
takes precedence and uploads an archive expected to contain the jar
files with the Spark code and its dependencies.
Existing deployments should keep working, mostly. This change drops
support for the "SPARK_JAR" environment variable, and also does not
fall back to using "jarOfClass" if no configuration is set, falling
back to finding files under SPARK_HOME instead. This should be fine
since "jarOfClass" probably wouldn't work unless you were using
spark-submit anyway.
Tested with the unit tests, and trying the different config options
on a YARN cluster.

Test build #52415 has started for PR 11500 at commit da39f4b.

Test build #52415 has finished for PR 11500 at commit da39f4b.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/52415/
Test FAILed.

Test build #52607 has started for PR 11500 at commit 9bab2ea.

Test build #52607 has finished for PR 11500 at commit 9bab2ea.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/52607/
Test PASSed.

Merged build finished. Test PASSed.

Ping anyone?

Mostly eyeballing it here, but it looks reasonable to me given its goal. You'll know a lot more about what needs to happen to make this work than I would.

minor nit about comment otherwise lgtm.
I assume you tested both archives and jars on a real yarn cluster in both cluster/client mode?

both archives and jars on a real yarn cluster in both cluster/client mode

Not sure I tested client mode, but I'll take a look. Shouldn't really make a difference, but you never know.

Test build #52873 has started for PR 11500 at commit 35e4762.

Test build #52873 has finished for PR 11500 at commit 35e4762.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/52873/
Test PASSed.

Merged build finished. Test PASSed.

+1


docker compose throws error: exit status 1

Using sedge v0.5.1 because the newest version wouldn't let me create JWT Secret.
For the last 3 days I have been syncing my consensus nodes and execution nodes. This is the command that I ran to set it up
 sedge cli --network mainnet -c prysm -e geth
After everything gets synced up, a few days later i get prompted Would you like to run validator service? When I hit Y then it runs the following docker compose
docker compose -f docker-compose-scripts/docker-compose.yml up -d validator
After this runs, I get the following error
[ERRO] command 'docker compose -f docker-compose-scripts/docker-compose.yml up -d validator' throws error: exit status 1
Any idea how to fix this? The error code isn't helpful as it doesn't say why it is throwing an error

Hi @mdszn and thanks for reporting. About the jwtsecret issue in our newer version is something we are aware of. A quick fix for that should be adding the -p . flag so Sedge use a different datadir.
About your new issue with the validators. Have you run sedge keys or imported some keystores  manually to the sedge docker-compose-script directory? If yes please try running the following command and provide us the outputs:
docker compose -f docker-compose-scripts/docker-compose.yml up validator
In case you have not imported keystores please run the sedge keys command to have sedge generate them or copy them inside the docker-compose-scripts/keystore/validator_keys/ directory and create a keystore_password.txt file inside docker-compose-script/keystore directory that contains the passphrase you used to encrypt the keystores.
All of this files will be used by sedge to setup your validator. In case you do not want to run a validator use sedge cli with the --no-validator flag.

Ah okay thank you this was able to fix it and I was able to get the consensus and execution clients up. How am I able to connect to the clients? If the execution client ws is running on port 8546, i should be able to connect to it via http://host:8546/ correct? Everything I try and connect to it I get failure

Good to hear that solved your issue @mdszn. About your question. By default client's HTTP APIs are only accessible inside the docker-compose network except for those used for peering. If you want to access them from your machine you must use the corresponding container IP. To get these IP addresses you'll need to run something like this:
docker inspect -f {{.NetworkSettings.Networks.sedge_network.IPAddress}} execution-client

In case you want to expose these ports to your localhost you can add them to the generated docker-compose file or use the sedge cli --map-all flag. Keep in mind exposing these ports could be insecure in some cases so using a firewall is advised.


fix: signature of provideTextDocumentContent

According to docs
https://code.visualstudio.com/api/references/vscode-api#TextDocumentContentProvider
TextDocumentContentProvider.provideTextDocumentContent return ProviderResult<string>
provideTextDocumentContent(uri: Uri, token: CancellationToken): ProviderResult<string>

and ProviderResult<string> is defined as
ProviderResult: T | undefined | null | Thenable<T | undefined | null>

Current signature does not allow to request text content asynchronously from the server.

Thank you!


Non breaking changes

Change hasEqualProperties to gracefully handle parsers of inconsistent types.
False is returned if the parsers are not of the same type matching general Dart equality semantics and keeping the signatures of all methods that implement hasEqualProperties consistent.

Thank you for the fix.

Thanks for the quick merge!
On Mon, Jan 26, 2015 at 11:08 PM, Lukas Renggli<EMAIL_ADDRESS>wrote:

Thank you for the fix.
—
Reply to this email directly or view it on GitHub
https://github.com/petitparser/dart-petitparser/pull/43#issuecomment-71599109
.


Add only External review to State field in Reviewer Settings

Related to https://github.com/HyphaApp/hypha/issues/2168
Description
As a manager I need to add 'only External review' as an option to State field in  EDITING Reviewer Settings to limit the Reviewer group's access to applications.
The Reviewer group with active members do not need to have access to applications they have reviewed permanently. We will have a process to share information with this group when requested.

Thank you -- looks great! 👍


Text.lowercase in RTS

[x] Try to implement lowercase in the RTS, using what we have at hand.
[x] Expose it as a new primitive with the compiler.
[ ] Tests pass -- there tests, but some strange behavior at the moment.

Superseded by https://github.com/dfinity/motoko/pull/4216


field string case format change from 'ANy cASe' to 'Title Case'

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I remove or skip any mandatory* field

Checklist

[X] I'm requesting a feature unrelated to a specific site
[X] I've looked through the README
[X] I've verified that I'm running yt-dlp version 2022.10.04 (update instructions) or later (specify commit)
[X] I've searched the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue

Provide a description that is worded well enough to be understood
Functionality/options to change/convert 'ANy cASe' field string case format to 'Title Case'
(for fields like 'Title', 'FileName', 'Keywords', etc.)
#5334
https://www.reddit.com/r/youtubedl/comments/ydpy8j/ytdlp_field_string_case_format_change_from_any/
Provide verbose output that clearly demonstrates the problem

[ ] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[ ] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
No response

Was just going to open a new issue about this, but luckily found this after a while..
So, any news about this?
I mean, I studied the official readme, and yt-dlp has really powerful metadata features by now, apparently (e.g. --parse-metadata, --replace-in-metadata), but no built-in option for title case or something?
There's another option that is entirely new to me (--print-to-file ), is that something that could be used here?
To be honest, from the description that is in the readme at the moment, I don't really understand what this option does, maybe someone can enlighten me with a good example?

We use python's regex, str.format and printf-formatting to power these functionality. But the problem is none of these support case changes natively and so we'll need to implement some sort of custom syntax for it.

There's another option that is entirely new to me (--print-to-file ), is that something that could be used here?

No, a the name suggests, it's just --print, but to a file instead of stdout

Okay, thanks  for your reply and the explanation, I appreciate it, and the really outstanding work you guys are doing with yt-dlp!
🥂


Azure Monitor/Log Analytics for AVS

Note on this page says that this solution is deprecated.
What is the current solution for monitoring VMs in Azure VMWare Solution?
I understand that LA/AM Agent can be installed on AVS guest VM. However, installing agent on individual VMs will not scale to 1000s of AVS VMs.
What options are available to deploy LA/AM agent at scale for AVS?

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

ID: 722cdf93-af91-26ac-697a-f090134a71a2
Version Independent ID: 1b4085ee-0c27-b620-3b4a-8ec4a2707b32
Content: VMware Monitoring solution in Azure Monitor - Azure Monitor
Content Source: articles/azure-monitor/insights/vmware.md
Service: azure-monitor
Sub-service: logs
GitHub Login: @bwren
Microsoft Alias: bwren

@Mahesh-MSFT Thanks for your comment. We will review the issue and get back to you shortly

@Mahesh-MSFT The VMs for AVS live in the Azure Service Fabric control pane and you see them within vCenter. Anything that's possible for IaaS management/maintenance will also be possible for VMs living in the private cloud deployment. So you can use Azure Monitor for VM's solution.  Kindly note that this documentation will be updated with latest information.
Also to deploy MMA at scale , you can take advantage of built-in initiatives of Azure Policy

@Mahesh-MSFT Just following to check if you need further assistance on the issue.

@Mahesh-MSFT We will close the issue for now. If there are further questions , please revert and we will be glad to assist you.

Thanks @SwathiDhanwada-MSFT for your support . Please close this issue.