Forced vertical cut-off of a post ("see more / less")

After upgrade to the latest version, I've noticed a change on how AdaptiveCards are displayed.
Currently, we have implemented a custom AdaptiveCard with all the necessary info, but in order to fully view it you have to click "see more" button. It's a small, but impactful change to our workflow. As everything in that post is important and especially that all the action buttons are on the bottom of the AdaptiveCard.
Can you implement a setting for channel or user to set a view size behavior of "see more / less"? Instead of forcefully deciding what's cluttering and best for the user, let the user to decide what he wants in this case.
Screenshots:
See more:

See less:

Thank you for your time!
Microsoft Teams Version: <IP_ADDRESS>55 (64-bit)

Sure!

AdaptiveCard JSON:
{
	"Type": "message",
	"Summary": "[REDACTED]",
	"Attachments": [
		{
			"ContentType": "application/vnd.microsoft.card.adaptive",
			"Content": {
				"type": "AdaptiveCard",
				"version": "1.3",
				"body": [
					{
						"type": "Container",
						"items": [
							{
								"type": "TextBlock",
								"size": "extraLarge",
								"weight": "bolder",
								"color": "attention",
								"text": "[REDACTED]"
							}
						]
					},
					{
						"type": "Container",
						"items": [
							{
								"type": "ColumnSet",
								"columns": [
									{
										"type": "Column",
										"width": "90px",
										"items": [
											{
												"type": "TextBlock",
												"weight": "bolder",
												"text": "[REDACTED]"
											},
											{
												"type": "TextBlock",
												"weight": "bolder",
												"text": "[REDACTED]"
											},
											{
												"type": "TextBlock",
												"weight": "bolder",
												"text": "[REDACTED]"
											},
											{
												"type": "TextBlock",
												"weight": "bolder",
												"text": "[REDACTED]"
											},
											{
												"type": "TextBlock",
												"weight": "bolder",
												"text": "[REDACTED]"
											}
										]
									},
									{
										"type": "Column",
										"items": [
											{
												"type": "TextBlock",
												"text": "[REDACTED]"
											},
											{
												"type": "TextBlock",
												"text": "[REDACTED]"
											},
											{
												"type": "TextBlock",
												"text": "[REDACTED]"
											},
											{
												"type": "TextBlock",
												"text": "[REDACTED]"
											},
											{
												"type": "TextBlock",
												"text": "[REDACTED]"
											}
										]
									}
								]
							}
						],
						"separator": true
					},
					{
						"type": "Container",
						"items": [
							{
								"type": "ColumnSet",
								"columns": [
									{
										"type": "Column",
										"width": "90px",
										"items": [
											{
												"type": "TextBlock",
												"weight": "bolder",
												"text": "[REDACTED]"
											}
										]
									},
									{
										"type": "Column",
										"items": [
											{
												"type": "Container",
												"items": [
													{
														"type": "ColumnSet",
														"columns": [
															{
																"type": "Column",
																"items": [
																	{
																		"type": "TextBlock",
																		"text": "[REDACTED]",
																		"wrap": true
																	}
																]
															},
															{
																"type": "Column",
																"items": [
																	{
																		"type": "TextBlock",
																		"id": "[REDACTED]",
																		"color": "accent",
																		"text": "[REDACTED]"
																	},
																	{
																		"type": "TextBlock",
																		"id": "[REDACTED]",
																		"color": "accent",
																		"text": "[REDACTED]",
																		"isVisible": false
																	}
																],
																"selectAction": {
																	"type": "Action.ToggleVisibility",
																	"targetElements": [
																		"[REDACTED]",
																		"[REDACTED]",
																		"[REDACTED]"
																	]
																}
															}
														]
													},
													{
														"type": "Container",
														"id": "[REDACTED]",
														"items": [
															{
																"type": "TextBlock",
																"text": "[REDACTED]",
																"wrap": true
															},
															{
																"type": "TextBlock",
																"text": "[REDACTED]",
																"wrap": true
															}
														],
														"isVisible": false
													}
												]
											}
										]
									}
								]
							}
						]
					},
					{
						"type": "TextBlock",
						"text": "[REDACTED]",
						"wrap": true,
						"maxLines": 10
					}
				],
				"actions": [
					{
						"type": "Action.ShowCard",
						"card": {
							"type": "AdaptiveCard",
							"version": "1.3",
							"actions": [
								{
									"type": "Action.OpenUrl",
									"url": "[REDACTED]",
									"title": "[REDACTED]"
								},
								{
									"type": "Action.OpenUrl",
									"url": "[REDACTED]",
									"title": "[REDACTED]"
								},
								{
									"type": "Action.OpenUrl",
									"url": "[REDACTED]",
									"title": "[REDACTED]"
								},
								{
									"type": "Action.OpenUrl",
									"url": "[REDACTED]",
									"title": "[REDACTED]"
								},
								{
									"type": "Action.OpenUrl",
									"url": "[REDACTED]",
									"title": "[REDACTED]"
								},
								{
									"type": "Action.OpenUrl",
									"url": "[REDACTED]",
									"title": "[REDACTED]"
								}
							]
						},
						"title": "[REDACTED]"
					},
					{
						"type": "Action.OpenUrl",
						"url": "[REDACTED]",
						"title": "[REDACTED]"
					},
					{
						"type": "Action.ShowCard",
						"card": {
							"type": "AdaptiveCard",
							"version": "1.3",
							"actions": [
								{
									"type": "Action.OpenUrl",
									"url": "[REDACTED]",
									"title": "[REDACTED]"
								},
								{
									"type": "Action.OpenUrl",
									"url": "[REDACTED]",
									"title": "[REDACTED]"
								},
								{
									"type": "Action.OpenUrl",
									"url": "[REDACTED]",
									"title": "[REDACTED]"
								},
								{
									"type": "Action.OpenUrl",
									"url": "[REDACTED]",
									"title": "[REDACTED]"
								},
								{
									"type": "Action.OpenUrl",
									"url": "[REDACTED]",
									"title": "[REDACTED]"
								}
							]
						},
						"title": "[REDACTED]"
					},
					{
						"type": "Action.OpenUrl",
						"url": "[REDACTED]",
						"title": "[REDACTED]"
					}
				],
				"msteams": {
					"Width": "Full"
				}
			}
		}
	]
}

@grietine - Thank you for sharing the JSON, we are also able to repro this issue with new channel experience in Teams. We will check this internally and get back to you. Thank you.

@Meghana-MSFT Also want to say this "bug" is causing major frustrations for us as well. thnx

@CDSFounder - Apologies for the inconvenience caused. We have shared this feedback with team. We will keep you posted. Thank you.

@CDSFounder - Apologies for the inconvenience caused. We have shared this feedback with team. We will keep you posted. Thank you.

What is the status / response from your team?

Unfortunately, we do not have any update to share. Thank you for your understanding.

Can we vote anywhere to make this issue a priority?
This is a major concern for us as well

Unfortunately, there is no such option. We are following up with the team internally. We will keep you posted. Thank you.

Fix has been made to this issue. But it hasn't reached the public rings yet. We will keep you posted.

@Meghana-MSFT my company is suffering from this affliction as well. Is there any kind of timeline for a fix?

This is affecting us and our customers as well. Any updates on this?

@Meghana-MSFT  Any update on publishing the fix? This is very disappointing to our users. I read above that the fix was made but not published yet.

@Meghana-MSFT our company is also affected by this, would be nice to have this fix ASAP, since it is disrupting our workflow a lot.

Apologies for the inconvenience caused to you. Fix is going to rollout in few weeks, but we don't have any exact ETA to share.

Apologies for the inconvenience caused to you. Fix is going to rollout in few weeks, but we don't have any exact ETA to share.

Any updates on when Microsoft will rollout the fix?

Same issue here, very frustrating. Any ETA for the fix?

This issue is fixed in new Teams T2.1. As you can see in below screenshot, see more/less button is removed.

Teams T2.1 is the new version of Teams. We tested in below version of Teams.

@Meghana-MSFT What about the teams web app? As a linux user i only use Teams in the Browser and i don't see the issue fixed there.

@co-sic - This issue is fixed in web client as well in the new version of Teams. Please find the version details in below screenshot.
Version details:

No see more/less button:

@Meghana-MSFT I am still seeing the issue in the version screenshotted below.

I’m on a PC

@Meghana-MSFT I am still seeing the issue in the version screenshotted below.

Same problem here. Same version of Teams. Also web version still exhibits the problem. macOS Sonoma 14.1.2

We will check internally and get back to you.

Still not working. Not on the desktop client - latest version. Not on the web client. And you never got back to us.

Please note that the fix was done for adaptive cards and the original issue in this thread is also reported for adaptive cards. If you are still facing the issue with adaptive cards, then please share the card payload using the fiddler trace so that we can confirm that the Teams client is indeed getting the 'Adaptive card' type and then we can proceed from there.
Please follow these steps -

Have Fiddler running/capturing network traces.
Like the message that contains the card:

After you've liked the message, stop capturing and find the following in the traces:

