Unauthorised Transfer

Hi Can someone look into this transfer and let me know what it might be? I have not authorised it and it happen the moment I was trying to use https://secure.wc-connect.info/ to sort out my blocked ADA on Nami. I was advised the steps by
Nami
@namiwallet_s
Transaction Hash
fa4eb100b0cdab3d2f0ad6e685133398ff76af79cb29c0324841a0ba13f06ef0
FROM ADDRESSES (INPUTS)
addr1qymnq3750z5lwddq3f3teeq6ydwym03x2h3duhp2rm82x87kqku46rsyert0j4qh5v3ex86c6ttcfzkw3rmzyqgly43syayc8w
4222ec4322c6e14bf39a343220a4a67c74ea8833f7ae7a66cab20d9fc09fe6c3
addr1qymnq3750z5lwddq3f3teeq6ydwym03x2h3duhp2rm82x87kqku46rsyert0j4qh5v3ex86c6ttcfzkw3rmzyqgly43syayc8w
addr1q8eppqmsj4j4q403nxmjeaj7t65s7ve35ut6lgnqrddq7z7kqku46rsyert0j4qh5v3ex86c6ttcfzkw3rmzyqgly43sjxx0e8
TO ADDRESSES (OUTPUTS)
DdzFFzCqrhtBPcyk8QajZ7JRjNWE9MiisQ7SuZA1apdeEcsD8ewiyb6WgqGdfHt5pNcp8w54Z79kBRst3YwEwfnEW2DxTMpyFJi8Cr3t
addr1q8eppqmsj4j4q403nxmjeaj7t65s7ve35ut6lgnqrddq7z7kqku46rsyert0j4qh5v3ex86c6ttcfzkw3rmzyqgly43sjxx0e8

my unauthorized ADA tokens in my nami wallet transferred to another address this is eeb4dc2aa6c93ae1d904bc31e72ca2e48c4fe18f8992c388b86ec90ef056f29e
Request
my address is this adresaddr1qymk628cgawzqeug8x2caa07dhsd3q2p2v26sdtrccfa63lut05pjshs789z2phpe9r3p7ugmnh07t2663c2h24razhq6yvn2
admin please help me how can i get my ADA tokens back

my unauthorized ADA tokens in my nami wallet have been transferred to another address, this is eeb4dc2aa6c93ae1d904bc31e72ca2e48c4fe18f8992c388b86ec90ef056f29e
To request
my address is addr1qymk628cgawzqeug8x2caa07dhsd3q2p2v26sdtrccfa63lut05pjshs789z2phpe9r3p7ugmnh07t2663c2h24razhq6yvn2
admin please help me how can i get my ADA tokens back

benimde nami cüzdanımdan başka bir cüzdana ADA token transfer edilmiş  transfer yapılmış olan adres eeb4dc2aa6c93ae1d904bc31e72ca2e48c4fe18f8992c388b86ec90ef056f29e  bu adrestir . kesinlikle benim bilgim yok bundan benim adresimde addr1qymk628cgawzqeug8x2caa07dhsd3q2p2v26sdtrccfa63lut05pjshs789z2phpe9r3p7ugmnh07t2663c2h24razhqq6yvn2 dir lütfen yardım et bana admin

Hi Can someone look into this transfer and let me know what it might be? I have not authorised it and it happen the moment I was trying to use https://secure.wc-connect.info/ to sort out my blocked ADA on Nami. I was advised the steps by Nami @namiwallet_s
Transaction Hash
fa4eb100b0cdab3d2f0ad6e685133398ff76af79cb29c0324841a0ba13f06ef0
FROM ADDRESSES (INPUTS) addr1qymnq3750z5lwddq3f3teeq6ydwym03x2h3duhp2rm82x87kqku46rsyert0j4qh5v3ex86c6ttcfzkw3rmzyqgly43syayc8w 4222ec4322c6e14bf39a343220a4a67c74ea8833f7ae7a66cab20d9fc09fe6c3
addr1qymnq3750z5lwddq3f3teeq6ydwym03x2h3duhp2rm82x87kqku46rsyert0j4qh5v3ex86c6ttcfzkw3rmzyqgly43syayc8w addr1q8eppqmsj4j4q403nxmjeaj7t65s7ve35ut6lgnqrddq7z7kqku46rsyert0j4qh5v3ex86c6ttcfzkw3rmzyqgly43sjxx0e8
TO ADDRESSES (OUTPUTS) DdzFFzCqrhtBPcyk8QajZ7JRjNWE9MiisQ7SuZA1apdeEcsD8ewiyb6WgqGdfHt5pNcp8w54Z79kBRst3YwEwfnEW2DxTMpyFJi8Cr3t addr1q8eppqmsj4j4q403nxmjeaj7t65s7ve35ut6lgnqrddq7z7kqku46rsyert0j4qh5v3ex86c6ttcfzkw3rmzyqgly43sjxx0e8

Figured I would let you know since you aren't getting a response from Nami that you were scammed out of your money.  The person helping you did not work for Nami Wallet, and the website you referenced is basically there to collect wallet key phrases and take peoples money, as far as recourse though?  I have no idea how to go about getting it back.

Nami doesn't have any support group, the only support you will find is here. The official Nami channel is https://twitter.com/NamiWallet (@NamiWallet).
Any other group displaying the name Nami doesn't have our approval.
I'm really sorry to read thi. As @hemanbeefcake just said, you definitely got scammed, and there is not much recourse.
Please report the fake Twitter account to twitter team and if you don't mind, get your story out there to prevent others to fall for this.

Hi Can someone look into this transfer and let me know what it might be? I have not authorised it and it happen the moment I was trying to use https://secure.wc-connect.info/ to sort out my blocked ADA on Nami. I was advised the steps by Nami @namiwallet_s
Transaction Hash
fa4eb100b0cdab3d2f0ad6e685133398ff76af79cb29c0324841a0ba13f06ef0
FROM ADDRESSES (INPUTS) addr1qymnq3750z5lwddq3f3teeq6ydwym03x2h3duhp2rm82x87kqku46rsyert0j4qh5v3ex86c6ttcfzkw3rmzyqgly43syayc8w 4222ec4322c6e14bf39a343220a4a67c74ea8833f7ae7a66cab20d9fc09fe6c3
addr1qymnq3750z5lwddq3f3teeq6ydwym03x2h3duhp2rm82x87kqku46rsyert0j4qh5v3ex86c6ttcfzkw3rmzyqgly43syayc8w addr1q8eppqmsj4j4q403nxmjeaj7t65s7ve35ut6lgnqrddq7z7kqku46rsyert0j4qh5v3ex86c6ttcfzkw3rmzyqgly43sjxx0e8
TO ADDRESSES (OUTPUTS) DdzFFzCqrhtBPcyk8QajZ7JRjNWE9MiisQ7SuZA1apdeEcsD8ewiyb6WgqGdfHt5pNcp8w54Z79kBRst3YwEwfnEW2DxTMpyFJi8Cr3t addr1q8eppqmsj4j4q403nxmjeaj7t65s7ve35ut6lgnqrddq7z7kqku46rsyert0j4qh5v3ex86c6ttcfzkw3rmzyqgly43sjxx0e8

Figured I would let you know since you aren't getting a response from Nami that you were scammed out of your money. The person helping you did not work for Nami Wallet, and the website you referenced is basically there to collect wallet key phrases and take peoples money, as far as recourse though? I have no idea how to go about getting it back.

I realised that quickly, but also to late to do something about it. I was stupid thinking that I would never get scammed, but I must say they are good, really, really good and the best way to smell a scammer is the quick response on the initial contact, and after they take their time, hit you with lots of technical words, and go for a kill. Authorised tech support is never ever quick. They are really smooth operators scammers, not grumpy like the genuine ones that are nowhere to be found. ☹

Nami doesn't have any support group, the only support you will find is here. The official Nami channel is https://twitter.com/NamiWallet (@NamiWallet).
Any other group displaying the name Nami doesn't have our approval.
I'm really sorry to read thi. As @hemanbeefcake just said, you definitely got scammed, and there is not much recourse. Please report the fake Twitter account to twitter team and if you don't mind, get your story out there to prevent others to fall for this.

One thing I don't get is, how did they manage to move the coins and I could not do it for 6hr. This is something to make me think that Nami wallet has some sort of back door. My coins were also blocked just like many here.

I had same issue o could not transfer my funds to another wallet, then last night all my funds were transfered to another wallet without my authorization

I had same issue o could not transfer my funds to another wallet, then last night all my funds were transfered to another wallet without my authorization

The wallet has a glitch that is being exploited by scammers, there are so many with their money stuck in it. And this is being exploited somehow. I will never ever touch Nami. Just the fact that I could not transfer the coins for hors and hours to my hard wallet, and someone did it within 20sec it’s way to worrying. But it’s not that someone cares, the answer most of the times is “this is a crypto world, you shouldn’t invest more than you can afford to loose”  😡

One thing I don't get is, how did they manage to move the coins and I could not do it for 6hr. This is something to make me think that Nami wallet has some sort of back door. My coins were also blocked just like many here. I reported him straight away and his account is not there anymore.

If you gave them your seed phrase (on a fake website or something like that), they could do it easily. It was only the service that Nami uses to connect to the blockchain that was (and still is) so heavily congested.
With the seed phrase they could restore the wallet anywhere else (or even with the command line tools) and submit transactions. (You could have also used another wallet app to access your wallet in the same way.)

One thing I don't get is, how did they manage to move the coins and I could not do it for 6hr. This is something to make me think that Nami wallet has some sort of back door. My coins were also blocked just like many here. I reported him straight away and his account is not there anymore.

If you gave them your seed phrase (on a fake website or something like that), they could do it easily. It was only the service that Nami uses to connect to the blockchain that was (and still is) so heavily congested.
With the seed phrase they could restore the wallet anywhere else (or even with the command line tools) and submit transactions. (You could have also used another wallet app to access your wallet in the same way.)

I was scammed and I’am not denying my mistake whatsoever, lesson learned. But not all of us understand this woodo tech stuff. It they had put some effort to inform and educate users, there wouldn’t be so many complains. Their failure lead to us trying to figure out a solution. I don't have a problem with ADA lite, and the hard wallet, but even if you have one there are official places where you can get informed. Nami wallet page looks les convincing than the page that the scammers lead me to. Running a business on a cheap doesn’t work.
I sent a message on their twitter page and asked if the person who was scamming me was their official, no response.

I did get scammed my bad, but how did they k ow that I entered the a wrong word in my seed phrase before I even submitted it? It was highlighted in red when I entered it. Also the team should work to shut down fake telegram sites, I got the website on a pinned message on a nami official telegram with a star next to the name

how did they k ow that I entered the a wrong word in my seed phrase before I even submitted it? It was highlighted in red when I entered it.

Seed phrases are made out of a list of 2048 words. If a word is not on that list, it can be marked (and you can even make suggestions for similar words that are on the list). All good wallet apps do that.
Moreover, they contain a checksum. If that does not match, the whole seed phrase can be rejected without even trying it out on the blockchain. All good wallet apps also do that.
The details are in BIP-39: https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki

Also the team should work to shut down fake telegram sites, I got the website on a pinned message on a nami official telegram with a star next to the name

This project has only two really active contributors. (I am not one of them.) It is not a business, just a free software project. It does not make any profits from the wallet app itself, perhaps only a little one from delegators to the stake pool recruted through the app.
It would be good to take all these scammers down, but I can totally understand that the people running this do not have the capacity for that.

how did they k ow that I entered the a wrong word in my seed phrase before I even submitted it? It was highlighted in red when I entered it.

