Error with kadira and new RC

Hi, I was testing my app using kadira and then I updated to 1.0.4, and this happend:
W20150310-00:48:19.327(-3)? (STDERR)
W20150310-00:48:19.327(-3)? (STDERR) /home/caio/.meteor/packages/meteor-tool/.1.0.42-rc.2.m5ehz++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/server-lib/node_modules/fibers/future.js:245
W20150310-00:48:19.328(-3)? (STDERR) 						throw(ex);
W20150310-00:48:19.328(-3)? (STDERR) 						      ^
W20150310-00:48:19.381(-3)? (STDERR) TypeError: Cannot call method 'bind' of undefined
W20150310-00:48:19.381(-3)? (STDERR)     at [object Object].MongoInternals.RemoteCollectionDriver.open (packages/meteorhacks:collection-utils/index.js:5:1)
W20150310-00:48:19.381(-3)? (STDERR)     at [object Object].open (packages/meteorhacks:kadira/lib/hijack/db.js:11:1)
W20150310-00:48:19.381(-3)? (STDERR)     at [object Object].Mongo.Collection (packages/mongo/collection.js:104:1)
W20150310-00:48:19.382(-3)? (STDERR)     at new Mongo.Collection (packages/dburles:mongo-collection-instances/mongo-instances.js:5:1)
W20150310-00:48:19.382(-3)? (STDERR)     at exposeMongoLivedata (packages/meteorhacks:meteorx/lib/mongo-livedata.js:3:1)
W20150310-00:48:19.382(-3)? (STDERR)     at packages/meteorhacks:meteorx/lib/server.js:21:1
=> Exited with code: 8

Just to note, without the package it runs fine.

Okay. Let me see what going on here.
On 2015 මාර්තු 10, අඟහ at පෙ.ව. 9.17 Caio Reis<EMAIL_ADDRESS>wrote:

Just to note, without the package it runs fine.
—
Reply to this email directly or view it on GitHub
https://github.com/meteorhacks/kadira/issues/141#issuecomment-77991380.

Okay. Seems like you are using meteorhacks:aggregate.
So, I've made some fixes for that.
Update like this:
meteor refresh
meteor update meteorhacks:aggregate

Make sure you've<EMAIL_ADDRESS>
Let me know how this works.

@arunoda, it is working fine now! Thanks!

Awesome.
On Tue, Mar 10, 2015 at 10:42 AM Caio Reis<EMAIL_ADDRESS>wrote:

@arunoda https://github.com/arunoda, it is working fine now! Thanks!
—
Reply to this email directly or view it on GitHub
https://github.com/meteorhacks/kadira/issues/141#issuecomment-77997085.


Network Error in plugin

Describe The Bug:
In the past few days - I’m not certain exactly when this started, or whether a node or other upgrade was involved - the plugin has started to return a network error.
The frustrating part is that I’m able to access http://zero-enviro.local:8001/ and get the JSON output from a browser running on a different machine; and also run curl http://zero-enviro.local:8001/ at the console on the homebridge server:
pi@homebridge:~ $ curl http://zero-enviro.local:8001
{"temperature": "21.55", "pressure": "100301.49", "humidity": "40.35", "P2": "2", "P1": "4"}pi@homebridge:~

Logs:
[25/12/2021, 16:35:17] [EnviroplusAirQuality] Unable to obtain data from Enviro+ Server http://zero-enviro.local:8001 Error: Network Error
    at XMLHttpRequest.req.onerror (/usr/local/lib/node_modules/homebridge-enviroplus/src/platformAccessory.ts:43:16)
    at XMLHttpRequest.dispatchEvent (/usr/local/lib/node_modules/homebridge-enviroplus/node_modules/src/XMLHttpRequest.ts:803:49)
    at XMLHttpRequest.handleError (/usr/local/lib/node_modules/homebridge-enviroplus/node_modules/src/XMLHttpRequest.ts:866:14)
    at ClientRequest.errorHandler_1 (/usr/local/lib/node_modules/homebridge-enviroplus/node_modules/src/XMLHttpRequest.ts:553:22)
    at ClientRequest.emit (node:events:390:28)
    at Socket.socketErrorListener (node:_http_client:447:9)
    at Socket.emit (node:events:390:28)
    at emitErrorNT (node:internal/streams/destroy:157:8)
    at emitErrorCloseNT (node:internal/streams/destroy:122:3)
    at processTicksAndRejections (node:internal/process/task_queues:83:21)

Plugin Config:
This is the Enviro+ section of the homebridge config.
       {
            "server": "http://zero-enviro.local:8001",
            "serial": "1234567890",
            "interval": 5,
            "excellent": 10,
            "good": 20,
            "fair": 25,
            "inferior": 50,
            "poor": 50,
            "platform": "EnviroplusAirQuality"
        }

Environment:

Plugin Version: 1.0.2
Homebridge Version: 1.3.8
Node.js Version: 16.13.1
NPM Version: 8.1.2
Operating System: Raspberry Pi OS Bullseye

Doing some debugging on this locally. I modified platformAccessory.js to log the error in more detail, and it looks like it is hitting a DNS error:
Error: getaddrinfo ENOTFOUND zero-enviro.local
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:71:26)

Still digging around here, but this may be an IPv6 thing. I’ve also had some situations where the homebridge box has showed up with incremental suffixes in Avahi, so I’ll have to see if there’s something going wrong in the network configuration.

Current status is that I’ve disabled ipv6 usage in /etc/avahi/avahi-daemon.conf and also edited /etc/nsswitch.conf to prioritise mdns over dns. This appears to have resolved the issue locally (more likely to be the former edit than the latter, I think). One of these days I need to do a proper network remap at home to sort out all of these lookup and naming oddities…

Thanks for investigating. I have both IPv4 and IPv6 on my network, and haven't experienced these problems with this plug-in. It shouldn't be necessary to disable IPv6. If after you've had a look at your network and you still have problems, let me know.

Thanks for investigating. I have both IPv4 and IPv6 on my network, and haven't experienced these problems with this plug-in. It shouldn't be necessary to disable IPv6. If after you've had a look at your network and you still have problems, let me know.


issue with CJMCU-22 board

Hello Leo
I am trying to use your library with the CJMCI-22 board (GP 22) for a smart flow meter
I receive always this message from TDCtalk :
attached pinChangeISR_debug
/Temp sensor: no addresses.
Starting up
///Test took 312 us
Read/write test failed!
I use a UNO R3

 10 -> SS with a level shift

11 -> MOSI a level shift

12 -> MISO a level shift

13 -> SCK a level shift

2  -> INT a level shift

3.3V -> VCC (NOT 5 VDC)

GND -> GND

2 piezo cells in SP1 / GND and SP2 / GND
I guess I have miss something ?
Could you give me some advices ?
Best regards
Franck

Hi, were you able to solve your problem? were you able to use the CJMCU Gp22?

Hi, were able to fix the issue?are you able to use the CJMCU GP22 board?