4.Drag the network request to the Composer tab, and remove the "like" reaction from the Request Body. Remove /properties?name=emotions&replace=true from the request URL (it's at the very end), and change the method from PUT to GET. You should end up with something like this:

Click Execute.
Click on the new Request that pops up and decode the response.
Go to TextView and you'll see the following:
For Message Extension Card:

For Bot Cards

For Bot Cards, you will need to decode the b64 object using some site like this: https://www.base64decode.org/ . Copy everything besides the quotes of the value assigned with the Swift b64 and pasted it in the decoder. You should get something like this:

This is a response going through the steps above from a card from our Azure DevOps integration that is still showing "see more":
{"sequenceId":29913,"conversationid":"19:de8dda2a58934e37ba460187e9abed3a@thread.tacv2","conversationLink":"https://amer.ng.msg.teams.microsoft.com/v1/users/ME/conversations/19:de8dda2a58934e37ba460187e9abed3a@thread.tacv2","contenttype":"text","type":"Message","s2spartnername":"SMBA","annotationsSummary":{},"hasAnnotated":true,"id":"1707935024139","clientmessageid":"1707935024003","version":"1707935414485","messagetype":"RichText/Media_Card","content":"<URIObject type="SWIFT.1" url_thumbnail="https://urlp.asm.skype.com/v1/url/content?url=https://neu1-urlp.secure.skypeassets.com/static/card-128x128.png\">Build 20240214.6 - succeededBuild 20240214.6 - succeeded<Swift b64="eyJ0eXBlIjoibWVzc2FnZSIsInN1bW1hcnkiOiJCdWlsZCAyMDI0MDIxNC42IC0gc3VjY2VlZGVkIiwidGV4dEZvcm1hdCI6Im1hcmtkb3duIiwiYXR0YWNobWVudHMiOlt7ImNvbnRlbnQiOnsic3VtbWFyeSI6IkJ1aWxkIDIwMjQwMjE0LjYgLSBzdWNjZWVkZWQiLCJ0aGVtZUNvbG9yIjoiIzEwN2MxMCIsInNlY3Rpb25zIjpbeyJ0ZXh0IjoiPHA+QnVpbGQgZm9yIDxpbWcgc3JjPVwiaHR0cHM6Ly91cy1wcm9kLmFzeW5jZ3cudGVhbXMubWljcm9zb2Z0LmNvbS91cmxwL3YxL3VybC9jb250ZW50P3VybD1odHRwcyUzYSUyZiUyZmNkbi52c2Fzc2V0cy5pbyUyZmNvbnRlbnQlMmZub3RpZmljYXRpb25zJTJmdGVhbXMtcHVzaHJlcG8ucG5nXCIgYWx0PVwiUmVwbyBJY29uXCI+IDxhPjwvYT4gPGltZyBzcmM9XCJodHRwczovL3VzLXByb2QuYXN5bmNndy50ZWFtcy5taWNyb3NvZnQuY29tL3VybHAvdjEvdXJsL2NvbnRlbnQ/dXJsPWh0dHBzJTNhJTJmJTJmY2RuLnZzYXNzZXRzLmlvJTJmY29udGVudCUyZm5vdGlmaWNhdGlvbnMlMmZ0ZWFtcy1icmFuY2gucG5nXCIgYWx0PVwiQnJhbmNoIEljb25cIj4gPGEgaHJlZj1cIi8jdmVyc2lvbj1HQm1haW5cIj5tYWluPC9hPiwgZmluaXNoZWQgMDIvMTQvMjAyNCAxODoyMzozMCBVVEM8L3A+IiwiYWN0aXZpdHlUaXRsZSI6IjxwPjxhIGhyZWY9XCJodHRwczovL2Rldi5henVyZS5jb20vaXRhcC1pbmZvcm1hdGljcy1henVyZS82MDlhOTU3Ni1kYjM2LTQyZmUtYjJmYS02MWI2OGE4MDg3ZTAvX2J1aWxkL3Jlc3VsdHM/YnVpbGRJZD0xMzY3N1wiPkRFViBSZWxlYXNlIC8gMjAyNDAyMTQuNjwvYT4gKFN1Y2NlZWRlZCk8L3A+IiwiYWN0aXZpdHlTdWJ0aXRsZSI6IjxwPlRyaWdnZXI6IG1hbnVhbCBmb3IgV2lsbCBHcmF1dm9nZWw8L3A+IiwiYWN0aXZpdHlJbWFnZSI6Imh0dHBzOi8vdXMtcHJvZC5hc3luY2d3LnRlYW1zLm1pY3Jvc29mdC5jb20vdXJscC92MS91cmwvY29udGVudD91cmw9aHR0cHMlM2ElMmYlMmZjZG4udnNhc3NldHMuaW8lMmZjb250ZW50JTJmbm90aWZpY2F0aW9ucyUyZnRlYW1zLWJ1aWxkLXN1Y2NlZWRlZC5wbmciLCJhY3Rpdml0eUltYWdlVHlwZSI6ImFydGljbGUiLCJtYXJrZG93biI6dHJ1ZSwic3RhcnRHcm91cCI6ZmFsc2V9XSwicG90ZW50aWFsQWN0aW9uIjpbXX0sImNvbnRlbnRUeXBlIjoiYXBwbGljYXRpb24vdm5kLm1pY3Jvc29mdC50ZWFtcy5jYXJkLm8zNjVjb25uZWN0b3IifV19" />","from":"https://amer.ng.msg.teams.microsoft.com/v1/users/ME/contacts/28:integration:bxi61rx48u","fromTenantId":"4130bd39-7c53-419c-b1e5-8758d6d63f21","imdisplayname":"Azure DevOps","composetime":"2024-02-14T18:23:44.1390000Z","originalarrivaltime":"2024-02-14T18:23:44.1390000Z","properties":{"meta":"{"connectorSenderGuid":"dd63c2fc-4ea3-491a-9e74-fcc31f346478","providerAccountUniqueId":"ddadc0c6-be28-601f-b39d-40a1dda7e279","connectorConfigurationAlternateId":"496c81a294b94bfd87832bbc1c8a9095"}","s2spartnername":"SMBA","emotions":[{"key":"like","users":[]}]}}%
And decoding the Base64 data:
{"type":"message","summary":"Build 20240214.6 - succeeded","textFormat":"markdown","attachments":[{"content":{"summary":"Build 20240214.6 - succeeded","themeColor":"#107c10","sections":[{"text":"Build for    main, finished 02/14/2024 18:23:30 UTC","activityTitle":"DEV Release / 20240214.6 (Succeeded)","activitySubtitle":"Trigger: manual for Will Grauvogel","activityImage":"https://us-prod.asyncgw.teams.microsoft.com/urlp/v1/url/content?url=https%3A%2F%2Fcdn.vsassets.io%2Fcontent%2Fnotifications%2Fteams-build-succeeded.png","activityImageType":"article","markdown":true,"startGroup":false}],"potentialAction":[]},"contentType":"application/vnd.microsoft.teams.card.o365connector"}]}%

As we can see from the payload (see the contentType value at the end) it's a o365connector card as suspected and not an Adaptive card which is why you're seeing the 'see more'. Anyway, even for O365 connector cards, compared to Teams classic, the card was being truncated at much shorter height in latest Teams so, engineering team has pushed a change to bring parity with classic Teams and based on Teams releases, looks like that change will take some time to reach the general ring.

We are no longer able to avoid leaving Teams Classic and now are gravely afflicted by this for many integrations.  It's near crippling with respect to something that used to be so seamless and useful
Version 24004.1304.2655.7488 (24004.1304.2655.7488)
When we set up our Integrations we started trying to use Adaptive Cards, but were unable and had to use https://learn.microsoft.com/en-us/outlook/actionable-messages/message-card-reference for Jira -> Teams Connector Webhooks Cards and for Webhooks sent directly from CI/CD Code
Please do one or all of the following:

If these Legacy Message Cards are different from o365connector cards, please add Legacy Message Card as another case that needs to be addressed
Please suggest an alternative relief.  I'm not sure if we could get off Legacy Message Cards but if you could suggest how it would be welcomed

It so discouraging having something so useful working and an escape like this ruin it

The initial comment on this thread highlights a broader concern.
Rather than imposing clutter and making unilateral decisions on behalf of users, could you instead implement configuration options to customize the display size and behavior of the 'see more/less' feature?
This has crippled our integrations and general experience with Teams.

@Meghana-MSFT
Please provide an update on when this issue might be solved in all the venues it remains broken.  I was able to review to Teams Classic for awhile but now that option has been taken from me.
This is so painful for something that worked so seemlessly.

Same issue. You just broke an app that we took months to build. You seriously degraded the user experience for us. New ms teams is not fixed....


Add Hover on Submit

Hey !!
I would like to add one feature in this already beautiful looking website, i wanted to add the hovering effect on the submit button in the contact section .

assign me this work @Priyaaa1 #326


[Flake] push reports invalid configuration

[kind/bug]

What versions of software are you using?

On OpenShift CI
Actual behavior
Error out
Expected behavior
Should pass
Any logs, error output, etc?
odo sub component command tests when component is in the current directory and --project flag is used
  creates and pushes local nodejs component and then deletes --all
  /go/src/github.com/openshift/odo/tests/integration/component.go:329
 Created dir: /tmp/724815433
Creating a new project: texjxuxufc
Running odo with args [odo project create texjxuxufc -w -v4]
[odo] I0904 13:18:24.552396   19818 preference.go:118] The path for preference file is /tmp/724815433/config.yaml
[odo] I0904 13:18:24.552472   19818 occlient.go:479] Trying to connect to server api.ci-op-d1whffy3-f09f4.origin-ci-int-aws.dev.rhcloud.com:6443
[odo] I0904 13:18:24.567450   19818 occlient.go:486] Server https://api.ci-op-d1whffy3-f09f4.origin-ci-int-aws.dev.rhcloud.com:6443 is up
[odo] I0904 13:18:24.631580   19818 occlient.go:409] isLoggedIn err:  <nil>
[odo]  output: "developer"
[odo]  •  Waiting for project to come up  ...
[odo]  ✓  Waiting for project to come up [353ms]
[odo]  ✓  Project 'texjxuxufc' is ready for use
[odo]  ✓  New project created and now using project : texjxuxufc
[odo] I0904 13:18:25.006691   19818 odo.go:70] Could not get the latest release information in time. Never mind, exiting gracefully :)
Current working dir: /go/src/github.com/openshift/odo/tests/integration
Setting current dir to: /tmp/724815433
Running odo with args [odo component create nodejs my-component --app app --project texjxuxufc --env key=value,key1=value1]
[odo]  •  Validating component  ...
[odo]  ✓  Validating component [37ms]
[odo] Please use `odo push` command to create the component with source deployed

[odo]
Running odo with args [odo component push --context /tmp/724815433]
[odo]  ✗  invalid configuration: [context was not found for specified context: jgjryhzmbp/api-ci-op-d1whffy3-f09f4-origin-ci-int-aws-dev-rhcloud-com:6443/developer, cluster has no server defined]
[odo] Please login to your server:
[odo]
[odo] odo login https://mycluster.mydomain.com

[odo]
Setting current dir to: /go/src/github.com/openshift/odo/tests/integration
Deleting project: texjxuxufc
Running odo with args [odo project delete texjxuxufc -f]
[odo]  •  Deleting project texjxuxufc  ...
[odo]  ✓  Deleting project texjxuxufc [5s]
[odo]  ✓  Deleted project : texjxuxufc
Deleting dir: /tmp/724815433
 • Failure [6.659 seconds]
odo sub component command tests
/go/src/github.com/openshift/odo/tests/integration/cmd_cmp_sub_test.go:13
  when component is in the current directory and --project flag is used
  /go/src/github.com/openshift/odo/tests/integration/component.go:306
    creates and pushes local nodejs component and then deletes --all [It]
    /go/src/github.com/openshift/odo/tests/integration/component.go:329
     No future change is possible.  Bailing out early after 0.102s.

    Running odo with args [odo component push --context /tmp/724815433]
    Expected
        <int>: 1
    to match exit code:
        <int>: 0
     /go/src/github.com/openshift/odo/tests/helper/helper_run.go:32

one more similar failure in travis job - https://travis-ci.com/openshift/odo/jobs/231580215#L2435
odo component command tests Creating Component even in new project

  should create component

  /home/travis/gopath/src/github.com/openshift/odo/tests/integration/component.go:264

Created dir: /tmp/573029857

Running odo with args [odo create nodejs cmp-git --git https://github.com/openshift/nodejs-ex --project vplsuceubh --context /tmp/573029857 --app testing]

[odo]  •  Validating component  ...

[odo]  ✓  Validating component [7ms]

[odo] Please use `odo push` command to create the component with source deployed

Running odo with args [odo push --context /tmp/573029857 -v4]

[odo] I0905 19:51:34.186768   32748 common_push.go:127] SourceLocation: https://github.com/openshift/nodejs-ex

[odo] I0905 19:51:34.186892   32748 config.go:642] Git source type detected, not correcting SourcePath location

[odo] I0905 19:51:34.187029   32748 common_push.go:135] Source Path: https://github.com/openshift/nodejs-ex

[odo] I0905 19:51:34.188492   32748 cmdutils.go:48] Error:

[odo] invalid configuration: no configuration has been provided

[odo] Please login to your server:

[odo]

[odo] odo login https://mycluster.mydomain.com

[odo]  ✗  invalid configuration: no configuration has been provided

