proxyRes.on('data', function) does not work.

I'm trying to grab body from response before send it to client. But it seems socket ( .on(...) ) function is not executed. However, the response is sent to client successfully.
Did I miss anything or did anything wrong ?

It does... data is in a stream. you have to parse it.

Does anyone know how to return custom response in res object based on proxyRes, but do not copy the data directly from res object?
The question from stackoverflow: https://stackoverflow.com/questions/54005345/custom-response-with-http-proxy-middleware-package
Need help with that :)

Seems that this is not working for us on windows, but it works on mac...
same node version
same module versions..
Mac - proxyRes.on('data' fires the callback
on windows, it just doesn't fire
the client(browser) does not receive any response data...

we still get a status 200 and response headers....
@taweesoft @nahushf make sure you are setting selfHandleResponse: true

same as "the client(browser) does not receive any response data".

I am having a similar issue, but it only happens on every second request that proxyRes.on('data', data => {}); does not fire. end always fires however.  50% of the time it works fine. There is no such issue when hitting the proxied end point directly.

It does... data is in a stream. you have to parse it.

Heres a quick copy pasta:
      const apiProxy = createProxyMiddleware("/api", {
        logLevel: "debug",
        target: "http://localhost:3020",
        onProxyRes: (proxyRes, req, res) => {
          proxyRes.on("data", (data) => {
            console.log("received data as stream");
            const bufferAsString = data.toString("utf-8");
            console.log(bufferAsString);
          });
        },
      });

It does... data is in a stream. you have to parse it.

Heres a quick copy pasta:
      const apiProxy = createProxyMiddleware("/api", {
        logLevel: "debug",
        target: "http://localhost:3020",
        onProxyRes: (proxyRes, req, res) => {
          proxyRes.on("data", (data) => {
            console.log("received data as stream");
            const bufferAsString = data.toString("utf-8");
            console.log(bufferAsString);
          });
        },
      });

responseInterceptor might help:
https://github.com/chimurai/http-proxy-middleware/blob/master/recipes/response-interceptor.md


Error 500 repeatedly on map

Wiped out my local repo due to some problems after upgrading from 1.4.3 to 1.5.0 now everything is working great except - when a user logs in and goes to the map page, they get logged out again right away with an Error 500.
My Pathfinder error logs aren't showing anything about it but the Apache2 error.log shows the following:
[Tue Mar 12 20:56:59.116829 2019] [php7:notice] [pid 16997] [client xxx.xxx.xxx.xxx:3287] mkdir(): Permission denied, referer: https://pathfinder.example.com/map/MTI%3D [Tue Mar 12 20:56:59.116870 2019] [php7:notice] [pid 16997] [client xxx.xxx.xxx.xxx:3287] [vendor/league/flysystem/src/Adapter/Local.php:375] mkdir(), referer: https://pathfinder.example.com/map/MTI%3D [Tue Mar 12 20:56:59.116875 2019] [php7:notice] [pid 16997] [client xxx.xxx.xxx.xxx:3287] [vendor/league/flysystem/src/Filesystem.php:262] League\\Flysystem\\Adapter\\Local->createDir(), referer: https://pathfinder.example.com/map/MTI%3D [Tue Mar 12 20:56:59.116878 2019] [php7:notice] [pid 16997] [client xxx.xxx.xxx.xxx:3287] [vendor/cache/filesystem-adapter/FilesystemCachePool.php:47] League\\Flysystem\\Filesystem->createDir(), referer: https://pathfinder.example.com/map/MTI%3D [Tue Mar 12 20:56:59.116881 2019] [php7:notice] [pid 16997] [client xxx.xxx.xxx.xxx:3287] [app/main/lib/api/AbstractClient.php:156] Cache\\Adapter\\Filesystem\\FilesystemCachePool->__construct(), referer: https://pathfinder.example.com/map/MTI%3D [Tue Mar 12 20:56:59.116884 2019] [php7:notice] [pid 16997] [client xxx.xxx.xxx.xxx:3287] [vendor/exodus4d/pathfinder_esi/app/Client/AbstractApi.php:737] lib\\api\\AbstractClient->lib\\api\\{closure}(), referer: https://pathfinder.example.com/map/MTI%3D [Tue Mar 12 20:56:59.116887 2019] [php7:notice] [pid 16997] [client xxx.xxx.xxx.xxx:3287] [vendor/exodus4d/pathfinder_esi/app/Client/AbstractApi.php:726] Exodus4D\\ESI\\Client\\AbstractApi->getCacheMiddlewareStorage(), referer: https://pathfinder.example.com/map/MTI%3D [Tue Mar 12 20:56:59.116891 2019] [php7:notice] [pid 16997] [client xxx.xxx.xxx.xxx:3287] [vendor/exodus4d/pathfinder_esi/app/Client/AbstractApi.php:682] Exodus4D\\ESI\\Client\\AbstractApi->getCacheMiddlewareStrategy(), referer: https://pathfinder.example.com/map/MTI%3D [Tue Mar 12 20:56:59.116894 2019] [php7:notice] [pid 16997] [client xxx.xxx.xxx.xxx:3287] [vendor/exodus4d/pathfinder_esi/app/Client/AbstractCcp.php:22] Exodus4D\\ESI\\Client\\AbstractApi->initStack(), referer: https://pathfinder.example.com/map/MTI%3D [Tue Mar 12 20:56:59.116897 2019] [php7:notice] [pid 16997] [client xxx.xxx.xxx.xxx:3287] [vendor/exodus4d/pathfinder_esi/app/Client/AbstractApi.php:634] Exodus4D\\ESI\\Client\\AbstractCcp->initStack(), referer: https://pathfinder.example.com/map/MTI%3D [Tue Mar 12 20:56:59.116900 2019] [php7:notice] [pid 16997] [client xxx.xxx.xxx.xxx:3287] [vendor/exodus4d/pathfinder_esi/app/Lib/WebClient.php:51] Exodus4D\\ESI\\Client\\AbstractApi->Exodus4D\\ESI\\Client\\{closure}(), referer: https://pathfinder.example.com/map/MTI%3D [Tue Mar 12 20:56:59.116903 2019] [php7:notice] [pid 16997] [client xxx.xxx.xxx.xxx:3287] [vendor/exodus4d/pathfinder_esi/app/Client/AbstractApi.php:635] Exodus4D\\ESI\\Lib\\WebClient->__construct(), referer: https://pathfinder.example.com/map/MTI%3D [Tue Mar 12 20:56:59.116906 2019] [php7:notice] [pid 16997] [client xxx.xxx.xxx.xxx:3287] [vendor/exodus4d/pathfinder_esi/app/Client/AbstractApi.php:304] Exodus4D\\ESI\\Client\\AbstractApi->initClient(), referer: https://pathfinder.example.com/map/MTI%3D [Tue Mar 12 20:56:59.116909 2019] [php7:notice] [pid 16997] [client xxx.xxx.xxx.xxx:3287] [vendor/exodus4d/pathfinder_esi/app/Client/AbstractApi.php:793] Exodus4D\\ESI\\Client\\AbstractApi->getClient(), referer: https://pathfinder.example.com/map/MTI%3D [Tue Mar 12 20:56:59.116912 2019] [php7:notice] [pid 16997] [client xxx.xxx.xxx.xxx:3287] [vendor/exodus4d/pathfinder_esi/app/Client/ESI.php:175] Exodus4D\\ESI\\Client\\AbstractApi->request(), referer: https://pathfinder.example.com/map/MTI%3D [Tue Mar 12 20:56:59.116914 2019] [php7:notice] [pid 16997] [client xxx.xxx.xxx.xxx:3287] [app/main/controller/api/map.php:882] Model\\CharacterModel->updateLog(), referer: https://pathfinder.example.com/map/MTI%3D [Tue Mar 12 20:56:59.116927 2019] [php7:notice] [pid 16997] [client xxx.xxx.xxx.xxx:3287] [index.php:20] Base->run(), referer: https://pathfinder.example.com/map/MTI%3D

Looking at the stack trace, pathfinder_esi is failing to create a log directory due to a permissions denied error.
Make sure both your log and cache directories exist, and that they're writable by the webserver.

Both directories are there, both directories have permissions and were not touched after the upgrade, where they working fine prior.

I had this issue and discovered that there's a missing instruction, in the root of your main pathfinder install, create a cache directory:
drwxr-xr-x  2 http http  4096 Feb 20 14:34 cache
This is in addition to the one that is in DOCROOT/tmp/cache

That did the trick, thank you dude!

@TrinityErik Thanks for your report! I fixed the bug in 346209d . You can either wait for the next release, or replace the changed lines.
Problem
The cache backend set in config.ini → API_CACHE is used as cache backend in pathfinder_esi API client. The default value folder=tmp/cache/ defines a filesystem based cache backend. Unfortunately there is a default dir used (created) named 'cache' if no folder is provided. Switching to the correct dir tmp/cache/ afterwards still remains with the default 'cache' dir.


WaletConnect doesn't work for certain TX Signing, build 3.14(370) #2462

Fixes #2462

@hboon should be ok, tested with https://example.walletconnect.org/ worked for me fine.

@hboon should be ok, tested with https://example.walletconnect.org/ worked for me fine.

Forced pushed to fix typo in commit message (important because might not be able to find "WalletConnect" otherwise)

Forced pushed to fix typo in commit message (important because might not be able to find "WalletConnect" otherwise)

From https://github.com/AlphaWallet/alpha-wallet-ios/issues/2462#issuecomment-762837760:

and it appears because we cconnect to stored walletConnect sessions but we don't save urlToServer

But this only fixes the problem after the app is restarted, right?
I can't reproduce the issue with https://example.walletconnect.org/ if I don't restart the app even without applying the PR:
i.e

Don't apply PR
Connect
Don't restart app
Sign typed data
It works

From https://github.com/AlphaWallet/alpha-wallet-ios/issues/2462#issuecomment-762837760:

and it appears because we cconnect to stored walletConnect sessions but we don't save urlToServer

But this only fixes the problem after the app is restarted, right?
I can't reproduce the issue with https://example.walletconnect.org/ if I don't restart the app even without applying the PR:
i.e

Don't apply PR
Connect
Don't restart app
Sign typed data
It works

From #2462 (comment):

and it appears because we cconnect to stored walletConnect sessions but we don't save urlToServer

But this only fixes the problem after the app is restarted, right?
I can't reproduce the issue with https://example.walletconnect.org/ if I don't restart the app even without applying the PR:
i.e

Don't apply PR
Connect
Don't restart app
Sign typed data
It works

Does the build you tested already support the new EIP712?
I just tested it again using the testflight build 3.14(370). I can reproduce it
https://share.icloud.com/photos/0ViCFpAeE927zvs3KtlKM5dUw

From #2462 (comment):

and it appears because we cconnect to stored walletConnect sessions but we don't save urlToServer

But this only fixes the problem after the app is restarted, right?
I can't reproduce the issue with https://example.walletconnect.org/ if I don't restart the app even without applying the PR:
i.e

Don't apply PR
Connect
Don't restart app
Sign typed data
It works

Does the build you tested already support the new EIP712?
I just tested it again using the testflight build 3.14(370). I can reproduce it
https://share.icloud.com/photos/0ViCFpAeE927zvs3KtlKM5dUw

I just tested it again using the testflight build 3.14(370). I can reproduce it

I was wrong. I can reproduce it now.

I just tested it again using the testflight build 3.14(370). I can reproduce it

I was wrong. I can reproduce it now.

But this only fixes the problem after the app is restarted, right?

seems like yes, i was able to reproduce error only while switching between wallets, but its another issue.

But this only fixes the problem after the app is restarted, right?

seems like yes, i was able to reproduce error only while switching between wallets, but its another issue.

I was wrong. I can reproduce it now.

@hboon can u tell me eexact steps to reproduce this? i followed these steps:
Don't apply PR
Connect
Don't restart app
Sign typed data
It works

I was wrong. I can reproduce it now.

@hboon can u tell me eexact steps to reproduce this? i followed these steps:
Don't apply PR
Connect
Don't restart app
Sign typed data
It works

I was wrong.  It might have been fixed prior to this PR.

I was wrong.  It might have been fixed prior to this PR.

I was wrong.  It might have been fixed prior to this PR. Look for a commit around 8 jan.

i mean that i can't reproduce it with changes maded in #2469 (maybe i do something wrong)

I was wrong.  It might have been fixed prior to this PR. Look for a commit around 8 jan.

i mean that i can't reproduce it with changes maded in #2469 (maybe i do something wrong)

@hboon could this happens because instead of receiving eth_signTypedData we receive eth_signTypedData_v3?

@hboon could this happens because instead of receiving eth_signTypedData we receive eth_signTypedData_v3?

Oh I think I confused you with my remark earlier. Let me try again. I believe this is true:

I can now reproduce it if I checkout the commit around 8 Jan (I thought I couldn’t previously)
I think it’s already fixed in master
I can reproduce it after this PR is applied too

So if you can’t reproduce this anymore, it’s good :)

