Apply various runner service fixes

Highlights:

runme server now has the --dev flag to enable a development mode. Currently, it affects only logs which will have a more friendly formatting and a debug level. Without the flag, the logs are JSON structured logs and have an info level. Closes https://github.com/stateful/runme/issues/129.
ExecuteRequest has a new field called stop that is an enum. It allows terminating the running command. Closes https://github.com/stateful/runme/issues/131.
Logic waiting for the command to finish got improved. It should handle cases when a command is run with TTY (aka interactive mode) and finishes on its own. The RPC method will exit instead of hanging until the client closes the send direction. Closes https://github.com/stateful/runme/issues/130.

@adambabik
After testing client-side here's what I have:
Stop

For non-TTY, since the client has to end its input stream early, there is no way to send a stop request in this case.
For TTY, works great!

TTY End

Works fine, but after the session ends, my logs look like this:

2023-02-16T09:36:16.070-0600	INFO	runner/service.go:126	running Execute in runnerService
2023-02-16T09:36:17.075-0600	INFO	runner/command.go:273	read all from stdin
2023-02-16T09:36:17.076-0600	INFO	runner/service.go:300	finished command execution	{"exitCode": 0}
2023-02-16T09:36:17.076-0600	INFO	runner/service.go:208	failed to receive requests; stopping program	{"error": "rpc error: code = Canceled desc = context canceled"}
2023-02-16T09:36:17.076-0600	INFO	runner/command.go:296	failed to close pty; continuing
2023-02-16T09:36:17.076-0600	INFO	runner/command.go:302	failed to terminate process group; trying Process.Signal()	{"error": "no such process"}
2023-02-16T09:36:17.076-0600	INFO	runner/command.go:304	failed to signal process; trying Process.Kill()	{"error": "os: process already finished"}
2023-02-16T09:36:17.076-0600	INFO	runner/service.go:210	failed to stop program	{"error": "os: process already finished", "errorVerbose": "os: process already finished\ngithub.com/stateful/runme/internal/runner.(*command).stop\n\t/Users/mxs/Projects/runme/internal/runner/command.go:305\ngithub.com/stateful/runme/internal/runner.(*command).Kill\n\t/Users/mxs/Projects/runme/internal/runner/command.go:282\ngithub.com/stateful/runme/internal/runner.(*runnerService).Execute.func3\n\t/Users/mxs/Projects/runme/internal/runner/service.go:209\nruntime.goexit\n\t/opt/homebrew/Cellar/go/1.19.5/libexec/src/runtime/asm_arm64.s:1172"}

I think we're running into the issue I was mentioning before - the server ends the stream, which causes srv.Recv to get an error since it has to stop blocking. Looks like somehow there are then two requests to end the process happening.
Other
Getting the following after trying to INTERRUPT a program:
2023-02-16T09:31:02.870-0600	INFO	runner/service.go:281	command finalizer failed	{"error": "open /var/folders/cs/k8y186rn3rv2gm63f46pnmfr0000gn/T/713880327/.env_end: no such file or directory", "errorVerbose": "open /var/folders/cs/k8y186rn3rv2gm63f46pnmfr0000gn/T/713880327/.env_end: no such file or directory\ngithub.com/stateful/runme/internal/runner.(*command).readEnvFromFile\n\t/Users/mxs/Projects/runme/internal/runner/command.go:314\ngithub.com/stateful/runme/internal/runner.(*command).collectEnvs\n\t/Users/mxs/Projects/runme/internal/runner/command.go:336\ngithub.com/stateful/runme/internal/runner.(*command).Finalize\n\t/Users/mxs/Projects/runme/internal/runner/command.go:359\ngithub.com/stateful/runme/internal/runner.(*runnerService).Execute\n\t/Users/mxs/Projects/runme/internal/runner/service.go:280\ngithub.com/stateful/runme/internal/gen/proto/go/runme/runner/v1._RunnerService_Execute_Handler\n\t/Users/mxs/Projects/runme/internal/gen/proto/go/runme/runner/v1/runner_grpc.pb.go:238\ngoogle.golang.org/grpc.(*Server).processStreamingRPC\n\t/Users/mxs/go/pkg/mod/google.golang.org/grpc@v1.53.0/server.go:1620\ngoogle.golang.org/grpc.(*Server).handleStream\n\t/Users/mxs/go/pkg/mod/google.golang.org/grpc@v1.53.0/server.go:1708\ngoogle.golang.org/grpc.(*Server).serveStreams.func1.2\n\t/Users/mxs/go/pkg/mod/google.golang.org/grpc@v1.53.0/server.go:965\nruntime.goexit\n\t/opt/homebrew/Cellar/go/1.19.5/libexec/src/runtime/asm_arm64.s:1172"}

This error only happens when running INTERRUPT (with tty), but not when running KILL.

For non-TTY, since the client has to end its input stream early, there is no way to send a stop request in this case.

That's true. That's why I pushed for cancelling the connection from the client which would be equivalent to killing the process, but that's out of equation.
After introducing ExecuteRequest.stop, the client should never close the send direction. I need to fix the code to make it work without this assumption.
Also, based on our Slack convo, when the handler exits and there is an active srv.Recv(), it will get the rpc canceled error. I need to fix that as well as I thought rpc canceled is possible to receive only if the client sends it.

For TTY, it works fine, but I have the following error after trying to INTERRUPT a program:

This is a bit odd because the logic is the same and both signals INT and KILL should work the same in the worst case scenario. Regarding the command finalizer failed log, I can recognize that a process was interrupted and avoid trying to collect envs as it's doomed anyway if the process is interrupted (unless we improve the logic behind collecting envs but it's not going to happen very soon).

Works fine, but after the session ends, my logs look like this:

I think we're running into the issue I was mentioning before - the server ends the stream, which causes srv.Recv to get an error since it has to stop blocking. Looks like somehow there are then two requests to end the process happening.

Yes, my assumption was incorrect as described above in this comment.
Stay tuned for fixes! :)

@adambabik
Good stuff!

This is a bit odd because the logic is the same and both signals INT and KILL should work the same in the worst case scenario. Regarding the command finalizer failed log, I can recognize that a process was interrupted and avoid trying to collect envs as it's doomed anyway if the process is interrupted (unless we improve the logic behind collecting envs but it's not going to happen very soon).

Yeah, I did some digging and it would appear that the following line in command.go is basically not being executed by the shell on interrupt:
		_, _ = script.WriteString("env > " + filepath.Join(envStorePath, envEndFileName) + "\n")

Which makes sense, because the program will never get to that point in the script if interrupted. Not sure why it still executes on kill though (maybe this was a user error?)
At any rate, I definitely think that we should not try to collect envs in the case of an interrupt. Arguably we probably don't want to collect envs unless the exit code is 0. Or we can just do a check to make sure that the env end file exists, and if not, not try to collect envs (and maybe log).

I definitely think that we should not try to collect envs in the case of an interrupt. Arguably we probably don't want to collect envs unless the exit code is 0.

That's my strategy for now. I think collecting envs can be done much smarter, for example using trap. Then, we could collect them even if the program failed or was interrupted.

Which makes sense, because the program will never get to that point in the script if interrupted. Not sure why it still executes on kill though (maybe i just misread the logs idk)

I can't reproduce, at least with https://github.com/stateful/runme/pull/134/commits/0bb412dcf1ef3f0f57a81361d3a91921aa48a342. The result is the same regardless of the signal I send:
$ buf curl --protocol grpc --http2-prior-knowledge http://localhost:7890/runme.runner.v1.RunnerService/Execute -d @-
{"program_name": "/usr/local/bin/bash", "commands": ["cat - | tr a-z A-Z"], "tty": true}
{"stop": 1}
{"exitCode":130}

$ buf curl --protocol grpc --http2-prior-knowledge http://localhost:7890/runme.runner.v1.RunnerService/Execute -d @-
{"program_name": "/usr/local/bin/bash", "commands": ["cat - | tr a-z A-Z"], "tty": true}
{"stop":2}
{"exitCode":137}