[odo] Please login to your server:

[odo]

[odo] odo login https://mycluster.mydomain.com

[odo]

Deleting project: vplsuceubh

Running odo with args [odo project delete vplsuceubh -f]

[odo]  ✗  The project vplsuceubh does not exist. Please check the list of projects using `odo project list`

Deleting dir: /tmp/573029857

• Failure [1.578 seconds]

odo component command tests

/home/travis/gopath/src/github.com/openshift/odo/tests/integration/cmd_cmp_test.go:13

  Creating Component even in new project

  /home/travis/gopath/src/github.com/openshift/odo/tests/integration/component.go:255

    should create component [It]

    /home/travis/gopath/src/github.com/openshift/odo/tests/integration/component.go:264

    No future change is possible.  Bailing out early after 0.757s.

    Running odo with args [odo push --context /tmp/573029857 -v4]

    Expected

        <int>: 1

    to match exit code:

        <int>: 0

    /home/travis/gopath/src/github.com/openshift/odo/tests/helper/helper_run.go:32

same flake - https://travis-ci.com/openshift/odo/jobs/233878023#L714

One more - https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/pr-logs/pull/openshift_odo/2128/pull-ci-openshift-odo-master-v4.1-integration/119

Day by day the flake frequency is growing
one more - https://travis-ci.com/openshift/odo/jobs/236911619#L735

one more - https://travis-ci.com/openshift/odo/jobs/238431066#L2444

Recent occurrence - https://travis-ci.com/github/openshift/odo/jobs/319873569

/remove-lifecycle stale

Total we have 8 occurrence till date since the issue has been created.