Oh I think I confused you with my remark earlier. Let me try again. I believe this is true:

I can now reproduce it if I checkout the commit around 8 Jan (I thought I couldn’t previously)
I think it’s already fixed in master
I can reproduce it after this PR is applied too

So if you can’t reproduce this anymore, it’s good :)


mistune 2.0.4 doesn't work in IronPython 2.7

Hello,
I'm trying to use mistune in a python script that runs in IronPython 2.7.
When I try to run it, I get this error:
\mistune\scanner.py", line 3, in <module>
AttributeError: 'module' object has no attribute 'Scanner'

Somehow, it cannot find re.Scanner.
I have to put the source code of the library right next to the script, because in the end, the script will be running on a server with IronPython where it is not possible to install additional packages.

There is no claim that mistune support IronPython


Adhere to semver rules when using workspace:^ dependencies, fixes #1290

This fixes #1290.
I've adjusted the tests, and also ran my local code against the backstage repository.
On my current version, the main version updates some 200 packages, and with my patch it goes down to some 90.
CC @Rugvip , @freben from that side.
PS: I went for a major release of all affected packages, as this is breaking backwards compat. yarn changeset status gives me:
🦋  info NO packages to be bumped at patch
🦋  ---
🦋  info NO packages to be bumped at minor
🦋  ---
🦋  info Packages to be bumped at major:
🦋  info
🦋  - @changesets/assemble-release-plan
🦋  - @changesets/cli
🦋  - @changesets/get-release-plan

I started to dabble into the ~ part, and then got stuck in a rabbit hole.
I think the culprit here are pre-releases, which is going to limit the impact this can have for projects like backstage:
> semverSatisfies('1.0.1','~1.0.0')
true
> semverSatisfies('1.0.1-alpha.0','~1.0.0')
false
> semverSatisfies('1.0.1-alpha.0','^1.0.0')
false

This goes back to https://github.com/npm/node-semver?tab=readme-ov-file#prerelease-tags, which reads in backstage lingo: If we bump @backstage/core-plugin-api in a pre-release, we need to also ship a pre-release version of @backstage/plugin-todo, which references that core package with the specific pre-release version.
More details on why that also then affects the non-pre releases is in Emma's comment in https://github.com/changesets/changesets/pull/382#discussion_r434434182.

