The result of the openssl pkcs8 command execution was not as expected

openssl version: OpenSSL 3.3.2 3 Sep 2024 (Library: OpenSSL 3.3.2 3 Sep 2024)
it is system provided
os version: Linux 6.11.2-amd64 #1 SMP PREEMPT_DYNAMIC Kali 6.11.2-1kali1 (2024-10-15) x86_64 GNU/Linux
command:
openssl pkcs8 -in ./pk8_priv.key -traditional -nocrypt -out ./pk1_priv.key

This command is executed without an error message and the file is empty.
pk8_priv.key
-----BEGIN PRIVATE KEY-----
MIGHAgEAMBMGByqGSM49AgEGCCqBHM9VAYItBG0wawIBAQQg3UjXaRXCpATHVcJv
K/vDrx1zmkq9G/umdXJLn4UobPahRANCAARjsDIu8EAXDHspsCvacLrZV4CVQC8s
PEeNcsSU78OIxNonodbfobHNZPasWDLpwAWWq4EY0GUamlCf3hmcOAk5
-----END PRIVATE KEY-----

The short reason is that this code neglects to check the return code from the function call and therefore does not notice that it has failed:
https://github.com/openssl/openssl/blob/ea5817854cf67b89c874101f209f06ae016fd333/apps/pkcs8.c#L367-L369
It should detect the failure and then print a suitable error message. If we were to make that change then we would see an error message here about "unsupported public key type".
The underlying reason for that is that this is an SM2 key and during decoding it does not associate the key with an old style "ameth", which subsequently results in this code failing:
https://github.com/openssl/openssl/blob/ea5817854cf67b89c874101f209f06ae016fd333/crypto/pem/pem_pkey.c#L356-L363
This is all associated with the weird relationship between SM2 keys and EC keys. If I hard code pem_str in the above to EC PRIVATE KEY then the subsequent PEM_ASN1_write_bio call seems to suceed and we get (apparently) sane output.
Potentially we might be missing some SM2 special-casing here?

The short reason is that this code neglects to check the return code from the function call and therefore does not notice that it has failed:
https://github.com/openssl/openssl/blob/ea5817854cf67b89c874101f209f06ae016fd333/apps/pkcs8.c#L367-L369
It should detect the failure and then print a suitable error message. If we were to make that change then we would see an error message here about "unsupported public key type".
The underlying reason for that is that this is an SM2 key and during decoding it does not associate the key with an old style "ameth", which subsequently results in this code failing:
https://github.com/openssl/openssl/blob/ea5817854cf67b89c874101f209f06ae016fd333/crypto/pem/pem_pkey.c#L356-L363
This is all associated with the weird relationship between SM2 keys and EC keys. If I hard code pem_str in the above to EC PRIVATE KEY then the subsequent PEM_ASN1_write_bio call seems to suceed and we get (apparently) sane output.
Potentially we might be missing some SM2 special-casing here?

I am very grateful for your reply.
As you say, this is indeed an SM2 prinate key. i can provide the steps for this private key to be created, although i'm not sure if this will help you.
openssl ecparam -genkey -name SM2 -out ./priv.key
openssl pkcs8 -in ./priv.key -topk8 -nocrypt -out ./pk8_priv.key
openssl pkcs8 -in ./pk8_priv.key -traditional -nocrypt -out ./pk1_priv.key


Talk request: I18n / I10n of javascript applications

I would be very interested in a talk about I18n / I10n of javascript applications.

This varies a lot between frameworks. Can you narrow it down?

I edited the request. :)

@the-architect if you need "translation as a service", check out these tools:

https://react.i18next.com
https://localizejs.com


Stremio returns 415 Media Unsupported code

Hello,
Im using your image to host a personal stremio server over http. However im getting a 415 Media Unsupported error code when trying to stream anything. Do you have any idea what could be wrong?
Thanks