Count 9 - https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/pr-logs/pull/openshift_odo/2880/pull-ci-openshift-odo-master-v4.2-integration-e2e-benchmark/1959
Hit the similar issue but this time in component create level. Previously we were hitting the issue at push level.
The cluster server it logins is ````api.ci-op-0v6lz496-18180.origin-ci-int-aws.dev.rhcloud.com:6443but sometimes in duration of test run it looks for serverapi.ci-op-0v6lz496-18180.origin-ci-int-aws.dev.rhcloud.com:6443``` causing below mentioned failure logs
 Running odo with args [odo component create nodejs cmp-git --git https://github.com/openshift/nodejs-ex --project lzulkwdlcz --context /tmp/544511353 --app testing]
[odo]  ✗  invalid configuration: [context was not found for specified context: exsnqqfono/api-ci-op-0v6lz496-18180-origin-ci-int-aws-dev-rhcloud-com:6443/developer, cluster has no server defined]
[odo] Please login to your server:
[odo]
[odo] odo login https://mycluster.mydomain.com
[odo]
Deleting project: lzulkwdlcz
Running odo with args [odo project delete lzulkwdlcz -f]
[odo]  •  Deleting project lzulkwdlcz  ...
[odo]

I am not sure if it could be a glitch from CI side. @mohammedzee1000 Can you please share your thoughts if any

one more hit in https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/pr-logs/pull/openshift_odo/2925/pull-ci-openshift-odo-master-v4.3-integration-e2e-benchmark/2226#1:build-log.txt%3A395

Hitting the same issue in one of our periodic job - https://deck-ci.apps.ci.l2s4.p1.openshiftapps.com/view/gcs/origin-ci-test/logs/periodic-ci-openshift-odo-master-v4.5-integration-e2e-periodic/1275489038496698368
It see the KUBECONFIG path was misplaced somehow in the spec teardown steps. It will be tracked and fixed through the issue https://github.com/openshift/odo/issues/3337.

I am easily able to reproduce it but the error what CI is hitting is completely different.
To reproduce it locally you just need to set the KUBECONFIG to some unknown path then try odo command. For example
Running odo with args [odo project delete mzlihqtelf -f]
[odo] W0815 18:53:38.757434   19642 loader.go:223] Config not found: /no/such/path
[odo]  ✗  invalid configuration: no configuration has been provided
[odo] Please login to your server:
[odo]
[odo] odo login https://mycluster.mydomain.com
[odo]

But in CI both travis and prow the the error is different
prow
[odo]  ✗  invalid configuration: [context was not found for specified context: exsnqqfono/api-ci-op-0v6lz496-
18180-origin-ci-int-aws-dev-rhcloud-com:6443/developer, cluster has no server defined]

travis
[odo] I0905 19:51:34.188492   32748 cmdutils.go:48] Error:
[odo] invalid configuration: no configuration has been provided

Right now each spec in the test suite is referring to the correct KUBECONFIG path. I am not sure if this is happening wrong from the cluster level.


Add Observation RPC call metrics to ZetaClientd

Is your feature request related to a problem? Please describe.
It is difficult to gain insight in to zetaclient observer RPC calls without clear metrics per method and chain.
Describe the solution you'd like
We would like to see additional metrics exposed for RPC call success/failure, and latency. Ideally failures and latency would be tracked by method and chain.
Describe alternatives you've considered
We have considered

Dropping a local nginx proxy in the middle to capture calls placed by Zetaclient.
Modifying the upstream RPC load balancer to capture and expose these metrics upstream

Motivation and Context
With metrics of individual RPC calls exposed, we will be better equipped to diagnose potential odd behavior related to observation, and isolate the issue to a specific observer's RPC call.

Related to https://github.com/zeta-chain/node/issues/1524

BTC RPC metrics blocked by https://github.com/btcsuite/btcd/issues/1547


Add support for scrollwheel clicks

Since scroll wheel actions are just a click with another mouse button code, it should be trivial to add a ScrollUp and ScrollDown to the MouseButton enum that translate to the appropriate code in the MouseButton::to_number method.

Sorry, I'm not actively maintaining this because I don't use i3/sway anymore, as you can see the last commit was in 2017.
But I can merge patches or add you as a collaborator on the repo :)

I'd be more than happy to contribute to the project, it's right down my alley and makes my life much easier :)

Fixed in 845363d.


Cannot erase input value through mask symbols (Android 4.4, Android 4.2)

There is a problem was reproduced under several devices

Android Chrome, Android 4.2
Default browser, Android 4.4(either reproduced under genymotion emulator model motorola moto x)

All cases was reproduced only with Android default keyboard(!!!!)
Test case:
$("#field").inputmask({"mask": "+7(999)-999-999-99"});
Input 123456.
Got +7(123)-456-_-
Try to erase text with <- button(backspace)
ER: text was erased
AR: cannot erase through '-' symbol. But if u put caret between '5' and '6', u can erase 4 and 5 with backspace.
Root cause is android problem, like http://stackoverflow.com/questions/22503559/backspace-not-firing-the-keyup-event-in-android-mobile
no keydown/keyup event fires with backspace pressing, only input event.
Is there any workaround for inputmask?

@Enfree ,
Can you try with the latest which has a fix for this.

@RobinHerbots
Well, current problem is not reproduced, but now mask symbols can be deleted with backspace, actually i can clear input field and input whetever i want.
TC: +7(999)-999-999-999 mask
input: 123456,
result: +7(123)-456--
Start erasing with backspace, got
+7(123)-456--
+7(123)-456___-___
+7(123)-45___-___
+7(123)-4___-___
....
-
Besides i can input every symbols:
aaaaa___-___
After onblur:
+7(123)-456--

@Enfree ,
Hmm I cannot reproduce this.  I tested on Android 4.2.2 and latest Chrome

@RobinHerbots
i tested on android 4.4 default browser, ill try under 4.2 chrome

@Enfree ,
I just committed a little fix which might help

@RobinHerbots
so strange. Did you use AOSP keyboard? I can reproduce under 4.2 chrome either.
I'll try new fix.

ok. at first backspace it doesen't trigger, but if you need to have 2 or 3 backspaces, it will continue to do it.

Im doing a Regex with the inputmask, it works but it still has bugs when your in the middle of a string (mine uses spaces) and hit backspace. It looks like it jumps back to its original position (where the bug happens) when your select a different position with the mouse onclick.
Would greatly appreciate the effort ty!


supporting mounting proc with namespaces

Can you make this into a specific feature test, so we can disable it in older versions of Linux where this is not supported?

Do you mean an arg passed to the userchroot program (like --install-devices) or a build time -D flag?

Actually the current implementation using unshare, will require kernel version 3.8 or higher. Providing the CLONE_NEWPID flag to unshare is supported in 3.8+ per the documentation (http://man7.org/linux/man-pages/man2/unshare.2.html)
I'm going to switch to using clone instead of unshare + fork because the CLONE_NEWPID support in clone() requires 2.6.24+

hmm... I was expecting us to mount /proc on the --install-devices command and unmount on the --uninstall-devices. But maybe if we mount it in the namespace it goes away as that process exits?

After reading a bit more, I think you're right, the mount will just go away as the process leaves and the namespace disappears.

One more thing, I think you should accept /proc to already exist, since more than one userchroot invocation could be made on the the same directory.

The code accepts having a /proc directory and it'll mount the new /proc over the old one. You don't mean that they can exist at the same time in the same chroot directory right?

I meant the mkdir call that aborts everything if it fails...

it won't abort if the directory already exists. I check for EEXIST != errno

ah, sorry, I missed that.

Any updates?


[DOC] User doc tools should be clear about --filter_apps and also --filter-criteria

Report incorrect documentation
Location of incorrect documentation
https://docs.nvidia.com/spark-rapids/user-guide/latest/qualification/quickstart.html#command-options
https://docs.nvidia.com/spark-rapids/user-guide/latest/qualification/jar-usage.html#deploying-tools-jar
Describe the problems or issues found in the documentation
Python version has an option --filter_apps, -f.
Jar version has another option -f, --filter-criteria  <arg>
In fact, we can use jar version's option --filter-criteria in the python tool command line.
We need to document it clearly that:
a. In python tool's doc, what does -f mean? --filter_apps or --filter-criteria.
b. In python tool's doc, can you give an example of both --filter_apps and --filter-criteria are used?

Thanks @viadea !
Can I use --filter-criteria with the Python CLI cmd?
Actually, The python CLI allows argument forwarding to the Jar cmd.
This is a feature that was hidden from the documentation based on the request of the product owners. I believe their intuition is to keep the documentation simple and keep this extra argument from internal usage only.
If you run spark_rapids qualification -- --help there will be in the last line
    Additional flags are accepted.
        A list of valid Qualification tool options. Note that the wrapper ignores ["output-directory", "platform"] flags, and it does not support multiple "spark-property" arguments. For more details on Qualification tool options, please visit https://docs.nvidia.com/spark-rapids/user-guide/latest/qualification/jar-usage.html#running-the-qualification-tool-standalone-on-spark-event-logs

For Example, in the python CLI, you can use --filter_criteria to be forwarded to the Jar cmd (note that the hyphen is becoming underscore)...
spark_rapids qualification   \
             --cluster $CPU_CLUSTER_PROPS   \
             --output_folder $LOCAL_OUTPUT_DIR   \
             --eventlogs $LOCAL_CPU_EVENT_LOGS   \
             --tools_jar $LOCAL_JAR   \
             --estimation_model XGBOOST   \
             --verbose \
             --filter_criteria 1-newest-filesystem

Then in the stdout, you can find that the python is passing --filter-criteria to the JAR cmd.
What is filter_apps?
This argument filters the results displayed in the STDOUT of the Python CLI.
filter_apps was a feature requested by the product owners to filter the results summary of the python STDOUT. For example, by default the STDOUT shows the applications from the TCL.
Users interested in Cost-savings can override the behavior to show all the applications that can achieve a GPU cost savings.
Users also can override that behavior to list all the applications (even with negative cost-savings/ or no speedups).
In summary, I doubt users are interested in this argument because everyone is consuming the CSV files. Mainly, it is used internally by our devs for Demo purposes.
Finally, the "SPEEDUPS" value will be dropped in the future because we are moving away from the legacy speedup.
   -f, --filter_apps=FILTER_APPS
        Type: Optional[str]
        Default: None
        filtering criteria of the applications listed in the final STDOUT table is one of the following (ALL, SPEEDUPS, SAVINGS, TOP_CANDIDATES). Requires "Cluster".

        Note that this filter does not affect the CSV report. "ALL" means no filter applied. "SPEEDUPS" lists all the apps that are either 'Recommended', or 'Strongly Recommended' based on speedups. "SAVINGS" lists all the apps that have positive estimated GPU savings except for the apps that are "Not Applicable". "TOP_CANDIDATES" lists all apps that have unsupported operators stage duration less than 25% of app duration and speedups greater than 1.3x.

I agree with you that the two names are confusing.
We can consider one of them to avoid confusion.


Error communicating with OpenAI

Getting Error as below. Translate was stopped.
"Rate limit reached for default-gpt-3.5-turbo in organization org-deKP3GRnO0RcmJUoQ0jfkGsG on requests per min. Limit: 20
/ min. Current: 30 / min. Contact<EMAIL_ADDRESS>if you continue to have issues. Please add a payment method to your
account to increase your rate limit. Visit https://platform.openai.com/account/billing to add a payment method. will
sleep  60 seconds
Error communicating with OpenAI: HTTPSConnectionPool(host='api.openai.com', port=443): Max retries exceeded with url:
/v1/chat/completions (Caused by ProxyError('Cannot connect to proxy.', ConnectionResetError(10054, 'An existing
connection was forcibly closed by the remote host', None, 10054, None)))
you can resume it next time"

Feishu is calling ChatGPT API well.

Use —api_base

I've just tried on Google Colab. There is the similar error.
"Rate limit reached for default-gpt-3.5-turbo in organization
org-deKP3GRnO0RcmJUoQ0jfkGsG on requests per min. Limit: 20 / min. Current: 30 /
min. Contact<EMAIL_ADDRESS>if you continue to have issues. Please add a
payment method to your account to increase your rate limit. Visit
https://platform.openai.com/account/billing to add a payment method.
you can resume it next time
0% 0/1068 [01:12<?, ?it/s]"

Use —api_base

How to use --api_base?

I'm trying --api_base "https://api.openai.com/v1". Waiting for the result.

@Hinkerliu H
same as https://github.com/yihong0618/xiaogpt/issues/74


Node sizes change after resolving errors

I think we lose the actual node sizes when we resolve errors. This can be seen in sample 2, just resolve errors, download SBGNML file and open it in Newt. All non-compound node sizes are 30 by 30.

@ugurdogrusoz @hasanbalci it works correct now. It occurs due to processing the process nodes before validation and solved by adding one if statement for resolve part.

Node size issue looks solved, thanks! Another small issue I noticed: The below image is after resolving errors in Sample 2. Should we move the process outside into the compartment on the left? Actually if I download the SBGNML file and open it in Newt, I see that process node is inside the compartment. It seems that the file and image aren't consistent after we resolve the errors.

Also in same sample, I realized that there is an inconsistency in Error 2. There is a fix explanation but it seems unfixed. And label shows "(2)", but I cannot see any such label in the image.

Node size issue looks solved, thanks! Another small issue I noticed: The below image is after resolving errors in Sample 2. Should we move the process outside into the compartment on the left? Actually if I download the SBGNML file and open it in Newt, I see that process node is inside the compartment. It seems that the file and image aren't consistent after we resolve the errors.

@hasanbalci  I think is is related to Newt, not related to Sybvals. Try following steps,
first load sample 2 do validation and resolve, then download the sbgn file.
Then upload it to both sybvals and newt, corresponding maps are different but.
Content of the sbgn file is changed in newt. There is no compartment ref related to process node you mentioned, but it in newt, it is compartment referenced.

@YusufZiyaOzgul Newt also applies a postprocessing for process nodes while loading the file, so it may not be a good place to test this issue. But if you check the content of the file downloaded from Sybvals after error fixing, you can see that there are 2 processes, 1 uncertain process and 2 association nodes without compartment references. You can also see that when you upload it to Syblars which doesn't apply any postprocessing on process nodes.

This seems resolved.


Fix crash in abi builder on unknown type with short name

What was wrong?
The abi builder crashed on an unknown type (with a short name) in a function signature. Eg:
contract F:
  pub def f(x: foo) -> bool:
    return true

This presumably should have been caught by the analyzer; I haven't looked into how it slipped through the cracks.
How was it fixed?
changed if &base[..6] == "string" to if base.starts_with("string"). Other similar tests all use starts_with already, btw.
To-Do

[ ] OPTIONAL: Update Spec if applicable

[ ] Add entry to the release notes (may forgo for trivial changes)

[ ] Clean up commit history

Oh, this resolves #213. I happened upon it when I misspelled u256 uint.

Oh, this resolves #213. I happened upon it when I misspelled u256 uint.


problem updating Oh My Zsh

Hello,
I have a problem... in Root, I have no problem for install update oh my zsh but...
with non root mode oh my zsh not functionnal...
$ > upgrade_oh_my_zsh
Updating Oh My Zsh
Cannot pull with rebase: You have unstaged changes.
Please commit or stash them.
There was an error updating. Try again later?

I use Agnoster theme.
What should I do?

Did you modify any file except your .zshrc ?

You must have modified some file in oh-my-zsh. Go to your oh-my-zsh folder and run:
git status
git diff

Quick fix is to go cd ~/.oh-my-zsh and git stash, then retry upgrade_oh_my_zsh

@jondeaton it works for me thanks!!

It was a change in the folder indeed.
If anyone wants the changes to be back after the upgrade, like in my case where I stored a Theme, all you have to do is:
cd ./.oh-my-zsh     # zsh Source Folder
git stash                # Stores all the changes you've made and reverses to the previous commit
upgrade_oh_my_zsh    # Updates the zsh client
git pop                   # Pops in the folder the previous changes you've made

Although, I would suggest the themes to not be changed in the zsh folder. If not everyone, most people use a theme and it's somewhat impractical to do this process every time.


Add HTML reference

I have added an HTML, well-designed reference. It's the CSS visual guide's counterpart.

We already have MDN, and it doesn't look like this adds anything more so I'm going to leave this off. Thanks for the PR tho!


Cilium pods missing ressources in cluster roles

Bug report
While installing a Kubernetes cluster I instrucked Kubespray to deploy Cilium 1.7.1.
When installation ended, all cilium pods were in crashCoopbackOff.
cilium-4xrlg                            0/1     CrashLoopBackOff    12         43m
cilium-6mk2t                            0/1     CrashLoopBackOff    12         43m
cilium-6rt7q                            0/1     CrashLoopBackOff    12         43m
cilium-72cq9                            0/1     CrashLoopBackOff    12         43m
cilium-9bj7r                            0/1     CrashLoopBackOff    12         43m
cilium-dn6p4                            0/1     CrashLoopBackOff    12         43m
cilium-kpxb8                            0/1     CrashLoopBackOff    12         43m
cilium-lkc5k                            0/1     CrashLoopBackOff    12         43m
cilium-n7plm                            0/1     CrashLoopBackOff    12         43m
cilium-operator-5d74fc4fd6-lfp2x        0/1     ContainerCreating   0          43m
cilium-r6226                            0/1     CrashLoopBackOff    12         43m

Logs showed:
level=fatal msg="Unable to create CiliumNode resource" error="ciliumnodes.cilium.io is forbidden: User \"system:serviceaccount:kube-system:cilium\" cannot create resource \"ciliumnodes\" in API group \"cilium.io\" at the cluster scope" subsys=nodediscovery

So I edited the cilium clusterole:
$ kubectl edit clusterrole cilium -n kube-system
...
- apiGroups:
 - cilium.io
 resources:
 - ciliumnetworkpolicies
 - ciliumnetworkpolicies/status
 - ciliumendpoints
 - ciliumendpoints/status
 - ciliumnodes   <============
  verbs:
 - '*'

Then I got:
level=error msg=k8sError error="github.com/cilium/cilium/pkg/k8s/watchers/cilium_clusterwide_network_policy.go:132: Failed to list *v2.CiliumClusterwideNetworkPolicy: ciliumclusterwidenetworkpolicies.cilium.io is forbidden: User \"system:serviceaccount:kube-system:cilium\" cannot list resource \"ciliumclusterwidenetworkpolicies\" in API group \"cilium.io\" at the cluster scope" subsys=k8s

So I updated the cluster role again:
- apiGroups:
  - cilium.io
  resources:
  - ciliumnetworkpolicies
  - ciliumnetworkpolicies/status
  - ciliumendpoints
  - ciliumendpoints/status
  - ciliumnodes
  - ciliumclusterwidenetworkpolicies  <===============
  verbs:
  - '*'

After this edit the pods were all running !
General Information

Cilium version
1.7.1
Kernel version (run uname -a)
Linux master2 5.5.7-1.el7.elrepo.x86_64 #1 SMP Fri Feb 28 12:21:58 EST 2020 x86_64 x86_64 x86_64 GNU/Linux
Orchestration system version in use (e.g. kubectl version, Mesos, ...)
Kubernetes:
Client Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.7", GitCommit:"be3d344ed06bff7a4fc60656200a93c74f31f9a4", GitTreeState:"clean", BuildDate:"2020-02-11T19:34:02Z", GoVersion:"go1.13.6", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.7", GitCommit:"be3d344ed06bff7a4fc60656200a93c74f31f9a4", GitTreeState:"clean", BuildDate:"2020-02-11T19:24:46Z", GoVersion:"go1.13.6", Compiler:"gc", Platform:"linux/amd64"}

How to reproduce the issue

Install a Kubernetes cluster using Kubespray 1.12.1 and upgrading its cilium version to 1.7.1
Pods are crashing
Edit the cilium clusterrole and add the missing ressources of cilium.io.
Everything should go back to normal

@Docteur-RS thanks for opening the issue. Did you follow the upgrade guide https://docs.cilium.io/en/v1.7/install/upgrade/ to upgrade cilium to version 1.7.1?

@aanm Hey !
I don't have anything to upgrade from because there was no cilium installed previously.
When I used the "upgrade" keyword I meant that Kubespray was initially using the 1.5.x version but I updated this value before I started the installation. So the version installed was directly the 1.7.1.

@Docteur-RS this will be fixed by https://github.com/kubernetes-sigs/kubespray/pull/5438 once it's merged

@aanm Ok then.
I tried with 1.6.5 and had the same errors.
Before I close this issue would you know what release I should try to be clear of this problem ?
Thx

@Docteur-RS Can't you can still install cilium with kubespray and use this upgrade guide to upgrade to 1.7.1?

Sure ! I also tried to uninstall and resintall cilium the following way:
kubectl delete -f https://raw.githubusercontent.com/cilium/cilium/v1.7/install/kubernetes/quick-install.yaml
kubectl create -f https://raw.githubusercontent.com/cilium/cilium/v1.7/install/kubernetes/quick-install.yaml

Its working great ! All the pods were up. 😄

But I am searching for something working out of the box... In my previous Kubespray It was bundled with cilium v1.3.0 and it was working smoothly.
I guess that there is at least one working cilium release that has the missing RBAC requirements and that is newer then my old v1.3.0 ?


ASUS ROG Harpe Ace Aim Lab Edition

Would the ASUS ROG Harpe Ace Aim Lab Edition be supported in the future?  I have included an lsusb as I saw in another reported issue to see if it could be added and supported.  I tried to configure a .device file to no avail, it still won't detect it.  Using wirelessly in 2.4 Ghz mode with the dongle.
Let me know if I can provide any additional information to help with this request.
lsusb -vd 0b05:1a94

Bus 001 Device 006: ID 0b05:1a94 ASUSTek Computer, Inc. ROG HARPE ACE AIM LAB EDITION
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0        64
  idVendor           0x0b05 ASUSTek Computer, Inc.
  idProduct          0x1a94
  bcdDevice            3.06
  iManufacturer           1 ASUSTeK
  iProduct                2 ROG HARPE ACE AIM LAB EDITION
  iSerial                 3 N9MPGDD19368h
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength       0x005b
    bNumInterfaces          3
    bConfigurationValue     1
    iConfiguration          4 Default configuration
    bmAttributes         0xe0
      Self Powered
      Remote Wakeup
    MaxPower              500mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass         3 Human Interface Device
      bInterfaceSubClass      0
      bInterfaceProtocol      0
      iInterface              0
        HID Device Descriptor:
          bLength                 9
          bDescriptorType        33
          bcdHID               1.11
          bCountryCode            0 Not supported
          bNumDescriptors         1
          bDescriptorType        34 Report
          wDescriptorLength      34
         Report Descriptors:
           ** UNAVAILABLE **
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x01  EP 1 OUT
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               1
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         3 Human Interface Device
      bInterfaceSubClass      1 Boot Interface Subclass
      bInterfaceProtocol      2 Mouse
      iInterface              0
        HID Device Descriptor:
          bLength                 9
          bDescriptorType        33
          bcdHID               1.11
          bCountryCode            0 Not supported
          bNumDescriptors         1
          bDescriptorType        34 Report
          wDescriptorLength      82
         Report Descriptors:
           ** UNAVAILABLE **
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               1
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        2
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         3 Human Interface Device
      bInterfaceSubClass      0
      bInterfaceProtocol      0
      iInterface              0
        HID Device Descriptor:
          bLength                 9
          bDescriptorType        33
          bcdHID               1.11
          bCountryCode            0 Not supported
          bNumDescriptors         1
          bDescriptorType        34 Report
          wDescriptorLength     136
         Report Descriptors:
           ** UNAVAILABLE **
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               1
Device Status:     0x0001
  Self Powered

@kyokenn

I have pushed .device file for the mouse:
https://github.com/kyokenn/libratbag/blob/harpe/data/devices/asus-rog-harpe-ace-aim-lab.device
You can download and add the .device file if you have the latest libratbag from master or try to build from this branch:
https://github.com/kyokenn/libratbag/tree/harpe

Hi @kyokenn - Thank you very much for getting this done so quickly!  I was able to put this .device file and it detected my mouse.  However, I'm seeing some odd behavior and didn't know how to resolve it?  I also know that in Windows (I dual boot) I have 4 set DPIs in the bloated Asus tool.  Is it possible to show those 4 DPIs on the piper app as selections with the current one already selected?
Including a screenshot of Piper below:

Can you post an output of "ratbagd --verbose=raw" ?

I did some research and figured out that newer mice uses "write only" DPI settings. But I think I could implement some workaround for those mice.
Can you change line "Leds=1" to "Leds=3" and test saving and loading of the missing LED slots? You can test by setting some specific color, unplug and turn off the mouse and then turn on and plug it back to check if the colors was saved.
It works for my mouse, but I just wanted to make sure.


chore(deps): unpdate deps to remove known vulnerabilities

Updated the deps to remove all currently known vulnerabilities:

@kmartens27 Please review and merge this one before the others after it


bug: $ionicRefresher exception: Uncaught TypeError: Can

Type: bug
Ionic Version: 1.x
Platform: all
When switching states it appears randomly, however all of my states use the ion-refresher module.
I can assure that during the exception no refreshing is in progress.
The exception is:
**Uncaught TypeError: Cannot read property 'classList' of null**

The location is in the $ionicRefresher module,
function setScrollLock(enabled) {
      // set the scrollbar to be position:fixed in preparation to overscroll
      // or remove it so the app can be natively scrolled
      if (enabled) {
        ionic.requestAnimationFrame(function() {
          scrollChild.classList.add('overscroll');
          show();
        });

      } else {
        ionic.requestAnimationFrame(function() {
          **scrollChild.classList.remove('overscroll');  <--- EXCEPTION**
          hide();
          deactivate();
        });
      }
    }

Hello! Is this still an issue with the latest version of ionic? Thanks!

Hello all! As it seems it has been a while since there was any activity on this issue i will be closing it for now. Feel free to comment if you are still running into this issue. Thanks for using Ionic!

I'm facing this issue on my ionic project. I use ion-refresher in my app and when I pull to refresh, every time I get the following exceptions.
Uncaught TypeError: Cannot read property 'style' of null Uncaught TypeError: Cannot read property 'style' of null Uncaught TypeError: Cannot read property 'classList' of null

I am still facing this issue as well in our ionic1/angular1 project.

Message
Uncaught Exception: Uncaught TypeError: Cannot read property 'classList' of null at (compiled_code):26

TypeError: Cannot read property 'classList' of nullat file:///android_asset/www/default/js/vendor.js:26:15686

Same place Barocsi pointed out.


CHttpRequest.php on line 124, CErrorHandler.php on line 293, CCache.php on line 108, error

when open index page with browser showing the following errors, i am using magento 2.4.1
Deprecated: Function get_magic_quotes_gpc() is deprecated in /home/532747.cloudwaysapps.com/bdtyrdnggq/public_html/jalil/yii/web/CHttpRequest.php on line 124
Warning: Cannot modify header information - headers already sent by (output started at public_html/migrate/yii/web/CHttpRequest.php:124) in public_html/migrate/yii/base/CErrorHandler.php on line 293
Notice: unserialize(): Unexpected end of serialized data in public_html/migrate/yii/caching/CCache.php on line 108
Notice: unserialize(): Error at offset 0 of 1 bytes in public_html/migrate/yii/caching/CCache.php on line 108
Error 500
Function get_magic_quotes_gpc() is deprecated

is there any one who can help please

@Asifjalil99 , thanks for working around our migration script here.
Due to our limited resources, we could not keep the script up to date in accordance with the recent Magento releases.
Please consider moving forward with our newer Pro version which is fully compatible with Magento 2.4.2 (You will not encounter the error notices you mentioned above.)
Regards,
Ubertheme team


Should not be able to path_open absolute path

path_open an absolute path should error. This behavior is consistent amongst Wasmtime, WasmEdge, Wazero, WAMR.  Fixing this does not break clients using wasi-libc as it already strips the prefix by matching the path with the appropriate preopened directory.
WASI folks have also stated absolute path should not work at the raw WASI level. https://github.com/WebAssembly/WASI/issues/374

@yagehu it would be fantastic if you could implement the openat() algorithm used by WASI for sandboxing. There is some discussion about it in https://github.com/libuv/libuv/issues/4167. You could implement it directly in uvwasi if you don't want to send a PR to libuv. If that were implemented, I believe we could revert https://github.com/nodejs/uvwasi/commit/1da5f325af83d80fae20da75cdcfa1b308c50ada


internal/oci: Strip leading slashes from tar header

When adding the tar header for the built binary, the leading slashes in the path should be stripped since members within a tar archive should have a relative path. This way, when the tar archive is unpacked in the current directory, or in a different directory when invoked with tar -C, the structure within the archive is mirrored outside of the archive.
Prior to this commit, if you built an image with gopack, attempted to fetch the individual layer blob from a registry, and print the layer's contents, you would see an error like this:
tar: Removing leading `/' from member names
/app/gopack-test