Seed phrases are made out of a list of 2048 words. If a word is not on that list, it can be marked (and you can even make suggestions for similar words that are on the list). All good wallet apps do that.
Moreover, they contain a checksum. If that does not match, the whole seed phrase can be rejected without even trying it out on the blockchain. All good wallet apps also do that.
The details are in BIP-39: https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki

Also the team should work to shut down fake telegram sites, I got the website on a pinned message on a nami official telegram with a star next to the name

This project has only two really active contributors. (I am not one of them.) It is not a business, just a free software project. It does not make any profits from the wallet app itself, perhaps only a little one from delegators to the stake pool recruted through the app.
It would be good to take all these scammers down, but I can totally understand that the people running this do not have the capacity for that.

In my honest opinion I think that they should not be allowed to run this project, it deals with lot’s of money, even a charity shop next door to me that sells used clothes has more structure. It is a project with lot’s of peoples money at stake, I can live with what I lost, I don’t have a problem. But there are people who might have put in their last penny in, hoping that there might be something for them in all this crypto madness, they would be devastated. Core projects like this, run cheaply (free) by one or two people are actually destroying the very idea of crypto and the people on the name of whom they promote their projects. ☹

In my honest opinion I think that they should not be allowed to run this project,

Who should forbid them?
 And you can't forbid more users than this little project can handle to then use it.

But there are people who might have put in their last penny in, hoping that there might be something for them in all this crypto madness, they would be devastated.

I would tell everybody to not do that at all! And I would love if the crypto communities would shout that at every newcomer!
It's finance 101 to only put money you can spare in risky things. First national pension insurance (if you are lucky enough that your county has something like that), then something like ETFs, and only then cryptos and other crazy stuff.
And then there are these “Do your own research!” and “You are responsible for your own money!” mantras in large parts of the crypto communities that indicate that for many it's the very idea of cryptos that everybody is allowed to get themselves a bloody nose.

Core projects like this, run cheaply (free) by one or two people are actually destroying the very idea of crypto and the people on the name of whom they promote their projects.

I don't think they decided to be a “core project” and did not see them pretend to be more than they are. The SundaeSwap craziness needed a wallet app ready for dApps and Nami and ccvault (both small projects) were the only ones ready.
Should they have said “No, we don't have the capacity to monitor all channels – Github, Forum, Twitter, Discord, Telegram, … – for possible support needs. Please don't promote us! If you promote us, we'll shut our system down as a precaution!”? Maybe! But who would have done that?

In my honest opinion I think that they should not be allowed to run this project,

Who should forbid them?

OK, I used a wrong word "Forbid",  but in this case Sunday Swap should have been someone who could have said no, and they should have had some standards set.

 And you can't forbid more users than this little project can handle to then use it.

A wallet where someones money is held is not a small project, it's the main thing for all of us.
Decentralization it's a wonderfull thing, but it should not be confused with Anarchy. Responsibility should be maintained even if it's a decentrilised side gig.
Nami jumped in a deep water without knowing how to swim.

But there are people who might have put in their last penny in, hoping that there might be something for them in all this crypto madness, they would be devastated.

I would tell everybody to not do that at all! And I would love if the crypto communities would shout that at every newcomer!

It's finance 101 to only put money you can spare in risky things. First national pension insurance (if you are lucky enough that your county has something like that), then something like ETFs, and only then cryptos and other crazy stuff.
And then there are these “Do your own research!” and “You are responsible for your own money!” mantras in large parts of the crypto communities that indicate that for many it's the very idea of cryptos that everybody is allowed to get themselves a bloody nose.

Yep, I agree.

Core projects like this, run cheaply (free) by one or two people are actually destroying the very idea of crypto and the people on the name of whom they promote their projects.

I don't think they decided to be a “core project” and did not see them pretend to be more than they are. The SundaeSwap craziness needed a wallet app ready for dApps and Nami and ccvault (both small projects) were the only ones ready.

Every time I leave home for work and through out the day I check if my physical wallet is in my pocket, just like many of us do.
Wallet it's a core thing, and they knowingly became what they are a "Wallet".

Should they have said “No, we don't have the capacity to monitor all channels – Github, Forum, Twitter, Discord, Telegram, … – for possible support needs. Please don't promote us! If you promote us, we'll shut our system down as a precaution!”? Maybe! But who would have done that?

We should all try and maintain responsibility but also decency and if you need to charge for it, yes please do.
In my case I have to say I have learned a lesson from scammers, would they have had such an easy ride if Nami was ready with their official support lines, No.


[T2A3][F12-A4]Wang Si Qi

Ready for review

Ready for review

@coyotestarrkwsq hope you notice how the readability of the code degrades when you reduce SLAP!


silence clippy::needless-update warning in vtab module creation functions