Hello,
are you using the latest commit (#18b9295)?
What browser are you using?
Are you using a local IP/hostname to access the server/client?


Fix NPE in JdbcTokenStore

If an old Authentication failed to deserialize (e.g., after upgraded Spring Security core libs) during the creation of a token, a NPE would be thrown as readAuthentication return null in that case. This should fix that.

Thanks for the PR @MikeN123. Can you please provide a test that demonstrates the fix resolves the issue.

That's quite difficult, as in our case it was triggered by an outdated serialized version of a class, which caused:
java.lang.IllegalArgumentException: java.io.InvalidClassException: org.springframework.security.core.authority.SimpleGrantedAuthority; local class incompatible: stream classdesc serialVersionUID = 530, local class serialVersionUID = 540

Of course I can fake some kind of a deserialization problem, but it won't really be the real thing...
Suggestions on how to approach this?

I have added a test that writes an invalid serialized version of the authentication object to the database and then tries to read it back. This test fails with the old code and succeeds with the new code. It does log a WARN though, but that is unavoidable as that is always logged if the deserialization fails.

I've replied to your comment (commenting here so the bot can do his job and update the labels).

Thanks for this fix @MikeN123 ! This is now in master and 2.4.x.


Use a io.Seeker for body data

An attempt to fix #1 we get after a while where uploads start failing after a while

Manually deployed and tested, continues to work it seems!

Manually deployed and tested, continues to work it seems!


[Bug]: ButtonGroup type mutiple data-state does't get updated

Environment
Developement/Production OS: Macbook pro m1
Node version: 16.0.0
Package manager<EMAIL_ADDRESS>Radix Vue version: 1.5.2
Vue version: latest
CSS framework: latest
Browser: Chrome 90.0.4430.212

Link to minimal reproduction
https://stackblitz.com/edit/uhbmps?file=src%2FApp.vue
Steps to reproduce

[ ] Open stackblitz
[ ] toggle the button

Describe the bug
The data-state toggle is not working in my project and in the stackblitz which is provided on the website https://www.radix-vue.com/components/toggle-group.html#root.
the state binded with v-model isn't updating either (like the single), but the @update:modelValue="(v) => console.log(v)" is providing the state.
Expected behavior
I expect the data-state toggle in sync with data-active as in the example on the website. I downgraded to version 1.4.9 and it works like expected.

Context & Screenshots (if applicable)

Related
https://github.com/radix-vue/radix-vue/issues/754

Duplicate of https://github.com/radix-vue/radix-vue/issues/754. Will publish the fixed version soon

Hallo, I see you have fixed it in version 1.5.3 thank you!!


Update readme

Updating readme with puppet module

I've updated the CI environment if you'd like to rebase master and try again.

Ok I don't know why there ended up with two pull requests. I'm going to just close these and open up an updated single one that combines the commits and removes glide.


No type generation for library

I have the following library/contract file:
// SPDX-License-Identifier: MIT
pragma solidity >=0.8.0 <0.9.0;

import "./Kiosk.sol";
import "./SnackbarToken.sol";
import<EMAIL_ADDRESS>// used in Registry
import<EMAIL_ADDRESS>// used in Registry
import<EMAIL_ADDRESS>// used in Registry

library KioskDeployer {
    function deployKiosk(address payable treasurer, string memory name, SnackbarToken sck) public returns (address){
        Kiosk kiosk = new Kiosk(treasurer, name, sck);
        return address(kiosk);
    }
}

contract Registry {<contract that uses KioskDeployer>}

My package.json is as follows:
{
  "name": "backend",
  "version": "1.0.0",
  "license": "MIT",
  "scripts": {
    "compile": "truffle compile",
    "generate-types": "yarn compile && typechain --target=truffle-v5 './build/contracts/*.json' --show-stack-traces",
    "generate-types-client": "yarn compile && typechain --target=web3-v1 './build/contracts/*.json'",
    "postinstall": "yarn generate-types && yarn generate-types-client",
    "migrate:clean": "rm -rf ./build/migrations/*",
    "migrate:compile": "yarn migrate:clean && npx tsc -p ./tsconfig.migrate.json --outDir ./build/migrations",
    "migrate": "yarn migrate:compile && truffle migrate",
    "test:clean": "rm -rf ./build/test/*",
    "test:compile": "yarn test:clean && npx tsc -p ./tsconfig.test.json --outDir ./build/test",
    "test:registry": "yarn test:compile && truffle test \"./build/test/registry.js\"",
    "test:kiosk": "yarn test:compile && truffle test \"./build/test/kiosk.js\"",
    "test": "yarn test:compile && truffle test",
    "sizes": "truffle run contract-size",
    "ganache-cli": "ganache-cli -p 7545 --gasLimit=0x1fffffffffffff --allowUnlimitedContractSize -e<PHONE_NUMBER> > /dev/null &",
    "coverage": "yarn test:compile && truffle run coverage",
    "typecheck": "tsc --noEmit"
  },
  "devDependencies": {
    "@openzeppelin/contracts": "^4.6.0",
    "@openzeppelin/test-helpers": "^0.5.15",
    "@typechain/truffle-v5": "^8.0.0",
    "@typechain/web3-v1": "^6.0.0",
<EMAIL_ADDRESS>"^5.1.0",
    "@types/chai": "^4.3.0",
    "@types/chai-as-promised": "^7.1.5",
    "@types/deep-equal-in-any-order": "^1.0.1",
    "@types/mocha": "^9.0.0",
    "@types/sinon-chai": "^3.2.8",
    "@types/web3": "^1.2.2",
    "chai-as-promised": "^7.1.1",
    "chai-bn": "^0.3.1",
    "deep-equal-in-any-order": "^1.1.19",
    "ethereum-waffle": "^3.4.4",
    "ganache": "^7.2.0",
    "solidity-coverage": "0.8.0-beta.1",
    "truffle": "^5.5.16",
    "truffle-contract-size": "^2.0.1",
    "truffle-typings": "^1.0.8",
    "typechain": "^8.0.0",
    "typescript": "^4.5.4"
  },
  "dependencies": {
    "truffle-contract-size": "^2.0.1"
  }
}

The whole project (and therefore the package.json) is a modified version of this repo. My issue is that after calling yarn generate-types everything gets types - except for the library KioskDeployer. Putting the library into a separate file does not change anything. Here you can see all generated types:

As you can see KioskDeployer was successfully compiled.

I can resupply you with relevant information if you want.

A solidity external library is a contract meant to be delegate called by another contract, and cannot interact with EOA. Hence, the ABI that the compiler generates does not include these methods, thus no types are generated for it.

@zemse is probably right. Is there abi inside of KioskDeployer?

@0xCourtney I am using solc in version 0.8.10.
@krzkaczor there is indeed no abi (abi: []) but I am wondering if there should be some "placeholder type" in case one wants to import it for linking since importing the untyped KioskDeployer leads to an ugly error:
$ yarn test:kiosk
[...]
test/kiosk.ts:16:41 - error TS2769: No overload matches this call.
  The last overload gave the following error.
    Argument of type '"KioskDeployer"' is not assignable to parameter of type '"SnackbarToken"'.

16 const KioskDeployer = artifacts.require("KioskDeployer");
                                           ~~~~~~~~~~~~~~~

  types/truffle-contracts/index.d.ts:34:7
    34       require(name: "SnackbarToken"): SnackbarTokenContract;
             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    The last overload is declared here.

Found 1 error in test/kiosk.ts:16

test/kiosk.ts:16: const KioskDeployer = artifacts.require("KioskDeployer");

I don't think so as libraries can't be instantiated 🤔
Anyway, this is not a TypeChain issue but rather something that you want to discuss on solidity-related chats.

It would be preferrable if there was a flag --skipEmptyAbis=false


Teach Cache to be transparent in get_lazy.

This allows Cache<std::string, X> and Cache<Triplet, X> to do lookups using a StringView without allocations.
Extracted for a more focused discussion from https://github.com/microsoft/vcpkg-tool/pull/404.

I am still not a huge fan of how much machinery this needs compared to a more directly specialized StringCache, however I don't think the harm outweighs the benefits.

I did try making a StringCache instead when I made this; however there are lots of places that have like Cache<Triplet, ...> that also benefit from transparency, so I went back to this.

If there's another use case than std::string then the machinery becomes worth it to me. Thanks!


[discussion] Can we make RxJS stack traces shallower?

Performance work is 50% optimizing code and 50% unwinding RxJS stack traces
~ me, half-jokingly

I've been working a lot lately with performance inspector for my project, and this is what I've been dealing with:

To get to my app's functions, I have to expand so many RxJS functions, I literally run out of space on my 24'' display. That's how unreasonably many of them are there.
Of course this is a different case of the same problem as when dealing with errors that are somewhere deep in RxJS stack trace - #2663. Both make the developer experience of working with RxJS really frustrating.
Now, my question is — why are RxJS stack traces so deep? On my count, the screenshot has just 4 rx operations - switchMap, switchMap, distinctUntilChanged, ReplaySubject.
Is this level of depth truly necessary for RxJS's functionality? performance? Do we really need to go through subscriber → subscriber → next → _next → next → __tryOrUnsub → subscriber on every operator?
Or is it just an unfortunate side effect of whatever convention/structure/something that was used, and could be easily, at least partly, remedied by some basic refactoring and folding multiple functions into one?
Or if this is because of performance, could we make the stack traces shallower in debug?

@benlesh has been working on re-writing the underlying implementation and his mutable-subscriber approach should address this. Have a look at this branch, if you are curious: https://github.com/ReactiveX/rxjs/tree/experiment-mutable-subscribers
As to why things are the way they are, my understanding is that it's that way for performance reasons. Reasons that are - AFAICT - historical. Closures used to be much more expensive and the current, class-based implementation had perf advantages. This is no longer the case.

Hi @benlesh -- is this problem going to improve with version 7?


Jenkins Library update for Gradle Check Publish Optimization

Description
Coming from https://github.com/opensearch-project/OpenSearch/issues/11217#issuecomment-2118322724, this PR will ensure we have the PR number identified by commitID even for post_merge_action. This data will be used in gradle metrics dashboard OpenSearch Gradle Check Metrics.
With this change we can get the associated PR for failed tests on post_merge_action.
The required gradle check change PR https://github.com/opensearch-project/OpenSearch/pull/13786.
The required jenkinsfile change PR https://github.com/opensearch-project/opensearch-build/pull/4719.
Issues Resolved
Part of: https://github.com/opensearch-project/OpenSearch/issues/3713
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

This is a better and more complete update to gradle check lib.
Thanks.


Update IconPicker.php

Fixes default relationship implementation

Thank you for the PR, Martin! Since https://github.com/lukas-frey/filament-icon-picker/pull/18 was created before yours, I merged theirs. :)


Update 'Documentation' : Update DeveloperGuide.md

Update StorageClassDiagram.png
Add emailcontact implementation details

Codecov Report

Merging #133 (337c101) into master (63dfc96) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #133   +/-   ##
=========================================
  Coverage     54.00%   54.00%
  Complexity      669      669
=========================================
  Files           146      146
  Lines          2807     2807
  Branches        276      276
=========================================
  Hits           1516     1516
  Misses         1191     1191
  Partials        100      100

Continue to review full report at Codecov.

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


Is this normal? Autodraw looks like shid

we need blues and other colors

Now drawing like this:

It took over 2 minutes and 15k commands to draw that image. The best way to reduce that is by selecting a simpler image.


JS: add taint step through object/array spread operators

Evaluation underway.
Intentionally does not deal with spread operators in argument lists.
Fixes https://jira.semmle.com/browse/ODASA-7670

Evaluation looks good.


Internal Server Error with underscore in PluginName

When setting up a Craft 3 Module and with a Module Name using an underscore (example used: "k4_Ajax"), there is a Server Error:
Internal Server Error
RecursiveDirectoryIterator::__construct(/home/forge/pluginfactory.io/craft/storage/runtime/temp/pluginfactory/k4ajaxmodule): failed to open dir: No such file or directory
Might be related to issue #64

This is confirmed a bug


Automated Package Upgrade

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[Broker] Fix and improve topic ownership assignment

Motivation
This PR depends on #13066 .
When a lookup is made to a topic that isn't currently loaded, the decision will be made in a distributed fashion on the follower brokers since the information about the leader broker is missing (because LeaderElectionService.getCurrentLeader() always returned Optional.empty()). This leads to races when assigning the topic ownership to a broker, since the decision isn't made centrally on the leader broker.
This PR adds a test to verify the behavior and also uses a cached way to get available brokers.
Modifications

builds upon changes from #13066
add failing test case MultiBrokerLeaderElectionTest.shouldProvideConsistentAnswerToTopicLookup
adds more logging to topic ownership assignment decision made in NamespaceService.searchForCandidateBroker
optimizes performance of the topic ownership assignment by using LoadManager.getAvailableBrokers instead of reading the list every time from Zookeeper

I converted this PR to draft since there are more problems.
I started a separate branch targeting 2.8.x , that is https://github.com/lhotari/pulsar/commits/lh-fix-topic-ownership-assignment-branch-2.8 . It currently contains a test case that reproduces error 404 and error 500 issues.
The problems are different when using a real Zookeeper server. In the port of this fix for branch-2.8, I  made a change to use TestZKServer from pulsar-metadata , https://github.com/lhotari/pulsar/commit/d44bf6faaca922182b3178b4de17397bdfe7d4ce .
That produces issues that seem to match the analysis made by @zbentley in https://github.com/apache/pulsar/issues/12552#issuecomment-955748696 .

My 2.8 test is invalid, I'll fix it and verify.

I fixed the test in https://github.com/lhotari/pulsar/commits/lh-fix-topic-ownership-assignment-branch-2.8 . I can now consistently reproduce the issue. It results in error 500 :
10:22:44.069 [metadata-store-150-1] INFO  org.apache.pulsar.common.naming.NamespaceBundleFactory - Policy updated for namespace public/default, refreshing the bundle cache.
10:22:44.069 [metadata-store-220-1] INFO  org.apache.pulsar.common.naming.NamespaceBundleFactory - Policy updated for namespace public/default, refreshing the bundle cache.
10:22:44.069 [metadata-store-80-1] INFO  org.apache.pulsar.common.naming.NamespaceBundleFactory - Policy updated for namespace public/default, refreshing the bundle cache.
10:22:44.069 [metadata-store-45-1] INFO  org.apache.pulsar.common.naming.NamespaceBundleFactory - Policy updated for namespace public/default, refreshing the bundle cache.
10:22:44.069 [metadata-store-325-1] INFO  org.apache.pulsar.common.naming.NamespaceBundleFactory - Policy updated for namespace public/default, refreshing the bundle cache.
10:22:44.069 [metadata-store-185-1] INFO  org.apache.pulsar.common.naming.NamespaceBundleFactory - Policy updated for namespace public/default, refreshing the bundle cache.
10:22:44.069 [metadata-store-255-1] INFO  org.apache.pulsar.common.naming.NamespaceBundleFactory - Policy updated for namespace public/default, refreshing the bundle cache.
10:22:44.069 [metadata-store-290-1] INFO  org.apache.pulsar.common.naming.NamespaceBundleFactory - Policy updated for namespace public/default, refreshing the bundle cache.
10:22:44.069 [metadata-store-115-1] INFO  org.apache.pulsar.common.naming.NamespaceBundleFactory - Policy updated for namespace public/default, refreshing the bundle cache.
10:22:44.070 [metadata-store-255-1] WARN  org.apache.pulsar.broker.lookup.TopicLookupBase - Failed to lookup broker for topic persistent://public/default/lookuptest0e133752-6e62-415f-994b-ef5d9ad57730-0: org.apache.pulsar.metadata.api.MetadataStoreException$BadVersionException: org.apache.zookeeper.KeeperException$BadVersionException: KeeperErrorCode = BadVersion for /admin/local-policies/public/default
java.util.concurrent.CompletionException: org.apache.pulsar.metadata.api.MetadataStoreException$BadVersionException: org.apache.zookeeper.KeeperException$BadVersionException: KeeperErrorCode = BadVersion for /admin/local-policies/public/default
	at java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:331) ~[?:?]
	at java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:346) ~[?:?]
	at java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:632) ~[?:?]
	at java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506) ~[?:?]
	at java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2088) ~[?:?]
	at org.apache.pulsar.metadata.impl.ZKMetadataStore.lambda$storePut$15(ZKMetadataStore.java:226) ~[pulsar-metadata-2.8.2.jar:2.8.2]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]
	at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) [netty-common-4.1.68.Final.jar:4.1.68.Final]
	at java.lang.Thread.run(Thread.java:829) [?:?]
Caused by: org.apache.pulsar.metadata.api.MetadataStoreException$BadVersionException: org.apache.zookeeper.KeeperException$BadVersionException: KeeperErrorCode = BadVersion for /admin/local-policies/public/default
	at org.apache.pulsar.metadata.impl.ZKMetadataStore.getException(ZKMetadataStore.java:308) ~[pulsar-metadata-2.8.2.jar:2.8.2]
	... 5 more
Caused by: org.apache.zookeeper.KeeperException$BadVersionException: KeeperErrorCode = BadVersion for /admin/local-policies/public/default
	at org.apache.zookeeper.KeeperException.create(KeeperException.java:122) ~[zookeeper-3.6.3.jar:3.6.3]
	at org.apache.zookeeper.KeeperException.create(KeeperException.java:54) ~[zookeeper-3.6.3.jar:3.6.3]
	at org.apache.pulsar.metadata.impl.ZKMetadataStore.getException(ZKMetadataStore.java:304) ~[pulsar-metadata-2.8.2.jar:2.8.2]
	... 5 more
10:22:44.070 [metadata-store-185-1] WARN  org.apache.pulsar.broker.lookup.TopicLookupBase - Failed to lookup broker for topic persistent://public/default/lookuptest0e133752-6e62-415f-994b-ef5d9ad57730-0: org.apache.pulsar.metadata.api.MetadataStoreException$BadVersionException: org.apache.zookeeper.KeeperException$BadVersionException: KeeperErrorCode = BadVersion for /admin/local-policies/public/default
java.util.concurrent.CompletionException: org.apache.pulsar.metadata.api.MetadataStoreException$BadVersionException: org.apache.zookeeper.KeeperException$BadVersionException: KeeperErrorCode = BadVersion for /admin/local-policies/public/default
	at java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:331) ~[?:?]
	at java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:346) ~[?:?]
	at java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:632) ~[?:?]
	at java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506) ~[?:?]
	at java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2088) ~[?:?]
	at org.apache.pulsar.metadata.impl.ZKMetadataStore.lambda$storePut$15(ZKMetadataStore.java:226) ~[pulsar-metadata-2.8.2.jar:2.8.2]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]
	at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) [netty-common-4.1.68.Final.jar:4.1.68.Final]
	at java.lang.Thread.run(Thread.java:829) [?:?]
