Git client security fix for preflight, additional Goss test to verify that Mastodon deployed succesfully and that the Web UI is accessible and final Jammy fix

Got more stuff:

Fixed permission issue introduced by Git 2.35.2 Security Update: https://github.blog/2022-04-12-git-security-vulnerability-announced/ (Present currently only on Jammy)
Created new Goss test that checks if we deployed the site correctly and is not 500ing
Made localhost respond to mastodon.local

And the best thing for last:

Finally got Ubuntu Jammy working (Ubuntu NodeJS defaults to OpenSSL 1.1.1 and we don't require the legacy OpenSSL flag)

==> jammy: Running provisioner: shell...
    jammy: Running: inline script
    jammy: Set localhost to answer to mastodon.local
==> jammy: Running provisioner: shell...
    jammy: Running: inline script
    jammy: Running Goss tests:
    jammy: The target is ubuntu
    jammy:   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
    jammy:                                  Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 11.8M  100 11.8M    0     0   9.9M      0  0:00:01  0:00:01 --:--:-- 20.3M
    jammy: /tmp/goss: OK
    jammy: ..................................................................................
    jammy:
    jammy: Total Duration: 0.520s
    jammy: Count: 82, Failed: 0, Skipped: 0

Sanity checked everything and lo and behold the new test did its job. Due of missing parentheses the asset precompiling wasn't firing off and resulted in 500. Locally focal and rhel9 work so assuming rest will as well
TASK [web : Precompile assets] *************************************************
skipping: [focal] => {"changed": false, "skip_reason": "Conditional result was False"}

Arbitrary sleep statements in tests should be a measure of last resort. Have you tried Ansible’s “wait_for”?

Also, for the curl-based check, goss has a fairly extensive “http” check: https://github.com/aelsabbahy/goss/blob/master/docs/manual.md#http
We could increase the time between retries for goss as well (via —retry-timeout), which would means it tries a few times to verify/validate.

Apologies, still fairly new in regards of creating tests so don't know the best practices
Should be fixed now and added Ansible pause to sleep 1 minute after the nginx task is ran

Don't worry about your supposed unfamiliarity with the framework(s), I truly appreciate you stepping up and trying to dig into the field :heart:
As for the solution now: I believe this to be worse since now you've added an additional minute to every single Ansible run, regardless of whether or not we're running the tests or not. I think we should either use wait_for (with the relevant nginx port) or tell goss to retry the test itself if it fails once or twice (by using --retry-timeout for the execution).
I'm also a little concerned that it would take nginx up to 60 seconds to be started/serve a response ..

Honestly I think we can get rid of the nginx wait timer altogether as the possible long nginx boot times during local testing are caused by a combination of running 4 different VMs on almost a decade old laptop and the general issues with Virtualbox 7.0.2 and MacOS Ventura.
I'll create a new commit to remove the NGINX timer, and if the builds still pass, we can keep the timer out.

@thunderysteak let me know if you need some more help or wish to pair on a solution, happy to help!

@moritzheiber Believe I got it now with the usage of Ansible's uri and until functions.
It tries 5 times before it gives up with 5 second wait time between retries. On RHEL its instant but Ubuntu needs around 10 to 15 secons for NGINX to start serving content.
In prod deployments it should be functional as well unless the user is in a network environment that does not support reverse NAT (AKA issue that almost only occurs on residential ISPs on outdated routers)
TASK [web : Check if Mastodon instance is up and running] **********************
FAILED - RETRYING: [focal]: Check if Mastodon instance is up and running (5 retries left).
FAILED - RETRYING: [focal]: Check if Mastodon instance is up and running (4 retries left).
ok: [focal] => {"attempts": 3, "cache_control": "max-age=0, public", "changed": false, "connection": "close", "content_security_policy": "base-uri 'none'; default-src 'none'; frame-ancestors 'none'; font-src 'self' https://mastodon.local; img-src 'self' https: data: blob: https://mastodon.local; style-src 'self' https://mastodon.local 'nonce-J55ehOSPmQvhTIFaDdpsJA=='; media-src 'self' https: data: https://mastodon.local; frame-src 'self' https:; manifest-src 'self' https://mastodon.local; connect-src 'self' data: blob: https://mastodon.local https://mastodon.local wss://mastodon.local; script-src 'self' https://mastodon.local 'unsafe-eval'; child-src 'self' blob: https://mastodon.local; worker-src 'self' blob: https://mastodon.local", "content_type": "text/html; charset=utf-8", "cookies": {"_mastodon_session": "BIRKPmPSltzuQ8h8xc75GFG3F5Kzp4e4n42zb5I%2B53fjUzqh7HNHQ%2BD1HU5bRlmlgFPDBRrSmCzHzqLfxYVRdVo9XzR9%2FaxRBV%2B1ZkzTkIOWmEiJiIN7ybSne3Fu9cdOhPxXT4UL9ND0Kwxthijuq4cvvQUblR9xWr0y2nA9a3%2B%2FEi%2BTbxYLhkP0DUoagXqKPmuheicoH3FSX0bm8GVTmJPSXZ4KRA0GCrn2mfY5frFGT4j7qvJU%2BRnIu5FazqGPq5xhIXX4XrGe%2FZ2BZ9FDVOZnn6VWia4i%2F9DebbXgl06ACNXI%2FXI0F3K%2BvDeQchdPA5HrOCW3JnGAUPvUvw%3D%3D--87pobDT1EzQYmZpU--n4yGmBppjjyZT3PJbEUrrg%3D%3D"}, "cookies_string": "_mastodon_session=BIRKPmPSltzuQ8h8xc75GFG3F5Kzp4e4n42zb5I%2B53fjUzqh7HNHQ%2BD1HU5bRlmlgFPDBRrSmCzHzqLfxYVRdVo9XzR9%2FaxRBV%2B1ZkzTkIOWmEiJiIN7ybSne3Fu9cdOhPxXT4UL9ND0Kwxthijuq4cvvQUblR9xWr0y2nA9a3%2B%2FEi%2BTbxYLhkP0DUoagXqKPmuheicoH3FSX0bm8GVTmJPSXZ4KRA0GCrn2mfY5frFGT4j7qvJU%2BRnIu5FazqGPq5xhIXX4XrGe%2FZ2BZ9FDVOZnn6VWia4i%2F9DebbXgl06ACNXI%2FXI0F3K%2BvDeQchdPA5HrOCW3JnGAUPvUvw%3D%3D--87pobDT1EzQYmZpU--n4yGmBppjjyZT3PJbEUrrg%3D%3D", "date": "Mon, 14 Nov 2022 23:37:08 GMT", "elapsed": 0, "etag": "W/\"647c34235ed58b2026651a279bfe29ab\"", "msg": "OK (unknown bytes)", "permissions_policy": "interest-cohort=()", "redirected": false, "referrer_policy": "origin", "server": "Mastodon", "set_cookie": "_mastodon_session=BIRKPmPSltzuQ8h8xc75GFG3F5Kzp4e4n42zb5I%2B53fjUzqh7HNHQ%2BD1HU5bRlmlgFPDBRrSmCzHzqLfxYVRdVo9XzR9%2FaxRBV%2B1ZkzTkIOWmEiJiIN7ybSne3Fu9cdOhPxXT4UL9ND0Kwxthijuq4cvvQUblR9xWr0y2nA9a3%2B%2FEi%2BTbxYLhkP0DUoagXqKPmuheicoH3FSX0bm8GVTmJPSXZ4KRA0GCrn2mfY5frFGT4j7qvJU%2BRnIu5FazqGPq5xhIXX4XrGe%2FZ2BZ9FDVOZnn6VWia4i%2F9DebbXgl06ACNXI%2FXI0F3K%2BvDeQchdPA5HrOCW3JnGAUPvUvw%3D%3D--87pobDT1EzQYmZpU--n4yGmBppjjyZT3PJbEUrrg%3D%3D; path=/; HttpOnly; SameSite=Lax; secure", "status": 200, "strict_transport_security": "max-age=63072000; includeSubDomains", "transfer_encoding": "chunked", "url": "https://mastodon.local/about", "vary": "Accept-Encoding", "x_content_type_options": "nosniff", "x_frame_options": "DENY", "x_request_id": "27b448ce-fb73-479a-af00-830c5079f77a", "x_runtime": "0.330323", "x_xss_protection": "0"}


Getting started with Spring Boot caching

Article checklist
ATTENTION: In your PR - add the ISSUE (topic form) # that this PR corresponds to. You can do this by also adding a comment that states "This fixes #(enter your Idea Content Form #)" to link and close your Idea Content (issue) when the PR is merged.
NOTE: (Please ensure that you have only one open issue + linked pull request at a time. This will ensure that we complete the article in a timely manner from inception to publishing.)
If you have not already please go over our Resources Page for more tips and tricks on how to improve our overall technical writing.
Preliminary Checks - Formatting and Structure

[x] Does your article follow any of the suggested structure formats? - see example formats
[x] Is your article properly formatted in Markdown? - see Github Markdown guide
[x] Have you used the correct folder and file structure? - see Contribution Guidelines
[x] Is your article over 750 words? - Tool: Wordcounter.net
[x] Have you used our preferred heading structure? - H3 (###) and up
[x] Does your article provide enough value and detail about your topic? - Articles should be clear, accurate, and fully explained.
[x] Can your article be understood by beginners? - Assume the audience is smart but has no prior exposure to the common terminology in your article.
[x] Have you included a hero image that is 600x400 pixels and have the copyright to use it? - Tools: Pixlr Image Editor for resizing and Unsplash for Creative Commons images
[x] In your PR - add a comment that states "This fixes #(enter your Idea Content Form #)" to link and close your Idea Content (issue) when the PR is merged.

Grammar & plagiarism checks

[x] Have you spellchecked and grammar checked your article? - Tools: Write&Improve - ProWritingAid -  Grammarly
[x] Please place your article through a 3rd party plagiarism checker? We suggest using Quetext, this tool is free and has a daily limit. We typically accept articles with 10% or less.
[x] Have you checked your article for readability? - Tool: Hemmingway
[x] Have you added sources for quotes and images that aren't yours?

Technical checks

[x] Are your code snippets properly formatted for syntax highlighting - see Syntax guide

Contribution guidelines
For first-time contributors and for more details, see Contributing Guidelines
This fixes #2512

@elizabeth962
Good afternoon and thank you for submitting your article for publishing.
Your article has been entered into our queue and should be reviewed (and published pending any changes) as soon as a peer reviewer is finished with the ones in the queue before it. 🚀
Thank you.

@elizabeth962
Thanks for the PR.
Will do the review by tomorrow.

plagiarism check done

@elizabeth962
Any updates?

Hello @srishilesh I have made the requested changes.

Hi @elizabeth962
This is a really great article. The flow is simple and easy to follow through. Great work! :+1:
You can check my commit for minor fixes.
cc: @srishilesh. Awesome job on the review :rocket:


Running docker behind a proxy on openSuSE 13.2

Hi All,
I'd like to know how to configure docker behind a proxy server.
Thanks in advanced.

Searching the issues for existing similar questions can be very useful: https://github.com/docker/docker/search?q=proxy&state=open&type=Issues&utf8=✓
This isn't a support forum for general questions. There are open issues related to proxies.
I'm going to close this issue as there are no actionable items. Please feel free to comment and discuss.


feat(ChatbotAttachment): Wired FileDropZone into chatbot demo

Had to make some adjustments so the title text wouldn't get cut off. The attachment tag hasn't merged yet (https://github.com/patternfly/virtual-assistant/pull/91), so I have a placeholder in for now.

Preview: https://virtual-assistant-pr-virtual-assistant-95.surge.sh

It does not handle errors right now. Here's the attachment button issue: https://github.com/patternfly/virtual-assistant/issues/100


Spryker: Two vhosts - one for zed and one for yves

Here we create a copy of the "default" vhost, to allow us to inherit the goodness from the php-nginx parent image.
We then allow this new vhost to use slightly different variables to the default version.
site_base.conf.tmpl is customised from php-nginx to remove the "root" statement.
README.md to follow later as it appears to be missing currently(!)

if it wasn't for GCE volume issues I'd have just suggested separate containers for each. Production should ideally be able to scale each separately

In the config I've got going, remote dev will be one container which handles both and for other environments there will be a separate set of containers for yves and zed.

@sroze I want to see if the single vhost way would work before merging this

@andytson-inviqa sure; are you testing it?

I'd like for a way to turn this off, as in a split up environment, you wouldn't want Zed to be routable from the Yves container and might have security implications

Apache image appears to work correctly and APP_SERVICES removes undeclared ones correctly, so I think if somone can just review the last 3 commits we can merge this


Update broken GAB links

GH Source links on https://genappbuilder-demo-lnppzg3rxa-uc.a.run.app/ are currently pointing to 404s

Those links are where this code is going to be hosted once https://github.com/GoogleCloudPlatform/generative-ai/pull/3 gets reviewed and merged


Model not loading

Hi
Thank you for introducing this project as it is a long due.  Without this can't really implement three.js into angular. I am currently using Angular 8 app. All I am trying to do is to load a .stl file in the view.   As there is little or no documentation to say, Getting Started, I had lot of errors like missing module three and other three related modules. I have installed them all.

All I am trying to do is this simple one line to view the model which is not working or throwing any errors.  Can you please give step by step implementation how to make it work?
Thank You

@shan75 you know there is a live demo using this small compontent:
https://tevim.github.io/angular-stl-model-viewer/examples/basic/dist/my-app/
the code is also part of this repo, where you can see, how to integrate it in an angular cli project:
https://github.com/tevim/angular-stl-model-viewer/tree/master/examples/basic

due to inactivity


Unclear how to build a stable snapshot between command line and XCode

Please feel free to close, I'm not sure anyone else cares about this issue beyond Shorebird, seeking council and a bug seemed like the right mechanism to write it down.
We're hitting an issue in 3.16.3 where when we build the app flutter build the snapshot (App.framework) ends up slightly different from when it's built in XCode.  By different here I mean "contents of the Dart snapshot contained within the Mach-O container" not just signing of the Mach-O file (which is often different).
It's probably hard for others outside Shorebird to notice these differences since Mach-O files are often signed and I wouldn't be surprised if the signing is slightly different between command line and XCode and that would mask detection of any snapshot differences (we had to build our own mach-o parser in order to dump the Dart guts out of a mach-o snapshot in order to have something stable to depend on anyway 😮💨 ).
We'd be happy to upstream our mach-o loader to Dart to make it easier for others to run analyze_snapshot on mach-o binaries and see differences like this.  https://github.com/dart-lang/sdk/issues/53938 has a slightly old copy attached.
Our flutter build:
flutter --local-engine-src-path=../engine/src --local-engine=ios_release --local-engine-host=host_release build ipa --release --export-options-plist=ExportOptions.plist

Where our export options is:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
  <key>manageAppVersionAndBuildNumber</key>
  <false/>
  <key>signingStyle</key>
  <string>automatic</string>
  <key>uploadBitcode</key>
  <false/>
  <key>method</key>
  <string>app-store</string>
</dict>
</plist>

flutter build ios --config-only --local-engine-src-path=../engine/src --local-engine ios_release --local-engine-host host_release

With Scheme set to "Release" in XCode (otherwise no changes).
Curious if anyone has any hints (before we go digging through command line flags)?  Presumably some flag is being passed to gen_snapshot in one but not the other causing slight differences?  This breaks our "linker" because we link the "release" snapshot to the "patch" snapshot and depend on the "release" not changing between when we link it (from our CLI build) and when we're trying to debug it (in XCode which is a dev-only workflow).  Alternatively, we could figure out how to hack XCode not to bother building the app snapshot at all (just use the one already built from the CLI) I guess. 🤷.
This currently breaks our debug flow on iOS, because we can't run an updated app in XCode without it crashing in the "omg your base snapshot is not what you linked against" asserts we added.  Linking is a new feature for us, so it's possible this behavior has always existed on iOS and we just never noticed, because we haven't (until now) depended on the snapshot (App.framework) in this way (on Android we do depend on it not changing, but there is no "go build again in xcode" flow in Android so we've not had trouble in this way there).

I suspect the way we'll work around this in Shorebird is just to not try and depend on these two snapshots being identical (which is only a debugging concern) and instead just use whatever App.framework the XCode UI builds for our "linking" step rather than depending on the CLI invocation of XCode/Flutter producing an identical one to the UI invocation.

If you set VERBOSE_SCRIPT_LOGGING=YES in your Xcode build settings you should be able to see all the flags and environment variables being passed into the underlying flutter assemble command
In the Xcode build output under Run custom shell script 'Run Script'

You should be able to compare the exports and flags to the same output from flutter build ipa --verbose to see what's different.

Thank you!


Convert ClassDefKind to an enum class

Motivation

enum class is better than enum (gets it's own namespace, not implicitly
convertible to int).
Test plan

See included automated tests.

Thank you


E?????????

undefined:1
error code: 502
^
SyntaxError: Unexpected token 'e', "error code: 502" is not valid JSON
at JSON.parse ()
at IncomingMessage. (/ratterscannerFrontEnd/dist/index.js:117:37)
at IncomingMessage.emit (node:events:531:35)
at endReadableNT (node:internal/streams/readable:1696:12)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
Node.js v20.15.1

that's precise!

hi @sylus-squared , can you share more about this issue? What causes this error to be triggered?

It just showed up completely randomly when uploading a file and has not showed up since.


fix build issues

My apologies with the last PR. I did not check that there were build issues.

I should check it before the release 😅

Thanks for the quick turnaround :) Looking forward to the new release.

1.2.1 pushed 🎉


design: basic readme covering basic design goals for project

Rendered: https://github.com/rust-embedded/gpio-utils/blob/basic-design/README.md
@nastevens I put some initial thoughts on putting together a gpio-utils.  The main design work that has been done so far is thinking about the configuration file.  Although toml is a bit less commonplace than JSON/YML, it is efficient to parse (comparted to YML) and allows for things like comments (unlike JSON).  https://github.com/toml-lang/toml#comparison-with-other-formats
Obviously, rust support is known to be very good as well (via https://github.com/alexcrichton/toml-rs).

This is super solid 👍
I also really liked seeing clap in action. That is a very elegant interface for command line parameters.


Added timeout for http requests

Problem
Proxy timeout for HTTP-requests
Summary of changes
If the HTTP-request exceeds 15s, it would be killed.

Clippy isn't happy with the latest change, but it overall looks good.
Some rightward drift could be prevented by matching first on the timeout and then the handle error, rather than nesting them.
let result = match result {
    Ok(r) => r,
    Err(e) => timeout,
};
match result {
    Ok(r) => success,
    Err(e) => failure,
}

But I don't mind too much

Yes, I thought about it, but in case of the timeout I still have to return json response with attached headers. And I didn't came up to much nicer way doing it.


Why Transformer++

I found this project being discussed in local llama subreddit.
I read the paper but had questions.
One of the questions that came up that is gnawing at me... Why Transformer++ as your basis of comparison? That model is basically from the Stone Age at this point.
Have you performed any comparisons with more recent SOTA models or against the frontier models?
Thanks!

We chose Transformer++ as the base architecture for our language model because it serves as the foundation for many modern state-of-the-art models, such as LLaMa2/3, Mistral, Qwen, and Yi. These models have built upon the Transformer++ architecture with minor modifications, demonstrating its effectiveness and versatility.
Moreover, recent research on linear transformers, such as Mamba and GLA, has utilized Transformer++ as the baseline for comparison. This further highlights the significance and relevance of the Transformer++ architecture in the field of natural language processing.
The perceived underperformance of our model can be attributed to the limited training data compared to other models. For instance, Gemma was trained on 6 trillion tokens, while LLaMa 3 was trained on an impressive 15 trillion tokens. These numbers are clearly reported in their respective papers, and the training data used is not openly available.
Although we have access to the fineweb corpus, which contains 15 trillion tokens, training a model on such a large dataset remains a challenging and resource-intensive task. It is estimated that renting the necessary H100 GPUs to train on this scale would cost nearly 1 million dollars.
We are actively seeking support and contributions from the community to help us train our model on larger datasets and further improve its performance. If you are interested in contributing those computation resources, we would be immensely grateful for your support. ^_^


Fix events JSON blob format

Proposed changes
The example JSON blob given doesn't match up with the values I experience when running docker-compose events myself, so I'm updating the documentation to save someone else some time. In addition, the events are listed in the API reference, so I've added a link to there for convenience.

Thanks for including the link, it makes total sense! Let's ship it 🚀


Provide the SEMVER "Affected ranges" in addition to the GIT "Affected ranges"

https://osv.dev/vulnerability/GSD-2021-1000677
The "Affected versions" and the GIT "Affected ranges" range values are available. But providing the SEMVER "Afected ranges" too, will help with the enhanced affected component mapping.

This is technically feasible: we'd just need to correlate the introduced/fixed/limit git hashes to the closest git tags and add the additional ranges.

For https://api.osv.dev/v1/vulns/GSD-2021-1000677
"ranges": [
        {
          "type": "GIT",
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/",
          "events": [
            {
              "introduced": "a7d42ddb3099727f58366fa006f850a219cce6c8"
            },
            {
              "limit": "c757c1f1e65d89429db1409429436cf40d47c008"
            }
          ]
        }
      ],

also include a
        {
          "type": "SEMVER",
          "events": [
            {
              "introduced": "3.19-rc6"
            },
            {
              "limit": "4.14.234"
            }
          ]
        }

For the Kernel, this might be difficult if the tag isn't valid SEMVER...


Changes for Implementation of getAudioPassThruCapabilities getter in pro...

Resolve issue #56 with commit 011c835f8eda91aa46c08a8c35d537b9747b909b

@mrapitis we are starting to follow the GitFlow Workflow, which requires feature branches to be merged into the develop branch of the main project.  This PR is attempting to be merged into master, which is supposed to only contain releases.  Here's a good picture explaining the merge process.

Please re-create this PR and request to merge into develop instead of master.


Select checkboxes - How to change checkbox style type?

Hi,
How to change checkboxes style from "indeterminate-checkbox" to "filled-in" checkbox type in select dropdown?

There is no way of doing this currently. What is the use case?

As a designer i have defined style-guide for project.
Checkbox type is filled-in. That means project should be consisten , and each checkbox should have same styling (in my case always visible square/ filled in type of checkbox).

@pavlito you got the solution?


More selection rules discussion + a keyboard shortcut

After deleting a layer, the layer underneath it should be selected. This allows rapid deletion of layers by clicking the trashcan icon, rather than the current behavior, which requires going back and forth between the trash icon and the next layer. When deleting the bottommost layer, the layer above it should be selected.
Finally, we should add a shortcut, say Shift-Backspace, for deleting layers.

This is easy to do. @kne42 is going to move over the current keybindings to the new style soon. once that is done i can do this

CC @stefanv who just pinged me privately to ask for exactly this. ;)

fixed by #472

This is amazing @sofroniewn! I just tried it and it's soooo much nicer! :clap:
I agree wholeheartedly with the decision to merge and revisit default bindings later, btw. =) Thank you!