Another possible workaround, until Changesets code owners review the pull request, can be to patch (via PNPM if it's your default package manager or the patch-package module<EMAIL_ADDRESS>dependency with @Pike proposed fix (thanks to him).
Patching is working well confirming the issue fix 🎉 .
I hope this workaround can unblock projects while not rushing @Andarist and the Changesets team 👍 .

@adbayb indeed, we'll try it out and see how it works: https://github.com/backstage/backstage/pull/24614. In particular, I expect this to improve our patch release process where we currently see too many package bumps.

I think this fix is already good enough to unblock the vast majority of cases with "workspace:" protocol. Even without a proper support of ~, support workspace caret range is already a big improvement.
@Andarist could you take a look at this PR and prioritize it?


Casmuser 2912 release 2.1 - Fix dependent role sourcing

Summary and Scope
This PR corrects the issue where UAN release builds were pulling supporting content from dev/master branches instead of from release branches.
It also brings in the kdump support from the stash repo to github for UAN.
Issues and Related PRs

Resolves CASMUSER-2912

Testing
Tested on:
Will be tested on:

baldar

Test description:
Will install unstable artifacts and will verify the build functioned and contained the correct versions after this PR build completes.

Were the install/upgrade-based validation checks/tests run (goss tests/install-validation doc)?  Yes
Were continuous integration tests run? If not, why? Yes
Was upgrade tested? If not, why? Yes
Was downgrade tested? If not, why? No
Were new tests (or test issues/Jiras) created for this change? No

Risks and Mitigations
Roles from other products are now release versions which should be what we want but have not been in the past.
Pull Request Checklist

[ X] Version number(s) incremented, if applicable
[ X] Copyrights updated
[ X] License file intact
[X ] Target branch correct
[ ] CHANGELOG.md updated
[ ] Testing is appropriate and complete, if applicable
[ ] HPC Product Announcement prepared, if applicable

The PR build for this had a some snyk scan failures coming from the base layer cray-ims-load-artifacts:1.3.6
https://app.snyk.io/org/shasta-csm-oss/project/ee0975ff-b1e8-4df9-98ee-9df236fc20a3/history/a2e3571e-63eb-41b3-9309-96e62712ff8c
I suggest updating to the latest ims 1.3 version which would be 1.3.56:
https://artifactory.algol60.net/ui/repos/tree/General/csm-docker%2Fstable%2Fcray-ims-load-artifacts%2F1.3.56
That would be a change to runBuildPrep-image-recipe.sh


Support APQs (automated-persisted queries) in Android

Feature request:
Support APQs (automated-persisted queries) in Android client - as only GET will be supported for CDN caching (e.g. Akamai, Centurylink etc...)

+1 plsss

Just for the reference: we have feature persisted queries but it not automatic. The hash of the query is static, generated at build time, the previous idea was that this mapping of hash to query collected from the client ant stored on the server side at compile time.
In order to support automatic persisted query we can reuse the hash that we are currently generating:
https://github.com/apollographql/apollo-android/blob/master/apollo-compiler/src/test/graphql/com/example/hero_name/TestQuery.java#L30
Couple links for the ref:
https://github.com/apollographql/apollo-link-persisted-queries#protocol
https://blog.apollographql.com/persisted-graphql-queries-with-apollo-client-119fd7e6bba5
https://blog.apollographql.com/automatic-persisted-queries-and-cdn-caching-with-apollo-server-2-0-bf42b3a313de

How to change the client to use GET http?

right now we can't, it's a new future to be added.

I have started adding it here:
https://github.com/toby78/apollo-android/blob/persisted_queries/apollo-runtime/src/main/java/com/apollographql/apollo/internal/interceptor/ApolloServerInterceptor.java
...due to lack of time this can take a while. I already added a testcase with variables.

hi  is there any example to use http GET with persisted Queries?
I have already .enableAutoPersistedQueries(true)  but the request is still http POST


Bug in Match The Time part of Tell the Time Android App

I get the same score in both the cases where I correctly match the time in all problems and where I don't match any of them.
Here you can see a video explaining this.

Hey.
Has this issue been resolved or does it still persist?

Can I PR for this issue?


Broadcast Error

[error] [object Object]
{ code: 'ERROR', error: 'Error querying the blockchain' }
Tx made, signed but can't be broadcasted.

testnet or livenet?

livenet; And I'm really in a bind. We have a lot of coins 'locked' because the txs won't broadcast. It's a multisig HD Wallet with 3/4. 3 of 4 signed it but none of us can broadcast. 2 of them are using the mobile copay wallet.

you are using a custom script to broadcast the transaction?  Are you using
the public BWS instance or your own?
On Tue, Nov 10, 2015 at 10:35 AM, Jeremy<EMAIL_ADDRESS>wrote:

livenet; And I'm really in a bind. We have a lot of coins 'locked' because
the txs won't broadcast. It's a multisig HD Wallet with 3/4. 3 of 4 signed
it but none of us can broadcast. 2 of them are using the mobile copay
wallet.
—
Reply to this email directly or view it on GitHub
https://github.com/bitpay/bitcore-wallet-client/issues/176#issuecomment-155420375
.

--
Matías Alejo Garcia
@ematiu
Roads? Where we're going, we don't need roads!

We are using the bitcore wallet client. the command-line client made the txs and in one case it failed to broadcast. Other txs were sent to and signed on the copay wallets.

Sorry, I am not sure I understand the problem.
Is the problem persist? Do you still have a transaction that wont
broadcast? The error you are getting when you try to broadcast is ''Error
querying the blockchain'?
Can you delete the TX and create a new one?
On Tue, Nov 10, 2015 at 10:44 AM, Jeremy<EMAIL_ADDRESS>wrote:

We are using the bitcore wallet client. the command-line client made the
txs and in one case it failed to broadcast. Other txs were sent to and
signed on the copay wallets.
—
Reply to this email directly or view it on GitHub
https://github.com/bitpay/bitcore-wallet-client/issues/176#issuecomment-155422612
.

--
Matías Alejo Garcia
@ematiu
Roads? Where we're going, we don't need roads!

Yes, 'Error querying the blockchain' is the error I get. I made a tx: wallet -f mywallet.dat send.... Then I signed, wallet -f mywallet.dat signed f343. Then other wallets signed, but then none of us could broadcast. On a different wallet where i was the only needed signature, I made, signed and tried to broadcast the tx, but it would broadcast. In this case, I was able to rm the tx and remake it and broadcast. But on the 3/4 account the funds are locked and none of us can broadcast or rm the tx. The problem persists.

I have the same issue , I have a tx that is not broadcasting and there is no option to delete it .

I have the same issue , I have a tx that is not broadcasting and there is no option to delete it .

I had to wait 24 hours to delete the transaction and free the bitcoin in the wallet. The issue might have been related to everyone using copay on different devices and having different version numbers, I'm not sure. I have switched to bitgo since.

Same issue here. So cancel the transaction requires 24 hours and one has to rely on mere hope?

Boradcasting error is normally because tx's inputs were spent in other tx.
In multisig wallets, The creator of the tx can remove it at any time and
the others need to wait 24hrs.
In single sig wallets, it can be deleted any time.
The restriction it to give time to copayers to sign the tx.
On Fri, Jan 22, 2016 at 6:50 PM David<EMAIL_ADDRESS>wrote:

Same issue here. So cancel the transaction requires 24 hours and one has
to rely on mere hope?
—
Reply to this email directly or view it on GitHub
https://github.com/bitpay/bitcore-wallet-client/issues/176#issuecomment-174063908
.

I've come across this same issue. I've got a test wallet with a single used address: https://insight.getsumbits.com/address/14W9HYbHiWxHyLACe6jTnbSZdEDceGVKRu (obviously running our own BitCore suite).
I'm writing a small Node.js application to act as a proxy to BWS for a specific wallet.dat. Here is the code I have.
app.post('/send/:address', function(req, res) {
	amount = Math.floor(parseFloat(req.query.amount) * Math.pow(10, 8));
	client.sendTxProposal({
		toAddress: req.params.address,
		amount: amount,
		message: req.query.description
	}, function(err, tx) {
		if (err) {
			res.json({error: err.message});
		} else {
			client.signTxProposal(tx, function(err, tx) {
				if (err) {
					res.json({error: err.message});
				} else {
					console.log(tx);
					client.broadcastTxProposal(tx, function(err, tx) {
						if (err) {
							res.json({error: err.message});
						} else {
							res.json(tx);
						}
					});
				}
			});
		}
	});
});

It successfully signs the transaction, but when it goes to broadcast it, the response it gets is "Error querying the blockchain".
The only related log I have from BitCore is the following:
ERR! /v1/txproposals/01453878781515c8970868-288d-479d-ad30-8e7efb642a24/broadcast/ :500:Error querying the blockchain ```

Chris in your case it just means that insight is not yet available.
Probably insight did not end
syncing the block chain. Check curl -v http://localhost:3001/insight-api/sync or status. In the Insight-api
readme are more details.
On Wed, Jan 27, 2016 at 4:20 AM, Chris Rico<EMAIL_ADDRESS>wrote:

I've come across this same issue. I've got a test wallet with a single
used address:
https://insight.getsumbits.com/address/14W9HYbHiWxHyLACe6jTnbSZdEDceGVKRu
(obviously running our own BitCore suite).
I'm writing a small Node.js application to act as a proxy to BWS for a
specific wallet.dat. Here is the code I have.
app.post('/send/:address', function(req, res) {
amount = Math.floor(parseFloat(req.query.amount) * Math.pow(10, 8));
client.sendTxProposal({
toAddress: req.params.address,
amount: amount,
message: req.query.description
}, function(err, tx) {
if (err) {
res.json({error: err.message});
} else {
client.signTxProposal(tx, function(err, tx) {
if (err) {
res.json({error: err.message});
} else {
console.log(tx);
client.broadcastTxProposal(tx, function(err, tx) {
if (err) {
res.json({error: err.message});
} else {
res.json(tx);
}
});
}
});
}
});
});
It successfully signs the transaction, but when it goes to broadcast it,
the response it gets is "Error querying the blockchain".
The only related log I have from BitCore is the following:
WARN Insight http://localhost:3001/insight-api/tx/send Returned Status:
503
ERR!
/v1/txproposals/01453878781515c8970868-288d-479d-ad30-8e7efb642a24/broadcast/
:500:Error querying the blockchain
—
Reply to this email directly or view it on GitHub
https://github.com/bitpay/bitcore-wallet-client/issues/176#issuecomment-175459192
.

--
Matías Alejo Garcia
@ematiu
Roads? Where we're going, we don't need roads!

Hi Matias. Our insight is working fine otherwise and lets me create and
sign the transaction. https://insight.getsumbits.com
To clarify, the log messages with localhost in them are from the bitcored
server. The code is running on another server.
On Jan 27, 2016 5:07 AM, "Matias Alejo Garcia"<EMAIL_ADDRESS>wrote:

Chris in your case it just means that insight is not yet available.
Probably insight did not end
syncing the block chain. Check curl -v http://localhost:3001/insight-api/sync
http://localhost:3001/insight-api/sync or status. In the Insight-api
readme are more details.
On Wed, Jan 27, 2016 at 4:20 AM, Chris Rico<EMAIL_ADDRESS>wrote:

I've come across this same issue. I've got a test wallet with a single
used address:

https://insight.getsumbits.com/address/14W9HYbHiWxHyLACe6jTnbSZdEDceGVKRu

(obviously running our own BitCore suite).
I'm writing a small Node.js application to act as a proxy to BWS for a
specific wallet.dat. Here is the code I have.
app.post('/send/:address', function(req, res) {
amount = Math.floor(parseFloat(req.query.amount) * Math.pow(10, 8));
client.sendTxProposal({
toAddress: req.params.address,
amount: amount,
message: req.query.description
}, function(err, tx) {
if (err) {
res.json({error: err.message});
} else {
client.signTxProposal(tx, function(err, tx) {
if (err) {
res.json({error: err.message});
} else {
console.log(tx);
client.broadcastTxProposal(tx, function(err, tx) {
if (err) {
res.json({error: err.message});
} else {
res.json(tx);
}
});
}
});
}
});
});
It successfully signs the transaction, but when it goes to broadcast it,
the response it gets is "Error querying the blockchain".
The only related log I have from BitCore is the following:
WARN Insight http://localhost:3001/insight-api/tx/send Returned Status:
503
ERR!

/v1/txproposals/01453878781515c8970868-288d-479d-ad30-8e7efb642a24/broadcast/

:500:Error querying the blockchain
—
Reply to this email directly or view it on GitHub
<
https://github.com/bitpay/bitcore-wallet-client/issues/176#issuecomment-175459192
.

--
Matías Alejo Garcia
@ematiu
Roads? Where we're going, we don't need roads!
—
Reply to this email directly or view it on GitHub
https://github.com/bitpay/bitcore-wallet-client/issues/176#issuecomment-175563174
.

Could you try again just in case?
Note that signing / creating does not depends on insight, but only on BWS
On Wed, Jan 27, 2016 at 11:14 AM, Chris Rico<EMAIL_ADDRESS>wrote:

Hi Matias. Our insight is working fine otherwise and lets me create and
sign the transaction. https://insight.getsumbits.com
To clarify, the log messages with localhost in them are from the bitcored
server. The code is running on another server.
On Jan 27, 2016 5:07 AM, "Matias Alejo Garcia"<EMAIL_ADDRESS>wrote:

Chris in your case it just means that insight is not yet available.
Probably insight did not end
syncing the block chain. Check curl -v http://localhost:3001/insight-api/sync
http://localhost:3001/insight-api/sync
http://localhost:3001/insight-api/sync or status. In the Insight-api
readme are more details.
On Wed, Jan 27, 2016 at 4:20 AM, Chris Rico<EMAIL_ADDRESS>wrote:

I've come across this same issue. I've got a test wallet with a single
used address:

https://insight.getsumbits.com/address/14W9HYbHiWxHyLACe6jTnbSZdEDceGVKRu

(obviously running our own BitCore suite).
I'm writing a small Node.js application to act as a proxy to BWS for a
specific wallet.dat. Here is the code I have.
app.post('/send/:address', function(req, res) {
amount = Math.floor(parseFloat(req.query.amount) * Math.pow(10, 8));
client.sendTxProposal({
toAddress: req.params.address,
amount: amount,
message: req.query.description
}, function(err, tx) {
if (err) {
res.json({error: err.message});
} else {
client.signTxProposal(tx, function(err, tx) {
if (err) {
res.json({error: err.message});
} else {
console.log(tx);
client.broadcastTxProposal(tx, function(err, tx) {
if (err) {
res.json({error: err.message});
} else {
res.json(tx);
}
});
}
});
}
});
});
It successfully signs the transaction, but when it goes to broadcast
it,
the response it gets is "Error querying the blockchain".
The only related log I have from BitCore is the following:
WARN Insight http://localhost:3001/insight-api/tx/send Returned
Status:
503
ERR!

/v1/txproposals/01453878781515c8970868-288d-479d-ad30-8e7efb642a24/broadcast/

:500:Error querying the blockchain
—
Reply to this email directly or view it on GitHub
<

https://github.com/bitpay/bitcore-wallet-client/issues/176#issuecomment-175459192

.

--
Matías Alejo Garcia
@ematiu
Roads? Where we're going, we don't need roads!
—
Reply to this email directly or view it on GitHub
<
https://github.com/bitpay/bitcore-wallet-client/issues/176#issuecomment-175563174
.

—
Reply to this email directly or view it on GitHub
https://github.com/bitpay/bitcore-wallet-client/issues/176#issuecomment-175651899
.

--
Matías Alejo Garcia
@ematiu
Roads? Where we're going, we don't need roads!

Still getting the same result. Note these lines from the bitcored log:
ERR! /v1/txproposals/01453904381955797c5282-3b99-46ae-9612-d8d7fc0e7bd4/broadcast/ :500:Error querying the blockchain```

Doesn't creating the transaction depend on Insight? If not, how else does it gather the unspent outputs for the wallet? Let me post all of the code I'm using so that you have a beter ide

@matiu I just registered this wallet with https://bws.bitpay.com/bws/api and I'm getting the same error when trying to broadcast the transaction. Even using the bitcore-wallet command line utility against your server, I get the same error.
[error] [object Object]
{ code: 'ERROR', error: 'Error querying the blockchain' }```

At the time the TX was reject, we have these logs in bitcoind:

2016-01-27 19:16:39 ERROR: AcceptToMemoryPool: free transaction rejected by
rate limiter

2016-01-27 19:16:46 ERROR: AcceptToMemoryPool: nonstandard transaction: dust

does this sounds like your TX?
On Wed, Jan 27, 2016 at 4:18 PM, Chris Rico<EMAIL_ADDRESS>wrote:

@matiu https://github.com/matiu I just registered this wallet with
https://bws.bitpay.com/bws/api and I'm getting the same error when trying
to broadcast the transaction. Even using the bitcore-wallet command line
utility against your server, I get the same error.
$ ./wallet broadcast 239a
[error] [object Object]
{ code: 'ERROR', error: 'Error querying the blockchain' }
—
Reply to this email directly or view it on GitHub
https://github.com/bitpay/bitcore-wallet-client/issues/176#issuecomment-175806322
.

--
Matías Alejo Garcia
@ematiu
Roads? Where we're going, we don't need roads!

Possibly? The address has a balance of 0.0001 BTC and I was trying to send 1/10 of that. I just tried again sending 0.00005 BTC and I got the same error. Is that under the dust limit?

dust limit is 5430 or 540 satoshis, depending the version. Could you try a
higher value just in case?
On Wed, Jan 27, 2016 at 4:37 PM, Chris Rico<EMAIL_ADDRESS>wrote:

Possibly? The address has a balance of 0.0001 BTC and I was trying to send
1/10 of that. I just tried again sending 0.00005 BTC and I got the same
error. Is that under the dust limit?
—
Reply to this email directly or view it on GitHub
https://github.com/bitpay/bitcore-wallet-client/issues/176#issuecomment-175814810
.

--
Matías Alejo Garcia
@ematiu
Roads? Where we're going, we don't need roads!

Ah hah! I realize what the problem was. The balance was 0.0001 BTC. There was a very small sweet spot of bits I could send without either the spending or change outputs being considered dust. I ended up sending 7420 with a fee of 2580 (no change).


Fixing error on windows clients (unable to create puppetlabs.txt in facts.d)

Windows clients run in to trouble with the linux paths for the puppetlabs.txt. This if/else flow adds the windows support, so that the puppetlabs.txt will also be created in the propper directory on windows nodes. This has been tested on Windows 2008r2.

Thanks! I'm going to rework this a little bit to put it into the params class. Thanks for catching this!


WHY AndroidHandlerMainThreadSupport.isMainThread() use Looper.myLooper() but not Looper.getMainLooper() ?

If invoke this method in a sub-thread, say a HandlerThread, it will return a wrong result.
Use Looper.getMainLooper() is correct, right?

Look at how it is constructed:
https://github.com/greenrobot/EventBus/blob/3670d97835f15d0966e29fb8f52785ca3e87c2af/EventBus/src/org/greenrobot/eventbus/EventBusBuilder.java#L168-L187
looper will be the main looper.
Closing. Please re-open if your question was not answered.
-ut


👋 Examples/Demo App

An examples app would be a great addition to the project.

quickly review what the package can offer
quickly test if allows certain levels of customization
allow for more images/screenshots in README.md

Thank you for the suggestion!
Adding an examples app is indeed a great idea.
In the meantime, users can check out the Wiki page for some examples and previews until the demo project is ready.

I've added a sample project to the repository: MaterialUIKit Sample Project. For more examples and previews, check the wiki.


Forbid users with the ID of the empty string or all whitespace

The empty string is a valid username right now.  Probably newlines are too.

What we should do is replace internal newlines, the same way String::from_utf8_lossy does:

U+FFFD REPLACEMENT CHARACTER, which looks like this: �

If they want to pass us usernames with internal spaces, or leading/trailing spaces, it won't break the database.  A newline will.

Ditto the empty string.  This is an application-level policy.

This is a breaking change, because it maps previously valid (but stupid) usernames to similar usernames destructively, and it hides the fact that it's doing it.  If someone somehow already has as user with a "\n" in their username and another user with a "\u{FFFD}" in their username and the names are otherwise identical, then things could go wrong.  I'm not too stressed about that.


Animate part of the number

is there a way to animate the number (e.g 111 => 112) so only last 1 becomes 2 instead of animating the whole number, because it doesn't make sense to animate numbers if they are not going to be changed.
is there a way to do that?

pls use react-awesome-animated-number

@heyman333, can we get this please.

I think this can be done by changing line  70 from  key={${keyCount.current++}} to  key = {index}


docs: create ReferenceGrant documentation

Problem statement
After introducing support for Gateway v1 we seem to only have ReferenceGrant documented in the example: https://github.com/Kong/kubernetes-ingress-controller/blob/628fe6a585abb5b1cb49568c597fd68e319a2668/examples/gateway-referencegrant-httproute.yaml.
Acceptance criteria

[x] Gateway API's ReferenceGrant is documented in https://docs.konghq.com/kubernetes-ingress-controller/latest/

Done: https://github.com/Kong/docs.konghq.com/pull/6677


[Feature] Learning Rate Modified by Steps

I've experimented with a learning rate that changes as the steps increase due to seeing Aphantasia develop a general image very quickly, but then slowing down to make small details. I believe that my proposed alternative puts more focus on larger shapes, and less on details.
I expose the learning_rate variable and add a learning_rate_max variable in the Generate cell, remove the optimizer = torch.optim.Adam(params, learning_rate) line and instead add this to def train(i):
learning_rate_new = learning_rate + (i / steps) * (learning_rate_max - learning_rate)
optimizer_new = torch.optim.Adam(params, learning_rate_new)

With this, I find that a learning_rate of 0.0001 and a learning_rate_max of 0.008 at the highest value works well, for 300-400 steps and about 50 samples at least.

thanks for proposal, will check that! i did notice fancy behaviour of training details, but haven't performed so thorough tests.
the process for single image looked ok for me as is, but i had tough time struggling with multi-phrase continuous runs - the imagery tended to get stuck after 7-10 steps. meanwhile i resorted to weird tricks of mixed initialization + further interpolation; hopefully your approach may help there (since optimizer and params are recreated every cycle anyway).
i'll keep this open till further exploration.

@torridgristle i gave it a try, here is my findings:

your settings decrease "overpopulation" indeed, producing more sparse and less clogged look;
lower rate (0.003~0.004) seems to produce similar effect on its own, without progressive setup;
progressive decrease also gives quite interesting results (dense painting, better colors);
all above was observed on ViT model; i didn't notice any specific effect for RN101 yet.

i will add and expose progressive mode as an option (and change default lrate) anyway, to encourage further experiments.
please note also that:

learning rate of the optimizer can be changed on the fly without recreation, as following:

for g in optimizer.param_groups:
    g['lr'] = lr_init + (i / steps) * (lr_max - lr_init)

the generation is proceeded by patches/samples of random size (and position), and it's their size that directly affects size of painted features. so it may be worth changing that size progressively in slice_imgs function (@jonathanfly proposed that while ago, but i didn't dig into that).

further tests have shown that in most cases progressive lrate does have some impact on the composition. i would not call it "larger shapes enhancements" (sometimes it just drew significantly less elements of all kinds), but it's worth having in the options.
exact lrate values depend heavily on the model, prompts and (especially) the resolution: even 0.03~0.05 was not enough to cover the whole 4k frame in some cases (training up to 1000 steps and 256 samples). i also tested rates as big as 1~10, and they also have their interesting specifics (not explicitly generalizable as a common rule).

@torridgristle implemented and mentioned on readme. thanks for discovering; closing now.


Set maxdepth in find because we do not need all the files recursively

Codecov Report

Merging #14 (9213d91) into main (4a15645) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main      #14   +/-   ##
=======================================
  Coverage   83.43%   83.43%
=======================================
  Files           1        1
  Lines         332      332
=======================================
  Hits          277      277
  Misses         55       55

Impacted Files
Coverage Δ

rsync_time_machine.py
83.43% <100.00%> (ø)


Feature: Testing as an EOA

I am presently working with @captnseagraves on a project which uses EOA signatures to authorize operations. Is there presently a way to produce these signatures within foundry tests? If not, would be a useful feature.

Yes! Check out the cheatcodes listed in here particularly this one:
// Signs data, (privateKey, digest) => (v, r, s)
function sign(uint256,bytes32) external returns (uint8,bytes32,bytes32);

Yep as bjerg said that's the way.

is there a way to generate RLP encoding from (v, r, s) in tests to pass it to contracts that expects Ethereum signed message?

Yes, vm.sign cheatcode! https://book.getfoundry.sh/tutorials/testing-eip712?highlight=vm.sign#diving-in

@gakonst vm.sign is giving (v,r,s), doing bytes signature = abi.encodePacked(r, s, v) is not a valid RLP notation correct? https://ethereum.org/en/developers/docs/data-structures-and-encoding/rlp/

@gakonst I guess we don't have support to generate RLP from (v,r,s) yet. https://github.com/foundry-rs/foundry/issues/517#issuecomment-1252982917 vm.sign only providers (v,r,s) and not RLP encoded hex string https://ethereum.stackexchange.com/a/107498/18370


Error in New Front End Pool Step 6 and 7 (cannot be done in SQL 2017)

In the section Deploy an Always On Availability Group on an existing pool that does not use database mirroring Step 6 Create the availability group. The instructions say to create the AG.  However with SQL 2017 you cannot create an AG on a server with no databases.
In step 7: Use Topology Builder to create the Front End pool, as explained in Create and publish new topology in Skype for Business Server. When you do, specify the AG as the SQL store for the pool.  The AG is not an object in AD (I.E. no FQDN for an AG since an AG has not IP address).
So what I think you have to do is first create the database using no availability group setting, and using the primary server for the SQL server, then Build the database, then build the listener and then build then set the availability group setting in topology builder.

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

ID: 0c3f0aa8-8192-73c1-0b5d-acafc7bc0860
Version Independent ID: 39eeb704-22ec-0945-b02e-08d1ca5aee5a
Content: Deploy an Always On Availability Group on a Back End Server in Skype for Business Server
Content Source: Skype/SfbServer/deploy/deploy-high-availability-and-disaster-recovery/alwayson-availability-group.md
Product: skype-for-business-itpro
GitHub Login: @MicrosoftHeidi
Microsoft Alias: heidip

@youseeadam Thank you for this feedback
We appreciate you pointing this out to us and taking the time to help make the docs better. I will get this over to the Teams/Skype for Business team for investigation and updating.
I was able to get this into the backlog for the Teams/Skype for Business team. The team will get this prioritized into a sprint plan. Thank you for reporting and making the docs better. Much appreciated.
I made a note to request the team to update this when the work is complete.

@AndreaBarr Yeah~,I also found the issue said by @youseeadam .When  I gone to the end of step 8, the command "Install-CsDatabase -Update"could not work perfectly.Error message is "Install-CsDatabase : Parameter set cannot be resolved using the specified named parameters." Thanks

Hello @DriveHeart thanks for your feedback.
As I could not reproduce it, it will be better if you direct your inquiry to support resources https://support.microsoft.com/en-us/supportforbusiness/productselection
Thank you

@DriveHeart  - thank you for submitting feedback.
I think the best way forward is if you open a service ticket in your tenant so this can get resolved ASAP. Based on the outcome let me know if it is something that can be called out in the docs.
Please follow this link to contact support for business products:  https://docs.microsoft.com/office365/admin/contact-support-for-business-products
Please keep us posted here on the resolution so we can feed whatever information you discover into the content.

@officedocsbot close


Make upcoming Clippy 1.40 happy

The Clippy version shipped with the upcoming 1.40 release will have a few new complaints about our build scripts which this commit fixes.

Pull Request Test Coverage Report for Build 1261

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 95.184%

Totals

Change from base Build 1259:
0.0%

Covered Lines:
3182

Relevant Lines:
3343

💛  - Coveralls

bors: r+


Where to run the Powershell scripts?

Is the Meeting Migration Service (MMS) in

Azure
SharePoint On-Premises
Windows Computer on the domain network

It wonderful that this service exists yet this documentation assumes too much.  The related topic maybe
Connect PowerShell to Office 365 services
The question is which resource should one use in Office 365

Azure Active Directory      Connect to Office 365 PowerShell
Exchange Online      Connect to Exchange Online PowerShell
Security & Compliance Center      Connect to Office 365 Security & Compliance Center PowerShell
Skype for Business Online      Connecting to Skype for Business Online by using Windows PowerShell
SharePoint Online      Connect to SharePoint Online PowerShell

I am starting at Skype for Business Online. Grateful, if someone can verify that I'm on the right track.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 990ca74b-6bba-a14b-071a-d13adb723a4c
Version Independent ID: 52f55a58-30ce-c140-3ee7-8042b1d105f0
Content: Using the Meeting Migration Service (MMS)
Content Source: Skype/SfbOnline/audio-conferencing-in-office-365/setting-up-the-meeting-migration-service-mms.md
Service: skype-for-business-online
GitHub Login: @tonysmit
Microsoft Alias: tonysmit

@GrooveCS  - thank you for submitting feedback.
I think the best way forward is if you open a service ticket in your tenant so this can get resolved ASAP. Based on the outcome let me know if it is something that can be called out in the docs.
Please follow this link to contact support for business products:  https://docs.microsoft.com/office365/admin/contact-support-for-business-products
Please keep us posted here on the resolution so we can feed whatever information you discover into the content.

@officedocsbot close


Problem after upgrading xcode (6.3)

Hello,
I am getting this error when i want to run app on my iphone
dyld: Library not loaded: @rpath/SwiftHTTP.framework/SwiftHTTP
Referenced from: /private/var/mobile/Containers/Bundle/Application/42046EBB-DDED-4838-BA51-79601629B1F0/Powerlabel.app/Powerlabel
Reason: image not found

Sorry fixed it.

hi utku dalmaz how dit you fixed it ?


Code editor has padding on the right

For some reason, no characters are allowed after this red line, even though there is space for one or two more.

Seems like Boundary wrapping counts spaces as part of the words... So this seems more on Godot's side. For the time being, I'd rather not get too intense making my own  TextEdits or anything like that, so I'll just leave this open.


Consistent log keys across all runtimes

Is your feature request related to a problem? Please describe.

Python and Typescript use snake_case for all outputs.  Java uses a mix of snake_case and camel_case.
Customers will use the same tool (CloudWatch Logs, Loggly, Datadog, etc.) to search data across logs, and if main keys are different they will find half of the information when using multiple runtimes.
At the sametime, if we break language consistency and the other application(not using powertools but standard logging libs) loose that tracking on single visibility.
Considering both the above rationale, for now, we should standardize on the same key name (snake_case) for logging output - we, Golang will also using snake_case albeit in the early phase. As it’s a breaking change for Java, let’s strive for making it configurable but a v2 should standardize it on snake_case.
Describe the solution you'd like
Ability to configure if customers want consistent logging keys same as used in powertools logging for other runtimes.
Describe alternatives you've considered
None
Additional context

#1435


Reach out to users team to ask them about their search bar and see what we need to consolidate

We will be coordinating with the users team to discuss potentially making a consolidated search bar that works for searching both games and user accounts.

We've been coordinating with the user team to determine the best approach for a unified search feature.
@omarelkashef from the user team highlighted two main methods for implementing search and filtering:

Allowing users to filter results while searching, akin to the functionality on Rate Your Music and Board Game Geek.
Providing the option to search first and then apply filters, similar to what is done on Goodreads and Letterboxd.

During our discussions, we found the Board Game Geek's search implementation to be particularly streamlined. We also considered whether to include tournament data in the search results and think it may be beneficial to consult with the tournaments team on this matter.

We have met with the user team and have decided to create two two issues that members from both teams will work on.
Issues:

Create a search bar with the ability to specify whether users or games are being queried.
Create a search landing page to display either users or games.

Once, these issues are created, they will be linked and this issue will be closed.

During the sprint review meeting on 11/06/23, @elizabethli31 mentioned that the matches team also discussed the need for a search bar, so we need to make sure our implementation fits their use as well.

During the sprint review meeting on 11/06/23, @elizabethli31 mentioned that the matches team also discussed the need for a search bar, so we need to make sure our implementation fits their use as well.

My instinct is that a general search for users or games would be separate from a match search. @nugerhard do you have any thoughts?

@frowenz: this makes sense to me. I think we were imagining the lobby search as a filtering tool on an existing list of lobbies vs. an aggregating tool in its own right. While we could add lobbies as reachable by this "consolidated platform search", I feel like that type of search is better reserved for more static entities like users, games, groups, etc.
I'd also note that Board Game Arena lobbies/tables don't seem searchable from the main search bar, which is another point for this design choice.

@nugerhard that is probably the best approach. In that case, we just keep the search bar for users and games

Closing this issue.
We reached out to the user and tournament teams and came up with the following plan:
The general search bar will be for users and games only. ChiGame Users will decide whether they are searching for users or games as they search. A first pass has been implemented in #176. The current strategy involves a shared search results page, with distinct handling of search views and URLs.
The main remaining tasks are to add autocomplete (#95) and to add search and filtering capabilities on the results page (#191). A smaller remaining task (no issue yet) is to improve the UI.

Issue Score: Excellent
Comments:
The only thing this issue is missing is a goal in the summary. Something like "reach out to the users team to decide if/how our search bar will integrate users and games".
Great work communicating and updating the issue with information from discussions and meetings!
Great work outlining and then linking relevant issues as well.
This is a phenomenal example of an communication and design-focused issue.


Artifactory Ansible -  Failed resolving master key, Service wont start

Is this a request for help?:
Yes
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
BUG REPORT

Which installer:
Ansible Collection
Which product and version (eg: ansible & collection version - 7.24.2):
latest ansible collection and ansible
Which operating system and version(eg: ubuntu & version - 20.4):
Ubuntu 22.04
Which product license (Enterprise/Pro):
Enterprise
JFrog support reference (if already raised with support team):
What happened:
Artifactory won't start after a fresh install with the Ansible Collection. Nginx says "503 - Bad Gateway" for the user and in the Nginx-Logs we see the following:
root@lraus-lab0:/opt/jfrog/artifactory/var/log# cat /var/log/nginx/artifactory-error.log
2022/12/18 19:11:35 [error] 13219#13219: *89 connect() failed (111: Unknown error) while connecting to upstream, client: <IP_ADDRESS>, server: test.artifactory.com, request: "GET /ui/ HTTP/1.1", upstream: "http://<IP_ADDRESS>:8082/ui/", host: "<IP_ADDRESS>"
2022/12/18 19:11:35 [error] 13219#13219: *89 connect() failed (111: Unknown error) while connecting to upstream, client: <IP_ADDRESS>, server: test.artifactory.com, request: "GET /favicon.ico HTTP/1.1", upstream: "http://<IP_ADDRESS>:8082/favicon.ico", host: "<IP_ADDRESS>", referrer: "http://<IP_ADDRESS>/ui/"

In the Router-Service-Log on can see that the Master-Key can somehow not be decrypted:
root@lraus-lab0:/opt/jfrog/artifactory/var/log# cat router-service.log
2022-12-18T18:47:33.266Z [jfrou] [INFO ] [0d96be6e3486ae79] [bootstrap.go:77               ] [main                ] [] - Router (jfrou) service initialization started. Version: 7.50.0-1 Revision: 027126ff8a8e43e22ade6fbbf02d8226df457cba PID: 5398 Home: /opt/jfrog/artifactory
2022-12-18T18:47:33.266Z [jfrou] [INFO ] [0d96be6e3486ae79] [bootstrap.go:80               ] [main                ] [] - JFrog Router IP: <IP_ADDRESS>
2022-12-18T18:49:33.268Z [jfrou] [FATAL] [0d96be6e3486ae79] [bootstrap.go:99               ] [main                ] [] - Failed resolving master key: encoding/hex: invalid byte: U+0054 'T'

The Master-Key was successfully deployed by the ansible role.

After some times the "artifcatory"-Service fails. With a ``systemctl restart artifcatory` the service reboots and the webinterface is now shown!
What you expected to happen:
The service should have been started immediatly. A manual restart should not be necessary!
How to reproduce it (as minimally and precisely as possible):
Execute the following playbook on an Ubuntu 20.04 machine.
---
- hosts: all
  become: true
  become_method: sudo
  vars:
    ## Note: These values are global and have precedence over role/<product>/defaults/main.yaml
    ## For production deployments, You may want to generate your master and join keys and apply it to all the nodes.
    master_key: bbc8cdfbf6f999a7500e4e43cf620b9d570965c0af17623c749949b18717398a
    join_key: 94808af081282886c54644de48e74c469fac381793695228a0eaf43edf6c10f7

    jfrog_url: >-
      "http://{{ hostvars[groups['artifactory_servers'][0]]['ansible_host'] }}:8082"

    ## Products enabled
    artifactory_enabled: true
    xray_enabled: false
    distribution_enabled: false
    insight_enabled: false
    postgres_enabled: true

    # Artifactory DB details
    artifactory_db_type: postgresql
    artifactory_db_driver: org.postgresql.Driver
    artifactory_db_name: artifactory
    artifactory_db_user: artifactory
    artifactory_db_password: password
    artifactory_db_url: >-
      jdbc:postgresql://{{ hostvars[groups['postgres_servers'][0]]['ansible_host'] }}:5432/{{ artifactory_db_name }}

    # Postgresql users and databases/schemas
    database:
      artifactory:
        name: "{{ artifactory_db_name }}"
        owner: "{{ artifactory_db_user }}"
        username: "{{ artifactory_db_user }}"
        password: "{{ artifactory_db_password }}"
        enabled: "{{ artifactory_enabled }}"

  tasks:
    - name: Print Jfrog jfrog
      debug:
        msg: "{{ jfrog_url }}"

  roles:
    - role: jfrog.platform.postgres
      when: postgres_enabled | bool
    - role:  jfrog.platform.artifactory
      when: artifactory_enabled | bool

Anything else we need to know:
Already tried other OS (e.g Ubuntu 20.04) and

@localleon : Is the issue still persist?
Though you have mentioned the latest ansible collection. Can you specify the exact version of it?
Do you have any customizations done to the system.yaml file?

@localleon , gentle reminder..

Hey,
sorry for the late reply. I was on a holiday leave.
The issue still persists.
ansible [core 2.14.1]
  config file = None
  configured module search path = ['/home/lraus/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /home/lraus/.local/lib/python3.10/site-packages/ansible
  ansible collection location = /home/lraus/.ansible/collections:/usr/share/ansible/collections
  executable location = /home/lraus/.local/bin/ansible
  python version = 3.10.6 (main, Nov 14 2022, 16:10:14) [GCC 11.3.0] (/usr/bin/python3)
  jinja version = 3.0.3
  libyaml = True

Using

community.general-6.1.0
jfrog.platform-10.10.1

@localleon we are unable to reproduce this issue . Please provide detailed steps to reproduce  the issue

@localleon , gentle reminder..   Let us know if we can close this issue.


Approach and ideas to reduce the amount of console windows...

Since some time i try to reduce the amount of open console windows.
But only sudo -E in console seems to work. So each GUI app has an additional console window open.
My plan is to start GUI apps without additional console window.
With lots of started GUI apps you have as much open console windows and you loose count of it.
Sadly gksu did not work although there is an option to preserve environment variables like sudo -E.
I tried pkexec together with sudo -E, but it is only working with rudimental GUI apps which work without preserving enviroment variables.
Has anyone other approaches to get a double sudo -E working with graphical authentification without a console window?
I thought about hiding annoying console windows, but it seems even that is not possible in an easy practical way.

Are you sure that this is the right project? :)


Google button not showing icon

I copied & pasted the code in the README file but it did not show the google icon

me too why?


Delayed outputs?

What is the best way to implement sending messages to an output with a delay? The docs suggest a self-scheduling mechanism, e.g.:
scheduler.schedule_event(Duration::from_secs(1), Self::push_msg, msg);

with a corresponding handler
fn push_msg(&mut self, msg: Msg) {
    self.output.send(msg);
}

but I feel this might get slightly tedious in complex models. Ideally, I would like to simply write
self.output.send_in(Duration::from_secs(1), msg);

I found myself trying to build this on top of asynchronix, for example a simple (fairly non-optimized) approach would be
// AX_OUT just describes all types that can be sent over outputs
#[derive(Default)]
pub struct DelayedOutput<MsgT: AX_OUT> {
    pub output: Output<MsgT>,
    queue: VecDeque<TimedMsg<MsgT>>,
    time: u64,
}

impl<MsgT: AX_OUT> DelayedOutput<MsgT> {
    pub fn send(&mut self, msg: MsgT, delay: u64) {
        self.queue.push_back(TimedMsg {
            msg,
            time: self.time + delay,
        });
    }
    fn release(&mut self) {
        while let Some(TimedMsg { msg, time }) = self.queue.front() {
            if *time > self.time { break; }
            let TimedMsg { msg, .. } = self.queue.pop_front().unwrap();
            executor::block_on(self.output.send(msg));
        }
        self.time += 1;
    }
}

but this is not too flexible (what about request outputs? maybe other future output types?) and I would like to stick closer asynchronix. Any suggestions how I should do this?

(though much of my struggles might stem from my inexperience with the language :) so apologies if I'm over-engineering simple things, happy to learn more)

There is no real way to avoid the scheduler here, but you could save yourself a bit of typing by declaring a macro:
macro_rules! deferred_send {
    ($m:ty, $o:ident, $v:ty) => {{
        async fn deferred(m: &mut $m, v: $v) {
            let _ = m.$o.send(v).await;
        }

        deferred
    }};
}

which you would use as follows:
scheduler.schedule_event(Duration::from_secs(1), deferred_send!(MyModel, output, Msg), msg).unwrap();

The macro works for requestor ports too, but obviously the reply is ignored.
If you come to the conclusion that the macro is worth adding to the library and/or have ideas how to improve it, please let me know.

Thanks, this works.


SetInterruptHandler and SetMemoryLimit missing

I want to configure the memory limit and define a custom interrupt handler in QuickJS.
To do this the following functions need to be implemented:

JS_SetMemoryLimit
JS_SetInterruptHandler

Example:
// this script will keep running
while (true) { }

With a custom interrupt handler, it is possible to prevent abuse.

Done, I prefered to wrap the JS_SetInterruptHandler in cpp code instead exporting it to the dart side, Example can be found in:
https://github.com/ekibun/flutter_qjs/blob/32aac42c194bd9631fb44e0582e6fde1778807d0/test/flutter_qjs_test.dart#L124-L153


请问是不是停止维护了？好像是登录google translate的问题

Traceback (most recent call last):
File "translate", line 33, in
File "translate", line 29, in main
File "mkTranslation\translator.py", line 163, in translate_doc
File "mkTranslation\translator.py", line 98, in write_tx
File "mkTranslation\translator.py", line 72, in translate
File "mkTranslation\translate_google.py", line 63, in translate
File "mkTranslation\translate_google.py", line 100, in _translate
File "mkTranslation\network.py", line 175, in do
File "mkTranslation\network.py", line 67, in _update
AttributeError: 'NoneType' object has no attribute 'group'
[19168] Failed to execute script translate

I am getting the same error. Is there any solution?


接收数据有丢失

请教一下，我使用此驱动，在接收10ms一次的数据时，偶尔会出现数据丢失的问题，可能会是什么原因造成的？使用的是ch340模块，用pc上位机接收时不会丢失数据的

me too

please check: https://github.com/mik3y/usb-serial-for-android/wiki/FAQ#I_observed_codereadcode_data_loss_with_continuous_transfer_at_high_baud_rates

please check: https://github.com/mik3y/usb-serial-for-android/wiki/FAQ#I_observed_codereadcode_data_loss_with_continuous_transfer_at_high_baud_rates

Thank you very much, the problem has been solved

please check: https://github.com/mik3y/usb-serial-for-android/wiki/FAQ#I_observed_codereadcode_data_loss_with_continuous_transfer_at_high_baud_rates

Thank you very much, the problem has been

please check: https://github.com/mik3y/usb-serial-for-android/wiki/FAQ#I_observed_codereadcode_data_loss_with_continuous_transfer_at_high_baud_rates

Thank you very much, the problem has been solved

你改了哪里解决了呢？


xow: init at 0.4

Motivation for this change
Taking over from #76185 .
Things done

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

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

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

The bindir in the service file still seems wrong to me? It should probably be based on the same DESTDIR as everything else.

 Or are you fine with leaving that as is.

 Or are you fine with leaving that as is.

I think I'd be more comfortable not maintaining this.
Thanks again for your efforts!

Thank you both for the work.


feat: support multi-level directory with intersection types

Checklist

[x] npm test passes
[ ] tests and/or benchmarks are included
[ ] documentation is changed or added
[x] commit message follows commit guidelines

Affected core subsystem(s)

Description of change

优化多级目录生成的声明文件。
  interface IController {
    home: ExportHome;
    // add Intersection Types
    parent: ExportParent & {
      sub: ExportParentSub;
    }
  }

Codecov Report

Merging #53 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #53      +/-   ##
==========================================
+ Coverage   97.16%   97.17%   +<.01%
==========================================
  Files          16       16
  Lines         671      673       +2
  Branches       97       99       +2
==========================================
+ Hits          652      654       +2
  Misses          7        7
  Partials       12       12

Impacted Files
Coverage Δ

src/index.ts
94.73% <ø> (ø)
:arrow_up:

src/generators/class.ts
97.82% <100%> (+0.09%)
:arrow_up:

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 cfe7d18...7ffcb59. Read the comment docs.


Support for scanning changed files only (IaC mode)

Trivy-action does not offer the ability to scan changed files only (i.e. files introduced or modified in a pull request).
Instead it scans all files in a directory, or specified files only. This increases scanning time unnecessarily during the CI process.

bump

Trivy action only supports what Trivy has to offer. Currently Trivy does not offer this feature in the open source version.

Trivy action only supports what Trivy has to offer. Currently Trivy does not offer this feature in the open source version.

Come on its a simple for_each in bash.. How come I can write it in 5min myself for OSS version but it cannot be baked into the action?


Handle unknown releases better

I have .net-4.6 and when I run the tool it just reports that I have .net-4.5. This is misleading and unhelpful because it suggests I have something that is older than .net-4.5.2. Instead, it should say that it scanned “381029” and doesn’t know about it yet.

@binki are the changes in my pull request OK?

It’s better, but it is hard to find the link being referenced by the text “Please log an issue using the link at the bottom of the page including this information”—the link should probably just be placed like Please log an issue including this information.

Done

Nice, that handles much more gracefully than the currently-hosted code. @shanselman, please consider merging this.


[Compose] bogus warning: Ignoring: volume: [Volume]

~/gopath/src/github.com/containerd/nerdctl/examples/compose-wordpress$ nerdctl compose up
WARN[0000] Ignoring: volume: [Volume]
WARN[0000] Ignoring: volume: [Volume]
INFO[0000] Ensuring image wordpress:5.7

The warning is bogus and should be removed.
The volume is actually supported.
ccfe513d4adbf60944f7863792e7540eead6ec87

Seems caused by https://github.com/compose-spec/compose-go/commit/6d1c5982084f0270fb8330ecc9e475f670f3cfe9#diff-afdd0b33342d2a26302203894a804248181a35b49d42c425a4beb5a6c349b757R133


CMake support

At the moment this library does not support clients using CMake. Is there a plan to change that?
The documentation's You can just copy the content of the "include" folder suggestion is not acceptable.
Since this is a header-only library with no dependency on other Boost libraries, the lists file to provide support would look trivial.
I could make a PR adding a lists file if desired.

I'd appreciate a PR with CMake support. Please provide tests and usage examples.

I'd appreciate a PR with CMake support. Please provide tests and usage examples.

Sure, I already have a minimal implementation at cmake-support, which only defines the usage requirements of the project, but it follows a convention for naming and directory structure that you might not like, so let me ask a few questions first:
How would you like clients to find your library? At the moment the lists file defines <prefix>/lib/cmake/BoostPFR-2.0.1 as the install location for the config file that describes the project. This path is trivially findable by CMake, but I want to know what is your stance on the name BoostPFR and the version embedded in the folder name.
How would you like the exported target name to be called? At the moment the library target is called pfr and when installing this is namespaced to Boost::, i.e. it becomes Boost::pfr in clients' lists files. There is also the ALIAS target which makes the usage uniform even if the client decides to pull the library into their build tree:
# Installed in a prefix location
find_package(BoostPFR)
# Or pulled into the build tree
add_subdirectory("path to pfr")

# In both cases the usage looks the same
target_link_library(tgt PRIVATE Boost::pfr)

Sure, I already have a minimal implementation at cmake-support, which only defines the usage requirements of the project, but it follows a convention for naming and directory structure that you might not like, so let me ask a few questions first:
How would you like clients to find your library? At the moment the lists file defines <prefix>/lib/cmake/BoostPFR-2.0.1 as the install location for the config file that describes the project. This path is trivially findable by CMake, but I want to know what is your stance on the name BoostPFR and the version embedded in the folder name.
How would you like the exported target name to be called? At the moment the library target is called pfr and when installing this is namespaced to Boost::, i.e. it becomes Boost::pfr in clients' lists files. There is also the ALIAS target which makes the usage uniform even if the client decides to pull the library into their build tree:
# Installed in a prefix location
find_package(BoostPFR)
# Or pulled into the build tree
add_subdirectory("path to pfr")

# In both cases the usage looks the same
target_link_library(tgt PRIVATE Boost::pfr)

Please follow the existing practice where possible. Here's an example of CMake for another header-only boost library https://github.com/boostorg/any/blob/develop/CMakeLists.txt .

BoostPFR-2.0.1 seems good. SameMajorVersion is what I was intending in the library.
Lowercase target name seems better Boost::pfr. It would also follow the existing practice https://github.com/boostorg/mp11/blob/develop/CMakeLists.txt
Skip the tests rewrite on CMake. Leave it b2.
Provide some minimal usage example with CMake. So that I could embed that example in the b2 test suite and make sure that the CMake is working fine.

Please follow the existing practice where possible. Here's an example of CMake for another header-only boost library https://github.com/boostorg/any/blob/develop/CMakeLists.txt .

BoostPFR-2.0.1 seems good. SameMajorVersion is what I was intending in the library.
Lowercase target name seems better Boost::pfr. It would also follow the existing practice https://github.com/boostorg/mp11/blob/develop/CMakeLists.txt
Skip the tests rewrite on CMake. Leave it b2.
Provide some minimal usage example with CMake. So that I could embed that example in the b2 test suite and make sure that the CMake is working fine.

That lists file from any is woefully incomplete, I'm unsure what is there to follow. The target name should have a name so that prefixed with a namespace it ends up as the desired name. If the target is called boost_pfr then the resulting export set with a namespace prefix will install as Boost::boost_pfr, which is really undesirable.
cmake-support at the moment contains a "complete" lists file, which can be trivially consumed and installed like so:
# assuming UNIX and the build system is Ninja or Make
cmake -S . -B build -D CMAKE_BUILD_TYPE=Release
cmake --build build
sudo cmake --install build

The above commands with the current lists file will do the correct thing on all platforms, but also enable trivial packaging with cpack:
(cd build && cpack) # will use the default generators, but parameterizing is trivial

I am in fact using this property of it being trivially consumable, because I don't want to package and maintain a personal Debian repository for this.

That lists file from any is woefully incomplete, I'm unsure what is there to follow. The target name should have a name so that prefixed with a namespace it ends up as the desired name. If the target is called boost_pfr then the resulting export set with a namespace prefix will install as Boost::boost_pfr, which is really undesirable.
cmake-support at the moment contains a "complete" lists file, which can be trivially consumed and installed like so:
# assuming UNIX and the build system is Ninja or Make
cmake -S . -B build -D CMAKE_BUILD_TYPE=Release
cmake --build build
sudo cmake --install build

The above commands with the current lists file will do the correct thing on all platforms, but also enable trivial packaging with cpack:
(cd build && cpack) # will use the default generators, but parameterizing is trivial

I am in fact using this property of it being trivially consumable, because I don't want to package and maintain a personal Debian repository for this.

Hm... Then please do it the right way :)
Please, also write a letter to the "Boost developers mailing list" with the description of issues with the current cmake approach. People just started the cmake transition and some things may be done wrong. We'd appreciate a guidance or at least some hints on how to do it better

