Set wifi clock enable bits in the correct register

This PR fixes esp-wifi/#211

Hold on I reverted a change that was not present in esp-idf and now my firmware is broken again

Okay, this needs much more work than I thought when I uploaded. Current state is that the PR breaks wifi completely, the driver hangs in register_chipv7_phy now. Turns out that not setting the 1 << 10 bit in wifi_clk_en fixes this, but since that is not what esp-idf does, I'm reluctant to propose the change.
I'll continue to play "find the 5 differences" with this, but esp-idf is a bit cryptic in why some things are done (like, setting 0 bits in a register at some point).

@bjoernQ
// from experiments `0x00FB9FCF` is not enough for esp-wifi to work
const SYSTEM_WIFI_CLK_EN: u32 = 0xFFFFFFFF;

The reason why you had to do this is that the enable_phy and disable_phy functions modified the wrong register. This means that the clock initialization had to enable all clocks to also enable the PHY. This seems to be an "accidentally okay" situation.
After writing clock enable bits in the correct register, this constant no longer has to be all-1s.


bump honeybadger to 2+ since we're not on jruby

Depends on #641
V 2+ backgrounds jobs automatically if it detects a background worker framework, e.g sidekiq. I've configured the production_config/honeybadger to support both new and old versions of the gem by default.

Are we still planning on running sidekiq on JRuby or is that on MRI as well?

Good point, i'm not sure yet but switching the base image to MRI (still trying to get an image up for testing) will force sidekiq to use mri. We'd need to split sidekiq into it's own docker image / deploy setup to be deployed with panoptes staging.


Switching to new query editor doesn't clear results/messages for input without results

Azure Data Studio Version: 1.8.0
Steps to Reproduce:

Open new query window
Run query that returns results
Open another new query window
Toggle query results (shift + win + r on Windows)
Results and messages are still there from previous query window

I wonder what the desired behavior here is. do we show the window but with blank panels, or just not show the window? @kburtram @Charles-Gagnon @yualan

The current default behavior of hiding the tabs if there aren't any results is fine, and then if a user does manually toggle the window I'd say we just do what SSMS does and show a blank messages window.

My pr basically does that, but shows a blank results tab and messages tab. I could change the logic to only be the messages tab if it's important.

I'm fine with having both, not like there's anything useful anyways.


[latency] New latency visualization tool

Adds a build config - latent_see - that configures a module and some macros to allow recording of latency information through the stack and across threads. One can then use tools that understand the chromium event trace format (eg ui.perfetto.dev) to visualize the traces.

I made some modifications to the flow interface... I'd prefer to keep it so that the metadata is captured just once - otherwise there's an easy class of bugs to introduce (different metadatum being used at start & end).


Improve scratch getting-started-guide.

Supercedes #11454

Addressed all comments in #11454
Just need rubberstamp.
@davidopp @lavalamp

Rebase?

Would be nice to get the flag comments resolved, since you have to rebase anyway. LGTM apart from that

Rebased.  Working on comments.

updated.

Sorry, some of my comments about "this should be a sub-bullet of..." are based on misreading what you had. So you can generally ignore those, but please check all of your lists to make sure they are rendering the way you want.

I am happy with my lists.

fixed david's comments in next push

ready

LGTM

fixed.

LGTM


Add Delegate counterparts of Action and Func type properties

For example, there is the following property in the Bridge.NET\Core\Html5\WindowInstance.cs
public Action<Event> OnFocus;

It doesn't allow to set an arbitrary handler, for example, an Action without parameters. So, it might be worth to have a Delegate counterpart on the onFocus property, like:
public Delegate OnFocusDelegate;

We might be able to come up with a better name.
Slated for the future.

See Also
#2767.

Closing this issue as we will not be implementing this feature. All Html5 functionality is moving to Retyped.


12 accordion variation

Please always provide the GitHub issue(s) your PR is for, as well as test URLs where your change can be observed (before and after):
Fix #12
Test URLs:

Before: https://main--macquarie-help-centre--hlxsites.hlx.page/help/drafts/ujjgupta/helping-you-transact-online
After: https://12-accordion--macquarie-help-centre--hlxsites.hlx.page/help/drafts/ujjgupta/helping-you-transact-online

animation for carousel is still pending, I suppose that would be covered as part of seperate PR, rest looks good.

@asthabh23 you meant accordion right? :)

@asthabh23 you meant accordion right? :)
definitely yes @ujjwal5 :)


Fix: Ensure All Tensors and Models are on the Same Device

Resolve the error on some devices resulting from SparseGPTrainer.train() where:
RuntimeError: Expected all tensors to be on the same device, but found at least two devices, cuda:0 and cpu! (when checking argument for argument tensors in method wrapper_CUDA_cat)

The unit tests do not account for tests on GPUs, and the error is reproduced in the following colab notebook. One solution is that for making the inference, it should explicitly be moved over to the CPU (i.e., self.y_val.detach().cpu().numpy()) and also give the users which device they would like BaseTrainer class to be trained on.

The unit tests do not account for tests on GPUs, and the error is reproduced in the following colab notebook. One solution is that for making the inference, it should explicitly be moved over to the CPU (i.e., self.y_val.detach().cpu().numpy()) and also give the users which device they would like BaseTrainer class to be trained on.

Apply hard reset to shorten the number of commits which was mostly for debugging on google colab

Patched after hard reset in favor of PR https://github.com/Unco3892/UncertaintyPlayground/pull/2


feat: add jenkins integration doc.

Fix: https://github.com/casbin/casdoor/pull/364
Signed-off-by: 0x2a<EMAIL_ADDRESS>

@Steve0x2a plz fix:


[SAM-webui] - A simple tool for using SAM

Hi! I just release a simple webui for the Segment Anything Model.
There are positive point / negative point / boxes prompts and auto inference to be used!
Feel free to try it.
This is my small project and it's my first time to write a webui.
If you have any question or suggestion, you can post it on my issue. Thanks!
https://github.com/derekray311511/SAM-webui

Thanks for sharing!


Business logic and tests

Description
Create the business logic for the working of the game, as well as the interface to reflect changes in the UI.
Includes tests in multiple scopes proving that the code works both independently and in integration.

[x] New feature (non-breaking change which adds functionality)

Closes #13
How Has This Been Tested?
GameFragmentTest:

[x] confirms updation of content description

NavigationTest:

[x] confirms that navigation works as expected

TicTacToeViewModelTest:

[x] set_EXAMPLE_row_test_row_returns_true() suite: confirms that getting three in a row returns a win
[x] set_top_left_to_bottom_right_diagonal_test_live_data_values_change(): confirms isWin and winningPlayer liveData
update properly on win
[x] set_icon_as_x_confirm_returns_x_icon(): confirms viewModel.getIcon() functionality
[x] set_icon_as_illegal_arg_confirm_returns_exception_and_error_icon(): confirms viewModel.getIcon() edge case

Test Configuration:

Firmware version: API 31
Hardware: Pixel 4
Toolchain: Tests launched with Gradle on emulator
SDK: Android SDK

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

@j-roskopf Gotcha! I actually had the same thought after posting this. And refactored it to have an underlying interface which I made a fake of for testing. I want there to only be one instance throughout the app that I can reset after each game.
If I hadn't have done that, would an @After notation with some cleanup have taken care of it in testing, or would it just be preferable in general to make it a class?
I wasn't sure if it could then create multiple conflicting instances when called from different modules. It gets referenced a lot.
Will push the aforementioned code shortly.

using an interface and then creating a 'real' and a 'fake' implementation for prod / testing is a great strategy.
using @after in your unit tests to cleanup the state would have also solved it yeah

@j-roskopf I had multiple issues crop up around testing the singleton, as you predicted!
It makes me a little uncomfortable, but for the moment I have the fake modeled as a class. This way each test can have its own state. I tried my utmost to reset the gameboard between tests even while using the same object, but it clearly got me nowhere. I suppose I just don't understand what exactly is going on behind the scenes yet.
I don't think testing it as a class would have any catastrophic effect on the actual function of the game.
I believe that some difference in the way the tests ran compared to the actual application was causing it not to reset properly.
Resetting the game board after each game should still function normally.
If this still seems fine, I am ready to merge this branch and finalize the full functionality in a new one.
Hope you're doing well,
Thanks again for all the help!

@j-roskopf I've actually finished the full function branch as well and I'll make a pr for you to review as soon as you ok this one! If you find anything I'll work on that first of course!


Add ability to configure which port

Configuration currently does not offer an option to specify which port the websocket listens on.

Fixed.


Hyundai longitudinal (CAN): detect and conditionally send FCA12

Per discussion with @sshane on Discord, we need to detect and conditionally send FCA12 to HKG CAN platforms that have FCA12.
Prerequisite of

https://github.com/commaai/openpilot/pull/26967

Detecting a new signal usually requires some verification, like measuring its startup time, to ensure we don't not detect it (the toyota gas pedal signal took too long to start, so we had to hard code it by platform). I would consult the list I posted in the other PR to see if it's safe to use FCA11 now that we know which platforms it's on.

List for reference: https://github.com/commaai/openpilot/pull/28479#issuecomment-1683423682

We only need to detect FCA12 if we plan to enable longitudinal on the cars where FCA12 != FCA11 existing. That is only one in your list in https://github.com/commaai/openpilot/pull/26967; HYUNDAI KONA ELECTRIC 2019. Can you test on that platform still sending FCA12?

FCA12 is just a user setting mode message largely, perhaps we need to set/unset other bits to not fault on the cars where it does now.

You can also omit the Kona from the PR and just merge individual cars (preferred), that already have FCA.


Build on commit

Need to automate the build of the dagster code when a configuration file updates.
Need to document and automate the whole build process when a config file changes. It would be good to do this all the way to docker containers.
Need to diagram this flow out better in the documents.

workflows for containers build into nsfearthcube

Do we want to build in a gleenerio dockerhub?
Then we might need to set a variable for the image names


gulp.src does not copy subdirs within symlink

$ gulp -v
CLI version 1.2.2
Local version 4.0.0-alpha.2

Directory structure of images and symlink'ed directory (shared-assets):
├── images
│   └── branding -> ../shared-assets/branding/     (this is a symlink)
├── shared-assets
│   ├── branding
│   │   ├── img1.png
│   │   ├── img2.png
│   │   └── dir1
│   │       ├── img3.png
│   │       └── img4.png

gulp.src('..../images/**/*.{.jpg,.png}').pipe(gulp.dest('dist/images'))

Produces:
├── images
│   ├── branding
│   │   ├── img1.png
│   │   └── img2.png

gulp.src('..../images/**/*').pipe(gulp.dest('dist/images'))  // matches all files

Produces:
├── images
│   ├── branding
│   │   ├── img1.png
│   │   └── img2.png
│   └── dir1  (empty dir)

I expected dir1 and its contents to be in the output. To further clarify, I do want gulp to copy the contents (vs copying the symlink) which it does correctly with img1.png, img2.png, just not with subdirs or their contents img3.png, img4.png.
Is this expected behavior? Bug?
I don't feel like it's a fault of my glob string, since I can use /**/*.{jpg,png} for any number of subdirs of any depth that aren't symlinked.

Anything I can do to push this along? I'm new to node, but willing to help.

There is an option follow, which can help you.
gulp.src('..../images/**/*', { follow: true })
But be aware of cyclic links. That kind of mistake maybe cause delete of all files.
Optionally, you can use workaround too
`var vfs = require('vinyl-fs');
gulp.task('myTask', [], function() {
vfs.src'..../images/**/*')
.pipe(vfs.dest('dist/images'))
)};`