register module (fix #52)

Nicer with ES6:
import 'source-map-support/register'

// Instead of:
import sourceMapSupport from 'source-map-support'
sourceMapSupport.install()

Source maps support can be enabled on demand directly from the command line for many CLIs:
> mocha --require source-map-support/register

Any comments @marcominetti @mprobst @joeyespo?

It's a better practice for module-level code (import / require) to not mutate the environment, but I agree it's quite nice for the --require case.
I'd say keep .install() as the main way to install it and mention /register for that nice shorthand.

It's a pretty standard way to do it:

Babel
CoffeeScript

@julien-f Note Babel has a big "Not suitable for libraries" warning message for that option and CoffeeScript only recommends using their register hook in "configuration such as Mocha". They added this out of convenience, not out of being standard.
I do think it'd be nice to have for this use case or for personal preference in a small project, just not as the main suggested way since module-level mutations can be surprising.

Personally I do not install source-map-support in my libraries even though I provide source maps with them. I only enable them in Mocha and in final apps.
Anyways, you suggest I change the README back to require(..).install() and add a section about register?

Gotcha. Yeah, that sounds good.

The PR has been updated.

That looks good. Thanks, @julien-f!


[WIP] Webhooks/REST Hooks support

refs #tbd
Support for http://resthooks.org style webhooks that can be used with Zapier triggers.

add webhooks table to store event names and target urls
add POST and DELETE endpoints for /webhooks/

Note: We should merge and release #9199 before this. #9199 for Tuesday then 👍

Is the plan for these to be used for things other than zapier? ie I can create hooks to a gateway I've written to get events from ghost?
If so, are they going to be signed? It'd be great if they were signed like GitHub ones! https://developer.github.com/webhooks/securing/

@jloh this is for outgoing webhooks, I don't think the GitHub style signed requests make sense here. It's a basic implementation of http://resthooks.org

The receiver (zapier, other service etc) still need a way to verify that the webhook they receive is genuine and not from someone else. The GitHub method of signing hooks is mentioned on their security page http://resthooks.org/docs/security/

Signing may well be added later on, it's not something we're looking at for this early version. Security with Zapier is handled through the unique target_url and UUID of the webhook in Ghost - to exploit the receiver in Zapier someone would have had to access your database or sniff HTTP traffic on the original webhook creation request if you are hosting your blog on HTTP instead of HTTPS.

@ErisDS I've attempted a refactor to make this more Ghost-like in https://github.com/TryGhost/Ghost/pull/9230/commits/1e75a11982a3e151ba152f03500dd10df2dacd21, feel free to shoot that approach down if I've gone the wrong way, I'm certainly not attached to it! 😄

@kirrg001 I've added the composite unique constraint which works but I no longer get a ValidationError back from the API, is there some extra handling needed for that?

@kevinansfield You have to catch the database error.

@kirrg001 looks like we're running into another MySQL limitation here 😞
ER_TOO_LONG_KEY: Specified key was too long; max key length is 767 bytes
I think the max chars we can have is considerably less than that, 191 if we're using utf8mb4 charset which will be way too short for storing the event name + webhook url.
Any bright ideas on how to work around this or should I revert to the manual search & insert I had before? It's possible to increase the max key length with the innodb_large_prefix flag (actually on by default with MySQL 5.7) but I'm guessing we can't dictate that to self-hosters.
I know in Postgres you can create a unique index across hashes of column values to reduce the index size. I had a quick look and it seems something similar is possible in MySQL 5.7 with generated columns, if that's not available we need to use triggers or application code to create the unique hash value for the constraint at which point I'm not sure how much benefit we're getting compared to the manual check we had previously.

191 if we're using utf8mb4 charset which will be too short for storing the event name + webhook url

It may not be too bad actually, I've just checked my test setup, subscriber.deleted + Zapier's hook URL comes to 100 chars. We shouldn't need to deal with crazy long target_url values because hook URLs won't have UTM params or anything like that which typically bulk out URLs.

Yeah each unique key is limited to the same character length, which is 191.

Zapier's hook URL comes to 100 chars

Is that their official limit? The webhooks are a general implementation, i am afraid we will run into problems later as soon as a url needs more space.

Is that their official limit?

No, they don't have any official limits so it's possible they will use a different format in the future. This is an example of one of the resthook URLs they're currently creating:
https://hooks.zapier.com/hooks/standard/2665800/ae8965c1740e4db78571dfb486f7ccd0/
(81 chars)
If we were to limit the composite index to 191 chars it needs to be split between the event name and the URL, so something like 30/161. That's on the assumption we never have our own event names > 30 chars (maybe 35 would be more reasonable?) and resthook URLs of other services don't reach double the length of Zapier's which I think is reasonable but we have no data to back that up.

I've been looking at other webhook URL examples
https://discordapp.com/api/webhooks/380692408364433418/mGLHSRyEoUaTvY91Te16WOT8Obn-BrJoiTNoxeUqhb6klKERb9xaZkUBYC5AfduwYCCy
(123 chars)
https://hooks.slack.com/services/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
(77 chars)
Discord is getting pretty close to the suggested 161 or 156 limit for target_url. For future compatibility I'd probably swing towards dropping the db constraint and reverting to the in-app validation when adding so there's no real chance of running into length limitations.

I've reverted the db-level uniqueness constraint. Running a quick live test then I'll remove the WIP flag.

@kirrg001 comments addressed


fix: The functionality to show relationships between components (Graph view) in the components module is not working.

🐛 The bug
When I try to configure routerRules in the nuxt.config.ts file, it does not show me the references and dependencies.

nuxt.config.ts

export default defineNuxtConfig({
...
  routeRules: {
    '/**': { ssr: false },
  },
...
});

🛠 To reproduce
https://stackblitz.com/edit/github-tk7sxe?file=nuxt.config.ts,components%2FChild%2FAlert%2FAlert.vue,components%2FChild%2FChildButton.vue
🌈 Expected behavior

ℹ Additional context
No response

I have been experiencing the same.


Add istioctl proxy-config all

Fixes https://github.com/istio/istio/issues/28191
Open questions:

Should we support filters? The behavior is a bit awkward
Should we instead have kubectl semantics? ie we can do pc all, pc cluster, or pc cluster,listener,secret. One downside is because these
would not be subcommands we would not have per-command filter flags, so
we have the same awkward flag support as we have here

[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[ ] Does not have any changes that may affect Istio users.

@howardjohn: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
1d64318d06dc2c368b6782f1dd9fe44678600e48
link
/test lint_istio

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


Install failed on MacOS Sierra 10.12.6

The installer fails during the last step with the text "The installation failed."
Strangely the program's icon does appear in the applications folder, however, does not respond when opened.

Thanks for opening this, and sorry the installer didn't work. I'd appreciate it if you could check a few things for me:

Can you share the relevant contents from /var/log/install.log? Maybe the past day's worth of logs if you aren't sure what' relevant. We can email if you aren't comfortable posting logs in a public issue.
Does /Library/Extensions/softu2f.kext exist?
Does ~/Library/LaunchAgents/com.github.SoftU2F.plist exist?
What is the output of ps aux | grep -i softu2f?
What is the output of sudo kextstat -b com.github.SoftU2FDriver?

I'm also seeing this error, and I think it's caused by my UNIX username having a space in it (I know, I know, unfortunately I can't change it).
The installer dies in the ./postinstall script, and should be fixed by changing this line to:  chown "${USER}:staff" $LAUNCH_AGENT_PLIST

Also worth noting that it prompts the user to approve the System Extension by going to System Preferences > Security & Privacy and clicking the "Allow" button at the bottom of the first pane. After doing that, my user stephen (no spaces) worked fine with the Installer.


Quietly collect debug logs.

Don't print any status/info messages to stdout when running the collect-debug-logs script in -q silent mode.
Design Decisions

Added a helper function, print_info, that prints to stdout only when collect-debug-logs is in silent mode.
The helper function wraps printf and not echo in order to have more flexibility when wanting to print special characters (i.e newlines). The caveats include:

You always need to add a newline to the end of each status/info message.
Watchout when printing --, which has a special meaning for printf (i.e ignore everything after --).

Demo video.
Reverts #100 and Fixes #106

LGTM, thanks!


Ordering of installation of vscode:extensions matters and leads to errors on loading

Behaviour:

Upon opening a GitHub code space with the following configuration of extensions, I get an error saying that one of the extensions are not installed (but it should be installed since it is in the list).

VS Code Version: Version: 1.83.1 (Universal) / Commit: f1b07bd25dfad64b0167beb15359ae573aecd2cc

OS Version: macOS 13.6 (22G120)

Steps to Reproduce:

Use GitHub code spaces with the following .devcontainer (see below)
Open the GitHub code space
When loaded you get the error: "Cannot activate the 'autopep8' extension because it depends on the 'Python' extension, which is not loaded. Would you like to reload the window to load the extension?"

Diagnosis:
In speaking with the GitHub code spaces team, I learned that:

"It looks like all of the extensions are being passed into the VS Code server at the same time, so it would require upstream changes in VS Code to handle the installation order in a better way."

and

"My guess is that the extensions are installed in parallel and the python one just takes longer to install/activate and the pep8 one is trying to activate too early before the python finishes installing"

devcontainer.json includes
{
	"name": "Python 3",
	"image": "mcr.microsoft.com/devcontainers/python:0-3.11",
	"features": {
	    "ghcr.io/devcontainers-contrib/features/poetry:2": {},
	    "ghcr.io/devcontainers/features/github-cli:1": {}
	},

	"customizations": {

		"vscode": {
			"extensions": [
				"ms-python.python",
				"ms-toolsai.jupyter",
				"eamodio.gitlens",

				"redhat.vscode-yaml",
				"GitHub.copilot",
				"ms-python.vscode-pylance",
				"ms-python.autopep8"
			],
			"settings": {
			    "python.testing.pytestArgs": [
			        "data"
			    ],
			    "python.testing.unittestEnabled": true,
			    "python.testing.pytestEnabled": true,
			    "[python]": {
			        "editor.defaultFormatter": "ms-python.autopep8",
			        "editor.formatOnSave": true
			    }
			}
		}
	}
}

I've also been seeing such issues for months, particularly for extensions that depend on ms-python.python.
As someone maintaining the development setup environment for a team, it would be really helpful to have any solution that works without a manual reload or special configuration for each user.

We have a similar issue with C#. If you install the C# extension or the C# DevKit extension, it will install quicker than it's dependent ".NET Install Tool" extension.
This race condition leads to a prompt that shows up the majority of the time to reload the editor to install the dependent extension.

I have been running into this same situation, except inside a devcontainer. The Black Formatter extension and the Flake8 extension fail 100% of the time and VSCode suggests reloading. Reloading always works.
Is anyone aware of a workaround in the meantime to enforce an ordering?

I stumbled upon a workaround with a long-running updateContentCommand in .devcontainer.json, so I suspect for anyone having this issue you could potentially do something like:
"updateContentCommand": "sleep 20",

Not pretty, but neither is the "always click the reload button" option.

I'm seeing the same behavior as @mjpizz with a slight clarification:

The Black Formatter extension_, the isort extension, _and the Flake8 extension fail 100% of the time when calling Rebuild and Reopen in Container, and VSCode suggests reloading. Reloading always works. Just doing Reopen in Container also seems to always work.

I have the following in my .devcontainer.json:

			"extensions": [
				"bierner.markdown-mermaid",
				"donjayamanne.githistory",
				"h5web.vscode-h5web",
				"janisdd.vscode-edit-csv",
				"jebbs.plantuml",
				"ms-azuretools.vscode-docker",
				"ms-python.black-formatter",
				"ms-python.flake8",
				"ms-python.isort",
				"ms-python.python",
				"ms-toolsai.jupyter",
				"ryanluker.vscode-coverage-gutters"
			]

Order (moving python above black-formatter, flake8, and isort) doesn't seem to matter.

@craiglpeters

This bug makes it rough to create a "minimal" template for .NET and Python developers with the .NET/Python extensions as it will almost always ask you to reopen the codespace.
Even this configuration will require a "reopen" prompt:
{
  "customizations": {
    "vscode": {
      "extensions": [
        "ms-dotnettools.csdevkit"
      ]
    }
  }
}

Something like an "extension-order" setting, similar to the features, would be amazing in VS Code or development containers.

Or at least loading extensions in the order as given in the extensions list, then users could at least easily hand-sort to avoid these annoying dependency problems until a "real" fix comes along. Presumably/hopefully this could be a quick fix as it's a small change?

@sandy081
Repro steps

I use this button to open the seesharprun/codespace-test repository as a codespace:

Relevant devcontainer configuration:
{
  "customizations": {
    "vscode": {
      "extensions": [
        "ms-dotnettools.csdevkit"
      ]
    }
  }
}

I waited for the C# extensions to install and to observe the "Cannot activate the 'C#' extension because it depends on the '.NET Install Tool' extension, which is not loaded. Would you like to reload the window to load the extension?" popup.

F1 > Open View > Server

Here's the logs:
2023-11-29 15:41:44.047 [trace] Remote configuration data at /home/codespace/.vscode-remote
2023-11-29 15:41:44.047 [trace] process arguments: {"_":[],"host":"<IP_ADDRESS>","port":"0","connection-token-file":"/home/codespace/.vscode-remote/data/Machine/.connection-token-1a5daa3a0231a0fbba4f14db7ec463cf99d7768e","without-connection-token":false,"disable-websocket-compression":false,"print-startup-performance":false,"print-ip-address":false,"accept-server-license-terms":true,"server-data-dir":"/home/codespace/.vscode-remote","enable-smoke-test-driver":false,"disable-telemetry":false,"disable-workspace-trust":false,"log":["trace"],"force-disable-user-env":true,"enable-sync":false,"use-test-resolver":false,"extensions-download-dir":"/home/codespace/.vscode-remote/extensionsCache","install-extension":["ms-dotnettools.csdevkit"],"install-builtin-extension":["GitHub.vscode-pull-request-github","github.github-vscode-theme","github.codespaces"],"list-extensions":false,"show-versions":false,"force":false,"do-not-sync":true,"pre-release":false,"start-server":true,"enable-remote-auto-shutdown":true,"remote-auto-shutdown-without-delay":false,"use-host-proxy":false,"without-browser-env-var":false,"help":false,"version":false,"user-data-dir":"/home/codespace/.vscode-remote/data","builtin-extensions-dir":"/vscode/bin/linux-x64/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/extensions","extensions-dir":"/home/codespace/.vscode-remote/extensions","logsPath":"/home/codespace/.vscode-remote/data/logs/20231129T154143"}
2023-11-29 15:41:44.047 [info]

2023-11-29 15:41:44.047 [trace] [File Watcher (node.js)] Request to start watching: /home/codespace/.vscode-remote/data/Machine (excludes: <none>, includes: <all>, correlationId: <none>),/home/codespace/.vscode-remote/data/Machine/settings.json (excludes: <none>, includes: <all>, correlationId: <none>)
2023-11-29 15:41:44.047 [trace] Installing builtin extensions passed via args...
2023-11-29 15:41:44.047 [trace] Started scanning user extensions {"$mid":1,"external":"file:///home/codespace/.vscode-remote/extensions/extensions.json","path":"/home/codespace/.vscode-remote/extensions/extensions.json","scheme":"file"}
2023-11-29 15:41:44.047 [trace] Installing extensions passed via args...
2023-11-29 15:41:44.047 [info] Extension host agent started.
2023-11-29 15:41:44.052 [trace] [File Watcher (node.js)] Started watching: '/home/codespace/.vscode-remote/data/Machine'
2023-11-29 15:41:44.053 [trace] [File Watcher (node.js)] Request to start watching: /home/codespace/.vscode-remote/extensions (excludes: <none>, includes: <all>, correlationId: <none>)
2023-11-29 15:41:44.059 [trace] [File Watcher (node.js)] Started watching: '/home/codespace/.vscode-remote/data/Machine/settings.json'
2023-11-29 15:41:44.061 [info] Started initializing default profile extensions in extensions installation folder. file:///home/codespace/.vscode-remote/extensions
2023-11-29 15:41:44.061 [trace] Started scanning user extensions {"$mid":1,"fsPath":"/home/codespace/.vscode-remote/extensions","external":"file:///home/codespace/.vscode-remote/extensions","path":"/home/codespace/.vscode-remote/extensions","scheme":"file"}
2023-11-29 15:41:44.076 [trace] Deleting from cache /home/codespace/.vscode-remote/extensionsCache/formulahendry.code-runner-0.12.1
2023-11-29 15:41:44.077 [trace] Deleting from cache /home/codespace/.vscode-remote/extensionsCache/vscjava.vscode-java-debug-0.55.0
2023-11-29 15:41:44.077 [trace] Deleting from cache /home/codespace/.vscode-remote/extensionsCache/ms-toolsai.jupyter-2023.11.1003351000
2023-11-29 15:41:44.078 [trace] Deleting from cache /home/codespace/.vscode-remote/extensionsCache/vscode-icons-team.vscode-icons-12.6.0
2023-11-29 15:41:44.081 [trace] [File Watcher (node.js)] Started watching: '/home/codespace/.vscode-remote/extensions'
2023-11-29 15:41:44.086 [debug] ComputeTargetPlatform: linux-x64
2023-11-29 15:41:44.086 [trace] Scanned user extensions: 0
2023-11-29 15:41:44.088 [trace] [File Watcher (node.js)] [raw] ["rename"] extensions.json
2023-11-29 15:41:44.088 [trace] [File Watcher (node.js)] [raw] ["change"] extensions.json
2023-11-29 15:41:44.089 [trace] [File Watcher (node.js)] [ADDED] /home/codespace/.vscode-remote/extensions/extensions.json
2023-11-29 15:41:44.136 [info] Completed initializing default profile extensions in extensions installation folder. file:///home/codespace/.vscode-remote/extensions
2023-11-29 15:41:44.138 [trace] [File Watcher (node.js)] Request to start watching: /home/codespace/.vscode-remote/extensions/extensions.json (excludes: <none>, includes: <all>, correlationId: <none>)
2023-11-29 15:41:44.142 [trace] Scanned user extensions: 0
2023-11-29 15:41:44.142 [trace] [File Watcher (node.js)] Started watching: '/home/codespace/.vscode-remote/extensions/extensions.json'
2023-11-29 15:41:44.144 [info] [<IP_ADDRESS>][2bf0f2be][ManagementConnection] New connection established.
2023-11-29 15:41:44.145 [trace] Started scanning user extensions {"$mid":1,"fsPath":"/home/codespace/.vscode-remote/extensions","external":"file:///home/codespace/.vscode-remote/extensions","path":"/home/codespace/.vscode-remote/extensions","scheme":"file"}
2023-11-29 15:41:44.153 [debug] ComputeTargetPlatform: linux-x64
2023-11-29 15:41:44.155 [trace] resolveShellEnv(): skipped (--force-disable-user-env)
2023-11-29 15:41:44.222 [trace] [File Watcher (node.js)]  >> normalized [ADDED] /home/codespace/.vscode-remote/extensions/extensions.json
2023-11-29 15:41:44.227 [trace] [File Watcher (node.js)] [CHANGED] /home/codespace/.vscode-remote/extensions/extensions.json
2023-11-29 15:41:44.232 [trace] Scanned user extensions: 0
2023-11-29 15:41:44.281 [trace] Started scanning system extensions
2023-11-29 15:41:44.282 [trace] Started scanning user extensions {"$mid":1,"fsPath":"/home/codespace/.vscode-remote/extensions/extensions.json","external":"file:///home/codespace/.vscode-remote/extensions/extensions.json","path":"/home/codespace/.vscode-remote/extensions/extensions.json","scheme":"file"}
2023-11-29 15:41:44.282 [trace] Started scanning system extensions
2023-11-29 15:41:44.283 [trace] Started scanning user extensions {"$mid":1,"fsPath":"/home/codespace/.vscode-remote/extensions/extensions.json","external":"file:///home/codespace/.vscode-remote/extensions/extensions.json","path":"/home/codespace/.vscode-remote/extensions/extensions.json","scheme":"file"}
2023-11-29 15:41:44.283 [trace] ExtensionManagementService.refreshReportedCache
2023-11-29 15:41:44.284 [trace] resolveShellEnv(): skipped (--force-disable-user-env)
2023-11-29 15:41:44.284 [trace] Started scanning system extensions
2023-11-29 15:41:44.291 [trace] Started scanning user extensions {"$mid":1,"fsPath":"/home/codespace/.vscode-remote/extensions/extensions.json","external":"file:///home/codespace/.vscode-remote/extensions/extensions.json","path":"/home/codespace/.vscode-remote/extensions/extensions.json","scheme":"file"}
2023-11-29 15:41:44.294 [info] Log level changed to info
2023-11-29 15:41:45.641 [info] [<IP_ADDRESS>][db55662e][ExtensionHostConnection] New connection established.
2023-11-29 15:41:45.675 [info] [<IP_ADDRESS>][db55662e][ExtensionHostConnection] <1742> Launched Extension Host Process.
2023-11-29 15:41:46.267 [info] Installing builtin extension 'github.github-vscode-theme'...
2023-11-29 15:41:46.276 [info] Getting Manifest... github.github-vscode-theme
2023-11-29 15:41:46.300 [info] Installing builtin extension 'github.vscode-pull-request-github'...
2023-11-29 15:41:46.321 [info] Getting Manifest... github.vscode-pull-request-github
2023-11-29 15:41:46.335 [info] Installing builtin extension 'github.codespaces'...
2023-11-29 15:41:46.336 [info] Getting Manifest... github.codespaces
2023-11-29 15:41:46.431 [info] Installing extension: github.github-vscode-theme
2023-11-29 15:41:46.435 [info] Installing extension: github.codespaces
2023-11-29 15:41:46.448 [info] Installing extension: github.vscode-pull-request-github
2023-11-29 15:41:47.529 [warning] Extension signature verification failed with error 'ENOENT': github.github-vscode-theme
2023-11-29 15:41:47.547 [warning] Extension signature verification failed with error 'ENOENT': github.codespaces
2023-11-29 15:41:47.677 [info] Extracted extension to file:///home/codespace/.vscode-remote/extensions/github.github-vscode-theme-6.3.4: github.github-vscode-theme
2023-11-29 15:41:47.700 [info] Renamed to /home/codespace/.vscode-remote/extensions/github.github-vscode-theme-6.3.4
2023-11-29 15:41:47.706 [info] Extracting extension completed. github.github-vscode-theme
2023-11-29 15:41:47.726 [warning] Extension signature verification failed with error 'ENOENT': github.vscode-pull-request-github
2023-11-29 15:41:47.734 [info] Extension installed successfully: github.github-vscode-theme
2023-11-29 15:41:47.735 [info] Extension 'github.github-vscode-theme' v6.3.4 was successfully installed.
2023-11-29 15:41:47.956 [info] Extracted extension to file:///home/codespace/.vscode-remote/extensions/github.vscode-pull-request-github-0.76.1: github.vscode-pull-request-github
2023-11-29 15:41:47.982 [info] Renamed to /home/codespace/.vscode-remote/extensions/github.vscode-pull-request-github-0.76.1
2023-11-29 15:41:47.988 [info] Extracting extension completed. github.vscode-pull-request-github
2023-11-29 15:41:48.013 [info] Extension installed successfully: github.vscode-pull-request-github
2023-11-29 15:41:48.016 [info] Extension 'github.vscode-pull-request-github' v0.76.1 was successfully installed.
2023-11-29 15:41:48.172 [info] Extracted extension to file:///home/codespace/.vscode-remote/extensions/github.codespaces-1.16.2: github.codespaces
2023-11-29 15:41:48.192 [info] Renamed to /home/codespace/.vscode-remote/extensions/github.codespaces-1.16.2
2023-11-29 15:41:48.196 [info] Extracting extension completed. github.codespaces
2023-11-29 15:41:48.213 [info] Extension installed successfully: github.codespaces
2023-11-29 15:41:48.215 [info] Extension 'github.codespaces' v1.16.2 was successfully installed.
2023-11-29 15:41:48.216 [info] Installing extensions...
2023-11-29 15:41:48.645 [info] Installing extension 'ms-dotnettools.csdevkit'...
2023-11-29 15:41:48.646 [info] Getting Manifest... ms-dotnettools.csdevkit
2023-11-29 15:41:48.665 [info] Installing extension: ms-dotnettools.csdevkit
2023-11-29 15:41:49.241 [info] Getting Manifest... ms-dotnettools.csharp
2023-11-29 15:41:49.360 [info] Getting Manifest... ms-dotnettools.vscode-dotnet-runtime
2023-11-29 15:41:49.472 [info] Getting Manifest... ms-dotnettools.vscodeintellicode-csharp
2023-11-29 15:41:49.566 [info] Getting Manifest... ms-dotnettools.csharp
2023-11-29 15:41:49.706 [info] Installing extension: ms-dotnettools.csharp
2023-11-29 15:41:49.706 [info] Installing the extension without checking dependencies and pack ms-dotnettools.csharp
2023-11-29 15:41:49.752 [info] Installing extension: ms-dotnettools.csharp ms-dotnettools.csdevkit
2023-11-29 15:41:49.754 [info] Installing extension: ms-dotnettools.vscode-dotnet-runtime ms-dotnettools.csdevkit
2023-11-29 15:41:49.754 [info] Installing extension: ms-dotnettools.vscodeintellicode-csharp ms-dotnettools.csdevkit
2023-11-29 15:41:50.556 [warning] Extension signature verification failed with error 'ENOENT': ms-dotnettools.vscode-dotnet-runtime
2023-11-29 15:41:50.712 [warning] Extension signature verification failed with error 'ENOENT': ms-dotnettools.csharp
2023-11-29 15:41:50.973 [info] Extracted extension to file:///home/codespace/.vscode-remote/extensions/ms-dotnettools.vscode-dotnet-runtime-2.0.0: ms-dotnettools.vscode-dotnet-runtime
2023-11-29 15:41:51.002 [info] Renamed to /home/codespace/.vscode-remote/extensions/ms-dotnettools.vscode-dotnet-runtime-2.0.0
2023-11-29 15:41:51.010 [info] Extracting extension completed. ms-dotnettools.vscode-dotnet-runtime
2023-11-29 15:41:53.781 [info] Extracted extension to file:///home/codespace/.vscode-remote/extensions/ms-dotnettools.csharp-2.0.251: ms-dotnettools.csharp
2023-11-29 15:41:53.820 [info] Renamed to /home/codespace/.vscode-remote/extensions/ms-dotnettools.csharp-2.0.251
2023-11-29 15:41:53.830 [info] Extracting extension completed. ms-dotnettools.csharp
2023-11-29 15:41:53.848 [info] Extension installed successfully: ms-dotnettools.csharp
2023-11-29 15:41:54.874 [info] Getting Manifest... github.vscode-pull-request-github
2023-11-29 15:41:55.008 [info] Installing extension: github.vscode-pull-request-github
2023-11-29 15:41:55.008 [info] Installing the extension without checking dependencies and pack github.vscode-pull-request-github
2023-11-29 15:41:55.247 [warning] Extension signature verification failed with error 'ENOENT': ms-dotnettools.csharp
2023-11-29 15:41:55.313 [info] Extension installed successfully: github.vscode-pull-request-github
2023-11-29 15:41:56.006 [info] Getting Manifest... ms-dotnettools.vscode-dotnet-runtime
2023-11-29 15:41:56.028 [info] Extensions is already requested to install ms-dotnettools.vscode-dotnet-runtime
2023-11-29 15:41:56.739 [info] Getting Manifest... github.codespaces
2023-11-29 15:41:56.762 [info] Installing extension: github.codespaces
2023-11-29 15:41:56.762 [info] Installing the extension without checking dependencies and pack github.codespaces
2023-11-29 15:41:57.272 [info] Extension installed successfully: github.codespaces
2023-11-29 15:41:58.010 [info] Getting Manifest... github.vscode-github-actions
2023-11-29 15:41:58.038 [info] Installing extension: github.vscode-github-actions
2023-11-29 15:41:58.040 [info] Installing the extension without checking dependencies and pack github.vscode-github-actions
2023-11-29 15:41:58.973 [warning] Extension signature verification failed with error 'ENOENT': github.vscode-github-actions
2023-11-29 15:42:00.258 [info] Extracted extension to file:///home/codespace/.vscode-remote/extensions/github.vscode-github-actions-0.26.2: github.vscode-github-actions
2023-11-29 15:42:00.472 [info] Renamed to /home/codespace/.vscode-remote/extensions/github.vscode-github-actions-0.26.2
2023-11-29 15:42:00.554 [info] Extracting extension completed. github.vscode-github-actions
2023-11-29 15:42:00.729 [info] Extension installed successfully: github.vscode-github-actions
2023-11-29 15:42:04.255 [info] Getting Manifest... github.vscode-github-actions
2023-11-29 15:42:04.460 [info] Getting Manifest... ms-dotnettools.vscodeintellicode-csharp
2023-11-29 15:42:04.545 [info] Getting Manifest... ms-dotnettools.csdevkit
2023-11-29 15:42:04.608 [info] Getting Manifest... ms-dotnettools.csharp
2023-11-29 15:42:04.643 [info] Installing extension: github.vscode-github-actions
2023-11-29 15:42:04.643 [info] Installing the extension without checking dependencies and pack github.vscode-github-actions
2023-11-29 15:42:04.645 [info] Extensions is already requested to install ms-dotnettools.vscodeintellicode-csharp
2023-11-29 15:42:04.645 [info] Extensions is already requested to install ms-dotnettools.csdevkit
2023-11-29 15:42:04.646 [info] Installing extension: ms-dotnettools.csharp
2023-11-29 15:42:04.646 [info] Installing the extension without checking dependencies and pack ms-dotnettools.csharp
2023-11-29 15:42:05.508 [info] Extension installed successfully: github.vscode-github-actions
2023-11-29 15:42:08.049 [warning] Extension signature verification failed with error 'ENOENT': ms-dotnettools.csharp
2023-11-29 15:42:22.900 [info] Extracted extension to file:///home/codespace/.vscode-remote/extensions/ms-dotnettools.csharp-2.10.28-linux-x64: ms-dotnettools.csharp
2023-11-29 15:42:22.941 [info] Renamed to /home/codespace/.vscode-remote/extensions/ms-dotnettools.csharp-2.10.28-linux-x64
2023-11-29 15:42:22.953 [info] Extracting extension completed. ms-dotnettools.csharp
2023-11-29 15:42:23.454 [info] Marked extension as uninstalled ms-dotnettools.csharp-2.0.251
2023-11-29 15:42:24.391 [warning] Extension signature verification failed with error 'ENOENT': ms-dotnettools.csdevkit
2023-11-29 15:42:28.945 [info] Extracted extension to file:///home/codespace/.vscode-remote/extensions/ms-dotnettools.csharp-2.12.4-linux-x64: ms-dotnettools.csharp
2023-11-29 15:42:29.172 [info] Extracted extension to file:///home/codespace/.vscode-remote/extensions/ms-dotnettools.csdevkit-1.0.14-linux-x64: ms-dotnettools.csdevkit
2023-11-29 15:42:29.254 [info] Renamed to /home/codespace/.vscode-remote/extensions/ms-dotnettools.csharp-2.12.4-linux-x64
2023-11-29 15:42:29.266 [info] Extracting extension completed. ms-dotnettools.csharp
2023-11-29 15:42:29.278 [info] Renamed to /home/codespace/.vscode-remote/extensions/ms-dotnettools.csdevkit-1.0.14-linux-x64
2023-11-29 15:42:29.282 [info] Extracting extension completed. ms-dotnettools.csdevkit
2023-11-29 15:42:29.296 [info] Extension installed successfully: ms-dotnettools.csharp
2023-11-29 15:42:29.306 [info] Marked extension as uninstalled ms-dotnettools.csharp-2.10.28-linux-x64
2023-11-29 15:42:30.856 [warning] Extension signature verification failed with error 'ENOENT': ms-dotnettools.vscodeintellicode-csharp
2023-11-29 15:42:36.079 [info] Extracted extension to file:///home/codespace/.vscode-remote/extensions/ms-dotnettools.vscodeintellicode-csharp-0.1.26-linux-x64: ms-dotnettools.vscodeintellicode-csharp
2023-11-29 15:42:36.102 [info] Renamed to /home/codespace/.vscode-remote/extensions/ms-dotnettools.vscodeintellicode-csharp-0.1.26-linux-x64
2023-11-29 15:42:36.103 [info] Extracting extension completed. ms-dotnettools.vscodeintellicode-csharp
2023-11-29 15:42:36.132 [info] Extension installed successfully: ms-dotnettools.vscode-dotnet-runtime
2023-11-29 15:42:36.132 [info] Extension installed successfully: ms-dotnettools.csharp
2023-11-29 15:42:36.132 [info] Extension installed successfully: ms-dotnettools.csdevkit
2023-11-29 15:42:36.132 [info] Extension installed successfully: ms-dotnettools.vscodeintellicode-csharp
2023-11-29 15:42:36.136 [info] Extension 'ms-dotnettools.csdevkit' v1.0.14 was successfully installed.
2023-11-29 15:42:36.393 [info] Deleted uninstalled extension from disk ms-dotnettools.csharp /home/codespace/.vscode-remote/extensions/ms-dotnettools.csharp-2.10.28-linux-x64
2023-11-29 15:42:36.440 [info] Deleted uninstalled extension from disk ms-dotnettools.csharp /home/codespace/.vscode-remote/extensions/ms-dotnettools.csharp-2.0.251

I repeated this experiment using a Codespace on a different repository and configuration file.

Repository: seesharprun/codespace-test-python

Codespaces link: https://codespaces.new/seesharprun/codespace-test-python?quickstart=1&devcontainer_path=.devcontainer%2Fdevcontainer.json

Devcontainer configuration:
{
  "customizations": {
    "vscode": {
      "extensions": [
    	  "bierner.markdown-mermaid",
    	  "donjayamanne.githistory",
    	  "h5web.vscode-h5web",
    	  "janisdd.vscode-edit-csv",
    	  "jebbs.plantuml",
    	  "ms-azuretools.vscode-docker",
    	  "ms-python.black-formatter",
    	  "ms-python.flake8",
    	  "ms-python.isort",
    	  "ms-python.python",
    	  "ms-toolsai.jupyter",
    	  "ryanluker.vscode-coverage-gutters"
      ]
    }
  }
}

I could not repro the same issue that @Codym48 observed. I may be missing an important step to repro.

@seesharprun Thanks for the log. From the log it seems following extensions are requested to be installed

github.codespaces
github.vscode-github-actions
github.vscode-pull-request-github

and following extensions are requested to be installed again

ms-dotnettools.vscodeintellicode-csharp
ms-dotnettools.csdevkit
ms-dotnettools.csharp
ms-dotnettools.vscode-dotnet-runtime

By any chance, you have settings sync enabled and you have above extensions synced?

I do have settings sync enabled with the C# and C# DevKit extensions.

Thank you for trying @seesharprun! I tried your seesharprun/codespace-test-python and also didn't see the issue. Given @mjpizz's workaround, maybe the codespace takes just long enough to load things before opening the window to avoid the Reload prompt?
I reproduced the issue in a smaller repository via the Dev Containers and WSL extensions and the following container spec
{
    "name": "Python 3",
    "image": "mcr.microsoft.com/devcontainers/python:0-3.11",
    "customizations": {
        "vscode": {
            "extensions": [
                "ms-python.python",
                "ms-python.black-formatter",
                "ms-python.isort",
                "ms-python.flake8"
            ]
        }
    },
    "postCreateCommand": "pip3 install black isort flake8"
}

Help > About:
Version: 1.68.1 (user setup)
Commit: 30d9c6cd9483b2cc586687151bcbcd635f373630
Date: 2022-06-14T12:48:58.283Z
Electron: 17.4.7
Chromium: 98.0.4758.141
Node.js: 16.13.0
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19045
Note this is an older version of VS Code than I used above (https://github.com/microsoft/vscode/issues/196794#issuecomment-1830356267).
F1 > Open View > Log (Remote Server)
[2023-12-01 04:53:14.820] [remoteagent] [info] Extension host agent started.
[2023-12-01 04:53:14.911] [remoteagent] [info] [<IP_ADDRESS>][609518d8][ManagementConnection] New connection established.
[2023-12-01 04:53:15.835] [remoteagent] [info] [<IP_ADDRESS>][ce546b6e][ExtensionHostConnection] New connection established.
[2023-12-01 04:53:15.873] [remoteagent] [info] [<IP_ADDRESS>][ce546b6e][ExtensionHostConnection] <270> Launched Extension Host Process.
[2023-12-01 04:53:17.035] [remoteagent] [info] Getting Manifest... ms-python.black-formatter
[2023-12-01 04:53:17.114] [remoteagent] [info] Getting Manifest... ms-python.isort
[2023-12-01 04:53:17.121] [remoteagent] [info] Installing extension: ms-python.black-formatter
[2023-12-01 04:53:17.295] [remoteagent] [info] Installing extension: ms-python.isort
[2023-12-01 04:53:17.408] [remoteagent] [error] Failed to install extension. ms-python.flake8
[2023-12-01 04:53:17.422] [remoteagent] [error] Incompatible: Can't install 'ms-python.flake8' extension because it is not compatible with the current version of Visual Studio Code (version 1.68.1).
    at _.checkAndGetCompatibleVersion (/vscode/vscode-server/bin/linux-x64/30d9c6cd9483b2cc586687151bcbcd635f373630/out/vs/server/node/server.main.js:102:11814)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async _.installFromGallery (/vscode/vscode-server/bin/linux-x64/30d9c6cd9483b2cc586687151bcbcd635f373630/out/vs/server/node/server.main.js:102:3200)
    at async S.installFromGallery (/vscode/vscode-server/bin/linux-x64/30d9c6cd9483b2cc586687151bcbcd635f373630/out/vs/server/node/server.main.js:81:1328)
    at async /vscode/vscode-server/bin/linux-x64/30d9c6cd9483b2cc586687151bcbcd635f373630/out/vs/server/node/server.main.js:80:141569
    at async Promise.all (index 3)
    at async S.installExtensions (/vscode/vscode-server/bin/linux-x64/30d9c6cd9483b2cc586687151bcbcd635f373630/out/vs/server/node/server.main.js:80:141484)
[2023-12-01 04:53:17.661] [remoteagent] [info] Getting Manifest... ms-python.python
[2023-12-01 04:53:17.797] [remoteagent] [info] Installing extension: ms-python.python
[2023-12-01 04:53:18.480] [remoteagent] [info] Getting Manifest... ms-python.python
[2023-12-01 04:53:19.026] [remoteagent] [info] Getting Manifest... ms-python.python
[2023-12-01 04:53:20.296] [remoteagent] [info] Getting Manifest... ms-python.vscode-pylance
[2023-12-01 04:53:21.348] [remoteagent] [info] Getting Manifest... ms-python.vscode-pylance
[2023-12-01 04:53:21.671] [remoteagent] [info] Getting Manifest... ms-toolsai.jupyter
[2023-12-01 04:53:22.165] [remoteagent] [info] Getting Manifest... ms-toolsai.jupyter-keymap
[2023-12-01 04:53:22.253] [remoteagent] [info] Getting Manifest... ms-python.vscode-pylance
[2023-12-01 04:53:22.406] [remoteagent] [info] Getting Manifest... ms-toolsai.jupyter
[2023-12-01 04:53:22.600] [remoteagent] [info] Getting Manifest... ms-toolsai.jupyter-renderers
[2023-12-01 04:53:22.984] [remoteagent] [info] Installing extension: ms-python.vscode-pylance
[2023-12-01 04:53:22.985] [remoteagent] [info] Installing extension: ms-toolsai.jupyter
[2023-12-01 04:53:22.986] [remoteagent] [info] Installing extension: ms-toolsai.jupyter-keymap
[2023-12-01 04:53:22.987] [remoteagent] [info] Installing extension: ms-toolsai.jupyter-renderers
[2023-12-01 04:53:23.349] [remoteagent] [info] Getting Manifest... ms-toolsai.jupyter-keymap
[2023-12-01 04:53:23.506] [remoteagent] [info] Downloaded extension: ms-toolsai.jupyter /root/.vscode-server/extensionsCache/ms-toolsai.jupyter-2022.5.1001601848
[2023-12-01 04:53:23.510] [remoteagent] [info] Downloaded extension: ms-toolsai.jupyter-keymap /root/.vscode-server/extensionsCache/ms-toolsai.jupyter-keymap-1.1.0
[2023-12-01 04:53:23.511] [remoteagent] [info] Downloaded extension: ms-python.python /root/.vscode-server/extensionsCache/ms-python.python-2022.16.1
[2023-12-01 04:53:23.513] [remoteagent] [info] Downloaded extension: ms-toolsai.jupyter-renderers /root/.vscode-server/extensionsCache/ms-toolsai.jupyter-renderers-1.0.9
[2023-12-01 04:53:23.626] [remoteagent] [info] Extracted extension to /root/.vscode-server/extensions/.389438c2-7eff-49b0-8a6d-de8ee8cdc05d: ms-toolsai.jupyter-keymap
[2023-12-01 04:53:23.647] [remoteagent] [info] Renamed to /root/.vscode-server/extensions/ms-toolsai.jupyter-keymap-1.1.0
[2023-12-01 04:53:23.659] [remoteagent] [info] Extracting completed. ms-toolsai.jupyter-keymap
[2023-12-01 04:53:23.729] [remoteagent] [info] Getting Manifest... ms-toolsai.jupyter-renderers
[2023-12-01 04:53:24.028] [remoteagent] [info] Extension is already requested to install ms-python.python
[2023-12-01 04:53:24.028] [remoteagent] [info] Extension is already requested to install ms-python.vscode-pylance
[2023-12-01 04:53:24.028] [remoteagent] [info] Extension is already requested to install ms-toolsai.jupyter
[2023-12-01 04:53:24.028] [remoteagent] [info] Extension is already requested to install ms-toolsai.jupyter-renderers
[2023-12-01 04:53:24.134] [remoteagent] [info] Downloaded extension: ms-python.black-formatter /root/.vscode-server/extensionsCache/ms-python.black-formatter-2022.4.0
[2023-12-01 04:53:24.396] [remoteagent] [info] Getting Manifest... ms-toolsai.jupyter
[2023-12-01 04:53:24.795] [remoteagent] [info] Getting Manifest... ms-toolsai.jupyter-keymap
[2023-12-01 04:53:25.007] [remoteagent] [info] Getting Manifest... ms-toolsai.jupyter-renderers
[2023-12-01 04:53:25.196] [remoteagent] [info] Extension is already requested to install ms-python.python
[2023-12-01 04:53:25.197] [remoteagent] [info] Extension is already requested to install ms-python.vscode-pylance
[2023-12-01 04:53:25.197] [remoteagent] [info] Extension is already requested to install ms-toolsai.jupyter
[2023-12-01 04:53:25.197] [remoteagent] [info] Extension is already requested to install ms-toolsai.jupyter-renderers
[2023-12-01 04:53:25.367] [remoteagent] [info] Downloaded extension: ms-python.isort /root/.vscode-server/extensionsCache/ms-python.isort-2022.2.0
[2023-12-01 04:53:25.933] [remoteagent] [info] Extracted extension to /root/.vscode-server/extensions/.65621849-e307-4794-99cd-de016b5bfd01: ms-toolsai.jupyter-renderers
[2023-12-01 04:53:25.954] [remoteagent] [info] Renamed to /root/.vscode-server/extensions/ms-toolsai.jupyter-renderers-1.0.9
[2023-12-01 04:53:25.967] [remoteagent] [info] Extracting completed. ms-toolsai.jupyter-renderers
[2023-12-01 04:53:27.175] [remoteagent] [info] Extracted extension to /root/.vscode-server/extensions/.09dcb16d-b955-49b2-b4db-4cd35da5f4e4: ms-python.isort
[2023-12-01 04:53:27.196] [remoteagent] [info] Renamed to /root/.vscode-server/extensions/ms-python.isort-2022.2.0
[2023-12-01 04:53:27.205] [remoteagent] [info] Extracting completed. ms-python.isort
[2023-12-01 04:53:27.206] [remoteagent] [info] Extension installed successfully: ms-python.isort
[2023-12-01 04:53:28.082] [remoteagent] [info] Extracted extension to /root/.vscode-server/extensions/.d8569ab8-99d8-4cba-aa0a-30308e1850fc: ms-python.black-formatter
[2023-12-01 04:53:28.335] [remoteagent] [info] Renamed to /root/.vscode-server/extensions/ms-python.black-formatter-2022.4.0
[2023-12-01 04:53:28.344] [remoteagent] [info] Extracting completed. ms-python.black-formatter
[2023-12-01 04:53:28.347] [remoteagent] [info] Extension installed successfully: ms-python.black-formatter
[2023-12-01 04:53:28.713] [remoteagent] [info] Extracted extension to /root/.vscode-server/extensions/.dcbee190-bcbf-4c0e-9e1b-d9db930aeba9: ms-toolsai.jupyter
[2023-12-01 04:53:28.790] [remoteagent] [info] Renamed to /root/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848
[2023-12-01 04:53:28.948] [remoteagent] [info] Extracting completed. ms-toolsai.jupyter
[2023-12-01 04:53:32.370] [remoteagent] [info] Extracted extension to /root/.vscode-server/extensions/.ea3ded73-2958-4593-aedd-38be47ed159a: ms-python.python
[2023-12-01 04:53:32.416] [remoteagent] [info] Renamed to /root/.vscode-server/extensions/ms-python.python-2022.16.1
[2023-12-01 04:53:32.429] [remoteagent] [info] Extracting completed. ms-python.python
[2023-12-01 04:53:32.500] [remoteagent] [info] Downloaded extension: ms-python.vscode-pylance /root/.vscode-server/extensionsCache/ms-python.vscode-pylance-2023.1.10
[2023-12-01 04:53:39.782] [remoteagent] [info] Extracted extension to /root/.vscode-server/extensions/.01d6f240-55a4-4cd3-8dab-fb4aa3e404fc: ms-python.vscode-pylance
[2023-12-01 04:53:39.809] [remoteagent] [info] Renamed to /root/.vscode-server/extensions/ms-python.vscode-pylance-2023.1.10
[2023-12-01 04:53:39.814] [remoteagent] [info] Extracting completed. ms-python.vscode-pylance
[2023-12-01 04:53:39.816] [remoteagent] [info] Extension installed successfully: ms-toolsai.jupyter-keymap
[2023-12-01 04:53:39.817] [remoteagent] [info] Extension installed successfully: ms-toolsai.jupyter-renderers
[2023-12-01 04:53:39.817] [remoteagent] [info] Extension installed successfully: ms-toolsai.jupyter
[2023-12-01 04:53:39.817] [remoteagent] [info] Extension installed successfully: ms-python.python
[2023-12-01 04:53:39.817] [remoteagent] [info] Extension installed successfully: ms-python.vscode-pylance
[2023-12-01 04:53:39.829] [remoteagent] [error] Error: Failed Installing Extensions: ms-python.flake8
    at S.installExtensions (/vscode/vscode-server/bin/linux-x64/30d9c6cd9483b2cc586687151bcbcd635f373630/out/vs/server/node/server.main.js:81:42)

This is without Settings Sync enabled

We closed this issue because we don't plan to address it in the foreseeable future. If you disagree and feel that this issue is crucial: we are happy to listen and to reconsider.
If you wonder what we are up to, please see our roadmap and issue reporting guidelines.
Thanks for your understanding, and happy coding!

We closed this issue because we don't plan to address it in the foreseeable future.

I have to admit that I'm confused.
The linked page talks about closing out-of-scope feature requests. I don't see how this can be relevant here, as this report is of extension loading being broken/erroring. In fact, I'm confused why the bug label was removed by @sandy081.
Furthermore, users have supplied logs as requested, and even repos for reproduction, yet the info-needed label was not removed, and now failing extension loading is closed as out-of-scope?
@isidorn I'd be curious about the decision process here, to be honest. 😞 ☮

Yeah - I also disagree with closing as not planned here. I'm continuing to see wierd bugs with extensions here - these are effective usability problems that cause friction and requires workarounds.
Example with latest version of VSCode:
Version: 1.85.1 (Universal)
Commit: 0ee08df0cf4527e40edc9aa28f4b5bd38bbff2b2
Date: 2023-12-13T09:48:06.308Z
Electron: 25.9.7
ElectronBuildId: 25551756
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: <IP_ADDRESS>-electron.0
OS: Darwin arm64 22.6.0

Behaviour

Upon opening a GitHub code space with the following configuration of extensions, I get an error saying that one of the extensions are not installed (but it should be installed since it is in the list).

Steps to Reproduce:

Use GitHub code spaces with the following .devcontainer (see below)
Open the GitHub code space
When loaded you get the error: "Cannot activate the 'autopep8' extension because it depends on the 'Python' extension, which is not loaded. Would you like to reload the window to load the extension?"

// For format details, see https://aka.ms/devcontainer.json. For config options, see the
// README at: https://github.com/devcontainers/templates/tree/main/src/python
{
	"name": "Python 3",
	// Or use a Dockerfile or Docker Compose file. More info: https://containers.dev/guide/dockerfile
	"image": "mcr.microsoft.com/devcontainers/base:ubuntu",
	// Features to add to the dev container. More info: https://containers.dev/features.
	"features": {
		"ghcr.io/devcontainers/features/python:1": {
			"version": "3.12",
			"installTools": true,
			"installJupyterlab": true,
			"configureJupyterlabAllowOrigin": "*"
		},
		"ghcr.io/devcontainers-contrib/features/poetry:2": {},
		"ghcr.io/devcontainers/features/github-cli:1": {}
	},
	// Configure tool-specific properties.
	"customizations": {
		// Configure properties specific to VS Code.
		"vscode": {
			"extensions": [
				"ms-toolsai.jupyter",
				"GitHub.copilot",
				"ms-python.python",
				"ms-python.vscode-pylance",
				"ms-python.black-formatter"
			],
			"settings": {
				"[python]": {
					"editor.defaultFormatter": "ms-python.black-formatter"
				},
				"python.formatting.provider": "none"
			}
		},
		"codespaces": {
			"repositories": {
				"github/thehub": {
					"permissions": {
						"contents": "read"
					  }
				}
			}
		}
	},

	// Use 'forwardPorts' to make a list of ports inside the container available locally.
	// "forwardPorts": [9000],
	"forwardPorts": [
		8888,
		8889
	],

	// Use 'portsAttributes' to set default properties for specific forwarded ports.
	// More info: https://containers.dev/implementors/json_reference/#port-attributes
	// "portsAttributes": {
	// 	"9000": {
	// 		"label": "Hello Remote World",
	// 		"onAutoForward": "notify"
	// 	}
	// },

	// Use 'postCreateCommand' to run commands after the container is created.
	// using "features" above instead
	"postCreateCommand": "git config --global --add safe.directory /workspaces/cliff && git pull --update && poetry install --no-root",
	"postStartCommand": "bash .devcontainer/postStartCommand.sh"
	// Uncomment to connect as root instead. More info: https://aka.ms/dev-containers-non-root.
	// "remoteUser": "root"
}

Despite clearly declaring Python extension, I get this error in the log:
Visual Studio Code (1.85.1, codespaces, desktop)
Jupyter Extension Version: 2023.11.1003402403.
Python Extension not installed.
Pylance Extension not installed.

Now if I close and reopen the codespace, I get thing working:
Visual Studio Code (1.85.1, codespaces, desktop)
Jupyter Extension Version: 2023.11.1003402403.
Python Extension Version: 2023.22.1.
Pylance Extension Version: 2023.12.1.
Platform: linux (x64).
Workspace folder /workspaces/cliff, Home = /home/vscode
14:05:35.243 [info] Start refreshing Kernel Picker<PHONE_NUMBER>242)
14:05:35.262 [info] Using Pylance
14:05:36.466 [warn] Failed to get activated env vars for /usr/local/python/current/bin/python in 1040ms
14:05:36.786 [info] Process Execution: /usr/local/python/current/bin/python -c "import site;print("USER_BASE_VALUE");print(site.USER_BASE);print("USER_BASE_VALUE");"
14:05:36.838 [error] Unable to determine site packages path for python /usr/local/python/current/bin/python (Unknown)
14:05:36.873 [info] Process Execution: /usr/local/python/current/bin/python -m pip list
14:05:37.928 [info] End refreshing Kernel Picker<PHONE_NUMBER>242)
14:05:38.417 [info] Start refreshing Kernel Picker<PHONE_NUMBER>417)
14:05:39.557 [info] End refreshing Kernel Picker<PHONE_NUMBER>417)