assertExists: type errors with PageObject

https://github.com/bendemboski/fractal-page-object/compare/main...nicolechung:page_object_element_not_assignable_to_parameter_of_type_pageobject?expand=1

I'm having problems with the selector and assertExists.
Seems like if I specify an ElementType it does not work with assertExists.
Also if I specify an ElementType it does not work with selector as shown in the docs.

@nicolechung I wonder if there's something odd with your IDE setup? When I drop that new test in, my VSCode doesn't flag any errors, and when I run yarn test from the command-line, it compiles and executes correctly (although the test fails, but that's a runtime error because the assertion isn't quite right, not a type error).
Can you try running yarn test and see if you get similar results (i.e. a failed assertion rather than a type error during compilation)?

@bendemboski  Okay, will do and let you know what happens.
For more information, looks like I have typescript 4.9.4 installed in node_modules.
Also the error is reproducible in VS code currently for me:

That first error has nothing to do with assertExists -- for some reason your setup doesn't even understand selector's types. Do you see an error flagged here?

No worries -- feel free to close it out if everything resolves, or update if you're still seeing issues.

Sorry for the late reply - this definitely worked when I updated my fork.
But gave me an idea - I think we have multiple versions in the monorepo, and if I miss any of them I think that's where the type errors are coming from...


Make --open work in chromeOS

