Suggestions regression since 3.6.0-dev.20190713

TypeScript Version: 3.6.0-dev.20190717 (first version with problem 3.6.0-dev.20190713)

Search Terms: completion, completionInfo, autoimport
It is hard to provide repro code since this problem is found in large (4388 files processed by TS) code base with closed source.
However I see two regressions:

Performance hit even for suggestions for variables/imports in current file
Suggestions of other files exports are missing (even if there is already one named import from file where expected completion item located)

Performance problem
import { getSelectorData } from 'tools/store-reference';
...
function retrieveValue() {
    const valueType = getSe/* cursor here */
}

In TS Server log is see huge difference in performance and value for Semantic work
Log for 3.6.0-dev.20190713 (and later)
Info 4207 [15:36:38.239] request:
    {"seq":26,"type":"request","command":"completionInfo","arguments":{"file":"<filename>","line":30,"offset":28,"includeExternalModuleExports":true,"includeInsertTextCompletions":true}}
Info 4208 [15:36:38.240] getCompletionData: Get current token: 0
Info 4209 [15:36:38.240] getCompletionData: Is inside comment: 0
Info 4210 [15:36:38.240] getCompletionData: Get previous token 1: 0
Info 4211 [15:36:38.240] getCompletionData: Get previous token 2: 0
Info 4212 [15:36:38.240] getCompletionsAtPosition: isCompletionListBlocker: 0
Info 4213 [15:36:49.509] getCompletionData: Semantic work: 11269
Info 4214 [15:36:49.518] getCompletionsAtPosition: getCompletionEntriesFromSymbols: 8
Perf 4215 [15:36:49.525] 26::completionInfo: elapsed time (in milliseconds) 11286.3765
Info 4216 [15:36:49.526] response: <response object>

Log for 3.6.0-dev.20190712
Info 4180 [15:47:10.169] request:
    {"seq":23,"type":"request","command":"completionInfo","arguments":{"file":"<filename>","line":30,"offset":28,"includeExternalModuleExports":true,"includeInsertTextCompletions":true}}
Info 4181 [15:47:10.170] getCompletionData: Get current token: 0
Info 4182 [15:47:10.170] getCompletionData: Is inside comment: 0
Info 4183 [15:47:10.170] getCompletionData: Get previous token 1: 0
Info 4184 [15:47:10.170] getCompletionData: Get previous token 2: 0
Info 4185 [15:47:10.171] getCompletionsAtPosition: isCompletionListBlocker: 1
Info 4186 [15:47:10.238] getCompletionData: Semantic work: 67
Info 4187 [15:47:10.250] getCompletionsAtPosition: getCompletionEntriesFromSymbols: 11
Perf 4188 [15:47:10.260] 23::completionInfo: elapsed time (in milliseconds) 90.6148
Info 4189 [15:47:10.261] response: <response object (has more values than latest versions)>

Suggestion form other files
import { getSelectorData /*correctly suggest dispatchAction and other exports here*/ } from 'tools/store-reference';
...
dispatchAction/*no suggestion here*/