While GNU tar(1) will strip the leading slashes from member names, it would likely be better to remove the leading slash from the member name entirely when the header is written.
After using gopack with this patch applied, attempting to list the archive members from the retrieved layer/blob, the tar warning goes away.

Thank you for the fix!

You're most welcome! :smile:
Thank you for accepting it!


How do you limit documents when using getDocs?

im trying to limit the documents i get, I am using ,limit after collection in the getdocs function. It's not working. Please tell me the right way
const querySnapshot = await getDocs(
collection(db, collectionName.Name),
limit(20)
);

To limit data you need a query:
getDocs(
  query(
    collection(db, collectionName.Name),
    limit(20)
  )
)

I recommend keeping the documentation on ordering and limiting data handy for cases such as this.
Also going forward, please only post issues with the code snippet to this repo. Questions about how to use the API are best handled on Stack Overflow.


Fix a bug when set memo in pinot visibility store

What changed?
Currently it exists memo not equals to nil but data is empty, pinot will save it to search attribute and cause issue when list workflow executions and deserialize

Why?
Bug fix

How did you test it?
Unit test

Potential risks

Release notes

Documentation Changes

Pull Request Test Coverage Report for Build 018f30bb-dcf0-4fbe-a31a-33230e9129c8
Details

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
63 unchanged lines in 15 files lost coverage.
Overall coverage decreased (-0.02%) to 67.915%

Files with Coverage Reduction
New Missed Lines
%

common/task/weighted_round_robin_task_scheduler.go
2
89.05%

common/persistence/sql/sqlplugin/postgres/task.go
2
73.4%

common/task/parallel_task_processor.go
2
93.06%

common/persistence/execution_manager.go
2
83.74%

service/matching/db.go
2
73.23%

service/matching/matcher.go
2
90.72%

common/log/tag/tags.go
3
50.46%

service/history/task/fetcher.go
3
85.57%

service/history/queue/timer_queue_processor_base.go
4
77.66%

service/frontend/wrappers/metered/metered.go
4
66.67%

Totals

Change from base Build 018f2f7f-db2f-46d8-b64d-f304962b54b6:
-0.02%

Covered Lines:
99721

Relevant Lines:
146831

💛  - Coveralls


Document major changes ideas for outdated flows and matching

This is for providing initial summary and document the major expected changes ideas for outdated flows and matching  on issues #19 and #30

Closing this since https://github.com/kytos-ng/kytos/pull/278 has landed, nad this was a placeholder for the blueprint.


Add spec for EQL allow_partial_search_results

Add spec for EQL allow_partial_search_results and for allow_partial_search_results parameters.
These allow EQL queries to keep running in case of shard failures.
Relates to https://github.com/elastic/elasticsearch/pull/116388
Wait for https://github.com/elastic/elasticsearch/pull/118862 (backport of the above) before merging!

Validation not supported from forks, reopening as https://github.com/elastic/elasticsearch-specification/pull/3342