The option mentioned by @MasterOfZozo is actually followSymlinks but it is defaulted to true already.  Please provide a reproduction repository for people to debug against.

@phated https://github.com/k-funk/gulp-symlink-subdir-bug
I included followSymlinks: true so that @MasterOfZozo could see it happen.

I think that the bug is a naming between glob-stream, and glob. followSymLinks is being passed as an option to glob.Glob, instead of follow here: https://github.com/gulpjs/glob-stream/blob/master/index.js#L28
If I add ourOpt.follow = true; right before calling var globber = new glob.Glob(ourGlob, ourOpt);, all is well. Could you ensure that this option gets passed correctly ASAP?
For future minor/major releases:
I'm not entirely sure why one-level-deep of files within a symlink were read into the stream, but 2+ levels were not. My guess is that wrap-with-vinyl-file.js is handling more than is necessary... but I could be wrong.

@k-funk we pass all options through to node-glob;  I think that's what @MasterOfZozo was talking about with the `{ follow: true }

Not quite understanding the benefits of having followSymlinks be true, and follow being false. Seems to me that if someone wants to follow symlinks to non-symlinked files, they'd want to include subdirectories and their contents as well.

followSymlinks turns symbolic links into hard files (reads the contents of the linked file and creates duplicate files in the output, etc).  It might be a poor name for what it actually does, but that's what we have right now.  follow does something different, in which it follows symlinks throughout a tree, and isn't enabled by default in node-glob because it breaks on circular links. Those 2 behaviors are mutually exclusive so we can't force follow on if followSymlinks is set to true.
It's a frustrating state of naming but imagine followSymlinks as convertToFile and you'd have { follow: true, convertToFile: true } (notice how they are very different with better naming).
I'm going to close this and chalk it up to a documentation problem (which have multiple issues open), but I'll open an issue on vinyl-fs to revisit the naming of the followSymlinks option.  Thanks for bringing this up!


Added roadmap for blockchain

Fixes Issue
#205
Changes proposed

Screenshots

Note to reviewers

HI @siddhant-khisty please review my PR and merge it

@c99SRS We are going to remove the roadmap which is on the website. Please don't link to the website. The roadmap needs to be converted to a markdown format which can be displayed here on GitHub.

HI @siddhant-khisty  removed the roadmap from the readme file. Please review it

Please refer to #207 for how you have to make the PR

@c99SRS I think you didn't get the issue. Please refer the PR #207 to see how they have contributed to this issue. I am closing this PR


Request support for Ledvance SMART+ Planon Plus Backlight

Log message
2024-12-23 15:58:19.666 DEBUG (SyncWorker_11) [custom_components.tuya_local.helpers.device_config] Loaded device config ledvance_ceiling_light.yaml
2024-12-23 15:58:19.667 DEBUG (MainThread) [custom_components.tuya_local.helpers.config] Adding light for light_mainlight
2024-12-23 15:58:19.843 DEBUG (MainThread) [custom_components.tuya_local.device] TV Licht received {"20": true, "21": "white", "22": 20, "23": 0, "24": "00db01f4026c", "26": 0, "41": false, "full_poll": true}
2024-12-23 15:58:19.945 DEBUG (MainThread) [custom_components.tuya_local.device] TV Licht persistant connection set to True
2024-12-23 15:58:29.479 DEBUG (MainThread) [custom_components.tuya_local.device] TV Licht received {"51": "AAcA2wH0AmwAFAAA", "full_poll": false}
2024-12-23 15:58:29.593 DEBUG (MainThread) [custom_components.tuya_local.device] TV Licht received {"20": true, "22": 20, "23": 0, "24": "00db01f4026c", "full_poll": false}
2024-12-23 15:58:29.708 DEBUG (MainThread) [custom_components.tuya_local.device] TV Licht received {"30": "AAAAdQUBBgAAAAAAAAABBh4AAAAAFBkBCQAAAAAAZGQBFAAAAAAAUDIBFx4AAAAAAAA=", "full_poll": false}
2024-12-23 15:58:29.822 DEBUG (MainThread) [custom_components.tuya_local.device] TV Licht received {"31": "AAA=", "full_poll": false}
2024-12-23 15:58:29.935 DEBUG (MainThread) [custom_components.tuya_local.device] TV Licht received {"32": "AAA=", "full_poll": false}
2024-12-23 15:58:39.517 DEBUG (MainThread) [custom_components.tuya_local.device] TV Licht received {"51": "AAcA2wH0AmwAFAAA", "full_poll": false}
2024-12-23 15:58:39.630 DEBUG (MainThread) [custom_components.tuya_local.device] TV Licht received {"20": true, "22": 20, "23": 0, "24": "00db01f4026c", "full_poll": false}
2024-12-23 15:58:39.744 DEBUG (MainThread) [custom_components.tuya_local.device] TV Licht received {"30": "AAAAdQUBBgAAAAAAAAABBh4AAAAAFBkBCQAAAAAAZGQBFAAAAAAAUDIBFx4AAAAAAAA=", "full_poll": false}
2024-12-23 15:58:39.859 DEBUG (MainThread) [custom_components.tuya_local.device] TV Licht received {"31": "AAA=", "full_poll": false}
2024-12-23 15:58:39.973 DEBUG (MainThread) [custom_components.tuya_local.device] TV Licht received {"32": "AAA=", "full_poll": false}

{
  "home_assistant": {
    "installation_type": "Home Assistant OS",
    "version": "2024.12.5",
    "dev": false,
    "hassio": true,
    "virtualenv": false,
    "python_version": "3.13.0",
    "docker": true,
    "arch": "x86_64",
    "timezone": "Europe/Berlin",
    "os_name": "Linux",
    "os_version": "6.6.66-haos",
    "supervisor": "2024.12.0",
    "host_os": "Home Assistant OS 14.1",
    "docker_version": "27.2.0",
    "chassis": "vm",
    "run_as_root": true
  },
  "custom_components": {
    "tuya_local": {
      "documentation": "https://github.com/make-all/tuya-local",
      "version": "2024.12.1",
      "requirements": [
        "tinytuya==1.15.1",
        "tuya-device-sharing-sdk>=0.1.9,<=0.2.99"
      ]
    },
    "hacs": {
      "documentation": "https://hacs.xyz/docs/configuration/start",
      "version": "2.0.1",
      "requirements": [
        "aiogithubapi>=22.10.1"
      ]
    },
  },
  "integration_manifest": {
    "domain": "tuya_local",
    "name": "Tuya Local",
    "codeowners": [
      "make-all"
    ],
    "config_flow": true,
    "dependencies": [],
    "documentation": "https://github.com/make-all/tuya-local",
    "integration_type": "device",
    "iot_class": "local_push",
    "issue_tracker": "https://github.com/make-all/tuya-local/issues",
    "requirements": [
      "tinytuya==1.15.1",
      "tuya-device-sharing-sdk>=0.1.9,<=0.2.99"
    ],
    "version": "2024.12.1",
    "is_built_in": false,
    "overwrites_built_in": false
  },
  "setup_times": {
    "null": {
      "setup": 4.330500041760388e-05
    },
    "01JFQNENKQCPYZN1EFYDPZP6QA": {
      "wait_import_platforms": -4.064988811999683,
      "config_entry_setup": 4.1368223780000335
    }
  },
  "data": {
    "name": "Tisch Licht",
    "type": "ledvance_ceiling_light",
    "device_id": "**REDACTED**",
    "device_cid": "",
    "local_key": "**REDACTED**",
    "host": "**REDACTED**",
    "protocol_version": 3.3,
    "tinytuya_version": "1.15.1",
    "api_version_set": 3.3,
    "api_version_used": 3.3,
    "api_working": true,
    "status": {},
    "cached_state": {
      "updated_at":<PHONE_NUMBER>.4073772,
      "20": true,
      "26": 0,
      "41": false,
      "51": "AAYAAAPoA+gD6AAA"
    },
    "pending_state": {},
    "connected": true,
    "force_dps": [],
    "home_assistant": {
      "name": "Tisch Licht",
      "name_by_user": null,
      "disabled": false,
      "disabled_by": null,
      "entities": [
        {
          "disabled": false,
          "disabled_by": null,
          "entity_category": null,
          "device_class": null,
          "original_device_class": null,
          "icon": null,
          "unit_of_measurement": null,
          "state": {
            "entity_id": "light.tisch_licht_mainlight",
            "state": "on",
            "attributes": {
              "min_color_temp_kelvin": 3000,
              "max_color_temp_kelvin": 6500,
              "min_mireds": 153,
              "max_mireds": 333,
              "supported_color_modes": [
                "color_temp"
              ],
              "color_mode": "color_temp",
              "brightness": 0,
              "color_temp_kelvin": null,
              "color_temp": null,
              "hs_color": null,
              "rgb_color": null,
              "xy_color": null,
              "friendly_name": "Tisch Licht Mainlight",
              "supported_features": 0
            },
            "last_changed": "2024-12-23T12:40:04.754382+00:00",
            "last_reported": "2024-12-23T12:47:56.710938+00:00",
            "last_updated": "2024-12-23T12:47:56.710938+00:00"
          }
        },
        {
          "disabled": false,
          "disabled_by": null,
          "entity_category": null,
          "device_class": null,
          "original_device_class": null,
          "icon": null,
          "unit_of_measurement": null,
          "state": {
            "entity_id": "light.tisch_licht_backlight",
            "state": "on",
            "attributes": {
              "supported_color_modes": [
                "hs"
              ],
              "color_mode": "hs",
              "brightness": null,
              "hs_color": null,
              "rgb_color": null,
              "xy_color": null,
              "friendly_name": "Tisch Licht Backlight",
              "supported_features": 0
            },
            "last_changed": "2024-12-23T12:40:04.755022+00:00",
            "last_reported": "2024-12-23T12:40:04.755022+00:00",
            "last_updated": "2024-12-23T12:40:04.755022+00:00"
          }
        },
        {
          "disabled": false,
          "disabled_by": null,
          "entity_category": "config",
          "device_class": null,
          "original_device_class": null,
          "icon": null,
          "unit_of_measurement": null,
          "state": {
            "entity_id": "select.tisch_licht_scene",
            "state": "unknown",
            "attributes": {
              "options": [
                "WW 100%",
                "WW 50%",
                "WW 1%",
                "WN 100%",
                "WN 50%",
                "WN 1%",
                "CW 100%",
                "CW 50%",
                "CW 1%",
                "NW 100%",
                "NW 50%",
                "NW 1%",
                "RGB RED 100%",
                "RGB RED 50%",
                "RGB RED 1%",
                "WW+RED 100%",
                "WW+RED 50%",
                "WW+RED 1%"
              ],
              "icon": "mdi:palette",
              "friendly_name": "Tisch Licht Scene"
            },
            "last_changed": "2024-12-23T12:51:48.016552+00:00",
            "last_reported": "2024-12-23T12:51:48.016552+00:00",
            "last_updated": "2024-12-23T12:51:48.016552+00:00"
          }
        },
        {
          "disabled": false,
          "disabled_by": null,
          "entity_category": "config",
          "device_class": null,
          "original_device_class": null,
          "icon": null,
          "unit_of_measurement": "min",
          "state": {
            "entity_id": "number.tisch_licht_timer",
            "state": "0.0",
            "attributes": {
              "min": 0.0,
              "max": 1440.0,
              "step": 1.0,
              "mode": "auto",
              "unit_of_measurement": "min",
              "friendly_name": "Tisch Licht Timer"
            },
            "last_changed": "2024-12-23T12:40:04.756267+00:00",
            "last_reported": "2024-12-23T12:40:04.756267+00:00",
            "last_updated": "2024-12-23T12:40:04.756267+00:00"
          }
        }
      ]
    }
  }
}

