kubernetes.io/hostname label not working in NodeAffinity for Aerospike Kubernetes Operator

Similar issue in Karpenter: https://github.com/aws/karpenter-provider-aws/issues/4671
Related issue in Aerospike: https://github.com/aerospike/aerospike-kubernetes-operator/issues/305
Use-case: There is a feature in Aerospike Kubernetes Operator (AKO) called k8sNodeBlockList (list of K8s node names)  where a user can define a list of K8s nodes that should be ignored from scheduling for Aerospike Cluster pods. This feature of AKO helps users in K8s cluster maintenance by migrating pods to other K8s nodes. It uses  kubernetes.io/hostname label along with NotIn operator in the NodeAffinity to move pods away from those nodes.
        affinity:
          nodeAffinity:
            requiredDuringSchedulingIgnoredDuringExecution:
              nodeSelectorTerms:
              - matchExpressions:
                - key: kubernetes.io/hostname
                  operator: NotIn
                  values:
                  - gke-abhisek-test-default-pool-d04arw3-r5ts

Issue: Karpenter has a sweeping check where it blocks the kubernetes.io/hostname in NodeAffinity. Ref code: https://github.com/kubernetes-sigs/karpenter/blob/d5660acf4472db796d5f4fac58a147d14b320451/pkg/apis/v1beta1/labels.go#L90
As a result if there are pending pods with kubernetes.io/hostname NodeAffinity, they remain in pending state as Karpenter doesn't scale K8s node.
Questions:

Is there a plan to remove that sweeping check for kubernetes.io/hostname label?
Is it possible to only block In operator and allow NotIn operator for  kubernetes.io/hostname label?
Is there a work-around possible to bypass that check?

Could you reopen this issue in kubernetes-sigs/karpenter?

Closing to track upstream.


Typo on paragraph #30

This change has been checked in from a different PR https://github.com/Microsoft/Windows-Machine-Learning/commit/6b99d3cd053a8a3c8d10024f828b2fbf6b9109d6


Autocomplete improvements & editor refactorings

Autocompletion:

suggest local function names
suggest parameter names
don't suggest unreachable vars (declared below or in unreachable local scopes)
different icon for local functions

Grammar improvements:

functions with 0 parameters don't break the parser
trailing expressions are now really optional (they weren't, but Lezer recovered from it so it didn't matter)

Editor refactorings:

create view and state only once and store them without React refs (this unfortunately broke hot reloading in Storybook, but it simplifies the implementation and is still worth it)
squiggleLanguageSupport is a compartment and is properly reconfigured if project prop changes (this never happens in practice, though)

Other:

fixed types in prettier-plugin-squiggle for standalone.js
made some progress towards enabling noImplicitAny, which is still blocked by Lezer, but will be fixed when the patch for https://github.com/lezer-parser/lezer/issues/41 is releazed
added basic tests for grammar and autocompletion

FYI, I think it would be useful to be a bit more precise with these summaries.
"trailing expressions are now really optional" -> Can you give a short example?  Do you mean trailing commas?

Sorry, I should've said "end expressions".
Before this PR, any Squiggle program that didn't have end expressions ("results") was parsed by Lezer as incorrect, with implicit recovery, because the grammar always expected to see an expression at the end.
Old parser:
> parser.parse('x=1').toString()
'Program(NonEmptyProgram(Binding(VariableName,Equals,Number),⚠))'

New parser:
> parser.parse('x=1').toString()
'Program(Binding(VariableName,Equals,Number))'


skypeforlinux: <IP_ADDRESS> -> <IP_ADDRESS>

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/skypeforlinux/versions.
meta.description for skypeforlinux is: '"Linux client for skype"'.

Checks done (click to expand)

built on NixOS
/bin/sh passed the binary check.
1 of 1 passed binary check by having a zero exit code.
0 of 1 passed binary check by having the new version present in output.
found <IP_ADDRESS> with grep in /nix/store/51jqpi7x2a467kkqkc4cg4mdfr4qr094-skypeforlinux-<IP_ADDRESS>
directory tree listing: https://gist.github.com/f57c858d3b0438477d9a794276512efd
du listing: https://gist.github.com/595b1dcd0d2a98b265162cafcbe9fea6

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

1 total rebuild path(s)
1 package rebuild(s)
1 x86_64-linux rebuild(s)
0 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
0 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
skypeforlinux

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/51jqpi7x2a467kkqkc4cg4mdfr4qr094-skypeforlinux-<IP_ADDRESS> \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A skypeforlinux https://github.com/r-ryantm/nixpkgs/archive/1a714f16a44f854fcc02bf160acf3879474e0625.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/51jqpi7x2a467kkqkc4cg4mdfr4qr094-skypeforlinux-<IP_ADDRESS>
ls -la /nix/store/51jqpi7x2a467kkqkc4cg4mdfr4qr094-skypeforlinux-<IP_ADDRESS>/bin

cc @panaeon @jraygauthier for testing.

I built this with:

And then tried to start it with ./result/bin/skypeforlinux and got

Am I doing something wrong?

@endgame I get the same error message. It looks like a missing dependency that was added in the new version.

@endgame Can you test it again? It comes up now, but I don't have a Skype account to try.

I have successfully built it and it runs. I logged in and tested camera but not mic.


modify vgg16 cats/dogs example on Colab to include fetching data from google drive

currently the user has to manually pull the data from Kaggle, and since colab data storage is not persistent, it has to be fetched fresh each time.
Better solution would be to set up the python script to grab it from google drive and organize it locally each time.

resolved with commit 6215da9
Now fetches data automatically from a public Google drive link using !gdrive
Also adopted the updated model definition and test harness from @AdkPete   - so the colab notebook here is largely redundant with  Pete's python module here

resolved with commit 6215da9
Now fetches data automatically from a public Google drive link using !gdrive
Also adopted the updated model definition and test harness from @AdkPete   - so the colab notebook here is largely redundant with  Pete's python module here


properly handle python path injection

the original implementation fails when there is ~ in the path

What about source /home/kyle/scripts/gdb-pt-dump/pt.py?

I haven't tried it yet. But I think it will work.

Yeah, that's what I do locally. I think using ~ and adding your patch wouldn't be a good solution since the script may not be placed in the user's path. e.g. if it's run under root let's say.

Thanks for your PR though. Will not merge and closing.


Update-2022-03-28

 Update Backend

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.003%) to 85.008%

Totals

Change from base Build<PHONE_NUMBER>:
0.003%

Covered Lines:
30709

Relevant Lines:
36125

💛  - Coveralls


107 Quantize omz model ssd mobilenet v1 coco

Add JNB 107 to Optimize and quantize the Open Model Zoo ssd_mobilenet_v1_coco model

Please note that as of now JNB 107-quantize-omz-model-ssd_mobilenet_v1_coco is complete here as a standalone, however it will no longer be updated because it is being merged with JNB 108-quantize-omz-model-yolo-v4-tf on a new branch which will contain a new merged JNB 107-name-to-be-decided-soon that can run using either of the two models ssd_mobilenet_v1_coco and yolo-v4-tf.


Button text is cut off in the bottom

Bug Report
Steps
Create a Button, for example
< Button content= "See how this very long text shows up on the button" / >
Expected Result
Button text is fully visible and not cut off in the bottom
Actual Result
Button text is cut off in the bottom on letter such as 'y' and 'g'
Version
^0.29.1
Testcase

This is just missing a line-height of 20px

Oh, looks like we might have a reset adding arbitrary line-heights??


Let Customers Ask Chatbot for Shipping Price

Tutorials: https://developers.sap.com/tutorials/cai-bot-shipping-3-price-parcel.html
I am unable to get the right response in step 8

There is a warning
Undefined context path 'memory.parcel-size.name'
Undefined context path 'memory.parcel-size.price'
The response JSON
{
"type": "message",
"value": {
"type": "text",
"content": "A  parcel sent to 52 Place de la Madeleine, 75008 Paris, France will cost $",
"markdown": false,
"delay": null,
"value": "A {{memory.parcel-size.name}} parcel sent to {{memory.location.formatted}} will cost ${{memory.parcel-size.price}}"
}
}
Can you please advice
Regards
Advit

It seems that "parcel-size" is not saved in memory.
Do you have a requirement for parcel-size?

In the conversation, can you see in the memory "parcel-size"?

Can you send what you have?

Thank you for your feedback. We haven't heard from you in a while, so we are closing the issue.
If you still have questions, feel free to reopen the issue.


allow StringCrossFloatTransform to cross individual features

@deerzq @saurfang

@deerzq thanks for review, updated!

one more comment, LGTM


How to add line breaks my text is sent as a string

Hello @bonface221, sorry for a long response. Please use \n between lines.
You can use md.join method to make it look cleaner:
let msg = md.join(
  [
    md`${md.bold("🎉 New Website Inquiry Received 🎉")}`,
    "",
    md`${md.bold("Name:")} ${name}`,
    md`${md.bold("Subject:")} ${subject}`,
    md`${md.bold("Phone Number:")} ${phone}`,
    md`${md.bold("Email Address:")} ${email}`,
    md`${md.bold("Message:")} ${message}`
  ],
  '\n'
)

Please see this example in my telegram bot: https://github.com/vlad-iakovlev/raxee-bot/blob/main/modules/poker/constants.ts


Improve types for index fields

Some documents have properties that are automatically indexed, e.g. actor name and img. Furthermore, systems can use CONFIG to make more properties automatically indexed. These would be improvements to CompendiumCollection.IndexEntry

[ ] fromUuidSync should maybe be returning IndexEntry?
[ ] Core-provided properties in metadata.compendiumIndexFields should always be indexed
[ ] Provide an interface that aligns with CONFIG[documentType].compendiumIndexFields for expanding this.
[ ] Provide a way to register packs so game.packs.get("dnd5e.spells") is known to return an Item compendium

[ ] Consider implementing some form of JSON importer so more information can be derived from the package manifest

This also ripples to Folder#documentClass and Folder#documentCollection


Fix SliderBar's Current implementation

Closes #3088.

[x] Depends on https://github.com/ppy/osu-framework/pull/3089

Tested against osu!, can confirm fixes the related issue.

Shouldn't there be a framework-side test for this?

The behaviour is tested in AggregateBindableTest already, so I thought it was pretty redundant to add one specifically for this.

I meant a test for SliderBar, but alright.


Redesign the JSON-LD output for occurrence records

The occurrence-level JSON-LD output is nor semantically-correct. Better would be to present as an annotation such that we can have metadata on the link between subject and object as desired.