Caused by: org.apache.pulsar.metadata.api.MetadataStoreException$BadVersionException: org.apache.zookeeper.KeeperException$BadVersionException: KeeperErrorCode = BadVersion for /admin/local-policies/public/default
	at org.apache.pulsar.metadata.impl.ZKMetadataStore.getException(ZKMetadataStore.java:308) ~[pulsar-metadata-2.8.2.jar:2.8.2]
	... 5 more
Caused by: org.apache.zookeeper.KeeperException$BadVersionException: KeeperErrorCode = BadVersion for /admin/local-policies/public/default
	at org.apache.zookeeper.KeeperException.create(KeeperException.java:122) ~[zookeeper-3.6.3.jar:3.6.3]
	at org.apache.zookeeper.KeeperException.create(KeeperException.java:54) ~[zookeeper-3.6.3.jar:3.6.3]
	at org.apache.pulsar.metadata.impl.ZKMetadataStore.getException(ZKMetadataStore.java:304) ~[pulsar-metadata-2.8.2.jar:2.8.2]
	... 5 more

Problem happens here: https://github.com/apache/pulsar/blob/0b9d51bb49a9fb7a94ba5d38b52dc7ea287f7731/pulsar-broker/src/main/java/org/apache/pulsar/common/naming/NamespaceBundleFactory.java#L104-L110

Exception gets swallowed here: https://github.com/apache/pulsar/blob/e1fbccdd7cf0a6f6ed29f6fadeb498524b9635b4/pulsar-broker/src/main/java/org/apache/pulsar/broker/namespace/NamespaceService.java#L205-L208

I have a fix for branch-2.8 in https://github.com/lhotari/pulsar/commit/1a350804 . I'll make similar changes to this PR since they aren't 2.8 specific.

@codelipenghui @eolivelli Please review the recent changes.

PR to backport this fix to branch-2.8 is #13117


Missions engine

This feature contains more than one functions. We are:

createMission to create and register mission
closeMission to close the registered mission
isMissionClosed to check if the mission is closed
missionState to the check the mission state
missionGenerator to generate random mission configured in description.ext
spawnMissionHelicopterCrashInTown to create and register a sample mission. This mission spawn units and goal in a random town of the map.

A mission maker can add this own mission inside the description.ext and if this is a beginner, it can be use exclusively the editor inspite of little bit of configuration since description.ext.


Issues verifying backups when using the backup-container

We've started using the BCDevOps/backup-container to backup an instance of traction and we're running into errors with the automated backup verification process.
The errors are due to that fact that the traction database and agent instances use the default postgres user account for all access to the databases/wallets.  This causes issues for the backup-container which assumes there is a different user account created for "user" level access to the database.  When the backup-container goes to create the local copy of the database for verification using the supplied credentials it errors out because the postgres user already exists.  This stops the local postgres instance from starting properly and therefore causes the backup verification process to fail.
While it would be possible to add support for such a use case to the backup-container, it would be better if we could update the traction deployments to use separate accounts for database creation/access and reserve the postgres user account for admin use (database creation/administration).  This would align to best practice and conform to what the backup-container is expecting.

FYI @i5okie

This should be resolved with the latest version of the charts. We should re-assess after the new deployments have been stood-up - adding blocker issues.

Closing as new deployments will use a non-privileged user to manage the database schemas after the helm upgrades, and old deployments will all be decommissioned. Can reopen, if required, in the future.


fix: typo in readme

Extremely valuable contribution by a proud open source contributor.

Bump for critical merge


Creating A New Script That Extends class_name'd script should use the name, not path.

Godot version:

3.1
When you create a  new script, the dialog box asks you if you want to extend another script. If the script you choose is your own script it puts extends "res://scripts/my-class.gd".
It would be nice if the script has a class_name MyClass declaration, the extends clause at the top of the new script should use that name. This eliminates any dependencies on paths, and just looks cleaner.

In order to achieve this functionality you can simply put the name of the extended class in the 'extends' field. Now that I know that, this feature no longer seems like a worthwhile proposition. Closing.


just-nix plans

