Fix for expiration date calculation

Potential fix for #790
expiresIn function is used in only one place, so the fix should be 'safe'
that why I think would be better to remove this.now() or we have to rename this function to expiresOn

I think the better fix would be to fix this line (as opposed to Utils.expiresIn):
accessTokenResponse.expiresOn = new Date((Utils.now() + exp) * 1000);

which would be
accessTokenResponse.expiresOn = new Date(exp * 1000);

(I'm also surprised to not see any unit tests failing as a result of this PR, meaning we should probably add some)

Done.
@jasonnutter Can you please help find the right place for the assertion? (if you want me to add test to this PR before the merge).  I cannot find tests that verify that JWT access token is interpreted correctly.

@sergey-tihon There are some added with #742; Also @pkanher617 when this change is made I thought we considered this use case? Did we not add tests?

Unfortunately this won't fix your issue. expiresIn comes back from the server as the lifetime of the token in seconds (i.e. 3599 seconds, or one hour), which we convert this to milliseconds and add to the current time to get the expiration Date object. Date constructor takes Unix time, which is in milliseconds. I think the parentheses are just off, it should be Utils.now() + (exp * 1000).
I am surprised we don't have unit tests covering this, I will make sure to add those. I can add a separate PR for these changes, or you can add it here and merge this, and I can just add the unit tests after.

@pkanher617 In this context, the value of exp is the value that comes back from Utils.expiresIn already includes the current timestamp in its value.

I think a better strategy is to fix Utils.ts to just return parseInt(expires, 10) in the expiresIn function.

@pkamalamsft That was my initial idea and first commit in this PR.
But than @jasonnutter point me out that we use const expiresIn = Utils.expiresIn in accessTokenValue construction and it will be wrong there if we remove Utils.now() from Utils.expiresIn.

I will make sure to add those. I can add a separate PR for these changes, or you can add it here and merge this, and I can just add the unit tests after.

@pkamalamsft it would be awesome if you can help me with tests for this case.
One more strange thing
If I understand correctly, msal.js persist accessTokenKey+ accessTokenValue in localStorage.
But why token value (for login/identity token) store expiresIn as a Number

but accessTokenValue  for resource/graph token is stored as a string

Just checking, it is by design or maybe fixed in one of upcoming (not merged) PRs?
If this is an unexpected behavior I can create new issue.

@sergey-tihon You may have tagged the wrong person lol.
I have added a PR #799 to fix this issue.

That was my initial idea and first commit in this PR.
But than @jasonnutter point me out that we use const expiresIn = Utils.expiresIn in accessTokenValue construction and it will be wrong there if we remove Utils.now() from Utils.expiresIn.

@jasonnutter was correct, our caching logic breaks if we change it there completely, so I have moved that calculation out of the Utils function and calculate at cache time the expiration.

it would be awesome if you can help me with tests for this case.

No problem, I have added tests.

Just checking, is it by design or maybe fixed in one of upcoming (not merged) PRs?
If this is an unexpected behavior I can create new issue.

Yes this was fixed in an unmerged PR. This happens because in the case of an id token, we do not receive the expiration lifetime from the server, so we extract this from the token. I have fixed this to always store as a string. Please let me know if these changes work. I will merge my PR if the changes seem to work for you.

Close this PR (😢) in favor of #799


added note on tfsec

This PR fixes #
Checklist

[ ] I have signed the CLA
[ ] I have updated/added any relevant documentation

Description
What's the goal of this PR?
What changes did you make?
What alternative solution should we consider, if any?

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


Sleep inside KeyDown

It seems like you can't supress a keypress in the keydown event if there is any sort of delay?
Any idea what causes this?

I hope I was not mistaken about the topic, and this same issue is mentioned here.
I came across it when implementing key interception through SetWindowsHookEx:
[DllImport("user32.dll")]
private static extern IntPtr SetWindowsHookEx(int idHook, LowLevel_KeyboardProc Ipfn, IntPtr hMod, uint dwThreadId);

The problem is that if there is "Thread.Sleep" inside the event handler or somewhere inside its code, then after a couple of clicks the event completely stops registering. In this library, I encountered the same behavior.
private void GlobalHookKeyPress(object sender, KeyPressEventArgs e)
{
        Console.WriteLine("KeyPress: \t{0}", e.KeyChar);
        Thread.Sleep(500);
}


Add Portuguese (Brazilian)

Added Português do Brasil

Looks good! Would you mind adding a .json extension to the file?

Ops something are wrong ⚠

i updated the correct file 👍


Buttons in the editor view are blocked by the system's title bar

Search first

[X] I searched and no similar issues were found

What Happened?
The buttons in the editor view are blocked by the system's title bar. You can see it, but you can only click on the bottom half of the button.
Reproduce the Bug

Open the editor view
Try to click button such as 'Line'

Screenshots
No response
Environment Information
macOS 13.5.1
logseq 0.9.15
plugin 1.4.0
Additional Context
No response
Are you willing to submit a PR? If you know how to fix the bug.

[ ] I'm willing to submit a PR (Thank you!)

This issue needs to be addressed by logseq, I have already raised an issuehttps://github.com/logseq/logseq/issues/10043 for it.


which one should i download

ffmpeg-master-latest-win64-gpl-shared.zip or ffmpeg-master-latest-win64-gpl.zip

If you need shared libs, the one with shared libs. Otherwise just use the completely static one.

If you need shared libs, the one with shared libs. Otherwise just use the completely static one.

what does that mean? I need it to edit videos

If you don't know what shared libraries are, there's a very high chance you don't need them.
You only need them if you are developing an application yourself, or need to use ffmpeg as plugin in other software.

You should try ffmpeg-master-latest-win64-gpl-shared.zip

Don't use a shared build unless you know you need one. It's just needlessly inviting issues with DLL collisions some other software might have installed.
Gonna close the issue. Feel free to re-open if you feel like you didn't get the answer you were looking for yet.

Hello @BtbN,
I read somewhere shared package included DLL so it was better and I installed it.
Apparently it was wrong.
I think you should explain in the README for people like us who just want to install a working version of ffmpeg on their Windows.
Example of explanation:

For normal people, you should download non-shared packages.

And as a bonus, but maybe not necessary, maybe explain what is a shared package.


Unable to build

Hello @dsuess ! I cloned your repo within a mediapipe repo (so it could have access to all the mediapipe utils and calculators) - however, when I run the build command, I run into these error which I'm not sure how to resolve:

Thanks!

This has likely to do with WORKSPACE referencing the master branch of rules_foreign_cc: https://github.com/dsuess/mediapipe-pytorch/blob/master/WORKSPACE#L51C10-L51C57. However, that repo has renamed the branch to main.
Note that most of that WORKSPACE file was copy-pasted from the same file in the media pipe repo, so just check out their rule for rules_foreign_cc: https://github.com/google/mediapipe/blob/master/WORKSPACE#L47
However, note that this repo is relatively outdated, so you probably want to update to a more recent version of media pipe anyway.

I see! To make sure I'm understanding correctly, I should use the mediapipe repo's rules for rules_foreign.cc instead of the one currently in your repo?

That would be my first guess. There's a chance that the version specified there is too new, then you either need to update other packages in WORKSPACE or try to figure out which version of rules_foreign works with the current setup through trial-and-error

Gotcha, thank you so much!


Update L2Block to contain public data

What should we include on the L2Block? I understand that the L2Block should carry enough information so all nodes can 1) update their respective world state trees, and 2) can identify which txs got included in that block. So far the data needed for both was the same: the new leaves for the private data, nullifier, and contract trees. These covered all state updates needed, and the hash of a tx could be derived from those.
With public functions, we now probably want to include all PublicDataWrites in the block (ie what leaves in the public data tree were changed into what values). However, this is not enough for reconstructing tx hashes.
A tx hash needs to be known by the client as they send it. This means that it cannot depend on any processing done by the sequencer, so it should be derived from 1) the outputs of the private kernel circuit and 2) the public tx requests. Today a tx is structured as:

The private kernel circuit public outputs, its proof, and unverified data
A signed tx request for public operations

Either of the two or both can be set. From that, we are calculating the tx hash as:

If the tx only has private data, the hash of the new leaves (as we did so far)
If the tx only has a public tx request, its hash (including the signature, like Ethereum does)
If the tx has both, the hash of the two hashes above

This is probably insufficient, since the private kernel circuit public outputs may include a public call stack that represents further calls to public functions, that we should hash as well. But let's move ahead. Going back to the original question, for each tx, we'd need to include in the block one of:

The signed public tx request
The hash of the signed public tx request
The tx hash itself (probably this one makes the most sense since it's smaller)

This probably means that the root rollup circuit would need to output a hash of all these, and for that the base and merge rollup circuits should receive the tx hash from the public inputs of the kernel circuit. If all this reasoning is correct (which I find unlikely), then we'd need to:

Have the kernel circuit output the tx hash, which can assembled since the circuit receives all tx data
Roll it up as part of the calldata_hash, so it gets validated by the rollup processor
Include all individual tx hashes in the L2 block

This is probably insufficient, since the private kernel circuit public outputs may include a public call stack that represents further calls to public functions, that we should hash as well. But let's move ahead.

As a separate conversation: does it make sense to completely remove the signed tx request part of the tx, and require that all public calls in a tx are started from a private call? So a tx would only have the public outputs of the kernel private circuit, which may include a public_call_stack that represents the public calls to run. This would remove the need for the public_kernel_circuit_no_input altogether, and simplify the tx flow. It may also align well with account abstraction, so users always kickstart operations by calling a private function in their wallet, and the wallet is responsible for kicking off any subsequent private or public ops by populating the private or public call stacks of the circuit outputs.

For reference, please could you write exactly what's contained within a private tx's txHash, in our codebase at the moment?
Also for reference, here's the data which is hashed in Ethereum, to form the txHash:

nonce
gas price
gas limit
to
value in wei
data
ecdsaV
ecdsaR
ecdsaS

what's contained within a private tx's txHash, in our codebase at the moment

A SHA256 hash of the tx's new commitments, nullifiers, and contracts, as inserted on their respective trees (ie contracts are represented as the pedersen hash of the contract address, portal contract address, and function tree root).
https://github.com/AztecProtocol/aztec3-packages/blob/eeae55cafd511cb2d47f361212c08eeec77fd821/yarn-project/types/src/create_tx_hash.ts#L15-L24

here's the data which is hashed in Ethereum

For the sake of completeness, since EIP155 the chainId is also included, and EIP2718 introduces typed tx envelopes (which we may want to copy so we can change tx formats in the future without breaking compat).

As a separate conversation: does it make sense to completely remove the signed tx request part of the tx, and require that all public calls in a tx are started from a private call?...

Interesting question!
The downsides would be:

Latency for users who only want to execute a public function (they'd need to generate two proofs locally; one of a private function and one of the private kernel circuit).
Possibly extra constraints for the sequencer, and hence extra cost for the user (the private kernel circuit proof would now need to be verified within the "public kernel circuit which verifies a private kernel circuit"). This will cost more in constraints if the cost of signature verification exceeds the cost of recursive proof verification (but it might not, with Goblin Honk!).
Every external public function in a Noir Contract would need to instead be wrapped in an external private function which "wraps" the public function. This might be an initially-confusing user experience.

We can probably(?) design account abstraction interfaces in a way where a user could validate either of a public or private tx.
I'd vote for keeping the ability to send a public txRequest to the txpool directly, for now, but I'm still digesting your initial post at the top of this issue.

Latency for users who only want to execute a public function (they'd need to generate two proofs locally; one of a private function and one of the private kernel circuit).

True. Nevertheless, given these actions are "simple" (just pushing a public call stack item), would proofs be faster? Or is the difference negligible?

This will cost more in constraints if the cost of signature verification exceeds the cost of recursive proof verification (but it might not, with Goblin Honk!).

Agree, but on the other side, we end up with a single verification flow for the public kernel circuit, since we can drop the signature verification variant and focus on optimizing just a single version.

Every external public function in a Noir Contract would need to instead be wrapped in an external private function which "wraps" the public function. This might be an initially-confusing user experience.

Not if we roll this out along with AA: the entrypoint for every user action would be an external private function in their "wallet contract", which in turn calls the external public function that the user wanted to call. So the smart contract dev doesn't need to wrap anything, it's taken care of by the user's smart wallet.

I'd vote for keeping the ability to send a public txRequest to the txpool directly, for now,

Agree. We can revisit this later.


Enhancement: Normalize composer.json

This PR

[x] normalizes composer.json

💁♂ I ran
$ composer global require localheinz/composer-normalize:^1.0.0

followed by
$ composer normalize

For reference, also see

https://github.com/localheinz/composer-normalize
https://localheinz.com/blog/2018/01/15/normalizing-composer.json/

Thank you, @B-Galati, @curry684, and @OskarStark!


Release/1.18.0

What

Use go modules
Upgraded to go version 1.13.7
Healthcheck
Log.go instead of go-ns/log

How to review
Working in develop environment
Who can review
Anyone.

I already reviewed it too (@nshumoogum did the work and I created this release branch)


Trash/delete keybinding for forward delete on MacOS

Adding MacOS forward delete keybinding to move files to trash or delete.
This PR fixes #108862

Yeah, why not. Thanks a lot for this PR.


graphene-hardened-malloc: 1 -> 2

Motivation for this change
Unexciting bump, hopefully.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Thank you


fix(date-picker): Fixed picker not closing when clicking in another picker

Description:
When opening one picker by clicking on the input and then opening another picker by clicking the input, the old picker doesn't close anymore. This happens because we catch click event to don't disturb other parent elements.
Solution:
To work around this I notify all flatpickr instances manually about the click and therefore close them.

Don't you want to add a test?


ABI conventions for function arguments

Discussing function arguments convention after https://github.com/raiden-network/raiden-contracts/pull/198 is merged.
(As mentioned, until now, the contracts have been refactored numerous times, with the main focus on features rather than consistency. I consider this the phase where we should align on consistency & security.)
Scope: Make sure the interface is consistent and agreed upon. This minimizes confusion in the Raiden client or other clients that may be used.
Predominant convention used now:

channel_identifier
participant address most important to the call, usually defined as participant
arguments that belong to 2.
other participant address, if necessary, usually defined as partner
arguments that belong to 4.
signatures, if necessary, in the participants order as seen above

Functions that do not follow the above convention:

updateNonClosingBalanceProof - 2. & 4. are reversed, as the most important address here is non_closing_participant
unlock - 2. & 4. are reversed, as the most important address here is actually partner in my opinion, who sent the pending transfers. This is because these pending transfers will not necessarily go to participant.

Additional Ideas:

use more suggestive names, instead of participant and partner. E.g. payer_participant, payee_participant for unlock; receiving_participant for the participant receiving the deposit or similar.

Questions:

is the above a good convention? what are other proposals?
what function interface needs changing?

Implementation:
function setTotalDeposit(
        uint256 channel_identifier,
        address participant,
        uint256 total_deposit,
        address partner
    )

function setTotalWithdraw(
        uint256 channel_identifier,
        address participant,
        uint256 total_withdraw,
        address partner,
        bytes participant_signature,
        bytes partner_signature
    )

function closeChannel(
        uint256 channel_identifier,
        address partner,
        bytes32 balance_hash,
        uint256 nonce,
        bytes32 additional_hash,
        bytes signature
    )

function updateNonClosingBalanceProof(
        uint256 channel_identifier,
        address closing_participant,
        address non_closing_participant,
        bytes32 balance_hash,
        uint256 nonce,
        bytes32 additional_hash,
        bytes closing_signature,
        bytes non_closing_signature
    )

function settleChannel(
        uint256 channel_identifier,
        address participant1,
        uint256 participant1_transferred_amount,
        uint256 participant1_locked_amount,
        bytes32 participant1_locksroot,
        address participant2,
        uint256 participant2_transferred_amount,
        uint256 participant2_locked_amount,
        bytes32 participant2_locksroot
    )

function unlock(
        uint256 channel_identifier,
        address participant,  # address who would receive the claimed locked tokens
        address partner,   # address who sent the pending transfers in the merkle tree
        bytes merkle_tree_leaves
    )

function cooperativeSettle(
        uint256 channel_identifier,
        address participant1_address,
        uint256 participant1_balance,
        address participant2_address,
        uint256 participant2_balance,
        bytes participant1_signature,
        bytes participant2_signature
    )

I think I need to warn against changing the ordering of arguments at this point.  Even after swapping two addresss, the function signature hash stays the same.  So, one has to be extremely careful when they have to deal with multiple versions of the TokenNetwork contract.

I agree. At this point it also makes little sense to change something that is working, with the risk of introducing bugs/attacks. We can revisit this if needed, later on. I will close this for now.


Jenkins - collector running but no data & why am I not authorized to configure a widget?

Hi,
I'm trying to setup Hygieia and almost done with the setup. Able to run the api, UI & mongo successfully and even started jenkins collector..  I have few problems after the setup. Could you please help.
**1) After Login I have created couple dashboards i.e., team dashboards & product dashboards.. and able to view them and when I click on created dashboard.. I'm able to see the tabs i.e, Build, Code rep, Feature, Monitor, Deploy, Quality. But when I click on "Configure widget" it says you are not authorized. Please help me how to configure widgets.
2) Started jenkins collector and I can see the jenkins job details populated in collector_items in mongo. But not sure where can I see them in my HYGIEIA UI. **
Please find the logs.. (The below log is after couple restarts - In first attempt I'm sure I have seen some number beside fetched jobs)
2016-11-30 14:47:51,609 INFO  c.c.dashboard.config.MongoConfig - Initializing Mongo Client server at: 192.168.XX.XX:27017
2016-11-30 14:47:51,614 INFO  org.mongodb.driver.cluster - Cluster created with settings {hosts=[192.168.XX.XX:27017], mode=SINGLE, requiredClusterType=UNKNOWN, serverSelectionTimeout='30000 ms', maxWaitQueueSize=500}
2016-11-30 14:47:51,617 INFO  c.c.dashboard.config.MongoConfig - Connecting to Mongo: Mongo{options=MongoClientOptions{description='null', readPreference=primary, writeConcern=WriteConcern{w=1, wtimeout=0, fsync=false, j=false, codecRegistry=org.bson.codecs.configuration.ProvidersCodecRegistry@8d79c150, minConnectionsPerHost=0, maxConnectionsPerHost=100, threadsAllowedToBlockForConnectionMultiplier=5, serverSelectionTimeout=30000, maxWaitTime=120000, maxConnectionIdleTime=0, maxConnectionLifeTime=0, connectTimeout=10000, socketTimeout=0, socketKeepAlive=false, sslEnabled=false, sslInvalidHostNamesAllowed=false, alwaysUseMBeans=false, heartbeatFrequency=10000, minHeartbeatFrequency=500, heartbeatConnectTimeout=20000, heartbeatSocketTimeout=20000, localThreshold=15, requiredReplicaSetName='null', dbDecoderFactory=com.mongodb.DefaultDBDecoder$1@164a604b, dbEncoderFactory=com.mongodb.DefaultDBEncoder$1@da3bd17, socketFactory=javax.net.DefaultSocketFactory@16525fa0, cursorFinalizerEnabled=true, connectionPoolSettings=ConnectionPoolSettings{maxSize=100, minSize=0, maxWaitQueueSize=500, maxWaitTimeMS=120000, maxConnectionLifeTimeMS=0, maxConnectionIdleTimeMS=0, maintenanceInitialDelayMS=0, maintenanceFrequencyMS=60000}, socketSettings=SocketSettings{connectTimeoutMS=10000, readTimeoutMS=0, keepAlive=false, receiveBufferSize=0, sendBufferSize=0}, serverSettings=ServerSettings{heartbeatFrequencyMS=10000, minHeartbeatFrequencyMS=500}, heartbeatSocketSettings=SocketSettings{connectTimeoutMS=20000, readTimeoutMS=20000, keepAlive=false, receiveBufferSize=0, sendBufferSize=0}}}
2016-11-30 14:47:51,694 INFO  org.mongodb.driver.connection - Opened connection [connectionId{localValue:5, serverValue:93}] to 192.168.XX.XX:27017
2016-11-30 14:47:51,697 INFO  org.mongodb.driver.cluster - Monitor thread successfully connected to server with description ServerDescription{address=192.168.XX.XX:27017, type=STANDALONE, state=CONNECTED, ok=true, version=ServerVersion{versionList=[3, 0, 14]}, minWireVersion=0, maxWireVersion=3, electionId=null, maxDocumentSize=16777216, roundTripTimeNanos=1534208}
2016-11-30 14:47:53,079 INFO  o.s.j.e.a.AnnotationMBeanExporter - Registering beans for JMX exposure on startup
2016-11-30 14:47:53,101 INFO  com.capitalone.dashboard.Application - Started Application in 10.147 seconds (JVM running for 11.922)
2016-11-30 14:48:00,001 INFO  c.c.d.collector.CollectorTask - Running Collector: Hudson
2016-11-30 14:48:00,083 INFO  c.c.d.collector.CollectorTask - -----------------------------------
2016-11-30 14:48:00,083 INFO  c.c.d.collector.CollectorTask - http://192.168.XX.XXX:80XX/
2016-11-30 14:48:00,084 INFO  c.c.d.collector.CollectorTask - -----------------------------------
2016-11-30 14:48:01,064 INFO  c.c.d.collector.CollectorTask - Fetched jobs                     1s
2016-11-30 14:48:01,067 INFO  c.c.d.collector.CollectorTask - New jobs                0        0s
2016-11-30 14:48:01,121 INFO  c.c.d.collector.CollectorTask - New builds              0        0s
2016-11-30 14:48:01,122 INFO  c.c.d.collector.CollectorTask - Finished                         1s
2016-11-30 14:49:00,000 INFO  c.c.d.collector.CollectorTask - Running Collector: Hudson
2016-11-30 14:49:00,026 INFO  c.c.d.collector.CollectorTask - -----------------------------------
2016-11-30 14:49:00,027 INFO  c.c.d.collector.CollectorTask - http://192.168.XX.XX:80XX/

properties file:
dbname=dashboarddb
dbhost=192.168.XX.XX
dbport=27017
#dbreplicaset=[false if you are not using MongoDB replicaset]
#dbhostport=[host1:port1,host2:port2,host3:port3]
dbusername=dashboarduser
dbpassword=dbpassword
jenkins.cron=0 0/1 * * * *
jenkins.servers[0]=http://192.168.XX.XX:80XX/
#   set username/apiKey to use HTTP Basic Auth (blank=no auth)
jenkins.usernames[0]=
jenkins.apiKeys[0]=
jenkins.saveLog=true

Closed this issue as a complete restart resolved couple of my problems above.. Will open a new request with updated content.
Thanks.

Reopened issue with updated issue comments

Lol.. It got resolved.. Looks like I have created with other user and trying to access with a different user.. Hence closing it


optimize setting up problem

As I mentioned before in #2, changing from tr(F*Z) to dot(F, Z) dramatically improves performance, so I'm submitting it as a PR here. I also did a couple of fixes to the tests so everything would run.
For benchmarking I used the code
using QuantumNPA
using MosekTools
using JuMP

function benchmark()
    @dichotomic A1 A2 B1 B2
    S = A1 * (B1 + B2) + A2 * (B1 - B2)

    for level in 1:16
        println("Level $level:")
        gamma = npa_moment(S, level)
        @time model = npa2jump(S, gamma; solver = Mosek.Optimizer)
    end
end

Before the change I got
Level 1:
  0.000920 seconds (5.54 k allocations: 266.219 KiB)
Level 2:
  0.001654 seconds (40.01 k allocations: 2.812 MiB)
Level 3:
  0.013942 seconds (252.50 k allocations: 18.960 MiB, 48.40% gc time)
Level 4:
  0.024541 seconds (1.08 M allocations: 82.240 MiB)
Level 5:
  0.111893 seconds (3.50 M allocations: 269.043 MiB, 17.43% gc time)
Level 6:
  0.282036 seconds (9.40 M allocations: 724.695 MiB, 14.52% gc time)
Level 7:
  0.685988 seconds (22.00 M allocations: 1.659 GiB, 15.45% gc time)
Level 8:
  1.549258 seconds (46.36 M allocations: 3.501 GiB, 15.54% gc time)
Level 9:
  3.607801 seconds (90.01 M allocations: 6.798 GiB, 23.36% gc time)
Level 10:
  6.860917 seconds (163.63 M allocations: 12.359 GiB, 15.32% gc time)
Level 11:
 14.217260 seconds (281.84 M allocations: 21.294 GiB, 19.05% gc time)
Level 12:
 25.891500 seconds (464.09 M allocations: 35.058 GiB, 19.29% gc time)
Level 13:
 45.181614 seconds (735.46 M allocations: 55.565 GiB, 20.28% gc time)
Level 14:
 74.688912 seconds (1.13 G allocations: 85.201 GiB, 21.90% gc time)
Level 15:
117.945080 seconds (1.68 G allocations: 126.985 GiB, 22.33% gc time)
Level 16:
177.768142 seconds (2.44 G allocations: 184.620 GiB, 22.56% gc time)

And after it
Level 1:
  0.269014 seconds (506.21 k allocations: 34.541 MiB, 14.69% gc time, 99.57% compilation time)
Level 2:
  0.001372 seconds (37.29 k allocations: 1.503 MiB)
Level 3:
  0.003807 seconds (240.13 k allocations: 9.833 MiB)
Level 4:
  0.014111 seconds (1.04 M allocations: 42.509 MiB)
Level 5:
  0.090406 seconds (3.40 M allocations: 139.224 MiB)
Level 6:
  0.224277 seconds (9.20 M allocations: 375.420 MiB, 12.35% gc time)
Level 7:
  0.551686 seconds (21.60 M allocations: 881.630 MiB, 17.85% gc time)
Level 8:
  1.137214 seconds (45.64 M allocations: 1.820 GiB, 16.84% gc time)
Level 9:
  2.158229 seconds (88.78 M allocations: 3.536 GiB, 17.26% gc time)
Level 10:
  3.839511 seconds (161.64 M allocations: 6.433 GiB, 17.50% gc time)
Level 11:
  6.458086 seconds (278.72 M allocations: 11.093 GiB, 16.74% gc time)
Level 12:
 10.558023 seconds (459.40 M allocations: 18.276 GiB, 17.05% gc time)
Level 13:
 16.585933 seconds (728.60 M allocations: 28.987 GiB, 17.13% gc time)
Level 14:
 25.178052 seconds (1.12 G allocations: 44.473 GiB, 17.12% gc time)
Level 15:
 37.362517 seconds (1.67 G allocations: 66.321 GiB, 17.20% gc time)
Level 16:
 54.556266 seconds (2.43 G allocations: 96.482 GiB, 17.40% gc time)

Now what made the time become comparable to moment was to set up the primal instead of the dual. I wrote a primal version of the function:
function sdp2jump_primal(expr, ineqs; goal = :maximise, solver = nothing, verbose = nothing)
    if goal in (:maximise, :maximize, :max)
        maximise = true
        s = 1
    elseif goal in (:minimise, :minimize, :min)
        maximise = false
        s = -1
    end

    model = !isnothing(solver) ? Model(solver) : Model()

    mons = collect(m for m in monomials(expr, ineqs) if !isidentity(m))
    coeffs = [expr[m] for m in mons]

    nvars = length(mons)
    @variable(model, x[1:nvars])

    objective = expr[Id] + LinearAlgebra.dot(coeffs,x)
    if maximise
        @objective(model, Min, objective)
    else
        @objective(model, Max, objective)
    end

    Fs = [ineqs[1][m] for m in mons]

    d = size(ineqs[1])[1]
    bigF = spzeros(d^2, nvars)
    for i = 1:nvars
        bigF[:,i] .= vec(ineqs[1][mons[i]])
    end

    moment_matrix = ineqs[1][Id] + reshape(bigF*x,d,d)
    @constraint(model, LinearAlgebra.Symmetric(moment_matrix) in PSDCone())
    set_verbosity!(model, verbose)

    return model
end

And with it the times are:
Level 1:
  0.002385 seconds (4.49 k allocations: 170.281 KiB)
Level 2:
  0.001507 seconds (8.96 k allocations: 423.141 KiB)
Level 3:
  0.001799 seconds (21.99 k allocations: 1.184 MiB)
Level 4:
  0.003552 seconds (46.68 k allocations: 2.838 MiB)
Level 5:
  0.008864 seconds (91.25 k allocations: 5.992 MiB)
Level 6:
  0.019090 seconds (173.10 k allocations: 11.520 MiB)
Level 7:
  0.044233 seconds (285.85 k allocations: 20.156 MiB)
Level 8:
  0.086811 seconds (448.05 k allocations: 32.428 MiB)
Level 9:
  0.141756 seconds (673.39 k allocations: 50.452 MiB)
Level 10:
  0.262950 seconds (977.21 k allocations: 73.765 MiB)
Level 11:
  0.428602 seconds (1.37 M allocations: 107.310 MiB)
Level 12:
  0.725241 seconds (1.94 M allocations: 148.197 MiB, 3.46% gc time)
Level 13:
  1.108296 seconds (2.59 M allocations: 200.118 MiB)
Level 14:
  1.744433 seconds (3.39 M allocations: 265.745 MiB, 3.24% gc time)
Level 15:
  2.625790 seconds (4.36 M allocations: 343.377 MiB, 5.41% gc time)
Level 16:
  4.130944 seconds (5.53 M allocations: 443.056 MiB, 11.99% gc time)

Unfortunately when we send the primal problem to MOSEK it becomes really, really slow. One can see that it is indeed solving the primal instead of the dual, and apparently this doesn't work for this problem.
Now there should be a way to get the setup up time as fast as the primal and the solution time as fast as the dual, I'll write to the JuMP devs to see if they know.

And as I hoped, the tireless @blegat showed up to save the day: https://discourse.julialang.org/t/performance-of-primal-versus-dual-forms-in-jump/116633
Don't merge this yet, I'll implement his solution properly tomorrow.

That's more like it.

That would be great, I want to see it beat Moment.

I'll check but I'm not super optimistic. At the moment I get (on a slow VM):
julia> @time gamma = npa_moment(S, 16);
  5.718031 seconds (70.07 M allocations: 1.882 GiB, 6.82% gc time, 0.13% compilation time)

This is not dramatically slower than the old version (git checkout bfad4e6 ., from 29 Jul 2022):
julia> @time gamma = npa_moments(ops_at_level(S, 16));
  4.867666 seconds (61.98 M allocations: 1.460 GiB, 5.69% gc time)

For comparison, my old Lisp version (on the same VM) seems to be ten times as fast or more:
NPA-USER> (time
           (with-operators (A1 A2 B1 B2)
             (let ((ops (monomials-at-level (list A1 A2 B1 B2) 16)))
               (npa-moments ops))))
Evaluation took:
  0.346 seconds of real time
  0.346212 seconds of total run time (0.326470 user, 0.019742 system)
  100.00% CPU
  812,203,052 processor cycles
  230,122,336 bytes consed

So I'm doubtful if it's the algorithm that's the bottleneck.

Sounds like a simple implementation detail is holding it back.

Well I can have a shot at profiling in a couple of weeks when I'm more likely to have the time. But in the end, if Julia isn't as fast as Lisp then there won't really be anything I can do about it.

Lol there is no way Julia is the problem. Look at some benchmarks here. Julia is competitive with C and FORTRAN, which LISP is definitely not.

No, compiled Common Lisp can get in the same ballpark with performance as C. See the benchmark results here or the results of this study for instance.


It seems you got one learning rate per epoch.

If I read your code correctly, I think your learning rate computes based on number of epochs, not loops. According to the paper, it seems the learning rate should be computed based on number of loops.

@ArchNew The parameter epochcan be INT as well as FLOAT.
So you can provide the value like 0.01, 0.02, ...
In other words, you can calculate the fractional value of epoch which is propotional to steps, and then you can use the value.
Something like..

for epoch in ...
    for step in ...
       curr_epoch = epoch + float(step) / num_steps

Thanks!


chore: add issues templates

Added issues templates. Templates are mostly copied from MUI. Feel free to edit :smiley:

great @ChromeGG thanks for the contribution


can I send a message directly to the DLQ before it reaches the maximum number of retries?

FEATURE REQUEST
Is there any way to get the message retry to end early and then put the message in the dead letter queue?

If the consumer can decide don't want to re-consume the message again, the consumer could return consume success to mock drop the message instead to try send to DLQ


Bring in Helmet w/ all the necessary custom data.

Fixed in https://github.com/storycopter/storycopter-idoc/commit/e3f2093b0b2f0cf1bf1b785a7c21c4f7a89493fa and https://github.com/storycopter/storycopter-idoc/commit/4cb7f96fff4f3914f7c2a48057abe51e6945acee


Update to v1.6.8

Kata Containers has moved and updated the binary dependencies to containerd v1.6.8.  Due to this, let's rebase the branch on our side.

We've tested this branch in kata with commit https://github.com/kata-containers/kata-containers/pull/5698/commits/1bc0705729278d3592c7298118209182b0637622 and running tests
http://jenkins.katacontainers.io/job/tests-CCv0-ubuntu-20.04-x86_64-CC_CRI_CONTAINERD_K8S-PR/205/consoleFull and http://jenkins.katacontainers.io/job/tests-CCv0-ubuntu-20.04-x86_64-CC_CRI_CONTAINERD-PR/290/ which passed, so I'm happy to merge based on this


add KubeRay manifests

Added All the KubeRay Manifests from ODH Contrib Manifests into this repo.
Updated the KfDef to pull the KubeRay manifests from this repo.
Updated the README and QuickStart to account for new content in this repo.

@MichaelClifford Could you also change the following paragraph in quick-start because it's outdated by the oc apply -f odh-core.yaml -n opendatahub.
If you do not currently have Open Data Hub installed on your cluster, you can find instructions for installing it [here](https://opendatahub.io/docs/getting-started/quick-installation.html).
To
If you do not currently have Open Data Hub installed on your cluster, you can find instructions for Installing the Open Data Hub Operator [here](https://opendatahub.io/docs/getting-started/quick-installation.html).

@MichaelClifford can you rebase this?

Thanks for the reviews @accorvin and @tedhtchang,rebased and changes made.


feat: Count up - Allowing counting days since an event

Prerequisites

[X] I have read the Contributing Guidelines.
[X] I agree to follow the Code of Conduct.
[X] I have searched for existing issues that already include this feature request, without success.

Describe the Feature Request
Currently, the app only can be used as an countdown to see how much time is left until an specific date is reached.
I wanted to do the same for the time since an event has happened.
Describe the Use Case
I can't really say what I am tracking, but my goal is to get something done until an specific date in about half an year. I wanted to track the dates since I started to get an feeling of the speed of progress.
Describe Preferred Solution
If an date is set in the past , the text "days until" changes to "days since" and the number of days starts adding up
Describe Alternatives
No response
Related Code
No response
Additional Information
No response

Thanks for your feature proposal! I think the feature you want is like:
Now(03/19)
Countup from 03/16: 3days
Countdown for 03/21: 2days
It should be quite useful. I'll add this feature to the next release :+1:


Best practice: test build without actually deploying

How can I test the action completely without actually deploying it - Is there a property I can set or a different action I should use?

Azure Static Web Apps is a wrapper of Web App + Azure Functions API. You can test each one separately as you would do without Azure Static Web Apps, based on the libraries/technology you chose.

That isn't quite right. While Azure Static Web Apps supports a lot of the same behaviors as using a Web App + Azure Function in conjunction, there is a lot more (i.e. global distribution, free SSL certs) that is added as well. It isn't simply a wrapper.
@dfberry you could have a separate workflow that runs on every commit to simply run the build / test components without deploying. To do this, you can remove the ' azure_static_web_apps_api_token' from your workflow file inputs and add 'skip_deploy_on_missing_secrets' as an environment variable with the value 'true'. Similar to this thread: https://github.com/Azure/static-web-apps/issues/679

@miwebst of course. I meant that the code is separated from Azure Static Web Apps hosting and the code can be built as a regular app.
Azure Static Web Apps is super cool service :)


Fix Typos in Documentation

This PR addresses minor typographical errors in the documentation to enhance readability and maintain grammatical accuracy:

README.md

Corrected "double check" to "double-check".

crates/examples/push-cdn/README.md

Updated "a nvidia GPU" to "an nvidia GPU".

Key Places to Review

README.md: Ensure clarity and proper use of "double-check".
crates/examples/push-cdn/README.md: Verify appropriate grammatical correction.

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


Changes to alert PIG jobs and an extra rule in alerting

This PR contains the following changes:

If a PIG job execution is retried & parameter set in this execution is retried >=2 times then set the flag auto tuning fault to true in job execution. This way this job execution gets alerted and the parameter set gets penalized. Due to the unavailability of exception fingerprinting for PIG, this is a very elementary approach to alert PIG jobs.

Developers are alerted if a parameter set is in the "EXECUTED" state for the last 2 days.

Test on EI , rest is fine

Tested on EI, everything works fine.


fix: properly pass the git token to private quickstarts if the domains match

so we can use, say, github enterprise and quickstarts hosted on a private GHE server

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign jstrachan
You can assign the PR to them by writing /assign @jstrachan in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/approve

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jstrachan
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [jstrachan]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Don't bundle the fallback grab/grabbing cursor images when running gulp mozcentral

These cursor images are only necessary as a fallback for older browsers, hence there's no reason to keep shipping them in Firefox as far as I can tell; see https://developer.mozilla.org/en-US/docs/Web/CSS/cursor#Browser_compatibility

/botio-linux preview

I would agree that Firefox does not need this. Thanks!


Nested custom headers

I'm trying to add authentication to the header using http-data, but the nested object becomes an array instead of a nested object.
{ "headers": { "Authorization": 'TOKENKEY' } }
Becomes: headers[Authorization]:

I could solve it by setting a global setting for vue-resource.
Vue.http.headers.common['Authorization'] = $.cookie('access_token');
But it would be great if this could be passed correctly to vuetable instead.

@tmikaeld According to vue-resource doc, it is supposed to be and Object, not an Array.
  <vuetable
     //...
     :http-data="options"
  ></vuetable>

  new Vue({
    el: 'body',
    data: {
      options: {
        headers: {
          "Authorization": $.cookie('access_token')
        }
      }
    }
  })

If i set it up exactly like that, it is created as a query parameter in the request rather than a header.

@tmikaeld I didn't really use this feature myself, so I'm not sure what happens.
Can you please give me and example on how it should actually look in the request? May be I can check and do something with it.

What i think happens is that the nested Authorization object is converted to an array.
You can see in vue-resource that it's referenced like this:
Vue.http.headers.common['Authorization'] = $.cookie('access_token');
This is how it should look:

If i set the Auth object directly to line 625 in vuetable, it works - so it's obviously somewhere else it get converted to a different type:
Line 625:
 this.$http.get(url, this.httpData, {headers: {"Authorization": $.cookie('access_token')}}).then(function (response) {....

@tmikaeld, could you give us a code snippet on how you finally solved this?

@abishekrsrikaanth Just change :http-data="options" to :http-options="options"

@tmikaeld , thank you. much appreciated


Add a Gitter chat badge to README.md

nebula-plugins/nebula-plugin-plugin now has a Chat Room on Gitter
@rspieldenner has just created a chat room. You can visit it here: https://gitter.im/nebula-plugins/nebula-plugin-plugin.
This pull-request adds this badge to your README.md:

If my aim is a little off, please let me know.
Happy chatting.
PS: Click here if you would prefer not to receive automatic pull-requests from Gitter in future.

Nebula » nebula-plugin-plugin-pull-requests #11 SUCCESS
This pull request looks good


fix: duplicate adds

Fixes issue where subdeps could be added twice
Adds pkg.pr.new previews to PRs

hoping comments start working next time


Linda bugs 524 merge to master

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/exchange-web-services/get-started-with-ews-client-applications.md
:white_check_mark:Succeeded

docs/exchange-web-services/how-to-access-contacts-as-a-delegate-by-using-ews-in-exchange.md
:white_check_mark:Succeeded

docs/exchange-web-services/how-to-add-and-remove-delegates-by-using-ews-in-exchange.md
:white_check_mark:Succeeded

docs/exchange-web-services/how-to-work-with-conversations-by-using-ews-in-exchange.md
:white_check_mark:Succeeded

docs/management/how-to-get-a-list-of-mail-users-by-using-the-exchange-management-shell.md
:white_check_mark:Succeeded

docs/web-service-reference/applyconversationactionresponsemessage.md
:white_check_mark:Succeeded

docs/web-service-reference/baseshape.md
:white_check_mark:Succeeded

docs/web-service-reference/cancelcalendaritem.md
:white_check_mark:Succeeded

docs/web-service-reference/conversationid.md
:white_check_mark:Succeeded

docs/web-service-reference/convertidresponsemessage.md
:white_check_mark:Succeeded

docs/web-service-reference/copyfolderresponsemessage.md
:white_check_mark:Succeeded

docs/web-service-reference/copyitemresponsemessage.md
:white_check_mark:Succeeded

docs/web-service-reference/createattachmentresponsemessage.md
:white_check_mark:Succeeded

docs/web-service-reference/createfolderpathresponsemessage.md
:white_check_mark:Succeeded

docs/web-service-reference/createfolderresponsemessage.md
:white_check_mark:Succeeded

docs/web-service-reference/createitemresponsemessage.md
:white_check_mark:Succeeded

docs/web-service-reference/createmanagedfolderresponsemessage.md
:white_check_mark:Succeeded

docs/web-service-reference/createuserconfigurationresponsemessage.md
:white_check_mark:Succeeded

docs/web-service-reference/deletefolderresponsemessage.md
:white_check_mark:Succeeded

docs/web-service-reference/dictionarykey.md
:white_check_mark:Succeeded

docs/web-service-reference/disconnectphonecallresponse.md
:white_check_mark:Succeeded

docs/web-service-reference/emptyfolderresponsemessage.md
:white_check_mark:Succeeded

docs/web-service-reference/endtime.md
:white_check_mark:Succeeded

docs/web-service-reference/entry-emailaddress.md
:white_check_mark:Succeeded

docs/web-service-reference/entry-imaddress.md
:white_check_mark:Succeeded

docs/web-service-reference/entry-phonenumber.md
:white_check_mark:Succeeded

docs/web-service-reference/entry-physicaladdress.md
:white_check_mark:Succeeded

docs/web-service-reference/expanddlresponsemessage.md
:white_check_mark:Succeeded

docs/web-service-reference/exportitemsresponsemessage.md
:white_check_mark:Succeeded

docs/web-service-reference/extendedproperty-pathtoextendedfieldtype.md
:white_check_mark:Succeeded

docs/web-service-reference/fieldorder.md
:white_check_mark:Succeeded

docs/web-service-reference/filterhtmlcontent.md
:white_check_mark:Succeeded

docs/web-service-reference/findconversationresponse.md
:white_check_mark:Succeeded

docs/web-service-reference/findfolderresponsemessage.md
:white_check_mark:Succeeded

docs/web-service-reference/finditemresponsemessage.md
:white_check_mark:Succeeded

docs/web-service-reference/findmessagetrackingreportresponse.md
:white_check_mark:Succeeded

docs/web-service-reference/folderid.md
:white_check_mark:Succeeded

docs/web-service-reference/forwarditem.md
:white_check_mark:Succeeded

docs/web-service-reference/getattachmentresponsemessage.md
:white_check_mark:Succeeded

docs/web-service-reference/geteventsresponsemessage.md
:white_check_mark:Succeeded

docs/web-service-reference/getfolderresponsemessage.md
:white_check_mark:Succeeded

docs/web-service-reference/getinboxrulesresponse.md
:white_check_mark:Succeeded

docs/web-service-reference/getitemresponsemessage.md
:white_check_mark:Succeeded

docs/web-service-reference/getmessagetrackingreportresponse.md
:white_check_mark:Succeeded

docs/web-service-reference/getpasswordexpirationdateresponse.md
:white_check_mark:Succeeded

docs/web-service-reference/getphonecallinformationresponse.md
:white_check_mark:Succeeded

docs/web-service-reference/getroomlistsresponse.md
:white_check_mark:Succeeded

docs/web-service-reference/getroomsresponse.md
:white_check_mark:Succeeded

docs/web-service-reference/getservertimezonesresponsemessage.md
:white_check_mark:Succeeded

docs/web-service-reference/getserviceconfigurationresponse.md
:white_check_mark:Succeeded

This comment lists only the first 50 files in the pull request.
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Bus filters

In this PR we move the concept of Filter from the level of CommandBus to the level of Bus.
This makes the flow of Bus.post() more fluent and general.

@armiol, PTAL.

@armiol, PTAL again.

@armiol, PTAL again.

@armiol, PTAL again.

DeadMessageHandler renamed to DeadMessageTap;
MessageRejection moved to io.spine.core.

Let's discuss the packaging preferences (io.spine.core vs io.spine.server.bus).


Add support for (new) workspace feature

See http://flutter.dev/go/pub-workspace

Hi @kevmoo, I see there's a pubspec_parse_update branch and #1946 in the past few days -- any change this will be in there or a different PR?


Cannot set the RTC on the NUCLEO-F746ZG

I can properly set the RTC on the DISCO-F746NG, but not on the NUCLEO-F746ZG
...kevin

@bcostm @adustm

I checked the Nucleo_display_time example on both DISCO_F746 and NUCLEO_F746 and it works. I used mbed lib v116. Which code do you use ? Can you share it ?

I cannot share this code publicly.  I will try the Nucleo_display_time example and will get back to you on Tuesday.
Thanks,...kevin
On Friday, March 18, 2016 7:39 AM, bcostm<EMAIL_ADDRESS>wrote:

I checked the Nucleo_display_time example on both DISCO_F746 and NUCLEO_F746 and it works. I used mbed lib v116. Which code do you use ? Can you share it ?—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub

My issue had to do with the mktime structure.  I was not subtracting 1900 from the year, creating a -1 return value for total seconds.  Sorry for the false alarm.

@loopsva For the future, please add code snippet  to reproduce the problem.


Selecting token and clicking INIT on sheet gives error "no token selected for rolling initiative!"

When I select a token and click Init on their sheet to add them to initiative.

This happens when the token has not been added to the combat tracker.


R.juxt should be a binary function

According to the documentation, R.juxt "applies a list of functions to a list of values".
I assumed the function would be of type [a -> b] -> [a] -> [b], but it actually has a complex type I find difficult to grok: [(a, b, ..., m) -> n] -> ((a, b, ..., m) -> [n]).
What's our reason for choosing this type?
For now I'll use R.ap, which in my view is a much simpler function. (I currently wish to apply a list of functions to a single value, so the difference between ap and juxt is not important.)

What's our reason for choosing this type?

i think that is traceable to its clojure roots.
i agree the sig you suggest is clearer. it is essentially the sig of ap.

Discussions in #986 and #1495.
The basic idea was that it should behave like compose, cond, converge, et. al.
While it does overlap with ap, it is more powerful (and filled with more JS goodies weirdness.)

I personally find the current behavior very intuitive in JS context, and quite useful (see R.partition). I rarely find ap useful for arrays, and when I did use it, it was wrapped with something like useWith(ap, [identity, of]).

How would the proposed function behave? It would have signature [a -> b] -> [a] -> [b]. But would the result of R.juxt([f, g, h], [x, y, z]) be [f x, g y, h z] or would it be [f x, f y, f z, g x, g y, g z, h x, h y, h z]? The former is identical to R.zipWith(R.call) and the later is identical to R.ap. So neither seems useful.

welcome back, @paldepind !

Agreed on all points @paldepind.  (uh oh!  :smile:)  And, also, welcome back.

Thank you very much :smile: I'm not making a grand return. But I do miss you.

"applies a list of functions to a list of values"

Are there some more concrete terms for describing how a list of functions can be applied to a list of values? Because I can think of a few different possibilities which @paldepind has also alluded to.
For instance, isn't there a possible difference in the output order depending on how list items are processed?
[f x, g x, h x] + [f y, g y, h y] + [f z, g z, h z]
vs
[f x, f y, f z] + [g x, g y, g z] + [h x, h y, h z]

How about

Creates a new function out of a list of functions that will return a list created by applying each of those functions to the arguments supplied.  For example, if fn = juxt([f, g, h]), then fn(a, b) //=> [f(a, b), g(a, b), h(a, b)]

??

:thumbsup: that is better for sure. i like how you show the function application with generics

I won't bother doing anything about this until we figure out #1774, but if we keep juxt, I think this would be a reasonable improvement.

There is an edge case to consider where the function list only contains 0-ary functions. In this case, i think a binary_juxt may behave unexpectedly if curryN is used internally.
const fns = [always(0)] // 0-ary function list

juxt(fns)() // executes fine -- returns 0
binary_juxt(fns)() // will not execute due to curryN requiring one more value

Maybe the same consideration with applySpec, if it ever gets turned to binary function.


[CursorAI] Activating Swift extension failed: Failed to find lldb-dap in Swift toolchain

Describe the bug
I am trying out CursorAI which is an editor based off VSCode 1.91.1. Commonly there are no issues with extensions, but when I add Swift one, I get an error toast  saying "Activating Swift extension failed: Failed to find lldb-dap in Swift toolchain".
After some googling around, common fix stated is "install swift", however when I run swift --version I do get following output
swift-driver version: 1.115 Apple Swift version 6.0 (swiftlang-<IP_ADDRESS>.10 clang-16<IP_ADDRESS>)
Target: arm64-apple-macosx15.0

So am currently not sure if there is anything else I could try, hence leading me to think that this might be a bug with either using cursor or swift 6.0?
I also did not get any prompts to set any extras up after installing the extension.
To Reproduce
Steps to reproduce the behavior:

Download https://www.cursor.com
Add Swift Extension, restart editor just in case
Open any swift project that uses some import i.e. SwiftUI and you'll get errors all across when using any of the views
Additionally observe error toast that pops up at the bottom left

Expected behavior
Should install and set everything up correctly.
Environment

OS: macOS Sequoia
Swift version:

swift-driver version: 1.115 Apple Swift version 6.0 (swiftlang-<IP_ADDRESS>.10 clang-16<IP_ADDRESS>)
Target: arm64-apple-macosx15.0

Visual Studio Code version: Version: 0.40.4, VSCode Version: 1.91.1
vscode-swift version: v1.11.0

Additional context

Hi @xzilja, from inside Cursor could you do >  Swift: Capture VS Code Swift Diagnostic Bundle, choose Capture Minimal Diagnostics and attach the results to this issue?
Do you have Xcode installed, have you installed a Swift toolchain from https://www.swift.org/download/, or none of the above?
In the meantime you can try working around this by setting "swift.debugger.useDebugAdapterFromToolchain": false in your VS Code user settings.json.

@plemarquand Sure thing, here are the results
extension-logs.txt
settings.txt
I have latest XCode 16 RC installed and did not install Swift toolchain separately (is this one of the requirements? I was under impression that it comes bundled with XCode when it is set up).
I tried adding "swift.debugger.useDebugAdapterFromToolchain": false but am still seeing a lot of "not found" errors like this one that happens for @Model macro from SwfitData for example (all is fine within XCode):
External macro implementation type 'SwiftDataMacros.PersistentModelMacro' could not be found for macro 'Model()'; plugin for module 'SwiftDataMacros' not foundSourceKit
MyTestModel.swift(5, 13): 'Model()' declared here (SwiftData.Model)

Thanks for attaching more info. Xcode16 Beta should be sufficient, I was just trying to get an idea of how Swift was installed on your system.

Apologies, I should have said set "swift.debugger.useDebugAdapterFromToolchain": true not false. That will use the lldb debug adapter from Xcode and not from the CodeLLDB VS Code extension.

@xzilja I've addressed the failed activation with my most recent PR, but it's not really going to solve your issue if you want to use lldb-dap (if you're not enabling swift.debugger.useDebugAdapterFromToolchain then you're probably fine for now). I'm interested in determining why the extension couldn't identify your lldb-dap executable. Could you try running xcrun --find lldb-dap in your terminal and provide the output here?

@xzilja could you try running xcrun --find lldb-dap in your terminal and provide the output here?

@xzilja we're closing this, please reopen if you're still seeing


Fix typos

/ok-to-test

@mgrachev thanks for this PR.  Can you address the DCO action to move this forward?

@mgrachev can you please sign off your commits and bump the chart version? TIA
/assign

Done.

Would be much better to have separate PRs for each of the charts, so we can resolve separate issues.
There seems to be an issue with the Redis and Keycloak charts as well.

https://github.com/helm/charts/pull/8632
https://github.com/helm/charts/pull/8679
https://github.com/helm/charts/pull/8680
https://github.com/helm/charts/pull/8695
https://github.com/helm/charts/pull/8696
https://github.com/helm/charts/pull/8699
https://github.com/helm/charts/pull/8700
https://github.com/helm/charts/pull/8701
https://github.com/helm/charts/pull/8702
https://github.com/helm/charts/pull/8703
https://github.com/helm/charts/pull/8704


Chromium: installed app won't launch

Describe the bug
I discovered today a really fun feature: installing web apps in chromium. For instance, if you browse to https://xournal.online/ on chromium, you can install the app locally:

Once installation is done, the website now runs as a separate application. You also should see on your desktop:

and in chrome://apps/ the app you installed. If you directly launch the app from chrome://apps/ it works directly. However, if you click on the app from the desktop, nothing happens. When inspecting the .desktop file, the reason is clear: it contains a line pointing to the unwrapped chromium:
Exec=/nix/store/76qscl06ahki1v240c9y76l4lixj45af-chromium-unwrapped-95.0.4638.54/libexec/chromium/chromium --profile-directory=Default --app-id=ncokflffjgpjncjjifkomecgbombmdgj

Instead, it should point to the wrapped chromium.
Steps To Reproduce
Steps to reproduce the behavior:

Go to https://xournal.online/
Install the app (button in url bar)
Launch it from the shortcut added in your desktop (at least appears in KDE plasma)

How to fix it (edited)
I think the issue comes from this line in the wrapper script:
exec "/nix/store/76qscl06ahki1v240c9y76l4lixj45af-chromium-unwrapped-95.0.4638.54/libexec/chromium/chromium"   "$@"

To ensure the name of the executable is propagated properly, I guess it should instead be something like:
exec -a "$0" "/nix/store/76qscl06ahki1v240c9y76l4lixj45af-chromium-unwrapped-95.0.4638.54/libexec/chromium/chromium"   "$@"

Notify maintainers
@primeos @danielfullmer @Frostman @thefloweringash

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/chromium-based-installed-apps-pwa-sometimes-accidentally-garbage-collected/35700/8


Fix for running on Mono

Fix for Fleck not working fully on Mono so added compiler runtime checks. Tested on Windows 8.1 also.

Thanks. CI should deploy a new Nuget in awhile.


Monitor goes totally black when monitorcontrol is started

Checklist

[x] I have searched for existing issues
[x] I have looked through the Monitor Troubleshooting wiki
[x] I have updated MonitorControl to the latest version

Describe the issue
When I open monitorcontrol, the monitor screen simply goes totally black. After a few seconds the cursor appears and can be moved around but nothing else does. Adjusting the brightness through monitorcontrol on my laptop screen doesn't have any affect, and the blackness continues after mc is quit, until I disconnect the monitor and reconnect it.
Screenshots
The weird thing is that screenshots appear as if the display is functioning normally. Here's a comparison, I took a screen recording and then a video with my phone: https://imgur.com/a/hCYSS0U
Environment Information:

macOS version: catalina, 10.15.6
MonitorControl version: 2.1.0
Monitor(s): HP 24fw with audio, 24 inch
Mac model: macbook pro 2019, 13 inch
Monitor Cable(s)/Connection(s): HDMI and an adapter for USB-C "thunderbolt"

I have same issue, suddenly my screen goes black and can only see mouse cursor
Environment Information:
macOS version: catalina, 10.15.6
MonitorControl version: 2.1.0
Monitor(s): Dell S2721QS with audio, 27 inch
Mac model: mac mini 2018
Monitor Cable(s)/Connection(s): DisplayPort to USB-C "thunderbolt"

solved after I change another DisplayPort to USB-C "thunderbolt" cable. I guess the problem comes from hardware rather than software

Damn, I tried that and it didn't do anything. Maybe neither adapter was good enough though, they were both 30 odd quid from amazon. I've seen direct USB-C to HDMI-out cables, so I might give that a go

Since this seems to be a hardware/adapter problem, I'll close this issue. Some adapters scramble ddc communication which might cause issues with the display as it can't interpret the i2c communication properly and writes data to the wrong registers in this case making the display crash or reboot. This is a rare but real problem unfortunatelly.


 IF YOU DO NOT FOLLOW THE FORMAT OR MAKE A GENERIC TOKEN REQUEST YOUR ISSUE WILL BE DELETED WITHOUT COMMENT
YOUR JUSTLIST MUST FOLLOW THE JSON SPECIFICATION
https://github.com/justswaporg/justlists/example.justlists.ts
Checklist

[x] I understand that this is not the place to request a token listing.
[ ] I have tested that my JustList is compatible by pasting the URL into the add a list UI at justswap.org.
[ ] I understand that filing an issue or adding liquidity does not guarantee addition to the justlists website.

Please provide the following information for your token.
JustList URL must be HTTPS.
JustList URL:
JustList Name:
Link to the official homepage of the JustList manager:

Sorry, but your issue will be closed because you did not submit your information in the correct format.

On Mon, 12 Apr 2021 at 11:24, JustSwapTeam @.***> wrote:

Closed #870 https://github.com/justswaporg/justlists/issues/870.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/justswaporg/justlists/issues/870#event-4580890827,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATNPH3MQACMQDD3UPQSCZNDTIK357ANCNFSM42FXEQ3A
.


Cannot download ebook

Hello,
Could you please to take a look on below issue when I'm trying to download:
orly-0.1.6\src\epub\builder.rs:236:17:
assertion left == right failed
left: 0
right: 1
stack backtrace:
0:     0x7ff7d2ae25c8 -
1:     0x7ff7d270adf9 -
2:     0x7ff7d2ad4c91 -
3:     0x7ff7d2ae3fa6 -
4:     0x7ff7d2ae389a -
5:     0x7ff7d2ae47a7 -
6:     0x7ff7d2ae41e7 -
7:     0x7ff7d2ae412f -
8:     0x7ff7d2ae4118 -
9:     0x7ff7d2c27a14 - locale_charset
10:     0x7ff7d2c27bf3 - locale_charset
11:     0x7ff7d2c292c4 - locale_charset
12:     0x7ff7d2a02d6a -
13:     0x7ff7d26aec72 -
14:     0x7ff7d26c9377 -
15:     0x7ff7d26c0cef -
16:     0x7ff7d2653af0 -
17:     0x7ff7d26cb53b -
18:     0x7ff7d2bf6dec - locale_charset
19:     0x7ffa3f20257d - BaseThreadInitThunk
20:     0x7ffa40b4af28 - RtlUserThreadStart

What is the id of the book? I want to reproduce it

What is the id of the book? I want to reproduce it

Hi @hurlenko ,
Book's ID<PHONE_NUMBER>489
Thank you.

@kumiter Try version 0.1.7

Hi @hurlenko ,
Many thanks for your quick response, let me try and back to you the result.

Hi @hurlenko ,
I can download ebook without issue. But there is some font issue with special characters. Example below:

Original:

Downloaded:

I don't have this problem, it might be something with your reader

Hi @hurlenko ,
I've tried both online and offline reader and also convert to PDF with same issue. Maybe relating with my font decoder during output process.
Many thanks for your help.

There might be some errors because the source files of the book may contain incompatible css rules or html tags. This is something I don't really want to dig in. Many ebook readers deal with it just fine, but still, the epub files produced by orly are not always 100% correct. Even though i tried to fix all errors and make it pass the epubcheck validator, each book might contain some incompatible css or html. You can try to convert it to some other format like mobi using calibre before using. It helps sometimes


Update requirements to MXNet 1.2.1

Pull Request Checklist

[x] Changes are complete (if posting work-in-progress code, prefix your pull request title with '[WIP]'
until you can check this box.
[x] Unit tests pass (pytest)
[x] Passed code style checking (./style-check.sh)
[x] Updated major/minor version in sockeye/__init__.py. Major version bump if this is a backwards incompatible change.
[x] Updated CHANGELOG.md

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

How about change numpy >= 1.14 to avoid the libiomp conflict in conda environment?

Merging for now. I will do the requirement for numpy >= 1.14 separately.


Missing Author addition

As requested, I added Pascal Bihler to author list and restored alphabetica…l order

Thanks.


consider using lodash modules

There are a number of core functions (like "flatten array") that are implemented in one way or another in ally.js, but could (and shoul) simply be replaced with the corresponding functions from lodash. Unlike underscore (currently loaded as devDependency but not used), lodash allows us to require specific functions, rather than the entire library.
Using lodash functions has a couple of benefits.

they're focused on making those utilities work as intended (we're offloading testing).
we don't need to care about that code anymore (we're reducing the amount of code we have to maintain).
code get's a tiny bit more readable.

import flattenArray from 'lodash/array/flatten';
flattenArray(data);

lodash/array/flatten could be used instead of the atrocious .requce(…) sprinkled all over ally.js:

maintain/disabled
style/focus-within
util/sort-element-by-tabindex (possibly)

lodash/lang/cloneDeep could replace occurrences of JSON.parse(JSON.stringify(
lodash/collection/contains could replace occurrences of .indexOf( that test against -1

Of course the current implementation works and using lodash modules would add weight to the library. The pros and cons of this need to be discussed.

That's a good idea. There can be a speed benefit as well.
It also allows to remove the "array.prototype.findindex": "^1.0.0" dependency I see in package.json...
Ideally, it would lead to two build versions: one including the used Lodash functions, for standalone usage, and another one requiring to load Lodash before Ally. The latter would result in a lighter library (80 KB minified is a bit heavy; of course, I don't expect a significant gain, though) for projects (like mines) already depending on Lodash.

It also allows to remove the "array.prototype.findindex": "^1.0.0" dependency

true.

Ideally, it would lead to two build versions: one including the used Lodash functions, for standalone usage, and another one requiring to load Lodash before Ally.

I think that may lead to an explosion of builds down the road. I believe it's ok to just bundle the few lodash components. My assumption here is that if you really care about that sort of stuff, you're going to go consume individual modules of ally anyway.
Is this something you'd like to tackle (so we're able to see the difference in file size)?

I would be my pleasure, although I haven't looked at the code yet (but you provide useful hints), not even started to use Ally (but I will soon, thanks to your help).
But I fear my limited free time will not allow this experiment, so don't rely on my help, alas.


Introduce VaryTec Hero Spot 60 fixture

According to user manual at https://images.thomann.de/pics/atg/atgdata/document/manual/449221_c_449221_481679_v3_en_online.pdf

coverage: 28.055%. remained the same when pulling 288af991ed6257486b6b1f25c317b12950528451 on hjtappe:fixtures-Hero-Spot-60 into 5807cb8daf975304a59673a730ed0c095e2a9550 on mcallegari:master.

Thanks for spotting and fixing this.


cuda out of memory

When I use one RTX4090 to train the modernNCA model, the cuda out of memory occurs. It seems that the modernNCA model need large cuda memory for trainning. My datasets have one million or more samples  with 10 category features and 31 numerical features. How to make the trainning work by single RTX4090? Thank you !

Thank you for trying modernNCA! As a retrieval model, the memory usage during training increases linearly with the size of the retrieval set, meaning that memory consumption can become significant when dealing with large-scale tabular datasets. If your computational resources are limited, you can try the following methods to reduce the memory usage of modernNCA:
We’ve found that even with extremely low sample rates (e.g., 1%–10%), performance only slightly decreases with proper hyperparameter tuning on most large-scale datasets. Therefore, you can opt to tune the model parameters with low sample rate and use a smaller batch size during inference. This will lower memory usage with small performance impact.
modernNCA uses PLR (lite) embedding to further enhance its capabilities, while it also increases memory usage. In some cases, you can disable PLR (lite) embedding by setting num_embeddings to None:
"num_embeddings": ["categorical",[None]]
Overall, we recommend using multiple GPUs for training if you have them available, as this will allow the model to fully realize its potential. You can achieve this by slightly modifying the framework with torch.nn.parallel.DataParallel.


SFDX Org Creation command fails with strange error DomainNotFound The org cannot be found

Summary
I have a command in the CI to create a scratch org
sfdx force:org:create -f config/project-scratch-def.json -a scratch-org -s -d 1 -u Prod --json
Whether I execute it through the CI or manually, I got the following error:
{
"status": 1,
"name": "DomainNotFound",
"message": "The org cannot be found",
"exitCode": 1,
"actions": [
"Verify that the org still exists',",
"If your org is newly created, wait a minute and run your command again',",
"If you deployed or updated the org's My Domain, logout from the CLI and authenticate again",",
"If you are running in a CI environment with a DNS that blocks external IPs, try setting SFDX_DISABLE_DNS_CHECK=true'"
],
"context": "Create",
"stack": "DomainNotFound: The org cannot be found\n    at Messages.createError (/Users/bdovh/.local/share/sfdx/client/7.182.1-dad7ae3/node_modules/@salesforce/core/lib/messages.js:446:16)\n    at Connection.isResolvable (/Users/bdovh/.local/share/sfdx/client/7.182.1-dad7ae3/node_modules/@salesforce/core/lib/org/connection.js:244:28)\n    at async Connection.retrieveMaxApiVersion (/Users/bdovh/.local/share/sfdx/client/7.182.1-dad7ae3/node_modules/@salesforce/core/lib/org/connection.js:190:9)\n    at async Connection.useLatestApiVersion (/Users/bdovh/.local/share/sfdx/client/7.182.1-dad7ae3/node_modules/@salesforce/core/lib/org/connection.js:214:32)\n    at async Connection.create (/Users/bdovh/.local/share/sfdx/client/7.182.1-dad7ae3/node_modules/@salesforce/core/lib/org/connection.js:98:17)\n    at async Org.init (/Users/bdovh/.local/share/sfdx/client/7.182.1-dad7ae3/node_modules/@salesforce/core/lib/org/org.js:766:31)\n    at async Org.create (/Users/bdovh/.local/share/sfdx/client/7.182.1-dad7ae3/node_modules/@salesforce/kit/lib/creatable.js:57:9)\n    at async scratchOrgCreate (/Users/bdovh/.local/share/sfdx/client/7.182.1-dad7ae3/node_modules/@salesforce/core/lib/org/scratchOrgCreate.js:174:24)\n    at async Create.createScratchOrg (/Users/bdovh/.local/share/sfdx/client/7.182.1-dad7ae3/node_modules/@salesforce/plugin-org/lib/commands/force/org/create.js:187:68)\n    at async Create._run (/Users/bdovh/.local/share/sfdx/client/7.182.1-dad7ae3/node_modules/@salesforce/command/lib/sfdxCommand.js:102:40)\nCaused by: MyDomainResolverTimeoutError: The client has timed out.\n    at PollingClient.subscribe (/Users/bdovh/.local/share/sfdx/client/7.182.1-dad7ae3/node_modules/@salesforce/core/lib/status/pollingClient.js:91:19)\n    at async MyDomainResolver.resolve (/Users/bdovh/.local/share/sfdx/client/7.182.1-dad7ae3/node_modules/@salesforce/core/lib/status/myDomainResolver.js:103:45)\n    at async Connection.isResolvable (/Users/bdovh/.local/share/sfdx/client/7.182.1-dad7ae3/node_modules/@salesforce/core/lib/org/connection.js:239:13)\n    at async Connection.retrieveMaxApiVersion (/Users/bdovh/.local/share/sfdx/client/7.182.1-dad7ae3/node_modules/@salesforce/core/lib/org/connection.js:190:9)\n    at async Connection.useLatestApiVersion (/Users/bdovh/.local/share/sfdx/client/7.182.1-dad7ae3/node_modules/@salesforce/core/lib/org/connection.js:214:32)\n    at async Connection.create (/Users/bdovh/.local/share/sfdx/client/7.182.1-dad7ae3/node_modules/@salesforce/core/lib/org/connection.js:98:17)\n    at async Org.init (/Users/bdovh/.local/share/sfdx/client/7.182.1-dad7ae3/node_modules/@salesforce/core/lib/org/org.js:766:31)\n    at async Org.create (/Users/bdovh/.local/share/sfdx/client/7.182.1-dad7ae3/node_modules/@salesforce/kit/lib/creatable.js:57:9)\n    at async scratchOrgCreate (/Users/bdovh/.local/share/sfdx/client/7.182.1-dad7ae3/node_modules/@salesforce/core/lib/org/scratchOrgCreate.js:174:24)\n    at async Create.createScratchOrg (/Users/bdovh/.local/share/sfdx/client/7.182.1-dad7ae3/node_modules/@salesforce/plugin-org/lib/commands/force/org/create.js:187:68)",
"warnings": [],
"commandName": "Create"
}
I don't understand why this error happens and how to fix it or find a workaround to it?
I can see the production org has the correct enhanced domain and the Sfdx Auth Url is correct and has not been changed. What is wrong here?
Steps To Reproduce:

Register for a new DevHub Trial org by a link https://developer.salesforce.com/promotions/orgs/dx-signup

You might see some error here, but actually looks like the devhub is created but with some delay.

Execute command sfdx force:auth:web:login -a bdssdxtry
In my case on this step I receive another error

So to workaround this error I use sfdx force:auth:web:login -a bdssdxtry -r https://incredible-appy-102739.my.salesforce.com but you need to replace it with your domain.

Try to execute a command sfdx force:org:create -f config/project-scratch-def.json -a scratch-org -s -d 1 --json or simply sfdx force:org:create -f config/project-scratch-def.json -a scratch-org -s -d 1.
I guess the scratch org definition file doesn't matter for this case, so you might just create a new blank sfdx project.
In case if it does matter, I can attach my file here https://gist.github.com/bdovh/408f1c570e8c5b030be05577f17f19ce

Expected result
I expect the scratch org to be created without issues.
Actual result
The error happens
{
"status": 1,
"name": "DomainNotFound",
"message": "The org cannot be found",
"exitCode": 1,
"actions": [
"Verify that the org still exists',",
"If your org is newly created, wait a minute and run your command again',",
"If you deployed or updated the org's My Domain, logout from the CLI and authenticate again",",
"If you are running in a CI environment with a DNS that blocks external IPs, try setting SFDX_DISABLE_DNS_CHECK=true'"
],
"context": "Create",
"stack": "DomainNotFound: The org cannot be found\n    at Messages.createError (/Users/bdovh/.local/share/sfdx/client/7.182.1-dad7ae3/node_modules/@salesforce/core/lib/messages.js:446:16)\n    at Connection.isResolvable (/Users/bdovh/.local/share/sfdx/client/7.182.1-dad7ae3/node_modules/@salesforce/core/lib/org/connection.js:244:28)\n    at async Connection.retrieveMaxApiVersion (/Users/bdovh/.local/share/sfdx/client/7.182.1-dad7ae3/node_modules/@salesforce/core/lib/org/connection.js:190:9)\n    at async Connection.useLatestApiVersion (/Users/bdovh/.local/share/sfdx/client/7.182.1-dad7ae3/node_modules/@salesforce/core/lib/org/connection.js:214:32)\n    at async Connection.create (/Users/bdovh/.local/share/sfdx/client/7.182.1-dad7ae3/node_modules/@salesforce/core/lib/org/connection.js:98:17)\n    at async Org.init (/Users/bdovh/.local/share/sfdx/client/7.182.1-dad7ae3/node_modules/@salesforce/core/lib/org/org.js:766:31)\n    at async Org.create (/Users/bdovh/.local/share/sfdx/client/7.182.1-dad7ae3/node_modules/@salesforce/kit/lib/creatable.js:57:9)\n    at async scratchOrgCreate (/Users/bdovh/.local/share/sfdx/client/7.182.1-dad7ae3/node_modules/@salesforce/core/lib/org/scratchOrgCreate.js:174:24)\n    at async Create.createScratchOrg (/Users/bdovh/.local/share/sfdx/client/7.182.1-dad7ae3/node_modules/@salesforce/plugin-org/lib/commands/force/org/create.js:187:68)\n    at async Create._run (/Users/bdovh/.local/share/sfdx/client/7.182.1-dad7ae3/node_modules/@salesforce/command/lib/sfdxCommand.js:102:40)\nCaused by: MyDomainResolverTimeoutError: The client has timed out.\n    at PollingClient.subscribe (/Users/bdovh/.local/share/sfdx/client/7.182.1-dad7ae3/node_modules/@salesforce/core/lib/status/pollingClient.js:91:19)\n    at async MyDomainResolver.resolve (/Users/bdovh/.local/share/sfdx/client/7.182.1-dad7ae3/node_modules/@salesforce/core/lib/status/myDomainResolver.js:103:45)\n    at async Connection.isResolvable (/Users/bdovh/.local/share/sfdx/client/7.182.1-dad7ae3/node_modules/@salesforce/core/lib/org/connection.js:239:13)\n    at async Connection.retrieveMaxApiVersion (/Users/bdovh/.local/share/sfdx/client/7.182.1-dad7ae3/node_modules/@salesforce/core/lib/org/connection.js:190:9)\n    at async Connection.useLatestApiVersion (/Users/bdovh/.local/share/sfdx/client/7.182.1-dad7ae3/node_modules/@salesforce/core/lib/org/connection.js:214:32)\n    at async Connection.create (/Users/bdovh/.local/share/sfdx/client/7.182.1-dad7ae3/node_modules/@salesforce/core/lib/org/connection.js:98:17)\n    at async Org.init (/Users/bdovh/.local/share/sfdx/client/7.182.1-dad7ae3/node_modules/@salesforce/core/lib/org/org.js:766:31)\n    at async Org.create (/Users/bdovh/.local/share/sfdx/client/7.182.1-dad7ae3/node_modules/@salesforce/kit/lib/creatable.js:57:9)\n    at async scratchOrgCreate (/Users/bdovh/.local/share/sfdx/client/7.182.1-dad7ae3/node_modules/@salesforce/core/lib/org/scratchOrgCreate.js:174:24)\n    at async Create.createScratchOrg (/Users/bdovh/.local/share/sfdx/client/7.182.1-dad7ae3/node_modules/@salesforce/plugin-org/lib/commands/force/org/create.js:187:68)",
"warnings": [],
"commandName": "Create"
}
It happens both on CI and on the local machine. On the latest version of the sfdx and also on the previous versions of the SFDX CLI.
Repository to reproduce: dreamhouse-lwc
System Information

Which shell/terminal are you using? (e.g. bash, zsh, powershell 5, powershell 7, cmd.exe, etc.)
I think it doesn't matter, on local machine zsh or bash.
On github actions I guess the default shell is used.

If you are using sfdx

Run sfdx version --verbose --json

If you are using sf

Run sf version --verbose --json
On my local machine

{
"cliVersion": "sfdx-cli/7.182.1",
"architecture": "darwin-x64",
"nodeVersion": "node-v18.12.1",
"pluginVersions": [
"@mshanemc/plugin-streaming 1.1.7 (user)",
"@mshanemc/sfdx-sosl 1.1.0 (user)",
"@oclif/plugin-autocomplete 1.3.6 (core)",
"@oclif/plugin-commands 2.2.1 (core)",
"@oclif/plugin-help 5.1.19 (core)",
"@oclif/plugin-not-found 2.3.9 (core)",
"@oclif/plugin-plugins 2.1.8 (core)",
"@oclif/plugin-search 0.0.4 (core)",
"@oclif/plugin-update 3.0.7 (core)",
"@oclif/plugin-version 1.1.3 (core)",
"@oclif/plugin-warn-if-update-available 2.0.15 (core)",
"@oclif/plugin-which 2.2.2 (core)",
"alias 2.1.12 (core)",
"apex 1.3.0 (core)",
"auth 2.3.3 (core)",
"community 2.0.18 (core)",
"config 1.4.22 (core)",
"custom-metadata 2.0.5 (core)",
"data 2.1.17 (core)",
"evergreen 0.34.0 (user)",
"evergreen-build 0.20.2 (user)",
"generator 2.0.13 (core)",
"info 2.2.13 (core)",
"limits 2.1.3 (core)",
"org 2.2.19 (core)",
"packaging 1.10.10 (core)",
"schema 2.1.19 (core)",
"signups 1.2.12 (core)",
"source 2.3.8 (core)",
"telemetry 2.0.5 (core)",
"templates 55.1.0 (core)",
"trust 2.2.2 (core)",
"user 2.1.22 (core)",
"@salesforce/sfdx-plugin-lwc-test 1.0.1 (core)",
"@salesforce/sfdx-scanner 3.7.1 (user)",
"salesforce-alm 54.8.4 (core)",
"shane-sfdx-plugins 4.43.0 (user)"
],
"osVersion": "Darwin 20.5.0",
"shell": "zsh",
"rootPath": "/Users/bdovh/.local/share/sfdx/client/7.182.1-dad7ae3"
}
On the github action ci
v16.18.1

added 984 packages, and audited 119 packages in 24s

77 packages are looking for funding
  run `npm fund` for details

3 vulnerabilities (1 moderate, 2 high)

To address all issues, run:
  npm audit fix

Run `npm audit` for details.
Version of SFDX CLI is: sfdx-cli/7.182.1 linux-x

Additional information

Same issue here. This is the error message I get:
ERROR running force:org:create:  The org cannot be found

Try this:
Verify that the org still exists',
If your org is newly created, wait a minute and run your command again',
If you deployed or updated the org's My Domain, logout from the CLI and authenticate again",
If you are running in a CI environment with a DNS that blocks external IPs, try setting SFDX_DISABLE_DNS_CHECK=true'

This seems to be working as normal again.

This seems to be working as normal again.

this is strange, what was that? why it is working as normal now?

This seems to be working as normal again.

this is strange, what was that? why it is working as normal now?

They probably had some DNS issues that they resolved.

Hi @warbio @bdovh seems like this has been resolved for both of you?

I

it seems to be working now. Do you know if this issue is going to reoccur?

Great, unfortunately, I don't know if it'll happen again. we are in a release period which can lead to some issues
https://github.com/forcedotcom/cli/issues/1690

@WillieRuemmele the issue has reoccured
Org creation failed with error DomainNotFound DomainNotFound: The org cannot be found
Run echo $(sfdx force:org:create -f src/unpackaged/config/project-scratch-def.json -a scratch-org -s -d 1 --json) > create.json
Create scratch org failed
Error message: DomainNotFound DomainNotFound: The org cannot be found
at Messages.createError (/usr/local/lib/node_modules/sfdx-cli/node_modules/@salesforce/core/lib/messages.js:446:16)
at Connection.isResolvable (/usr/local/lib/node_modules/sfdx-cli/node_modules/@salesforce/core/lib/org/connection.js:244:28)
at async Connection.retrieveMaxApiVersion (/usr/local/lib/node_modules/sfdx-cli/node_modules/@salesforce/core/lib/org/connection.js:190:9)
at async Connection.useLatestApiVersion (/usr/local/lib/node_modules/sfdx-cli/node_modules/@salesforce/core/lib/org/connection.js:214:32)
at async Function.create (/usr/local/lib/node_modules/sfdx-cli/node_modules/@salesforce/core/lib/org/connection.js:98:17)
at async Org.init (/usr/local/lib/node_modules/sfdx-cli/node_modules/@salesforce/core/lib/org/org.js:766:31)
at async Function.create (/usr/local/lib/node_modules/sfdx-cli/node_modules/@salesforce/kit/lib/creatable.js:57:9)
at async scratchOrgCreate (/usr/local/lib/node_modules/sfdx-cli/node_modules/@salesforce/core/lib/org/scratchOrgCreate.js:174:24)
at async Create.createScratchOrg (/usr/local/lib/node_modules/sfdx-cli/node_modules/@salesforce/plugin-org/lib/commands/force/org/create.js:187:68)
at async Create._run (/usr/local/lib/node_modules/sfdx-cli/node_modules/@salesforce/command/lib/sfdxCommand.js:102:40)
Caused by: MyDomainResolverTimeoutError: The client has timed out.
at PollingClient.subscribe (/usr/local/lib/node_modules/sfdx-cli/node_modules/@salesforce/core/lib/status/pollingClient.js:91:19)
at async MyDomainResolver.resolve (/usr/local/lib/node_modules/sfdx-cli/node_modules/@salesforce/core/lib/status/myDomainResolver.js:103:45)
at async Connection.isResolvable (/usr/local/lib/node_modules/sfdx-cli/node_modules/@salesforce/core/lib/org/connection.js:239:13)
at async Connection.retrieveMaxApiVersion (/usr/local/lib/node_modules/sfdx-cli/node_modules/@salesforce/core/lib/org/connection.js:190:9)
at async Connection.useLatestApiVersion (/usr/local/lib/node_modules/sfdx-cli/node_modules/@salesforce/core/lib/org/connection.js:214:32)
at async Function.create (/usr/local/lib/node_modules/sfdx-cli/node_modules/@salesforce/core/lib/org/connection.js:98:17)
at async Org.init (/usr/local/lib/node_modules/sfdx-cli/node_modules/@salesforce/core/lib/org/org.js:766:31)
at async Function.create (/usr/local/lib/node_modules/sfdx-cli/node_modules/@salesforce/kit/lib/creatable.js:57:9)
at async scratchOrgCreate (/usr/local/lib/node_modules/sfdx-cli/node_modules/@salesforce/core/lib/org/scratchOrgCreate.js:174:24)
at async Create.createScratchOrg (/usr/local/lib/node_modules/sfdx-cli/node_modules/@salesforce/plugin-org/lib/commands/force/org/create.js:187:68)

@bdovh - this happens when DNS isn't performing normally, which is outside the control of the CLI.  However you can manipulate how the CLI handles DNS resolution by setting a few environment variables:
SFDX_DNS_TIMEOUT: Specifies the number of seconds that the force:org:* commands wait for a response when checking whether an org is connected. If the commands don’t receive a response in that time, they time out. Default value is 3.  You could increase it to (e.g.) 30.
SFDX_DISABLE_DNS_CHECK: Disable the DNS resolution entirely by setting to true.  There may be issues encountered with later commands or it could be fine.

Well, when I install SFDX CLI on the CI environment, I have command to set SFDX_DISABLE_DNS_CHECK to true
npm install sfdx-cli --global
export SFDX_DISABLE_DNS_CHECK=true
And also I have it second time on push

name: "Push source to scratch org"
id: "deploy0"
shell: bash
env:
SFDX_DISABLE_DNS_CHECK: true
run: |
cd src/unpackaged
echo "Changed dir"
DEBUG=sf:MyDomainResolver
echo "Set debug to $DEBUG"
SFDX_DISABLE_DNS_CHECK=true
echo "Set SFDX_DISABLE_DNS_CHECK to $SFDX_DISABLE_DNS_CHECK"
sfdx force:source:deploy -p force-app --json > ../../deploy.txt || true
echo "File created"

Should I try to copy it again just before the executing create org command? Isn't it enough to include that variable just once?

Could you please tell me if this error is also related to DNS resolution problem?
Org creation failed with error ScratchOrgInfoTimeout ScratchOrgInfoTimeout: The client has timed out. at PollingClient.subscribe (/usr/local/lib/node_modules/sfdx-cli/node_modules/@salesforce/core/lib/status/pollingClient.js:91:19) at async pollForScratchOrgInfo (/usr/local/lib/node_modules/sfdx-cli/node_modules/@salesforce/core/lib/org/scratchOrgInfoApi.js:303:34) at async scratchOrgCreate (/usr/local/lib/node_modules/sfdx-cli/node_modules/@salesforce/core/lib/org/scratchOrgCreate.js:165:17) at async Create.createScratchOrg (/usr/local/lib/node_modules/sfdx-cli/node_modules/@salesforce/plugin-org/lib/commands/force/org/create.js:187:68) at async Create._run (/usr/local/lib/node_modules/sfdx-cli/node_modules/@salesforce/command/lib/sfdxCommand.js:102:40) at async Config.runCommand (/usr/local/lib/node_modules/sfdx-cli/node_modules/@oclif/core/lib/config/config.js:272:25) at async run (/usr/local/lib/node_modules/sfdx-cli/node_modules/@oclif/core/lib/main.js:74:5)

@bdovh that's more related to the --wait parameter on the command timing out. It could be timing out for a DNS issue, but a lot of other things could by causing your SO to take a while to create. Try increasing your --wait parameter

@bdovh that's more related to the --wait parameter on the command timing out. It could be timing out for a DNS issue, but a lot of other things could by causing your SO to take a while to create. Try increasing your --wait parameter

what is default value and what is the maximum value?

sfdx force:org:create --help => wait's default is 6 minutes, maximum... not sure there is one

where do you see the default value on executing this command?
Since when I execute it, I see
sfdx help force:org:create
create a scratch or sandbox org

USAGE
  $ sfdx force org create [name=value...] [-t scratch|sandbox] [-f <filepath>] [-n] [-c] [-i <string>] [-s] [-a <string>] [-w <minutes>] [-d <integer>] [-v <string>] [-u
    <string>] [--apiversion <string>] [--json] [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]

FLAGS
  -a, --setalias=<value>                                                            alias for the created org
  -c, --noancestors                                                                 do not include second-generation package ancestors in the scratch org
  -d, --durationdays=<value>                                                        [default: 7] duration of the scratch org (in days) (default:7, min:1, max:30)
  -f, --definitionfile=<value>                                                      path to an org definition file
  -i, --clientid=<value>                                                            connected app consumer key; not supported for sandbox org creation
  -n, --nonamespace                                                                 create the scratch org with no namespace
  -s, --setdefaultusername                                                          set the created org as the default username
  -t, --type=(scratch|sandbox)                                                      [default: scratch] type of org to create
  -u, --targetusername=<value>                                                      username or alias for the target org; overrides default target org
  -v, --targetdevhubusername=<value>                                                username or alias for the dev hub org; overrides default dev hub org
  -w, --wait=<value>                                                                [default: [object Object]] the streaming client socket timeout (in minutes)
  --apiversion=<value>                                                              override the api version used for api requests made by this command
  --json                                                                            format output as json
  --loglevel=(trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL)  [default: warn] logging level for this command invocation

DESCRIPTION
  create a scratch or sandbox org
  Creates a scratch org or a sandbox org using the values specified in a configuration file or key=value pairs that you specify on the command line. Values specified on the command
  line override values in the configuration file. Specify a configuration file or provide key=value pairs while creating a scratch org or a sandbox. When creating scratch orgs,
  —targetdevhubusername (-v) must be a Dev Hub org. When creating sandboxes, the --targetusername (-u) must be a production org with sandbox licenses. The —type (-t) is required if
  creating a sandbox.

ALIASES
  $ sfdx force org beta create

EXAMPLES
  $ sfdx force:org:create -f config/enterprise-scratch-def.json -a MyScratchOrg

  $ sfdx force:org:create edition=Developer -a MyScratchOrg -s -v devHub

  $ sfdx force:org:create -f config/enterprise-scratch-def.json -a ScratchOrgWithOverrides<EMAIL_ADDRESS>
  $ sfdx force:org:create -t sandbox -f config/dev-sandbox-def.json -a MyDevSandbox -u prodOrg

I can't find anything in the documentation but I could instead to find out this value experimentally.
If we try to experiment we will find out the following results:
sfdx force:org:create -s -d 30 -a o$(( RANDOM % 1000)) -f config/manual.json -w<PHONE_NUMBER>999999999999
(node:45988) TimeoutOverflowWarning: 6.0000000000000006e+26 does not fit into a 32-bit signed integer.
Timeout duration was set to 1.
(Use `node --trace-warnings ...` to show where the warning was created)
ERROR running force:org:create:  The client has timed out.

Clearly -w parameter should be less than maximum value of 32-bit signed integer, which is (2^31) - 1 or<PHONE_NUMBER>.
Further, let's try to pass the value of max signed int into -w parameter
sfdx force:org:create -s -d 30 -a o$(( RANDOM % 1000)) -f config/manual.json -w<PHONE_NUMBER>
(node:46082) TimeoutOverflowWarning:<PHONE_NUMBER>20000 does not fit into a 32-bit signed integer.
Timeout duration was set to 1.
(Use `node --trace-warnings ...` to show where the warning was created)

Ok, looks like the minutes parameter is multiplied by 60000 to be converted into number of milliseconds and that value should be less than max signed int. So let's just divide<PHONE_NUMBER> by 60000 and take floor of the result.
sfdx force:org:create -s -d 30 -a o$(( RANDOM % 1000)) -f config/manual.json -w 35791
Successfully created scratch org: 00D8N0000005l0YUAQ, username<EMAIL_ADDRESS>
So, the maximum value is 35791

If we try 35792 then we receive an error
sfdx force:org:create -s -d 30 -a o$(( RANDOM % 1000)) -f config/manual.json -w 35792
(node:46439) TimeoutOverflowWarning:<PHONE_NUMBER> does not fit into a 32-bit signed integer.
Timeout duration was set to 1.
(Use `node --trace-warnings ...` to show where the warning was created)
ERROR running force:org:create:  The client has timed out.


Clarifies grammar to indicate that named types cannot be inlined within other named types

Issue #, if available:
N/A
Description of changes:
The ISL grammar indicates that named, inlined types might be allowed, like this:
type::{
  name: foo,
  type: list,
  element: type::{
    name: bar,
    type: string,
  }
}

This contradicts the Type Definition section of the spec, which says:

an unnamed type may be inlined anywhere a <TYPE_REFERENCE> is expected
[emphasis added]

This change updates the grammar to clearly differentiate between named and unnamed types so that it is clear that ISL does not support naming any inlined types. This does not preclude us from allowing named, inline types in the future if the need should arise.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

This looks great--do we need an issue in the implementations to make sure we're not inadvertently supporting this misfeature?

I don't think so. We're not supporting it right now, but it also doesn't throw any exceptions if you try to do it. Right now it just silently ignores the names of any inline types.
I think it is fine to leave the implementation the way it is because

Users who try to call getType(name: String) to retrieve an inline type with a name field will already get null (ie. not found).
Throwing an InvalidSchemaException for the name would be a breaking change. The fix is trivial (remove/comment out the name)—unless you are depending on schemas vended by someone else, in which case managing change across teams/organizations could be a pain point.
The Ion Schema spec does allow for open content in ISL. The name field is technically an example of open content.

I just wanted to address the inconsistency in the spec because I wasn't sure at first whether or not the current implementation was supposed to support named, inline types.


Could you please show off AgeDB result?

@PistonY
This AgeDB result is ok. But this model was trained about one year ago. If I can find the training log, I will show the training results of AgeDB.

Great job, thx.


added new overloaded constructor options to match TypedArray pattern

added additional overloaded arguments to accomodate byteOffset and length at init to match the TypedArray constructor pattern
new TypedArray(buffer)
new TypedArray(buffer, byteOffset)
new TypedArray(buffer, byteOffset, length)

also added a few test cases to cover the new constructor patterns, with various lengths of arrays, as well as testing byteOffset to ensure it offsets by 8 bits per byte
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/TypedArray#constructor
closes https://github.com/swiing/Bit-TypedArray/issues/1

I am going to close this PR for the following reasons:
1- as said here I need a compelling argument why ByteOffset would make sense for bit arrays.
2- even if we would like to allow byteOffset/length, the code does not comply to the standard. E.g. new BitArray("011010", 0, 9).length === 9 should be false, not true.  In order to convince you, check new Uint32Array([0,1,1,0,1,0], 0, 9).length (the value of which is 6, not 9). This is because the proposed code applies byteOffset/length to iterables, not to ArrayBuffers.
Anyway, thanks for sharing this. It raises interesting considerations.