Product ID
mqhdyyri23fguocm
Product Name
Smart+PlaBL60x60B
DPS information
"dps": {
    "20": true,
    "21": "scene",
    "22": 1000,
    "23": 0,
    "24": "000003e803e8",
    "26": 0,
    "28": "",
    "30": "AAEAdwUBBgAAAAAAAAABBh4AAAAAFBkBCQAAAAAAZGQBFAAAAAAAUDIBFx4AAAAAAAA=",
    "31": "AAA=",
    "32": "AAA=",
    "36": "AAABAQIODgAAyAAAAAA=",
    "41": false,
    "51": "AAUAAAPoA+gD6AAA"
},

Information about how the device functions
Hi I have 2 of these Ledvance Ceeling Lights with Backlight and some issue with setting up the tuya_local device.

This is the device:
https://www.ledvance.com/consumer/products/smart-home/smart-luminaires/smart-indoor-luminaires/smart-panel-luminaires-with-wifi-technology/panel-luminaires-with-frame--backlight-and-wifi-technology/smart-panel-with-main-and-backlight-with-wifi-technology-tw-rgb-and-dimmable-c204214
It has 2 light modes which can be enabled differently (main and backlight).
I have already the config to set the color and brightness of both the main and the backlight (see config at the bottom).
My issue is in the Ledvance App I can enable/disable both lights individually (see screenshot below).

From monitoring the DP changes I found out that it's changed in the DPS51 on the
e.g.
AAUAAAPoA+gD6AAA = main WW brightness 100%, Backlight brightness 100%,  Main Light = on, Backlight = off
AAcAAAPoA+gD6AAA  = main WW brightness 100%, Backlight brightness100%,   Main Light = on, Backlight = on
AAYAAAPoA+gD6AAA  = main WW brightness 100%, Backlight brightness100%,   Main Light = off, Backlight = on

So the 3rd char defines which light is on/off (besides the main switch at DPS20)
If both lights are disabled it sets DPS20 = false
How can I configure the Device so that i can change the 3rd Char of the DPS51 string accordingly?
Is there any information somewhere how the DPS51 is configured?
I only found specific values by monitoring and set them through scene.
This is currently also the only way i can switch on/off the different light states through home assistant.
My current device config file:
ledvance_ceiling_light.zip
Additional Question:
I have currently installed the 1.0.4 firmware on both lights (shipped with this version)
The ledvance App prompts that an update is possible to 1.0.6,
Does Anyone know if the device can be controlled afterwards as it is possible now?
Or if is there some changelog for these Ledvance devices somewhere?
I don't want to lose my current solution only because i updated to the latest firmware.
edit: added the full_poll

You are definitely misunderstanding masks if you are expecting to get a U and c out of a 1 bit mask.
Try mask: "000200000000000000000000", type: base64, and comparing dps_val of 1 and 0 in the mapping.

The issue is that I have 3 states on the third character of that string on DP51.
Its not an boolean.
c = main on, backlight on
Y = main off, backlight on
U = main on, backlight off
for main off, backlight off the dp21 is set to false.
Is there any information about this base64 encoding of these DP values?
I just have made the changes in the Ledvance application and looked what value has been changed and try to do the same with tuya-local.

Sometimes the QueryThingsDataModel result contains a detailed explanation, usually in Chinese, to describe the encoding of complex DP values.  The "main" light here is a single bit, but of course it is in encodes to a different character when another bit within the same 6-bit grouping that corresponds to a base64 character is changed.

I have tried your suggestion and it worked and i can now enable/disable the backlight seperatly.
Do you have an idea what i can try to disable/enable the main light seperatly?
I guess the main problem is that if both main/backlight are off the DP21 = false
and if one of the lights is on the DP51 value is changed at the mentioned position.
I still have problems to understand how i can figure out the mask myself.
I try to understand what the mask is doing but i am not familar with base64 and bitwise operations.
Maybe you could help me with that.
I tried to decode the string like this to get a better understanding
values = {
"main on, backlight on": 'AAcAAAPoA+gD6AAA',
"main off, backlight on": 'AAUAAAPoA+gD6AAA',
"main on, backlight off": 'AAYAAAPoA+gD6AAA',
"test" : 'AAYA'
}

for value in values:
    base64 = values[value]
    print(f'state {value}: {base64}')
    binary_data = b64decode(base64)
    print(f"Binary data: {binary_data}")

    print(f"Equivalent bits:")
    for byte in binary_data:
        print(format(byte, '08b'), end=" ")
    print('\n')

the output is
state main on, backlight on: AAcAAAPoA+gD6AAA
Binary data: b'\x00\x07\x00\x00\x03\xe8\x03\xe8\x03\xe8\x00\x00'
Equivalent bits:
00000000 00000111 00000000 00000000 00000011 11101000 00000011 11101000 00000011 11101000 00000000 00000000

state main off, backlight on: AAUAAAPoA+gD6AAA
Binary data: b'\x00\x05\x00\x00\x03\xe8\x03\xe8\x03\xe8\x00\x00'
Equivalent bits:
00000000 00000101 00000000 00000000 00000011 11101000 00000011 11101000 00000011 11101000 00000000 00000000

state main on, backlight off: AAYAAAPoA+gD6AAA
Binary data: b'\x00\x06\x00\x00\x03\xe8\x03\xe8\x03\xe8\x00\x00'
Equivalent bits:
00000000 00000110 00000000 00000000 00000011 11101000 00000011 11101000 00000011 11101000 00000000 00000000

state test: AAYA
Binary data: b'\x00\x06\x00'
Equivalent bits:
00000000 00000110 00000000

