Implement API client connector details page

created ApiConnectorDetailsPage and components
added WithApiConnector and WithApiConnectorHelpers to work with backend
removed a couple UI components and their stories that are no longer being used
added delete functionality to ApiConnectorListItem and ApiConnectorsPage
created ApiConnectorReview component for use on details page
updated ApiConnectorListItem and ApiConnectorListView stories
added details and edit route to ApiClientConnectorsModule, resolvers, and routes
fixed a bug in ExtensionsPage so that used by message is now correct

TODO (I'll write issues on these @gashcrumb):

errors and warnings on review page are not being displayed since the type I'm using (Connector) does not have those properties.
refactor components into openapi shared components
create API connector wizard (upload) has not been implemented
icon editing/uploading on details screen has not been implemented
component tests should be written

PR Storybook available here


Dropping UMD module format was a bad decision

I just found out you dropped the UMD format in favour of strict CommonJS format. In the docs you tell to rely on browserify (or webpack for that matter). I had to pinned chai-as-promised to 5.3.0 to avoid that change in my test environment and want to encourage you to bring it back.
It is not always feasible to use webpack/browserify for you tests. I.e. I use karma to test isomorphic code  in various browsers, not only for the sake of making sure they work in the browser (as opposed to my node.js tests using mocha where commonjs is used) but also to make sure my UMD bundles work - it is sort of an integration test thing. Still a lot of users don't use webpack/systemJS but rather include <script> tags to add my library and access it via a global variable. Thats why in the karma test run, I have to make sure this works and all tests execute successfully. In the past various bugs in webpack have resulted in breaking this kind of inclusion.
Please think about bringing back a chai-as-promised UMD bundle - those could co-exist with a commonJS approach and be created by webpack automatically.

Sorry, I'm not interested in doing that. The maintenance burden on me as an open-source maintainer was too high; it is not worth my time to continue working on this library with that requirement. You're welcome to maintain your own fork if you don't like using tools for the reasons you list.


Content size changes ignored

Current behavior
When the content's size changes (e.g. due to an image without pre-set dimensions being loaded), ngx-nested-ellipsis doesn't re-calculate the ellipsis:
https://stackblitz.com/edit/github-m7ud36?file=src/app/app.component.ts
(Only when the element's border box size changes the ellipsis will be auto-applied.)
Expected behavior
The ellipsis is also re-applied when the elements content size changes.

Fixed in<EMAIL_ADDRESS>- see https://stackblitz.com/edit/ngx-nested-ellipsis-fixed-content-resize-detection?file=src%2Fapp%2Fapp.component.ts


Missing method: hasPackage()

The method hasPackage() as used in the last example of the Managing the packages on a user section does not exist in the Auth class. I'd love to open a pull request with a fix, but I'd need to know if this is a mistake in the docs or simply a missing method.

Great spot, thanks very much @michaspiss ! Have now added that method in #5
I'm going to tag a release up as v1.3.0 which contains both this and the solution to #3 so you should just be a composer update away from getting things fixed.
Thanks very much again for taking the time to raise bugs and PR's, it's really appreciated!

You are welcome, thanks for creating this awesome package!


ng serve removes dist folder from the project, but it stops PhpStorm IDE from updating project folder structure.

Every time I do ng build then follows ng serve, my PhpStorm project folder view freezes  and stop updating file structure.
MacOS 10.12.3 + angular-cli beta.31 + PhpStorm 2016.3
It maybe an IDE bug rather than angular-cli bug, or not...

Definitely IDE specific. I wouldn't expect VS Code to have this for example.
Try disabling plugins just in case, and if the problem continues, please report it to JetBrains tracker.

No problem for me with this IDE (angular-cli.rc0 + PhpStorm 2016.3 + Win7 64)

Thanks. I guess this is something only happens on macOS + JetBrains then.


reorganize packages to be more clear and understandable

reorganize packages to be more clear and understandable

It was already fine.

We will do corrections if required.

Thank You 👍


Update cache-control-header.png for correction of an incorrect CC value

https://developers.google.com/web/tools/lighthouse/audits/cache-policy has an image which displays an incorrect cache-control value must_revalidate, it should be must-revalidate. I've modified the image (it's also 8KB lighter, wihoo) to correct this. I have also updated the reference to cache-bust the image, such that it is reflected on the live page:
-<img src="images/cache-control-header.png"
+<img src="images/cache-control-header.png?v=2"

Thank you for the fix. This guide now lives on web.dev so I have copied the new optimized image over to that repository: https://github.com/GoogleChrome/web.dev/pull/3134


Definitions dialog is no longer visible when hovering the word

The issue was the MouseBlocker node, not sure why it was there 🤔


Modularize core SDK

Is your feature request related to a problem? Please describe.
I would like for the core SDK to be modularized, so I can include in my project only the features I want/use. This would result in smaller binary size, but also it could help avoid crashes caused by some of the (unused) features, like the one described in #678
Describe the solution you'd like
A clear and concise description of what you want to happen.
Separate artifacts for RUM, logs, tracing and crash reporting, something like this:
"com.datadoghq:dd-sdk-android-core:x.x.x" <- main entry point
"com.datadoghq:dd-sdk-android-rum:x.x.x"
"com.datadoghq:dd-sdk-android-logs:x.x.x"
"com.datadoghq:dd-sdk-android-traces:x.x.x"
"com.datadoghq:dd-sdk-android-crash-reporting:x.x.x"
Change DataDog initialization method to something like this:
fun initialize(
    context: Context,
    credentials: Credentials,
    trackingConsent: TrackingConsent,
    vararg features: Feature
)

Which could be used like this:
Datadog.initialize(
    this,
    credentials,
    TrackingConsent.GRANTED,
    Feature.Logs.Builder().build(),
    Feature.RUM.Builder().build(),
    Feature.Tracing.Builder().build(),
)

Hi @eduardb, thanks for the suggestion, indeed this align with some of the improvement we might want to add in the future. This is a huge refactor though, so I can't give you any ETA on when that might come.

Hello @eduardb!
We now have first beta of SDK v2 available which have a better modularization and allows to use individual products without pulling unnecessary code overhead. Please check migration guide for more details.


[Bugfix] Conflict fix

Problem
There are leftover conflict markers that were immaterial to the operation of the app but needed to be removed

thanks.

thanks.


Escaping is broken for $ during substitution in Vim

gives

As the case with Vim, :%s/$/dollar doesn't work either. However search using /\$ works.

You have found a bug in this workaround.
The underlying issue relates to vim's use of searchcursor and zero-width matches. In searchcursor.js line 242 there is code (workaround for vim?) that breaks zero-width matches at end of line boundary.
We can fix the use case above in vim.js, but it'll still fail when $ isn't at the end of the pattern (e.g. (a|$) or $|b). It will also fail for other assertion types. Example :%s/(?<=buffe)r/d/ finds matches and moves the cursor, but doesn’t replace anything or show an error.
Here’s roughly what happens:

searchcursor finds a match, returns the matched substring and position.
vim does a regex replace on the substring. Starts again at position + 1.

With lookahead/lookbehind assertions, the pattern can be larger than the match substring. In these cases the replace method finds no match in the substring. In my example the substring is "r" but the pattern requires "buffer" to do the substitution.
I'm not sure which is more effort: 1) making vim.js work with searchcursor.js, or 2) removing the dependency and workarounds.
Can we change searchcursor to return an empty match if at the line boundary (and somehow avoid matching the same boundary over and over)?

TL;DR Here's a simple patch that'll improve* the workaround:
5069c5069
<           if (regexPart && regexPart[regexPart.length - 1] === '$') {
---
>           if (/(^|[^\\])(\\\\)*\$$/.test(regexPart)) {

@marijnh Would you accept such a pattern?
* Doesn't fix when $ is mid-pattern, or the other assertions. E.g. :s/\b/@/g adds @ at start of words but not at the end.

I don't understand enough of vim, or even our vim bindings, to really provide a well-founded judgement here. So, uh, if this fixes some cases that were previously broken without breaking new cases, I guess I'm okay with it. (If possible, add a test case if you create a PR.)

And I don't know enough about searchcursor (or whatever else depends on it). I'd say effort would be better spent designing/building a new vim module for CM6, then backport that to CM5 once complete enough. Well, that's the dream...
It won't break anything that isn't already broken, so I'll go ahead with a test and PR.


feat(backend): alias in update user info

🍰 Pullrequest

Issues

new defined rule-set find in #2874

Todo

[X] None

I decided not to use the class validator. The overhead to create proper, easy to handle error messages is so high, that it is in no relation to the advantages we may gain.

please find in the decription of this PR a new definition for alias-rules and first elements of blacklist


NotFoundError: Resource localhost/logdir:

Hi
I tried to run the 'train.py' with my data, but it showed below error during epoch 11/20:
File "", line 3, in raise_from
tensorflow.python.framework.errors_impl.NotFoundError: Resource localhost/logdir:logs/mobilenetv22019-04-22/class tensorflow::SummaryWriterInterface does not exist. [Op:WriteScalarSummary]
name: epoch_loss/
Please let me know how I can sove the problem.
Regards

remove tensorboard callback

Thanks. Done.


Programmatically enable/disable dock icon

Enable dock icon for Fullscreen View
Disable otherwise (when just a menu bar agent)

Fixed on Testing Branch


Separate CLI package

I hope this will be received in a positive spirit.
This was requested before: https://github.com/showdownjs/showdown/issues/348
Isn't in clear now why they should be separated?
Yargs is not needed by anyone using this package as a library but it adds 16 dependencies (it and 15 more).
└─┬<EMAIL_ADDRESS>  ├─┬<EMAIL_ADDRESS>  │ ├──<EMAIL_ADDRESS>deduped
  │ ├─┬<EMAIL_ADDRESS>  │ │ └──<EMAIL_ADDRESS>  │ └─┬<EMAIL_ADDRESS>  │   ├─┬<EMAIL_ADDRESS>  │   │ └─┬<EMAIL_ADDRESS>  │   │   └──<EMAIL_ADDRESS>  │   ├──<EMAIL_ADDRESS>deduped
  │   └──<EMAIL_ADDRESS>deduped
  ├──<EMAIL_ADDRESS>  ├──<EMAIL_ADDRESS>  ├──<EMAIL_ADDRESS>  ├─┬<EMAIL_ADDRESS>  │ ├──<EMAIL_ADDRESS>  │ ├──<EMAIL_ADDRESS>  │ └──<EMAIL_ADDRESS>deduped
  ├──<EMAIL_ADDRESS>  └──<EMAIL_ADDRESS>
Every one of those is yet

more possible vulnerabilities
more npm outdated messages
more "needs update" and therefore busy work.
more possible intentional breakage like the recent colors package fiasco
more chances for one of the packages to be compromised and that issue passed on to users of this package.

And multiply all of that by every user of this package as a library (that's 1000s and 1000s of users).
Doesn't seem like it would be better to remove those 15 packages that are not needed by people using this as a library?
As another possibility, you could make showdown-lib (the lib only version) and then either keep showdown as is or make showdown the cli part plus the dependencies on showdown-lib.
Note: I get that I can fork this project and do it myself. I thought I'd ask though before I go do that.

I love the idea. Personally I would prefer to make showdown the  core library and add a new package called showdown-cli. To me it seems the cli is less used then the library itself.

The issue is that the CLI is dependant on some functionalities and implementation details of the main library, it might become a challenge to maintain them in sync. Also, version mismatch might occur.
However, the CLI does not really need yargs.
I think a more favourable approach would be to refactor the CLI, to remove yargs dependency, and keep the libraries together. All yargs is doing is making it easier to create the CLI code boilerplate. Shouldn't be too hard to refactor, since the CLI doesn't implement many commands anyway.

This is fixed in the latest release


Support agg_state in Aggregate Table

Feature request
Request for Future Support of agg_state in Aggregated Table Model.
Hello,
I want to inquire if there are any plans to support agg_state in the aggregated table model. In our case, there is a need for array-type aggregation, and this feature would be highly beneficial.
Thank you for considering this request.

https://github.com/StarRocks/starrocks/issues/49000 pls refer to this issue and its related pr.


Add Blazor WASM debug note

https://github.com/dotnet/aspnetcore/issues/24623#issuecomment-670300570

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

ID: ec2f61c7-9f51-6735-e328-3c7b495d70c3
Version Independent ID: 4d06e565-282d-6387-aa90-cb2c2986d35a
Content: Debug ASP.NET Core Blazor WebAssembly
Content Source: aspnetcore/blazor/debug.md
Product: aspnet-core
Technology: aspnetcore-blazor
GitHub Login: @guardrex
Microsoft Alias: riande

@guardrex One thing that came up today is that we should clarify that this will cause performance issues in the app to account for overhead needed to set up for debugging.

Did u mean to put that here? This issue was about surfacing ...
**Start Without Debugging** (Ctrl+F5) isn't supported.

... or really that "start without" and "start with" do the same thing.

Should I open a new issue?
btw --- Clarify what "this" means.

or really that "start without" and "start with" do the same thing.

Start without and start with do the same thing. The consequence of that is that there is some performance overhead to debugging.

ok ... I'll open a new issue and take care of it by EOD.


:art: command refactoring

Probable minus: a lot of unused variables in IDEA 🤔

@ShuffleZZZ @Shuffle45 kkPowerful


added whole quote sharing feature

#24 solved
@danishzayan Pls confirm everything is good ?

#24 solved @danishzayan Pls confirm everything is good ?

@RohanTheProgrammer After testing i will merge your code...😊

Sorry it took a long time, although it was a small change but I didn't knew the technology so...
Thank you very much for giving me the chance to work on this project I learned a hell lot of new things with this project.
Thank you😄

@RohanTheProgrammer your code has merged...


Add what is opentelemetry page in french

@open-telemetry/docs-fr-approvers @iguitton, @pierrehilbert PTAL!

I think you should remove the lang:pt from this PR to avoid confusion.
I can't approve the PR but looks great to me, thanks for taking into account my suggestions.
@svrnm Should I follow this process by adding both you and @dmathieu to be able to approve this kind of PRs?

I think you should remove the lang:pt from this PR to avoid confusion. I can't approve the PR but looks great to me, thanks for taking into account my suggestions. @svrnm Should I follow this process by adding both you and @dmathieu to be able to approve this kind of PRs?

I'd like to follow the process and stick with the expectations for membership from our guidelines. This means you would need ~5 PRs to be written or reviewed to request membership. The exact number depends on the complexity of the different PRs you helped with.
So what we will do until then is counting your textual reviewes ("lgtm", "looks good to me") as if you have approver status. Just tag me or @open-telemetry/docs-maintainers and one of us can help you with that.


Indicate that user can swipe cells

How to make the first cell to expand and collapse very quickly to help user indicate that he can swipe cell?

Look at the API related to swiping a cell with code.


Update stable version in repo from 0.2.2 to 0.3.0

Think about update stable version to 0.3.0
Version: stable=0.2.2 (338 days old) => latest=0.3.0 (15 days old)
Installs: stable=459 (62.88%), latest=50 (6.85%), total=730
Click to use developer portal
Click to edit
Do not close this issue manually as a new issue will be created if condition for update still exists.
Please drop a comment if any reason exists which blocks updating to version 0.3.0 at this time.
Note: This is an automatically generated message and not personally authored by bluefox!
@mcm1957 for evidence

This issue seems to be outdated.
This issue suggests to update the stable version of this adapter to 0.3.0 but the current stable version is already 0.3.0.
So this issue should be closed.
@mcm1957 for evidence


Il2cpp.module is not being cached and makes dump slower

any call that use it like relativeVirtualAddress on method will try to fetch the module again and can slow full dump from 6s to almost few minutes
no idea if this something wrong with my setup

The caching happens here; are you using Il2Cpp.perform?

oh was not using Il2Cpp.perform when testing so that shouldnt be decorated with lazy ?

but ye it only happens when not using Il2Cpp.perform


Add read-configuration subcommand to output a merged devcontainer configuration

Note: If we implement option 1 from https://github.com/coder/envbuilder/issues/211, we could punt this feature for the time being.
This feature is a pre-requisite for generating a computed devcontainer.json for use by e.g. coder modules. This can help resolve issues like https://github.com/coder/envbuilder/issues/68 where a list of extensions needs to be available during installation of vscode, code-server, etc.
This commands main purpose is to output a merged configuration based on the projects devcontainer.json as well as configuration introduced by features.
A logical approach would be to mimic @devcontainer/cli output. Doing so would make envbuilder a versatile tool for interpreting devcontainer features, and potentially a drop-in single binary alternative.
Here's an example output from @devcontainer/cli when run against the microsoft/vscode repo.

devcontainer read-configuration --include-merged-configuration --log-format json --workspace-folder /tmp/envbuilder/vscode
{
	"configuration": {
		"name": "Code - OSS",
		"build": {"dockerfile": "Dockerfile"},
		"features": {"ghcr.io/devcontainers/features/desktop-lite:1": {}},
		"containerEnv": {"DISPLAY": ""},
		"overrideCommand": false,
		"privileged": true,
		"mounts": [
			{"source": "vscode-dev", "target": "/vscode-dev", "type": "volume"}
		],
		"postCreateCommand": "./.devcontainer/post-create.sh",
		"customizations": {
			"vscode": {
				"settings": {
					"resmon.show.battery": false,
					"resmon.show.cpufreq": false
				},
				"extensions": [
					"dbaeumer.vscode-eslint",
					"EditorConfig.EditorConfig",
					"GitHub.vscode-pull-request-github",
					"ms-vscode.vscode-github-issue-notebooks",
					"ms-vscode.vscode-selfhost-test-provider",
					"mutantdino.resourcemonitor"
				]
			}
		},
		"forwardPorts": [6080, 5901],
		"portsAttributes": {
			"5901": {"label": "VNC TCP port", "onAutoForward": "silent"},
			"6080": {"label": "VNC web client (noVNC)", "onAutoForward": "silent"}
		},
		"hostRequirements": {"memory": "9gb"},
		"configFilePath": {
			"$mid": 1,
			"fsPath": "/tmp/envbuilder/vscode/.devcontainer/devcontainer.json",
			"path": "/tmp/envbuilder/vscode/.devcontainer/devcontainer.json",
			"scheme": "vscode-fileHost"
		}
	},
	"workspace": {
		"workspaceFolder": "/workspaces/vscode",
		"workspaceMount": "type=bind,source=/tmp/envbuilder/vscode,target=/workspaces/vscode"
	},
	"featuresConfiguration": {
		"featureSets": [
			{
				"sourceInformation": {
					"type": "oci",
					"manifest": {
						"schemaVersion": 2,
						"mediaType": "application/vnd.oci.image.manifest.v1+json",
						"config": {
							"mediaType": "application/vnd.devcontainers",
							"digest": "sha256:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855",
							"size": 0
						},
						"layers": [
							{
								"mediaType": "application/vnd.devcontainers.layer.v1+tar",
								"digest": "sha256:9b79df4771f1f348da15db16e84ae640164027b2ea89ea86643394c6c2ff4dad",
								"size": 28160,
								"annotations": {
									"org.opencontainers.image.title": "devcontainer-feature-desktop-lite.tgz"
								}
							}
						],
						"annotations": {"com.github.package.type": "devcontainer_feature"}
					},
					"manifestDigest": "sha256:e7dc4d37ab9e3d6e7ebb221bac741f5bfe07dae47025399d038b17af2ed8ddb7",
					"featureRef": {
						"id": "desktop-lite",
						"owner": "devcontainers",
						"namespace": "devcontainers/features",
						"registry": "ghcr.io",
						"resource": "ghcr.io/devcontainers/features/desktop-lite",
						"path": "devcontainers/features/desktop-lite",
						"version": "1",
						"tag": "1"
					},
					"userFeatureId": "ghcr.io/devcontainers/features/desktop-lite:1",
					"userFeatureIdWithoutVersion": "ghcr.io/devcontainers/features/desktop-lite"
				},
				"features": [
					{
						"id": "desktop-lite",
						"version": "1.0.8",
						"name": "Light-weight Desktop",
						"documentationURL": "https://github.com/devcontainers/features/tree/main/src/desktop-lite",
						"description": "Adds a lightweight Fluxbox based desktop to the container that can be accessed using a VNC viewer or the web. GUI-based commands executed from the built-in VS code terminal will open on the desktop automatically.",
						"options": {
							"version": {
								"type": "string",
								"proposals": ["latest"],
								"default": "latest",
								"description": "Currently Unused!"
							},
							"noVncVersion": {
								"type": "string",
								"proposals": ["1.2.0"],
								"default": "1.2.0",
								"description": "NoVnc Version"
							},
							"password": {
								"type": "string",
								"proposals": ["vscode", "codespaces", "password"],
								"default": "vscode",
								"description": "Enter a password for desktop connections"
							},
							"webPort": {
								"type": "string",
								"proposals": ["6080"],
								"default": "6080",
								"description": "Enter a port for the VNC web client"
							},
							"vncPort": {
								"type": "string",
								"proposals": ["5901"],
								"default": "5901",
								"description": "Enter a port for the desktop VNC server"
							}
						},
						"init": true,
						"entrypoint": "/usr/local/share/desktop-init.sh",
						"containerEnv": {"DISPLAY": ":1"},
						"installsAfter": ["ghcr.io/devcontainers/features/common-utils"],
						"included": true,
						"value": {},
						"cachePath": "/tmp/devcontainercli-coder/container-features/0.60.0-1716804265094/desktop-lite_0",
						"consecutiveId": "desktop-lite_0"
					}
				],
				"internalVersion": "2",
				"computedDigest": "sha256:e7dc4d37ab9e3d6e7ebb221bac741f5bfe07dae47025399d038b17af2ed8ddb7"
			}
		],
		"dstFolder": "/tmp/devcontainercli-coder/container-features/0.60.0-1716804265094"
	},
	"mergedConfiguration": {
		"name": "Code - OSS",
		"build": {"dockerfile": "Dockerfile"},
		"features": {"ghcr.io/devcontainers/features/desktop-lite:1": {}},
		"containerEnv": {"DISPLAY": ""},
		"overrideCommand": false,
		"privileged": true,
		"mounts": [
			{"source": "vscode-dev", "target": "/vscode-dev", "type": "volume"}
		],
		"forwardPorts": [6080, 5901],
		"portsAttributes": {
			"5901": {"label": "VNC TCP port", "onAutoForward": "silent"},
			"6080": {"label": "VNC web client (noVNC)", "onAutoForward": "silent"}
		},
		"hostRequirements": {"cpus": 0, "memory": "9663676416"},
		"configFilePath": {
			"$mid": 1,
			"fsPath": "/tmp/envbuilder/vscode/.devcontainer/devcontainer.json",
			"path": "/tmp/envbuilder/vscode/.devcontainer/devcontainer.json",
			"scheme": "vscode-fileHost"
		},
		"init": true,
		"entrypoints": ["/usr/local/share/desktop-init.sh"],
		"customizations": {
			"vscode": [
				{"extensions": ["dbaeumer.vscode-eslint"]},
				{"extensions": ["dbaeumer.vscode-eslint"]},
				{"extensions": ["dbaeumer.vscode-eslint"]},
				{
					"settings": {
						"resmon.show.battery": false,
						"resmon.show.cpufreq": false
					},
					"extensions": [
						"dbaeumer.vscode-eslint",
						"EditorConfig.EditorConfig",
						"GitHub.vscode-pull-request-github",
						"ms-vscode.vscode-github-issue-notebooks",
						"ms-vscode.vscode-selfhost-test-provider",
						"mutantdino.resourcemonitor"
					]
				}
			]
		},
		"onCreateCommands": [],
		"updateContentCommands": [],
		"postCreateCommands": ["./.devcontainer/post-create.sh"],
		"postStartCommands": [],
		"postAttachCommands": [],
		"remoteUser": "node",
		"remoteEnv": {}
	}
}

Under .configuration the only new field is .configuration.configFilePath. Otherwise this is the project devcontainer.json as-is. The rest: .workspace, .featuresConfiguration and .mergedConfiguration are all added by read-configuration (and the merged config flag).
For this issue, we're mainly interested in implementing .mergedConfiguration.
Reference:

https://github.com/devcontainers/cli/blob/be1f2034e10395f42843ebf26600a42e11e66531/example-usage/tool-vscode-server/start.sh#L11-L11
https://github.com/devcontainers/cli/blob/be1f2034e10395f42843ebf26600a42e11e66531/example-usage/tool-vscode-server/server/init-vscode-server.sh#L38-L42

Logs (for reference)
{"type":"text","level":3,"timestamp":1716804265041,"text":"@devcontainers/cli 0.60.0. Node.js v18.20.2. linux 5.19.17-051917-generic x64."}
{"type":"start","level":2,"timestamp":1716804265041,"text":"Run: git rev-parse --show-cdup"}
{"type":"stop","level":2,"timestamp":1716804265049,"text":"Run: git rev-parse --show-cdup","startTimestamp":1716804265041}
{"type":"start","level":2,"timestamp":1716804265050,"text":"Run: docker ps -q -a --filter label=devcontainer.local_folder=/tmp/envbuilder/vscode --filter label=devcontainer.config_file=/tmp/envbuilder/vscode/.devcontainer/devcontainer.json"}
{"type":"stop","level":2,"timestamp":1716804265072,"text":"Run: docker ps -q -a --filter label=devcontainer.local_folder=/tmp/envbuilder/vscode --filter label=devcontainer.config_file=/tmp/envbuilder/vscode/.devcontainer/devcontainer.json","startTimestamp":1716804265050}
{"type":"start","level":2,"timestamp":1716804265072,"text":"Run: docker ps -q -a --filter label=devcontainer.local_folder=/tmp/envbuilder/vscode"}
{"type":"stop","level":2,"timestamp":1716804265094,"text":"Run: docker ps -q -a --filter label=devcontainer.local_folder=/tmp/envbuilder/vscode","startTimestamp":1716804265072}
{"type":"text","level":1,"timestamp":1716804265095,"text":"workspace root: /tmp/envbuilder/vscode"}
{"type":"text","level":1,"timestamp":1716804265095,"text":"configPath: /tmp/envbuilder/vscode/.devcontainer/devcontainer.json"}
{"type":"text","level":1,"timestamp":1716804265096,"text":"--- Processing User Features ----"}
{"type":"text","level":1,"timestamp":1716804265096,"text":"[* user-provided] ghcr.io/devcontainers/features/desktop-lite:1"}
{"type":"text","level":3,"timestamp":1716804265096,"text":"Resolving Feature dependencies for 'ghcr.io/devcontainers/features/desktop-lite:1'..."}
{"type":"text","level":2,"timestamp":1716804265097,"text":"* Processing feature: ghcr.io/devcontainers/features/desktop-lite:1"}
{"type":"text","level":1,"timestamp":1716804265097,"text":"> input: ghcr.io/devcontainers/features/desktop-lite:1"}
{"type":"text","level":1,"timestamp":1716804265097,"text":">"}
{"type":"text","level":1,"timestamp":1716804265097,"text":"> resource: ghcr.io/devcontainers/features/desktop-lite"}
{"type":"text","level":1,"timestamp":1716804265097,"text":"> id: desktop-lite"}
{"type":"text","level":1,"timestamp":1716804265097,"text":"> owner: devcontainers"}
{"type":"text","level":1,"timestamp":1716804265097,"text":"> namespace: devcontainers/features"}
{"type":"text","level":1,"timestamp":1716804265097,"text":"> registry: ghcr.io"}
{"type":"text","level":1,"timestamp":1716804265097,"text":"> path: devcontainers/features/desktop-lite"}
{"type":"text","level":1,"timestamp":1716804265097,"text":">"}
{"type":"text","level":1,"timestamp":1716804265097,"text":"> version: 1"}
{"type":"text","level":1,"timestamp":1716804265097,"text":"> tag?: 1"}
{"type":"text","level":1,"timestamp":1716804265097,"text":"> digest?: undefined"}
{"type":"text","level":1,"timestamp":1716804265097,"text":"manifest url: https://ghcr.io/v2/devcontainers/features/desktop-lite/manifests/sha256:e7dc4d37ab9e3d6e7ebb221bac741f5bfe07dae47025399d038b17af2ed8ddb7"}
{"type":"text","level":1,"timestamp":1716804265322,"text":"[httpOci] Attempting to authenticate via 'Bearer' auth."}
{"type":"text","level":1,"timestamp":1716804265324,"text":"[httpOci] No authentication credentials found for registry 'ghcr.io' via docker config or credential helper."}
{"type":"text","level":1,"timestamp":1716804265324,"text":"[httpOci] No authentication credentials found for registry 'ghcr.io'. Accessing anonymously."}
{"type":"text","level":1,"timestamp":1716804265324,"text":"[httpOci] Attempting to fetch bearer token from:  https://ghcr.io/token?service=ghcr.io&scope=repository:devcontainers/features/desktop-lite:pull"}
{"type":"text","level":1,"timestamp":1716804265766,"text":"[httpOci] 200 on reattempt after auth: https://ghcr.io/v2/devcontainers/features/desktop-lite/manifests/sha256:e7dc4d37ab9e3d6e7ebb221bac741f5bfe07dae47025399d038b17af2ed8ddb7"}
{"type":"text","level":1,"timestamp":1716804265767,"text":"> input: ghcr.io/devcontainers/features/desktop-lite:1"}
{"type":"text","level":1,"timestamp":1716804265767,"text":">"}
{"type":"text","level":1,"timestamp":1716804265767,"text":"> resource: ghcr.io/devcontainers/features/desktop-lite"}
{"type":"text","level":1,"timestamp":1716804265767,"text":"> id: desktop-lite"}
{"type":"text","level":1,"timestamp":1716804265767,"text":"> owner: devcontainers"}
{"type":"text","level":1,"timestamp":1716804265767,"text":"> namespace: devcontainers/features"}
{"type":"text","level":1,"timestamp":1716804265767,"text":"> registry: ghcr.io"}
{"type":"text","level":1,"timestamp":1716804265767,"text":"> path: devcontainers/features/desktop-lite"}
{"type":"text","level":1,"timestamp":1716804265767,"text":">"}
{"type":"text","level":1,"timestamp":1716804265767,"text":"> version: 1"}
{"type":"text","level":1,"timestamp":1716804265767,"text":"> tag?: 1"}
{"type":"text","level":1,"timestamp":1716804265767,"text":"> digest?: undefined"}
{"type":"text","level":1,"timestamp":1716804265768,"text":"blob url: https://ghcr.io/v2/devcontainers/features/desktop-lite/blobs/sha256:9b79df4771f1f348da15db16e84ae640164027b2ea89ea86643394c6c2ff4dad"}
{"type":"text","level":1,"timestamp":1716804265769,"text":"[httpOci] Applying cachedAuthHeader for registry ghcr.io..."}
{"type":"text","level":1,"timestamp":1716804266117,"text":"[httpOci] 200 (Cached): https://ghcr.io/v2/devcontainers/features/desktop-lite/blobs/sha256:9b79df4771f1f348da15db16e84ae640164027b2ea89ea86643394c6c2ff4dad"}
{"type":"text","level":1,"timestamp":1716804266125,"text":"./ : Directory"}
{"type":"text","level":1,"timestamp":1716804266128,"text":"./NOTES.md : File"}
{"type":"text","level":1,"timestamp":1716804266129,"text":"./README.md : File"}
{"type":"text","level":1,"timestamp":1716804266129,"text":"./devcontainer-feature.json : File"}
{"type":"text","level":1,"timestamp":1716804266129,"text":"./install.sh : File"}
{"type":"text","level":1,"timestamp":1716804266135,"text":"Files extracted from blob: ./NOTES.md, ./README.md, ./devcontainer-feature.json, ./install.sh"}
{"type":"text","level":1,"timestamp":1716804266138,"text":"Found metadata file 'devcontainer-feature.json' in blob"}
{"type":"text","level":2,"timestamp":1716804266139,"text":"* Processing feature: ghcr.io/devcontainers/features/common-utils"}
{"type":"text","level":1,"timestamp":1716804266139,"text":"> input: ghcr.io/devcontainers/features/common-utils"}
{"type":"text","level":1,"timestamp":1716804266139,"text":">"}
{"type":"text","level":1,"timestamp":1716804266139,"text":"> resource: ghcr.io/devcontainers/features/common-utils"}
{"type":"text","level":1,"timestamp":1716804266139,"text":"> id: common-utils"}
{"type":"text","level":1,"timestamp":1716804266139,"text":"> owner: devcontainers"}
{"type":"text","level":1,"timestamp":1716804266139,"text":"> namespace: devcontainers/features"}
{"type":"text","level":1,"timestamp":1716804266139,"text":"> registry: ghcr.io"}
{"type":"text","level":1,"timestamp":1716804266139,"text":"> path: devcontainers/features/common-utils"}
{"type":"text","level":1,"timestamp":1716804266139,"text":">"}
{"type":"text","level":1,"timestamp":1716804266139,"text":"> version: latest"}
{"type":"text","level":1,"timestamp":1716804266139,"text":"> tag?: latest"}
{"type":"text","level":1,"timestamp":1716804266139,"text":"> digest?: undefined"}
{"type":"text","level":1,"timestamp":1716804266139,"text":"manifest url: https://ghcr.io/v2/devcontainers/features/common-utils/manifests/latest"}
{"type":"text","level":1,"timestamp":1716804266139,"text":"[httpOci] Applying cachedAuthHeader for registry ghcr.io..."}
{"type":"text","level":1,"timestamp":1716804266380,"text":"[httpOci] 200 (Cached): https://ghcr.io/v2/devcontainers/features/common-utils/manifests/latest"}
{"type":"text","level":1,"timestamp":1716804266380,"text":"> input: ghcr.io/devcontainers/features/common-utils"}
{"type":"text","level":1,"timestamp":1716804266380,"text":">"}
{"type":"text","level":1,"timestamp":1716804266380,"text":"> resource: ghcr.io/devcontainers/features/common-utils"}
{"type":"text","level":1,"timestamp":1716804266380,"text":"> id: common-utils"}
{"type":"text","level":1,"timestamp":1716804266380,"text":"> owner: devcontainers"}
{"type":"text","level":1,"timestamp":1716804266380,"text":"> namespace: devcontainers/features"}
{"type":"text","level":1,"timestamp":1716804266380,"text":"> registry: ghcr.io"}
{"type":"text","level":1,"timestamp":1716804266380,"text":"> path: devcontainers/features/common-utils"}
{"type":"text","level":1,"timestamp":1716804266380,"text":">"}
{"type":"text","level":1,"timestamp":1716804266380,"text":"> version: latest"}
{"type":"text","level":1,"timestamp":1716804266380,"text":"> tag?: latest"}
{"type":"text","level":1,"timestamp":1716804266380,"text":"> digest?: undefined"}
{"type":"text","level":1,"timestamp":1716804266381,"text":"[* resolved worklist] ghcr.io/devcontainers/features/desktop-lite:1"}
{"type":"text","level":1,"timestamp":1716804266381,"text":"[\n  {\n    \"type\": \"user-provided\",\n    \"userFeatureId\": \"ghcr.io/devcontainers/features/desktop-lite:1\",\n    \"options\": {},\n    \"dependsOn\": [],\n    \"installsAfter\": [\n      {\n        \"type\": \"resolved\",\n        \"userFeatureId\": \"ghcr.io/devcontainers/features/common-utils\",\n        \"options\": {},\n        \"featureSet\": {\n          \"sourceInformation\": {\n            \"type\": \"oci\",\n            \"manifest\": {\n              \"schemaVersion\": 2,\n              \"mediaType\": \"application/vnd.oci.image.manifest.v1+json\",\n              \"config\": {\n                \"mediaType\": \"application/vnd.devcontainers\",\n                \"digest\": \"sha256:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855\",\n                \"size\": 0\n              },\n              \"layers\": [\n                {\n                  \"mediaType\": \"application/vnd.devcontainers.layer.v1+tar\",\n                  \"digest\": \"sha256:d846c58d563c29194c84f0af63fcfdef7b9c27982e9c974e0eff94c48fb89c4b\",\n                  \"size\": 47104,\n                  \"annotations\": {\n                    \"org.opencontainers.image.title\": \"devcontainer-feature-common-utils.tgz\"\n                  }\n                }\n              ],\n              \"annotations\": {\n                \"dev.containers.metadata\": \"{\\\"id\\\":\\\"common-utils\\\",\\\"version\\\":\\\"2.4.3\\\",\\\"name\\\":\\\"Common Utilities\\\",\\\"documentationURL\\\":\\\"https://github.com/devcontainers/features/tree/main/src/common-utils\\\",\\\"description\\\":\\\"Installs a set of common command line utilities, Oh My Zsh!, and sets up a non-root user.\\\",\\\"options\\\":{\\\"installZsh\\\":{\\\"type\\\":\\\"boolean\\\",\\\"default\\\":true,\\\"description\\\":\\\"Install ZSH?\\\"},\\\"configureZshAsDefaultShell\\\":{\\\"type\\\":\\\"boolean\\\",\\\"default\\\":false,\\\"description\\\":\\\"Change default shell to ZSH?\\\"},\\\"installOhMyZsh\\\":{\\\"type\\\":\\\"boolean\\\",\\\"default\\\":true,\\\"description\\\":\\\"Install Oh My Zsh!?\\\"},\\\"installOhMyZshConfig\\\":{\\\"type\\\":\\\"boolean\\\",\\\"default\\\":true,\\\"description\\\":\\\"Allow installing the default dev container .zshrc templates?\\\"},\\\"upgradePackages\\\":{\\\"type\\\":\\\"boolean\\\",\\\"default\\\":true,\\\"description\\\":\\\"Upgrade OS packages?\\\"},\\\"username\\\":{\\\"type\\\":\\\"string\\\",\\\"proposals\\\":[\\\"devcontainer\\\",\\\"vscode\\\",\\\"codespace\\\",\\\"none\\\",\\\"automatic\\\"],\\\"default\\\":\\\"automatic\\\",\\\"description\\\":\\\"Enter name of a non-root user to configure or none to skip\\\"},\\\"userUid\\\":{\\\"type\\\":\\\"string\\\",\\\"proposals\\\":[\\\"1001\\\",\\\"automatic\\\"],\\\"default\\\":\\\"automatic\\\",\\\"description\\\":\\\"Enter UID for non-root user\\\"},\\\"userGid\\\":{\\\"type\\\":\\\"string\\\",\\\"proposals\\\":[\\\"1001\\\",\\\"automatic\\\"],\\\"default\\\":\\\"automatic\\\",\\\"description\\\":\\\"Enter GID for non-root user\\\"},\\\"nonFreePackages\\\":{\\\"type\\\":\\\"boolean\\\",\\\"default\\\":false,\\\"description\\\":\\\"Add packages from non-free Debian repository? (Debian only)\\\"}}}\",\n                \"com.github.package.type\": \"devcontainer_feature\"\n              }\n            },\n            \"manifestDigest\": \"sha256:e9e1d402031416ed5fc500f242c27ffa1043a27b5ba612e6596ea62503c8ae70\",\n            \"featureRef\": {\n              \"id\": \"common-utils\",\n              \"owner\": \"devcontainers\",\n              \"namespace\": \"devcontainers/features\",\n              \"registry\": \"ghcr.io\",\n              \"resource\": \"ghcr.io/devcontainers/features/common-utils\",\n              \"path\": \"devcontainers/features/common-utils\",\n              \"version\": \"latest\",\n              \"tag\": \"latest\"\n            },\n            \"userFeatureId\": \"ghcr.io/devcontainers/features/common-utils\",\n            \"userFeatureIdWithoutVersion\": \"ghcr.io/devcontainers/features/common-utils\"\n          },\n          \"features\": [\n            {\n              \"id\": \"common-utils\",\n              \"included\": true,\n              \"value\": {}\n            }\n          ]\n        },\n        \"dependsOn\": [],\n        \"installsAfter\": [],\n        \"roundPriority\": 0,\n        \"featureIdAliases\": [\n          \"common-utils\"\n        ]\n      }\n    ],\n    \"roundPriority\": 0,\n    \"featureSet\": {\n      \"sourceInformation\": {\n        \"type\": \"oci\",\n        \"manifest\": {\n          \"schemaVersion\": 2,\n          \"mediaType\": \"application/vnd.oci.image.manifest.v1+json\",\n          \"config\": {\n            \"mediaType\": \"application/vnd.devcontainers\",\n            \"digest\": \"sha256:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855\",\n            \"size\": 0\n          },\n          \"layers\": [\n            {\n              \"mediaType\": \"application/vnd.devcontainers.layer.v1+tar\",\n              \"digest\": \"sha256:9b79df4771f1f348da15db16e84ae640164027b2ea89ea86643394c6c2ff4dad\",\n              \"size\": 28160,\n              \"annotations\": {\n                \"org.opencontainers.image.title\": \"devcontainer-feature-desktop-lite.tgz\"\n              }\n            }\n          ],\n          \"annotations\": {\n            \"com.github.package.type\": \"devcontainer_feature\"\n          }\n        },\n        \"manifestDigest\": \"sha256:e7dc4d37ab9e3d6e7ebb221bac741f5bfe07dae47025399d038b17af2ed8ddb7\",\n        \"featureRef\": {\n          \"id\": \"desktop-lite\",\n          \"owner\": \"devcontainers\",\n          \"namespace\": \"devcontainers/features\",\n          \"registry\": \"ghcr.io\",\n          \"resource\": \"ghcr.io/devcontainers/features/desktop-lite\",\n          \"path\": \"devcontainers/features/desktop-lite\",\n          \"version\": \"1\",\n          \"tag\": \"1\"\n        },\n        \"userFeatureId\": \"ghcr.io/devcontainers/features/desktop-lite:1\",\n        \"userFeatureIdWithoutVersion\": \"ghcr.io/devcontainers/features/desktop-lite\"\n      },\n      \"features\": [\n        {\n          \"id\": \"desktop-lite\",\n          \"included\": true,\n          \"value\": {},\n          \"version\": \"1.0.8\",\n          \"name\": \"Light-weight Desktop\",\n          \"documentationURL\": \"https://github.com/devcontainers/features/tree/main/src/desktop-lite\",\n          \"description\": \"Adds a lightweight Fluxbox based desktop to the container that can be accessed using a VNC viewer or the web. GUI-based commands executed from the built-in VS code terminal will open on the desktop automatically.\",\n          \"options\": {\n            \"version\": {\n              \"type\": \"string\",\n              \"proposals\": [\n                \"latest\"\n              ],\n              \"default\": \"latest\",\n              \"description\": \"Currently Unused!\"\n            },\n            \"noVncVersion\": {\n              \"type\": \"string\",\n              \"proposals\": [\n                \"1.2.0\"\n              ],\n              \"default\": \"1.2.0\",\n              \"description\": \"NoVnc Version\"\n            },\n            \"password\": {\n              \"type\": \"string\",\n              \"proposals\": [\n                \"vscode\",\n                \"codespaces\",\n                \"password\"\n              ],\n              \"default\": \"vscode\",\n              \"description\": \"Enter a password for desktop connections\"\n            },\n            \"webPort\": {\n              \"type\": \"string\",\n              \"proposals\": [\n                \"6080\"\n              ],\n              \"default\": \"6080\",\n              \"description\": \"Enter a port for the VNC web client\"\n            },\n            \"vncPort\": {\n              \"type\": \"string\",\n              \"proposals\": [\n                \"5901\"\n              ],\n              \"default\": \"5901\",\n              \"description\": \"Enter a port for the desktop VNC server\"\n            }\n          },\n          \"init\": true,\n          \"entrypoint\": \"/usr/local/share/desktop-init.sh\",\n          \"containerEnv\": {\n            \"DISPLAY\": \":1\"\n          },\n          \"installsAfter\": [\n            \"ghcr.io/devcontainers/features/common-utils\"\n          ]\n        }\n      ]\n    },\n    \"featureIdAliases\": [\n      \"desktop-lite\"\n    ]\n  }\n]"}
{"type":"text","level":1,"timestamp":1716804266382,"text":"[raw worklist]: ghcr.io/devcontainers/features/desktop-lite:1"}
{"type":"text","level":3,"timestamp":1716804266382,"text":"Soft-dependency 'ghcr.io/devcontainers/features/common-utils' is not required.  Removing from installation order..."}
{"type":"text","level":1,"timestamp":1716804266382,"text":"[worklist-without-dangling-soft-deps]: ghcr.io/devcontainers/features/desktop-lite:1"}
{"type":"text","level":1,"timestamp":1716804266382,"text":"Starting round-based Feature install order calculation from worklist..."}
{"type":"text","level":1,"timestamp":1716804266382,"text":"\n[round] ghcr.io/devcontainers/features/desktop-lite:1"}
{"type":"text","level":1,"timestamp":1716804266382,"text":"[round-candidates] ghcr.io/devcontainers/features/desktop-lite:1 (0)"}
{"type":"text","level":1,"timestamp":1716804266382,"text":"[round-after-filter-priority] (maxPriority=0) ghcr.io/devcontainers/features/desktop-lite:1 (0)"}
{"type":"text","level":1,"timestamp":1716804266383,"text":"[round-after-comparesTo] ghcr.io/devcontainers/features/desktop-lite:1"}
{"type":"text","level":1,"timestamp":1716804266383,"text":"--- Fetching User Features ----"}
{"type":"text","level":2,"timestamp":1716804266383,"text":"* Fetching feature: desktop-lite_0_oci"}
{"type":"text","level":1,"timestamp":1716804266383,"text":"Fetching from OCI"}
{"type":"text","level":1,"timestamp":1716804266384,"text":"blob url: https://ghcr.io/v2/devcontainers/features/desktop-lite/blobs/sha256:9b79df4771f1f348da15db16e84ae640164027b2ea89ea86643394c6c2ff4dad"}
{"type":"text","level":1,"timestamp":1716804266384,"text":"[httpOci] Applying cachedAuthHeader for registry ghcr.io..."}
{"type":"text","level":1,"timestamp":1716804266615,"text":"[httpOci] 200 (Cached): https://ghcr.io/v2/devcontainers/features/desktop-lite/blobs/sha256:9b79df4771f1f348da15db16e84ae640164027b2ea89ea86643394c6c2ff4dad"}
{"type":"text","level":1,"timestamp":1716804266617,"text":"./ : Directory"}
{"type":"text","level":1,"timestamp":1716804266617,"text":"./NOTES.md : File"}
{"type":"text","level":1,"timestamp":1716804266618,"text":"./README.md : File"}
{"type":"text","level":1,"timestamp":1716804266618,"text":"./devcontainer-feature.json : File"}
{"type":"text","level":1,"timestamp":1716804266618,"text":"./install.sh : File"}
{"type":"text","level":1,"timestamp":1716804266621,"text":"Files extracted from blob: ./NOTES.md, ./README.md, ./devcontainer-feature.json, ./install.sh"}
{"type":"text","level":2,"timestamp":1716804266623,"text":"* Fetched feature: desktop-lite_0_oci version 1.0.8"}
{"type":"start","level":2,"timestamp":1716804266682,"text":"Run: docker inspect --type image mcr.microsoft.com/devcontainers/typescript-node:18-bookworm"}
{"type":"stop","level":2,"timestamp":1716804266705,"text":"Run: docker inspect --type image mcr.microsoft.com/devcontainers/typescript-node:18-bookworm","startTimestamp":1716804266682}
{"type":"text","level":1,"timestamp":1716804266706,"text":"> input: mcr.microsoft.com/devcontainers/typescript-node:18-bookworm"}
{"type":"text","level":1,"timestamp":1716804266706,"text":">"}
{"type":"text","level":1,"timestamp":1716804266706,"text":"> resource: mcr.microsoft.com/devcontainers/typescript-node"}
{"type":"text","level":1,"timestamp":1716804266706,"text":"> id: typescript-node"}
{"type":"text","level":1,"timestamp":1716804266706,"text":"> owner: devcontainers"}
{"type":"text","level":1,"timestamp":1716804266706,"text":"> namespace: devcontainers"}
{"type":"text","level":1,"timestamp":1716804266706,"text":"> registry: mcr.microsoft.com"}
{"type":"text","level":1,"timestamp":1716804266706,"text":"> path: devcontainers/typescript-node"}
{"type":"text","level":1,"timestamp":1716804266706,"text":">"}
{"type":"text","level":1,"timestamp":1716804266706,"text":"> version: 18-bookworm"}
{"type":"text","level":1,"timestamp":1716804266706,"text":"> tag?: 18-bookworm"}
{"type":"text","level":1,"timestamp":1716804266706,"text":"> digest?: undefined"}
{"type":"text","level":1,"timestamp":1716804266706,"text":"manifest url: https://mcr.microsoft.com/v2/devcontainers/typescript-node/manifests/18-bookworm"}
{"type":"text","level":1,"timestamp":1716804266932,"text":"[httpOci] 404 (NoAuth): https://mcr.microsoft.com/v2/devcontainers/typescript-node/manifests/18-bookworm"}
{"type":"text","level":1,"timestamp":1716804266932,"text":"Did not fetch target with expected mimetype 'application/vnd.docker.distribution.manifest.v2+json': {\"errors\":[{\"code\":\"MANIFEST_UNKNOWN\",\"message\":\"OCI index found, but accept header does not support OCI indexes\"}]}\n"}
{"type":"text","level":1,"timestamp":1716804267105,"text":"[httpOci] 200 (NoAuth): https://mcr.microsoft.com/v2/devcontainers/typescript-node/manifests/18-bookworm"}
{"type":"text","level":1,"timestamp":1716804267105,"text":"Fetched: {\n    \"schemaVersion\": 2,\n    \"mediaType\": \"application/vnd.oci.image.index.v1+json\",\n    \"manifests\": [\n        {\n            \"mediaType\": \"application/vnd.oci.image.manifest.v1+json\",\n            \"digest\": \"sha256:a3193b69f2d1f0ce6d6511b85c913579c17f4e7fe0ad8fb71c3d53c717580f6b\",\n            \"size\": 4485,\n            \"platform\": {\n                \"architecture\": \"amd64\",\n                \"os\": \"linux\"\n            }\n        },\n        {\n            \"mediaType\": \"application/vnd.oci.image.manifest.v1+json\",\n            \"digest\": \"sha256:e9a4f6e413715d8989a0fa381b6b3fb3144d15d729367cb0fd4cda6b3e4544e9\",\n            \"size\": 4485,\n            \"platform\": {\n                \"architecture\": \"arm64\",\n                \"os\": \"linux\"\n            }\n        },\n        {\n            \"mediaType\": \"application/vnd.oci.image.manifest.v1+json\",\n            \"digest\": \"sha256:73d619643bd152d04f7fa9f777f2825633a529e278e5c2bdc2e438feecf15daa\",\n            \"size\": 566,\n            \"annotations\": {\n                \"vnd.docker.reference.digest\": \"sha256:a3193b69f2d1f0ce6d6511b85c913579c17f4e7fe0ad8fb71c3d53c717580f6b\",\n                \"vnd.docker.reference.type\": \"attestation-manifest\"\n            },\n            \"platform\": {\n                \"architecture\": \"unknown\",\n                \"os\": \"unknown\"\n            }\n        },\n        {\n            \"mediaType\": \"application/vnd.oci.image.manifest.v1+json\",\n            \"digest\": \"sha256:3375f4eed28c1b8a3082b8a0d9d6f0e3ed74c32d67a2e319e22a84ed97c289c7\",\n            \"size\": 566,\n            \"annotations\": {\n                \"vnd.docker.reference.digest\": \"sha256:e9a4f6e413715d8989a0fa381b6b3fb3144d15d729367cb0fd4cda6b3e4544e9\",\n                \"vnd.docker.reference.type\": \"attestation-manifest\"\n            },\n            \"platform\": {\n                \"architecture\": \"unknown\",\n                \"os\": \"unknown\"\n            }\n        }\n    ]\n}"}
{"type":"text","level":1,"timestamp":1716804267426,"text":"[httpOci] 200 (NoAuth): https://mcr.microsoft.com/v2/devcontainers/typescript-node/manifests/sha256:a3193b69f2d1f0ce6d6511b85c913579c17f4e7fe0ad8fb71c3d53c717580f6b"}
{"type":"text","level":1,"timestamp":1716804267426,"text":"blob url: https://mcr.microsoft.com/v2/devcontainers/typescript-node/blobs/sha256:e01bfe3472dd64911ad4c13469b9400de923cdc3fc11367aef217cf5bab01988"}
{"type":"text","level":1,"timestamp":1716804267944,"text":"[httpOci] 200 (NoAuth): https://mcr.microsoft.com/v2/devcontainers/typescript-node/blobs/sha256:e01bfe3472dd64911ad4c13469b9400de923cdc3fc11367aef217cf5bab01988"}

@mafredri Would this achieve something similar to what I'm currently doing in a sidecar container? I would love to help implement this but don't really know whether you are looking for outside help on these
My current solution for this:
https://github.com/onezerocompany/devcontainers/blob/8c21304f76548d711bba2abe00b3d9f4baa73c33/images/settings-gen/gen.sh#L21


Contact Form Problem and solution

I saw that there were a lot of comments on the contact.php form and not being able to submit. I also had this problem and after a handful of hours trying to find a solution, I went ahead and just went with formspree.io instead of the contact.php.
For future developers using this theme who encounter this problem. Just comment out the existing form and then add this. Once you've taken the 5 minutes to verify with formspree, this should work.
      <form action="https://formspree.io/YOUR_EMAIL" method="POST" />

            Name
            <input class="form-control" id="name" type="text" placeholder="Name" required="required" data-validation-required-message="Please enter your name.">

            Email Address
            <input class="form-control" id="email" type="email" placeholder="Email Address" required="required" data-validation-required-message="Please enter your email address.">

            Message
            <textarea class="form-control" id="message" rows="5" placeholder="Message" required="required" data-validation-required-message="Please enter a message."></textarea>

          <button type="submit" class="btn btn-primary btn-xl" id="sendMessageButton">Send</button>

      </form>

formspree needs to have the name element in each input to be included in the message that is forwarded.
so for example
            <textarea class="form-control" id="message" rows="5" placeholder="Message" required="required" data-validation-required-message="Please enter a message."></textarea>

needs to be
            <textarea class="form-control" id="message" rows="5" placeholder="Message" required="required" data-validation-required-message="Please enter a message." name="message"></textarea>

after that thought it works great, thanks for the tip.

Keeping this open since it's an important way around using the PHP mailer that is included with this theme.
If you're trying to use the PHP mailer and it's not working after you upload it to your web server, it could be a problem that is outlined here on this post on StackOverflow https://stackoverflow.com/questions/24644436/php-mail-function-doesnt-complete-sending-of-e-mail
If your server doesn't support sending mail, for example, if you're hosting your site on GitHub Pages, then Formspree is an excellent solution.

Hello! I came up with this issue today and fixed it by changing the code on line #23 of contact_me.js from:url: “contact_me.php”, to:  url: "././assets/mail/contact_me.php”,
And now the form works in my server.

Hello! I came up with this issue today and fixed it by changing the code on line #23 of contact_me.js from:url: “contact_me.php”, to: url: "././assets/mail/contact_me.php”,
And now the form works in my server.

It indeed works. I tested it too. Thanks a lot. So many people missed this simple error.

formspree needs to have the name element in each input to be included in the message that is forwarded.
so for example
<textarea class="form-control" id="message" rows="5" placeholder="Message" required="required" data-validation-required-message="Please enter a message."></textarea>

needs to be
<textarea name="message" class="form-control" id="message" rows="5" placeholder="Message" required="required" data-validation-required-message="Please enter a message." ></textarea>

after that thought it works great, thanks for the tip.

Would be useful to change the code in the original issue, are these editable?

At this point in time, the free tier for Formspree is a lot more limited than it once was. There are a lot of ways to add forms to static sites at this point in time, and I am considering dropping the 'working form functionality' from the theme all together in the upcoming Bootstrap 5 compatible version.
The PHP scripts with jQuery validation is becoming more and more antiquated, and it's a difficult thing to provide troubleshooting and support for. Instead we may set up an article or guide on the various techniques one could use to add functionality to a form.

Formspree is recommending a change in endpoint destination as the legacy form is no longer supported. I updated the index form and removed the contact-me.php file.  I can get it to work locally however, at first load the code will revert back to original instead of initially loading my changes.  When I change in back and refresh it works. Below is what I am trying to get the form to do but it is getting overwritten during the build phase (i'm assuming) somehow.  Suggestions to get it working correctly?

Contact Us

Name

Email Address

Phone Number

Message

Send

I was having a lot of issues getting the formspree form to work. I needed to make a formspree account (free). Then cope the end point HTML code and implant in the action section however, I was only updating the index file. There were about 3 separate files including some or all portions of the contact form that needed to be updated and committed with intended code for it work. Hopefully this helps some other novice that is banging their head against a wall currently.

Either using formspree.  Or you can create your own smtp service powered by Nodemailer/NodeJS or similar in the backend to run on a free cloud hosting server like Heroku/Render to proxy off your nominated free SMTP server of your choice ie Hotmail, Gmail, Yahoo etc. And all you can do with your contact form is to point the form submit endpoint to your NodeJS smtp service to run it.  You're good to go.
You'll learn more to setup this way.


Tested with ARM

Tested with ARM
Change default shaoe to E4.Flex
Added ability to control operator state

May i know the default shape will be E4 or A1.? In variables A1 is set as default but in doc and terraform.tfvars E4 is set as default.

I think we'll keep to E4 for now


Custom Transformation - AtlasMapUI

Hi ,
we are trying to import some custom jar into Atlas Map UI [2.2.3] , the mapping works fine in UI but gives a Null pointer exception while calling the atlasmap component  inside the code .

Steps to Reproduce the issue -->

Clone this Repository https://github.com/sahilsethi12/custom-java-trasnformer
Import existing adm file [ atlasmap-mapping-jsontoxml.adm , currently working to transform  json to xml without custom transformation ] .
Import the custom jar [ creating custom jar ----> Clone this repo https://github.com/sahilsethi12/custom-java-trasnformer and run mvn clean install and jar created inside directory upload the .jar in the UI ]
Once You Import the jar u can see the same java class inside the transformation drop down , map for any field and see the results by clicking  on the preview section and confirm the output [screenshot working_ui.png attached ]
Now click on export a new .adm file
Now call this new custom .adm file inside the code and  check the error [already posted in read me file in the same repo]

Can you also upload the reproducer to run your mapping? through camel-atlasmap or invoking AtlasMap runtime API directly? What's the code exactly?

@igarashitm There's a camel route written :

@igarashitm updated the code in  https://github.com/sahilsethi12/custom-java-trasnformer/blob/main/README.md

Nope not enough, please demonstrate how did you build your camel app and run it

One random guess, did you put custom transformation and service declaration files into the classpath of your camel app? it won't load from .adm file

Also this is fishy Invalid serialized mapping definition content detected, discarding - can you enable debug log for io.atlasmap and find more clue?

@igarashitm Please find my comments inline :
Nope not enough, please demonstrate how did you build your camel app and run it ---> Basically we are running camel app as a spring boot application , and running Application.java class
You can find the complete code --> https://github.com/sahilsethi12/camel-atlasmap-poc
One random guess, did you put custom transformation and service declaration files into the classpath of your camel app? it won't load from .adm file --> yes custom transformation and service declaration files are not in classpath of camel application , What exactly  needs to add , can you please guide here ??
Also this is fishy Invalid serialized mapping definition content detected, discarding - can you enable debug log for io.atlasmap and find more clue? Sure will do that


Redundant data in anagram.json?

In exercism/xphp#74 @petemcfarlane noted that we have redundant data in the anagram.json.
Should we remove the redundant cases? Do they serve a particular purpose, e.g. triangulation?

22! That's a lot of tests. How many edge cases can there be for an anagram?
Rust has 11 tests. That seemed fine. Though I imagine most people have a working solution well before they hit their 11th test.
After quickly glancing at the current json file, the following jump out as candidates for removal

https://github.com/exercism/x-common/blob/master/anagram.json#L60
https://github.com/exercism/x-common/blob/master/anagram.json#L77
https://github.com/exercism/x-common/blob/master/anagram.json#L78
https://github.com/exercism/x-common/blob/master/anagram.json#L102
https://github.com/exercism/x-common/blob/master/anagram.json#L129
https://github.com/exercism/x-common/blob/master/anagram.json#L135

A closer inspection would probably turn up more.

I might have some students pair on this, for the experience.  Let me find out if I can get some takers... Good subject matter anyway.

+1 for having students work on it. It's a great first/early patch.


Binomial distribution

split from #1177.
I implemented binomial distribution.

Jenkins CI test (for commit 0b225d3edab4af29453d84785c95a635d98bc5a4) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

Jenkins CI test (for commit c4a5fa031ddfc32fa0f3bd7d13bb174490f25374) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

Jenkins CI test (for commit 861ab5414615c30e8518dfc7ffac8c550039497a) succeeded without errors!

very happy!

LGTM!


fix: savers withdraw percent safety factor

Description

Notice

[ ] Have you followed the guidelines in our Contributing guide?
[ ] Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Pull Request Type

[ ] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[ ] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[ ] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)

closes #
Risk

Testing

Engineering

Operations

Screenshots (if applicable)

Current dependencies on/for this PR:

develop

PR #3701   👈

This comment was auto-generated by Graphite.

Admin merging as effectively approved in https://github.com/shapeshift/web/pull/3703#issuecomment-1407214011


read token expire date from settings

Default token expire period is still two days, while this commit let user change this behavior in settings by changing value of PASSWORD_RESET_TOKEN_EXPIRES in seconds.

Thanks! Done in https://github.com/brutasse/django-password-reset/commit/28bbe2e6323c6ed9d184285b3221686d58ece6ef and available in version 0.9 on PyPI.


Update Ollama for Aspre 9

For the Aspire 9 release of the Ollama Community Toolkit integrations we have quite a large overhaul coming (see https://github.com/CommunityToolkit/Aspire/discussions/194).
The docs here need to be updated to reflect those changes.

Would you mind deleting this issue and instead creating a breaking-change issue, based on this template please?


Use BIP39 passphrase to encrypt plaintext mnemonic

This is what samurai wallet uses and I think its a user-friendly and effective way to secure the mnemonic.

fixed in #80


fix(rollup): only enable chain-monitor in rollup-relayer

Purpose or design rationale of this PR
Yet another config decoupling PR, before this PR, will cause a nil pointer error without chain-monitor configs, after this PR gas-oracle won't need chain-monitor configs in config.json.
PR title
Your PR title must follow conventional commits (as we are doing squash merge for each PR), so it must start with one of the following types:

[x] fix: A bug fix

Deployment tag versioning
Has tag in common/version.go been updated or have you added bump-version label to this PR?

[x] Yes

Breaking change label
Does this PR have the breaking-change label?

[x] No, this PR is not a breaking change

Summary by CodeRabbit

Bug Fixes

Improved the initialization logic for the chain monitor client, ensuring it activates only for the relevant service type, which may enhance performance and reduce unnecessary resource usage.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 52.06%. Comparing base (968a396) to head (6f14041).

Additional details and impacted files
@@           Coverage Diff            @@
##           develop    #1569   +/-   ##
========================================
  Coverage    52.06%   52.06%
========================================
  Files          157      157
  Lines        12472    12472
========================================
  Hits          6494     6494
  Misses        5418     5418
  Partials       560      560

Flag
Coverage Δ

rollup
57.15% <100.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.


Main Material Site does not function in Firefox

When going to the https://material-ui.com/ sometimes the site is not functional

[x] This is a v1.x issue (v0.x is no longer maintained).
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

I load the Documentation site in Firefox, and the drawer on the left opens
Current Behavior

When I click on the hamburger, nothing happens. I get the following in the console
Loading failed for the <script> with source “https://material-ui.com/_next/55ccf6e1-9d1b-4119-8d87-068f098ba238/page/_app.js”.
material-ui.com:38
Loading failed for the <script> with source “https://material-ui.com/_next/55ccf6e1-9d1b-4119-8d87-068f098ba238/page/_error.js”.
material-ui.com:38
Loading failed for the <script> with source “https://material-ui.com/_next/static/commons/main-a152ab07849ea9fef63e.js”.
material-ui.com:38
Loading failed for the <script> with source “https://material-ui.com/_next/55ccf6e1-9d1b-4119-8d87-068f098ba238/page/index.js”.
material-ui.com:38

Note: This does not always happens, but when it does work I see no errors in the console
Steps to Reproduce (for bugs)

Go to https://material-ui.com/ with Firefox
If you see the above console errors, the hamburger will not work

Context

I need to switch to Chrome to read the docs.
Your Environment

Tech
Version

FireFox
60.0.2

what version of firefox are you using?

I found a similar issue on stack overflow (here)... in that case the problem was caused by a browser extension
You could try running Firefox in safe mode and see if the problem still occurs.

@zdrummond You might have an issue with the service workers. Try clearing the cache :/.


Add a travis worker with sge

Here some references:

https://scidom.wordpress.com/2012/01/18/sge-on-single-pc/
https://gist.github.com/dan-blanchard/6586533
https://github.com/drmaa-python/drmaa-python/blob/master/travis/install_sge.sh

It will probably require to do some conditional matrix travis worker as done in scikit-learn https://github.com/scikit-learn/scikit-learn/blob/master/.travis.yml

It will probably require to do some conditional matrix travis worker as done in scikit-learn https://github.com/scikit-learn/scikit-learn/blob/master/.travis.yml

This is done in 53330787d33be4b27d474d98cfea58053727734f

Done in #22

:beers: :


Add specs for single invoice download

Notion card
Summary

Added specs for a single invoice download.
Functionality PR-
https://github.com/saeloun/miru-web/pull/780

Preview

Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to
not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?

Checklist:

[ ] I have manually tested all workflows
[ ] I have performed a self-review of my own code
[ ] I have added automated tests for my code

Please resolve conflicts.


feat: add kademlia peer reachability status

This change is

Draft PR, the code was moved to #2564


[NEMO-440] Migrate to Java11 and use Java 11 Features

JIRA: NEMO-440: Migrate to Java11 and use Java 11 Features
Major changes:

Upgrade POM and modify travis to check Java 11

Minor changes to note:

None

Tests for the changes:

None

Other comments:

None

Closes #291

@johnyangk Could you take a look at the PR? It's super simple 😄

I guess Java 10 and below (including Java 8) are no longer supported by Nemo? I am neutral on this, but it might be helpful to send an email to the Nemo mailing list about dropping Java 8 support to give a heads up before proceeding? (since perhaps not all of the folks in the community are following each github issue)

Sure, that would be a good idea. I'll seek for opinions.

@johnyangk Here are a few replies on the email thread. I also think that it would be nice to move forward. 😄


Rename WebView postMessage method to postMessageNative.

Rename WebView postMessage to postMessageNative. The old name "postMessage" breaks the functional of some scripts in WebView using cross-domain communication via postMessage. Example: https://api-maps.yandex.ru/2.1/?lang=ru_RU
Motivation (required)
The old name "postMessage" breaks the functional of some scripts in WebView using cross-domain communication via postMessage. This bug avalible if WebView has onMessage callback.
Test Plan (required)
Not working

Working

Send message to react-native WebView - window.postMessageNative("data", "*");
Replace original window.postMessage - bad idea;

This bag avalible only if WebVev has onMessage callback

I think something like window.rnBridge.postMessage would be preferable. It would also let you use the  built-inJavascriptInterface directly on Android. The current implementation is slightly bugged.

This PR is strongly needed, because many users get Error Setting onMessage on a WebView overrides existing values of window.postMessage, but a previous value was defined
see  #10865 for detailed info.

Just ran into this today. Real pain :(

The current implementation is completely 100% broken and unusable. Using it results in a red page that says Setting onMessage on a WebView overrides existing values of window.postMessage, but a previous value was defined. It always results in that red page, no matter what you do.
Given that context, I think we should merge this. Something is clearly better than nothing. And even nothing is better than something that's 100% broken.

100% agree with @mcmar we are needing to be able to use onMessage for an app we are building.

Current implementation breaks for webviews that load Meteor js content.

I believe we can fix this without breaking backward compatibility. What if we can call window.originalPostMessage inside our overridden postMessage? Seems we can do it on Android right now, but we have to change the way we communicate with native side on iOS.

window.postMessage is a browser API. The subject issues are due to RCTWebview hijacking this window function.
In the case for RN Webviews I think its safe to assume we are using postMessage to achieve some kind of bridging between webview <--> RN ?
If so, if the concern is breaking backwards compatibility, does it make sense to instead have a parallel window.postMessageNative that doesn't impact current window.postMessage?

@mkonicek is this an acceptable PR to solve #10941 ?

@nazrdogan the proposed changes in this PR work. I made my own fork for current version react-native (warning; lots of work) and added similar changes for renaming postMessage to postMessageNative

This should definitely not be closed.

Yeah, so this issue (see here: https://github.com/facebook/react-native/issues/10865) was brought up in 2016 and I'm still getting it in production. And a bot automatically closes a PR to fix this? Get it together you guys.

This PR is something we MUST have. Currently, it conflicts several web SDKs including Google's, which relies on window.postMessage.


[Feature]: Add event binding on the Input component

Describe the feature
It would be great if we could use the listener like @blur, @focus, @input, etc. on the Input component.
Additional information

[ ] I intend to submit a PR for this feature.
[ ] I have already implemented and/or tested this feature.

Hello There !
Since the shad-vue Input component is itself a single html input, any event handlers would be attached directly on it via Fallthrough Attributes.
For example, this following code already works.
<script setup lang="ts">
import { Input } from '@/components/ui/input'

function onBlur(){
}

function onFocus(){
}

function onPaste(){
}
</script>

<template>
  <Input type="email" placeholder="Email"  @blur="onBlur" @focus="onFocus" @paste="onPaste"/>
</template>


Please create a new release tag

What feature do you want to see added?
Hey Gang,
I'm hoping you can just generate a new release based upon the latest changes in the repo. There have been quite a few between 2.235.1 and 2.346.3. We use some tooling which pulls based upon a tag, and it'd be nice to have an updated release tag.
thanks!
Upstream changes
No response

You should probably change your tooling to depend on the docker repository tag or label rather than depending on a tag placed in the git repository.  We don't use tags in this repository to track releases.


Any Way to Undo Quest Faliure?

I don't know whether to file this under bug, unimplemented request, or lack of user knowledge, but editing quest flags seems to do nothing to the actual quests. I tried setting mq008_done to 0 to undo the quest failing, and it didn't work. I then took another game and added mq008_done=1 and it didn't fail the quest either. I have two saves with identical quest flags right now, and in one the quest is failed and in the other I am in the middle of it. I tried this with another quest as well and no dice. Any insight would be appreciated.

Beige nippIes


Regression with get table producers

In the following cleos call:
cleos.sh get table eosio eosio producers

We used to receive a last_produced_block attribute in the json, which was incredibly helpful to us in regards to implementing producer failover strategies. We had a bash script like this:
TIMESTAMP="$(./cleos.sh get table eosio eosio producers -l 150 | grep blockmatrix1 -A 8 | grep last_produced_block | cut -d':' -f2)"
DATE = date --date "@$((($TIMESTAMP * 500 +<PHONE_NUMBER>00) / 1000))"

This would allow us to determine whether our producer had fallen behind 2 minutes 6 seconds, and we could automatically switch to a backup producer (using a different signing key) via regproducer.
Without the last_produced_block attribute we are left with 2 options. Implement a stateful check against the unpaid_blocks attribute, or to parse logs on the active producer. Neither of these are ideal, and requires a lot more boilerplate to implement a solid failover strategy.
Could this attribute be reinstated, or is there a recommendation for a more reliable method to detect producer failure?

+1 I’ve go a similar python script doing a check on the field.

Agreed, this would be a great feature for failover.

We can restore that tracking in our reference implementation however, this will not necessarily trigger an upgrade of any active chain out there in world.

For reference: this was removed in https://github.com/EOSIO/eos/commit/8d0417fd8a575220b0b0f1a16e7ceef5d348f174

I think contract developers should generally follow a principle of not including additional data in consensus state (i.e. EOSIO persistent state which contracts have access to) than what is needed for the operation of those smart contracts.
When we start violating that principle we open ourselves to slowly justifying inclusion of all kinds of metadata that would be useful for some application or service but that serves no purpose to the smart contract itself. And all this additional data would need to be covered by the EOSIO RAM which due to its scarcity is typically expected to be quite expensive compared to alternative places this metadata could be stored.
In my opinion this metadata should either be tracked in custom-built plugins that can be loaded into a nodeos API node, or alternatively a service can derive the metadata using the logged and indexed data from a general purpose indexing plugin (e.g. the mongodb plugin that we are adding back in a near future release). This approach allows the plugins/services to be easily updated to track other metadata that can be derived from blockchain data and/or transaction side-effects without requiring the much more difficult process of, for example, upgrading a contract on a live blockchain.

In order to focus our efforts on issues that are currently creating difficulty for the community we are closing tickets that were created prior to the EOSIO 2.0 release.  If you believe this issue is still relevant please feel free to reopen it or create a new one.  Thank you for your continued support of EOSIO!


Feature Request - Add TCP Flags to SPI

I'd like to be able to see is the tcp session flag count in the SPI data.  This would be useful in knowing if the session was not normal; such as only syn or reset flags.

Can you give more details on what you want to see and how you would use it?  This kind of overlaps with #226 but we never did.

I was thinking to treat it the same way protocols are currently treated. Just a count of the flags seen during the session.
syn(1), syn-ack(1), ack(18), push-ack(2), fin-ack(2)


chore: replace ts-jest with @swc-node/jest

Not too much specs... So just 1.507 s vs 4.408 s

Thanks :)


Empty results on token

Hi,I'm making an app which used omniauth-github gem to generate user token with user and admin:org scope
Its giving me empty results while try to fetch an organization's members
This is the curl request I'm sending, with the token generated using the gem -
curl -u shreyaq3:<omniauth toekn>  https://api.github.com/orgs/org_id/members
And this is response -
[ ]
I'm pretty  sure that the scopes are correct.
I'm using setup phase in omniauth to dynamically set the client id and secret
Rails.application.config.middleware.use OmniAuth::Builder do
   provider :github, setup: true, scope: "user,read:org,write:org,admin:org"
end

def setup
  request.env['omniauth.strategy'].options[:client_id] = app_id
  request.env['omniauth.strategy'].options[:client_secret] = app_secret
end

However when I manually create a token for the same scope using github's token generation tool, I get correct results
This is request -
curl -u shreyaq3:<github token>  https://api.github.com/orgs/org_id/members
Response -
[
  {
    "login": "xxx",
    "id": yyy,
    ....
    "type": "User",
    "site_admin": false
  }
]

Could you tell me if what am I missing. Is there something wrong with the token or perhaps I'm missing a step in authentication?

The requests you have listed require different authentication methods.
When using the token provided by the app, you must do so in this fashion:
curl https://api.github.com/?access_token=<token>
So, in your case ...
curl https://api.github.com/orgs/<org_id>/members?access_token=<token>
Going to close this for now. Feel free to reopen should you have additional issues.


fix: use cjs for browser fields

We should not be using pre-built files for the browser.  Resolves https://github.com/wycats/handlebars.js/issues/1553

Related to https://github.com/wycats/handlebars.js/pull/1540
@ouijan I think this PR is a nonbreaking solution with similar, perhaps improved, results for the issue you were seeing with imports.  While I think the packaged min.js file may function in some cases, it's breaking in others... But I think these cjs cover your case and the general. If you don't mind 👀 on this.


Filter Array throws error when using contains

Describe the Bug with repro steps
Filter Array works with "is equal to". This code works.
{
"type": "Query",
"inputs": {
"from": "@body('Parse_JSON')",
"where": "@equals(item()?['value'],'DPI Decision Disapproved')"
},
"runAfter": {
"Parse_JSON": [
"Succeeded"
]
}
}
This code with contains
{
"type": "Query",
"inputs": {
"from": "@body('Parse_JSON')",
"where": "@contains(item()?['value'],'DPI Decision Disapproved')"
},
"runAfter": {
"Parse_JSON": [
"Succeeded"
]
}
}
Throws the error
The execution of template action 'Filter_array_value_DPI_Decision_Contains' failed: The evaluation of 'query' action 'where' expression '@contains(item()?['value'],'DPI Decision Disapproved')' failed: 'The template language function 'contains' expects its first argument 'collection' to be a dictionary (object), an array or a string. The provided value is of type 'Null'.'.
What type of Logic App Is this happening in?
Consumption (Portal)
Which operating system are you using?
Windows
Are you using new designer or old designer
New Designer
Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg
Yes
Workflow JSON
{
  "type": "Query",
  "inputs": {
    "from": "@body('Parse_JSON')",
    "where": "@contains(item()?['value'],'DPI Decision Disapproved')"
  },
  "runAfter": {
    "Parse_JSON": [
      "Succeeded"
    ]
  }
}

Screenshots or Videos
No response
Browser
Edge
Additional context
No response

Transferring to backend but it looks like this might currently be by design? Is it possible that item()?['value'] can be NULL?


Merge Nuget branch

Pulls in changes for Nuget package building.

Appveyor doesn't appear to support this project type. Oh well.


Prepare for 0.3.2 release

Gah rubocop what is this I don't even :scream:

Seems like that cop was added recently: https://github.com/bbatsov/rubocop/blob/9276d072f4f2eb09d7ac87cd7b1afc3c9531b74c/config/enabled.yml#L131-L133
If we don't agree with it we could still disable it.

@pxlpnk I've resolved these in #121

:+1:
this brings up the issue on how we want to deal with changing style guides.


LLM Fine-tuning example

It is amazing that mlx supports efficient training with metal.
While we have the LLM inference example with Llama and Mistral, could you share an example or advice on how to fine-tune LLM (or quantized model) using MLX?

Never mind. I found the Lora example. Thank you!


Updates from rspec-dev (2015-02-08)

These are some updates, generated from rspec-dev's rake tasks.

Passed so merged...


polymer

would be good to wrap with polymer 1.1
i saw in the past #581 issue someone tried to use the old polymer 0.5

And what is the issue?

no issues. its a feature request

Issue is closed because of outdated/irrelevant/not actual/needed more information/inactivity.
If this issue is still actual and reproducible for latest version of Swiper, please create new issue and fill the issue template correctly:

Clearly describe the issue including steps to reproduce when it is a bug.
Make sure you fill in the earliest version that you know has the issue.
Provide live link or JSFiddle/Codepen or website with isssue


transaction redis

sails-redis
how to create multi transaction when use cache redis

Hi, @linhbkhn95! To allow us to help you as best we can, could you provide us with your version info and a brief description of your use case? Thanks!

@madisonhicks  i want insert 1000 record in a transaction of redis,
i need it redis nodejs https://www.npmjs.com/package/redis#clientmulticommands

Hi, @linhbkhn95! Thanks for the information. Is there any chance your could provide us with some more specific information? Thanks!


Multiple DHCP records  after change guest VM IP address

ISSUE TYPE

Bug Report

COMPONENT NAME

VR

CLOUDSTACK VERSION

<IP_ADDRESS>

CONFIGURATION

Advanced Networking
L3 Network
Isolated
Shared

--

OS / ENVIRONMENT

SUMMARY

STEPS TO REPRODUCE

1. shutdown Guest VM
2. Change IP address for NIC
3. start Guest VM
4. VM will get previous IP again
5.  In VR , dnsmasq config has two dhcp record.

> cat /etc/dhcphosts.txt  |grep TC-APP09CE
1e:00:aa:00:00:6a,<IP_ADDRESS>,TC-APP09CE,infinite
1e:00:aa:00:00:6a,<IP_ADDRESS>,TC-APP09CE,infinite

EXPECTED RESULTS

after change IP addreses for guest VM. remove  previous IP from dnsmasq record. The  VM will get New IP

ACTUAL RESULTS

VM get previous IP from dhcp server

@havengit how did you change the IP address of nic? Or did you add adding secondary IPs to the nic?

cc @Pearl1594 @weizhouapache

@rhtyd @havengit
I can reproduce the issue. I will work on it

Fantastic thanks @weizhouapache

@havengit how did you change the IP address of nic? Or did you add adding secondary IPs to the nic?

no secondary IPs
From UI ,instance  --> nic --> change ip address

Fixed by #5059


Blogger: Controller

Hello Reviewer...
In this PR I:
Created:

[ ] A route.

[ ] An action in the correct controller.

[ ] A view file.

Included placeholders in plain HTML in every view file.

Added code to handle only the 4 required URLs.
Have a great day.

Thank you sir @tufoinnkuo10


Audit of all visualizations that use contributor query

The contributor query now includes the following:

Commits
Issues: open, close, comment
Pull Requests: open, close, merge, review, comment

Check each visualization for use case on if anything needs to change with new information

Audit complete: no changes necessary, will keep this in mind as new visualizations are built


Greyscale classes (Saw, Triforce) on Ability Selection screen

The desaturation of the selected card works on most classes great. Even works OK-ish on Triforce/Elementalist because all of their cards have some color (though trickier)
However many of the Saw/Sawbones cards have no color at all, so when selected there's no visual feedback other than the selected cards list - which isn't as easy to spot which cards are selected when sorting through which cards to give up/take.
No idea on best way to do this - keep zoom on selected cards? Add some sort of flash on the card?

Damn sawbone. We've had some issues with this one already on the play screen, so we changed the UI for something less color-dependant.
We'll think about that; Or maybe i'll turn the cards white instead ;)
#134 #135

Suggestion for keeping readability, perhaps just add a glow to the selected cards?

That would be a simple fix :)

Just applied the same green halo than the play page


Chapters not parsed for newly added entries upon updating library

Steps to reproduce

Add entries from sources like Hitomi or E-hentai without opening up
Update them from library

Expected behavior
Every entry from every source can parse chapters upon updating library
Actual behavior
Chapters aren't loaded up.
I added 2 entries from each of these sources in the testing category:
MangaDex
Tsumino
Nhentai
Imhentai
HentaiNexus
Hentai2Read
E-hentai
Hitomi
Results: all entries loaded chapters ... Except:

1 entry of nhentai
both e-hentai entries
all Hitomi

Crash logs
No response
Komikku version
r9523
Android version
Android 12/13
Device
OnePlus 5T, Lenovo Tab M3
Other details
Details on discord. We talked about this already.
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] If this is an issue with an official extension, I should be opening an issue in the extensions repository.
[X] I have gone through the FAQ and troubleshooting guide.
[X] I have updated the app to version 1.12.1.
[X] I have updated all installed extensions.
[X] I will fill out all of the requested information in this form.

komikku_crash_logs.txt

Additional note
The problem doesn't concern only the newly added entries.
For instance, I have many entries from Imhentai having already a chapter fetched, but I must refresh all of them to re-download them (maybe an url change), and none of them refreshed the chapter.
And... I used the trick of Migration. I mean, I selected a bunch of them and tapped on migrate and selected only their same source, then cancelled the migration, and in this way the found entries are forced refresh properly.
So, in library it doesn't work, but in the migration process yes.


HTTP2: Android gRPC h2c calls fail with PROTOCOL_ERROR

Describe the bug
Calling gRPC hosted on Kestrel from an Android device over h2c will fail. The client on Android reports a protocol error.
The original reporter of the issue tested Android calling C-core and it succeeded. Android calling Kestrel with TLS succeeded.
Combination of these three will fail:

gRPC on Kestrel
Android client
h2c

Originally reported:

https://github.com/grpc/grpc-dotnet/issues/564#issuecomment-536572569
Repro: https://github.com/ivan-penchev/gRPC-Java-dotnetcore3/tree/master

To Reproduce
Steps to reproduce the behavior:

Run Kestrel with a gRPC service
Run Android emulator and call gRPC service
Call fails

Expected behavior
Call succeeds.
Screenshots

Additional context
.NET Core 3.0 GA
Wireshark log: android-protocol-error-nodocker.zip

@Tratcher @halter73 @anurse

We definitely haven't invested a lot in h2c scenarios (since mainstream browsers don't support it). With gRPC it's probably a good idea to dig a little deeper into it.

FYI, the original issue and sample uses Docker. You don't need to run Kestrel inside Docker to reproduce this.
Android calling Kestrel on a local machine will reproduce this.

The error doesn't look related to h2c, it should behave the same with and without TLS.
There should be server logs detailing what we thought the problem was.
First impression: The client is starting with stream id 3 instead of 1. That should be valid but it's unusual and may trip some of the validation logic.

I'll re-test with verbose logs.

dbug: Microsoft.Extensions.Hosting.Internal.Host[1]
      Hosting starting
dbug: Grpc.AspNetCore.Server.Model.Internal.ServiceRouteBuilder[2]
      Discovering gRPC methods for GrpcService10.GreeterService.
dbug: Grpc.AspNetCore.Server.Model.Internal.ServiceRouteBuilder[1]
      Added gRPC method 'SayHello' to service 'Greet.Greeter'. Method type: 'Unary', route pattern: '/Greet.Greeter/SayHello'.
dbug: Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServer[0]
      Using development certificate: CN=localhost (Thumbprint: 2FE5E630929AB7660BC1C995E3F989C91B6CDE2F)
info: Microsoft.Hosting.Lifetime[0]
      Now listening on: https://localhost:5001
info: Microsoft.Hosting.Lifetime[0]
      Now listening on: http://localhost:5000
dbug: Microsoft.AspNetCore.Hosting.Diagnostics[0]
      Loaded hosting startup assembly GrpcService10
info: Microsoft.Hosting.Lifetime[0]
      Application started. Press Ctrl+C to shut down.
info: Microsoft.Hosting.Lifetime[0]
      Hosting environment: Development
info: Microsoft.Hosting.Lifetime[0]
      Content root path: C:\Users\James\source\repos\GrpcService10\GrpcService10
dbug: Microsoft.Extensions.Hosting.Internal.Host[2]
      Hosting started
dbug: Microsoft.AspNetCore.Server.Kestrel[39]
      Connection id "0HLQ948TUS99R" accepted.
dbug: Microsoft.AspNetCore.Server.Kestrel[1]
      Connection id "0HLQ948TUS99R" started.
trce: Microsoft.AspNetCore.Server.Kestrel[37]
      Connection id "0HLQ948TUS99R" sending SETTINGS frame for stream ID 0 with length 18 and flags NONE
trce: Microsoft.AspNetCore.Server.Kestrel[37]
      Connection id "0HLQ948TUS99R" sending WINDOW_UPDATE frame for stream ID 0 with length 4 and flags 0x0
trce: Microsoft.AspNetCore.Server.Kestrel[37]
      Connection id "0HLQ948TUS99R" received SETTINGS frame for stream ID 0 with length 0 and flags NONE
trce: Microsoft.AspNetCore.Server.Kestrel[37]
      Connection id "0HLQ948TUS99R" sending SETTINGS frame for stream ID 0 with length 0 and flags ACK
trce: Microsoft.AspNetCore.Server.Kestrel[37]
      Connection id "0HLQ948TUS99R" received SETTINGS frame for stream ID 0 with length 0 and flags ACK
trce: Microsoft.AspNetCore.Server.Kestrel[37]
      Connection id "0HLQ948TUS99R" received HEADERS frame for stream ID 3 with length 138 and flags END_HEADERS
trce: Microsoft.AspNetCore.Server.Kestrel[37]
      Connection id "0HLQ948TUS99R" received DATA frame for stream ID 3 with length 20 and flags END_STREAM
dbug: Microsoft.AspNetCore.Server.Kestrel[35]
      Trace id "0HLQ948TUS99R:00000003": HTTP/2 stream error "PROTOCOL_ERROR". A Reset is being sent to the stream.
Microsoft.AspNetCore.Connections.ConnectionAbortedException: The request :scheme header 'https' does not match the transport scheme 'http'.
trce: Microsoft.AspNetCore.Server.Kestrel[37]
      Connection id "0HLQ948TUS99R" sending RST_STREAM frame for stream ID 3 with length 4 and flags 0x0
trce: Microsoft.AspNetCore.Server.Kestrel[37]
      Connection id "0HLQ948TUS99R" received GOAWAY frame for stream ID 0 with length 8 and flags 0x0
dbug: Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets[6]
      Connection id "0HLQ948TUS99R" received FIN.
dbug: Microsoft.AspNetCore.Server.Kestrel[36]
      Connection id "0HLQ948TUS99R" is closing.
dbug: Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets[7]
      Connection id "0HLQ948TUS99R" sending FIN because: "The client closed the connection."
dbug: Microsoft.AspNetCore.Server.Kestrel[36]
      Connection id "0HLQ948TUS99R" is closed. The last processed stream ID was 3.
dbug: Microsoft.AspNetCore.Server.Kestrel[2]
      Connection id "0HLQ948TUS99R" stopped.

The request :scheme header 'https' does not match the transport scheme 'http'.
Ah, that's a legit bug in the client.

It seems rather suspicious.
Before we point fingers, we should double check the HTTP/2 spec.

For my knowledge, is it common to use h2c with android for this scenario? Also, I'm not sure if this is a 3.1 candidate if it's only h2c?

In development, yes. All gRPC guides and samples use h2c. That's common across all gRPC stacks apart from .NET.

The client is clearly using the wrong value, they're connecting over http, not https. The real question here is how strict the server should be about that.
While we work that out a bug should also be filed against the client.

That's here: https://github.com/grpc/grpc-java/issues/6202#issuecomment-538593147

Given that the scheme is supposed to represent the URL, I lean towards thinking that validating it is the correct behavior. The spec seems unclear on if the :scheme has to be validated. It certainly would be an HTTP/1.1 "protocol error" to try and speak https when the URL that the user specified was http://....
Can we see what other servers do in this situation? IIS and maybe one like NGINX? Should be possible to craft the HTTP/2 packets correctly such that we are using h2c but sending :scheme https, right?

In HTTP/1.1 the scheme is never presented in the request, it's assumed based on the transport.
IIS doesn't support h2c.

It really feels like this is correct behavior on Kestrel's side. The scheme is incorrect, thus the protocol has been violated.

Our initial triage sense is that we don't plan to take action here. At best we'd be ignoring a malformed HTTP/2 request, which seems bad.

If there isn't traction on the client bug, we can revisit this decision. It is true that some other servers are not as rigid about the :scheme psuedo-header.

The spec seems unclear on if the :scheme has to be validated.

Hello from gRPC. We think the scheme should not be validated. As the spec is unclear, validating it may be too risky. Assuming a client talk to a server through a proxy, the client talk to the proxy using https, and the proxy talk to the server using plaintext. In this case the scheme can be https, and it is not matching the transport.

In the case of the proxy, we tell app developers to configure middleware to set the appropriate scheme. If you trust the request is coming from a proxy server, you can pull the original scheme from X-Forwarded-Proto or something like that.
If we decide not validate the scheme, we would report the real scheme instead of the invalid one provided by the psuedo-header.

Is anyone aware of any proxies that use the :scheme instead of something else like X-Forwarded-Proto to communicate the scheme of the  request?

@halter73 I haven't even seen signs of a proxy that supports HTTP/2 yet. Most still seem to tunnel it using the standard HTTPS tunneling.

I'll re-open to continue considering but it still feels wrong to allow an invalid request like this. The spec is pretty clear that "The ":scheme" pseudo-header field includes the scheme portion of the target URI ([RFC3986], Section 3.1)" and the scheme for an h2c connection should already be http... Sending https is incorrect.
As for proxies, it would also be invalid for a proxy to simply pass through the https value. Generally proxies do not attempt to masquerade as the client, the X-Forwarded- headers are there to make clear when a request is proxies and what the original values are.

I agree with you that :scheme is part of the target URI, but I think the URI should be the client's URI.
To your response, I have two main arguments for not checking the scheme. First, the X-Forwarded- headers are a de facto standard, but not an official standard. Use something less standardized to replace a standard is risky. Second, a server can just get the type of connection without the need to check the :scheme. Validating it is not helpful.
We went through some old http work group threads, and found some messages clearly arguing for our side (1 2). I also have to said there are people against our option too.
If these are not enough to convince you, I think bring this to ietf for a clarification is a good idea.

I agree with you that :scheme is part of the target URI, but I think the URI should be the client's URI.

The client URI for h2c is "http", not "https".
The proxy discussion is hypothetical at this point, let's focus on the Java library.

There are real people using gRPC through TCP proxies right now, why do you think it is hypothetical?
I think the focus should be interpretation of the HTTP/2 spec.

Interesting. When you first mentioned proxies, I was thinking about a layer 7 proxy. I hadn't considered how validation might play with a simple TLS termination proxy. Definitely something to consider.
How do these proxies communicate the result of the ALPN handshake? Are they configured to route the connection to a different endpoint based on the negotiated protocol?

Can anybody give names of specific HTTP/2 proxies they're using that would be worth doing interop testing with?

At this point, given that the gRPC Java client has been updated to fix this, we're going to close this. If there are use cases that come up for which this validation is a problem, we can reconsider. Right now, this is the only client we've encountered in the wild with this mismatch.

https://tools.ietf.org/html/rfc8164 outlines a use case where sending an http scheme over a TLS HTTP/2 connection has specific semantics and is disallowed unless the server has indicated support for it.


Investigate regular failure of BlobSidecarsByRangeIntegrationTest

As part of https://github.com/Consensys/teku/pull/7609 BlobSidecarsByRangeIntegrationTest.requestBlobSidecars_shouldReturnCanonicalBlobSidecarsOnDenebMilestone() was failing regularly on the line assertThat(peer.getOutstandingRequests()).isEqualTo(0);.
That line was commented out in order for the test to pass on CI and the condition afterwards were still passing but it needs to be investigated why this assertion fails. It would be most likely related to the increase of the size of the blobs given that minimal uses the same FIELD_ELEMENTS_PER_BLOB as mainnet.

@StefanBratanov This is normally fixed, right? Should we close it?

Ah yes, thanks. Closing that now. It has been fixed as part of https://github.com/Consensys/teku/pull/7627