Too many errors for endpoint 'https://...': retrying later

I would like to understand better the cause of the following error message...
2023-09-10 01:39:06 GMT | CORE | ERROR | (pkg/forwarder/worker.go:179 in process) | Too many errors for endpoint 'https://<IP_ADDRESS>:3834/api/v1/series?api_key=<blahblah>': retrying later

The agent is running on Windows and is configured to use an haproxy serving TLS endpoints with a self-signed certificate. The certificate has been added to the Windows system trust chain.
Looking into the source code, it appears that actually it (seems to) mean that the target has been blocked by a 'circuit breaker' intended to blacklist certain targets (?!).
	// Run the endpoint through our blockedEndpoints circuit breaker
	target := t.GetTarget()
	if w.blockedList.isBlock(target) {
		requeue()
		log.Errorf("Too many errors for endpoint '%s': retrying later", target)
	} else if err := t.Process(ctx, w.Client); err != nil {
		w.blockedList.close(target)
		requeue()
		log.Errorf("Error while processing transaction: %v", err)
	} else {
		w.blockedList.recover(target)
	}

Further investigation is still required, but I'm filing this as a 'support' request, even though I feel it is bordering on a 'bug report' as the error message is just far too ambiguous, and lacks any detail that would help normal users understand what needs to be investigated and fixed. Why has my target been blocked?!
Also, doing some Googling I'm not the only person that's scratched their head over this one. The usual advice seems to be to send Datadog Support a flare. Really, that's not the best advice. If everyone has to file private support requests and generate flares every time they come across a poorly written error message, that's going to create a huge amount of unnecessary resistance, work and lost time for both Datadog support and us customers. So, I'm filing this here as a 'support request' on GitHub instead to try to save more people's precious time.
Please feel free to move to 'bug report' if I've misjudged it.

Hey @rossigee,
First, thanks for the time you've spent investigating this to open a meaningful issue 👍
I'll explain a bit this piece of code but TL;DR: blockedList is an unfortunate naming (not really a blocking list, but more of a list maintaining a health status for every endpoint), and this error message is sent when the backoff policy (avoiding too many retries on a continuously failing endpoint) has decided to slow down on continuing to try to use this endpoint because its health status looks bad.
For a more detailed answer:
In order to reach the Datadog intake, there is a part of the Agent called the Forwarder which deals with all the endpoints.
When everything is working fine, the payload sent by the Forwarder reaches the intake and an info log is displayed, either this one or this one after many payloads have been successful sent.
However, if there is an error reaching an endpoint, an error message is thrown, there are multiple possible errors, this one, that one, or that one (the actual call to print that one out is later on in the branch). These contain useful information to better understand what's not working with the connection and you should be able to see a few of them in your Agent logs.
That's when the "blocking list"/backoff policy enters the scene: when there is such an error, a mechanism is counting per endpoint how many times in a row these fails happens and it slows down between each try, because if these requests continuously fail, there are no reasons continuing to try to push the data. This is when you can start seeing the error you mentioned, Too many error for endpoint. Since previous errors while trying to reach this endpoint have been displayed already, this one is only mentioning that for now, the Forwarder has decided to wait for a while before retrying to reach this endpoint.
In your specific case, I agree that this specific error isn't enough to troubleshoot your problem, however, the previous endpoint connection errors in your Agent logs should have more information on what's happening with the connection. If the previous error messages are still not enough to troubleshoot the problem, don't hesitate to reach our support by opening a support case related to this 👍 Don't hesitate to mention that conversation into the support ticket if you feel it's necessary, and on my side, I'll also open a ticket about renaming this blockedList object to something more meaningful.
I hope this helps.

Hi @remeh,
Thanks for taking the time to elaborate publicly on the issue. I'm sure others that encounter this will appreciate the additional context. I certainly do.
While it took me a moment, I did eventually figure out that the repeated "Too many errors" meant that there was an earlier repeated failure. It then clicked that I should look much much further back in the logs to identify the error that was the actual root cause. This led me quickly to identify and solve my misconfiguration and move on.
Now, I should probably have realised this all sooner, but the wording used here threw me on a bit of a wild goose chase. I guess we there is a little room for improvement regarding the terminology and function, as per your suggestion. I would perhaps rename blockedList to backoffList or something for clarity in the first case, and then refactor it a bit to capture and store the error message (caught from one of the three causes you mentioned above) against the endpoint in the map too. That way, when we present the error message that gets constantly repeated we can also repeat the root cause too, which should save any operator confusion, and any need to go hunting for clues way back in the log history.
Cheers :+1:

👋
Happy to hear you've solved your initial problem! I created an entry in our backlog as a follow-up of this conversation. I'm closing this issue (SEO will still do its job and this conversation will pop on search engines).


Rename Matrix class to SaddlePoints

Trying to implement the 'matrix' exercise with a class named Matrix
caused CI failures, as it was already implemented here.