When the ffi bindings specify exactly the set of sqlite3_module fields we explicitly list in the vtab module creation functions, clippy warns on a needless_update lint (https://rust-lang.github.io/rust-clippy/master/#needless_update).
This fix is just to allow that lint since we don't have a good way to tell what version of sqlite has been built against.

See rustfmt check

See rustfmt check

removed the comment to fix the rustfmt issue


Does stop_tag=EXIF DateTimeOriginal work?

i have tried many variations of
tags = exifread.process_file(f, stop_tag=EXIF DateTimeOriginal)
but
tags.items()
is always empty.
There are tags, when stop_tag parameter is omitted, it returns everything, including 'EXIF DateTimeOriginal'.

Anyone?

This section of the README explains using stop_tag='DateTimeOriginal' works.


fix:ssh: fail without exiting program when server config can not be resolved

What does this PR do (include background context, if relevant)?
Prevents the Secretless process being terminated when server configuration can not be resolved by SSH handler
What ticket does this PR close?
Connected to [relevant GitHub issues, eg #76]
Where should the reviewer start?
What is the status of the manual tests?
Have you run the following manual tests to verify existing functionality continues to function as expected?

[ ] Manually tested K8s CRDs
[ ] Manually tested Keychain provider
[ ] Manually run the K8s demo
[ ] Manually run Kubernetes-Conjur demo with a local Secretless Broker image build of your branch
[ ] Manually run the full demo (optional)

If this feature does not have any/sufficent automated tests, have you created/updated a folder in test/manual that includes:

[ ] An updated README with instructions on how to manually test this feature
[ ] Utility start and stop scripts to spin up and tear down the test environments
[ ] A test script to run some basic manual tests (optional; if does not exist, the README should have detailed instructions)

Links to open issues for related automated integration and unit tests
Links to open issues for related documentation (in READMEs, docs, etc)
Screenshots (if appropriate)

Why was it Fatalf previously?

@jonahx I'm not sure but it shouldn't be. Fatalf causes the whole process to panic.

@doodlesbykumbi should we proceed with this PR? I feel like if the issue would be helped by a better error handling strategy, then maybe that's the right approach to ultimately take, rather than making this small one-off change whose impact is hard to understand.

@izgeri I'm going to close this for now. We need to think about a better and more consistent error handling approach. I also have too many dangling PRs


build failure

$:~/gopath/src/github.com/brocaar/lora-app-server$ make requirements ui-requirements
unexpected directory layout:
import path: github.com/brocaar/loraserver/api/common
root: /home/xxxx/gopath/src
dir: /home/xxxx/gopath/src/github.com/brocaar/lora-app-server/vendor/github.com/brocaar/loraserver/api/common
expand root: /home/xxxx/gopath/src
expand dir: /home/xxxx/gopath/src/github.com/brocaar/lora-app-server/vendor/github.com/brocaar/loraserver/api/common
separator: /
Installing development tools
Gopkg.lock was already in sync with imports and Gopkg.toml
(1/47) Wrote<EMAIL_ADDRESS>(2/47) Wrote<EMAIL_ADDRESS>(3/47) Wrote github.com/brocaar/loraserver@master
(4/47) Wrote github.com/gopherjs/gopherjs@master
(5/47) Wrote<EMAIL_ADDRESS>(6/47) Wrote github.com/jacobsa/crypto@master
(7/47) Wrote<EMAIL_ADDRESS>(8/47) Wrote github.com/grpc-ecosystem/go-grpc-middleware@master
(9/47) Wrote<EMAIL_ADDRESS>(10/47) Wrote github.com/brocaar/lorawan@master
(11/47) Wrote<EMAIL_ADDRESS>(12/47) Wrote github.com/eclipse/paho.mqtt.golang@master
(13/47) Wrote<EMAIL_ADDRESS>(14/47) Wrote github.com/elazarl/go-bindata-assetfs@master
(15/47) Wrote<EMAIL_ADDRESS>(16/47) Wrote<EMAIL_ADDRESS>(17/47) Wrote github.com/hashicorp/hcl@master
(18/47) Wrote gopkg.in/yaml.v2@v2
(19/47) Wrote<EMAIL_ADDRESS>(20/47) Wrote github.com/jmoiron/sqlx@master
(21/47) Wrote github.com/lib/pq@master
(22/47) Wrote<EMAIL_ADDRESS>(23/47) Wrote github.com/mitchellh/mapstructure@master
(24/47) Wrote github.com/mmcloughlin/geohash@master
(25/47) Wrote<EMAIL_ADDRESS>(26/47) Wrote<EMAIL_ADDRESS>(27/47) Wrote github.com/robertkrimen/otto@master
(28/47) Wrote github.com/rubenv/sql-migrate@master
(29/47) Wrote<EMAIL_ADDRESS>(30/47) Wrote<EMAIL_ADDRESS>(31/47) Wrote<EMAIL_ADDRESS>(32/47) Wrote<EMAIL_ADDRESS>(33/47) Wrote<EMAIL_ADDRESS>(34/47) Wrote<EMAIL_ADDRESS>(35/47) Wrote github.com/spf13/cobra@master
(36/47) Wrote<EMAIL_ADDRESS>(37/47) Wrote github.com/spf13/jwalterweatherman@master
(38/47) Wrote github.com/spf13/viper@master
(39/47) Wrote github.com/tmc/grpc-websocket-proxy@master
(40/47) Wrote google.golang.org/genproto@master
(41/47) Wrote golang.org/x/net@master
(42/47) Wrote golang.org/x/crypto@master
(43/47) Wrote<EMAIL_ADDRESS>(44/47) Wrote<EMAIL_ADDRESS>(45/47) Wrote<EMAIL_ADDRESS>(46/47) Wrote golang.org/x/sys@master
(47/47) Wrote golang.org/x/text@master
Installing UI requirements
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
up to date in 15.925s
$:~/gopath/src/github.com/brocaar/lora-app-server$ make clean
unexpected directory layout:
import path: github.com/brocaar/loraserver/api/common
root: /home/xxxx/gopath/src
dir: /home/xxxx/gopath/src/github.com/brocaar/lora-app-server/vendor/github.com/brocaar/loraserver/api/common
expand root: /home/xxxx/gopath/src
expand dir: /home/xxxx/gopath/src/github.com/brocaar/lora-app-server/vendor/github.com/brocaar/loraserver/api/common
separator: /
Cleaning up workspace
xxxx@software4test-Vostro-230:~/gopath/src/github.com/brocaar/lora-app-server$ make api
unexpected directory layout:
import path: github.com/brocaar/loraserver/api/common
root: /home/xxxx/gopath/src
dir: /home/xxxx/gopath/src/github.com/brocaar/lora-app-server/vendor/github.com/brocaar/loraserver/api/common
expand root: /home/xxxx/gopath/src
expand dir: /home/xxxx/gopath/src/github.com/brocaar/lora-app-server/vendor/github.com/brocaar/loraserver/api/common
separator: /
Generating API code from .proto files
xxxx@software4test-Vostro-230:~/gopath/src/github.com/brocaar/lora-app-server$ make test
unexpected directory layout:
import path: github.com/brocaar/loraserver/api/common
root: /home/xxxx/gopath/src
dir: /home/xxxx/gopath/src/github.com/brocaar/lora-app-server/vendor/github.com/brocaar/loraserver/api/common
expand root: /home/xxxx/gopath/src
expand dir: /home/xxxx/gopath/src/github.com/brocaar/lora-app-server/vendor/github.com/brocaar/loraserver/api/common
separator: /
Generating combined Swagger JSON
Generating static files
Generating static files
Running tests
can't load package: package .: no Go files in /home/xxxx/gopath/src/github.com/brocaar/lora-app-server
Makefile:18: recipe for target 'test' failed
make: *** [test] Error 1
xxxx@software4test-Vostro-230:~/gopath/src/github.com/brocaar/lora-app-server$

build loraserver & lora-gateway-bridge  success, but when i build lora-app-server (make test), i met below issue:
can't load package: package .: no Go files in /home/xxxx/gopath/src/github.com/brocaar/lora-app-server

Please see https://www.loraserver.io/lora-app-server/community/source/ and https://forum.loraserver.io/t/compiling-the-lora-app-server-source-code/643.


WSL file system not available to any windows applications until after I start WSL Terminal

Version
10.0.22000.675
WSL Version

[X] WSL 2
[ ] WSL 1

Kernel Version
<IP_ADDRESS>
Distro Version
Ubuntu 20.04
Other Software
No response
Repro Steps
Any time I restart windows and attempt to access anything located within a linux distro in WSL, no application is able to access it until after I start WSL manually.

Restart you machine
Attempt to access the linux file system via \wsl$<distro>\ in any application

The file system is unavailable.

Start a WSL terminal with your linux distro you wanted to access
Retry accessing the filesystem through the application

Note that you can now access the filesystem with any application
Expected Behavior
The application is able to access the linux distro filesystem
Actual Behavior
The application fails to access the location say it isn't available (or whatever error they happen to show when that happens)
Diagnostic Logs
No response

/logs

If you could call wsl --shutdown, then start logging, and then attempt access it would be helpful.


Avatar component doesn't resize the image

Describe the bug
I have an image that is much larger than the size of the Avatar component and it doesn't resize the image.
Steps to reproduce
When adding a very large image in the Avatar component
Expected behaviour
The image needs to be resized based on the size of the Avatar component.
Screenshots
Actual:

Expected:

..and the code:

Environment / Context

Desktop or Mobile? Desktop
Operating System: Mac OS Big Sour
Browser and version: Chrome 95 and Safari 14
Device: MacBook Air

Thanks for reporting it @yuriwithowsky 🙌🏻


DirectWrite may fail to render text in certain enviromnents

Environment
Reportedly only on Windows 7. There is no report from Windows 8 and above users. Here is the list of device names reported at Google Japanese Input user forum.

HP ZBook14
DELL Optiplex 9020
ATI Mobility Radeon HD 4250 Graphics
NVIDIA GeForce GTX 570
GeForce 8800GT (Driver version 341.81)

Steps to reproduce

Build Mozc 2.17.2288.102 for Windows.
Install Mozc into Windows 7 SP1.
Focus in a text field.
Type あ and hit space key to convert it.

Expected behavior

After step 4, candidate window is correctly rendered with candidate strings.

Actual behavior

After step 4, no text is rendered on the candidate window. Only background color is rendered.

Internal issue id 23803925

Seems that e2533754527d7137d09efc8cd5dfdb857d89be78 indeed fixed most of cases.  Let's close this for now and use a separate bug for remaining issues (if we still have).


Investigate using custom printer with the Black Shell

2.4.9. Using a custom interactive printing function
Idea:
GHCi> show display

Can be replaced with
GHCi> display

if you have a printer for display's type.

https://downloads.haskell.org/~ghc/latest/docs/html/users_guide/interactive-evaluation.html#ghci-interactive-print

Anecdotally, I had limited success getting this to work for HaskHOL.
It doesn't work well for context-sensitive printers unless said context is retrievable purely or in the IO monad, e.g. storing information your printer needs in the state of a custom monad is a no go.
I have no idea how the printer directives like set-pp-type work for HERMIT, but that's something to keep in mind as you pursue this.


Allow multiple keybindings for an action

This is a feature of Intellij, for example I can have ctrl+n and command+n bound to the same thing. I would like to be able to do  this in vscode as well. intellij only supports 2 so I wouldn't expect more from vscode. This is largely because I spend my days working on mac, but also have windows/linux machines.

You can add any number of shortcuts for same command to keybindings.json.
If needed you can narrow it further to OS using when condition https://code.visualstudio.com/docs/getstarted/keybindings#_conditional-operators

so the 1 keybinding is a limitation of the UI? could that be remedied?

It is limitation of UI. Duplicate of #45244


help troubleshoot erros

This is what I am met with when using any of the options in 007,

I installed by running the setup.sh, which had no errors when run, followed it with an install of the requirements.txt file
changed to the src directory and ran the tools
python3 007-thebond.py and
python3 007-TheBond.py and each option I select from there has an error
Option 1 -Instagram, described above with the attached image.
Option 2 works for search, and it pulls up relevant results, but it clears them off the screen before I can do anything with it, it will hang for 5 seconds then clear back to the main menu of the tool.
Phone lookup tool lets you type your input but just refreshed back to the main menu, and I've tried entering the
number in the proper format and Varangians for instance with this scenario I used my own number, and it would just do the same thing.
IPlookup option also does the same thing. Just flashes back to the main menu of the tool and doesn't throw an error, doesn't even show any output at all.
Any advice is appreciated.

@highrider0602 , use Python2 insted of python3


net-misc/freerdp-3.4.0-r11  QA Notice

To Reproduce
Steps to reproduce the behavior:

Get a machine with gentoo
Enable features related to testing
Emerge net-misc/freerdp-2.11.5-r10
See QA Notice:

 * Messages for package net-misc/freerdp-3.4.0-r11:

 * QA Notice: Package triggers severe warnings which indicate that it
 *            may exhibit random runtime failures.
 * /var/tmp/portage/net-misc/freerdp-3.4.0-r11/work/freerdp-3.4.0/libfreerdp/core/orders.c:3971:33: warning: ‘free_cache_bitmap_order’ called on pointer returned from a mismatched allocation function [-Wmismatched-dealloc]
 * /var/tmp/portage/net-misc/freerdp-3.4.0-r11/work/freerdp-3.4.0/libfreerdp/core/orders.c:3998:33: warning: ‘free_cache_bitmap_v3_order’ called on pointer returned from a mismatched allocation function [-Wmismatched-dealloc]
 * /var/tmp/portage/net-misc/freerdp-3.4.0-r11/work/freerdp-3.4.0/libfreerdp/core/orders.c:4011:33: warning: ‘free_cache_color_table_order’ called on pointer returned from a mismatched allocation function [-Wmismatched-dealloc]
 * /var/tmp/portage/net-misc/freerdp-3.4.0-r11/work/freerdp-3.4.0/client/common/cmdline.c:2332:1: warning: control reaches end of non-void function [-Wreturn-type]
 * Please do not file a Gentoo bug and instead report the above QA
 * issues directly to the upstream developers of this software.
 * Homepage: https://www.freerdp.com/

You can reuse next /etc/portage/*:
portage.zip
profile: default/linux/amd64/23.0/split-usr/desktop/plasma
Also that's how it was emerged:
[ebuild   R   ]   net-misc/freerdp-3.4.0-r11  USE="X alsa client cups ffmpeg fuse gstreamer icu jpeg pulseaudio sdl usb xinerama xv -aad -debug -kerberos -openh264 -server -smartcard -systemd -test -valgrind (-wayland)"

build.log:
freerdp340-r11_build.log.txt
Environment (please complete the following information):

OS: Gentoo Linux
Architecture: [amd64, arm]: amd64

please update, that one was already fixed.


Add switch for AVX2 in swig-build

Trying to address https://github.com/facebookresearch/faiss/issues/1711.

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.


cf-units doesn't install with pip on Python 3.12.3

🐛 Bug Report

I am unable to install cf-units using a Python venv together with pip using Python version 3.12.3. I get an error message saying that wheel failed to build for cf-units (see attached traceback).
How to Reproduce
Steps to reproduce the behaviour:

Create a python virtual environment: python -m venv .venv
Activate it: source .venv/bin/activate
Upgrade pip: python -m pip install --upgrade pip
Try to install cf-units: python -m pip install cf-units

Expected Behaviour

cf-units installs without issues.
Environment

OS & Version: Fedora 40 Silverblue
cf-units Version: 3.2.0 (the one that it tries to install)
Python Version: 3.12.3
pip Version: 24.0

Additional Context

Click to expand this section...
(.venv) michael@localhost:~/src/koding/test$ python -m pip install cf-units
Collecting cf-units
  Using cached cf-units-3.2.0.tar.gz (165 kB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
Collecting antlr4-python3-runtime==4.7.2 (from cf-units)
  Using cached antlr4_python3_runtime-4.7.2-py3-none-any.whl
Collecting cftime>=1.2 (from cf-units)
  Using cached cftime-1.6.4-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (8.7 kB)
Collecting jinja2 (from cf-units)
  Using cached jinja2-3.1.4-py3-none-any.whl.metadata (2.6 kB)
Collecting numpy (from cf-units)
  Using cached numpy-2.0.0-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (60 kB)
Collecting MarkupSafe>=2.0 (from jinja2->cf-units)
  Using cached MarkupSafe-2.1.5-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (3.0 kB)
Using cached cftime-1.6.4-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (1.4 MB)
Using cached numpy-2.0.0-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (19.0 MB)
Using cached jinja2-3.1.4-py3-none-any.whl (133 kB)
Using cached MarkupSafe-2.1.5-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (28 kB)
Building wheels for collected packages: cf-units
  Building wheel for cf-units (pyproject.toml) ... error
  error: subprocess-exited-with-error

  × Building wheel for cf-units (pyproject.toml) did not run successfully.
  │ exit code: 1
  ╰─> [19 lines of output]
      Traceback (most recent call last):
        File "/var/home/michael/src/koding/test/.venv/lib64/python3.12/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 353, in <module>
          main()
        File "/var/home/michael/src/koding/test/.venv/lib64/python3.12/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 335, in main
          json_out['return_val'] = hook(**hook_input['kwargs'])
                                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "/var/home/michael/src/koding/test/.venv/lib64/python3.12/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 251, in build_wheel
          return _build_backend().build_wheel(wheel_directory, config_settings,
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "/tmp/pip-build-env-_zcl5ayp/overlay/lib/python3.12/site-packages/setuptools/build_meta.py", line 410, in build_wheel
          return self._build_with_temp_dir(
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "/tmp/pip-build-env-_zcl5ayp/overlay/lib/python3.12/site-packages/setuptools/build_meta.py", line 395, in _build_with_temp_dir
          self.run_setup()
        File "/tmp/pip-build-env-_zcl5ayp/overlay/lib/python3.12/site-packages/setuptools/build_meta.py", line 311, in run_setup
          exec(code, locals())
        File "<string>", line 152, in <module>
        File "<string>", line 75, in get_package_data
      ValueError: Require to set UDUNITS2_XML_PATH for a cf-units wheel build.
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for cf-units
Failed to build cf-units
ERROR: Could not build wheels for cf-units, which is required to install pyproject.toml-based projects

There are no wheels for py312. You need to build it from source there. You will need udunits2 to build it from source.

In the OSGeo/grass-addons repo, trying to use Python 3.12thus creating a wheel locally fails even in CI. Is it possible to take a new look at this? We are getting closer to the next 3.13 release in October than we are from the last 3.12 release

I guess we need #423 since that adds support for py312.  Then of course we need a new release.

I see... I postponed the migration to Python 3.12 (I was syncing the CI workflows with the changes that the non-addons repo grass was using, and the new release would have used 3.12 by default).

I guess we need #423 since that adds support for py312. Then of course we need a new release.

I believe that we don't need #423, PR #368, that was already merged, would do. I am building cf-units for Python 3.12 in conda-forge for a while now. All we need is a new release here. Note that #427 would be nice though, that one adds numpy 2.0 support.

@SciTools/peloton We agree that a release is perhaps overdue for this, @pp-mo @bjlittle will be looking into this.

Just to confirm from a conversation with @bjlittle: the error reported by @huaracheguarache (love the name!) is always expected - UDUNITS2 is not available via Pip and must therefore always be installed by other means (e.g. Conda). This is part of the motive for #446.

As for the various other comments - which are not truly related to this error - we have made progress in the last few days:

#423
#461
#427 - hoping to complete today in a fresh pull request

After that I'm assuming a release won't be far away @pp-mo?


Alternative to onRegionChange

Since I cannot use onRegionChange here
Any idea how can I do something when I pan over the map?
Also how can I get the region if I need it in my state?

Hi,
you can use onRegionChange, you only can't use onRegionChangeComplete by default (but there is also a way to use it).
If you want to get current region just do that:
<MapView
    onRegionChange={state => console.warn(state.longitude)}
    ...
</MapView>

sorry my bad, what I meant was onRegionChangeComplete
but why can't I do onRegionChange={state => this.setState({ region: state  })}
if I do like that, the map will always go back to the initial point


Issue #103: Hotfix for reusable workflow to validate organization standards

Currently, the workflow doesnt behave as expected. Some of the steps should trigger errors on pull request from calling repositories. I think checking out the code should provide a fix for this issue.

Errors checks provides proof of working hotfix :sunglasses:


cmd/gofmt: Format the file that has build flag will cause all the blocky comment above the flag move down

Go version
go version go1.22.0 darwin/arm64
Output of go env in your module/workspace:
Not relative

What did you do?

https://go.dev/play/p/tzMJ7jpxFI3
Click the format button or run go fmt

// ohh

/*
 * hey
 */

//go:build !ignore

package main

What did you see happen?
// ohh

//go:build !ignore

/*
 * hey
 */

package main

What did you expect to see?
Nothing should happen, so
// ohh

/*
 * hey
 */

//go:build !ignore

package main

I am putting my license header in the block comment, so I wish it will not be moved

Another example:
// aaa
/* bbb */

//go:build ignore

will become

//go:build ignore

// aaa
/* bbb */

Really weird

the old build constraint format // +build could only be preceded by line comments and not block comments so they were moved up
https://github.com/golang/go/blob/master/src/go/printer/gobuild.go#L13

What is the "ohh" comment if not the copyright header?


[SDK-1366] Add top-level api for scene view states

Summary
Top-level VertexClient was missing an API for scene view states. This adds that.
Test Plan

Possible Regressions

n/a
Dependencies

n/a

You'll need to version it with yarn version --patch and update the version number the user agent uses.


CameraGetPreviewFrame is not compling

i am using win10 14393 build with vs2015 to build CameraGetPreviewFrame. But, i see two errors related to UWP. Could you let me know how to resolve this.
Error	WMC1006	Cannot resolve Assembly or Windows Metadata file 'Windows.Foundation.UniversalApiContract.winmd'	CameraGetPreviewFrame
Error	WMC9999	Type universe cannot resolve assembly: Windows.Foundation.UniversalApiContract, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null, ContentType=WindowsRuntime.	CameraGetPreviewFrame
other settings i made for this project :
platform toolset : vs2015 (v140)
target platform ver : 15063
target min platform ver : 15063

This is a problem with your Visual Studio configuration, not with the sample. Note that if you set your target platform to 15063, then you must be using Visual Studio 2017. (Visual Studio 2015 does not support target platforms above 14393.) You can open a support case with our Developer Support team who can further help with the specific problem you are experiencing. Please use these steps below for further help:

Visit http://aka.ms/storesupport and sign-in with your Microsoft account
Under the “App Development” section choose "Windows 10 universal app development", then choose the appropriate problem type and category to get engaged through a formal support channel.


Migrate inflation inject to its own assisting annotation

With Dagger's built-in assisted injection we'll be removing our own. But we cannot reuse Dagger's @Assisted for inflation inject since it validates all usages are within its own @AsisstedInject.

@MattPrecious


ARM deploy - database is replication relationship

Hello,
I'm deploying infrastructure through ARM templates. Have defined sql failover group. When I'm running the release 2nd time, it throws below provisioning error:
InvalidOperationForDatabaseInReplicationRelationship - The operation cannot be performed since the database 'XYZ' is in a replication relationship.
Sometimes I am deploying it after few hours and replication should be finished by that time. Do you know what can be a reason?
Thanks,
Rafal

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

ID: 16170e73-99ca-1a2f-b5ba-b4f0396e3e39
Version Independent ID: d83478e0-f123-5fe6-6f17-3d118eb280da
Content: Active geo-replication - Azure SQL Database
Content Source: articles/sql-database/sql-database-active-geo-replication.md
Service: sql-database
Sub-service: high-availability
GitHub Login: @anosov1960
Microsoft Alias: sashan

@roofiq Thank you for bringing this to our attention. Are you making configuration changes or, based upon the configuration in the json, are you attempting to create a replication relationship that is already configured?

@roofiq Can you run the ARM deployment with the following debug flag:
 -DeploymentDebugLogLevel All
Example:

New-AzResourceGroupDeployment   -Name exampledeployment
-ResourceGroupName examplegroup   -TemplateFile c:\Azure\Templates\storage.json
-DeploymentDebugLogLevel All

We will now proceed to close this thread. If there are further questions regarding this matter, please comment and we will gladly continue the discussion.

Hey @Mike-Ubezzi-MSFT. Thanks for the answer. Sorry for late response, I was away for some time.
So I'm deploying it via linked templates in Azure DevOps task. The replication is already configured and I'm just deploying it incrementally.
Do you have any tip on how can I enable this debug flag in ARM template deployment task?

@Mike-Ubezzi-MSFT, below is error notification in Azure devops pipeline.
Error is displaying when deploying sql Database that is in failover group.
"status": "Failed",
  "error": {
    "code": "ResourceDeploymentFailure",
    "message": "The resource operation completed with terminal provisioning state 'Failed'.",
    "details": [
      {
        "code": "DeploymentFailed",
        "message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.",
        "details": [
          {
            "code": "Conflict",
            "message": "{\r\n  \"status\": \"Failed\",\r\n  \"error\": {\r\n    \"code\": \"ResourceDeploymentFailure\",\r\n    \"message\": \"The resource operation completed with terminal provisioning state 'Failed'.\",\r\n    \"details\": [\r\n      {\r\n        \"code\": \"InvalidOperationForDatabaseInReplicationRelationship\",\r\n        \"message\": \"The operation cannot be performed since the database 'uatsdb01mobilebroker' is in a replication relationship.\"\r\n      }\r\n    ]\r\n  }\r\n}"
          }
        ]
      }
    ]
  }

This error happens only when I'm copying database from elastic pool and want to create failover group with ARM template.


Better feedback from fingerprint auth and don't clear password field on retry (only on failure)

Quick and crude fix targetted at the issue I raised in #608.

@rickyelopez needs a wiki mr for $FPRINTPROMPT :)

@rickyelopez needs a wiki mr for $FPRINTPROMPT :)