Logs from the servers:
2023-02-16T19:10:18.170+0100    INFO    runner/service.go:126   running Execute in runnerService
2023-02-16T19:10:18.171+0100    DEBUG   runner/service.go:176   command config  {"cfg": {"ProgramName":"/usr/local/bin/bash","Args":null,"Directory":"","Session":{"ID":"cfn732k3c37gk8tks74g","Metadata":null},"Tty":true,"Stdin":{},"Stdout":{},"Stderr":{},"IsShell":true,"Commands":["cat - | tr a-z A-Z"],"Script":"","Logger":{}}}
2023-02-16T19:10:35.912+0100    INFO    runner/service.go:233   requested the program to stop
2023-02-16T19:10:35.914+0100    INFO    runner/service.go:292   command finished        {"exitCode": 130}
2023-02-16T19:10:35.915+0100    INFO    runner/service.go:305   command was finalized successfully
2023-02-16T19:10:35.915+0100    INFO    runner/service.go:321   sending the final response with exit code
2023-02-16T19:10:51.111+0100    INFO    runner/service.go:126   running Execute in runnerService
2023-02-16T19:10:51.111+0100    DEBUG   runner/service.go:176   command config  {"cfg": {"ProgramName":"/usr/local/bin/bash","Args":null,"Directory":"","Session":{"ID":"cfn73as3c37gk8tks750","Metadata":null},"Tty":true,"Stdin":{},"Stdout":{},"Stderr":{},"IsShell":true,"Commands":["cat - | tr a-z A-Z"],"Script":"","Logger":{}}}
2023-02-16T19:10:57.440+0100    INFO    runner/service.go:233   requested the program to stop
2023-02-16T19:10:57.440+0100    INFO    runner/service.go:292   command finished        {"exitCode": 137}
2023-02-16T19:10:57.441+0100    INFO    runner/service.go:305   command was finalized successfully
2023-02-16T19:10:57.441+0100    INFO    runner/service.go:321   sending the final response with exit code

@adambabik
Just tested on client, it's all fixed, except that the issue of non-PTY programs not exiting is still present - see my response on your comment, the code to close stdin never gets called since InputData is empty on initial request.

I can't reproduce, at least with https://github.com/stateful/runme/commit/0bb412dcf1ef3f0f57a81361d3a91921aa48a342

Hmm, not sure what's going on here then.

@adambabik Works now 👍


Increased span_stack_trace_min_duration to 500ms

What does this PR do?
Fixes #2402
Checklist

[x] This is something else

[x] I have updated CHANGELOG.asciidoc

:grey_exclamation: Build Aborted

There is a new build on-going so the previous on-going builds have been aborted.

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Reason: Aborted from #2

Start Time: 2022-01-19T12:27:27.643+0000

Duration: 4 min 58 sec

Commit: 6fbcbcef9cb402430440fa8cadccc10e84dd8e16

:robot: GitHub comments
To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.

run benchmark tests : Run the benchmark test.

run compatibility tests : Run the JDK Compatibility test.

run integration tests : Run the APM-ITs.

/test

As explained in https://github.com/elastic/apm/pull/585#issuecomment-1021371791, we'll only change the default for Node.js for now.


shared: Bump version to 0.0.5.

This is mostly in preparation for moving the code for polls into shared, but should also be good in general.
I'm not sure what the process is for pushing this to npm, @showell, can you let me know what I need to do for that?

Whoever merges this should also add the shared-0.0.5 tag. I don't think I can encode that in a Github PR.

I've used yarn-link to test that this upgrade doesn't break typeahead in the mobile app.

@gnprice has done all the previous @zulip/shared uploads (see npm view @zulip/shared).

Whoever merges this should also add the shared-0.0.5 tag. I don't think I can encode that in a Github PR.

Yeah, the way our instructions are meant to work is that the git push command there (with the version-bumping commit, and the tag) literally means a git push.
These changes LGTM; please go ahead and push, and push a shared-0.0.5 tag pointing to that commit.
I'd also be happy to see a docs change on those instructions making explicit that that part really is a direct git push and not a GitHub PR :slightly_smiling_face: . (And as with any pure docs/comments changes, I'm happy to review or discuss when you're not sure, but when you have an edit you're confident of please feel free to push it directly without a PR, wiki-style.)

I don't actually have permission to push to @zulip/zulip — could I get those? Not sure what our policies are around that.


What installer framework do you use it looks beautiful

Curious what framework you use. The installer looos beautiful

https://github.com/oleg-shilo/wixsharp


Semantic changes for delete confirmation message

Describe the feature you'd like
Delete message for Badge and clipart are:

Delete badge successfully and Delete clipart successfully.

Which is semantically not correct. It should be:

Badge deleted successfully and Clipart deleted successfully.

For saving the clipart the message is correct:  Clipart saved successfully.
So doing the changes for delete msg on similar lines.
Would you like to work on the issue?
Yes

This is merged now


Option to Expand to Open Folder in Files App (Like in Windows Explorer)

What feature or improvement do you think would benefit Files?
In Windows Explorer, there's an option under Folder Options > View called "Expand to open folder." This feature automatically expands the folder structure in the sidebar to display the currently open folder, making it easier to navigate and see the folder hierarchy (as shown in the first image).
In Files, I would like to know if there's a similar option to automatically expand the sidebar to display the currently open folder, as in Windows Explorer (demonstrated in the second image). This functionality is helpful for easily navigating through different folder levels while keeping the structure visibl

Requirements

Add an option similar to "Expand to open folder" in the Files app.
Automatically expand the folder structure in the sidebar when navigating through directories.
Ensure that this feature behaves similarly to Windows Explorer, where each open folder is visibly expanded in the sidebar.

Files Version
<IP_ADDRESS>
Windows Version
10.0.22621.4169
Comments
No response

Thanks for the feedback, We're tracking this in #1928.  You can check there or click subscribe in the right sidebar for updates.
Right now Files doesn't have folder tree support at all.


CAMEL-19644 - camel-jbang - Add command to generate SBOM report

Description

Target

[x] I checked that the commit is targeting the correct branch (note that Camel 3 uses camel-3.x, whereas Camel 4 uses the main branch)

Tracking

[x] If this is a large change, bug fix, or code improvement, I checked there is a JIRA issue filed for the change (usually before you start working on it).

Apache Camel coding standards and style

[x] I checked that each commit in the pull request has a meaningful subject line and body.

[x] I have run mvn clean install -DskipTests locally and I have committed all auto-generated changes

Okay this would work for an existing maven project if there is a pom.xml.
Can you look at how dependency copy does it, as it does a silent export in the background, and then after that executes that maven plugin.
This allows users to do
camel sbom

On a jbang "project"
If you want to generate a sbom on an actual maven project, then you would do it the standard maven way with a  in the pom.xml etc.

Okay this would work for an existing maven project if there is a pom.xml.
Can you look at how dependency copy does it, as it does a silent export in the background, and then after that executes that maven plugin.
This allows users to do
camel sbom

On a jbang "project"
If you want to generate a sbom on an actual maven project, then you would do it the standard maven way with a in the pom.xml etc.

Yeah, it makes sense, I removed that part. I didn't think about it. Thanks for pointing it out. I'll fix this accordingly.


[BUG] The XML file of Proxy Configuration Cluster has an error

Reproduction steps
check the xml file : https://github.com/project-chip/connectedhomeip/blob/v<IP_ADDRESS>/src/app/zap-templates/zcl/data-model/chip/proxy-configuration-cluster.xml
lack one attribute

The specifications (1.0 and 1.2) describe as below

Bug prevalence
each time
GitHub hash of the SDK that was being used
561d23d0db215a99705ff0696e73853c8edf11b2
Platform
other
Platform Version(s)
v<IP_ADDRESS> and v1.0.0
Anything else?
No response