So how does the mask: "000200000000000000000000" correspond that if 3rd char swtiches from c => U its true/false?
I have also the Problem that when i change the backlight color and turn it off/on the displayed backlight color in Home Assistant changed back to the default red. But the actual color is still the one which i have set before but isn't displayed in Home Assistant.
So i guess the backlight color must also be set in DP51 and not DP24 alone.
I see the following in the log when i change the color
2024-12-30 17:48:41.648 DEBUG (MainThread) [custom_components.tuya_local.device] Light sending dps update:
{"24": "011200fa03e8"}
2024-12-30 17:48:41.760 DEBUG (MainThread) [custom_components.tuya_local.device] Light received
{"51": "AAcBEgD6A+gD6AAA",


Sort params are hard to generalize

Description
Let's say you have a bunch of indices that all need pagination and sorting.
You could try to use generic structs + serdes flatten and then write a sub function that does all the sort + page query params.
Problem is you need to pass a &[&str] to the sort param. So if you have some kind of sort: Vec<String> then you have to first do sort.iter().map(|v|v.as_ref()).collect(). But this a Vec<&str>. Meaning this has to live for as long as the query exists, thus you can't do something like
fn handle_basics(params: &BaseParams, query: &mut SearchQuery) {
 let c: Vec<_> = a.iter().map(|v|v.as_str()).collect();
 b.sort = Some(&c); // needs &[&str]
 // now c would get leaked, creating a lifetime error, c's Vec has to outlive this..
}
fn handle_search(query: BaseParam<Entity>) {
let mut query =...
handle_basics(&params, &mut query);
[..]

Basic example
see above
Other
I'm not sure what the best approach is here. Only solution would be to let SeachQuery own the sort Vec. (sort: Vec<&str>)
Maybe also something like impl Iterator<T> where T: AsRef<str>.

Hey @0xpr03, indeed it's not the best usage :/ Adding an implementation impl Iterator<T> where T: AsRef<str>. is a good option for me to fix this


[FEAT]: Send out notifications when credential is generated

What is the feature request for?
Registry Core
What problem/inconvenience (if any) will this feature solve?
Registry should be able to send out notifications even when the credential is created or updated.
Describe the feature clearly.
Current version of Registry sends notifications only when the actor is invited to the system. There is no notification that can be sent if the credential is issued or credential is updated. This feature should enable that functionality to send out a notification to actor on the operations of create update of credentials

[x] Get template from the Schema. If not present, the get the default template
[x] Formulate a message that needs to sent to actor
[x] Send out a notification using APIs
[x] Configure a way that notification can be sent via messaging queue based on configuration
[x] Tests
[ ] Documentation

@varadeth Can you share below details if we have thought about this?

Can you share the notificate sample template.
Also does this include notification when claim has been raised or approved?
where can each issuer need to setup the configs for the SMS, tokens etc? Have we thought of this UI?

Documentation is also added


fix(ci): rename package.json scripts

Rename publish and package to vsce:publish and vsce/package to prevent trigger that script when semantic release run publish script.

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

npm package (@latest dist-tag)
Visual Studio Marketplace
GitHub release

Your semantic-release bot :package::rocket:


Allow basic auth to be configured on the upstream

When forwarding the request to an upstream, it is possible that this upstream has a required authorization header. The proxy currently has no way of setting the basic auth or any other authorization header.
Description
Adds an option to set the upstream authorization header
Motivation and Context
The upstream has a hard requirement (Apache Karaf) on a user and couldn't disable this user. We needed to set the Authorization header, eg Basic Auth. I wanted to make it configurable so that also Bearer or any other form is allowed as it is plain text. Use on your own risk.
How Has This Been Tested?
We're using this in production now as a fork and it works like magic
Checklist:

[X] My change requires a change to the documentation or CHANGELOG.
[X] I have updated the documentation/CHANGELOG accordingly.
[X] I have created a feature (non-master) branch for my PR.

Wrong feature branch - I'll clean it up and reopen


thanks for your work, keep it up!

thanks for your work, keep it up!
ready to support with a donation
It would also be great to have such functions

Viewing archive cards
Ability to collapse columns
write subtasks

[ ]
- [ ]

ability to organize tags #type/done
ability to save tags in the filter after restarting the application

Yes, the ability to add and render subtasks would be a great addition. Hope it gets added.


Fix spooled temporary file exceptions on file upload

Reverted implementation of SpooledTemporaryFile to prior behaviour due to bug as described in https://bugs.python.org/issue26175
Resolves: #1344

HI @davidism - I made an attempt to revert back to the previous default_stream_factory behaviour without SpooledTemporaryFile.

I amended the test_large_file test to make sure the returned file object from the default_stream_factory the abstract attributes exits.
I also, added a test_small_file test for when the data's length is below the max_size for when an in-memory buffer file object would be returned

Hi @davidism
The amendments to the unit tests look to be failing on python 2.7 :frowning:
Can these particular tests be skipped when executed in a py2 environ or should I investigate further?

Closing this in favor of the other solution discussed in #1344.


Update pybind11 to 2.10.1 and rebuild Docker images.

Retry https://github.com/iree-org/iree/pull/11155, after incorporating feedback.
Pybind 2.10.1 includes support for Python 3.11.

Seeing some very strange errors on presubmits. Might be worth rebuilding the Docker images without any changes to the Dockerfiles to see if the pybind changes are at fault. Unfortunately, rebuilding the images takes several hours :/

Closing in favor of https://github.com/iree-org/iree/pull/11728


submission/tristankindig - Client/Server Distinction

The Process file indicates that branches should be broken down into client and server sub-branches. However, the Spec file doesn't mention any breakdown between client-side and server-side code. The spec should be more specific about the functional expectations of the client-side and the server-side.

Great point, thank you. I've adjusted the specifications so that there is a single branch.


Deploy Argo as part of the platform

This would allow us to show CI/CD integration as well:  bring up the platform, show the console, show the Argo UI
Argo could then help manage deployment of apps into the platform too.
"aws ref platform with full GitOps support for app + infra" - @prasek

Another option here could be Flux as that it what is being evangelized by AWS in their paris distro.

We could consider doing this in a separate dedicated reference platform, instead of only as part of platform-ref-aws.

This is sort of.a flipside approach from what Viktor did that I took with CP and ArgoCD. It's a shell script that installs argo cd in a cluster, that then installs uxp, a config pkg equivalent, a sample XR/XRC. and Gatekeeper.

I think deploying Argo/Flux or GitOps is better served in a specific reference platform for that.  For example https://marketplace.upbound.io/configurations/devops-toolkit/dot-gitops/, or other GitOps focused reference platform that may be created in the future 😊


Show proposal links in metadata box

fixed ipfs link on https://github.com/nance-eth/nance-interface/commit/14b11067d41375ed8f49f50f9e9652d3f6321b80
it will display Discussion, Snapshot and IPFS link if they are not empty.


Only log warnings and errors

We don't want Debug logging by default since it prints PII and stuff that is not needed or dangerous in production.
Only log warnings and errors for the time being. Next step is to make this more configurable and document that.

👍


Update parser

I should update the parser as the old one is VERY buggy and generally horrible

I'm tired, complete this issue later (maybe tomorrow)


vstest.console is missing debug symbols

I tried building an SDK from the current master branch and running it through check-debug-symbols:
error: missing .debug_info section in  dotnet/sdk/5.0.100/vstest.console
error: missing .debug_abbrev section dotnet/sdk/5.0.100/vstest.console
error: missing FILE symbols in dotnet/sdk/5.0.100/vstest.console

Some other info:
$ file dotnet/sdk/5.0.100/vstest.console
dotnet/sdk/5.0.100/vstest.console: ELF 64-bit LSB shared object, x86-64, version 1 (GNU/Linux), dynamically linked (uses shared libs), for GNU/Linux 2.6.32, BuildID[sha1]=23473f4299002b6bf3aad7044f3ad355bd25191d, not stripped
$ readelf --section-headers dotnet/sdk/5.0.100/vstest.console | grep -E 'debug|gnu'
  [ 3] .note.gnu.build-i NOTE<PHONE_NUMBER>0002ac  000002ac
  [ 4] .gnu.hash         GNU_HASH<PHONE_NUMBER>0002d0  000002d0
  [ 7] .gnu.version      VERSYM<PHONE_NUMBER>0020b8  000020b8
  [ 8] .gnu.version_r    VERNEED<PHONE_NUMBER>002210  00002210
  [29] .gnu_debuglink    PROGBITS<PHONE_NUMBER>000000  000214f7

It's not stripped (?) and has a .gnu_debuglink section (which is supposed to point to a file that has the debug information) but doesn't actually contain debug information sections (.debug_info and .debug_abbrev).
What created this file? Perhaps it was pre-processed by the build system? I am going to dig further into this as soon as I find some time.

cc @tmds

This looks like an apphost... first because of the files near it that seem like the "rest" of the app:
vstest.console
vstest.console.deps.json
vstest.console.dll
vstest.console.dll.config
vstest.console.runtimeconfig.json

and then it does have the string apphost in it (but not sure why this string is there, other than it being the original name of the template binary file):
#> strings sdk/sdk/5.0.100/vstest.console | grep apphost
  - %s&apphost_version=%s
apphost
apphost.dbg

The Microsoft SDK doesn't have a vstest.console host... I think we ended up with one because of this patch:
https://github.com/dotnet/source-build/blob/8d3666b97b0ec8e228e7c578cdac1d210fadb994/patches/vstest/0006-build-for-.NET-5.patch#L200-L206
In 3.0 we started generating an apphost by default, so I think the TFM change triggers that. I believe we can add <UseAppHost>false</UseAppHost> to that patch to get rid of it. https://github.com/dotnet/core/issues/3686
The apphost template binary most likely comes from the tooling/prebuilt SDK (.dotnet/packs/Microsoft.NETCore.App.Host.linux-x64), so I think we need to get rid of it for clean source-build.
(If we actually need to create an apphost in some other situation, I think we should be able to force a project to use the apphost pack we build in dotnet/runtime rather than the one in the tooling SDK. I don't know offhand how to do that though, and it isn't the right direction in this case anyway.)

Done in https://github.com/dotnet/source-build/pull/1875, thanks @tmds!
(The "fixes #..." link doesn't fire because release/3.1 is still our default branch rather than master. 😄)


Notebook cannot load user site packages correctly after updated to 2022.2.101

Applies To

[X] Notebooks (.ipynb files)
[ ] Interactive Window and/or Cell Scripts (.py files with #%% markers)

What happened?
My notebooks cannot load user site packages after the extension updated to 2022.2.101
In notebook, following code print 'False'.
import site
print(site.ENABLE_USER_SITE)

Reverting the Jupyter extension to 2022.1 can solve this problem
I'm using raw Python on remote CentOS 7.9 machine, without any virtual env
VS Code Version
Version: 1.65.0 Commit: b5205cc8eb4fbaa726835538cd82372cc0222d43 Date: 2022-03-02T11:12:36.248Z Electron: 13.5.2 Chromium: 91.0.4472.164 Node.js: 14.16.0 V8: 9.1.269.39-electron.0 OS: Linux x64 5.13.0-28-generic snap
Jupyter Extension Version
2022.2.102
Jupyter logs
Visual Studio Code (1.65.0, ssh-remote, desktop)
Jupyter Extension Version: 2022.2.1020642448.
Python Extension Version: 2022.2.1924087327.
User belongs to experiment group 'jupyterTest'
User belongs to experiment group 'jupyterEnhancedDataViewer'
Error 12:10:29: Exception while attempting zmq : Error: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by /home/xhtang/.vscode-server/extensions/ms-toolsai.jupyter-2022.2.1020642448/out/client/node_modules/zeromq/prebuilds/linux-x64/node.napi.glibc.node)
    at Object.Module._extensions..node (internal/modules/cjs/loader.js:1122:18)
    at Module.load (internal/modules/cjs/loader.js:928:32)
    at Function.Module._load (internal/modules/cjs/loader.js:769:14)
    at Function.n._load (/home/xhtang/.vscode-server/bin/b5205cc8eb4fbaa726835538cd82372cc0222d43/out/vs/workbench/api/node/extensionHostProcess.js:104:32148)
    at Function.S._load (/home/xhtang/.vscode-server/bin/b5205cc8eb4fbaa726835538cd82372cc0222d43/out/vs/workbench/api/node/extensionHostProcess.js:104:28737)
    at Function.g._load (/home/xhtang/.vscode-server/bin/b5205cc8eb4fbaa726835538cd82372cc0222d43/out/vs/workbench/api/node/extensionHostProcess.js:99:60372)
    at Module.require (internal/modules/cjs/loader.js:952:19)
    at require (internal/modules/cjs/helpers.js:88:18)
    at load (/home/xhtang/.vscode-server/extensions/ms-toolsai.jupyter-2022.2.1020642448/out/client/node_modules/node-gyp-build/index.js:1:543)
    at Object.<anonymous> (/home/xhtang/.vscode-server/extensions/ms-toolsai.jupyter-2022.2.1020642448/out/client/node_modules/zeromq/lib/native.js:1:136)
    at Module._compile (internal/modules/cjs/loader.js:1063:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10)
    at Module.load (internal/modules/cjs/loader.js:928:32)
    at Function.Module._load (internal/modules/cjs/loader.js:769:14)
    at Function.n._load (/home/xhtang/.vscode-server/bin/b5205cc8eb4fbaa726835538cd82372cc0222d43/out/vs/workbench/api/node/extensionHostProcess.js:104:32148)
    at Function.S._load (/home/xhtang/.vscode-server/bin/b5205cc8eb4fbaa726835538cd82372cc0222d43/out/vs/workbench/api/node/extensionHostProcess.js:104:28737)
    at Function.g._load (/home/xhtang/.vscode-server/bin/b5205cc8eb4fbaa726835538cd82372cc0222d43/out/vs/workbench/api/node/extensionHostProcess.js:99:60372)
    at Module.require (internal/modules/cjs/loader.js:952:19)
    at require (internal/modules/cjs/helpers.js:88:18)
    at Object.<anonymous> (/home/xhtang/.vscode-server/extensions/ms-toolsai.jupyter-2022.2.1020642448/out/client/node_modules/zeromq/lib/index.js:1:82)
    at Module._compile (internal/modules/cjs/loader.js:1063:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10)
    at Module.load (internal/modules/cjs/loader.js:928:32)
    at Function.Module._load (internal/modules/cjs/loader.js:769:14)
    at Function.n._load (/home/xhtang/.vscode-server/bin/b5205cc8eb4fbaa726835538cd82372cc0222d43/out/vs/workbench/api/node/extensionHostProcess.js:104:32148)
    at Function.S._load (/home/xhtang/.vscode-server/bin/b5205cc8eb4fbaa726835538cd82372cc0222d43/out/vs/workbench/api/node/extensionHostProcess.js:104:28737)
    at Function.g._load (/home/xhtang/.vscode-server/bin/b5205cc8eb4fbaa726835538cd82372cc0222d43/out/vs/workbench/api/node/extensionHostProcess.js:99:60372)
    at Module.require (internal/modules/cjs/loader.js:952:19)
    at require (internal/modules/cjs/helpers.js:88:18)
    at Object.92747 (/home/xhtang/.vscode-server/extensions/ms-toolsai.jupyter-2022.2.1020642448/out/client/extension.js:2:3878485)
    at __webpack_require__ (/home/xhtang/.vscode-server/extensions/ms-toolsai.jupyter-2022.2.1020642448/out/client/extension.js:2:4545798)
    at d.zmqSupported (/home/xhtang/.vscode-server/extensions/ms-toolsai.jupyter-2022.2.1020642448/out/client/extension.js:2:973026)
    at d.isSupportedForLocalLaunch (/home/xhtang/.vscode-server/extensions/ms-toolsai.jupyter-2022.2.1020642448/out/client/extension.js:2:972817)
    at d.get isSupported [as isSupported] (/home/xhtang/.vscode-server/extensions/ms-toolsai.jupyter-2022.2.1020642448/out/client/extension.js:2:972727)
    at t.registerTypes (/home/xhtang/.vscode-server/extensions/ms-toolsai.jupyter-2022.2.1020642448/out/client/extension.js:2:983912)
    at /home/xhtang/.vscode-server/extensions/ms-toolsai.jupyter-2022.2.1020642448/out/client/extension.js:2:1070474
    at /home/xhtang/.vscode-server/extensions/ms-toolsai.jupyter-2022.2.1020642448/out/client/extension.js:2:4547373
    at e.activate (/home/xhtang/.vscode-server/extensions/ms-toolsai.jupyter-2022.2.1020642448/out/client/extension.js:2:4547050)
Info 12:10:29: Old kernelspecs (created by Jupyter extension) stored in directory /home/xhtang/.local/share/jupyter/kernels/__old_vscode_kernelspecs
Info 12:10:29: Preferred kernel connection found in cache .jvsc74a57bd05b3ded1ccb95c1d9bd405e7b823d9e85424cde40fbb5985eb47e999ef50e15b4./bin/python3.8./bin/python3.8.-m#ipykernel_launcher
Info 12:10:29: PreferredConnection: .jvsc74a57bd05b3ded1ccb95c1d9bd405e7b823d9e85424cde40fbb5985eb47e999ef50e15b4./bin/python3.8./bin/python3.8.-m#ipykernel_launcher found for NotebookDocument: untitled:Untitled-1.ipynb?jupyter-notebook
Info 12:10:29: Early registration of controller for Kernel connection .jvsc74a57bd05b3ded1ccb95c1d9bd405e7b823d9e85424cde40fbb5985eb47e999ef50e15b4./bin/python3.8./bin/python3.8.-m#ipykernel_launcher
Info 12:10:29: TargetController found ID: .jvsc74a57bd05b3ded1ccb95c1d9bd405e7b823d9e85424cde40fbb5985eb47e999ef50e15b4./bin/python3.8./bin/python3.8.-m#ipykernel_launcher for document untitled:Untitled-1.ipynb?jupyter-notebook
Info 12:10:29: Setting controller affinity for untitled:Untitled-1.ipynb?jupyter-notebook .jvsc74a57bd05b3ded1ccb95c1d9bd405e7b823d9e85424cde40fbb5985eb47e999ef50e15b4./bin/python3.8./bin/python3.8.-m#ipykernel_launcher
Info 12:10:29: Experiment status for python is {"enabled":true,"optInto":[],"optOutFrom":[]}
Info 12:10:29: Creating controller for jupyter-notebook with interpreter /bin/python3.8
Info 12:10:29: Getting activation commands for /bin/python3.8 are not cached. May take a while.
Info 12:10:29: Getting activation commands for /usr/bin/python3.8 are not cached. May take a while.
Info 12:10:29: Interrupt requested & no kernel.
Info 12:10:29: Setting setActiveController for untitled:Untitled-1.ipynb?jupyter-notebook
Info 12:10:29: KernelProvider switched kernel to id = .jvsc74a57bd05b3ded1ccb95c1d9bd405e7b823d9e85424cde40fbb5985eb47e999ef50e15b4./bin/python3.8./bin/python3.8.-m#ipykernel_launcher
Info 12:10:29: Starting Notebook in kernel.ts id = .jvsc74a57bd05b3ded1ccb95c1d9bd405e7b823d9e85424cde40fbb5985eb47e999ef50e15b4./bin/python3.8./bin/python3.8.-m#ipykernel_launcher
Info 12:10:29: Checking for server existence.
Info 12:10:29: Checking for server usability.
Info 12:10:29: Registering dummy command feature
Info 12:10:30: Process Execution: > /bin/python3.8 -m pip list
> /bin/python3.8 -m pip list
Info 12:10:30: Process Execution: > /usr/bin/python3.8 -c "import jupyter"
> /usr/bin/python3.8 -c "import jupyter"
Info 12:10:30: Process Execution: > /usr/bin/python3.8 -c "import notebook"
> /usr/bin/python3.8 -c "import notebook"
Info 12:10:30: Process Execution: > /usr/bin/python3.8 -m jupyter kernelspec --version
> /usr/bin/python3.8 -m jupyter kernelspec --version
Info 12:10:30: Starting notebook server.
Info 12:10:30: Connecting to server
Info 12:10:30: Launching server
Info 12:10:30: Starting Notebook
Info 12:10:31: Generating custom default config at /tmp/b00dafac-6062-4c9c-a0a1-5d0d7ab29989/jupyter_notebook_config.py
Info 12:10:31: Starting Jupyter Notebook
Starting Jupyter from /usr/bin/python3.8 with command line --no-browser --notebook-dir="/home/xhtang/crypto-log" --config=/tmp/b00dafac-6062-4c9c-a0a1-5d0d7ab29989/jupyter_notebook_config.py --NotebookApp.iopub_data_rate_limit=10000000000.0
Info 12:10:31: Creating daemon pool for /usr/bin/python3.8 with env variables count 42
Info 12:10:31: Process Execution: > /usr/bin/python3.8 -m vscode_datascience_helpers.daemon --daemon-module=vscode_datascience_helpers.jupyter_daemon -v --ppid 134272
> /usr/bin/python3.8 -m vscode_datascience_helpers.daemon --daemon-module=vscode_datascience_helpers.jupyter_daemon -v --ppid 134272
Info 12:10:31: Process Execution: > /usr/bin/python3.8 -m vscode_datascience_helpers.daemon --daemon-module=vscode_datascience_helpers.jupyter_daemon -v --ppid 134272
> /usr/bin/python3.8 -m vscode_datascience_helpers.daemon --daemon-module=vscode_datascience_helpers.jupyter_daemon -v --ppid 134272
Info 12:10:31: Process Execution: > /usr/bin/python3.8 -m vscode_datascience_helpers.daemon --daemon-module=vscode_datascience_helpers.jupyter_daemon -v --ppid 134272
> /usr/bin/python3.8 -m vscode_datascience_helpers.daemon --daemon-module=vscode_datascience_helpers.jupyter_daemon -v --ppid 134272
Info 12:10:31: Process Execution: > /usr/bin/python3.8 (daemon) -m jupyter notebook --no-browser --notebook-dir="/home/xhtang/crypto-log" --config=/tmp/b00dafac-6062-4c9c-a0a1-5d0d7ab29989/jupyter_notebook_config.py --NotebookApp.iopub_data_rate_limit=10000000000.0
> /usr/bin/python3.8 (daemon) -m jupyter notebook --no-browser --notebook-dir="/home/xhtang/crypto-log" --config=/tmp/b00dafac-6062-4c9c-a0a1-5d0d7ab29989/jupyter_notebook_config.py --NotebookApp.iopub_data_rate_limit=10000000000.0
Info 12:10:31: Waiting for Jupyter Notebook
/usr/local/lib/python3.8/site-packages/traitlets/traitlets.py:2196: FutureWarning: Supporting extra quotes around Unicode is deprecated in traitlets 5.0. Use '/home/xhtang/crypto-log' instead of '"/home/xhtang/crypto-log"' – or use CUnicode.
  warn(
Info 12:10:31: /usr/local/lib/python3.8/site-packages/traitlets/traitlets.py:2196: FutureWarning: Supporting extra quotes around Unicode is deprecated in traitlets 5.0. Use '/home/xhtang/crypto-log' instead of '"/home/xhtang/crypto-log"' – or use CUnicode.
  warn(

[I 12:10:31.692 NotebookApp] The port 8888 is already in use, trying another port.
Info 12:10:31: /usr/local/lib/python3.8/site-packages/traitlets/traitlets.py:2196: FutureWarning: Supporting extra quotes around Unicode is deprecated in traitlets 5.0. Use '/home/xhtang/crypto-log' instead of '"/home/xhtang/crypto-log"' – or use CUnicode.
  warn(
[I 12:10:31.692 NotebookApp] The port 8888 is already in use, trying another port.

[I 12:10:31.694 NotebookApp] Serving notebooks from local directory: /home/xhtang/crypto-log
Info 12:10:31: /usr/local/lib/python3.8/site-packages/traitlets/traitlets.py:2196: FutureWarning: Supporting extra quotes around Unicode is deprecated in traitlets 5.0. Use '/home/xhtang/crypto-log' instead of '"/home/xhtang/crypto-log"' – or use CUnicode.
  warn(
[I 12:10:31.692 NotebookApp] The port 8888 is already in use, trying another port.
[I 12:10:31.694 NotebookApp] Serving notebooks from local directory: /home/xhtang/crypto-log

[I 12:10:31.694 NotebookApp] Jupyter Notebook 6.3.0 is running at:
Info 12:10:31: /usr/local/lib/python3.8/site-packages/traitlets/traitlets.py:2196: FutureWarning: Supporting extra quotes around Unicode is deprecated in traitlets 5.0. Use '/home/xhtang/crypto-log' instead of '"/home/xhtang/crypto-log"' – or use CUnicode.
  warn(
[I 12:10:31.692 NotebookApp] The port 8888 is already in use, trying another port.
[I 12:10:31.694 NotebookApp] Serving notebooks from local directory: /home/xhtang/crypto-log
[I 12:10:31.694 NotebookApp] Jupyter Notebook 6.3.0 is running at:

[I 12:10:31.694 NotebookApp] http://localhost:8889/?token=e30f0a8d076ac90951ee1b9ba730c2d22126dd5117c81f98
Info 12:10:31: /usr/local/lib/python3.8/site-packages/traitlets/traitlets.py:2196: FutureWarning: Supporting extra quotes around Unicode is deprecated in traitlets 5.0. Use '/home/xhtang/crypto-log' instead of '"/home/xhtang/crypto-log"' – or use CUnicode.
  warn(
[I 12:10:31.692 NotebookApp] The port 8888 is already in use, trying another port.
[I 12:10:31.694 NotebookApp] Serving notebooks from local directory: /home/xhtang/crypto-log
[I 12:10:31.694 NotebookApp] Jupyter Notebook 6.3.0 is running at:
[I 12:10:31.694 NotebookApp] http://localhost:8889/?token=e30f0a8d076ac90951ee1b9ba730c2d22126dd5117c81f98

Info 12:10:31: Process Execution: > /usr/bin/python3.8 (daemon) ~/.vscode-server/extensions/ms-toolsai.jupyter-2022.2.1020642448/pythonFiles/vscode_datascience_helpers/getServerInfo.py
> /usr/bin/python3.8 (daemon) ~/.vscode-server/extensions/ms-toolsai.jupyter-2022.2.1020642448/pythonFiles/vscode_datascience_helpers/getServerInfo.py
[I 12:10:31.695 NotebookApp]  or http://<IP_ADDRESS>:8889/?token=e30f0a8d076ac90951ee1b9ba730c2d22126dd5117c81f98
Info 12:10:31: /usr/local/lib/python3.8/site-packages/traitlets/traitlets.py:2196: FutureWarning: Supporting extra quotes around Unicode is deprecated in traitlets 5.0. Use '/home/xhtang/crypto-log' instead of '"/home/xhtang/crypto-log"' – or use CUnicode.
  warn(
[I 12:10:31.692 NotebookApp] The port 8888 is already in use, trying another port.
[I 12:10:31.694 NotebookApp] Serving notebooks from local directory: /home/xhtang/crypto-log
[I 12:10:31.694 NotebookApp] Jupyter Notebook 6.3.0 is running at:
[I 12:10:31.694 NotebookApp] http://localhost:8889/?token=e30f0a8d076ac90951ee1b9ba730c2d22126dd5117c81f98
[I 12:10:31.695 NotebookApp]  or http://<IP_ADDRESS>:8889/?token=e30f0a8d076ac90951ee1b9ba730c2d22126dd5117c81f98

Info 12:10:31: Process Execution: > /usr/bin/python3.8 (daemon) ~/.vscode-server/extensions/ms-toolsai.jupyter-2022.2.1020642448/pythonFiles/vscode_datascience_helpers/getServerInfo.py
> /usr/bin/python3.8 (daemon) ~/.vscode-server/extensions/ms-toolsai.jupyter-2022.2.1020642448/pythonFiles/vscode_datascience_helpers/getServerInfo.py
[I 12:10:31.695 NotebookApp] Use Control-C to stop this server and shut down all kernels (twice to skip confirmation).
Info 12:10:31: /usr/local/lib/python3.8/site-packages/traitlets/traitlets.py:2196: FutureWarning: Supporting extra quotes around Unicode is deprecated in traitlets 5.0. Use '/home/xhtang/crypto-log' instead of '"/home/xhtang/crypto-log"' – or use CUnicode.
  warn(
[I 12:10:31.692 NotebookApp] The port 8888 is already in use, trying another port.
[I 12:10:31.694 NotebookApp] Serving notebooks from local directory: /home/xhtang/crypto-log
[I 12:10:31.694 NotebookApp] Jupyter Notebook 6.3.0 is running at:
[I 12:10:31.694 NotebookApp] http://localhost:8889/?token=e30f0a8d076ac90951ee1b9ba730c2d22126dd5117c81f98
[I 12:10:31.695 NotebookApp]  or http://<IP_ADDRESS>:8889/?token=e30f0a8d076ac90951ee1b9ba730c2d22126dd5117c81f98
[I 12:10:31.695 NotebookApp] Use Control-C to stop this server and shut down all kernels (twice to skip confirmation).

[C 12:10:31.697 NotebookApp]

    To access the notebook, open this file in a browser:
        file:///home/xhtang/.local/share/jupyter/runtime/nbserver-134543-open.html
    Or copy and paste one of these URLs:
        http://localhost:8889/?token=e30f0a8d076ac90951ee1b9ba730c2d22126dd5117c81f98
     or http://<IP_ADDRESS>:8889/?token=e30f0a8d076ac90951ee1b9ba730c2d22126dd5117c81f98
Info 12:10:31: /usr/local/lib/python3.8/site-packages/traitlets/traitlets.py:2196: FutureWarning: Supporting extra quotes around Unicode is deprecated in traitlets 5.0. Use '/home/xhtang/crypto-log' instead of '"/home/xhtang/crypto-log"' – or use CUnicode.
  warn(
[I 12:10:31.692 NotebookApp] The port 8888 is already in use, trying another port.
[I 12:10:31.694 NotebookApp] Serving notebooks from local directory: /home/xhtang/crypto-log
[I 12:10:31.694 NotebookApp] Jupyter Notebook 6.3.0 is running at:
[I 12:10:31.694 NotebookApp] http://localhost:8889/?token=e30f0a8d076ac90951ee1b9ba730c2d22126dd5117c81f98
[I 12:10:31.695 NotebookApp]  or http://<IP_ADDRESS>:8889/?token=e30f0a8d076ac90951ee1b9ba730c2d22126dd5117c81f98
[I 12:10:31.695 NotebookApp] Use Control-C to stop this server and shut down all kernels (twice to skip confirmation).
[C 12:10:31.697 NotebookApp]

    To access the notebook, open this file in a browser:
        file:///home/xhtang/.local/share/jupyter/runtime/nbserver-134543-open.html
    Or copy and paste one of these URLs:
        http://localhost:8889/?token=e30f0a8d076ac90951ee1b9ba730c2d22126dd5117c81f98
     or http://<IP_ADDRESS>:8889/?token=e30f0a8d076ac90951ee1b9ba730c2d22126dd5117c81f98

Info 12:10:31: Connecting to process server
Info 12:10:31: Connecting server kernel http://localhost:8889/
Info 12:10:31: Creating server with settings : {"baseUrl":"http://localhost:8889/","appUrl":"","wsUrl":"ws://localhost:8889/","token":"e30f0a8d076ac90951ee1b9ba730c2d22126dd5117c81f98","appendToken":true,"init":{"cache":"no-store","credentials":"same-origin"}}
Info 12:10:31: Connection complete server
Info 12:10:31: Server started.
[I 12:10:31.959 NotebookApp] Creating new notebook in
Info 12:10:31: Process Execution: > /usr/bin/python3.8 (daemon) ~/.vscode-server/extensions/ms-toolsai.jupyter-2022.2.1020642448/pythonFiles/vscode_datascience_helpers/getServerInfo.py
> /usr/bin/python3.8 (daemon) ~/.vscode-server/extensions/ms-toolsai.jupyter-2022.2.1020642448/pythonFiles/vscode_datascience_helpers/getServerInfo.py
Info 12:10:31: installMissingDependencies /bin/python3.8
Info 12:10:31: IPykernel found previously in this environment /bin/python3.8
Info 12:10:32: Process Execution: > /usr/bin/python3.8 (daemon) ~/.vscode-server/extensions/ms-toolsai.jupyter-2022.2.1020642448/pythonFiles/vscode_datascience_helpers/getServerInfo.py
> /usr/bin/python3.8 (daemon) ~/.vscode-server/extensions/ms-toolsai.jupyter-2022.2.1020642448/pythonFiles/vscode_datascience_helpers/getServerInfo.py
Info 12:10:32: Spec argv[0] updated from '/bin/python3.8' to '/bin/python3.8'
Warn 12:10:32: Falling back to Python Execution Service due to failure in daemon h [Error]: Failed to execute using the daemon, Traceback (most recent call last):
  File "/home/xhtang/.vscode-server/extensions/ms-toolsai.jupyter-2022.2.1020642448/pythonFiles/vscode_datascience_helpers/getServerInfo.py", line 13, in <module>
    for si in server_list:
  File "/usr/local/lib/python3.8/site-packages/notebook/notebookapp.py", line 2387, in list_running_servers
    with io.open(os.path.join(runtime_dir, file_name), encoding='utf-8') as f:
FileNotFoundError: [Errno 2] No such file or directory: '/home/xhtang/.local/share/jupyter/runtime/nbserver-97690.json'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/xhtang/.vscode-server/extensions/ms-toolsai.jupyter-2022.2.1020642448/pythonFiles/vscode_datascience_helpers/daemon/daemon_python.py", line 54, in _decorator
    return func(self, *args, **kwargs)
  File "/home/xhtang/.vscode-server/extensions/ms-toolsai.jupyter-2022.2.1020642448/pythonFiles/vscode_datascience_helpers/daemon/daemon_python.py", line 135, in m_exec_file
    return self._execute_and_capture_output(exec_file)
  File "/home/xhtang/.vscode-server/extensions/ms-toolsai.jupyter-2022.2.1020642448/pythonFiles/vscode_datascience_helpers/daemon/daemon_python.py", line 106, in _execute_and_capture_output
    func()
  File "/home/xhtang/.vscode-server/extensions/ms-toolsai.jupyter-2022.2.1020642448/pythonFiles/vscode_datascience_helpers/daemon/daemon_python.py", line 132, in exec_file
    runpy.run_path(file_name, globals())
  File "/usr/local/lib/python3.8/runpy.py", line 265, in run_path
    return _run_module_code(code, init_globals, run_name,
  File "/usr/local/lib/python3.8/runpy.py", line 97, in _run_module_code
    _run_code(code, mod_globals, init_globals,
  File "/usr/local/lib/python3.8/runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "/home/xhtang/.vscode-server/extensions/ms-toolsai.jupyter-2022.2.1020642448/pythonFiles/vscode_datascience_helpers/getServerInfo.py", line 38, in <module>
    builtins.print.write(result.stdout.decode(encoding))
AttributeError: 'builtin_function_or_method' object has no attribute 'write'

    at a.processResponse (/home/xhtang/.vscode-server/extensions/ms-toolsai.jupyter-2022.2.1020642448/out/client/extension.js:2:131513)
    at a.execFileWithDaemon (/home/xhtang/.vscode-server/extensions/ms-toolsai.jupyter-2022.2.1020642448/out/client/extension.js:2:131860)
    at a.exec (/home/xhtang/.vscode-server/extensions/ms-toolsai.jupyter-2022.2.1020642448/out/client/extension.js:2:128905)
    at d.wrapCall (/home/xhtang/.vscode-server/extensions/ms-toolsai.jupyter-2022.2.1020642448/out/client/extension.js:2:170884)
    at b.getRunningJupyterServers (/home/xhtang/.vscode-server/extensions/ms-toolsai.jupyter-2022.2.1020642448/out/client/extension.js:2:574419) {
  category: 'daemon'
}
Info 12:10:32: Process Execution: > /usr/bin/python3.8 ~/.vscode-server/extensions/ms-toolsai.jupyter-2022.2.1020642448/pythonFiles/vscode_datascience_helpers/getServerInfo.py
> /usr/bin/python3.8 ~/.vscode-server/extensions/ms-toolsai.jupyter-2022.2.1020642448/pythonFiles/vscode_datascience_helpers/getServerInfo.py
Info 12:10:32: Starting a new session for kernel id = .jvsc74a57bd05b3ded1ccb95c1d9bd405e7b823d9e85424cde40fbb5985eb47e999ef50e15b4./bin/python3.8./bin/python3.8.-m#ipykernel_launcher, name = python383jvsc74a57bd05b3ded1ccb95c1d9bd405e7b823d9e85424cde40fbb5985eb47e999ef50e15b4
[I 12:10:32.411 NotebookApp] Kernel started: 98dbdffa-651d-4e87-b027-33bcb8de0706, name: python383jvsc74a57bd05b3ded1ccb95c1d9bd405e7b823d9e85424cde40fbb5985eb47e999ef50e15b4
Info 12:10:32: Waiting for idle on (kernel): 98dbdffa-651d-4e87-b027-33bcb8de0706 -> unknown
[W 12:10:32.444 NotebookApp] delete /Untitled-1-jvsc-b1ffece1-b2a1-4a84-845e-83284af9ee92.ipynb
Info 12:10:32: Finished waiting for idle on (kernel): 98dbdffa-651d-4e87-b027-33bcb8de0706 -> idle
Info 12:10:32: Started session for kernel .jvsc74a57bd05b3ded1ccb95c1d9bd405e7b823d9e85424cde40fbb5985eb47e999ef50e15b4./bin/python3.8./bin/python3.8.-m#ipykernel_launcher
Info 12:10:32: Finished connecting kernel .jvsc74a57bd05b3ded1ccb95c1d9bd405e7b823d9e85424cde40fbb5985eb47e999ef50e15b4./bin/python3.8./bin/python3.8.-m#ipykernel_launcher
Info 12:10:32: Executing silently Code (idle) = import sys\nprint(sys.executable)
Info 12:10:33: Executing silently Code (completed) = import sys\nprint(sys.executable)
Info 12:10:33: Executing silently Code (idle) = import site\nsite.addsitedir(site.getusersitepackages())\n__vsc_ipynb_file__ = "Untitled-1.ipynb"\n%con
Info 12:10:33: Executing silently Code (completed) = import site\nsite.addsitedir(site.getusersitepackages())\n__vsc_ipynb_file__ = "Untitled-1.ipynb"\n%con
Info 12:10:33: Waiting for idle on (kernel): 98dbdffa-651d-4e87-b027-33bcb8de0706 -> idle
Info 12:10:33: Finished waiting for idle on (kernel): 98dbdffa-651d-4e87-b027-33bcb8de0706 -> idle
Info 12:10:37: Execute Cells request 0, 1
Info 12:10:37: Execute Cell 0 untitled:Untitled-1.ipynb?jupyter-notebook
Info 12:10:37: Execute Cell 1 untitled:Untitled-1.ipynb?jupyter-notebook
Info 12:10:38: Cell 0 executed with state Success
Info 12:10:38: Cell 1 executed with state Success
Info 12:10:41: Loading webview. View is notset
Info 12:10:41: Loading web view...
Info 12:10:41: Webview panel created.
Info 12:10:42: Web view react rendered
Info 12:10:42: Executing silently Code (idle) = # Query Jupyter server for the info about a dataframe\nimport json as _VSCODE_json\nimport builtins as
Info 12:10:42: Executing silently Code (idle) = # Query Jupyter server for the info about a dataframe\nimport json as _VSCODE_json\nimport builtins as
Info 12:10:42: Executing silently Code (completed) = # Query Jupyter server for the info about a dataframe\nimport json as _VSCODE_json\nimport builtins as
Info 12:10:42: Executing silently Code (idle) = import builtins\n_rwho_ls = %who_ls\nbuiltins.print(_VSCODE_getVariableTypes(_rwho_ls))
Info 12:10:42: Executing silently Code (completed) = # Query Jupyter server for the info about a dataframe\nimport json as _VSCODE_json\nimport builtins as
Info 12:10:42: Executing silently Code (idle) = import builtins\n_rwho_ls = %who_ls\nbuiltins.print(_VSCODE_getVariableTypes(_rwho_ls))
Info 12:10:42: Executing silently Code (completed) = import builtins\n_rwho_ls = %who_ls\nbuiltins.print(_VSCODE_getVariableTypes(_rwho_ls))
Info 12:10:42: Executing silently Code (completed) = import builtins\n_rwho_ls = %who_ls\nbuiltins.print(_VSCODE_getVariableTypes(_rwho_ls))
Info 12:10:43: Searching for token colors ...
Info 12:10:43: Attempting search for colors ...
Warn 12:10:43: Color theme Default Dark+ not found. Using default colors.
Info 12:10:43: Attempting search for colors ...
Warn 12:10:43: Color theme Default Dark+ not found. Using default colors.
Info 12:12:03: Searching for token colors ...
Info 12:12:03: Attempting search for colors ...
Warn 12:12:03: Color theme Default Dark+ not found. Using default colors.
Info 12:12:03: Attempting search for colors ...
Warn 12:12:03: Color theme Default Dark+ not found. Using default colors.

Coding Language and Runtime Version
Python 3.8.3
Language Extension Version (if applicable)
No response
Anaconda Version (if applicable)
No response
Running Jupyter locally or remotely?
Remote

thanks for filling this issue, im sorry your running into an issue.
this should work as were adding the site packages back when starting the kernel as follows
import site
site.addsitedir(site.getusersitepackages())

hence your site packages should load

please could you print the value for sys.path
also could you provide more information on where your site packages folder is and what's different from that path compared to the path listed in sys.path

The change introduced ensures packages in your environment (associated with the kernel) are given preference over other paths.ie packages in the site packages of your current environment is first searched for packages before looking else where globally

i think i know what's going on here, will upload a fix soon

Hi @DonJayamanne, I just found this issue is caused by earlier changes in 2022.2.101. You suggestions are still helpful
sys.path (discriminated by extension version)
['/home/xhtang/crypto-log', '/home/xhtang/.vscode-server/extensions/ms-toolsai.jupyter-2022.1.1301854968/pythonFiles', '/home/xhtang/.vscode-server/extensions/ms-toolsai.jupyter-2022.1.1301854968/pythonFiles/lib/python', '/usr/local/lib/python38.zip', '/usr/local/lib/python3.8', '/usr/local/lib/python3.8/lib-dynload', '', '/home/xhtang/.local/lib/python3.8/site-packages', '/usr/local/lib/python3.8/site-packages', '/usr/local/lib/python3.8/site-packages/pycurl-7.44.1-py3.8-linux-x86_64.egg', '/usr/local/lib/python3.8/site-packages/IPython/extensions', '/home/xhtang/.ipython']

['/home/xhtang/crypto-log', '/home/xhtang/.vscode-server/extensions/ms-toolsai.jupyter-2022.2.1020642448/pythonFiles', '/home/xhtang/.vscode-server/extensions/ms-toolsai.jupyter-2022.2.1020642448/pythonFiles/lib/python', '/usr/local/lib/python38.zip', '/usr/local/lib/python3.8', '/usr/local/lib/python3.8/lib-dynload', '', '/usr/local/lib/python3.8/site-packages', '/usr/local/lib/python3.8/site-packages/pycurl-7.44.1-py3.8-linux-x86_64.egg', '/usr/local/lib/python3.8/site-packages/IPython/extensions', '/home/xhtang/.ipython', '/home/xhtang/.local/lib/python3.8/site-packages']
False

Please confirm the kernel selected is for /usr/local/lib/python3.8
The difference now is that site packages will first be loaded from '/usr/local/lib/python3.8/site-packages', instead of /home/xhtang/.local/lib/python3.8/site-packages
This is correct, and expected.
This way we give preference to site packages in the environment you have selected.

Please could you provide details of the errors you are getting.
Please could you open the output panel and go into the Jupyter Server Console output and provide output from there

@OneMoreSecond I'll be submitting a fix and you should be able to test this by installing the pre-release version of the extension.
I'll let you know when it is ready to test.
Here's the place to switch to the pre-release version (click the button) & it will get the latest pre-release version

The first cell is the expected result (like raw Python or IPython), and the second cell is unexpected after update.

My output panel doesn't have Jupyter Server Console in the drop-down list. There is only "Jupyter" and I have pasted it above.

To discuss with the team

I think we should back out the change that changes the site packages paths
This was added as @rchiodo wasn't able to start a kernel on his machine as ipykernel was not being used from the environment, but used from the global site packages.

We addressed this by changing where packages are loaded, by first giving preference to packages in the environment.
However this is non-standard, regular python & ipython (Jupyter) don't work like this.
We can get kernel startup (ipykernel loading) to work as a result of this, but could break others.
On the flip site we could get ipykernel failures because we load from the environment instead of the usual place & users complain that it works in the terminal & jupyter (because the one in global site packages is correct)

FYI - Not saying that we shouldnt have addressed the issue Rich ran into, just giving some context (an actual bug), something that had to be fixed, and likely that users too were running into this same issue.
I think an alternative to the path mangling approach is:

Check where ipykernel is sourced from, & then check if there's an ipykernel in the environment as well
If startup fails, then attempt to use the approach of changing the paths & once the kernel has loaded, then change the PATHS yet again to ensure its as expected.

However this is non-standard, regular python & ipython (Jupyter) don't work like this.

I believe this is false. That's what I found in the original bug when debugging it: https://github.com/microsoft/vscode-jupyter/issues/8553
Jupyter was modifying the site packages list.

I believe this is false

oh, on thanks. need to look into this.
however based on user feedback, aren't we'd didn't from regular python and ipython. something to check .
ill dig into this when im back and see can discuss based on my findings
thanks rich

@OneMoreSecond
Please could you install the pre-release version of the Extension and let me know if this works as expected.
Just go into the extension panel and install the pre-release version see below.
Click the Switch to pre-release version

Once installed you should see the green badge indicating you are on pre-release

@DonJayamanne  I also have this problem with vs code insider and jupyter pre-release version.
BUT I can run jupyter notebook in terminal and vs code will auto forward port 8888, then I connect to this jupyter server in vs code by "specify the URL of an existing server".

Visual Studio Code - Insiders (1.65.0-insider, ssh-remote, desktop)
Jupyter Extension Version: 2022.3.1000652335.
Python Extension Version: 2022.2.1924087327.
User belongs to experiment group 'jupyterTestcf'
User belongs to experiment group 'jupyterEnhancedDataViewer'
Error 01:46:20: Exception while attempting zmq : Error: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by /home/user-name/.vscode-server-insiders/extensions/ms-toolsai.jupyter-2022.3.1000652335/out/client/node_modules/zeromq/prebuilds/linux-x64/node.napi.glibc.node)
    at Object.Module._extensions..node (internal/modules/cjs/loader.js:1122:18)
    at Module.load (internal/modules/cjs/loader.js:928:32)
    at Function.Module._load (internal/modules/cjs/loader.js:769:14)
    at Function.n._load (/home/user-name/.vscode-server-insiders/bin/8440b8f47231147823ba9696913d642e5f2d9d58/out/vs/workbench/api/node/extensionHostProcess.js:104:32148)
    at Function.S._load (/home/user-name/.vscode-server-insiders/bin/8440b8f47231147823ba9696913d642e5f2d9d58/out/vs/workbench/api/node/extensionHostProcess.js:104:28737)
    at Function.g._load (/home/user-name/.vscode-server-insiders/bin/8440b8f47231147823ba9696913d642e5f2d9d58/out/vs/workbench/api/node/extensionHostProcess.js:99:60372)
    at Module.require (internal/modules/cjs/loader.js:952:19)
    at require (internal/modules/cjs/helpers.js:88:18)
    at load (/home/user-name/.vscode-server-insiders/extensions/ms-toolsai.jupyter-2022.3.1000652335/out/client/node_modules/node-gyp-build/index.js:1:543)
    at Object.<anonymous> (/home/user-name/.vscode-server-insiders/extensions/ms-toolsai.jupyter-2022.3.1000652335/out/client/node_modules/zeromq/lib/native.js:1:136)
    at Module._compile (internal/modules/cjs/loader.js:1063:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10)
    at Module.load (internal/modules/cjs/loader.js:928:32)
    at Function.Module._load (internal/modules/cjs/loader.js:769:14)
    at Function.n._load (/home/user-name/.vscode-server-insiders/bin/8440b8f47231147823ba9696913d642e5f2d9d58/out/vs/workbench/api/node/extensionHostProcess.js:104:32148)
    at Function.S._load (/home/user-name/.vscode-server-insiders/bin/8440b8f47231147823ba9696913d642e5f2d9d58/out/vs/workbench/api/node/extensionHostProcess.js:104:28737)
    at Function.g._load (/home/user-name/.vscode-server-insiders/bin/8440b8f47231147823ba9696913d642e5f2d9d58/out/vs/workbench/api/node/extensionHostProcess.js:99:60372)
    at Module.require (internal/modules/cjs/loader.js:952:19)
    at require (internal/modules/cjs/helpers.js:88:18)
    at Object.<anonymous> (/home/user-name/.vscode-server-insiders/extensions/ms-toolsai.jupyter-2022.3.1000652335/out/client/node_modules/zeromq/lib/index.js:1:82)
    at Module._compile (internal/modules/cjs/loader.js:1063:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10)
    at Module.load (internal/modules/cjs/loader.js:928:32)
    at Function.Module._load (internal/modules/cjs/loader.js:769:14)
    at Function.n._load (/home/user-name/.vscode-server-insiders/bin/8440b8f47231147823ba9696913d642e5f2d9d58/out/vs/workbench/api/node/extensionHostProcess.js:104:32148)
    at Function.S._load (/home/user-name/.vscode-server-insiders/bin/8440b8f47231147823ba9696913d642e5f2d9d58/out/vs/workbench/api/node/extensionHostProcess.js:104:28737)
    at Function.g._load (/home/user-name/.vscode-server-insiders/bin/8440b8f47231147823ba9696913d642e5f2d9d58/out/vs/workbench/api/node/extensionHostProcess.js:99:60372)
    at Module.require (internal/modules/cjs/loader.js:952:19)
    at require (internal/modules/cjs/helpers.js:88:18)
    at Object.92747 (/home/user-name/.vscode-server-insiders/extensions/ms-toolsai.jupyter-2022.3.1000652335/out/client/extension.js:2:3879808)
    at __webpack_require__ (/home/user-name/.vscode-server-insiders/extensions/ms-toolsai.jupyter-2022.3.1000652335/out/client/extension.js:2:4547476)
    at u.zmqSupported (/home/user-name/.vscode-server-insiders/extensions/ms-toolsai.jupyter-2022.3.1000652335/out/client/extension.js:2:973952)
    at u.isSupportedForLocalLaunch (/home/user-name/.vscode-server-insiders/extensions/ms-toolsai.jupyter-2022.3.1000652335/out/client/extension.js:2:973695)
    at u.get isSupported [as isSupported] (/home/user-name/.vscode-server-insiders/extensions/ms-toolsai.jupyter-2022.3.1000652335/out/client/extension.js:2:973605)
    at t.registerTypes (/home/user-name/.vscode-server-insiders/extensions/ms-toolsai.jupyter-2022.3.1000652335/out/client/extension.js:2:984838)
    at /home/user-name/.vscode-server-insiders/extensions/ms-toolsai.jupyter-2022.3.1000652335/out/client/extension.js:2:1071301
    at /home/user-name/.vscode-server-insiders/extensions/ms-toolsai.jupyter-2022.3.1000652335/out/client/extension.js:2:4549051
    at e.activate (/home/user-name/.vscode-server-insiders/extensions/ms-toolsai.jupyter-2022.3.1000652335/out/client/extension.js:2:4548728)
Info 01:46:20: Checking for server existence.
Info 01:46:20: Checking for server usability.
Info 01:46:20: Starting notebook server.
Info 01:46:20: Connecting to server
Info 01:46:20: Connecting to process server
Info 01:46:20: Connecting server kernel http://localhost:8888/
Connecting to Jupyter server at http://localhost:8888/
Info 01:46:20: Creating server with settings : {"baseUrl":"http://localhost:8888/","appUrl":"","wsUrl":"ws://localhost:8888/","token":"<generated>","appendToken":true,"init":{"cache":"no-store","credentials":"same-origin"}}
Info 01:46:20: Connection complete server
Info 01:46:20: Server started.
Info 01:46:20: Creating server with settings : {"baseUrl":"http://localhost:8888/","appUrl":"","wsUrl":"ws://localhost:8888/","token":"<generated>","appendToken":true,"init":{"cache":"no-store","credentials":"same-origin"}}
Info 01:46:20: Disposing session manager
Info 01:46:20: SessionManager - dispose contents manager
Info 01:46:20: ShutdownSessionAndConnection - dispose session manager
Info 01:46:20: Finished disposing jupyter session manager
Error 01:46:20: Failed to get remote kernel connections FetchError: request to http://localhost:8888/api/kernels?1646462780375 failed, reason: connect ECONNREFUSED <IP_ADDRESS>:8888
    at ClientRequest.<anonymous> (/home/user-name/.vscode-server-insiders/extensions/ms-toolsai.jupyter-2022.3.1000652335/out/client/extension.js:2:3896753)
    at ClientRequest.emit (events.js:315:20)
    at Socket.socketErrorListener (_http_client.js:469:9)
    at Socket.emit (events.js:315:20)
    at emitErrorNT (internal/streams/destroy.js:106:8)
    at emitErrorCloseNT (internal/streams/destroy.js:74:3)
    at processTicksAndRejections (internal/process/task_queues.js:80:21)
Info 01:46:20: Experiment status for python is {"enabled":true,"optInto":[],"optOutFrom":[]}
Info 01:46:20: Creating server with settings : {"baseUrl":"http://localhost:8888/","appUrl":"","wsUrl":"ws://localhost:8888/","token":"<generated>","appendToken":true,"init":{"cache":"no-store","credentials":"same-origin"}}
Error 01:46:20: SessionManager cannot enumerate kernelspecs. Returning default {}.
Info 01:46:20: Disposing session manager
Info 01:46:20: SessionManager - dispose contents manager
Info 01:46:20: ShutdownSessionAndConnection - dispose session manager
Info 01:46:20: Finished disposing jupyter session manager
Error 01:46:20: Failed to get remote kernel connections FetchError: request to http://localhost:8888/api/kernels?1646462780733 failed, reason: connect ECONNREFUSED <IP_ADDRESS>:8888
    at ClientRequest.<anonymous> (/home/user-name/.vscode-server-insiders/extensions/ms-toolsai.jupyter-2022.3.1000652335/out/client/extension.js:2:3896753)
    at ClientRequest.emit (events.js:315:20)
    at Socket.socketErrorListener (_http_client.js:469:9)
    at Socket.emit (events.js:315:20)
    at emitErrorNT (internal/streams/destroy.js:106:8)
    at emitErrorCloseNT (internal/streams/destroy.js:74:3)
    at processTicksAndRejections (internal/process/task_queues.js:80:21)
Error 01:46:20: SessionManager cannot enumerate kernelspecs. Returning default {}.
Info 01:46:20: Creating controller for jupyter-notebook with interpreter ~/apps/miniconda/envs/py3/bin/python
Info 01:46:20: Find preferred kernel for ~/ycq/finalCode/code.ipynb with metadata {"interpreter":{"hash":"bdb01d8a15b4a6345e5784f5a21d4e0da2c265b2063c7c2dac9c493b1be069a1"},"kernelspec":{"display_name":"Python 3 (ipykernel)","language":"python","name":"python3"},"language_info":{"codemirror_mode":{"name":"ipython","version":3},"file_extension":".py","mimetype":"text/x-python","name":"python","nbconvert_exporter":"python","pygments_lexer":"ipython3","version":"3.8.2"}} & preferred interpreter ~/apps/miniconda/envs/py3/bin/python
Info 01:46:20: findKernel found py3 (Python 3.8.2)
Info 01:46:20: PreferredConnection: .jvsc74a57bd0eb19a54d4fd03c7e61c066493b945d2bec84db826f433b8c146903a698b93891./home/user-name/apps/miniconda/envs/py3/python./home/user-name/apps/miniconda/envs/py3/python.-m#ipykernel_launcher found for NotebookDocument: ~/ycq/finalCode/code.ipynb
Info 01:46:20: TargetController found ID: .jvsc74a57bd0eb19a54d4fd03c7e61c066493b945d2bec84db826f433b8c146903a698b93891./home/user-name/apps/miniconda/envs/py3/python./home/user-name/apps/miniconda/envs/py3/python.-m#ipykernel_launcher for document ~/ycq/finalCode/code.ipynb
Info 01:46:20: Setting controller affinity for ~/ycq/finalCode/code.ipynb .jvsc74a57bd0eb19a54d4fd03c7e61c066493b945d2bec84db826f433b8c146903a698b93891./home/user-name/apps/miniconda/envs/py3/python./home/user-name/apps/miniconda/envs/py3/python.-m#ipykernel_launcher
Info 01:46:21: Registering dummy command feature
Info 01:46:21: Got activated conda env vars ourselves for ~/apps/miniconda/envs/py3/bin/python in 550
Info 01:46:21: Process Execution: > ~/apps/miniconda/envs/py3/bin/python -m pip list
> ~/apps/miniconda/envs/py3/bin/python -m pip list
Info 01:46:21: Process Execution: > ~/apps/miniconda/envs/py3/bin/python -c "import jupyter"
> ~/apps/miniconda/envs/py3/bin/python -c "import jupyter"
Info 01:46:21: Process Execution: > ~/apps/miniconda/envs/py3/bin/python -c "import notebook"
> ~/apps/miniconda/envs/py3/bin/python -c "import notebook"
Info 01:46:21: Process Execution: > ~/apps/miniconda/envs/py3/bin/python -m jupyter kernelspec --version
> ~/apps/miniconda/envs/py3/bin/python -m jupyter kernelspec --version

@OpenWaygate
does it work when you go back to the version 2022.1.xxxx.
please confirm.
if it's still doesn't work, then your running into a separate issue, please created a separate issue of that's the case.

Pre-release version has solved my problem. Thanks.

Awesome thanks, closing in favor of https://github.com/microsoft/vscode-jupyter/issues/9234

@OneMoreSecond thanks for the confirmation, we'll be pushing out a stable release tomorrow with these fixes.


Add Dark mode support to listings and also fix functionality to next/previous buttons

The commit messages are self-explanatory.

commit 99700aea2ce14c72aa2f486d2f22fe27304565bb
Author: Dennis Chen<EMAIL_ADDRESS>Date:   Mon Aug 5 17:31:03 2024 -0700
Add dark variants for Previous/Next buttons

commit cc72a0c8f6b9125b2aea2a0d358f7c50a3c7e741
Author: Dennis Chen<EMAIL_ADDRESS>Date:   Mon Aug 5 17:21:12 2024 -0700
Fix Listings button functionality

- the previous and next buttons took people to /browse/PAGENUMBER rather
  than /browse/?page=PAGENUMBER, where the frontend expects the latter.
  Fixed.
- having fixed that, when we go to a new page, the listings do not
  refresh because the useEffect calling handleSearch has never been
  called; the useEffect hook now updates when pageNumber changes.

commit 3c6f3fa793d2848fd3b38f717ed3fdbb513c522e
Author: Dennis Chen<EMAIL_ADDRESS>Date:   Mon Aug 5 17:20:50 2024 -0700
Make previous/next buttons on left/right of screen

commit 7f72c077bae68e77252b34da0c244c884b837e9c
Author: Dennis Chen<EMAIL_ADDRESS>Date:   Mon Aug 5 17:09:52 2024 -0700
Make dark mode version of ListingGridCard

It may not be a bad idea to

- add a placeholder image/text when none is present for a listing (even
  something as simple as "No Image" to make it clear that this was
  intentional from the part of the listing creator, and not a network
  error)
- remove the `animate-pulse` effect in dark mode; I hesitantly kept it
  in for now but it is plausible that animate-pulse loses its magic in
  dark mode.

The GitHub action history is a bit of a mess because I screwed up rebasing. All is good now.
Here's a screenshot.

Before:

why does the image in your screenshot look messed up?

why does the image in your screenshot look messed up?

Fixed in a separate PR. This is a pre existing issue


Style images on the homepage

The homepage could use a little styling. Adjust the layout or images a little to make things a little prettier.


Can't bundle yaml file with json output file

Describe the bug
I need to bundle a yaml file, but I want a json output format.
When a provide output with a json extension, I get an error.
How to Reproduce
asyncapi bundle asyncapi.yaml -o asyncapi.json

I'm getting this message:
TypeError: The "data" argument must be of type string or an instance of Buffer, TypedArray, or DataView. Received an instance of Object

Expected behavior
Generate a json bundle file without errors.
Workaround
If I provide a yaml file with no extension as input, I can write the output to a new file as expected:
asyncapi bundle asyncapi_file_without_extension > asyncapi.json

Thanks for the issue.
@Souvikns hey can you have a look 🙏

I was able to reproduce the error and this is why it is happening:
https://github.com/asyncapi/bundler/blob/70a64bb6516af5c0ca1a1ea8ee85ffeec3668d1b/src/document.ts#L39 in bundler document.json() returns an object.


Not loaded after HA upgrade to 2024.06.0

After upgrading HA to 2024.06.0 an error appear

Looks like the issue is that HA updated bleak and https://github.com/builder555/pinecil_lib/blob/master/pyproject.toml#L12C10-L12C17 is too strict

Opened https://github.com/builder555/pinecil_lib/issues/1

I will give the maintainer some time to respond, will consider forking if no solution is reached upstream.

The upstream maintainer has pushed and released a solution, will upgrade on this end

@brusarp I pushed a fix for the dependency version. It seems to work for me:

let me know if it does for you

Good, thank you!
The error is gone but I can't try to connect the soldering iron because I don't have it here with me right now...

ERR_NOT_ENOUGH_PINECILS

Sorry for delay, I'm going to close this issue as I tested also with Pinecil and now all works. Thank you @t3chguy !