sshcode has the functionality to open up code-server in my browser window. I think this is done using the command www-browser --client --url http://www.google.com for example, is it possible to have this feature in code-server?

I think you're missing the point. The point of code-server is to be a server (being ran all the time), while sshcode is a code-server CLI to run it.

I see your point however, for my use case, code-server act as a convenient way of running VSCode locally on a Chromebook without having to use the Linux app architecture.  With this workflow I have no need for sshcode, however I noticed that it was able to open Chrome in my browser from the crostini terminal. This was a nice touch, however if it is too much to ask then its not a problem.

This issue has already solved here: https://github.com/cdr/sshcode/issues/78

This is still an issue, but seems to be really low prio. Will definitely re-open if many requests come in!


fix: DIA-666: [FE] Semantic search polish

Hi @yyassi-heartex!
This PR was created in a response to PRs in upstream repos:

https://github.com/HumanSignal/dm2/pull/266

This PR is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 10 days.

This PR was closed because it has been stalled for 10 days with no activity.


left lane‘s s need to recalculate from reverse

Since the s of the left lane is opposite to the right lane, although we have reversed the lane boundaries, we need to recalculate s too.

#24 we reverse s in lane sample


Suggestion to use consistent information about running docs locally

Idea is about to leave Ruby/Bundler commands in tooling section/readme/space, and on main readme use npm scripts syntax.