Fixes form button from becoming unusable in case of missing any selection

When a step, such as selection / creation of a network is missed during VM deployment, though prompted to take necessary action - once the correction has been made, the form is no longer usable as the Launch Virtual Machine button becomes unusable

@blueorangutan package

@Pearl1594 a Jenkins job has been kicked to build primate packages. I'll keep you posted as I make progress.

Seems reasonable please review @davidjumani @andrijapanicsb

Packaging result: :heavy_check_mark:centos :heavy_check_mark:debian :heavy_check_mark:archive.
QA: http://primate-qa.cloudstack.cloud:8080/client/pr/715 (JID-3473)


max_entries of flow_directions map sets from configuration

The flow_directions map with hardcoded max_entries as 1 << 24 needs to lock over 2GB of memory.
sudo bpftool map show name flow_directions
563: lru_hash  name flow_directions  flags 0x0
	key 43B  value 1B  max_entries 16777216  memlock<PHONE_NUMBER>B
	btf_id 664

This PR sets max entries from user configuration as for aggregate_flows. With a default value (5000) needs about 650KB.
sudo bpftool map show name flow_directions
556: lru_hash  name flow_directions  flags 0x0
	key 43B  value 1B  max_entries 5000  memlock 652160B
	btf_id 656

The key flow_id is pretty heavy (43B), and having it readable in the flow_directions map is unnecessary. I analysed if there is a better key to use, but found nothing yet.

Codecov Report
Attention: Patch coverage is 0% with 2 lines in your changes missing coverage. Please review.

Project coverage is 47.58%. Comparing base (d7d75a1) to head (9f28c6b).

Files
Patch %
Lines

pkg/internal/netolly/ebpf/sock_tracer.go
0.00%
1 Missing :warning:

pkg/internal/netolly/ebpf/tracer.go
0.00%
1 Missing :warning:

Additional details and impacted files
@@             Coverage Diff             @@
##             main     #959       +/-   ##
===========================================
- Coverage   71.45%   47.58%   -23.87%
===========================================
  Files         130      131        +1
  Lines       10319    10330       +11
===========================================
- Hits         7373     4916     -2457
- Misses       2314     5063     +2749
+ Partials      632      351      -281

Flag
Coverage Δ

integration-test
?

k8s-integration-test
?

oats-test
?

unittests
47.58% <0.00%> (?)

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Thanks again @bareckidarek !


⚠ Bofrost.at has degraded performance

In e668286, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 3105 ms

Resolved: Bofrost.at performance has improved in 6dff046.


Fix endpoint IP calculation

If the bind address on a port is '<IP_ADDRESS>', use the host's
IP address for public endpoints. This bug always existed if a user
were to explicitly set their IP on the port to <IP_ADDRESS>, but no one
does that in real life. This is an issue now becauseexternal scheduler
explicity sets it to <IP_ADDRESS> for all ports that haven't explicity set
it.
for https://github.com/rancher/rancher/issues/7556
for https://github.com/rancher/rancher/issues/7605

LGTM


This script is only tested and validated on the K2

This is more of a notification to anyone that comes across the repo with another keyboard model from Keychron, like the K1. Unless someone can chime in that this fixes all issues with all their keyboards then I wouldn't assume this script works.
That said, it won't actually hurt anything if you give the actual line of bash a try in the terminal. It would be reset on reboot.

I tested it on Keychron K3, it works without problems.

tested on Keychron K6, it works !

I can add the keyboards listed here as tested to the readme; thanks for trying it out!

K1 SE works too :+1:

Works on K8

Thanks everyone! These keyboards have been added to the readme. Ping me if there are others.

Thank you so much. Works on dareu A87 V2.


Support multi-AZ Elasticsearch for high availability

Is your feature request related to a problem? Please describe.
When the ElasticsearchInstanceCount property is set to a value greater than one in the Amplify API parameters file, the extra ES instances are all created in the same AZ. This means that it is not possible to have a highly available ES cluster using Amplify.
Describe the solution you'd like
Enable multi-AZ in the generated Cloudformation templates when the ElasticsearchInstanceCount is greater than 1.
Describe alternatives you've considered
Modify manually in the AWS Console, however this is reverted on the next Amplify push if the ElasticsearchInstanceCount or ElasticsearchInstanceType is changed.
Additional context
This is an essential feature for any production workload using Elasticsearch.

has this been addressed?

Hi @jeff-accountably @chris-merapar thanks for filing this issue. We've since launched the ability to override the generated resources under the hood. https://docs.amplify.aws/cli/graphql/override/
amplify override api

import { AmplifyApiGraphQlResourceStackTemplate } from '@aws-amplify/cli-extensibility-helper';

export function override(resources: AmplifyApiGraphQlResourceStackTemplate) {
  resources.opensearch.OpenSearchDomain.elasticsearchClusterConfig = {
    ...resources.opensearch.OpenSearchDomain.elasticsearchClusterConfig,
    zoneAwarenessConfig: {
      availabilityZoneCount: 2
    }
  }
}


trigger update feature

Currently the trigger option for the local.Command function does not allow for triggering a resource update. This will alway trigger a replacement.
https://www.pulumi.com/registry/packages/command/api-docs/local/command/#inputs
I would like the expected functionality of a value change to trigger a non-destructive update in addition to the existing functionality where a value change triggers a replacement.

@AaronFriel the scenario I have is the deployment of an API proxy using CLI commands.
In an update scenario either update will be run, or if not specified then create will be run.
For my use case this means that my create command which does a seamless redeploy of a new version will run
i.e.
create=pulumi.Output.all(name=self.api_proxy.name, \
                        rev=self.api_proxy.revision, token=self.token, \
                        org=self.organization_id).apply(
                            lambda args: f"apigeecli apis deploy \
                                    -o {args['org']} \
                                    -n {args['name']} \
                                    -v {args['rev'][-1]} \
                                    -e {self.env_name} \
                                    -t {args['token']} \
                                    -r"),

However, from the above command I need to ignore token changes from create/delete which is a shortlived auth token.
and so must leverage triggers on proxy revision
opts=pulumi.ResourceOptions(
    ignore_changes=["create", "delete"]
),
triggers=[self.api_proxy_revision]

In a replace scenario default behavior is create/delete where the seamless redeploy occurs, and then an undeploy occurs and I am left with no proxy.
If I override the default behaviour with delete_before_replace then the proxy is undeployed and then redeployed which results in downtime for the API proxy which is undesirable.

I have currently resolved my issue by using another command which can leverage environment vars to pass the token value, and so I am not  required to use triggers right now, though this still seems to me like worthwhile functionality.
environment={'CLOUDSDK_AUTH_ACCESS_TOKEN': token},
create=pulumi.Output.format("gcloud apigee apis deploy {0} --organization={1} --environment={2} --api={3} --override",
                                        revision,
                                        self.organization_id,
                                        self.env_name,
                                        self.api_proxy_name),
opts=pulumi.ResourceOptions(
                ignore_changes=["environment"],
)


Renaming a Deployment

I've run into a few cases where I've wanted to rename a BOSH deployment, without changing anything else (composition / addressing / etc.).
I've done some experimental hacking and I believe the following things need to be done:

Change the deployments.name field in the database
Notify all agents of the rename (I did this manually via sed -i'' -e 's/oldname/newname/' /var/vcap/bosh/spec.json on each VM)

Are there any landmines to doing this?  Is this something we would want (like a bosh rename deployment oldname newnme command?)  If so, I'll gladly work on it.

