PIR and SIG architecture

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
If updating an existing version, please select the specific langauge SDKs and CLIs that must be refreshed after the swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No refresh required for updates in this PR

Contribution checklist:

[ ] I commit to follow the Breaking Change Policy of "no breaking changes"
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[ ] Check this box if any of the following apply to the PR so that label "WaitForARMFeedback" will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you are using OpenAPIHub to initialize the PR for adding a new version. More details, refer to the wiki.

[ ] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in a stable version
[ ] Removing properties in a stable version
[ ] Removing API version(s) in a stable version
[ ] Updating API in a stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

/azp run

LGTM

@ArcturusZhang  ready for merging. Please merge

/azp run

We have a model collision issue on tag package-2021-08-01. I will make a change to this branch to remove the corresponding tag so that we could work that around and defer the real fix for that.

It turns out that we have to fix it in this PR because the package that is reporting errors has already been released, and we cannot remove it.
The issue was introduced by the recent additions of x-ms-identifiers. Some files were added and some were not. Considering the tags in this RP are kind of entangled with each other - therefore if you added the extension to one of the file, you will have to add the same to other files in the same tag - and there is a chain reaction starting.
I wonder why they could merge the PR that adds the new extension.
I will push some commits to this branch to resolve that


PassthroughCluster using HTTP/1.1 instead of HTTP/2

Bug description
I have a service deployment (protocol specified as http2) with 2 replicas. Both the pods have a sidecar container running. Assume one of the pods to be the master and other, the slave. When I trigger a HTTP/2 service request from the slave to the master using the master pod IP, PassthroughCluster is used and on the inbound I see the protocol being changed from HTTP/2 to HTTP/1.1.
Here is the log from the sidecar on the slave pod:
[2020-06-08T20:39:42.106Z] "GET / HTTP/2" 200 - "-" "-" 0 612 3 2 "-" "curl/7.52.1" "4510cd78-8428-99b6-9906-0364e6b34e0c" "<IP_ADDRESS>:8200" "<IP_ADDRESS>:8200" PassthroughCluster <IP_ADDRESS>:34076 <IP_ADDRESS>:8200 <IP_ADDRESS>:34074 - allow_any
And this is the log from the sidecar on the master pod:
[2020-06-08T20:39:42.106Z] "GET / HTTP/1.1" 200 - "-" "-" 0 612 1 0 "-" "curl/7.52.1" "4510cd78-8428-99b6-9906-0364e6b34e0c" "<IP_ADDRESS>:8200" "<IP_ADDRESS>:8200" inbound|8200|http2|my-nginx.default.svc.cluster.local <IP_ADDRESS>:53072 <IP_ADDRESS>:8200 <IP_ADDRESS>:34076 - default
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[X] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Expected behavior
PassthroughCluster to use HTTP/2. It should not downgrade the request to HTTP/1.1 and therefore, I expect the sidecar on the master pod to forward HTTP/2 request to the service container.
Steps to reproduce the bug

Deploy a service with 2 replicas (with sidecar)
Exec into the service container of one of the pods
Trigger a HTTP/2 request to the service, something like curl -v --http2-prior-knowledge http://<IP_ADDRESS>:8200, where <IP_ADDRESS> is the master pod IP
Check the logs on both the sidecars. You will see logs similar to what I have mentioned in the description