The Proxy bits are provisional and not implemented and about to be removed from the spec.


Add support for Sub Searches to export

Description
As part of Patient and Group exports additional resources need to be retrieved based on the primary resources being exported. This requires additional searches based on the results returned from the primary search. As each of these sub searches could have multiple pages of data, and in the case of Group export could have sub searches of their own, the continuation tokens and page counts for these searches need to be stored. This will allow the export job to resume if it is interrupted in the middle of a sub search without duplicating exported data.
Within the ExportJobRecord the continuation token and current page of the search is stored in the ExportJobProgress object. This object just stores the continuation token and page. By adding a recursive reference to the ExportJobProgress and an Id for the resource that is currently being used for sub searches all the necessary data to resume an interrupted job would be present.
Related issues
Testing
No new functionality to test yet.

Incorporated into the branch that consumed the changes being made.


Automator: update<EMAIL_ADDRESS>in<EMAIL_ADDRESS>

Generated by Automator - 2023-02-08T06:34:56+00:00

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio_release-1.15
aa051e23fefd22cb45aa1658d4bbc553fe8dfbf8
link
true
/test unit-tests-arm64

integ-security-multicluster_istio_release-1.15
aa051e23fefd22cb45aa1658d4bbc553fe8dfbf8
link
true
/test integ-security-multicluster

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest


ImageDataUtil.getPixels returns pixels in a order different from older version of lime

For non-flash targets ImageDataUtil now returns pixels in a different order. That broke texture rendering of my openfl-stage3d based apps.
Why did you change that??
https://github.com/openfl/lime/blob/4cec0df3156296e8465d04ce8296beb97c8f2d63/lime/graphics/utils/ImageDataUtil.hx

You should be able to fix using #if (lime > "2.0.3") in your code, I apologize for the problem.
Using getPixels (as well as getPixel or getPixel32) should be consistent when using it against different data store types. The getPixel or getPixel32 values returned pixels in ARGB format, similar to Flash or HTML5. When calling getPixels it was inconsistent, which was a bad way to go.
I think we could consider doing a different color order if it made sense not to use ARGB, or if there was a really compelling reason, we could allow it to be data type specific, but I would prefer to avoid it.

By the way, in an unrelated, I'm interested still in your Node.js work, I had trouble finding a way to build the node NDLL module, if that was working, I have a feeling we're pretty close to being able to use it as a target, that and thinking if there was a way to make a Node.js binary that works without arguments

This is really confusing... What is "consistency" you are talking about? Isn't that true for little endian systems?
I believe pixels are originally stored in RGBA format in ImageBuffer, which can be directory passed to glTexImage2D with GL_RGBA format. Currently getPixels converts this to ... GBAR? What are you trying to do? Did you want to convert pixels to BGRA, so that images can be uploaded to GPU without swapping channels?
//0123
//RGBA
//1230
//GBAR
[0] = g; // (i + 1)
[1] = b; // (i + 2)
[2] = a; // (i + 3)
[3] = r; // (i)

If so I don't think that is a very good idea, because WebGL doesn't support BGRA and UNSIGNED_INT_8_8_8_8_REV, and breaks compatibility with flash target.

For node.js target
I think I have uploaded "package.json" to starling-openfl repo.
Copy json file to bin directory and execute "npm install". bindings module will be installed.
bindings is a node module that helps developers to load native addons, I suppose.
node_ndll can be easily built with node-gyp.
You should place the addon(node_ndll.node) by yourself since it is still not published to npm.
(Maybe there is a way to install addon from local repo, but I don't know it since I'm still new to node.)
Place it in "build" directory so that bindings module can find it.
You should fork node.js to execute an app without arguments and console.
On linux you don't have to do anything special to hide console, I think.
I already tried that in my own fork, so you can check it out.
Hope this helps.

The intention is to provide consistency if you use Image.getPixel, Image.getPixel32 or Image.getPixels in regards to the color order. I believe it should ARGB now on all targets, or that is the intention. If this is not the case, then we should fix it, unless we decide that Lime should be RGBA across the board, but I'm not sure. Either way, it should be one or the other.
This is different, potentially, then the data store format. The imageBuffer.data property might be RGBA so that it's consistent with what OpenGL expects. Part of this is the difference (and intention behind) the unified, higher-level (and optional) Image pixel APIs, versus setting the data directly.

You didn't mention endianness. Are you sure that byte order changes on big endian computers?
I beilieve pixels are not correctly ordered even for little-endian computers. They cannot be uploaded with BGRA(and UNSIGNED_INT_8_8_8_8_REV) format correctly. They should be stored in "BGRA" format to maintain consistency with getPixel32, because on little endian computers pixels are stored in reversed over.
BGRA is how OpenGL calls 32bit texture format which is natural for little-endian computers. Direct3D9 was calling texture formats in the opposite way since it was only designed for little endian computers, but this is really confusing for me.

And

Sorry I was also confused. BitmapData.getPixels always returns pixels in big endian format. Then pixels should be stored in ARGB, not BGRA.

Then this is corect behaviour... Maybe I should directly get ImageBuffer with untyped to get RGBA data without expensive swizzle operation.

Yeah, perhaps it should be public, or there should be bitmapData.getImage () or something, so you could bitmapData.getImage ().buffer.data directly, or something like that


Edit-Competition Phases Error

I have uploaded a competition with 2 phases:
Phase 1 :

Phase 2 :

Now when I click Edit my competition and go to Phases tab and click the arrows to show details, it gives me this error:

Which is wrong because Phase 1 starts before Phase 2

The arrows are supposed to give details or to change the order of the phase?
In my experience, this warning is annoying but does work.

The arrows are supposed to show dertails.
The error should not be there because the phases are actually ok.
For example check this competition: https://www.codabench.org/competitions/518/?secret_key=606dc7aa-256f-4b07-91b3-f91116c3dae4
Phase 1 : 24-01-2023 to 10-02-2023

Phase 2: 20-02-2023 to 31-03-2023

But when you go to edit>phases and click an arrow then this error is shown:

The phase are OK, but for some reason Codabench thinks that Phase 2 is prior to Phase 1

I just tried, and I confirm that the arrow change the order of the phases

You are right. It is confusing for me. Maybe it is ok for other people

I agree that it is a bit confusing


space-hash causing build to fail

using the experimental branch
running middleman contentful --rebuild with .[app]-site-hash present in root i get the following error:

deleting the .[app]-site-hash from root allows the build to run without issue:

any thoughts as to why the site-hash file would interfere with my webpack build?
here is my config.rb:
activate :directory_indexes
activate :autoprefixer

# Per-page layout changes:
#
# With no layout
page '/*.xml', layout: false
page '/*.json', layout: false
page '/*.txt', layout: false

set :relative_links, true
set :relative_paths, true
set :css_dir, 'assets/stylesheets'
set :js_dir, 'assets/javascripts'
set :images_dir, 'assets/images'
set :fonts_dir, 'assets/fonts'
set :layout, 'layouts/app'
set :partials_dir, 'layouts/partials'

# Reload the browser automatically whenever files change
configure :development do
  activate :livereload
end

###########################
## Helpers
###########################
helpers do

  def render_partial( partial_name )
    partial "layouts/partials/#{partial_name}"
  end

end

activate :contentful do |f|
  f.access_token  = ENV['ACCESS_TOKEN']
  f.space         = { annuity_support: ENV['SPACE'] }
  f.content_types = { resource: 'resource' }
end

# Build-specific configuration
configure :build do
  activate :favicon_maker do |f|
    f.icons = {
      'favicon.png' => [
        { icon: 'favicon.png', size: '16x16' },
        { icon: 'favicon.ico', size: '64x64,32x32,24x24,16x16' }
      ]
    }
  end

  activate :relative_assets
  activate :gzip
  activate :minify_css
  activate :minify_html
  activate :minify_javascript
  activate :asset_hash
  activate :meta_tags
end

activate :deploy do |deploy|
  deploy.build_before = true
  deploy.deploy_method = :git