Hm... Then please do it the right way :)
Please, also write a letter to the "Boost developers mailing list" with the description of issues with the current cmake approach. People just started the cmake transition and some things may be done wrong. We'd appreciate a guidance or at least some hints on how to do it better

I have no idea how mailing lists work. However, I am all for the Boost project achieving better CMake usage.
Suffice to say, CMake usage and dependency management in general is in a pretty bad situation when it comes to C++. The Boost project adopting better CMake usage and acquiring an exemplary status should potentially alleviate these common pains.

I have no idea how mailing lists work. However, I am all for the Boost project achieving better CMake usage.
Suffice to say, CMake usage and dependency management in general is in a pretty bad situation when it comes to C++. The Boost project adopting better CMake usage and acquiring an exemplary status should potentially alleviate these common pains.

Peter is hard at work to bring CMake to Boost, so I can safely close this issue.

Hi! I see the original post mentions find_package support, and currently the master branch doesn't contain neither the install rules nor BoostPFRConfig.cmake. As a consequence I see some parties consume pfr using FetchContent without FIND_PACKAGE_ARGS, e.g. https://github.com/Meumeu/WiVRn/blob/23298a1581e792c1ac7a09db238a87e7ad7c7c2c/CMakeLists.txt#L84 (which is obviously damaging to ecosystems like vcpkg or nixpkgs, etc)
I'm not familiar with the CMake support efforts in Boost, so I thought I'd ask before opening follow-up issues or PRs. What are the current plans regarding the install rules and find_package? Thanks!