@dshorthouse This sort of thing does my head in :(  I think the first @reverse works fine, it generates the statements you want (e.g., some occurrence dwciri:identifiedBy some person).
I'm not sure I buy the annotation, either the way it's shown here, or whether annotation is actually what you want. When I translate this into triples I get things like:
<https://json-ld.org/playground/BionomiaLink42153317> <http://www.w3.org/ns/oa#Annotation> <http://localhost:4567/occurrence/769281222> .

which misuses <http://www.w3.org/ns/oa#Annotation>, it's not a predicate, it's the class of annotations. The connect between an occurrence and an annotation as you've modelled it is oa:source, which could be used instead of annotation in the @reverse statement, but then you're in trouble because the tree-structure would require yet a further @reverse for @target before you get to the annotation! So I think this way lies madness, and the tree structure starts to get unmanageable.
I'm wondering why use annotations to model this? I don't think these are annotations, what you're really trying to do is give the provenance for the assertion some occurrence dwciri:identifiedBy some person.  Annotations don't really express that. It feels a bit of a hack to assert dwciri:identifiedBy by annotating  some text label on the GBIF page .
I think you might want to think about either (a) using nanopubs to express the provenance of the statement that someone identified something, or (b) maybe use something like schema:Role to handle provenance. Nanopubs are cool but come with some overhead. But they capture what you want. I'm not sure it would be useful trying to embed them into the JSON-LD tree above though.
The other approach is to embed provenance directly in the graph using schema:Role, see "A Scalable Approach to Incrementally Building Knowledge Graphs" 10.1007/978-3-319-43997-6_15 PDF here It's a cool idea, but it breaks everyone's expectation of just getting simple triples. I think it's probably a reasonable model for when we aggregate data across multiple sources and want to track potential conflicts.
Hope some of this makes sense.

Thanks for having a look. Indeed, it's spectacular mess. What I'm really trying to do is say:
some person stated at timestamp that some occurrence dwciri:identifiedBy some person
Give the naked assertion some qualifier as it were. So yes, it is provenance but I do not see how/where I can express the first bit as qualifier unless I consider this some sort of annotation.

This is interesting and might perhaps be what I'm looking for. But, am baffled as to how I'd represent this in JSON-LD.

The entity on the left evidently has a property that is a list for the many schema:name.

OK this is how I think we'd represent this:
{
	"@context": {
		"@vocab": "http://schema.org/",
		"prov": "http://www.w3.org/TR/prov-o/"
	},

	"@id": "http://thing.org/royLichtenstein",
	"@type": "Person",
	"name": [{
			"@type": "Role",
			"name": "Roy L.",
			"prov:wasGeneratedBy": [
				"http://a.source.org/",
				"http://another.source.org/"
			]
		},
		{
			"@type": "Role",
			"name": "Lichtenstein",
			"prov:wasGeneratedBy": "http://someother.source.org/"
		}

	],
	"birthDate": {
		"@type": "Role",
		"birthDate": "1923-10-27",
		"prov:wasGeneratedBy": "http://a.source.org/"
	}

}

And here it is in triples:
<http://thing.org/royLichtenstein> <http://schema.orgbirthDate> _:b0 .
<http://thing.org/royLichtenstein> <http://schema.orgname> _:b1 .
<http://thing.org/royLichtenstein> <http://schema.orgname> _:b2 .
<http://thing.org/royLichtenstein> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://schema.orgPerson> .
_:b0 <http://schema.orgbirthDate> "1923-10-27" .
_:b0 <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://schema.orgRole> .
_:b0 <http://www.w3.org/TR/prov-o/wasGeneratedBy> "http://a.source.org/" .
_:b1 <http://schema.orgname> "Roy L." .
_:b1 <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://schema.orgRole> .
_:b1 <http://www.w3.org/TR/prov-o/wasGeneratedBy> "http://a.source.org/" .
_:b1 <http://www.w3.org/TR/prov-o/wasGeneratedBy> "http://another.source.org/" .
_:b2 <http://schema.orgname> "Lichtenstein" .
_:b2 <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://schema.orgRole> .
_:b2 <http://www.w3.org/TR/prov-o/wasGeneratedBy> "http://someother.source.org/" .

And as a graph:

In a sense this is a classic case of indirection, schema:name doesn't point to the value for the name, it points to a pointer to the value for the name. AFAIK the choice of schema:Role as the type of the intermediate node is arbitrary, but it has been used in various ways to do this sort of thing, e.g. http://blog.schema.org/2014/06/introducing-role.html I also used this in Ozymandias to model order of authorship, but now I've switched to using RDF lists instead.

OK, I think am getting closer. A big part of the messiness here is that the root entity is of type PreservedSpecimen that has some DwC-based properties recordedBy, which may be lists of other entities of type People that were created by yet other People via schema:Role.

Reverted back to original JSON-LD output without the arguably messy, annotation component(s).


Minor iAPS left-overs

These are nits - just providing this list so they are available for update when and if desired.
I am testing only alpha branch (soon to be dev).
Configuration: commit 99effeb7
This is a plist file so a little different:

Open-iAPS/FreeAPS/Resources/Info.plist
contains <string>com.artificial-pancreas-iaps</string>

The rest of these are in *.swift files and indicate the line numbers where hard-coded "iAPS" exists:

FreeAPS/Sources/Shortcuts/State/

ListStateIntent.swift, line 6, 12, (not sure about the StateiAPSResults, see next file)
StateIntentRequest.swift (I suspect this should be left alone - I do not know what it does)
ListStateView.swift (same comment)

Note: many of the rest of these should (later) be modified to use appName instead of hard coded string

I did not list all the places with hard-coded Open-iAPS but there are a lot
In the short term - simplest solution is to replace the hard-coded "iAPS" with hard-coded "Open-iAPS"
Next update, we can modify to using appName instead - that takes more time and effort

Hard-coded string from iAPS to Open-iAPS

Open-iAPS/FreeAPS/Sources/Application/FreeAPSApp.swift, line 58
Open-iAPS/FreeAPS/Sources/Modules/HealthKit/View/AppleHealthKitRootView.swift line 16
Open-iAPS/FreeAPS/Sources/Modules/NightscoutConfig/View/NightscoutConfigRootView.swift lines 106 and 132
Open-iAPS/FreeAPS/Sources/Modules/NotificationsConfig/View/NotificationsConfigRootView.swift line 95
Open-iAPS/FreeAPS/Sources/Modules/PreferencesEditor/PreferencesEditorStateModel.swift lines 44, 240, 381
Open-iAPS/FreeAPS/Sources/Modules/PreferencesEditor/View/PreferencesEditorRootView.swift line 25
Open-iAPS/FreeAPS/Sources/Services/WatchManager/GarminManager.swift line 160
Open-iAPS/FreeAPS/Sources/Services/Calendar/CalendarManager.swift line 96
Open-iAPS/FreeAPSWatch WatchKit Extension/ComplicationController.swift lines 11, 55

Hard-coded string from FAX to Open-iAPS

Open-iAPS/FreeAPS/Sources/Modules/PreferencesEditor/PreferencesEditorStateModel.swift line 150
Open-iAPS/FreeAPSWatch WatchKit Extension/ComplicationController.swift lines 62, 81

Here are some links for your review:
refers to widgetURL(URL(string: "freeaps-x://"))

https://github.com/nightscout/Trio/blob/dev/LiveActivity/LiveActivity.swift#L291

refers to a loopandlearn dot org page that I don't think exists anymore

https://github.com/nightscout/Trio/blob/dev/FreeAPS/Sources/Modules/PreferencesEditor/PreferencesEditorStateModel.swift#L35

The same phrase is in all the strings files too.
Other than this, I believe the left-overs are taken care of.

Here are some links for your review:
refers to widgetURL(URL(string: "freeaps-x://"))

https://github.com/nightscout/Trio/blob/dev/LiveActivity/LiveActivity.swift#L291

Thanks.
The url string can be updated to the hardcoded "Trio-x://". But we should probably use $(APP_URL_SCHEME) instead. Will have to test before making a PR. If someone wants to pick that up before me, please go ahead.
https://github.com/nightscout/Trio/blob/f23b38ad8b1ca3865ffc56482bf6c6740cad8ecf/Config.xcconfig#L9
https://github.com/nightscout/Trio/blob/f23b38ad8b1ca3865ffc56482bf6c6740cad8ecf/FreeAPS/Resources/Info.plist#L36-L38

refers to a loopandlearn dot org page that I don't think exists anymore

https://github.com/nightscout/Trio/blob/dev/FreeAPS/Sources/Modules/PreferencesEditor/PreferencesEditorStateModel.swift#L35

The same phrase is in all the strings files too.
Other than this, I believe the left-overs are taken care of.

Perhaps this is something for @t1dude to look at, to get to grips with how we best make changes to strings that are translated, now that Crowdin is being set up.

@MikePlante1 , I am nut sure what this does. I assumed it was to open the app when tapping the Live Activity, but that works also when URL(string: "freeaps-x://"
https://github.com/nightscout/Trio/blob/f23b38ad8b1ca3865ffc56482bf6c6740cad8ecf/LiveActivity/LiveActivity.swift#L291
I made the PR #197 anyways, for completeness. (replacing the old URL(string: "freeaps-x://")

Closing this as completed now that PR #197 is merged.

refers to a loopandlearn dot org page that I don't think exists anymore

https://github.com/nightscout/Trio/blob/dev/FreeAPS/Sources/Modules/PreferencesEditor/PreferencesEditorStateModel.swift#L35

The same phrase is in all the strings files too.

Other than this, I believe the left-overs are taken care of.

Perhaps this is something for @t1dude to look at, to get to grips with how we best make changes to strings that are translated, now that Crowdin is being set up.

@marionbarker , the LnL link is not fixed yet, but probably will be when #216 is merged.


mifos account password changed

I got an automated alert (from some Google Cloud Monitoring that I had set up) that the mifos account's password on the Fineract.dev demo server changed.
So you currently actually cannot _login with e.g. mifos/password (anymore), as per https://www.fineract.dev.
 It doesn't really matter which one it is - I now must manually reset the mifos user's password.
The more interesting question is perhaps how to prevent this from happening again.... couple of thoughts with ideas what we could do here for the general underlying issue - opinions welcome, e.g. from @ptuomola or @davidyaha or anyone else interested:

Should we look into introducing a feature in Fineract (core) to have "locked passwords"? Then set that on the mifos account. It would likely prevent "accidental" changes, but someone truly malicious could still create ANOTHER admin account on the demo server and then use that one to change the mifos user account... so yeah, maybe not.

Should we just not have a default mifos/password on our community demo server at all anymore?! But that would then require some other mechanism to "sign up" to get a personal account on it. Could be interesting. Slightly raises the bar for people to try it though. Perhaps that could be a good thing?

Hey @vorburger
I think the 2nd approach is preferable. we have a bit of experience with something like that with the "fineract as a service" we used to have. it is currently down and we don't have the capacity to maintain it but something like that could be both easy to use and "safer". Another feature that could be added to what we've done is a population of demo data for each tenant.
This way, each user that wishes to checkout Fineract would have their own tenant with demo data to play with.
This could a significant effort to get this working but so a quick fix for the meantime would be creating an SQL script that sets mifos/password each night with something like a scheduled google function.

Hey @vorburger
I think the 2nd approach is preferable. we have a bit of experience with something like that with the "fineract as a service" we used to have. it is currently down and we don't have the capacity to maintain it but something like that could be both easy to use and "safer". Another feature that could be added to what we've done is a population of demo data for each tenant.
This way, each user that wishes to checkout Fineract would have their own tenant with demo data to play with.
This could a significant effort to get this working but so a quick fix for the meantime would be creating an SQL script that sets mifos/password each night with something like a scheduled google function.

a quick fix for the meantime would be creating an SQL script that sets mifos/password each night with something like a scheduled

Yeah, I'm going to fix this doing something like that, for now. One of these evenings or on a future week-end! 😃
Re. population of demo data, let's continue that discussion in https://issues.apache.org/jira/browse/FINERACT-1238, if you like.

a quick fix for the meantime would be creating an SQL script that sets mifos/password each night with something like a scheduled

Yeah, I'm going to fix this doing something like that, for now. One of these evenings or on a future week-end! 😃
Re. population of demo data, let's continue that discussion in https://issues.apache.org/jira/browse/FINERACT-1238, if you like.

I've FINALLY gotten around to fixing this (just been busy, see also https://github.com/openMF/fineract-pentaho/issues/25), at least manually one off, for now.
Because there also are frequent java.lang.OutOfMemoryError, I've just gone ahead and: 1. took a backup of DB instance, 2. stopped server, 3. deleted fineract_default DB (NOT instance), 4. re-created fineract_default DB, 5. restarted server.
Keeping this issue open for future automation, as above.

Great stuff - thanks Michael! Good to see Fineract.dev usable again
Just wondering about the permanent fix:

Locking this account so that it’s password cannot be changed will just shift the problem to another account - i.e. the root account that then can be used to “unlock” this account. Unless we want to make it so that the unlocking can only be done at a database level? That would work.

Registering for your own account is something that works well with the demo but I’m not sure if it’s a useful feature for a real core banking solution - you really don’t want to allow people to create their own accounts on a real production banking system…

Would the easiest way just be to write a script that resets the Fineract.dev database to original state once a day / once a week?
Alternatively we can do #1 above in such way that the unlocking can only be done at a database level - that should be pretty straightforward….
Regards
Petri

On 27 Jun 2021, at 10:27 PM, Michael Vorburger ⛑ @.***> wrote:
I've FINALLY gotten around to fixing this (just been busy, see also openMF/fineract-pentaho#25 https://github.com/openMF/fineract-pentaho/issues/25), at least manually one off, for now.
Because there also are frequent java.lang.OutOfMemoryError, I've just gone ahead and: 1. took a backup of DB instance, 2. stopped server, 3. deleted fineract_default DB (NOT instance), 4. re-created fineract_default DB, 5. restarted server.
Keeping this issue open for future automation, as above.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/vorburger/www.fineract.dev/issues/5#issuecomment-869172589, or unsubscribe https://github.com/notifications/unsubscribe-auth/AASJVCUY6ZYTXC2TSB4ZZULTU4YOTANCNFSM4WGBRLFA.

@ptuomola Thank You for https://github.com/apache/fineract/pull/2001 for https://issues.apache.org/jira/browse/FINERACT-1452.
I've now "activated" this for the demo instance (using UPDATE m_appuser SET cannot_change_password = true; // WHERE id = 1).
Problem solved & case closed! Thanks again.


i2c, pin, spi: Figure out a way for driver to communicate real chosen speed back to user

Use cases:

spi.Port.Connect()
spi.PortCloser.LimitSpeed()
i2c.Bus.SetSpeed()
pin.PinOut.PWM()

In these cases, if the host driver had to choose a different frequency, it has no way to communicate this information back to the user.

Ported to https://github.com/periph/conn/issues/33.


[Lightbox media viewer] Web Component & React: Include the layout updates

User Story

As a [user role below]:
Carbon for ibm.com developer

I need to:
create/change the Lightbox media viewer

so that I can:
provide the ibm.com adopter developers components they can use to build ibm.com web pages

Additional information

Story within Storybook with corresponding knobs
Utilize Carbon
Create with Shadow DOM and Custom Elements standards
See the Epic for the Design and Functional specs information
Web Components Visual QA testing issue (#?designqa issue?)
Design specs done by Kirby Evans
Web Components Prod QA testing issue (#?prodqa issue?)

Design specs for the proposed solution can be found here:
PDF
Sketch file
Preview of specs for Lightbox media viewer

Acceptance criteria

[ ] Include README for the web component and corresponding styles
[ ] Create Web Components styles in styles package
[ ] Do not create knobs in Storybook that include JSON objects
[ ] Break out Storybook stories into multiple variation stories, if applicable
[ ] Create codesandbox example under /packages/web-components/examples/codesandbox and include in README
[ ] Minimum 80% unit test coverage
[ ] Update the Carbon for ibm.com website component data file to be sure the web site Component Status and Storybook links are correct
[ ] Use the Visual QA checklist to verify design quality
[ ] Include the DDS design consultant in the Pull Request for the Visual QA
[ ] Provide a direct link to the deploy preview for the designer in the Pull Request description
[ ] A comment is posted in the Prod QA issue, tagging Praveen when development is finished

Team has discussed and will do both Web Components and React at the same time. Will close the React story.

Func spec done.
@RobertaJHahn this is ready for Monday's engineering refinement. Looks like James is not feeling well the past few days, so I can present the specs.


fix(FX-3072): jerky popover message

The type of this PR is: Fix

This PR resolves FX-3072
Description

Multiple toasts onscreen at the same time results in somewhat jerky movement of the toasts when one disappears. We would like to prevent this movement so that the user has a smooth experience.
We only need one single toasts as its a toggle and should reflect the last action for clarity. So a new toast would move in and replace the current.

iOS
https://user-images.githubusercontent.com/3513494/125271415-67c85c80-e313-11eb-82bd-47994ad255fc.mp4
Android
https://user-images.githubusercontent.com/3513494/125272300-5b90cf00-e314-11eb-9c7b-b052a7ed60be.mp4

PR Checklist (tick all before merging)

[x] I have included screenshots or videos to illustrate my changes, or I have not changed anything that impacts the UI.
[x] I have tested my changes on iOS and Android.
[x] I have added tests for my changes, or my changes don't require testing, or I have included a link to a separate Jira ticket covering the tests.
[x] I have added a feature flag, or my changes don't require a feature flag. (How do I add one?)
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added an app state migration, or my changes do not require one. (What are migrations?)
[x] I have added a CHANGELOG.yml entry below or my changes do not require one.

Changelog updates
Changelog updates

Cross-platform user-facing changes

Stop jerky movement of multiple toasts - dzmitry tratsiak

iOS user-facing changes

Android user-facing changes

Dev changes

This PR contains the following changes:

Cross-platform user-facing changes (Stop jerky movement of multiple toasts - dzmitry tratsiak)

  Generated by :no_entry_sign: dangerJS against 67616278a59fd2cc6649c8369bb74b0cfe8d7fe5

@mdole Thanks. It's nice to hear such words


PipsPager: API Update

Description

This PR updates API of the PipsPager based on the revised specs.
Motivation and Context

What has been done:

Updated naming for several components
Revised IDL and removed experimental flag
PipsPagerSelectedIndexChangedEventArgs are now empty
Removed 2.5 themeresources
Fixed little bug making outer scrollViewers also scroll

How Has This Been Tested?


Spelling mistake

"WC3 WebAuthn standard" should probably be "W3C WebAuthn standard"

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

ID: e1d3d10a-690c-6744-53bf-3f1e75c79908
Version Independent ID: e1d3d10a-690c-6744-53bf-3f1e75c79908
Content: How to enable passkeys in Microsoft Authenticator sign in for Microsoft Entra ID (preview) - Microsoft Entra ID
Content Source: docs/identity/authentication/how-to-enable-authenticator-passkey.md
Service: entra-id
Sub-service: authentication
GitHub Login: @Justinha
Microsoft Alias: justinha

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

@vlijmenfileer
Thanks for reporting this! We have created a PR for this issue and the changes should go live soon.
https://github.com/MicrosoftDocs/entra-docs-pr/pull/3226


[Java] ErrorProne Warnings to be considered as Errors

Describe the enhancement requested
Even though we have integrated the ErrorProne module in each module, we still see iterative development cycle introduces more warnings, and to avoid this it would be better to error them so that in the development time these are properly tracked and addressed. This must be done for each module.

[X] Algorithm

Component(s)
Java

@lidavidm looking into the available flags we do have the following https://errorprone.info/docs/flags
For instance, the available flags don't seem to have something like an error warning, rather it has -XepAllErrorsAsWarnings.  Not sure if we have an option the other way around? But we can do it manually for each category of warnings like -Xep:MissingOverride:ERROR. But this requires making a list of items that may not cover all the angles we hope for.   Still needs further investigation...

Um, (1) warnings-as-errors is just a javac option (2) my original concern wasn't about the errorprone warnings, it was just about the regular javac deprecation warnings.

I see, I have misunderstood it. Either way, I will make the improvements on both fronts as required. And I will investigate about (1) and how to add that.


Clarify that the context root can be iterated over

Since some implementations differ on whether the root of the context stack can be iterated over, this adds langauge to the "Sections" spec clarifying that it can. It also adds a test for this case.
Fixes #87. I did not add the two additional tests for the "Interpolation" spec that I recommended in that issue since there are tests that cover them now (not sure if these are new or if I just missed them before).
The first commit here is just the result of running rake build before making the above changes, since the current JSON and YAML are out of sync. I can separate that into a different PR if helpful, or you can just review this by focusing on the second commit. (As a side note: would it be helpful to have a GitHub action to check PRs for whether the JSON and YAML are in sync? I’m happy to do a PR that adds that.)

(As a side note: would it be helpful to have a GitHub action to check PRs for whether the JSON and YAML are in sync? I’m happy to do a PR that adds that.)

Yes please!

Is this just fixing an omission (I say yes) or do some consider this "too breaking"?

From a semantic versioning and spec-based perspective, I think this is a minor release/new feature (so: v1.4.0). It is adding definition where behavior is currently undefined.
That said, I can definitely see the argument that, from an implementor perspective, this is breaking and requires a major release, since code that passes tests and matches the specs today could become incorrect as soon as this lands (e.g. Hogan would become non-compliant). But the same could be said for a lot of (most?) new features in the spec. I think the more salient thing is whether this changes existing defined behavior, and it does not do that.

You said the interpolation tests you suggested… were already included. I found the second one but not the first

Ah! I should have linked them in the PR description, sorry. They are:

The one I called "Dotted Names - Single Period" is covered by: https://github.com/mustache/spec/blob/982aa9bf9d68b08f1baef049c289196e781ed2ab/specs/sections.yml#L68-L75
(This one is already in the "Sections" spec, which is good. I think you are correct that it’s a better place than where I was thinking in the "Interpolation" spec.)

The one I called "Dotted Names - Root-level Single Period" is covered by: https://github.com/mustache/spec/blob/982aa9bf9d68b08f1baef049c289196e781ed2ab/specs/interpolation.yml#L202-L208
(I’m not sure why this has “implicit iterators” in the name, since it’s not iterating… 🤷)

From a semantic versioning and spec-based perspective, I think this is a minor release/new feature (so: v1.4.0). It is adding definition where behavior is currently undefined.

This didn't sit well with me, but fortunately, the README is quite clear about what should happen:

Roughly described, major version changes will always represent backwards incompatible changes,

As you wrote, the change is not backwards incompatible, so no major version.

minor version changes will always represent new language features and will be backwards compatible,

I would argue that there is no new language feature in play here.  Hence, I don't think this is a minor version, either.

and patch ('tiny') version changes will always be bug fixes.

My interpretation of "bug" here is

something about the infrastructure that doesn't work;
having two tests (or more) that contradict each other (inconsistency label);
missing a test for something that was already intended during an earlier change (omission label).

My interpretation of your change is that it is an instance of number 3, so I think this change by itself would constitute a patch version.

@spullara or @bobthecow, do you agree we can merge this?

Looks good to me. I am pretty sure this is already my current behavior.

Thanks and congratulations @Mr0grog!

👍 to merging it, but 👎 for making it a patch release. it's specifying previously unspecified behavior, so it's at least a minor version. "bug" is "we meant a thing, but tested for it poorly".
i'd interpret the backwards compatibility requirement not as "won't make existing implementations non-compliant" but as "changing a thing previously required", i.e. it wouldn't be possible to pass both the previous version and this version of the spec. so this feels like a minor version change to me.

👍 to merging it, but 👎 for making it a patch release. it's specifying previously unspecified behavior, so it's at least a minor version. "bug" is "we meant a thing, but tested for it poorly".

Do you think this is previously unspecified behavior? I think this was intended all along, but tested incompletely. In #87, everyone seemed to have interpreted the spec in this way already. Just a few comments up, @Mr0grog also pointed out that similar behavior was already specified for the interpolation tag, which makes it seem reasonable that the section tag should behave analogously:
https://github.com/mustache/spec/blob/982aa9bf9d68b08f1baef049c289196e781ed2ab/specs/interpolation.yml#L202-L208

i'd interpret the backwards compatibility requirement not as "won't make existing implementations non-compliant" but as "changing a thing previously required", i.e. it wouldn't be possible to pass both the previous version and this version of the spec. (...)

Sound like we all agree on how to decide whether something is a major release. Perhaps you missed my previous comment: https://github.com/mustache/spec/pull/176#issuecomment-1813519077.

Do you think this is previously unspecified behavior? I think this was intended all along, but tested incompletely.

if that's the case, and if everyone implemented it this way, then i'm fine with "patch".

Perhaps you missed my previous comment

I didn't miss it, I was confirming that I don't think it requires a major version, as an aside, while talking about whether it was minor or patch 😛


Setting maxRetry amount

@jcramer
In case of Bitcoin Cash node service are not ready yet SLPDB will continuously try to connect to it.
Right now SLPDB hardcode a maxRetries amount to 2 lead to the server crash after 2 retries.
https://github.com/simpleledger/SLPDB/blob/7e487d234d20421596fe9f59485594f6050433c9/rpc.ts#L26
My suggested solution is to add an environment variable to make maxRetries configurable to a higher number.
Example fix.
https://github.com/ActorForth/SLPDB-src/pull/6/commits/e49770cee5ce0b92b43dafdf4572ed38a2abb935
If you are ok with the sample implementation I can create a PR after.

I'd be fine with a pr that preserves the original default for maxTries.  It looks the mentioned commit updates the default to 100.

@jcramer
Which branch should I create PR to.

master is fine.


Increase process numbers to 1000 from 500 in Oracle test

Related to #3781, #3798

https://github.com/prestosql/presto/pull/3795/checks?check_run_id=692927473

@ebyhr can you leave the comment in the test updated with the new value, so that we know what value is configured


libint: 2.8.2 -> 2.9.0

Description of changes
Libint upstream update: https://github.com/evaleev/libint/releases/tag/v2.9.0
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

CI failed on x86_64-linux

CI failed on x86_64-linux

The build is too long for OfBorg. It times out. I could successfully build it locally.


Deleting a node does not update the widget

Bug report
Bug summary
When I delete a node from the graph, the previously displayed widgets are not updated.
Code for reproduction
#%%
from ipycytoscape import CytoscapeWidget
import networkx as nx

G = nx.Graph()
G.add_nodes_from([0,1])
G.add_edge(0, 1)

cyto_widget = CytoscapeWidget()
cyto_widget.graph.add_graph_from_networkx(G)
cyto_widget

#%%
cyto_widget.graph.remove_node_by_id('0')

#%%
cyto_widget

Actual outcome

The left panel is the output from the first time the widget is shown and the right panel is from the second time the widget is shown (which is the expected output).
Version Info

ipycytoscape version : 1.2.0
Python version: 3.9
Jupyter(Lab) version: 3.0

Thanks for the bug report @ahrm!
I think I fixed this issue months ago in the open PR, at least that's the name for my commit: https://github.com/QuantStack/ipycytoscape/pull/177/commits/593c1c8d0d30a9539ac17ec81f5f4687cd6605f2
Apparently what's missing here to merge this PR is my input for documenting it and creating tests, I'll try to get into it!

Fixed by #177


Bumping version 2.2.2 -> 2.2.3

Given that we are removing the need for cowboy in production we should probably bump the version.

Actually maybe this should be 2.3.0?


Added a new AppBundle to comply with Symfony Best Practices

Q
A

Bug fix?
no

New feature?
yes

BC breaks?
no

Deprecations?
no

Tests pass?
yes

Fixed tickets
#671

License
MIT

Doc PR
-

Symfony Best Practices recommend to start developing your applications with a single AppBundle bundle. This PR allows to include that AppBundle in the Symfony Standard Edition, to make it easier for developers.
I used the same skeleton as for the generate:bundle command, but I thought that it would be better to simplify it and remove the $name route parameter and use just a static template without parameters.

:+1:
finally, I got an idea
this rocks


Where is Joe Biden model from the GitHub demo?[QUESTION]

Question title (e.g. Where do I download RVC models?)
looking for additional voice models outside the included Bark models. The GitHub repo has a demo using Joe Biden's voice - is this available?  Is there a recommended place to download models?

I believe it's this one (although I might be wrong)
https://huggingface.co/0x3e9/Biden_RVC
The clip was created by first using bark to clone from a short clip of biden speaking, then I used the RVC model to improve the resemblence.


Prevent committing all of r-releases

I just released that the build_universe.yaml action is committing all the little text files in r-releases/r-releases. This PR amends the action to avoid this, and it deletes the duplicate copy of github.com/r-releases/r-releases.

I only meant to commit packages.json! Unfortunately the deploy action seems to commit an entire folder. I don't see an option to change that.


cleanup: remove notes from removed  parts related to traffic_manager

sorry @maskit , I had to stale it as there were some conflics with latest master changes.


Formally prove bidirectional_bridge core lemmas

Our goal is to formally prove the bidirectional_bridge core lemmas described in #35.
Informal proofs of these lemmas are given in https://github.com/input-output-hk/fm-ouroboros/issues/15#issuecomment-486381795.

I’m closing this issue, since this development will take place in the new repository network-equivalences.


[WIP] Revise mako

I needed to add in datatables for CSV viewing, so I did some work to address #271 .  Further work could be done to unify the css similarly.
This only works with a relatively recent Girder master, so maybe should wait to go in until v1.4.2, or else I should update the Girder branch in Travis to master.
@jbeezley I didn't touch any of the testing stuff so as to not get in your way.  Let me know if this moves things in the direction you want or if you have specific advice.

Thanks for the heads up.  It's unlikely I will get to making any changes that conflicts with what you are doing in this branch anytime soon.

@mgrauer why its WIP? Are you expecting more changes?

@aashish24 I wanted to gather feedback and also it pushes us onto Girder master (at least as far as Travis is concerned).
My feeling is that it is better for us to got to Girder v1.4.2 once that gets released, and make all of the changes at one time.  I'm happy to hear other opinions on this, such as, perhaps we could move Travis to Girder master for now and then peg to v1.4.2 upon its release.
I'll force push the branch to clean it up at least and then we can discuss further.

@kotfic  Let me know if this satisfies your needs in #271.

Talking to @kotfic  and @zachmullen today about integration branches gave me the idea to do that here.
Currently we are pegged to girder v1.4.1 in travis and a few other places.  Some branches, like this one, and #259, should go against the next Girder release, when we  move to that in Minerva.  We could create an integration branch in Minerva (called girder_1_5_0 or something), and then target and merge any PRs into that which need Girder functionality past v1.4.1.  We could set the travis Girder version to "master" in that integration branch, or set it commit by commit as PRs get merged into it.
There will probably be merge conflicts to resolve when we bring the integration branch into master.  Another option is to leave these types of PRs hanging around, and then merge them into master individually when the time is right, but that would likely result in merge conflicts also.
Any strong opinions here?

@mgrauer this looks good for my use case (LGFMUC?) - which initiated #271.
From a practical perspective I need this change,  and the change in girder, before I can continue work on the cumulus/minerva front-end integration. If there was an integration branch that tracked girder master (until there is a release)  I think that would make that easier.  I just don't want to be in a position where i need a fix that has gone into minerva/master  and not into minerva/girder_1_5_0
So do we merge minerva/master into this integration branch after PR's go into master? rebase with force-lease? Who is responsible for making sure the integration branch is in sync with minerva/master?

@kotfic
Here's what I propose:

I'll create a GH label girder_1_5_0
I'll create a new branch called girder_1_5_0 that will have a standing PR, and that changes

travis to Girder:master
ansible to Girder:master
specifies somewhere in the docs that it is pinned to girder 1.5.0

I'll create a new PR for this (#277) branch and for #259 that target the branch girder_1_5_0, have the label girder_1_5_0, link the new PRs back to the originals, then close this (#277) and #259, and merge these PRs.  As part of creating those new PRs I will probably change those branches a bit to remove the travis/ansible girder version changes.

Then any new PRs that need Girder 1.5.0 would target the girder_1_5_0 branch and have the label girder_1_5_0.
Any new PRs that don't need Girder 1.5 would target Minerva's master (the usual flow), and upon merging those PRs into Minerva's master, I will merge Minerva's master into the girder_1_5_0 branch.
Hopefully Girder 1.5.0 comes out soon and we can peg the 3 parts of that branch to Girder v1.5.0 and then merge girder_1_5_0 into Minerva master.
How does this sound?

We have elected to bump the version of girder we peg to.  After #281 gets merged, this branch should be rebased from there and then could go directly in.

I will rebase this on master, then test locally and with ansible.

@kotfic @danlamanna
This works for me, travis, and ansible.
PTAL.

Live by the LGFMUC, die by the LGFMUC.  Merging.

@mgrauer


Fix unclear issue with columns not uniquely identified

We found an issue when trying to use the qra code for the US death forecasts. Somehow (unclear why) there is a problem when having multiple creation dates. The error gets thrown in line 307 (now 308) in spread(quantile, weight), because some columns are not uniquely identified.
Running the weights through unique() once seems to fix the issue.
However: I don't know what causes the problem and it might be good to investigate this further

if your seeing this on a spread call its because there is a variable there that shouldn't be present I think. Have you tried debugging into the function to see what is before and afterwards?

Closing as potentially obfuscating issue.


Why remove "Check for updates"?

Issue Type: Feature Request
In old version (insider release), there is a "Check for update" under Help.
I like it and uses from time to time.
Why remove it?
VS Code version: Code - Insiders 1.26.0-insider (573d53815e74f8e4a52c2b6665f5ba9a92dbd341, 2018-08-01T05:17:54.216Z)
OS version: Windows_NT x64 10.0.17134

@sbatten Did you maybe remove this with the new menu?
fyi @joaomoreno

@sbatten Added bug label, please add repro steps.


Sound Implementation In-Engine

Put sounds into the engine to hear how they actually sound and tweak their settings

Sorry, wrong repo :-D


.well-known/openid-configuration failed

Describe the bug
I tried with this lib for my angular project. I configured everything with responseType: 'code'. When I try to login, I could see that I got the token already, but the page will still trying to get login again and again because I got the error:
'Access to XMLHttpRequest at 'https://xxx/.well-known/openid-configuration' from origin 'xxxyyyzzz' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.'
But this .well-known/openid-configuration is open directory, I could do it with simple curl xxx/.well-known/openid-configuration.
My Codes Snippets
Provide a minimal stackblitz based example that shows the issue. For this, you can use the example application of this repo and the identity providers used here.
export class SecurityService {
  private static readonly AUTH_CODE_FLOW_CONFIG: AuthConfig = {
    issuer: 'https://xxx/oauth/token',
    tokenEndpoint: 'https://xxx/oauth/token',
    clientId: 'clientId',
    responseType: 'code',
    scope: 'openid,roles,user_attributes',
    showDebugInformation: true,
  };
  constructor(private oauthService: OAuthService) {
    this.oauthService.configure(SecurityService.AUTH_CODE_FLOW_CONFIG);
    this.oauthService.issuer = 'https://xxx/oauth/token';
    this.oauthService.loadDiscoveryDocument('https://xxxm/.well-known/openid-configuration');
    this.oauthService.initCodeFlow();
    localStorage.setItem('test', 'test');
    console.log('from securityService constructor()');
  }

  login() {
    this.oauthService.tryLogin({
      onTokenReceived: receivedTokens => {
        localStorage.setItem('receivedToken', JSON.stringify(receivedTokens));
      },
      onLoginError: onLoginError => {
        localStorage.setItem('onLoginError', JSON.stringify(onLoginError));
      }
    })
      .then(p => {
        if (p === true) {
          this.oauthService.loadUserProfile().then(u => {
            this.userClaims = this.oauthService.getIdentityClaims();
            localStorage.setItem('userClaims', JSON.stringify(this.userclaims));
            localStorage.setItem('userInfo', JSON.stringify(u));
          });
        }
      });
    console.log('from securityService login()');
  }

I could see the access_token is already set successfully. But I always got a refresh of the page, because the XMLHttpRequest. to my openid-configuration is always CORS.
Expected behavior
logged successfully
Additional context
Add any other context about the problem here.

If you get CORS errors on the openid-configuration endpoint, that's likely a server configuration issue. It makes sense that cURL doesn't care, I don't think it does anything with CORS headers, as that's more of an instruction to browsers.
If the config is open, mind sharing which it is? Without access to it, it's hard for us to tell what the issue is.
You could always skip loading the discovery document, and configure everything manually.

Thx for your reply. I configure the openid-configuration manually in oauthService.loadDiscoveryDocument('https://xxx/.well-known/openid-configuration');. It works now. thanks for support !


Add GraalVM native test support for examples

Purpose

$Subject

Examples
N/A
Checklist

[ ] Linked to an issue
[ ] Updated the specification
[ ] Updated the changelog
[ ] Added tests

Closing this for now, since currently there are no tests in the examples


chore(java): workflow to test using different jdk versions

🧭 What and Why
Validate compatibility with different environments:

Java LTS versions: 8, 11 and 17
Java distributions: temurin and zulu

🎟 JIRA Ticket: APIC-643
Changes included:
Add javacompat job to check workflow.
On each Java version/distribution, the job builds Java API client and runs CTS tests.

Nothing more to add

converted to draft until we come back to this

closing since we choose a different implem


carbon-aggregator latest partial datapoint

Hi,
I have a SSD based node with carbon-aggregator being in front of 5 carbon-caches. I have a problem with aggregated metrics, the latest value that is stored in whisper file is always +/- twice lower than the usual metric value.
In the following case im aggregating data from 80 nodes (cpu usage).
Whisper file for cpu-idle looks like this:

1425610260 99681.524708
1425610320 99755.657654
1425610380 51996.786829
1425610440 None

As you can see the latest not-none value is smaller than first 2 values (which are regular ones). After next datapoint come in:

1425610260 99681.524708
1425610320 99755.657654
1425610380<PHONE_NUMBER>13
1425610440 52114.747810
1425610500 None

As you can see the latest value is again twice smaller. This becomes very confusing because there is always a fake-drop, and when the real drop appears we wont notice it and wont be able to react fast.
Im feeding graphite with collectd, with interval of 60 seconds, the aggregation rule looks like:
Aggregated.hosting.cpu.< cpumetric > (60) = sum Hosting.node.*.cpu-*.< cpumetric >
hint: (There are no spaces after less than and before more than signs but markdown dont want to accept it without spaces..)
And my config: http://pastebin.com/Ljtrwnm7
Playing with MAX_UPDATES_PER_SECOND didnt help me. Tried also to play with the aggregation method buffering time but it didnt make the trick. When i compose graph using aggregated metrics then it looks like on the end of graph(newest data) there is always a big drop (half value). However, when I compose this graph using non-aggregated data (just aggregating cllient side in grafana using graphite queries with "*") the graph is looking alright (no drops).
What can cause this behaviour?

Im closing as this most certainly is misconfiguration and not an actual bug. Sorry for confusion

No worries. :heart:


[jobScheduler]: Fixes #44 Setup Job to send notifications

Setup Job to send notifications for reminders ending in one hour

test link:
test link


sql: stub domain type info cols in information_schema.columns

PR: https://github.com/cockroachdb/cockroach/pull/33267
From release notes:

CockroachDB now defines columns domain_catalog, domain_schema and domain_name in information_schema.columns (using NULL values, since domain types are not yet supported) for compatibility with PostgreSQL clients. [#33267][#33267] {% comment %}doc{% endcomment %}

I'll take this one off your hands, @rmloveland. Simple fix.


fix: Retroactively add granularity param to charts

SUMMARY
We ran into some data accuracy issues in our environment where time range filters wouldn't apply to certain charts (like Big Number) when set on a dashboard. We determined that this was because these charts somehow didn't have a granularity param set on them, so the time range wasn't appropriately set on the chart query. This was especially dangerous, because the chart showed as applying the filter, but it wasn't actually applied to the query.
The fix is this db migration that adds the granularity param onto charts that should have one but don't.
TEST PLAN
Before the migration, see big number charts without the granularity or granularity_sqla param not filter by time range correctly.
Run the migration, and see the dashboard perform the filter appropriately.
ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Changes UI
[x] Requires DB Migration.
[x] Confirm DB Migration upgrade and downgrade tested.
[ ] Introduces new feature or API
[ ] Removes existing feature or API

to: @john-bodley @ktmud @graceguo-supercat @villebro
cc: @junlincc

Codecov Report

Merging #12960 (12210ca) into master (9982fde) will decrease coverage by 20.34%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master   #12960       +/-   ##
===========================================
- Coverage   69.14%   48.79%   -20.35%
===========================================
  Files        1025      478      -547
  Lines       48767    17243    -31524
  Branches     5188     4453      -735
===========================================
- Hits        33718     8414    -25304
+ Misses      14915     8829     -6086
+ Partials      134        0      -134

Flag
Coverage Δ

cypress
48.79% <ø> (-2.04%)
:arrow_down:

javascript
?

python
?

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

Impacted Files
Coverage Δ

...uperset-frontend/src/dashboard/util/dnd-reorder.js
0.00% <0.00%> (-100.00%)
:arrow_down:

...erset-frontend/src/common/hooks/useChangeEffect.ts
0.00% <0.00%> (-100.00%)
:arrow_down:

...rset-frontend/src/dashboard/util/getEmptyLayout.js
0.00% <0.00%> (-100.00%)
:arrow_down:

...dashboard/components/resizable/ResizableHandle.jsx
0.00% <0.00%> (-100.00%)
:arrow_down:

...dashboard/components/nativeFilters/ScopingTree.tsx
6.25% <0.00%> (-93.75%)
:arrow_down:

.../src/dashboard/util/getFilterScopeFromNodesTree.js
0.00% <0.00%> (-93.48%)
:arrow_down:

...set-frontend/src/views/CRUD/alert/ExecutionLog.tsx
11.76% <0.00%> (-88.24%)
:arrow_down:

...src/dashboard/components/gridComponents/Header.jsx
10.52% <0.00%> (-86.85%)
:arrow_down:

superset-frontend/src/components/IconTooltip.tsx
13.33% <0.00%> (-86.67%)
:arrow_down:

...rc/dashboard/components/gridComponents/Divider.jsx
13.33% <0.00%> (-86.67%)
:arrow_down:

... and 885 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 9982fde...12210ca. Read the comment docs.

@etr2460 I noticed a similar weirdness when I was fixing a regression in the table chart. For some reason the chart looked different in the dashboard compared to the Explore view. When looking at the metadata I noticed that the chart was missing a control value that had been added to the control panel after the chart had been created. Upon closer inspection it turned out Explore merges the chart metadata on top of the default control values, but dashboard doesn't. I didn't yet have time to look into this more closely, but I believe making sure the metadata flow is the same in Dashboard and Explore view might solve this problem, potentially making the migration unnecessary.

@etr2460 I noticed a similar weirdness when I was fixing a regression in the table chart. For some reason the chart looked different in the dashboard compared to the Explore view. When looking at the metadata I noticed that the chart was missing a control value that had been added to the control panel after the chart had been created. Upon closer inspection it turned out Explore merges the chart metadata on top of the default control values, but dashboard doesn't. I didn't yet have time to look into this more closely, but I believe making sure the metadata flow is the same in Dashboard and Explore view might solve this problem, potentially making the migration unnecessary.

I looked into this, and it turns out default values are in fact applied on the Chart form data on the Dashboard similarly as on the Explore view. The control panel on the Table chart was just setting the value of the queryModel control (which had the default value null) while rendering the control panel based on other form data.
Going forward we should potentially make default values "smarter", by making it possible to introduce hooks that return defaults based on other context. In the case of queryMode in table model, it would be inferred from the other formData, and in the case of granularity, it could default to main_dttm_col in the dataset if missing/unset.

Close and reopen to trigger docker-build and python-lint (3.7):

FYI a migration was merged today, so I believe we need to update the downgrade revision id. https://github.com/apache/superset/pull/13052

good call, updating now. And I agree @villebro there's some weirdness going on with passing parameters the same way between dashboard and explore. This might not be a long term fix, but more so fixes weirdness that's been cropping up currently


CI test

This change is

PR is added to the queue for testing as 1. task. (cb3ec72)

Test (Fail) 62379570 build is completed (cb3ec72)
See https://github.com/ThaliTester/TestResults/tree/62379570cb3ec72_CI_test_vjrantal/ for the logs

PR is added to the queue for testing as 1. task. (572d9da)

Test (Fail) 62379570 build is completed (cb3ec72)
See https://github.com/ThaliTester/TestResults/tree/62379570cb3ec72_CI_test_vjrantal/ for the logs

Test (Fail) 62379570 build is completed (572d9da)
See https://github.com/ThaliTester/TestResults/tree/62379570572d9da_CI_test_vjrantal/ for the logs

Test (Fail) 62379570 build is completed (572d9da)
See https://github.com/ThaliTester/TestResults/tree/62379570572d9da_CI_test_vjrantal/ for the logs


[Identity] Propagate additional token type values

Doesn't hurt to propagate this value if available.

API change check
API changes are not detected in this pull request.


Legacy execution order

Summary
Fixes https://github.com/facebook/jest/pull/6098
Summary
Facebook internally depended on undocumented execution order.
The order used to be less intuitive (IMO), as beforeAll scheduled inside of tests would go BEFORE the beforeAll scheduled inside the suite. It is now possible to restore that order by switching on the flag legacyExecutionOrder: true in jest's project configuration.
Keeping this undocumented on purpose.
Test plan
@mjesun added a test, I've added another one for the flag turned off.

Not needed after #6177


Update issue templates

I've created some issue templates in order to make reporting and tracking easier. We have:
Bug reports
Suggestions or feature requests
How-To questions
And all other types of issue.

What about a separate category for documentation?
Case in point: The README for the Tensorflow examples contains the old build instructions, should be updated to follow the main README.

Yes, documentation is an interesting question.
So the plan is that the documentation here in the repository is basically going to vanish. Maybe just a few things will remain, a link to the new documentation, the contribution guidelines and so on.
Then there'll be a proper "Picamera2 Manual" written from scratch that will be much more extensive than what's here now. Once that exists we'll make sure we have some way to report errors in it, maybe that will be issues here. Do you think it's worth having a documentation category in the interim for the old readme? I'm not sure. I suppose it would stop people wondering why there's no documentation category...!
I note that you're right about that tensorflow readme, though. It's quite out-of-date and actually wrong in many respects. It probably just wants deleting because everything is covered in the main readme.
Thanks!

Do you think it's worth having a documentation category in the interim for the old readme? I'm not sure.

Agreed. My suggestion was triggered by the outdated Tensorflow README.
Will the official documentation have its own repository or be part of the overall documentation repository?
I guess in the interim we could report those type of issues in the 'Other' category.

My suggestion was triggered by the outdated Tensorflow README.

There's now a PR to get rid of that, so thanks for pointing it out!

Will the official documentation have its own repository or be part of the overall documentation repository?

That's up to the documentation overlords, of whom I am not one... hopefully I'll know more soon.

@davidplowman They all look good to me, I think keeping an issue to a single item makes a lot of sense.  Happy for me to merge now?


[bug] broken panels on k8s-views-nodes in specific cases

Describe the bug
The k8s-views-nodes.json dashboard will have many broken panels in specific Kubernetes setups.
This is currently the case on OKE.
Apparently, this happens when the node label from kube_node_info doesn't match the nodename label from node_uname_info.
Here's some extracted metrics from a broken setup where the labels differ.
TL;DR: node="k8s-wrk-002" and nodename="kind-kube-prometheus-stack-worker2".
kube_node_info:
{
    __name__="kube_node_info",
    container="kube-state-metrics",
    container_runtime_version="containerd://1.6.19-46-g941215f49",
    endpoint="http",
    instance="<IP_ADDRESS>:8080",
    internal_ip="<IP_ADDRESS>",
    job="kube-state-metrics",
    kernel_version="6.2.12-arch1-1",
    kubelet_version="v1.26.3",
    kubeproxy_version="v1.26.3",
    namespace="monitoring",
    node="k8s-wrk-002",
    os_image="Ubuntu 22.04.2 LTS",
    pod="kube-prometheus-stack-kube-state-metrics-6df68756d8-zvd58",
    pod_cidr="<IP_ADDRESS>/24",
    provider_id="kind://docker/kind-kube-prometheus-stack/kind-kube-prometheus-stack-worker2",
    service="kube-prometheus-stack-kube-state-metrics",
    system_uuid="8422f117-6154-45bd-97c0-e3dec80a3f60"
}

node_uname_info:
{
    __name__="node_uname_info",
    container="node-exporter",
    domainname="(none)",
    endpoint="http-metrics",
    instance="<IP_ADDRESS>:9100",
    job="node-exporter",
    machine="x86_64",
    namespace="monitoring",
    nodename="kind-kube-prometheus-stack-worker2",
    pod="kube-prometheus-stack-prometheus-node-exporter-qvn22",
    release="6.2.12-arch1-1",
    service="kube-prometheus-stack-prometheus-node-exporter",
    sysname="Linux",
    version="#1 SMP PREEMPT_DYNAMIC Thu, 20 Apr 2023 16:11:55 +0000"
}

This issue will continue the discussion started in https://github.com/dotdc/grafana-dashboards-kubernetes/pull/41
@fcecagno @Chewie
How to reproduce?
You can use https://github.com/dotdc/kind-lab, that will create a kind cluster with renamed nodes.
# Create the kind cluster
./start.sh

# Export configuration
export KUBECONFIG="$(pwd)/kind-kubeconfig.yml"

# Expose Grafana
kubectl port-forward svc/kube-prometheus-stack-grafana -n monitoring 3000:80

Open http://localhost:3000
login: admin
password: prom-operator
Open broken dashboard:
http://localhost:3000/d/k8s_views_nodes/kubernetes-views-nodes?orgId=1&refresh=30s
Expected behavior
Dashboard should work with a relabel_configs like suggested @Chewie.
The solution should be described in https://github.com/dotdc/grafana-dashboards-kubernetes#known-issues
Additional context
No response

Thank you for the reproduction scenario!
I'll take a stab at documenting this and give some relabeling config.
My particular case was easier since there already was another label in grafana agent's node exporter that could be used for the nodename, but I'll need to investigate the scenario you provided to see if there's a way to make that info appear in node exporter.

Update: turns out the solution was in plain sight, right in the kube-prometheus-stack helm values.
This relabeling should take care of all situations where node-exporter is deployed through kube and decides to expose the name of its pod as a nodename.
I just need to check if this relabeling also works with the grafana agent (in theory it should, it uses the same codebase as prometheus for service discovery), then I'll open a PR documenting this relabeling :)

That would be great! I drafted a PR with the workaround explanation, eager to know if this fix works for your setup!

That's great!
@Chewie, does it work with the Grafana Agent?
@fcecagno, please let us know if the rule work on OKE.

@fcecagno Workaround is available here : https://github.com/dotdc/grafana-dashboards-kubernetes#known-issues


Master nodes get wrong label

Hi,
I am testing out this operator on our cluster but it fails to finish on our vmware plaform because the nodes joins the cluster a worker.
By manual changing the labels to master and control-plane is works.
This is our config:
apiVersion: machine.openshift.io/v1
kind: ControlPlaneMachineSet
metadata:
  name: cluster
  namespace: openshift-machine-api
spec:
  replicas: 3
  selector:
    matchLabels:
      machine.openshift.io/cluster-api-cluster: cl01-f7p2m
      machine.openshift.io/cluster-api-machine-role: master
      machine.openshift.io/cluster-api-machine-type: master
  state: Active
  strategy:
    type: RollingUpdate
  template:
    machineType: machines_v1beta1_machine_openshift_io
    machines_v1beta1_machine_openshift_io:
      metadata:
        labels:
          machine.openshift.io/cluster-api-cluster: cl01-f7p2m
          machine.openshift.io/cluster-api-machine-role: master
          machine.openshift.io/cluster-api-machine-type: master
      spec:
        metadata:
          labels:

        providerSpec:
          value:
            numCoresPerSocket: 4
            diskGiB: 240
            snapshot: ''
            userDataSecret:
              name: worker-user-data
            memoryMiB: 32768
            credentialsSecret:
              name: vsphere-cloud-credentials
            metadata: { }
            numCPUs: 4
            kind: VSphereMachineProviderSpec
            network:
              devices:
                - networkName: xxx
                - networkName: xxx
            workspace:
              datacenter: ITS
              folder: /ITS/vm/OpenShift/
              datastore: xxxx
              resourcePool: xxxx
              server: xxxx
            template: /ITS/vm/OpenShift/templates/openshift-4.14.1
            apiVersion: machine.openshift.io/v1beta1

and this is the lables set on the node
 cl01-f7p2m-master-gpgvk-0                 Ready                 worker

adding this to the spec.template.spec fix the issue, but is this also they way to go? because this is not documented.
https://docs.openshift.com/container-platform/4.14/machine_management/control_plane_machine_management/cpmso-configuration.html#cpmso-yaml-sample-cr_cpmso-configuration
spec:
  ...
  template:
     ...
      spec:
        metadata:
          labels:
            node-role.kubernetes.io/control-plane: ""
            node-role.kubernetes.io/master: ""


Pin pandas dependency to 1.2

This should resolve the nightly test failures observed in:
https://github.com/dask-contrib/dask-sql/actions/runs/1737510437

Codecov Report

Merging #376 (20b5504) into main (bba282a) will increase coverage by 0.13%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #376      +/-   ##
==========================================
+ Coverage   95.46%   95.60%   +0.13%
==========================================
  Files          67       67
  Lines        2932     2932
  Branches      546      546
==========================================
+ Hits         2799     2803       +4
+ Misses         83       79       -4
  Partials       50       50

Impacted Files
Coverage Δ

dask_sql/physical/rel/custom/show_models.py
80.00% <0.00%> (+26.66%)
:arrow_up:

Continue to review full report at Codecov.

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

Closing in favor of #377


More presence options

I wanted to keep roPresence open all the time without it always showing me as playing Roblox when just on the website, so I edited the code for the ability to toggle which presence status to show through the config for toggling offline and website presence. I'm making a pull request just to share my changes.

Looks good to me.
Is it working on your side?

Yeah, i've been using it for a few hours with offline and website presence disabled and it works fine only showing in game and in studio, testing it with them enabled works exactly the same as normal


Need help in configuring s3 ping for keycloak cache stack

Hi Team,
It is not an issue which i am raising here.
While checking the keycloak distributed cache articles for aws ec2 instances, i landed up in the git page. I have gone through the read me document of this git page.
Still i am not sure, whether i have to use the "jgroups-aws/src/main/java/org/jgroups/protocols/aws/S3_PING.java" under my keycloak directory.
I follow the document like two things are clear to me.

Pom.xml changes
keycloak conf cache-ispn.xml chnages.

But certain other details are not clear to me, sorry if i am asking like a layman terms.

Can you link the keycloak documentation you used?
I am assuming they haven't upgraded to JGroups 5.x, thus they using this version - https://github.com/jgroups-extras/jgroups-aws/tree/native-s3-ping-1.0.0.Final

Hi Radoslav,
Main article from keycloak is "https://www.keycloak.org/server/caching".
Under here, you can check the heading "Additional transport stacks"
Additional transport stacks
The following table shows transport stacks that are supported by Keycloak,
but need some extra steps to work. Note that none of these stacks are
Kubernetes / OpenShift stacks, so no need exists to enable the "google"
stack if you want to run Keycloak on top of the Google Kubernetes engine.
In that case, use the kubernetes stack. Instead, when you have a
distributed cache setup running on AWS EC2 instances, you would need to set
the stack to ec2, because ec2 does not support a default discovery
mechanism such as UDP.
Stack name
Transport protocol
Discovery
ec2
TCP
NATIVE_S3_PING
google
TCP
GOOGLE_PING2
azure
TCP
AZURE_PING
Cloud vendor specific stacks have additional dependencies for Keycloak. For
more information and links to repositories with these dependencies,
see the Infinispan
documentation
https://infinispan.org/docs/dev/titles/embedding/embedding.html#jgroups-cloud-discovery-protocols_cluster-transport
.
Followed the link "
https://infinispan.org/docs/dev/titles/embedding/embedding.html#jgroups-cloud-discovery-protocols_cluster-transport"
and ended up in the github page of yours.
On Tue, 26 Jul 2022 at 16:36, Radoslav Husar @.***>
wrote:

Can you link the keycloak documentation you used?
I am assuming they haven't upgraded to JGroups 5.x, thus they using this
version -
https://github.com/jgroups-extras/jgroups-aws/tree/native-s3-ping-1.0.0.Final
—
Reply to this email directly, view it on GitHub
https://github.com/jgroups-extras/jgroups-aws/issues/210#issuecomment-1195340135,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AP4YZ5MKF7MDS4HWP4LA733VV7BFFANCNFSM54VMCIJQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Regards,
Arulaln A R
+91-8754438576

I see, that documentation is lacking and is a bit sloppy. The https://www.keycloak.org/server/caching links to the 'dev' version of infinispan - https://infinispan.org/docs/dev/titles/embedding/embedding.html#jgroups-cloud-discovery-protocols_cluster-transport -  as opposed to the one actually used, so the documentation doesn't match.
I assume what the documentation tells you is to do something like:
cd providers
wget https://repository.jboss.org/nexus/content/repositories/releases/org/jgroups/aws/s3/native-s3-ping/1.0.0.Final/native-s3-ping-1.0.0.Final.jar
bin/kc.sh build --cache-stack=ec2

Hi Radoslav,
Thanks for the details. I am trying to use the same.
Downloaded the jar file and then included the cache stack as ec2.
Configured the cache-ispn.xml file. But there is something i am missing
which is pom.xml, where do i change that?
If you are free, we can connect via zoom call and discuss this.
Please let me know.
On Tue, 26 Jul 2022 at 17:53, Radoslav Husar @.***>
wrote:

I see, that documentation is lacking and is a bit sloppy. The
https://www.keycloak.org/server/caching links to the 'dev' version of
infinispan -
https://infinispan.org/docs/dev/titles/embedding/embedding.html#jgroups-cloud-discovery-protocols_cluster-transport

as opposed to the one actually used, so the documentation doesn't match.

I assume what the documentation tells you is to do something like:
cd providers
wget https://repository.jboss.org/nexus/content/repositories/releases/org/jgroups/aws/s3/native-s3-ping/1.0.0.Final/native-s3-ping-1.0.0.Final.jar
bin/kc.sh https://repository.jboss.org/nexus/content/repositories/releases/org/jgroups/aws/s3/native-s3-ping/1.0.0.Final/native-s3-ping-1.0.0.Final.jarbin/kc.sh build --cache-stack=ec2
—
Reply to this email directly, view it on GitHub
https://github.com/jgroups-extras/jgroups-aws/issues/210#issuecomment-1195414097,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AP4YZ5PY3OOXCVHHUSDMMZDVV7KERANCNFSM54VMCIJQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Regards,
Arulaln A R
+91-8754438576

Hi,
I had similar issue.  To resolve I did the following:

In docker file don't specify either env var KC_CACHE_STACK or cli parameter cache-stack ec2 (since current keycloak isn't yet on latest jgroups and copy dependencies:
`
RUN curl -sL https://search.maven.org/remotecontent?filepath=org/jgroups/aws/jgroups-aws/2.0.1.Final/jgroups-aws-2.0.1.Final.jar -o /opt/keycloak/providers/jgroups-aws-2.0.1.Final.jar
RUN curl -sL https://search.maven.org/remotecontent?filepath=com/amazonaws/aws-java-sdk-core/1.12.304/aws-java-sdk-core-1.12.304.jar -o /opt/keycloak/providers/aws-java-sdk-core-1.12.304.jar
RUN curl -sL https://search.maven.org/remotecontent?filepath=com/amazonaws/aws-java-sdk-s3/1.12.304/aws-java-sdk-s3-1.12.304.jar -o /opt/keycloak/providers/aws-java-sdk-s3-1.12.304.jar
RUN curl -sL https://search.maven.org/remotecontent?filepath=com/amazonaws/jmespath-java/1.12.304/jmespath-java-1.12.304.jar -o /opt/keycloak/providers/jmespath-java-1.12.304.jar
RUN curl -sL https://search.maven.org/remotecontent?filepath=joda-time/joda-time/2.11.1/joda-time-2.11.1.jar -o /opt/keycloak/providers/joda-time-2.11.1.jar

These are customized, from default.  should just be able to use stack ec2 option once keycloak infinispan version is updated.
COPY --chown=keycloak conf/cache-ispn-ec2.xml /opt/keycloak/conf/cache-ispn-ec2.xml
COPY --chown=keycloak conf/custom-jgroups-ec2.xml /opt/keycloak/conf/custom-jgroups-ec2.xml
RUN chmod 664 /opt/keycloak/conf/cache-ispn-ec2.xml
RUN chmod 664 /opt/keycloak/conf/custom-jgroups-ec2.xml
RUN /opt/keycloak/bin/kc.sh build --db=mysql --cache-config-file=cache-ispn-ec2.xml
`

In custom cache-ispn-ec2.xml add jgroups section and define transport in cache-container:
`

...
`

define your custom-jgroups-ec2.xml as per the example in readme file.

Regards,
Harold

Hi.
I've been struggle with this as well.  I did everything above but now I get:
java.lang.NullPointerException: Cannot invoke "org.infinispan.commons.configuration.io.ConfigurationResourceResolver.resolveResource(String)" because "resourceResolver" is null
What am I missing?   In keycloak, where does that pom.xml file go?
Thanks
Mike

Keycloak: 20.0.3
To implement default "ec2" Infinispan stacks protocol you should:

Put these files in ./providers dir

"jgroups-aws-2.0.1.Final.jar" (stacks protocol)
"aws-java-sdk-core-1.12.410.jar" (access to AWS creds, etc.)
"aws-java-sdk-s3-1.12.410.jar" (access to S3, etc.)
"joda-time-2.12.2.jar" (is used)

JAVA_OPTS_APPEND='-Djgroups.s3.region_name=us-east-1 -Djgroups.s3.bucket_name=<backet_name>'

IAM profile role should be applied to EC2 instance (for AWS creds) and S3 bucket created

Build Keycloak with option "--cache-stack=ec2" (no --cache-config-file option!)

bin/kc.[sh|bat] build --cache-stack=ec2

By me it's working) GL& HF!
Logs:
2023-02-21 09:47:28,062 INFO  [org.infinispan.server.core.transport.EPollAvailable] (keycloak-cache-init) ISPN005028: Native Epoll transport not available, using NIO instead: java.lang.ExceptionInInitializerError
2023-02-21 09:47:28,453 WARN  [org.infinispan.CONFIG] (keycloak-cache-init) ISPN000569: Unable to persist Infinispan internal caches as no global state enabled
2023-02-21 09:47:28,472 WARN  [org.infinispan.PERSISTENCE] (keycloak-cache-init) ISPN000554: jboss-marshalling is deprecated and planned for removal
2023-02-21 09:47:28,506 INFO  [org.infinispan.CONTAINER] (keycloak-cache-init) ISPN000556: Starting user marshaller 'org.infinispan.jboss.marshalling.core.JBossUserMarshaller'
2023-02-21 09:47:28,987 INFO  [org.keycloak.broker.provider.AbstractIdentityProviderMapper] (main) Registering class org.keycloak.broker.provider.mappersync.ConfigSyncEventListener
2023-02-21 09:47:29,086 INFO  [org.infinispan.CONTAINER] (keycloak-cache-init) ISPN000128: Infinispan version: Infinispan 'Triskaidekaphobia' 13.0.10.Final
2023-02-21 09:47:29,270 INFO  [org.infinispan.CLUSTER] (keycloak-cache-init) ISPN000078: Starting JGroups channel `ISPN`
2023-02-21 09:47:29,290 WARN  [org.jgroups.stack.Configurator] (keycloak-cache-init) NATIVE_S3_PING has been deprecated; please upgrade to a newer version of the protocol
2023-02-21 09:47:30,181 INFO  [org.jgroups.aws.s3.NATIVE_S3_PING] (keycloak-cache-init) using Amazon S3 ping in region us-east-1 with bucket 'my-jgroups-s3-bucket-test' and prefix ''
2023-02-21 09:47:30,937 INFO  [org.jgroups.aws.s3.NATIVE_S3_PING] (keycloak-cache-init) found bucket my-jgroups-s3-bucket-test
2023-02-21 09:48:04,101 INFO  [org.infinispan.CLUSTER] (keycloak-cache-init) ISPN000094: Received new cluster view for channel ISPN: [ip-10-68-49-170-40943|3] (2) [ip-10-68-49-170-40943, ip-10-68-49-190-31671]
2023-02-21 09:48:04,111 INFO  [org.infinispan.CLUSTER] (keycloak-cache-init) ISPN000079: Channel `ISPN` local address is `ip-10-68-49-190-31671`, physical addresses are `[<IP_ADDRESS>:7800]`

2023-02-21 09:48:07,087 INFO  [io.quarkus] (main) Keycloak 20.0.3 on JVM (powered by Quarkus 2.13.6.Final) started in 78.156s. Listening on: http://<IP_ADDRESS>:8080 and https://<IP_ADDRESS>:8443
2023-02-21 09:48:07,087 INFO  [io.quarkus] (main) Profile prod activated.

@serhiiKalchenko I scoured the web and saw countless answers. Yours was the one which let me have Keycloak working with S3 discovery. Thank you so much. I'll probably edit this post soon with a full doc how to solve the full Keycloak distributed cache on Elastic Beanstalk EC2 Docker containers mystery.

Keycloak: 20.0.3 To implement default "ec2" Infinispan stacks protocol you should:

Put these files in ./providers dir

jgroups-aws-2.0.1.Final.jar (stacks protocol)
aws-java-sdk-core-1.12.410.jar (access to AWS creds, etc.)
aws-java-sdk-s3-1.12.410.jar (access to S3, etc.)
joda-time-2.12.2.jar (is used)

JAVA_OPTS_APPEND='-Djgroups.s3.region_name=us-east-1 -Djgroups.s3.bucket_name=<backet_name>'

IAM profile role should be applied to EC2 instance (for AWS creds) and S3 bucket created

Build Keycloak with option --cache-stack=ec2 (no --cache-config-file option!)

bin/kc.[sh|bat] build --cache-stack=ec2

By me it's working) GL & HF!
Logs:
2023-02-21 09:47:28,062 INFO  [org.infinispan.server.core.transport.EPollAvailable] (keycloak-cache-init) ISPN005028: Native Epoll transport not available, using NIO instead: java.lang.ExceptionInInitializerError
2023-02-21 09:47:28,453 WARN  [org.infinispan.CONFIG] (keycloak-cache-init) ISPN000569: Unable to persist Infinispan internal caches as no global state enabled
2023-02-21 09:47:28,472 WARN  [org.infinispan.PERSISTENCE] (keycloak-cache-init) ISPN000554: jboss-marshalling is deprecated and planned for removal
2023-02-21 09:47:28,506 INFO  [org.infinispan.CONTAINER] (keycloak-cache-init) ISPN000556: Starting user marshaller 'org.infinispan.jboss.marshalling.core.JBossUserMarshaller'
2023-02-21 09:47:28,987 INFO  [org.keycloak.broker.provider.AbstractIdentityProviderMapper] (main) Registering class org.keycloak.broker.provider.mappersync.ConfigSyncEventListener
2023-02-21 09:47:29,086 INFO  [org.infinispan.CONTAINER] (keycloak-cache-init) ISPN000128: Infinispan version: Infinispan 'Triskaidekaphobia' 13.0.10.Final
2023-02-21 09:47:29,270 INFO  [org.infinispan.CLUSTER] (keycloak-cache-init) ISPN000078: Starting JGroups channel `ISPN`
2023-02-21 09:47:29,290 WARN  [org.jgroups.stack.Configurator] (keycloak-cache-init) NATIVE_S3_PING has been deprecated; please upgrade to a newer version of the protocol
2023-02-21 09:47:30,181 INFO  [org.jgroups.aws.s3.NATIVE_S3_PING] (keycloak-cache-init) using Amazon S3 ping in region us-east-1 with bucket 'my-jgroups-s3-bucket-test' and prefix ''
2023-02-21 09:47:30,937 INFO  [org.jgroups.aws.s3.NATIVE_S3_PING] (keycloak-cache-init) found bucket my-jgroups-s3-bucket-test
2023-02-21 09:48:04,101 INFO  [org.infinispan.CLUSTER] (keycloak-cache-init) ISPN000094: Received new cluster view for channel ISPN: [ip-10-68-49-170-40943|3] (2) [ip-10-68-49-170-40943, ip-10-68-49-190-31671]
2023-02-21 09:48:04,111 INFO  [org.infinispan.CLUSTER] (keycloak-cache-init) ISPN000079: Channel `ISPN` local address is `ip-10-68-49-190-31671`, physical addresses are `[<IP_ADDRESS>:7800]`

2023-02-21 09:48:07,087 INFO  [io.quarkus] (main) Keycloak 20.0.3 on JVM (powered by Quarkus 2.13.6.Final) started in 78.156s. Listening on: http://<IP_ADDRESS>:8080 and https://<IP_ADDRESS>:8443
2023-02-21 09:48:07,087 INFO  [io.quarkus] (main) Profile prod activated.

What is the health check you've configured in Target Group?

@serhiiKalchenko I scoured the web and saw countless answers. Yours was the one which let me have Keycloak working with S3 discovery. Thank you so much. I'll probably edit this post soon with a full doc how to solve the full Keycloak distributed cache on Elastic Beanstalk EC2 Docker containers mystery.

Did you create a document on how to achieve it?

Indeed, thanks for the reminder!
I've written a blog article about putting Keycloak in production in our Beanstalk environment. Please let me know if it needs some more details! 🙂

Keycloak: 20.0.3 To implement default "ec2" Infinispan stacks protocol you should:

Put these files in ./providers dir

jgroups-aws-2.0.1.Final.jar (stacks protocol)
aws-java-sdk-core-1.12.410.jar (access to AWS creds, etc.)
aws-java-sdk-s3-1.12.410.jar (access to S3, etc.)
joda-time-2.12.2.jar (is used)

JAVA_OPTS_APPEND='-Djgroups.s3.region_name=us-east-1 -Djgroups.s3.bucket_name=<backet_name>'

IAM profile role should be applied to EC2 instance (for AWS creds) and S3 bucket created

Build Keycloak with option --cache-stack=ec2 (no --cache-config-file option!)

bin/kc.[sh|bat] build --cache-stack=ec2

By me it's working) GL & HF!
Logs:
2023-02-21 09:47:28,062 INFO  [org.infinispan.server.core.transport.EPollAvailable] (keycloak-cache-init) ISPN005028: Native Epoll transport not available, using NIO instead: java.lang.ExceptionInInitializerError
2023-02-21 09:47:28,453 WARN  [org.infinispan.CONFIG] (keycloak-cache-init) ISPN000569: Unable to persist Infinispan internal caches as no global state enabled
2023-02-21 09:47:28,472 WARN  [org.infinispan.PERSISTENCE] (keycloak-cache-init) ISPN000554: jboss-marshalling is deprecated and planned for removal
2023-02-21 09:47:28,506 INFO  [org.infinispan.CONTAINER] (keycloak-cache-init) ISPN000556: Starting user marshaller 'org.infinispan.jboss.marshalling.core.JBossUserMarshaller'
2023-02-21 09:47:28,987 INFO  [org.keycloak.broker.provider.AbstractIdentityProviderMapper] (main) Registering class org.keycloak.broker.provider.mappersync.ConfigSyncEventListener
2023-02-21 09:47:29,086 INFO  [org.infinispan.CONTAINER] (keycloak-cache-init) ISPN000128: Infinispan version: Infinispan 'Triskaidekaphobia' 13.0.10.Final
2023-02-21 09:47:29,270 INFO  [org.infinispan.CLUSTER] (keycloak-cache-init) ISPN000078: Starting JGroups channel `ISPN`
2023-02-21 09:47:29,290 WARN  [org.jgroups.stack.Configurator] (keycloak-cache-init) NATIVE_S3_PING has been deprecated; please upgrade to a newer version of the protocol
2023-02-21 09:47:30,181 INFO  [org.jgroups.aws.s3.NATIVE_S3_PING] (keycloak-cache-init) using Amazon S3 ping in region us-east-1 with bucket 'my-jgroups-s3-bucket-test' and prefix ''
2023-02-21 09:47:30,937 INFO  [org.jgroups.aws.s3.NATIVE_S3_PING] (keycloak-cache-init) found bucket my-jgroups-s3-bucket-test
2023-02-21 09:48:04,101 INFO  [org.infinispan.CLUSTER] (keycloak-cache-init) ISPN000094: Received new cluster view for channel ISPN: [ip-10-68-49-170-40943|3] (2) [ip-10-68-49-170-40943, ip-10-68-49-190-31671]
2023-02-21 09:48:04,111 INFO  [org.infinispan.CLUSTER] (keycloak-cache-init) ISPN000079: Channel `ISPN` local address is `ip-10-68-49-190-31671`, physical addresses are `[<IP_ADDRESS>:7800]`

2023-02-21 09:48:07,087 INFO  [io.quarkus] (main) Keycloak 20.0.3 on JVM (powered by Quarkus 2.13.6.Final) started in 78.156s. Listening on: http://<IP_ADDRESS>:8080 and https://<IP_ADDRESS>:8443
2023-02-21 09:48:07,087 INFO  [io.quarkus] (main) Profile prod activated.

Thank you so much for this answer. This is the only configuration that works. Although, I was trying to implement this with KC23 and using the latest versions of the jars that are available on maven. And it kept failing with NoSuchBucketException.
This is probably because of some breaking changes in the infinispan versions used between KC20 and 23. Has anyone got the latest version KC23 working with S3_PING?

Keycloak: 20.0.3 To implement default "ec2" Infinispan stacks protocol you should:

Put these files in ./providers dir

jgroups-aws-2.0.1.Final.jar (stacks protocol)
aws-java-sdk-core-1.12.410.jar (access to AWS creds, etc.)
aws-java-sdk-s3-1.12.410.jar (access to S3, etc.)
joda-time-2.12.2.jar (is used)

JAVA_OPTS_APPEND='-Djgroups.s3.region_name=us-east-1 -Djgroups.s3.bucket_name=<backet_name>'

IAM profile role should be applied to EC2 instance (for AWS creds) and S3 bucket created

Build Keycloak with option --cache-stack=ec2 (no --cache-config-file option!)

bin/kc.[sh|bat] build --cache-stack=ec2

By me it's working) GL & HF!
Logs:
2023-02-21 09:47:28,062 INFO  [org.infinispan.server.core.transport.EPollAvailable] (keycloak-cache-init) ISPN005028: Native Epoll transport not available, using NIO instead: java.lang.ExceptionInInitializerError
2023-02-21 09:47:28,453 WARN  [org.infinispan.CONFIG] (keycloak-cache-init) ISPN000569: Unable to persist Infinispan internal caches as no global state enabled
2023-02-21 09:47:28,472 WARN  [org.infinispan.PERSISTENCE] (keycloak-cache-init) ISPN000554: jboss-marshalling is deprecated and planned for removal
2023-02-21 09:47:28,506 INFO  [org.infinispan.CONTAINER] (keycloak-cache-init) ISPN000556: Starting user marshaller 'org.infinispan.jboss.marshalling.core.JBossUserMarshaller'
2023-02-21 09:47:28,987 INFO  [org.keycloak.broker.provider.AbstractIdentityProviderMapper] (main) Registering class org.keycloak.broker.provider.mappersync.ConfigSyncEventListener
2023-02-21 09:47:29,086 INFO  [org.infinispan.CONTAINER] (keycloak-cache-init) ISPN000128: Infinispan version: Infinispan 'Triskaidekaphobia' 13.0.10.Final
2023-02-21 09:47:29,270 INFO  [org.infinispan.CLUSTER] (keycloak-cache-init) ISPN000078: Starting JGroups channel `ISPN`
2023-02-21 09:47:29,290 WARN  [org.jgroups.stack.Configurator] (keycloak-cache-init) NATIVE_S3_PING has been deprecated; please upgrade to a newer version of the protocol
2023-02-21 09:47:30,181 INFO  [org.jgroups.aws.s3.NATIVE_S3_PING] (keycloak-cache-init) using Amazon S3 ping in region us-east-1 with bucket 'my-jgroups-s3-bucket-test' and prefix ''
2023-02-21 09:47:30,937 INFO  [org.jgroups.aws.s3.NATIVE_S3_PING] (keycloak-cache-init) found bucket my-jgroups-s3-bucket-test
2023-02-21 09:48:04,101 INFO  [org.infinispan.CLUSTER] (keycloak-cache-init) ISPN000094: Received new cluster view for channel ISPN: [ip-10-68-49-170-40943|3] (2) [ip-10-68-49-170-40943, ip-10-68-49-190-31671]
2023-02-21 09:48:04,111 INFO  [org.infinispan.CLUSTER] (keycloak-cache-init) ISPN000079: Channel `ISPN` local address is `ip-10-68-49-190-31671`, physical addresses are `[<IP_ADDRESS>:7800]`

2023-02-21 09:48:07,087 INFO  [io.quarkus] (main) Keycloak 20.0.3 on JVM (powered by Quarkus 2.13.6.Final) started in 78.156s. Listening on: http://<IP_ADDRESS>:8080 and https://<IP_ADDRESS>:8443
2023-02-21 09:48:07,087 INFO  [io.quarkus] (main) Profile prod activated.

Thank you so much for this answer. This is the only configuration that works. Although, I was trying to implement this with KC23 and using the latest versions of the jars that are available on maven. And it kept failing with NoSuchBucketException. This is probably because of some breaking changes in the infinispan versions used between KC20 and 23. Has anyone got the latest version KC23 working with S3_PING?

Yes I've got KC23 working with S3_PING

Hi @shkmaaz11 Thanks for the quick response. Would you mind sharing the dockerfile/providers used and the configuration/environment variables used.
I am trying to run it on EC2, so I how did you make the private IP's discoverable and also I am assuming that the IAM Instance Profile Role linked to the EC2 instance should be enough for the keycloak (running in a container) to be able to access S3.
Thanks.

Hi @shkmaaz11 Thanks for the quick response. Would you mind sharing the dockerfile/providers used and the configuration/environment variables used.
I am trying to run it on EC2, so how did you make the private IP's discoverable and also I am assuming that the IAM Instance Profile Role linked to the EC2 instance should be enough for the keycloak (running in a container) to be able to access S3.
Thanks.

Please go through this. I've documented it here https://medium.com/@maaz11/configuring-keycloak-with-s3-ping-protocol-on-aws-ecs-fargate-with-postgresql-rds-81aea8824dc6

@serhiiKalchenko Why can't you specify a custom cache configuration file? What should I do if i want to set number of owners of the distributedCaches to something different?