end

activate :external_pipeline,
         name: :webpack,
         command: build? ?
          './node_modules/webpack/bin/webpack.js --bail -p' :
          './node_modules/webpack/bin/webpack.js --watch -d --progress --color',
         source: '.tmp/dist',
         latency: 1

Hey @joshRpowell,
As promised, a DEPLOYING file has been added to document platform specific issues.
It's currently being reviewed and will be merged ASAP.
https://github.com/contentful/contentful_middleman/pull/112
Cheers

This has been merged.
Cheers

@dlitvakb I don't really see how #112 was related to this issue. I'm having the same issue: Apparently external_pipeline gets triggered when running bundle exec middleman contentful.

Hey @crtvhd,
You should add the .*-site-hash to your .gitignore.
The idea of the DEPLOYING file, is to give users a chance to share deployment platform specific solutions, e.g. "When deploying on Netlify, do such and such to avoid seeing X". It "solves", this issue because this was a platform specific problem that @joshRpowell got to fix, and that's why this document was provided.
The document as of now is currently empty, but I'd love for @joshRpowell to share his solution.
Cheers

@crtvhd I have a PR open for Netlify the DEPLOYING file.
when I need to update Contentful data I have to remove the site-hash
rm -r .*-space-hash

then run
middleman contentful --rebuild


chore: properly quote the values inside LDAP fields for pg_hba.conf

Only some of the values quoted meaning that that could lead to some issues with the pg_hba.conf parser in PostgreSQL. Also, there was an issue with secrets containing a new line at the end, now we add a \ before the newline so PostgreSQL will read it only as one line.
Closes #2688

/test

/ok-to-merge tests have unrelated failures


version 1 french for the GitHub actions wiki

Here is version 1 of the GitHub Actions wiki in French.
Please review the structure of the course and approve the quality of the content and examples.
Let me know if you'd like any further adjustments :)

Merge conflicts due to recent changes to navigation. Please udpate with new navigation from main when you can.


Multiple routes issue

I have the following .Caddyfile :

{
  order rate_limit before basicauth
  admin off
}

(rate_limit_num_per_min) {
  rate_limit {
      zone register_limit {
      key    {http.request.remote.host}
      events {args.0}
      window {args.1}s
      }
  }
}