Boost.PFR is a Level 0 header-only library and Peter Dimov has introduced CMake client support to Boost. You can find_package(Boost REQUIRED) and link to Boost::headers for PFR.

If I were to contact wivrn developers, would it be reasonable to suggest that they depend on the whole Boost::headers instead?


Improvement remove radix sort

Proposed changes
remove radix sort
radix sort
mysql [test]>SELECT COUNT() FROM (   SELECT UserID   FROM hits_1m   ORDER BY FlashMajor   LIMIT 50000000 ) t;
+----------+
| count(*) |
+----------+
|  1000000 |
+----------+
1 row in set (0.30 sec)

pdq sort
mysql [test]>SELECT COUNT() FROM (   SELECT UserID   FROM hits_1m   ORDER BY FlashMajor   LIMIT 50000000 ) t;
+----------+
| count(*) |
+----------+
|  1000000 |
+----------+
1 row in set (0.24 sec)

run buildall

run buildall


Add user picture and Treat bot accounts appropriately

Hi @kaakaa-san,
I saw your development progressing. This is nice. The original version of my change did not treat user's icon and a bot account appropriately. This PR addresses those issues.
I still have a difficulty to handle time stamp in the footer. I am wondering if Mattermost is capable to time zone in the footer.

Seems like MessageWillBePosted() is not called when posting in iPhone app. And occasionally it isn't called by Desktop app as well.
Also I notice that there is a case that embedding a bot icon doesn't work. It seems to occur with incoming webhook accounts. Not sure why yet.