Thank you 👍


Clarify NPM requirement

The existing list of three things required to use Capacitor is confusing because it implies that Capacitor is compatible with other package managers which use package.json such as PNPM or Yarn. Updated to clarify the current reality.

this is not true, there are a lot of people using pnpm and yarn in their Capacitor apps without problems


[Test Proxy] Remove custom default matcher setup in proxy_startup

Per https://github.com/Azure/azure-sdk-for-python/pull/23148, we now call set_custom_default_matcher within proxy_startup.py in order to preserve backwards compatibility and ignore headers that we now omit from recordings. Eventually, once recordings are free from these headers, we should remove this call and use the default matcher upon startup.
Note: at this point, we should also revert any set_custom_default_matcher calls that set bodiless matching to set_bodiless_matcher. The linked PR has details about this change as well.

This is tracked by https://github.com/Azure/azure-sdk-for-python/issues/34897.


Add option to execute battles on specific cores

This adds the set_cpus (very bad name, but its what docker uses and I can't come up with anything better, open to your suggestions) option. It lets users specify a list of cores such that instead of every battle being executed on cores 1-4 you can select the first to be on the first two and the second on the other two.

The name may be a bit silly, but I think consistency with the docker syntax is more helpful than coming up with another name ourselves.


Replace invalid characters in string decoding

According to the EDF standard, header fields can only contain (printable) ASCII characters. edfio relaxes this constraint to UTF-8 upon reading, which enables the package to read non-standard EDF files (which are very common in the wild).
However, it might still be the case that people populate header fields with other encodings (such as Latin-1) that are incompatible with UTF-8. For example:
>>> "é".encode("latin1").decode()
UnicodeDecodeError

This PR adds the errors="replace" argument, which adds support for all non-UTF-8 characters, but replaces them with �.
>>> "é".encode("latin1").decode(errors="replace")
'�'

Nice idea, thanks @cbrnr!
To make sure we don't break this in the future, could you add a testcase? I think we don't need to introduce a non-compliant test file just for this, something like that should be fine:
sig = EdfSignal(np.arange(2), 1)
sig._label = "è".ljust(16).encode("latin-1")
assert sig.label == "�"

Also please add an entry to the changelog (and feel free to credit yourself in it)!

Done. I added a more direct test of decode_str(), which spares us from having to import EdfSignal and numpy.

Perfect, thanks @cbrnr!


PLATFORM IS DOWN AND NOT WORKING!!!

Website is down and all the chatbots that are created on this platform not working now.

Hey! Yup, turns out the disk space was totally full because of the debug logging. Couldn't SSH into the server to add a new disk, so I had to go with recovery mode instead. Lesson learned XD
Thanks for giving me the heads up!