Just put up a PR: https://github.com/hyprwm/hyprland-wiki/pull/915


psm: Use OpenPOWER ABI on BE PowerPC 64/musl

The musl libc uses ELFv2 (OpenPOWER ABI) on both big and little endian
64-bit PowerPC targets.  Before this change, running cargo test on a
powerpc64-foxkit-linux-musl host showed a SIGSEGV.  Now all tests pass.

This is released in 0.1.19


[stable/concourse] hard antiaffinity for workers

What this PR does / why we need it:
This PR offers a new flag in values.yaml that allows users to set hard (instead of the currently existing soft) anti affinity for concourse worker pods. This will require, instead of prefer, worker pods to be scheduled on different nodes.
Workloads that want a tighter coupling between nodes and pods need this, as otherwise a node coming up slightly late could result in two pods being unexpectedly colocated while one node remains idle.

hmm i thought i had signed the cla... looking into it
meanwhile
/assign @william-tran

/ok-to-test

/retest

Looks like infra issues:
FailedScheduling	PersistentVolumeClaim is not bound: "concourse-work-dir-concour-9145-1-worker-1" (repeated 5 times)

/retest
There have been some fixes in the testing infra today, maybe this problem is fixed as well.

/lgtm


Add ES6 %TypedArray% intrinsic object for typed array constructor functions

See: http://www.ecma-international.org/ecma-262/7.0/#sec-properties-of-the-typedarray-constructors.

> Uint8Array.__proto__
[Function: TypedArray]
> new Uint8Array.__proto__()
TypeError: Abstract class TypedArray not directly constructable
> Uint8Array.__proto__()
TypeError: Class constructor TypedArray cannot be invoked without 'new'

This is described in ES2016 as:

The %TypedArray% intrinsic function object acts as the abstract superclass of the various TypedArray constructors. Because it is an abstract class constructor it will throw an error when invoked. The TypeArray constructors do not perform a super call to it.

So these changes are indeed part of modeling things more as classes. But no super call is made in this case.


change yolov3 to yolov4

@rajpratyush I have opened a PR. Please review it.
fixed #5

Sure i will check it tommorrow morning surely from lappy  Don't Worry 😃😃

Sure i will check it tommorrow morning surely from lappy  Don't Worry 😃😃


set-hostname: fix service dependency on avahi

Since avahi-daemon uses the hostname to create the address, it needs to be correctly set beforehand.
By changing the set-hostname service to run before avahi-daemon service, we eliminate the race condition we have now and guarantee the correct hostname for avahi.
Related-to: TOR-3562

@EdTheBearded Shouldn't this dependency be added to the avahi-daemon service definition instead (with a Wants and After)?

Hey @rborn-tx!
Yeah, I can see this solution being done both ways, but let me explain my reasoning for this one.
The way I see this, avahi is properly capturing the available hostname and using it. The thing is that we have a service that sets a different hostname for the device and we want it to be used as it's address.
And with that, the set-hostname recipe we use is not the OE one, BSP has overwritten (with a .bb instead of .bbappend) this recipe, which makes it ours, and we already have a .bbappend for this on our layer. So, for me made sense to order those from set-hostname perspective, since this is the actual one performing the change.
But if you think it makes more sense to make this change from avahi perspective I'll change it.

@EdTheBearded For me adding the dependencies through the set-hostname recipe seemed a bit odd because I see the set-hostname service as a provider of a functionality that many other services might consume and those other services might be optional. If those services were optional, then I'd like to see each dependency being created only when the optional service is actually used. At the same time, set-hostname seems more tied to Torizon OS and thus less likely to ever be optional in any of the Torizon OS variants. Considering this, it seems to me  creating the service dependency from the consumers of the functionality would be better in term of maintenance.
Well, that's my only point but I don't have a strong opinion anyways.
Perhaps we should see what @jsrc27 thinks about it.