Version (include the output of istioctl version --remote and kubectl version and helm version if you used Helm)
istioctl version --remote
client version: 1.4.6
control plane version: 1.6.0
data plane version: 1.6.0 (5 proxies)
kubectl version
Client Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.2", GitCommit:"c97fe5036ef3df2967d086711e6c0c405941e14b", GitTreeState:"clean", BuildDate:"2019-10-15T19:18:23Z", GoVersion:"go1.12.10", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.0", GitCommit:"2bd9643cee5b3b3a5ecbd3af49d09018f0773c77", GitTreeState:"clean", BuildDate:"2019-09-18T14:27:17Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"linux/amd64"}
helm version
Client: &version.Version{SemVer:"v2.15.1", GitCommit:"cf1de4f8ba70eded310918a8af3a96bfe8e7683b", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.15.1", GitCommit:"cf1de4f8ba70eded310918a8af3a96bfe8e7683b", GitTreeState:"clean"}
How was Istio installed?
istioctl install --set profile=demo
Environment where bug was observed (cloud vendor, OS, etc)
Minikube

@sha-rath we are tracking this in https://github.com/istio/istio/issues/24706, I am actively looking into this and I think I know a fix. I was able to reproduce the issue, thanks for the help. We will continue updates in that issue. Thanks!


Deleted msal-node's package-lock.json

This file should have been deleted as part of the original npm workspaces PR. It breaks npm workspaces when developing in msal-node.

Codecov Report

Merging #6571 (8c9b59c) into dev (81d34b4) will decrease coverage by 3.97%.
Report is 354 commits behind head on dev.
The diff coverage is n/a.

Flag
Coverage Δ

msal-angular
?

msal-browser
?

msal-common
?

msal-core
?

msal-node
81.02% <ø> (-2.37%)
:arrow_down:

msal-node-extensions
?

msal-react
?

node-token-validation
?

see 235 files with indirect coverage changes


Sync log name not queryable using logName=

Environment details

OS: Container (base node:12-slim)
Node.js version: 12
npm version: 7.18.1
@google-cloud/logging version: 9.5.4

Steps to reproduce

Create service w/ code:

 const {Logging} = require('@google-cloud/logging');
 const logging = new Logging();
 await logging.setProjectId()
 await logging.setDetectedResource()

 const msg = "my test sync message";
 const metadata = {
   severity: 'ERROR',
 };

 const log = logging.logSync("test-sync-name");
 const entry = log.entry(metadata, msg);
 log.write(entry);

Deploy to Cloud Run:

gcloud beta run deploy logging-test --source .

Try querying in Cloud Logging console:

resource.type="cloud_run_revision"
logName="projects/PROJECT/logs/test-sync-name"

Above does not work compared to:
resource.type="cloud_run_revision"
jsonPayload.logName="projects/PROJECT/logs/test-sync-name"

I would expect to query the log name the same as other logs and not have to search the JSON payload

It seems no repro anymore - closing it


26137: context.is_active() and context.add_callback() do not work whe…

…n using grpc.aio

@nicolasnoble

@lidizheng Will this require a gRFC?

We can claim these methods belonging to the shared context object class grpc.aio.RpcContext. So, this PR will be a patch to fix missing methods. I think it should be fine without gRFC.

@lidizheng any review  comments on these changes so that  they can be taken  up for merge? Please advise on any next steps from my side to take it  further.

Is there a plan to merge this change to master branch? I too have a use case for a gnmi server implementation where when subscription is ended by gnmi client I need a way in gnmi server to tap that and deregister the streaming request from providers.

I am not sure if I am missing something, I built the python package usinf SaeerMahajan-GSLab:master and I am adding a callback but I get below exception
How I am adding the callback:
async def Subscribe(self, request_iterator, context):
...
context.add_callback(self.OnDone)
...
async def OnDone(self):
self.logger.info("Client Terminating")
I get below exception:
Exception has occurred: AttributeError
'grpc._cython.cygrpc.RPCState' object has no attribute 'callbacks'
File "$FILE_PATH1", line 107, in Subscribe
context.add_callback(self.OnDone)
File "$FILE_PATH2", line 43, in
asyncio.run(AsyncServer.run(args))
When I looked at the RPCState (defined in src/python/grpcio/grpc/_cython/_cygrpc/aio/server.pyx.pxi), it doesn't have the callbacks attribute so below one is failing.
def add_callback(self, callback):
if type(self._rpc_state.callbacks) == list:
self._rpc_state.callbacks.append(callback)
return
cdef class RPCState:
def __cinit__(self, AioServer server):
    init_grpc_aio()
    self.call = NULL
    self.server = server
    grpc_metadata_array_init(&self.request_metadata)
    grpc_call_details_init(&self.details)
    self.client_closed = False
    self.abort_exception = None
    self.metadata_sent = False
    self.status_sent = False
    self.status_code = StatusCode.ok
    self.status_details = ''
    self.trailing_metadata = _IMMUTABLE_EMPTY_METADATA
    self.compression_algorithm = None
    self.disable_next_compression = False

Am I doing something wrong here? Any help/pointers will be highly appriciated?
Thanks,
HA

The proposed APIs are merged in #27767.


Error in .External2: unable to start data viewer

Hi,
I'm getting this error when trying to plot some data. It used to work before orca was installed. This only happens on EC2 headless server (Red Hat Linux 7.5), not locally (Ubuntu with gtk desktop).
Warning: Error in .External2: unable to start data viewer
  125: View

We add this line to the /etc/systemd/system/shiny-server.service file, under [Service]
Environment="DISPLAY=:1

Also this (should run before launching shiny service?)
# launch headless server (the final & makes the program run in background)
Xvfb :1 -screen 0 1024x768x16 &

Thanks!

Closing as it was not related to orca


Rework of dataloader

closes #43

Codecov Report

Merging #47 into master will decrease coverage by 0.17%.
The diff coverage is 86.27%.

@@            Coverage Diff             @@
##           master      #47      +/-   ##
==========================================
- Coverage   58.12%   57.94%   -0.18%
==========================================
  Files          71       71
  Lines        1944     1950       +6
==========================================
  Hits         1130     1130
- Misses        814      820       +6

Flag
Coverage Δ

#unittests
57.94% <86.27%> (-0.18%)
:arrow_down:

Impacted Files
Coverage Δ

mantisshrimp/models/__init__.py
100.00% <ø> (ø)

mantisshrimp/models/mantis_detr.py
96.66% <50.00%> (-3.34%)
:arrow_down:

mantisshrimp/test_utils/simple_model.py
84.61% <50.00%> (-6.30%)
:arrow_down:

...tisshrimp/models/mantis_rcnn/mantis_faster_rcnn.py
52.17% <55.55%> (ø)

mantisshrimp/models/mantis_rcnn/mantis_rcnn.py
34.48% <92.85%> (ø)

mantisshrimp/models/mantis_module.py
100.00% <100.00%> (ø)

mantisshrimp/models/mantis_rcnn/__init__.py
100.00% <100.00%> (ø)

...antisshrimp/models/mantis_rcnn/mantis_mask_rcnn.py
64.00% <100.00%> (ø)

...ntisshrimp/models/mantis_rcnn/rcnn_param_groups.py
33.33% <100.00%> (ø)

mantisshrimp/test_utils/records.py
92.85% <100.00%> (ø)

... and 2 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 60e7cd9...0276f71. Read the comment docs.


Updating .scss Stylesheet During Development Breaks Script Integrity

When running npm run dev & npm run dev:server (and store is pointed to local checkout), after editing a .scss file (for instance _checkoutHeader.scss) and refreshing the checkout page, the script integrities break, requiring the dev server to be restarted.
I temporarily resolved this by turning off integrities on the webpack config when not in production, but it's still producing a non-blocking error.

Thanks for reporting this @hunterashaw , we will have a look at this in the next couple of weeks.

We’ve released a feature that allows you to bypass the integrity hash values in the local development environment.
You could get it by rebasing your code to the latest master.


[Feature Request] Android: Option to pause playback on audio becoming noisy

What is the need and use case of this feature?
In Android pausing audio when a headset or bluetooth disconnects is a standard playback behavior. This is accomplished by listening to the ACTION_AUDIO_BECOMING_NOISY intent and pausing audio.
Describe the ideal solution
It would be great if there was a RNTP option something like pausePlaybackOnAudioBecomingNoisy: boolean.
Describe alternatives you've considered
I'm not sure there's any other workarounds possible.
How I can Help
I'd be happy to work on a PR although I believe it also requires a change in the KotlinAudio repo.

@mattleff this seems like something that we'd want to support. My question would be if this should be standard behavior or if it should be configurable. We'd also want feature parity on iOS, have you looked into that side at all?
@dcvz thoughts? Basically auto pause when disconnecting an audio device like headphones.

@jspizziri Good point about iOS. It appears that currently iOS pauses playback automatically whenever an output channel is disconnected. So that would be an argument to have it be standard for Android too.

@mattleff do you need any direction before opening a PR? Probably just for the unconfigurable option.

@jspizziri I've opened a simple PR for this: https://github.com/doublesymmetry/KotlinAudio/pull/26 I'm not sure to how to test it, so any guidance there would be appreciated.

Nice, at this point we'll need to wait for feedback from the DoubleSymmetry team. TBH, testing updates to KotlinAudio within the context of this project is something I've not figured out yet. However, I've requested some documentation from those in the know which, once I have, will be added to this repository.
I'm quite the n00b when it comes to Gradle, but at a high level what I've been told is that you can publish your local modifications to a local maven repository and then install the local version in this package. If that means anything to you please run with it. If I don't get docs in a few weeks I'll probably try to figure it out myself again (but that didn't go well last time ha).


Needs a new maintainer

This project is mostly unmaintained. Someone who uses it actively would be a better candidate for maintainership. @oe1rfc, @bartmeuris, @JulienPalard, @emu-signal? If so, we can just call your fork the new official repo and I'll sign over the PyPI ownership using whatever process is used for that.

Sorry, I'm not actively using it at the moment. I added the update_wpa_key researching a few things, but the requirements for the setup changed, and I ended up not needing it at all. I created the PR since I thought it could be a useful additional feature.

It's more or less the same for me, we're using it for a small hotspot project where it's doing the desired job, but I don't really want to do further projects using ubnt's proprietary firmware+controller.

Same here, wait until I finished translating the whole Python Documentation in french, then I'll choose another project ^^

I will be more than happy to maintain it, already created a private fork which uses new requests module instead of urllib. If you need any help in maintaining this project please let me know.

Question still relevant?
We have actively used the Unifi and api for it.

It is. I'd prefer for someone who's already contributed something to take over it, but yes.

Just discovered this. Really awesome tool guys. Hope you all maintain this!!

I just collect different pieces of code from project's forks (https://github.com/calmh/unifi-api/pull/39) and wrote a number of samples, such as get_health get_setting. Today or tomorrow I will try to make the pullrequest.

FYI: not a fork, but I've been working on a lightweight CLI for UniFi using some of the API endpoints identified in this project.


[ja] Remove content/ja/docs/reference/kubectl/overview.md

content/ja/docs/reference/kubectl/overview.md should be removed from ja because it had been removed from en.
In en, the contents of overview.md was moved in _index.md and overview.md removed in #29847.
It is needed the same fix in ja.
This PR is included the following.

The contents of content/ja/docs/reference/kubenet/overview.md was moved to content/ja/docs/reference/kubenet/_index.md.
The _index.md was fixed the top's comment(line 12-20) and "What's next" at the bottom.
The link to docs/reference/kubectl/overview/ was changed to /docs/reference/kubectl/ in some files.
The content/ja/docs/reference/kubelet/overview.md was removed.

Related: #29847
Fixes: #39848

I have realized something when I was creating this PR.
I think it needs to be fixed in another PR.

The content/ja/docs/reference/kubectl/_index.md need to be updated to the latest like en.
The content/ja/docs/tasks/tools/install-kubectl.md will need to be removed. Instead, the following 3 files will need to be created.

content/ja/docs/tasks/tools/install-kubectl-linux.md
content/ja/docs/tasks/tools/install-kubectl-macos.md
content/ja/docs/tasks/tools/install-kubectl-windows.md

The netlify build (deploy) failed with error 'Build exceeded maximum allowed runtime'.
After force push, the build was able to pass.

/cc @atoato88 @t-inu

The main target page on preview site:

https://deploy-preview-39849--kubernetes-io-main-staging.netlify.app/ja/docs/reference/kubectl/

And we could check the removing of overview page.

@s-kawamura-w664
I would like to check the content of update.
As you wrote in description, the content of _index.md is as-is on current content, just moved?
In other word, you didn't update the content of _index.md to sync with _index.md on current en?

Current codebase of this PR does not include the section of here "In-cluster authentication and namespace overrides" in en, that's why I commented above.

@atoato88

As you wrote in description, the content of _index.md is as-is on current ja content, just moved?
In other word, you didn't update the content of _index.md to sync with _index.md on current en?
Yes.
The first, I just moved from overview.md to _index.md.
I tried to fix _index.md to the latest in the second commit, but it was so much to fix, so I decided to do it in the next PR.

Ok, I also think it's reasonable.

Content of this PR looks good.
But building preview failed, this didn't  relate with the content of this PR, I think.
Could you create empty commit for building preview again?

/check-cla

/lgtm

/assign @nasa9084
Could you review this?

/approve
Thank you~


How does the caching DbDependency work exactly?

I'm starting to use the built in query caching such as:
$sql = $db->createCommand('SELECT * FROM my_table WHERE something=1')->cache(3600)->queryAll();
Now I tried to find out how to delete the cache for this item once the database info has been changed, as I understand you can't do it with the normal delete method as you need to provide a key, which you obviously don't use with query caching.
Then I thought about using the DbDependency, however unsure how this is beneficial.
How does it know the data has changed and needs to invalidate the cache item? Wouldn't it need to run the query to find out and thus defeat the purpose of caching in the first place!?
I am I better off using something like TagDependency instead so that when I change the data I can then just invalidate the cache myself?
Additional info

Q
A

Yii version
2.0.9

PHP version
5.5.28

Operating system
Win7 / CentOS

@samdark I am trying to post on the forum but it's not sending me my password reset email; I have tried multiple times.

@cyphix333 ping me on IRC (#yii on freenode), to fix your forum login.


Ewallet Balance PHPDoc

Hey there,
The PHPDoc on EoneoPay\PhpSdk\Endpoints\Ewallet defines a method to get the balances as @method mixed[]|null getBalances() which tells us it will either return an array or null.
But the PHPDoc on EoneoPay\PhpSdk\Traits\EwalletTrait for the $balances property is @var \EoneoPay\PhpSdk\Endpoints\Balance|null which tells us it will either return a Balance object or null.
Because of that the auto-completion in PHPStorm told us we're dealing with an array so it broke when we started to test it.

@natepage The typehint has been updated and available in tag 1.0.0-RC6.


MaxAbsScalerModel incorrect values when case SparseVector

The MaxAbsScalerModel gives a SparseVector with different results than the equivalent model in Spark.
I think there are two problems:
line 40 of MaxAbsScalerModel.scala:
vs(i) *= raw
To make it emulate Spark the line would need to be:
vs(i) = raw
Also, line 38 of MaxAbsScalerModel.scala
val raw = max(-1.0, min(1.0, values(i) / maxAbsUnzero(i)))
To emulate Spark the line needs to be:
val raw = max(-1.0, min(1.0, values(i) / maxAbsUnzero(indices(i))))
I would've just made the code change for your review, but I've never used Git before.

PR here: https://github.com/combust/mleap/pull/273
Thanks for finding this bug!

@smorring Would you care to make a PR for review? Would be happy to help with any git knowledge you would need.

I'd certainly love to contribute in some way.
I come from a SVN background, so I'm not familiar with Git.  I assume a PR is a Pull Request?
I've clicked "Create Pull Request" from GitHub and am presented with the following choices:

release/v0.8https://github.com/combust/mleap/compare/master...release/v0.814 minutes ago
feature/ensemblehttps://github.com/combust/mleap/compare/master...feature/ensemble3 days ago
feature/asynchttps://github.com/combust/mleap/compare/master...feature/async3 days ago
feature/corshttps://github.com/combust/mleap/compare/master...feature/corson Jun 30
master<EMAIL_ADDRESS>
I'm suppose I should click "release/v0.8?
FYI.  I'm using Intellij and can get to a Clone Repository dialog that asks for a "Git Repository URL".
I'd love to contribute if you could help me get started the first time.

From: Hollin Wilkins<EMAIL_ADDRESS>Sent: Monday, September 25, 2017 9:39 PM
To: combust/mleap
Cc: smorring; Mention
Subject: Re: [combust/mleap] MaxAbsScalerModel incorrect values when case SparseVector (#272)
@smorringhttps://github.com/smorring Would you care to make a PR for review? Would be happy to help with any git knowledge you would need.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/combust/mleap/issues/272#issuecomment-332069525, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Aex569taO0qHSli2euJwdfgDcgrdNP7Gks5smGPxgaJpZM4PjimY.

First thing to do is to fork mleap. Click on the button in the upper right on this screen. This makes a copy of mleap for your user.

Next thing is to clone the fork.
git clone --recursive<EMAIL_ADDRESS>This makes a local copy on your computer.

Make a branch to work on git branch feature/issue272 && git checkout feature/issue272

Make your changes

Commit your changes git add . && git commit -m "Fix issue with MaxAbsScaler"

Push your changes to your fork git push -u origin feature/issue272

Create a pull request with combust/mleap

Let me know if you run into any trouble on the way!

I think I've completed all the steps you mentioned.
Please let me know if the changes I pushed aren't visible to you.

From: Hollin Wilkins<EMAIL_ADDRESS>Sent: Monday, September 25, 2017 11:42 PM
To: combust/mleap
Cc: smorring; Mention
Subject: Re: [combust/mleap] MaxAbsScalerModel incorrect values when case SparseVector (#272)

First thing to do is to fork mleap. Click on the button in the upper right on this screen. This makes a copy of mleap for your user.

Next thing is to clone the fork.
git clone --recursive<EMAIL_ADDRESS>This makes a local copy on your computer.

Make a branch to work on git branch feature/issue272 && git checkout feature/issue272

Make your changes

Commit your changes git add . && git commit -m "Fix issue with MaxAbsScaler"

Push your changes to your fork git push -u origin feature/issue272

Create a pull request with combust/mleap

Let me know if you run into any trouble on the way!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/combust/mleap/issues/272#issuecomment-332084777, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Aex566ZzT9GNzU8RBEg_jVBqMKjoQXejks5smIDAgaJpZM4PjimY.

Closing this issue along with merging the PR. Thanks for the catch!


Update org.nodejs pkg to 4.1.2

-- https://nodejs.org/en/blog/release/v4.1.2/

Thank you for the contribution. It was merged directly as 6e934b2625086f937b0e971e992b9f7b9c4b8955 to keep commit history cleaner. Your contribution is still credited to you.


PDFBOX-5715: Lines vanish when printing on MacOS

This a fix for the PDFBOX-5715 Lines vanish when printing on MacOS.
PageDrawer class sets clip the same as drawn path on line https://github.com/apache/pdfbox/blob/6441a8b6117c7ac9963491de79c8c5f07e4a52df/pdfbox/src/main/java/org/apache/pdfbox/rendering/PageDrawer.java#L998
When the graphics scale is less than 1.0 and the path stroke width is less than 1.0 then the clip width or height is less than 1.0 and it can be rounded in the device space to have a zero area.
The issue with the fop project is reproduced on MacOS because CPrinterJob sets graphics scale to 1 for Printable, PDFBox adds scale 0.4842 in code:
https://github.com/apache/pdfbox/blob/2b60e17e1db7bfc29d32ba33530d305c6441aaa1/pdfbox/src/main/java/org/apache/pdfbox/printing/PDFPrintable.java#L213
where imageable area is [288, 432], crop box area: [0.0,0.0,594.72,792.0] and the scaleX is 288/594.72 = 0.4842, and the linePath stroke is 0.283.
On Linux RasterPrinterJob sets the graphics scale to 4.16 which is enough to properly draw the line path in the device space.
The RasterPrinterJob calculates x/yScale as  getX/YRes() / 72.0 where the default getX/YRes is 300.
The fix checks if the graphics scale is less than 1.0 and the scaled linePath bounds width or height is less than 1.0 and then enlarges the clip bounds to cover at least 1 point plus 0.5 on one and another side in the device space to allow to draw the linePath inside the clip.
The linePath can consists from different lines but when its bounds width or height is less than 1.0 it seems safe to use a rectangle as a clip instead of the real path.
For performance reasons the fix first checks if the graphics scale is less than 1.0 and if it is not the case the initial clip is used. It still can be the case that the scale is larger than 1.0 but the line stroke width is less than 1.0 so the total stroke width in the device space is less than 1.0.
The tests pass on Linux with the fix.
There are failing tests on MacOS but as I can see the same tests fail on MacOS even without the fix:
The only test which uses the graphics scale less than 1.0 on Linux is org.apache.pdfbox.tools.imageio.TestImageIOUtils but its linePath bounds widht and height are greater than 1.0.

Interesting, I tested on windows and it makes no difference at 100% (which your text mentions) but it makes a difference at 50% in PDFDebugger. I'll wait for feedback from Trey.

I'll wait for feedback from @tresf

@THausherr sorry, I should have subscribed to notifications.  Yes, by running the PDFBOX-5715 test case against this PR, it directly fixes the symptom.

Before: borders.pdf has random lines missing
After: borders.pdf show all lines

I tested on windows and it makes no difference at 100% (which your text mentions) but it makes a difference at 50% in PDFDebugger.

I've only tested on macOS, but since the test provided in PDFBOX-5715 uses a page size of 4x6 (roughly 50% of a US Letter or A4 Letter), this may explain the difference.
If you'd like some further regression testing before merging, please let me know.  I can run the prepared example on any system you wish, including printing to a physical printer.

There are failing tests on MacOS but as I can see the same tests fail on MacOS even without the fix

Just curiosity, I won't be able to do anything myself: what tests fails on MacOS?

There are failing tests on MacOS but as I can see the same tests fail on MacOS even without the fix

Just curiosity, I won't be able to do anything myself: what tests fails on MacOS?

FWIW, my results on M1 / OpenJDK@11 all pass on the OP's branch PDFBOX-5715-TRUNK:
[INFO] Reactor Summary for Apache PDFBox 4.0.0-SNAPSHOT:
[INFO]
[INFO] PDFBox parent ...................................... SUCCESS [  0.964 s]
[INFO] Apache PDFBox io ................................... SUCCESS [  4.623 s]
[INFO] Apache FontBox ..................................... SUCCESS [  4.240 s]
[INFO] Apache XmpBox ...................................... SUCCESS [  2.406 s]
[INFO] Apache PDFBox ...................................... SUCCESS [ 28.867 s]
[INFO] Apache PDFBox Debugger ............................. SUCCESS [  0.631 s]
[INFO] Apache PDFBox tools ................................ SUCCESS [ 11.235 s]
[INFO] Apache PDFBox application .......................... SUCCESS [  3.188 s]
[INFO] Apache PDFBox Debugger application ................. SUCCESS [  2.728 s]
[INFO] Apache PDFBox examples ............................. SUCCESS [ 11.809 s]
[INFO] Apache PDFBox ...................................... SUCCESS [  0.014 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  01:11 min
[INFO] Finished at: 2023-11-30T11:23:49-05:00
[INFO] ------------------------------------------------------------------------

Just curiosity, I won't be able to do anything myself: what tests fails on MacOS?

I am sorry. I found that I had used ssh to build and install PDFBox jars to the local maven repository and some tests failed because they couldn't initialize the graphics environment.
I checked that PDFBox tests pass with and without the fix with UI on MacOS.

Thank you so much for this, @AlexanderScherbatiy. Please close your PR, it has been committed. (I forgot to add the close command in the commit msg)

The committed fix: https://github.com/apache/pdfbox/commit/73f2fff550ada9db999f7f22dca781782c5fb5bc


Game Crashes on load when randomizer is enabled

just saw your video and tried to play the randomizer, but unfortunately the game crashes.
I'm using Windows 11 with Dolphin Emulator and (stock) riivolution. I downloaded your pack, right click the USA version of NSMBW, start with riivolution patches, and then no matter which randomizer setting I select, the game doesn't work as long as the patch is enabled. the game works without patches, and even works with Newer smbw's riivolution patch (to narrow down the issue).

the mod extracted to here in my folder, and the riivolution .xml went into the folder with all the other .xml files (as it should).
When I start the game, it shows the wii safety popup and the "hold your wii remote sideways", and then gives me infinite dolphin panic handlers, which when ignored freeze the game with a blackscreen.
I hope this can be reproduced or there is a simple fix on my side that I can attempt, dual core speedup is off.

I think I may have found the issue. Can you try using this build from the latest commit?
NSMBW-Pipe-Randomizer.zip

I have the same issue i used the link you used. only thing i can give is this. its stuck on boot. when i click ok at just changes a few of the numbers on it

same thing with the update for me. crashes on boot.

Wait, it worked?


Make graph work with tearoffs - add tooltips

Add tooltips in D2 from documentation comments.

This should probably be merged "squashed" given the changes and rollbacks.

LGTM, thanks!


Move docs to nuxt-generate

Hi @mariolamacchia, do you mind if i'll make your docs as nuxt generate project?

Do you mean to generate a static project from the docs?

Yes, it will resolve #81. And i just want to do something on nuxt generate, so it's better to do something helpful)

It would be awesome 😄


Report multiple LICENSE files

Closes #71
Relates to 3.0.0 release #77
Open question: Should we change --with-license-file to --with-license-files for added clarity?
Unit tests will be updated once consensus is reached on the approach/design.
Tested against the opencv-python-headless package, which has two included LICENSE files.
Supported:

[X] PlainVertical
[X] JSON
[X] JSON LicenseFinder (does not support License files anyway)
[X] Plain (see comment)
[ ] HTML
[ ] CSV
[ ] RST
[ ] Markdown
[ ] Confluence

By default plain looks something like (with truncated license files):
 Name                    Version   License  LicenseFile                                                                                LicenseText
 opencv-python-headless  <IP_ADDRESS>  MIT      ['c:\\users\\user\\github\\pip-licenses\\venv\\lib\\site-packages\\opencv_python_headless-<IP_ADDRESS>.dist-info\\LICENSE-3RD-PARTY.txt', 'c:\\users\\user\\github\\pip-licenses\\venv\\lib\\site-packages\\opencv_python_headless-<IP_ADDRESS>.dist-info\\LICENSE.txt']  ['OpenCV library is redistributed within opencv-python package.\nThis license applies to OpenCV binary in the directory cv2/.\n\nBy downloading, copying, installing or using the software you agree to this license.\nIf you do not agree to this license, do not download, install,\ncopy or use the software.\n\n\n                          License Agreement\n               For Open Source Computer Vision Library\n                       (3-clause BSD License)\n\n', 'MIT License\n\nCopyright (c) Olli-Pekka Heinisuo\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\n']

Personally, this doesn't seem much worse than the status quo formatting wise, and also conveys all of the information. Not sure if people would actually use plain format with license files or not, but it is deliminated as a Python list.

HTML:

        Name
        Version
        License
        LicenseFile
        LicenseText

        opencv-python-headless
        <IP_ADDRESS>
        MIT
        ['c:\\users\\user\\github\\pip-licenses\\venv\\lib\\site-packages\\opencv_python_headless-<IP_ADDRESS>.dist-info\\LICENSE-3RD-PARTY.txt', 'c:\\users\\user\\github\\pip-licenses\\venv\\lib\\site-packages\\opencv_python_headless-<IP_ADDRESS>.dist-info\\LICENSE.txt']
        ['OpenCV library is redistributed within opencv-python package.\nThis license applies to OpenCV binary in the directory cv2/.\n\nBy downloading, copying, installing or using the software you agree to this license.\nIf you do not agree to this license, do not download, install,\ncopy or use the software.\n\n\n                          License Agreement\n               For Open Source Computer Vision Library\n                       (3-clause BSD License)\n\n', 'MIT License\n\nCopyright (c) Olli-Pekka Heinisuo\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\n']

Ideally these could be broken into a list using
, but this is implemented in the prettytable.get_html_string() so it is not easily modifiable in this project.

CSV:
"Name","Version","License","LicenseFile","LicenseText"
"opencv-python-headless","<IP_ADDRESS>","MIT","['c:\\users\\user\\github\\pip-licenses\\venv\\lib\\site-packages\\opencv_python_headless-<IP_ADDRESS>.dist-info\\LICENSE-3RD-PARTY.txt', 'c:\\users\\user\\github\\pip-licenses\\venv\\lib\\site-packages\\opencv_python_headless-<IP_ADDRESS>.dist-info\\LICENSE.txt']","['OpenCV library is redistributed within opencv-python package.\nThis license applies to OpenCV binary in the directory cv2/.\n\nBy downloading, copying, installing or using the software you agree to this license.\nIf you do not agree to this license, do not download, install,\ncopy or use the software.\n\n\n                          License Agreement\n               For Open Source Computer Vision Library\n                       (3-clause BSD License)\n\n', 'MIT License\n\nCopyright (c) Olli-Pekka Heinisuo\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\n']"

We could customize this in CSVPrettyTable but I'm not sure what the best way forward is here, or if we should even try to support CSV for --with-license-files.

@raimon49 Let me know if you have feedback/ideas on the direction of this. I really like how plain-vertical and json look (the two most-likely used options with license files). I'm unsure exactly the best choice for the others (or if they should even be supported with --with-license-files).

@johnthagen Thanks for the PR.
First, I would like the base branch of PR to be release-3.0 instead of master. And it's better if the branch branch source is rebased to release-3.0.

Personally, this doesn't seem much worse than the status quo formatting wise, and also conveys all of the information. Not sure if people would actually use plain format with license files or not, but it is deliminated as a Python list.

Yes, I agree with you. This is a surprisingly good look.

Ideally these could be broken into a list using
, but this is implemented in the prettytable.get_html_string() so it is not easily modifiable in this project.

Yes, this is indeed a bad look.
Even though it's hard to replace
 -
 with , it's better to be served like a Python list in a single  element.

We could customize this in CSVPrettyTable but I'm not sure what the best way forward is here, or if we should even try to support CSV for --with-license-files.

We could customize this in CSVPrettyTable but I'm not sure what the best way forward is here, or if we should even try to support CSV for --with-license-files.
I think that if there is a single license file found, output it without enclosing it in [].

I really like how plain-vertical and json look (the two most-likely used options with license files). I'm unsure exactly the best choice for the others (or if they should even be supported with --with-license-files).

If you replace a valid option with --with-license-files, you will be warned when a user specifies the old option --with-license-file.
For example, before pip-license 1.x to 2.x, the system warns to user if the deprecated option is specified. See sample implementation.
Of course, the idea is to release 3.0 with the --with-license-file option intact. However, the behavior has changed so much that it seems better for users to know that they are now a "different option".

First, I would like the base branch of PR to be release-3.0 instead of master.

Done.

If you replace a valid option with --with-license-files, you will be warned when a user specifies the old option --with-license-file.

Done.

I think that if there is a single license file found, output it without enclosing it in [].

I implemented this for CSV class. Note that CSV still suffers from \n in the LicenseFile contents themselves.

It looks like the base hasn't been changed yet.
You can change it from the Edit button.

It looks like the base hasn't been changed yet.

Ah, got it. I had rebased the fork via Git, but hadn't told GitHub to change the base for viewing purposes on GitHub.

@raimon49 Checking in on this. Anything else you want to see before the 3.0.0 release? I noticed Python 3.9 comes out tomorrow.

@johnthagen Thanks for the notification.
I have taken this Pull Request and considered releasing version 3.0.0. But the scope of the changes is wide and some unit tests are broken. In particular, it conflicts with the tests added in #76.
Your idea is great, but I'm releasing version 3.0.0 with no changes in the handling of the license file.

@raimon49 Is handling multiple license files still something that can be considered? If so, do you know what approach you would accept?

@johnthagen Handling multiple license files is an idea worth considering.
The problem is that the current pip-licenses code and testing is vulnerable to major changes. I will attempt to resolve the problem when I have the time to do so. I may then cherry-pick some commits from your open Pull Request.

Sounds great! When you get to it, if you'd like any more help shoot me a ping.

I'm guessing this never got addressed?

AFAIK not for now, as well as some other stuff from the version 4.0 list (which is not correctly updated and some stuff might be biased like a settings file for VS Code or environment caching benefits), although version 4.0 has been released over a year ago.


Support for the Neewer GL1 Key Light

Any chance to add full support for the GL1 Key Light?
product page
As of now, I can discover the light and switch it on/off, but moving the BRR and CCT sliders switches the light off and it cannot be toggled again unless I close NeewerLite, reconfigure the light with the official macOS app (Neewer Live) and close it, then restart NeewerLite.

Do you see any crash report from bluetoothd in the /Library/Logs/DiagnosticReports folder?

Thanks for your follow-up.
No files with anything related to BlueTooth in that directory.

Please check to see if the v0.9 works.

Sorry: same problem with version 0.9.
Once I touch any of the sliders, the light goes off and I cannot interact with the light anymore, even if I kill and restart the app. I can only get the light to register with NeewerLite after I re-attaach that light to my Mac using the official "Neewer Live" app.

Just noting that the same happens on my system.

v1.1 add support for this light


Error attempting to locate Jupyter: Running cells with (...) requires jupyter package.

Environment data

VS Code version: 1.69.2
Jupyter Extension version (available under the Extensions sidebar): v2022.6.1201981810
Python Extension version (available under the Extensions sidebar): v2022.10.1
OS (Windows | Mac | Linux distro) and version: macOS Monterey (12.4 (21F79))
Python and/or Anaconda version: Python 3.10.5 / conda 4.13.0
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): conda
Jupyter server running: Local

Expected behaviour
Jupyter installation in conda environment is recognized by vscode-jupyter.
Actual behaviour
VS Code does not recognize correctly installed Jupyter packages in conda environments. Jupyter Notebooks in the browser can be launched successfully from the activated environment. When attempting to run a notebook in VS Code, an error is thrown:

info 12:44:44.504: Starting Jupyter Session id = 'startUsingPythonInterpreter:.jvsc74a57bd0ec1689aadfb31809087390f003aaaf48945ecfc3bbda01b3082716ecd7919b65./opt/miniconda3/envs/menv/python./opt/miniconda3/envs/menv/python.-m#ipykernel_launcher' (Python Path: /opt/miniconda3/envs/menv, EnvType: Conda, EnvName: 'menv', Version: 3.10.5) for '/Users/myuser/Downloads/Untitled.ipynb' (disableUI=true)
info 12:44:44.504: Checking for server existence.
info 12:44:44.504: Checking for server usability.
info 12:44:44.506: Server not usable (should ask for install now)
info 12:44:44.509: Process Execution: > /opt/miniconda3/envs/menv/bin/python -c "import jupyter"
> /opt/miniconda3/envs/menv/bin/python -c "import jupyter"
info 12:44:44.510: Process Execution: > /opt/miniconda3/envs/menv/bin/python -c "import notebook"
> /opt/miniconda3/envs/menv/bin/python -c "import notebook"
warn 12:44:44.610: Error occurred while trying to start the kernel, options.disableUI=true [i [Error]: Jupyter cannot be started. Error attempting to locate Jupyter: Running cells with 'Python 3.10.5 ('menv')' requires jupyter package.
	at S.startServer (/Users/myuser/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:98875)
	at processTicksAndRejections (node:internal/process/task_queues:96:5)
	at async S.createServer (/Users/myuser/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:97995)
	at async l.connect (/Users/myuser/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:75175)
	at async g.create (/Users/myuser/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:95736)
	at async p.createJupyterSession (/Users/myuser/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:160545)
	at async p.start (/Users/myuser/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:154488)
	at async Function.wrapKernelMethodImpl (/Users/myuser/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:336119)] {
  category: 'jupyterinstall'
}

Any attempt to proceed by clicking "install" ends with:
info 12:59:11.118:
# All requested packages already installed.

Steps to reproduce:

install miniconda (M1)
create a new virtual environment (python 3.9) and install jupyter
install VS Code (M1)
install the Jupyter extension
select the conda environment as kernel

Logs

Output for Jupyter in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Jupyter)

info 13:13:3.698: Execute Cell 1 /Users/myuser/Downloads/Untitled1.ipynb
info 13:13:3.699: Starting Jupyter Session id = 'startUsingPythonInterpreter:.jvsc74a57bd0ec1689aadfb31809087390f003aaaf48945ecfc3bbda01b3082716ecd7919b65./opt/miniconda3/envs/menv/python./opt/miniconda3/envs/menv/python.-m#ipykernel_launcher' (Python Path: /opt/miniconda3/envs/menv, EnvType: Conda, EnvName: 'menv', Version: 3.10.5) for '/Users/myuser/Downloads/Untitled1.ipynb' (disableUI=false)
info 13:13:3.699: Checking for server existence.
info 13:13:3.700: Checking for server usability.
info 13:13:3.700: Server not usable (should ask for install now)
info 13:13:3.703: Process Execution: > /opt/miniconda3/envs/menv/bin/python -c "import jupyter"
> /opt/miniconda3/envs/menv/bin/python -c "import jupyter"
info 13:13:3.704: Process Execution: > /opt/miniconda3/envs/menv/bin/python -c "import notebook"
> /opt/miniconda3/envs/menv/bin/python -c "import notebook"
warn 13:13:3.800: Error occurred while trying to start the kernel, options.disableUI=false [i [Error]: Jupyter cannot be started. Error attempting to locate Jupyter: Running cells with 'Python 3.10.5 ('menv')' requires jupyter package.
	at S.startServer (/Users/myuser/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:98875)
	at processTicksAndRejections (node:internal/process/task_queues:96:5)
	at async S.createServer (/Users/myuser/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:97995)
	at async l.connect (/Users/myuser/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:75175)
	at async g.create (/Users/myuser/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:95736)
	at async p.createJupyterSession (/Users/myuser/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:160545)
	at async p.start (/Users/myuser/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:154488)
	at async Function.wrapKernelMethodImpl (/Users/myuser/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:336119)] {
  category: 'jupyterinstall'
}
warn 13:13:3.800: Kernel Error, context = start [i [Error]: Jupyter cannot be started. Error attempting to locate Jupyter: Running cells with 'Python 3.10.5 ('menv')' requires jupyter package.
	at S.startServer (/Users/myuser/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:98875)
	at processTicksAndRejections (node:internal/process/task_queues:96:5)
	at async S.createServer (/Users/myuser/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:97995)
	at async l.connect (/Users/myuser/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:75175)
	at async g.create (/Users/myuser/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:95736)
	at async p.createJupyterSession (/Users/myuser/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:160545)
	at async p.start (/Users/myuser/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:154488)
	at async Function.wrapKernelMethodImpl (/Users/myuser/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:336119)] {
  category: 'jupyterinstall'
}
info 13:13:3.803: Process Execution: > /opt/miniconda3/envs/menv/bin/python -c "import jupyter"
> /opt/miniconda3/envs/menv/bin/python -c "import jupyter"
info 13:13:3.804: Process Execution: > /opt/miniconda3/envs/menv/bin/python -c "import notebook"
> /opt/miniconda3/envs/menv/bin/python -c "import notebook"
info 13:13:5.815: Process Execution: > /opt/miniconda3/condabin/conda install -c conda-forge --name menv jupyter -y
> /opt/miniconda3/condabin/conda install -c conda-forge --name menv jupyter -y
info 13:13:6.313: Collecting package metadata (current_repodata.json): ...working...
info 13:13:7.200: done

info 13:13:7.200: Solving environment: ...working...
info 13:13:8.65: done

info 13:13:8.253:
# All requested packages already installed.

info 13:13:8.457: Process Execution: > /opt/miniconda3/envs/menv/bin/python -c "import jupyter"
> /opt/miniconda3/envs/menv/bin/python -c "import jupyter"
info 13:13:8.469: Dispose Kernel '/Users/myuser/Downloads/Untitled1.ipynb' associated with '/Users/myuser/Downloads/Untitled1.ipynb'
error 13:13:8.469: Error in execution [i [Error]: Jupyter cannot be started. Error attempting to locate Jupyter: Running cells with 'Python 3.10.5 ('menv')' requires jupyter package.
	at S.startServer (/Users/myuser/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:98875)
	at processTicksAndRejections (node:internal/process/task_queues:96:5)
	at async S.createServer (/Users/myuser/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:97995)
	at async l.connect (/Users/myuser/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:75175)
	at async g.create (/Users/myuser/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:95736)
	at async p.createJupyterSession (/Users/myuser/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:160545)
	at async p.start (/Users/myuser/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:154488)
	at async Function.wrapKernelMethodImpl (/Users/myuser/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:336119)] {
  category: 'jupyterinstall'
}
error 13:13:8.469: Error in execution (get message for cell) [i [Error]: Jupyter cannot be started. Error attempting to locate Jupyter: Running cells with 'Python 3.10.5 ('menv')' requires jupyter package.
	at S.startServer (/Users/myuser/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:98875)
	at processTicksAndRejections (node:internal/process/task_queues:96:5)
	at async S.createServer (/Users/myuser/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:97995)
	at async l.connect (/Users/myuser/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:75175)
	at async g.create (/Users/myuser/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:95736)
	at async p.createJupyterSession (/Users/myuser/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:160545)
	at async p.start (/Users/myuser/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:154488)
	at async Function.wrapKernelMethodImpl (/Users/myuser/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:336119)] {
  category: 'jupyterinstall'
}

A complete clean re-install of VS Code and miniconda (including all environments) seems to resolve the issue.

Hmm, it sounds like we're trying to use pip when we should use conda?
@avasyanin do you have the output logs? Can you tell if it's using pip  to install?

@rchiodo, for conda env it tries to use conda:
`Visual Studio Code (1.69.2, undefined, desktop)
Jupyter Extension Version: 2022.6.1201981810.
Python Extension Version: 2022.10.1.
Workspace folder /Users/alex/Library/CloudStorage/OneDrive-Личная/Projects/MD
error 22:27:35.280: Exception while attempting zmq : [Error: No native build was found for platform=darwin arch=arm64 runtime=electron abi=103 uv=1 armv=8 libc=glibc node=16.13.2 electron=18.3.5
loaded from: /Users/alex/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/node_modules/zeromq
at Function.load.path (/Users/alex/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/node_modules/node-gyp-build/index.js:1:3163)
at load (/Users/alex/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/node_modules/node-gyp-build/index.js:1:648)
at Object.<anonymous> (/Users/alex/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/node_modules/zeromq/lib/native.js:1:198)
at Module.u._compile (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/loader.js:4:1313)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1216:10)
at Module.load (node:internal/modules/cjs/loader:1035:32)
at Module._load (node:internal/modules/cjs/loader:876:12)
at Function.c._load (node:electron/js2c/asar_bundle:5:13343)
at Function.i._load (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:111:32133)
at Function.v._load (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:111:28715)
at Function.b._load (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:106:61601)
at Module.require (node:internal/modules/cjs/loader:1059:19)
at p (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/loader.js:4:699)
at Object.<anonymous> (/Users/alex/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/node_modules/zeromq/lib/index.js:1:144)
at Module.u._compile (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/loader.js:4:1313)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1216:10)
at Module.load (node:internal/modules/cjs/loader:1035:32)
at Module._load (node:internal/modules/cjs/loader:876:12)
at Function.c._load (node:electron/js2c/asar_bundle:5:13343)
at Function.i._load (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:111:32133)
at Function.v._load (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:111:28715)
at Function.b._load (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:106:61601)
at Module.require (node:internal/modules/cjs/loader:1059:19)
at p (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/loader.js:4:699)
at Object.92747 (/Users/alex/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:39:361303)
at __webpack_require__ (/Users/alex/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:39:1151770)
at l.zmqSupported (/Users/alex/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:253757)
at l.isSupportedForLocalLaunch (/Users/alex/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:253500)
at l.get isSupported [as isSupported] (/Users/alex/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:253410)
at t.registerTypes (/Users/alex/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:268208)
at /Users/alex/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:39:1157232
at /Users/alex/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:39:1157985
at /Users/alex/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:39:1157993
at e.activate (/Users/alex/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:39:1158115)
at Function._callActivateOptional (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:97:17470)
at Function._callActivate (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:97:17131)
at /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:97:14945
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async b._activate (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:85:8180)
at async b._waitForDepsThenActivate (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:85:8122)
at async b._initialize (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:85:7486)]

Пользователь принадлежит к экспериментальной группе "jupyterTest"
Пользователь принадлежит к экспериментальной группе "jupyterEnhancedDataViewer"
info 22:27:35.526: LSP Notebooks experiment is disabled -- not in treatment group
info 22:27:35.717: Starting Jupyter Session id = 'startUsingPythonInterpreter:.jvsc74a57bd08c5c3ac57842afd298ce977f4db813296c2aa38680c36608f12b93dcfc17f7e9./Users/alex/miniforge3/envs/py310/python./Users/alex/miniforge3/envs/py310/python.-m#ipykernel_launcher' (Python Path: /Users/alex/miniforge3/envs/py310, EnvType: Conda, EnvName: 'py310', Version: 3.10.5) for '/Users/alex/Library/CloudStorage/OneDrive-Личная/Projects/MD/Diagram.ipynb' (disableUI=true)
info 22:27:35.717: Checking for server existence.
info 22:27:35.717: Checking for server usability.
info 22:27:35.848: Experiment status for python is {"enabled":true,"optInto":[],"optOutFrom":[]}
info 22:27:35.868: Preferred Remote kernel for /Users/alex/Library/CloudStorage/OneDrive-Личная/Projects/MD/Diagram.ipynb is undefined
info 22:27:35.868: Find preferred kernel for /Users/alex/Library/CloudStorage/OneDrive-Личная/Projects/MD/Diagram.ipynb with metadata {"interpreter":{"hash":"8c5c3ac57842afd298ce977f4db813296c2aa38680c36608f12b93dcfc17f7e9"},"kernelspec":{"display_name":"Python 3.10.4 ('py310')","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.10.5"},"orig_nbformat":4} & preferred interpreter /opt/homebrew/bin/python3
info 22:27:35.870: Preferred Remote kernel for /Users/alex/Library/CloudStorage/OneDrive-Личная/Projects/MD/Diagram.ipynb is undefined
info 22:27:35.870: Preferred kernel .jvsc74a57bd08c5c3ac57842afd298ce977f4db813296c2aa38680c36608f12b93dcfc17f7e9./Users/alex/miniforge3/envs/py310/python./Users/alex/miniforge3/envs/py310/python.-m#ipykernel_launcher is exact match
info 22:27:35.870: PreferredConnection: .jvsc74a57bd08c5c3ac57842afd298ce977f4db813296c2aa38680c36608f12b93dcfc17f7e9./Users/alex/miniforge3/envs/py310/python./Users/alex/miniforge3/envs/py310/python.-m#ipykernel_launcher found for NotebookDocument: /Users/alex/Library/CloudStorage/OneDrive-Личная/Projects/MD/Diagram.ipynb
info 22:27:35.989: Process Execution: > /opt/homebrew/bin/python3 -c "import jupyter"

/opt/homebrew/bin/python3 -c "import jupyter"
info 22:27:35.990: Process Execution: > /opt/homebrew/bin/python3 -c "import notebook"
/opt/homebrew/bin/python3 -c "import notebook"
info 22:27:35.991: Process Execution: > /opt/homebrew/bin/python3 -m pip list
/opt/homebrew/bin/python3 -m pip list
info 22:27:36.103: Server not usable (should ask for install now)
info 22:27:36.107: Process Execution: > /opt/homebrew/bin/python3 -c "import jupyter"
/opt/homebrew/bin/python3 -c "import jupyter"
info 22:27:36.117: Process Execution: > /opt/homebrew/bin/python3 -c "import notebook"
/opt/homebrew/bin/python3 -c "import notebook"
warn 22:27:36.172: Error occurred while trying to start the kernel, options.disableUI=true [i [Error]: Не удается запустить Jupyter. Ошибка при попытке найти Jupyter: Для выполнения ячеек с "Python 3.9.13 64-bit" требуется пакет jupyter и notebook.
at S.startServer (/Users/alex/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:98875)
at async S.createServer (/Users/alex/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:97995)
at async l.connect (/Users/alex/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:75175)
at async g.create (/Users/alex/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:95736)
at async p.createJupyterSession (/Users/alex/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:160545)
at async p.start (/Users/alex/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:154488)
at async Function.wrapKernelMethodImpl (/Users/alex/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:336119)] {
category: 'jupyterinstall'
}
error 22:27:36.425: Failed to get activated environment variables ourselves [Error: Command failed: conda activate py310 && echo 'e8b39361-0157-4923-80e1-22d70d46dee6' && python /Users/alex/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/pythonFiles/printEnvVariables.py

CommandNotFoundError: Your shell has not been properly configured to use 'conda activate'.
To initialize your shell, run
$ conda init <SHELL_NAME>

Currently supported shells are:

bash
fish
tcsh
xonsh
zsh
powershell

See 'conda init --help' for more information and options.
IMPORTANT: You may need to close and restart your shell after running 'conda init'.
at ChildProcess.exithandler (node:child_process:406:12)
at ChildProcess.emit (node:events:390:28)
at maybeClose (node:internal/child_process:1064:16)
at Socket.<anonymous> (node:internal/child_process:450:11)
at Socket.emit (node:events:390:28)
at Pipe.<anonymous> (node:net:687:12)] {

killed: false,
code: 1,
signal: null,
cmd: "conda activate py310 && echo 'e8b39361-0157-4923-80e1-22d70d46dee6' && python /Users/alex/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/pythonFiles/printEnvVariables.py"
}
error 22:27:36.426: Execing shell command, Class name = h, completed in 566ms, has a falsy return value, Arg 1: "~/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/pythonFiles/printEnvVariables.py", Arg 2: {"env":{"ELECTRON_RUN_AS_NODE":"1","USER":"alex","MallocNanoZone":"0","__CFBundleIdentifier":"com.microsoft.VSCode","COMMAND_MODE":"unix2003","DISPLAY":"/private/tmp/com.apple.launchd.OdmtF9uFeI/org.xquartz:0","LOGNAME":"alex","PATH":"/Users/alex/miniforge3/bin:/Users/alex/miniforge3/condabin:/opt/homebrew/bin:/opt/homebrew/sbin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/TeX/texbin:/opt/X11/bin:/Users/alex/orca_5_0_0_macosx_arm64_openmpi411","SSH_AUTH_SOCK":"/private/tmp/com.apple.launchd.wgWPPgUJt0/Listeners","SHELL":"/bin/zsh","HOME":"/Users/alex","__CF_USER_TEXT_ENCODING":"0x1F5:0x7:0x31","TMPDIR":"/var/folders/gy/s_tn_jqd225c2r7mv1236gj00000gn/T/","XPC_SERVICE_NAME":"application.com.microsoft.VSCode.65724099.65724105","XPC_FLAGS":"0x0","ORIGINAL_XDG_CURRENT_DESKTOP":"undefined","VSCODE_CWD":"/","VSCODE_NLS_CONFIG":"{"locale":"ru","availableLanguages":{"*":"ru"},"_languagePackId":"f1271d778ec77496b280bb178e5ed275.ru","_translationsConfigFile":"/Users/alex/Library/Application Support/Code/clp/f1271d778ec77496b280bb178e5ed275.ru/tcf.json","_cacheRoot":"/Users/alex/Library/Application Support/Code/clp/f1271d778ec77496b280bb178e5ed275.ru","_resolvedLanguagePackCoreLocation":"/Users/alex/Library/Application Support/Code/clp/f1271d778ec77496b280bb178e5ed275.ru/3b889b090b5ad5793f524b5d1d39fda662b96a2a","_corruptedFile":"/Users/alex/Library/Application Support/Code/clp/f1271d778ec77496b280bb178e5ed275.ru/corrupted.info","_languagePackSupport":true}","VSCODE_CODE_CACHE_PATH":"/Users/alex/Library/Application Support/Code/CachedData/3b889b090b5ad5793f524b5d1d39fda662b96a2a","VSCODE_IPC_HOOK":"/Users/alex/Library/Application Support/Code/1.69.2-main.sock","VSCODE_PID":"73204","SHLVL":"0","PWD":"/","OLDPWD":"/","HOMEBREW_PREFIX":"/opt/homebrew","HOMEBREW_CELLAR":"/opt/homebrew/Cellar","HOMEBREW_REPOSITORY":"/opt/homebrew","MANPATH":"/opt/homebrew/share/man::","INFOPATH":"/opt/homebrew/share/info:","TERM":"xterm-256color","CLICOLOR":"1","CONDA_EXE":"/Users/alex/miniforge3/bin/conda","_CE_M":"","CE_CONDA":"","CONDA_PYTHON_EXE":"/Users/alex/miniforge3/bin/python","CONDA_SHLVL":"1","CONDA_PREFIX":"/Users/alex/miniforge3","CONDA_DEFAULT_ENV":"base","CONDA_PROMPT_MODIFIER":"(base) ","":"/Applications/Visual Studio Code.app/Contents/MacOS/Electron","VSCODE_AMD_ENTRYPOINT":"vs/workbench/api/node/extensionHostProcess","VSCODE_HANDLES_UNCAUGHT_ERRORS":"true","PYTHONWARNINGS":"ignore"},"shell":"bash","timeout":60000,"maxBuffer":1000000,"throwOnStdErr":false} [Error: Command failed: conda activate py310 && echo 'e8b39361-0157-4923-80e1-22d70d46dee6' && python /Users/alex/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/pythonFiles/printEnvVariables.py
CommandNotFoundError: Your shell has not been properly configured to use 'conda activate'.
To initialize your shell, run
$ conda init <SHELL_NAME>

Currently supported shells are:

bash
fish
tcsh
xonsh
zsh
powershell

See 'conda init --help' for more information and options.
IMPORTANT: You may need to close and restart your shell after running 'conda init'.
at ChildProcess.exithandler (node:child_process:406:12)
at ChildProcess.emit (node:events:390:28)
at maybeClose (node:internal/child_process:1064:16)
at Socket.<anonymous> (node:internal/child_process:450:11)
at Socket.emit (node:events:390:28)
at Pipe.<anonymous> (node:net:687:12)] {

killed: false,
code: 1,
signal: null,
cmd: "conda activate py310 && echo 'e8b39361-0157-4923-80e1-22d70d46dee6' && python /Users/alex/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/pythonFiles/printEnvVariables.py"
}
info 22:27:36.466: Registering dummy command feature
info 22:27:36.543: Registering dummy command feature
info 22:27:36.682: Preferred Remote kernel for /Users/alex/Library/CloudStorage/OneDrive-Личная/Projects/MD/Diagram.ipynb is undefined
info 22:27:36.682: Find preferred kernel for /Users/alex/Library/CloudStorage/OneDrive-Личная/Projects/MD/Diagram.ipynb with metadata {"interpreter":{"hash":"8c5c3ac57842afd298ce977f4db813296c2aa38680c36608f12b93dcfc17f7e9"},"kernelspec":{"display_name":"Python 3.10.4 ('py310')","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.10.5"},"orig_nbformat":4} & preferred interpreter /opt/homebrew/bin/python3
info 22:27:36.684: Preferred Remote kernel for /Users/alex/Library/CloudStorage/OneDrive-Личная/Projects/MD/Diagram.ipynb is undefined
info 22:27:36.684: Preferred kernel .jvsc74a57bd08c5c3ac57842afd298ce977f4db813296c2aa38680c36608f12b93dcfc17f7e9./Users/alex/miniforge3/envs/py310/python./Users/alex/miniforge3/envs/py310/python.-m#ipykernel_launcher is exact match
info 22:27:36.685: Preferred Remote kernel for /Users/alex/Library/CloudStorage/OneDrive-Личная/Projects/MD/Diagram.ipynb is undefined
info 22:27:37.395: Process Execution: > ~/miniforge3/envs/py310/bin/python -m pip list

~/miniforge3/envs/py310/bin/python -m pip list
info 22:27:43.656: Execute Cell 0 /Users/alex/Library/CloudStorage/OneDrive-Личная/Projects/MD/Diagram.ipynb
info 22:27:43.657: Starting Jupyter Session id = 'startUsingPythonInterpreter:.jvsc74a57bd08c5c3ac57842afd298ce977f4db813296c2aa38680c36608f12b93dcfc17f7e9./Users/alex/miniforge3/envs/py310/python./Users/alex/miniforge3/envs/py310/python.-m#ipykernel_launcher' (Python Path: /Users/alex/miniforge3/envs/py310, EnvType: Conda, EnvName: 'py310', Version: 3.10.5) for '/Users/alex/Library/CloudStorage/OneDrive-Личная/Projects/MD/Diagram.ipynb' (disableUI=false)
info 22:27:43.657: Checking for server existence.
info 22:27:43.657: Checking for server usability.
info 22:27:43.657: Server not usable (should ask for install now)
info 22:27:43.660: Process Execution: > /opt/homebrew/bin/python3 -c "import jupyter"
/opt/homebrew/bin/python3 -c "import jupyter"
info 22:27:43.661: Process Execution: > /opt/homebrew/bin/python3 -c "import notebook"
/opt/homebrew/bin/python3 -c "import notebook"
warn 22:27:43.681: Error occurred while trying to start the kernel, options.disableUI=false [i [Error]: Не удается запустить Jupyter. Ошибка при попытке найти Jupyter: Для выполнения ячеек с "Python 3.9.13 64-bit" требуется пакет jupyter и notebook.
at S.startServer (/Users/alex/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:98875)
at async S.createServer (/Users/alex/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:97995)
at async l.connect (/Users/alex/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:75175)
at async g.create (/Users/alex/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:95736)
at async p.createJupyterSession (/Users/alex/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:160545)
at async p.start (/Users/alex/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:154488)
at async Function.wrapKernelMethodImpl (/Users/alex/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:336119)] {
category: 'jupyterinstall'
}
warn 22:27:43.681: Kernel Error, context = start [i [Error]: Не удается запустить Jupyter. Ошибка при попытке найти Jupyter: Для выполнения ячеек с "Python 3.9.13 64-bit" требуется пакет jupyter и notebook.
at S.startServer (/Users/alex/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:98875)
at async S.createServer (/Users/alex/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:97995)
at async l.connect (/Users/alex/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:75175)
at async g.create (/Users/alex/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:95736)
at async p.createJupyterSession (/Users/alex/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:160545)
at async p.start (/Users/alex/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:154488)
at async Function.wrapKernelMethodImpl (/Users/alex/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:336119)] {
category: 'jupyterinstall'
}
info 22:27:43.684: Process Execution: > /opt/homebrew/bin/python3 -c "import pip"
/opt/homebrew/bin/python3 -c "import pip"
info 22:27:43.684: Process Execution: > /opt/homebrew/bin/python3 -c "import jupyter"
/opt/homebrew/bin/python3 -c "import jupyter"
info 22:27:43.685: Process Execution: > /opt/homebrew/bin/python3 -c "import notebook"
/opt/homebrew/bin/python3 -c "import notebook"
info 22:27:49.524: Process Execution: > ~/miniforge3/envs/py310/bin/python -c "import jupyter"
~/miniforge3/envs/py310/bin/python -c "import jupyter"
info 22:27:49.528: Process Execution: > ~/miniforge3/envs/py310/bin/python -c "import notebook"
~/miniforge3/envs/py310/bin/python -c "import notebook"
info 22:27:52.626: Process Execution: > /conda install -c conda-forge --name py310 jupyter -y
/conda install -c conda-forge --name py310 jupyter -y
error 22:27:52.627: Error in execution [Error: spawn /conda ENOENT
at Process.ChildProcess._handle.onexit (node:internal/child_process:282:19)
at onErrorNT (node:internal/child_process:477:16)
at processTicksAndRejections (node:internal/process/task_queues:83:21)] {
errno: -2,
code: 'ENOENT',
syscall: 'spawn /conda',
path: '/conda',
spawnargs: [
'install',
'-c',
'conda-forge',
'--name',
'py310',
'jupyter',
'-y'
]
}
error 22:27:52.628: Error in execution (get message for cell) [Error: spawn /conda ENOENT
at Process.ChildProcess._handle.onexit (node:internal/child_process:282:19)
at onErrorNT (node:internal/child_process:477:16)
at processTicksAndRejections (node:internal/process/task_queues:83:21)] {
errno: -2,
code: 'ENOENT',
syscall: 'spawn /conda',
path: '/conda',
spawnargs: [
'install',
'-c',
'conda-forge',
'--name',
'py310',
'jupyter',
'-y'
]
}
`

@rchiodo, for conda env it tries to use conda, see log file attached.
jupyter.log

@rchiodo, probably it's the same, it worked well, nothing changed with conda before VSCode update. This issue happened only with VSCode update.

@avasyanin Your error is not the same as what @michaelweinold is seeing. Your error is failing to install because conda has not been initialized to support bash. If you create a conda terminal and then run conda init bash, it should fix our install.

@michaelweinold I'm not sure why yours was failing and since it's working now, I'm going to close this issue. From what I can tell running this:
/opt/miniconda3/envs/menv/bin/python -c "import jupyter"

Was failing even though the menv environment had jupyter installed.
If it repros again, we'd need the output from running that exact command.
We should probably log the stderr when it fails. This code here:
https://github.com/microsoft/vscode-jupyter/blob/dabbf13b1d0bfe774a9a479f2be6785f6c580513/src/platform/common/process/pythonEnvironment.node.ts#L63

@rchiodo you are right. conda init bash helped in my case. But how it worked before? Anyway, thanks for clarification!

But how it worked before?

We cache the 'jupyter' environment we use. The cache may have been invalidated when updating VS code. So we no longer had the 'jupyter' environment to use and had to find/make a new one. This making of a new one seems to be where it was failing for you.

I am getting the same error. Again after reinstalling VS code. I dont know why i get this error repeatedly


iOS & OS X

Hello
It is possible to pass data between an app of OS X and app iOS?

MMWormhole uses the global notification on a device, so not with this technique.
You could use iCloud/CloudKit, Handoff or a server depending on what you are trying to achieve.


Update Build Controller to v0.6.0

Changes

Update release manifest to use Shipwright Build v0.6.0.
Move the namespace and TektonConfig RBAC definitions to the
kubebuilder annotations.
Added RBAC to manage the shipwright-build-controller deployment.
Added RBAC manage the shipwright-build-controller service account.
Added RBAC to create the namespaced role/rolebindings for the build
controller

/kind feature
Submitter Checklist

[x] Includes tests if functionality changed/was added
[ ] Includes docs if changes are user-facing
[x] Set a kind label on this PR
[x] Release notes block has been filled in, or marked NONE

See the contributor guide
for details on coding conventions, github and prow interactions, and the code review process.
Release Notes
Upgrade the deployed build controller to v0.6.0

/approve
Self-approving


Use ephemeral ids for addressing offline messages

Currently every offline message is addressed to the peer id of its recipient. This would allow a network spy to view the exact quantity of messages any peer is receiving, which is useful information (eg it is likely proportional to trade volume). It would also allow a relay like Duo to know who its users is talking to, and how often.
I suggest that the following protocol is used:

First message (online or offline) to peer - use peer id (A)
Peer response (offline or online) includes a randomly generated id (B) (which it stores in its db). This id is of a different format to normal peer ids.
User stores new id (B) in its db, associated with the peer id (A)
Upon any following offline messages from user to peer, this new id (B) is used for addressing. New online messages to the peer include the id (B) within the body for acknowledgement.
If the user recieves a new message (online or offline, including acks) from the peer, the ephemeral id is updated (C)
Upon any following offline messages from user to peer, this new id (C) is used for addressing. New online messages to the peer include the id (C) within the body for acknowledgement.
When the peer receives online (with acknowledgement of C) or offline (addressed to C) messages from the user, they stop looking for the old id (B) in DHT

Peers would search DHT for a list of ephemeral ids as well as their peer id, 1-2 (1 if the last communication was from user to them, 2 in the opposite case) for every user they have previously communicated with. To prevent growing network load due to this, ids can have a timeout, less than the offline message timeout, after which point offline messages from the user to the peer will revert to the peer id, and the peer will stop searching for the ephemeral address.
A snooper can now only tell when a peer receives a message from someone they haven't communicated from before (though it's occasionally someone they have, due to the timeout). A relay can only acertain the set of peers that a user has ever talked to, but not whether it occured multiple times (and thus, it could be a follow or something similarly harmless).
I also suggest that pings return an ephemeral id, so that users can obtain an id when the vendor is online, for use later when they are offline.
This solves a lot of the aims of #275.

DHT keys use prefix filtering so it isn't possible to determine who a message is intended for with any accuracy.

I appreciate that this means that a key is not reversable into the peer id (without essentially brute forcing it with every peer id on the network), but surely even with prefix filtering multiple messages to the same peer are addressed to the same key. This would allow you to work out which keys are most active, and then brute forcing it to obtain a peer id is not particularly difficult (if you want to acertain who might be behind a very active key, there are probably currently only a handful of vendors it could be)

It's not just the hash of the key. If the peerId is 818b5cc5f21d3e6e4e6071c06294528d44595022218446d8b79304d2b766327a
Only 81 might go into the DHT. There's no brute forcing you can do to tell you what the rest of the key is. It could be one of any number of people.

I see, that makes more sense, thanks


Unable to Publish "beyondcode/laravel-ask-database" Package in AskQuestion Module

I'm encountering difficulties while attempting to integrate the "beyondcode/laravel-ask-database" package into my AskQuestion module. Here's a breakdown of the steps I've followed:
Updated the composer.json file in the AskQuestion module with the correct package name and verified versions.
Navigated to the module directory [/Module/AskQuestion] and executed "composer install" to install the package.
Went to the project directory [/Project] and ran the command "php artisan module:update AskQuestion" to ensure the module is updated.
However, I'm facing an issue when trying to publish the "laravel-ask-database" package within the AskQuestion module. Despite attempting manual registration of package providers, aliases, and configuration in the module's service provider file, the package doesn't seem to load in the module.
Even after manual registration steps, the package is not loaded within the AskQuestion module.
Any guidance or assistance in resolving this issue would be greatly appreciated.

Could you provide a public repo so I can look into what you've tried.


Include source code in robotium-solo-2.x.jar

From<EMAIL_ADDRESS>on September 16, 2011 04:51:12
It look like robotium-solo-2.5.jar does not include the source files. Would it be possible for you to include them in the jar? This way we don't have to download is separately.
If you use Maven this may help: http://www.digitalpains.net/programming/maven/how-to-make-jar-files-include-both-java-sources-and-class-files-with-maven Also Eclipse jar bundeling has the option to include src and ressources: http://www.vogella.de/articles/Eclipse/article.html#firstjava_export Best regards, Lars
Original issue: http://code.google.com/p/robotium/issues/detail?id=158

From<EMAIL_ADDRESS>on September 16, 2011 06:09:24
This is not something that we are planning. Most Robotium users do not care about the source code so it would just be an unnecessary overhead if included. The source code can be synced and downloaded from github.
Status: WontFix

From<EMAIL_ADDRESS>on September 18, 2011 23:10:10
Thanks


BRD4 cohort potential problem?

When I load the NIPBL cohort, there are 22 phenopackets, but only 18 individuals get loaded. Yet there is no error warning. Can we take a closer look?
Loaded 22 phenopackets (NIPBL).
Individuals Processed: 100%|██████████| 22/22 [00:00<00:00, 380.69individuals/s]
Loaded 18 individuals
Validated under permissive policy
No errors or warnings were found

NIPBL loaded and validated OK on my end, so this is probably a mismatch of cohorts (NIPBL -  22 individuals, BRD4 - 18 individuals as of Phenopacket Store 0.1.21).
Let's reopen if the issue shows up again...


[BUG] Linking fails on Linux building for x86_64-pc-windows-msvc

Describe the bug
I am trying to build for x86_64-pc-windows-msvc from Linux.
To Reproduce
Install windows sdk with cargo xwin, and use following cargo config:
[build]
target = "x86_64-pc-windows-msvc"

[target.x86_64-pc-windows-msvc]
runner = "wine64"
linker = "lld-link-15"
rustflags = [
  "-Lnative=/home/louis/.xwin/crt/lib/x86_64",
  "-Lnative=/home/louis/.xwin/sdk/lib/um/x86_64",
  "-Lnative=/home/louis/.xwin/sdk/lib/ucrt/x86_64"
]

[env]
CC_x86_64_pc_windows_msvc = "clang-cl-15"
CXX_x86_64_pc_windows_msvc = "clang-cl-15"
CFLAGS_x86_64_pc_windows_msvc = "-Wno-everything -flto=thin -fuse-ld=lld-link -I/home/louis/.xwin/crt/include -I/home/louis/.xwin/sdk/include/um -I/home/louis/.xwin/sdk/include/ucrt -I/home/louis/.xwin/sdk/include/shared"
CXXFLAGS_x86_64_pc_windows_msvc = "-Wno-everything -flto=thin -fuse-ld=lld-link -I/home/louis/.xwin/crt/include -I/home/louis/.xwin/sdk/include/um -I/home/louis/.xwin/sdk/include/ucrt -I/home/louis/.xwin/sdk/include/shared"
AR_x86_64_pc_windows_msvc = "llvm-lib-15"

Run cargo test --features fltk-bundled,static-msvcrt
Output
error: could not compile `fltk` (example "calculator") due to previous error
error: linking with `lld-link-15` failed: exit status: 1
  = note: lld-link-15: error: duplicate symbol: __cxa_pure_virtual
          >>> defined at libfltk_sys-264599c1122f0e01.rlib(Fl_Widget.cxx.obj)

          lld-link-15: error: duplicate symbol: __cxa_pure_virtual
          >>> defined at libfltk_sys-264599c1122f0e01.rlib(Fl_Overlay_Window.cxx.obj)

          lld-link-15: error: duplicate symbol: __cxa_pure_virtual
          >>> defined at libfltk_sys-264599c1122f0e01.rlib(Fl_Image_Surface.cxx.obj)

          lld-link-15: error: duplicate symbol: __cxa_pure_virtual
          >>> defined at libfltk_sys-264599c1122f0e01.rlib(Fl_Valuator.cxx.obj)

          lld-link-15: error: duplicate symbol: __cxa_pure_virtual
          >>> defined at libfltk_sys-264599c1122f0e01.rlib(Fl_Browser_.cxx.obj)

          lld-link-15: error: duplicate symbol: __cxa_pure_virtual
          >>> defined at libfltk_sys-264599c1122f0e01.rlib(Fl_Copy_Surface.cxx.obj)

Desktop info

OS: Ubuntu 22.04.2 LTS
FLTK git tag 1.4.7.

Hi
Never tried cross-compiling for msvc from any other os. What do you get if you remove the static-msvcrt feature?

I get the same. But looking more closely at the output there is also this error:
error: could not compile `fltk` (example "threads_windows") due to previous error
error: linking with `lld-link-15` failed: exit status: 1
  |
  = note: LC_ALL="C" PATH="/home/louis/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/bin:/home/louis/.cargo/bin:/home/louis/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin" VSLANG="1033" "lld-link-15" "-flavor" "link" "/NOLOGO" "/tmp/rustckp5ziS/symbols.o" "/home/louis/Projects/fltk-rs/target/x86_64-pc-windows-msvc/debug/deps/fltk_sys-96b51adae66666be.26ibyze46vol9evk.rcgu.o" "/home/louis/Projects/fltk-rs/target/x86_64-pc-windows-msvc/debug/deps/fltk_sys-96b51adae66666be.27ea2srogtr1pg9d.rcgu.o" "/home/louis/Projects/fltk-rs/target/x86_64-pc-windows-msvc/debug/deps/fltk_sys-96b51adae66666be.3c569anf9k93t1ba.rcgu.o" "/home/louis/Projects/fltk-rs/target/x86_64-pc-windows-msvc/debug/deps/fltk_sys-96b51adae66666be.3g5rof2sytd3sa59.rcgu.o" "/home/louis/Projects/fltk-rs/target/x86_64-pc-windows-msvc/debug/deps/fltk_sys-96b51adae66666be.tc6zzpxdgssb3qk.rcgu.o" "/home/louis/Projects/fltk-rs/target/x86_64-pc-windows-msvc/debug/deps/fltk_sys-96b51adae66666be.4zntjt53vxrmi1gs.rcgu.o" "/LIBPATH:/home/louis/Projects/fltk-rs/target/x86_64-pc-windows-msvc/debug/deps" "/LIBPATH:/home/louis/Projects/fltk-rs/target/debug/deps" "/LIBPATH:/home/louis/.xwin/crt/lib/x86_64" "/LIBPATH:/home/louis/.xwin/sdk/lib/um/x86_64" "/LIBPATH:/home/louis/.xwin/sdk/lib/ucrt/x86_64" "/LIBPATH:/home/louis/Projects/fltk-rs/target/x86_64-pc-windows-msvc/debug/build/fltk-sys-c0d1beed8cb6e931/out/build" "/LIBPATH:/home/louis/Projects/fltk-rs/target/x86_64-pc-windows-msvc/debug/build/fltk-sys-c0d1beed8cb6e931/out/build/Release" "/LIBPATH:/home/louis/Projects/fltk-rs/target/x86_64-pc-windows-msvc/debug/build/fltk-sys-c0d1beed8cb6e931/out/lib" "/LIBPATH:/home/louis/Projects/fltk-rs/target/x86_64-pc-windows-msvc/debug/build/fltk-sys-c0d1beed8cb6e931/out/lib64" "/LIBPATH:/home/louis/Projects/fltk-rs/target/x86_64-pc-windows-msvc/debug/build/fltk-sys-c0d1beed8cb6e931/out/lib/Release" "/LIBPATH:/home/louis/Projects/fltk-rs/target/x86_64-pc-windows-msvc/debug/build/fltk-sys-c0d1beed8cb6e931/out/lib64/Release" "/LIBPATH:/home/louis/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-pc-windows-msvc/lib" "/WHOLEARCHIVE:cfltk.lib" "/WHOLEARCHIVE:fltk.lib" "/WHOLEARCHIVE:fltk_images.lib" "/WHOLEARCHIVE:fltk_png.lib" "/WHOLEARCHIVE:fltk_jpeg.lib" "/WHOLEARCHIVE:fltk_z.lib" "ws2_32.lib" "comctl32.lib" "gdi32.lib" "oleaut32.lib" "ole32.lib" "uuid.lib" "shell32.lib" "advapi32.lib" "comdlg32.lib" "winspool.lib" "user32.lib" "kernel32.lib" "odbc32.lib" "gdiplus.lib" "/home/louis/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-pc-windows-msvc/lib/libtest-5459090c31682786.rlib" "/home/louis/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-pc-windows-msvc/lib/libgetopts-ac0f63d82480c4f5.rlib" "/home/louis/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-pc-windows-msvc/lib/libunicode_width-936458f0bd6f1655.rlib" "/home/louis/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-pc-windows-msvc/lib/librustc_std_workspace_std-62e25712b16d597a.rlib" "/home/louis/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-pc-windows-msvc/lib/libstd-f54c5a8dc7e7febf.rlib" "/home/louis/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-pc-windows-msvc/lib/libpanic_unwind-92f7800729779464.rlib" "/home/louis/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-pc-windows-msvc/lib/librustc_demangle-6da5127b1b379d8e.rlib" "/home/louis/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-pc-windows-msvc/lib/libstd_detect-efa74c8d8702db5b.rlib" "/home/louis/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-pc-windows-msvc/lib/libhashbrown-e9ed0b4fbfe1d158.rlib" "/home/louis/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-pc-windows-msvc/lib/librustc_std_workspace_alloc-23c6870c75efea7d.rlib" "/home/louis/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-pc-windows-msvc/lib/libminiz_oxide-19857ab63c6bf99c.rlib" "/home/louis/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-pc-windows-msvc/lib/libadler-0d8b8ed2a2fb22e9.rlib" "/home/louis/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-pc-windows-msvc/lib/libunwind-3a3d97b2ce691588.rlib" "/home/louis/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-pc-windows-msvc/lib/libcfg_if-60ba5e33f92355d7.rlib" "/home/louis/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-pc-windows-msvc/lib/liblibc-94c0a2e24d7696be.rlib" "/home/louis/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-pc-windows-msvc/lib/liballoc-edd8efb6a2cb3252.rlib" "/home/louis/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-pc-windows-msvc/lib/librustc_std_workspace_core-cb8dd18d30da7a99.rlib" "/home/louis/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-pc-windows-msvc/lib/libcore-75c0b134deed8bd9.rlib" "/home/louis/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-pc-windows-msvc/lib/libcompiler_builtins-96d2ffc8ffc7b9b5.rlib" "kernel32.lib" "kernel32.lib" "advapi32.lib" "bcrypt.lib" "kernel32.lib" "ntdll.lib" "userenv.lib" "ws2_32.lib" "kernel32.lib" "msvcrt.lib" "/NXCOMPAT" "/LIBPATH:/home/louis/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-pc-windows-msvc/lib" "/OUT:/home/louis/Projects/fltk-rs/target/x86_64-pc-windows-msvc/debug/deps/fltk_sys-96b51adae66666be.exe" "/OPT:REF,NOICF" "/DEBUG"
  = note: lld-link-15: error: could not open 'cfltk.lib': No such file or directory
          lld-link-15: error: could not open 'fltk.lib': No such file or directory
          lld-link-15: error: could not open 'fltk_images.lib': No such file or directory
          lld-link-15: error: could not open 'fltk_png.lib': No such file or directory
          lld-link-15: error: could not open 'fltk_jpeg.lib': No such file or directory
          lld-link-15: error: could not open 'fltk_z.lib': No such file or directory

So the duplicate symbol errors are gone, it only fails to find the generated libs?

Sorry it is not clear, they are not gone. I am only showing one error but there are repeating. There is the first one and the second one.

I could get rid of the first error, but not the second. I think basically the build script is not building fltk libraries for this target.

The duplicate symbol error?
I tried searching online and reading the cargo xwin source code. It seems cargo xwin creates a cmake toolchain script which overrides some of the flags used by cfltk.
How were you able to fix it?
Regarding the second error, it seems a build.rs issue, in that it can find the libs in the passed search dirs.
It would be useful to lnow where the generated libs are installed, and possibly modify the build script accordingly.

I was just using xwin, not cargo xwin

And how was the issue resolved?

Anyways, this isn't an fltk-rs issue, since whatever you're using (xwin or cargo-xwin, you never specified the steps to reproduce the issue) differ in their behavior from MSVC. You should probably open an issue there. And since you're using the fltk-bundled flag, the fltk libs are already built. It should be just a matter of finding them.


Add apt-get dependency link for Ubuntu systems, rather than building directly from source

Why did I want this again? Closing until if-it-aint-broke-don't-fix-it stops working in my brain again


Biopsy form: other observations

Background
As part of recording a biopsy record BMMRO need to record other observations specific to the biopsy event
Acceptance criteria
AC1: add fields (create)
given I am logged into the BMMRO app and within the context of an encounter
when I click the "Add" button to create a new biopsy record
then I can see a section called "Other observations" with the following fields displayed:

"other observations" - free text box with maximum character limit

Acceptance criteria
AC1: add fields (create)
given I am logged into the BMMRO app and within the context of an encounter
when I click the "Add" button to create a new biopsy record
then I can see a section called "Other observations" with the following fields displayed beneath a section header of "Other observations"

(no question header as we have the section header): free text entry box

AC2: on edit: check the updated values are in firebase
given I open an existing, un-exported, biopsy record
when I change values in the other observations section
and click save
then the values are updated in firebase and the export script
AC3: open biopsy form in view mode for exported records
given I have already exported a biopsy record
when I open a biopsy record which has previously been exported
then the biopsy form & the other observations section cannot be edited
and exported records are not in the exported data
AC5: MS Access database (biopsy csv)
given I run the export script
then the other observations fields are visible in the exported data, with the below mapping:

AC6: update specimen csv
given I run the export script
then the "other observations" are included in the specimen csv, mapping below:

Dev QA passed


Implementing backlight management

Implementing backlight management thought third button in Clock app. Improving screen flickering as well. Code cleanup

Adding auto backlight management in second commit. Left run for days without facing any issue.

Hi @malcolmholmes If you have time to review this PR, this could be great, it definitively solve #15 and brings improvement. Thanks


how to set verify verbosity in code?

Just got this notification for some reason. What is this 'yorth' anyway?


add script for server benchmarking

Simple script for running a server benchmark so I don't have to keep running commands in two different tabs for this.

aaaand.. merged!


Spools are no longer available

System Health details
System Information

version
core-2024.11.1

installation_type
Home Assistant OS

dev
false

hassio
true

docker
true

user
root

virtualenv
false

python_version
3.12.4

os_name
Linux

os_version
6.6.54-haos

arch
x86_64

timezone
Europe/Berlin

config_dir
/config

Home Assistant Community Store

GitHub API
ok

GitHub Content
ok

GitHub Web
ok

HACS Data
ok

GitHub API Calls Remaining
4990

Installed Version
2.0.1

Stage
running

Available Repositories
1470

Downloaded Repositories
28

Home Assistant Cloud

logged_in
false

can_reach_cert_server
ok

can_reach_cloud_auth
ok

can_reach_cloud
ok

Home Assistant Supervisor

host_os
Home Assistant OS 13.2

update_channel
stable

supervisor_version
supervisor-2024.11.3

agent_version
1.6.0

docker_version
27.2.0

disk_total
30.8 GB

disk_used
6.4 GB

healthy
true

supported
true

host_connectivity
true

supervisor_connectivity
true

ntp_synchronized
true

virtualization
kvm

board
ova

supervisor_api
ok

version_api
ok

installed_addons
Matter Server (6.6.0), File editor (5.8.0), Advanced SSH & Web Terminal (19.0.0), Get HACS (1.3.1), Mosquitto broker (6.4.1), Node-RED (18.1.1), MQTT Explorer (browser-1.0.3)

Dashboards

dashboards
1

resources
19

views
5

mode
storage

Recorder

oldest_recorder_run
2. November 2024 um 21:11

current_recorder_run
11. November 2024 um 23:35

estimated_db_size
385.57 MiB

database_engine
sqlite

database_version
3.45.3

Checklist

[X] I have enabled debug logging for my installation.
[X] I have filled out the issue template to the best of my ability.
[X] This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
[X] This issue is not a duplicate issue of currently previous issues..

Describe the issue
Occasionally the error occurs that the HA integration cannot connect to the API. An internal server error occurs. After a new fetch (after 15 minutes) it usually works again. The error occurs rather sporadically. According to log details 14x within ~22 hours.
I will submit more DEBUG logs later. Since I activated it first, only the ERROR was visible in the log.
Reproduction steps

Don't know how to reproduce the error

Debug logs
2024-11-12 21:41:01.210 ERROR (MainThread) [custom_components.spoolman.coordinator] Error fetching Spoolman data data: Error fetching data from API: 500, message='Internal Server Error', url='http://<IP_ADDRESS>:8000/api/v1/spool?allow_archived=False'

Diagnostics dump
No response

Thank you for that issue! It seems that spoolman is occasionally not available (because of that 500 error) or HA can't connect to it. That's not a problem of the integration nor I can mitigate this. The only thing in can do is to throw that exception.
You need track that error down with spoolman and check the connectivity. Please check the logs of spoolman if there are errors.
Sorry!

Thank you for your reply! I gonna close this. Bit you can keep us informed what the reason was (or reference this issue at the spoolman repo)


*: add peer perfix for network metrics between peers

/cc @heyitsanthony @gyuho
We will add network metrics for clients too.

s/perfix/prefix in commit title
lgtm