Multi-root workspace with hidden directories uses wrong python interpreter

Type: Bug

Behaviour
If you create a multi-root workspace, select different interpreters for each workspace and create python files inside a hidden directory (folder whose name starts with '.'), the wrong interpreter gets used for syntax highlighting and code completion. It seems to just use the first workspace's interpreter.
Steps to reproduce:

Create a multi-root workspace, and create separate virtual environments for each of them.

mkdir ws1 ws2
python3.11 -m venv ws1/.venv
python3.11 -m venv ws2/.venv
code ws1/ ws2/

Install different libraries in each virtual env

./ws1/.venv/bin/python -m pip install PyJwt
./ws2/.venv/bin/python -m pip install pydantic

Create 4 files, ./ws1/ws1.py ./ws1/.hidden_folder/ws1_hidden.py, ./ws2/ws2.py ./ws2/.hidden_folder/ws2_hidden.py, with exact same content:

from jwt import decode
from pydantic import model_serializer

Select the interpreter for both workspaces in vscode
Open all 4 files, and notice that the syntax highlighting is incorrect for ./ws2/.hidden_folder/ws2_hidden.py. "Go to Definition" also open the library files in ws1 instead of ws2.

Diagnostic data

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

2024-12-05 11:54:17.874 [info] Telemetry is disabled
2024-12-05 11:54:17.874 [info] Telemetry level is off
2024-12-05 11:54:17.874 [info] Experiments are disabled, only manually opted experiments are active.
2024-12-05 11:54:17.874 [warning] Dir "/home/cnoor/work/scratch/pythonMultiRoot/ws1/.pixi/envs" is not watchable (directory does not exist)
2024-12-05 11:54:17.874 [warning] Dir "/home/cnoor/work/scratch/pythonMultiRoot/ws2/.pixi/envs" is not watchable (directory does not exist)
2024-12-05 11:54:17.874 [info] Default formatter is set to ms-python.black-formatter for workspace /home/cnoor/work/scratch/pythonMultiRoot/ws1
2024-12-05 11:54:17.874 [info] Default formatter is set to ms-python.black-formatter for workspace /home/cnoor/work/scratch/pythonMultiRoot/ws2
2024-12-05 11:54:17.874 [info] Not enabling terminal env var experiment in multiroot remote workspaces
2024-12-05 11:54:17.874 [info] Starting Environment refresh
2024-12-05 11:54:17.874 [info] Starting Environment refresh
2024-12-05 11:54:17.874 [info] > pixi --version
2024-12-05 11:54:17.874 [info] > hatch env show --json
2024-12-05 11:54:17.874 [info] cwd: ~/work/scratch/pythonMultiRoot/ws2
2024-12-05 11:54:17.874 [info] > hatch env show --json
2024-12-05 11:54:17.874 [info] cwd: ~/work/scratch/pythonMultiRoot/ws1
2024-12-05 11:54:17.874 [info] Python interpreter path: ./.venv/bin/python
2024-12-05 11:54:18.546 [info] > /opt/bb/bin/python3.12 -I ~/.vscode-server/extensions/ms-python.python-2024.14.1/python_files/get_output_via_markers.py ~/.vscode-server/extensions/ms-python.python-2024.14.1/python_files/interpreterInfo.py
2024-12-05 11:54:18.583 [info] > ~/work/scratch/pythonMultiRoot/ws1/.venv/bin/python -I ~/.vscode-server/extensions/ms-python.python-2024.14.1/python_files/get_output_via_markers.py ~/.vscode-server/extensions/ms-python.python-2024.14.1/python_files/interpreterInfo.py
2024-12-05 11:54:18.584 [info] Environments refresh paths discovered: 1069 milliseconds
2024-12-05 11:54:18.586 [info] Environments refresh paths discovered: 1072 milliseconds
2024-12-05 11:54:18.646 [info] > ~/work/scratch/pythonMultiRoot/ws2/.venv/bin/python -I ~/.vscode-server/extensions/ms-python.python-2024.14.1/python_files/get_output_via_markers.py ~/.vscode-server/extensions/ms-python.python-2024.14.1/python_files/interpreterInfo.py
2024-12-05 11:54:18.669 [info] Environments refresh finished (event): 1154 milliseconds
2024-12-05 11:54:18.672 [info] Environment refresh took 1157 milliseconds
2024-12-05 11:54:18.677 [info] > ~/.pyenv/bin/pyenv which python
2024-12-05 11:54:18.677 [info] cwd: ~/work/scratch/pythonMultiRoot/ws1
2024-12-05 11:54:18.704 [info] Environments refresh finished (event): 1190 milliseconds
2024-12-05 11:54:18.705 [info] Environment refresh took 1192 milliseconds
2024-12-05 11:54:18.863 [info] Not enabling terminal env var experiment in multiroot remote workspaces
2024-12-05 11:54:19.691 [info] Starting Environment refresh
2024-12-05 11:54:19.693 [info] Python interpreter path: ./.venv/bin/python
2024-12-05 11:54:19.753 [info] Environments refresh paths discovered: 62 milliseconds
2024-12-05 11:54:19.753 [info] Environments refresh finished (event): 62 milliseconds
2024-12-05 11:54:19.755 [info] Environment refresh took 64 milliseconds
2024-12-05 11:54:19.767 [info] > ~/.pyenv/bin/pyenv which python
2024-12-05 11:54:19.767 [info] cwd: ~/work/scratch/pythonMultiRoot/ws2
2024-12-05 11:54:20.517 [info] Not enabling terminal env var experiment in multiroot remote workspaces
2024-12-05 11:54:20.518 [info] Starting Pylance language server.
2024-12-05 11:54:25.409 [info] Python interpreter path: ./.venv/bin/python
2024-12-05 11:54:29.217 [info] Starting Pylance language server.
2024-12-05 11:54:34.332 [info] Python interpreter path: ./.venv/bin/python
2024-12-05 11:55:09.061 [info] Python interpreter path: ./.venv/bin/python
2024-12-05 12:06:58.579 [info] Python interpreter path: ./.venv/bin/python
2024-12-05 12:07:01.722 [info] Python interpreter path: ./.venv/bin/python
2024-12-05 12:07:03.539 [info] Python interpreter path: ./.venv/bin/python
2024-12-05 12:07:04.784 [info] Python interpreter path: ./.venv/bin/python
2024-12-05 12:07:06.471 [info] Python interpreter path: ./.venv/bin/python
2024-12-05 12:08:10.626 [info] Python interpreter path: ./.venv/bin/python
2024-12-05 12:08:10.867 [info] Not enabling terminal env var experiment in multiroot remote workspaces
2024-12-05 12:08:10.872 [warning] could not find a pixi interpreter for the interpreter at /home/cnoor/work/scratch/pythonMultiRoot/ws1/.venv/bin/python
2024-12-05 12:08:10.998 [info] Send text to terminal: source /home/cnoor/work/scratch/pythonMultiRoot/ws1/.venv/bin/activate