Also, this probably could've been avoided by replacing line 21 of .travis.yml with:
- for dir in `ls -d exercises/*/`; do elixirc --warnings-as-errors $dir/example.exs $dir/*test.exs -o ./tmp > /dev/null; done

That way, each directory's compiler check is independent of any others. Not sure what happens with the return code if one in the middle fails, so this may have been considered before and not used.


Fix slash_commands example  unregister on shutdown

The current slash_commands example has on option to unregister commands on shutdown that was not implemented.
This PR adds the unregister on shutdown by remembering all registered commands and unregisters them later.

This is a duplicate of PR #911.


Update Android.gitignore add idea folder.

1, without this there will be conflict every time you download a VCS projects in another directory, i suggest to add *.iml too.

As discussed in #1637, we're tracking all the JetBrains-specific rules in Global/JetBrains.gitignore to help with sharing across tooling and reducing duplication.
I'd also love to understand where this new *.iml rule came from, and what it's there for. Could you provide a link so I can understand more about this?

Closing this out because I confused the PRs and there's no *.iml rule here.


Passing environment variables to Elastic Agents from templates

Hello guys,
I'm using GO.CD Elastic Agents and everything works fine except for passing environment variables from Templates.
When passing varibles from Elastic Agent configuration everything works but I would like to pass encrypted variables from my Template definition. Is there a way to pass environment varibles to Elastic Agent Pods from Templates?
Thanks in advance,
Ronal

Hi @ronalcelaya,
Here we're talking about two different "Environment Variables", the GoCD Environment Variables and the Environment Variables specified to the Pod as Pod Yaml Spec.
In Kubernetes Elastic Agent Plugin Pod Yaml Spec, the Environment Variables are the Kubernetes supported Environment Variables, which will be passed on to the Pod and eventually will be consumed by GoCD Elastic Agent. Hence, we can not specify Encrypted Environment Variables as part of Pod Yaml Spec.
There are following two approaches to pass encrypted environment variables to the Kubernetes Elastic Agent Pod:
1. Using GoCD Environment:
GoCD Environment contains pipelines, agents and environment variables. The environment variables from the environment are passed to the agents. You can create an environment for the pipeline(which requires k8s elastic agent) and then specify the secure environment variable, which will be available to the k8s EA pod. You can find more information about GoCD Environments here.
Note, You don't need to specify the GoCD environment to the Kubernetes Elastic Agent. As the pipeline belongs to the environment, all the elastic agents of that pipeline too will be added to the same environment.
2. Using Kubernetes Secrets:
We can use Kubernetes secrets to pass secure values to the pods as environment variables. Know more about it at kubernetes.io.

Hi @GaneshSPatil
Thanks for your answer.
I'm using Kubernetes Secrets and now everything works as expected. Thanks for your help
Best regards


Please fix the spell mistake in 2.4.0

https://github.com/visionmedia/debug/blob/master/debug.js#L126
https://travis-ci.org/fex-team/node-ral/jobs/183832044

see my pull request ;-) https://github.com/visionmedia/debug/pull/349
this is really a problem right now

126:  debug.color = selectColor(namespae);
should be namespace

Yes, this is breaking many apps.

How can this be released!
This should have been caught by a very simple static analysis!

please use eslint before deploy)

Ha I just came here for the same reason.  Was recording a dailydrip episode when suddenly my build, which worked moments prior, was failing during the recording :)

Geez, the timing!!! Same issue.

@JustFly1984 maybe you could put together a PR that adds it as a pre-commit hook

Sending you a bill for $75 in lost earnings while troubleshooting 7 failed builds.

  Did you pay him for the passing builds?

sorry I have my own things to do, and I don't know how to do PR yet, and currently have no time to learn that, altho you can just edit the module by yourself until it will be fixed by module owner

This is a problem because the NodeJS ecosystem allows automatic upgrades.
It's much easier in Python since dependencies are usually frozen.

It astonishes me that a library downloaded ~7 million times per month has no test spec or even static analysis commit hook.

@glebec send a PR - this wasn't malicious, but it sucks.  Imagine, though, if people only talked to you about your project when it broke their build.  yarn.lock would fix it, or pinning a version.  Have some empathy for the maintainers.

For everyone that ends up here, pasting this from the fine folks at ember-cli on their issue tracking this:
Mitigations

Use yarn with a yarn.lock would have prevented this issue from affecting your project.
Run npm install --save-dev -E<EMAIL_ADDRESS>&& rm -rf node_modules && npm install will force usage of a known working version in your app

@knewter agreed on all counts — I'm not actually angry, just amazed.

@glebec I just feel bad for him.  I was suggesting that you direct the amazed energy at a quick PR to help avoid the problems in the future too :)

I created a module that leverages other modules to help maintain a good development environment, including automatically running npm scripts from git hooks (using git-validate). It will create these under ./git/hooks/pre-commit as well as place .eslint in the root and test directories. A script using the depcheck module leverages a .depcheckrc file for confirmation to make sure the dependencies in package.json line up to your project.
npm i -D developer-tools

npm run depcheck
npm run validate
npm run lint

This is rediculous!
Don't you have 100% coverage for such a commonly used npm module???

Come on... it's breaking my work right now...

Please tone it down, everybody. Mistakes happen. It's been about 30-40 minutes, and it's being worked on right now.

Hey guys.  Apologies for the busted release.  We currently don't have static analysis or tests set up.  I've released 2.4.1 with a hotfix.    Currently adding test coverage and static analysis via eslint myself to make sure future releases don't shit the bed :)

I wasn't at all serious about the invoice, but we do currently have two developers assigned to investigate this internally.
Our yarn.lock file was supposed to install 2.3.3 during our CI/CD process, but for some reason it jumped to the broken 2.4.0 version. This highlights an issue with our build/deploy process rather than this package itself, broken releases are always a possibility but it shouldn't be possible to install a different version to Production than on a local Development environment.
I'm starting to wonder if it's a bug in Yarn itself. It's the end of the day here for us, and luckily none of our deploys were mission-critical (again, I was joking about the invoice). Hopefully this is resolved by tomorrow, otherwise we'll use one of the above workarounds (or lock down the debug.js version in package.json and switch back to npm install).
Also, hopefully this means automated testing can be added to this package to prevent these issues from occurring in future. There already seems to be some great suggestions above.

Just did an npm install, and all works fine now.  Just facing the issue and it is already fixed :). Good job guys!

now ok

@thebigredgeek

@2.4.1 Released :tada:

@chrisatomix It's not a problem with yarn nor your own CI/CD process. It's a general problem with the npm ecosystem because most dependencies of projects are dynamic.
In my case, it's not a direct dependency of my project. But it's a dependency of a dependency where we don't have control anymore.

@chrisatomix it broke my build too, but I really can't figure out how - as far as I can tell everything (including dependencies) is locked to 2.3.3.

@thebigredgeek Thank you very much for the quick response and the fix.

@thebigredgeek thanks for the quick fix, and thank You and @TooTallNate for Your hard work. This kind of little mistakes make us better, so don't worry too much about it. Please keep up the great work, we really appreciate it. :)

That's an awesome thread people :)
Thanks @thebigredgeek for your hard work!
Merry Xmas :)

🎉  Huge thanks to everyone who jumped on this so quickly. Your efforts are much appreciated.

@chrisatomix @doublesharp are you installing yarn using npm? yarn itself depends on debug so it you aren't using the pre-packaged builds then that's probably your issue: https://github.com/yarnpkg/yarn/blob/master/package.json#L15

@koresar not me.  Thanks to everyone who put in PRs.  All I had to do was hit the merge button, run a sanity check, and publish haha.

With regards to yarn, I highly recommend installing via yum/homebrew/apt-get.  You'll have a better experience

@chancancode I think you've nailed it, we assumed it was because of a browsersync dependency. Didn't realise this package was also used by Yarn itself! Definitely need to switch to pre-packaged builds.
@thebigredgeek Great advice :+1: This typo might turn out to be a blessing in disguise if it makes our builds more robust :)

害苦我了

This is a good wake up call to start using npm shrinkwrap or yarn

Glad this shit show can be a learning lesson for some of us haha

@chancancode I'm not using yarn, this is an express app.

@chrisatomix Are you using yarn in production ?
#761 is still open, which doesn't install correct dependencies on using --production flag.
So does your production build include dev dependencies ?
cc: @thebigredgeek @awestroke

https://github.com/visionmedia/debug/commit/dafc99b98cf52212aed816bb5d4671de9f1a63b6 < in case anyone is interested, boilerplate for tests, linting, and v3 roadmap (ES2015 + full test coverage) has been added.  Waiting on admin access to integrate with circle ci :)

@KunalKapadia Using it on our CI/CD server to compile CSS/JS files, if the build is successful then it deploys to Production. We don't actually use Yarn on our Production servers themselves. Also, all our dependencies are specified as dev dependencies, so I don't think that open issue would affect us anyway.

@thebigredgeek I just sent a PR that duplicates some of what you did and includes a few other things that might be useful, feel free to use as you please. Thanks!

@doublesharp thanks will look into it when I get some free time.  Currently sick, so deploying tonight probably wasn't a great choice on my part

@halt-hammerzeit lol

thank you for the quick fix <3

@doublesharp don't grep package.json, do npm ls debug

@codeaholics Sorry, I wasn't totally clear, I did that, and then I grep'd just to double check. Everything is either 2.2.0 or 2.3.3, so I'm not sure what was grabbing the latest version of debug.
npm ls debug
├─┬<EMAIL_ADDRESS>│ └─┬<EMAIL_ADDRESS>│   └─┬<EMAIL_ADDRESS>│     └──<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>│ ├─┬<EMAIL_ADDRESS>│ │ └──<EMAIL_ADDRESS>│ └─┬<EMAIL_ADDRESS>│   └─┬<EMAIL_ADDRESS>│     └─┬<EMAIL_ADDRESS>│       └─┬<EMAIL_ADDRESS>│         └─┬<EMAIL_ADDRESS>│           └──<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>│ └─┬<EMAIL_ADDRESS>│   └──<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>│ ├──<EMAIL_ADDRESS>│ ├─┬<EMAIL_ADDRESS>│ │ └──<EMAIL_ADDRESS>│ └─┬<EMAIL_ADDRESS>│   └──<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>└─┬<EMAIL_ADDRESS>  └─┬<EMAIL_ADDRESS>    └─┬<EMAIL_ADDRESS>      └──<EMAIL_ADDRESS>

Interesting. As others have pointed out, Yarn uses (perhaps directly, perhaps transitively) debug. I know you said you aren't using Yarn, but I just checked, and so does NPM - although latest (4.0.3) still only appears to bring in debug 2.2.0. It seems like there's a difference between the versions of the tools (or the NPM config?) being used between your laptop and your CI server.
Either way, I'm guessing you're all sorted now any way.

@codeaholics It's all working again, but definitely confusing. FWIW - the version of node and npm is the same, and the Jenkins server deletes the workspace and installs node locally for each build... I actually just reinstalled both from scratch a few days ago so I'm certain this is the case. The only difference is my laptop is a Mac and Jenkins is on CentOS7.

@thebigredgeek Let me know if you want some help setting up CI. It'll save your bacon in cases like this, and I am a QA professional by day as well as my company's build engineer, so I'm willing to offer what assistance I can. The SockDrawer team really appreciates the Debug library :) I'd love to help give something back

Folks who mentioned spending time tracking down a broken dependency - you should give https://greenkeeper.io/ a shot.  It creates a branch to run CI for every update to every one of your first-order dependencies.  Since we started using it, we have not once had to track down which dep broke our build (e.g., I came in this morning and already knew debug had broken a couple projects :smile_cat:)
/CC @chrisatomix

To the entitled people: donate some money, then maybe people will have more time to devote to the free software that you use every day.

Contributing to the project or just being gracious won't hurt either.
On Dec 14, 2016 10:09 AM, "TJ Holowaychuk"<EMAIL_ADDRESS>wrote:
To the entitled people: donate some money, then maybe people will have more
time to devote to the free software that you use every day.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/visionmedia/debug/issues/347#issuecomment-267109014,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAi4ULMXu2sixyf7WtC_Npurcqz8xcOIks5rIDDfgaJpZM4LMl7l
.

To follow up on what @tj said, you can read about just how one-sided and broken this situation is in Nadia Eghbal's report, Roads and Bridges.
If you want to help fix this problem, some thoughts:

Donate money to projects, for example the ones on Open Collective
Submit a pull request

This time of year you can use 24 Pull Requests
Find some issues on CodeTriage
Find some issues with First Timers Only
Every month we post a "Who needs contributors?" thread on HN

Ask maintainers if you can help triage issues
As @doublesharp said: at the minimum, just show some empathy
Push back against demanding or entitled people, but also help them to understand just how broken OSS is for maintainers

And though I'm biased, keep an eye on https://github.com/code-corps, too, to find ways to help. Clearly the contributor funnel is broken. We also need to be kinder. Do what you can to help fix it.

I honestly don't hold it against anyone here who was upset by the broken release.  The industry itself is way more high stress than it should be, with engineers working under constant pressure for 60+ hours a week and their jobs always threatened by unreasonable managers.  So when a package like this breaks they flip out.  I think it has less to do with OSS being broken for maintainers and more to do with the industry as a whole being dysfunctional and that dysfunction cascading into OSS

That too, industry is a mess!

Agreed. Lecturing people on github issues isn't any way to enact real change.

@yamikuronue if you wanna submit a PR to add coveralls integration and coverage reporting with our existing mocha tooling, it would be much appreciated :)

@codeaholics @chancancode @chrisatomix
I figured out how I was getting the latest version and @dashmug is correct that it is caused by semantic versioning/semver. Using npm ls debug shows the required versions, but when you grep the package.json file you see that many of them are included as "debug": "^2.3.3". The caret will result in it using the latest available version that is less than "3.0.0", so when "2.4.0" was released npm used it as an acceptable version.
Using "debug": "2.3.3" would lock it to that version, but a lot of widely used modules use a caret range, like superagent (which is a dependency of supertest), which is being used to run tests on my Jenkins server.

@doublesharp In our case it was Yarn which was installing 2.4.0, due to this line:
"debug": "^2.2.0",
If we'd been using the precompiled version of Yarn instead of running npm install -g yarn our builds wouldn't have failed.
The irony is that it turned out our CI provider already includes Yarn in their default image! We didn't realise they'd added it last month, so we were able to remove the install command from our build script. It shaved about 10 seconds off our average build time :)
Like I said, this error might be a blessing in disguise. Especially now that everyone has realised how much of a critical component it is in so many other packages, the developer may get more support than he ever anticipated. It might even encourage the Facebook Yarn team to go through all their dependencies and make sure each one has automated testing in place.

Looking for more input on V3 here: https://github.com/visionmedia/debug/issues/370

@chrisatomix For sure, I never knew about npm shrinkwrap to lock all the dependencies to a particular version until it occurred to me how npm install was handling the semantic versioning. To be honest I never really thought that much about how it worked previously. I'm planning to generate an npm-shrinkwrap.json and manage the versions manually for anything critical - which is good knowledge to gain from a few failed builds :)

@doublesharp the doco for npm ls says:

This  command  will  print  to stdout all the versions of packages that are installed, as well as their dependencies, in a tree-structure.

If you're saying it just prints the required version, and not actually the installed version, then that seems pretty broken to me!

@codeaholics You're right, there must be something screwy with my project. I just created a test project, installed supertest, and it correctly shows the installed version of debug and not the caret range. Not sure why it was showing the old versions for me (especially considering I deleted node_modules and rebuilt them... I've since actually upgraded debug, so I'm giving up trying to figure out what was going on. :/


feat: add hyperbolic api to eliza

Relates to:

Risks
Low
Background
What does this PR do?
This PR adds hyperbolic as a new model provider.
What kind of change is this?
Features (non-breaking change which adds functionality)

Why are we doing this? Any context or related work?
Add more model providers to provide a more diverse set of model offerings. As another huge plus, hyperbolic is in the web3 space: offering decentralized services for inference and building a verification mechanism for decentralized inference.
Documentation changes needed?
Any documentation necessary for adding Hyperbolic as a model provider.

Testing
I tested locally by running pnpm dev with a new character that had ModelProviderName.HYPERBOLIC as the modelProvider. Everything seemed to work well.
Where should a reviewer start?
Register at https://app.hyperbolic.xyz.
Visit https://app.hyperbolic.xyz/settings, grab your api key, and add to your .env file under HYPERBOLIC_API_KEY
Detailed testing steps
None, automated tests are fine.

Discord username
mtrz

Thanks for working on this! Do you mind updating the modelprovider documentation with this new addition as well as add this Register at https://app.hyperbolic.xyz/.
Visit https://app.hyperbolic.xyz/settings, grab your api key, and add to your .env file under HYPERBOLIC_API_KEY on it thanks!

@monilpat thanks for the review! It looks like the documentation updates are run via pnpm build and because my repo is a fork, it updates all the package links in the documentations to point to my forked repo (https://github.com/meppsilon/eliza). Is there a better way to generate that? Also, in what file would you like me to place the text about grabbing the hyperbolic api key?

Hey @monilpat , I manually updated a couple of the model documentation files. Let me know where you would like me to add the info about grabbing the hyperbolic api key.

hey @monilpat, I see that the ModelProviderName.md has been updated and now conflicts with my PR but it looks like the conflicts are changing code references to your fork of the codebase. Do you want me to go with those changes?

Feel free to go ahead with your changes - we need to resolve the how docs get generated so it doesn't flood PRs, but feel free to use your local changes after rebasing on top of main :) Thanks for doing this :)

@monilpat No problem! Okay, I resolved the conflicts with my changes. Let me know if there's anything else you'd like for me to add into this PR.


chore(Styleguide): add args to toggle story

Overview
Per sarah's request

Add args to Toggle story

PR Checklist

[ ] Related to designs:
[ ] Related to JIRA ticket: ABC-123
[ ] I have run this code to verify it works
[ ] This PR includes unit tests for the code change

📬Published Alpha Packages<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://5fc66f38ddfbcd00b4908ea2--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://5fc6707f6c3c56011c10f960--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://5fc7b17a8cb005ba1927da38--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://5fc7f1b7c8c1b700cd18a490--gamut-preview.netlify.appDeploy Logs


Flutter 3.24.4 Not Supported Yet

$> monarch run
Using flutter sdk at C:\src\flutter\bin\flutter

Downloading the Monarch UI for this project's flutter version...

We could not find a compatible Monarch UI for this version of Monarch and Flutter.
You could try switching Flutter versions. Or, create a GitHub issue in the Monarch repo
and let us know which Flutter version your project is using:
https://github.com/Dropsource/monarch/issues

My current Flutter Version
Flutter 3.24.4 • channel stable • https://github.com/flutter/flutter.git
Framework • revision 603104015d (3 days ago) • 2024-10-24 08:01:25 -0700
Engine • revision db49896cf2
Tools • Dart 3.5.4 • DevTools 2.37.3

facing the same issue here...

Hello. Sorry for the trouble. A couple of the build machines had rebooted incorrectly. I fixed the issue.
Monarch is only going to support the latest Flutter version for now. To use monarch, please get on latest stable flutter (3.24.4), then run monarch run again.

i am also facing the same issue here
`/karthikeyansk/fvm/versions/3.24.3/bin/flutter
Enabling Flutter for desktop
Downloading the Monarch UI for this project's flutter version...
We could not find a compatible Monarch UI for this version of Monarch and Flutter.
You could try switching Flutter versions. Or, create a GitHub issue in the Monarch repo
and let us know which Flutter version your project is using:
https://github.com/Dropsource/monarch/issues
Flutter 3.24.3 • channel stable • https://github.com/flutter/flutter.git
Framework • revision 2663184aa7 (8 weeks ago) • 2024-09-11 16:27:48 -0500
Engine • revision 36335019a8
Tools • Dart 3.5.3 • DevTools 2.37.3
Monarch version 2.2.7
Monarch modules:

cli: 3.0.5
controller: 1.4.2
platform_app: 2.1.1
preview_api: 2.4.1

Revision:
c5831d1176003a005bcc20ae70e9650be272f118
`

Hello @karthiKN-sk. Please see my previous comment here.


Add endpoint for importing attendance from People Counter

We need a new endpoint added in Apiary so we can accept attendance data from People Counter.
This endpoint needs to accept a GTID and a timestamp and determine the team association based on previous attendance for that GTID.
People Counter will call this endpoint when someone swipes at the RoboJackets kiosk, and we'll likely backfill data as well.

We may also want to pass the visit ID, not sure.

Closing as People Counter has been decommissioned. Data was copied over prior to shutdown.


release checklist for v1.2

[x] (DEV) Close or defer all tickets in the epics (code complete/scope closure) - code freeze
[x] (DEV) Create release candidate branch (branching, tagging) - Middleware and Frontend
[x] (Business Owner) Identify destination & distribution targets (communications, announcements)
[x] (SRE) Ensure SRE pipelines are in place
[x] (DEV) unit & Integration tests have passed
[x] (DEV) Create readme in git repo (scope closure)
[ ] (DEV) ensure changelog is in place
[ ] (SRE) acceptance tests in a production environment has passed
[ ] (DEV) Documentation updates are in place (docs team)

Is complete now


Minor refactoring

Hi!
I took a little look at the code and found a few places where the code could be simpler and better. Maybe I'll look into your project again! You have a large and interesting code base!

Thank you! LGTM!


CI split between master (full) and PR (smoke) for ESP32

Problem
We spend a lot of time waiting for PR CI.
Change overview
Moved full ESP32 separate builds(about 1h each, 2h combined) into master builds only, moved the PR builds as a "smoke test" only that is expected to finish faster (under 30 min).
Consolidated ESP32 into only one build instead of trying to parallelize.
Testing
CI will validate.

/rebase

/rebase

These split CI's have caused issues today twice now, and missed build coverage. Suggest reverting, given this is only saving an hour or so of 12-14 hours of CI time.


CentOS 7: ERROR: missing input file '@external_libs//:mysql/byte_order_generic_x86_64.h'

On CentOS 7.6 64bit with MariaDB 10.3.12, resolved older git issue https://github.com/google/mysql-ripple/issues/12 only to run into another issue
bazel version
Build label: 0.23.1- (@non-git)
Build target: bazel-out/k8-opt/bin/src/main/java/com/google/devtools/build/lib/bazel/BazelServer_deploy.jar
Build time: Mon Mar 4 13:43:11 2019<PHONE_NUMBER>)
Build timestamp:<PHONE_NUMBER>
Build timestamp as int:<PHONE_NUMBER>

Using GCC 8.2.1
gcc --version
gcc (GCC) 8.2.1 20180905 (Red Hat 8.2.1-3)
Copyright (C) 2018 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Git updated from 1.8.3 via IUS Community repo https://dl.iuscommunity.org/pub/ius/stable/CentOS/7/x86_64/repoview/git2u.html
git --version
git version 2.16.5

MariaDB 10.3.12 via official mariadb.org YUM repo for CentOS 7
yum list MariaDB* -q | egrep 'MariaDB|Available|Installed'
Installed Packages
MariaDB-client.x86_64                     10.3.13-1.el7.centos    @mariadb
MariaDB-common.x86_64                     10.3.13-1.el7.centos    @mariadb
MariaDB-compat.x86_64                     10.3.13-1.el7.centos    @mariadb
MariaDB-devel.x86_64                      10.3.13-1.el7.centos    @mariadb
MariaDB-server.x86_64                     10.3.13-1.el7.centos    @mariadb
MariaDB-shared.x86_64                     10.3.13-1.el7.centos    @mariadb
Available Packages
MariaDB-backup.x86_64                     10.3.13-1.el7.centos    mariadb
MariaDB-cassandra-engine.x86_64           10.3.13-1.el7.centos    mariadb
MariaDB-connect-engine.x86_64             10.3.13-1.el7.centos    mariadb
MariaDB-cracklib-password-check.x86_64    10.3.13-1.el7.centos    mariadb
MariaDB-gssapi-server.x86_64              10.3.13-1.el7.centos    mariadb
MariaDB-oqgraph-engine.x86_64             10.3.13-1.el7.centos    mariadb
MariaDB-rocksdb-engine.x86_64             10.3.13-1.el7.centos    mariadb
MariaDB-test.x86_64                       10.3.13-1.el7.centos    mariadb
MariaDB-tokudb-engine.x86_64              10.3.13-1.el7.centos    mariadb

mysqladmin ver
mysqladmin  Ver 9.1 Distrib 10.3.13-MariaDB, for Linux on x86_64
Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.

Server version          10.3.12-MariaDB
Protocol version        10
Connection              Localhost via UNIX socket
UNIX socket             /var/lib/mysql/mysql.sock
Uptime:                 25 days 15 hours 28 min 9 sec

Threads: 8  Questions: 5238456  Slow queries: 0  Opens: 35  Flush tables: 1  Open tables: 27  Queries per second avg: 2.364

yum -y install bazel
cd /svr-setup
git clone https://github.com/google/mysql-ripple.git
cd mysql-ripple
source /opt/rh/devtoolset-8/enable
export CC=gcc
bazel build :all
bazel test :all

bazel build :all
Starting local Bazel server and connecting to it...
DEBUG: Rule 'com_google_googletest' modified arguments {"shallow_since": "1537409963 -0400"}
DEBUG: Rule 'com_google_protobuf' modified arguments {"shallow_since": "1537216885 -0700"}
DEBUG: Rule 'bazel_skylib' modified arguments {"shallow_since": "1535465090 -0400"}
DEBUG: Rule 'com_google_absl' modified arguments {"shallow_since": "1538751188 -0400"}
DEBUG: Rule 'com_google_glog' modified arguments {"shallow_since": "1531725486 +0200"}
DEBUG: Rule 'com_github_gflags_gflags' modified arguments {"shallow_since": "1530829475 +0100"}
INFO: Analysed 50 targets (39 packages loaded, 1394 targets configured).
INFO: Found 50 targets...
INFO: From Compiling log_event.cc:
log_event.cc: In member function 'bool mysql_ripple::RawLogEventData::ParseFromBuffer(const uint8_t*, int)':
log_event.cc:62:30: warning: comparison of integer expressions of different signedness: 'uint32_t' {aka 'unsigned int'} and 'int' [-Wsign-compare]
   return header.event_length <= buffer_length;
          ~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~
log_event.cc: In member function 'virtual bool mysql_ripple::FormatDescriptorEvent::ParseFromBuffer(const uint8_t*, int)':
log_event.cc:206:66: warning: comparison of integer expressions of different signedness: 'uint' {aka 'unsigned int'} and 'int' [-Wsign-compare]
   for (uint offset = kServerVersionStringLen + 2 + 4 + 1; offset < len - 1;
                                                           ~~~~~~~^~~~~~~~~
log_event.cc: In member function 'virtual bool mysql_ripple::QueryEvent::SerializeToBuffer(uint8_t*, int) const':
log_event.cc:426:14: warning: comparison of integer expressions of different signedness: 'int' and 'std::basic_string<char>::size_type' {aka 'long unsigned int'} [-Wsign-compare]
   if (remain < query.size()) {
       ~~~~~~~^~~~~~~~~~~~~~
INFO: From Compiling gtid.cc:
gtid.cc: In member function 'void mysql_ripple::GTIDList::CheckMerge(mysql_ripple::GTIDList::GTIDStream*, int)':
gtid.cc:635:13: warning: comparison of integer expressions of different signedness: 'int' and 'std::vector<mysql_ripple::GTIDSet::Interval>::size_type' {aka 'long unsigned int'} [-Wsign-compare]
   if (i + 1 >= stream->intervals.size())
       ~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~
gtid.cc: In member function 'bool mysql_ripple::GTIDList::ValidSuccessor(const mysql_ripple::GTID&) const':
gtid.cc:490:1: warning: control reaches end of non-void function [-Wreturn-type]
 }
 ^
ERROR: missing input file '@external_libs//:mysql/byte_order_generic_x86_64.h'
ERROR: /root/.cache/bazel/_bazel_root/09eccf19d891989ba4aefba106852854/external/external_libs/BUILD.bazel:15:1: @external_libs//:mysqlclient: missing input file '@external_libs//:mysql/byte_order_generic_x86_64.h'
ERROR: /root/.cache/bazel/_bazel_root/09eccf19d891989ba4aefba106852854/external/external_libs/BUILD.bazel:15:1 1 input file(s) do not exist
INFO: Elapsed time: 49.073s, Critical Path: 4.61s
INFO: 64 processes: 64 processwrapper-sandbox.
FAILED: Build did NOT complete successfully

location for byte_order_generic_x86_64.h
locate byte_order_generic_x86_64.h
/usr/include/mysql/server/byte_order_generic_x86_64.h

This is interesting. I've setup external_libs.BUILD.bazel file to match what I have on a Debian machine. For me the file is in /usr/include/mysql/byte_order_generic_x86_64.h and is provided by libmariadbclient-dev package, which has version 10.1.37-1. I guess either MariaDB 10.3 has changed the packaging, or the packaging is different for CentOS.
I think the best way to fix this is actually not to depend on the files installed on the system and pull them from MariaDB/MySQL repo. I'll look into doing that. For now you can try to modify external_libs.BUILD.bazel file locally to match your file location. Sorry.

yeah
on CentOS 7 official mariadb.org 10.0.38 it's at
locate byte_order_generic_x86_64.h
/usr/include/mysql/byte_order_generic_x86_64.h

on CentOS 7 official mariadb 10.1.37 it's at
locate byte_order_generic_x86_64.h
/usr/include/mysql/byte_order_generic_x86_64.h

tried manual editing of external_libs.BUILD.bazel by finding headers from MariaDB-devel package for 10.3 and matching it against headers defined in external_libs.BUILD.bazel and sed replacing them
headers.txt
        "mysql/byte_order_generic_x86_64.h",
        "mysql/little_endian.h",
        "mysql/m_ctype.h",
        "mysql/m_string.h",
        "mysql/my_alloc.h",
        "mysql/my_attribute.h",
        "mysql/my_byteorder.h",
        "mysql/my_config.h",
        "mysql/my_compiler.h",
        "mysql/my_dbug.h",
        "mysql/my_dir.h",
        "mysql/my_global.h",
        "mysql/my_list.h",
        "mysql/my_net.h",
        "mysql/my_pthread.h",
        "mysql/my_sys.h",
        "mysql/my_valgrind.h",
        "mysql/mysql.h",
        "mysql/mysql_com.h",
        "mysql/mysql_time.h",
        "mysql/mysql_version.h",
        "mysql/mysqld_error.h",
        "mysql/private/violite.h",
        "mysql/typelib.h",

so will sed replace 1st column value with 2nd column value in external_libs.BUILD.bazel
cat headers.txt | sed -e 's|,||' -e 's|"||g' -e 's|mysql/||'| while read i; do name=$(basename $i); echo -n "$name " ;rpm -ql MariaDB-devel |grep '/server/'| fgrep -m1 $i ; done | sed -e 's|\/usr\/include\/mysql||'
byte_order_generic_x86_64.h /server/byte_order_generic_x86_64.h
little_endian.h /server/little_endian.h
m_ctype.h /server/m_ctype.h
m_string.h /server/m_string.h
my_alloc.h /server/my_alloc.h
my_attribute.h /server/my_attribute.h
my_byteorder.h /server/my_byteorder.h
my_config.h /server/my_config.h
my_compiler.h /server/my_compiler.h
my_dbug.h /server/my_dbug.h
my_dir.h /server/my_dir.h
my_global.h /server/my_global.h
my_list.h /server/my_list.h
my_net.h /server/my_net.h
my_pthread.h /server/my_pthread.h
my_sys.h /server/my_sys.h
my_valgrind.h /server/my_valgrind.h
mysql.h /server/mysql.h
mysql_com.h /server/mysql_com.h
mysql_time.h /server/mysql_time.h
mysql_version.h /server/mysql_version.h
mysqld_error.h /server/mysqld_error.h
violite.h /server/private/violite.h
typelib.h /server/typelib.h

so headers in external_libs.BUILD.bazel become
    hdrs = [
        "mysql/server/byte_order_generic_x86_64.h",
        "mysql/server/little_endian.h",
        "mysql/server/m_ctype.h",
        "mysql/server/m_string.h",
        "mysql/server/my_alloc.h",
        "mysql/server/my_attribute.h",
        "mysql/server/my_byteorder.h",
        "mysql/server/my_config.h",
        "mysql/server/my_compiler.h",
        "mysql/server/my_dbug.h",
        "mysql/server/my_dir.h",
        "mysql/server/my_global.h",
        "mysql/server/my_list.h",
        "mysql/server/my_net.h",
        "mysql/server/my_pthread.h",
        "mysql/server/my_sys.h",
        "mysql/server/my_valgrind.h",
        "mysql/server/mysql.h",
        "mysql/server/mysql_com.h",
        "mysql/server/mysql_time.h",
        "mysql/server/mysql_version.h",
        "mysql/server/mysqld_error.h",
        "mysql/server/private/violite.h",
        "mysql/server/typelib.h",
    ],

cd /svr-setup
git clone https://github.com/google/mysql-ripple.git
cd mysql-ripple
source /opt/rh/devtoolset-8/enable
export CC=gcc
cp -a external_libs.BUILD.bazel external_libs.BUILD.bazel.org
cat headers.txt | sed -e 's|,||' -e 's|"||g' -e 's|mysql/||'| while read i; do name=$(basename $i); echo -n "$name " ;rpm -ql MariaDB-devel |grep '/server/'| fgrep -m1 $i ; done | sed -e 's|\/usr\/include\/mysql||' | while read a b; do if [[ $a = 'violite.h' ]]; then a=private/violite.h; fi ;sed -i "s|mysql\/$a|mysql${b}|" external_libs.BUILD.bazel; done
bazel build :all
bazel test :all

but run into error
bazel build :all
INFO: Analysed 50 targets (1 packages loaded, 56 targets configured).
INFO: Found 50 targets...
ERROR: /svr-setup/mysql-ripple/BUILD.bazel:368:1: C++ compilation of rule '//:encryption' failed (Exit 1) gcc failed: error executing command /opt/rh/devtoolset-8/root/usr/bin/gcc -U_FORTIFY_SOURCE -fstack-protector -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer '-std=c++0x' -MD -MF ... (remaining 51 argument(s) skipped)

Use --sandbox_debug to see verbose messages from the sandbox
In file included from my_crypt.h:25,
                 from encryption.cc:23:
external/external_libs/mysql/my_global.h:3:2: warning: #warning This file should not be included by clients, include only <mysql.h> [-Wcpp]
 #warning This file should not be included by clients, include only <mysql.h>
  ^~~~~~~
In file included from my_crypt.h:26,
                 from encryption.cc:23:
external/external_libs/mysql/mysql.h:59:10: fatal error: mariadb_com.h: No such file or directory
 #include "mariadb_com.h"
          ^~~~~~~~~~~~~~~
compilation terminated.
INFO: Elapsed time: 1.316s, Critical Path: 0.34s
INFO: 0 processes.
FAILED: Build did NOT complete successfully

This sounds like MariaDB 10.3 has a "mariadb_com.h" header along with "mysql_com.h".  Maybe you should change external_libs.BUILD.bazel to look like this:

cc_library(
    name = "mysqlclient",
    includes = [
        "mysql",
        "mysql/server",
    ],
    hdrs = [
...
    ],
    linkopts = [
        "-l:libmariadbclient.a",
        "-ldl",
        "-lpthread",
        "-lz",
    ],
    visibility = ["//visibility:public"],
)

revisiting this sorry for late reply changing external_libs.BUILD.bazel to add  to includes array "mysql/server",
gives this error
bazel build :all
Starting local Bazel server and connecting to it...
INFO: Analyzed 50 targets (43 packages loaded, 1266 targets configured).
INFO: Found 50 targets...
INFO: Deleting stale sandbox base /root/.cache/bazel/_bazel_root/09eccf19d891989ba4aefba106852854/sandbox
ERROR: missing input file '@external_libs//:mysql/byte_order_generic_x86_64.h'
ERROR: missing input file '@external_libs//:mysql/little_endian.h'
ERROR: missing input file '@external_libs//:mysql/m_ctype.h'
ERROR: missing input file '@external_libs//:mysql/m_string.h'
ERROR: missing input file '@external_libs//:mysql/my_alloc.h'
ERROR: missing input file '@external_libs//:mysql/my_attribute.h'
ERROR: missing input file '@external_libs//:mysql/my_byteorder.h'
ERROR: missing input file '@external_libs//:mysql/my_compiler.h'
ERROR: missing input file '@external_libs//:mysql/my_dbug.h'
ERROR: missing input file '@external_libs//:mysql/my_dir.h'
ERROR: missing input file '@external_libs//:mysql/my_list.h'
ERROR: missing input file '@external_libs//:mysql/my_net.h'
ERROR: missing input file '@external_libs//:mysql/my_pthread.h'
ERROR: missing input file '@external_libs//:mysql/my_valgrind.h'
ERROR: missing input file '@external_libs//:mysql/mysql_time.h'
ERROR: missing input file '@external_libs//:mysql/private/violite.h'
ERROR: missing input file '@external_libs//:mysql/typelib.h'
ERROR: /root/.cache/bazel/_bazel_root/09eccf19d891989ba4aefba106852854/external/external_libs/BUILD.bazel:17:1: @external_libs//:mysqlclient: missing input file '@external_libs//:mysql/byte_order_generic_x86_64.h'
ERROR: /root/.cache/bazel/_bazel_root/09eccf19d891989ba4aefba106852854/external/external_libs/BUILD.bazel:17:1: @external_libs//:mysqlclient: missing input file '@external_libs//:mysql/little_endian.h'
ERROR: /root/.cache/bazel/_bazel_root/09eccf19d891989ba4aefba106852854/external/external_libs/BUILD.bazel:17:1: @external_libs//:mysqlclient: missing input file '@external_libs//:mysql/m_ctype.h'
ERROR: /root/.cache/bazel/_bazel_root/09eccf19d891989ba4aefba106852854/external/external_libs/BUILD.bazel:17:1: @external_libs//:mysqlclient: missing input file '@external_libs//:mysql/m_string.h'
ERROR: /root/.cache/bazel/_bazel_root/09eccf19d891989ba4aefba106852854/external/external_libs/BUILD.bazel:17:1: @external_libs//:mysqlclient: missing input file '@external_libs//:mysql/my_alloc.h'
ERROR: /root/.cache/bazel/_bazel_root/09eccf19d891989ba4aefba106852854/external/external_libs/BUILD.bazel:17:1: @external_libs//:mysqlclient: missing input file '@external_libs//:mysql/my_attribute.h'
ERROR: /root/.cache/bazel/_bazel_root/09eccf19d891989ba4aefba106852854/external/external_libs/BUILD.bazel:17:1: @external_libs//:mysqlclient: missing input file '@external_libs//:mysql/my_byteorder.h'
ERROR: /root/.cache/bazel/_bazel_root/09eccf19d891989ba4aefba106852854/external/external_libs/BUILD.bazel:17:1: @external_libs//:mysqlclient: missing input file '@external_libs//:mysql/my_compiler.h'
ERROR: /root/.cache/bazel/_bazel_root/09eccf19d891989ba4aefba106852854/external/external_libs/BUILD.bazel:17:1: @external_libs//:mysqlclient: missing input file '@external_libs//:mysql/my_dbug.h'
ERROR: /root/.cache/bazel/_bazel_root/09eccf19d891989ba4aefba106852854/external/external_libs/BUILD.bazel:17:1: @external_libs//:mysqlclient: missing input file '@external_libs//:mysql/my_dir.h'
ERROR: /root/.cache/bazel/_bazel_root/09eccf19d891989ba4aefba106852854/external/external_libs/BUILD.bazel:17:1: @external_libs//:mysqlclient: missing input file '@external_libs//:mysql/my_list.h'
ERROR: /root/.cache/bazel/_bazel_root/09eccf19d891989ba4aefba106852854/external/external_libs/BUILD.bazel:17:1: @external_libs//:mysqlclient: missing input file '@external_libs//:mysql/my_net.h'
ERROR: /root/.cache/bazel/_bazel_root/09eccf19d891989ba4aefba106852854/external/external_libs/BUILD.bazel:17:1: @external_libs//:mysqlclient: missing input file '@external_libs//:mysql/my_pthread.h'
ERROR: /root/.cache/bazel/_bazel_root/09eccf19d891989ba4aefba106852854/external/external_libs/BUILD.bazel:17:1: @external_libs//:mysqlclient: missing input file '@external_libs//:mysql/my_valgrind.h'
ERROR: /root/.cache/bazel/_bazel_root/09eccf19d891989ba4aefba106852854/external/external_libs/BUILD.bazel:17:1: @external_libs//:mysqlclient: missing input file '@external_libs//:mysql/mysql_time.h'
ERROR: /root/.cache/bazel/_bazel_root/09eccf19d891989ba4aefba106852854/external/external_libs/BUILD.bazel:17:1: @external_libs//:mysqlclient: missing input file '@external_libs//:mysql/private/violite.h'
ERROR: /root/.cache/bazel/_bazel_root/09eccf19d891989ba4aefba106852854/external/external_libs/BUILD.bazel:17:1: @external_libs//:mysqlclient: missing input file '@external_libs//:mysql/typelib.h'
ERROR: /root/.cache/bazel/_bazel_root/09eccf19d891989ba4aefba106852854/external/external_libs/BUILD.bazel:17:1 17 input file(s) do not exist
INFO: Elapsed time: 10.547s, Critical Path: 0.08s
INFO: 0 processes.
FAILED: Build did NOT complete successfully

Does this error happen when you have changes you've described earlier (https://github.com/google/mysql-ripple/issues/13#issuecomment-474619591)? Specifically I'm asking about changes to hdrs in external_libs.BUILD.bazel file?

yes above errors are with your changes which as I understand it is changing the file from
    includes = [
        "mysql",
    ],

to
    includes = [
        "mysql",
        "mysql/server",
    ],

right ?

In the earlier comment (https://github.com/google/mysql-ripple/issues/13#issuecomment-474619591) you've also said that you've changed all hdrs to point to files under "mysql/server/" rather than "mysql/". It looks like that change is also necessary.


Remove known settings from ConnectionStringSettingName prompt

This PR fixes #17827.
Using the doc here: https://docs.microsoft.com/en-us/azure/azure-functions/functions-app-settings
I used the list to remove the settings and only list connection strings settings.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

5 of 10 (50.0%)  changed or added relevant lines in 1 file are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.006%) to 42.388%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

extensions/sql-bindings/src/common/azureFunctionsUtils.ts
5
10
50.0%

Files with Coverage Reduction
New Missed Lines
%

extensions/notebook/src/book/bookTreeView.ts
2
38.21%

Totals

Change from base Build<PHONE_NUMBER>:
-0.006%

Covered Lines:
27558

Relevant Lines:
60781

💛  - Coveralls


Improve processing of UC sets

This PR improves processing of uc_sets. Closes #226

This should progress once #223 is merged.


Understand environment initialization on kernel startup

Applies To

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

What happened?
I've been running some deep networks (with CUDA 11.3) happily, via interactive .pys for a while. I then upgraded from cuda 11.3 -> 11.6 but the notebook still thinks I'm using cuda 11.3 + pytorch throws. Now I realize I don't even know how cuda 11.3 was initially sourced -- I think this is ultimately a Jupyter extension issue.

In general, I set cuda variables via environment variables in .bashrc (a detail is that the cluster I'm using manages cuda via ModuleFiles but the issue persists with explicit setting). In vscode interactive shell, variables like CUDA_PATH are set correctly.
https://github.com/microsoft/vscode-jupyter/issues/8270 suggests .bashrc is never sourced for jupyter kernels i.e. I expect no environment variables to be set at all in this case. However, various test variables I put in .bashrc are set and printed via os.environ in the interactive window.
However, export CUDA_PATH=11.6 doesn't survive into the jupyter notebook (while other dummy variables do). Specifically, it appears to be overridden back to 11.3. This suggests something in Jupyter initialization is doing this.
Note that for example CUDA_PATH is printed correctly early on in the attached log.
Based on the logs, I think jupyter is inheriting cuda info from a conda environment (rlpyt), which has a pytorch installation with built in cudnn 8.2.0 (corresponding to cuda 11.3), so perhaps the environment variables are totally irrelevant.
Confusingly, several commands are logged from both a new conda env (py10_2) and this old rlpyt.  How is Jupyter initializing with both these environments? How can I specify which one to initialize with? The kernel defaults to py10_2 in the interactive window on fresh restarts. Finally, why does jupyter seem to attempt (and fail) to initialize conda a few times before succeeding (in a different mode)?

VS Code Version
1.68.1
Jupyter Extension Version
v2022.5.1001601848
Jupyter logs
Visual Studio Code (1.68.1, ssh-remote, desktop)
Jupyter Extension Version: 2022.5.1001601848.
Python Extension Version: 2022.16.1.
Workspace folder /home/joelye/projects/fingerprint_gelsight
error 17:35:40.106: Exception while attempting zmq : [Error: /opt/gcc/4.9.2/lib64/libstdc++.so.6: version `CXXABI_1.3.9' not found (required by /home/joelye/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/out/node_modules/zeromq/prebuilds/linux-x64/node.napi.glibc.node)
	at Object.Module._extensions..node (node:internal/modules/cjs/loader:1183:18)
	at Module.load (node:internal/modules/cjs/loader:981:32)
	at Function.Module._load (node:internal/modules/cjs/loader:822:12)
	at Function.s._load (/home/joelye/.vscode-server/bin/30d9c6cd9483b2cc586687151bcbcd635f373630/out/vs/workbench/api/node/extensionHostProcess.js:102:32307)
	at Function.w._load (/home/joelye/.vscode-server/bin/30d9c6cd9483b2cc586687151bcbcd635f373630/out/vs/workbench/api/node/extensionHostProcess.js:102:28750)
	at Function.S._load (/home/joelye/.vscode-server/bin/30d9c6cd9483b2cc586687151bcbcd635f373630/out/vs/workbench/api/node/extensionHostProcess.js:97:61578)
	at Module.require (node:internal/modules/cjs/loader:1005:19)
	at require (node:internal/modules/cjs/helpers:102:18)
	at load (/home/joelye/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/out/node_modules/node-gyp-build/index.js:1:566)
	at Object.<anonymous> (/home/joelye/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/out/node_modules/zeromq/lib/native.js:1:136)
	at Module._compile (node:internal/modules/cjs/loader:1101:14)
	at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
	at Module.load (node:internal/modules/cjs/loader:981:32)
	at Function.Module._load (node:internal/modules/cjs/loader:822:12)
	at Function.s._load (/home/joelye/.vscode-server/bin/30d9c6cd9483b2cc586687151bcbcd635f373630/out/vs/workbench/api/node/extensionHostProcess.js:102:32307)
	at Function.w._load (/home/joelye/.vscode-server/bin/30d9c6cd9483b2cc586687151bcbcd635f373630/out/vs/workbench/api/node/extensionHostProcess.js:102:28750)
	at Function.S._load (/home/joelye/.vscode-server/bin/30d9c6cd9483b2cc586687151bcbcd635f373630/out/vs/workbench/api/node/extensionHostProcess.js:97:61578)
	at Module.require (node:internal/modules/cjs/loader:1005:19)
	at require (node:internal/modules/cjs/helpers:102:18)
	at Object.<anonymous> (/home/joelye/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/out/node_modules/zeromq/lib/index.js:1:82)
	at Module._compile (node:internal/modules/cjs/loader:1101:14)
	at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
	at Module.load (node:internal/modules/cjs/loader:981:32)
	at Function.Module._load (node:internal/modules/cjs/loader:822:12)
	at Function.s._load (/home/joelye/.vscode-server/bin/30d9c6cd9483b2cc586687151bcbcd635f373630/out/vs/workbench/api/node/extensionHostProcess.js:102:32307)
	at Function.w._load (/home/joelye/.vscode-server/bin/30d9c6cd9483b2cc586687151bcbcd635f373630/out/vs/workbench/api/node/extensionHostProcess.js:102:28750)
	at Function.S._load (/home/joelye/.vscode-server/bin/30d9c6cd9483b2cc586687151bcbcd635f373630/out/vs/workbench/api/node/extensionHostProcess.js:97:61578)
	at Module.require (node:internal/modules/cjs/loader:1005:19)
	at require (node:internal/modules/cjs/helpers:102:18)
	at Object.92747 (/home/joelye/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/out/extension.node.js:2:3839954)
	at __webpack_require__ (/home/joelye/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/out/extension.node.js:2:4466880)
	at u.zmqSupported (/home/joelye/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/out/extension.node.js:2:580874)
	at u.isSupportedForLocalLaunch (/home/joelye/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/out/extension.node.js:2:580617)
	at u.get isSupported [as isSupported] (/home/joelye/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/out/extension.node.js:2:580527)
	at t.registerTypes (/home/joelye/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/out/extension.node.js:2:595635)
	at /home/joelye/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/out/extension.node.js:2:4471788
	at /home/joelye/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/out/extension.node.js:2:4472541
	at /home/joelye/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/out/extension.node.js:2:4472549
	at e.activate (/home/joelye/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/out/extension.node.js:2:4472671)
	at Function._callActivateOptional (/home/joelye/.vscode-server/bin/30d9c6cd9483b2cc586687151bcbcd635f373630/out/vs/workbench/api/node/extensionHostProcess.js:88:17470)
	at Function._callActivate (/home/joelye/.vscode-server/bin/30d9c6cd9483b2cc586687151bcbcd635f373630/out/vs/workbench/api/node/extensionHostProcess.js:88:17131)
	at /home/joelye/.vscode-server/bin/30d9c6cd9483b2cc586687151bcbcd635f373630/out/vs/workbench/api/node/extensionHostProcess.js:88:14945
	at async S._activate (/home/joelye/.vscode-server/bin/30d9c6cd9483b2cc586687151bcbcd635f373630/out/vs/workbench/api/node/extensionHostProcess.js:83:8180)
	at async S._waitForDepsThenActivate (/home/joelye/.vscode-server/bin/30d9c6cd9483b2cc586687151bcbcd635f373630/out/vs/workbench/api/node/extensionHostProcess.js:83:8122)
	at async S._initialize (/home/joelye/.vscode-server/bin/30d9c6cd9483b2cc586687151bcbcd635f373630/out/vs/workbench/api/node/extensionHostProcess.js:83:7486)] {
  code: 'ERR_DLOPEN_FAILED'
}
User belongs to experiment group 'jupyterTestcf'
User belongs to experiment group 'jupyterEnhancedDataViewer'
info 17:35:42.228: Attempting to start a server because of preload conditions ...
info 17:35:42.234: LSP Notebooks experiment is enabled
info 17:35:42.263: Checking for server existence.
info 17:35:42.265: Checking for server usability.
info 17:35:42.560: Experiment status for python is {"enabled":true,"optInto":[],"optOutFrom":[]}
error 17:35:44.872: Failed to get activated environment variables ourselves Error: Command failed: conda activate rlpyt && echo 'e8b39361-0157-4923-80e1-22d70d46dee6' && python /home/joelye/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/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:397: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 rlpyt && echo 'e8b39361-0157-4923-80e1-22d70d46dee6' && python /home/joelye/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/pythonFiles/printEnvVariables.py"
}
error 17:35:44.874: Execing shell command, Class name = h, completed in 1395ms, has a falsy return value, Arg 1: "~/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/pythonFiles/printEnvVariables.py", Arg 2: {"env":{"XDG_SESSION_ID":"24099","SHELL":"/bin/bash","SSH_CLIENT":"<IP_ADDRESS> 45102 22","USER":"joelye","VSCODE_AGENT_FOLDER":"/home/joelye/.vscode-server","MAIL":"/var/spool/mail/joelye","PATH":"/home/joelye/.vscode-server/bin/30d9c6cd9483b2cc586687151bcbcd635f373630/bin/remote-cli:/opt/git/2.30/bin:/opt/matlab/9.5/bin:/opt/cuda/11.6/bin:/opt/gcc/6.3.0/bin:/home/joelye/anaconda3/envs/py10_2/bin:/home/joelye/anaconda3/condabin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/opt/cuda/11.6/bin:$PATH","PWD":"/home/joelye","SHLVL":"4","HOME":"/home/joelye","LOGNAME":"joelye","SSH_CONNECTION":"<IP_ADDRESS> 45102 <IP_ADDRESS> 22","XDG_RUNTIME_DIR":"/run/user/23041","DISPLAY":"localhost:11.0","_":"/home/joelye/.vscode-server/bin/30d9c6cd9483b2cc586687151bcbcd635f373630/node","VSCODE_HANDLES_SIGPIPE":"true","CUDA_PATH":"/opt/cuda/11.6","MANPATH":"/opt/gcc/6.3.0/share/man:/usr/share/man:/usr/local/share/man","HOSTNAME":"mind-1-11.eth","HISTSIZE":"1000","CUDA_DUMMY":"0","CONDA_SHLVL":"2","CONDA_PROMPT_MODIFIER":"","QT_GRAPHICSSYSTEM_CHECKED":"1","LD_LIBRARY_PATH":"/opt/cudnn/cuda-11.6/<IP_ADDRESS>/cuda/lib:$LD_LIBRARY_PATH","LS_COLORS":"","CONDA_EXE":"/home/joelye/anaconda3/bin/conda","CPATH":"/opt/cudnn/cuda-11.6/<IP_ADDRESS>/cuda/include:$CPATH","_CE_CONDA":"","CONDA_PREFIX_1":"/home/joelye/anaconda3","C_INCLUDE_PATH":"/opt/cudnn/cuda-11.6/<IP_ADDRESS>/cuda/include:$C_INCLUDE_PATH","CONDA_PREFIX":"/home/joelye/anaconda3/envs/py10_2","CONDA_TEST":"0","_LMFILES_":"/usr/share/Modules/modulefiles/gcc-6.3.0:/usr/share/Modules/modulefiles/cuda-11.6:/usr/share/Modules/modulefiles/cudnn-11.6-v<IP_ADDRESS>:/usr/share/Modules/modulefiles/matlab-9.5:/usr/share/Modules/modulefiles/git-2.30","LANG":"en_US.UTF-8","MODULEPATH":"/usr/share/Modules/modulefiles:/etc/modulefiles","LOADEDMODULES":"gcc-6.3.0:cuda-11.6:cudnn-11.6-v<IP_ADDRESS>:matlab-9.5:git-2.30","_CE_M":"","SSH_ASKPASS":"/usr/libexec/openssh/gnome-ssh-askpass","HISTCONTROL":"ignoreboth","RTMA":"/home/joelye/projects/rtma","NLB_HOME":"/home/joelye/user_data/nlb/","PYTHONPATH":"/home/joelye/projects/icms_modeling/scripts/blackrock/:/home/joelye/projects/rlpyt/:","CONDA_PYTHON_EXE":"/home/joelye/anaconda3/bin/python","XDG_DATA_DIRS":"/home/joelye/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share","MODULESHOME":"/usr/share/Modules","CONDA_DEFAULT_ENV":"py10_2","LESSOPEN":"||/usr/bin/lesspipe.sh Error: Command failed: conda activate rlpyt && echo 'e8b39361-0157-4923-80e1-22d70d46dee6' && python /home/joelye/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/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:397: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 rlpyt && echo 'e8b39361-0157-4923-80e1-22d70d46dee6' && python /home/joelye/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/pythonFiles/printEnvVariables.py"
}","BASH_FUNC_module()":"() {  eval `/usr/bin/modulecmd bash $*`\n}","VSCODE_LOG_NATIVE":"false","VSCODE_AMD_ENTRYPOINT":"vs/workbench/api/node/extensionHostProcess","VSCODE_PIPE_LOGGING":"true","VSCODE_VERBOSE_LOGGING":"true","VSCODE_HANDLES_UNCAUGHT_ERRORS":"true","VSCODE_LOG_STACK":"false","VSCODE_NLS_CONFIG":"{\"locale\":\"en\",\"availableLanguages\":{}}","BROWSER":"/home/joelye/.vscode-server/bin/30d9c6cd9483b2cc586687151bcbcd635f373630/bin/helpers/browser.sh","VSCODE_EXTHOST_WILL_SEND_SOCKET":"true","VSCODE_CWD":"/home/joelye","VSCODE_IPC_HOOK_CLI":"/run/user/23041/vscode-ipc-5ecca03f-2d69-4176-87cd-d337f766bc03.sock","APPLICATION_INSIGHTS_NO_DIAGNOSTIC_CHANNEL":"true","cuda_ver":"11.6","ver":"<IP_ADDRESS>","PYTHONWARNINGS":"ignore"},"shell":"bash","timeout":60000,"maxBuffer":1000000,"throwOnStdErr":false}
error 17:35:44.879: Failed to get activated environment variables ourselves Error: Command failed: conda activate py10_2 && echo 'e8b39361-0157-4923-80e1-22d70d46dee6' && python /home/joelye/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/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:397: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 py10_2 && echo 'e8b39361-0157-4923-80e1-22d70d46dee6' && python /home/joelye/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/pythonFiles/printEnvVariables.py"
}
error 17:35:44.879: Execing shell command, Class name = h, completed in 1424ms, has a falsy return value, Arg 1: "~/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/pythonFiles/printEnvVariables.py", Arg 2: {"env":{"XDG_SESSION_ID":"24099","SHELL":"/bin/bash","SSH_CLIENT":"<IP_ADDRESS> 45102 22","USER":"joelye","VSCODE_AGENT_FOLDER":"/home/joelye/.vscode-server","MAIL":"/var/spool/mail/joelye","PATH":"/home/joelye/.vscode-server/bin/30d9c6cd9483b2cc586687151bcbcd635f373630/bin/remote-cli:/opt/git/2.30/bin:/opt/matlab/9.5/bin:/opt/cuda/11.6/bin:/opt/gcc/6.3.0/bin:/home/joelye/anaconda3/envs/py10_2/bin:/home/joelye/anaconda3/condabin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/opt/cuda/11.6/bin:$PATH","PWD":"/home/joelye","SHLVL":"4","HOME":"/home/joelye","LOGNAME":"joelye","SSH_CONNECTION":"<IP_ADDRESS> 45102 <IP_ADDRESS> 22","XDG_RUNTIME_DIR":"/run/user/23041","DISPLAY":"localhost:11.0","_":"/home/joelye/.vscode-server/bin/30d9c6cd9483b2cc586687151bcbcd635f373630/node","VSCODE_HANDLES_SIGPIPE":"true","CUDA_PATH":"/opt/cuda/11.6","MANPATH":"/opt/gcc/6.3.0/share/man:/usr/share/man:/usr/local/share/man","HOSTNAME":"mind-1-11.eth","HISTSIZE":"1000","CUDA_DUMMY":"0","CONDA_SHLVL":"2","CONDA_PROMPT_MODIFIER":"","QT_GRAPHICSSYSTEM_CHECKED":"1","LD_LIBRARY_PATH":"/opt/cudnn/cuda-11.6/<IP_ADDRESS>/cuda/lib:$LD_LIBRARY_PATH","LS_COLORS":"","CONDA_EXE":"/home/joelye/anaconda3/bin/conda","CPATH":"/opt/cudnn/cuda-11.6/<IP_ADDRESS>/cuda/include:$CPATH","_CE_CONDA":"","CONDA_PREFIX_1":"/home/joelye/anaconda3","C_INCLUDE_PATH":"/opt/cudnn/cuda-11.6/<IP_ADDRESS>/cuda/include:$C_INCLUDE_PATH","CONDA_PREFIX":"/home/joelye/anaconda3/envs/py10_2","CONDA_TEST":"0","_LMFILES_":"/usr/share/Modules/modulefiles/gcc-6.3.0:/usr/share/Modules/modulefiles/cuda-11.6:/usr/share/Modules/modulefiles/cudnn-11.6-v<IP_ADDRESS>:/usr/share/Modules/modulefiles/matlab-9.5:/usr/share/Modules/modulefiles/git-2.30","LANG":"en_US.UTF-8","MODULEPATH":"/usr/share/Modules/modulefiles:/etc/modulefiles","LOADEDMODULES":"gcc-6.3.0:cuda-11.6:cudnn-11.6-v<IP_ADDRESS>:matlab-9.5:git-2.30","_CE_M":"","SSH_ASKPASS":"/usr/libexec/openssh/gnome-ssh-askpass","HISTCONTROL":"ignoreboth","RTMA":"/home/joelye/projects/rtma","NLB_HOME":"/home/joelye/user_data/nlb/","PYTHONPATH":"/home/joelye/projects/icms_modeling/scripts/blackrock/:/home/joelye/projects/rlpyt/:","CONDA_PYTHON_EXE":"/home/joelye/anaconda3/bin/python","XDG_DATA_DIRS":"/home/joelye/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share","MODULESHOME":"/usr/share/Modules","CONDA_DEFAULT_ENV":"py10_2","LESSOPEN":"||/usr/bin/lesspipe.sh Error: Command failed: conda activate py10_2 && echo 'e8b39361-0157-4923-80e1-22d70d46dee6' && python /home/joelye/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/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:397: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 py10_2 && echo 'e8b39361-0157-4923-80e1-22d70d46dee6' && python /home/joelye/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/pythonFiles/printEnvVariables.py"
}","BASH_FUNC_module()":"() {  eval `/usr/bin/modulecmd bash $*`\n}","VSCODE_LOG_NATIVE":"false","VSCODE_AMD_ENTRYPOINT":"vs/workbench/api/node/extensionHostProcess","VSCODE_PIPE_LOGGING":"true","VSCODE_VERBOSE_LOGGING":"true","VSCODE_HANDLES_UNCAUGHT_ERRORS":"true","VSCODE_LOG_STACK":"false","VSCODE_NLS_CONFIG":"{\"locale\":\"en\",\"availableLanguages\":{}}","BROWSER":"/home/joelye/.vscode-server/bin/30d9c6cd9483b2cc586687151bcbcd635f373630/bin/helpers/browser.sh","VSCODE_EXTHOST_WILL_SEND_SOCKET":"true","VSCODE_CWD":"/home/joelye","VSCODE_IPC_HOOK_CLI":"/run/user/23041/vscode-ipc-5ecca03f-2d69-4176-87cd-d337f766bc03.sock","APPLICATION_INSIGHTS_NO_DIAGNOSTIC_CHANNEL":"true","cuda_ver":"11.6","ver":"<IP_ADDRESS>","PYTHONWARNINGS":"ignore"},"shell":"bash","timeout":60000,"maxBuffer":1000000,"throwOnStdErr":false}
info 17:35:49.3: Process Execution: > ~/anaconda3/envs/rlpyt/bin/python -c "import notebook"
> ~/anaconda3/envs/rlpyt/bin/python -c "import notebook"
info 17:35:49.171: Process Execution: > ~/anaconda3/envs/py10_2/bin/python -m pip list
> ~/anaconda3/envs/py10_2/bin/python -m pip list
info 17:35:49.200: Process Execution: > ~/anaconda3/envs/rlpyt/bin/python -c "import jupyter"
> ~/anaconda3/envs/rlpyt/bin/python -c "import jupyter"
info 17:35:49.370: Process Execution: > ~/anaconda3/envs/rlpyt/bin/python -m jupyter kernelspec --version
> ~/anaconda3/envs/rlpyt/bin/python -m jupyter kernelspec --version
info 17:35:49.887: Starting notebook server.
info 17:35:49.889: Connecting to server
info 17:35:49.889: Launching server
info 17:35:49.892: Starting Notebook
info 17:35:49.893: Starting Jupyter Notebook
Starting Jupyter from ~/anaconda3/envs/rlpyt/bin/python with command line --no-browser --NotebookApp.iopub_data_rate_limit=10000000000.0 --KernelManager.autorestart=False --port=8897
info 17:35:49.995: Creating daemon pool for /home/joelye/anaconda3/envs/rlpyt/bin/python with env variables count 68
info 17:35:50.28: Process Execution: > ~/anaconda3/envs/rlpyt/bin/python -m vscode_datascience_helpers.daemon --daemon-module=vscode_datascience_helpers.jupyter_daemon -v --ppid 3770
> ~/anaconda3/envs/rlpyt/bin/python -m vscode_datascience_helpers.daemon --daemon-module=vscode_datascience_helpers.jupyter_daemon -v --ppid 3770
info 17:35:50.70: Process Execution: > ~/anaconda3/envs/rlpyt/bin/python -m vscode_datascience_helpers.daemon --daemon-module=vscode_datascience_helpers.jupyter_daemon -v --ppid 3770
> ~/anaconda3/envs/rlpyt/bin/python -m vscode_datascience_helpers.daemon --daemon-module=vscode_datascience_helpers.jupyter_daemon -v --ppid 3770
info 17:35:50.107: Process Execution: > ~/anaconda3/envs/rlpyt/bin/python -m vscode_datascience_helpers.daemon --daemon-module=vscode_datascience_helpers.jupyter_daemon -v --ppid 3770
> ~/anaconda3/envs/rlpyt/bin/python -m vscode_datascience_helpers.daemon --daemon-module=vscode_datascience_helpers.jupyter_daemon -v --ppid 3770
info 17:35:50.294: Process Execution: > ~/anaconda3/envs/rlpyt/bin/python (daemon) -m jupyter notebook --no-browser --NotebookApp.iopub_data_rate_limit=10000000000.0 --KernelManager.autorestart=False --port=8897
> ~/anaconda3/envs/rlpyt/bin/python (daemon) -m jupyter notebook --no-browser --NotebookApp.iopub_data_rate_limit=10000000000.0 --KernelManager.autorestart=False --port=8897
info 17:35:50.296: Waiting for Jupyter Notebook
[W 2022-11-30 17:35:51.880 LabApp] 'iopub_data_rate_limit' has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.
info 17:35:51.882: [W 2022-11-30 17:35:51.880 LabApp] 'iopub_data_rate_limit' has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.

[W 2022-11-30 17:35:51.880 LabApp] 'port' has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.
info 17:35:51.883: [W 2022-11-30 17:35:51.880 LabApp] 'iopub_data_rate_limit' has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.
[W 2022-11-30 17:35:51.880 LabApp] 'port' has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.

[W 2022-11-30 17:35:51.880 LabApp] 'port' has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.
info 17:35:51.884: [W 2022-11-30 17:35:51.880 LabApp] 'iopub_data_rate_limit' has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.
[W 2022-11-30 17:35:51.880 LabApp] 'port' has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.
[W 2022-11-30 17:35:51.880 LabApp] 'port' has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.

[W 2022-11-30 17:35:51.880 LabApp] 'port' has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.
info 17:35:51.884: [W 2022-11-30 17:35:51.880 LabApp] 'iopub_data_rate_limit' has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.
[W 2022-11-30 17:35:51.880 LabApp] 'port' has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.
[W 2022-11-30 17:35:51.880 LabApp] 'port' has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.
[W 2022-11-30 17:35:51.880 LabApp] 'port' has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.

[I 2022-11-30 17:35:51.894 LabApp] JupyterLab extension loaded from /home/joelye/anaconda3/envs/rlpyt/lib/python3.7/site-packages/jupyterlab
info 17:35:51.895: [W 2022-11-30 17:35:51.880 LabApp] 'iopub_data_rate_limit' has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.
[W 2022-11-30 17:35:51.880 LabApp] 'port' has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.
[W 2022-11-30 17:35:51.880 LabApp] 'port' has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.
[W 2022-11-30 17:35:51.880 LabApp] 'port' has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.
[I 2022-11-30 17:35:51.894 LabApp] JupyterLab extension loaded from /home/joelye/anaconda3/envs/rlpyt/lib/python3.7/site-packages/jupyterlab

[I 2022-11-30 17:35:51.895 LabApp] JupyterLab application directory is /home/joelye/anaconda3/envs/rlpyt/share/jupyter/lab
info 17:35:51.896: [W 2022-11-30 17:35:51.880 LabApp] 'iopub_data_rate_limit' has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.
[W 2022-11-30 17:35:51.880 LabApp] 'port' has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.
[W 2022-11-30 17:35:51.880 LabApp] 'port' has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.
[W 2022-11-30 17:35:51.880 LabApp] 'port' has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.
[I 2022-11-30 17:35:51.894 LabApp] JupyterLab extension loaded from /home/joelye/anaconda3/envs/rlpyt/lib/python3.7/site-packages/jupyterlab
[I 2022-11-30 17:35:51.895 LabApp] JupyterLab application directory is /home/joelye/anaconda3/envs/rlpyt/share/jupyter/lab

[I 17:35:51.904 NotebookApp] Serving notebooks from local directory: /home/joelye
info 17:35:51.906: [W 2022-11-30 17:35:51.880 LabApp] 'iopub_data_rate_limit' has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.
[W 2022-11-30 17:35:51.880 LabApp] 'port' has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.
[W 2022-11-30 17:35:51.880 LabApp] 'port' has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.
[W 2022-11-30 17:35:51.880 LabApp] 'port' has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.
[I 2022-11-30 17:35:51.894 LabApp] JupyterLab extension loaded from /home/joelye/anaconda3/envs/rlpyt/lib/python3.7/site-packages/jupyterlab
[I 2022-11-30 17:35:51.895 LabApp] JupyterLab application directory is /home/joelye/anaconda3/envs/rlpyt/share/jupyter/lab
[I 17:35:51.904 NotebookApp] Serving notebooks from local directory: /home/joelye

[I 17:35:51.904 NotebookApp] Jupyter Notebook 6.4.3 is running at:
info 17:35:51.907: [W 2022-11-30 17:35:51.880 LabApp] 'iopub_data_rate_limit' has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.
[W 2022-11-30 17:35:51.880 LabApp] 'port' has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.
[W 2022-11-30 17:35:51.880 LabApp] 'port' has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.
[W 2022-11-30 17:35:51.880 LabApp] 'port' has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.
[I 2022-11-30 17:35:51.894 LabApp] JupyterLab extension loaded from /home/joelye/anaconda3/envs/rlpyt/lib/python3.7/site-packages/jupyterlab
[I 2022-11-30 17:35:51.895 LabApp] JupyterLab application directory is /home/joelye/anaconda3/envs/rlpyt/share/jupyter/lab
[I 17:35:51.904 NotebookApp] Serving notebooks from local directory: /home/joelye
[I 17:35:51.904 NotebookApp] Jupyter Notebook 6.4.3 is running at:

[I 17:35:51.904 NotebookApp] http://localhost:8897/?token=a9404c6172f63d6a72c92b24d340afc550f2a081e31c2c68
info 17:35:51.908: [W 2022-11-30 17:35:51.880 LabApp] 'iopub_data_rate_limit' has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.
[W 2022-11-30 17:35:51.880 LabApp] 'port' has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.
[W 2022-11-30 17:35:51.880 LabApp] 'port' has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.
[W 2022-11-30 17:35:51.880 LabApp] 'port' has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.
[I 2022-11-30 17:35:51.894 LabApp] JupyterLab extension loaded from /home/joelye/anaconda3/envs/rlpyt/lib/python3.7/site-packages/jupyterlab
[I 2022-11-30 17:35:51.895 LabApp] JupyterLab application directory is /home/joelye/anaconda3/envs/rlpyt/share/jupyter/lab
[I 17:35:51.904 NotebookApp] Serving notebooks from local directory: /home/joelye
[I 17:35:51.904 NotebookApp] Jupyter Notebook 6.4.3 is running at:
[I 17:35:51.904 NotebookApp] http://localhost:8897/?token=a9404c6172f63d6a72c92b24d340afc550f2a081e31c2c68

info 17:35:51.911: Process Execution: > ~/anaconda3/envs/rlpyt/bin/python (daemon) ~/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/pythonFiles/vscode_datascience_helpers/getServerInfo.py
> ~/anaconda3/envs/rlpyt/bin/python (daemon) ~/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/pythonFiles/vscode_datascience_helpers/getServerInfo.py
[I 17:35:51.905 NotebookApp]  or http://<IP_ADDRESS>:8897/?token=a9404c6172f63d6a72c92b24d340afc550f2a081e31c2c68
info 17:35:51.917: [W 2022-11-30 17:35:51.880 LabApp] 'iopub_data_rate_limit' has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.
[W 2022-11-30 17:35:51.880 LabApp] 'port' has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.
[W 2022-11-30 17:35:51.880 LabApp] 'port' has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.
[W 2022-11-30 17:35:51.880 LabApp] 'port' has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.
[I 2022-11-30 17:35:51.894 LabApp] JupyterLab extension loaded from /home/joelye/anaconda3/envs/rlpyt/lib/python3.7/site-packages/jupyterlab
[I 2022-11-30 17:35:51.895 LabApp] JupyterLab application directory is /home/joelye/anaconda3/envs/rlpyt/share/jupyter/lab
[I 17:35:51.904 NotebookApp] Serving notebooks from local directory: /home/joelye
[I 17:35:51.904 NotebookApp] Jupyter Notebook 6.4.3 is running at:
[I 17:35:51.904 NotebookApp] http://localhost:8897/?token=a9404c6172f63d6a72c92b24d340afc550f2a081e31c2c68
[I 17:35:51.905 NotebookApp]  or http://<IP_ADDRESS>:8897/?token=a9404c6172f63d6a72c92b24d340afc550f2a081e31c2c68

info 17:35:51.920: Process Execution: > ~/anaconda3/envs/rlpyt/bin/python (daemon) ~/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/pythonFiles/vscode_datascience_helpers/getServerInfo.py
> ~/anaconda3/envs/rlpyt/bin/python (daemon) ~/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/pythonFiles/vscode_datascience_helpers/getServerInfo.py
[I 17:35:51.905 NotebookApp] Use Control-C to stop this server and shut down all kernels (twice to skip confirmation).
info 17:35:51.923: [W 2022-11-30 17:35:51.880 LabApp] 'iopub_data_rate_limit' has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.
[W 2022-11-30 17:35:51.880 LabApp] 'port' has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.
[W 2022-11-30 17:35:51.880 LabApp] 'port' has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.
[W 2022-11-30 17:35:51.880 LabApp] 'port' has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.
[I 2022-11-30 17:35:51.894 LabApp] JupyterLab extension loaded from /home/joelye/anaconda3/envs/rlpyt/lib/python3.7/site-packages/jupyterlab
[I 2022-11-30 17:35:51.895 LabApp] JupyterLab application directory is /home/joelye/anaconda3/envs/rlpyt/share/jupyter/lab
[I 17:35:51.904 NotebookApp] Serving notebooks from local directory: /home/joelye
[I 17:35:51.904 NotebookApp] Jupyter Notebook 6.4.3 is running at:
[I 17:35:51.904 NotebookApp] http://localhost:8897/?token=a9404c6172f63d6a72c92b24d340afc550f2a081e31c2c68
[I 17:35:51.905 NotebookApp]  or http://<IP_ADDRESS>:8897/?token=a9404c6172f63d6a72c92b24d340afc550f2a081e31c2c68
[I 17:35:51.905 NotebookApp] Use Control-C to stop this server and shut down all kernels (twice to skip confirmation).

[C 17:35:51.914 NotebookApp]

    To access the notebook, open this file in a browser:
        file:///home/joelye/.local/share/jupyter/runtime/nbserver-3931-open.html
    Or copy and paste one of these URLs:
        http://localhost:8897/?token=a9404c6172f63d6a72c92b24d340afc550f2a081e31c2c68
     or http://<IP_ADDRESS>:8897/?token=a9404c6172f63d6a72c92b24d340afc550f2a081e31c2c68
info 17:35:51.927: [W 2022-11-30 17:35:51.880 LabApp] 'iopub_data_rate_limit' has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.
[W 2022-11-30 17:35:51.880 LabApp] 'port' has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.
[W 2022-11-30 17:35:51.880 LabApp] 'port' has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.
[W 2022-11-30 17:35:51.880 LabApp] 'port' has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.
[I 2022-11-30 17:35:51.894 LabApp] JupyterLab extension loaded from /home/joelye/anaconda3/envs/rlpyt/lib/python3.7/site-packages/jupyterlab
[I 2022-11-30 17:35:51.895 LabApp] JupyterLab application directory is /home/joelye/anaconda3/envs/rlpyt/share/jupyter/lab
[I 17:35:51.904 NotebookApp] Serving notebooks from local directory: /home/joelye
[I 17:35:51.904 NotebookApp] Jupyter Notebook 6.4.3 is running at:
[I 17:35:51.904 NotebookApp] http://localhost:8897/?token=a9404c6172f63d6a72c92b24d340afc550f2a081e31c2c68
[I 17:35:51.905 NotebookApp]  or http://<IP_ADDRESS>:8897/?token=a9404c6172f63d6a72c92b24d340afc550f2a081e31c2c68
[I 17:35:51.905 NotebookApp] Use Control-C to stop this server and shut down all kernels (twice to skip confirmation).
[C 17:35:51.914 NotebookApp]

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

info 17:35:52.433: Connecting to process server
info 17:35:52.433: Connecting server kernel http://localhost:8897/
info 17:35:52.434: Creating server with url : http://localhost:8897/
info 17:35:52.544: Connection complete server
info 17:35:52.544: Server started.
warn 17:35:52.577: Falling back to Python Execution Service due to failure in daemon h [Error]: Failed to execute using the daemon, Traceback (most recent call last):
  File "/home/joelye/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/pythonFiles/vscode_datascience_helpers/getServerInfo.py", line 19, in <module>
    for si in server_list:
  File "/home/joelye/anaconda3/envs/rlpyt/lib/python3.7/site-packages/notebook/notebookapp.py", line 2387, in list_running_servers
    with io.open(os.path.join(runtime_dir, file_name), encoding='utf-8') as f:
FileNotFoundError: [Errno 2] No such file or directory: '/home/joelye/.local/share/jupyter/runtime/nbserver-30473.json'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/joelye/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/pythonFiles/vscode_datascience_helpers/daemon/daemon_python.py", line 54, in _decorator
    return func(self, *args, **kwargs)
  File "/home/joelye/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/pythonFiles/vscode_datascience_helpers/daemon/daemon_python.py", line 135, in m_exec_file
    return self._execute_and_capture_output(exec_file)
  File "/home/joelye/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/pythonFiles/vscode_datascience_helpers/daemon/daemon_python.py", line 106, in _execute_and_capture_output
    func()
  File "/home/joelye/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/pythonFiles/vscode_datascience_helpers/daemon/daemon_python.py", line 132, in exec_file
    runpy.run_path(file_name, globals())
  File "/home/joelye/anaconda3/envs/rlpyt/lib/python3.7/runpy.py", line 263, in run_path
    pkg_name=pkg_name, script_name=fname)
  File "/home/joelye/anaconda3/envs/rlpyt/lib/python3.7/runpy.py", line 96, in _run_module_code
    mod_name, mod_spec, pkg_name, script_name)
  File "/home/joelye/anaconda3/envs/rlpyt/lib/python3.7/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/home/joelye/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/pythonFiles/vscode_datascience_helpers/getServerInfo.py", line 43, in <module>
    ["jupyter", "notebook", "list", "--jsonlist"], stdout=PIPE, stderr=PIPE
  File "/home/joelye/anaconda3/envs/rlpyt/lib/python3.7/subprocess.py", line 488, in run
    with Popen(*popenargs, **kwargs) as process:
  File "/home/joelye/anaconda3/envs/rlpyt/lib/python3.7/subprocess.py", line 800, in __init__
    restore_signals, start_new_session)
  File "/home/joelye/anaconda3/envs/rlpyt/lib/python3.7/subprocess.py", line 1551, in _execute_child
    raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: 'jupyter': 'jupyter'

    at a.processResponse (/home/joelye/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/out/extension.node.js:2:881364)
    at a.execFileWithDaemon (/home/joelye/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/out/extension.node.js:2:881711)
    at runNextTicks (node:internal/process/task_queues:61:5)
    at processImmediate (node:internal/timers:437:9)
    at a.exec (/home/joelye/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/out/extension.node.js:2:878756)
    at d.wrapCall (/home/joelye/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/out/extension.node.js:2:922335)
    at E.getRunningJupyterServers (/home/joelye/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/out/extension.node.js:2:351105) {
  category: 'daemon'
}
info 17:35:52.605: Process Execution: > ~/anaconda3/envs/rlpyt/bin/python ~/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/pythonFiles/vscode_datascience_helpers/getServerInfo.py
> ~/anaconda3/envs/rlpyt/bin/python ~/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/pythonFiles/vscode_datascience_helpers/getServerInfo.py
info 17:35:52.657: Process Execution: > ~/anaconda3/envs/rlpyt/bin/python (daemon) ~/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/pythonFiles/vscode_datascience_helpers/getServerInfo.py
> ~/anaconda3/envs/rlpyt/bin/python (daemon) ~/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/pythonFiles/vscode_datascience_helpers/getServerInfo.py
info 17:35:52.707: Process Execution: > ~/anaconda3/envs/rlpyt/bin/python (daemon) ~/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/pythonFiles/vscode_datascience_helpers/getServerInfo.py
> ~/anaconda3/envs/rlpyt/bin/python (daemon) ~/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/pythonFiles/vscode_datascience_helpers/getServerInfo.py
info 17:36:17.138: Starting interactive window for resource '/home/joelye/projects/fingerprint_gelsight/analyze.py'
info 17:36:17.346: Attempting to start a server because of preload conditions ...
info 17:36:17.389: Preferred Remote kernel for Interactive-1.interactive is undefined
info 17:36:17.457: Starting Jupyter Session id = 'startUsingPythonInterpreter:.jvsc74a57bd0a147e1c999bda7a4e0e03e52e4a39eeff00e88a4d3ebd8feb03c46e4d8141747./home/joelye/anaconda3/envs/py10_2/python./home/joelye/anaconda3/envs/py10_2/python.-m#ipykernel_launcher' (Python Path: /home/joelye/anaconda3/envs/py10_2, EnvType: Conda, EnvName: 'py10_2', Version: 3.10.7) for 'Interactive-1.interactive' (disableUI=false)
[I 17:36:17.496 NotebookApp] Creating new notebook in
/home/joelye/anaconda3/envs/rlpyt/lib/python3.7/json/encoder.py:257: UserWarning: date_default is deprecated since jupyter_client 7.0.0. Use jupyter_client.jsonutil.json_default.
  return _iterencode(o, 0)
info 17:36:17.552: installMissingDependencies /home/joelye/anaconda3/envs/py10_2/bin/python, ui.disabled=false for resource '/home/joelye/projects/fingerprint_gelsight/analyze.py'
info 17:36:18.107: Process Execution: > ~/anaconda3/envs/py10_2/bin/python -c "import ipykernel"
> ~/anaconda3/envs/py10_2/bin/python -c "import ipykernel"
info 17:36:18.890: Spec argv[0] updated from '/home/joelye/anaconda3/envs/py10_2/bin/python' to '/home/joelye/anaconda3/envs/py10_2/bin/python'
[I 17:36:19.216 NotebookApp] Kernel started: 6d5165a6-e846-412b-bdd4-8e0e49d68aae, name: python3107jvsc74a57bd0a147e1c999bda7a4e0e03e52e4a39eeff00e88a4d3ebd8feb03c46e4d8141747
info 17:36:19.279: Waiting for idle on (kernel): 6d5165a6-e846-412b-bdd4-8e0e49d68aae -> unknown
[W 17:36:19.303 NotebookApp] delete /analyze.py-jvsc-68cfd96f-74f9-4928-a4c3-8dec4d3255e80c7ae6df-03b2-404b-8c79-edb19b639594.ipynb
info 17:36:20.770: Finished waiting for idle on (kernel): 6d5165a6-e846-412b-bdd4-8e0e49d68aae -> idle
info 17:36:20.771: Started session for kernel startUsingPythonInterpreter:.jvsc74a57bd0a147e1c999bda7a4e0e03e52e4a39eeff00e88a4d3ebd8feb03c46e4d8141747./home/joelye/anaconda3/envs/py10_2/python./home/joelye/anaconda3/envs/py10_2/python.-m#ipykernel_launcher
info 17:36:20.771: Finished connecting kernel startUsingPythonInterpreter:.jvsc74a57bd0a147e1c999bda7a4e0e03e52e4a39eeff00e88a4d3ebd8feb03c46e4d8141747./home/joelye/anaconda3/envs/py10_2/python./home/joelye/anaconda3/envs/py10_2/python.-m#ipykernel_launcher
/home/joelye/anaconda3/envs/rlpyt/lib/python3.7/json/encoder.py:257: UserWarning: date_default is deprecated since jupyter_client 7.0.0. Use jupyter_client.jsonutil.json_default.
  return _iterencode(o, 0)
info 17:36:20.881: UpdateWorkingDirectoryAndPath in Kernel
info 17:36:20.884: Executing silently Code (idle) = import types as _VSCODE_types\nimport os\nimport hashlib as _VSCODE_hashlib\nfrom IPython import get_ip
info 17:36:20.960: Executing silently Code (completed) = import types as _VSCODE_types\nimport os\nimport hashlib as _VSCODE_hashlib\nfrom IPython import get_ip
info 17:36:20.961: Waiting for idle on (kernel): 6d5165a6-e846-412b-bdd4-8e0e49d68aae -> idle
info 17:36:20.962: Finished waiting for idle on (kernel): 6d5165a6-e846-412b-bdd4-8e0e49d68aae -> idle
info 17:36:20.979: Executing silently Code (idle) = __file__ = '/home/joelye/projects/fingerprint_gelsight/analyze.py'
info 17:36:21.38: Executing silently Code (completed) = __file__ = '/home/joelye/projects/fingerprint_gelsight/analyze.py'
info 17:36:21.44: Generated code for 1 = <ipython-input-1-0d03f167214e> with 33 lines
info 17:36:30.245: Cell 1 executed with state Success
info 17:37:5.321: Executing silently Code (idle) = # Query Jupyter server for the info about a dataframe\nimport json as _VSCODE_json\nimport builtins as
info 17:37:5.388: Executing silently Code (completed) = # Query Jupyter server for the info about a dataframe\nimport json as _VSCODE_json\nimport builtins as
info 17:37:5.389: Executing silently Code (idle) = import builtins\n_rwho_ls = %who_ls\nbuiltins.print(_VSCODE_getVariableTypes(_rwho_ls))
info 17:37:5.441: Executing silently Code (completed) = import builtins\n_rwho_ls = %who_ls\nbuiltins.print(_VSCODE_getVariableTypes(_rwho_ls))

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

I'll add that my current situation is slightly manageable but still very strange --
I manually set LD_LIBRARY_PATH (which is the main cuda env variable that fails my later code) to either my desired setting or to an empty string; this fails the first time I run the cells but works the second time (I have no idea why this happens).

Environment variables for kernels are best sourced from .env files.
I.e. if you want to configure environment variables for a kernel, then add them into a .env file within the root directory of your vscode workspace folder.
When making changes to the bashrc file you'll need to exit VS Code completely for the variables to be loaded into processes spawed by VS Code. (unless you're using a kernel that manually launches a bash process or the like)

How is Jupyter initializing with both these environments? How can I specify which one to initialize with? The kernel defaults to py10_2 in the interactive window on fresh restarts. Finally, why does jupyter seem to attempt (and fail) to initialize conda a few times before succeeding (in a different mode)?

We activate conda environments using the command conda run
That command is used to run python code and internally that command will activate the necessary conda environment and source the necessary env variables.
Once again, my suggestion would be to use a .env file to customize environment variagbles.

Please feel free to re-open this issue or ask questions in the discussions channel, if the above doesn't answer all of your queries.