localhost {

  encode zstd gzip
  reverse_proxy /*  https://www.example.com

  route  /user/login {
    import rate_limit_num_per_min 5 10
  }

  route  /user/register {
   import rate_limit_num_per_min 1 10
  }

}

However on both limited routes the same rate limit is applied (5 requests per 10 minutes) and both routes share the cooldown, which is not the desired outcome.
This is maybe the supposed to work like that (not very experienced with Caddy)?
If there is a better way to do this or even group the rate limit to cover multiple routes with same parameters but not share the limit I would appreciate help.

That's because both those routes use the same zone. Give the zone a different name to use different state.


The type or method 'GetLastErrorText' cannot be used for 'Extension' development.

Why is this not possible?
Is there another way of doing this?

Duplicate of #313.


docs: creating new readme

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Grade range in one slider

Using a custom slider, we could have grade range in a single input. This is probably more intuitive and also frees up some space on the UI as we can compress one line into two as discussed in #39.
The linked plugin will probably be fairly easy to use, but I'd like to make sure that the style matches well, so it may require some CSS customization to get it looking just right.

I tried a quick version with the noUIslider, it get's pretty dense due to the 16 Steps.
and if we want to keep it inline with the other boxes we need to make the slider pretty small. not really happy with this solution, but with some more css modification it may work …

@gardaholm Cool! Couple of ideas:

Let's move the slider to be the first filter. I think this is both a good idea in terms of usability (I assume its the most commonly adjusted filter) and in terms of appearance.
Could we move the "Grade" label to be floating above or below the slider? Actually, do we even need a label? I feel like it is pretty self explanatory. Ideally we'd keep the font conversion as well, at least until we offer some kind of preferences to show one or the other.
If 2 works, we can make the slider the full width of the card (since there is no label). Also, I don't see any issue with increasing the height as well if there are usability issues. Seems okay for it to take up the space of 1.5 or 2 rows of filters if needed (though maybe not necessary)

true, top position is a good idea and we still would win space by removing the 2 input boxes blow for min and max grades …

Nice! LGTM


I want to get path of cropped image

Hello, I used this plugin this works well for me. When I crop the image and want to get the path of this image then get some problems.
Image image = await controller.croppedImage();
data = await image.toByteData(format: ImageByteFormat.png);
I'm passing the image which i get from controller.croppedImage(). But they said The method 'toByteData' isn't defined for the type 'Image'.. So can you please help me out with this problem?

There's no path, the cropping is done on the bitmap itself, that is, in memory. If you need it as a file, save it for yourself first.


fix Zack's ID in OWNERS

Task for https://github.com/open-cluster-management/backlog/issues/9923

:tada: This PR is included in version 2.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Remote connection cannot be established

Does this issue occur when all extensions are disabled?: Yes/No

Version: 1.68.0 (user setup)
Commit: 4af164ea3a06f701fe3e89a2bcbb421d2026b68f
Date: 2022-06-08T11:44:16.822Z
Electron: 17.4.7
Chromium: 98.0.4758.141
Node.js: 16.13.0
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19044
This issue comes from a Codespaces client report where users create a codespace from their private repository so I can't really specify the steps to reproduce.
There's not a clear set of steps to follow in order to reproduce it but the issue can happen on something as simple as opening a medium size file (4k lines or so) within the codespace.
The following logs show up in the devtools console after the message of the remote extension host exiting:
workbench.desktop.main.js:597  WARN Skipping extension /c:/Users/Maximilian.Hartig/.vscode/extensions/ms-vscode.references-view-0.0.89 with lower version 0.0.89.
workbench.desktop.main.js:597  INFO Invoking resolveAuthority(codespaces)
workbench.desktop.main.js:597  INFO resolveAuthority(codespaces) returned 'localhost:35179' after 6746 ms
workbench.desktop.main.js:620 WebSocket connection to '[ws://localhost:35179/stable-4af164ea3a06f701fe3e89a2bcbb421d2026b68f?reconnectionToken=c4c70134-c119-4d92-bdc5-7ce988d666c2&reconnection=false&skipWebSocketFrames=false'](ws://localhost:35179/stable-4af164ea3a06f701fe3e89a2bcbb421d2026b68f?reconnectionToken=c4c70134-c119-4d92-bdc5-7ce988d666c2&reconnection=false&skipWebSocketFrames=false%27) failed:
w @ workbench.desktop.main.js:620
workbench.desktop.main.js:597   ERR [remote-connection][Management   ][c4c70…][initial][localhost:35179] socketFactory.connect() failed or timed out. Error:
workbench.desktop.main.js:597   ERR Error: WebSocket close with status code 1006
    at WebSocket.<anonymous> (vscode-file://vscode-app/c:/Users/Maximilian.Hartig/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:620:43150)
workbench.desktop.main.js:597   ERR [remote-connection] An error occurred in the very first connect attempt, it will be treated as a permanent error! Error:
3workbench.desktop.main.js:597   ERR Error: WebSocket close with status code 1006
    at WebSocket.<anonymous> (vscode-file://vscode-app/c:/Users/Maximilian.Hartig/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:620:43150)
workbench.desktop.main.js:597   ERR Cannot register remote filesystem provider. Error while fetching remote environment. WebSocket close with status code 1006
workbench.desktop.main.js:802 Failed to connect to the remote extension host server (Error: WebSocket close with status code 1006)
onDidChangeNotification @ workbench.desktop.main.js:802
workbench.desktop.main.js:597   ERR Error: WebSocket close with status code 1006
    at WebSocket.<anonymous> (vscode-file://vscode-app/c:/Users/Maximilian.Hartig/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:620:43150)
workbench.desktop.main.js:802 Could not fetch remote environment
onDidChangeNotification @ workbench.desktop.main.js:802
workbench.desktop.main.js:597  WARN Ignoring the error while validating workspace folder vscode-remote://codespaces%2Brahxam-quadrio-kiss-cloud-navigator-jqqqq5q2p7qp/workspaces/kiss-cloud-navigator - No file system provider found for resource 'vscode-remote://codespaces%2Brahxam-quadrio-kiss-cloud-navigator-jqqqq5q2p7qp/workspaces/kiss-cloud-navigator'
workbench.desktop.main.js:597   ERR ENOPRO: No file system provider found for resource 'vscode-remote://codespaces%2Brahxam-quadrio-kiss-cloud-navigator-jqqqq5q2p7qp/workspaces/kiss-cloud-navigator'
    at h.withProvider (vscode-file://vscode-app/c:/Users/Maximilian.Hartig/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:597:14021)
    at async h.doWatch (vscode-file://vscode-app/c:/Users/Maximilian.Hartig/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:597:27783)
    at async vscode-file://vscode-app/c:/Users/Maximilian.Hartig/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:597:27649
workbench.desktop.main.js:597   ERR No file system provider found for resource '[vscode-remote://codespaces%2Brahxam-quadrio-kiss-cloud-navigator-jqqqq5q2p7qp/workspaces/kiss-cloud-navigator/.git/config': ENOPRO: No file system provider found for resource 'vscode-remote://codespaces%2Brahxam-quadrio-kiss-cloud-navigator-jqqqq5q2p7qp/workspaces/kiss-cloud-navigator/.git/config](vscode-remote://codespaces%2Brahxam-quadrio-kiss-cloud-navigator-jqqqq5q2p7qp/workspaces/kiss-cloud-navigator/.git/config':%20ENOPRO:%20No%20file%20system%20provider%20found%20for%20resource%20'vscode-remote://codespaces%2Brahxam-quadrio-kiss-cloud-navigator-jqqqq5q2p7qp/workspaces/kiss-cloud-navigator/.git/config)'
    at h.withProvider (vscode-file://vscode-app/c:/Users/Maximilian.Hartig/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:597:14021)
    at async h.exists (vscode-file://vscode-app/c:/Users/Maximilian.Hartig/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:597:16616)
    at async Promise.all (index 0)
workbench.desktop.main.js:597   ERR ENOPRO: No file system provider found for resource 'vscode-remote://codespaces%2Brahxam-quadrio-kiss-cloud-navigator-jqqqq5q2p7qp/workspaces/kiss-cloud-navigator/app/library/resources/de/quadrio/kiss/cloud_navigator/library/wizard/CustomWizard.js'
    at h.withProvider (vscode-file://vscode-app/c:/Users/Maximilian.Hartig/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:597:14021)
    at async h.withReadProvider (vscode-file://vscode-app/c:/Users/Maximilian.Hartig/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:597:14144)
    at async h.readFileStream (vscode-file://vscode-app/c:/Users/Maximilian.Hartig/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:597:19195)
    at async p.doRead (vscode-file://vscode-app/c:/Users/Maximilian.Hartig/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:2760:42343)
    at async p.readStream (vscode-file://vscode-app/c:/Users/Maximilian.Hartig/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:2760:42018)
    at async wr.resolveFromFile (vscode-file://vscode-app/c:/Users/Maximilian.Hartig/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:2749:66850)
    at async c.doResolve (vscode-file://vscode-app/c:/Users/Maximilian.Hartig/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:2760:36878)
    at async pl.doResolveAsText (vscode-file://vscode-app/c:/Users/Maximilian.Hartig/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:2163:89530)
    at async f.setInput (vscode-file://vscode-app/c:/Users/Maximilian.Hartig/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:2724:94289)
    at async doSetInput (vscode-file://vscode-app/c:/Users/Maximilian.Hartig/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:2722:6429)
    at async doOpenEditor (vscode-file://vscode-app/c:/Users/Maximilian.Hartig/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:2722:4791)
    at async d.openEditor (vscode-file://vscode-app/c:/Users/Maximilian.Hartig/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:2722:3783)
    at async vscode-file://vscode-app/c:/Users/Maximilian.Hartig/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:2925:16970
workbench.desktop.main.js:597   ERR No file system provider found for resource '[vscode-remote://codespaces%2Brahxam-quadrio-kiss-cloud-navigator-jqqqq5q2p7qp/workspaces/kiss-cloud-navigator/pom.xml': ENOPRO: No file system provider found for resource 'vscode-remote://codespaces%2Brahxam-quadrio-kiss-cloud-navigator-jqqqq5q2p7qp/workspaces/kiss-cloud-navigator/pom.xml](vscode-remote://codespaces%2Brahxam-quadrio-kiss-cloud-navigator-jqqqq5q2p7qp/workspaces/kiss-cloud-navigator/pom.xml':%20ENOPRO:%20No%20file%20system%20provider%20found%20for%20resource%20'vscode-remote://codespaces%2Brahxam-quadrio-kiss-cloud-navigator-jqqqq5q2p7qp/workspaces/kiss-cloud-navigator/pom.xml)'
    at h.withProvider (vscode-file://vscode-app/c:/Users/Maximilian.Hartig/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:597:14021)
    at async h.exists (vscode-file://vscode-app/c:/Users/Maximilian.Hartig/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:597:16616)
    at async Promise.all (index 0)
workbench.desktop.main.js:597   ERR WebSocket close with status code 1006: Error: WebSocket close with status code 1006
    at WebSocket.<anonymous> (vscode-file://vscode-app/c:/Users/Maximilian.Hartig/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:620:43150)
workbench.desktop.main.js:597   ERR No file system provider found for resource '[vscode-remote://codespaces%2Brahxam-quadrio-kiss-cloud-navigator-jqqqq5q2p7qp/workspaces/kiss-cloud-navigator': ENOPRO: No file system provider found for resource 'vscode-remote://codespaces%2Brahxam-quadrio-kiss-cloud-navigator-jqqqq5q2p7qp/workspaces/kiss-cloud-navigator](vscode-remote://codespaces%2Brahxam-quadrio-kiss-cloud-navigator-jqqqq5q2p7qp/workspaces/kiss-cloud-navigator':%20ENOPRO:%20No%20file%20system%20provider%20found%20for%20resource%20'vscode-remote://codespaces%2Brahxam-quadrio-kiss-cloud-navigator-jqqqq5q2p7qp/workspaces/kiss-cloud-navigator)'
    at h.withProvider (vscode-file://vscode-app/c:/Users/Maximilian.Hartig/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:597:14021)
    at async h.doResolveFile (vscode-file://vscode-app/c:/Users/Maximilian.Hartig/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:597:15103)
    at async h.resolve (vscode-file://vscode-app/c:/Users/Maximilian.Hartig/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:597:14826)
    at async i.findWorkspaces (vscode-file://vscode-app/c:/Users/Maximilian.Hartig/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:1974:6353)
workbench.desktop.main.js:597   ERR No file system provider found for resource '[vscode-remote://codespaces%2Brahxam-quadrio-kiss-cloud-navigator-jqqqq5q2p7qp/workspaces/kiss-cloud-navigator/.vscode': ENOPRO: No file system provider found for resource 'vscode-remote://codespaces%2Brahxam-quadrio-kiss-cloud-navigator-jqqqq5q2p7qp/workspaces/kiss-cloud-navigator/.vscode](vscode-remote://codespaces%2Brahxam-quadrio-kiss-cloud-navigator-jqqqq5q2p7qp/workspaces/kiss-cloud-navigator/.vscode':%20ENOPRO:%20No%20file%20system%20provider%20found%20for%20resource%20'vscode-remote://codespaces%2Brahxam-quadrio-kiss-cloud-navigator-jqqqq5q2p7qp/workspaces/kiss-cloud-navigator/.vscode)'
    at h.withProvider (vscode-file://vscode-app/c:/Users/Maximilian.Hartig/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:597:14021)
    at async h.exists (vscode-file://vscode-app/c:/Users/Maximilian.Hartig/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:597:16616)
    at async vscode-file://vscode-app/c:/Users/Maximilian.Hartig/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:2259:6314
    at async Promise.all (index 0)
    at async E._initWorkspaceFolderSnippets (vscode-file://vscode-app/c:/Users/Maximilian.Hartig/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:2259:6479)
workbench.desktop.main.js:597   ERR WebSocket close with status code 1006: Error: WebSocket close with status code 1006
    at WebSocket.<anonymous> (vscode-file://vscode-app/c:/Users/Maximilian.Hartig/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:620:43150)
workbench.desktop.main.js:597   ERR Error: WebSocket close with status code 1006
    at WebSocket.<anonymous> (vscode-file://vscode-app/c:/Users/Maximilian.Hartig/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:620:43150)
workbench.desktop.main.js:597   ERR No file system provider found for resource '[vscode-remote://codespaces%2Brahxam-quadrio-kiss-cloud-navigator-jqqqq5q2p7qp/workspaces/kiss-cloud-navigator': ENOPRO: No file system provider found for resource 'vscode-remote://codespaces%2Brahxam-quadrio-kiss-cloud-navigator-jqqqq5q2p7qp/workspaces/kiss-cloud-navigator](vscode-remote://codespaces%2Brahxam-quadrio-kiss-cloud-navigator-jqqqq5q2p7qp/workspaces/kiss-cloud-navigator':%20ENOPRO:%20No%20file%20system%20provider%20found%20for%20resource%20'vscode-remote://codespaces%2Brahxam-quadrio-kiss-cloud-navigator-jqqqq5q2p7qp/workspaces/kiss-cloud-navigator)'
    at h.withProvider (vscode-file://vscode-app/c:/Users/Maximilian.Hartig/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:597:14021)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async h.exists (vscode-file://vscode-app/c:/Users/Maximilian.Hartig/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:597:16616)
    at async Promise.all (index 0)
    at async vscode-file://vscode-app/c:/Users/Maximilian.Hartig/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:2141:2110
workbench.desktop.main.js:620 WebSocket connection to '[ws://localhost:35179/stable-4af164ea3a06f701fe3e89a2bcbb421d2026b68f?reconnectionToken=6d274576-da89-4690-9b13-b8888eb34977&reconnection=false&skipWebSocketFrames=false'](ws://localhost:35179/stable-4af164ea3a06f701fe3e89a2bcbb421d2026b68f?reconnectionToken=6d274576-da89-4690-9b13-b8888eb34977&reconnection=false&skipWebSocketFrames=false%27) failed:
w @ workbench.desktop.main.js:620
workbench.desktop.main.js:597   ERR [remote-connection][ExtensionHost][6d274…][initial][localhost:35179] socketFactory.connect() failed or timed out. Error:
workbench.desktop.main.js:597   ERR Error: WebSocket close with status code 1006
    at WebSocket.<anonymous> (vscode-file://vscode-app/c:/Users/Maximilian.Hartig/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:620:43150)
workbench.desktop.main.js:597   ERR [remote-connection] An error occurred in the very first connect attempt, it will be treated as a permanent error! Error:
workbench.desktop.main.js:597   ERR Error: WebSocket close with status code 1006
    at WebSocket.<anonymous> (vscode-file://vscode-app/c:/Users/Maximilian.Hartig/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:620:43150)
workbench.desktop.main.js:597   ERR Error received from starting extension host (kind: Remote)
workbench.desktop.main.js:597   ERR Error: WebSocket close with status code 1006
    at WebSocket.<anonymous> (vscode-file://vscode-app/c:/Users/Maximilian.Hartig/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:620:43150)
workbench.desktop.main.js:597   ERR WebSocket close with status code 1006: Error: WebSocket close with status code 1006
    at WebSocket.<anonymous> (vscode-file://vscode-app/c:/Users/Maximilian.Hartig/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:620:43150)
DevTools failed to load source map: Could not load content for https://ticino.blob.core.windows.net/sourcemaps/4af164ea3a06f701fe3e89a2bcbb421d2026b68f/core/vs/workbench/workbench.desktop.main.js.map: Load canceled due to load timeout

@alexdima this issue is happening constantly for the user.
He just sent out some screenshots, hope this helps debug the issue better.

@osortega It is not clear from the errors what the root cause is. Is the customer on a machine with a proxy configuration? I have seen in the past that some misconfigured proxies would prevent a connection to localhost. Would it be possible to change the codespaces resolver to return <IP_ADDRESS> instead of localhost, like our other resolvers to avoid any such problems?

@alexdima looks like the costumer can reproduce this without a proxy configuration at all. I went ahead and made the change to the extension anyway but the problem might not be related to that change.
Is there any other information we can gather from the costumer that could help figuring this out?

Hi,
I tried multiple times, but it crashes so fast, that I cannot get it working
[2022-06-29 13:14:12.480] [renderer7] [error] Error: WebSocket close with status code 1006
    at WebSocket.<anonymous> (vscode-file://vscode-app/c:/Users/Maximilian.Hartig/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:620:43150)
[2022-06-29 13:14:12.480] [renderer7] [info] [remote-connection][ExtensionHost][28bc8…][reconnect] A temporarily not available error occurred while trying to reconnect, will try again...
[2022-06-29 13:14:12.481] [renderer7] [info] [remote-connection][ExtensionHost][28bc8…][reconnect] waiting for 10 seconds before reconnecting...
[2022-06-29 13:14:16.669] [renderer7] [info] [remote-connection][Management   ][dd683…][reconnect] resolving connection...
[2022-06-29 13:14:16.670] [renderer7] [info] Invoking resolveAuthority(codespaces)
[2022-06-29 13:14:17.072] [renderer7] [info] [remote-connection][ExtensionHost][28bc8…][reconnect] received socket timeout event.
[2022-06-29 13:14:18.528] [renderer7] [info] resolveAuthority(codespaces) returned 'localhost:40605' after 1859 ms
[2022-06-29 13:14:18.529] [renderer7] [info] [remote-connection][Management   ][dd683…][reconnect] connecting to localhost:40605...
[2022-06-29 13:14:19.098] [renderer7] [error] [remote-connection][Management   ][dd683…][reconnect][localhost:40605] socketFactory.connect() failed or timed out. Error:
[2022-06-29 13:14:19.098] [renderer7] [error] Error: WebSocket close with status code 1006
    at WebSocket.<anonymous> (vscode-file://vscode-app/c:/Users/Maximilian.Hartig/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:620:43150)
[2022-06-29 13:14:19.099] [renderer7] [info] [remote-connection][Management   ][dd683…][reconnect] A temporarily not available error occurred while trying to reconnect, will try again...
[2022-06-29 13:14:19.099] [renderer7] [info] [remote-connection][Management   ][dd683…][reconnect] waiting for 10 seconds before reconnecting...
[2022-06-29 13:14:19.738] [renderer7] [info] [remote-connection][Management   ][dd683…][reconnect] received socket timeout event.
[2022-06-29 13:14:22.493] [renderer7] [info] [remote-connection][ExtensionHost][28bc8…][reconnect] resolving connection...
[2022-06-29 13:14:22.493] [renderer7] [info] [remote-connection][ExtensionHost][28bc8…][reconnect] connecting to localhost:40605...
[2022-06-29 13:14:23.116] [renderer7] [error] [remote-connection][ExtensionHost][28bc8…][reconnect][localhost:40605] socketFactory.connect() failed or timed out. Error:
[2022-06-29 13:14:23.116] [renderer7] [error] Error: WebSocket close with status code 1006
    at WebSocket.<anonymous> (vscode-file://vscode-app/c:/Users/Maximilian.Hartig/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:620:43150)
[2022-06-29 13:14:23.117] [renderer7] [info] [remote-connection][ExtensionHost][28bc8…][reconnect] A temporarily not available error occurred while trying to reconnect, will try again...
[2022-06-29 13:14:23.117] [renderer7] [info] [remote-connection][ExtensionHost][28bc8…][reconnect] waiting for 10 seconds before reconnecting...

@rahxam You mentioned that you had to try multiple times, because it constantly disconnects before you can open the url in a browser. I think you are hitting the exact same problem from your browser as we are hitting from within vscode. Do you perhaps have some piece of software running on your machine which would monitor ports / the network and try to block them? (maybe some sort of aggressive antivirus or network firewall software?)
@osortega You mentioned that you have changed the extension to return <IP_ADDRESS>, but it looks like it still returns localhost in the latest screenshots. Was the change released?
@deepak1556 Do you know of any reasons why we would not be able to connect to a port on localhost? Is there a way to instrument Chromium (maybe a command line flag) so we find out the root cause of the 1006 error. The 1006 error is intentionally lacking information, but maybe you would be aware of some Chromium flags that would lead it to print more info?

Hello @alexdima,
I can reproduce the issue with different notebboks with a completely different software stack and I am not aware of any issue. Also, I have this issue with this Project. Other Projects are working fine. In the same time I had a second codespace open with a different project and it worked find.
Best Regards,
Maximilian

In the same time I had a second codespace open with a different project and it worked fine.

Aha! Thank you, this is super helpful! This then indicates a problem on the server side. Does opening the codespace from the web ui work?

I can use it, but it will lead to the same errors:
[2022-06-29 13:40:56.310] [window] [info] [GitHub.vscode-pull-request-github]: `remoteHub/pullRequest` is not a valid menu identifier
[2022-06-29 13:40:56.601] [window] [error] [xabikos.JavaScriptSnippets]: Unknown language in `contributes.JavaScriptSnippets.language`. Provided value: vue
[2022-06-29 13:40:56.806] [window] [info] Request to 'https://rahxam-quadrio-kiss-cloud-navigator-jqqqq5q2p7qp.github.dev/assets/F08495E28C4EFDCB7757B3A16C6D3D98BA30/38851/vscode-remote-resource?path=%2Fvscode%2Fbin%2Flinux-x64%2F30d9c6cd9483b2cc586687151bcbcd635f373630%2Fextensions%2Fgit-base%2Fsyntaxes%2Fgit-commit.tmLanguage.json&tkn=30d9c6cd9483b2cc586687151bcbcd635f373630' failed with status code 504
[2022-06-29 13:40:56.814] [window] [error] Unable to load and parse grammar for scope text.git-commit from vscode-remote://codespaces%2Brahxam-quadrio-kiss-cloud-navigator-jqqqq5q2p7qp/vscode/bin/linux-x64/30d9c6cd9483b2cc586687151bcbcd635f373630/extensions/git-base/syntaxes/git-commit.tmLanguage.json {}
[2022-06-29 13:40:56.881] [window] [info] Request to 'https://rahxam-quadrio-kiss-cloud-navigator-jqqqq5q2p7qp.github.dev/assets/F08495E28C4EFDCB7757B3A16C6D3D98BA30/38851/vscode-remote-resource?path=%2Fvscode%2Fbin%2Flinux-x64%2F30d9c6cd9483b2cc586687151bcbcd635f373630%2Fextensions%2Fgit-base%2Fsyntaxes%2Fgit-rebase.tmLanguage.json&tkn=30d9c6cd9483b2cc586687151bcbcd635f373630' failed with status code 504
[2022-06-29 13:40:56.889] [window] [error] Unable to load and parse grammar for scope text.git-rebase from vscode-remote://codespaces%2Brahxam-quadrio-kiss-cloud-navigator-jqqqq5q2p7qp/vscode/bin/linux-x64/30d9c6cd9483b2cc586687151bcbcd635f373630/extensions/git-base/syntaxes/git-rebase.tmLanguage.json {}
[2022-06-29 13:40:56.895] [window] [info] Request to 'https://rahxam-quadrio-kiss-cloud-navigator-jqqqq5q2p7qp.github.dev/assets/F08495E28C4EFDCB7757B3A16C6D3D98BA30/38851/vscode-remote-resource?path=%2Fvscode%2Fbin%2Flinux-x64%2F30d9c6cd9483b2cc586687151bcbcd635f373630%2Fextensions%2Fmarkdown-math%2Fsyntaxes%2Fmd-math-block.tmLanguage.json&tkn=30d9c6cd9483b2cc586687151bcbcd635f373630' failed with status code 504
[2022-06-29 13:40:56.902] [window] [error] Unable to load and parse grammar for scope markdown.math.block from vscode-remote://codespaces%2Brahxam-quadrio-kiss-cloud-navigator-jqqqq5q2p7qp/vscode/bin/linux-x64/30d9c6cd9483b2cc586687151bcbcd635f373630/extensions/markdown-math/syntaxes/md-math-block.tmLanguage.json {}
[2022-06-29 13:40:56.936] [window] [info] Request to 'https://rahxam-quadrio-kiss-cloud-navigator-jqqqq5q2p7qp.github.dev/assets/F08495E28C4EFDCB7757B3A16C6D3D98BA30/38851/vscode-remote-resource?path=%2Fvscode%2Fbin%2Flinux-x64%2F30d9c6cd9483b2cc586687151bcbcd635f373630%2Fextensions%2Fmarkdown-math%2Fsyntaxes%2Fmd-math-inline.tmLanguage.json&tkn=30d9c6cd9483b2cc586687151bcbcd635f373630' failed with status code 504
[2022-06-29 13:40:56.943] [window] [error] Unable to load and parse grammar for scope markdown.math.inline from vscode-remote://codespaces%2Brahxam-quadrio-kiss-cloud-navigator-jqqqq5q2p7qp/vscode/bin/linux-x64/30d9c6cd9483b2cc586687151bcbcd635f373630/extensions/markdown-math/syntaxes/md-math-inline.tmLanguage.json {}
[2022-06-29 13:41:01.318] [window] [error] [Extension Host] (node:3115) [DEP0128] DeprecationWarning: Invalid 'main' field in '/home/node/.vscode-remote/extensions/numso.prettier-standard-vscode-0.9.2/node_modules/find-parent-dir/package.json' of 'find-parent-dir.js'. Please either fix that or report it to the module author
(Use `node --trace-deprecation ...` to show where the warning was created)
[2022-06-29 13:41:22.516] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.543] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] starting reconnecting loop. You can get more information with the trace log level.
[2022-06-29 13:41:22.551] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] resolving connection...
[2022-06-29 13:41:22.558] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] connecting to codespaces+rahxam-quadrio-kiss-cloud-navigator-jqqqq5q2p7qp:443...
[2022-06-29 13:41:22.565] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.573] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.581] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.588] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.596] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.604] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.611] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.619] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.627] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.634] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.640] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.647] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.653] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.659] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.665] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.672] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.679] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.685] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.692] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.698] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.705] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.712] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.720] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.727] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.733] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.739] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.746] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.753] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.759] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.766] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.772] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.778] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.784] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.791] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.796] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.803] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.810] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.816] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.823] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.829] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.836] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.843] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.849] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.855] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.862] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.868] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.874] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.881] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.887] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.894] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.901] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.907] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.913] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.920] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.927] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.934] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.940] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.947] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.954] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.960] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.967] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.973] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.980] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.987] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:22.993] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.000] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.007] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.013] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.020] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.028] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.034] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.044] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.051] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.058] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.064] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.071] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.077] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.084] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.091] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.098] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.104] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.111] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.118] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.150] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.160] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.194] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.211] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.223] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.270] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.295] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.304] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.343] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.355] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.368] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.375] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.381] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.387] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.394] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.401] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.408] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.415] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.421] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.428] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.435] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.442] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.449] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.456] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.462] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.469] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.475] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.482] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.488] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.496] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.502] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.509] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.516] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.523] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.530] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.537] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.544] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.551] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.558] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.567] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.574] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.583] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.590] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.597] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.604] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.611] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.618] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.625] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.643] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.652] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.664] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.674] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.694] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.704] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.711] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.718] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.724] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.751] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.768] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.784] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.807] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.814] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.821] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.828] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.835] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.843] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.850] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.864] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.871] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.878] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.885] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.893] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.914] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.922] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.929] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.937] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.943] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.950] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.957] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.964] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.971] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.978] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.986] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:23.993] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:24.000] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:24.007] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:24.015] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:24.021] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:24.029] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:24.037] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:24.045] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:24.053] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:24.060] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:24.067] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:24.075] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:28.055] [window] [info] [remote-connection][Management   ][6bef7…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:28.064] [window] [info] [remote-connection][Management   ][6bef7…][reconnect] starting reconnecting loop. You can get more information with the trace log level.
[2022-06-29 13:41:28.072] [window] [info] [remote-connection][Management   ][6bef7…][reconnect] resolving connection...
[2022-06-29 13:41:28.083] [window] [info] [remote-connection][Management   ][6bef7…][reconnect] connecting to codespaces+rahxam-quadrio-kiss-cloud-navigator-jqqqq5q2p7qp:443...
[2022-06-29 13:41:28.093] [window] [info] [remote-connection][ExtensionHost][b3f39…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).
[2022-06-29 13:41:28.103] [window] [info] [remote-connection][Management   ][6bef7…][reconnect] received socket close event (wasClean: undefined, code: undefined, reason: undefined).

@rahxam Is this failure happening immediately on startup or do you have a chance to interact with the web ui? If you have a chance to interact with the web ui, can you please run View > Output > Log (Remote Server) and then also take a look at Log (Remote Extension Host)? Those logs would be on the server side and might reveal something relevant as to why the server process would crash.

@rahxam I have recently learned that a codespace can be accessed directly via ssh / command line. It would be helpful to get our server-side logs, which can be found inside the codespace at /home/codespace/.vscode-remote/data/logs/.

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


archi download url fix

Archi download url fix, based on the following error:
> scoop install archi
WARN  Purging previous failed installation of archi.
ERROR 'archi' isn't installed correctly.
Removing older version (5.1.0).
'archi' was uninstalled.
Installing 'archi' (5.1.0) [64bit] from extras bucket
The remote server returned an error: (404) Not Found.
URL https://www.archimatetool.com/downloads/archi.php?/5.1.0/Archi-Win64-5.1.0.zip is not valid

[x] I have read the Contributing Guide.

/verify

/verify

Fixed in #12155.


Decouple QT GUI from HWI

It would be nice to have the QT GUI bundled optionally with HWI. I think a lot of different projects use HWI only for the command line and then roll their own user interfaces.
This would reduce bundle load and allow for building on raspberry pi.
I ran into an issue when building on PI related to the shiboken2 package not being compatible with ARM.
relevant comment: https://github.com/python-poetry/poetry/issues/3837#issuecomment-808820635

Here is a PR showing how to do that: https://github.com/bitcoin-core/HWI/pull/561

Close as completed via https://github.com/bitcoin-core/HWI/pull/655?


feat: replace python devnet by katana, remove python as dependency

Feature Request
Describe the Feature Request
feat: replace python devnet by katana, remove python as dependency
### Tasks
- [ ] Add Katana to the repo
- [ ] Integrate Katana in kakarot-rpc
- [ ] Remove python as dependency

Remaining questions:

Do we use docker or directly rust binary?
Do we need to alter kakarot-rpc Dockerfile?

@Eikix , since I have worked on the docker image, I guess I can take this.
On your questions here are my views and suggestions:
- "Do we use docker or directly rust binary?"
I guess it is better to use the docker container, otherwise, we would have to either add katana as a submodule, which will get built then, or use direct binaries, in that case again we would have to use some shell scripting to run the correct one.
This all has already been taken care of in the docker container, and since it has mult-arch built, it will run on native speed.
If someone wants to run the rust binary themselves, then they can do it themselves, as the RPC will simply connect with the local binary via the .env config.
If need be we can in the future add support for Rust binary as well.
"Do we need to alter kakarot-rpc Dockerfile?"
I don't think we need to change anything for that, as the RPC simply takes in .env config to decide where to connect. So, as far as I can see, there should be no need to change it.

Alright sounds good to me;D


[Examples] MLIRGPU Dialect examples

I add gpu.alloc, gpu.dealloc, gpu.memcpy, gpu.memset, gpu.spmm, gpu-index-ops, gpu.shuffle, gpu.printf operations example.
In the mlir document, the gpu-to-cubin pass has been deleted. I fix this bug and change the makefile

Do not simply copy and paste the test from upstream. Modify it specifically according to the meaning you wish to convey through the example, then add comments and analysis. See here as an example.
Add tests for each use case. See here as an example.

Ok, I will rewrite some examples and add comments and analysis on them

Ok, I will rewrite some examples and add some comments, analysis on them. @zhanghb97


Filter out unlocked ships or ships away for mission from ships ready for warm up

In the future such filtering should be done on server side, but for the moment, this is a great filter to check  the most significant waiting list.

Fixed with 430b2a971768c4e053393cdfdbb7fe19a091c978.
That said Ship.away_for_mission is not updated on time or at least not propagated to the client with one shot. Need to fix that.

Fixed with 430b2a971768c4e053393cdfdbb7fe19a091c978.
That said Ship.away_for_mission is not updated on time or at least not propagated to the client with one shot. Need to fix that.


Test05_C depends on Decl'NetCDF plugin but is compiled whenever Decl'HDF5 is

In GitLab by @jbigot on Dec 27, 2021, 11:21

mentioned in commit 1f580236b9b21571841778bfb5ec150de9883e9d

mentioned in commit 6208568c8336bb45cdb7a21897a921151f454ed2

mentioned in commit ca10e4590f5d57804a3e56b9fd71bb3533694b80


404 static template not rendering with 'minimal' example project

just get '404 Not Found' without terminal theme

could be related to #34

#77


use default manager instead of 'objects'

see #411 for context.

Money Quote from the docs:

If you’re writing some code that must handle an unknown model, for example, in a third-party app that implements a generic view, use this manager (or _base_manager) rather than assuming the model has an objects manager.

Hi @simonkern,
I saw this notification only after I saw your response in the discussion. I didn't want to steal your thunder. I mentioned you in the release notes, but I can't undo alter tags or commits the HEAD branch.
I also opted for _base_manager, since the default manager could implement behavior that prevents locks. The base manager, on the other hand, should always work as expected.

Nah, we're good ;-)
Thanks for your quick reaction.


[Q] wandb login in a automated environment

If I want to send a job remotely, how do I login?

Hi @AtomicNess123, happy to help. Could you please expand on your questions and what you meant by "sending a job remotely". Thanks

Thanks. I am sending my script to a supercomputer via ssh to be queued and run.

@AtomicNess123 you can set wandb username and API key in environment variable like below:
os.environ['WANDB_API_KEY']='your-API-key' os.environ['WANDB_ENTITY']='your-wandb-username'

@AbhiKhoyani , thank you for the assistance and feedback to @AtomicNess123. @AtomicNess123 , did the comment address your question or do you need additional support. More on environment variable here.

Thank you! I have modified my script accordingly, and will test tomorrow.
Just one more question:
What does checkin mean here?
# Only needed if you don't checkin the wandb/settings file
WANDB_ENTITY=$username
WANDB_PROJECT=$project

Thank you for the update @AtomicNess123. Checkin is referring to version controlling of your project. The wandb/settings folder contains identifying user information( i.e username). If you set entity/project there, you don't have to set the environment variable from your command line/script.

Thanks! So it doesn't hurt to have it, right? I don't have any wandb/settings folder that I know of. Should I create it?

Hi @AtomicNess123 , you don't have to create a settings file .config/wandb/settings, but you are welcome to if you want more control over your environment settings.