Extension version: 2024.4.1
VS Code version: Code 1.91.1 (f1e16e1e6214d7c44d078b1f0607b2388f29d729, 2024-07-09T22:06:49.809Z)
OS version: Windows_NT x64 10.0.19045
Modes:
Remote OS version: Linux x64 <IP_ADDRESS>-microsoft-standard-WSL2
Remote OS version: Linux x64 <IP_ADDRESS>-microsoft-standard-WSL2

Python version (& distribution if applicable, e.g. Anaconda): 3.12.7
Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): Venv
Value of the python.languageServer setting: Pylance

User Settings

Multiroot scenario, following user settings may not apply:

languageServer: "Pylance"

Installed Extensions

Extension Name
Extension Id
Version

autoDocstring - Python Docstring Generator
njpwerner.autodocstring
0.6.1

Data Workspace
ms-mssql.data-workspace-vscode
0.5.0

GitLens — Git supercharged
eamodio.gitlens
15.6.1

Increment Selection
albymor.increment-selection
0.2.0

JavaScript Debugger
ms-vscode.js-debug
1.91.0

Jest
Orta.vscode-jest
6.2.5

Prettier - Code formatter
esbenp.prettier-vscode
11.0.0

Pylance
ms-python.vscode-pylance
2024.10.1

Python
ms-python.python
2024.14.1

Python Debugger
ms-python.debugpy
2024.8.0

Python Environment Manager
donjayamanne.python-environment-manager
1.2.4

Python Extension Pack
donjayamanne.python-extension-pack
1.7.0

Table Visualizer for JavaScript Profiles
ms-vscode.vscode-js-profile-table
1.0.9

transpose
v4run.transpose
0.0.6

vscode-styled-components
styled-components.vscode-styled-components
1.7.8

YAML
redhat.vscode-yaml
1.15.0

System Info

Item
Value

CPUs
12th Gen Intel(R) Core(TM) i7-12800H (20 x 2803)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
undefined

Memory (System)
63.67GB (37.66GB free)

Process Argv
--file-uri vscode-remote://dev-container%2B7b22686f737450617468223a225c5c5c5c77736c2e6c6f63616c686f73745c5c5562756e74752d32322e30345c5c686f6d655c5c636e6f6f725c5c776f726b5c5c736372617463685c5c646576436f6d62696e6564436f6e7461696e6572222c226c6f63616c446f636b6572223a66616c73652c22636f6e66696746696c65223a7b22246d6964223a312c2270617468223a222f686f6d652f636e6f6f722f776f726b2f736372617463682f646576436f6d62696e6564436f6e7461696e65722f2e646576636f6e7461696e65722f646576636f6e7461696e65722e6a736f6e222c22736368656d65223a227673636f64652d66696c65486f7374227d7d/vscode/dev_workspace.code-workspace

Screen Reader
no

VM
0%

Item
Value

Remote
Dev Container: dev_workspace

OS
Linux x64 <IP_ADDRESS>-microsoft-standard-WSL2

CPUs
12th Gen Intel(R) Core(TM) i7-12800H (2 x 0)

Memory (System)
24.46GB (20.03GB free)

VM
0%

Item
Value

Remote
WSL: Ubuntu-22.04

OS
Linux x64 <IP_ADDRESS>-microsoft-standard-WSL2

CPUs
12th Gen Intel(R) Core(TM) i7-12800H (2 x 0)

Memory (System)
24.46GB (20.03GB free)

VM
0%

For ./ws1/ws1.py and ./ws1/.hidden_folder/ws1_hidden.py the syntax highlighting correct shows jwt is installed, but pydantic is not
For ./ws2/ws2.py the syntax highlighting correct shows pydantic is installed, but jwt is not
But, for ./ws2/.hidden_folder/ws2_hidden.py, it incorrectly shows jwt is installed, but pydantic is not. The file seems to use ws1's interpretter.

@Cnoor0171 When you run the hidden script does it pick the right environment?

Yes. If I run the script using python.execInTerminal or debugpy.debugInTerminal vscode commands, it does use the correct environment.


Bumps ethereumjs-util, ethereumjs-wallet, web3 and websocket deps

This PR removes the need to compile with node-gyp :rocket:
Install stats (via github)
This PR: 35.099s
Current develop: 94.833s

Coverage increased (+0.2%) to 82.75% when pulling 6740ec80f03421be9f75384dd826e05e02e8572a on Tenderly:develop into 196fcce92f41e3b162295d283e0904c359b9ad4c on trufflesuite:develop.

Coverage increased (+0.2%) to 82.75% when pulling 6740ec80f03421be9f75384dd826e05e02e8572a on Tenderly:develop into 196fcce92f41e3b162295d283e0904c359b9ad4c on trufflesuite:develop.

Hey @gnidan, @davidmurdoch
This PR and https://github.com/trufflesuite/ganache-cli/pull/770 are some the last few things needed to completely node-gyp from the entire ecosystem.
Can you take a look at them?
Thanks!

Hey @davidmurdoch @seesemichaelj
I've resolved the conflicts here and in https://github.com/trufflesuite/ganache-cli/pull/770. Can you take a look?
Cheers!