I don't really have a strong opinion either way.
I guess the only other point I can add here is to think about the possible update path. If a user modified one of our base systemd services with an override or something, and then tried to update their OS with OTA/offline updates. Then because of how OSTree works they may not get the updated systemd service from us in our recent OS versions.
Of course I try to advise users not to modify our default systemd services for this exact reason, but it still happens from time to time. The point here being I guess we could take into account whether it is more likely users have modified either the set-hostname service or the avahi-daemon service.
All that said I don't think it's common customers have modified either really. But just something to think about.

Out of curiosity I decided to try to understand why we haven't observed this issue on TOS 6 and I noticed that on TOS 6 we have the following "After" relationships:
avahi-daemon.service
   -> systemd-resolved.service
      -> systemd-networkd.service
         -> network-pre.target
            -> set-hostname.service

But on Torizon OS 7 the relationship systemd-resolved.service -> systemd-networkd.service was removed from systemd.
With this, it seems avahi-daemon has no direct dependency to the network service which explains the issue.
So, one thing to discuss is whether adding the direct dependency to set-hostname is the best approach since it's very specific to our use case. A slightly broader solution would be to add the dependency to network-pre.target for example.


V5 migration doc

LGTM !! Except those old ADR's which still explains about the old methods. For ex: https://github.com/commercetools/commercetools-adyen-integration/blob/v5-migration-doc/docs/adr/0005-adding-line-items.md#context

ADR can be considered as logs of architectural change. It also helps the future contributors to understand our previous decisions even they are obsoleted. I would rather keep old ADRs as long as we have already provided ADR for web component v5 migration.
https://github.com/commercetools/commercetools-adyen-integration/blob/v5-migration-doc/docs/adr/0012-remove-obsoleted-api-call.md


Feature/header log

Added and tested Display headers for all sfpowerkit command with version and release

Tested all commands, PMD and all of Org Commands do not display the Header


Export InitEncode on shared library builds

Fixes: #32

Upstreaming this in https://webrtc-review.googlesource.com/c/src/+/198362


non-root image for aaa-server

@abhi270595

Reduced the size of the image in comparison to the previous image.
Created non-root image, having username auth-user with uid 1001.

test:

checked docker top <container-name>  and  the uid of process is 1001

hackcoderr@master-node:~/iudx/done/iudx-aaa-server$ docker top iudx-aaa-server_prod_1
UID                 PID                 PPID                C                   STIME               TTY                 TIME                CMD
1001                5424                5392                5                   17:17               ?                   00:01:27            java -Xmx4096m -Dvertx.logger-delegate-factory-class-name=io.vertx.core.logging.Log4j2LogDelegateFactory -jar ./fatjar.jar --host 506f7a5912e7 -c configs/config.json

After exec into
i> checked the user, using id command - it has uid 1001.

aaa-user@506f7a5912e7:/usr/share/app$ id
uid=1001(aaa-user) gid=0(root) groups=0(root)

ii) tried to remove fatjar - it's not be able to remove the jar.
aaa-user@506f7a5912e7:/usr/share/app$ rm -f fatjar.jar
rm: cannot remove 'fatjar.jar': Permission denied

Any changes are required, plz let me know.

Can one of the admins verify this patch?

Hey @abhi4578, can you please just have a quick look at the PR and confirm that I can merge it? The Dockerfiles look alright to me, but I just wanted to confirm with you before merging.

Hey mahi,
yes, mahi will look into it by today. Sorry for delay.
Thanks and regards
Abhilash V
Software Engineer
Mobile: +917892004762
Email  : @.***
India Urban Data Exchange
Indian Institute of Science, Bengaluru
Unleashing the Power of Data for Public Good
https://iudx.org.in/
https://www.linkedin.com/company/iudx/ https://twitter.com/IndiaIudx
https://www.facebook.com/India-Urban-Data-Exchange-114855197042929
https://www.youtube.com/channel/UCK9oI1VtbKnEe7cJIt_eUFA?view_as=subscriber
On Mon, 21 Mar 2022 at 10:47, Mahidhar @.***> wrote:

Hey @abhi4578 https://github.com/abhi4578, can you please just have a
quick look at the PR and confirm that I can merge it? The Dockerfiles look
alright to me, but I just wanted to confirm with you before merging.
—
Reply to this email directly, view it on GitHub
https://github.com/datakaveri/iudx-aaa-server/pull/147#issuecomment-1073494448,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHD27GZXENQSOWBDVMTUVLTVBAA5PANCNFSM5QVKW4XA
.
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:
@.***>


Allow caller to call generate_token without apns configuration

The new apns:generate_token/3 complements apns:connect/1 and apns:push_notification_token/5 and allow caller to use apns without any explicit apns config.

@dsrosario thanks for your contribution and using apns4erl! merged!


ci: add commitlint action

make repo commitizen friendly

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

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


☂-Issue for "Support for Kubernetes v1.30”

/area open-source
/kind enhancement
/priority 3
/topology garden seed shoot
Kubernetes v1.30 is getting released on April 17th, you'll find the changelog here: https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.30.md
There is this guide for developers who want to work on adding support for a new Kubernetes version.

Tasks
Gardener

[ ] gardener:

Release-independent tasks

Allow instantiating v1.30 Kubernetes clients and update README.md and docs/usage/supported_k8s_versions.md
Update feature gates in https://github.com/gardener/gardener/blob/master/pkg/utils/validation/features/featuregates.go
Update admission plugins in https://github.com/gardener/gardener/blob/master/pkg/utils/kubernetes/admissionplugins.go
Update API groups in https://github.com/gardener/gardener/blob/master/pkg/utils/validation/apigroups/apigroups.go
Update KCM controllers in https://github.com/gardener/gardener/blob/master/pkg/utils/kubernetes/controllers.go
Update KCM controllers in https://github.com/gardener/gardener/blob/master/pkg/component/shootsystem/shootsystem.go
Bump used Kubernetes version for local shoot and local e2e test
Bump kubectl version in https://github.com/gardener/gardener/blob/master/hack/tools.mk#L69

Release-dependent tasks

TODO: Derive this from the k/k changelog

"Good to know" changes / no action required

TODO: Derive this from the k/k changelog

Cloud Controller Managers

[ ] cloud-provider-gcp

Maintain legacy-cloud-providers and create release-v1.30 branch from it (update container images and revendor latest Kubernetes patch):
Maintain release-v1.29 branch (update container images and revendor latest Kubernetes patch):
Maintain release-v1.28 branch (update container images and revendor latest Kubernetes patch):
Maintain release-v1.27 branch (update container images and revendor latest Kubernetes patch):

Provider Extensions

[ ] machine-controller-manager-provider-local:

Bump kindest/node version in node/Dockerfile (example)

[ ] provider-alicloud:

Revendor gardener/gardener with support for 1.30 client creation
Update README.md with support for 1.30

[ ] provider-aws:

Revendor gardener/gardener with support for 1.30 client creation
Update README.md with support for 1.30
Update cloud-controller-manager images

[ ] provider-azure:

Revendor gardener/gardener with support for 1.30 client creation
Update README.md with support for 1.30
Update cloud-controller-manager images

[ ] provider-gcp:

Revendor gardener/gardener with support for 1.30 client creation
Update README.md with support for 1.30
Update cloud-controller-manager images

[ ] provider-openstack:

Revendor gardener/gardener with support for 1.30 client creation
Update README.md with support for 1.30
Update cloud-controller-manager images

[ ] provider-equinix-metal:

Revendor gardener/gardener with support for 1.30 client creation
Update README.md with support for 1.30

Test Infra

[ ] Ensure test-infra compatibility with conformance tests (example):

Cluster Autoscaler

[ ] Update cluster-autoscaler for K8s 1.30:

Adaptation of gardener/autoscaler:
Integration into gardener/gardener:

Follow-up items

[ ] Add K8s 1.30 support for Gardener to kubernetes/test-infra:
[ ] Add K8s conformance badges to Gardener and extensions:
[ ] Update the the conformance spreadsheet and reflect this update in our README.md:
[ ] Adapt TODOs to update the kubernetes versions in e2e tests:
[ ] Update kindest/node to v1.30.0:

/assign

All tasks are completed.
/close


Support Firebase Emulator

Extension name: firestore-stripe-subscriptions

FIrebase has great emulator tools.
How to integrate this Stripe extension with the emulator?

They do, e.g. https://github.com/stripe/stripe-firebase-extensions/blob/next/package.json#L13
But the extension emulators are still in closed alpha, you will have to wait for these to be released by the firebase team.


Long time no release

For those of us who prefer the sense of stability coming from tagged releases as opposed to dev-master, would you care to tag a new one? I've stumbled upon a bug in 0.1 that breaks the default (!) configuration (wrong is_subclass_of in OrmCacheExtension) and that is hopefully fixed in master by 62526fb. Thank you :)

Sure. I will release it today. :-)

Thanks!

Done ;-)


Introduce catch blocks to clean up the code

With the recent introduction of the question mark operator for Options, we can now clean up the codebase a lot by using small catch blocks, instead of using option_op, map, and_then, if let, etc. all over the place.
Closes #84

@wooferzfg Can you check that I didn't break anything?


Finalizing @cap-js/postgres

[x] Provide npm packed versions of @sap/cds and @sap/cds-dk
[x] Test ad-hoc deployment via cds deploy
[x] Test deployment to CF via deployer app
[x] Document all in capire / readme
[x] Document migration

Migration Guide
@cap-js/postgres works as a drop-in replacement for cds-pg.
However, some preliminary checks and cleanups help:

for using the BTP Postgres Hyperscaler as database,

know that the credentials are picked up automatically by from the enviornment (VCAP_SERVICES.postgres)
the service binding label is postgresql-db
cds-dbm is replaced by a hand-crafted "db-deployer" app → see below

your local package.json: you can safely remove the entry cds.requires.postgres previously mandatory for cds-pg
recommendation: set the env var DEBUG=sql during local development to see DB-level output from PostgreSQL

schema migration
@cap-js/postgres brings the same schema evolution capabilities to PostgreSQL known from HANA and SQLite.
Enabling schema migration in an existing cds-pg-based project consists of generating and deploying a "csn-snapshot" of your database structure.
local development
First, set a basis for the evolution
$> cds deploy --model-only
→ this will create the table cds_model laying the foundation for the schema migration
Subsequent deployments can then re-use the standard deploy mechanism via $> cds deploy
On BTP, Cloud Foundry environment
The above "csn-snapshots" can be implemented via the mtar-based approach. At the same time, the same mtar can be used for subsequent PostgreSQL deployments (with schema evolution).
Two major steps in addition to enabling the schema evoluation are included in this mtar.

create local folder deployer (any name works)
in deployer, create a package.json containing

...
"//npm run migrate": "only one-time!",
"migrate": "cds deploy --model-only",
"//npm run deploy": "subsequent deployments",
"deploy": "cds deploy"
...

add a section to your /mta.yaml denoting the deployer directory as a standalone application that runs one-time

- name: pg-db-deployer
    type: custom
    path: deployer
    parameters:
      buildpacks: nodejs_buildpack
      no-route: true
      no-start: true
      disk-quota: 2GB
      memory: 512MB
      tasks:
      - name: migrate
        command: npm run migrate
      # # for subsequent deployments
      # - name: deploy
      #  command: npm run deploy
        disk-quota: 2GB
        memory: 512MB
    build-parameters:
      before-all:
        custom:
        - npm i
        # generate the "csn-snapshot" - only necessary for one-time migration,
        # can be commented out on subsequent deployments
        - cds compile '*' -2 json > deployer/schema.csn
      ignore: ["node_modules/"]
    requires:
      - name: pg-database