Agreed. We've also ran into this.
We are currently in the middle of introducing some long reaching changes into the Director. Once we merge it in (story: https://www.pivotaltracker.com/story/show/100170490) I think it makes sense to do it. We are also trying to stop sending all kinds of unnecessary information to the VM (deployment name is not something agent should care about), so changes would pretty much be change the DB and trigger deploy.

+1

+1

Any movement on this, @cppforlife ?

Since we followed these instructions yesterday: +1
We also changed /var/vcap/instance/deployment

+1

This is something I would be very interested in for the On Demand Broker.
Users want to specify a deployment prefix, so we would like to rename all existing instances to have this pre-fix.

+1

1

+1

+1

+1

+1 - This would greatly help in reorganizing / moving around some of our existing deployments.

+1

Thanks all for the feedback. I've created story: https://www.pivotaltracker.com/story/show/159605314 to look further into this. Not sure on timelines yet, but the large number of +1's is certainly encouraging.

+1 yay! This issue was opened in 2015!

+1

+1

+1

+1

@mfine30
Please note that when using non absolute credhub variable names (i.e. they do not start with a /), the director will append the director name and Deployment Name before it fetches/generates these variables from credhub.
Need to take that into consideration this feature is worked on.

+1

+1

Any updates on this? I would love to use this feature.

+1

@cppforlife did https://www.pivotaltracker.com/story/show/100170490 ever get merged?

+1

Dmitriy has evolved away from BOSH since last Basel CF Summit… like 3 years ago… But hey James, I'm glad to see you still care in your post-S&W life! ;-)
By the way, does anyone know what “dynamic provisioning” is supposed to mean, in this Tracker Story #100170490
About CredHub secrets, that's a tricky matter. I have a tough experience in “moving” them inside the CredHub directory (after renaming a Concourse pipeline, for instance). Only updating the path in the database does not work. There is some fingerprinting or encryption that needs to be updated using the new path, which makes me wonder what is the design (and why).


Keyboard navigation (e.g. moving card using , and .) does not update WiP limits etc.

This was because I accidently deleted a letter in the function name :P


5 teaser block createtion

Please always provide the GitHub issue(s) your PR is for, as well as test URLs where your change can be observed (before and after):
Fix #5
Test URLs:
Before: https://develop--dva-showcase--ifahrentholz.hlx.live/
After: https://5-teaser-block-createtion--dva-showcase--ifahrentholz.hlx.page/

Example implementation :
https://5-teaser-block-createtion--dva-showcase--ifahrentholz.hlx.page/develop/chris/


Fix workspace creation 303

PR checklist
Docs

[ ] If you added new code; is it self documenting? (all the variable names clear, comments added where appropriate)
[ ] If you touched existing code; did you refactor existing naming, added comments where necessary?

Tests

[ ] If your ticket adds new functionality; have you added unit tests to verify behaviour?
[ ] If your ticket alters user interaction with the UI; have you added integration tests?
[ ] Do your tests check for every convievable user behabviour? (all behaviours the user can perform)

Typing

[ ] If you added new code; have you added typing?
[ ] If you touched existing code; have you improved its typing?

Styling

[ ] If new styles were created; Did you refactor/add more styles in css-in-js style?

Looks like #304 fixed the #303, so the PR could be closed.


chore: unusable 0.0.1

Changes Unknown when pulling 66b5bdfcb4fc384e8610384e7b29098d5cd6b1a0 on chore/initial_version into ** on latest**.


Breaking Change on 2.3.1 - Can't encode Bitwise Permissions

Steps to Reproduce
After upgrade from 2.3.0 to 2.3.1 old perms_map dont work.
Unable to find a clue in Changelog:
v2.3.1
Change compile time loading of configuration to only load permissions allowing the app to change things like ttl or secret key at runtime
Expected Result
defstruct perms_map: %{
              account_viewer: %{
                account: [
                  :read,
                  :dashboard
                ]
              },
}

alias MyApp.Guardian
test = %{
  account: [:read, :dashboard]
}
test |> Guardian.encode_permissions!()

%{account: 123}

PS: some bitwise number.
Actual Result
** (Guardian.Permissions.PermissionNotFoundError) Elixir.MyApp.Guardian Type: account Missing Permissions: read,
dashboard

I think that on 2.3.1 and ongoing need to define on config.exs.
base_permissions_list = [
:read,
:export_drilldown,
:export_reports,
:export_campaigns,
:export_messages,
:export_people,
:export_templates,
:template,
:people,
:campaign,
:write,
:delete,
:dashboard
]
config :my_app, MyApp.Guardian,
allowed_algos: ["HS512"],
issuer: "myapp",
token_ttl: %{
"reset" => {10, :minutes},
"magic" => {10, :minutes},
"access" => {30, :minutes},
"user" => {2, :hours},
"myuser" => {2, :hours},
"company" => {52, :weeks}
},
allowed_drift: 2000,
secret_key: Application.compile_env(:peoplex_services, :guardian_secret_key),
permissions: %{
account: base_permissions_list,
group: base_permissions_list,
mgmt: base_permissions_list
}

Do you mind creating an example project showcasing the issue or much better to create a PR?

cc: @geofflane 😭

It works with all permissions in config.exs. My suggestions, since this is a "new behaviour", is to enhance documentation.
We use Guardian for more than 5 years, and our list of permissions grew since.

Do you mind creating an example project showcasing the issue or much better to create a PR?

It works as intended with all permissions in config.exs. My suggestions, since this is a "new behaviour", is to enhance / clarify documentation. The changelog in our opinion it is not clear enough.
We use Guardian for more than 5 years, so our list of permissions grew since and we didn't bother updating back our config.exs.

@pedromvieira do you mind opening a PR about the topic?

@pedromvieira I will encourage you to improve the documentation based on your experience. I am going to close the issue for now.


language-plutus-core/plutus-ir: add default Pretty instances

While the full-on pretty-printing machinery is useful, and we do want it
for PIR (so we can e.g. get debug printing of uniques), it's nice to
have a default implementation of plain Pretty for "boring" usage.
As a side benefit, this lets me define a printing function that works
for both PLC and PIR, which will be helpful for my demo. (Possibly we
can do this already but I am unable to figure out how to.)

I care about this less since I've stripped down what I'm doing in my demo, but I still think it's a good idea.

I think, we can do the following:
type PrettyClassic = PrettyClassicBy PrettyConfigName

prettyClassicDef :: PrettyClassic a => a -> Doc ann
prettyClassicDef = prettyBy $ PLC.PrettyConfigClassic PLC.defPrettyConfigName

...

instance PrettyClassic (PLC.Term tyname name a) => Pretty (PLC.Term tyname name a) where
    pretty = prettyClassicDef

...

instance PrettyClassic (PIR.Term tyname name a) => Pretty (PIR.Term tyname name a) where
    pretty = prettyClassicDef

@effectfully I'm not sure what your last suggestion adds over the current one? Is it just that we can then have the same constraint on the PIR and PLC functions (i.e. PrettyClassic)? But we already get that by giving them a Pretty instance.

Okay, I did that, it is indeed a bit nicer.

I think this is useful, and we can revert it later if we don't use it.


[tools] update tools schema

Proposed changes
Issue Number: close #xxx
Update tpcds tools table customer_demographics's bucket column as its primary key column, avoid performance issue due to data skew.
From: https://github.com/apache/doris/pull/35873

run buildall


WIP: check CI on Julia 1.9

The threaded CI failure looks real (same on Linux and macOS) :disappointed:
https://github.com/trixi-framework/Trixi.jl/actions/runs/4934469215/jobs/8819547326#step:7:3336

I'm installing 1.9 later today and can check the failing DGMulti tests locally.

Great, thanks!

The error seems related to the fact that Static.False() == true returns false in 1.8.5 but breaks in 1.9.
julia> Static.False() == true
ERROR: TypeError: in typeassert, expected False, got a value of type True
Stacktrace:
 [1] convert
   @ ./number.jl:7 [inlined]
 [2] _promote
   @ ./promotion.jl:358 [inlined]
 [3] promote
   @ ./promotion.jl:381 [inlined]
 [4] ==(x::False, y::Bool)
   @ Base ./promotion.jl:449
 [5] top-level scope
   @ REPL[15]:1

https://github.com/SciML/Static.jl/issues/108

Static v0.8.7 should have fixed some of Static.True-related CI issues.

/home/runner/work/Trixi.jl/Trixi.jl/examples/p4est_3d_dgsem/elixir_euler_ec.jl

[5213] signal (15): Terminated
in expression starting at /home/runner/work/Trixi.jl/Trixi.jl/test/runtests.jl:9

[1779] signal (15): Terminated
in expression starting at /home/runner/work/_actions/julia-actions/julia-runtest/v1/test_harness.jl:7

===================================================================================
=   BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES
=   PID 5220 RUNNING AT fv-az210-40
=   EXIT CODE: 9
=   CLEANING UP REMAINING PROCESSES
=   YOU CAN IGNORE THE BELOW CLEANUP MESSAGES
===================================================================================
YOUR APPLICATION TERMINATED WITH THE EXIT STRING: Killed (signal 9)
This typically refers to a problem with your application.
Please see the FAQ page for debugging suggestions
Error: The operation was canceled.

MPI on Linux :cry:

MPI tests pass locally on Linux (without coverage tracking)

Ci failed again
[ Info: Testset elixir_advection_cubed_sphere.jl finished in 9.761835486 seconds.

Please see the FAQ page for debugging suggestions
epoll_wait at /lib/x86_64-linux-gnu/libc.so.6 (unknown line)
epoll_wait at /lib/x86_64-linux-gnu/libc.so.6 (unknown line)
Error: The operation was canceled.

It's also failing on main...
 [ Info: Testset elixir_advection_amr.jl finished in 93.04042979500001 seconds.
WARNING: replacing module TrixiTestModule.
WARNING: replacing module TrixiTestModule.
════════════════════════════════════════════════════════════════════════════════════════════════════
/home/runner/work/Trixi.jl/Trixi.jl/examples/p4est_3d_dgsem/elixir_advection_amr_unstructured_curved.jl

████████╗██████╗ ██╗██╗  ██╗██╗
╚══██╔══╝██╔══██╗██║╚██╗██╔╝██║
   ██║   ██████╔╝██║ ╚███╔╝ ██║
   ██║   ██╔══██╗██║ ██╔██╗ ██║
   ██║   ██║  ██║██║██╔╝ ██╗██║
   ╚═╝   ╚═╝  ╚═╝╚═╝╚═╝  ╚═╝╚═╝

┌──────────────────────────────────────────────────────────────────────────────────────────────────┐
│ SemidiscretizationHyperbolic                                                                     │
│ ════════════════════════════                                                                     │
│ #spatial dimensions: ………………………… 3                                                                │
│ mesh: ………………………………………………………………… P4estMesh{3, Float64}                                            │
│ equations: …………………………………………………… LinearScalarAdvectionEquation3D                                  │
│ initial condition: ……………………………… initial_condition_gauss                                          │
│ boundary conditions: ………………………… 1                                                                │
│ │ all: ……………………………………………………………… Trixi.BoundaryConditionDirichlet…Trixi.initial_condition_gauss)} │
│ source terms: …………………………………………… nothing                                                          │
│ solver: …………………………………………………………… DG                                                               │
│ total #DOFs: ……………………………………………… 24000                                                            │
────────────────────────────────────────────────────────────────────────────────────────────────────
 Simulation running 'LinearScalarAdvectionEquation3D' with DGSEM(polydeg=4)
────────────────────────────────────────────────────────────────────────────────────────────────────
 #timesteps:                  0                run time:       4.40000000e-06 s
 Δt:             1.00000000e+00                └── GC time:    0.00000000e+00 s (0.000%)
 sim. time:      0.00000000e+00                time/DOF/rhs!:
Please see the FAQ page for debugging suggestions
Error: The operation was canceled.

https://github.com/trixi-framework/Trixi.jl/actions/runs/4944887550/jobs/8840879095#step:7:9721

Linux MPI CI passes with use --heap-size-hint=1G for MPI runs in CI - at least in the first run :partying_face:

There is just a minor floating point difference in some DGMulti run - I will adapt the tolerance there

Second successful Linux MPI run :partying_face:

This seems to look quite good to me. Some notable results are

with the new heap size limit kwarg introduced in Julia v1.9, Linux MPI passed two times
the performance specializations run in 30 + 40 minutes instead of >1h + >1h
the other CI runs also appear to be a bit faster

Thus, I would like to move at least some part of our testing infrastructure to Julia v1.9. However, we do not use other features introduced in Julia v1.9. Thus, I would also like to keep backwards compatibility with Julia v1.8. We cannot test everything on Julia v1.8, too, since that defeats a lot of the gains from moving to v1.9. Thus, I see two options

Test everything on Julia v1.9 and add cheap tests with Julia 1.8 - the threaded tests runnign without coverage
Test everything on Julia v1.8 except the tests that benefit the most - MPI and performance specializations

Any thoughts?

Any thoughts?

Thanks for having a closer look at this! I am not sure why my tests with the new heap size hint did not really produce any measurable improvements, but I am happy (maybe not happy, but at least the world makes sense again) for the mounting evidence that the MPI failures are, after all, a memory issue.
I would argue that considering what we know now, there is no need for anyone to not switch to Julia v1.9 (except maybe, in fact, these memory issues in case of MPI jobs). Therefore, since this is or will become or main development version, we should run our tests with v1.9 as well. Thus, I'd vote for moving our testing infrastructure to v1.9 and keep some additional tests around for backward compatibility with v1.8.

@sloede CI reveals a problem with the new Makie extension that I did not anticipate: The docs build fails since Julia v1.9.0 recognizes the extension and tries to precompile it. However, we guard the loading of Makie behind a check for Julia v1.9.1. Thus, it tries to use the Requires.jl version on Julia v1.9.0 and fails. Thus, we cannot use this approach.

TODO: add threaded_legacy to required CI checks. I added it with a new job name since we do not include the Julia version in the CI job names.

MPI CI passes again. I am optimistic that it really was a memory issue that is fixed by passing --heap-size-hint=1G to the new Julia processes


⚠ Unifi Controller has degraded performance

In 04b6ad0, Unifi Controller (https://unifi.vflits.com/) experienced degraded performance:

HTTP code: 502
Response time: 2160 ms

Resolved: Unifi Controller performance has improved in d73e8f9 after 3 minutes.


Question: query performance without loading full index into mem?

Describe what you are looking for

The latter allows you to serve indexes from external memory, enabling you to optimize your server choices for indexing speed and serving costs. This can result in 20x cost reduction on AWS and other public clouds.

other_view = Index(ndim=..., metric=...)
other_view.view("index.usearch")

Hi, usearch is great vector search library, and I saw that we can view the index without loading it into RAM fully, do we have any performance benchmark in this case, and how about comparing with the case loading full index into RAM?
Can you contribute to the implementation?

[ ] I can contribute

Is your feature request specific to a certain interface?
It applies to everything
Contact Details
No response
Is there an existing issue for this?

[X] I have searched the existing issues

Code of Conduct

[X] I agree to follow this project's Code of Conduct

This highly depends on the latency if your SSDs.


TypeError: object is not a function (from xml

..../node_modules/engine.io-client/lib/transports/polling.js:23
  var xhr = new XMLHttpRequest({ xdomain: false });
            ^
TypeError: object is not a function

https://travis-ci.org/angular/angular.js/jobs/48693062#L3892
I'm getting this error when bootstrapping socket.io on Travis (linux).
It works fine on my MacBook.
I was able to reproduce the same issue on my Ubuntu when I was installing the NPM package (karma which depends on socket.io) from github url, then I switched to a version published on NPM (the same content) and the issue went away. Unfortunately it didn't go away on Travis.
Did anybody see this before?

I discovered that this issue only occurs when npm-shrinkwrap is used.

This is due to the way Angular.js cleans npm-shrinkwrap. It removes the resolved information, which which results in a different version being installed if it was from a source other than the npmjs registry.
In any case, it's not an engine.io issue, so this can be closed.

See https://github.com/angular/angular.js/commit/d64bf98a1a2c267ca76087e992efd74300474caf

We removed github url dependencies, thus it seems the issue wouldn't occur anymore.


Getter and setter for parameters in Feedstock, Pretreatment, EnzymaticHydrolysis and Bioreactor classes

Add getters & setters to

add validation parameters bounds (check that a user assigns a parameter in the allowed interval)
automatically convert units for some parameters when getting and setting a value.
automatically rewrite the parameter's YAML file

TODO:

[x] Write getter/setter functions
[x] Update the sweep function in the optimization notebook and verify the correctness
[x] Update Optimization class
[x] Update the optimization function in the notebook and verify the correctness

The user doesn't need to know about unit conversion, but the YAML file stores converted values. This may confuse the user if one looks at the parameter file

Made a new issue so we don't lose track of the unit conversion, can this issue be closed now?


Freezes when expanding tables and database contains lots of tables

SQL Operations Studio Version: sqlops 0.27.3 (9474415ad68b5a70e8b851698c8c836664a9d5b5, 2018-03-27T05:25:59.481Z)
OS Version: Windows_NT x64 6.3.9600
Extensions:

Extension
Author (truncated)
Version

server-report
Mic
0.1.0

Steps to Reproduce:

Get a database with a huge number of tables (tested with a database containing around 50 000 tables)
Expand the "Tables" folder under "Servers"
The application freezes and becomes unresponsive, and must be killed

Reproduces without extensions: Yes/No

With recent improvements, ADS doesn't freeze if Object Explorer is slow to fetch data. Operations can be performed in parallel with 'Parallel Message Processing' enabled by default. Closing as resolved.


Import ADA Private Key from Atomic Wallet into Daedalus?

Hello,
How may we Import ADA Private Key from Atomic Wallet into Daedalus?
Thank you.

In what format is this private key?

I don't know how to answer that question.  What are the different types of formats?
This key has 180 characters.

@CarlosLopezDeLara will look into this and get back to you here in the thread.
Thank you for your patience!

@automaticprofits I'm still digging around on Atomic docs, but what I know for sure is that the 12-word recovery phrase you get from them helps you to restore a Legacy Wallet, the same that you find under Settings>PrivateKeys>Cardano>LegacyPrivateKey.
We still  need to find how they are building the Shelley wallet starting from that same 12-word. I'm awaiting response from them.
Importing from xprv should be possible. Still working on this. I'll keep you posted.

@automaticprofits Hello Mate, Sorry to hear about your issue, you can contact Atomic Wallet Support on Telegram via the weblink www.t.me/theatomicwallet. They'll be happy to resolve your issue. Cheers.

@CarlosLopezDeLara any news on this one?

@automaticprofits Atomic wallet still uses Byron wallets only. There is no way to import those into Daedalus.
I suggest you to create a Shelley wallet in Daedalus and move your funds to it so you can delegate them and earn rewards.


Csm load model

@alawibaba @doctoryes @macdiesel: This builds on https://github.com/edx/edx-load-tests/pull/3 to add a model of current CSM load.
Todo:

[x] Set the weights for get_many and set_many
[ ] Call set_many if get_many can't return enough documents

[PLAT-601]

LGTM :+1:

:+1:


Dark theme for fact-Bounty

Prerequisites
it would be better if we can add Dark theme feature for fact-Bounty
Please answer the following questions for yourself before submitting an issue. YOU MAY DELETE THE PREREQUISITES SECTION.

[x] I am running the latest version
[ ] I checked to make sure that this issue has not already been filed

Expected Behavior
toggle theme feature user can toggle Dark and light ( currently ) theme.
Please describe the behavior you are expecting
Current Behavior
What is the current behavior?
Failure Information (for bugs)
Please help provide information about the failure if this is a bug. If it is not a bug, please remove the rest of this template.
Steps to Reproduce
Please provide detailed steps for reproducing the issue.
motivate from Bassa https://github.com/scorelab/Bassa/issues/733

step 1
step 2
you get it...

Context
Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.
Failure Logs
Please include any relevant log snippets or files here.

@SamTube405 @root5533 @Anmolbansal1  what do you think about this. Please review me.
thank you : )

Sounds like good idea


WebStorm test runner integration

As a WebStorm user, I want to run my tests from within the app, so that I don't need to context switch between the terminal.
Acceptance criteria:

unit tests can run from within WebStorm

Probable prerequisite: #51

Similar to #205, I think the test runner functionality would be pretty limited, though the IJ platform is a little better about configurability (e.g. run the build step before running tests)


t7

t7

/prombench master

⏱ Welcome to Prometheus Benchmarking Tool. ⏱
Compared versions: PR-44 and master
After successful deployment, the benchmarking metrics can be viewed at:

Prometheus Meta
Prombench Dashboard
Grafana Exlorer, Loki logs

Other Commands:
To stop benchmark: /prombench cancel
To restart benchmark: /prombench restart v2.12.0

/prombench cancel

Benchmark cancel is in progress.


Add documentation for performing a transition in a transaction

Fixes https://github.com/geekq/workflow-activerecord/issues/16

Thanks for your contribution, Roman!
Stay strong!


give flex widgets the ability to take up the whole cross axis

Description
This PR gives the ability to specify whether the Flex should take up as much space as it can, or should take up as much space as it need. Currently, the size of the cross axis depends on the children. The greatest cross axis extent will be the cross axis size of the parent Flex. Moving forward, Column and Row will take a CrossAxisSize (min, max), where min means to keep the previous behavior and max means to expand as far as possible in the cross axis. The default if not provided is CrossAxisSize.min
For example:
import 'package:flutter/material.dart';

void main() {
  runApp(
    MaterialApp(
      home: Scaffold(
        body: SafeArea(
          child: Container(
            decoration: BoxDecoration(border: Border.all()),
            child: Column(
              mainAxisAlignment: MainAxisAlignment.center,
              crossAxisAlignment: CrossAxisAlignment.center,
              children: const <Widget>[
                Text('a'),
                Text('aaa'),
                Text('aaaaa'),
                Text('aaaaaaa'),
                Text('aaaaa'),
                Text('aaa'),
                Text('a'),
              ],
            ),
          ),
        ),
      ),
    ),
  );
}

import 'package:flutter/material.dart';

void main() {
  runApp(
    MaterialApp(
      home: Scaffold(
        body: SafeArea(
          child: Container(
            decoration: BoxDecoration(border: Border.all()),
            child: Column(
              mainAxisAlignment: MainAxisAlignment.center,
              crossAxisAlignment: CrossAxisAlignment.center,
              crossAxisSize: CrossAxisSize.max,
              children: const <Widget>[
                Text('a'),
                Text('aaa'),
                Text('aaaaa'),
                Text('aaaaaaa'),
                Text('aaaaa'),
                Text('aaa'),
                Text('a'),
              ],
            ),
          ),
        ),
      ),
    ),
  );
}

Related Issues
#45544
Tests
I added the following tests:
flex_test.dart:

'Flexible with CrossAxisSize.max horizontal'
'Flexible with CrossAxisSize.max vertical'
'Flexible with CrossAxisSize.min horizontal'
'Flexible with CrossAxisSize.min vertical'

basic_test.dart:

'Flex has crossAxisSize'
'Flex defaults crossAxisSize to CrossAxisSize.min'
'Flex creates RenderFlex with crossAxisSize'
'Flex updates RenderFlex with crossAxisSize'
'Column has crossAxisSize'
'Row has crossAxisSize'

Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I signed the CLA.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I updated/added relevant documentation (doc comments with ///).
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Did any tests fail when you ran them? Please read Handling breaking changes.

[x] No, no existing tests failed, so this is not a breaking change.
[ ] Yes, this is a breaking change. If not, delete the remainder of this section.

[ ] I wrote a design doc: https://flutter.dev/go/template Replace this with a link to your design doc's short link
[ ] I got input from the developer relations team, specifically from: Replace with the names of who gave advice
[ ] I wrote a migration guide: Replace with a link to your migration guide

You can already achieve this today by doing something like this:
import 'package:flutter/material.dart';

void main() {
  runApp(
    MaterialApp(
      home: Scaffold(
        body: SafeArea(
          child: Container(
            decoration: BoxDecoration(border: Border.all()),
            child: Column(
              mainAxisAlignment: MainAxisAlignment.center,
              crossAxisAlignment: CrossAxisAlignment.center,
              children: const <Widget>[
                SizedBox(
                  width: double.infinity,
                  child: Center(child: Text('a')),
                  ),
                Text('aaa'),
                Text('aaaaa'),
                Text('aaaaaaa'),
                Text('aaaaa'),
                Text('aaa'),
                Text('a'),
              ],
            ),
          ),
        ),
      ),
    ),
  );
}

Row/Column are already pretty complicated, so we'd like to avoid adding more stuff to it unless there's a really good reason for it.

I am going to close this with the comment above.


DaisyUI classes not recognised

Hi, I've been playing around with this project to get some familiarity with DaisyUI. One thing that I have noticed is I can't seem to set the background colour on any element to anything other than bg-primary or bg-base-*.
For example, this works.

Admin Dashboard Starter Kit

But this does not.

Admin Dashboard Starter Kit

I can't work out what's different between this project and the base DaisyUI configuration. I really need to be able to set the background colours on table rows for a project that I'm working on.

Ignore this, I was completely fogetting about PurgeCSS meaning that changing the class in the inspector wasn't going to work.


[FR]: share_limits ratio conditionals

Is your feature request related to a problem? Please elaborate.
I would like an option to define different share limits based on current ratio. For example, a reduced max_seeding_time when ratio is above 1.0 and a longer one when it's not to abide by tracker minimum seeding time rules
Describe the solution you'd like
Something like
min_ratio: 1.0
min_ratio_max_seeding_time: 1440
max_seeding_time: 2940
Does your solution involve any of the following?

[X] New config option
[ ] New command option

Describe alternatives you've considered
I currently do not see any way to check for ratio in the configuration options
Who will this benefit?
People who are racing while strapped for disk space
Additional Information
No response

This doesn't make sense.  Ratio or seed time is whichever is hit first for removal.  If you want to ensure a min seed time is still hit regardless of if the ratio has been met already that attribute already exists