Merging this would be greatly appreciated since it also resolves websocket-related security vulnerabilities that currently have to be resolved manually by ganache-core consumers.

Thanks @nebojsa94!


hotfix: Add a.txt

This PR is a to test #10.

Branch name does not start with feature/ or fix/.

The workflow has to be triggered when a pull request changes its target.

hotfix/* branches are allowed to target only ["1.0","2.0"] branch(es).

Good.


feat: "Custom splash screen" or "not hiding the index.html content on app start"

It would be nice if the index.html wasn't hidden in angular + ionic application.
In clean Angular project without Ionic the index.html content (div elements, etc.) isn't hidden on start-up. So it's possible to insert some content within the  tag and make a nice splash screen.
In Ionic project the content you place in  is hidden until all the *.js files are loaded. So all the "splash screen" effect is lost.
Angular only app generated by the Angular CLI:

Ionic+Angular app generated by the Ionic CLI:

The content added to the app-root tag in index.html:
<app-root>

INDEX.HTML

   </app-root>
As you can see the content is gone in  the ionic+angular app.
Article that i used to make splash-screen:
https://medium.com/@tomastrajan/how-to-style-angular-application-loading-with-angular-cli-like-a-boss-cdd4f5358554
Maybe it is possible not to hide this content?

Article that i used to make splash-screen:
https://medium.com/@tomastrajan/how-to-style-angular-application-loading-with-angular-cli-like-a-boss-cdd4f5358554

Any comments about this?

So I did a quick check to see if the content is actually getting rendered in app-root, which it is.

What I think is happening here is the initial rendering of app-root shows "INDEX.HTML" quickly, but the app has been bootstrapped, so it's only visible for a few milliseconds. You can more visibly see that index.html is there if you emulate slower networks.

And a live example can be seen at
https://startrack-ng.web.app
So I'm not sure this is an actual issue, but more just the app is bootstrapping so fast.

@mhartington Thanks for the reply.
I saw that the index.html is been rendered. But after small amount of time the  content is been hidden for some reason of ionic bootstrap/startup. My suggestion was not to hide the index.html  content. So we can make dynamic splash screen and not use static cordova splash screen. Now you can only add css to the index.html  tag that would not be "hidden".

Again the reason is not from Ionic, just that Angular and everything is bootstrapped and ready to load.
In theory, you could defer the main bootstrapping in main.ts and have something. Play an animation, fire an event, then on the event fire, you load the app. But that's beyond the scope of this issue and does not have anything to do with Ionic.
Going to close this is this as this is not an issue with broken functionality or feature request. You should ask this on the Ionic forum
https://forum.ionicframework.com


Migrate content from Wordpress to Prismic.

Export content from Wordpress into the format that prismic.io expects as an import.
https://prismic.io/docs/full-import-reference

Busy  in the process. Just some notes:

[x] Author IDs need populating
[ ] Nicola Cook and Lousja as authors doesn't work (Wordpress doesn't support multi-contributors)
[x] Some WP articles have added titles to galleries, let's apply those properly e.g. https://wellcomecollection.org/articles/outsiders-the-prostitute
[ ] How do we attach digital stories... There are a few ideas, potentially creating them as separate  content type...

Close in favour of #814


Non-smooth Projectiles

Describe the bug
When firing most weapons with custom projectiles, they move in a jittery way, rather than smoothly interpolating between positions like everything else in Minecraft.
To Reproduce
Steps to reproduce the behavior:

Spawn a projectile weapon (Such as the Coin Tosser or Snowballer. Multi-projectile weapons make it easier to see)
Fire it
Note how the projectiles move

Expected behavior
Smooth projectile movement, at least client-side
Screenshots
Still images won't help with this.
Crash Reports & Logs
Not applicable
Version Info (please complete the following information):

QuiverBow: Restrung 0.4.0
Forge <IP_ADDRESS>60
Minecraft 1.12.2

Additional context
Tested with only Quiverbow and Patchouli.
Sorry for making so many issues, but I figure it's best to report them separately instead of in one conglomerate issue.
It's what the template suggests, too, so...

I figure it's best to report them separately instead of in one conglomerate issue
Absolutely. Issues are fixed individually, so it becomes harder to track which are fixed if a single issue report contains multiple unrelated issues,

Projectile movement seems smooth to me. I'll need a video of the issue. Don't make a GIF, the compression artifacts will make the issue harder to see.

Huh.
Maybe I was just tired that day or something, because I'm not seeing it now.
I'll be sure to reopen the issue with a video if I happen to catch it, but for whatever reason, it seems fine now.


Use mailhog on mixed environment server?

Our server runs both the production and staging environments for a website.
I want to use mailhog, but only for the staging site.
If there an easy way to confgure mailhog to only catch emails sent from the staging site and not the live one?

Sorry if I'm a little direct here but:
Make the staging site send e-mails to Malhog and make the live site not send e-mails to Mailhog?

@C-Duv that's what I'm asking how to do 😄
When I've used Mailhog in the past, it's just been on a VM and I have not had to configure the application specifically to send emails to Mailhog, it's just worked out of the box.

This has nothing to do with MailHog then. It's just a question of how you configure your applications/websites.
In the configuration of your staging website you have the IP/FQDN + port of the MailHog server as outgoing (SMTP) server.
So in the configuration of your live website use the IP/FQDN + port of a "real" outgoing (SMTP) server (GMail, OVH, etc. whatever it is...).

@C-Duv what aout if you are just using PHP's mail() function, and no specfic SMTP config?

Then you can't: because PHP mail() uses sendmail and I believe sendmail does not support multiple "outputs".
Maybe the $additional_parameters parameter of PHP mail()?
Or maybe MailHog could support an e-mail header that PHP would send (via $additional_headers parameter of mail()) and would tell MailHog to not catch and send it to the Internet.
But in the end it's not MailHog's job to do that... It's an SMTP server without Internet output (unless manually asked to) and an integrated webmail. It's goal is, to my point of view, to help developers during development phases without risking to send e-mails out in the Internet.

@C-Duv cool, I get ya 👍
To be fair, we should be using SMTP, but thought I'd ask about PHP mail() incase it was possible.

Indeed, nothing todo with Mailhog. Sendmail will be used for php and will relay to localhost and maybe therefor Mailhog will pick it up.
tip: stop using native mail and implement for example the symfony mailer. Easy lib and easy to configure. Even as an one on one replacement.


Add heroku recharging page

Currently we are using the heroku free usage tier, which does not allow an app to run for more than 18 hours in a 24 hour period.
Create a custom html page for errors and maintenance that heroku will serve up in the event that our quota is hit and the app is offline
It would be useful to include the Google analytics hooks on this page as well, so we can track how often people are unable to view sermons due to downtime.
https://devcenter.heroku.com/articles/error-pages#customize-pages

Heroku has changed their free usage tier. I believe my account has enough credits to run full time free of charge.


Add GitLab support

Can't go through GraphQL yet because of https://gitlab.com/gitlab-org/gitlab/-/issues/196170

v4 REST API should be usable, but perhaps punt for a while

I was confused for a bit because the configuration specification in the README.md contains:
# Repos not on GitHub to synchronize.
[git.repos]
asm = "https://gitlab.ow2.org/asm/asm.git"

This led me to try to gitout some GitLab repositories. Once I cloned them and checked with git log this error is output:

$ git log
fatal: your current branch 'master' does not have any commits yet

Maybe, the README.md should clarify that GitLab doesn't work yet or replace the example URL?

Does git log work in bare repositories?
This feature is for discovering your repositories through your GitLab username. You're always able to clone any git repo from anywhere if you list the full URL.

Does git log work in bare repositories?

Yes. If I clone a repository (e.g. git clone --bare https://github.com/JakeWharton/gitout.git) then I can successfully invoke git log.

This feature is for discovering your repositories through your GitLab username.

Thanks for the clarification.

You're always able to clone any git repo from anywhere if you list the full URL.

The full URL, e.g. https://gitlab.com/oeffi/oeffi or https://gitlab.com/oeffi/oeffi.git works for cloning it seems but then git log fails as stated before.

Thanks I'll play with it. We delegate everything to libgit2 which can have differing behavior from git proper. At worst, I just create a repro and file a bug upstream.


wire data must be bytes

Should fix #892

no clue what travis has changed again - pypy and cpy 3.3 interpreters are missing. I am merging this nevertheless ..


Update MD file on new branch 2017-21-03_15-12-55

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestRef.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Encryption is currently not used

There are no calls to the encryption / decryption methods in the latest version 1.6.1
Therefore all account data is visible in the Launchbuddy.bin

Closing as merged pull request fixes the issue.


Cameras not being detected on published app, works just fine when build set to Debug.

I am using the camera view to take pictures, it works well when I set the build to Debug however as soon as I publish the app and change build to Release the app crashes. It's almost as if it no longer detects the cameras.  I have tried it with this sample (https://github.com/jfversluis/MauiCameraMauiSample) as well with the same issues, is there something I am doing wrong ?
See screenshots attached.

It looks like you're missing camera permissions inside your manifest. In case you are compiling versus api 33 (android:targetSdkVersion="33"):

Btw you could connect you device and launch release build while having been typed in terminal "adb logcat" to see in logs why you are crashing.
Now to be able to save your photos You'd need to manually request Storage access permissions for android below 10 only. Those above do not need them to save and read their own photos (compiling vs api >= 33 only), moreover if you request this permission for android 13 you will not get a prompt and the permission will always be refused, so..

Thank you for your suggestion I will check the logcat however I can confirm that I am requesting camera permissions, the dialog does appear at the beginning, I've tested on 2 devices a Poco M3 Pro(Android 12) and a Xiaomi Redmi 8A(Android 11)  with the same result.
see android manifest below
<manifest xmlns:android="http://schemas.android.com/apk/res/android">
	<application android:allowBackup="true" android:icon="@mipmap/icon" android:roundIcon="@mipmap/icon_round" android:supportsRtl="true">
		<provider android:name="androidx.core.content.FileProvider"
          android:authorities="${applicationId}.fileprovider"
          android:exported="false"
          android:grantUriPermissions="true">

			<meta-data android:name="android.support.FILE_PROVIDER_PATHS"
						   android:resource="@xml/file_paths"></meta-data>
		</provider>
	</application>
	<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
	<uses-permission android:name="android.permission.INTERNET" />
	<uses-permission android:name="android.permission.CAMERA" />
	<uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE" />
	<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
	<uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION" />
	<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />
	<uses-permission android:name="android.permission.ACCESS_BACKGROUND_LOCATION" />
	<uses-feature android:name="android.hardware.location" android:required="false" />
	<uses-feature android:name="android.hardware.location.gps" android:required="false" />
	<uses-feature android:name="android.hardware.location.network" android:required="false" />	<queries>
		<intent>
			<action android:name="android.media.action.IMAGE_CAPTURE" />
		</intent>
	</queries>
</manifest>

I have the same issue. Camera not running in Release.

What is the android version of devices that are failing?
What is android sdk you are compile with?
Again, if you are compiling vs api33 (android 13) remove
<uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE">
from manifest, use only
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"  android:maxSdkVersion="28"/>
<uses-permission android:name="android.permission.CAMERA" />

if you are compiling for lower api you must have both read and write permissions declarations inside manifest.
Now about the code inside app. You have to check current android version using DeviceInfo. If it's android >=13 do nothing.
If it's lower android:
A - If you compiled vs api33:
ask user for permissions Permissions.StorageWrite. if this device android < 10
B - If you compiled vs lower api
ask user for permissions Permissions.StorageWrite. if this device is running < 13
Again you have to manually ask user for storage write permissions, having declaration in the manifest is not enough. cameraview will not do that for you, and such code is missing in the example app at the moment.

1 on which version of android does crash, is it real device or emulator?
2 have you implemented any code for Permissions.StorageWrite?

It happens on my device Samsung  Galaxy Note20 Ultra (Android 13).
Read or Write_External_Storage makes no difference. (Not need it anyhow)
I don't know how it works with adb log.
And again. Your Camera.MAUI.Test has the same problem. In Debug all fine. In Release camera not woring.

Also (https://github.com/jfversluis/MauiCameraMauiSample)  has the same problem.

1 this this not my repository
2 does your error happen when you click on Start button or when you open the page with camera? If it happens when you click on button my quick guess you just have to wrap all calls to cameraView.StartCameraAsync(); with a MainThread.BeginInvokeOnMainThread, that could matter if on Release the optimized code launches "async void" handlers in back thread, then calls camera permissions and crashes because this must be done on ui thread only.

In Camera.MAUI.Test (Release) nothing happens when click on Start Camera button. In Debug all fine.

My guessing was wrong, for me cameraView.Cameras are just empty on Release. The problem looks heavy.

I don't need to release tomorrow. So I can continue developing and debugging.
I hope you are able to find the issue. I very much appreciate your repository.

Experiencing the same problem，debug mode was ok，but RC version failed.
Log: 'cameraView.Cameras.Count' is 0

Hi all,
I’m changing the entire android handler for the new release and adapt it to Camera2 and not CameraX (as now). I hope that it resolves all android problems.

Hi All
when do you expect this problem will be solving solve?
Thanks

Hi,
I have published a new realease 1.3. It changes the android handler and this problems must be resolved. Also It adds recording video feature.

Great! It seems to work perfectly. Only the Zoomfactor seems not to work. Is that so?

Hi Peter,
with the new handler, zoom only works on API 30 or greater (at least for the moment).

I'm using API 33, but when I add ZoomFactor="2" to the cameraView is has no effect.

And after testing a bit more I experience some unexpected behaviour. I'm switching between different pages with a cameraView and sometimes the page is crashing. Still looking for the issue.

Hi Hjam40, I'm using API 33, but the ZoomFactor seems to have no effect.
And another thing is that it seems that the scanner does not respond when reading the same QR Code for the second time. Is that intended?

Hi Peter,
I'm trying the ZoomFactor in all platforms and it works fine for me... Could you verify the MaxZoomFactor for your selected Camera?
In reference to the scanner, yes, I changed the event behaviour to trigger only if the result is different from the previous but I'm thinking that maybe is not a good idea and I will create a property for set the behaviour as the user prefers.

Hi hjam40, sorry to bother you about the ZoomFactor. Wrong coding on my end. Problem solved.
And yes, I prefer that the scanner can read the same code multiple times.
One more question: I have a square frame for my cameraView (300 x 300). But then the image is stretched in height. Is there a way to solve that?

And sometimes I'm getting:
Android.Hardware.Camera2.CameraAccessException: 'CAMERA_ERROR (3): endConfigure:740: Camera 0: Error configuring streams: Broken pipe (-32)'
Is this my code or something else?

Is there a way to detect video resolution selected by Android?

And I'm using StopCameraAsync. I don't find StopPreviewAsync.

Sorry, my mistake, it's correct StopCameraAsync.
No way (at least I didn't find it) to know the Camera video resolution using in a preview in Android....

Having the similar issue after updating to 1.3.
The preview seems to be weirdly stretched.

Hi, I got it all working fine now. Thanks for the hard work.
Except for the stretching of the preview. This was not there in the previous version. I hope this can be resolved.

Thanks for the fix Hector, it works now. Keep up the good work.

Hi,
I have created a new realease 1.3.1 where I have changed the aspect ratio for Android Preview... I hope it works for you.

I updated, but then I get:
System.InvalidCastException: 'Specified cast is not valid.'

After update I'm getting:
System.InvalidCastException: 'Specified cast is not valid.'
at StartCameraAsync

Hi Peter,
Sorry, but I can't get that error... Could you give me more information? Maybe the line where the exception throws.. You could clone the git repository and run the app on your device.


[HTML5] ConfigFile.load returns ERR_CANT_OPEN

Godot version:
3.1.stable.official
OS/device including version:
HTML5, Chrome, Windows 10
Issue description:
When running in a HTML5 exported game the following auto-loaded script attempts to load a Config.ini file but fails and the error is ERR_CANT_OPEN. This code works fine when I run the project locally or from a Windows executable export. Config.ini is at the root of the project.
extends Node
class_name Config

var configFile: ConfigFile = ConfigFile.new();
onready var err = configFile.load("res://Config.ini");

I see no network requests for this file so I assume it's expected to be packaged as part of the wasm file.
Is there some additional setup I need to do for custom config files like this? Is "res://" not valid for HTML5?
Thank you!

To include .ini files for export, you must add *.ini to the list of non-resource files to export in the Resources tab of the export dialog. This must be done for every export preset individually.

This worked! Thank you.
So I guess the implication is that only standard assets like images, sounds, 3D model files, etc will be exported by default?
Perhaps this page should mention that: https://docs.godotengine.org/en/3.1/getting_started/workflow/export/exporting_for_web.html

Only files recognized as Resources by Godot will be exported with the default mode, unless manually added. This is true when exporting for any platform. https://docs.godotengine.org/en/3.1/getting_started/workflow/export/exporting_projects.html#export-mode

Well if that's true then there is some inconsistency. When I exported to Windows I did not have to do anything the ini file was included by default.


Implement VCP support

[ ] Baud rate handling on the USB side
[ ] UART driver (USART2)
[ ] Automatic baud rate detection?

For the VCP remember to swap the RX/TX pair if testing :) They were accidentally swapped in the design.

Huh? Connections and labels are totally correct from my perspective. Where they were swapped?

At the ESD chip

Yes, but stlink signal names are also backwards:

Anyway, I'll be careful :)

Oh, maybe I got it wrong 2 times xD

Yes, but stlink signal names are also backwards:

Anyway, I'll be careful :)

what is this evil lol

@Yatekii UM2448, chapter 9.1.2 "STDC14 (STM32 JTAG/SWD and VCP)"


check for tx termination

 Issue by jexp
Thursday Apr 06, 2017 at 11:37 GMT
Originally opened as https://github.com/neo4j-contrib/neo4j-apoc-procedures/issues/375

[ ] Periodic
[ ] Graph Refactorings
[ ] The new renaming methods
[ ] cypher.runFile
[ ] exports
[ ] load.json, load.jdbc, load.xml

In a sensible place in the outmost loop that's iterate a reasonable number of times.

 Comment by jexp
Thursday Jul 06, 2017 at 13:51 GMT

Two more thoughts:
what do we do:

abort
return what we have (needed e.g. for runTimeboxed() or mapParallel )

also there is a difference between read and write operations
there could be also a central check, e.g. Util.inTx() that checks for abortion, but then we have to carry over the original kernel-tx (or wrapped in an interface) to the place where to check.

 Comment by jexp
Saturday Jul 29, 2017 at 09:51 GMT

@AngeloBusato See also the approach that we took in graph algorithms:
Issue: https://github.com/neo4j-contrib/neo4j-graph-algorithms/issues/196
and related PRs


Erroneous resource allocation in partition "E880"

Describe the problem
Allocating a distributed computing client with custom CPU/mem settings in the E880 partition does not actually allocate the specified resources.
Steps To Reproduce
from acme import ParallelMap, esi_cluster_setup
myClient = esi_cluster_setup(n_workers=3, cores_per_worker=16, mem_per_worker="5GB", partition="E880", timeout=timedelta(minutes=10).total_seconds(),
                             n_workers_startup=1, verbose=True, debug=True)

This produces sbatch scripts missing the CPU spec and thus using default core allocations:
#!/usr/bin/env bash#SBATCH -J dask-worker
#SBATCH -p E880
#SBATCH -n 1

Additional Information
Changing the underlying SLURMCluster call to
 cluster = SLURMCluster(queue="E880", cores=16, memory="8GB", processes=16)

fixes the problem:
scontrol show job 26317414
JobId=26317414 JobName=dask-worker
   ...
   NumNodes=1 NumCPUs=16 NumTasks=1 CPUs/Task=16 ReqB:S:C:T=0:0:*:*
   TRES=cpu=16,mem=8G,node=1,billing=16
   Socks/Node=* NtasksPerN:B:S:C=0:0:*:* CoreSpec=*
   MinCPUsNode=16 MinMemoryNode=8G MinTmpDiskNode=0
   ...

A possible fix in esi_cluster_setup could be the following change of line L203
     processes_per_worker = kwargs.pop("processes_per_worker", cores_per_worker)

An additional bug emerged here as well: the job_directives_skip removes any lines from the generated sbatch that contain the specified string, e.g.,
cluster = SLURMCluster(cores=32, memory="4000MB", processes=4, queue="E880", job_cpu = 56, job_directives_skip=['--mem'])

print(cluster.job_script())

#!/usr/bin/env bash
#SBATCH -J dask-worker
#SBATCH -p E880
#SBATCH -n 1
#SBATCH --cpus-per-task=56
#SBATCH -t 00:30:00

cluster = SLURMCluster(cores=32, memory="4000MB", processes=4, queue="E880", job_cpu =56, job_directives_skip=['t'])

print(cluster.job_script())
#!/usr/bin/env bash
#SBATCH -J dask-worker
#SBATCH -p E880
#SBATCH -n 1
#SBATCH --mem=4G


Add test for XMLHttpRequest Level 2

Hello,
This is a patch to add a test for "XMLHttpRequest Level 2" in the "Communication" section.
In particular, I believe a main change since Level 1 is everything related to upload:
http://www.w3.org/TR/XMLHttpRequest2/#the-upload-attribute
Thus, a basic feature detection is used with:
var hasXhr2 = window.XMLHttpRequest && ('upload' in new XMLHttpRequest());
See also http://www.caniuse.com/xhr2

A number of test regarding XMLHttpRequest Level 2 have been added to beta.html5test.com and will be included in the next version.


Update README and add MIT license

Preview available on my fork (https://github.com/noamzaks/bazelrio)
Assuming MIT license is fine by you (I really have no specific opinion on the matter).
Also, should we add a note on the usage of WPILib and other libraries? Or change the license accordingly?
Thoughts?

MIT is fine with me. Will do a more thorough review tomorrow.

Pending a fix from /tag/ to /tags/


Make ready for Flask 2

Requires the following PRs (and still a bit of love):

https://github.com/inveniosoftware/invenio-base/pull/160
https://github.com/inveniosoftware/invenio-accounts/pull/377
https://github.com/inveniosoftware/invenio-rest/pull/126
https://github.com/inveniosoftware/invenio-userprofiles/pull/125
https://github.com/inveniosoftware/invenio-assets/pull/141

The example apps are returning an exit code of 1 unexpectedly, and there seems to be an issue with a newer version of PyJWT

Update: The PyJWT issue was fixed in this PR, and the example apps run through (with exit code 0) with Flask 2.x when a patched version of Flask-Collect is installed.
Note: The checks on this PR are currently passing because some dependencies (linked PRs) are still pinning Flask<2.0, which causes the Flask-Collect issue to not surface.


Added Ark-x Talent Factory

ARKx est un accélérateur de talents en nouvelles technologies.
Nous proposons des services centrés sur les compétences technologiques, allant des bootcamps de montée en compétences et de reconversion au déploiement d'équipes-projet pour nos partenaires. C'est GRATUIT au marocain

@YouHad-x First stage of verification passed, official domain for Ark-x Talent Factory is arkx.group as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@YouHad-x Regrettably, I have to close the request without merging, because this organization is a training center, not a college, nor a university. Please ensure that you are familiar with this repository rules located at the bottom of this page.
Please apply for an appropriate licensing option (which may also be free) at https://www.jetbrains.com/community/education/#courses.
Thank you for your understanding!


GitHub OAuth2

#37 GitHub OAuth2 Implementation

Thanks @njuettner for the PR.
Can you create a REDME.md section for github OAuth2 similar to the google section?
And please fix the build https://github.com/zalando/gin-oauth2/pull/40 should do it.

Thanks for looking at it. I've added the section how to use GitHub in README.

:+1:

👍


remove local docusaurus

not needed anymore now that we have the docs repo setup

@jnsdls this should be safe right? just disable the job on zeet and that's it? https://zeet.co/nftlabs/nftlabs-typescript-sdk


Improve int/tinyint/smallint/bigint handling in H2

Impact

[x] Bug fix (non-breaking change which fixes expected existing functionality)
[ ] Enhancement/New feature (adds functionality without impacting existing logic)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description
Implement support to consider integer precision by parsing to the specific integer type (tiny, integer or bigint) depending on the specified size.
Fixes #3250
Fixes #3300
Things to be aware of

This change only impacts integer data type for H2.

Things to worry about

Nothing.

Additional Context

Nothing.

I think it's fine to be checking the size here for int and converting to the correct actual types, since new h2 does not support precision like that.
But, the issue still exists where someone specifying smallint(3) or bigint(15) or whatever will still fail. So I think we need fixes to TinyIntType, SmallIntType, etc. that simply ignore the parameters passed since h2 doesn't support that. I don't think we need to do logic like "smallint(10) means bigint".
Also, could you add a changeset to the h2 integration test changelog with the different int, smallint, etc. types for columns to ensure the final SQL is valid?

@nvoxland If I didn't get it wrong, what you are asking for here is being addressed as part of this PR. Can you please have a look and confirm?
Thanks,
Daniel.

@MalloD12 yes, that other PR picks up the other problems, I hadn't seen that one yet. Since it's touching similar code we could have done it as a single PR addressing both issues, but fine to keep them separate since you've made both already.
Both could use integration test items for them still, though.

@MalloD12 yes, that other PR picks up the other problems, I hadn't seen that one yet. Since it's touching similar code we could have done it as a single PR addressing both issues, but fine to keep them separate since you've made both already.
Both could use integration test items for them still, though.

if you are ok with that, I can still unify these two PRs in just a single one and then close one of them? I think some of them already have integration test created, but yeah some others don't.

Could you please include the fix for BOOLEAN Types as well?
Currently with H2 2.1.214, Liquibase is not able to translate 1 to TRUE (or) 0 to FALSE. With previous version of H2 1.4.200, Liquibase was able to translate it.
Steps to reproduce:
databaseChangeLog:

changeSet:
id: '1'
author: author
comment: 'initial schema'
changes:

addColumn:
tableName: order
columns:

column:
name: order_status
type: VARCHAR(255)
constraints:
nullable: false
value: NONE

update:
columns:

column:
name: order_status
value: EXECUTED
tableName: order
where: executed = 1

Reason: liquibase.exception.DatabaseException: Values of types "BOOLEAN" and "INTEGER" are not comparable; SQL statement:
UPDATE PUBLIC.order SET order_status = 'EXECUTED' WHERE executed = 1 [90110-214] [Failed SQL: (90110) UPDATE PUBLIC.order SET order_status = 'EXECUTED' WHERE executed = 1]

@VeluchamySC that won't be something we can fix. The where clause can be arbitrarily complex and so it's something we can try to parse and understand. All we do is pass it along as the update statement's where clause exactly as you have it.
It looks like a change in what h2 will do for data type conversions between 1.x and 2.x. If you have just switched to h2 2.x you can update the statement to use executed = true. (You will need to add a validCheckSum tag to it knows you know what you are doing). If you still need to support both versions, you can use a changelog parameter like ${trueValue} which you set to 1 or true depending on the version of h2 you are using.

Hi @TomBenjamins We are looking for getting another review on this PR. Once that happens we will be ready to merge this. We are expecting to have this close soon to include it in the next release,  which hopefully should be in about two weeks.
Thanks,
Daniel.-

Hi,
Has this issue been fixed for raw sql changes as well? After migration from 4.4.0 to 4.18.0 scripts are failing on H2 with exactly the same message.
Example changeset:
<sql>             CREATE TABLE SampleTable             (                 id          bigint(20) NOT NULL PRIMARY KEY AUTO_INCREMENT             ) </sql>

Bump for the fix...


All React tutorial deploy previews are failing

3:22:38 PM: Creating an optimized production build...
3:22:40 PM: Failed to compile.
3:22:40 PM:
3:22:40 PM: ./src/index.js
3:22:40 PM: Error: [BABEL] /opt/build/repo/src/index.js: Cannot find module 'gensync' (While processing: "/opt/build/repo/node_modules/babel-preset-react-app/index.js")
3:22:40 PM:
3:22:40 PM:
3:22:40 PM: error Command failed with exit code 1.
3:22:40 PM:
3:22:40 PM: info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
3:22:40 PM:
3:22:40 PM: ┌─────────────────────────────┐
3:22:40 PM: │   "build.command" failed    │
3:22:40 PM: └─────────────────────────────┘
3:22:40 PM:
3:22:40 PM:   Error message
3:22:40 PM:   Command failed with exit code 1: yarn build
3:22:40 PM:
3:22:40 PM:   Error location
3:22:40 PM:   In Build command from settings:
3:22:40 PM:   yarn build
3:22:40 PM:
3:22:40 PM:   Resolved config
3:22:40 PM:   build:
3:22:40 PM:     command: yarn build
3:22:40 PM:     publish: /opt/build/repo/build

@mattrosno is this good?


Authorization

This allows authorization of subjects for publish and subscribe filters with enforcement.
/cc @kozlovic @ColinSullivan1

Coverage decreased (-0.4%) to 90.092% when pulling 7730fac9e24d0016d4a1b9eb001461acd62ddb6f on authorization into 5a42a9a54e91fdd2be2820416912991c68446a11 on master.

Coverage decreased (-0.7%) to 89.751% when pulling a55b7c2744db7aae858ff20b4073308444a4e6a1 on authorization into 5a42a9a54e91fdd2be2820416912991c68446a11 on master.

Coverage decreased (-0.8%) to 89.694% when pulling 248bd8d3662a35a9d6434a27e29b844289529b2a on authorization into 5a42a9a54e91fdd2be2820416912991c68446a11 on master.

Coverage decreased (-0.6%) to 89.812% when pulling 49e5dfd7971954259a720c1505bfca1bbef7ea1e on authorization into 5a42a9a54e91fdd2be2820416912991c68446a11 on master.

Done with the review, I have a doubt about a possible unbounded growth of the pub cache. Otherwise, LGTM.

Thanks @kozlovic, agree on cache growth, already added those checks in. Will look more closely at the other comments as well.

I'm wrapped up with the review as well.  Apart from the potential log growth issue, LGTM.

Coverage decreased (-0.7%) to 89.794% when pulling fa95bd936b7b8ce7d00ef2df7ad43f89d65da546 on authorization into 5a42a9a54e91fdd2be2820416912991c68446a11 on master.

LGTM

Coverage decreased (-0.3%) to 90.153% when pulling 8d07e06b91836f760dd32c8825dfa4613bf808e0 on authorization into 5a42a9a54e91fdd2be2820416912991c68446a11 on master.


"Fork Me on Github" function for hosted tools and workflows

It would be extremely nice to support forking in some automated way.  For example, a user finds a tool they like on Dockstore.org but it's not quite correct (say, it leaves out some parameterization that they need).  We can automate the process of forking the repo on Bitbucket or Github (depending on the source) and drop this off in the users account.  They can then make changes to the Dockerfile or Dockstore.cwl and issue a pull request back to the original author.  Or, they can build this with Quay.io (or some other mechanism) and register it themselves as a new tool on Dockstore.org.  The latter being not necessarily great since it will create duplications but at least it will give them a route to moving forward.
If we can't support automatic forking bases on the source repo, perhaps we can give directions for the user to do this themselves.
┆Issue is synchronized with this Jira Story
┆fixVersions: Open-ended research tasks
┆friendlyId: DOCK-448
┆sprint: Backlog
┆taskType: Story

Resurrecting this and redefining it.
This is basically phase 2 of #1615
A user when happy with a hosted workflow on Dockstore should be able to take it from Dockstore and put it on GitHub in some way. Possibilities include forking a repo in some way, using a bot user, etc.

One model I like is when you select a new room on Gitter it offers to create a PR adding the Gitter Badge.

This could work with Dockstore offering to create a PR to one of a user's repos.

This can be done using a simple hyperlink, though it will fork the whole repo https://github.com/dockstore/dockstore/fork


xsltproc compatible

xsltproc does not support msxsl:node-set()

I can publish a release without that code.  Removing that function should allow for it to work the same way in other xslt processors, but Microsoft XSLT required them.

I added a new branch without the node-set references if you want to try it out and let me know.

I think removing msxsl:node-set() isn't enough by itself. Do you know what would be the xsltproc compatible syntax?

I will be downloading xslt proc to see what is going on.  There is a known stackoverflow problem for larger XML files that I have come up with a way to fix, but have not implemented it yet.

I fixed the xsltproc version and did some surface level testing and it is working.  It uses the exslt node-set function instead of the Microsoft version.

it's fixed for xsltproc in the latest xsltproc branch release.  It needed a different node-set library/
On Saturday, November 17, 2018, 4:07:07 PM EST, Raphaël Droz<EMAIL_ADDRESS>wrote:
I think removing msxsl:node-set() isn't enough by itself. Do you know what would be the xsltproc compatible syntax?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Thank you, it works great under xsltproc now!
Note 1: in README.md => input.xml => <root> instead of </root>
Note 2: could you please remove my above (named) quote? I was mistaken and removed my comment afterwards btw.


Code for this tutorial didn't link

I am very interested in using modules and am happy Visual Studio is being so proactive about supporting them.  I tried to build the sample described in this page.  It doesn't link.  The first time I noticed the error I was using VS 17.0.0.  After seeing the error I upgraded to VS 17.0.4.  However, the build still doesn't work for me.  Maybe I missed a step?
Build started...
1>------ Build started: Project: ModulesTutorial, Configuration: Debug x64 ------
1>Scanning sources for module dependencies...
1>BasicPlane.Figures-Point.ixx
1>BasicPlane.Figures.ixx
1>BasicPlane.Figures-Rectangle.ixx
1>Compiling...
1>BasicPlane.Figures-Point.ixx
1>BasicPlane.Figures-Rectangle.ixx
1>BasicPlane.Figures.ixx
1>BasicPlane.Figures-Rectangle.cpp
1>ModulesTutorial.cpp
1>Generating Code...
1>C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Microsoft\VC\v170\Microsoft.CppCommon.targets(1087,5): error MSB6006: "link.exe" exited with code 1120.
1>ModulesTutorial.obj : error LNK2019: unresolved external symbol "int __cdecl area(struct Rectangle const &)" (?area@@YAHAEBURectangle@@@Z::<!BasicPlane.Figures>) referenced in function main
1>  Hint on symbols that are defined and could potentially match:
1>    "int __cdecl area(struct Rectangle const &)" (?area@@YAHAEBURectangle@@@Z)
1>C:\Users\eric\source\repos\ModulesTutorial\x64\Debug\ModulesTutorial.exe : fatal error LNK1120: 1 unresolved externals
1>Done building project "ModulesTutorial.vcxproj" -- FAILED.
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 01648994-5c73-a88d-bc78-dbab40d834d7
Version Independent ID: 01648994-5c73-a88d-bc78-dbab40d834d7
Content: Named modules tutorial in C++
Content Source: docs/cpp/tutorial-named-modules-cpp.md
Product: visual-cpp
Technology: cpp-language
GitHub Login: @corob-msft
Microsoft Alias: corob

ModulesTutorial.zip

#3615 duplicate

@erz42
Thanks for the report. The code didn't link for me in 17.0.4 either, but then I noticed this line in the tutorial:

For this tutorial, you'll need Visual Studio 2022 17.1.0 or later.

I verified that the tutorial does in fact work in the 17.1 preview builds. We don't usually publish tutorials until the compiler they require is released, so someone may have poked the publish button on this article too soon. Possibly me. Apologies for the misuse of your time.
I'm closing the issue as 17.1 previews are available now and the 17.1 release is coming shortly, probably within a couple of weeks.