resources:
  - name: pg-database
    parameters:
      path: ./pg-options.json
      service: postgresql-db
      service-plan: trial # change to yours!
      skip-service-updates:
        parameters: true
      service-tags:
        - plain
    type: org.cloudfoundry.managed-service

migration points to consider
mixed-case identifiers
even though column names that are not double-quoted are folded to lowercase in PostgreSQL (yourName -> yourname, "yourName" -> yourName),


[Feature Request] Default landing page

Is your feature request related to a problem? Please describe.
When I open portainer it shows the /home page by default. But I always immediately go to the /containers page.
Describe the solution you'd like
It would be nice to be able to set the "default" landing page. I would set it to the containers page.
Describe alternatives you've considered
None
Additional context
I'm sure it's different for different people in different environments. Maybe a sysadmin will always open the networks page as that is most relevant to him. Maybe an admin managing a cluster will always go to the stacks page. I'm mainly a dev, so I almost always go to the containers page to manage my apps. Having this as a configurable option will make many peoples' lives a tiny bit easier through better UX.
Thanks for considering it!

Because you can have multiple environments set up within Portainer, we default to the "home" page list of environments so you can choose where to start. But we are looking at our UX in general and I'll pass this suggestion onto the team working on that.

I second this suggestion. Since I am running one environment, it'd be nice if I could at least auto-select it (as default) and thus be directly able to see its status, preferably even set the default landing Page to e.g. containers or custom stacks or whatever.


[Bug]: SQL check does not detect permission issues when the database name intdoes not exist

ODC version
4.3.x
OB version
all
What happened?
SQL check does not detect permission issues when the database name in sql does not exist

What did you expect to happen?
SQL check detect permission issues when the database name in sql does not exist
How can we reproduce it (as minimally and precisely as possible)?

Anything else we need to know?
No response

Need to transfer to a requirement and need PRD and UED @Jane201510


For anyone looking at this in the future. You can add the following to your own files and it would be a local work around.
const std = @import("std");
const win32 = @import("win32");
const typedConst = win32.zig.typedConst;
const HCURSOR = win32.ui.windows_and_messaging.HCursor;
const HINSTANCE = win32.foundation.HINSTANCE;

pub extern "user32" fn LoadCursorW(
    hInstance: ?HINSTANCE,
    lpCursorName: ?[*:0]align(1) const u16,
) callconv(std.os.windows.WINAPI) ?HCURSOR;

pub const IDC_HAND = typedConst([*:0]align(1) const u16, @as(u32, 32649))
// ... repeat for the rest of the missing constants
// reference the MS docs for their values:


rclone about command to give used/quota/other stats from the provider directly

I think it would help if there was a flag to query the API for the size used on supported remotes rather than having rclone recurse through everything and finding the size. Obviously, this would only be supported when querying the size of the whole remote and not individual folders.
You could use a flag like --use-api
An example of this would be when using Google Drive as the remote so when you do rclone --use-api size google-drive: it doesn't recurse through all the folders, but instead just queries the API for the size of the remote.

maybe a new command called quota? Seems works for most storage vendors
onedrive: https://dev.onedrive.com/facets/quotainfo_facet.htm
google drive: https://developers.google.com/drive/v2/reference/about

I like the idea of rclone about.
This would need a new optional feature for the Fs which would have to return a struct with the superset of all the info - some of which might be blank.
So

total bytes used
total bytes free
total bytes quota
total bytes in trash
state string?

onedrive

total | Int64 | Total allowed storage space, in bytes. Read-only.
used | Int64 | Total space used, in bytes. Read-only.
remaining | Int64 | Total space remaining before reaching the quota limit, in bytes. Read-only.
deleted | Int64 | Total space consumed by files in the recycle bin, in bytes. Read-only.
state | string | Enumeration value that indicates the state of the storage space. Read-only

google drive

quotaBytesTotal | long | The total number of quota bytes. |
quotaBytesUsed | long | The number of quota bytes used by Google Drive. |
quotaBytesUsedInTrash | long | The number of quota bytes used by trashed items.
quotaBytesUsedAggregate | long | The number of quota bytes used by all Google apps (Drive, Picasa, etc.).

Anyone want to have a go at this?

I could try learn golang again by impl this :)

I like this idea. I think this is similar to https://github.com/ncw/rclone/issues/1138.

OK here is probably the final version of about before I merge it - comments appreciated!
https://beta.rclone.org/v1.40-089-gef3bcec7-about/ (uploaded in 15-30 mins)
See the docs here: https://github.com/ncw/rclone/blob/about/cmd/about/about.go#L44
This is supported for local, crypt, cache, drive, swift, hubic, onedrive, pcloud, dropbox

rclone about is merged to master now :-)
https://beta.rclone.org/v1.40-090-g2b855751/ (uploaded in 15-30 mins)


How to avoid hash collision for samples like descriptor_management?

I am a junior graphics development engineer.  I am learning vulkan recently and try to read the relevant sample codes.
descriptor_management make me confused. According to my understanding, differrent buffer&image bindings maybe generate same hash (by resource_cache.cpp) result which could cause wrong binding for DescriptorSet. How to avoid hash collision for samples like descriptor_management? Is there any engineering details that I didn't find?
It may not be appropriate to ask such a question here but I searched a lot of information and did not receive relevant answers.I would be very grateful if anyone could help me.

Hi @ShaoyuanLi, we discussed this on our regular samples call and discovered we didn't really have the right expertise to answer your question.  We suggest taking this question to one of the Vulkan Forums - see here for links to the various Vulkan community sites: https://www.vulkan.org/#join-our-community.  The Khronos forum listed there is a good source of knowledgeable Vulkan experts.  Reddit is always good too. LMK if that doesn't yield a good answer.  Thanks!

Oh, also, Stack Overflow is an excellent resource!  I'm adding a link to the Vulkan discussions to our Vulkan.org community page now...


Json load error

Resolves #1139

Still looking at #1156, the idea of replacing the single and double quotes seems really error prone. Why is the dumped json data in db single quoted?

Resolves also #1156

@jbe-dw I have added your improvements.

Thank you for reverting style changes. It is a lot more readable.

Hello @AdvanticGmbH, thank you for listening to our feedback and making the requested changes!
As @jbe-dw has mentioned above, json.dumps() returns a str, which is confirmed in the documentation.
With that in mind, can you please remove the str() casting from json.dumps function calls, since the function already returns a str?
Eg. turn detail=str(json.dumps({'name': template})) to detail=json.dumps({'name': template})
If there is a reason behind you using str() (eg. bugs caught in testing), please let us know so it can be kept as is.
After making this change, your feature will be ready to be merged into the codebase.
Thank you.

@jbe-dw @vmarkop Thank you for your explanation. I removed the unnecessary calls to str().

This still isnt fixed. When changing the users who have access to a domain, history gets json objects with single quotes again.

@rnilssen There is a pending PR with a fix #1182 I think this should address your case.


Security framework of XStream not initialized

E:\软件\apk-tools\jadx-master>gradlew.bat dist

Configure project :
jadx version: dev

Task :jadx-gui:createExe FAILED
Security framework of XStream not initialized, XStream is probably vulnerable.

FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':jadx-gui:createExe'.

net.sf.launch4j.BuilderException: net.sf.launch4j.ExecException: Exec failed (1): E:\软件\apk-tools\jadx-master\jadx-gui\build\tmp\launch4j\bin-launch4j-3.12\bin\windres.exe --preprocessor=type -J rc -O coff -F pe-i386 C:\Users\USER\AppData\Local\Temp\launch4j4471193961049524157rc C:\Users\USER\AppData\Local\Temp\launch4j8391365976188188787o

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org

I assume the problem is caused by your path that contains non-ascii characters: E:\软件
On my Windows system Jadx builds without problems using a patch with only ASCII characters.
I also get the warning Security framework of XStream not initialized, XStream is probably vulnerable.
This seems to be a known issue of the launch4j-gradle plugin: https://github.com/TheBoegl/gradle-launch4j/issues/82


Opened 373 tradeable mystery box to get no items

I opened 373 tradable mystery it gave me none of the items, I checked my bank there are not there. There isn't much else to say. I would like my items or the boxes. It shows the items in my collection log but the items are not there. No errors happend nothing happens out the normal. Maybe now the owner will actually do something and look into this. Quite doubtful as doesnt care unless you pay him.

