Cannot build the ServiceGenerator project. Can't find GTMSessionFetcherService.m

Users of Google Cloud Endpoints need to use the Tools/ServiceGenerator project to generate client code for their APIs. These instructions (which are woefully out of date, but that's another story) talk you through it:
https://cloud.google.com/appengine/docs/java/endpoints/consume_ios
Adapting those instructions to the git repo, I am instead trying:
git clone https://github.com/google/google-api-objectivec-client.git
cd google-api-objectivec-client/Source/Tools/ServiceGenerator/
xcodebuild CONFIGURATION_BUILD_DIR=./service-generator-bin

Full build output is linked below, but in short, this project depends on GTMSessionFetcher and I've done nothing to pull it in. How should I do that? Your "BuildingTheLibrary" page on the wiki leaves me none the wiser.
build_output.txt
Supposing I want to build the ServiceGenerator using cocoapods. I create a new iOS project in XCode and add a Podfile as follows:
pod 'GoogleAPIClient', '~> 1.0.2'
pod 'GTMOAuth2', '~> 1.1.0'

Now I run pod install and see what I've got. There is no Source/Tools/ServiceGenerator directory. So then I have a look at the podspec:
https://github.com/CocoaPods/Specs/blob/master/Specs/GoogleAPIClient/1.0.2/GoogleAPIClient.podspec.json
There is no subspec for the ServiceGenerator. What am I supposed to do here?

If you stick --recursive in your clone (git clone --recursive https://github.com/google/google-api-objectivec-client.git), then you'll also pull the contents of the Deps directory and things will build.
Add spec support to build the generator would be fine also, feel free to send out a PR for that.
Most folks having needed to directly use the generator because we provide most of the generated code with the library.

fyi - I just updated the ServiceGenerator wiki also: https://github.com/google/google-api-objectivec-client/wiki/ServiceGenerator

Thanks for the quick response. Adding a subspec for the ServiceGenerator seems like the right approach, but I can't see how to submit a PR for it. The spec is of course in a separate repo. This note in that repo suggests bumping the version of the pod and that sounds like something you should be doing, not me:
https://github.com/CocoaPods/Specs/pull/12199

https://github.com/google/google-api-objectivec-client/blob/master/GoogleAPIClient.podspec is our spec.  Just send in a PR, once we merge it, we'll cut a release so folks can pull via versions, and push the spec back out.

Done: #181

@perotinus Any suggestions on if it make sense/how to add the ServiceGenerator so it is easier to get it built for use in a project?  It's a little odd because one doesn't really want the ServiceGenerators sources added to the thing that wants to use it, instead you'd just want to get it built so you could then add your own action to run it and generate some sources.

Hmm. You could add the xcodeproj to the preserve_paths, along with a script that runs it and whatever else it needs. I agree that we it's odd to add random things in Podfiles that don't get linked into the product being built.
We could also add the subspec, and a Podfile with a ServiceGenerator target, and a script that pod installs and builds that project. This might cause pod try to do funky things though, so we should make sure that that flow works correctly (or fails gracefully).

@thomasvl The updated ServiceGenerator wiki is missing the --recursive flag for git which is still critical

@bubenheimer thanks, updated.


Assets stolen

Over 6000 xlm has have disappeared from my account int he ledger saying that have been transfered to this adress
below GAL7NSYYC4CPPDQXTQYZG3UXWDWEX4TRYDG7OH42BRWZJEBFVZIJTNRD

Almost 7000 XLM has been stolen from my account in the ledger . Assets been transfered to the adresss below . GDG7YKVATM5GY4VHS4TJCQOYKG2FBCHB7SREOKGUCYURQLD4EB3AH7UE

Do you have the ID Operation to both assets disappearing? Or time and date each transaction occurred? This is not the first time people have stated assets have disappeared from a wallet/wallets. I would like to review the transactions and archive them in a repository dedicated to stolen funds/secret keys/etc.

Hello,
Thank you very much for your email
Here is a list of oll the assets that dissapeared from my ledger account
Unrecognised transactions
1 :
XLM Asset Transaction ID -
267d7d39174ce74991a087fbbbbaf80188514ee18de4b35aa1ceb2b4a3c561e4
Time of unrecognised transaction - 10:31 am
2:
XLM Asset Transaction id -
8ea1fb5a94dec9b4426c2abe9c1137e393798992b1bed221be44f3eed8a4b66a
Time of unrecognised transaction-05:31 pm
3: Cronos Crypto.com transaction Id -
523FD98C6FE10171C63B66442D422D183DF42A8D52C55C003801720C37755A4D
Time of unrecognised transaction- 10:32 am
4: Enjin coin Transaction Id-
0xdd03f29df8db44012bf0d8f4c6c7fc4e8d420fa3f57f455a4f08fc21bc948fd4
Time of unrecognised transaction- 10:34 am
5: Solana Transaction id -
5VYyyfHNRj3vTqjnLMLp1U9kK6nLeCCm2e9Fn8Syoc616PaqJ81xFr3qrizWCqkfkKvUW1v34GWXaKweoN4jsd77
Time of unrecognised transaction- 07:57 pm
Best regards
Cristian vicol
On Fri, 6 Jan 2023, 14:58 MelissaKilgore, @.***> wrote:

Do you have the ID Operation to both assets disappearing? Or time and date
each transaction occurred? This is not the first time people have stated
assets have disappeared from a wallet/wallets. I would like to review the
transactions and archive them in a repository dedicated to stolen
funds/secret keys/etc.
—
Reply to this email directly, view it on GitHub
https://github.com/stellar-expert/stellar-expert-explorer/issues/714#issuecomment-1373738935,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A47EJMMJEYPAWDI5BKEWPKDWRAXKVANCNFSM6AAAAAATKXOCJY
.
You are receiving this because you authored the thread.Message ID:
@.***>

Você tem a operação de ID para ambos os ativos desaparecerem? Ou hora e data em que cada transação ocorreu? Esta não é a primeira vez que as pessoas afirmam que os ativos desapareceram de uma carteira/carteiras. Gostaria de revisar as transações e arquivá-las em um repositório dedicado a fundos roubados/chaves secretas/etc.

bc1qw76tugkzhjgqrft7fzxg2eenzm8qj9muf5g92g

bc1qw76tugkzhjgqrft7fzxg2eenzm8qj9muf5g92g
Em sex., 6 de jan. de 2023 12:09, VcL13 @.***> escreveu:

Hello,
Thank you very much for your email
Here is a list of oll the assets that dissapeared from my ledger account
Unrecognised transactions
1 :
XLM Asset Transaction ID -
267d7d39174ce74991a087fbbbbaf80188514ee18de4b35aa1ceb2b4a3c561e4
Time of unrecognised transaction - 10:31 am
2:
XLM Asset Transaction id -
8ea1fb5a94dec9b4426c2abe9c1137e393798992b1bed221be44f3eed8a4b66a
Time of unrecognised transaction-05:31 pm
3: Cronos Crypto.com transaction Id -
523FD98C6FE10171C63B66442D422D183DF42A8D52C55C003801720C37755A4D
Time of unrecognised transaction- 10:32 am
4: Enjin coin Transaction Id-
0xdd03f29df8db44012bf0d8f4c6c7fc4e8d420fa3f57f455a4f08fc21bc948fd4
Time of unrecognised transaction- 10:34 am
5: Solana Transaction id -
5VYyyfHNRj3vTqjnLMLp1U9kK6nLeCCm2e9Fn8Syoc616PaqJ81xFr3qrizWCqkfkKvUW1v34GWXaKweoN4jsd77
Time of unrecognised transaction- 07:57 pm
Best regards
Cristian vicol
On Fri, 6 Jan 2023, 14:58 MelissaKilgore, @.***> wrote:

Do you have the ID Operation to both assets disappearing? Or time and
date
each transaction occurred? This is not the first time people have stated
assets have disappeared from a wallet/wallets. I would like to review the
transactions and archive them in a repository dedicated to stolen
funds/secret keys/etc.
—
Reply to this email directly, view it on GitHub
<
https://github.com/stellar-expert/stellar-expert-explorer/issues/714#issuecomment-1373738935
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/A47EJMMJEYPAWDI5BKEWPKDWRAXKVANCNFSM6AAAAAATKXOCJY
.
You are receiving this because you authored the thread.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub
https://github.com/stellar-expert/stellar-expert-explorer/issues/714#issuecomment-1373750876,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A37FXH2BIBX3N66GJXMOHIDWRAYSDANCNFSM6AAAAAATKXOCJY
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***
com>

bc1qw76tugkzhjgqrft7fzxg2eenzm8qj9muf5g92g
Preciso urgente transformar em dinheiro
Em sex., 6 de jan. de 2023 12:09, VcL13 @.***> escreveu:

Hello,
Thank you very much for your email
Here is a list of oll the assets that dissapeared from my ledger account
Unrecognised transactions
1 :
XLM Asset Transaction ID -
267d7d39174ce74991a087fbbbbaf80188514ee18de4b35aa1ceb2b4a3c561e4
Time of unrecognised transaction - 10:31 am
2:
XLM Asset Transaction id -
8ea1fb5a94dec9b4426c2abe9c1137e393798992b1bed221be44f3eed8a4b66a
Time of unrecognised transaction-05:31 pm
3: Cronos Crypto.com transaction Id -
523FD98C6FE10171C63B66442D422D183DF42A8D52C55C003801720C37755A4D
Time of unrecognised transaction- 10:32 am
4: Enjin coin Transaction Id-
0xdd03f29df8db44012bf0d8f4c6c7fc4e8d420fa3f57f455a4f08fc21bc948fd4
Time of unrecognised transaction- 10:34 am
5: Solana Transaction id -
5VYyyfHNRj3vTqjnLMLp1U9kK6nLeCCm2e9Fn8Syoc616PaqJ81xFr3qrizWCqkfkKvUW1v34GWXaKweoN4jsd77
Time of unrecognised transaction- 07:57 pm
Best regards
Cristian vicol
On Fri, 6 Jan 2023, 14:58 MelissaKilgore, @.***> wrote:

Do you have the ID Operation to both assets disappearing? Or time and
date
each transaction occurred? This is not the first time people have stated
assets have disappeared from a wallet/wallets. I would like to review the
transactions and archive them in a repository dedicated to stolen
funds/secret keys/etc.
—
Reply to this email directly, view it on GitHub
<
https://github.com/stellar-expert/stellar-expert-explorer/issues/714#issuecomment-1373738935
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/A47EJMMJEYPAWDI5BKEWPKDWRAXKVANCNFSM6AAAAAATKXOCJY
.
You are receiving this because you authored the thread.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub
https://github.com/stellar-expert/stellar-expert-explorer/issues/714#issuecomment-1373750876,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A37FXH2BIBX3N66GJXMOHIDWRAYSDANCNFSM6AAAAAATKXOCJY
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***
com>

bc1qw76tugkzhjgqrft7fzxg2eenzm8qj9muf5g92g
bc1qw76tugkzhjgqrft7fzxg2eenzm8qj9muf5g92g
bitcoin:bc1qw76tugkzhjgqrft7fzxg2eenzm8qj9muf5g92g?amount=0.00381237
Preciso transformar em dinheiro BRL e não sei e não consigo fazer.
Em sex., 6 de jan. de 2023 12:09, VcL13 @.***> escreveu:

Hello,
Thank you very much for your email
Here is a list of oll the assets that dissapeared from my ledger account
Unrecognised transactions
1 :
XLM Asset Transaction ID -
267d7d39174ce74991a087fbbbbaf80188514ee18de4b35aa1ceb2b4a3c561e4
Time of unrecognised transaction - 10:31 am
2:
XLM Asset Transaction id -
8ea1fb5a94dec9b4426c2abe9c1137e393798992b1bed221be44f3eed8a4b66a
Time of unrecognised transaction-05:31 pm
3: Cronos Crypto.com transaction Id -
523FD98C6FE10171C63B66442D422D183DF42A8D52C55C003801720C37755A4D
Time of unrecognised transaction- 10:32 am
4: Enjin coin Transaction Id-
0xdd03f29df8db44012bf0d8f4c6c7fc4e8d420fa3f57f455a4f08fc21bc948fd4
Time of unrecognised transaction- 10:34 am
5: Solana Transaction id -
5VYyyfHNRj3vTqjnLMLp1U9kK6nLeCCm2e9Fn8Syoc616PaqJ81xFr3qrizWCqkfkKvUW1v34GWXaKweoN4jsd77
Time of unrecognised transaction- 07:57 pm
Best regards
Cristian vicol
On Fri, 6 Jan 2023, 14:58 MelissaKilgore, @.***> wrote:

Do you have the ID Operation to both assets disappearing? Or time and
date
each transaction occurred? This is not the first time people have stated
assets have disappeared from a wallet/wallets. I would like to review the
transactions and archive them in a repository dedicated to stolen
funds/secret keys/etc.
—
Reply to this email directly, view it on GitHub
<
https://github.com/stellar-expert/stellar-expert-explorer/issues/714#issuecomment-1373738935
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/A47EJMMJEYPAWDI5BKEWPKDWRAXKVANCNFSM6AAAAAATKXOCJY
.
You are receiving this because you authored the thread.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub
https://github.com/stellar-expert/stellar-expert-explorer/issues/714#issuecomment-1373750876,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A37FXH2BIBX3N66GJXMOHIDWRAYSDANCNFSM6AAAAAATKXOCJY
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***
com>

Você tem uma operação de ID para ambos os ativos desaparecerem? Ou hora e dados em que cada transação ocorreu? Esta não é a primeira vez que as pessoas afirmam que os ativos desapareceram de uma carteira/carteiras. Gostaria de revisar as transações e arquivá-las em um repositório dedicado a fundos roubados/chaves secretas/etc.

está acontecendo a troca agora mas não se concretiza em dólares.

Boa tarde, ID do usuário16385891
On-line: 253
$ 22288,65
Saldo em 6 de janeiro às 12h58min12s
Em sex., 6 de jan. de 2023 às 11:58, MelissaKilgore <
@.***> escreveu:

Do you have the ID Operation to both assets disappearing? Or time and date
each transaction occurred? This is not the first time people have stated
assets have disappeared from a wallet/wallets. I would like to review the
transactions and archive them in a repository dedicated to stolen
funds/secret keys/etc.
—
Reply to this email directly, view it on GitHub
https://github.com/stellar-expert/stellar-expert-explorer/issues/714#issuecomment-1373738935,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A37FXH26DDGRF7E6KY6NCJLWRAXKXANCNFSM6AAAAAATKXOCJY
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***
com>

Thank you, Cristian, for prompt return of requested information. I will use the information to build a record of transactions and wallets associated with the transactions moving from your ledger into other ledgers/wallets/exchanges. After completed, I will publish for your view.

You are welcome.
Meu nome ANA MARIA DUNZER
Preciso vender urgente, como faço?
Eu não consigo fazer a troca por dólares .
O que devo fazer?
Em sex., 6 de jan. de 2023 às 13:01, MelissaKilgore <
@.***> escreveu:

Thank you, Cristian, for prompt return of requested information. I will
use the information to build a record of transactions and wallets
associated with the transactions moving from your ledger into other
ledgers/wallets/exchanges. After completed, I will publish for your view.
—
Reply to this email directly, view it on GitHub
https://github.com/stellar-expert/stellar-expert-explorer/issues/714#issuecomment-1373834388,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A37FXHZKQQQHEBO62CMRCWLWRA6URANCNFSM6AAAAAATKXOCJY
.
You are receiving this because you commented.Message ID:
@.***>

Thank you very much for your help, really appreciated.
Best regards
C. Vicol
On Fri, 6 Jan 2023, 16:01 MelissaKilgore, @.***> wrote:

Thank you, Cristian, for prompt return of requested information. I will
use the information to build a record of transactions and wallets
associated with the transactions moving from your ledger into other
ledgers/wallets/exchanges. After completed, I will publish for your view.
—
Reply to this email directly, view it on GitHub
https://github.com/stellar-expert/stellar-expert-explorer/issues/714#issuecomment-1373834388,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A47EJML3T74V2QVXBLMGNC3WRA6URANCNFSM6AAAAAATKXOCJY
.
You are receiving this because you authored the thread.Message ID:
@.***>

RECONHECE

Esperado dentro de 1 hora.

Solução imediata

Sempre eu Ana Maria Dunzer, Esperado imediato 01 hora.

Aguardando resposta

Same thing happened to me but thanks to Blackhathacker111 who helped me message him on telegram his telegram username is https://t.me/Blackhathacker111

I've fallen for this too and lost 17k XLM
I was obviously dubious on seeing the initial email from what looked like Binance. I decided to head directly over to the stellar foundation site to check on staking and everything seemed to add up when I set up the transaction.
The process seemed so legitimate! I can't believe how it trapped me. Somehow I was fooled into thinking I was still on the legitimate Stellar foundation site whilst setting up the transfer for staking!
Geeezus !   Seem the funds ended up in this wallet :
GAF6XHGIRIMWG5BXR5OVPWHRZIJ4DOPQN4AEXT3VI2GZJHGLCJGFKQTQ
The wallet still shows a balance of over 1 million XLM !


Using different texture

The old texture somehow was not red-channel-only after being written to the gltf (color space conversion?). This texture works though and is a bit clearer that it's actually a texture instead of solid red.

Yes certainly looks better than before.


Code style check for better code quality

Should we add a code style check by maven-checkstyle-plugin? We can do it one by one for all sub modules.

We already support this in Gradle.

Thanks, @jerryshao, I close this issue.


Grafana 5

Finally, switching to grafana 5.4
The series does the minimal changes needed so master would look ok and add a uid to the dashboards.
Note, you need to use -v master -M master to get the right dashboards.

@amnonh can you please share before and after screen capture?


twitter bot

I wrote a little R script [code/twitter_bot.R] that takes the data and generates some text, and 4 plots, and then posts it to a new twitter account (@ddhypothesis) that I made just for this. I got a dev account with twitter, and set-up the tokens for access. Locally, everything works fine.
Q: Can you help me set up a chron job scheduler for this on the server* to run the script 1x/day? (*is it allowed?)
Given the app is always loaded, I thought this might be a fun way to drive some interest.
p.s. I'm still working in the enhance pathways branch, so pushed changes there. Also, I .gitignored the R file where I save the tokens. This is supposed to be loaded into the environment, so will need to do that for it to have access.

In OpenShift there is a CronJob that can will periodically run a job.
Good to hear you already figured out the .gitignore bit.
We can store the tokens as a secret in OpenShift and let OpenShift pretend it's a file.
Unfortunately our OpenShift console doesn't seem to have UI for managing CronJobs, so I will need to create it on the command line.
If there are different requirements we may need to build another image or add them to the requirements for our app.
I don't see the code for twitter_bot.R in the enhance pathways branch.
Do you want to try this out in OpenShift from the enhance pathways branch?

Perhaps it'd help if I pushed, after committing changes. 🤦♂
It's there now.
Great to hear that OpenShift will run it, and if you can whip up something easy from the command line for 1x/day, that'd be great. The script doesn't load the data (assumes that the data is already loaded; same assumption for the functions). The only extra package it requires is rtweet

@matthewhirschey
Could you create a Generic Secret in OpenShift with the contents of token.R?
Steps

Go to https://manage.cloud.duke.edu/console/project/depmap/create-secret
Select "Generic Secret" in the Secret Type.
For Secret Name type "twitter-bot-token"
For Key type "token.R"
For Value browser for your file or paste the contents in the box.
Click Create.

I can then Setup a CronJob that will pull this in as code/token.R.
Thanks.

Done.
As you can see, the R script calls a function from rtweet that creates the token, and stores it in the environment. I don't call library() because this never runs alone (it's run from within the other R script).

Running twitter_bot.R fails with object 'surprise_genes' not found
It looks like twitter_bot.R assumes surprise_genes, gene_summary, etc are already loaded in the R environment.
Do we need to add some readRDS calls or is there some other method to setup the R environment?

Yes, that is the assumption. If this is going to be run as a stand alone script (i.e not in the environment of the app), then I will add some readRDS and source calls.

@matthewhirschey Looks like you got the readRDS and source calls added. I think I have the CronJob ready to go.
Are you good with me setting it up to run at 12 to see if it works?

I gave a 👍, but I'll be more explicit: yes, OK to test anytime. Yesterday, I 'spammed' the one follower I had while developing it LOL. But really not that big of a deal

I finally got everything sorted out. There should be two new tweets. The one from around 12:40 is from the cron job.
There was an issue with create_token failing when trying to write .rtweet_token.rds. I used the set_renv flag = FALSE and passed the token directly to post_tweet.
@matthewhirschey What is the twitter handle we are posting to?

@ddhypothesis
https://twitter.com/ddhypothesis

Where is the cron job code? I'm curious to take a look.

I pushed the cron job template to the enhance_pathways.
https://github.com/matthewhirschey/ddh/blob/enhance_pathways/openshift/TwitterCronJob.yaml

The schedule  line value "0 8 * * *" specifies 8 AM: https://crontab.guru/every-day-8am

The version I deployed is slightly different from what I pushed to github. The current deployed version uses an image built from the enhance_pathways branch and will tweet around 12:40 each day. The version pushed to github should be good for when the enhanced_pathways branch is merged.


Fix wrong variable names in text.md

Fixes #1269

These lines seem to be 4 years old - no one read it all the at carefully I guess?


Register Phi 3.5 moe SUT + Add "instruct" to Phi UIDs

And sorry to be rude, but I'm merging this so I can build the hopefully-final docker image.


CMakeLists: Fix Cross Compile

When Cross compiling, the CMAKE_INSTALL_PREFIX (i.e. target) might be different from the CMAKE_PREFIX_PATH (i.e. host). In order, to properly cross-compile, use the CMAKE_PREFIX_PATH instead of CMAKE_INSTALL_PREFIX.
Signed-off-by: Matthias Schoepfer<EMAIL_ADDRESS>

Any opinions here?!

I'm slightly hesitant to approve this just because the primary scenario this packages is used in does not have this problem and I know that the current behavior works the way we want it to in all supported cases. This is a bit of a drive by review and so I haven't taken the time to consider whether the proposed change still produces the desired behavior in our principal use case.
This package is primarily intended to support the generation of ROS 2's modular binary packages (the debs and rpms) and that process explicitly does not support cross-compilation.
Can you please share a bit more about how you're using this package, with this change, in a cross-compilation context.

Hi!
My company wants to use ROS in a real world product. Not just an interface to ros, but actually run the robot with ros. We therefore use meta-ros since Ubuntu is not a good solution if you want to have your custom embedded linux distribution.


ci: Run Integration Tests as part of PR checks

Description
As the PR title suggests, this allows us to enforce that integration tests are run as part of the PR validation checks.
Currently, we are only running unit tests with make test. In the past, make test used to cover a lot more via EnvTest, but this part has been moved to a make integration-test target since https://github.com/janus-idp/operator/pull/272).
As I almost always happen to run this target (along with the E2E tests) when reviewing PRs, I think we should enforce those integration tests as part of the automatic PR checks. Unlike the E2E tests, they don't take that long to run and do not require a cluster to run.
Which issue(s) does this PR fix or relate to
—
PR acceptance criteria

[ ] Tests
[ ] Documentation
[ ] If the bundle manifests have been updated, make sure to review the rhdh-operator.csv.yaml file accordingly

How to test changes / Special notes to the reviewer
Job passing: https://github.com/janus-idp/operator/actions/runs/9177666830/job/25235797784?pr=365

/cc @gazarenkov @coreydaley

I think "make test" already included integration_tests, no?
Like:
ok      redhat-developer/red-hat-developer-hub-operator/controllers     0.529s  coverage: 22.8% of statements
ok      redhat-developer/red-hat-developer-hub-operator/integration_tests       7.824s  coverage: 42.2% of statements
ok      redhat-developer/red-hat-developer-hub-operator/pkg/model       1.240s  coverage: 84.6% of statements

🤔 Interesting.. I thought so initially, but they didn't seem to be included on my machine:
$ make test
test -s /home/asoro/work/projects/backstage/janus-idp/operator/bin/controller-gen || GOBIN=/home/asoro/work/projects/backstage/janus-idp/operator/bin go install<EMAIL_ADDRESS>/home/asoro/work/projects/backstage/janus-idp/operator/bin/controller-gen rbac:roleName=manager-role crd webhook paths="./..." output:crd:artifacts:config=config/crd/bases
/home/asoro/work/projects/backstage/janus-idp/operator/bin/controller-gen object:headerFile="hack/boilerplate.go.txt" paths="./..."
test -s /home/asoro/work/projects/backstage/janus-idp/operator/bin/goimports || GOBIN=/home/asoro/work/projects/backstage/janus-idp/operator/bin go install<EMAIL_ADDRESS>find . -not -path '*/\.*' -name '*.go' -exec /home/asoro/work/projects/backstage/janus-idp/operator/bin/goimports -w {} \;
go vet ./...
test -s /home/asoro/work/projects/backstage/janus-idp/operator/bin/setup-envtest || GOBIN=/home/asoro/work/projects/backstage/janus-idp/operator/bin go install sigs.k8s.io/controller-runtime/tools/setup-envtest@c7e1dc9b5302d649d5531e19168dd7ea0013736d
mkdir -p /home/asoro/work/projects/backstage/janus-idp/operator/bin/default-config && cp config/manager/default-config/* /home/asoro/work/projects/backstage/janus-idp/operator/bin/default-config
LOCALBIN=/home/asoro/work/projects/backstage/janus-idp/operator/bin KUBEBUILDER_ASSETS="/home/asoro/work/projects/backstage/janus-idp/operator/bin/k8s/1.25.0-linux-amd64" go test redhat-developer/red-hat-developer-hub-operator redhat-developer/red-hat-developer-hub-operator/api/v1alpha1 redhat-developer/red-hat-developer-hub-operator/controllers redhat-developer/red-hat-developer-hub-operator/integration_tests redhat-developer/red-hat-developer-hub-operator/pkg/model redhat-developer/red-hat-developer-hub-operator/pkg/utils -coverprofile cover.out
?       redhat-developer/red-hat-developer-hub-operator [no test files]
?       redhat-developer/red-hat-developer-hub-operator/api/v1alpha1    [no test files]
ok      redhat-developer/red-hat-developer-hub-operator/controllers     0.013s  coverage: 22.8% of statements
?       redhat-developer/red-hat-developer-hub-operator/pkg/utils       [no test files]
ok      redhat-developer/red-hat-developer-hub-operator/pkg/model       0.057s  coverage: 85.4% of statements

I think "make test" already included integration_tests, no?
Like:
ok      redhat-developer/red-hat-developer-hub-operator/controllers     0.529s  coverage: 22.8% of statements
ok      redhat-developer/red-hat-developer-hub-operator/integration_tests       7.824s  coverage: 42.2% of statements
ok      redhat-developer/red-hat-developer-hub-operator/pkg/model       1.240s  coverage: 84.6% of statements

🤔 Interesting.. I thought so initially, but they didn't seem to be included on my machine:
$ make test
test -s /home/asoro/work/projects/backstage/janus-idp/operator/bin/controller-gen || GOBIN=/home/asoro/work/projects/backstage/janus-idp/operator/bin go install<EMAIL_ADDRESS>/home/asoro/work/projects/backstage/janus-idp/operator/bin/controller-gen rbac:roleName=manager-role crd webhook paths="./..." output:crd:artifacts:config=config/crd/bases
/home/asoro/work/projects/backstage/janus-idp/operator/bin/controller-gen object:headerFile="hack/boilerplate.go.txt" paths="./..."
test -s /home/asoro/work/projects/backstage/janus-idp/operator/bin/goimports || GOBIN=/home/asoro/work/projects/backstage/janus-idp/operator/bin go install<EMAIL_ADDRESS>find . -not -path '*/\.*' -name '*.go' -exec /home/asoro/work/projects/backstage/janus-idp/operator/bin/goimports -w {} \;
go vet ./...
test -s /home/asoro/work/projects/backstage/janus-idp/operator/bin/setup-envtest || GOBIN=/home/asoro/work/projects/backstage/janus-idp/operator/bin go install sigs.k8s.io/controller-runtime/tools/setup-envtest@c7e1dc9b5302d649d5531e19168dd7ea0013736d
mkdir -p /home/asoro/work/projects/backstage/janus-idp/operator/bin/default-config && cp config/manager/default-config/* /home/asoro/work/projects/backstage/janus-idp/operator/bin/default-config
LOCALBIN=/home/asoro/work/projects/backstage/janus-idp/operator/bin KUBEBUILDER_ASSETS="/home/asoro/work/projects/backstage/janus-idp/operator/bin/k8s/1.25.0-linux-amd64" go test redhat-developer/red-hat-developer-hub-operator redhat-developer/red-hat-developer-hub-operator/api/v1alpha1 redhat-developer/red-hat-developer-hub-operator/controllers redhat-developer/red-hat-developer-hub-operator/integration_tests redhat-developer/red-hat-developer-hub-operator/pkg/model redhat-developer/red-hat-developer-hub-operator/pkg/utils -coverprofile cover.out
?       redhat-developer/red-hat-developer-hub-operator [no test files]
?       redhat-developer/red-hat-developer-hub-operator/api/v1alpha1    [no test files]
ok      redhat-developer/red-hat-developer-hub-operator/controllers     0.013s  coverage: 22.8% of statements
?       redhat-developer/red-hat-developer-hub-operator/pkg/utils       [no test files]
ok      redhat-developer/red-hat-developer-hub-operator/pkg/model       0.057s  coverage: 85.4% of statements

They appear to be included in the CI, but I still am not sure why they are not on my machine. Closing this PR since they run in CI - will look into the local issue later.
/close


Update tld package to 0.12

Summary:

Changes user_requirements.txt to tld~=0.12

Removes SD's separate parsing of the TLD file, compensating with additional checks using the tld package

Maintains compatibility with tld 0.90, so SD instances runners don't have to run
  pip3 install --user -r user_requirements.txt --upgrade

after this merges. SD instance runners should do so, but things won't break if they don't.

Adds additional "misleading link" tests to CI

Adds an additional exclusion to the "misleading link" detection, so link text which is at the end of the URL is not detected (e.g. not detect detect URLs like "https://example.com/foo.txt" for link text "foo.txt")

Fixes Travis CI so that it tests the code in PRs, rather than always testing the current master branch.

Longer description:
As a result of a change in where the TLD list is stored on the net, the tld package has been updated to version 0.12 to fetch the list from the new URL. This is the same issue that brought our SD instances down a few days ago. Merging this PR and then all SD instance runners executing:
pip3 install --user -r user_requirements.txt --upgrade

will get us back to a bit better off than we were prior to the URL change.
Moving to tld~=0.12 resulted in some incompatibilities with our code, so additional changes to SD were needed.
Specifically, the tld.defaults.NAMES_LOCAL_PATH property was removed from the package. That property was undocumented and not supported by the tld package. We were using the property to determine where the tld package stores the file containing the list of TLDs in order for SD to parse the file itself and verify that the link text we were testing contained all of a TLD preceded by a .. Effectively, this resulted in verifying that the link text contained a first level domain (FLD) in addition to a TLD. The only place this was being used was in the "misleading link" detection. The code for our parsing the TLD file was removed and an additional check was added to perform the same overall task, but not requiring us to parse the TLD file ourselves.
Compatibility was maintained with tld version 0.9.0, which was the version we previously specified as the minimum. This should allow this to be merged and run on existing SD instances without requiring that they update to tld 0.12 prior to running on this commit.
We're no longer using an undocumented feature of tld, so the package is allowed to use future releases based on the 0.* version, rather than locking it to 0.12.*.
(Not actually part of updating to tld 0.12): An additional exclusion was added to reduce FP on the misleading link detection. Link text which parses to a domain will no longer be detected, if the tail of the href URL matches the link text. This means that it won't detect URLs like "https://example.com/foo.txt" for link text "foo.txt".
Some additional tests were added for misleading links.
The issue with Travis always testing the master branch was identified after this PR was opened. There's more detail in my later comments.

I'm not sure what's going on with Travis CI. The output from Travis CI indicates it's testing the old code, not the code as of the last commit in this PR. The output shows the  test/test_findspam.py tests without the ones which were added in the PR's 4th commit (8057ddb), and shows log output of "malicious.com: not an SE domain", which was a log output that was removed in the PR's 2nd commit
(872730d).
Basically, the Travis CI output is at least very similar to what I recall when testing the code with only the PR's 1st commit.

So, for the CI tests, Travis only gets "collected 299 items", but Circle CI gets "collected 304 items".
I've tried running this on Travis in my fork. When the code is in a branch other than master, it fails, but if I run the same thing in the master branch, it passes.

OK. Found the problem. The .travis.yml file includes the lines:
before_script:
  - sh test/spinup_git.sh

And test/spinup_git.sh includes:
git checkout --track origin/deploy
git checkout master

The history for those two files indicates those two git commands have been run since 2018-10. So, at least since that time, Travis CI hasn't been actually running on any PR. It's always been running against the master branch. It's only causing a problem here because the master branch fails with tld package version 0.12 and the pip3 install -r user_requirements.txt --upgrade is executed after Travis checks out the branch that is supposed to be tested and before test/spinup_git.sh is run.
I'll push a fix.

@iBug @teward Just a heads-up that after this PR is merged, in order to update the tld package to 0.12, it will be desired that you pull and execute:
pip3 install -r user_requirements.txt --upgrade

However, it is not required that you do so. Your SD instances will run with this code merged and tld versions between 0.9.0 and 0.9.8, which were the permitted versions with the old user_requirements.txt entry. Until the tld version is updated on your instance, the instance will continue to be unable to update the TLD list, as is currently the case.

@iBug @teward Just a heads-up that after this PR is merged, in order to update the tld package to 0.12, it will be desired that you pull and execute:
pip3 install -r user_requirements.txt --upgrade

However, it is not required that you do so. Your SD instances will run with this code merged and tld versions between 0.9.0 and 0.9.8, which were the permitted versions with the old user_requirements.txt entry. Until the tld version is updated on your instance, the instance will continue to be unable to update the TLD list, as is currently the case.

Uhhhhh... Osiris is actually running a fork of 0.11 with the changes that were included in 0.12 early.  So there's actually no need to pull until we update anything else heh.

@teward

Uhhhhh... Osiris is actually running a fork of 0.11 with the changes that were included in 0.12 early. So there's actually no need to pull until we update anything else heh.

With effectively tld 0.12, there's a minor issue which causes some undesired operation in the "misleading link" code.  It will be resolved when this PR is merged.

I went ahead and merged this. Having it merged should get the "misleading link" detection functional again.


password encrypted with jasypt is breaking when refreshed

we are using spring boot version 2.1.10.RELEASE and cloud version  Greenwich.SR3 and we are using jasypt for encrypted passwords. I kept encrypted passwords on application.yml file. During configserver startup it is getting decripted properly and working fine. If I make any changes on application.yml file  and hit bus/refresh, my decripted password automatically getting encrypted back and not decripting. Can some one help on this?

Are you guys using the starter plugin?

can you try version 3.0.3 that just went out?

I got confirmation the refresh mechanism should be back in business from another issue #211, closing


fix getAttachment, return default value

related issue https://github.com/apache/dubbo/issues/9972

Codecov Report

Merging #10008 (8fb0773) into 3.0 (bce439e) will decrease coverage by 0.21%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##                3.0   #10008      +/-   ##
============================================
- Coverage     65.69%   65.47%   -0.22%
- Complexity      294      320      +26
============================================
  Files          1215     1215
  Lines         53040    53004      -36
  Branches       8034     8004      -30
============================================
- Hits          34842    34704     -138
- Misses        14386    14480      +94
- Partials       3812     3820       +8

Impacted Files
Coverage Δ

.../main/java/org/apache/dubbo/rpc/RpcInvocation.java
65.85% <0.00%> (-0.49%)
:arrow_down:

...dubbo/remoting/zookeeper/ZookeeperTransporter.java
55.55% <0.00%> (-33.34%)
:arrow_down:

...ng/zookeeper/curator5/Curator5ZookeeperClient.java
44.44% <0.00%> (-27.06%)
:arrow_down:

.../remoting/api/SingleProtocolConnectionManager.java
61.53% <0.00%> (-23.08%)
:arrow_down:

...nt/metadata/ServiceInstanceHostPortCustomizer.java
65.78% <0.00%> (-21.06%)
:arrow_down:

...ache/dubbo/remoting/transport/AbstractChannel.java
75.00% <0.00%> (-12.50%)
:arrow_down:

...dubbo/common/status/support/LoadStatusChecker.java
50.00% <0.00%> (-11.54%)
:arrow_down:

.../remoting/transport/netty4/NettyServerHandler.java
62.79% <0.00%> (-9.31%)
:arrow_down:

...ava/org/apache/dubbo/rpc/proxy/InvocationUtil.java
81.81% <0.00%> (-9.10%)
:arrow_down:

...mmon/threadpool/support/fixed/FixedThreadPool.java
80.00% <0.00%> (-7.50%)
:arrow_down:

... and 54 more

Continue to review full report at Codecov.

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


PR failed on jdk10 build

My PR https://github.com/knowm/XChange/pull/2784 failed on the jdk10 build due, so it seems, to something outside of my control. JDK8 build was fine.
What do I need to do to resolve this?

Seems there was a problem with the maven repository during build.
I've left you some comments in your PR. When you've push the fixed a new build will start.


repository structure?

Hi Christopher,
I appreciate your book and your code, but I'm not very happy with the way this repository is organised. Could you split it and move the tools separate from the sources?
I'm using OS X and the Windows specific tools are of little use for me (not to mention the use of Git for distributing very large binaries, available anyway from their publishers).
Also, a more portable approach would be highly appreciated. For ARM projects you can use Eclipse and the GNU ARM Eclipse plug-ins.
Thank you,
Liviu

Hi I like the your book but I'm having serious problems implementing your examples.
I am seeing the previous discussions and I realize that the repository is directed to use an IDE and the process becomes seriously terrible, if that IDE is not used in particular. I think that anyone should implement your examples from a simple terminal

Hi. Thanks for the comment. Yes, I am aware of this weakness. Would *nix Makefiles for GNUmake be a good starting point? I could generate these if desired.
Regards, Chris.

From my experience with GNU ARM Eclipse, properly written makefiles are quite portable.
However, for Windows, the key is having a new and correctly configured & packed make, otherwise there are countless problems, like line length, paths with spaces, etc.
For those interested, I maintain a Windows Build Tools package that can be used without problems outside GNU ARM Eclipse: http://gnuarmeclipse.github.io/windows-build-tools/.

A generic Makefile would be a very good idea

The various points in this issue have been handled.
Repository structure is now cleaner.
Generic build is supported with various build improvements over the years.


get_output_names() returns garbled text on MacOS

get_output_names() returns garbled text and duplicates same name.
>>> import mido
>>> mido.get_output_names()
['IACdriver „Éê„Çπ1', 'IACdriver „Éê„Çπ1']

Here is an actual setting of Mac MIDI studio.

Environment

mido 1.2.10
MacOS Ventura on M1 Mac
Python 3.9.13 (Universal2 version)

Here is the result.
>>> import mido
>>> mido.backend
<backend mido.backends.rtmidi (not loaded)>

Thank you, I'll try to reproduce as soon as I can (I have a mac laying around but it's not my main OS).

Hello. I found the problem is also happened on get_ports() of python-rtmidi.
And my macOS is Japanese version and actual port name contained Japanese multibyte character.
It seems python-rtmidi can't handle multibyte character of port name.
So I will close this issue. Thank you for your help.

Thanks for reporting back!
Have you filed a bug upstream?
If so, I'd like to have a link to track the resolution.
Else, could you please do so.
Thanks again.

Hello. I submitted a issue on python-rtmidi GitHub.
https://github.com/SpotlightKid/python-rtmidi/issues/180
Now I found the issue also happens on Windows, not only Mac.

There was an answer at rtmidi issue, but the problem was resolved by specifying encoding like below.
rtmidi.MidiOut().get_ports("utf-8")
Now, I also tried to set encoding on mido.get_output_names(), but the result was unchanged.
Is there any solutions? Thank you.

>>> import mido
>>> mido.backend
<backend mido.backends.rtmidi (not loaded)>

>>> mido.get_output_names()
['Microsoft GS Wavetable Synth 0', 'loopMIDI Port 1', 'loopMIDI Port 1ã\x81»ã\x81\x92 2']

>>> mido.get_output_names(encoding="utf-8")
['Microsoft GS Wavetable Synth 0', 'loopMIDI Port 1', 'loopMIDI Port 1ã\x81»ã\x81\x92 2']


Use specificity score in result filtering

https://issues.redhat.com/browse/HACBS-1986

This approach was inspired by CSS Specificity.
I was happily surprised at how well the algorithm behaves with the existing tests. No change in behavior other than fixing the issue reported in HACBS-1986 which is encouraging.
I can see an argument that this approach makes it harder for a user to understand the filtering rules. However, it does feel natural to leverage specificity as a mechanism to determine precedence.

Does this change mean the existing examples now do work as described?

Does this change mean the existing examples now do work as described?
Edit: I think it does from your comment above.

Yup!


Add SNMP

Add SNMP to Repository

tested
passed builds 0.5.0
Documentation DE/EN/RU
Languages DE/EN/RU

Realy great job! I checked everything again and looks really great. There is no news in the io-package.json, but it is a new adapter and ready for the repository. thx

Welcome snmp :-))


Add ctr flags for configuring default TLS credentials for registry

This adds new flags to the ctr tool for configuring TLS credentials:

--tls-root-ca is the path to a root CA certificate, to be used when verifying the server's identity.
--tls-client-cert and --tls-client-key are paths to the components of a TLS client keypair, used to authenticate with a server that requires mTLS authn.

See https://github.com/containerd/containerd/issues/3071 for context. This approach is more flexible than the hosts.toml solution (at the cost of higher per-call config verbosity), and can be used for cases such as integration tests and ad-hoc administrative scripts where maintaining a separate directory structure of per-registry certs is impractical.
R: @crosbymichael,@estesp
CC: @mmoriarity-stripe

The CI / cgroup2 (pull_request) test failure appears unrelated, though I don't know enough about the containerd test suite to confirm that.

Please squash the commits

Please squash the commits

Done.


required class panel missing

Tried to set up the panel, pretty sure I set it up right but when I go to the site I just get "The required class PDO could not be found. "
not sure what I could do about this help would be appreciated thanks.

I would guess your PHP version is too old, see if you can change it to PHP 7.4 or PHP 8.

I'm on php8 using FreeBSD for the OS and "Caddyserver" has the webserver, I can't really see why it isn't working should I be using something like apache or similar?

I would guess that your PHP doesn't have the PDO driver in it, you'd have to find how to get that for your specific version.

Hey, I've managed to add the driver but now I'm just getting a blank page, it might just be the permissions but I didn't think that it needed perms other than just what there was there (rx) to display is there something I didn't do right here or~

Spent a bit more time working on it, even switched to apache to see if that would work better and now i'm getting this error:
PHP Fatal error:  Uncaught Error: Call to undefined function session_status() in /usr/local/www/apache24/data/class/class.base.php:7\nStack trace:\n#0 /usr/local/www/apache24/data/assets/php/session-header.php(3): require_once()\n#1 /usr/local/www/apache24/data/security.php(3): require_once('/usr/local/www/...')\n#2 /usr/local/www/apache24/data/index.php(3): require_once('/usr/local/www/...')\n#3 {main}\n  thrown in /usr/local/www/apache24/data/class/class.base.php on line 7

Sounds like you have PHP 5.3 or earlier installed.

php -v returns with php 8.0.13

Yes but the apache or the earlier webserver might use it's own PHP version. session_status() was added in PHP 5.4.

I'll try to check but not sure where exactly I'd be looking for this

Create a PHP file containing <?php phpinfo(); ?> and open that page to see all the PHP information.

did that and it looked fine, I also tried updating "Zend" or whichever and now I'm getting this instead:
PHP Fatal error:  Uncaught Error: Undefined constant "FILTER_SANITIZE_STRING" in /usr/local/www/apache24/data/__UNAM_LIB/unam_lib.php:141\nStack trace:\n#0 /usr/local/www/apache24/data/assets/php/session-header.php(38): unam_lib->unam_filterAllParameters(10000)\n#1 /usr/local/www/apache24/data/security.php(3): require_once('/usr/local/www/...')\n#2 /usr/local/www/apache24/data/index.php(3): require_once('/usr/local/www/...')\n#3 {main}\n  thrown in /usr/local/www/apache24/data/__UNAM_LIB/unam_lib.php on line 141

Hey, wondering if you found anything or the such just am not sure what is going wrong here now so yeah help would be appreciated if you don't mind thanks either way though

No I haven't really seen that error before, did you follow a guide to set it all up or just winged it?

Well I mostly did just wing it but all my php dependencies and such should be updated and working, I know with my caddy setup PHP works well so really I'm not sure what I could've done differently

Really weird, I've released a new version now but that shouldn't really change that, FILTER_SANITIZE_STRING has gotten deprecated as of PHP 8.1 (though you have 8.0) and even then it's still usable of course.

Hey, yeah I tried the update and it seemed to have the same error, I'm not sure what I would've done wrong, is there anything you could think of that might cause this?

Just got it fixed somehow thanks for your help with this really appreciate it!


DatePicker is not being Displayed in tiny Breakpoints for some of the DatetimePicker tests.

Description
Datepicker is not being displayed in tiny breakpoints for some of the Datetimepicker tests. due to which WDIO tests of MPAGE Theme repo are failing as the datepicker element is not being found in the DOM.
During the PR #2452 for [UpdateBreakpoint ranges] the defaultElement prop of ResponsiveElement was removed and existing defaultElement prop was updated to tiny. this needs to updated in this repo as well for terra-datepicker.
Steps to Reproduce
Refer Terra-responsive-element from master branch of terra-core and check the below tests for Terra-Datetime-picker in tiny breakpoints.
https://engineering.cerner.com/terra-framework/#/tests/terra-date-time-picker/date-time-picker/date-time-picker-filter-dates
Additional Context / Screenshots
issue screenshot :-

Correct screenshot :-

Expected Behavior
DatePicker should display for all the breakpoints of datetimepicker examples
Possible Solution
Update defaultElement prop of ResponsiveElement in DatePicker.jsx as tiny

For clarity, this is only a problem in the theme repositories because they are pulling all snapshots from master. Terra Framework cannot be updated until the changes to the responsive element have been released.

Just found couple of place which also needs to be updated with Responsive element changes :

terra-application-header-layout

2.terra-tabs

Fixed by : https://github.com/cerner/terra-framework/pull/745


Sharedrop keeps loading after deployment

I think I might have done something wrong, as I'm not familiar, with the firebase db.
I created a realtime db, copied the link shown under the "Data" tab and put it in the FIREBASE_URL env.
I changed the rules to this:
{
  "rules": {
    ".read": true,
    ".write": true
  }
}

[Sign up](https://www.firebase.com/) for a Firebase account and create a database.
Go to "Security Rules" tab, click "Load Rules" button and select firebase_rules.json file.
Take note of your database URL and its secret, which can be found in "Secrets" tab.

I think some things might have changed on the firebase side as I couldn't find "Load Rules", just a Rules tab.
The "Secrets" tab I couldn't find that either. I guess it's all within the Rules editor now?
I put nothing in the FIREBASE_SECRET env (for testing).
Unfortunately I don't see any logs of not being able to connect to a firebase db.
So I'm not sure if it connects or not.
Can someone tell me what I'm doing wrong?
https://sharedrop.mindglowing.art/

the same thing happens to me

how can we solve it

You can get FIREBASE_SECRET when you go to Project settings -> Service accounts -> Database secrets.
However, I do not know if these secrets are created for new Firebase projects, as they are marked as deprecated.

@kenjibailly The error handling could be done better, but the error I'm getting on your page is the following:
"FIREBASE FATAL ERROR: Cannot parse Firebase url. Please use https://<YOUR FIREBASE>.firebaseio.com "

I tried to find that "firebasio" url, but couldn't find it. So I just tried to change FIREBASE_URL with these:
https://sharedrop-mindglowingart.firebaseio.com/
https://sharedrop-mindglowingart-default-rtdb.europe-west1.firebaseio.com/
But they also keep loading.
All I can find is
https://sharedrop-mindglowingart-default-rtdb.europe-west1.firebasedatabase.app/
I'm not entirely sure how to proceed from here, thanks for answering though!

For Sharedrop the FIREBASE_URL is https://sharedrop.firebaseio.com. This is the URL that I see in Firebase console when I go to "Realtime Database" and "Data":

If you deploy a new version with a correct FIREBASE_URL and it still doesn't work, let me know and I can see if I can find what's wrong. This would help me to update the docs to make it easier for others to deploy it themselves.

For Sharedrop the FIREBASE_URL is https://sharedrop.firebaseio.com. This is the URL that I see in Firebase console when I go to "Realtime Database" and "Data":

If you deploy a new version with a correct FIREBASE_URL and it still doesn't work, let me know and I can see if I can find what's wrong. This would help me to update the docs to make it easier for others to deploy it themselves.

Well that's the initial url I used, please have a look at my screenshot.

Got it. Most likely the URL pattern has changed, but the ~10 year old version of Firebase library used in Sharedrop does not support the new URL pattern :/ I can see if I can update the library, but it might be non-trivial, as a lot has changed :/

Got it. Most likely the URL pattern has changed, but the ~10 year old version of the Firebase library used in Sharedrop does not support the new URL pattern :/ I can see if I can update the library, but it might be non-trivial, as a lot has changed :/

Okay thank you for looking into it, please let us know if you got an update regarding this!

I changed the json file and removed all . and $ and stuff like that

firebase.txt

can it be a solution?
because then you can load that file

Has someone found a solution to the new URL format of Firebase databases?


[tests-only][full-ci]added test to list drives after the share role has been disabled

Description
This PR adds the test to list the available drives after the share role has been disabled.
Related Issue

https://github.com/owncloud/ocis/issues/10711

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Technical debt
[x] Tests only (no source changes)

Checklist:

[ ] Code changes
[ ] Unit tests added
[x] Acceptance tests added
[ ] Documentation ticket raised:

Moving this PR to in progress to update according to comment https://github.com/owncloud/ocis/pull/10744/files#r1899452910

Moving this PR to in progress to update according to comment https://github.com/owncloud/ocis/pull/10744/files#r1899452910

Back to Review on Progress :eyes:


Improved smartSearchEngine for migration process

added cyrillic letters and chapter reference strip

@jobobby04 would you merge this?


Extension causes high cpu load

Issue Type: Performance
Extension Name: vscode-kubernetes-tools
Extension Version: 0.1.18
OS Version: Darwin x64 18.5.0
VSCode version: 1.33.1

ms-kubernetes-tools.vscode-kubernetes-tools-unresponsive.cpuprofile.txt
Find more details here: https://github.com/Microsoft/vscode/wiki/Explain:-extension-causes-high-cpu-load

Possibly related #519
We should consider bundling the extension, as suggested here: https://github.com/Microsoft/vscode/wiki/Explain:-extension-causes-high-cpu-load#code-loading
There's an open ticket for this #500 - which I'll try to do this weekend.

@bnookala you wanna circle round here? We don't get a lot of these complaints, so I suspect it might be gone yet, but just doing due diligence...

It still needs work, if only because the extension is still slow to start up.  I have a proof of concept of Webpacking the extension but it's brittle as.

Should be resolved now as a consequence of https://github.com/Azure/vscode-kubernetes-tools/pull/586


issue with named curve X25519 in openssl 1.0.2

I am using ECDHE and trying to generate a EC_KEY using the named curve x25519 (29). All the API succeeds. But finally when I am using EC_POINT_point2oct() api to convert the key, it returns a 35 bytes key. I am expecting a 32 bytes key for the named curve 29. Is there a known issue with openssl 1.0.2 for the named curve 29.

I don't know what the code is doing, but 1.0.2 does not support 25519.  Are you sure you are using that version?

I'm not sure what you've done but you are mixing up various different things:

OpenSSL 1.0.2 does not support X25519 at all. You need to use OpenSSL1.1.0 for that.

The curve is 25519. The algorithm is X25519 (which works much like standard ECDH). In its implementation it is quite different to all of the other OpenSSL curves. You cannot create an EC_KEY for it even in OpenSSL1.1.0. You must use the EVP routines to work with it. The primitive functions are not exposed via the API.

X25519 has the number 29 in the TLS Supported Groups registry (https://www.iana.org/assignments/tls-parameters/tls-parameters.xhtml#tls-parameters-8). This is TLS specific and libcrypto EC* functions know nothing about it.

Thanks a lot @richsalz  and @mattcaswell for responding to my query. I am using openssl 1.0.2.
@mattcaswell  Yes, I mixed different things. I am generating a key pair which can support named curve 29. So I used the following APIs.
EC_KEY *eckey = EC_KEY_new_by_curve_name(nid);
EC_KEY_generate_key(ec_key);
EVP_PKEY *evpkey = EVP_PKEY_new();
EVP_PKEY_assign_EC_KEY(evpkey, eckey);
To serialize the key, I am using the EC_POINT_point2oct() API. This generally works for other named curves but specifically has problem with curve 29 (25519). Like you said, this is probably because the openssl 1.0.2 doesn't have support for curve 25519.
I want to upgrade the openssl but there is no new openssl version which is declared as LTS yet post 1.0.2.
So I am little hesitant to upgrade as of now.

Okay, you know that 1.0.2 does not support Curve 25519, and you can't upgrade.  Closing this issue.

To serialize the key, I am using the EC_POINT_point2oct() API. This generally works for other named curves but specifically has problem with curve 29 (25519). Like you said, this is probably because the openssl 1.0.2 doesn't have support for curve 25519.

Even if you had an OpenSSL version with 25519 support you couldn't do it this way anyway. Curve 25519 works entirely differently internally to all the other EC stuff. You can't use any of the EC_* functions on it. You can only use EVP_* functions.


Add and update tests for midstream exception policy bug 5825 - v2

Previous (draft) PR: https://github.com/OISF/suricata-verify/pull/1216
Changes:

add tests to check on midstream behaviors in IDS and IPS mode, with the different variations of midstream policy/midstream enabled/disabled IPS (IDS mode is missing cases for 'drop-flow' in ids mode. Felt redundant, but now I feel I must add those.
tests for bug-5825 (midstream exception policy config conflict) added into dedicated directory
test 'exception-policy-ids-midstream-disabled-reject' fails possibly due to bug where we don't differentiate the reject if we're in IDS or IPS mode?
test 'bug-2491-02' set midstream policy to 'ignore' as 'drop-flow' would lead to Suri refusing to init for invalid config
Better explain 'exception-policy-midstream-03' behavior and scenario in the README

TODO:

add test cases for 'drop-flow' in ids mode
double-check if tests do what we expect them to

Suricata PR: https://github.com/OISF/suricata/pull/8948

Replaced by: https://github.com/OISF/suricata-verify/pull/1226


Schemas scraped

Hi John,
FYI, I have written code to scrape down the schemas recently.
Code: https://github.com/blais/ameritrade/tree/master/tools
Output: https://github.com/blais/ameritrade/tree/master/ameritrade/schemas
There's still a few quirks, I'll be cleaning them up over the next few days or weeks.

Here, for you and all the others using the APIs:
https://github.com/blais/ameritrade-api-schemas
BTW I've asked the APIfolk for a package like this a year ago and they said they'd provide a clean one but they've never done it. 2021 goals is to start selling vol in earnest so I did this a few days ago to finish building up my API. Scraping was a bit of a pain, hopefully it saves you some time. I'll be parsing this and generating a corresponding set of Protocol Buffer definitions. You can Haskell the bejeezus out of it, whatever concrete message format is most useful there.

Here, for you and all the others using the APIs:
https://github.com/blais/ameritrade-api-schemas
BTW I've asked the APIfolk for a package like this a year ago and they said they'd provide a clean one but they've never done it. 2021 goals is to start selling vol in earnest so I did this a few days ago to finish building up my API. Scraping was a bit of a pain, hopefully it saves you some time. I'll be parsing this and generating a corresponding set of Protocol Buffer definitions. You can Haskell the bejeezus out of it, whatever concrete message format is most useful there.

Thank you, Martin!


Deposits query

Description
This PR introduces a new GetStakeDelegDeposits query that is needed by cardano-cli to get to current deposits that delegators have left. As such it also bumps up versions in network
This is the first time I am adding a query, so please double check if I got all the versioning stuff right
NOTE - This PR is still missing a changelog entry. I need to figure out how this scriv stuff works, never used it before.
Checklist

Branch

[x] Commit sequence broadly makes sense
[x] Commits have useful messages
[x] The documentation has been properly updated
[ ] New tests are added if needed and existing tests are updated
[x] Any changes affecting Consensus packages must have an entry in the appropriate changelog.d directory created using scriv. If in doubt, see the Consensus release process.
[ ] Any changes in the Consensus API (every exposed function, type or module) that has changed its name, has been deleted, has been moved, or altered in some other significant way must leave behind a DEPRECATED warning that notifies downstream consumers. If deprecating a whole module, remember to add it to ./scripts/ci/check-stylish.sh as otherwise stylish-haskell would un-deprecate it.
[ ] If this branch changes Network and has any consequences for downstream repositories or end users, said changes must be documented in interface-CHANGELOG.md
[ ] If serialization changes, user-facing consequences (e.g. replay from genesis) are confirmed to be intentional.

Pull Request

[x] Self-reviewed the diff
[x] Useful pull request description at least containing the following information:

What does this PR change?
Why these changes were needed?
How does this affect downstream repositories and/or end-users?
Which ticket does this PR close (if any)? If it does, is it linked?

[x] Reviewer requested

@lehins for adding the changelog fragment see this section. HTH!

@dnadales and @amesgen Thank you for your reviews.

CI is currently failing due to stylish-haskell failures,

Fixed.

there are also golden test failures which can be accepted by running the Shelley/Cardano test suite locally, as well as CDDL failures.

I can't find any failures. It probably was due to the PR not being rebase on master. I've fixed some golden tests in my previous PR.

There is something funny going on with sylish-haskell on cicero:
x86_64-linux > -module Ouroboros.Network.NodeToClient.Version (
x86_64-linux > - NodeToClientVersion (..)
x86_64-linux > +module Ouroboros.Network.NodeToClient.Version
x86_64-linux > + ( NodeToClientVersion (..)

This is not what sylish-haskell does for me locally. I am using the one from nix shell:
$ which stylish-haskell
/nix/store/gl25c05xzmfmw0i658jpq1f1kw66f667-stylish-haskell-exe-stylish-haskell-<IP_ADDRESS>/bin/stylish-haskell
$ stylish-haskell -i ouroboros-network-api/src/Ouroboros/Network/NodeToClient/Version.hs
$ git diff
diff --git a/ouroboros-network-api/src/Ouroboros/Network/NodeToClient/Version.hs ...
...
-module Ouroboros.Network.NodeToClient.Version
-  ( NodeToClientVersion (..)
+module Ouroboros.Network.NodeToClient.Version (
+    NodeToClientVersion (..)
...

@lehins Network uses a different configuration file for stylish-haskell, you can run
./scripts/ci/check-stylish-network.sh

to do that locally (there also is ./scripts/ci/check-stylish.sh for Consensus).

Network uses a different configuration file for stylish-haskell

Yeah, I totally support you plan of splitting the two projects into separate repos.

I think I made stylish-haskell happy enough.
Entries to changelog have been added.
However, I cannot decipher what is going on with cicero. Can someone give me a clue? Is it even related to this PR? If I had to guess the failure is unrelated, but I don't understand cicero output whatsoever.

bors merge


Fixing Ruby updates dependencies

Sorry, I hadn't seen this PR... is it still valid?

I think is fixed by https://github.com/sonata-nfv/son-gkeeper/pull/292, you can close it


Retry remote downloads.

Remote operations fail sometimes due to network failures or other external reasons. Add retry logic to all the remote downloads, so that a transient failure at pageserver startup or tenant attach doesn't cause the whole tenant to be marked as Broken.
Like in the uploads retry logic, we print the failure to the log as a WARNing after three retries, but keep retrying. We will retry up to 10 times now, before returning the error to the caller.
To test the retries, I created a new RemoteStorage wrapper that simulates failures, by returning an error for the first N times that a remote operation is performed. It can be enabled by setting a new "test_remote_failures" option in the pageserver config file.
Fixes #3112

Two more general thoughts (not for this PR):

the only place that actually needs retries is S3 now (remote_storage could happen to be some NFS though, yet unlikely), so we might want to bring the retrying wrapper closer (into?) the GenericRemoteStorage.
This would make us to move all the failure code into the storage itself, presumably as

#[not(cfg(testing))]
fn run_operation(op) -> Result<...> {
    op.await
}

#[cfg(testing)]
fn run_operation(op) -> Result<...> {
    if self.failures(op) > ... {}
}

IMO, quite simplifes the whole picture and might help with the type discussions.

If I've got the code right, the test_remote_failures=1 makes the remote storage to do "error", "successful op" in a loop per operation. We now don't detect such cycles, but they seem to be relatively important.
We can add a metric to track the general error numbers: if they occur to much, we can potentially spot it in the metrics.


Open source Microsoft.SqlServer.TransactSql.ScriptDom

Can you please please open source Microsoft.SqlServer.TransactSql.ScriptDom.dll?
The parser is useful, but there are still a lot of gaps that we'd like to contribute to.
This doesn't strike me as a sensitive library and we can already 'see it' in ILSpy or any other decompiler.
Could someone please raise it to the relevant people at Microsoft?

Pretty please anyone from Microsoft could you please help 🙏?

ScriptDom is still on the list of components to open source and is part of the DacFx project, so this is the correct location for this discussion.

Thank you @dzsquared for your update.
To clarify, are you saying that it is on the roadmap to open source it? I understand this might not be a priority but is there a rough ETA?

I'd like to raise my hand and offer any help that might be useful to get the script Dom library open source.

🙏🙏🙏

So it's been 2 and half years and no movement at all on this.
What's blocking this from moving forward?
The parser has lots of bugs and we have no way of fixing them...

😪

I also join the comments of Mr. @clement911 and hope that Microsoft will initiate this open-source project, which will definitely lead to an improvement in the quality of writing tsql code for the entire community.

ScriptDom is now open-source https://github.com/microsoft/SqlScriptDom

OMG thank you!!! 💙💙💙


CLOUD-44414 release udev cookies/semaphores if the udev-worker got killed

@akanto @biharitomi
Should we open an issue in Docker?

Jenkins build failed.
Refer to this link for build results: http://ci.sequenceiq.com/job/cloudbreak-pull-request/1816/

Jenkins build finished, all tests passed.
Refer to this link for build results: http://ci.sequenceiq.com/job/cloudbreak-pull-request/1817/

LGTM


Pseudo events not supported with accessibility rule

Describe the bug
Hi, I would like to use accessibility rules as described here but they don't support pseudo events.

Context and configuration
Please share:

Which rule is causing the problem: template-click-events-have-key-events

Expected behavior
Support of pseudo events for accessibility rules.
Code
{{name}}

Since we're talking about accessibility, that thing's supposed to be a button, not an anchor.

@lazarljubenovic In this case selectGroup(name) do a redirection using the PlatformLocation API. IMO the  element is appropriate.

It's an anchor tag without href, which means it's a "placeholder for a link". Things like "Open in new tab" won't work. You should pre-compute the URL and then use routerLink.

@lazarljubenovic Ok noted, thanks for the advice.
However it doesn't resolve the main problem with pseudo events. Here is an other example without link element :

{{person.name}}

The rule should cover this case as described here.

A non-interactive element that has a click event, should be accompanied by one of the key events (keyup, keydown or keypress)

But it fails when using pseudo events.

Yeah, sorry for side-tracking the topic :pray: You're completely correct that it's a bug (or, well, a missing feature) in Codelyzer.

@mohammedzamakhan do you think you can alter the rule template-click-events-have-key-events so we can handle this case?

yes we can update it to handle it, I will take a look into it

Fixed in #893


Implement supervision

Implicit Supervision
This type of supervision must be built right into Actors.

[x] introduce Stop message,
[x] implement onmessage(..., ::Exit),
[ ] introduce :system actor (doesn't exit if peers exit),
[x] connect and disconnect actors,
[x] monitor and demonitor actors,
[x] introduce Connect message,
[ ] implement onmessage(..., ::Connect),
[x] conn::Array{Connection, 1} entry in _ACT variable,
[ ] introduce _ROOT actor, a :system actor,
[x] connect to _ROOT if called from Main,
[x] different Connection types: Parent, Peer, Child, Monitor, Monitored,
[ ] implement restarting strategies :transient, :permanent, :temporary,
[ ] spawn supervised worker actors with restart=:transient, (or other restarting strategies)
[ ] onerror methods/reactions for all types of connections,
[ ] onmessage(..., ::Exit) reaction can be parametrized by a supervision strategy,

In principle it is possible to build a supervision tree implicitly with those methods. But generally this kind of supervision has no fixed structure.
Explicit Supervision Tree
The possibility to define a supervision tree in a module with callback functions will be implemented in a separate library

[x] create Supervisors.jl,
[ ] specify Supervisors,

System Actors
Like in Erlang/Elixir a :system actor traps Exit signals and does not propagate them further. Only if a :system actors fails, it sends Exit signals to connected actors.
If an actor fails, the exception and a stack trace are preserved in its link/channel. Therefore a :system actor needs to store the link to the failed actor to be able to preserve all necessary information about the failure.
A failing actor therefore sends the exception and its own link to its connections, which forward the Exit signal until eventually a :system actor gets it. The :system actor reports the exception and stores the link to the failed actor in its task_local_storage. The diagnostic information can be retrieved from the system actor via diag.
Thus every :default actor can become a :system actor and does then have this functionality.
There is one restriction to this logic: actors extending the Actors protocol like :genserver or :guard cannot become :system actors without loosing their functionality.


Spring Cloud Config Server - Support Vault AppRole Auth method

Enhancement
Currently Config Server only supports token based Auth for Vault backend and often tokens expire regularly. Also, tokens doesn't work when Vault clusters are in performance replication (Enterprise Licensed version feature).  All enterprise Vault clusters uses performance replication for HA and tokens and leases doesn't replicate. Only Auth methods , secret backends gets replicated across clusters.
The enhancement request is to make Config Server support the most prominent auth method which is AppRole used by the Machines and applications.

This requirement should be met with https://github.com/spring-cloud/spring-cloud-config/pull/1526


Ninjafix: Add sbt/sbt-launch*.jar to gitignore

Build against Scala 2.10 finished with failure

Build against Scala 2.11 finished with failure


Renamed /models to /faq, added some FAQ to /faq

i forgot who asked but it used to be called FAQ and we renamed it

Max was OK renaming it, and we need a place to put the other FAQ info


Adding support for Guarani

Can you clarify if and when Guarani(grn) will be supported by Babel?
Currently trying to parse this code throws an error
from babel import Locale
Locale.parse('grn')
>> babel.core.UnknownLocaleError: unknown locale 'grn'

This part of Babel is just an interface to CLDR, a data repository managed
by the Unicode consortium. It seems like Guarani is, unfortunately, not
supported yet by CLDR so there is not much that the Babel project can do.
On Thu, May 28, 2015 at 2:53 AM, Milton Madanda<EMAIL_ADDRESS>wrote:

Can you clarify if and when Guarani(grn) will be supported by Babel?
Currently trying to parse this code throws an error
from babel import Locale
Locale.parse('grn')>> babel.core.UnknownLocaleError: unknown locale 'grn'
—
Reply to this email directly or view it on GitHub
https://github.com/mitsuhiko/babel/issues/159.

@miltontony as @benselme said, the specs should be at CLDR.


[Build] Gulp to Webpack

Due to the nature of this module, gulp seems to be more suitable than webpack.


Feat/design updates

Design updates
https://github.com/Cantara/Whydah-StatisticsDashboard/assets/4509009/812f3b8e-014b-47c4-843b-32a26a556dfd
Redesign dashboard, missing today panel, not finished yet but pushing for feedback.
Changes

Merge appid tables, use stacked instead of multiple tables, handles a variable amount of apps. (@totto, I wasn't able to set stacks as categories, so I ended up with stack labels for now)
Add stacked chart to each StatsNode
Colors will get decided later, what I used is something I think looks OK, but there is every opportunity to change them.
Fix font awesome, and google-fonts
Fix date-fns plugin for nuxt3
Handle null fields
A lot of CSS changes to the visuals
Setup basic resolution scaling

Great work @roosta aka Daniel!
On Mon, Sep 25, 2023 at 11:21 AM Daniel Berg @.***>
wrote:

Design updates
https://github.com/Cantara/Whydah-StatisticsDashboard/assets/4509009/812f3b8e-014b-47c4-843b-32a26a556dfd
Redesign dashboard, missing today panel, not finished yet but pushing for
feedback.
Changes

Merge appid tables, use stacked instead of multiple tables, handles
a variable amount of apps. @.*** https://github.com/totto, I
wasn't able to set stacks as categories, so I ended up with stack labels
for now)
Add stacked chart to each StatsNode
Colors will get decided later, what I used is something I think
looks OK, but there is every opportunity to change them.
Fix font awesome, and google-fonts
Fix date-fns plugin for nuxt3
Handle null fields
A lot of CSS changes to the visuals
Setup basic resolution scaling

You can view, comment on, or merge this pull request online at:
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73
Commit Summary

1cdf2e4
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/1cdf2e4995a4c57852cd0e559d6b92bf95f38fa6
Ignore data dir
75407e8
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/75407e8653bfe2c0b7254af5bb75e209c3d15f1c
doc: add note about application.properties
06e0fec
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/06e0fec9dca6a2a517201d792d348dc469a85acf
Setup color overrides
14432b5
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/14432b52a64ee755009b983f14301fa7e8df7382
Fix font family + build warning
9ea2f4e
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/9ea2f4e132b0bc58f5d7347a698e175f999adc5d
Set unused to warn
5cd5999
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/5cd5999216a2d2c6c94b5cc1071206cc627b844e
Move font declaration
1ae0bc6
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/1ae0bc61e51f7f92d112b05553f6f6831abaa962
Setup column layout, move charts
15b009d
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/15b009d99d35402249928f5a797bc5d46e85d35a
Setup new colors (WIP)
78d81d6
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/78d81d6b990123d22895cb02b56de04d053dd332
Disable chart credits
cc4d414
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/cc4d414959b0ce3649153b9823d80c460058579b
Adjust chart height + border-radius
72fcac9
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/72fcac993f10c9a1dd7f1edbe7416aa11aa35333
Merge branch 'main' into feat/design-updates
0f9d096
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/0f9d09665fb4d631226ff654d57eb85ee66d38f2
Adjust top layout + spacing
ad02319
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/ad02319647bf77b331455a015183b8392b2776f1
Expose sass color vars as javascript
ad59ce3
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/ad59ce34a5df4ebdc111051aca0eacb4b753c159
Add color dep
fbed176
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/fbed17617333e4c556de614c40c1090f3349b1e6
Setup styled mode for charts, and add custom style
6170df7
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/6170df7a6d1a9dab0966cae9decb57e1f4d2d38e
Add cool grey color
c1dfacc
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/c1dfaccc6236d7d571a0fa724f338ee21ae7a3ec
Desaturate table backgrounds
227bdbc
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/227bdbcd8c81cf724a80edf131ca08534ea1db46
Setup column layout for StatsNode
2241742
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/2241742230c7901d869c1eb15b3408f389a0d734
Cleanup colors
5141a2c
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/5141a2ca2086a25f2e2c90ed4cc2dcbe236c074b
Indent
ae5d475
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/ae5d4754f965c7750f8da5d2f643b2271fad5914
Change StatsNode container styles
16a9910
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/16a9910cf6a3edea73a0e85415b744e3401fcccb
Adjust color
b3fa3c8
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/b3fa3c841f66496a63154dc9f4b38b4215a1c636
Merge branch 'main' into feat/design-updates
e4f8a30
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/e4f8a30d783ddc661afae81a5affecd9fc71f3a1
Merge branch 'main' into feat/design-updates
1423362
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/1423362770ad484ad34b43cc5e452c51adf7b3f3
Merge branch 'main' into feat/design-updates
8b33735
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/8b337356e0054de8ec495d397156c85c066ef064
Merge branch 'main' into feat/design-updates
4b0e606
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/4b0e6069bb567a61131b0dcee55f2e32d87369e3
Merge branch 'main' into feat/design-updates
dffd6bb
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/dffd6bb0f1b310556c2235057417601212b536cd
Merge branch 'main' into feat/design-updates
d2518ba
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/d2518ba9595e5a7cb0eba8e2a2c2c2448266f60a
Merge branch 'main' into feat/design-updates
b5ad13c
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/b5ad13cae4261b2519687d6af0fc3abed9b28035
Merge branch 'main' into feat/design-updates
082e3b0
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/082e3b027a2582ac8222589fc574a169f5d228ec
Ignore dependency-reduce-pom-xml
028825f
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/028825f06b8b439f109dc9b95eba7ca6c1604f65
Add day chart (unfinished)
2ac2691
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/2ac2691131d677c61c1a0f491e5e1d1fd49a9376
Comment back in previous status display
479224a
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/479224a1706246c51bd59adb3715d9b686dd4257
Fix column issue with no data present
7c0b1e8
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/7c0b1e82cc84e681eb4617d1c941ab176314d22a
Setup appid based stacked column chart
f6c63df
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/f6c63df66a85b361d17ba16564b80c88208b8909
Merge branch 'main' into feat/design-updates
fcc23d4
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/fcc23d4b67b9f341422ce9c7ad66d4dd00a44913
whitespace
8d52518
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/8d525183658ecd8df6e78eed82f732cb618cf102
Reverse chart stacks, stack is now an appid
84eced7
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/84eced74f6f35a29db13e47255a92ba6f8305e48
Fix lodash plugin
96436ff
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/96436ff22eca601628ea1a11a6429afb9ac39cc4
Remove commented code
ee92de9
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/ee92de964ffec39005833b02822785a9f4544234
Add basic tooltip
bd227b5
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/bd227b56873a11d1fca683ae424b627012a745b1
Fix lodash plugin
6b79c29
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/6b79c291fa4c7b4deb4e31575326f3de9aa7116d
Use lodash flatten to flatten series
5a81e9b
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/5a81e9b64cfa819c4ba0efd85591a52856b3fb3f
Fix chart title
633524e
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/633524e128d414e6d4deb4e96bb0113bd9556886
Add appid to tooltip
f8177a9
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/f8177a95759fdcd2c018e25a4e21f638f5faa001
Fix chart column colors
5602b57
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/5602b57bec4b5f24c240e20810d54d2046a381c6
Remove commented out container styles
15edb1c
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/15edb1c65802e2147eed3231598b141b994771d7
Remove inline styles
36b6f83
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/36b6f83b0ed22a39a5a6c1d9ad4a33f94e55cbe0
Use error logging on errors
c587b81
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/c587b81442444655a0a054ca2625babb87f67cec
Setup basic column chart for StatsNode
42b6485
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/42b648599f909a1883c8291034a9c01315f95388
Add tooltip
81a7273
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/81a7273c126f0db5bc0061441487a035b37bb7a6
Cleanup and set column grouping
7282d7d
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/7282d7db1b5620b9c5d0c6dbd949e191edc29179
Set stacks to be appid
627be23
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/627be23e6b4c9267f1e00376c99ea243313ce1d6
Add stack labels to chart
541fec0
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/541fec0f14c00ca97f40f1ce73bc39738ab9c3ab
Fix missing stack labels
cb5230b
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/cb5230bee039f13b138a82e5a64489a04166e92c
Adjust StatsNode title styling
f75566b
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/f75566b572764c746e4940c00048d0a0dd72a2d1
Remove unused idx var
3eea82d
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/3eea82df23d6143cb680d04c5e8002a4c2b9d28e
Fix import statements
716b4bd
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/716b4bde710c12a3bdfdd04ed888b8834f066bf1
Enable font awesome icons
e60791e
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/e60791e2b8d028d88aa044ee35fb5112416c752e
Comment out css icon override
71fe535
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/71fe535da480313b19346eda0db8753a076d21b0
Remove unused color prop to chart data
27d4197
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/27d4197cb1844ee91059ca2bef5aee2bdfa86a10
Export dark grey
f9c10bb
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/f9c10bbf916b296f8adf56bd6eb638801b362ea8
Setup new stats node total layout
5e21f95
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/5e21f954ee348c5afa5fd211c2b3ef83ec8e28b0
Split out stats row
112ecec
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/112ececc59694d462425e686efd26aa382eb8a1d
Cleanup commented styles
7c60f58
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/7c60f588c71ed3c3d95149739310d62b138663c3
Add remaining statsNode rows
fd7b8f8
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/fd7b8f8c4db0ba92e07db08d5214d4408193b7e8
Fix StatsNode chart column colors
d9291ab
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/d9291ab8fca0d1f2956a3c89c7e74a34b0347a7e
Add Today component
bade02c
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/bade02c9a10c97a6d311fc50559f964ddb90684d
Adjust chart size
beeac6d
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/beeac6d2a05535f4804816bc00a51000679d0772
Remove debug log statement
fa08f11
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/fa08f11042c6e576972c40591e2db981c69542bc
Setup passing today to today panel
0b3efca
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/0b3efcaeca55f8f4915f6d9e67a36205ed9e35b6
Filter out today from stat nodes
aad7f61
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/aad7f615e82be61b6c4231eed66b7c3440421ef0
Add today headline
4bd0fcf
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/4bd0fcfde3659dd762c441ce9c70c9398550e36c
Add formatted headline date
ac64820
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/ac64820365f4f0d6631a22e9c09260c0669e6394
Merge branch 'main' into feat/design-updates
fcff0c9
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/fcff0c9d0baf361eb6cf406d5ef8306b74683144
Fix issue parsing null date
7221319
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/72213197af14aca6e41d686b0548881779549964
Fix issue iterating over null
cf1acbc
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/cf1acbc666d586820df785056f8126ba95a25e72
Fix dateIsValid in today component
ca42751
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/ca427513c142ebaa6bd38034bc29285cc587c3ce
Guard against more null dates
075dd19
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/075dd198137c1b0eb85122b115b84092edf4d634
Fix issue iterating over null
4ee4a0b
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/commits/4ee4a0b7cfc1d29f4c096398c97def1bb0b8d69a
Setup basic screen scaling

File Changes
(14 files
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/files)

M .gitignore
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/files#diff-bc37d034bad564583790a46f19d807abfe519c5671395fd494d8cce506c42947
(2)
M src/main/resources/nuxt-spa/.eslintrc.js
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/files#diff-9c157295bde741abcf221118ce0f473ac17d8eed0f2f01ba30d897a7f5a6bb04
(2)
M src/main/resources/nuxt-spa/README.md
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/files#diff-3a10e09cabaa18f5c94c04753202c45fb2e9ff0e181e904500b6a499c36b8f7a
(7)
A src/main/resources/nuxt-spa/assets/styles/_colors.module.scss
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/files#diff-575397a968dcf3774a5665fc0493b8a56d146d59e905b7ea76879f2205aad84c
(39)
M src/main/resources/nuxt-spa/assets/styles/main.scss
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/files#diff-960aa435eb936cd1e2a632f620363c710a183b1af333470506ca61b8f6d36f76
(81)
M src/main/resources/nuxt-spa/domain/pages/StatsNode.vue
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/files#diff-40c75651b938d16d43214944f70da09a0caa6be817571a656a2db55fe63324f2
(261)
A src/main/resources/nuxt-spa/domain/pages/StatsRow.vue
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/files#diff-48a09e5545a10a76ea36b7f074bc4754f5f9bfebf000ef99c8db567a39bef4f9
(46)
A src/main/resources/nuxt-spa/domain/pages/Today.vue
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/files#diff-8a6cfa5cc38d33b902be3fb59f7b49d23c21cd0a2ce60ee4ff42ef12b88ee965
(42)
M src/main/resources/nuxt-spa/nuxt.config.js
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/files#diff-9f07423977231d30144ec213294983d2c5938c3f411dfba2e6199d2ee74e2863
(12)
M src/main/resources/nuxt-spa/package-lock.json
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/files#diff-3e0ee94d1e3b049a98752f6709637374e18a549d82f97ff776a1c0a55106e13d
(138)
M src/main/resources/nuxt-spa/package.json
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/files#diff-6729eba8d161776351768301538005fee23196285a003153d3cac76be67ac7c8
(4)
M src/main/resources/nuxt-spa/pages/index.vue
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/files#diff-2fd8fec9c6f88271255190f4bc73df0491158465ee5fb35cffd62f6803e132b7
(237)
A src/main/resources/nuxt-spa/plugins/fontawesome.js
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/files#diff-b30196ca97d73e08f1417ca948f0463aac9f2ca9c0b6bcffd7a91851a37aa9bd
(10)
M src/main/resources/nuxt-spa/plugins/lodash.js
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73/files#diff-cd7c37874a4fda4069bf3b7e7f3119e1ca6977dcc63e3d8333a773f8f0bad74b
(15)

Patch Links:

https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73.patch
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73.diff

—
Reply to this email directly, view it on GitHub
https://github.com/Cantara/Whydah-StatisticsDashboard/pull/73, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AABI4ZDWHLTNRDPJJT4Y5ALX4FEJ3ANCNFSM6AAAAAA5FYXBSM
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Thanks @baardl :)


Migrate Slack files.upload API

The original web API method for uploading files to Slack, files.upload, is being sunset on March 11, 2025. Beginning May 8, 2024, newly-created apps will be unable to use this API method.

https://api.slack.com/changelog/2024-04-a-better-way-to-upload-files-is-here-to-stay
files.upload is used in SlackReporter.

https://qiita.com/seratch/items/971980506da92ea6c8db


Add the Power Platform 'Make' portal

I didn't see a command for getting to make.powerapps.com, and figured it'd be worth adding!
On a separate note - would it be worth splitting off 'Power Platform' to its own category? I'd love to contribute that here if possible!

Thanks for the PR!
Sorry it took so long to review.


Color palette selection

Would be cool to be able to choose e.g. Colodore, VICE, pepto color configurations

you can take the color settings for the ones above out of the spritemate repo if you like

"colodore":
              [
                "#000000","#ffffff","#813338","#75cec8",
                "#8e3c97","#56ac4d","#2e2c9b","#edf171",
                "#8e5029","#553800","#c46c71","#4a4a4a",
                "#7b7b7b","#a9ff9f","#706deb","#b2b2b2"
              ],
              "pepto":
              [
                "#000000","#ffffff","#67372d","#73a3b1",
                "#6e3e83","#5b8d48","#362976","#b7c576",
                "#6c4f2a","#423908","#98675b","#444444",
                "#6c6c6c","#9dd28a","#6d5fb0","#959595"

Done.. I added "petmate" (I don't remember where this came from, maybe vice?), "colodore" and "pepto".  If you have more, let me know.
If you find some issues with this when you try the next build (when I make on), then let's file new bugs and keep this closed.


Can I make an Among Us game by python? (Simple one)

Yes you can but it might take much more time than using a game engine like Unity or Unreal Engine.
Fun Fact: Among Us was developed using the Unity engine.

No description provided.

hello
have you asked the question?
that any one can create a game?
if anked and is ya a little thing not big

what we make among us game using python?

what we make among us game using python?

here I am ! the maintainer of the repository. Invite me for a pair programming, too.


Added check for "convert_urls" in TinyMCE config.

Found this as a part of Subsite/TinyMCE issue earlier today. Even when you set "convert_urls" to false in TinyMCE config, SS still converts them to relative links. This piece of code prevents that.

This seems alright for the 3 branch but will probably need rebasing.

Manual merge I think after a year

merged by hand (yes, I did drop the (int) casting)


BREAKING: allow setting multiple public cidrs

Closes: #58
Add a new variable cidr_authorization_contexts that allows for setting multiple public IPs. Turns out you cannot set the cidr_authorization_context in sub pools so i removed that feature
we use a map that expects there to be union of CIDRs defined in top_cidr with the cidrs in var.cidr_authorization_contexts[*].cidr

@troy-ameigh Testing this PR requires access to public external IPs that are imported to AWS. I dont have access to those. Luckily, the initial issue reporter was willing to test for us.
The change is pretty low risk since the overwhelming majority of our users do not BYOIP.
See reference: https://github.com/aws-ia/terraform-aws-ipam/issues/58#issuecomment-1634899894

I'm not exactly sure why tf docs is failing. it only started failing after i added the note in .header.md

@drewmullen ftfy
@pablo19sc or @NetDevAutomate, need one of you to review & approve to proceed to next steps.

Yeah man. The example readmes needed to be updated too, but that’s a larger issue. Also, if I miss a mention here, feel free to hit me up through an alternate channel like email. I try to stay on top of it, but there's lots of noise from GitHub to filter through, so I sometimes miss stuff.

i forgot your email 😅 will you email me? :)
if you forget just ask @pablo19sc - hes been my intermediate workaround LOL 😅
@tlindsay42


URL Asset Import dies with an NPE when source column is blank

Required Information

[x] ACS AEM Commons Version: 3.17.0
[x] Reproducible on Latest? yes

Expected Behavior
The row should be skipped and logged as an error, but the process shouldn't die
Actual Behavior
NPE is thrown and whole process halts on start
com.adobe.acs.commons.mcp.impl.processes.asset.UrlAssetImport.extractFile(UrlAssetImport.java:340) at
java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193) at
java.util.stream.ReferencePipeline$11$1.accept(ReferencePipeline.java:373) at
java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1374) at
java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481) at
java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471) at
java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708) at
java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) at
java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:499) at com.adobe.acs.commons.mcp.impl.processes.asset.UrlAssetImport.extractFilesAndFolders(UrlAssetImport.java:180) at ...```

Also the Spreadsheet class dies on reading the file if a header column is blank, instead of skipping the column

Shouldn't this issue be closed? @badvision already added the fix nearly a year ago.

Yes, but I should double-check the unit test is accurate before I close.

@badvision In #2145 I enhanced the unittests to cover this case as well, please check. Maybe we can close this issue then.

I think so.  I added this issue so I wouldn't forget to fix it but I might have inadvertently forgotten to close this issue. ;)  I'll re-open if necessary.


[JavaScript] Image outside an ImageSet sized differently

Platform

JavaScript

Version of SDK
latest main (designer on adaptivecards-ci)
Details
Image outside an ImageSet looks different from an Image inside an ImageSet. Expected them to look the same.

Payload:
{
    "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
    "type": "AdaptiveCard",
    "version": "1.2",
    "body": [
        {
            "type": "ImageSet",
            "images": [
                {
                    "type": "Image",
                    "url": "https://static.thenounproject.com/png/22802-200.png"
                }
            ]
        },
        {
            "type": "Image",
            "url": "https://static.thenounproject.com/png/22802-200.png"
        }
    ]
}

By design. Image in ImageSet is not the same as standalone Image.


pytest config preventing deprecation warnings being converted to errors

import warnings

def foo(a, b):
    warnings.warn("deprecated func", category=DeprecationWarning)
    return a + b

def test_foo():
    assert foo(1, 2) == 3

Put that in a script and run it as pytest script.py, it passes. Try pytest script.py -W error::DeprecationWarning and it fails -- that's the expected behaviour.
Try using -W error::DeprecationWarning when running the cogent3 test suite when we know there's deprecation warnings, they're not converted to failures.
Is this affecting others too? If so, there's a project setting issue.

Yes, they were not being raised as errors for me either!

Think there are two issues tracking this with #1620. I think I've found the culprit, and it's in the code not configuration, see this comment in #1620.


Days with strange schedules (ex all 8 classes) are weird

Clicking on classes doesn't work at all sometimes and othertimes toggles other classes. Lunch appears twice, and clicking on the bottom one toggles to upper one. Clubs tab stays open as well.

Issue reproduced for 12/19. Are there any other days with this problem (I
couldn't find any)?
On Mon, Nov 11, 2019, 11:38 AM TEspelien<EMAIL_ADDRESS>wrote:

Clicking on classes doesn't work at all sometimes and othertimes toggles
other classes. Lunch appears twice, and clicking on the bottom one toggles
to upper one. Clubs tab stays open as well.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/guberti/epschedule/issues/370?email_source=notifications&email_token=AAXNITUASPYA3SKVHHSO6NTQTGYDHA5CNFSM4JLZ4LZ2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HYQCXFA,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAXNITVX3AYIXY2D5LO72Q3QTGYDHANCNFSM4JLZ4LZQ
.

Closing for now


Error when running project on MacOS 11.6

I have followed every step from the README and I get the following error when running ./bin/Debug/GFXFramework:
dyld: Library not loaded: /mnt/c/Users/Florin/Desktop/egc/Framework-EGC/src/components_hidden/build/macos-x86_64/bin/Release/GFXComponents.dylib
  Referenced from: /Users/dimi/fac/egc/gfx-framework-master/build/bin/Debug/./GFXFramework
  Reason: image not found
[1]    22458 abort      ./GFXFramework

I guess there is a hardcoded reference in a prebuilt dependency.
I can give any additional information in order to solve this.
Thank you!

I found out the problem might be in the prebuilt GFXComponents.dylib file.
I found out using
$ grep -rnw './' --exclude-dir=build -e '/mnt/c/Users/Florin/Desktop/egc/Framework-EGC/src/components_hidden/build/macos-x86_64/bin/Release/GFXComponents.dylib'

And got
Binary file .//deps/prebuilt/GFXComponents/x86_64/GFXComponents.dylib matches