and my poetry managed environment is available to Jupyter.
It's really hard for my users to understand why they have to restart VSCode and reopen the codespace before the extension works.

I work at GitHub and I would be happy to jump on a call and walk you through how to reproduce this if you can't reproduce.

Thanks for feedback. I closed this because I do not see us investing resources in fixing issues like this in the next 6 months. Not saying it is invalid. We might still reopen it after I discuss with @sandy081
As for GitHub - I suggest to reach out to the Codespaces team and if they have capacity they can invest in making a PR.

any updates @isidorn or @sandy081 ?
I have another instance of this again: with "ms-python.python", clearly in the devcontainer

with a .devcontainer.json of:
"customizations": {
		// Configure properties specific to VS Code.
		"vscode": {
			"extensions": [
				"ms-toolsai.jupyter",
				"GitHub.copilot",
				"ms-python.python",
				"ms-python.vscode-pylance",
				"ms-python.black-formatter"
			],

any updates @isidorn or @sandy081 ?

Will investigate and see if I can repro

@sandy081 for my example, please see server log here: https://gist.github.com/krukow/9b0b4b8f6aeca97cce7fe1e48c73112e
With devcontainer.json and latest version
// For format details, see https://aka.ms/devcontainer.json. For config options, see the
// README at: https://github.com/devcontainers/templates/tree/main/src/python
{
	"name": "Python 3",
	// Or use a Dockerfile or Docker Compose file. More info: https://containers.dev/guide/dockerfile
	"image": "mcr.microsoft.com/devcontainers/base:ubuntu",
	// Features to add to the dev container. More info: https://containers.dev/features.
	"features": {
		"ghcr.io/devcontainers/features/python:1": {
			"version": "3.12",
			"installTools": true,
			"installJupyterlab": true,
			"configureJupyterlabAllowOrigin": "*"
		},
		"ghcr.io/devcontainers-contrib/features/poetry:2": {},
		"ghcr.io/devcontainers/features/github-cli:1": {}
	},
	// Configure tool-specific properties.
	"customizations": {
		// Configure properties specific to VS Code.
		"vscode": {
			"extensions": [
				"ms-toolsai.jupyter",
				"GitHub.copilot",
				"ms-python.python",
				"ms-python.vscode-pylance",
				"ms-python.black-formatter"
			],
			"settings": {
				"[python]": {
					"editor.defaultFormatter": "ms-python.black-formatter"
				},
				"python.formatting.provider": "none"
			}
		},
		"codespaces": {
			"repositories": {
				"github/thehub": {
					"permissions": {
						"contents": "read"
					  }
				}
			}
		}
	},

	// Use 'forwardPorts' to make a list of ports inside the container available locally.
	// "forwardPorts": [9000],
	"forwardPorts": [
		8888,
		8889
	]
}

System info
Version: 1.85.1 (Universal)
Commit: 0ee08df0cf4527e40edc9aa28f4b5bd38bbff2b2
Date: 2023-12-13T09:48:06.308Z
Electron: 25.9.7
ElectronBuildId: 25551756
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: <IP_ADDRESS>-electron.0
OS: Darwin arm64 23.2.0

this issue shows another simple repro example, they even provided a repo that reproduces this issue every time and it only has two extensions listed in devcontainer.json: https://github.com/PelicanQ/devcontainer-issue.git

As a follow-up to luabuds post above, this is the logs from F1 > Open View > Server.
21:46:47.776 [info] Installing extensions...
21:46:47.776 [info] Extension host agent started.
21:46:47.793 [info] Started initializing default profile extensions in extensions installation folder. file:///root/.vscode-server/extensions
21:46:47.801 [debug] ComputeTargetPlatform: linux-x64
21:46:47.809 [info] Completed initializing default profile extensions in extensions installation folder. file:///root/.vscode-server/extensions
21:46:47.815 [debug] ComputeTargetPlatform: linux-x64
21:46:47.921 [info] [<IP_ADDRESS>][f0ad4f32][ManagementConnection] New connection established.
21:46:47.940 [info] Log level changed to info
21:46:48.495 [info] [<IP_ADDRESS>][fc4073b9][ExtensionHostConnection] New connection established.
21:46:48.598 [info] [<IP_ADDRESS>][fc4073b9][ExtensionHostConnection] <275> Launched Extension Host Process.
21:46:49.404 [info] Installing extension 'ms-python.black-formatter'...
21:46:49.406 [info] Getting Manifest... ms-python.black-formatter
21:46:49.415 [info] Installing extension 'ms-python.python'...
21:46:49.415 [info] Getting Manifest... ms-python.python
21:46:49.538 [info] Installing extension: ms-python.black-formatter
21:46:49.586 [info] Installing extension: ms-python.python
21:46:50.185 [info] Getting Manifest... ms-python.python
21:46:50.346 [info] Getting Manifest... ms-python.vscode-pylance
21:46:50.562 [info] Installing extension: ms-python.vscode-pylance ms-python.python
21:46:50.788 [warning] Extension signature verification failed with error 'ENOENT': ms-python.python
21:46:50.982 [info] Getting Manifest... ms-python.vscode-pylance
21:46:51.150 [info] Waiting for already requested installing extension ms-python.python ms-python.black-formatter
21:46:51.151 [info] Waiting for already requested installing extension ms-python.vscode-pylance ms-python.black-formatter
21:46:51.309 [warning] Extension signature verification failed with error 'ENOENT': ms-python.black-formatter
21:46:52.187 [info] Extracted extension to file:///root/.vscode-server/extensions/ms-python.black-formatter-2023.6.0: ms-python.black-formatter
21:46:52.200 [info] Renamed to /root/.vscode-server/extensions/ms-python.black-formatter-2023.6.0
21:46:52.205 [info] Extracting extension completed. ms-python.black-formatter
21:46:55.111 [info] Extracted extension to file:///root/.vscode-server/extensions/ms-python.python-2023.22.1: ms-python.python
21:46:55.124 [info] Renamed to /root/.vscode-server/extensions/ms-python.python-2023.22.1
21:46:55.129 [info] Extracting extension completed. ms-python.python
21:46:55.309 [warning] Extension signature verification failed with error 'ENOENT': ms-python.vscode-pylance
21:47:03.113 [info] Extracted extension to file:///root/.vscode-server/extensions/ms-python.vscode-pylance-2023.12.1: ms-python.vscode-pylance
21:47:03.129 [info] Renamed to /root/.vscode-server/extensions/ms-python.vscode-pylance-2023.12.1
21:47:03.134 [info] Extracting extension completed. ms-python.vscode-pylance
21:47:03.143 [info] Extension installed successfully: ms-python.python
21:47:03.144 [info] Extension installed successfully: ms-python.vscode-pylance
21:47:03.148 [info] Finished waiting for already requested installing extension ms-python.python ms-python.black-formatter
21:47:03.148 [info] Finished waiting for already requested installing extension ms-python.vscode-pylance ms-python.black-formatter
21:47:03.149 [info] Extension 'ms-python.python' v2023.22.1 was successfully installed.
21:47:03.149 [info] Extension installed successfully: ms-python.black-formatter
21:47:03.150 [info] Extension 'ms-python.black-formatter' v2023.6.0 was successfully installed.

thanks @sandy081 🎉


GH-43410: [Python] Support Arrow PyCapsule stream objects in write_dataset

Rationale for this change
Expanding the support internally in pyarrow where we accept objects implementing the Arrow PyCapsule interface. This PR adds support in ds.write_dataset() since we already accept a RecordBatchReader as well.
What changes are included in this PR?
ds.write_dataset() and ds.Scanner.from_baches() now accept any object implementing the Arrow PyCapsule interface for streams.
Are these changes tested?
Yes
Are there any user-facing changes?
No

GitHub Issue: #43410

@jorisvandenbossche Do you want to update this?

Rebased, will merge if green.


🐞 [BUG] - Issue generating properties assignment for elements with kebab-case names

🐞Bug Report

Version: 1.2.0
Current behavior

When using kebab-case names in visual elements, such as:
<ui:UXML xmlns:ui="UnityEngine.UIElements" ...>
    <ui:VisualElement>
        <ui:Button text="Button text" name="some-button" />
    </ui:VisualElement>
</ui:UXML>

Rosalina binding generator generates bad query names in auto-generated code:
public Button SomeButton { get; private set; }

...

public void InitializeDocument()
{
    SomeButton = (Button)Root?.Q("SomeButton");
}

And then throws an NullReferenceException when interacting with the property.
Expected Behavior

Rosalina bindings generator should generate the appropriate query:
public Button SomeButton { get; private set; }

...

public void InitializeDocument()
{
    SomeButton = (Button)Root?.Q("some-button");
}

Steps to Reproduce

Create a new UI Document
Add an element
Set the name in kebab-case
Try to interact with the generated property.

Possible Solution

Might be related to this statement:
https://github.com/Eastrall/Rosalina/blob/e5b86250e51fdd50ebc185568f641617dc094880/Editor/Scripts/Generator/RosalinaBindingsGenerator.cs#L169
We are using the Name property, which should be only used for generating the elements properties. Instead, I believe we should use the OriginalName since it contains the element's raw name as described in UXML.
https://github.com/Eastrall/Rosalina/blob/e5b86250e51fdd50ebc185568f641617dc094880/Editor/Scripts/Generator/UIProperty.cs#L24-L40

Fixed in v1.2.1


Rename runtime/errors runtime/results

People get confused by the files runtime/errors runtime/results as they do not have  extensions,
so we should rename them to runtime/errors.log runtime/results.log
Moreover, we sometimes use runtime/errors  just for debug info, so we should check when this happens and instead use a runtime/debug.log file.

Agreed.
Not sure if current implementation only prints csv style info there

The grep line in tp{2,3}/execute.sh  takes care of it =)

smart!

@kuzeko, wrt all the "this goes to debug.log".
Once in query mode we use errors.log for debug see al the System.err.print(.

I see, we can live with that then.
I'll close the issue. We'll reopen if something seems out of place.


[cli chat] Error: stream ended before 1 bytes became available

╭─petty@bean in ~/GitHub/status-im/js-waku on main ✘ (origin/main)
╰$ npm run chat -- --staticNode /ip4/<IP_ADDRESS>/tcp/30303/p2p/16Uiu2HAmPLe7Mzm8TsYUubgCAW1aJoeFScxrLj8ppHFivPo97bUZ

><EMAIL_ADDRESS>chat
> ts-node src/chat/index.ts "--staticNode" "/ip4/<IP_ADDRESS>/tcp/30303/p2p/16Uiu2HAmPLe7Mzm8TsYUubgCAW1aJoeFScxrLj8ppHFivPo97bUZ"

PeerId:  QmSZ1HxMUrKLGWetceEk93E2p4f2ppnzU927GUF9Mya5pL
Listening on
	- /ip4/<IP_ADDRESS>/tcp/41475
	- /ip4/<IP_ADDRESS>/tcp/41475
	- /ip4/<IP_ADDRESS>/tcp/41475
Please choose a nickname: petty
Using default nick.
Hi, js-waku!
Dialing /ip4/<IP_ADDRESS>/tcp/30303/p2p/16Uiu2HAmPLe7Mzm8TsYUubgCAW1aJoeFScxrLj8ppHFivPo97bUZ

/home/petty/GitHub/status-im/js-waku/node_modules/p-some/index.js:31
			reject(new AggregateError(errors));
          ^
AggregateError:
    Error: stream ended before 1 bytes became available
        at /home/petty/GitHub/status-im/js-waku/node_modules/it-reader/index.js:37:9
        at processTicksAndRejections (node:internal/process/task_queues:94:5)
        at /home/petty/GitHub/status-im/js-waku/node_modules/it-length-prefixed/src/decode.js:80:20
        at oneChunk (/home/petty/GitHub/status-im/js-waku/node_modules/multistream-select/src/multistream.js:12:20)
        at Object.exports.read (/home/petty/GitHub/status-im/js-waku/node_modules/multistream-select/src/multistream.js:34:15)
        at module.exports (/home/petty/GitHub/status-im/js-waku/node_modules/multistream-select/src/select.js:21:19)
        at Upgrader._encryptOutbound (/home/petty/GitHub/status-im/js-waku/node_modules/libp2p/src/upgrader.js:385:36)
        at Upgrader.upgradeOutbound (/home/petty/GitHub/status-im/js-waku/node_modules/libp2p/src/upgrader.js:167:11)
        at ClassIsWrapper.dial (/home/petty/GitHub/status-im/js-waku/node_modules/libp2p-tcp/src/index.js:42:18)
        at TransportManager.dial (/home/petty/GitHub/status-im/js-waku/node_modules/libp2p/src/transport-manager.js:111:14)
    at maybeSettle (/home/petty/GitHub/status-im/js-waku/node_modules/p-some/index.js:31:11)
    at /home/petty/GitHub/status-im/js-waku/node_modules/p-some/index.js:69:23
    at processTicksAndRejections (node:internal/process/task_queues:94:5)
npm ERR! code 1
npm ERR! path /home/petty/GitHub/status-im/js-waku
npm ERR! command failed
npm ERR! command sh -c ts-node src/chat/index.ts "--staticNode" "/ip4/<IP_ADDRESS>/tcp/30303/p2p/16Uiu2HAmPLe7Mzm8TsYUubgCAW1aJoeFScxrLj8ppHFivPo97bUZ"

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/petty/.npm/_logs/2021-04-20T20_40_06_776Z-debug.log

Cc @corpetty

Could I please have:

OS
Node version

Current priority for js-waku is browser environment.
Do note that in my testing, I noticed issues with NodeJS version 12 & 13. Be sure to use 14 or above.


fix: FixedArray::from_array accept Array as parameter #534

Pull Request Test Coverage Report for Build 1664
Details

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 88.679%

Totals

Change from base Build 1660:
0.0%

Covered Lines:
2624

Relevant Lines:
2959

💛  - Coveralls

Pull Request Test Coverage Report for Build 1665
Details

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 88.679%

Totals

Change from base Build 1660:
0.0%

Covered Lines:
2624

Relevant Lines:
2959

💛  - Coveralls

hi @KKKIIO you may need sign the CLA first

hi @KKKIIO you may need sign the CLA first

Sure, sorry I didn't see it before.


The documentation site is down.

How to get documentation?

may refer to https://github.com/wikichua/simplecontrolpanel/wiki/Installation-&-Usage-Guide
my version is updated suit my need. so u need to trial and error to see what cant be used in ur package version

OK! Thank.
I started to study the LAP package for its finalization according to my needs.
I see you have added the ability to add a class to the config file. This is what was lacking in the first place.

@Khludev ya, i mod the crudgenerator too..

Package no longer maintained
Please consider Laravel AJAX CRUD instead: https://github.com/kdion4891/laravel-ajax-crud


pr_sep4_1

pr_sep4_1_comment

Started jenkins job (build + integration tests execution)
Please check after some time for the build status and test results


Apply changes

It would be great if we could apply the changes to be review into the code, something like a patch.

Could you please elaborate more. thanks :)

Are you taking about downloading patch and applying directly?


Automatic granting/removing of Advantage

Is your feature request related to a problem? Please describe.
Managing Advantage is a real pain
Describe the solution you'd like
Ideally, granting and removing advantage would be somewhat automated. When a PC or NPC wins an opposed test, 1 advantage is granted automatically. When they lose or take damage, all advantage is cleared.
Additional context
I know this isn't a problem with the System so much as a core feature that annoys me, but as a GM, managing the advantage, even with a macro, is tedious. If there was any way to automate the granting/removing of advantage, it would make my job a lot easier. I considered just eliminating it all together, but there are other mechanics that depend on it and then you're almost just playing WFRP 2e again.

Leaving this for GM toolkit


I wonder which file you change based on facebook's mask-rcnn

Because facebook's mask-rcnn has lots of files and I just want to know your algorithm code. And I have already known how to realize mask rcnn. So can you directly tell me where I can see your network design and your loss function.
And thanks.

network and loss function are defined in maskscoring_rcnn/maskrcnn_benchmark/modeling/roi_heads/mask_head/ and maskscoring_rcnn/maskrcnn_benchmark/modeling/roi_heads/maskiou_head/. There should also be some change in nms, but I haven't located it yet.

We do not change nms in this code.


Input boolean name and the proper icon not visible after data analyzer changes its state.

Bug Description
The data analyzer function works perfectly.  afterwards, the input boolean state has changed to true, but when I look at the list of all my Helpers, the entity name is blank and the icon is showing the default icon instead of the custom icon.
Note that when clicking on the helper, the name and icon display properly.
This is also affecting the badge I use to display the entity on my dashboard. Its missing the name and shows the wrong icon.
If i manually change the input helpers state after the data analyzer runs, the name and icon are restored.

1.3.1
Service Call

Paste your service call

Logs

Paste relevant logs here

Additional context

Im running home assistant version 2024.11.1

Thanks for reporting this!
I was able to reproduce the issue. I think the sensor state is not updated correctly. I have limited time at the moment, but will look at this soon!

This also happens when updating other sensors type. What is worst is that the sensor will never be checked "true" by a template, even if the state is correct.

Issue should be fixed and will be in the release.


Add license

Would be great if you could add a license file to this repository, ideally one that is compatible with the Settings app (I think that should be Apache 2.0)

Thank you! Its done: https://github.com/DerpFest-AOSP/vendor_support/commit/9d88317d9660bb03ac660671ac5290160e891a4c

Thanks!


Add option to atlas-cluster to skip user or cluster creation

should be possible to submit
clusters: []
users: []

HI @denist-huma -
Could you elaborate on why you would like this? Would rather an "Atlas Project" chart solve your use-case?
Thanks,
Jason

Hi @denist-huma. Does the "Atlas Project" chart resolve your issue?

@igor-karpukhin I had a custom Helm chart for Atlas Project and AtlasCluster.
Now I am not using it anymore.
I stop using AKO


Difficult to click on menu of issue

Currently the menu button on the right of each issue in the list has a very small clickable area. Oftentimes my click gets registered on the list item itself and opens the issue, which is annoying.
A whole square area on the right of the list item should work as clickable area for the menu. Similar to how the Apple design guidelines recommend a minimum 44*44 px tap area.

It still seems very small, and I'm misclicking lots of times. Better would be to have the clickable area be the full height of the row.


factory openSUSE PasslibUsing.py on Python 2

[  938s] Consider output of recursively compiled program: PasslibUsing.py
[  939s] Comparing output of 'PasslibUsing.py' using '/usr/bin/python2' with flags silent, expect_success, standalone, remove_output, ignore_warnings ...
[ 1025s] --- /usr/bin/python2 (stdout)
[ 1025s] +++ nuitka (stdout)
[ 1025s]
[ 1025s] @@ -1,4 +1 @@
[ 1025s]
[ 1025s] -hello
[ 1025s] -118
[ 1025s] -bye
[ 1025s]
[ 1025s] --- /usr/bin/python2 (stderr)
[ 1025s] +++ nuitka (stderr)
[ 1025s]
[ 1025s] @@ -1 +1,2 @@
[ 1025s]
[ 1025s] +PasslibUsing: /home/abuild/rpmbuild/BUILD/Nuitka-<IP_ADDRESS>6302073.5d14149b/nuitka/build/include/nuitka/helper/dictionaries.h:209: DICT_SET_ITEM: Assertion `Py_REFCNT(value) > 0' failed.
[ 1025s]
[ 1025s] Exit codes 0 (CPython) != -6 (Nuitka)

This is occurring only on Python 2.  It passes on Python 3.

Wow, that's a bad one, reference losses are the worst and luckily for some time typically rare, but very important to hunt down. Which version was this one? Factory or stable or both?

This is done with Nuitka factory, and using the openSUSE standard package for passlib, which is from https://build.opensuse.org/package/show/devel:languages:python/python-passlib and the openSUSE factory has identical version.  All 1.7.1, same as PyPI.  Note it has a patch, to allow testing against libxcrypt, but no change to the source.  Not sure if that is relevant.

Can you still reproduce this one, because I cannot.

Seems to be fixed


linux 下载问题

Problem encountered on https://dotnet.microsoft.com/download/linux-package-manager/centos/runtime-current
Operating System: Linux CentOS / Oracle
Provide details about the problem you are experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant.

We need information about what you are seeing in order to try and help. If you are still having troubles, reopen this issue and please provide details about the problem you are experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant.


Error when using sdm --customize

I read through the documentation and was testing out the sample command as shown in https://github.com/gitbls/sdm/wiki/Example:-Commands. However, I cannot build a customized image, because of the following error:
* Mount IMG '2022-09-22-raspios-bullseye-arm64.img.xz'
losetup: 2022-09-22-raspios-bullseye-arm64.img.xz: Warning: file does not fit into a 512-byte sector; the end of the file will be ignored.
mount: /mnt/sdm: special device /dev/loop27p2 does not exist.
? Error mounting IMG '2022-09-22-raspios-bullseye-arm64.img.xz'

I'm running this on Ubuntu 22.04 (64 bit).
Note: I changed the command from the example a bit by removing irrelevant switches and adding switches the script reported as mandatory:
removed:

--apps
added:
--user
--nowpa

I'm so stupid: I didn't notice I have to unzip the image first.
$ sudo apt install p7zip-full p7zip-rar
$ 7z e 2022-09-22-raspios-bullseye-arm64.img.xz

Afterwards it works like a charm. I'm closing this issue but leave it for other noobs so they can learn.

Glad that you sorted it out. sdm checks for a ".zip" file type, but did not get it updated yet for ".xz". Will take care of this. Thanks for the reminder!


[WIP] Volunteers system integration - for review

Proof of concept.
Just need to set the correct redirect URL.

@noam-almog @may-ben-arie Please take a look


implement oauth client for deployer - terraformboot and opentofu

currently the API calls to terraform boot insert the existing access token from the end user in the requests to terraformboot and opentofu.
This works fine for almost all usecases but fails when the request has no token or when the request is generated independently by xpanse.

[ ] implement an independent Oauth client on xpanse for sending requests to terraform-boot and open-tofu
[ ] we will need a property to enable or disable this.
[ ] Extend Zitadel/IAM config scripts to configure xpanse oauth client.
[ ] update documentation

generating client credentials automatically using the zitadel terraform provider is currently not available. Spoke to the Zitadel devs  and they informed that, it would be implemented this week. Will pause the user story until this is available.


adding stalebot to the repository as discussed with the team

Signed-off-by: Upkar Lidder<EMAIL_ADDRESS>

Merging to the main repo after discussing with the team. Ideally, somebody else approves and merges, but everybody is busy.


DynamoDB On-demand capacity

Hello,
Actually, the AFT table's in DynamoDB are provisioned with differents read/write capacity units
would it be possible to choose the capcity mode like on-demand ?
Thanks

Hey @Menahem1, thanks for reaching out, do you have any specific use case to help us better understand this request?

Hello @balltrev ,
Thanks for your reply !
it's just cost optimization, actually with provisioned capacity we pay in any case while with 'on-demand' it's just when we need
Thanks


Dynamic filter in a page query

How do I create a dynamic filter in a page query? In this example, I want to filter only posts that are less than or equal to today? I am able to pass a query variable using graphiql, but not sure how to pass that from inside gridsome.
<page-query>
query($today: Date!) {
  posts: allContentfulNews(
    filter: { launchDate: { lte: $today } }
  ) {
    edges {
      node {
        id
        title
        launchDate
      }
    }
  }
}
</page-query>

HI, to my. understanding, page-query seems to be server side so the variables can't reach Gridsome page-query.
You better use computed method to loop thru your datas and create each page ( or bloc if it is a component )
  computed: {     getNewsByLaunchDate () {       var newsData = this.$page.edges.filter( article => article.node. launchDate === this.$today)       return newsData[0].node     }   }
Should work.


Fix calibration error scaling

This fixes the calibration error scaling issue discussed in #56

This code proposal is correct as the read() function adds the error after the ax, ay and az are converted to G's.
(gyro idem).


Lithium 0.7.8 neighbor table direct access

Lithium 0.7.8 just released and it tripped the neighbor table crash/warning in FerriteCore.
populateNeighborTable = true works as advertised, so this isn't blocking.

Update FerriteCore, this is not a problem with 4.1.0 and above.


not grep compatible

Description
If you're suggesting a new feature then just a description will suffice.
If you do a "neofetch > 1.txt" "neofetch > 2.txt" etc a few times, then try to "grep *.txt $USER" it goes weird.... Just saying... I'd look at the code, but I am guessing each line isn't ending with a reset to terminal colors??

[ ] Does this issue still occur in the master branch? (Required if issue)

TBD, I'll give it a shot if I have time in the next few days.
Neofetch version
Screenshot
Not going to do that...
Config file
none
Verbose log
none

Run neofetch -vv 2> neofetchlog

Upload the contents of neofetchlog to pastebin, gist or equivalent.

test script:
mkdir ~/SysDat neofetch > ~l/SysDat/$(date '+%Y-%m-%d-%H:%M:%S') sleep 1 neofetch > ~l/SysDat/$(date '+%Y-%m-%d-%H:%M:%S') sleep 1 neofetch > ~l/SysDat/$(date '+%Y-%m-%d-%H:%M:%S') sleep 1 neofetch > ~l/SysDat/$(date '+%Y-%m-%d-%H:%M:%S') sleep 1 neofetch > ~l/SysDat/$(date '+%Y-%m-%d-%H:%M:%S') grep ~/SysDat/*.txt $HOST

There are multiple ways to get parseable information output.

neofetch --json.
neofetch cpu, neofetch battery, etc etc.
neofetch --stdout


 Ex1. It is inconvenient when [....]. Ex2. There is a recent paper [....], which is very helpful for [....].
Related resources
If there is an official code release or third-party implementations, please also provide the information here, which would be very helpful.
Additional context
Add any other context or screenshots about the feature request here. If you would like to implement the feature and create a PR, please leave a comment here and that would be much appreciated.

尝试在 git 上对modelscope的仓库修正 commit 记录的 GIT_COMMITTER_NAME 等信息后 git push -f 运行结果如下：   看起来像是权限不足的样子，请问如何才能放开这个权限，让自己的仓库能修正过去有误的 commit 信息并签入到云端
Describe the feature Features description
Motivation A clear and concise description of the motivation of the feature. Ex1. It is inconvenient when [....]. Ex2. There is a recent paper [....], which is very helpful for [....].
Related resources If there is an official code release or third-party implementations, please also provide the information here, which would be very helpful.
Additional context Add any other context or screenshots about the feature request here. If you would like to implement the feature and create a PR, please leave a comment here and that would be much appreciated.

看起来在 modelscope 平台上没有修改受保护分支的选项，只有跳到这个仓库真正的 gitlab 大后方才可能有对其分支解除保护，但是怎样才能找到并控制 modelscope 上的 repo 对应到 gitlab 的那个仓库，感觉每个 modelscope 账号背后都对应着一个 gitlab 账号，但是这个账号看起来对 modelscope 用户是不可知的

How to remove the stale label? Nobody replied me and no action was conducted after I created this issue. What's the problem?


Prerender error on Vercel Edge with latest @nuxtjs/robots version

Describe the bug
I wasn't sure whether to create an issue here or in the @nuxtjs/robots repo 😬
I’ve been using @nuxtjs/robots 3.0.0 so far but decided to switch to @nuxtjs/seo 2.0.0-rc.15.
Everything works perfectly fine in my local environment, but deploying to Vercel gives me this error:
[info] [nitro] Initializing prerenderer
[info] [nitro] Prerendering 1 routes
[error] [unhandledRejection] urls.forEach is not a function
  at .nuxt/prerender/chunks/runtime.mjs:2989:10
[warn] This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
[error] TypeError: urls.forEach is not a function
    at file:///vercel/path0/apps/spotlight/.nuxt/prerender/chunks/runtime.mjs:2989:10
[error] [nitro] [unhandledRejection] urls.forEach is not a function
  at .nuxt/prerender/chunks/runtime.mjs:2989:10
[log] [nitro]   ├─ /api/_content/cache.1721151996320.json (494ms)
[info] [nitro] Prerendered 1 routes in 38.51 seconds
[success] [nitro] Generated public .vercel/output/static

Unfortunately, these errors prevents edge runtime to serve the site. What helped:

downgrading @nuxtjs/seo to 2.0.0-rc.12 it didn't help 😓
downgrading @nuxtjs/robots to 3.0.0 (it helped with robots, but possibly introduced issues with sitemap)
disabling robots module

I tried to configure the module using both Robots.txt and Nuxt Config.
These findings suggest there may be an issue with the recent Robots version. I’m happy to provide more details if needed.
Reproduction
No response
System / Nuxt Info
- Operating System: `Darwin`
- Node Version:     `v20.10.0`
- Nuxt Version:     `3.12.3`
- CLI Version:      `3.12.0`
- Nitro Version:    `2.9.7`
- Package Manager<EMAIL_ADDRESS>- Builder:          `-`
- User Config:      `debug`, `devtools`, `experimental`, `future`, `typescript`, `app`, `alias`, `css`, `compatibilityDate`, `hooks`, `modules`, `routeRules`, `runtimeConfig`, `cookieConsent`, `content`, `dayjs`, `googleFonts`, `gtm`, `image`, `i18n`, `lodash`, `ogImage`, `seoExperiments`, `schemaOrg`, `linkChecker`, `security`, `site`, `sitemap`, `supabase`, `nitro`, `veeValidate`, `vite`
- Runtime Modules:  `<EMAIL_ADDRESS>`<EMAIL_ADDRESS>`<EMAIL_ADDRESS>`<EMAIL_ADDRESS>`<EMAIL_ADDRESS>`<EMAIL_ADDRESS>`<EMAIL_ADDRESS>`<EMAIL_ADDRESS>`<EMAIL_ADDRESS>`<EMAIL_ADDRESS>`<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>- Build Modules:    `-`

This is quite a strange bug, basically, the Nuxt Content integration is failing because the internal API call is failing for some reason.
I've pushed up some improvements so it can gracefully handle when these things fail instead of completely breaking.
You can try it out by deleting your lock file + node_modules and re-installing, this will use the latest nuxt robots version 4.0.2.
Let me know if you have any issues.

Works like a charm! Thank you so much for quickly looking into this, @harlan-zw. I didn’t find any issues anymore.
If you need my assistance in pinpointing the root cause on my end, just ping me.


Snake Game in Python

🚀 Feature
I would like to add a snake game using python to this project.
Have you read the Contributing Guidelines on Pull Requests?
Yes i have read the guidelines clearly
Motivation
I wish to contribute a fun, interactive and user friendly snake game.
Pitch
I would be implementing this using GUI programming and the special libraries available in python.
I am a GSSOC'21 participant and wish to contribute to this project. Can you please assign me this issue?

Hello @bhav09 !
I have given the pull request for this issue. Do have a look at it and let me know the changes if any.
Thank you!

@Swetha126 can you please link the PR here. That would be helpful.

Ya sure will do!


Bump vineyard to 0.8.5

What do these changes do?

Related issue number

Fixes

There shouldn't be any conflict, you could update the CI runner image directly.


OTA Publish to 0.9.18-ota, 0.12.7-ota, 0.13.7-ota

Description
OTA Publish to 0.9-prod 0.12-prod and 0.13-prod
Tags:

0.9.18-ota
0.12.7-ota
0.13.7-ota

On what platform have you tested the change?

[ ] Android - Emulator
[x] Android - Physical device
[x] iOS - Emulator
[ ] iOS - Physical device

Screenshots
Please attach screenshots showing the change if relevant
Checklist

[ ] I have updated mockServer

Out of scope and potential follow-up
Is there any related changes that you plan to do in a follow-up PR or voluntarily excluded from the scope?

@MikeD-ZOE does this cause any issues by changing the app.json?

No. These diff's are only showing because release-0.x-legacy was cut from develop a while ago. If you compare this the release-0.x-legacy to one of the tagged OTA releases, you'll see what the delta of what will be published.

@abubuwe : https://github.com/zoe/covid-tracker-react-native/compare/0.13.7-ota...develop

@selvach I'm still unclear what that would mean for older app versions on other release channels but if @MikeD-ZOE happy then I can go with that.

looks as expected


Text input caret resets to start in some LineEdits and TextEdits

Godot version:
4.0 ceed52493696d
OS/device including version:
win 10
Issue description:
EditorInspector line edit's and text areas reset the caret to the beginning. Note: this does not happen on line edit's and text areas in-game, seems to only be the editor. The behaviour is seen both when typing and clicking in the control area, as seen below.

Successfully repro'd while trying to repro https://github.com/godotengine/godot/issues/41962. I'll start checking this out.

This also affects every text editable property in Project Settings and Editor Settings, including 'Application' (Config etc.), 'Layer Names', etc. As a workaround you can write somewhere outside the editor and paste things in.

This is caused by #41697, as every refresh it's calling set_text. Also makes editing arrays etc impossible:

Why is cursor_pos set to zero on set_text()?


TextArea

Context
Create a component enabling the user to enter text (e.g. a description) in a given zone.

User flow

go on MassaStation
go to the "Search" page to access deployed sites
click on sidebar for upload a website
enter a text in the "description"

Time
Predicted : 2H
Final : 3H

Love the predicted vs final time @maxime-carabina. It's great to work like this as you will see your progress days after days ;)


[Palette] Christmas Sinistea

Encountering a sinistea results in your GUI migrating to the top left of your screen.

Summon/Send out a Christmas Sinistea Phony Form (unsure if its just this particular form or all forms of christmas sinistea)
Watch as your GUI migrates to the top left of your screen
See error

For no GUI migration to occur
Orion, likely all

This has been fixed.


Allow launch on Fabric for versions of the same major version

Mod does not launch on 1.21.1 Fabric

Fixed in 2.0.1, pr is not in need.
And this repo has been moved to https://git.deechael.net/DeeChael/Concentration-Reloaded.
Will not accept any pull requests


i18n for your language wanted

Hello TOAST UI Editor users.
If you found your language is not supported yet.
You can help us and become a contributor. This is a good first issue.
A PR #33  made by @elamperti is a good example. Please check it out.

Close this issue. And give PR if you want to add more languages in the future.


list community members

From @kyyberi on October 17, 2015 4:41
As a community member I want to see list of all community members. From each member, I want to see role and basic information.
Copied from original issue: APIOps/portal#19

This issue was moved to APIOps/apiops-meetup#11

This issue was moved to APIOps/apiops-meetup-website#17


PowerShell package not found on arm64 (aarch64) for centos 7.9

Prerequisites

[X] Write a descriptive title.
[X] Make sure you are able to repro it on the latest released version
[X] Search the existing issues.
[X] Refer to the FAQ.
[X] Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Steps to reproduce
Docs say arm64 support for centos 7 is in PowerShell 7.2. But the package isn't found. This works on amd64.
% docker run -ti --platform linux/arm64 centos:7 bash
Unable to find image 'centos:7' locally
7: Pulling from library/centos
6717b8ec66cd: Pull complete
Digest: sha256:9d4bcbbb213dfd745b58be38b13b996ebb5ac315fe75711bd618426a630e0987
Status: Downloaded newer image for centos:7
WARNING: image with reference centos was found but does not match the specified platform: wanted linux/arm64, actual: linux/amd64
[root@f24ea398bc68 /]# cat /etc/centos-release
CentOS Linux release 7.9.2009 (AltArch)
[root@f24ea398bc68 /]# uname -a
Linux f24ea398bc68 5.10.47-linuxkit #1 SMP Sat Jul 3 21:51:47 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux

[root@f24ea398bc68 /]# curl -fsS https://packages.microsoft.com/config/rhel/7.2/prod.repo | tee /etc/yum.repos.d/microsoft.repo && yum install -y powershell
[packages-microsoft-com-prod]
name=packages-microsoft-com-prod
baseurl=https://packages.microsoft.com/rhel/7.2/prod/
enabled=1
gpgcheck=1
gpgkey=https://packages.microsoft.com/keys/microsoft.ascLoaded plugins: fastestmirror, ovl
Determining fastest mirrors
 * base: mirror.vacares.com
 * extras: mirror.vacares.com
 * updates: mirror.vacares.com
base                                                                                | 3.6 kB  00:00:00
extras                                                                                | 2.9 kB  00:00:00
packages-microsoft-com-prod                                                                                | 3.0 kB  00:00:00
updates                                                                                | 2.9 kB  00:00:00
(1/5): base/7/aarch64/group_gz                                                                                | 153 kB  00:00:01
(2/5): extras/7/aarch64/primary_db                                                                                | 246 kB  00:00:01
(3/5): base/7/aarch64/primary_db                                                                                | 4.9 MB  00:00:01
(4/5): updates/7/aarch64/primary_db                                                                                | 2.1 MB  00:00:01
(5/5): packages-microsoft-com-prod/primary_db                                                                                |  81 kB  00:00:02
No package powershell available.
Error: Nothing to do

Expected behavior
Expected powershell to install in an arm64 image, just like it does on amd64.

Actual behavior
No package powershell available.

Error details
see above, sorry this is an installation issue not an issue using powershell

Environment data
testing on Docker for Mac 4.0.1, both M1 and Intel

Visuals
No response

I'm sorry I saw PowerShell 7.2 arm64 support under RHEL leadership 7 and assumed it was available for CentOS 7 too. I guess it's not? Do I have to use an alternate install method for arm64 centos 7?
https://docs.microsoft.com/en-us/powershell/scripting/install/installing-powershell-on-linux?view=powershell-7.1#red-hat-enterprise-linux-rhel