@casey Hi! Long time no see!
@kamadorueda is prototyping a couple of interesting things at https://github.com/on-nix/ and we have been discussing the possibility of extending just to exhibit a nix interface
into specially prepared **/task.nix contract files.
The general (incipient) idea would be that we can point in Justfile to an attribute of a nix evaluation that would then provide an attribute set of just-runnable tasks back to just according to  a well-defined interface.
If an entire repo automation shall be driven by such task runner (just-nix), we also are considering a fuzzy-search frontend to quickly search the task list.
makes has prototyped such an UX in combination with a strict naming scheme that identifies all tasks mandatorily by a relpath to the repo root, such as for example m . /patroni/enterPsqlOnLeader, a task that is defined (& fully auditable) at makes/patroni/enterPsqlOnLeader/*.
I wanted to open this issue to let you know and make this a shared brainstorming of sort so that we make sure we have your feedback before even starting.
Cheers!

Visual of current makes tui:

That's very cool! I'm not sure I understand how just and nix would integrate. Would just expose recipes to nix, or would things from nix be exposed to just?

In my current ideation, jobs from nix would be exposed to just.

With today's release of https://github.com/divnix/std by a good friend of mine, it seems to be about the right time to prototype a just "Organelle".
just could be instructed to consume all runnables below outputs.just.${system}.* of the flake.nix's outputs, in addition to what's in Justfile.

In my current ideation, jobs from nix would be exposed to just.

What is the advantage of running these jobs from just, instead of running them directly?

What is the advantage of running these jobs from just, instead of running them directly?

Directly can mean in reality a couple of things, most prominently, via the nix CLI interface, but also other CLI frontends are emerging for different use cases.
just is a well established task runner and has a pretty neat and familiar UX for a lot of devs.
I, therefore, see workflows play out where devs can prototype scripts in plain Justfiles which then can gradually be made reproducible via nix.
On the other hand, devops teams can deliver tooling right into the just frontends across various repos from a central location.

Maybe you'd be open to ideas to invoke just as a role to further filter tasks?
Maybe it's not the most useful idea, but I had thought about something like:

just --as dev
just --as devops
just --as pm (projectmanager)

If we can come up with an elegant way to pre-filter on metadata we can further reduce the noise and boost any repo's onboarding experience. (just --as newcomer)

I think I would need to see a concrete example, as simple as possible with as few moving pieces as possible, to understand the value proposition, as well as understand how difficult it would be to implement. I still don't understand if just would call nix or nix would call just, and what the actual concrete things are that the developer would do, i.e. files he would create and commands he would run.
My current feeling is that it sounds complicated (it would be a large change to the codebase to allow two sources of tasks, i.e. justfile recipes as well as nix expresssions) and I'm not sure if it would provide enough benefit to be useful. It would only be usable to the subset of people who use nix, and then an even smaller subset who knew about and took advantage of this integration.
And thinking about it more, I think even if it was definitely useful, I wouldn't want to do a specific integration with nix, but would rather some kind of more general plugin system, which allowed drawing additional commands from some other source.

but would rather some kind of more general plugin system, which allowed drawing additional commands from some other source.

That sounds about perfect! I'd have a strong & urgent motivation to implement such a plugin for flakes. :+1:

Here is an example of how a project could expose just tasks:
https://github.com/input-output-hk/bitte-cells/blob/WIP-cardano/cells/cardano/justTasks.nix
I think just also would require the equivalent of a task comment as some sort of "contract" attribute on every task. Running such task is then actually rather simple and equivalent to:
nix run .#justTasks.<current system>.cardano-node-2nix

We now ended up "rendering" Justfiles from their source task specifications (in Nix).
This has the added advantage that a consumer can still greet and read a familiar Justfile.
This bridges the gap into the DevOps lingua franca world of Nix for the un-initiated.
https://github.com/divnix/std/issues/118
Hence, I can close this particular issue.
Thank you for the discussion! I hope the plugin system idea might come up again in the future.

The "rendering" is, however, not very pretty. It would be great if we could consider support for going from JSON -> Justfile (see #1331).


Permissions to view and maintain

Please add some information about what roles people need to view the dashboards and manage the discover process.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: ad120c2f-c1d6-dfcd-e393-74214c1473bf
Version Independent ID: 3808fad7-df74-2005-a309-83b726eae4ef
Content: Deploying the Defender EASM Azure resource
Content Source: articles/external-attack-surface-management/deploying-the-defender-easm-azure-resource.md
Service: security
GitHub Login: @danielledennis
Microsoft Alias: dandennis

@DeanGross
Thanks for your feedback! We will investigate and update as appropriate.


⚠ PrivateHD has degraded performance

In 98e04de, PrivateHD ($PHD) experienced degraded performance:

HTTP code: 200
Response time: 4191 ms

Resolved: PrivateHD performance has improved in 617ab9e.


Document protocol? Pairing?

Hi,
thanks a lot for your work! I've just bought one of these, is that the right hardware?
Yesterday, I tried controlling the device but it seems that it requires a paring/bonding process (not sure yet what the difference is) before it accepts control messages. Is this also required for your hardware? How did you pair with the device?
I'm willing to document the protocol (the used characteristics etc.) and e.g. submit it as a PR, would that be accepted?

I found the pairing process is completely unnecessary, the device will accept all commands without pairing. The protocol is described here: http://torsten-traenkner.de/wissen/smarthome/heizung.php


Android GitHub Action: build workflow

We need a GitHub Action that does the following

Build an android APK of a given Meteor project using the build scripts
only on branch release and on [pull_request, push]
The workflow must not include linting and testing
I will provide an example project on the release branch that you can use to experiment and test the workflow

You may also read first into GitHub actions: https://help.github.com/en/actions/getting-started-with-github-actions/about-github-actions

The release branch is now up: https://github.com/leaonline/buildscripts/tree/release
The project to be build is in the simple-todos folder


Add Support for MQube.net

Checklist

[x] I'm reporting a new site support request
[x] I've verified that I'm running youtube-dl version 2019.04.30
[x] I've checked that all provided URLs are alive and playable in a browser
[x] I've checked that none of provided URLs violate any copyrights
[x] I've searched the bugtracker for similar site support requests including closed ones

Example URLs

Single audio: https://mqube.net/play/20181228624995
User: https://mqube.net/user/tsukunesoba

Description

MQube is a Japanese audio-sharing website. Signing in is not required.

Are there playlists?

Are there playlists?

Not that I'm aware of.


Stopwatch mode issues

"30 seconds until match begins" doesn't play

Massive tournament mode team/waiting for players UI thing before first round

Casual mode 10 second countdown + music doesn't play

Team names stay the same after switching sides

Funny example of team name issue:

Scramble doesn't reset stopwatch timer (maybe we need mp_tournament_restart)
This causes numerous issues including:

Round might insta-win after scramble
\ This wastes a round
\ Which causes the map vote to start after "round 1"
\ Which therefore the map doesn't actually change

No end of round music for win/loss? (Might be vanilla)

(At least casual mode end of match music still plays)

MAJOR ISSUE:
Map doesn't change after map vote
Timeline of events:

End of 2nd round, music plays
15 second bonus round
20 second chat time (tab menu)
Tab menu disappears and you can move around
Tournament has reset showing that team ready UI thing

Possible fix for major issue:
https://forums.alliedmods.net/showthread.php?t=99571&page=2

Also fix for another issue I have to encounter:
https://forums.alliedmods.net/showthread.php?p=2066621

If people are reading this, please look at https://github.com/leighmacdonald/uncletopia/issues for a list of separate issues related to stopwatch mode. This issue is outdated and contains things that have already been fixed.


fix documentation for icon_and_font_color editor setting

the documentation for the interface/theme/icon_and_font_color incorrectly states that the "dark" option makes the icons light, suitable for dark themes, and the "light" option makes the icons dark, suitable for light themes. this pr changes the documentation to say that the "dark" option makes the icons dark, suitable for light themes, and the "light" option makes the icons light, suitable for dark themes

Please squash your commits into one, see here

just wanted to make sure: this is all set, right?

Yep!

Thanks! And congrats for your first merged Godot contribution :tada:

Cherry-picked for 4.2.1.


Add RekaClient, the Vibe-Eval (Scenario and Auto-Evaluator)

Hi, in this PR, I added RekaClient and the Vibe-Eval. I did a canary run (50 instances) on Vibe-Eval scenario using Qwen-VL-Chat. Here's the result:
run_spec.json
scenario.json
per_instance_stats.json
And for running the full Vibe-Eval scenario, the conf is like:
entries: [
    {description: "vibe_eval:subject=difficulty-normal,model=vlm,num_respondents=1", priority: 1}
    {description: "vibe_eval:subject=difficulty-hard,model=vlm,num_respondents=1", priority: 1}
    ]

The credentials.conf file is like:
rekaApiKey: your-reka-api-key
critiqueModelName: reka/reka-core-20240415
critiqueType: model

Please let me know how I can improve it, thanks!

Thanks for the review @teetone! I think this PR is ready.


Add documentation for dirty-chai compatability

Thanks @graingert for this PR. I'd say this is more of a caveat with Dirty-Chai than Chai-As-Promised. Because of that I'm going to close this. If you haven't already please raise this on dirty-chai, and also please don't let this dissuade you from making more PRs against chai-as-promised! You work is valued!

@keithamus raised on https://github.com/prodatakey/dirty-chai/pull/18
It's just that this documentation would have saved me a few hours of debugging


reflex form parameter lists are uniqued

Bug Report
Describe the bug
Hello, love stimulus reflex, it makes things so simple. This is the first issue I have had in months, and I can work around it, so no rush. When creating a parameter list in a form, each key and value is made unique. This removes functionality for repeated input. Compared to rails controllers, this is not regular functionality. Thank you for any help.
To Reproduce
###view
= form_with url: user_page_path(id: Current.user.slug), multipart: true, method: :patch do
    %div{id: "user_tidbits_form", data: { controller: 'user-page-tidbits' }}
        = hidden_field_tag 'user[test][]', 'a'
        = hidden_field_tag 'user[test][]', 'a'
        = hidden_field_tag 'user[test][]', 'b'
        %button.btn{'data-reflex': 'click->User#tester'} yeet

###reflex
class User < ApplicationReflex
	before_reflex :make_as_list
	def tester
		morph :nothing
	end
	private
	def make_as_list
		5.times{ Rails.logger.info(params['user']) }
	end
end

Expected behavior
Log output should be
{"test"=>["a", "a", "b"]}
Actual behavior
Log output is
{"test"=>["a", "b"]}
Versions
StimulusReflex
gem: stimulus reflex 3.4.1
yarn<EMAIL_ADDRESS>External tools

Ruby: 2.7
Rails: <IP_ADDRESS>

Browser
firefox

@LukeClancy saw your post in the Discord - while I don't know how to fix it, I understand what you're saying is happening.
I made a simple sample app that will demonstrate the issue directly.
https://github.com/thewatts/reflex-params-example

Thanks so much, @thewatts! This will be super helpful.

This invites a new test, I'd argue


Update copyright info in the license

This: https://github.com/red-hat-storage/odf-console/blob/8268ff4b77a552b8336eeead1e62e99fbdc90863/LICENSE#L189 needs to be updated.
Reference: https://github.com/openshift/origin/blob/e6728e5e1d97886ba122ecca731716fc4d6e9ebf/LICENSE#L179

/assign @TimothyAsirJeyasing

https://github.com/red-hat-storage/odf-console/pull/610


Cannot install via composer

Trying to install but get the following issue:
composer require google/apiclient:^2.0
Your requirements could not be resolved to an installable set of packages.
Problem 1
- The requested package google/apiclient No version set (parsed as 1.0.0) is satisfiable by google/apiclient[No version set (parsed as 1.0.0)] but these conflict with your requirements or minimum-stability.
Installation failed, reverting ./composer.json to its original content.

I don't know all the ins and outs of composer. Please attach your composer.json file to make it easier to recreate this issue.

The composer file is the same one in this git.  I am basically downloading the git and running the composer require file.   I have tried adding the "google/apiclient:^2.0" directly to the composer file, but you still get the same error.

This git is google/apiclient so you'll want to just composer install after a clone.
You can run composer require google/apiclient:^2.0 from a different directory/project to treat this git as a dependency.


baboossh: 1.2.0 -> 1.2.1

Diff: https://github.com/cybiere/baboossh/compare/refs/tags/v1.2.0...v1.2.1
Changelog: https://github.com/cybiere/baboossh/releases/tag/v1.2.1
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 278121 run on aarch64-darwin 1

2 packages built:

baboossh
baboossh.dist

Result of nixpkgs-review pr 278121 run on x86_64-linux 1

2 packages built:

baboossh
baboossh.dist


[Bugfix] updates package name for docker (5.0.2 and 5.5.1)

I used this as a reference to update some package names for Dockerfiles
This relates to @dritter's commit 4f2286265bd18bf37bfd931cefafea1b86917391

I'll let @dritter handle this as our resident Docker, Travis, Vagrant, etc., expert =)


z.date() does not pick custom error messages

Using latest "zod": "^3.19.1"
import { z } from "zod";
...
      dateOfBirth: z
        .date({
          required_error: "Please select a date and time",
          invalid_type_error: "That's not a date!"
        })
...

Same issue.
As a workaround, you can override error message by passing errorMap.
      dateOfBirth: z
        .date({
          errorMap: (issue, { defaultError }) => ({
            message: issue.code === "invalid_date" ? "That's not a date!" : defaultError,
          }),
        })

It's nice if there's more convenient way to custom message.

The issue is here:
https://github.com/colinhacks/zod/blob/b898ee5763a0d374ffc8bb73572b03dec78e75a5/src/types.ts#L121
since the error code is invalid_date and not invalid_type then it returns the default error message.
const dateOfBirth = z.date( {
    required_error: "Please select a date and time",
    invalid_type_error: "That's not a date!"
} )

const invalidDate = new Date( '33/10/2022' )
const result = dateOfBirth.safeParse( invalidDate )
!result.success && console.log( result.error.issues[ 0 ].code )
// invalid_date

The more I think about this, I don't think this is a bug. It's just not intuitive. Maybe this should be documented or changed.

Argument of type '{ invalid_date_error: string; errorMap: (issue: ZodIssueOptionalMessage, { defaultError }: ErrorMapCtx) => { message: string; }; }' is not assignable to parameter of type '{ errorMap?: ZodErrorMap | undefined; invalid_type_error?: string | undefined; required_error?: string | undefined; description?: string | undefined; } & { coerce?: boolean | undefined; }'.
Types have to be fixed then

Perhaps this would help you:
https://github.com/JacobWeisenburger/zod_utilz#makeerrormap
import { zu } from 'zod_utilz'

const dateOfBirth = z.date({
    errorMap: zu.makeErrorMap({
        required: 'Please select a date and time',
        invalid_date: `That's not a date!`,
    }),
})

{
    const result = dateOfBirth.safeParse(undefined)
    !result.success && console.log(result.error.issues[0].message)
    // Please select a date and time
}

{
    const result = dateOfBirth.safeParse(new Date('33/10/2022'))
    !result.success && console.log(result.error.issues[0].message)
    // That's not a date!
}

Same problem here! :cry:

https://stackoverflow.com/questions/77465460/zod-coercion-to-date-custom-error-message?noredirect=1#comment136567416_77465460
recently happened to me as well!

I'm overriding the error map for my date field to always display a generic "Invalid date" message yet I get the message "Invalid Input" instead when parsing values such as 09/09/9999. Shouldnt this just render the only message I provided in the errorMap or am I misunderstanding it?
z.coerce
  .date({
    errorMap: () => ({
      message: "Invalid date"
    }),
  })

Hello, same problem here and when I try to use the workaround that has been provided here, with overwriting the errorMap, I keep getting errors. Console output for reference: "ARGH, an error: Error: Objects are not valid as a React child (found: object with keys {errorMap}). If you meant to render a collection of children, use an array instead.". Any other ideas on how to set a custom error message other than the standard "invalid date" on invalid date errors would be very welcome


postorgcreate emitted twice - first hook is emitted without await

Summary
This is specific to version 3.x in conjunction with the org plugin. The org plugin will ultimately call the core method scratchOrgCreate (in the org/scratchOrgCreate module). The scratchOrgCreate method will call emitPostOrgCreate (from org/scratchOrgLifecycleEvents) which emits the lifecycle event postorgcreate - this is emitted without an await (so it's properly async). The issue is that the org plugin also emits the lifecycle event postorgcreate, so we're effectively getting the hook firing twice, with the first invocation effectively being in parallel with the second.
Here are the code links to the two firings:

https://github.com/salesforcecli/plugin-org/blob/fbbcaf5d816c9e0e6040a2d5cb6690cdb6356674/src/commands/force/org/create.ts#L320

https://github.com/forcedotcom/sfdx-core/blob/050d7c5a7f49b85895c74422ebbb0494fcf0cb96/src/org/scratchOrgCreate.ts#L178

Steps To Reproduce:

Register a postorgcreate hook - a hook that just logs to the console will be sufficient
Create a scratch org

Expected result
A specific postorgcreate hook should only fire once
Actual result
The specific postorgcreate hook fires twice
System Information

Which shell/terminal are you using? (e.g. bash, zsh, powershell 5, powershell 7, cmd.exe, etc.)

zsh

If you are using sfdx

Run sfdx version --verbose --json

If you are using sf

Run sf version --verbose --json

Paste the output here

{
"cliVersion": "sfdx-cli/7.166.1",
"architecture": "darwin-x64",
"nodeVersion": "node-v16.14.0",
"pluginVersions": [
"@oclif/plugin-autocomplete 1.3.0 (core)",
"@oclif/plugin-commands 2.2.0 (core)",
"@oclif/plugin-help 5.1.12 (core)",
"@oclif/plugin-not-found 2.3.1 (core)",
"@oclif/plugin-plugins 2.1.0 (core)",
"@oclif/plugin-update 3.0.0 (core)",
"@oclif/plugin-version 1.1.2 (core)",
"@oclif/plugin-warn-if-update-available 2.0.4 (core)",
"@oclif/plugin-which 2.1.0 (core)",
"alias 2.1.0 (core)",
"apex 1.2.0 (core)",
"auth 2.2.3 (core)",
"community 2.0.1 (core)",
"config 1.4.17 (core)",
"custom-metadata 2.0.0 (core)",
"data 2.1.2 (core)",
"generator 2.0.2 (core)",
"info 2.0.1 (core)",
"limits 2.0.1 (core)",
"org 2.2.0 (core)",
"packaging 1.5.1 (core)",
"schema 2.1.1 (core)",
"signups 1.2.0 (core)",
"source 2.0.13 (core)",
"telemetry 2.0.0 (core)",
"templates 55.1.0 (core)",
"trust 2.0.3 (core)",
"user 2.1.0 (core)",
"@salesforce/sfdx-plugin-lwc-test 1.0.0 (core)",
"salesforce-alm 54.8.1 (core)",
"sfdx-bfs-plugin 2.1.0 (link) /usr/local/lib/node_modules/sfdx-bfs-plugin"
],
"osVersion": "Darwin 21.6.0",
"shell": "zsh",
"rootPath": "/usr/local/lib/node_modules/sfdx-cli"
}

I raised this over here as well: https://github.com/forcedotcom/sfdx-core/issues/634, but doesn't look like it's getting much action.

@mshanemc can this be closed now?

This was fixed in sfdx v7.169.1, see release notes: https://github.com/forcedotcom/cli/tree/main/releasenotes/sfdx#71691-sept-22-2022-stable

Hi all - I'm going to open another issue for this. The postorgcreate event will not fire at all anymore, as the lifecycleEventNames prop has been removed (here: https://github.com/salesforcecli/plugin-org/pull/391) which means no listeners are registered for the postorgcreate event (and hence don't fire the hooks). The emit in the core lib will have no effect (unless you've hooked into the lifecycle and added your own listener).


Makes editing CRAZY slow in VS2010

I don't know why, but when I was editing a test file with this add-on enabled, editing the test file becomes crazy slow.  CRAZY slow.  So slow that it lags significantly behind my typing and selecting regions of text in the test file source becomes sluggish, etc.  If I disable the add-on, then editing speed is back to normal.

This is likely down to the source code parsing that is done to identify the test macros - it could probably be a lot more efficient. To be honest I haven't looked at this addon for a while, but if I get a chance to fix it I'll update the source. Cheers for the report.


Compatibility with Base Station 2.0

Currently, all base stations 1.0 are out of stock. We are planning to buy a base station 2.0 and a tracker for our lab. Does anyone tried it and can tell us if it works? As far as I know, the tracker has to be "2018" version but it should work. I would like to be sure before buying.

Sorry, I have not got the 2.0 yet.
I think if the OpenVR works well with the Steam VR 2.0,
it's not so much hard to modify this repo to work.

Any updates on this?


no longer needed replace line in go.mod

It seems that Altinity/clickhouse-operator at now indirectly depends on newer safe version v0.5.0 of golang.org/x/text.
Keep following replace line in go.mod makes no sense but limits the update of golang.org/x/text. Should it be dropped or commented?
https://github.com/Altinity/clickhouse-operator/blob/master/go.mod#L7
replace (
    ...
    golang.org/x/text => golang.org/x/text v0.3.8
)

https://github.com/Altinity/clickhouse-operator/blob/master/go.mod#L85
golang.org/x/text v0.5.0 // indirect

@sunsingerus ^

explicit replace was used to satisfy dependencies version and looks like is not required any more. updated in 0.20.3 version


keepIccProfile doesn't retain profile on cmyk image

Possible bug
Is this a possible bug in a feature of sharp, unrelated to installation?

[x] Running npm install sharp completes without error.
[x] Running node -e "require('sharp')" completes without error.

If you cannot confirm both of these, please open an installation issue instead.
Are you using the latest version of sharp?

[x] I am using the latest version of sharp as reported by npm view sharp dist-tags.latest.

If you cannot confirm this, please upgrade to the latest version and try again before opening an issue.
If you are using another package which depends on a version of sharp that is not the latest, please open an issue against that package instead.
What is the output of running npx envinfo --binaries --system --npmPackages=sharp --npmGlobalPackages=sharp?
  System:
    OS: macOS 13.4.1
    CPU: (12) arm64 Apple M2 Max
    Memory: 16.30 GB / 96.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.10.0 - ~/.nvm/versions/node/v20.10.0/bin/node
    npm: 10.2.3 - ~/.nvm/versions/node/v20.10.0/bin/npm
  npmPackages:
    sharp: ^0.33.1 => 0.33.1

What are the steps to reproduce?
Load an cmyk image with embedded icc profile. Try to do anything with it using keepIccProfile and no profile is in the output.
What I'm actually want to achieve is to resize an image with cmyk where output is cmyk and icc profile is retained.
What is the expected behaviour?
That it retains the icc profile and output color space is cmyk.
Please provide a minimal, standalone code sample, without other dependencies, that demonstrates this problem
const sharp = require('sharp');
sharp('Channel_digital_image_CMYK_color.jpg')
	.keepIccProfile()
        .toColorspace('cmyk')
	.toBuffer()
	.then((data) => sharp(data).metadata())
	.then((metadata) => console.log('ICC', metadata.icc))
	.catch((err) => console.error(err));

Please provide sample image(s) that help explain this problem
https://upload.wikimedia.org/wikipedia/en/2/25/Channel_digital_image_CMYK_color.jpg

Have you tried setting the pipeline colourspace to ensure the image remains in CMYK throughout?
 .pipelineColourspace('cmyk')

https://sharp.pixelplumbing.com/api-colour#pipelinecolourspace

Yes, tried several combinations both with pipelineColorspace and keepMetadata as well.. but it always seems to comeout as srgb and without the icc profile.

When using the keepMetadata method, similar situations are also encountered
// test code
const sharp = require("sharp");
(async () => {
  console.log('origin metadata', await sharp("./cmyk.jpg").metadata());
  console.log('new metadata use toColorspace', await sharp(await sharp("./cmyk.jpg").toColorspace("cmyk").keepMetadata().toBuffer()).metadata());
  console.log('new metadata use pipelineColorspace', await sharp(await sharp("./cmyk.jpg").pipelineColorspace("cmyk").keepMetadata().toBuffer()).metadata());
})();

``

```js
origin metadata {
  format: 'jpeg',
  width: 500,
  height: 333,
  space: 'cmyk',
  channels: 4,
  depth: 'uchar',
  density: 180,
  chromaSubsampling: '4:4:4:4',
  isProgressive: false,
  resolutionUnit: 'inch',
  hasProfile: true,
  hasAlpha: false,
  orientation: 1,
  exif: <Buffer 45 78 69 66 00 00 49 49 2a 00 08 00 00 00 0a 00 0f 01 02 00 06 00 00 00 86 00 00 00 10 01 02 00 17 00 00 00 8c 00 00 00 12 01 03 00 01 00 00 00 01 00 ... 9492 more bytes>,
  icc: <Buffer 00 08 80 70 41 44 42 45 02 10 00 00 70 72 74 72 43 4d 59 4b 4c 61 62 20 07 d0 00 07 00 1a 00 05 00 29 00 35 61 63 73 70 41 50 50 4c 00 00 00 00 41 44 ... 557118 more bytes>,
  iptc: <Buffer 50 68 6f 74 6f 73 68 6f 70 20 33 2e 30 00 38 42 49 4d 04 25 00 00 00 00 00 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 38 42 49 4d 03 ed 00 00 ... 9948 more bytes>,
  xmp: <Buffer 3c 3f 78 70 61 63 6b 65 74 20 62 65 67 69 6e 3d 22 ef bb bf 22 20 69 64 3d 22 57 35 4d 30 4d 70 43 65 68 69 48 7a 72 65 53 7a 4e 54 63 7a 6b 63 39 64 ... 16899 more bytes>
}
new metadata use toColorspace {
  format: 'jpeg',
  size: 93328,
  width: 500,
  height: 333,
  space: 'srgb',
  channels: 3,
  depth: 'uchar',
  density: 180,
  chromaSubsampling: '4:2:0',
  isProgressive: false,
  resolutionUnit: 'inch',
  hasProfile: false,
  hasAlpha: false,
  orientation: 1,
  exif: <Buffer 45 78 69 66 00 00 49 49 2a 00 08 00 00 00 0a 00 0f 01 02 00 06 00 00 00 86 00 00 00 10 01 02 00 17 00 00 00 8c 00 00 00 12 01 03 00 01 00 00 00 01 00 ... 9490 more bytes>,
  iptc: <Buffer 50 68 6f 74 6f 73 68 6f 70 20 33 2e 30 00 38 42 49 4d 04 25 00 00 00 00 00 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 38 42 49 4d 03 ed 00 00 ... 9948 more bytes>,
  xmp: <Buffer 3c 3f 78 70 61 63 6b 65 74 20 62 65 67 69 6e 3d 22 ef bb bf 22 20 69 64 3d 22 57 35 4d 30 4d 70 43 65 68 69 48 7a 72 65 53 7a 4e 54 63 7a 6b 63 39 64 ... 16899 more bytes>
}
new metadata use pipelineColorspace {
  format: 'jpeg',
  size: 92010,
  width: 500,
  height: 333,
  space: 'srgb',
  channels: 3,
  depth: 'uchar',
  density: 180,
  chromaSubsampling: '4:2:0',
  isProgressive: false,
  resolutionUnit: 'inch',
  hasProfile: false,
  hasAlpha: false,
  orientation: 1,
  exif: <Buffer 45 78 69 66 00 00 49 49 2a 00 08 00 00 00 0a 00 0f 01 02 00 06 00 00 00 86 00 00 00 10 01 02 00 17 00 00 00 8c 00 00 00 12 01 03 00 01 00 00 00 01 00 ... 9490 more bytes>,
  iptc: <Buffer 50 68 6f 74 6f 73 68 6f 70 20 33 2e 30 00 38 42 49 4d 04 25 00 00 00 00 00 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 38 42 49 4d 03 ed 00 00 ... 9948 more bytes>,
  xmp: <Buffer 3c 3f 78 70 61 63 6b 65 74 20 62 65 67 69 6e 3d 22 ef bb bf 22 20 69 64 3d 22 57 35 4d 30 4d 70 43 65 68 69 48 7a 72 65 53 7a 4e 54 63 7a 6b 63 39 64 ... 16899 more bytes>
}

the space is not cmyk

Do we have any update on this. I am also facing kind of similiar issue. Where we have an image which is cmyk and when I am trying to process it using sharp it is changing the color space. And my image is not having the icc profile in it.

The test keep existing ICC profile seems to test for a Generic RGB Profile ICC profile in the output file.
Confirmed that the current implementation of keepIccProfile won't work for CMYK profiles with following test:
it('keep existing CMYK ICC profile', async () => {
  const data = await sharp(fixtures.inputJpgWithCmykProfile)
    .keepIccProfile()
    .toBuffer();

  const metadata = await sharp(data).metadata();
  const { description } = icc.parse(metadata.icc);
  assert.strictEqual(description, 'U.S. Web Coated (SWOP) v2');
});

Taking a look at the pipeline, it seems this fails because it converts to sRGB/P3 using the embedded profile:
https://github.com/lovell/sharp/blob/26d0b7147d874d497aa5500debce5df2804ffb6a/src/pipeline.cc#L330-L352
Updating that code to the following fixes the issue:
// Convert to sRGB/P3 using embedded profile
try {
  if ((baton->keepMetadata & VIPS_FOREIGN_KEEP_ICC) && baton->withIccProfile.empty()) {
    // New implementation
    if (image.interpretation() == VIPS_INTERPRETATION_CMYK) {
      baton->colourspace = VIPS_INTERPRETATION_CMYK;
    }

    image = image.icc_transform(inputProfile.first, VImage::option()
      ->set("input_profile", inputProfile.first)
      ->set("embedded", TRUE)
      ->set("depth", sharp::Is16Bit(image.interpretation()) ? 16 : 8)
      ->set("intent", VIPS_INTENT_PERCEPTUAL));

  } else {
    // Current implementation
    image = image.icc_transform(processingProfile, VImage::option()
      ->set("embedded", TRUE)
      ->set("depth", sharp::Is16Bit(image.interpretation()) ? 16 : 8)
      ->set("intent", VIPS_INTENT_PERCEPTUAL));
  }
} catch(...) {
  sharp::VipsWarningCallback(nullptr, G_LOG_LEVEL_WARNING, "Invalid embedded profile", nullptr);
}

@lovell All tests, including the new one for preserving a CMYK profile, pass successfully. I am uncertain if this adjustment is located in the most suitable part of the codebase though, as I have a limited understanding of C and the specific workings of ICC tranformations in the pipeline.
I'm willing to work on a preliminary PR if that helps facilitate a more detailed review and discussion on how best to integrate these changes.

The change in commit https://github.com/lovell/sharp/commit/fb70fbb09ff76440124b1fad567c39bd2997cc99 prevents the erroneous sRGB transformation when using CMYK everywhere, plus adds a slightly-modified version of @adriaanmeuris' example test case to help prevent regression. Thanks all for reporting and helping analyse this issue.

@lovell thank you so much for the recent update; I noticed that the profile is correcly attached now.
However, it seems this icc transform to sRGB is always happening:
https://github.com/lovell/sharp/blob/60f4048d6c33f414979169c660ce3bad69a395a6/src/pipeline.cc#L330-L344
Which results in a color shift. Commenting out the icc_transform solves this. Here's a comparison visual to illustrate the difference:

Adding this condition to the if statement instead of commenting out the icc_transform also fixed this, but it does result in the test tints cmyk image red to fail.
image.interpretation() != VIPS_INTERPRETATION_CMYK &&

Additionally, I found that to maintain the color profile, it's essential to use .pipelineColourspace('cmyk') and .toColourspace('cmyk'). I noticed that using await sharp(inFile).keepIccProfile().toFile(outFile); still results in a conversion to sRGB, despite the keepIccProfile option being set. Is this the expected behavior?
I'm happy to help out or provide additional information if needed.

@adriaanmeuris Are you able to test to see if the following patch fixes the problem you're seeing?
--- a/src/pipeline.cc
+++ b/src/pipeline.cc
@@ -331,6 +331,7 @@ class PipelineWorker : public Napi::AsyncWorker {
         sharp::HasProfile(image) &&
         image.interpretation() != VIPS_INTERPRETATION_LABS &&
         image.interpretation() != VIPS_INTERPRETATION_GREY16 &&
+        baton->colourspaceInput != VIPS_INTERPRETATION_CMYK &&
         !baton->input->ignoreIcc
       ) {
         // Convert to sRGB/P3 using embedded profile

(I need to refactor some of the variable naming in here as colourspaceInput should really be called something like colourspacePipeline instead.)

@lovell Yes, the patch works as expected. The profile is attached, and the output colors now align with the input colors. Looks great!

@adriaanmeuris Great, thanks for confirming, added via commit https://github.com/lovell/sharp/commit/3eeaee71c06c38d0d9e4d2abcb6b04397febe0b8

v0.33.3 now available, thanks everyone for your help fixing/testing this.


How to train the CornerNet_Saccade in a distributed way

I use four RTX 2080Ti to train the CornerNet_Saccade model on one machine. Unfortunately, I got CUDA out of memory error setting the batch_size to 48(chunk_size is set to be [12,12,12,12]). In practice, batch_size which is set to be 32 means that chunk_size is set to be [8,8,8,8] can run with no error. But in the MASTER NODE, GPU memory is almost full.
So I'd like to ask How to config the distributed training

RTX2080Ti has less memory than 1080Ti, so you will need to reduce the batch size to train on RTX2080Ti. Although our code supports distributed training, we never used it to train our model. All the models reported in the paper are trained on a single node with 4 1080Ti GPUs. Are your 4 GPUs on a single node? If so, I would suggest you to try a batch size of 44 (chunk size of [11, 11, 11, 11]).

I've test the case whose chunk size is [10,10,10,10],But it failed. I found that GPU Memory in the master node always is allocated about 2GB more than other nodes. In my setting, distributed training use NCCL 'backend' and 'env://' to run. Is that way correct?
I also review PyTorch Docs, in one case that they part datasets with different size to each node depend on their own rank, Have u used this strategy or something I'm wrong with it?

How to run it in a distributed way? I am failed


deprecate spi_flash_w25qxxdv

spi_flash_w25qxxdv has been superseded by spi_nor which is a generic driver that should support all JEDEC-compatible SPI NOR devices.  It should be removed because people with Winbond flash devices see it and think it's what they should use.  It's no longer active for any in-tree target.
There's some evidence this is being used in out-of-tree boards (a bug fix was merged 2019-04-16).
I don't see anything in the documentation providing a deprecation process for drivers.

the driver in the title does not exist anymore


Modifying default configuration in config/rubocop.rb is unclear

I want to specify config/rubocop.rb in my .rubocop.yml files, and in that ruby file, use a gem I own to load in configs, but I haven't been able to figure out or get working how to do this via the config loader.  I've looked through the rspec cop code, but have no working solution.
Pseudo code in my config/rubocop.rb (adapted from https://github.com/nevir/rubocop-rspec/blob/605caf1480215b185d36fd0c345869554924d896/lib/rubocop/rspec/inject.rb )
require "mygem/rubocop"
mygem_rubocop_config = MyGem.rubocop_config
config = ConfigLoader.merge_with_default(mygem_rubocop_config.hash, mygem_rubocop_config.path)
ConfigLoader.instance_variable_set(:@default_configuration, config)

but there's no way I see how to do that right now.  I'm happy to make  a PR to update the docs (or even code) if you can help me figure this out.
Up until now, I've had an inherited file in every repo, but that's getting hard to maintain.

I think I understand what you want. You want to use RubyGems to handle versioning and dependencies towards common configuration. And for that you need to involve a Ruby file. It's can't all be YAML.
I've done an experiment here, that takes from your idea and goes in a slightly different direction. See what you think.

@jonas054 pretty much, though I was doing
require: "config/rubocop.rb"

Can't you use inherit_gem?


Some conflict and error during generations

I got some conflict error reports when installing the repository, but I can get it to run successfully. Some errors show up in the 2nd image and fail to generate the result. Any solutions to that? Thanks!

@tadeodonegana Is it possible to run this without CUDA purely on the CPU?

I am running into the second error that you're running into. @tadeodonegana Is it possible to run this without CUDA purely on the CPU?

Hi @chen-rn ,
After setting the model weights in line 22 add the following line:
cfg.MODEL.DEVICE = "cuda" if torch.cuda.is_available() else "cpu"
There's a PR that currently proposes this as a solution, you can see it here #11. We are currently waiting to test the change properly and evaluate merging it.
Please let me know if this works.

This PR was just merged, and it should solve the issue for the app.py file (Gradio version).

CPU support was also added in #16 and the error about Torch not compiled with CUDA enabled should be now solved.


Improve i18n

The i18n is more complex than needed and too fragile. A page may crash if a lang file is incomplete. Also the ideology tree is repeated on each lang, witch may cause crashes and different results.
If you agree I can solve this issue.

Yea, I'm sadly aware of those 2 issues, if I had more free time I'd have fixed it already. A base english version with a single unified json per language with all the text seems like the ideal way to handle this.


Job status has strange string

When the job is first submitted it submitted in the Status column, but after some time (maybe while the job is running) it has a string that says something like INFO:mljob.geneplexus:3. run_SL... features=%s, features
If this is indeed for a running job, maybe just change the string to say Running?

@billspat This issue seems to be closed, but the status messages don't seem to be updated to the last message above. Are they in a new issue?

Also one thing I noticed it that before the message says completed, it looks like there is a space separated list of numbers printed out. Not sure what those number represent

@ChristopherMancuso  to answer your question above the numbers shouldn't be in there.    I captured the output of a curl  into the log and I'll suppress that output.   I'm glad you saw them (I never did).
As a fix for this issue, would you like this merged into the main geneplexus.net site for the reviewers or hold it with our other changes (in the dev branch) for post-review but pre-publication?

I don't think there is a reason to push this to the main site until after it is reviewed


[HTML5] Logitech Dual Action Gamepad FF/Linux

Reported here: https://github.com/godotengine/godot/pull/45078#issuecomment-803576712
Cherry picking is easy, but not automatic due to renames, let me know if I should make a 3.3 PR.

Thanks!

Cherry-picked for 3.3.


[Payment card / Subscription] Integrate “Add payment card” screen with backend data and “Payment card” section

This covers this section of the doc: https://docs.google.com/document/d/1jXV_vIsOGZuL0dMiuXDWRETAFRX64ODVAhWPtiuFXT8/edit?pli=1#bookmark=id.sww2rbm0jchn @fabioh8010
Issue OwnerCurrent Issue Owner: @narefyev91

Hi, I'm Fábio from Callstack - expert agency - and I would like to work on this issue.

Hi, I'm Nicolay from Callstack - expert agency - and I would like to work on this issue.

@narefyev91 Can you help me update the body of the issue with what exactly we're covering from the doc please? Thank you

Friendly bump on the above @narefyev91 🙇

Friendly bump on the above @narefyev91 🙇

Oh sorry just missed mention - yeah sure - i will double check what is it - and will send you info here

@MitchExpensify here you are https://docs.google.com/document/d/1jXV_vIsOGZuL0dMiuXDWRETAFRX64ODVAhWPtiuFXT8/edit?pli=1#bookmark=id.sww2rbm0jchn

@narefyev91 Any updates here?

@narefyev91 Any updates here?

WIP today will be a PR

Changes already located inside this PR https://github.com/Expensify/App/pull/43572 - (it was hard to isolate them)

I think you can just close this issue out, as https://github.com/Expensify/App/pull/43572 consolidated https://github.com/Expensify/App/issues/38619, https://github.com/Expensify/App/issues/38630, https://github.com/Expensify/App/issues/44118, https://github.com/Expensify/App/issues/38633.

Closing as this is completed and deployed.


Watch() extension method that allows include and exclude list.

Implement an extension method for IFileProvider that allows you to watch() for files, but using an include list and exclude list (of glob patterns, using DotNet.Glob
Have raised an issue to see if microsoft would consider putting this in the IFileProvider contract, as it allows more granular control of which files you are monitoring, which could be better for performance reasons:
https://github.com/aspnet/FileSystem/issues/253

The way I see this working, is to call Watch() on the underlying provider for each include pattern. Then evaluate the exclude patterns after the change tokens from the underlying provider are signalled. To do this, I need to be able to tell which file triggered the change token. May not be possible.


feat: projects v2 support

Describe what this PR does / why we need it
This PR implements the projects v2 interface as well as the picker for fzf-lua.
Adds:

Projects v2 support as well as the fzf-lua picker addition.

The interface for the new command changed a bit. Instead of add, move, and remove I went with set and remove. I The flow of projects v2 changed a bit and add and move felt a little too similar.

A config option default_to_projects_v2, which makes the card command default to use projects v2. Both versions are still available under the cardlegacy and cardv2 commands, regardless of this setting.

Does this pull request fix one issue?

Addresses https://github.com/pwntester/octo.nvim/discussions/414
Describe how you did it
Followed the pattern of the other cards command. As noted above I changed the interface for the new command slightly, but to something that made sense to me and how projects v2 flowed.
Describe how to verify it
Mess around with projects v2 inside Octo. Everything should work as expected.
Special notes for reviews
I added two small additions as riders:

Adds query timeout to searching in fzf-lua to make search more responsive.
Adds draft PR special highlighting when viewing an pr list in fzf-lua.

These are tiny changes that are just QoL adds for fzf-lua.
Also I updated the README to account for some fzf-lua changes as well.

Thanks for the PR, looks great! Will review ASAP

Cant wait to see this merged guys, the only reason I have Telescope installed is Octo. Thanks for this.

@Cih2001 fwiw, fzf-lua is already supported in Octo.nvim. This PR extends that support (even beyond Telescope's support) with Projects V2 additions. The bulk of Octo works just fine though

@milogert sorry for the late review. Can you please rebase against master?

I believe I am.. Right? I might be missing something though. My GitHub ui says that I'm just  8 commits ahead of master and no commits behind it

Oh, you are, sorry. It looks good to me, but can you please add placeholders for the missing pickers for telescope and vim-clap?

Yep, just pushed changes up over lunch :) Thanks for the eyes!

Thanks you for the contribution!

Hello,
I see this PR has already been reverted by https://github.com/pwntester/octo.nvim/pull/474
I guess because of the error about gh token not having the projects permission.
Just wanna share that I can overcome that.
I manually created a token with the permission. Then gh auth login, and use the option to fill an existing token instead of auto generating.
So I think this feature should be updated to be auto-available when the token has the permission.

Hello,
I see this PR has already been reverted by https://github.com/pwntester/octo.nvim/pull/474
I guess because of the error about gh token not having the projects permission.
Just wanna share that I can overcome that.
I manually created a token with the permission. Then gh auth login, and use the option to fill an existing token instead of auto generating.
So I think this feature should be updated to be auto-available when the token has the permission.

Thanks @tiev a couple of alternatives are being discussed here, feel free to chime in, but the idea of reverting this PR is to avoid people not using projects v2 to have to upgrade their tokens.


snake isn't built

I tried building snake but snake.c isn't generated:
$ make bin/snake
bin/mirth2
Building.
Done.
rm -f bin/mirth.c
gcc -std=c99 -Wall -Wextra -Wno-unused-function -Wno-unused-parameter -Werror -pedantic -o bin/snake bin/snake.c `pkg-config --libs sdl2`
gcc: error: bin/snake.c: No such file or directory
make: *** [Makefile:74: bin/snake] Error 1

Hi @kephas!
To get snake building, you will need to uncomment the line containing import(snake) in src/main.mth (line 67). I.e., turn it into
import(snake)

Then make bin/snake and make play-snake should work, assuming sdl2 is installed. Please let me know if you run into an issue.
(This is terrible UI, I know. I'm sorry, and I will fix it.)

Changed mirth.mth and it works like a charm!


Change keepalives idle field to numbers appropriate for minutes, not seconds.

Description

Do we set the Redshift session timeout_sec to 14400?  I have a customer that is seeing a large number of connections (336) during a 4 thread job run, and I am wondering if we are not reusing connections and a bunch are just idle and not timing out early enough.. Thoughts?

We supplied fields on the scale of seconds. It should instead be minutes.
Checklist

[x] I have read the contributing guide and understand what's expected of me
[x] I have signed the CLA
[x] I have run this code in development and it appears to resolve the stated issue
[x] This PR includes tests, or tests are not required/relevant for this PR
[x] I have opened an issue to add/update docs, or docs changes are not required/relevant for this PR
[x] I have run changie new to create a changelog entry

Holding off on merging just until I get word of whether we ought to backport this or not!

No backport needed.


Attention to MXO2 that offer payment services.

Today one of our affiliated partners has asked for support from this person. Mainly asked for $ 500 with invoice and prepayment. Then we checked out the company he had communicated and was closed for 6 months. Under the conversations. Pay close attention to the scammers and not paid first.

Him is not UK but Indian
Company dissolved : https://beta.companieshouse.gov.uk/company/10244996

ohhhh, thanks for information, we wanted to contact him, but already what we saw is enough

Yes, make attention to dont pay before. Him before told that name is Sam and company is Maximum oxigen ltd. Him register company online and dont pay tax, the company is dissolved. Can you inform with<EMAIL_ADDRESS>them have all info. Him is Indian and the name is Singh, Shimbhu

now it's a fashion to cheat. they invent anything
Thanks for information

Hi guys,
Please aware such person and https://touristcoin.net and https://www.listex.io...
First that person is just blackmailing us for give free services to them ...We have already share everything with him and these are the fact.

We didn't call or contact him for payment.
He is fake and just wasting our time whole days for asking solutions...we given perfect analysis and facts about the solutions.
We ask him to create invoice but he refused and saying pay through the BTC which is illegal.
If I ask to create invoice that mean it would be a legal process and mention that it would be from Indian company (see in chat) so how we are illegal.
We also told him that our company is registered in UK but we never doing any transaction or Trading there because some trademark issues so how were fraud..?
He removed some chat part and we never demand for any payment from him...so make sure before giving any support

We have complete billing and support system...
Finally...He is blackmailing us and we are ready to share whole chat if any one needed...

@minersbad Please ready fact and than share your views..

I know them well and I think it's good to close your mouth.

He is still black mailing us..please check screenshot..

@minersbad this ID is belong to same person..
Because Id  @minersbad is not having any activity but he is replied in this post..so guys these people of https://touristcoin.net and https://www.listex.io... doing scam to just blackmailing and want services free..

where you see it?
here my activity profile from a lot of time

I think that you are a scam true

@mxo2 sorry that it means that if someone does not post them they are?

@mxo2 I honestly saw the conversations on skype, and the facts say otherwise

@coinlisting the important thing is to be careful not to pay these improbable people who offer paid services first

BTC is illegal? @mxo2 I think you need a doctor

maybe him is illegal :D

please folks, the important thing that you pay attention to pay this person upfront. Those other people who talk about him.

these guys saying that they are mobile operator but I think such activity looking very childish...

@touristcoin quiet, we know who to believe well

:O Apollo IT i know, very seriuos him

I post for apollo IT because his fork is not working ...If posting issue is fake than its amazing...
Other people also agree with that...Still his fork is not stable for us..If it's not working means not working...that means not i am fake..

@mxo2 here we talk that you try to cheat people. Not that the fork works, do you realize it?

without words.  Those other people who talk about him.

I got information and found that these guys developing fraud tourism platform to get bitcoin and making money..This group is not accepting and paying though the banking system..they want btc Transaction..
Please don't invest , support these guys..
https://touristcoin.net and https://www.listex.io

@coinlisting Hi Mark, dont worry that CEO of ListEX and us have mailed github for this person abuse. now they will take provisions.

@touristcoin Yes, but I still want to understand why these people are given the computer. Illegal bitcoin. But why do you still trust him

@coinlisting  you are definitely right. @mxo2  It must be ignored

BTC illegal ahuauhhau. yes @coinlisting i back to work

coinlisting , mxo2, salvo, touristcoin and listex are same team of frauders. Be careful people! If you don't want to lose your money, dont use this service. It is a group of unprofessional morons, who do not have any respect for their customers and their opinions.

you are not credible


refactored large html in javascript

I moved html from app.js to index.html and used Jquery to update the movie data
Also removed a  from  for the movie title

movie-info does not show on second time user searches after closing modal. modal poster doesn't appear too.


Suite Variables with a value beginning with @ symbol cannot be overwritten

When I set a suite variable to a value beginning with '@', then i cannot overwrite it with a different value.
Repro code
test
    Set Suite Variable            ${test}         @testname1
    ${name2}                      set variable    anothername
    Set Suite Variable            ${test}         ${name2}
    Should Be Equal As Strings    ${test}         ${name2}

Console output
test                                                                  | FAIL |
@testname1 != anothername
ENV
robotframework==3.1.2
Python 3.7
Windows 10

Does using $test instead of ${test} with Set Suite Variable resolve the issue?

using $test works as long as ${name2} is set that way.
eg this works
Set Suite Variable             ${test}         @testname1
    ${name2}                      set variable    anothername
    Set Suite Variable         $test         ${name2}

but this does not
Set Suite Variable             $test         @testname1
    ${name2}                      set variable    anothername
    Set Suite Variable         ${test}         ${name2}

This is strange but actually documented behavior. The docs of Set Suite Variable first say this:

The name of the variable can be given either as a normal variable name (e.g. ${NAME}) or in escaped format as \${NAME} or $NAME. Variable value can be given using the same syntax as when variables are created in the Variable table.

and later there's this note:

NOTE: If the variable has value which itself is a variable (escaped or not), you must always use the escaped format to set the variable:

The reason for the behavior is that the name of the variable to be set can be given to Set Suite Variable as a variable and thus that variable needs to be resolved to get the real variable name. Here's a simple example:
*** Test Cases ***
Example
    Set Variable To X    $first
    Set Variable To X    @second

*** Keywords ***
Set Variable To X
    [Arguments]    ${name}
    Set Suite Variable    ${name}    X

It probably be clearer if you'd always need to use $var or \${var} syntax with this keyword and if you use ${var} then that variable would be resolved and the resulting value would be used as variable name. Changing it would be backwards incompatible, though, and I don't think that's worth the effort.

Forgot to mention that your example ended up creating new variable @{testname} with value ['anothername']. The should be a log message showing that.


0x173 repro - do not merge

Description
Triggering assert 0x173

https://github.com/microsoft/FluidFramework/pull/17401 fixed this, there is no need to showcase the repro anymore.


[JSPM] Unable to calculate canonical name with gulp build

Hi,
Not sure if this topic has been already raised, i got trouble with a fresh clone of the repo (jspm branch) when I tried to  build the app with "gulp build":
Error: Unable to calculate canonical name to bundle file:///f:/ng6/NG6-starter/../app.js
    at getCanonicalNamePlain (f:\webapp\ng6\NG6-starter\node_modules\jspm\node_modules\systemjs-builder\lib\utils.js:177:13)
    at getCanonicalName (f:\webapp\ng6\NG6-starter\node_modules\jspm\node_modules\systemjs-builder\lib\utils.js:88:19)
    at f:\ng6\NG6-starter\node_modules\jspm\node_modules\systemjs-builder\lib\arithmetic.js:84:38
    at process._tickCallback (node.js:366:9)

My relative path problem has been 'solved' when i replaced l.19 in Gulpfile.js by:
return path.relative(root, path.resolve(path.join(root, resolvePath, glob)));

Does anyone already encounter this issue on windows and solved it in a cleaner way?
Thanks

Thx! @stephanbureau Saved me some time!


AlignArguments edge case bug

AlignArguments does not properly format multi line argument clauses when there are two or more arguments on the same line, and one of the arguments spans more than one line:
A(
  short = short, longParamName = Map(
  one -> two
)
)

Failing test:
Format failure:
 ---- Expected ----
A(
  short         = short,
  longParamName = Map(
    one -> two
  )
)
 ---- but was-----
A(
  short         = short, longParamName = Map(
  one -> two
)
)

We have this problem. Another way to reproduce it
    def foo( a: Any ) = ???

    foo(
      a = (
      true
      || false
    )
    )

@cvogt The latter issue is resolved by https://github.com/daniel-trinh/scalariform/pull/101. No solution yet for the original issue.

@daniel-trinh The expected outcome in your example is inconsistent with some existing tests, namely
"""1 + (
     |  a, b, c)""" ==>
   """1 + (
     |  a, b, c
     |)"""

and
  """a(b,
    |(c), {
    |d})""" ==>
  """a(
    |  b,
    |  (c), {
    |    d
    |  }
    |)"""

which expect multiple arguments to be allowed on the same line. Personally I have no problem forcing arguments to live on their own line (when the argument list itself is already multiline).

This issue was moved to scala-ide/scalariform#183


Request Forwarding from another Language Server Extension

I am working on a language server extension for ConTeXt with embedded Lua code which I want to get Intellisense support on. My extension does not have any language features for Lua and I want to use request forwarding to achieve Intellisense for Lua.
I opened an issue on VScode's Extension Sample asking about language support using VSCode's request forwarding.
I am looking for some answers on how I could go about getting Lua language support (auto completion, for example) in my language server extension, whether through request forwarding and otherwise. May I ask if anyone has experience or resources in how I could go about doing so?

I have no experience with this, but I believe this is a pure client-side feature.

Hi @sumneko ,
Spending some time with this issue, I found that request forwarding works correctly with a different Lua extension I installed by (keyring) [https://github.com/keyring/vsc-lua] and auto completion suggestions are returned in embedded Lua code.
Previously, I only had this Lua extension installed and there were no auto complete suggestions even though I had not changed any code in my client, but now it works with another Lua extension installed.
This leads me to conclude that there is no response from this language server when VSCode sends a request through request forwarding to this extension.
Could there be an issue with how requests are being handled? Or is there some deviation from the LSP that I am unaware of?

Are you sure this server starts? Is there the process with name of "lua-language-server"?
If you confirm it can be started, you can add --loglevel=debug and --rpclog in command line (using Lua.misc.parameters) then provide your log

Hi Sumneko, I can confirm that the extension (id = sumneko.lua) is running when I run an extension host. Attached is the log file generated, I hope this helps!
Some things to note:

I'm trying to get the extension to run with files of extension (.tex), your extension works perfectly with (.lua) files
I'm only trying to get completion suggestions through request forwarding as I believe diagnostics are not supported with this feature yet
I tried with yet another Lua extension (by TenCent) and I cannot get a response from that extension either, so this might really be more of a VSCode request forwarding issue

file_c _Users_rlew_mock-context.log

Please provide log with --loglevel=debug and --rpclog in Lua.misc.parameters

Here are the debug logs, sorry about that, I had the wrong setting previously.
file_c_Users_rlew_mock-context.log
s

Please try to add "embedded-content" into Lua.workspace.supportScheme

Hi sumneko, updating the supportScheme did not seem to fix the issue, I've attached the new logs as I am unsure of what to make of it, rpc receive seems to get the right params for a completion request, but rpc send responds with a Content Length.
It is also worth noting that the log files only update when I open a .lua file in the editor, only then does the logging take place when I try on a demo.tex file.
file_c_Users_rlew_mock-context-2.log

It is also worth noting that the log files only update when I open a .lua file in the editor, only then does the logging take place when I try on a demo.tex file.

You can use VSCode API vscode.extensions.getExtension("sumneko.lua")?.activate()

You can try to debug this server, see https://github.com/sumneko/lua-language-server/wiki/Debug
Set breakpoint at script\provider\provider.lua:554

Lua.workspace.supportScheme should be string[] instead of string.

This fixed the issue, I can get completion results for .tex files.
Added "files" in the supportScheme to get the same support for .lua files as well. Thanks for the help!
Added vscode.extensions.getExtension("sumneko.lua")?.activate() in my extension client during the activation of my server, but the server only starts sending a response after opening a .lua file.
settings.json
"Lua.workspace.supportScheme" : [     "embedded-content",      "file",      "git" ]
extension.ts
`
export function activate(context: ExtensionContext) {
if (extensions.getExtension("sumneko.lua") != undefined) {
vscode.window.showInformationMessage("lua server activated")
extensions.getExtension("sumneko.lua")?.activate()
}
// The server is implemented in node
let serverModule = context.asAbsolutePath(path.join('server', 'out', 'server.js'));
// The debug options for the server
// --inspect=6009: runs the server in Node's Inspector mode so VS Code can attach to the server for debugging
let debugOptions = {
execArgv: ['--nolazy', '--inspect=6009'],
"context.trace.server": "verbose"
};
`

Added vscode.extensions.getExtension("sumneko.lua")?.activate() in my extension client during the activation of my server, but the server only starts sending a response after opening a .lua file.

I have no idea now.

I am closing the issue as the main issue has been resolved by adding Lua.workspace.supportScheme :["embedded-content"]  to my settings.json
Thanks a lot! I appreciate the help.


TwinCAT 4020 and older not working

Problems with downloading data types. Will be checked.

Development started. Closing this and continuing in issue #42


read --strip openapi_client_axios: Preserve responses

Potential fix to https://github.com/openapistack/openapicmd/issues/37

I think a better approach here is to replace responses with an empty array, to preserve type validity.
(Even though openapi-client-axios doesn't actually use responses for anything)

Fixed in https://github.com/openapistack/openapicmd/commit/8c89ffcc922e2b7d99f3deec1dfc4c70316684a4


Add API to assign/update owner of a grant

Problem
With the recent Import Grants feature, the default value for non-human access grants' owner field is empty. This is because Guardian can't determine the owner of the imported grants except for human accounts (individual email).
Requirements

Ability to assign a new owner to grants with empty owner
Ability to replace the existing owner

Proposed solution

Add API for updating grant's owner
PUT /grants/:id/owners with request body: { "account_id"<EMAIL_ADDRESS>}
Add generic update grant API (preferred)
PATCH /grants/:id with request body: { "owner"<EMAIL_ADDRESS>}

Checklist

[ ] Send notification to the new owner
[ ] Send notification to the previous owner (if any)
[ ] Record in audit log

Next:

Introduce co-owners: []string field into Grant. An access/grant can be owned by multiple people especially if it's a service account or group access. co-owners will receive notifications like expiring notif and revocation notif the same way as the original owner.

@ravisuhag @haveiss @mabdh @bsushmith requesting for your comments 🙏

This feature will also help us in assigning a new owner in case the previous owner is not part of the organization.
For example, we see for serviceAccounts, the previous owners are no longer in the org, and then nobody gets any reminders when the particular serviceAccount access will expire.

Would it be possible to remove owners also? In case somebody wants to re-assign their ownership and does not want to be notified about it?

Grants should have owner(s) unless it is undeterminable (like in ImportGrants). If a user doesn't want to receive notifications about certain grants, they should hand them over to someone else.

In the proposed options - I feel option2 might lead to abuse as people might use this to update other fields even if they are not intended to be.

this API should only work on allowed fields. For now, I think it'll be only owner, later after we introduced co-owners we can also add them.

Grants should have owner(s) unless it is undeterminable (like in ImportGrants). If a user doesn't want to receive notifications about certain grants, they should hand them over to someone else.

Yes. Agreed. I meant in a manner of -
Could we have similar restrictions in the way we add/remove approvers for a given step. We check to ensure at least one approver is present in case of removal. We should be able to do that here also.

Yeah, I feel the 2nd solution is simpler. But do we need to restrict the caller of the API? So not all people could update the owner field.
For the next co-owners: []string, I am not sure if it is that scalable to do so, but I think that could be discussed later.

But do we need to restrict the caller of the API?

@mabdh the API restriction will be done from the auth proxy (shield) only, as right now that's how we configure superadmin privileged APIs as well

@bsushmith @mabdh can we sign off on the preferred approach? if so I'll work on this soon

Agreed on the second approach with restrictions on what can be updated. 👍


do not run remote tests inside container

when running the podman integration tests inside a container, we should
not be running the remote tests.
Signed-off-by: baude<EMAIL_ADDRESS>

LGTM

/lgtm


Automatically build and push Docker images on tag pushes

Is it possible to also slim directly? And where should this be built?

Slimming is (or was?) possible in a GitLab CI pipeline, see https://gitlab.ids-mannheim.de/KorAP/CorpusCompositionAnalyzer/-/blob/master/.gitlab-ci.yml?ref_type=heads#L53
The last build failed, however. Don't know why. Don't know about GitHub.


on answering of 2nd question, I got old ui-tab title

and if you ask him "more". should tab title be renamed to "Bot | more"?

Better to always rename (special word list is bad )

added bc9c19d


New connection monitor

Setting up connection monitor referred to in this tutorial is the connection monitor (classic)
Can the tutorial be updated with the new one please?

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

ID: 3bf662d1-53fb-f651-ee67-6e174836d739
Version Independent ID: 67782b9a-1dd5-acb4-6d93-62ee9ff60d43
Content: Tutorial - Monitor network communication using the Azure portal
Content Source: articles/network-watcher/connection-monitor.md
Service: network-watcher
GitHub Login: @damendo
Microsoft Alias: damendo

@jschrap
Thanks for your feedback! We will investigate and update as appropriate.

@halkazwini There's a clear message stating that the classic CM is discontinued, with a clear redirection to the new CM documentation.
I think it's fine, unless consumer landed here from another documentation redirection.

@jschrap
Thank you for your feedback! I have this tutorial in my May backlog to update along with some other connection monitor articles.
#reassign:halkazwini
#please-close


Rename "Person" to "Guest"

Currently, the following components have been completed.

Model
testutil

Pull Request Test Coverage Report for Build 194

75 of 77 (97.4%)  changed or added relevant lines in 20 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 85.193%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/main/java/seedu/address/model/AddressBook.java
10
11
90.91%

src/main/java/seedu/address/model/util/SampleDataUtil.java
2
3
66.67%

Totals

Change from base Build 191:
0.0%

Covered Lines:
2077

Relevant Lines:
2438

💛  - Coveralls


Vue Typescript PropType not validating props

Version
3.0.11
Reproduction link
https://codesandbox.io/s/vue3-ts-proptype-ejt5f
Steps to reproduce
Open the sandbox, see no warning in the console about the msg prop
What is expected?
The prop msg is defined as String as PropType<'test' | 'trolley'>.
When we pass a different value than the ones in the enum, vue should display a warning in the console.
What is actually happening?
No console warning displayed.

I tried to make the validation work on vscode with Vetur extension but it was not warning me about invalid props.
While trying to debug it, I saw that vue was not detecting the invalid props either with PropType

Looks like an eslint parse error

Runtime validation requires validate. IDE validation can be achieved with VS code extensions like Volar and Vetur but it's not something that can be addressed in Vue Core