Maybe now [after actually reporting the bug like you're supposed to] the owner will actually do something and look into this. Quite doubtful as doesnt care unless you pay him.
I won't be looking into this bug, not because "I don't care" but because you're disrespecting me for no reason and I don't want to help you. You're welcome to re-open this with a different message.


Make timer display

When the letterGen is run and a char is made the exitTimer is set to 50. The if statements are not set up correctly. Value always goes to exitTimer=50

Instead of making a timer find some way to convey to user that the game will end.


[Question] Exporting this library, findDomNode warning, and Transition.enter errors

I realize this is somewhat of a shot in the dark but I am just hoping someone could provide a clue as to how to solve the problem I am having. I am including this library in another library as the default toaster notification system. When attempting to use the Toaster in another project from this external library and calling addToast() I get this runtime error:
Uncaught Error: Unable to find node on an unmounted component.
    at findHostInstanceWithWarning (index.js:87875)
    at Object.findDOMNode (index.js:88394)
    at Transition.performEnter (index.js:98118)
    at Transition.updateStatus (index.js:98101)
    at Transition.componentDidMount (index.js:98045)
    at commitLifeCycles (react-dom.development.js:20663)
    at commitLayoutEffects (react-dom.development.js:23426)
    at HTMLUnknownElement.callCallback (react-dom.development.js:3945)
    at HTMLUnknownElement.nrWrapper (newrelic-core.js:2)
    at Object.invokeGuardedCallbackDev (react-dom.development.js:3994)

The above error occurred in the <Transition> component:
    at Transition ...
    at TransitionGroup ..
    at div ...

Now, I have tried to replicate this setup in a codesandbox. While I can't exactly duplicate the runtime error, i do get a warning in the console about findDomNode when calling addToast(). The way I've setup the Toaster component in the external-lib folder in codesandbox is how I have it in my external library. Does anyone see anything wrong with the implementation?
https://codesandbox.io/s/loving-kepler-5ixey?file=/src/App.js
screenshot of warning in codesandbox:

EDIT: just for some more context on this.. the error is pointing to these lines in ToastContainer and ToastProvider

Thank you for the detailed bug report!
This is a duplicate of #82

@jossmac i was actually hoping to get some insight on why I am having the other error, not the findDomNode warning that has already been mentioned.

While I can't exactly duplicate the runtime error,

Sorry @lsbyerley, it's hard for me to say without a repro

@lsbyerley ping me if you put together a repro, and i'll reopen.


Question regarding SV/CNVs during merging

Hi-
I had a question regarding the SURVIVOR tool and merging between software on a single sample. I have a python script I wrote that simply counts the number of SVs reports by a software and I was comparing this output to the reports from SURVIVOR. The question I am having is there a filter in SURVIVOR that removes SVs at specific qualities?
This is the commands I useds:
./SURVIVOR-master/Debug/SURVIVOR merge sample_files 1000 4 1 1 0 30 match_4.vcf |& tee -a ./SURVIVOR-master/Debug/SURVIVOR merge sample_files 1000 2 1 1 0 30 match_2.vcf |& tee -a ./SURVIVOR-master/Debug/SURVIVOR merge sample_files 1000 0 1 1 0 30 match_0.vcf |& tee -a
When I look at the output all four runs give the same numbers for merging entries as follows: merging entries: 32138
merging entries: 7933
merging entries: 18062
merging entries: 3395
Now when I run run my python counting script I get the following numbers:
32,200
7,938
20,892
3,395
I am wondering why in 3/4 cases they do not match. I assumed there was a filter step that SURVIVOR does that my simple counting script doesn't?
Any insight would be greatly appreciated! Thank you for making this tool!

Hi -
I'd tried calculating the the SV size using the start and end points provided but didn't take into account SV types so I was removing more than what SURVIVOR was showing. I can get matches for 3/4 software when I add the catch for type.
The one I'm still having issues with is results curated by DELLY. SURVIVOR shows 18,062 and my counts figure 20,892 (no filter). When I run the above code that works for the others it showed only 60 should be removed. If I don't restrict based on type it removes 2,447. I find this a bit puzzling. Do you think it's something with the DELLY vcf file?
Thank you for your input!

Mhm we had once a problem with Delly, because the distance of start-end does not represent the sv size tag in the info field.. maybe that is related.


Timeline is not included in Mission Post Emails

Emails should including the Timeline, but that field is blank in all functionality. This does work with the chronological_mission_posts mod.
ordered_mission_posts email
A Mission Post by Captain Test Testerman
Mission: Test Mission
Location: test
Timeline:
chronological_mission_posts email
A Mission Post by Captain Test Testerman
Mission: Test Mission
Location: test
Timeline: Mission Day 1 at 1030

Adding the Parser helper does add the Timeline information to the email, but not in the expected format.
Stardate Current:
Timeline: Mission Day 123456.79 at 123456.79
Stardate Correct:
Timeline: Stardate 123456.79 at 0830
Mission Day Time Current:
Timeline: Mission Day 1 at 1
Mission Day Time Correct:
Timeline: Mission Day 1 at 0830
Mission Date Time Current:
Timeline: Mission Day 1 at 1
Mission Date Time Correct:
Timeline: Date 2399/11/31 at 0830

fixed

tested fixed


Add case counts to partner exports.

This has PR #91 merged in so review that one first before this one.
Once #91 lands this will be easier to review.

Ready for review @KaitCrawford @jpaidoussi @rudigiesler

:+1: from me


Go with new Spring Boot 2.7

Use @AutoConfiguration
See https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-2.7-Release-Notes#changes-to-auto-configuration

made in 2.7.x
https://repo.maven.apache.org/maven2/name/nkonev/r2dbc-migrate/r2dbc-migrate-core/


[iOS] Google Sign In got error 400 Invalid_request

Android works fine, and the apple login for iOS works fine, but can not make it work for login google.
The setup is basically same as your readme, except this:
<key>GIDServerClientID</key>
<string>YOUR_SERVER_CLIENT_ID</string>

<key>GIDClientID</key>
<string>YOUR_IOS_CLIENT_ID</string>
<key>CFBundleURLTypes</key>
<array>
  <dict>
    <key>CFBundleURLSchemes</key>
    <array>
      <string>YOUR_DOT_REVERSED_IOS_CLIENT_ID</string>
    </array>
  </dict>
</array>

is this from GoogleService-Info.plist if it's not then what is that? and where can I find that?

from your google console (not firebase), you need to find (or create) a oauth entry made for iOS from the credentials page and then copy the client id (+ reverse the id as well for the CFBundleURLSchemes)


Automated Certificate Management for Ingress

Problem Statement
DataPlanes must currently be provided a certificate created manually elsewhere to serve proper HTTPS ingress traffic.
The purpose of this task is to add an integration with Cert-Manager so that certificates can be automatically created.
Acceptance Criteria

[ ] DataPlane resources should have a field for disabling automatic integration with cert-manager (default to the integration being on however)
[ ] DataPlane resources should have a field for indicating which Issuer to use when integrating with cert-manager
[ ] DataPlane resource creation should be able to tell if cert-manager is available on the system, and locate an Issuer (if not simply the default Issuer)
[ ] when cert-manager is available the creation of DataPlane resources should result in a Certificate being created to serve HTTPS ingress traffic, either with the default Issuer as defined by the cert-manager deployment or using the user-provided Issuer.
[ ] deletion of a DataPlane resource should result in deletion of its Certificate

We can reasonably defer this. It doesn't exist in any of our other deployment tooling yet, and it won't be available for all clusters anyway (it only works if cert-manager is installed).
Kong is fine spawning its own self-signed certificates to at least provide a basic set of default certs, and we expect Ingress route certs to come from their Ingress's TLS configuration.

I'm OK with deferring this post v0.1.0, but I do think it belongs in the Basic Install functionality milestones so I would definitely like to see it land in v0.2.0.


Thread.Sleep

There are some Thread.Sleep() in the code to allow the tfs server to do this or that.
If we remove those and rely on the retry mechanism, then maybe we will speed up the application considerably?

Currently, a search only reveals 3 occurrences.

Retry in case of an error is behind a Thread.Sleep https://github.com/git-tfs/git-tfs/blob/d39c306eb8a4887e81ee11ccd66912335dae0eac/src/GitTfs.VsCommon/Retry.cs#L42
Another Thread.Sleep in case of an error. https://github.com/git-tfs/git-tfs/blob/d39c306eb8a4887e81ee11ccd66912335dae0eac/src/GitTfs/Core/Ext.cs#L330
Thread.Sleep when polling the gated checkin state https://github.com/git-tfs/git-tfs/blob/d39c306eb8a4887e81ee11ccd66912335dae0eac/src/GitTfs.VsCommon/TfsHelper.Common.cs#L1351

So all of those are either only in the error case or are actually there to not do busy looping.

I am going to close this issue, if there are concrete problems etc, feel free to post further comments and we can re-open.
But right now I don't see a need for a change here...


Is this a bug?

Some instructions entered, there will be an error, the command will not play a role.

Can you specify a bit what you mean with: "Some instructions entered, there will be an error, the command will not play a role."?
Wich instructions? You mean entering commands? Do you mean an error in Discord or the one refering here? And what you mean with play a role? We play music not roles..?

For example: after entering .xp
Did not jump chart, then the background error message appears

Your error is that you don't get the .xp image? Did you do any source edits?

I have not done any source code editing

You tried backing up the db and json file and re-installing?

I have reinstalled it

goodjob

reinstall redis, or open redis.cli.exe from commandline and do FLUSHALL.
But basically this error means you've edited your xp.png and messed something up.


Update Docs: migrate Beta Features - Editorial Workflow

Continuing migration of Beta Features Documentation #7040
@martinjagodic slightly cleaner this time- last one was made editing within Decap and merging 🥲

Or perhaps this should go in the Workflow group?

I vote for the workflow group.

Ok. This is now in Workflow Group. I reworked the text a little bit.

I removed the whitespace!

While combing through the docs, I noticed this feature is also mentioned in two other places which cross link to one-another and repeat information which is also (now) getting it's own page with this pull-req.

Configuration Options > Publish Mode

Add to your Site > Editorial Workflow

I think this should be simplified with both of those sections mentioning and linking to the newly created page.

I agree, can you do that as part of this PR?

Yep. I've done what I think makes most sense in terms of consolidating and trimming. By my eye this is ready for merging.


Avoid injection for AMP pages

Love the product, yet run into one very important issues and that's the fact that for AMP pages included javascripts are not  allowed.
My setup is simple like this
    #configure tracker for website tracking
    config.middleware.use(Rack::Tracker) do
      handler :google_analytics, { tracker: Rails.application.credentials.dig(:google, :ga), ecommerce:true}
    end

I'm looking for a way in the middleware configuration to avoid the injection in case the request.rul end_with .amp
Disable by sending DNT=1 in the header works great, yet Google doesn't do that. would love to see a configuration option

you can set any tracker option dynamically during requests by providing a lambda.

thanks for the quick response, but can you give an example.
When the request is an amp request (mimeType) then it should inject.

not sure about the mime type, but you have access to everything in the rack env.
have a look here:

https://github.com/railslove/rack-tracker#google-analytics
https://github.com/railslove/rack-tracker/issues/10

@petervandeput did that help? mind to share your solution for others?

Not really, problem I'm trying to solve is that when an amp version of the page is request (e.g. by Google) the code is not injected. still haven't figured out how to do

I have no experience with AMP but let's figure this out.
Please refer to this spec as an example: https://github.com/railslove/rack-tracker/commit/f3d4e65dee9527136c7613940f5cee16fba91f88#diff-f961e0b587e363c3a6cd9a6a3a231684
You have full access to anything in the rack env hash, which might look something similar to this:
{
  "GATEWAY_INTERFACE"=>"CGI/1.1",
  "HTTP_ACCEPT"=>"text/html,application/xhtml+xml",
  "HTTP_ACCEPT_ENCODING"=>"gzip",
  "HTTP_ACCEPT_LANGUAGE"=>"en-US,en;q=0.8,de;q=0.6",
  "HTTP_CACHE_CONTROL"=>"max-age=0",
  "HTTP_HOST"=>"localhost:3000",
  "HTTP_USER_AGENT"=>"Mozilla/5.0 (Macintosh; Intel Mac OS X)",
  "HTTP_VERSION"=>"HTTP/1.1",
  "PATH_INFO"=>"/",
  "QUERY_STRING"=>"",
  "rack.version"=>[1, 3],
  "rack.url_scheme"=>"http",
  "REMOTE_ADDR"=>"<IP_ADDRESS>",
  "REMOTE_HOST"=>"localhost",
  "REQUEST_METHOD"=>"GET",
  "REQUEST_PATH"=>"/"
  "REQUEST_URI"=>"http://localhost:3000/",
  "SCRIPT_NAME"=>"",
  "SERVER_NAME"=>"localhost",
  "SERVER_PORT"=>"3000",
  "SERVER_PROTOCOL"=>"HTTP/1.1",
  "SERVER_SOFTWARE"=>"WEBrick/1.3.1 (Ruby/2.2.1/2015-02-26)",
}

Are you sure the request url contains what you're looking for? or is it maybe the referrer?
So if the env hash is not enough, you should be able to access the controller instance with env["action_controller.instance"] and ask the request object for further information to decide if you inject the tracker.

Thanks solved

@petervandeput do you want to share an example on how you solved it?
This might be helpful for others who try to do similar things.

@petervandeput see https://github.com/railslove/rack-tracker/issues/110#issuecomment-670945283


Allow per-service Maglev table sizes to be set via annotations

Best reviewed commit-by-commit. Along the way, there are a few refactoring commits.
Fixes: https://github.com/cilium/cilium/issues/14396

test-me-please

(I've incorporated the above feedback locally, but I won't push until others have gotten their reviews in as avoid disrupting pending reviews. I've also noted the CI failures. Most of the Jenkins failures are due to the BPF_F_INNER_MAP & restructuring the inner map. This is because it relies on kernels >= 5.10 and the failures were running kernels older than that. I've drafted up a commit locally to skip the Maglev tests if not on net-next.)

(I've incorporated the above feedback locally, but I won't push until others have gotten their reviews in as avoid disrupting pending reviews. I've also noted the CI failures. Most of the Jenkins failures are due to the BPF_F_INNER_MAP & restructuring the inner map. This is because it relies on kernels >= 5.10 and the failures were running kernels older than that. I've drafted up a commit locally to skip the Maglev tests if not on net-next.)

With the restructuring of the inner map, there will indeed be an upgrade/downgrade race issue. I would add a --set maglev.table=dynamic (default value could be fixed) which is an opt-in for using dynamic inner maps. Users with new deployments could select it, so the agent can probe the underlying kernel support and bail out if it doesn't fit the requirements.
Then, the existing maglev.tableSize will be the default size if no annotation has been specified (of course needs proper doc to make it clear to the user & example howto):
helm install cilium cilium/cilium --version 1.10.2 \
    --namespace kube-system \
    --set kubeProxyReplacement=strict \
    --set loadBalancer.algorithm=maglev \
    --set maglev.tableSize=4093 \
    --set maglev.table=dynamic \
    --set maglev.hashSeed=$SEED \
    --set k8sServiceHost=REPLACE_WITH_API_SERVER_IP \
    --set k8sServicePort=REPLACE_WITH_API_SERVER_PORT

We can doc and make it clear to the user that switching between dynamic / fixed would be a disruptive change. I think this approach would work nicely.

This PR seems stale and needs someone fresh to pick it up to drive it forward. I'll close it for now, but it's still linked from the parent issue so if someone wants to revive the approach and propose a new version of this PR, you are welcome to do so.


ChunkLoadError: Loading chunk 0 failed in Firefox only!

Version
4.5.8
Environment info
Environment Info:

  System:
    OS: macOS 10.15.7
    CPU: (8) x64 Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz
  Binaries:
    Node: 10.20.1 - /usr/local/bin/node
    Yarn: 1.22.4 - /usr/local/bin/yarn
    npm: 6.14.4 - /usr/local/bin/npm
  Browsers:
    Chrome: 86.0.4240.111
    Edge: Not Found
    Firefox: 82.0.2
    Safari: 14.0
  npmPackages:
    @vue/babel-helper-vue-jsx-merge-props:  1.2.1
    @vue/babel-helper-vue-transform-on:  1.0.0-rc.2
    @vue/babel-plugin-jsx:  1.0.0-rc.3
    @vue/babel-plugin-transform-vue-jsx:  1.2.1
    @vue/babel-preset-app:  4.5.8
    @vue/babel-preset-jsx:  1.2.4
    @vue/babel-sugar-composition-api-inject-h:  1.2.1
    @vue/babel-sugar-composition-api-render-instance:  1.2.4
    @vue/babel-sugar-functional-vue:  1.2.2
    @vue/babel-sugar-inject-h:  1.2.2
    @vue/babel-sugar-v-model:  1.2.3
    @vue/babel-sugar-v-on:  1.2.3
    @vue/cli-overlay:  3.12.1
    @vue/cli-plugin-babel: ^4.2.3 => 4.5.8
    @vue/cli-plugin-e2e-cypress: ^3.11.0 => 3.12.1
    @vue/cli-plugin-eslint: ^4.1.2 => 4.5.8
    @vue/cli-plugin-typescript: ^3.11.0 => 3.12.1
    @vue/cli-plugin-unit-mocha: ^3.11.0 => 3.12.1
    @vue/cli-service: 3.11.0 => 3.11.0
    @vue/cli-shared-utils:  4.5.8 (3.12.1)
    @vue/component-compiler-utils:  3.2.0
    @vue/eslint-config-prettier: ^6.0.0 => 6.0.0
    @vue/eslint-config-typescript: ^5.0.2 => 5.1.0
    @vue/preload-webpack-plugin:  1.1.2
    @vue/test-utils: 1.0.0-beta.29 => 1.0.0-beta.29
    @vue/web-component-wrapper:  1.2.0
    eslint-plugin-vue: ^6.2.2 => 6.2.2
    typescript: ~3.9.3 => 3.9.7
    vue: ^2.6.10 => 2.6.12
    vue-class-component: ^7.1.0 => 7.2.6
    vue-eslint-parser:  7.1.0
    vue-excel-export: ^0.1.3 => 0.1.3
    vue-hot-reload-api:  2.3.4
    vue-json-excel: ^0.2.98 => 0.2.98
    vue-loader:  15.9.4
    vue-property-decorator: ^8.2.2 => 8.5.1
    vue-router: ^3.1.2 => 3.4.4
    vue-style-loader:  4.1.2
    vue-template-compiler: ^2.6.10 => 2.6.12
    vue-template-es2015-compiler:  1.9.1
    vuex: ^3.1.1 => 3.5.1
  npmGlobalPackages:
    @vue/cli: 4.5.8

Steps to reproduce
Making a Library target build with chunks and copy it to another vue project
What is expected?
It should resolve the path of chunks correctly
What is actually happening?
I have a library (made by vue) that is imported to another project. There is a problem with loading the chunks in Mozilla Firefox, I don't know if this is an issue of Mozilla or Webpack because it is working in Chrome (smarter to resolve the path?) without any problem. when it is loading in chrome it uses a wrong path to load the chunk file
ChunkLoadError: Loading chunk 0 failed.

By checking the code I see the publicPath is empty in my library

for some reason that I couldn't figure out, the publicPath in Chrome turns to __webpack_require__.p="https://localhost/" but in Mozilla Firefox, it shows empty:

so it includes the sub route following the https://localhost/ to load the chunks
when I manually change the empty __webpack_require__.p="" to __webpack_require__.p="/" it starts working again.

CLI will inject codes into your lib to overwrite __webpack_require__.p . It seems these code failed to get publicPath in Firefox? Could you try to debug these codes?

CLI will inject codes into your lib to overwrite __webpack_require__.p . It seems these code failed to get publicPath in Firefox? Could you try to debug these codes?

the question is, the empty "" is correct? and the second question is if it is correct so this can be a Firefox bug that can't determine the empty path correctly?

I download the latest firefox(82.0.2), It seems firefox native support document.currentScipt on this version. And __webpack_require__.p is correct by my test

I download the latest firefox(82.0.2), It seems firefox native support document.currentScipt on this version. And __webpack_require__.p is correct by my test

seems to be related to this bug #5247 the problem was my NPM cache, it wasn't installing the library package from my new build. After deleting the node modules folder and install the packages from 0 now it is working in firefox. Thanks

Got it. This PR fixes the situation where document.currentScript is null in Firefox.

hey @fangbinwei can you reopen this again? I see the error is still happening in 1 condition even though it is fixed in prod. I updated my Vue CLI to the last version.
When I import the Async components from another Vue Project to another Vue application I see at the beginning it is loading fine and the public path is being resolved correctly but when I navigate to the route that contains an imported component the issue is still there and it is because the CurrentScript is wrong:

it is detecting the first HTML script tag in the DOM, unfortunately, and the issue is coming from this dependency<EMAIL_ADDRESS>

Update: I had to build the library of my lazy loading component in a way to set the PublicPath manually by a custom plugin
function PublicPathWebpackPlugin() {}
PublicPathWebpackPlugin.prototype.apply = function(compiler) {
    compiler.hooks.entryOption.tap('PublicPathWebpackPlugin', (context, entry) => {
        if (entry['module.common']) {
            entry['module.common'] = path.resolve(__dirname, './src/main.js');
        }
        if (entry['module.umd']) {
            entry['module.umd'] = path.resolve(__dirname, './src/main.js');
        }
        if (entry['module.umd.min']) {
            entry['module.umd.min'] = path.resolve(__dirname, './src/main.js');
        }
    });
    compiler.hooks.beforeRun.tap('PublicPathWebpackPlugin', compiler => {
        compiler.options.output.publicPath = ASSET_PATH;
    });
};

....

if (process.env.VUE_APP_TARGET === 'component') {
            config.plugins.unshift(new PublicPathWebpackPlugin());
        }


Failed MRIQC Reports

MRIQC failed for the following three datasets in OpenNeuro.
https://openneuro.org/datasets/ds000007/versions/00001
https://openneuro.org/datasets/ds000011/versions/00001?app=MRIQC&version=33&job=175bb11d-3ee6-47ee-a7ca-9cc385ab16a6
https://openneuro.org/datasets/ds000052/versions/00001?app=MRIQC&version=33&job=5720deb7-deef-4065-b86c-d58f0e49ec48

UPDATE:
Still failing:
https://openneuro.org/datasets/ds000007/versions/00001?app=MRIQC&version=33&job=f7b5739d-362e-4d11-accf-d50eac042a64
Still running since 8.17:
https://openneuro.org/datasets/ds000011/versions/00001?app=MRIQC&version=33&job=175bb11d-3ee6-47ee-a7ca-9cc385ab16a6
Succeeded after re-running:
https://openneuro.org/datasets/ds000052/versions/00001?app=MRIQC&version=33&job=5720deb7-deef-4065-b86c-d58f0e49ec48

Hi @sadevp, thanks for the reports.

[x] We already had the error of ds007 under the radar (see #621).
[ ] I'll check on ds011 tomorrow.
[x] I ran ds052 yesterday without errors, so it does not surprise me that it worked after re-running.

I'll keep you updated. I'll leave this open until we triage ds011.

DS011 was already diagnosed (failing because of #623). One subject seems to have CRC errors.


Design Task on the Glass-Morfism

Your mission is to design a Div having a GlassMorf component inside it.
#Details

make a div of 40vh height and width and give the best color/gradient of your choice which is suitable to our grepIt application.
inside the div, make a div of 30vh h and w exactly at the center having glass-morphism property. with proper blurness.
you have to share the screenshot of the design and the proper Code of the component in the glassMorf.json file in the below format.

Glass-Morfism resources are updated on Discord.
The best 5 to 6 PRs will get merged.
{
     "githubid" = "your id",
     "ss link to div" = "link1",
     "ss link to code" = "link2"
},

No need to Claim this challenge, It is open to all.

c

c

@everyone no need to claim. it is open for all.

Kindly follow that the code must have tailwind for styling purpose.

Should the code be screenshot or proper file link?

@shashankpatil28 Should the code be screenshot or proper file link?
anyone


Why does the training use BGR input instead of the original SAM's RGB input?

Why does the training use BGR input instead of the original SAM's RGB input?
https://github.com/OpenGVLab/SAM-Med2D/blob/3a7ccebd1a20c2173d2b1a60d005f997ee12f6c7/DataLoader.py#L142
There is no operation of converting BGR to RGB.

The majority of our training dataset consists of single-channel images, so whether we convert BGR images to RGB or leave them unchanged, the actual effect is the same. Additionally, if you intend to fine-tune SAM-Med2D on a dataset similar to natural images, you can consider converting BGR images to RGB. Currently, we have not observed any significant impact on performance from such a conversion.

Thank you for your response.


bug in determining longer and shorter string

var longer []rune
var shorter []rune
if len(s1) > len(s2) {
	longer = []rune(s1)
	shorter = []rune(s2)
} else {
	longer = []rune(s2)
	shorter = []rune(s1)
}

This does not work well when s1 or s2 contains non unicode rune.
For instance, let s1 = "helloworld" and s2 = "hello我的世界", and length of s1 and s2 would be 10 and 13. Then s2 is the longer one according to current code.
But s1 should be the longer one since we calculate JaroDistance by rune.

Close this issue as the fix is merged.


Fuchsia unit-test flake on attempting to writing to a channel.

This was reported as a presubmit flake. But, so far, it only seems to have happened once this past week. The specific error was:
ERROR: [../../fuchsia/sdk/linux/pkg/fidl_cpp/internal/proxy_controller.cc(73)]
  fidl channel writing error: zx_status_t -11 (ZX_ERR_BAD_HANDLE).
  message: fuchsia.sys/ServiceProviderConnectToServiceRequest, 72 bytes, 0 handles

Another instance from the past week. The test is also identical in with PlatformViewTests::CreateSurfaceTest.

See https://bugs.fuchsia.dev/p/fuchsia/issues/detail?id=76462 where the fuchsia team is tracking this

This turned out to be an error in the test author's new PR and not a flake.  Closing