Sorry about that. Fixed it.
As for the iPhone Mobile app issue, I am also using v1.30.1. And I encountered with the successful case. The behavior seems not stable...
Multiple posts also seem to fail to expand a link but not always.

Thanks! It works fine now 👍
I'm sorry, but could you fix the formatting of the code? gofmt should be useful for you. gofmt is language-default formatter of golang, and should be installed by default. If gofmt is installed, gofmt -w server/ overwrite existing code by formatted code.
And if you run make check-style in the root of this repository, you can run the linter including the format check (it should be run as a CI, but I didn't configure it yet).

As for the iPhone Mobile app issue, I am also using v1.30.1. And I encountered with the successful case. The behavior seems not stable...
Multiple posts also seem to fail to expand a link but not always.

Thanks for additional comments. It's weird...
I create new issue #2 for this, so let's continue on #2.

Wow, what a nice feature! Thanks for letting me know.


[Doc] Semantic Functions with Multiple Arguments

It's possible that I merely haven't found the right spot in the docs yet, but: what is the preferred way of calling a Semantic Function which takes multiple arguments?
As a concrete example, the Rewriter function (in samples/WriterSkill) has the following prompt file:
Rewrite the given text like it was written in this style or by: {{$style}}.
MUST RETAIN THE MEANING AND FACTUAL CONTENT AS THE ORIGINAL.

{{$input}}

There are obviously two parameters - input for the text to be rewritten, and style to specify how things should be rephrased.
There's also the config.json file, with the following contents:
{
  "schema": 1,
  "type": "completion",
  "description": "Automatically generate compact notes for any text or text document",
  "completion": {
    "max_tokens": 256,
    "temperature": 0.0,
    "top_p": 0.0,
    "presence_penalty": 0.0,
    "frequency_penalty": 0.0
  }
}

One thing I have noticed is that some other skills have an input key in this JSON, which itself has a parameters key and a list. I'm not sure if this is significant.
Anyway, experimenting with this, it appears that the only way to change the value of the style parameter is by using a context:
context = kernel.create_new_context()
context["style"] = "Shakespeare"
target_text = """
I was walking along a street when I saw my friend. We stopped to say 'Hello' and catch up with recent events.
"""
result = rewriteFunction(target_text, context=context)
print(result)

All my attempts to put the style parameter directly into the rewriteFunction() call have come to naught, but this approach feels quite cumbersome. Have I missed something?
Running:
[x.name for x in rewriteFunction.parameters]

is showing two parameters, named according to the prompt, but I can't figure out how to use these simply in the rewriteFunction() call.

@riedgar-ms - here is what the config.json will look at (FYI)
{
"schema": 1,
"type": "completion",
"description": "Automatically generate compact notes for any text or text document",
"completion": {
"max_tokens": 256,
"temperature": 0,
"top_p": 0,
"presence_penalty": 0,
"frequency_penalty": 0
},
"input": {
"parameters": [
{
"name": "input",
"description": "",
"defaultValue": ""
},
{
"name": "style",
"description": "",
"defaultValue": ""
}
]
}
}
@dluc  can you help with how to do the calling.

In the current implementation, if you want to use multiple arguments in your functions, you'll need to make use of the SKContext and then put all the parameters there. I agree it feels strange, and we're reviewing the design of this. Take a look at this notebook for a more in-depth look at native/semantic functions:
https://github.com/microsoft/semantic-kernel/blob/main/samples/notebooks/python/08-native-function-inline.ipynb

We now have this sample: https://github.com/microsoft/semantic-kernel/blob/main/dotnet/samples/KernelSyntaxExamples/Example56_TemplateNativeFunctionsWithMultipleArguments.cs

This is now possible so closing this issue.


ssh-askpass not working anymore, even internal ask pass

Hi. I'm using this excellent git client since 8.20 (both Linux and Windows) and on Linux, since 8.21 the ask-pass feature is not working properly anymore.
Since 8.20 version, instead opening the ssh-askpass dialog, SourceGit open a new instance of SourceGit and the previous SourceGit Window   show the message below:
Received disconnect from xxxx.xx.xxx.xxx port xxxxx:2: Too many authentication failures
Disconnected from xxxx.xx.xxx.xxx port xxxxx
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
If you need more details, please let me know.
PopolonY2k

Could you please run git fetch command manually and copy the output message from terminal?

I've pushed a commit 1e0a2ab5f733572fed9743127b23ac292751e3b8 that add -o StrictHostKeyChecking=accept-new option to GIT_SSH_COMMAND, which will automatically accept new connections. You can try this build https://github.com/sourcegit-scm/sourcegit/actions/runs/10034206003

https://github.com/sourcegit-scm/sourcegit/actions/runs/10034206003

Hi friend...I tried now a git fetch at command line and it only request the password and nothing more (because there's no any data to fetch).

I've pushed a commit 1e0a2ab that add -o StrictHostKeyChecking=accept-new option to GIT_SSH_COMMAND, which will automatically accept new connections. You can try this build https://github.com/sourcegit-scm/sourcegit/actions/runs/10034206003

I tried this build but I'm facing the same problem

Hi friend...I tried now a git fetch at command line and it only request the password and nothing more (because there's no any data to fetch).

Is there any output message like Enter passphrase?

Hi friend...I tried now a git fetch at command line and it only request the password and nothing more (because there's no any data to fetch).

Is there any output message like Enter passphrase?

No...absolutely nothing. I dowloaded latest sourcegit from repository and started debugging. If I discover something I'll post here

No...absolutely nothing. I dowloaded latest sourcegit from repository and started debugging. If I discover something I'll post here

Thank you very much. I can NOT reproduce this issue on my Windows/macOS/Linux

By the way, you can remove this condition to see the message your ssh client calling SSH_ASKPASS with:
 private bool TryLaunchedAsAskpass(IClassicDesktopStyleApplicationLifetime desktop)
 {
     var args = desktop.Args;
-     if (args == null || args.Length != 1 || !args[0].StartsWith("Enter passphrase", StringComparison.Ordinal))
+     if (args == null || args.Length != 1)
        return false;

     desktop.MainWindow = new Views.Askpass(args[0]);
     return true;
 }

By the way, you can remove this condition to see the message your ssh client calling SSH_ASKPASS with:
 // File: App.axaml.cs
 private bool TryLaunchedAsAskpass(IClassicDesktopStyleApplicationLifetime desktop)
 {
      var args = desktop.Args;
-     if (args == null || args.Length != 1 || !args[0].StartsWith("Enter passphrase", StringComparison.Ordinal))
+     if (args == null || args.Length != 1)
        return false;

     desktop.MainWindow = new Views.Askpass(args[0]);
     return true;
 }

Yes....perfect....your suggestion fix the problem and now is showing SourceGit AskPass dialog correctly and all git operations (Fetch, Push, Pull) works again.
I think you have a bugfix for the next build :)
Thanks

Yes....perfect....your suggestion fix the problem and now is showing SourceGit AskPass dialog correctly and all git operations (Fetch, Push, Pull) works again.

So, what's the arguments your SSH client passed to SSH_ASKPASS to launch this app as ask-pass client? It is displayed as title of input box like:

So, what's the arguments your SSH client passed to SSH_ASKPASS to launch this app as ask-pass client? It is displayed as title of input box like:

Apparently it is not passing any parameter:

It is asking by password because my personal git is using Linux authentication only.

It is asking by password because my personal git is using Linux authentication only.

It seems that checking the argument with 'Enter passphrase' is not applicable in all cases.

But this app supports to open repository at commandline like:
sourcegit SOME_REPO

I need to find a way to distinguish between Open Repository and Launch as Askpass Client

But this app supports to open repository at commandline like:
sourcegit SOME_REPO

I need to find a way to distinguish between Open Repository and Launch as Askpass Client

Why not call your software with an extra parameter when it has been called as ask-pass, like a SourceGit --ask-pass command line parameter ??
Regards

When calling SourceGit --ask-pass you will be able to know exactly your software has been called to display the ass-pass dialog.
:)

Env SSH_ASKPASS can not have extra arguments. It is passed to execv function directly by SSH client.

see issue #239

Would you like to test this code for me?
// App.axaml.cs
+[GeneratedRegex(@"^([A-Za-z0-9_-]+(\.\w+)*@(\w+\.)+\w{2,5})'s password$")]
+private static partial Regex REG_ASKPASSWORD();

 private bool TryLaunchedAsAskpass(IClassicDesktopStyleApplicationLifetime desktop)
 {
     var args = desktop.Args;
     if (args == null || args.Length != 1)
         return false;

+    var arg = args[0];
+    if (!arg.StartsWith("Enter passphrase", StringComparison.Ordinal) && !REG_ASKPASSWORD().IsMatch(arg))
+        return false;

-    desktop.MainWindow = new Views.Askpass(args[0]);
+    desktop.MainWindow = new Views.Askpass(arg);
     return true;
 }

Never mind. I've pushed a commit e0319e3f9b36d8bd2116fe1d5ceb5e2a8cddc8e7 to fix this issue.
Here is the change:
        private bool TryLaunchedAsAskpass(IClassicDesktopStyleApplicationLifetime desktop)
        {
            var args = desktop.Args;
-           if (args == null || args.Length != 1 || !args[0].StartsWith("Enter passphrase", StringComparison.Ordinal))
+           if (args == null || args.Length != 1)
                return false;

-           desktop.MainWindow = new Views.Askpass(args[0]);
+           var param = args[0];
+           if (!param.StartsWith("enter passphrase", StringComparison.OrdinalIgnoreCase) &&
+               !param.Contains(" password", StringComparison.OrdinalIgnoreCase))
+               return false;
+
+           desktop.MainWindow = new Views.Askpass(param);
            return true;
        }

Hi @love-linger sorry by delaying to respond you. Your commit is working fine.
Thanks a lot.


ENH: stats.describe: add array API support

Reference issue
Towards https://github.com/scipy/scipy/issues/20544
What does this implement/fix?
Adds array API support to scipy.stats.describe.
Additional information
I think our policy of translating existing tests rather than rewriting is good, but it was pretty cumbersome for this one. Most of what we really need is one big property-based test showing that the results of describe match the results of the functions it calls. Those functions are tested elsewhere.

CI failure appears to be unrelated.

Thanks @mdhaber planning to review this and other from Wednesday onwards


Disable initializer for nightly env

The nightly env is using FIDC, in this env we would like to use the cs_config_manager tool to manage the config.
Disable the initializer from running in nightly.

Everything is in place to do this, but we need to review if we want too or not @dbadham-fr @BohoCode

See previous comments, need to review if we want to actually do this

This is done :+1:


Refs #32338 -- Removed field label for RadioSelect widgets

Refs Ticket 32338
This fixes the 2nd issue on the ticket against radioselect inputs.
The label for checkboxes was removed in #7449 on the grounds of usability. Applying the same logic for radios will allow for consitent behaviour between radios and checkboxes.
I added a release note, but I'm now wondering if this is  bug and therefore we don't need one?

@thibaudcolas thanks for your review on the other accessibility PR I have open. Did you want to take a look at this one as well?

@smithdc1 yep 🙂  It doesn’t look like I can assign myself as reviewer but I’ll be testing this as soon as possible. This is looking like a pretty clear improvement as it is, but I need to get this running locally to make sure I give the best review possible.

@thibaudcolas I asked "Accessibility Team" for a review, you can do it on its behalf.

Thanks for all the reviews. I've squashed and rebased.

buildbot, test this please

I wonder if we should have added a note somewhere to say we've changed the inheritance of checkboxes.
For example, on crispy-forms this changed caused the tests to fail as it used to check if a widget is a radio or checkbox via isinstance but now a checkbox is also an instance of a radio.


unicodeerror on windows 10

screencopy (windows  10) :
C:\Users\Public>python
Python 3.6.3 (v3.6.3:2c5fed8, Oct  3 2017, 18:11:49) [MSC v.1900 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.

from playsound import playsound
playsound('nougayork.mp3')
Traceback (most recent call last):
File "", line 1, in
File "C:\Users\brigitte and co\AppData\Roaming\Python\Python36\site-packages\playsound.py", line 35, in _playsoundWin
winCommand('open "' + sound + '" alias', alias)
File "C:\Users\brigitte and co\AppData\Roaming\Python\Python36\site-packages\playsound.py", line 30, in winCommand
'\n    ' + errorBuffer.value.decode())
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe8 in position 8: invalid continuation byte

same

The problem occurs when you have non-ascii characters in the path to the file.
Quick fix (not tested yet):
def winCommand(*command):
    buf = c_buffer(512)
    command = ' '.join(command).encode('utf-16')
    errorCode = int(windll.winmm.mciSendStringW(command, buf, 511, 0))
    if errorCode:
        errorBuffer = c_buffer(512)
        windll.winmm.mciGetErrorStringW(errorCode, errorBuffer, 511)
        exceptionMessage = ('\n    Error ' + str(errorCode) + ' for command:'
                            '\n        ' + command +
                            '\n    ' + errorBuffer.value.decode('utf-16'))
        raise PlaysoundException(exceptionMessage)
    return buf.value

After some testing and more fixes, _playsoundWin looks like this
def _playsoundWin(sound, block = True):
    '''
    snip
    '''
    from ctypes import c_buffer, windll
    from random import random
    from time   import sleep
    from sys    import getfilesystemencoding

    def winCommand(*command):
        buf = c_buffer(512)
        command = ' '.join(command)
        errorCode = int(windll.winmm.mciSendStringW(command.encode('utf-16'), buf, 511, 0))
        if errorCode:
            errorBuffer = c_buffer(512)
            windll.winmm.mciGetErrorStringW(errorCode, errorBuffer, 511)
            exceptionMessage = ('\n    Error ' + str(errorCode) + ' for command:'
                                '\n        ' + command +
                                '\n    ' + errorBuffer.raw.decode('utf-16').rstrip('\0'))
            raise PlaysoundException(exceptionMessage)
        return buf.raw.decode('utf-16').rstrip('\0')

    alias = 'playsound_' + str(random())
    winCommand('open "' + sound + '" alias', alias)
    winCommand('set', alias, 'time format milliseconds')
    durationInMS = winCommand('status', alias, 'length')
    winCommand('play', alias, 'from 0 to', durationInMS)

    if block:
        sleep(float(durationInMS) / 1000.0)

So here need one prompt encoding arg to avoid encode error, not only utf-16, I need gbk too...

@ClericPy if UTF-16 is not enough for Chinese then yes, it needs another encoding argument.

Hello!!,
Is there any plan to apply the fix in main branch?
Thanks!

No.
The reason why is because I don’t care. pip can install straight from a git url - use that if you want to get the version off this branch.
Taylor
Sent from my iPhone

On Aug 18, 2019, at 16:36, Danixu<EMAIL_ADDRESS>wrote:
Hello!!,
Is there any plan to apply the fix in main branch?
Thanks!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I see... the solution is there and you don't have to work, but is too hard to do it. You've lost more time writting the message than the one you need to merfe, but is better to do an unfriendly response.
Anyway, thanks to Insolor, your code works fine on Windows 10 and using paths with accents. I had to change two lines, but almost all was done. Later I'll see all forks because I've seen interesting things.
Greetings!!

I used to accept the patches/pull requests, but as you yourself just pointed out, you needed to modify two lines for it to work. I’ve found it’s a game of whack-a-mole - you accept one and suddenly there’s more people complaining about bugs introduced by the latest patch. It’s easier to just ignore all the complaints.
If I was getting paid for it, maybe I’d put more effort in. As is, I’m not.
If Unicode isn’t working, why not rename your files? Really, a higher priority for me with this (so low priority that I’ll also probably never do it) would be making it work on a Raspberry Pi.
Taylor
Sent from my iPhone

On Aug 18, 2019, at 17:50, Danixu<EMAIL_ADDRESS>wrote:
I see... the solution is there and you don't have to work, but is too hard to do it. You've lost more time writting the message than the one you need to merfe, but is better to do an unfriendly response.
Anyway, thanks to Insolor, your code works fine on Windows 10 and using paths with accents. I had to change two lines, but almost all was done. Later I'll see all forks because I've seen interesting things.
Greetings!!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

I see... the solution is there and you don't have to work, but is too hard to do it. You've lost more time writting the message than the one you need to merge, but is better to do an unfriendly response.
Anyway, thanks to Insolor, your code works fine on Windows 10 and using paths with accents. I had to change two lines, but almost all was done. Later I'll see all forks because I've seen interesting things.
Greetings!!

Hey, i didn't understand how are we suppose to fix it, can you help me ?

This should be fixed on master now. The testcase testBlockingCYRIL_WAV should ensure that regressions don't occur.
I'll try to upload what's on master to Pypi in the next day or two.