This is project written in JS has @types packages in node_modules 1 level above project package.json (since it isn't commited for everyone)
Related Issues:
Probably related to #31893 however it is unclear why there is big performance hit for "local" suggestions and why I'm unable to see suggestions from other files even (in the same folder).
I would understand why there might be no globals @types/* that are not specified in package.json, but not sure why there are no suggestion from other files at all.
Would be glad to follow instructions that will help to narrow this problem, however cannot provide source code.

The behavior I’ve coded here is to look for all package.jsons in scope for the current file and offer auto-imports from all of them.

If this statement in https://github.com/microsoft/TypeScript/pull/31893#issuecomment-502163680 is still true and it would include all package.json files between file and volume root then I would expect to see all suggestions (I have both package.json and node_modules/@types/* 1 level above the project)
@andrewbranch could you please confirm that all package.json files between edited file and volume root will be checked for @types packages?

Whoa, 90ms to 11 seconds? 😱 That’s obviously unacceptable, and since you isolated the change to a single day, I feel quite confident it’s #31893. I’m going to revert it for now because that’s just unusable.
As far as missing things go, there’s a test verifying that multiple levels of package.jsons are looked at, so I’m not sure what the problem is there, but would love your help investigating further once I can improve the performance.
Thanks for the detailed reports!

Do you have any suggestions what I should check (or profile) first in order to narrow root cause?
Also I would like to mention that I encountered this problem on large project, and when tried to create repro with 2-3 files everything worked as expected (suggestions were fast and also contained auto imports from other files).

Shouldn’t #31893 cause the compiler to do less work, not more?

I haven't done any profiling or detailed look at PR (so may be wrong in my assumptions), however first thing that I will check if it is because of deep nesting because of convention + 2 package.json files.
I suspect that there might be penalty when TS checks all parent folders while looking for package.json and then checks paths for dependencies.
Also comment https://github.com/microsoft/TypeScript/pull/31893#pullrequestreview-254809440 isn't marked as resolved so I'm not sure if it is possible to cache everything.
But at this time it's just a speculation on my part.

Shouldn’t #31893 cause the compiler to do less work, not more?

You’d think so intuitively, but no—all those external modules are already in the program, so getting the whole lot of them is pretty easy. Adding additional filters to them adds work. (Particularly, looking for and reading package.json files, and deduplicating re-exports of the same symbol taking into account that some re-exports might be in modules specified in package.json while some may not be.)

Also comment #31893 (review) isn't marked as resolved so I'm not sure if it is possible to cache everything.

It should be possible, but the caching didn’t make it into that PR. If I make a second attempt, it will likely have to include a caching scheme.

Do you have any suggestions what I should check (or profile) first in order to narrow root cause?

Do you mean for the performance regression or for the missing exports? For the perf, my plan is just to run a JS sampling profiler with ndb to see what’s taking so much time. For the missing exports, you could probably figure it out just by stepping through the filtering code I added to importFixes.ts. Of course I plan to do this at some point (likely not this week), but if you want to start investigating, that’s awesome 👍

I reverted the problematic PR, but I’ll leave this one open to track the progress of bringing it back.

@andrewbranch thank you! I will verify timings with that next build and follow up.
Also I tried to debug tsserver, but no luck. I was using approach described in Debugging Language Service in VS Code - I can see that process.env.TSS_DEBUG is set to 5859 inside devtools but I'm unable to attach any debugger (build in chrome or from another VS Code instance).
Do you know if this doc is still correct? If not could you please suggest proper docs on how to do that?
Or I should launch tsserver manually (with ndb) and call it directly to profile?

Yeah, but the order of the steps there is important—is it possible you set the environment variable and then tried to attach to an existing VS Code instance? I usually just do TSS_DEBUG=5859 code ., and then in another Code window, I just do ⌘⇧P → Attach to Node Process → pick the one with 5859.
Also, it’s much easier to debug a local build of TypeScript with source maps—not sure if you were doing that or not. Clone TypeScript, npm run build, then in the test project, point the TypeScript version specified in .vscode/settings.json to TypeScript/built/local. You can also ⌘⇧P → Restart TS Server to pick up a new build (from npm run build in the TypeScript repo) on the fly, then reattach.

If it works for you that it is something strange with my PC - nothing runs on selected post (even after project is fully processed by tsserver and I can see suggestions).
$ TSS_DEBUG=6699 code-insiders

$ curl localhost:6699/json/version
curl: (7) Failed to connect to localhost port 6699: Connection refused

Working examples for browser and node
Browser running with --remote-debugging-port=9222
$ curl localhost:9222/json/version
{
   "Browser": "Edg/<IP_ADDRESS>",
   "Protocol-Version": "1.3",
   "User-Agent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/77.0.3851.0 Safari/537.36 Edg/<IP_ADDRESS>",
   "V8-Version": "7.7.213",
   "WebKit-Version": "537.36 (@6cddbee7eee3614cce9c4226a6d6ace7937636d9)",
   "webSocketDebuggerUrl": "ws://localhost:9222/devtools/browser/75a2d31e-4a2c-494c-adcc-2400f7beecd7"
}

For node started as node --inspect-brk=9966 -e "console.log('works')"
$ curl localhost:9966/json/version
{
  "Browser": "node.js/v10.16.0",
  "Protocol-Version": "1.1"
}

Anyway, now I'm sure that it is correct way to debug tsserver and only one step left.

You can also ⌘⇧P → Restart TS Server to pick up a new build (from npm run build in the TypeScript repo) on the fly, then reattach.

Thanks for the tip! Will be useful when I will attach debugger.

FWIW I’m on a Mac and it looks like you’re on Windows, but everything I see here looks correct 🤔

As usually: checked 3 times on different ports that it doesn't work, posted GitHub comment, tried one more time and voilà - there is response for curl calls and I was able to attach debugger :)
Thanks for the help. I will let you know if I'll find anything useful.

Checked<EMAIL_ADDRESS>and suggestions are fast now - about 220-350 ms.
However it most likely caused by some changes to project and/or PC load because I see same timings for<EMAIL_ADDRESS>Haven't chance to profile slow nightly builds yet.

The culprit is the repeated calls of this stack: getNodeModulesPackageNameFromFileName -> getModuleSpecifier -> ... -> discoverProbableSymlinks. discoverProbablySymlinks seems to account for a pretty huge amount of the new time for getSymbolsFromOtherSourceFileExports.


Unable to make use of processing attribute stripPrefix of node-xml2js library

I'm a bit confused by the documentation and am willing to create a PR to improve it once I have a better understanding of the following. In https://github.com/bobby-brennan/rss-parser#xml2js-passthrough states that you can pass options to xml2js parser. I have the following:
const parser = new Parser({
  xml2js: {
    stripPrefix: "xmlns:event"
  },
});

I would like to make use of stripPrefix of the xml2js library. It still a bit confusing to me how to use xml2js from the documentation. This new xml2js.Parser() as shown in the docs won't work. What I am tryin to accomplish is to get the namespace fields.

from event a more descriptive image would be shown below:

However, when I try to console.log each item from the following function:
const convertRssIntoJson = rssFeed => {
   return new Promise((res, rej) => {
       parser.parseURL(rssFeed, (err, rss) => {
           if (err) {
               return rej(err);
           }
           // console.log(rss.stripPrefix()) is this how is use?
           rss.items.forEach(function(entry) {
             console.log(entry);
           });

           return res(rss);
       });
   });
};

I dont get the namespace fields from event. I would like to get those fields in the JSON without having to add customFields. How can I make use of stripPrefix option an use xml2js?

Currently the xml2js passthrough options are just passed to the xml2js constructor, not to parseString.
I'm happy to accept a PR that adds another option that can be passed to parseString to do things like stripPrefix.


Update SlicerMorph example tests

Tests in SlicerMorph are boiler plate and not currently testing module functionality. These can be used as examples for SlicerMorph specific tests.

Need to revisit this duriing summer.


docs: fix edit url to use main branch

Hello 🙂, this PR fixes a broken URL of the edit button on the documentation.
If you click the edit button on the documentation page, you will redirect to a URL like this: https://github.com/argoproj-labs/argocd-autopilot/edit/master/docs/index.md. But we could not access the page since the branch name was renamed from master to main at some time.
To fix the issue, we need to explicitly specify the edit_uri option of the mkdocs, which uses the master branch by default.
I confirmed this change works on my local build by running make serve-docs command.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thank you @shuuji3!

Thanks for merging and developing the autopilot! I'm currently enjoying my first argocd-autopilot deployment. 🙂


UXP code from Photoshop Actions

I would like to be able to use Alchemist in the follwing workflow: pre-recorded single Action > ActionToJavascript (specifically, the xbytor xtools utility) > Action Manager Code polyfill for UXP. Two sample scripts - generated with xtools - are provided here for test purposes.
resources_jls_071120.zip

I am considering it. This would require quite some time since I have to write a binary parser from scratch and .fromStream() function is not yet present in UXP.

Thanks. Does that missing functionality appear in the development roadmap just updated for UXP by Adobe: https://trello.com/b/Qag1BazI/q4-roadmap? If not, can I help with that?

It doesn't. I can do that feature myself. It will just take longer because this means that I have to write a binary parser not only for actions hierarchy but also descriptors itself with all their data types. So it is just more work.

Implemented in version 1.5.0

Thanks for your efforts. I have not a totally bored Occultist. The basic functionality seems OK, But I see that there are transfer errors, from Occultist back to Alchemist. Can I send the details by email?


BUG: npreadtext does not handle structured dtypes with offsets correctly

npreadtext currently assumes no-offset structured dtypes, including no aligned structured.  Thus, the following fails and would crash for some other examples:
from npreadtext import _loadtxt
_loadtxt(["1,2"], dtype=np.dtype("i2,i8", align=True), delimiter=",")

there is probably no way around adding support for this.  That will require advancing the data pointer differently and storing the row pointer.

Closed by gh-95


Remove hard-coded WP latest version check

This pull request updates the WP version handling and testing in the codebase. It includes the following changes:

Copies the wp-latest.json file from the tmp directory into the tests directory. This allows us to validate against the version of WP that WP is reporting for itself and remove the hard-coded versions.

Adds a helper method that gets the WP version from wp-latest.json.

Uses the version stored in wp-latest.json for testing.

These changes improve the accuracy and flexibility of WP version handling in the codebase.
This will fix the currently failing tests.

Linting is failing due to changes in PHP (or WP) CS relating to this sniff called out in our WP Coding Standards: https://github.com/pantheon-systems/Pantheon-WP-Coding-Standards/blob/main/Pantheon-WP-Minimum/ruleset.xml#L70C20-L70C45
That will need to be addressed separate from this PR

Noting here that there's no need to create a release for this update since it's only affecting testing.


ES6: Modules, Export and Import implementation

### Requirements:

Setup your project with git, NPM, Index.js, index.css, index.html, and create modules directory.
Re-created Awesome books app following ES6 syntax, use different modules, imported modules into index.js file,
Used arrow function for all case.
Display current date using "Luxon" library.

for details requirements please visit the link

hi @Nahid1911  I sent you a message on slack


build: Micronaut Framework 4.0.0-SNAPSHOT

@wetted can you merge master against this branch and get this PR ready?. Thanks!


[Bug] Table data is not populating when extra space inside the mustache binding

Issues occurs when extra space is provided in mustache binding:
{{
currentRow.dob == null ? "no birth" : moment(currentRow.dob).add(24, "years") < moment() ? "small" : moment(currentRow.dob).add(18, "years") < moment() ? "very small" : "very very small"
}}

Worked fine for:
{{currentRow.dob == null ? "no birth" : moment(currentRow.dob).add(24, "years") < moment() ? "small" : moment(currentRow.dob).add(18, "years") < moment() ? "very small" : "very very small"}}

Version: Cloud
OS: MacOSX
Browser: chrome
Environment: production

@hetunandu can you please list out the dependency here, What is pending right now, do we need some help from the UI building pod?

I was expecting the UI building pod to work on it since the change would also need migrations. Pasting the previous response here

This seems to happen only for column properties. The reason for this is that there is a map function under the hood to enable "currentRow". When a \n is added that the beginning of the binding, it makes it invalid. Same problem occurs in List widget child widget's properties
The template today is:
Table1.sanatizedTableData.map((currentRow) => { return currentRow.abc })
If we add a enter here, the js becomes invalid (cant have \n after return

currentRow.abc })```
One solution is to make the template as this
```Table1.sanatizedTableData.map((currentRow) => currentRow.abc )```
I tried this and it works.

> I have created a branch with changes to Table widget. List widget is still not handled in this. Also we will need to migrate old DSLs
fix/new-line-in-start-of-binding


escape 'if' in command.dhall

Before this change, I was seeing:
~/dev/go/src/github.com/ggilmore/buildkite.dhall escape*
❯ dhall --version                                                                                11:00:15
1.35.0
~/dev/go/src/github.com/ggilmore/buildkite.dhall escape*
❯ dhall --file command.dhall                                                                                11:00:25
dhall:
Error: Invalid input

command.dhall:22:13:
   |
22 |           , if : Optional Text
   |             ^
unexpected 'i'
expecting whitespace or }

thanks, i only tested it in dhall-to-json 1.6.4 and dhall 1.32.0
what version is your dhall-to-json? if it is compatible with the newer version I can update the readme too


fix: add ability to pass query params to Get() dns resources and records

Updating the DNSResources and DNSResourceRecords Get() apis to accept query params as specified in the API docs.
This fixes #89

Hey! arturshadnik has not signed the Canonical CLA which is required to get this contribution merged on this project.
Please head over to https://ubuntu.com/legal/contributors to read more about it.

Not sure why the check failed, I signed the CLA earlier today. I've resigned it just in case.

Hi @arturshadnik and thanks for the contribution!
It could be that something is not being properly updated on our side. I will check if there are any issues with the CLA check functionality (could be a stale cache).

Hi @arturshadnik
As you can observe, the issue with cla-check is gone. However, it seems that you need to align the fields inside the structs.
You can try with something like this snippet.


macOS Release Binaries Aren't Signed

macOS binaries should be signed to prevent tampering and eventually to notify gatekeeper that it is allowed to run.

Now to learn about signing in OSX....
Step 1: find a mac

For people having problems running the nebula binary on OSX for now:
-Select the nebula binary from within finder
-Press [control] and click the binary
-select open
-accept the warning and run the binary once
After this you can run it from the terminal without errors

Since both binaries are command line utils, you can also remove them from quarantine:
xattr -d com.apple.quarantine ~/bin/nebula-cert
xattr -d com.apple.quarantine ~/bin/nebula

@RoelWKramer thanks, works like a charm but disables a security layer.
Therefor executable signing is still an important feature request.

This is especially important in corporate environments where gatekeeper (only run signed apps) is mandatory. It would really be great if they could be codesigned.
Slack's Mac app is signed properly (albeit using the tinyspeck.com signature, not slack's own) so the knowledge and keys/Apple subscription are all there :)


Is it possible to edit the yml for an edit page title for a specific model?

Hi guys,
Is it possible to edit the "Edit page" title for a specific model? E.g. just for the User model...
en:
  admin:
    actions:
      edit:
        title: "Edit this but for User model only"

Rikki

That's not possible.


Refine the OLM subscriptions Chart

set default sn_registry to docker.cloudsmith.io/streamnative/operators/sn-catalog:latest
add the configuration channel which configures the channel for all subscriptions to SN operators
add the configuration approval which configures the installPlanApproval for all subscriptions to SN operators
let all SN operators subscribe to the same catalog source sn-catalog`
remove unused catalog sources function-mesh and sn-operator

These changes look good to me. I believe we'll need to get this merged in order for the subscriptions to resume functioning with the latest catalog images. Feel free to merge @fantapsody


Don't enforce SeqN directive order

Checked for duplicates
Yes - I've already checked
Alternatives considered
Yes - and alternatives don't suffice
Related problems
There isn't an intuitive reason (that I see) to enforce that directives are in a certain order, and the error messages aren't helpful because the grammar gets confused.
Describe the feature request
Suggest updating the SeqN grammar to allow directives in any order. If there are mission-specific preferences, it's trivial to implement custom linting to flag an error. Thoughts?

Fixed with Dictionary Caching work

Previously fixed


[NETBEANS-54] Module Review o.eclipse.jgit

Had to change from using a jar called:
org.eclipse.jgit-<IP_ADDRESS>501210735-r-nosignature.jar to
org.eclipse.jgit-<IP_ADDRESS>501210735-r.jar
Since the previous one wasnt in maven.  NO NOTICE file added - Not sure it needs one since its under EDL - see https://github.com/eclipse/jgit/tree/v<IP_ADDRESS>501210735-r

New binaries contain signatures - this might be a problem in the future, if so the build process need to be adjusted to strip the signatures away. Thank you.


[QUESTION] Support for .cjs extension of postcss config file?

Is it possible to specify a different extension for the PostCSS config file, e.g. postcss.config.cjs? Is this a configuration option available?
I'm using SvelteKit which requires the .cjs extensions since it is using ESM as the default import for .js files. I'm assuming perhaps the issue I'm facing has to do with the .cjs extension.
The exact issue is I'm using postcss-nesting to have nested styles but the following fails:
ModuleBuildError: Module build failed (from ./node_modules/svelte-loader/index.js):
Error: ParseError: Identifier is expected (24:5)
22: <style lang="postcss">
23:   section {
24:     & dl {
         ^
25:       @apply mr-6 border-r pr-6 border-gray-300 text-center;

It seems to be choking on the nesting syntax which I assume is either from my PostCSS config not being imported or perhaps the PostCSS addon is not being picked up in the Svelte template

I'm getting the same issue... Is there any fix for that?

so if anyone is having the same issue I found a fix for that: in storybook main.js addons change
- '@storybook/addon-postcss'
+   {
+      name: '@storybook/addon-postcss',
+      options: {
+       postcssLoaderOptions: {
+          implementation: require('postcss'),
+        },
+      },
+    },

@danawoodman the issue can be closed


Close all for multi opened editors

I closed this because it is the same issue for https://github.com/webida/webida-client/issues/359


Bug: Edit with multiple tabs - after "save and edit this item" selected tab got reset

Pull request for issue: https://github.com/Laravel-Backpack/CRUD/issues/2006

You're totally right! Thank you for the PR @tomsb , it fixes the problem. I've just merged and tagged it as 3.6.30, so it's now available with a composer update.
Thanks again! Keep 'em coming.


support ucase, lcase, or both for base32hex?

haskell base32hex code says it's case insensitive, but have Q out on Unison Discord asking if that is their intention

Unison's Arya Irai says case insensitive


module versions are not updated

Is there an existing issue for this?

[X] I have searched the existing issues

Description
With Terraform registry, we are easily reference this module
https://registry.terraform.io/modules/Azure/virtual-machine/azurerm/latest
module "virtual-machine" {
  source  = "Azure/virtual-machine/azurerm"
  version = "1.0.0"
  # insert the 7 required variables here
}

But currently we got new commits, but no new releases generated, still stay on the old codes based on Jun 2

New or Affected Resource(s)/Data Source(s)
all
Potential Terraform Configuration
module "virtual-machine" {
  source  = "Azure/virtual-machine/azurerm"
  version = "1.0.xxx"
  # insert the 7 required variables here
}

References
https://developer.hashicorp.com/terraform/language/modules/syntax

@ozbillwang Versions will appear after creating new tags.


Libtorrent takes so long that machine issuing the command sleeps and script breaks

Trying to use rtinst on an headless Raspberry B+ 1.2, an old slow machine.
As it is headless doing it via an ssh session from another machine,.
The "installing libtorrent" is taking ages (I see from another ssh window that it's compiling at 97% CPU).
If the ssh issuing machine times out/sleeps, I am afraid the script will break and quit working.
In that case is there a way to restart it without beginning anew?
Is there some "nohup" and backgrounding magic I could use when invoking the rtinst script so that even if the issuing ssh closes it will complete?
Thanks a lot.

You have opened an issue which is for issue reporting, not support... What you are looking for is called screen and you can find more information about it at How To Use Linux Screen.


Issue installing this on our build server

Using codeship I'm having issues installing this dependency, the server throws this error while trying:
npm ERR! Failed resolving git HEAD (https://github.com/moshen/node-googlemaps.git) fatal: ambiguous argument 'new-major-version': unknown revision or path not in the working tree.
notes: http://codeship.com

nvm it was my mistake (:


changed functioning of the nav bar

added class name to navigation bar items -"navbar-item"
removed text decoration of items with class -"navbar-item"
changed text color to white for nav bar items
added hover color functionality to the navbar

Thank you @suryanshkapil405, I will take that as a consideration


Failing to pick up first section from Vanes.html

The Vanes & Cranes page includes two tables, one for Northern Hemisphere, one for South.
The shopping list contains a target for the Southern Hemisphere, plus first page layer.
But, this first layer isn't being picked up. It looks-like our blacklist should skip the items before PageLayer, but it doesn't look like that is happening.

Fixed in #504 - one of the new exclusions we'd put in place meant that we were excluding the div we needed to capture because it had an image020 in it.


Images in custom attachment folder don't work

My attachments are in the following folder: \300 Conoscenza\390 allegati
If I reference an image from that folder, I get the following error:

I get the same error if I move the image into another folder.
If I however put the image in the vault root folder, it works.

Thanks for opening the issue.
Can you please share the complete Markdown from the note referencing wop-agenda.jpg? Thank you.

Also I'm transferring this issue to the yanki-obsidian repository since it's specific to the Obsidian plugin.


feat(fs): skip seek if offset is 0

I hereby agree to the terms of the CLA available at: https://databend.rs/dev/policies/cla/
Summary
closing #1056 , avoid seek if offset is 0

Mostly LGTM to me, can you also update the usage in blocking_read?

ok, done


Gladys SD Image Evolution to Debian 11 "Bullseye"

Maybe we can consider moving the actual SD distribution image to next stable version of Debian ?
https://www.raspberrypi.com/news/raspberry-pi-os-debian-bullseye/

Yep I will take a look ASAP. Thanks for issue

Yep I will take a look ASAP. Thanks for issue

@cicoub13 do you have time and pi to test? I've made a bullseye build ( successfully) in local but no pi on my side to test.

I have. What needs to be tested? Just boot and first launch or other specific features?

I've hosted image and info file on dropbox => https://www.dropbox.com/sh/no641e65f6tnvqp/AAD4xkX2ThnQAkt6xtQYJhmNa?dl=0

Flash
Boot
After a few minutes Gladys will be available. :)

Started with success on a Raspberry Pi 3 Model A Plus 🚀
Nothing particular in syslog/dmesg/daemon.log

Nice thank you for feedback, I will push new config file to make a new bullseye release 👍

I think it needs a bit more testing, but yes after that I'll publish it!
Need to check a few things:

Is the Wi-Fi configuration still working as before ? (I know it often change between Debian version)
Is the "Gladys is currently being installed" with temporary Nginx image still working ?
How are "native" Gladys services working with this version? (Bluetooth? USB related services?)

It's quite a big upgrade so I think we need to be really cautious.

Ok for deep check but it's not so big ( like arm64 build )
We are building on top of raspberry os prebuilt kernel.
Wifi config is handle by raspi-config like before.
Hope @cicoub13 can complete your checklist

⚠ https://www.framboise314.fr/raspberry-pi-un-ancien-raspberry-pi-os-pour-resoudre-les-problemes-de-bullseye/
Further tests

Wifi is still working
Gladys currently being installed image (and web page) still working
I will not be able to test some features (usb camera, bluetooth, ...)

Thanks @cicoub13 for the tests! Were you able to test Zigbee2mqtt as well?
I'm happy we weren't too fast to deploy, as the article says Bullseye seems to be breaking some stuff for many users. The comments are quite angry about this release ^^
IMO:

We still need to test physical integrations, it's where we could see most incompatibilities (USB, Bluetooth)
I think it's still good to wait a bit more before making this image the default on the website. I think for now it's good if we advertise this one when people ask, as "beta" image, but could old buster is still the most stable option for most users.

Wrote a post on the forum to get more testers: https://community.gladysassistant.com/t/recherche-de-testeurs-nouvelle-image-gladys-raspberry-pi-os-sous-bullseye/6718

A few issues found:

Zigbee2mqtt USB key not detected: https://community.gladysassistant.com/t/recherche-de-testeurs-nouvelle-image-gladys-raspberry-pi-os-sous-bullseye/6718/2?u=pierre-gilles
Issues with Docker based services: https://community.gladysassistant.com/t/configuration-mqtt-erreur-lors-de-la-connexion-veuillez-verifier-votre-configuration-apres-restauration-de-gladys-sur-limage-bullseye/6719/12?u=pierre-gilles


(Design suggestion) Migrate the UI to egui

It will remove most C/C++ dependencies on your program.

Egui is already used. All C/C++ dependencies are on image decoders.

@Kl4rry What about the GTK3 on the README?

I think that may just be a documentation error. I think I had a dependency on GTK3 but removed it.

@Kl4rry Thanks for the clarification, please update the system dependencies README.


Query paramters

As @patriciagarcia pointed out in https://github.com/hoodiehq/hoodie-server-account/issues/83, we currently do not specify error handling for invalid ?include parameter values. Instead of defining that for all resources & all requests, I think we can simply reference that JSON API instead. That will even reduce the current specification, as we do not need extra specification for things like GET /session?include=account.profile, as this can be derived from the JSON API specification.

I’ll merge it it not make https://github.com/hoodiehq/hoodie-server-account/issues/83 easier to get done, but if there are any objections  / suggestions please let’s address them in follow up issues / PRs


Couldn't read a new frame

Hi,
I met some problems when I was trying to get the frames from the live stream. Here is the error:
warning: Error opening file (/build/opencv/modules/videoio/src/cap_ffmpeg_impl.hpp:856)
warning: udp://<IP_ADDRESS>:8554 (/build/opencv/modules/videoio/src/cap_ffmpeg_impl.hpp:857)
It seems like there is no frame generated by the life stream since the images generated are always 0kb.
The running environment is Hero5, python3.6, windows 7.
Any help is appreciated!
BR
Cheng

Hey there, can you post the full code? What version of OpenCV do you have installed?

I think I should implement it in Linux. It seems like hero5 can’t do the live streaming in windows.

For windows I think the IP address needs to be specified in the file.


Newsletter subscription loading whole page

When hit the submit button on the footer Newsletter subscription form that load whole page instead it will load themselves be great.

@krahamath Yes you right at this stage idea is just to make things works. once it reach to kind a beta level then i will start adding more ajax and etc features. so i keep this idea in my list but possible won't work on it now.


Need an API to set TabColor

Description of the new feature/enhancement
There is an API to set the window title (ui.RawUI.WindowTitle). There should be a way to set the TabColor programmatically. It can be done with WT but only when spawning a new window.

Proposed technical implementation details (optional)
I presume the underlying mechanisms are there, but it just lacks an API akin to that for WindowTitle.

I believe this is a duplicate of #14910. You can try it out by running the command mentioned here in PowerShell: https://github.com/microsoft/terminal/discussions/14903#discussioncomment-5104434

Thanks. I'd close this, but it would still be nice to have it in the API to be uniform.

I want to make sure we're using the same terms.
There is an ambiguity between PowerShell as a console and PowerShell as a programming language. I have .ps1 files associated with pwsh, so I can run them in a cmd window in Windows Terminal. And it works fine to set the title. But the escape sequences only work in a PowerShell tab but not a cmd tab.
I want to make sure I properly understand this.
$host.ui.RawUI.WindowTitle = "hello"
seems to be associated with conhost since it works for any tab, whereas the escape sequence only works for a PowerShell tab.
So this is indeed a conhost request though I just happen to be using pwsh rather than a BAT file.

@BobFrankston Those escape sequences will work from any shell in Windows Terminal, but it's a little more complicated in a cmd shell or BAT file because it's not as easy to get an ESC character. From the cmd prompt you would need to type Ctrl+[ to generate ESC. You also need to be aware that the | character is reserved, so that has to be prefixed with ^|.
As a complete example, you can set the tab to white on red as follows:

Type echo
Press Ctrl+[
Type [2;15;1,^|
Press Return

What you should see at the prompt would be something like this:

To achieve the same thing with a BAT file, you'd need a way to get the ESC character into the file, which you can do like this:

Type echo
Press Ctrl+[
Type > tabcolor.bat
Press Return

At that point, if you edit the tabcolor.bat file in something like notepad, you'll see a ◻ glyph which is the ESC. If you prefix that with echo  and add [2;15;1,^| on the end, you'll have a BAT file that sets the tab color.

You're right -- don't know why my earlier tests were off, but this works in Typescript.
 console.log("\x1b[2;5;82,|");

and pwsh
echo "$([char]27)[2;15;6,|"

One thing that made the bat file example a challenge is that it is not at all obvious that ^[ meant control -- even though I've used that notation for half a century (no exaggeration - the early days of Emacs).  And ^| is not control? The other complicating factor is a plethora of examples that didn't seem consistent.
So, please, is there a URL to the documentation on this?
The RGB examples in https://github.com/microsoft/terminal/discussions/14903 don't seem to work.

And ^| is not control?

No. Visually it may look the same as a control character, but it's two separate characters: ^ and |.

So, please, is there a URL to the documentation on this?

If you meant the ^ escaping syntax for the cmd shell, I found some old documentation on the subject here. Search for carat to find the relevant section.
If you mean the escape sequences for changing the tab color, they aren't covered in the Windows Terminal documentation yet. But DECAC and DECCTR are standard DEC sequences which you can find documented in the DEC VT520 manual (see here and here). And OSC 4 is an XTerm sequence which you can find documented here. The only thing specific to the Windows Terminal implementation is the assignment of palette entries 263 and 264 to the tab colors.

The RGB examples in https://github.com/microsoft/terminal/discussions/14903 don't seem to work.

If you've been using the DECAC sequence to change the tab color, make sure that you've set that back to the default values (with echo "`e[2;263;264,|"), before attempting the RGB examples. Alternatively you could just open a new terminal tab first.

Thanks.
I understand I should wait, but one problem with software is the incremental reward of figuring out each puzzle.
I don't think I need to tell you about all the ambiguities in the examples and  [2 vs ]4 vs. ... and all those color indexes.
So I'll wait till I can find simple documentation for using RGB values for the foreground, background, tabs etc.


add missing variable to collector.update task

What does this PR do?
updates OCB_VERSION in ocb build test and adds file to collector.update invoke task
Motivation
https://dd.slack.com/archives/C06S6HQSK3Q/p1733862714614409
Describe how you validated your changes

pipeline tests should pass before merge

/merge


gnome3.pomodoro: 0.17.0 -> 0.18.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/gnome-shell-pomodoro/versions.
meta.description for gnome3.pomodoro is: "Time management utility for GNOME based on the pomodoro technique"
meta.homepage for gnome3.pomodoro is: "https://gnomepomodoro.org/"
meta.changelog for gnome3.pomodoro is: ""
Updates performed

Version update

To inspect upstream changes

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 0.18.0 with grep in /nix/store/1dq19xbm1xch1kb1gb00mlax2iicih6h-gnome-shell-pomodoro-0.18.0

directory tree listing: https://gist.github.com/e3ea400865d280ea62ae8b3f45dea970

du listing: https://gist.github.com/84ec4a7a1bfb82737995c012138957fb

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

3 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
gnome3.pomodoro

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/1dq19xbm1xch1kb1gb00mlax2iicih6h-gnome-shell-pomodoro-0.18.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A gnome3.pomodoro https://github.com/r-ryantm/nixpkgs/archive/693fdf955971b6ad4a4640045497aa0e0c92c95f.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/1dq19xbm1xch1kb1gb00mlax2iicih6h-gnome-shell-pomodoro-0.18.0
ls -la /nix/store/1dq19xbm1xch1kb1gb00mlax2iicih6h-gnome-shell-pomodoro-0.18.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review 1

1 package failed to build:

gnome3.pomodoro

Maintainer pings
cc @worldofpeace for testing.

Duplicate of https://github.com/NixOS/nixpkgs/pull/103675.


Improved Input Recording Service With Eye Gaze and Optimized Recording

Added Eye Gaze to InputRecordingService and InputPlaybackService. Optimized input recording. Added functions for asynchronous loading and saving:

InputRecordingService and InputPlaybackService now record and simulate eye gaze input.
Recording has been heavily optimized and should be able to keep a consistent framerate even while clearing the recording buffer.
Optimized saving to reduce recording file size and, by extension, save time, by about 50%.
Added functions for saving and loading files asynchronously. Framerate drops do still occur while saving, though it only lasts a few seconds.

Fixes: #8827 #8828

/azp run

/azp run

@julenka Seems that this PR addresses #8827 and #8828, so could you take a look if you could?

/azp run

< in XML comments leads to a parsing error since they're used to denote the start of a tag. < is an escape sequence for <

Ah I see, will revert the change. Could you let me know why there is an used event in InputPlaybackService.cs?

Could you let me know why there is an used event in InputPlaybackService.cs?

That's a public event for users who may want to write code that responds to playback pausing.

Could you let me know why there is an used event in InputPlaybackService.cs?

That's a public event for users who may want to write code that responds to playback pausing.

I see. Could you call it in the Pause function and remove the warning disable statement then?

/azp run

@DominicAglialoro Could you add the missing documentation and some tests as Julia suggested? Please see here for info on tests: https://microsoft.github.io/MixedRealityToolkit-Unity/Documentation/Contributing/UnitTests.html Thanks for the contribution!

/azp run

/azp run

/azp run


How to add location exif data to photo❓

Question
Hi,
We are currently using the react-native-camera library and are planning/hoping to replace it with this.
In react-native-camera it is possible to add the location to the photo exif data (see for example this https://github.com/react-native-camera/react-native-camera/pull/2573#issuecomment-575427945). This is something we need for our usage.
Is that possible to do also in react-native-vision-camera? If so, how can I achieve it?
Many thanks!
What I tried
No response
VisionCamera Version
2.12.0
Additional information

[ ] I am using Expo
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar questions in the issues page as well as in the discussions page and found none.

Hi! Take a look at the PhotoFile's metadata property. Just run the example to find out how it looks on iOS/Android

Hi @mrousavy! Thanks for the quick reply.
I already saw that property, but it looks like this is a read-only property containing the information that is in the photo when it is taken. Unless I am misstaken?
Location data is not automatically included in photos (at least for iOS, they strip it for privacy reasobs), so it wouldn't be included  in the exif meta data.
To have it included, it has to be added manually in one's own app code. In react-native-camera this is done with the writeExif prop as shown in the issue I linked above.
Is there some similar functionality in this lib? Or am I perhaps misunderstanding this and it already exists?

Hey @jaltin, no I am not doing this in VisionCamera yet.
I'm also not quite sure if this should be handled by VisionCamera, I will think about it. Either VisionCamera has a prop for this, or provides an easy API to access Exif data so you can write location yourself.

@mrousavy, in my opinion a good approach would be for this package to allow writing of the location exif data into the image (similar to how react-native-camera does in my link in the initial post).
This package should not be concerned with the location access requests that are needed before an app can get the location data from the os, as this is rather complicated and can take many different paths, and depends on each individual apps needs. It would be messy to maintain that logic here.
It would be great if you would this functionality, as at the moment that is blocking us from migrating over from react-native-camera. I suspect that it would be a functionality many others would benefit from too.
Thanks!

Sure. As a workaround you could write to the File directly, I believe there are Exif writers.

Hi @mrousavy
Any update for this?

Hi, no

Hi @mrousavy, to follow up on your last comment.

Hi, no

Do you have any idea/guesstimate of if/when you would add exif write possibility? Asking so I can have a realistic view of what my alternatatives are going forward.

Hi @jaltin. VisionCamera is a project I maintain for free for other people in my very limited free time, and it's hard to support features that I personally do not use myself, so features I would build entirely for other people, in my free time, for free.
VisionCamera is used in a lot of production apps out there, and I use it in ~4 different apps already (1 is mine, 3 are clients of Margelo).
Since this feature is quite complex and the immediate solution we discussed above (prop to include location data) should not be part of VisionCamera in my opinion, I do not have any plans to support those props in takePhoto(). In my opinion, this just makes everything messy and eventually we will end up like react-native-camera where everything is deprecated and it barely works and isn't maintainable anymore. I have a different philosophy with my libraries; everything should stay as lean as possible. Just like react-native core.
I did however make some experiments with an Image HostObject library (react-native-jsi-image) which will allow you to do any modifications in-memory, that will be separate from VisionCamera, will be very lean and extremely extensible (again, separate libs, different goals, but interoperability and extensibility is a core motivator).
So in short; I will not implement this feature now unless someone pays me to do so, but I will do further experiments with the Image HostObject lib I created and we will potentially have an even better solution to in-memory writing than we had with react-native-camera.

@jaltin did you found a way to add gps location to write exif into image before saving it to camera roll or another path?
i am using react-native-image-picker lib and there is also the same problem when you taking photo there is no gps location in the exif metadata..
did you found a solution?

@jaltin did you found a way to add gps location to write exif into image before saving it to camera roll or another path? i am using react-native-image-picker lib and there is also the same problem when you taking photo there is no gps location in the exif metadata..
did you found a solution?

@alexg-93 No I haven't done any further work on this yet, been busy with other things. If/when I look into it I will share my findings here.

So in short; I will not implement this feature now unless someone pays me to do so, but I will do further experiments with the Image HostObject lib I created and we will potentially have an even better solution to in-memory writing than we had with react-native-camera.

@mrousavy Thanks a lot for clarifying your position and philosophy on this, it makes it much clearer.
Cheers!

I'm also interested in the requested feature. @mrousavy, how much do you want to build the feature? @jaltin, @Pakile, @alexg-93 - are you also interested in contributing? Let's get it built.

I'm not sure how long it would take to implement the feature, and I'm not sure how I want the feature to be implemented.
Location Data could be written in a separate library, since all the Camera specific stuff is already being written in VisionCamera, I'd have to take a look at performance.
I'd love to take a look at this issue through my app development agency with our discounted open-source consulting rate, since my free time at the moment is very unpredictable and I don't want to waste any money here.
What size of financial contributions are you guys thinking?

@mrousavy I concur. Writing location data via the library seems to be outside of the project scope. What I'm suggesting is allowing the user to pass a prop that maps to location metadata the same way you're passing additional props:
this.camera.current.takePhoto({
  ...options,
  location: {
    latitude: '',
    longitude: '',
  }
});

this.camera.current.startRecording({
  ...options,
  location: {
    latitude: '',
    longitude: '',
  }
})

Thoughts?

Hi @mrousavy and @elirichey,
Sorry for my late response on this.
We are having to replace react-native-camera since it is deprecated (as is the case for many other users I suspect). As that repo suggested, we looked at this repo as an alternative and that is where we started to evaluate what was missing and if it is feasible to make the switch.
The location exif data is one of the blockers for us. And in principle we would be willing to co-sponsor work to get it implemented.
However, at the moment we feel that there are too many outstanding issues in this repo and too little activity for us to feel comfortable in attempting the switch.
Don't take me wrong here, we really appreciate the effort by @mrousavy with this package, but we just don't feel that it is mature enough for us to try the switch yet.
I'll leave this issue open as it is still a relevant feature request, but feel free to close it if that is more suitable.

@elirichey I finally got a solution that uses base64 and an external lib to write the location to the image

@elirichey I finally got a solution that uses base64 and an external lib to write the location to the image

@Pakile Awesome! Mind sharing the solution?

@elirichey after taking the image, I get the base64 of the image and use piexifjs to write the location to the picture. it works but is not the most optimal method

@Pakile If it works, it works! Thanks for sharing!

expo-camera does this by exposing an additionalExif option when taking photo like this:
const { coords, timestamp } = location
const picture = await cameraRef.current.takePictureAsync({
  exif: true,
  additionalExif: {
    GPSLatitude: coords.latitude,
    GPSLongitude: coords.longitude,
    GPSAltitude: coords.altitude,
    GPSSpeed: coords.speed,
    GPSTimeStamp: timestamp,
    UserComment: 'blah blah'
  },
})

Where location is the object from expo-location (or some other library). Not sure how hard is this to implement to this library 😄

@elirichey @Pakile: I'm trying to write the GPS data with piexifjs, but having trouble — if you could share a code sample it would be much appreciated.

VisionCamera is not a location library and will not support that, you can add that later on with an EXIF lib

Hey all, I noticed an example never got posted so I wanted to share how we are doing this in our app.
https://gist.github.com/glisom/5889b8fb52352d46278694d8ea83b268

@glisom the issue with piexifjs is that the entire image blob traverses the bridge twice:

tje first time to read it into javascript space
the second time to write it back (with exif tags added) into native storage

although less than ideal, it's probably the only way at the moment

Yeah, I think the only way to avoid would be a native module. Interesting there isn't an exif library already out there for react native specifically.

We have started to implement a native module solution as an open-source package here:
https://github.com/inaturalist/react-native-exif-reader
The package allows reading and writing of EXIF data.
Our main specific use-case is to take photo with vision-camera and write location into the EXIF data.

@mrousavy been using expo-camera but we came to a point where we need to switch to this package for performance and other needs. I've created a native Exif reader/writer to fix the only blocking feature of this package here:
https://github.com/lodev09/react-native-exify
Hoping this helps other people as well.
PS: not to overshadow @jtklein here but we needed a way to write exif to a local file image and not into an asset/camera roll image 🙏

@lodev09 nice work man! That library is really useful, I might use it for ShadowLens.
On another note, I think I'll add location tags to VisionCamera though after a lot of consideration. I'll do that in V4

Thanks @mrousavy! That would be awesome. We'll be using this lib until then. It has been a fun journey learning native ios/android this past few days ✨

Working on a PR for GPS Location here: https://github.com/mrousavy/react-native-vision-camera/pull/2665 :)
Pretty complicated on iOS, but I got it running! 😅

Working on a PR for GPS Location here: #2665 :)
Pretty complicated on iOS, but I got it running! 😅

Thanks for your dedication @mrousavy. I'm trying to access the output of location in the ['EXIF'] prop in photoFile interface, but I can't access it this way. Could you tell me how to access the location data, please?

hi @mrousavy  i   and trying to set the locationtags in my camera but i am getting this  error _NativeCameraModule.CameraModule.getLocationPermissionStatus is not a function (it is undefined)  any idea??


Metal positioning

Rewrite intro so that it points better towards running on real hardware, but the modern way. Position against cloud init.

Fixed by 19c8d16134286ae6395e56ae51f1521c7f52c4e6


Support binary/Base64-encoded secret values

Describe the solution you'd like
I have binary secret data, which I am storing in an external secret provider in Base64-encoded form. I want to be able to inject this Base64 data directly as a Secret value.
This isn't currently possible as ExternalSecrets template values are expected to be strings, which are then Base64-encoded into the K8s Secret values.
What is the added value?
Syncing of K8s Secret values that are binary data are supported.
Observations (Constraints, Context, etc):

Before the "fix" for https://github.com/external-secrets/external-secrets/issues/125 was applied, it looks like this would have been possible.
Previously discussed (by others) at https://github.com/external-secrets/external-secrets/discussions/581.
A key like .spec.target.template.valueType, defaulting to string could be used, and if its value is instead base64, then the value output by the template would be would be assumed to be Base64-encoded already, and would then not be Base64-encoded a second time before creating the Secret.

To clarify, this is for secrets stored on the provider backend as JSON, e.g.:
{
  "foo": "[b64-encoded binary data]",
  "bar": "[b64-encoded string data]"
}

It's possible to work around this, at least on AWS Secrets Manager, by storing the secret as a binary blob (SecretBinary on AWS) and then specifying all of the K8s Secret keys in the ExternalSecret via the data key (see below), but this prevents for example being able to usedataFrom, which would be possible with the above provider secret data, and means that a separate secret has to be created on the provider for at least each of the binary data values.
  data:
  - secretKey: foo
    remoteRef:
      key: aws-binary-secret-key
...

Hey! If i understand your issue correctly it boils down to not being able to extract base64-encoded properties from a secret value.
So you have the following value in AWS SM with key dev/example:
{
  "foo": "[b64-encoded binary data]",
  "bar": "[b64-encoded string data]"
}

and you want to create a secret with:
foo: [binary value]
bar: [binary value]

No, that's not correct.
For example, I have the following:
{
  "foo": "[Base-64-encoded binary data]", # Cannot be decoded to a string.
  "bar": "NTY3OAo=" # b64enc 5678
}

And I want to create a secret with the following (as output by kubectl get secret -o yaml, i.e. values are Base64-encoded):
data:
  foo: [Base-64-encoded binary data]
  bar: NTY3OAo=

dataFrom doesn't work, because it assumes that the values from the provider JSON are the actual secret value, not the secret value that's been Base64-encoded.
I can iterate over the data keys withtemplate, but the values resulting from a template are then Base64-encoded, so if I pass an already Base64-encode value, it's then Base64-encoded a second time into the K8s secret, resulting in a double-encoded value.

Hey! I was able to reproduce this issue, and gladly #701 already fixes it:
setup ran here:
pingenc=$(base64 /bin/ping | tr -d '\n')  #Binary file as base64enc
vault kv put secret/bar my-enc-value=$pingenc

Created the external secret below:
apiVersion: external-secrets.io/v1alpha1
kind: ExternalSecret
metadata:
  name: template-v2
spec:
  refreshInterval: 1h
  secretStoreRef:
    name: vault-backend
    kind: SecretStore
  target:
    name: secret-v2
    # this is how the Kind=Secret will look like
    template:
      engineVersion: v2
      data:
        file: "{{ .file | b64dec }}"
  data:
  - secretKey: file
    remoteRef:
      key: secret/bar
      property: my-enc-value

Got the file key from the secret secret-v2, saved into a new file and tried to run:
t=$(kubectl get secret secret-v2 -o jsonpath='{.data.file}')
echo $t | base64 -d > anewping
chmod u+x anewping
./anewping <IP_ADDRESS>

PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
./anewping: sendmsg: Operation not permitted
./anewping: sendmsg: Operation not permitted
^C
--- <IP_ADDRESS> ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1008ms

Internally the v1.Secret Data is of type map[string][]byte. Actually we don't base64encode the value at all - this is handled by the sdk.
The rendered template is treated as []byte and passed directly to the Secret.Data.


Please change Setting Up Visual Studio Code Mac OSX Section

To start code from terminal you should edit ~/.bash_profile and add the following line of code to that file
function code () { VSCODE_CWD="$PWD" open -n -b "com.microsoft.VSCode" --args $*; }
Please add to this document
to make those changes effective you should either write
source ~/.bash_profile or just . ~/.bash_profile

:+1:

https://github.com/Microsoft/vscode-docs/blob/master/docs/editor/setup.md


Make MarkDoc.Elements immutable

As of now Elements are mutable and should be refactored to only be initialized from their constructors

Total: 1h 2m

Total: 1h 22m


Access Violation when using optional input values

I appear to be running into an access violation when trying to serialize an input object with optional values.
When calling nullableValue.reset() I get the access violation:
https://github.com/microsoft/cppgraphqlgen/blame/main/include/graphqlservice/GraphQLClient.h#L167

I think something else might be causing this actually.

All ModifiedVariable's appear to have the same problem for me, optional or not:

Glad you solved it, thanks!


Add dark icon, for Windows light theme

Hi!
First of all - greap app! I was thinking about writing sth like this myself, since MS is crippling Windows 10 functionality and forces some over-simplified ideas.
But here is the catch: app should use dark tray icon, when user has Light theme enabled.

Light theme is available in Windows Insider builds. I am using 1903, build 18356.1

Unfortunately I've stopped development of this app so I (most probably) won't be looking at sorting this personally. Feel free to contribute a PR/create a fork, will be happy to help with that.
More info in #23

relevant: #24


Unable to connect to VS Code server: Error in request - ENOENT /run/user/1000/vscode-ipc-*.sock

This issue was originally reported in microsoft/vscode-remote-release#6997, but the cause was narrowed down to a file in this repo, src/vs/server/node/server.cli.ts.
Summary:
I'm occasionally but regularly seeing this error when using Remote SSH and running the code command in the built-in terminal.
Unable to connect to VS Code server: Error in request.
Error: connect ENOENT /run/user/1000/vscode-ipc-5cc265b0-6bec-4e0e-99c7-8fc48bccd7c4.sock
    at PipeConnectWrap.afterConnect [as oncomplete] (node:net:1161:16) {
  errno: -2,
  code: 'ENOENT',
  syscall: 'connect',
  address: '/run/user/1000/vscode-ipc-5cc265b0-6bec-4e0e-99c7-8fc48bccd7c4.sock'
}

Here's a temporary fix.
VSCODE_IPC_HOOK_CLI=$( lsof | grep $UID/vscode-ipc | awk '{print $(NF-1)}' | head -n 1 )

It searches for the first available VSCode IPC socket, gets its second to last column for the path to vscode-ipc-*.sock, and updates the relevant env variable.
After running the above line, the error no longer occurs.

It means the error is caused by that environment variable having a "stale" value, pointing at an old socket process which no longer exists.
https://github.com/microsoft/vscode/blob/f8ae10c8d05cf92f55c19b4937f0a5c5c0498778/src/vs/server/node/server.cli.ts#L372-L376
The env variable is passed to the http module for the option socketPath. When it's an invalid value, http.request throws, "Error in request - ENOENT".

The permanent solution seems to be: to check if VSCODE_IPC_HOOK_CLI is pointing to a living socket process, and if needed, refresh the value with the path to an available one.

VSCode Version: 1.69.2
Local OS Version: Darwin x64 18.2.0
Remote OS Version: Ubuntu 22.04 LTS
Remote Extension/Connection Type: SSH

Steps to Reproduce:
The error appears occasionally, maybe after host reboots or when Remote SSH reconnects.

Open new window with Remote SSH
Open terminal with CTRL/CMD+J
Run code some-file.txt

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.70.0. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

Just got this on the latest version using $BROWSER in Codespaces. Reloading the window fixed the issue.

i'm seeing this consistently.

I see it every time i use the code command in the vscode terminal
i have the latest version
i have tried deleting `~/.vscode-server/
the temporary fix described above doesn't work for me

before I apply the 'fix'
Unable to connect to VS Code server: Error in request.
Error: connect EACCES /mnt/wslg/runtime-dir/vscode-ipc-596ebb83-bf0f-4710-ac8e-d6442b87d8a6.sock
    at PipeConnectWrap.afterConnect [as oncomplete] (node:net:1157:16) {
  errno: -13,
  code: 'EACCES',
  syscall: 'connect',
  address: '/mnt/wslg/runtime-dir/vscode-ipc-596ebb83-bf0f-4710-ac8e-d6442b87d8a6.sock'
}

output when i apply the 'fix'
$ VSCODE_IPC_HOOK_CLI=$( lsof | grep $UID/vscode-ipc | awk '{print $(NF-1)}' | head -n 1 )
lsof: WARNING: can't stat() tmpfs file system /mnt/wsl/docker-desktop-data/version-pack-data/community/mount-services-cache/entries/services.tar/eae320734be940e610955446282e0484c6d4bc072f63eb699ff02f3f1dadef28/containers/services/acpid/tmp
      Output information may be incomplete.
lsof: WARNING: can't stat() overlay file system /mnt/wsl/docker-desktop-data/version-pack-data/community/mount-services-cache/entries/services.tar/eae320734be940e610955446282e0484c6d4bc072f63eb699ff02f3f1dadef28/containers/services/acpid/rootfs
      Output information may be incomplete.
lsof: WARNING: can't stat() tmpfs file system /mnt/wsl/docker-desktop-data/version-pack-data/community/mount-services-cache/entries/services.tar/eae320734be940e610955446282e0484c6d4bc072f63eb699ff02f3f1dadef28/containers/services/allowlist/tmp
      Output information may be incomplete.
lsof: WARNING: can't stat() overlay file system /mnt/wsl/docker-desktop-data/version-pack-data/community/mount-services-cache/entries/services.tar/eae320734be940e610955446282e0484c6d4bc072f63eb699ff02f3f1dadef28/containers/services/allowlist/rootfs
      Output information may be incomplete.
lsof: WARNING: can't stat() tmpfs file system /mnt/wsl/docker-desktop-data/version-pack-data/community/mount-services-cache/entries/services.tar/eae320734be940e610955446282e0484c6d4bc072f63eb699ff02f3f1dadef28/containers/services/binfmt/tmp
      Output information may be incomplete.
lsof: WARNING: can't stat() overlay file system /mnt/wsl/docker-desktop-data/version-pack-data/community/mount-services-cache/entries/services.tar/eae320734be940e610955446282e0484c6d4bc072f63eb699ff02f3f1dadef28/containers/services/binfmt/rootfs
      Output information may be incomplete.
lsof: WARNING: can't stat() tmpfs file system /mnt/wsl/docker-desktop-data/version-pack-data/community/mount-services-cache/entries/services.tar/eae320734be940e610955446282e0484c6d4bc072f63eb699ff02f3f1dadef28/containers/services/container-filesystem/tmp
      Output information may be incomplete.
lsof: WARNING: can't stat() overlay file system /mnt/wsl/docker-desktop-data/version-pack-data/community/mount-services-cache/entries/services.tar/eae320734be940e610955446282e0484c6d4bc072f63eb699ff02f3f1dadef28/containers/services/container-filesystem/rootfs
      Output information may be incomplete.
lsof: WARNING: can't stat() tmpfs file system /mnt/wsl/docker-desktop-data/version-pack-data/community/mount-services-cache/entries/services.tar/eae320734be940e610955446282e0484c6d4bc072f63eb699ff02f3f1dadef28/containers/services/devenv-service/tmp
      Output information may be incomplete.
lsof: WARNING: can't stat() overlay file system /mnt/wsl/docker-desktop-data/version-pack-data/community/mount-services-cache/entries/services.tar/eae320734be940e610955446282e0484c6d4bc072f63eb699ff02f3f1dadef28/containers/services/devenv-service/rootfs
      Output information may be incomplete.
lsof: WARNING: can't stat() tmpfs file system /mnt/wsl/docker-desktop-data/version-pack-data/community/mount-services-cache/entries/services.tar/eae320734be940e610955446282e0484c6d4bc072f63eb699ff02f3f1dadef28/containers/services/diagnose/tmp
      Output information may be incomplete.
lsof: WARNING: can't stat() overlay file system /mnt/wsl/docker-desktop-data/version-pack-data/community/mount-services-cache/entries/services.tar/eae320734be940e610955446282e0484c6d4bc072f63eb699ff02f3f1dadef28/containers/services/diagnose/rootfs
      Output information may be incomplete.
lsof: WARNING: can't stat() tmpfs file system /mnt/wsl/docker-desktop-data/version-pack-data/community/mount-services-cache/entries/services.tar/eae320734be940e610955446282e0484c6d4bc072f63eb699ff02f3f1dadef28/containers/services/dns-forwarder/tmp
      Output information may be incomplete.
lsof: WARNING: can't stat() overlay file system /mnt/wsl/docker-desktop-data/version-pack-data/community/mount-services-cache/entries/services.tar/eae320734be940e610955446282e0484c6d4bc072f63eb699ff02f3f1dadef28/containers/services/dns-forwarder/rootfs
      Output information may be incomplete.
lsof: WARNING: can't stat() tmpfs file system /mnt/wsl/docker-desktop-data/version-pack-data/community/mount-services-cache/entries/services.tar/eae320734be940e610955446282e0484c6d4bc072f63eb699ff02f3f1dadef28/containers/services/docker/tmp
      Output information may be incomplete.
lsof: WARNING: can't stat() overlay file system /mnt/wsl/docker-desktop-data/version-pack-data/community/mount-services-cache/entries/services.tar/eae320734be940e610955446282e0484c6d4bc072f63eb699ff02f3f1dadef28/containers/services/docker/rootfs
      Output information may be incomplete.
lsof: WARNING: can't stat() tmpfs file system /mnt/wsl/docker-desktop-data/version-pack-data/community/mount-services-cache/entries/services.tar/eae320734be940e610955446282e0484c6d4bc072f63eb699ff02f3f1dadef28/containers/services/http-proxy/tmp
      Output information may be incomplete.
lsof: WARNING: can't stat() overlay file system /mnt/wsl/docker-desktop-data/version-pack-data/community/mount-services-cache/entries/services.tar/eae320734be940e610955446282e0484c6d4bc072f63eb699ff02f3f1dadef28/containers/services/http-proxy/rootfs
      Output information may be incomplete.
lsof: WARNING: can't stat() tmpfs file system /mnt/wsl/docker-desktop-data/version-pack-data/community/mount-services-cache/entries/services.tar/eae320734be940e610955446282e0484c6d4bc072f63eb699ff02f3f1dadef28/containers/services/kmsg/tmp
      Output information may be incomplete.
lsof: WARNING: can't stat() overlay file system /mnt/wsl/docker-desktop-data/version-pack-data/community/mount-services-cache/entries/services.tar/eae320734be940e610955446282e0484c6d4bc072f63eb699ff02f3f1dadef28/containers/services/kmsg/rootfs
      Output information may be incomplete.
lsof: WARNING: can't stat() tmpfs file system /mnt/wsl/docker-desktop-data/version-pack-data/community/mount-services-cache/entries/services.tar/eae320734be940e610955446282e0484c6d4bc072f63eb699ff02f3f1dadef28/containers/services/nat/tmp
      Output information may be incomplete.
lsof: WARNING: can't stat() overlay file system /mnt/wsl/docker-desktop-data/version-pack-data/community/mount-services-cache/entries/services.tar/eae320734be940e610955446282e0484c6d4bc072f63eb699ff02f3f1dadef28/containers/services/nat/rootfs
      Output information may be incomplete.
lsof: WARNING: can't stat() tmpfs file system /mnt/wsl/docker-desktop-data/version-pack-data/community/mount-services-cache/entries/services.tar/eae320734be940e610955446282e0484c6d4bc072f63eb699ff02f3f1dadef28/containers/services/rngd/tmp
      Output information may be incomplete.
lsof: WARNING: can't stat() overlay file system /mnt/wsl/docker-desktop-data/version-pack-data/community/mount-services-cache/entries/services.tar/eae320734be940e610955446282e0484c6d4bc072f63eb699ff02f3f1dadef28/containers/services/rngd/rootfs
      Output information may be incomplete.
lsof: WARNING: can't stat() tmpfs file system /mnt/wsl/docker-desktop-data/version-pack-data/community/mount-services-cache/entries/services.tar/eae320734be940e610955446282e0484c6d4bc072f63eb699ff02f3f1dadef28/containers/services/sntpc/tmp
      Output information may be incomplete.
lsof: WARNING: can't stat() overlay file system /mnt/wsl/docker-desktop-data/version-pack-data/community/mount-services-cache/entries/services.tar/eae320734be940e610955446282e0484c6d4bc072f63eb699ff02f3f1dadef28/containers/services/sntpc/rootfs
      Output information may be incomplete.
lsof: WARNING: can't stat() tmpfs file system /mnt/wsl/docker-desktop-data/version-pack-data/community/mount-services-cache/entries/services.tar/eae320734be940e610955446282e0484c6d4bc072f63eb699ff02f3f1dadef28/containers/services/socks/tmp
      Output information may be incomplete.
lsof: WARNING: can't stat() overlay file system /mnt/wsl/docker-desktop-data/version-pack-data/community/mount-services-cache/entries/services.tar/eae320734be940e610955446282e0484c6d4bc072f63eb699ff02f3f1dadef28/containers/services/socks/rootfs
      Output information may be incomplete.
lsof: WARNING: can't stat() tmpfs file system /mnt/wsl/docker-desktop-data/version-pack-data/community/mount-services-cache/entries/services.tar/eae320734be940e610955446282e0484c6d4bc072f63eb699ff02f3f1dadef28/containers/services/syn-filter/tmp
      Output information may be incomplete.
lsof: WARNING: can't stat() overlay file system /mnt/wsl/docker-desktop-data/version-pack-data/community/mount-services-cache/entries/services.tar/eae320734be940e610955446282e0484c6d4bc072f63eb699ff02f3f1dadef28/containers/services/syn-filter/rootfs
      Output information may be incomplete.
lsof: WARNING: can't stat() tmpfs file system /mnt/wsl/docker-desktop-data/version-pack-data/community/mount-services-cache/entries/services.tar/eae320734be940e610955446282e0484c6d4bc072f63eb699ff02f3f1dadef28/containers/services/trim-after-delete/tmp
      Output information may be incomplete.
lsof: WARNING: can't stat() overlay file system /mnt/wsl/docker-desktop-data/version-pack-data/community/mount-services-cache/entries/services.tar/eae320734be940e610955446282e0484c6d4bc072f63eb699ff02f3f1dadef28/containers/services/trim-after-delete/rootfs
      Output information may be incomplete.
lsof: WARNING: can't stat() tmpfs file system /mnt/wsl/docker-desktop-data/version-pack-data/community/mount-services-cache/entries/services.tar/eae320734be940e610955446282e0484c6d4bc072f63eb699ff02f3f1dadef28/containers/services/volume-contents/tmp
      Output information may be incomplete.
lsof: WARNING: can't stat() overlay file system /mnt/wsl/docker-desktop-data/version-pack-data/community/mount-services-cache/entries/services.tar/eae320734be940e610955446282e0484c6d4bc072f63eb699ff02f3f1dadef28/containers/services/volume-contents/rootfs
      Output information may be incomplete.
lsof: WARNING: can't stat() tmpfs file system /mnt/wsl/docker-desktop-data/version-pack-data/community/mount-services-cache/entries/services.tar/eae320734be940e610955446282e0484c6d4bc072f63eb699ff02f3f1dadef28/containers/services/vpnkit-forwarder/tmp
      Output information may be incomplete.
lsof: WARNING: can't stat() overlay file system /mnt/wsl/docker-desktop-data/version-pack-data/community/mount-services-cache/entries/services.tar/eae320734be940e610955446282e0484c6d4bc072f63eb699ff02f3f1dadef28/containers/services/vpnkit-forwarder/rootfs
      Output information may be incomplete.
lsof: WARNING: can't stat() tmpfs file system /mnt/wsl/docker-desktop-data/version-pack-data/community/mount-services-cache/entries/services.tar/eae320734be940e610955446282e0484c6d4bc072f63eb699ff02f3f1dadef28/containers/services/vpnkit-tap-vsockd/tmp
      Output information may be incomplete.
lsof: WARNING: can't stat() overlay file system /mnt/wsl/docker-desktop-data/version-pack-data/community/mount-services-cache/entries/services.tar/eae320734be940e610955446282e0484c6d4bc072f63eb699ff02f3f1dadef28/containers/services/vpnkit-tap-vsockd/rootfs
      Output information may be incomplete.

and when i run the command again-
Command is only available in WSL or inside a Visual Studio Code terminal.

so that's.... something

I run ssh remote into a Linux system to use VSCode, occasionally run into this problem as well: typing in th terminal something like code some_file, the file is not opened in current VSCode, but the error message like "Error: connect ENOENT" shows. Usually after restarting VSCode the problem disappears.
Removing ~/.vscode-server is not a viable option, this directory usually has data larger than 1GB.

I have just started seeing this when connected to wsl guests. I'm up-to-date (1.77.3). I have tried deleting ~/.vscode-server* while vscode is not running. doesn't fix it.
in vscode wsl terminal:
$ code FILE
Unable to connect to VS Code server: Error in request.
Error: connect ENOENT /run/user/1000/vscode-ipc-cae625be-217b-4eb3-b699-7043b7a7a557.sock
    at PipeConnectWrap.afterConnect [as oncomplete] (node:net:1157:16) {
  errno: -2,
  code: 'ENOENT',
  syscall: 'connect',
  address: '/run/user/1000/vscode-ipc-cae625be-217b-4eb3-b699-7043b7a7a557.sock'
}
$ ls -l /run/user
total 0
$ lsof | grep $UID/vscode-ipc | wc -l
0

creating the missing directory is a workaround for me:
sudo mkdir -p /run/user/$UID
sudo chown $UID /run/user/$UID

This unfortunately isn't an option when one does not have write access to /run/user/, such as when working on a supercomputer. This is really a bummer since this means it is not possible to connect to a vscode running on an interactive job, such as for example to debug a heavy program. If anyone has any suggestions I'd be glad to hear them.

sudo mkdir -p /run/user/$UID
sudo chown $UID /run/user/$UID

This did the trick for me on WSL2.
Thanks, @Spongman

That (the above commands) also worked for me! Great work

This absolutely works!
VSCODE_IPC_HOOK_CLI=$(lsof | grep $USER | grep vscode-ipc | awk '{print $(NF-1)}' | head -n 1)

Check your VSCODE_IPC_HOOK_CLI contents before and after to see what kind of difference it makes.
Make sure to run it in the right environment.

Since I only have the issue in my Ubuntu 22.04 WSL environment and only when systemd is enabled, this superuser answer helped me to fix the missing /run/user/1000-dir (or whatever your user's id may be) which is stored in XDG_RUNTIME_DIR and is used by vs code:
loginctl enable-linger $(whoami)

After that I can observe on a freshly booted Ubuntu-Distro (wsl --shutdown in a windows-cmd and open new ubuntu shell), that /user/run/1000 exists and is already filled with some files in my case (I have wayland installed). This was not the case before that loginctl command.
Now I can execute code from within vs code just like I could without systemd.

It's alive! Thank you @mx-bernhard
Works like charm

@mx-bernhard that is brilliant! Thanks so much.

Since I only have the issue in my Ubuntu 22.04 WSL environment and only when systemd is enabled, this superuser answer helped me to fix the missing /run/user/1000-dir (or whatever your user's id may be) which is stored in XDG_RUNTIME_DIR and is used by vs code:
loginctl enable-linger $(whoami)

After that I can observe on a freshly booted Ubuntu-Distro (wsl --shutdown in a windows-cmd and open new ubuntu shell), that /user/run/1000 exists and is already filled with some files in my case (I have wayland installed). This was not the case before that loginctl command.
Now I can execute code from within vs code just like I could without systemd.

I've had this problem for ages. this immediately fixed it! Thanks so much.

@mx-bernhard Thanks!!! 👏

Using Remote - SSH after deleting all the forwarded ports I was receiving the error above.

I have the similar issue

**r4wand ** c

Since I only have the issue in my Ubuntu 22.04 WSL environment and only when systemd is enabled, this superuser answer helped me to fix the missing /run/user/1000-dir (or whatever your user's id may be) which is stored in XDG_RUNTIME_DIR and is used by vs code:
loginctl enable-linger $(whoami)

After that I can observe on a freshly booted Ubuntu-Distro (wsl --shutdown in a windows-cmd and open new ubuntu shell), that /user/run/1000 exists and is already filled with some files in my case (I have wayland installed). This was not the case before that loginctl command.
Now I can execute code from within vs code just like I could without systemd.

I've had this problem for ages. this immediately fixed it! Thanks so much.

This resolved my issue for months.
Thank you very much!

@mx-bernhard
It solved my issue for months.
Thank you so much! 👏

@mx-bernhard wow, It worked for me
Thank you so much

My issue was not this issue but rather that other alleged "duplicate" which, for some reason, got closed.
Good news: This absolutely works!
export VSCODE_IPC_HOOK_CLI=$(lsof | grep $USER | grep vscode-ipc | awk '{print $(NF-1)}' | head -n 1)

Check your VSCODE_IPC_HOOK_CLI contents before and after to see what kind of difference it makes.
Make sure to run it in the right environment.

lsof was quite slow in my dev container (>20s) so I modified this script slightly and now it runs in ~1s
export VSCODE_IPC_HOOK_CLI=$(lsof +D /tmp/ | grep $USER | grep vscode-ipc | awk '{print $(NF-1)}' | head -n 1)

@mx-bernhard wow, It worked for me
Thank you so much!!!!

Since I only have the issue in my Ubuntu 22.04 WSL environment and only when systemd is enabled, this superuser answer helped me to fix the missing /run/user/1000-dir (or whatever your user's id may be) which is stored in XDG_RUNTIME_DIR and is used by vs code:
loginctl enable-linger $(whoami)

After that I can observe on a freshly booted Ubuntu-Distro (wsl --shutdown in a windows-cmd and open new ubuntu shell), that /user/run/1000 exists and is already filled with some files in my case (I have wayland installed). This was not the case before that loginctl command.
Now I can execute code from within vs code just like I could without systemd.

I've had this problem for ages. this immediately fixed it! Thanks so much.

Worked for me as well. Thank you!

I'm just putting this here as a note for anyone else who Googles this same error. And potentially like me is using Cursor or VS as an IDE. I'm using using Python's Click library for terminal styling and the webbrowser module for browser integration in VS Code/Cursor, I encountered an issue where the styling suddenly stops working and browser links fail to open. Restarting the IDE doesn't fix the issue and I got the same error message:
Unable to connect to VS Code server: Error in request.
Error: connect ENOENT /run/user/[123456789x]/vscode-ipc-*.sock
I tried Checking environment variables (FORCE_COLOR, TERM, etc.) and looking for VS Code IPC socket issues as suggested by @mx-bernhard but couldn't get those solutions to work.
The solution was irritatingly simple but non-obvious: Kill the current terminal session and start a new one. Simply restarting the IDE was not sufficient. I'm guessing that this is related to the terminal session state and its connection to VS Code's IPC (Inter-Process Communication) socket. When the terminal session is killed and restarted, it creates a fresh connection to VS Code's IPC system, restoring the styling and browser integration functionality.
SSH into server
5.10.0-33-cloud-amd64 #1 SMP Debian 5.10.226-1 (2024-10-03) x86_64 GNU/Linux
Cursor
Version: 0.44.9
VSCode Version: 1.93.1
Commit: 316e524257c2ea23b755332b0a72c50cf23e1b00
Date: 2024-12-26T21:58:59.149Z
Electron: 30.5.1
Chromium: 124.0.6367.243
Node.js: 20.16.0
V8: <IP_ADDRESS>-electron.0
OS: Darwin arm64 23.6.0


Add streaming support to iterate over an array

Thanks for the PR!
Would you mind adding information about why you would like to have these methods? I'm asking because the project is in the early stage, and its API will likely change/evolve. Knowing which methods are necessary and why would be helpful in making decisions about shaping the API.

Because a stream is more a fluent and modern way of iterating as opposed to using an Iterator


[TASK]: Make sure that no PII data is ever logged. And logging in general for that matter...

Task Summary
related to: #246
PII (Personal Identifiable Information) has to be deletable at any point in time. Logging this kind of information out would force us to delete our logs or have complex log sanitation processes, and Logs should be "write only" in the first place anyway.
In general, it is a good idea to remove any and all non critical log statements.
A good log statement has the following properties:

Understandable, i.e. it provides enough information to make sense by itself. Example "New game session :id started", counter example (some component logging out some prop on its own) "3"
It enables us to understand system behavior. Example "Game :id failed to start - :reason", counter example "It is now :time".
It is not noisy. Logging always has to balance verbosity versus noise. It is easy to be tempted to just "log everything", but "logging everything" can be just as bad as "logging nothing", because the sheer amount of data makes it impossible to actually understand the logs

It is understandable that for debugging reasons one might want to add more verbose logs. One option is to put such logs behind feature flags, pipeline enforcement, or proper care during reviews.

Hey @VoidedName, I started work implementing a logging level system as I noticed console.log's were getting pushed to the repo and making their way to production. Of course, as a side effect that somewhat touches on this tickets statement on logging too much vs too little.
I'll make a branch and throw a link in here for further discussion?

@FragAverage Sure. Technically this is a subtask of this, but yea, go ahead.


#130 Add version file for project.

Add version file and apply the version file to different place.

setup.py
console.py

Coverage increased (+0.04%) to 59.5% when pulling 65606151fa4779823466de1b628cd1263cdbcccf on version-file-#130 into e7670d5af0f4105b51f2148ba473cf58560750ba on master.


Is it possible to suport video?

Hi, Good job!
I have used your working to upload image, so I want to know is it possible to suport video in future?

There are currently no plans in future development for this jQuery plugin. I also not really sure if it would work for videos. If this would work the encoded video would probably be so big that the page/browser would struggle.


panzoom function event alert not working in chrome

Hi ,
in the below line of code ,the alert is not coming in chrome
function registerEvents() {
panZoom = svgPanZoom('#ev2d', {
zoomEnabled: true,
controlIconsEnabled: false,
panEnabled: false,
//fit: true,
beforeZoom: function(){
alert("before zoom");
}
, onZoom: function(){
alert("on zoom");
}
, beforePan: function(){
}
, onPan: function(){
}
});
};
}

Please provide a full example (you can host it online on a service like jsfiddle.net).
But I do believe that the problem is somewhere in your code (I just tested last build and it works file).
If it is not the library problem but a problem of your code then please post this question on stackoverflow (like stated here) or any other help boards.


GPSPRINGSECURITYCORE-187: Spring security core plugin fails to deploy on JBOSS 7.1.3

Original Reporter: hsn
Environment: JBOSS 7.1.3-SNAPSHOT
Version: Grails-Spring-Security-Core <IP_ADDRESS>
Migrated From: http://jira.grails.org/browse/GPSPRINGSECURITYCORE-187
Grails application with spring security plugin installed fails to deploy on JBOSS 7.1.3-SNAPSHOT
Error messages are here: https://issues.jboss.org/browse/AS7-3719

13:13:34,031 WARN [org.jboss.as.server.deployment] (MSC service thread 1-13) JBAS015893: Encountered invalid class name 'org.xmlpull.mxp1.MXParser,org.xmlpull.mxp1_serializer.MXSerializer' for service type 'org.xmlpull.v1.XmlPullParserFactory'

{"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014671: Failed services" => {"jboss.web.deployment.default-host."/nxd-0.1"" => "org.jboss.msc.service.StartException in service jboss.web.deployment.default-host."/nxd-0.1": JBAS018040: Failed to start context"},"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.deployment.unit."nxd-0.1.war".jboss.security.jacc Missing[JBAS014861: ]"]}}}

Closing since the referenced bug report indicates it's fixed in JBoss 8


Remove unnecessary params

Description

Remove unnecessary params

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-messaging-webpubsubservice


config options: scriptAsync

Greetings @jamen 👋
How are you?
This is a small addition that allows for the passing of an option that lets js files load async.
If the user passes { scriptAsync: true} then the JS will load in the <head> with <script async="true">
this is a mirror of a change recently added to create-html
have a good weekend! 🌴

Hey @jekrb thanks!  I'll merge this.  But I will warn, your scripts probably wont work with this patch alone.  I figured out couple days ago that hyperscript is escaping the text I input for <script>, and can create syntax errors
I have created h2ml partially for this reason, it doesn't do any escaping.  I will add this in before publishing.

@jekrb So I ended up adding that in, but I also renamed it to pull-create-html, and changed how js/css files are streamed in.

@jamen thank you for the heads up. The changes look really good to me, I like them! 👍


Creating named cells

How can I create a named cell
Let's say I have a value 0.04 and I put it in B1 but that 0.04 is called "rate"
How do I pass in that information to Cell [] ? if at all

Hi @sudipto80 - FsExcel doesn't support that right now but it would be a useful feature.
One thing to consider would be whether we support the naming of ranges - maybe not initially.
Naming individual cells should be relatively straightforward to add.  Do you want to submit a PR or would you like me to have a go at it?  I'm easy either way.  It might take me a few days to get to it.
There are some contributor guidelines here: https://github.com/misterspeedy/FsExcel/blob/main/Contributing.md

Looking at doing this now.

Someone has pointed out that we need to consider the scope of names - worksheet or workbook.  I'm guessing that most people, most of the time will want to create a worksheet-scoped name (or won't care), so to keep that use-case simple, I propose that we add the following "keywords":
Name name // Creates a worksheet-scoped name

type NameScope = | Worksheet | Workbook
ScopedName(name, scope) // Creates an explicitly-scoped name where scope Worksheet or Workbook

Hi Kit, this can be closed now ?


Middleman + Redesign

I replaced Hugo with Middleman and redesigned the whole website, with a similar style to what @madjidtaha started.
Homepage:

Services list:

Looks good to me! Thanks for the kind work. 👍


Add kubeconform

Kubeval (https://github.com/instrumenta/kubeval) says it's no longer maintained and recommend using kubeconform (https://github.com/yannh/kubeconform) instead. It would be nice to be able to set this up instead or alongside kubeval

@FalconerTC thank you for the issue. I'll add kubeconform shortly

@FalconerTC kubeconform was added in v0.9.0
https://github.com/yokawasa/action-setup-kube-tools/releases/tag/v0.9.0
Again thank you so much for the issue!


How can I open an async TCP connection (std)

I'm aware of crates like async-std and edge-net, but I'm trying to figure out what the best path forward for layer-4 async network connections is. My understanding of the workings of async on esp32 is limited still, and so far I've been using esp_idf_svc::hal::task::block_on. Is async-std fully compatible with esp32? Is edge-net a good choice for std-enabled projects? Is there an example of using a TCP connection with esp-idf-svc + std? Thanks.
Update: it looks like async-std is not at all compatible, as it relies on a Posix environment.

Update: it looks like async-std is not at all compatible, as it relies on a Posix environment.

esp-idf is posix compatible in many places. For example the pthread support is done through it, also other filesystem related stuff, systemtime and also networking. That support is how we got a simple std rust support in the first place. Networking stuff is done through lwip and it uses BSD-Sockets. You can find out more about it here

I'm aware of crates like async-std and edge-net, but I'm trying to figure out what the best path forward for layer-4 async network connections is. My understanding of the workings of async on esp32 is limited still, and so far I've been using esp_idf_svc::hal::task::block_on. Is async-std fully compatible with esp32?

No. async-std is not compatible with ESP IDF and I fear it is also stagnating.
Your best bet is the smol crates or if you really insist - tokio.

Is edge-net a good choice for std-enabled projects?

If you use the GitHub version - yes. It has a lot of improvements (in fact, almost a complete redesign) compared to the last version published in crates.io.

Is there an example of using a TCP connection with esp-idf-svc + std? Thanks.

I guess you meant in an async way... because sync std is how it works out of the box without any external crates - because as @Vollbrecht mentioned - ESP IDF is posix-compatible. Anyway:
https://github.com/ivmarkov/rust-esp32-std-demo/blob/main/src/main.rs#L725


Scrollable Textarea

How to make a scrollable Textarea with SimpleMDE, and not create a very long vertical textarea.

Sorry, my bad, didn't read the whole instruction


add 2 error messages to catch invalid parameters being passed to joins

After spending longer than I wanted to debugging my code by adding inspects to Ecto, here are a couple error messages I added to make it easier next time. Happy to refactor if necessary...

I'd recommend adding some tests to these scenarios so it doesn't become hard to maintain later on :)

Refactored as suggested and added tests, please review again.

:green_heart: :blue_heart: :purple_heart: :yellow_heart: :heart:


Added support matrices

for docker releases

Did you also want to document kernel support like on https://docs.amd.com/bundle/ROCm-Release-Notes-v5.4.3/page/About_This_Document.html ?
BTW: I wanted to mess around with 6.2.8 kernel support for my  AMD Radeon™ RX 6850M XT 12GB GDDR6; i.e., Navi22 by hacking around [unofficial] patches referenced from https://github.com/RadeonOpenCompute/ROCm/issues/1668 at https://github.com/xuhuisheng/rocm-build.

Did you also want to document kernel support like on https://docs.amd.com/bundle/ROCm-Release-Notes-v5.4.3/page/About_This_Document.html ?
BTW: I wanted to mess around with 6.2.8 kernel support for my  AMD Radeon™ RX 6850M XT 12GB GDDR6; i.e., Navi22 by hacking around [unofficial] patches referenced from https://github.com/RadeonOpenCompute/ROCm/issues/1668 at https://github.com/xuhuisheng/rocm-build. - Specifically I want to know what kernel(s) are supported by this new version of ROCm and [offtopic] if you had any tips for porting to the latest kernel.

@SamuelMarks
My suggesetion is using upstream kernel of amdgpu version.
Its said that the latest version of kernel had already hold an merged amdgpu-dkms version. If kernel version too new to be supported by ROCm offically, we could use this built-in amdgpu-dkms version directly.

Thanks @xuhuisheng I'll give that a shot

Did you also want to document kernel support like on https://docs.amd.com/bundle/ROCm-Release-Notes-v5.4.3/page/About_This_Document.html ?
BTW: I wanted to mess around with 6.2.8 kernel support for my AMD Radeon™ RX 6850M XT 12GB GDDR6; i.e., Navi22 by hacking around [unofficial] patches referenced from #1668 at https://github.com/xuhuisheng/rocm-build. - Specifically I want to know what kernel(s) are supported by this new version of ROCm and [offtopic] if you had any tips for porting to the latest kernel.

@SamuelMarks I won't block this PR to address your concerns. However, #1995 was raised to track this.


Upgrade the Quorum platform code for Helm3

Description
As a developer I want to add helm3 related code for Quorum network so that the deployment is deployed & cleaned properly.
Please refer to PR : #1035 and #950 containing similar change for Quorum
Steps:

Take latest code from feature/helm3 branch
Run the Quorum network, ensuring that helm3 is installed.
Update the reset network code
Application charts (examples/supplychain-app/charts) should also be ugraded to have end-to-end testing of the platform.
Run reset network and verify all deployment components are deleted

Acceptance Criteria

Running reset network resets the whole network deployments
Testing for all 4 possible combination of consensus+transaction-manager of Quorum.
The cluster after reset, should work with helm2 (no CRD's should be left after cleanup)

4. Application charts (examples/supplychain-app/charts) should also be ugraded to have end-to-end testing of the platform.
=> The upgradation of the application code has been moved to a seperate issue.


[Mod Incompatibility] with the Dynamic Ressource loading option of ModernFix

Block texture are not loaded.
I get missing texture Texture in a Block Shape when placing any slabs and stairs vertically.
The HitBoxes of the Vertically placed shape is fine tough.

blame dynamic resource loading.


Added Heroku Button

Any documentation suggestions are welcome.

I'll close this since ^.

@dblock Sorry for not responding for a while. Anyways, I'll make a new PR to merge my repo with the examples we have so far.

So I've tried to integrate the button so that it will point to somewhere locally in alexa-app, (like /examples/heroku), but it seems as though Heroku doesn't like that.

What it's asking for is that the app.json must be on "the project root directory" (see here), and if this file is not on the root directory, it simply won't work.
While I see what you are asking for, I think it should be designated to a separate repository, since Heroku requires a bunch of specific files and the main repository shouldn't be cluttered with these extra files, should there be any other similar integrations.

So any chance of this PR being re-opened again?

I think what you suggested made sense - ie. to create a separate demo app repo and add it in that repo's README.

So I'll create a new PR, since I've deleted the original repository that contained the changes. If you want, I can transfer ownership of the alexa-app-example repository to the org and make the respective changes on the PR.


Various fixes for awesome.md

git.rustybever cannot be reached. Might be temporary
wording updates

Not sure how we want to handle (temp) unavailable resources.

Maybe having a waiting period for ~ 3 days makes sense? It surely differs for the domain at hand, e.g. I'd expect a git.something to be back earlier than a random personal website domain.

The problem is that within that week all CI checks will fail without any action.
And this causes interruption for automated processed and also takes developer time looking at runs and causes unneeded discussions about the failure per se.

Move linkchecking to a dedicated workflow as we do for security scanning and make it not required.

Good ideas overall.
The check is already optional.
To not block this PR due to this, I've added the resources again, so this PR is not blocked by this discussion.


Custom Certificate validation logic

We'd like to use certificates for backend services that don't match the host names of the machines they are deployed to. Still, we'd like to verify them against the name we expect and a valid chain. Right now, Ocelot only offers default validation or no validation at all. To implement a custom validation, we'd need a custom HttpClientHandler (or at least a way to provide an implementation for HttpClientHandler.ServerCertificateCustomValidationCallback).
Any chance to get this kind of flexibility? One way I could think about would be to have a callback in OcelotPipelineConfiguration that's called on newly created HttpClientHandlers, allowing to modify them before they are used to make backend calls. If this sounds like a valid solution, I could attempt to implement it myself and create a pull request ...

Your solution will be DangerousAcceptAnyServerCertificateValidator