wallet_watchAsset does not exist/is not available

I am trying to track a specific token following the steps provided here, but I always get the following response:
{     "jsonrpc":"2.0","id":6,     "error":{"code":-32601,"message":"the method wallet_watchAsset does not exist/is not available"} }
This is the request that is being made (I'm using the same token as in the example):
{      "method":"wallet_watchAsset",      "params":[{            "type":"ERC20",            "options":{                   "address":"0xcf664087a5bb0237a0bad6742852ec6c8d69a27a",                   "symbol":"WONE",                   "decimals":18,                   "image":"https://s2.coinmarketcap.com/static/img/coins/64x64/11696.png"              }      }],      "jsonrpc":"2.0",      "id":6 }
I got the same result on all networks that I tried:
Ethereum mainnet ( https://mainnet-infura.wallet.coinbase.com/ )
Ethereum Ropsten ( https://ropsten-infura.wallet.coinbase.com/ )
Binance Smart Chain Testnet ( https://data-seed-prebsc-1-s1.binance.org:8545/ )
Also, sending the params parameter as object, not as array, does not seem to work for Ethereum mainnet and Ethereum Ropsten, returning {"jsonrpc":"2.0","error":{"code":-32600,"message":"invalid json request"}}
SDK version: 3.0.1 (reproducible also on v2.4.4)
Browser: Chrome

You will have to synchronize your wallet and make sure you debug it with bech13.

@Yuxanju could you be more specific? What do you mean by "synchronize your wallet" and what is "bech13"? If by "synchronize wallet" you mean the process described here, I already did that. I was also able to switch/add networks as described here, it's just the wallet_watchAsset example that does not work.

By synchronizing your wallet_watchAsset will work .. I can send you the
link that will guide you to where you will click synchronize wallet and
then you click on that and you reboot your device
On Fri, Mar 4, 2022 at 12:45 AM @.***> wrote:

@Yuxanju https://github.com/Yuxanju could you be more specific? What do
you mean by "synchronize your wallet" and what is "bech13"? If by
"synchronize wallet" you mean the process described here
https://github.com/coinbase/coinbase-wallet-sdk#initializing-wallet-sdk-and-a-wallet-sdk-powered-web3-object,
I already did that. I was also able to switch/add networks as described
here
https://github.com/coinbase/coinbase-wallet-sdk#switching--adding-alternative-evm-compatible-chains,
it's just the wallet_watchAsset example that does not work.
—
Reply to this email directly, view it on GitHub
https://github.com/coinbase/coinbase-wallet-sdk/issues/379#issuecomment-1058958763,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AX54U7ENAJEPIJ6WF5V2ILLU6HET5ANCNFSM5PZZZHRQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

@Yuxanju secret links, rebooting devices (I'm in a browser context), sounds "great". Should I maybe just give you my private key and you can do that for me, please? :)
Anybody else having a more realistic idea about the cause of this issue?

How
On Fri, 4 Mar 2022, 6:40 PM ccosmincc @.***> wrote:

@Yuxanju https://github.com/Yuxanju secret links, rebooting devices
(I'm in a browser context), sounds "great". Should I maybe just give you my
private key and you can do that for me, please? :)
Anybody else having a more realistic idea about the cause of this issue?
—
Reply to this email directly, view it on GitHub
https://github.com/coinbase/coinbase-wallet-sdk/issues/379#issuecomment-1059045033,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATGRRY4KL5SIBUEWLG7KC6DU6HSA3ANCNFSM5PZZZHRQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Why would you give me your private key.. I don’t need that .. I’m only
trying to help you .. it’s an ellipal secure encrypted link meant for
synchronizing and debugging
On Fri, Mar 4, 2022 at 11:45 AM mikehunter1990 @.***>
wrote:

How
On Fri, 4 Mar 2022, 6:40 PM ccosmincc @.***> wrote:

@Yuxanju https://github.com/Yuxanju secret links, rebooting devices
(I'm in a browser context), sounds "great". Should I maybe just give you
my
private key and you can do that for me, please? :)
Anybody else having a more realistic idea about the cause of this issue?
—
Reply to this email directly, view it on GitHub
<
https://github.com/coinbase/coinbase-wallet-sdk/issues/379#issuecomment-1059045033
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/ATGRRY4KL5SIBUEWLG7KC6DU6HSA3ANCNFSM5PZZZHRQ
.
Triage notifications on the go with GitHub Mobile for iOS
<
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
<
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

—
Reply to this email directly, view it on GitHub
https://github.com/coinbase/coinbase-wallet-sdk/issues/379#issuecomment-1059463895,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AX54U7FDKBF6F22ACDNMCYDU6JR45ANCNFSM5PZZZHRQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

Y
On Sat, 5 Mar 2022, 3:48 AM Yuxanju Lee @.***> wrote:

Why would you give me your private key.. I don’t need that .. I’m only
trying to help you .. it’s an ellipal secure encrypted link meant for
synchronizing and debugging
On Fri, Mar 4, 2022 at 11:45 AM mikehunter1990 @.***>
wrote:

How
On Fri, 4 Mar 2022, 6:40 PM ccosmincc @.***> wrote:

@Yuxanju https://github.com/Yuxanju secret links, rebooting devices
(I'm in a browser context), sounds "great". Should I maybe just give
you
my
private key and you can do that for me, please? :)
Anybody else having a more realistic idea about the cause of this
issue?
—
Reply to this email directly, view it on GitHub
<

https://github.com/coinbase/coinbase-wallet-sdk/issues/379#issuecomment-1059045033

,
or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/ATGRRY4KL5SIBUEWLG7KC6DU6HSA3ANCNFSM5PZZZHRQ

.
Triage notifications on the go with GitHub Mobile for iOS
<

https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675

or Android
<

https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub

.
You are receiving this because you are subscribed to this
thread.Message
ID: @.***>

—
Reply to this email directly, view it on GitHub
<
https://github.com/coinbase/coinbase-wallet-sdk/issues/379#issuecomment-1059463895
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AX54U7FDKBF6F22ACDNMCYDU6JR45ANCNFSM5PZZZHRQ
.
Triage notifications on the go with GitHub Mobile for iOS
<
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
<
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub
.
You are receiving this because you were mentioned.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub
https://github.com/coinbase/coinbase-wallet-sdk/issues/379#issuecomment-1059466023,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATGRRY4OCGU2MBI4FUSJFZLU6JSJJANCNFSM5PZZZHRQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you commented.Message ID:
@.***>

How
On Sat, 5 Mar 2022, 3:50 AM Michael Buenavente <
@.***> wrote:

Y
On Sat, 5 Mar 2022, 3:48 AM Yuxanju Lee @.***> wrote:

Why would you give me your private key.. I don’t need that .. I’m only
trying to help you .. it’s an ellipal secure encrypted link meant for
synchronizing and debugging
On Fri, Mar 4, 2022 at 11:45 AM mikehunter1990 @.***>
wrote:

How
On Fri, 4 Mar 2022, 6:40 PM ccosmincc @.***> wrote:

@Yuxanju https://github.com/Yuxanju secret links, rebooting devices
(I'm in a browser context), sounds "great". Should I maybe just give
you
my
private key and you can do that for me, please? :)
Anybody else having a more realistic idea about the cause of this
issue?
—
Reply to this email directly, view it on GitHub
<

https://github.com/coinbase/coinbase-wallet-sdk/issues/379#issuecomment-1059045033

,
or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/ATGRRY4KL5SIBUEWLG7KC6DU6HSA3ANCNFSM5PZZZHRQ

.
Triage notifications on the go with GitHub Mobile for iOS
<

https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675

or Android
<

https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub

.
You are receiving this because you are subscribed to this
thread.Message
ID: @.***>

—
Reply to this email directly, view it on GitHub
<
https://github.com/coinbase/coinbase-wallet-sdk/issues/379#issuecomment-1059463895
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AX54U7FDKBF6F22ACDNMCYDU6JR45ANCNFSM5PZZZHRQ
.
Triage notifications on the go with GitHub Mobile for iOS
<
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
<
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub
.
You are receiving this because you were mentioned.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub
https://github.com/coinbase/coinbase-wallet-sdk/issues/379#issuecomment-1059466023,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATGRRY4OCGU2MBI4FUSJFZLU6JSJJANCNFSM5PZZZHRQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you commented.Message ID:
@.***>

You will have to use the ellipal encrypted secure site .  I don’t need that .. I’m only
trying to help you .. it’s an ellipal secure encrypted link meant for
synchronizing and debugging
On Fri, Mar 4, 2022 at 11:45 AM mikehunter1990 @.***>
wrote:

How
On Fri, 4 Mar 2022, 6:40 PM ccosmincc @.***> wrote:

@Yuxanju https://github.com/Yuxanju secret links, rebooting
devices
(I'm in a browser context), sounds "great". Should I maybe just give
you
my
private key and you can do that for me, please? :)
Anybody else having a more realistic idea about the cause of this
issue?
—
Reply to this email directly, view it on GitHub
<

https://github.com/coinbase/coinbase-wallet-sdk/issues/379#issuecomment-1059045033

,
or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/ATGRRY4KL5SIBUEWLG7KC6DU6HSA3ANCNFSM5PZZZHRQ

.
Triage notifications on the go with GitHub Mobile for iOS
<

https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675

or Android
<

https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub

.
You are receiving this because you are subscribed to this
thread.Message
ID: @.***>

—
Reply to this email directly, view it on GitHub
<

https://github.com/coinbase/coinbase-wallet-sdk/issues/379#issuecomment-1059463895

,
or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/AX54U7FDKBF6F22ACDNMCYDU6JR45ANCNFSM5PZZZHRQ

.
Triage notifications on the go with GitHub Mobile for iOS
<

https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675

or Android
<

https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub

.
You are receiving this because you were mentioned.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub
<
https://github.com/coinbase/coinbase-wallet-sdk/issues/379#issuecomment-1059466023
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/ATGRRY4OCGU2MBI4FUSJFZLU6JSJJANCNFSM5PZZZHRQ
.
Triage notifications on the go with GitHub Mobile for iOS
<
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
<
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub
.
You are receiving this because you commented.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub
https://github.com/coinbase/coinbase-wallet-sdk/issues/379#issuecomment-1059470897,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AX54U7BXRXJ62ERVHISXDMTU6JTC7ANCNFSM5PZZZHRQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

@Yuxanju I might be missing something (although I doubt it), but to me the whole issue revolves around the POST request that is being sent to one of the URLs from my first comment (based on the selectec network) and the failed response that the server returns. I can see it all in the Network tab of the browser's dev tools. Not sure what else is left for me to debug/synchronize, it seems like a server-side problem.

Just follow the url I sent to you and make sure you debug it
On Sat, Mar 5, 2022 at 2:02 AM ccosmincc @.***> wrote:

@Yuxanju https://github.com/Yuxanju I might be missing something
(although I doubt it), but to me the whole issue revolves around the POST
request that is being sent to one of the URLs from my first comment (based
on the selectec network) and the failed response that the server returns. I
can see it all in the Network tab of the browser's dev tools. Not sure what
else is left for me to debug/synchronize, it seems like a server-side
problem.
—
Reply to this email directly, view it on GitHub
https://github.com/coinbase/coinbase-wallet-sdk/issues/379#issuecomment-1059734326,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AX54U7DLIY6C7OR62GDHJRDU6MWMPANCNFSM5PZZZHRQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

Have you follow the url?
On Sat, Mar 5, 2022 at 2:07 AM Trezor Suites @.***> wrote:

Just follow the url I sent to you and make sure you debug it
On Sat, Mar 5, 2022 at 2:02 AM ccosmincc @.***> wrote:

@Yuxanju https://github.com/Yuxanju I might be missing something
(although I doubt it), but to me the whole issue revolves around the POST
request that is being sent to one of the URLs from my first comment (based
on the selectec network) and the failed response that the server returns. I
can see it all in the Network tab of the browser's dev tools. Not sure what
else is left for me to debug/synchronize, it seems like a server-side
problem.
—
Reply to this email directly, view it on GitHub
https://github.com/coinbase/coinbase-wallet-sdk/issues/379#issuecomment-1059734326,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AX54U7DLIY6C7OR62GDHJRDU6MWMPANCNFSM5PZZZHRQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

wallet_watchAsset was added to Coinbase Wallet after this issue was raised. there should be no issues with calling the JSON RPC method now, please raise another issue if otherwise

@jeongmincho now I get a different error when trying to call the same method with the same parameters as in the first comment. Below is the relevant stack trace:

wallet_watchAsset
Someone is using my wallet


Restore bus stop feature service

Looks like someone deleted all the points in the service.
http://services.arcgis.com/IZtlGBUe4KTzLOl4/arcgis/rest/services/BPX_RTD_BusStops2/FeatureServer/0/

This old service will be replaced by a new service in v2.5.
Here's the replacement URI:
http://services1.arcgis.com/M8KJPUwAXP8jhtnM/arcgis/rest/services/Denver_Bus_Stops/FeatureServer/0


is Input modification functionality available?

Based on a condition, I am trying to set a discount percentage on my input. but I did not find any documentation about that.
for example, I have this input:
{
  "country" : "US",
  "discount": null
}

and I expected that if the country is US the response should be:
{
  "input":{
    "country" : "US",
    "discount": null
  }
}

Hi, please have a look at our example: https://gorules.io/docs/user-manual/getting-started/tutorials/retail-shipping-fees.
It's somewhat outdated but should contain relevant information for your use case.


Document how to deploy and run RiboViz Shiny components

[x] Request @shahpr add information to this ticket on how to deploy and run RiboViz Shiny components locally.
[ ] Run through this information on a virtual machine
[ ] Update RiboViz documentation with this information.

Closed as Shiny content has been purged - see #139


Docker login fails on Travis

@Theaxiom the new travis config fails to log in to docker, docker login is actually waiting at a
"Username:" prompt forever and then gets cancelled after 10 minutes.
Maybe the travis version still requries the -e email switch as well?

The problem only occurs on branches which are in a fork. I will update the travis config soon, what is there right now was just to get automated build and push working and I hven't had the time to clean everything up yet.

On Feb 22, 2018, at 7:31 AM, Zsolt Ero<EMAIL_ADDRESS>wrote:
@Theaxiom https://github.com/theaxiom the new travis config fails to log in to docker, docker login is actually waiting at a
"Username:" prompt forever and then gets cancelled after 10 minutes.
Maybe the travis version still requries the -e email switch as well?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/phusion/baseimage-docker/issues/471, or mute the thread https://github.com/notifications/unsubscribe-auth/AADetUZ6daRwUcTMd5Bno-uvREIfJNuOks5tXYhjgaJpZM4SPgPy.

any update on this ?

Yeah, it is very annoying. I am going to be fixing it shortly. Thanks for your patience!

Apologies everyone for my lack of attendance, I've been really consumed by life lately. I have upgraded @kingdonb to admin along with @hyperknot -- I appreciate both of your help in maintaining this project! Thank you! I will eventually fix the Docker stuff, unless someone gets to it first. :)


Push more than one file (multiple links per Link header)

I'm sorry for not following the template, but I'm not sure if it makes sense in this case.
I use Caddy to push resources from the backend. To do this conditionally, I use Link header and a little bit of logic in the backend. However, if I understand Caddy's code correctly, it's currently implied that one Link header = one resource. Unfortunately, a lot of backends (e.g. Django) don't really support multiple headers with the same name, limiting http2 push to one resource.
Cloudflare had exactly this problem and solved it by allowing multiple links per Link header: https://blog.cloudflare.com/http-2-server-push-with-multiple-assets-per-link-header/ Do you think it's reasonable to do the same in Caddy?

/cc @wendigo What do you think?

Oh just got this problem too, looks like in Rails it's the same.

Here you go: https://github.com/mholt/caddy/pull/1798/files


Password needs to be encrypted while enabling TLS

Currently while creating certificates for TLS, user is asked to give one password for encrypting the privated key file, but this password can only be stored as clear-text, which may cause risk.
You may check the "searchguard.ssl.transport.pemkey_password" configuration entry for more information.
We expect it can be enhanced as encrypted format. thanks!

I guess the question is how to make elasticsearch.yml free of passwords, right? In that case, the recommendation is to use environment variable substitution:
https://www.elastic.co/guide/en/elasticsearch/reference/current/settings.html

I guess the question is how to make elasticsearch.yml free of passwords, right? In that case, the recommendation is to use environment variable substitution:
https://www.elastic.co/guide/en/elasticsearch/reference/current/settings.html

Hi floragunncom, thank you for reply! It seems environment variables much safer but they are almost the same actually. In case some hacker log in, he is able to open config file and check the clear-text password, he is also able to use echo command to get real value from environment. We are expecting there can be some encryption mechanism for this password, or you can define one interface so that real users can define customized implementation. Please check, thanks  very much!


trace-cmd: documentation fixes.

Following from this discussion:
https://github.com/ARM-software/workload-automation/commit/4d7ef408c97099658a340af4c9ed04154833ee69

Remove reference to default events from the overall workload
documentation. It was, as of recently, outdated, and was also
redundant, as the actual defaults will be in the parameter-specific
documentation.
Remove reference to Android-specific trace-cmd binary -- this was not
true for a long time.
Clarify that the on-host trace-cmd binary is not optional due to the
report_on_target config.
Fix a few misc typos.

LGTM, FWIW


Fixes #69

Fix an issue where the wrong action was being parsed causing total failure in special action profile loading

@SergueiFedorov Im mentioning you because it seems like youre the only other regularly active developer here. Is this project still in development? Does anyone know where Jay is?

@Ryochan7 Forked this project and made quite some changes already. He also merged your fix into his fork.
https://github.com/Ryochan7/DS4Windows

@JarnoVgr Thanks!


Update rust-native-tls and dev-dependencies to latest

rust-native-tls 0.23 is pretty old (2019) and lacks more recent ALPN support, needed for HTTP/2.
Updates some dev-dependencies to latest as well.
Lastly cleans up a compile warning that was seen when running cargo test (probably a new check in recent rustc?)

hello

It's been over a year, the project looks dead.
I've created a separate async-native-tls-alpn crate containing this patch.
I'll leave the PR open in case the project comes back to life, but in the meantime, anyone who is hitting ALPN issues can use that crate.


[WIP] Add support for wasi-http

@achille-roussel as discussed in https://github.com/tetratelabs/wazero/pull/1519 this adds wasi-http support.
This code is very incomplete and hacky, but it is working for limited use cases.
If this integration looks correct-ish, I will polish this up, add tests etc.
Thanks!

Ok, since this looks good, I will push it forward to something that might actually be mergeable (will likely take a few days because of real life)
Will also add the README.md and a test.

@achille-roussel this is now ready for review. I added a simple integration test. The coverage isn't great, but I plan to expand it in future PRs. Let me know if you want me to expand it before this merges.
Thanks!

Thanks for the review. I can squash commits if you want before it merges (or you can squash on merge)

I tagged a v0.7.0 release which includes these changes.


chapter 2 intro page locks on refresh

Pass chapter 1 and write down secret

Advance to chap 2 (see flash of a lock)

Refresh page

Go back to chap 1 outro page, click advance

Chapter 2 is unlocked again

I noticed in our network tab that the account progress is at 'CH1OUT2' after following these steps while localStorage is at 'CH2INT1' @daviroo will #923 resolve this?

I noticed in our network tab that the account progress is at 'CH1OUT2' after following these steps while localStorage is at 'CH2INT1' @daviroo will #923 resolve this?

I think so yes.

Closed by #923


Bump version to 0.3.0

Follows PRs #46 #60, depends on PRs #66 #67 #68.
I think we should release a minor update, because a lot of improvements have been made since last release.
Also, I've fixed Headings should be surrounded by blank lines rule in CHANGES.md.

This should probably be 0.3.0 not 0.2.1 because adding support for multiple systems is a minor change, not a patch or bugfix.

Also, I've fixed Headings should be surrounded by blank lines rule in CHANGES.md.

Where is this rule coming from?

Also, I've fixed Headings should be surrounded by blank lines rule in CHANGES.md.

Where is this rule coming from?

There is a markdown linter (and a plugin for VS Code powered by it, which I'm personally using) and I think it's pretty cool.

Also, I've fixed Headings should be surrounded by blank lines rule in CHANGES.md.

Where is this rule coming from?

There is a markdown linter (and a plugin for VS Code powered by it, which I'm personally using) and I think it's pretty cool.

Okay, I actually kind of disagree with this rule. I think it is better to have the text close to the header that it is associated with. This is a design principle I learned from the book The Non-Designer's Design Book:

The Principle of Proximity states: Group related items together. Move them physically close to each other so the related items are seen as one cohesive group rather than a bunch of unrelated bits.

Okay, I actually kind of disagree with this rule. I think it is better to have the text close to the header that it is associated with. This is a design principle I learned from the book The Non-Designer's Design Book:

The Principle of Proximity states: Group related items together. Move them physically close to each other so the related items are seen as one cohesive group rather than a bunch of unrelated bits.

That's a good point! Both variants look the same after formatting anyway.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@cbbff0c). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #70   +/-   ##
=========================================
  Coverage          ?   78.23%
=========================================
  Files             ?        2
  Lines             ?      147
  Branches          ?        0
=========================================
  Hits              ?      115
  Misses            ?       32
  Partials          ?        0

Flag
Coverage Δ

unittests
78.23% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

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 cbbff0c...e7dd235. Read the comment docs.


Enable dependabot

Objective
Enable dependabot
Why
Dependabot will automatically creates PR when there is new Golang, Docker or Github actions versions.
How

Add .github/dependabot.yml configuration file

Release plan

[ ] Merge this PR
[ ] Check PR after 1 week

#sre


IGAPP-714: Reenable web production delivery

This pull request belongs to an issue on our bugtracker.
You can find it there by looking for an issue with the key which is mentioned in the title of this pull request.
It starts with the keyword IGAPP.

:exclamation: DO NOT MERGE BEFORE 31.08 :exclamation:


Support ScaleMinMax for To<:Integer

Integer-valued images are not generally recommended (deciding contrast is a mess), but it's worth having them work. Note this also improves overflow-safety (for From<:Signed).

Coverage increased (+0.08%) to 75.495% when pulling 200ffe84b8eef59df58ec2d38d41fa428ad16e00 on teh/smm_int into 66a49566cf2a75326e70a7d19b127c7097e45973 on master.

Failure on 0.5 is https://github.com/JuliaLang/julia/pull/15675.


Add ability to set and retrieve "state" during the sign in redirect and callback

New Feature Proposal
For more information, see the CONTRIBUTING guide.
Description
Currently unable to retain original. This is typically solved using the state param on the authorize call, but this is currently hidden behind the setupOidcClient function.
Have spoken to Florian about this briefly and it would be useful to expose this in some way.
Background
When signing into our auth, we lose reference to the location we came from, so we will only ever be able to go to the hardcoded appUri specified in the setupOidcClient call

Thanks for bringing this up and for providing a fix!


[feature request] streaming support

smth like
await response.stream.read(2**8)

(read n bytes, throws EOF)
or at least
await response.content

would be useful
such that response directly includes the response headers & code, but the response content is async
soo similar to how aiohttp works

good idea.


fix: 🐛 (parse) call harness parser

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


feat: add from_device_and_advertisement_data classmethod to BluetoothServiceInfoBleak

This is a convenience method to make code a bit more DRY

thanks


Expanding the functionality of the App Bar and Navigation Bar

I propose to expand the functionality of these components:

Add a color change to the App Bar and Navigation Bar. if there are elements behind. If there are no elements behind, then there will be a background color, and if you start scrolling, the color of the components will change to another.

https://github.com/user-attachments/assets/2b84ba04-534f-431c-8e23-3afb21af9f37

Add an option to the App Bar with a large title that will hide when scrolling.

https://github.com/user-attachments/assets/afce04ca-bfa3-4327-ba46-11d0f2d0d81f

Add the ability to hide when scrolling to the App Bar and Navigation Bar.

https://github.com/user-attachments/assets/4eceda30-61b4-4f32-966a-6b17992df217
I understand if this suddenly violates the library's design principles and you don't want to add this feature.

I can add this, but as Sliver components (the one you put under CustomScrollView/NestedScroll) rather than Scaffold child. Scaffold was never meant to have a fancy scroll effect.


Libffi not found in Vagrant when trying to install plugins

Issue description
I am trying to install two plugin in vagrant: vagrant-bindfs and vagrant-hostmanager.
I install them with the normal vagrant workflow, but it fails in both case with the following error:
...
An error occurred while installing ffi (1.9.13), and Bundler cannot continue.
Make sure that `gem install ffi -v '1.9.13'` succeeds before bundling.

Warning: this Gemfile contains multiple primary sources. Using `source` more than once without a block is a security risk, and may result in installing unexpected gems. To resolve this warning, use a block to indicate which gems should come from the secondary source. To upgrade this warning to an error, run `bundle config disable_multisource true`.Gem::Ext::BuildError: ERROR: Failed to build gem native extension.

    /nix/store/cfagzvhnhh4hql3pg8x9nx6ds135aa1l-vagrant-1.8.1/opt/vagrant/embedded/bin/ruby -r ./siteconf20160710-22557-czop3m.rb extconf.rb
checking for ffi.h... *** extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of necessary
...

Manually checking the store, ls /nix/store/cfagzvhnhh4hql3pg8x9nx6ds135aa1l-vagrant-1.8.1/opt/vagrant/embedded/lib/, there is a libffi folder containing the headers ( /nix/store/cfagzvhnhh4hql3pg8x9nx6ds135aa1l-vagrant-1.8.1/opt/vagrant/embedded/lib/libffi-3.0.13/include/ffi), it seems that Vagrant does not know where to look for it's embedded headers.
Steps to reproduce
$ nix-env -iA nixos.vagrant
$ vagrant plugin install vagrant-bindfs
ERROR
$ vagrant plugin install vagrant-hostmanager
ERROR

Technical details

System: NixOS: 16.09pre85931.125ffff (Flounder)
Nix version: nix-env (Nix) 1.11.2
Nixpkgs version: "16.09pre85931.125ffff"

confirming on current master, on 16.03; works fine on 15.09


Unacceptable breaking changes without a major version increment !!!

Come on @sethvargo - how on earth are we going to maintain a stable chef ecosystem without being able to rely on pessimistic cookbook version matching to prevent breaking changes in cookbooks from bringing down our infrastructure !?!?!
If you need to release a breaking change, please bump the major version so we can rely on '~> 3.0.0' or even '~> 3.0' not breaking an otherwise stable chef converge.

Are you serious right now? Did you even read the changes?
In the future, please consider being less of a jerk. Thanks! :smile:

I appreciate that you are pissed at chef right now for trampling over chef-sugar without warning, however what's the point of talking about semantic versioning and having concepts like pessimistic version matching if people don't stick to it.
In an international corporate environment, providing a service to customers, we need to maintain a stable enterprise-quality environment and have to be able to rely on things like pessimistic version matching to avoid breaking changes affecting our systems.
We haven't moved up to chef-client 12 yet, with a lot of our estate not even up to 11.16.4 ! Before you released your breaking change this afternoon, all our servers were quite happy, blissfully unaware of any chef12 issues. Now however, because we make extensive use of compile_time from chef-sugar, we are faced with updating a number of library cookbooks, rebuilding and testing new versions of ten times as many application cookbooks,  and then the associated environment cookbooks and managing the deployment of the new cookbooks via exponentially more chef environments !!!
So I don't consider myself being a jerk, just highlighting to you the unnecessary impact you have caused by releasing a breaking change and not sticking to semver.

@robcoward Why haven't you pinned your version of chef-sugar? Are you using any community cookbooks as well that implement compile_time (with or without respond_to? checks)? If not, I think you'll be safe by pinning your version of chef-sugar to 3.0.0. If you are, you probably should make sure you've pinned those cookbooks to versions that don't implement compile_time in any chef_gem resources.

@robcoward
Okay, let's back up. First of all, I'm not "pissed" at Chef. Let's get that out of the way... I am angry with you as a human being. You have absolutely no entitlement to speak to or treat someone with the complete lack of dignity and respect you have demonstrated here. No one! Even more-so, you have no right to degrade or insult the people who provide you with free and open source software. None. Zero.
If you do not like Chef Sugar, then don't use it. I promise you, my feelings will not be hurt if you choose to use an alternative. I enjoy participating in healthy and happy communities. Your attitudes and actions compromise those very values, and I would strongly encourage you to reconsider your attitude, words, and actions towards others in the Chef community as this type of language and behavior is generally not tolerated (/cc @nathenharvey).
As representative of @nvmlabs (and @aunitt), you have portrayed your organization in a very negative light. You have verbally attacked the maintainer of software you use, and to what end? Do you feel better? Others are not the punching bags for your personal frustration. While I am sorry that you are frustrated and upset, I am not sympathetic to the attitude, actions, or words you have demonstrated here.
Nonetheless, I am still going to try and help you. Nothing is actually broken. If you are still on Chef 11.16.4, then Chef Sugar v3.0.1 is not breaking anything for you. For example, given the following recipe:
include_recipe "chef-sugar::default"

compile_time do
  chef_gem "pry"
end

The output is as follows:
-----> Starting Kitchen (v1.3.1)
-----> Converging <default-ubuntu-1204>...
       Preparing files for transfer
       Preparing dna.json
       Preparing current project directory as a cookbook
       Removing non-cookbook files before transfer
       Preparing solo.rb
-----> Chef Omnibus installation detected (11.16.4)
       Transferring files to <default-ubuntu-1204>
       Starting Chef Client, version 11.16.4
       Compiling Cookbooks...
       Recipe: chef-sugar::default
         * chef_gem[chef-sugar] action nothing (skipped due to action :nothing)
         * chef_gem[chef-sugar] action install (up to date)
       [2015-03-20T20:51:40+00:00] WARN:
       The Chef Sugar recipe DSL method `compile_time' has been renamed to
       `at_compile_time'! This is a breaking change that was released in a patch
       version, so please continue reading to understand the necessary semantic
       versioning violation.

       Despite having existed since October 15, 2013 (b4d4c0e) and being one of the
       most widely used cookbooks in the Chef ecosystem, Chef Software decided to
       implement their own version of `compile_time' in Chef 12.1, breaking any cookbook
       that uses or depends on Chef Sugar on Chef 12.1:

           https://www.chef.io/blog/2015/03/03/chef-12-1-0-released

       As is common with Chef-ecosystem tooling, no warning was given, and maintainers
       are left to pick up the pieces from upset Chef users who get rather bespoke
       error messages now:

           https://github.com/sethvargo/chef-sugar/issues/89
           https://github.com/opscode-cookbooks/xml/issues/22
           https://github.com/opscode-cookbooks/aws/pull/110

       In order to progress Chef Sugar forward, the DSL method has been renamed to
       avoid the namespace collision.

       In short, you should change this:

           compile_time do
             # ...
           end

       to this:

           at_compile_time do
             # ...
           end

       You are running a version of Chef Client that does not include the
       `compile_time' attribute on core Chef resources (most likely less than
       Chef 12.1), so this is just a warning. Please consider changing the Chef Sugar
       `compile_time' method to `at_compile_time' in your Chef recipes. If you upgrade
       Chef, your recipes WILL break.

         * chef_gem[pry] action install (up to date)
         * chef_gem[pry] action install (up to date)
         Converging 2 resources
         * chef_gem[chef-sugar] action nothing (skipped due to action :nothing)
         * chef_gem[pry] action nothing (skipped due to action :nothing)

       Running handlers:
       Running handlers complete
       Chef Client finished, 0/3 resources updated in 1.076749541 seconds
       Finished converging <default-ubuntu-1204> (0m3.40s).

Notice the "WARN"? It does not say "ERROR" it does not say "FATAL", it says warn. Meaning this is a warning.
Following that, the output shows:
         * chef_gem[pry] action install (up to date)
         * chef_gem[pry] action install (up to date)

Those lines indicate your previous code is working as it previously did. I believe the warning output is very clear:
You are running a version of Chef Client that does not include the
`compile_time' attribute on core Chef resources (most likely less than
Chef 12.1), so this is just a warning. Please consider changing the Chef Sugar
`compile_time' method to `at_compile_time' in your Chef recipes. If you upgrade
Chef, your recipes WILL break.

We haven't moved up to chef-client 12 yet, with a lot of our estate not even up to 11.16.4 !

That's great! As I demonstrated here, nothing is broken! Your Chef Client runs are going to have a bit more output, but that's it.

Before you released your breaking change this afternoon, all our servers were quite happy, blissfully unaware of any chef12 issues.

Are you actually experiencing issues or are you assuming you are going to have issues by reading the changeset? I cannot get Chef Sugar to error on Chef 11.x - I tested literally every released version. Perhaps if you are using Chef Sugar internals as a library, you may experience issues, but relying on the internals of a gem is never safe. The public API is clearly documented and anything outside of that API is considered unsafe.

Now however, because we make extensive use of compile_time from chef-sugar, we are faced with updating a number of library cookbooks, rebuilding and testing new versions of ten times as many application cookbooks, and then the associated environment cookbooks and managing the deployment of the new cookbooks via exponentially more chef environments !!!

A few things:

When you end a sentence in !!!, it sounds like you are yelling, much like when someone writes in ALL CAPS. It conveys emotions of anger making it very difficult for others to share empathy in your words.
As I have demonstrated above (and for the record - this is something I tested prior to releasing the new version) - Chef 11.x's behavior is unaffected by this new version. It behaves exactly the same as before, just outputting a warning message that, when you upgrade to Chef 12, you are going to have a bad day unless you make some changes first.

In closing, I am sorry this might have caused you issues. I hope you will re-consider your tact and approach when speaking to others in the future.

The Chef Community Guidelines include the following:

Be welcoming, inclusive, friendly, and patient.
Be considerate.
Be respectful.
Be professional.
Be careful in the words that you choose.
When we disagree, let’s all work together to understand why.

There's clearly a disagreement here and I would love to help understand why there's disagreement and see if there's a way that it can be resolved.
Issues, bugs, and breaking changes are to be expected with any software.  Can we work together to make sure that we can make dealing with those things easier?
How can I help?

@sethvargo, i apologise if the exclaimation marks come across as shouting. After 2 decades of working in the  industry, it still frustrates me when software updates are released late on a friday, just before everyone disappears for the weekend, leaving systems broken unless someone stays late to sort them out. In a traditional release management scenario, that's poor process management, however in the brave new world of automation the lines are a little more blurred.
@jtimberman we do use the environment cookbook pattern to control cookbook deployments through our software delivery pipeline, so we do have explicit versions
pinned on our servers, however in our application and llibrary cookbooks we only use pessimistic constraints so we can automatically benefit from minor releases and bug fixes with some comfort that semver versioning on community cookbooks wouldn't introduce a breaking change - we expect that depends 'some-cookbook', '~> 3.0.0' should be sufficient.
What broke this afternoon was our CI builds running test-kitchen against cookbook changes, where berkshelf pulled in the new release of chef-sugar since the pessimistic constraint was still satisfied. It was one of my collegues that was investigating the failures, so i only heard 2nd hand that chef-sugar had been updated and that was what was causing the test-kitchen converge to fail. I dont have access to our jenkins server atm, so i will have to wait until monday morning to dig out the logs and take a look for myself.
What concerned me was the comments in the changelog when i looked, describing a breaking change, with a key resource being renamed and comments about a verbose error message, yet the major version was not bumped. Seeing @sethvargo 's kitchen output however, it seems our kitchen failures need further investigation.

@robcoward you are pinning the chef-client itself.  why are you not equality pinning the chef-sugar version in production?  if you have production servers which are auto updating themselves with no oversight and no testing pipeline that will always end badly.


Volumetric terrain

Store/generate/modify terrain with volumetric data structures (something voxel-ish).

Based on this article and some thinking, I'm thinking we treat everything as a contiguous volum. We store a sparse voxel octree, where is either entirely inside or entirely outside the volume, or it contains a single surface vertex and a record of where the surface intersects the edges. If the surface intersects an edge, all the cubes adjacent to that edge (four of them) intersect the surface, too, so we generate four triangles using the four cubes' vertices and the intersection point of the edge.

WIP on the voxel branch.

Moving the pre-volumetric terrain to the pre-svo branch, merging the voxel branch into master, and moving leftover list items into separate issues.


Supplementing the article regarding semi-active pendulation attenuator with comments (#239 related) - substantive remarks

Substantive remarks

[x] In Eq. (2) and (3), it is not clear why the initial mass of the lower pendulum member is included. Some explanation is required.
[x] How this technology could be employed in practice. A better description of how the device could practically function is required.
[x] Frequency sweeps analysis - a sufficiently fine resolution then draw conclusions about whether resonance is controlled.
[x] In Fig. 7, why are the spectra shown not smooth? This suggests that the simulations were not at steady-state? Moreover, why has the peak frequency shifted when damping was added?
[x] Are the "frequency spectra" actually "power spectra"? If so, the labeling and units of the vertical axis are incorrect. If not, what are they showing? What is the purpose of showing power spectra if the system is excited at a single frequency?
[x] The authors must describe why the second peak at 1Hz was not shown in the experimental work.
[x] What is the purpose of studying the initial conditions of the system? These are transients that are not of great importance to the dynamic response of a system since they "die out" quite rapidly. It seems these comparisons should be omitted for brevity.
[x] After Fig. 6, what does "asymptotic stability (lack of the amplitude overloading)" mean?

Done.


add the notification and auto update the thread page without loading?

Can add the event handling of laravel for notification when the thread update in top of the like GitHub bell icon.
and also add the feature of auto update the thread when any user add the new reply without loading the page in real time.

Are you asking if it is possible to implement that or if we can do that? haha
Either way, it is possible, but not sure if it gets implemented soon by any of the developers. So if you could work on that, that'd be great 👍

@tjnapster555 You can listen for "ChatterAfterNewResponse" and then catch all users relations based on discussion id, and notify them.
https://laravel.com/docs/5.4/events#registering-events-and-listeners
https://laravel.com/docs/5.4/notifications


Fix Issue #244 where categories are not being handled properly when collapsed and moving from month to month.

Thank you!


Create Era5 object with netCDF file already downloaded

This function is based on the feedback from Kevin. Two possible solutions:

Follow the gridmet component implementation that can load files in cache instead of repeating the data download process.
Change the code for Era5 class in bmi_era5 to enable loading the data from an existing netCDF file.

This is implemented in release 0.1.4


Fix Kconfig

Note: Please adhere to Contributing Guidelines.
Summary
Minor typo in KConfig that result in
libs/libc/string/Kconfig:44: syntax error
libs/libc/string/Kconfig:43: unknown option "--help--"
libs/libc/string/Kconfig:44: unknown option "Use"

Impact
None
Testing
None

Duplicated https://github.com/apache/nuttx/pull/14388


RangePicker在禁用了开始时间后，开始时间还可以编辑， 官网上的禁用例子就可以复现。

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

Basic Info

Package Name And Version<EMAIL_ADDRESS>Browser: chrome<IP_ADDRESS>


V4.7.1 no  RMQ_SYS_TRACE_TOPIC

V4.7.1 no  RMQ_SYS_TRACE_TOPIC  var

@andyhewenhui The new version has enhanced the management and control of system topics, please refer to org.apache.rocketmq.common.topic.TopicValidator#RMQ_SYS_TRACE_TOPIC


Code Fix- Insecure URL & Tokens

in reference to #325 #326 #327

@all-contributors please @EitoZX for Security

@all-contributors please DD @EitoZX for Security

@all-contributors please ADD @EitoZX for Security


Enable PRC by default in AWS

Enables PlanResourceChange by default in pulumi-aws.
Part of https://github.com/pulumi/pulumi-terraform-bridge/issues/1785
Also has a few test fixes.

This got merged on the main branch.


Smooth Scroll doesn't work in Firefox 54

I'm using this .js in an Angular 4 app. It works well in all the browsers except in Firefox 54. In that version is has no scroll.
document.getElementById('foo').scrollIntoView({ behavior: 'smooth' });
This is an example of code that I'm using.
Please suggest any fix or workaround.
Thank you.
[EDIT]
So the issue seems to disappear if we don't have the following instruction in the same "scope" of the previous one:
window.scroll(0, window.scrollY - 50);
(we did this to adjust the position after the scroll).
So to be clear: if we have both instructions, there is no scroll at all... if only the first one exists, then we have a smooth scroll.
That being said, I'm not sure if this is a bug related to your polyfill but it's worth checking out I think.
Thank you

Since Firefox supports smooth scrolling, this library doesn't do anything in Firefox. That said, I've noticed that the polyfill is way better than Firefox's implementation and I'd be interested in having a way to always use the polyfill even in Firefox. I tried searching for a relevant Firefox Bugzilla bug but I'm having trouble finding a good search term.

Have you tested this without including the polyfill in your bundle? As @crccheck said, the polyfill does nothing in Firefox since native support is detected.

Yes, the behaviour that I described only happens with the polyfill added to the bundle...

I confirm that in Firefox 54 and 55 the polyfill doesn't do anything. So closing this.


Standardise instance count

Goal
Standardise the number of instances between:

the instances in generate_tilesets.py.
the instances in COCO files.
the instances in assess_model.py.

How

First, I chose to clip and explode the labels with the tiles before splitting the label parts into the different datasets in generate_tilesets.py. This gives the same distribution of instances as in the COCO files.
Second, to remain consistent, I also exploded the clipped labels with the tiles in assess_model.py. This seems to lower the recall.

This is open to discussion!

I tested again and the variation in metrics is negligible. So it's ok for me if you modify line 443.

I probably mixed up some files and it changed the metrics.


Question: Using dataloader-sequelize with multiple databases

Hi,
I am having an application which is having multiple databases, with same schema structure. When a request arrives based on the user, we resolve it to the right database models dynamically.
Is there any examples on switching the data loader context dynamically.

Created a ticket on graphql-sequelize repo
https://github.com/mickhansen/graphql-sequelize/issues/683


checkov: 3.2.42 -> 3.2.43

Diff: https://github.com/bridgecrewio/checkov/compare/refs/tags/3.2.42...3.2.43
Changelog: https://github.com/bridgecrewio/checkov/releases/tag/3.2.43
Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

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

2 packages built:

checkov
checkov.dist


Transaction list getting Frozen

Some problem with re-renders in transaction list... when syncing.

This is already fixed.


Hitting the 'Debug Cell' option can not stop at the breakpoint.

Environment data

VS Code version: 1.79.2
Jupyter Extension version (available under the Extensions sidebar): v2023.5.1101742258
Python Extension version (available under the Extensions sidebar): v2023.10.1
OS (Windows | Mac | Linux distro) and version: Windows 10
Python and/or Anaconda version: Python 3.9.13, Anaconda 2022.10.
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): conda
Jupyter server running: N/A
ipykernel version: 6.15.2

Expected behaviour
After hitting the 'Debug Cell' option, the code should stop at the breakpoint.
Actual behaviour
After hitting the 'Debug Cell' option, the code just run and run.
Steps to reproduce:

Logs

Output for Jupyter in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Jupyter)

17:04:28.002 [info] Started Kernel base (Python 3.9.13) (pid: 22280)
17:04:28.002 [info] Started new session e4d47585-6118-4878-a9a4-ac770546ca39
17:04:28.002 [info] Shutdown old session 6cab9445-81b8-40ed-808c-b3d873567429
17:04:28.002 [info] Dispose Kernel process 21316.
17:04:28.013 [info] Process Execution: c:\WINDOWS\System32\taskkill.exe /F /T /PID 21316
17:05:37.361 [info] Handle Execution of Cells 0,1 for d:\Nut_store\paper\Computational Neuroscience, AI, ML, DL, RL\power law and scale invariance\have a try\code\main.ipynb
17:05:37.415 [info] Kernel acknowledged execution of cell 0 @<PHONE_NUMBER>365
17:05:44.246 [info] End cell 0 execution @<PHONE_NUMBER>243, started @<PHONE_NUMBER>365, elapsed time = 6.878s
17:05:44.257 [info] Kernel acknowledged execution of cell 1 @<PHONE_NUMBER>247
17:05:44.313 [info] End cell 1 execution @<PHONE_NUMBER>273, started @<PHONE_NUMBER>247, elapsed time = 0.026s
17:05:52.631 [info] Starting debugging with mode 1
17:05:54.076 [info] Handle Execution of Cells 2 for d:\Nut_store\paper\Computational Neuroscience, AI, ML, DL, RL\power law and scale invariance\have a try\code\main.ipynb
17:05:54.092 [info] Kernel acknowledged execution of cell 2 @<PHONE_NUMBER>082
17:05:54.993 [error] Jupyter Extension (Error in requestVariables, method:requestVariables): Error [CodeExpectedError]: Traceback (most recent call last):
  File "<string>", line 1, in <module>
NameError: name '_VSCODE_getVariable' is not defined

    at e.RawDebugSession.P (vscode-file://vscode-app/d:/Public/20230215_VS_code/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:903:45017)
    at vscode-file://vscode-app/d:/Public/20230215_VS_code/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:903:44511
17:05:57.429 [error] Jupyter Extension (Error in requestVariables, method:requestVariables): Error [CodeExpectedError]: Thread id: pid_22280_id_2873526749408 is not current thread id.
    at e.RawDebugSession.P (vscode-file://vscode-app/d:/Public/20230215_VS_code/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:903:45017)
    at vscode-file://vscode-app/d:/Public/20230215_VS_code/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:903:44511

This problem may have the same cause as https://github.com/microsoft/vscode-jupyter/issues/8258.

https://github.com/microsoft/vscode-jupyter/pull/8335 claimed to fix https://github.com/microsoft/vscode-jupyter/issues/8258, but I still get this problem now. (My Windows user name is longer than 8 characters)

I solved this issue by creating a new virtual environment. Hope it helps.

Hi, I don't understand why creating a new virtual environment will help this, but I will try.

Closing this issue as its been over 4 weeks, since the information was requested.
We'll be happy to reopen the issue when the requested information has been provided.

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Site still refers to August 2021 stable release

https://github.com/sigstore/sigstore-website/blob/main/content/story/info.json
and
https://github.com/sigstore/sigstore-website/blob/main/components/textBanner.vue
both refer to Sigstore 1.0 release on August 2021 but other parts of the page still refer to Sigstore in beta. I know some stuff is 1.0 and a few things are almost 1.0 but might be worthwhile to clarify?

I looked at project releases today and the plan for sigstore GA is part of this board.
Given that is still beta, I think it would make sense to change it to stable release due soon and link to the GA board (or a GA tracking issue). @lukehinds what do you think?

@priyawadhwa fyi

thanks @k4leung4 !


update to v3.0.1, adding unittest

adding tests to meta.yml
See https://github.com/ihesp/IPART/issues/5#issuecomment-679213870

Checklist

[x] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


[BUG][Typescript] Children element type is not found on List, Edit, Show,Create component

Hi,
I use the examples described in the tutorial. I get this typescript error on all components.
Typescript error is;
List
Type '{ children: Element; }' has no properties in common with type 'IntrinsicAttributes & ListProps'.
Create
Type '{ children: Element; saveButtonProps: Partial<{ href: string; target?: string | undefined; onClick?: MouseEventHandler<HTMLElement> | undefined; } & BaseButtonProps & Omit<...> & { ...; } & Omit<...>> & { ...; }; }' is not assignable to type 'IntrinsicAttributes & CreateProps'.   Property 'children' does not exist on type 'IntrinsicAttributes & CreateProps'.
Edit
Type '{ children: Element; saveButtonProps: Partial<{ href: string; target?: string | undefined; onClick?: MouseEventHandler<HTMLElement> | undefined; } & BaseButtonProps & Omit<...> & { ...; } & Omit<...>> & { ...; }; }' is not assignable to type 'IntrinsicAttributes & EditProps'.   Property 'children' does not exist on type 'IntrinsicAttributes & EditProps'.
Show
Type '{ children: Element[]; isLoading: boolean; }' is not assignable to type 'IntrinsicAttributes & ShowProps'.   Property 'children' does not exist on type 'IntrinsicAttributes & ShowProps'.
I use
"@pankod/refine-antd": "^3.27.0",
"@pankod/refine-core": "^3.36.0",
"@pankod/refine-react-router-v6": "^3.25.2",
"@pankod/refine-simple-rest": "^3.25.6",
"@pankod/refine-strapi-graphql": "^3.25.8",
"@testing-library/jest-dom": "^5.16.4",
"@testing-library/react": "^13.3.0",
"@testing-library/user-event": "^13.5.0",
"@types/jest": "^27.5.2",
"@types/node": "^16.11.41",
"@types/react": "^18.0.14",
"@types/react-dom": "^18.0.5",
"react": "^18.2.0",
"react-dom": "^18.2.0",
"react-scripts": "5.0.1",
"typescript": "^4.7.4",
"web-vitals": "^2.1.4"

Hey @emehmet ,
Thank you for contacting us. A similar issue has been opened before, can you check here for details?

https://github.com/pankod/refine/issues/1839#issuecomment-1138177075

When I downgrade to React In 17.0.2, this time I am getting error in code.
import ReactDOM from 'react-dom/client'; in index.tsx
React is being imported with its latest version
create-react-app installs the code accordingly.
This detail should be explained in the documents until the transition to React@18

Thank you, we will publish our react@18 support soon.
for now, it may be easiest to use superplate-cli


materialize: 0.9.4 -> 0.10.0

Motivation for this change
Update materialize to latest version
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

If someone more knowledgeable looks at this, is there a way to avoid skipping tests that use the network in a nix derivation? The tests are just spinning up a server listening on localhost and test communication


Add support for custom_score

Would be nice if there was a way to set the custom_score property for a query.  This allows for some pretty complex result ordering that is useful for a lot of applications.

Jason, do you mean the custom_score query?

Yes sir.
On Oct 25, 2011, at 12:55 AM, Karel Minarik
<EMAIL_ADDRESS>wrote:

Jason, do you mean the custom_score query?
--
Reply to this email directly or view it on GitHub:
https://github.com/karmi/tire/issues/133#issuecomment-2513056

Should be easy to add, it's a straight-forward patch a la https://github.com/ralph/tire/commit/c2b496c, anybody got 20mins to do it? :)

Hi,
I take it

Great, Paco!

I'm getting the following error throwing the next query:
curl -X GET "http://localhost:9200/articles-test/_search?pretty=true" -d '{"custom_score":{"query":{"query_string":{"query":"title:T*"}},"script":"_score * doc['words'].value"}}

[2011-10-25 22:38:33,312][DEBUG][action.search.type       ] [Torrent] [articles-test][3], node[qxUNFpjMSR2wgWa8_4UH7A], [P], s[STARTED]: Failed to execute [org.elasticsearch.action.search.SearchRequest@9e5e21]
jvm 1    | org.elasticsearch.search.SearchParseException: [articles-test][3]: from[-1],size[-1]: Parse Failure [Failed to parse source [{"custom_score":{"query":{"query_string":{"query":"title:T*"}},"script":"_score * doc['words'].value"}}]]
jvm 1    | 	at org.elasticsearch.search.SearchService.parseSource(SearchService.java:495)
jvm 1    | 	at org.elasticsearch.search.SearchService.createContext(SearchService.java:407)
jvm 1    | 	at org.elasticsearch.search.SearchService.executeQueryPhase(SearchService.java:230)
jvm 1    | 	at org.elasticsearch.search.action.SearchServiceTransportAction.sendExecuteQuery(SearchServiceTransportAction.java:134)
jvm 1    | 	at org.elasticsearch.action.search.type.TransportSearchQueryThenFetchAction$AsyncAction.sendExecuteFirstPhase(TransportSearchQueryThenFetchAction.java:80)
jvm 1    | 	at org.elasticsearch.action.search.type.TransportSearchTypeAction$BaseAsyncAction.performFirstPhase(TransportSearchTypeAction.java:205)
jvm 1    | 	at org.elasticsearch.action.search.type.TransportSearchTypeAction$BaseAsyncAction.performFirstPhase(TransportSearchTypeAction.java:192)
jvm 1    | 	at org.elasticsearch.action.search.type.TransportSearchTypeAction$BaseAsyncAction$2.run(TransportSearchTypeAction.java:178)
jvm 1    | 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
jvm 1    | 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
jvm 1    | 	at java.lang.Thread.run(Thread.java:679)
jvm 1    | Caused by: org.elasticsearch.search.SearchParseException: [articles-test][3]: from[-1],size[-1]: Parse Failure [No parser for element [custom_score]]
jvm 1    | 	at org.elasticsearch.search.SearchService.parseSource(SearchService.java:481)
jvm 1    | 	... 10 more

I'm not pretty sure whats going on
Any thoughts?
I think you could test it importing the articles fixtures

You need to wrap custom_score in query{ }

Hi,
Maybe you could take a look to #139 , my first attempt to try to resolve this one. Excuse me but I don't know how to related that issue with this ;)
Any comments?
I'd tried to avoid the use of a query block inside the custom_score block
search = Item.search page: 1, per_page: 30 do
  query do
    custom_score script: "random()" do
      query { string "title:T*" }
    end
  end
end

And simply we can do
search = Item.search page: 1, per_page: 30 do
  query do
    custom_score script: "random()" do
      string "title:T*"
    end
  end
end

Everything inside the custom_score block is execute in a new query object context

Interesting idea.  Being able to pass parameters into the script would be very useful though.  Sure you could insert args in the script string, but then ES has to recompile the script each time it's different.  Doing it the way described in the ES docs is more efficient.

@jfalk: The beauty of ES's API and Paco's implementation is that passing parameters to scripts is already working, see examples in the last referenced commit.


[Question] New to PromiseKit, went through the docs and not sure what I'm doing wrong.

Please specify the PromiseKit major version you are using
6.13.1

[Please format your code in triple backticks and ensure readable indentation]

func requestRedditListings(url: URL) -> Promise<[RedditListingItem]> {
        return Promise { seal in
            firstly {   <-- 2(i) Generic parameter 'T' could not be inferred
                getRedditToken() <-- Cannot convert value of type 'Promise<String>' to closure result type 'Guarantee<T>'
            }.then { (token) in
                var request = URLRequest(url: url)
                let requestHeaders: [String:String] = ["Authorization": "Bearer \(token)"]
                request.allHTTPHeaderFields = requestHeaders
                URLSession.shared.dataTask(.promise, with: request).compactMap { (data: Data, response: URLResponse) in
                    try! JSONDecoder().decode(RedditListingParent.self, from: data)
                }
            }.done { (listings) in
                seal.fulfill(listings.data.children)
            }.catch { (error) in
                print(error)
            }
        }
    }

Please specify how you installed PromiseKit, ie. Carthage, CocoaPods, SwiftPM or other. If other provide DETAILED information about how you are integrating PromiseKit.
SwiftPM and using PMKFoundation 3.3.4

If you ignore this template we will close your ticket and link to this template until you provide this necessary information. We cannot help you without it.

I arrived at this based on rereading the knowledge base. I would apprecaite if someone can guide me if I'm on the right track
    func requestRedditListings(url: URL) -> Promise<[RedditListingItem]> {
        return Promise { seal in
            firstly {
                getRedditToken()
            }.done { (token) in
                var request = URLRequest(url: url)
                let requestHeaders: [String:String] = ["Authorization": "Bearer \(token)"]
                request.allHTTPHeaderFields = requestHeaders
                URLSession.shared.dataTask(.promise, with: request).compactMap { (data: Data, response: URLResponse) in
                    return try! JSONDecoder().decode(RedditListingParent.self, from: data)
                }.done { (listings) in
                    seal.fulfill(listings.data.children)
                }.catch { (error) in
                    print(error)
                }
            }.catch { (error) in
                print(error)
            }
        }
    }

What errors do you see now?

Nothing it is function but in the knowledge base it recommands me to use am inline function wrapped in a promise. So wondering if I should do that or is it good as it is.


predict() function in Sequence() missing with version installed with pip

Problem
I installed anago with pip install (version 1.0.8) on AWS node. The predict() function in Sequence() is missing, but it is present in the master branch codes. Could you add it to the pip version?

You can simply download master branch codes. Copy all the python files in anago\anago and replace the python files in your pip directory for anago.
eg. C:\Users<user name>\Anaconda3\envs<env name>\Lib\site-packages\anago

Same problem with version 1.0.0. Could you fix that problem? @Hironsan

I've run into the same kind of problem.
The problem with the version. @Alaska47 helped me with this
pip install git+https://github.com/Hironsan/anago.git


Cannot use _open_to() or children() when using URLs as selector ids

jstree v3.2.1
When using DOM elements that have URLs as selector ids
example DOM:

clinical history

The jstree code:
var firstSuggClassVal = 'http://purl.obolibrary.org/obo/OGMS_0000015';
 $('#jst_classr').jstree(true)._open_to(firstSuggClassVal).focus();

Fails with:
TypeError: $('#jst_classr').jstree(true)._open_to(firstSuggClassVal).focus is not a function. (In '$('#jst_classr').jstree(true)._open_to(firstSuggClassVal).focus()', '$('#jst_classr').jstree(true)._open_to(firstSuggClassVal).focus' is undefined)
This fails in the same way:
$('#jst_classr').jstree(true).get_node(firstSuggClassVal, true).children('.jstree-anchor')[0].focus();

There is no such thing as an URL selector - jstree will be very forgiving about ID format but you still need to be careful when specifying IDs - there are a many problems and invalid characters when using an URL as an ID. Sorry - you will just have to use cleaner IDs. Still I will have a look and determine exactly why this ID fails and do further escaping, but I do not consider this to be a jstree bug.
Best regards,
Ivan

Hi Ivan,
I've tried escaping all the special characters in the URL but Jstree still complains.
J

Hi Ivan, I cannot get any form of this to work.  Do you actually have a working example of moving a selected jstree element into view using scrollintoview, scrollto, scrolltop, focus, or one of the other approaches? I think the world would like to see it.  :-)

Notice to the world: while not perfect, this example works in FireFox, Chrome and Explorer 11 . Probably using scrolltop can give better results.

Do you have a jsfiddle demonstrating the functionality?

Yes I put the link in the post but (???) it go lost... http://jsfiddle.net/k0mkhfpm/1/

Thanks. I modified your Fiddle to use URLs as CSS ids and now I can't get it to work:
Yours (works):  http://jsfiddle.net/slimandslam/2v5ybp28/
Here's my forked version with URLs as ids and my attempt to make it work:
http://jsfiddle.net/slimandslam/p524dpuq/
Any ideas?  Ivan?

I figured out an answer:   https://groups.google.com/forum/#!topic/jstree/SjKrt25YS4s


feat:  introduce ElectionClient trait for meta

I hereby agree to the terms of the Singularity Data, Inc. Contributor License Agreement.
What's changed and what's your intention?
This section will be used as the commit message. Please do not leave this empty!
This PR introduces ElectionClient, where run_once executes an available campaign, which  will keep blocking if it runs normally, and when it returns normally, it represents a leader lost.
Checklist

[x] I have written necessary rustdoc comments
[x] I have added necessary unit tests and integration tests
[x] All checks passed in ./risedev check (or alias, ./risedev c)

Documentation
If your pull request contains user-facing changes, please specify the types of the changes, and create a release note. Otherwise, please feel free to remove this section.
Types of user-facing changes
Please keep the types that apply to your changes, and remove those that do not apply.

Installation and deployment
Connector (sources & sinks)
SQL commands, functions, and operators
RisingWave cluster configuration changes
Other (please specify in the release note below)

Release note
Please create a release note for your changes. In the release note, focus on the impact on users, and mention the environment or conditions where the impact may occur.
Refer to a related PR or issue link (optional)

Blocked by missing APIs in madsim etcd simulator. I'll fix them soon.

This PR already works, but it will make the meta start a few seconds longer, which will cause some problems with deterministic testing, I'm still working on it, and it will be ready when it's solved.

Related fixes on etcd simulator:

https://github.com/madsim-rs/madsim/pull/98
https://github.com/madsim-rs/madsim/pull/101
https://github.com/madsim-rs/madsim/pull/102

Hey @shanicky, let me know when this PR is ready for review. I think this is really important work and I would like to support you with it :)

Why did this PR delete all of the tests introduced in https://github.com/risingwavelabs/risingwave/pull/6937

Why did this PR delete all of the tests introduced in https://github.com/risingwavelabs/risingwave/pull/6937?
Shouldn't we add back equivalent tests for those deleted? @shanicky

The previous test was used for the original kv mode election and had some problems, so it was removed, this pr introduces a simple madsim-based simulation test, and more simulation tests will be added after the meta client is complete

Hey @shanicky,
I agree that using the simulation test is the superior approach, however should we maybe add/keep unit tests as well? Those may make it simpler to discover issues straight away. Sometimes finding the reason why a sim test failed is quite hard.

The simulation test is easy to reproduce the problem because of madsim


Ruff complains wrongly when we delete a variable in a function ( F821 )

Hi, Ruff raises an issue with the following code snippet, even when the code is running fine. Could you please fix this issue ?
MyHost :: adlakha$ ruff test.py
test.py:10:19: F821 Undefined name `ABC_123`
Found 1 error.

Code Snippet for reproducing the bug:
def abc():
    global ABC_123
    global XYZ_123

    class ABC_123():
        pass

    class XYZ_123():
        def inputs(self):
            yield ABC_123

    print(XYZ_123().inputs())

    del ABC_123
    del XYZ_123

abc()

Command invoked:
ruff <name-of-the-file>

Ruff version - 0.1.6

This likely won't be fixed in the near future since it requires tracing the function calls themselves -- i.e., we need to know that inputs() wasn't called after the variable was deleted, as in:
def abc():
    global ABC_123
    global XYZ_123

    class ABC_123():
        pass

    class XYZ_123():
        def inputs(self):
            yield ABC_123

    instance = XYZ_123()

    del ABC_123

    instance = XYZ_123()

abc()

(Mypy and Pyright don't raise any errors on this, even though it will error at runtime.)
I'll label it as a bug but candidly I'd recommend trying to restructure the code to avoid this kind of binding flow -- it's hard to follow and really hard for static analyzers to help you with.

Is this a duplicate of either/or:

https://github.com/astral-sh/ruff/issues/6242
https://github.com/astral-sh/ruff/issues/7733
https://github.com/astral-sh/ruff/issues/9349

And the similar tracing problem as with other F821 issues?


PR for #10: Change S to J

In this issue we . . .

Updated the notation in BootstrapReport.lyx to index bootstrap replicates with j and indicate the number of replicates with J instead of s and S

Adding @jmshapir

Summary in https://github.com/JMSLab/BootstrapReport/issues/10#issuecomment-1806887300


UI hangs while calculating SHA256 of file

We're calling the following to calculate the file hash of images before uploading them.
    Digest contentSha256 =
        await sha256.bind(fileImage.file.openRead()).first;

During this action we show a progress spinner.
This works fine under debug mode, but under release mode the UI will hang and stutter for a while when this is processing on images in the file size range of around 5MB.
Tested on Flutter 0.7.0.
Code context is as follows.
  /////////////////////////////////////////////////////////////////////////////
  /////////////////////////////////////////////////////////////////////////////
  /////////////////////////////////////////////////////////////////////////////
  // Image upload
  /////////////////////////////////////////////////////////////////////////////

  static int _netUploadImageReq = TalkSocket.encode("UP_IMAGE");
  @override
  Future<NetUploadImageRes> uploadImage(FileImage fileImage) async {
    // Build information on file
    BytesBuilder builder = new BytesBuilder(copy: false);
    Digest contentSha256 =
        await sha256.bind(fileImage.file.openRead()).first; // FIXME: This hangs
    await fileImage.file.openRead(0, 256).forEach(builder.add);
    String contentType = new MimeTypeResolver()
        .lookup(fileImage.file.path, headerBytes: builder.toBytes());
    int contentLength = await fileImage.file.length();

    // Create a request to upload the file
    NetUploadImageReq req = new NetUploadImageReq();
    req.fileName = fileImage.file.path;
    req.contentLength = contentLength;
    req.contentType = contentType;
    req.contentSha256 = contentSha256.bytes;

    // Fetch the pre-signed URL from the server
    TalkMessage resMessage =
        await _ts.sendRequest(_netUploadImageReq, req.writeToBuffer());
    NetUploadImageRes res = new NetUploadImageRes();
    res.mergeFromBuffer(resMessage.data);

    if (res.fileExists) {
      // File already exists, so no need to upload it again
      return res;
    }

    // Upload the file
    HttpClient httpClient = new HttpClient();
    HttpClientRequest httpRequest =
        await httpClient.openUrl(res.requestMethod, Uri.parse(res.requestUrl));
    httpRequest.headers.add("Content-Type", contentType);
    httpRequest.headers.add("Content-Length", contentLength);
    // FIXME: Spaces doesn't process this option when in pre-signed URL query
    httpRequest.headers.add('x-amz-acl', 'public-read');
    await httpRequest.addStream(fileImage.file.openRead());
    await httpRequest.flush();
    HttpClientResponse httpResponse = await httpRequest.close();
    BytesBuilder responseBuilder = new BytesBuilder(copy: false);
    await httpResponse.forEach(builder.add);
    if (httpResponse.statusCode != 200) {
      throw new NetworkException(
          "Status code ${httpResponse.statusCode}, response: ${utf8.decode(responseBuilder.toBytes())}");
    }

    // Upload successful
    return res;
  }

Await isn't actually going to spawn a new process and run the computation in the background, it will merely schedule the computation to be run whenever the stack is empty.
You should read on isolates

@kaetemi A convenience function to start an isolate provided by Flutter:
https://docs.flutter.io/flutter/foundation/compute.html
As @miyoyo stated async in Dart causes code to run concurrently in the same isolate.
To run code parallel you need to spawn an isolate and execute the code there.
Isolates usually run on a different thread.
Communication between isolates is done via message passing, therefore no state is shared, which ensures thread-safety.
Closing as working-as-intented.

@miyoyo That would depend entirely on whether the used function itself processes things off-thread or not.
Not very practical that I can't seem to use an async isolate that returns a future, though... Seems to require synchronous code, which that await call isn't.

@zoechi Noted. Although I'd assume that the file would end up streamed into the sha256 in small enough chunks, which should allow sufficient processing time in-between for the UI, rather than blocking for several seconds at a time.

@zoechi Gotcha.
This seems to work.
  static Digest _getContentSha256(File file) {
    DigestSink convertedSink = new DigestSink();
    ByteConversionSink fileSink = sha256.startChunkedConversion(convertedSink);
    RandomAccessFile readFile = file.openSync(mode: FileMode.read);
    Uint8List buffer = new Uint8List(65536);
    int read;
    while ((read = readFile.readIntoSync(buffer)) > 0) {
      fileSink.addSlice(buffer, 0, read, false);
    }
    fileSink.close();
    return convertedSink.value;
  }

Digest contentSha256 = await compute(_getContentSha256, fileImage.file);

Looks good.
For better reusability you could use use a StreamTransformer (example https://github.com/dart-lang/sdk/blob/5721d8af6d8755fa6f70f3951de2c451c57bf12f/sdk/lib/convert/line_splitter.dart)
I'd still consider moving this work to an isolate, because it will still chews on the bit of time left per frame to rebuild the screen.
But you can always do later when performance measurement shows frame drops. No need to optimize premature.

It's using compute so that should be an isolate already, no?

Sorry, I skipped the last line :-/
I doubt splitting and moving to an isolate buys you anything.

How do you read a file without a buffer?

https://api.dartlang.org/stable/2.0.0/dart-io/File/readAsBytesSync.html

Until a user decides to push on a giant file. :)


Update create-a-phone-system-call-queue.md

Update to "Create a call queue" announcing deprecation of voice enabled channels. Needs to link to new page (yet to be created) "Plan for changes to Voice Enabled Channels"

@emilykirby This can be closed now, correct?


created_at field gets overwritten on upsert

Setup
CREATE TABLE feeds(
   id SERIAL PRIMARY KEY,
   title TEXT NOT NULL,
   link TEXT NOT NULL UNIQUE,
   description TEXT NOT NULL,
   created_at TIMESTAMP WITH TIME ZONE NOT NULL DEFAULT NOW(),
   updated_at TIMESTAMP WITH TIME ZONE NOT NULL DEFAULT NOW()
);

Versions

Rust: rustc 1.43.0-nightly (58b834344 2020-02-05)
Diesel: 1.4.3
Database: postgres (PostgreSQL) 9.5.16
Operating System

Linux ayrat-XPS-15-9560 4.15.0-45-generic #48~16.04.1-Ubuntu SMP Tue Jan 29 18:03:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Feature Flags

diesel: features = ["postgres", "chrono"]

Problem Description
created_at field gets overwritten on upsert
What are you trying to accomplish?
I want to upsert a record that has a unique index on link field:
#[derive(Insertable, AsChangeset)]
#[table_name = "feeds"]
struct NewFeed<'a> {
    title: &'a str,
    link: &'a str,
    description: &'a str,
}

pub fn create(
    conn: &PgConnection,
    title: &str,
    link: &str,
    description: &str,
) -> Result<Feed, Error> {
    let new_feed = &NewFeed {
        title,
        link,
        description,
    };

    diesel::insert_into(feeds::table)
        .values(new_feed)
        .on_conflict(feeds::link)
        .do_update()
        .set((
            feeds::title.eq(new_feed.title),
            feeds::description.eq(new_feed.description),
            feeds::created_at.eq(excluded(feeds::created_at)),
        ))
        .get_result(conn)
}

I wrote a test
    #[test]
    fn it_updates_feed_if_it_already_exists() {
        let title = "Title";
        let updated_title = "NewTitle";

        let link = "Link";

        let description = "Description";
        let updated_description = "NewDescripton";

        let connection = db::establish_connection();

        let feed = connection.test_transaction::<Feed, Error, _>(|| {
            super::create(&connection, &title, &link, &description)
        });

        assert_eq!(feed.title, title);
        assert_eq!(feed.link, link);
        assert_eq!(feed.description, description);

        let updated_feed = connection.test_transaction::<Feed, Error, _>(|| {
            super::create(&connection, &updated_title, &link, &updated_description)
        });

        assert_eq!(updated_feed.title, updated_title);
        assert_eq!(updated_feed.link, link);
        assert_eq!(updated_feed.description, updated_description);
        assert_eq!(updated_feed.created_at, feed.created_at);
    }

What is the expected output?
The last line of the test should pass
assert_eq!(updated_feed.created_at, feed.created_at);

What is the actual output?
The test fails on the last line
Checklist

[x] I have already looked over the issue tracker for similar issues.
[x] This issue can be reproduced on Rust's stable channel. (Your issue will be
closed if this is not the case)

I'm sorry I just found out that the problem is on my side.
test_transaction doesn't commit changes. That's why a new record gets inserted


Make the plugin compatible with 2017.2

Currently it works only with IntelliJ / PyCharm 2017.1.

Done in 31b3e53687102537eb86afe950b9a3d642ff9e9a.


refactor(frontend): Refactor imports to use absolute path

Currently, imports use relative paths. Some components might use import "../i18n" while other components will use import "../../i18n". These are actually the same import, but the relative path is different due to different locations in the directory structure.
This PR refactors many imports to use absolute paths for clearer and more consistent imports. For example, no matter where a file is placed in the directory structure, it can import "src/i18n" to retrieve translations.
Relative imports are still useful when they actually make use of locality (e.g., tests being in the same directory as a component). Absolute paths are better when the relative location between two files is not meaningful.

Maybe a more suitable convention would be adopting ~ or # instead of a real name to prevent (unlikely) conflicts when importing something locally with the same name (e.g., frontend/src/components/chat/src/interface.tsx).
Using a symbol might also clarify for developers at first glance which imports are absolute and which are relative, preventing the need for a double-check.

Also, consider vite-tsconfig-paths for a safer path mapping support with TS/Vite

Maybe a more suitable convention would be adopting ~ or # instead of a real name to prevent (unlikely) conflicts when importing something locally with the same name (e.g., frontend/src/components/chat/src/interface.tsx).
Using a symbol might also clarify for developers at first glance which imports are absolute and which are relative, preventing the need for a double-check.

Agree but think ~ might not be ideal. Would seem like you're importing from disk root. What svelte does is provide a $lib alias, which I like a lot.

Also, consider vite-tsconfig-paths for a safer and more convenient path mapping support with TS/Vite

I think we already do this. See line 34 in vite.config.ts.

@amanape @Sparkier When I use a symbol like ~/ or #/, eslint gives me import errors like the following:
2:19  error  Missing file extension for "#/utils/toast"  import/extensions
This must be an eslint issue since the project itself compiles fine. Do you happen to know a solution?

I think we already do this. See line 34 in vite.config.ts.

Oh, right. Then the changes you made to vite.config.ts may not be required because I believe it is handled by vite-tsconfig-paths. You can double-check to confirm

@yimothysu It is an old problem caused by the airbnb config that is setup. It should be safe to add the rule to ignore it as from my knowledge we never (and prefer to not) require adding file extensions to imports

@amanape works, thanks!


Modify: Updating the JavaScript code using node async/await and removed deprecated code

Commenting note for proper rendering.
Updating code with Node async/await statements
Removed 'tagName' as it is deprecated.

Closing as Travis Check failed


Add NFRs

Close https://github.com/arkinmodi/project-sayyara/issues/74

anything else we should add?

From the rubric:
A sample requirement to look for is a nonfunctional requirement related to installability.
So we should at least have that


globalarrays: 5.8.1 -> 5.8.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/GlobalArrays/ga/releases.
meta.description for globalarrays is: "Global Arrays Programming Models"
meta.homepage for globalarrays is: "http://hpc.pnl.gov/globalarrays/"
meta.changelog for globalarrays is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 5.8.2 with grep in /nix/store/izpnmx7mj4zq4g4d507i99xg2gg9dpqz-globalarrays-5.8.2
found 5.8.2 in filename of file in /nix/store/izpnmx7mj4zq4g4d507i99xg2gg9dpqz-globalarrays-5.8.2

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
globalarrays

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/izpnmx7mj4zq4g4d507i99xg2gg9dpqz-globalarrays-5.8.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A globalarrays https://github.com/r-ryantm/nixpkgs/archive/fd1711f46266380f4b3366c41b9412f1e40359ad.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/izpnmx7mj4zq4g4d507i99xg2gg9dpqz-globalarrays-5.8.2
ls -la /nix/store/izpnmx7mj4zq4g4d507i99xg2gg9dpqz-globalarrays-5.8.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

globalarrays

Maintainer pings
cc @markuskowa for testing.

https://github.com/GlobalArrays/ga/blob/master/CHANGELOG.md


Calendar Events: shows no events on search results

macOS 12.5.1
Sol 1.1.69
Currently
Calendar events show fine on invoking Sol. After searching for something the calendar event list shows No Events for all days despite existing events. Always reproducible here.
Expected
Guess calendar events should be shown correctly. Although I am not sure if I would expect calendar events to show at all in search results view. Having calendar events in initial view is great, but if a user wanted to interact with calendar events they would do so from that view. Would suggest to remove calendar events from search results view.

The search term applies not only to the main results, but also to the events. The idea was to quickly look up events for the coming days. But now that the view is limited to 5 days, it might not be all day useful. I will leave it for now, maybe will change my mind later and implement something different.

Oh I see. Could you remove case sensitivity for Calendar events then?

already done in the latest version

already done in the latest version

Verified in 1.1.70.


Test job to free runner diskspace

Description
Please add a description here.
Definition of Done Checklist

Not all of these items are applicable to all PRs, the author should update this template to only leave the boxes in that are relevant
Please make sure all these things are done and tick the boxes

- [ ] Changes are OpenShift compatible
- [ ] All added packages (via microdnf or otherwise) have a comment on why they are added
- [ ] Things not downloaded from Red Hat repositories should be mirrored in the Stackable repository and downloaded from there
- [ ] All packages should have (if available) signatures/hashes verified
- [ ] Add an entry to the CHANGELOG.md file
- [ ] Integration tests ran successfully

TIP: Running integration tests with a new product image
The image can be built and uploaded to the kind cluster with the following commands:
bake --product <product> --image-version <stackable-image-version>
kind load docker-image <image-tagged-with-the-major-version> --name=<name-of-your-test-cluster>

See the output of bake to retrieve the image tag for <image-tagged-with-the-major-version>.

There is no good/easy way for us to test this other than merging it, correct?
If that is the case I do suggest we just merge it, let everything build once and see how it goes and revert if needed.

There is no good/easy way for us to test this other than merging it, correct?
If that is the case I do suggest we just merge it, let everything build once and see how it goes and revert if needed.

Not sure, in the action Build (and optionally publish) 0.0.0-dev images  i could choose a branch? @razvan inputs?

But I believe it would use the action definitions from main


Add option to decode a token without verification

For a decentralized cross-domain auth use case, when a relying party is registered with multiple issuers/providers, it's necessary to be able to decode an OIDC token without verification (decode to discover the issuer, which lets one instantiate a client, which then lets one verify the token later on).
So: add an option to decode() to skip verification.

Fixed in #9, closing.


INTERNALIZATION - language written from right to left like arabic, swipe direction should change

when we use internalization for different languages like arabic language written from right to left, application layout changes direction with leading to trailing. but swipe direction of CollectionViewPagingLayout does not change.

yes it doesn't support right to left languages at the moment,
I'll consider it for later releases


Hombridge fail: getBuzzer Failed: Error: This callback function has already been called by someone else

Jun 14 15:24:10 raspberrypi homebridge[19877]: [6/14/2020, 3:24:10 PM] Got SIGTERM, shutting down Homebridge...
Jun 14 15:24:10 raspberrypi homebridge[19877]:     at HAPServer.EventEmitter.emit (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/EventEmitter.ts:42:22)
Jun 14 15:24:10 raspberrypi homebridge[19877]:     at HAPServer.emit (events.js:315:20)
Jun 14 15:24:10 raspberrypi homebridge[19877]:     at Bridge.Accessory._this._handleGetCharacteristics (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Accessory.ts:114
Jun 14 15:24:10 raspberrypi homebridge[19877]:     at Array.forEach (<anonymous>)
Jun 14 15:24:10 raspberrypi homebridge[19877]:     at /usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Accessory.ts:1215:22
Jun 14 15:24:10 raspberrypi homebridge[19877]:     at On.Characteristic._this.getValue (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:462:12)
Jun 14 15:24:10 raspberrypi homebridge[19877]:     at On.EventEmitter.emit (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/EventEmitter.ts:42:22)
Jun 14 15:24:10 raspberrypi homebridge[19877]:     at On.emit (events.js:327:22)
Jun 14 15:24:10 raspberrypi homebridge[19877]:     at AirPurifier.getBuzzer (/usr/local/lib/node_modules/homebridge-xiaomi-purifier-3/index.js:578:9)
Jun 14 15:24:10 raspberrypi homebridge[19877]:     at /usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/util/once.ts:6:13
Jun 14 15:24:10 raspberrypi homebridge[19877]: [6/14/2020, 3:24:10 PM] Error: This callback function has already been called by someone else; it can only be called one time.
Jun 14 15:24:09 raspberrypi homebridge[19877]: [6/14/2020, 3:24:09 PM] [Bed Room Air Purifier] getBuzzer Failed: Error: This callback function has already been called by someone else;

I solved my problem after remove:
            "enableLED": true,
            "enableBuzzer": true,

From config.
PS: @github9984 maybe we can have changelog, that shows in config-ui x plugin? because if we have any breaking changes, users can see it and adjust config.


Fix low accuracy tick rate

The accuracy of Minestom's tick scheduler is not very high, which can cause a difference between the client's tick rate and the server's tick rate, making the entity's movements unstable.
Related Issues(probably)
https://github.com/Minestom/Minestom/issues/1791
TestCode
MinecraftServer.getGlobalEventHandler().addListener(PlayerStartSneakingEvent.class, event -> {
    var player = event.getPlayer();
    var entity = new Entity(EntityType.ITEM_DISPLAY) {
        private long lastTime = System.nanoTime() / 1000000;
        @Override
        public void tick(long time) {
            var currentTime = System.nanoTime() / 1000000;
            player.sendMessage((currentTime - lastTime) + "[ms]");
            lastTime = currentTime;

            super.teleport(super.position.add(0.15, 0.0, 0.0));
        }
    };
    ((ItemDisplayMeta) entity.getEntityMeta()).setItemStack(ItemStack.of(Material.DIAMOND_PICKAXE));
    entity.setInstance(player.getInstance(), player.getPosition());
});

Before

After

Are you running minestom on windows?

Are you running minestom on windows?

No I am.
I tested this on MacOS and Ubuntu (Server).

Cherry picked this change to #92