LND only supports bitcoind 0.18

The bitcoin repo uses the master branch, which is ahead of the latest release (0.18.1) Currently it's ahead in a way that makes the LND client shutdown.
This is how I fixed it for now:
./sv repos rm bitcoin
cd _repos
git clone --depth=1 --branch=0.18 --recursive https://github.com/bitcoin/bitcoin.git
./sv create [recipe] [name] -f
./sv enter [name]
./dc build
./dc up

For more info on LND only supporting 0.18, see this issue (I got the exact same error):
https://github.com/lightningnetwork/lnd/issues/3412

You steps to pin-point bitcoin repo are correct. You could also simply cd _repos/bitcoin && git checkout 0.18 without cloning it again. Simverse uses whatever you have present under _repos.
I looks like the issue has been present for quite some time and my simverse test suite was passing regardless. So it is not triggered every time.
In general I would like to find a patch or a workaround to allow simverse to use master versions of each project. This way we find regressions early.
Can you provide some steps how to trigger this issue? I would look into it.

You can trigger it like this.

Obviously have the latest updated repos
Create a recipe with a LND node and a bitcoind node
Create a simverse, enter and build,
during ./dc up you will see the following error from your LND node: Unable to create chain control: unable to retrieve best block
Also, ./dc ps yields an unhealthy LND node, although that might take a minute, because that might only happen after LND shuts itself down.

With regards to git checkout, I tried to checkout first, but git couldn't find the branch.
git branch -r yielded only the master branch.
Maybe because the repo was shallow? I didn't try unshallow.


MAINT: Bump installer links

Once https://github.com/mne-tools/mne-installers/releases/tag/v1.0.1 finished building I'll test all download links and the macOS installer, then merge and backport

All download links work, and macOS installer works. In it goes!


[IOS] Google ML Kit dependencies conflict with Firebase products

Steps to Reproduce

create a new flutter project
add the firebase_crashlytics: ^2.0.4 package
add the google_ml_kit: ^0.4.0 package
Run the app on IOS device and / or see the error during pod install.

I would add that according to this issue, it seems to happen with other FlutterFire packages such as cloud_firestore: ^2.2.0.
Expected results:
This issues comes using the google_ml_kit package.
An issue already exists there but the package is apparently consuming the latest versions of GoogleMLKit.
We expect to not see the GoogleDataTransport dependency conflict.
Actual results:
An error is raised in CocoaPods :

Logs
[!] CocoaPods could not find compatible versions for pod "GoogleDataTransport":
  In Podfile:
    firebase_crashlytics (from `.symlinks/plugins/firebase_crashlytics/ios`) was resolved to 2.0.4, which depends on
      Firebase/Crashlytics (= 8.0.0) was resolved to 8.0.0, which depends on
        FirebaseCrashlytics (~> 8.0.0) was resolved to 8.0.0, which depends on
          GoogleDataTransport (~> 9.0)

    google_ml_kit (from `.symlinks/plugins/google_ml_kit/ios`) was resolved to 0.0.1, which depends on
      GoogleMLKit/FaceDetection was resolved to 0.60.0, which depends on
        GoogleMLKit/MLKitCore (= 0.60.0) was resolved to 0.60.0, which depends on
          MLKitCommon (~> 0.60.0) was resolved to 0.60.0, which depends on
            GoogleDataTransport (~> 3.2)

Output of flutter doctor -v :
[✓] Flutter (Channel stable, 2.2.0, on macOS 11.3.1 20E241 darwin-x64, locale fr-FR)
    • Flutter version 2.2.0 at /Users/foxtom/Desktop/flutter
    • Framework revision b22742018b (10 days ago), 2021-05-14 19:12:57 -0700
    • Engine revision a9d88a4d18
    • Dart version 2.13.0

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Users/foxtom/Library/Android/sdk
    • Platform android-30, build-tools 30.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.5, Build version 12E262
    • CocoaPods version 1.10.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)

[✓] Connected device (3 available)
    • Tommy’s iPhone (mobile) • 700c28e00d8978a132f439820a90d99c6327a990 • ios            • iOS 14.5.1
    • macOS (desktop)         • macos                                    • darwin-x64     • macOS 11.3.1 20E241 darwin-x64
    • Chrome (web)            • chrome                                   • web-javascript • Google Chrome 90.0.4430.212
    ! Error: iPhone is not connected. Xcode will continue when iPhone is connected. (code -13)

• No issues found!

I hope to see a quick fix for this indeed :)

Hi @Tom3652
From what I can see, the issue is related to a FlutterFire plugin rather than to Flutter itself. Please open the issue in the dedicated repository.
Closing, as this isn't an issue with Flutter itself.
If you disagree, please write in the comments,  providing your flutter doctor -v, your pubspec.yaml, a minimal reproducible code sample that does not use 3rd party plugins, your complete flutter run -v logs running the minimal code sample
and I will reopen it.
Thank you

Hi @TahaTesser !
You are right i agree with you, i am opening this issue in the FlutterFire repository.
Regards


jax[cuda12_pip] -> jax[cuda12-pip] which installs different packages

uv rewrites jax[cuda12_pip]==0.4.25 as jax[cuda12-pip]==0.4.25 which results in different packages being installed by pip. IMHO it should preserve the exact spelling.
% cat req.in
jax[cuda12_pip]==0.4.25
% uv pip compile -v --find-links=https://storage.googleapis.com/jax-releases/jax_cuda_releases.html --no-strip-extras --no-annotate --no-header req.in

DEBUG uv 0.2.21
DEBUG Starting toolchain discovery for any Python
DEBUG Looking for exact match for request any Python
DEBUG Searching for Python interpreter in system path
DEBUG Found cpython 3.10.11 at `/home/tbirch/src/polez/conda/polez/bin/python3` (conda prefix)
DEBUG Using Python 3.10.11 interpreter at /home/tbirch/src/polez/conda/polez/bin/python3 for builds
DEBUG Using request timeout of 30s
DEBUG Found fresh response for: https://storage.googleapis.com/jax-releases/jax_cuda_releases.html
DEBUG Found 667 packages in `--find-links` entry: https://storage.googleapis.com/jax-releases/jax_cuda_releases.html
DEBUG Solving with installed Python version: 3.10.11
DEBUG Adding direct dependency: jax==0.4.25
DEBUG Adding direct dependency: jax[cuda12-pip]==0.4.25
DEBUG Found fresh response for: https://pypi.org/simple/jax/
DEBUG Searching for a compatible version of jax[cuda12-pip] (==0.4.25)
DEBUG Selecting: jax==0.4.25 (jax-0.4.25-py3-none-any.whl)
DEBUG Adding transitive dependency for jax==0.4.25: jax==0.4.25
DEBUG Adding transitive dependency for jax==0.4.25: jax[cuda12-pip]==0.4.25
DEBUG Searching for a compatible version of jax (==0.4.25)
DEBUG Selecting: jax==0.4.25 (jax-0.4.25-py3-none-any.whl)
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/ad/29/37cc2d58775917e6da532ef59cd3a66133d4de73fce1c16852e8475e5411/jax-0.4.25-py3-none-any.whl.metadata
DEBUG Adding transitive dependency for jax==0.4.25: ml-dtypes>=0.2.0
DEBUG Adding transitive dependency for jax==0.4.25: numpy>=1.22
DEBUG Adding transitive dependency for jax==0.4.25: opt-einsum*
DEBUG Adding transitive dependency for jax==0.4.25: scipy>=1.9
DEBUG Searching for a compatible version of jax[cuda12-pip] (==0.4.25)
DEBUG Selecting: jax==0.4.25 (jax-0.4.25-py3-none-any.whl)
DEBUG Adding transitive dependency for jax==0.4.25: jaxlib==0.4.25+cuda12.cudnn89
DEBUG Adding transitive dependency for jax==0.4.25: nvidia-cublas-cu12>=<IP_ADDRESS>
DEBUG Adding transitive dependency for jax==0.4.25: nvidia-cuda-cupti-cu12>=12.3.101
DEBUG Adding transitive dependency for jax==0.4.25: nvidia-cuda-nvcc-cu12>=12.3.107
DEBUG Adding transitive dependency for jax==0.4.25: nvidia-cuda-runtime-cu12>=12.3.101
DEBUG Adding transitive dependency for jax==0.4.25: nvidia-cudnn-cu12>=<IP_ADDRESS>
DEBUG Adding transitive dependency for jax==0.4.25: nvidia-cufft-cu12>=<IP_ADDRESS>
DEBUG Adding transitive dependency for jax==0.4.25: nvidia-cusolver-cu12>=<IP_ADDRESS>
DEBUG Adding transitive dependency for jax==0.4.25: nvidia-cusparse-cu12>=<IP_ADDRESS>
DEBUG Adding transitive dependency for jax==0.4.25: nvidia-nccl-cu12>=2.19.3
DEBUG Adding transitive dependency for jax==0.4.25: nvidia-nvjitlink-cu12>=12.3.101
DEBUG Found fresh response for: https://pypi.org/simple/ml-dtypes/
DEBUG Found fresh response for: https://pypi.org/simple/opt-einsum/
DEBUG Found fresh response for: https://pypi.org/simple/nvidia-cublas-cu12/
DEBUG Found fresh response for: https://pypi.org/simple/nvidia-cufft-cu12/
DEBUG Found fresh response for: https://pypi.org/simple/jaxlib/
DEBUG Found fresh response for: https://pypi.org/simple/nvidia-cuda-nvcc-cu12/
DEBUG Found fresh response for: https://pypi.org/simple/nvidia-cuda-runtime-cu12/
DEBUG Found fresh response for: https://pypi.org/simple/nvidia-cuda-cupti-cu12/
DEBUG Found fresh response for: https://pypi.org/simple/nvidia-cusparse-cu12/
DEBUG Searching for a compatible version of jaxlib (==0.4.25+cuda12.cudnn89)
DEBUG Selecting: jaxlib==0.4.25+cuda12.cudnn89 (jaxlib-0.4.25+cuda12.cudnn89-cp310-cp310-manylinux2014_x86_64.whl)
DEBUG Found fresh response for: https://pypi.org/simple/nvidia-nvjitlink-cu12/
DEBUG Found fresh response for: https://pypi.org/simple/nvidia-cudnn-cu12/
DEBUG Found fresh response for: https://pypi.org/simple/scipy/
DEBUG Found fresh response for: https://pypi.org/simple/nvidia-cusolver-cu12/
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/9d/15/e5af59287e712b26ce776f00911c45c97ac9f4cd82d46500602cc94127ed/ml_dtypes-0.4.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/f9/43/a5365b345c989d9f7de2f2406e59b4a792ba3541b5d47edda5031b2730a6/nvidia_cublas_cu12-<IP_ADDRESS>-py3-none-manylinux2014_x86_64.whl.metadata
DEBUG Found fresh response for: https://pypi.org/simple/nvidia-nccl-cu12/
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/bc/19/404708a7e54ad2798907210462fd950c3442ea51acc8790f3da48d2bee8b/opt_einsum-3.3.0-py3-none-any.whl.metadata
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/e4/85/f18c88f63489cdced17b06d3b627adca8add7d7b8cce8c11213e93a902b4/nvidia_cufft_cu12-<IP_ADDRESS>-py3-none-manylinux2014_x86_64.whl.metadata
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/44/cc/36363057676e6140d0bdb07fa6df5419b68203c5cba8c412b5600fd0d105/nvidia_cuda_nvcc_cu12-12.5.82-py3-none-manylinux2014_x86_64.whl.metadata
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/b3/29/03726191334fa523d9654e3dacca5cc152f24bb9fa1a5721e4dddac7a8c5/nvidia_cusparse_cu12-<IP_ADDRESS>-py3-none-manylinux2014_x86_64.whl.metadata
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/75/bc/e0d0dbb85246a086ab14839979039647bce501d8c661a159b8b019d987b7/nvidia_nvjitlink_cu12-12.5.82-py3-none-manylinux2014_x86_64.whl.metadata
DEBUG Found fresh response for: https://storage.googleapis.com/jax-releases/cuda12/jaxlib-0.4.25+cuda12.cudnn89-cp310-cp310-manylinux2014_x86_64.whl
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/71/05/80f3fe49e9905570bc27aea9493baa1891c3780a7fc4e1f872c7902df066/nvidia_cuda_runtime_cu12-12.5.82-py3-none-manylinux2014_x86_64.whl.metadata
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/49/3e/774e7be286248bfa269fca185858b8d50b4d378aeee02d4dc5ee0b64428a/nvidia_cudnn_cu12-<IP_ADDRESS>-py3-none-manylinux2014_x86_64.whl.metadata
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/e2/20/15c8fe0dfebb6facd81b3d08bf45dfa080e305deb17172b0a40eba59e927/scipy-1.14.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/33/73/57fbf55b3f378a73faecde397a0927ea205b458f06573dfb191b7d9fd1d3/nvidia_cusolver_cu12-<IP_ADDRESS>-py3-none-manylinux2014_x86_64.whl.metadata
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/3a/64/81515a1b5872dc0fc817deaec2bdba160dc50188e0d53b907d10c6e6d568/nvidia_cuda_cupti_cu12-12.5.82-py3-none-manylinux2014_x86_64.whl.metadata
DEBUG Adding transitive dependency for jaxlib==0.4.25+cuda12.cudnn89: scipy>=1.9
DEBUG Adding transitive dependency for jaxlib==0.4.25+cuda12.cudnn89: numpy>=1.22
DEBUG Adding transitive dependency for jaxlib==0.4.25+cuda12.cudnn89: ml-dtypes>=0.2.0
DEBUG Searching for a compatible version of ml-dtypes (>=0.2.0)
DEBUG Selecting: ml-dtypes==0.4.0 (ml_dtypes-0.4.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl)
DEBUG Adding transitive dependency for ml-dtypes==0.4.0: numpy>1.20
DEBUG Adding transitive dependency for ml-dtypes==0.4.0: numpy{python_version >= '3.10'}>=1.21.2
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/72/3a/1ff98da19ad6d54db45e5b2a1e3fb77bd19e54b75cdb20d89f8161384dbb/nvidia_nccl_cu12-2.22.3-py3-none-manylinux2014_x86_64.whl.metadata
DEBUG Found fresh response for: https://pypi.org/simple/numpy/
DEBUG Searching for a compatible version of numpy (>=1.22)
DEBUG Selecting: numpy==2.0.0 (numpy-2.0.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl)
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/d6/a8/6a2419c40c7b6f7cb4ef52c532c88e55490c4fa92885964757d507adddce/numpy-2.0.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata
DEBUG Searching for a compatible version of numpy{python_version >= '3.10'} (>=1.21.2)
DEBUG Selecting: numpy==2.0.0 (numpy-2.0.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl)
DEBUG Adding transitive dependency for numpy==2.0.0: numpy==2.0.0
DEBUG Adding transitive dependency for numpy==2.0.0: numpy{python_version >= '3.10'}==2.0.0
DEBUG Searching for a compatible version of numpy{python_version >= '3.10'} (==2.0.0)
DEBUG Selecting: numpy==2.0.0 (numpy-2.0.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl)
DEBUG Searching for a compatible version of opt-einsum (*)
DEBUG Selecting: opt-einsum==3.3.0 (opt_einsum-3.3.0-py3-none-any.whl)
DEBUG Adding transitive dependency for opt-einsum==3.3.0: numpy>=1.7
DEBUG Searching for a compatible version of scipy (>=1.9)
DEBUG Selecting: scipy==1.14.0 (scipy-1.14.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl)
DEBUG Adding transitive dependency for scipy==1.14.0: numpy>=1.23.5, <2.3
DEBUG Searching for a compatible version of nvidia-cublas-cu12 (>=<IP_ADDRESS>)
DEBUG Selecting: nvidia-cublas-cu12==<IP_ADDRESS> (nvidia_cublas_cu12-<IP_ADDRESS>-py3-none-manylinux2014_x86_64.whl)
DEBUG Searching for a compatible version of nvidia-cuda-cupti-cu12 (>=12.3.101)
DEBUG Selecting: nvidia-cuda-cupti-cu12==12.5.82 (nvidia_cuda_cupti_cu12-12.5.82-py3-none-manylinux2014_x86_64.whl)
DEBUG Searching for a compatible version of nvidia-cuda-nvcc-cu12 (>=12.3.107)
DEBUG Selecting: nvidia-cuda-nvcc-cu12==12.5.82 (nvidia_cuda_nvcc_cu12-12.5.82-py3-none-manylinux2014_x86_64.whl)
DEBUG Searching for a compatible version of nvidia-cuda-runtime-cu12 (>=12.3.101)
DEBUG Selecting: nvidia-cuda-runtime-cu12==12.5.82 (nvidia_cuda_runtime_cu12-12.5.82-py3-none-manylinux2014_x86_64.whl)
DEBUG Searching for a compatible version of nvidia-cudnn-cu12 (>=<IP_ADDRESS>)
DEBUG Selecting: nvidia-cudnn-cu12==<IP_ADDRESS> (nvidia_cudnn_cu12-<IP_ADDRESS>-py3-none-manylinux2014_x86_64.whl)
DEBUG Adding transitive dependency for nvidia-cudnn-cu12==<IP_ADDRESS>: nvidia-cublas-cu12*
DEBUG Searching for a compatible version of nvidia-cufft-cu12 (>=<IP_ADDRESS>)
DEBUG Selecting: nvidia-cufft-cu12==<IP_ADDRESS> (nvidia_cufft_cu12-<IP_ADDRESS>-py3-none-manylinux2014_x86_64.whl)
DEBUG Adding transitive dependency for nvidia-cufft-cu12==<IP_ADDRESS>: nvidia-nvjitlink-cu12*
DEBUG Searching for a compatible version of nvidia-cusolver-cu12 (>=<IP_ADDRESS>)
DEBUG Selecting: nvidia-cusolver-cu12==<IP_ADDRESS> (nvidia_cusolver_cu12-<IP_ADDRESS>-py3-none-manylinux2014_x86_64.whl)
DEBUG Adding transitive dependency for nvidia-cusolver-cu12==<IP_ADDRESS>: nvidia-cublas-cu12*
DEBUG Adding transitive dependency for nvidia-cusolver-cu12==<IP_ADDRESS>: nvidia-nvjitlink-cu12*
DEBUG Adding transitive dependency for nvidia-cusolver-cu12==<IP_ADDRESS>: nvidia-cusparse-cu12*
DEBUG Searching for a compatible version of nvidia-cusparse-cu12 (>=<IP_ADDRESS>)
DEBUG Selecting: nvidia-cusparse-cu12==<IP_ADDRESS> (nvidia_cusparse_cu12-<IP_ADDRESS>-py3-none-manylinux2014_x86_64.whl)
DEBUG Adding transitive dependency for nvidia-cusparse-cu12==<IP_ADDRESS>: nvidia-nvjitlink-cu12*
DEBUG Searching for a compatible version of nvidia-nccl-cu12 (>=2.19.3)
DEBUG Selecting: nvidia-nccl-cu12==2.22.3 (nvidia_nccl_cu12-2.22.3-py3-none-manylinux2014_x86_64.whl)
DEBUG Searching for a compatible version of nvidia-nvjitlink-cu12 (>=12.3.101)
DEBUG Selecting: nvidia-nvjitlink-cu12==12.5.82 (nvidia_nvjitlink_cu12-12.5.82-py3-none-manylinux2014_x86_64.whl)
DEBUG Tried 16 versions: jax 1, jaxlib 1, ml-dtypes 1, numpy 1, nvidia-cublas-cu12 1, nvidia-cuda-cupti-cu12 1, nvidia-cuda-nvcc-cu12 1, nvidia-cuda-runtime-cu12 1, nvidia-cudnn-cu12 1, nvidia-cufft-cu12 1, nvidia-cusolver-cu12 1, nvidia-cusparse-cu12 1, nvidia-nccl-cu12 1, nvidia-nvjitlink-cu12 1, opt-einsum 1, scipy 1
DEBUG Split  took 0.017s
Resolved 16 packages in 21ms
jax[cuda12-pip]==0.4.25
jaxlib==0.4.25+cuda12.cudnn89
ml-dtypes==0.4.0
numpy==2.0.0
nvidia-cublas-cu12==<IP_ADDRESS>
nvidia-cuda-cupti-cu12==12.5.82
nvidia-cuda-nvcc-cu12==12.5.82
nvidia-cuda-runtime-cu12==12.5.82
nvidia-cudnn-cu12==<IP_ADDRESS>
nvidia-cufft-cu12==<IP_ADDRESS>
nvidia-cusolver-cu12==<IP_ADDRESS>
nvidia-cusparse-cu12==<IP_ADDRESS>
nvidia-nccl-cu12==2.22.3
nvidia-nvjitlink-cu12==12.5.82
opt-einsum==3.3.0
scipy==1.14.0
% python -m pip install --find-links=https://storage.googleapis.com/jax-releases/jax_cuda_releases.html 'jax[cuda12-pip]==0.4.25'
Looking in links: https://storage.googleapis.com/jax-releases/jax_cuda_releases.html
Collecting jax==0.4.25 (from jax[cuda12-pip]==0.4.25)
  Downloading jax-0.4.25-py3-none-any.whl.metadata (24 kB)
Requirement already satisfied: ml-dtypes>=0.2.0 in ./conda/polez/lib/python3.10/site-packages (from jax==0.4.25->jax[cuda12-pip]==0.4.25) (0.3.2)
Requirement already satisfied: numpy>=1.22 in ./conda/polez/lib/python3.10/site-packages (from jax==0.4.25->jax[cuda12-pip]==0.4.25) (1.26.4)
Requirement already satisfied: opt-einsum in ./conda/polez/lib/python3.10/site-packages (from jax==0.4.25->jax[cuda12-pip]==0.4.25) (3.3.0)
Requirement already satisfied: scipy>=1.9 in ./conda/polez/lib/python3.10/site-packages (from jax==0.4.25->jax[cuda12-pip]==0.4.25) (1.10.0)
WARNING: jax 0.4.25 does not provide the extra 'cuda12-pip'
Downloading jax-0.4.25-py3-none-any.whl (1.8 MB)
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.8/1.8 MB 34.8 MB/s eta 0:00:00
DEPRECATION: classifier-module e275fddd7c2b90ea6df07b7257dd3e266b52754f has a non-standard version number. pip 24.1 will enforce this behaviour change. A possible replacement is to upgrade to a newer version of classifier-module or contact the author to suggest that they release a version with a conforming version number. Discussion can be found at https://github.com/pypa/pip/issues/12063
DEPRECATION: geopolars 0.1.0a4 has a non-standard dependency specifier pyarrow>=4.0.*. pip 24.1 will enforce this behaviour change. A possible replacement is to upgrade to a newer version of geopolars or contact the author to suggest that they release a version with a conforming dependency specifiers. Discussion can be found at https://github.com/pypa/pip/issues/12063
Installing collected packages: jax
  Attempting uninstall: jax
    Found existing installation: jax 0.4.23
    Uninstalling jax-0.4.23:
      Successfully uninstalled jax-0.4.23
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
chex 0.1.85 requires jaxlib>=0.1.37, which is not installed.
optax 0.1.9 requires jaxlib>=0.1.37, which is not installed.
orbax-checkpoint 0.5.3 requires jaxlib, which is not installed.
Successfully installed jax-0.4.25

[notice] A new release of pip is available: 24.0 -> 24.1.1
[notice] To update, run: pip install --upgrade pip
% python -m pip install --find-links=https://storage.googleapis.com/jax-releases/jax_cuda_releases.html 'jax[cuda12_pip]==0.4.25'
Looking in links: https://storage.googleapis.com/jax-releases/jax_cuda_releases.html
Requirement already satisfied: jax==0.4.25 in ./conda/polez/lib/python3.10/site-packages (from jax[cuda12_pip]==0.4.25) (0.4.25)
Requirement already satisfied: ml-dtypes>=0.2.0 in ./conda/polez/lib/python3.10/site-packages (from jax==0.4.25->jax[cuda12_pip]==0.4.25) (0.3.2)
Requirement already satisfied: numpy>=1.22 in ./conda/polez/lib/python3.10/site-packages (from jax==0.4.25->jax[cuda12_pip]==0.4.25) (1.26.4)
Requirement already satisfied: opt-einsum in ./conda/polez/lib/python3.10/site-packages (from jax==0.4.25->jax[cuda12_pip]==0.4.25) (3.3.0)
Requirement already satisfied: scipy>=1.9 in ./conda/polez/lib/python3.10/site-packages (from jax==0.4.25->jax[cuda12_pip]==0.4.25) (1.10.0)
WARNING: jax 0.4.25 does not provide the extra 'cuda12-pip'
Collecting jaxlib==0.4.25+cuda12.cudnn89 (from jax[cuda12_pip]==0.4.25)
  Downloading https://storage.googleapis.com/jax-releases/cuda12/jaxlib-0.4.25%2Bcuda12.cudnn89-cp310-cp310-manylinux2014_x86_64.whl (143.5 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 143.5/143.5 MB 8.6 MB/s eta 0:00:00
Collecting nvidia-cublas-cu12>=<IP_ADDRESS> (from jax[cuda12_pip]==0.4.25)
  Downloading nvidia_cublas_cu12-<IP_ADDRESS>-py3-none-manylinux2014_x86_64.whl.metadata (1.5 kB)
Collecting nvidia-cuda-cupti-cu12>=12.3.101 (from jax[cuda12_pip]==0.4.25)
  Downloading nvidia_cuda_cupti_cu12-12.5.82-py3-none-manylinux2014_x86_64.whl.metadata (1.6 kB)
Collecting nvidia-cuda-nvcc-cu12>=12.3.107 (from jax[cuda12_pip]==0.4.25)
  Downloading nvidia_cuda_nvcc_cu12-12.5.82-py3-none-manylinux2014_x86_64.whl.metadata (1.5 kB)
Collecting nvidia-cuda-runtime-cu12>=12.3.101 (from jax[cuda12_pip]==0.4.25)
  Downloading nvidia_cuda_runtime_cu12-12.5.82-py3-none-manylinux2014_x86_64.whl.metadata (1.5 kB)
Collecting nvidia-cudnn-cu12>=<IP_ADDRESS> (from jax[cuda12_pip]==0.4.25)
  Downloading nvidia_cudnn_cu12-<IP_ADDRESS>-py3-none-manylinux2014_x86_64.whl.metadata (1.6 kB)
Collecting nvidia-cufft-cu12>=<IP_ADDRESS> (from jax[cuda12_pip]==0.4.25)
  Downloading nvidia_cufft_cu12-<IP_ADDRESS>-py3-none-manylinux2014_x86_64.whl.metadata (1.5 kB)
Collecting nvidia-cusolver-cu12>=<IP_ADDRESS> (from jax[cuda12_pip]==0.4.25)
  Downloading nvidia_cusolver_cu12-<IP_ADDRESS>-py3-none-manylinux2014_x86_64.whl.metadata (1.6 kB)
Collecting nvidia-cusparse-cu12>=<IP_ADDRESS> (from jax[cuda12_pip]==0.4.25)
  Downloading nvidia_cusparse_cu12-<IP_ADDRESS>-py3-none-manylinux2014_x86_64.whl.metadata (1.6 kB)
Collecting nvidia-nccl-cu12>=2.19.3 (from jax[cuda12_pip]==0.4.25)
  Downloading nvidia_nccl_cu12-2.22.3-py3-none-manylinux2014_x86_64.whl.metadata (1.8 kB)
Collecting nvidia-nvjitlink-cu12>=12.3.101 (from jax[cuda12_pip]==0.4.25)
  Downloading nvidia_nvjitlink_cu12-12.5.82-py3-none-manylinux2014_x86_64.whl.metadata (1.5 kB)
Downloading nvidia_cublas_cu12-<IP_ADDRESS>-py3-none-manylinux2014_x86_64.whl (363.3 MB)
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 363.3/363.3 MB 10.9 MB/s eta 0:00:00
Downloading nvidia_cuda_cupti_cu12-12.5.82-py3-none-manylinux2014_x86_64.whl (13.8 MB)
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 13.8/13.8 MB 68.2 MB/s eta 0:00:00
Downloading nvidia_cuda_nvcc_cu12-12.5.82-py3-none-manylinux2014_x86_64.whl (22.5 MB)
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 22.5/22.5 MB 22.7 MB/s eta 0:00:00
Downloading nvidia_cuda_runtime_cu12-12.5.82-py3-none-manylinux2014_x86_64.whl (895 kB)
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 895.7/895.7 kB 62.9 MB/s eta 0:00:00
Downloading nvidia_cudnn_cu12-<IP_ADDRESS>-py3-none-manylinux2014_x86_64.whl (574.6 MB)
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 574.6/574.6 MB 7.9 MB/s eta 0:00:00
Downloading nvidia_cufft_cu12-<IP_ADDRESS>-py3-none-manylinux2014_x86_64.whl (192.5 MB)
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 192.5/192.5 MB 14.2 MB/s eta 0:00:00
Downloading nvidia_cusolver_cu12-<IP_ADDRESS>-py3-none-manylinux2014_x86_64.whl (130.3 MB)
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 130.3/130.3 MB 22.8 MB/s eta 0:00:00
Downloading nvidia_cusparse_cu12-<IP_ADDRESS>-py3-none-manylinux2014_x86_64.whl (217.6 MB)
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 217.6/217.6 MB 13.5 MB/s eta 0:00:00
Downloading nvidia_nccl_cu12-2.22.3-py3-none-manylinux2014_x86_64.whl (190.9 MB)
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 190.9/190.9 MB 22.3 MB/s eta 0:00:00
Downloading nvidia_nvjitlink_cu12-12.5.82-py3-none-manylinux2014_x86_64.whl (21.3 MB)
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 21.3/21.3 MB 63.0 MB/s eta 0:00:00
DEPRECATION: classifier-module e275fddd7c2b90ea6df07b7257dd3e266b52754f has a non-standard version number. pip 24.1 will enforce this behaviour change. A possible replacement is to upgrade to a newer version of classifier-module or contact the author to suggest that they release a version with a conforming version number. Discussion can be found at https://github.com/pypa/pip/issues/12063
DEPRECATION: geopolars 0.1.0a4 has a non-standard dependency specifier pyarrow>=4.0.*. pip 24.1 will enforce this behaviour change. A possible replacement is to upgrade to a newer version of geopolars or contact the author to suggest that they release a version with a conforming dependency specifiers. Discussion can be found at https://github.com/pypa/pip/issues/12063
Installing collected packages: nvidia-nvjitlink-cu12, nvidia-nccl-cu12, nvidia-cuda-runtime-cu12, nvidia-cuda-nvcc-cu12, nvidia-cuda-cupti-cu12, nvidia-cublas-cu12, nvidia-cusparse-cu12, nvidia-cufft-cu12, nvidia-cudnn-cu12, jaxlib, nvidia-cusolver-cu12
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
torch 2.2.0 requires nvidia-cuda-nvrtc-cu12==12.1.105; platform_system == "Linux" and platform_machine == "x86_64", which is not installed.
torch 2.2.0 requires nvidia-curand-cu12==<IP_ADDRESS>; platform_system == "Linux" and platform_machine == "x86_64", which is not installed.
torch 2.2.0 requires nvidia-nvtx-cu12==12.1.105; platform_system == "Linux" and platform_machine == "x86_64", which is not installed.
torch 2.2.0 requires nvidia-cublas-cu12==<IP_ADDRESS>; platform_system == "Linux" and platform_machine == "x86_64", but you have nvidia-cublas-cu12 <IP_ADDRESS> which is incompatible.
torch 2.2.0 requires nvidia-cuda-cupti-cu12==12.1.105; platform_system == "Linux" and platform_machine == "x86_64", but you have nvidia-cuda-cupti-cu12 12.5.82 which is incompatible.
torch 2.2.0 requires nvidia-cuda-runtime-cu12==12.1.105; platform_system == "Linux" and platform_machine == "x86_64", but you have nvidia-cuda-runtime-cu12 12.5.82 which is incompatible.
torch 2.2.0 requires nvidia-cudnn-cu12==<IP_ADDRESS>; platform_system == "Linux" and platform_machine == "x86_64", but you have nvidia-cudnn-cu12 <IP_ADDRESS> which is incompatible.
torch 2.2.0 requires nvidia-cufft-cu12==<IP_ADDRESS>; platform_system == "Linux" and platform_machine == "x86_64", but you have nvidia-cufft-cu12 <IP_ADDRESS> which is incompatible.
torch 2.2.0 requires nvidia-cusolver-cu12==<IP_ADDRESS>; platform_system == "Linux" and platform_machine == "x86_64", but you have nvidia-cusolver-cu12 <IP_ADDRESS> which is incompatible.
torch 2.2.0 requires nvidia-cusparse-cu12==<IP_ADDRESS>; platform_system == "Linux" and platform_machine == "x86_64", but you have nvidia-cusparse-cu12 <IP_ADDRESS> which is incompatible.
torch 2.2.0 requires nvidia-nccl-cu12==2.19.3; platform_system == "Linux" and platform_machine == "x86_64", but you have nvidia-nccl-cu12 2.22.3 which is incompatible.
Successfully installed jaxlib-0.4.25+cuda12.cudnn89 nvidia-cublas-cu12-<IP_ADDRESS> nvidia-cuda-cupti-cu12-12.5.82 nvidia-cuda-nvcc-cu12-12.5.82 nvidia-cuda-runtime-cu12-12.5.82 nvidia-cudnn-cu12-<IP_ADDRESS> nvidia-cufft-cu12-<IP_ADDRESS> nvidia-cusolver-cu12-<IP_ADDRESS> nvidia-cusparse-cu12-<IP_ADDRESS> nvidia-nccl-cu12-2.22.3 nvidia-nvjitlink-cu12-12.5.82

[notice] A new release of pip is available: 24.0 -> 24.1.1
[notice] To update, run: pip install --upgrade pip

Hi! Please see the PEP 685 specification which says:

When comparing extra names, tools MUST normalize the names being compared using the semantics outlined in PEP 503 for names:
re.sub(r"[-_.]+", "-", name).lower()

Using and displaying - is spec-compliant. Maybe something else is going wrong?

Could you split up your examples a bit with some explanation of what each invocation is demonstrating? It's pretty hard to understand as-is.

Yeah, this is an issue with pip, not uv, and is fixed in pip 24.1, as the notice says, update your pip:
[notice] A new release of pip is available: 24.0 -> 24.1.1
[notice] To update, run: pip install --upgrade pip

Or use uv to install, rather than pip.

Thanks @notatallshaw, appreciate the confirmation.


[Impeller] Consider caching or at least trying to reuse VkFramebuffer and RenderPass objects

Per https://registry.khronos.org/vulkan/specs/1.3-extensions/html/vkspec.html#renderpass-compatibility, we can reuse the framebuffer as long as the render passes are compatible (and the width/height haven't changed presumably).
I suspect for many frames, the previous frame's framebuffer is reusable.
We could also try to come up with a caching mechanism if this isn't sufficient.
Motivation is an internal trace of an app on a Pixel 5 device, which shows significant time spent in vkCreateFramebuffer:

There are a lot of caveats with framebuffer caching, @gaaclarke worked on this a bit last year. Essentially everything, down to the image views / images needs to be the same. They may not be safe to use until fences have been signaled. The management seems quite difficult.
Though rather than some sort of uniform caching system, we might consider caching the framebuffer for the onscreen render pass. As that should be a lot more static - and since we know the swapchain images invalidation cycle, it could be an easier first attempt/

My first thought was for the onscreen render pass - I'm not sure how much sense it'll make to cache offscreen passes that could be very different very frequently.
I think it should be a somewhat simple experiment to cache an onscreen pass FBO and see if it helps much.

Also worth noting that I believe the pixel 5 is an adreno whereas the 7s we have are arm, so the driver might have different performance characteristics

Rough idea:

Make SwapchainImageVK store some kind of vk::Framebuffer and vk::FramebufferCreateInfo.
When we create an RT for the swapchain image, put the framebuffer and info on it.
When we go to create the FBO for the rt, check if the FBO it has is compatible. If so, use it, if not, create new.
When we go to present the swapchain image, store the FBO and create info back on the swapchain image.

I'm not quite sure if this will work or how to do it cleanly yet (putting vulkan specific stuff on RenderTarget seems not quite right to me).

You might consider storing them on the TextureSource used by the swapchain images, which we have to access in the render_pass constructor. Then we don't leak vulkan specific objects.

A similar trace on a Mali GPU (pixel 7 pro) shows VkFramebuffer creation as taking very little time.

Here is a fun one:
More than half of CPU time is render pass creation. I have some ideas on how to fix this everywhere, though I think I've provied it can work for onscreen with: https://github.com/flutter/engine/pull/50142

This still needs to be done for onscreens.

Sorry about the closing idk why github decided to close it after I did a rebase on my personal fork!?

No worries, GitHub is weird


Running ts-jest leading to error

Bug report
Describe the bug
When running the tests ts-jest, on a component styled with Stitches, I'm encountering an error regarding the createCss function.
The error looks like this:
TypeError: Cannot read property 'length' of undefined
   5 | export type CSS = StitchesCss<typeof stitches>;
   6 |
>  7 | const stitches = createCss({
     |                  ^
   8 |   theme: {
   9 |     colors: {
  10 |       shadowLight: 'hsl(206 22% 7% / 35%)',

To Reproduce
The best way to reproduce this "bug", is simply by running the tests on this repo
yarn test
Expected behavior
The test should run without any errors.
Screenshots

System information

OS: [macOS]
Version of Stitches: [0.1.9 / 0.2.0]
Version of Node.js: tested in v14 and v16

Additional context
The project where I'm dealing with this was based on a TSDX template.

This bug is unique to Stitches 0.1.x. It is not present in Stitches v0.2.x.
The cause of the bug in 0.1.x is an incomplete DOM implementation in Jest, inherited from JSDOM.


Add definition for node-config-manager

https://www.npmjs.com/package/node-config-manager

node-config-manager/node-config-manager.d.ts
check list

[ ] is collect naming convention?

https://www.npmjs.com/package/node-config-manager
http://bower.io/search/?q=node-config-manager
others?

[ ] has a test file? (node-config-manager/node-config-manager-tests.ts or others)
[ ] pass the Travis-CI test?

ping @vvakame

sorry for late! it merged.


Support polling when a device has data that it doesn't broadcast

I slapped together a dumb prototype to enable the discussion I want to have around this. It is for reading the battery sensor on a MiFlora. You get the battery level by reading the first byte of 00001a02-0000-1000-8000-00805f9b34fb. Weirdly that is also the register that contains the firmware version.
The simple and dumb approach looks like this:
diff --git a/homeassistant/components/xiaomi_ble/sensor.py b/homeassistant/components/xiaomi_ble/sensor.py
index dcb9542260..c397ae9f26 100644
--- a/homeassistant/components/xiaomi_ble/sensor.py
+++ b/homeassistant/components/xiaomi_ble/sensor.py
@@ -1,8 +1,12 @@
 """Support for xiaomi ble sensors."""
 from __future__ import annotations
+import asyncio
+import datetime
+import logging

 from typing import Optional, Union

+from bleak import BleakClient
 from xiaomi_ble import (
     DeviceClass,
     DeviceKey,
@@ -13,6 +17,8 @@ from xiaomi_ble import (
 )
 from xiaomi_ble.parser import EncryptionScheme

+from homeassistant.components import bluetooth
+from homeassistant.helpers.event import async_track_time_interval
 from homeassistant import config_entries
 from homeassistant.components.bluetooth import BluetoothServiceInfoBleak
 from homeassistant.components.bluetooth.passive_update_processor import (
@@ -209,6 +215,7 @@ async def async_setup_entry(
     )
     entry.async_on_unload(coordinator.async_register_processor(processor))

+    async_add_entities([FlowerCareBatterySensor(entry)], True)

 class XiaomiBluetoothSensorEntity(
     PassiveBluetoothProcessorEntity[
@@ -222,3 +229,36 @@ class XiaomiBluetoothSensorEntity(
     def native_value(self) -> int | float | None:
         """Return the native value."""
         return self.processor.entity_data.get(self.entity_key)
+
+class FlowerCareBatterySensor(SensorEntity):
+
+    _attr_device_class: SensorDeviceClass.BATTERY
+    _attr_unit_of_measurement = PERCENTAGE
+    # _attr_has_entity_name = True
+
+    def __init__(self, entry: config_entries.ConfigEntry) -> None:
+        self._address = entry.unique_id
+        self._attr_device_info: DeviceInfo(
+            manufacturer="Xiaomi",
+            model="HHCCJCY01",
+            identifiers=set(("bluetooth", entry.unique_id))
+        )
+
+    async def async_added_to_hass(self) -> None:
+        self.async_on_remove(
+            async_track_time_interval(self.hass, self.async_poll, datetime.timedelta(days=1))
+        )
+        self.hass.async_add_job(self.async_poll())
+
+    async def async_poll(self, now=None):
+        if ble_device := bluetooth.async_ble_device_from_address(self.hass, self._address.upper()):
+            try:
+                async with BleakClient(ble_device) as client:
+                    payload = await client.read_gatt_char("00001a02-0000-1000-8000-00805f9b34fb")
+            except asyncio.TimeoutError:
+                return
+
+            # First byte is battery level, 2 byte unknown, rest of packet is the firmware version
+            self._attr_native_value = payload[0]
+
+            self.async_write_ha_state()
\ No newline at end of file

Things I immediately don't like:

The decision about which extra sensors to load is in HA, but the bulk of that is actually determined by XiaomiBluetoothDeviceData. This feels weird.
I don't want to replicate the device info logic from the existing passive sensors. I don't want to replicate the naming logic from the existing passive sensors.
The actual reading and parsing code shouldn't be in HA, that needs pulling into xiaomi-ble. But thats only a small part of this diff.
Given there are 2 values in this char, it would kind of be useful to have them in a update coordinator. Given one of them is the firmware version and applicable to every entity, it would be useful to be in the existing (passive) update coordinator.
This version has a bug: It tries to read the battery level on startup but the ble_device is never in the cache. Ideally the poll period is 24h as a default, so battery sensor will be unavailable until a day has elapsed.

I wondered about instead:

The battery should be defined in the XiaomiBluetoothDeviceData, and its value should be picked up from the class during an update() like normal. That would probably mean defining that the battery sensor exists but has no value at the time its defined (in response to a broadcast where we learn the model number). We could use the exact same and existing machinery on the HA side to get entities created, linked to a device and to push out new values.
I think instead of polling on a strict timer, we could use the advertisements as a tick, and a monotonic expiry timer to see "have 24 hours passed yet". This means we will poll at most once every 24 hour, and if a device is offline at start (or for more than 24 hours) we will poll it the next time we see it. Thats much nicer than one tick every 24 hours, and fixes the bug i mentioned.

However I don't have a full enough grasp of the existing sensor data API's to see if I can make this all pull together. While i defined a method to detect when a poll is due, I am not sure how that poll is run. Right now there is no awaitable code in xiaom-ble - its just parsing passive data.

Version 2. Roughly based on a conversation on Discord with @bdraco

This achieves my 2 main objects:

polls are every 24 hours, as soon as we see the device at startup, or as soon as we seen the device if its out of range or off etc.
we leverage the existing machinery around naming and the device registry. all the sensor definitions happen on the DeviceData side, not on the HA side. The HA side just does data type mapping, like with the passive updates.

https://github.com/Bluetooth-Devices/xiaomi-ble/compare/add_miflora_poll - xiaomi-ble changes
https://github.com/home-assistant/core/compare/dev...Jc2k:home-assistant:xiaomi_ble_poll_plant_battery - hass changes


Add trailing space to attributes in VariableDecl

A small fix for the generated trivia when using attributes and modifiers together in VariableDecl, as detailed in https://github.com/apple/swift-syntax/pull/667#issuecomment-1232598906.

@swift-ci please test


Add search functionality for website/docs

We need some sort of search on the website so we can traverse all the documentation. See adding search with Gatsby.

Design, where will the search bar be placed? (desktop and mobile)
What search library will we use?

@ddunn2 have you looked at implementing search before? I'm looking at using Algolia

@tomleah Sorry I didn't see this comment.
Is Algolia free to use? Or are you getting a license for it?
I was looking at using one of the Open Source options Gatsby has.
Once I'm hoping to start looking into this next week :)

I was looking at it based on Gatsby.org using it.
Algolia says:

Our free offering for small personal projects (non-commercial use)

I haven't looked at elasticlunr or js-search yet


Some hyperparameters are deprecated in pytorch-lightning new version (>1.8.5)

For example the args.resume_from_checkpoint = load_path is deprecated
And now you have to use args.ckpt_path = load_path to load the trained model
If I've fixed the deprecated function in your template can I just PR?

Sure! Thanks a lot!
Ian Peng @.***>于2022年12月20日 周二下午11:10写道：

For example the args.resume_from_checkpoint = load_path is deprecated
And now you have to use args.ckpt_path = load_path to load the trained
model
If I've fixed the deprecated function in your template can I just PR?
—
Reply to this email directly, view it on GitHub
https://github.com/miracleyoo/pytorch-lightning-template/issues/6, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ADWXH5EPAUY62WNEUOFGAYDWOKUQBANCNFSM6AAAAAATFJRB34
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

--
Zhongyang Zhang

Ph.D. Candidate, Zhongyang Zhang
University of Massachusetts Amherst
College of Information and Computer Science
@.***

Thanks ~ I've created PR.


Links are not working

Hi,
There are several links that are not working. I.e: if you go to https://www.adobe.io/photoshop/uxp/guides, these are not working:
https://www.adobe.io/photoshop/uxp/uxp_guide/uxp-misc/file-access/
https://www.adobe.io/photoshop/uxp/uxp_guide/uxp-misc/network-io/
https://www.adobe.io/photoshop/uxp/uxp-developer-tool/
https://www.adobe.io/photoshop/uxp/uxp_guide/uxp-misc/localization-and-platforms/
https://www.adobe.io/photoshop/uxp/uxp_guide/uxp-misc/flyout-menus/
Can you please update those?
Thank you
Rafael

I can't repro this on the site as it stands now; please double check and LMK if you're still having a problem.

Hi @kerrishotts thanks for your feedback.
On my side, every time I try to access one of the links I get a 404, no matter the browser I use or machine

Hi @rbgala84. The URLs in question are erroneous. How were they obtained? For example, the correct file access URL is:
https://www.adobe.io/photoshop/uxp/guides/uxp_guide/uxp-misc/file-access/
Which is correctly linked from here:
https://www.adobe.io/photoshop/uxp/guides/uxp_guide/uxp-misc/
But the URL you posted is:
https://www.adobe.io/photoshop/uxp/uxp_guide/uxp-misc/file-access/
which is missing the /guides/ inner path.
@kerrishotts I'm wondering if this is another case of "zombie" links not being purged?

Hi @chuckweger,
The links I've posted were coming from here:

I've checked again, and it seems the site is now pointing to the right ones!
Thanks for fixing this


Console error: Cannot read property 'toString' of undefined

Why I always got this error? I run this cmd: ManiaConverter.exe "-fileinput:beatmap" "-fileoutput:converted" "-mode:2" "-side:1" "-key:4" "-artist:Artist"
C:\Local\mania\lib\Utils.js:106
                map[i] = map_[i].toString();
                                ^

TypeError: Cannot read property 'toString' of undefined
    at Object.exports.getMapOptions (C:\Local\mania\lib\Utils.js:106:19)
    at fnf_to_osu (C:\Local\mania\lib\Converter.js:420:22)
    at Object.exports.convert (C:\Local\mania\lib\Converter.js:14:13)
    at Object.<anonymous> (C:\Local\mania\index.js:33:23)

uh, you sure what you have beatmap.json in folder with converter?

check new update, maybe it fixed

check new update, maybe it fixed

it fixed, thanks!


Change in Invite New Users Documentation

It should be mentioned in the documentation that we can only   "Generate Invite Link"  if we are administrator  . But it is not mentioned now .

@zulipbot claim

For context, we prevent multi-user invites with our require_realm_admin decorator.  It's possible that in the long term we might want a way to relax this restriction, but I agree with @SushanthReddyManda that we should document the current behavior.  Thanks for reporting this!
138 @require_realm_admin
139 @has_request_variables
140 def generate_multiuse_invite_backend(

@showell Changing like this is ok ??

I have created this https://github.com/zulip/zulip/pull/16956 . Which Updates above Issue to the Documentation . I am Happy to hear suggestions about this PR .


fix(mongodb): mongodb v6.4.0 & 6.5.0 support

Which problem is this PR solving?
the new version of mongodb v6.4.0 comes with some internal changes that break the instrumentation. Drtails of the changes are described in https://github.com/open-telemetry/opentelemetry-js-contrib/issues/1983#issuecomment-1979740812
Closes: #1983
Short description of the changes
patches of the changed methods have been refactored to accept both implementations

handling callbacks for <6.4.0
handling returned promises for >=6.4.0

@trentm I did the split you suggested but partially. I think it was overkill to split the logic of the connect patch.
Now I'm hitting a problem in test-all-versions script. It is failing for<EMAIL_ADDRESS>in the beforeEach method of the tests which is quite odd.
if I log the version under test...
--- a/plugins/node/opentelemetry-instrumentation-mongodb/test/mongodb-v4.test.ts
+++ b/plugins/node/opentelemetry-instrumentation-mongodb/test/mongodb-v4.test.ts
@@ -56,6 +56,9 @@ describe('MongoDBInstrumentation-Tracing-v4', () => {
   const COLLECTION_NAME = 'test-traces';
   const URL = `mongodb://${HOST}:${PORT}/${DB_NAME}`;

+  const version = require('mongodb/package.json').version;
+  console.log(`testing mongodb@${version}`);
+
   let client: mongodb.MongoClient;
   let collection: mongodb.Collection;

it turns out we get a different version for testing
><EMAIL_ADDRESS>test-v4
> nyc ts-mocha -p tsconfig.json --require '@opentelemetry/contrib-test-utils' 'test/mongodb-v4-v5-v6.metrics.test.ts' 'test/**/mongodb-v4.test.ts'

testing<EMAIL_ADDRESS>
  MongoDBInstrumentation-Metrics
    ✓ Should add connection usage metrics (101ms)
    ✓ Should add disconnection usage metrics (213ms)

  MongoDBInstrumentation-Tracing-v4
    Instrumenting query operations
      1) "before each" hook: mongoBeforeEach for "should create a child span for insert"
      2) "after each" hook for "should create a child span for insert"

  2 passing (4s)
  2 failing

....

@trentm I think you got into a similar situation but I can't find the issue or PR. Do you recall having a similar issue? 🤔

@trentm I think you got into a similar situation but I can't find the issue or PR. Do you recall having a similar issue? 🤔

Yup, it was described here: https://github.com/open-telemetry/opentelemetry-js-contrib/pull/1938#issuecomment-1960183358
At the time the conflict (also for version<EMAIL_ADDRESS>was -- I think -- because of a conflict with the "plugins/node/opentelemetry-instrumentation/mongodb/examples" package, which we've since removed. However, now we get the same because of a pinned "mongodb" transitive dep from instrumentation-mongoose:
[~/tm/opentelemetry-js-contrib2/plugins/node/opentelemetry-instrumentation-mongodb (git:1983-mongodb-6-4-support)]
% npm ls mongodb
<EMAIL_ADDRESS>/Users/trentm/tm/opentelemetry-js-contrib2
└─┬<EMAIL_ADDRESS>-> ./plugins/node/opentelemetry-instrumentation-mongodb
  └──<EMAIL_ADDRESS>
[~/tm/opentelemetry-js-contrib2/plugins/node/opentelemetry-instrumentation-mongodb (git:1983-mongodb-6-4-support)]
% npm install --no-save<EMAIL_ADDRESS>...

[~/tm/opentelemetry-js-contrib2/plugins/node/opentelemetry-instrumentation-mongodb (git:1983-mongodb-6-4-support)]
% npm ls mongodb
<EMAIL_ADDRESS>/Users/trentm/tm/opentelemetry-js-contrib2
└─┬<EMAIL_ADDRESS>-> ./plugins/node/opentelemetry-instrumentation-mongodb
  └──<EMAIL_ADDRESS>
The looking for any npm install felt it didn't need to install v4.17.1 locally:
[~/tm/opentelemetry-js-contrib2 (git:1983-mongodb-6-4-support)]
% npm ls mongodb
<EMAIL_ADDRESS>/Users/trentm/tm/opentelemetry-js-contrib2
├─┬<EMAIL_ADDRESS>-> ./plugins/node/opentelemetry-instrumentation-mongodb
│ └──<EMAIL_ADDRESS>└─┬<EMAIL_ADDRESS>-> ./plugins/node/instrumentation-mongoose
  └─┬<EMAIL_ADDRESS>    └──<EMAIL_ADDRESS>
Ew. This has to be an npm bug. I'm not sure how to cope with this in general.
We discussed (in DMs) explicitly skipping v4.17.1 in the .tav.yml file. That's a hack, but I can't think of anything better.

So the split decreased the coverage enough to block the PR. Will add more tests to increase it back shortly

By looking at the docs there is no way to tell codecov that a specific code path is expected to not to be covered. I guess the solution would be to make use of merge reports but IMO this is out of scope of this PR
@pichlermarc do you think is okay to move forward and have a follow-up PR about merging coverage reports from unit testing?

I agree dealing with merging of coverage reports is out of scope for this PR.


Subsetting Changes Object's Class

The documented return value suggests that it should remain a MAF object if the input is a MAF.
laml.maf <- system.file("extdata", "tcga_laml.maf.gz", package = "maftools")
laml <- read.maf(maf = laml.maf)
> class(laml)
[1] "MAF"
miniExample <- subsetMaf(laml, levels(laml@data[["Tumor_Sample_Barcode"]])[1:20])
> class(miniExample)
[1] "data.table" "data.frame"

Hi,
By default subsetMaf returns data.table, but you can set mafObj = TRUE to get MAF object.
In the beginning I thought it made sense to return data-table, but after I received several issues, I think it would make sense to return maf object by default. I will change it in next push.

I overlooked the parameter mafObj. I assumed that subsetting is endomorphic (function's return type is the same as the input data type).

Hi,
I have changed default value for mafObj to TRUE. Thanks for the reporting.


musescore: 3.6.2 -> 4.0

Description of changes
Updated MuseScore to version 4
Closes #206539.
Still needs someone to test on Darwin. Should work but I don’t have a Mac.
Did this relatively naively, please also check out #206559 for a different approach (but w/o updating the Darwin version)

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Can we decide whether we want to continue here or in https://github.com/NixOS/nixpkgs/pull/206559?

I think it might be better to continue with #206559 because that one keeps the packaging from before intact (only a few changes) whereas I tore down the entire packaging—but also, it’s unclear which of the fixes are still needed since MS4 is such a big overhaul

Any update or help needed?
Looking forward to seeing this updated!
Also, is there a way to be able to install MuseHub in the future? (I know it is not FOSS)

We already updated MuseScore in #206559. You may need to wait for the next NixOS release or switch to the unstable channel to get it.
As to Muse Hub, you can file a packaging request here. It’s however difficult to package because it’s only distributed as a .deb package last I checked.


TFT.ino in example/TFT does not draw to screen

Using latest Arduino IDE. TFT_eSPI library is installed. girl.h, logo.h, logo2.h, pin_config.h are all in the same folder as TFT.ino. Code will upload but display remains on and blank. Please include all details needed to draw to the screen. Are there any config files that need to be changed?

I'm guessing you're in download mode. Please unplug the device and be careful not to hold down the key while reconnecting to run user code.

I plugged it in without holding down the key and the code still does not run.

Did you recognize the serial port? Do you have a serial port software like this? This software is downloaded from Microsoft.

Is the screen damaged. I upload a test firmware for you to test.
测试程序.zip

Screen is not damaged. I uploaded the firmware you posted and when I plug in the USB there is a logo of "LILYGO" and the led light changes colors. But the TFT.ino code still doesn't won't work if I upload it onto the esp32.

I did a fresh install of everything and redownloaded all the files in "lib" and now it's working. I guess just a fresh install of Arduino IDE and all files for this project fixed it.


mmrotate

Hi,thanks for your excellent work.I was wondering when your work will be added to MMRotate1. x?Looking forward to seeing you work on mmarotate1.x.

I think this job is not good enough to be included in mmrotate😂, but you can still use it for your own work.

您好，我想在DIOR-R数据集上复现您的ARS-DETR模型，但在测试时出现了错误，您可否提供关于DIOR-R数据集的配置文件？谢谢您的工作！
酒醉逍遥
@.**

------------------ 原始邮件 ------------------
发件人:                                                                                "httle/ARS-DETR"                                                                                @.>;
发送时间: 2023年10月16日(星期一) 上午9:06
@.>;
<EMAIL_ADDRESS>主题: Re: [httle/ARS-DETR] mmrotate (Issue #5)
I think this job is not good enough to be included in mmrotate😂, but you can still use it for your own work.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>


Add tenantID support for tempo

I like this change, but there are a few extra steps to ensure that the generated content stays up to date.
Can you run the helm-docs and make regenerate-example-outputs steps. See https://github.com/grafana/k8s-monitoring-helm#contributing for more context.

Can do, I should've checked that doc before throwing these over the fence.  I'll get the additional work done later today. Thanks!


SharedDirectory's header blob re-used for a SharedMap

As per this IcM incident, we see that the "header" blob of a SharedDirectory is being used for a SharedMap.
Initial analysis points to this being a bug in the driver. More details in the IcM ticket.

related #5346

@anthony-murphy we can remove the OCE tag since the related incidents were mitigated by disabling blob deduping, right?

Removing OCE tag per note this was mitigated already.

@jatgarg Can you verify that this is resolved and then close this bug? Thanks!

This but and #5353 are not resolved, but we have turned off the feature. We either need to intestigate further, or just remove the offending feature to close

I want to propose we move it out to May.
Mitigations are in (including disabling code in driver).
We need to get back to it and make a call on what to do next, but I feel like the call would be - not use deduping at all for time being, especially that it's efficiency would be close to zero with blob aggregation.
We have a lot of other work this month (really - last month before GA).

We already have an issue open for that: https://github.com/microsoft/FluidFramework/issues/5444
Maybe we can close this issue as we are not facing this anymore due to disabling blob deduping. @vladsud

Closing this issue as we not seeing any new instances for this.


CosmosDB (*ContainerClient).ReadItem() not thread safe (any longer)

When upgrading from azcosmos 0.3.6 to 1.0.1 we see race detector warnings when concurrently doing (*ContainerClient).ReadItem(). We do this in several places for performance/concurrency, and so far it has worked well.

Previous write at 0x00c0002e59f0 by goroutine 142:
  github.com/Azure/azure-sdk-for-go/sdk/data/azcosmos.(*clientRetryPolicy).resetPolicyCounters()
      /home/runner/go/pkg/mod/github.com/!azure/azure-sdk-for-go/sdk/data/azcosmos@v1.0.1/cosmos_client_retry_policy.go:178 +0x70
  github.com/Azure/azure-sdk-for-go/sdk/data/azcosmos.(*clientRetryPolicy).Do()
      /home/runner/go/pkg/mod/github.com/!azure/azure-sdk-for-go/sdk/data/azcosmos@v1.0.1/cosmos_client_retry_policy.go:30 +0x68
  github.com/Azure/azure-sdk-for-go/sdk/azcore/internal/exported.(*Request).Next()
      /home/runner/go/pkg/mod/github.com/!azure/azure-sdk-for-go/sdk/azcore@v1.11.1/internal/exported/request.go:107 +0x218
  github.com/Azure/azure-sdk-for-go/sdk/data/azcosmos.(*sharedKeyCredPolicy).Do()
      /home/runner/go/pkg/mod/github.com/!azure/azure-sdk-for-go/sdk/data/azcosmos@v1.0.1/shared_key_credential.go:122 +0x466
  github.com/Azure/azure-sdk-for-go/sdk/azcore/internal/exported.(*Request).Next()
      /home/runner/go/pkg/mod/github.com/!azure/azure-sdk-for-go/sdk/azcore@v1.11.1/internal/exported/request.go:107 +0x218
  github.com/Azure/azure-sdk-for-go/sdk/azcore/runtime.(*retryPolicy).Do()
      /home/runner/go/pkg/mod/github.com/!azure/azure-sdk-for-go/sdk/azcore@v1.11.1/runtime/policy_retry.go:121 +0x739
  github.com/Azure/azure-sdk-for-go/sdk/azcore/internal/exported.(*Request).Next()
      /home/runner/go/pkg/mod/github.com/!azure/azure-sdk-for-go/sdk/azcore@v1.11.1/internal/exported/request.go:107 +0x218
  github.com/Azure/azure-sdk-for-go/sdk/data/azcosmos.(*globalEndpointManagerPolicy).Do()
      /home/runner/go/pkg/mod/github.com/!azure/azure-sdk-for-go/sdk/data/azcosmos@v1.0.1/cosmos_global_endpoint_manager_policy.go:32 +0x14b
  github.com/Azure/azure-sdk-for-go/sdk/azcore/internal/exported.(*Request).Next()
      /home/runner/go/pkg/mod/github.com/!azure/azure-sdk-for-go/sdk/azcore@v1.11.1/internal/exported/request.go:107 +0x218
  github.com/Azure/azure-sdk-for-go/sdk/data/azcosmos.(*headerPolicies).Do()
      /home/runner/go/pkg/mod/github.com/!azure/azure-sdk-for-go/sdk/data/azcosmos@v1.0.1/cosmos_headers_policy.go:51 +0x7f8
  github.com/Azure/azure-sdk-for-go/sdk/azcore/internal/exported.(*Request).Next()
      /home/runner/go/pkg/mod/github.com/!azure/azure-sdk-for-go/sdk/azcore@v1.11.1/internal/exported/request.go:107 +0x218
  github.com/Azure/azure-sdk-for-go/sdk/azcore/runtime.telemetryPolicy.Do()
      /home/runner/go/pkg/mod/github.com/!azure/azure-sdk-for-go/sdk/azcore@v1.11.1/runtime/policy_telemetry.go:70 +0x2a5
  github.com/Azure/azure-sdk-for-go/sdk/azcore/runtime.(*telemetryPolicy).Do()
      <autogenerated>:1 +0x5a
  github.com/Azure/azure-sdk-for-go/sdk/azcore/internal/exported.(*Request).Next()
      /home/runner/go/pkg/mod/github.com/!azure/azure-sdk-for-go/sdk/azcore@v1.11.1/internal/exported/request.go:107 +0x218
  github.com/Azure/azure-sdk-for-go/sdk/azcore/runtime.includeResponsePolicy()
      /home/runner/go/pkg/mod/github.com/!azure/azure-sdk-for-go/sdk/azcore@v1.11.1/runtime/policy_include_response.go:19 +0x2e
  github.com/Azure/azure-sdk-for-go/sdk/azcore/internal/exported.PolicyFunc.Do()
      /home/runner/go/pkg/mod/github.com/!azure/azure-sdk-for-go/sdk/azcore@v1.11.1/internal/exported/request.go:177 +0x33
  github.com/Azure/azure-sdk-for-go/sdk/azcore/internal/exported.(*Request).Next()
      /home/runner/go/pkg/mod/github.com/!azure/azure-sdk-for-go/sdk/azcore@v1.11.1/internal/exported/request.go:107 +0x218
  github.com/Azure/azure-sdk-for-go/sdk/azcore/internal/exported.Pipeline.Do()
      /home/runner/go/pkg/mod/github.com/!azure/azure-sdk-for-go/sdk/azcore@v1.11.1/internal/exported/pipeline.go:76 +0x8f
  github.com/Azure/azure-sdk-for-go/sdk/data/azcosmos.(*Client).executeAndEnsureSuccessResponse()
      /home/runner/go/pkg/mod/github.com/!azure/azure-sdk-for-go/sdk/data/azcosmos@v1.0.1/cosmos_client.go:476 +0x113
  github.com/Azure/azure-sdk-for-go/sdk/data/azcosmos.(*Client).sendGetRequest()
      /home/runner/go/pkg/mod/github.com/!azure/azure-sdk-for-go/sdk/data/azcosmos@v1.0.1/cosmos_client.go:357 +0x124
  github.com/Azure/azure-sdk-for-go/sdk/data/azcosmos.(*ContainerClient).ReadItem()
      /home/runner/go/pkg/mod/github.com/!azure/azure-sdk-for-go/sdk/data/azcosmos@v1.0.1/cosmos_container.go:350 +0x351
...

The actual race seems to be on a counter of sorts, I'm not sure if this is new and should be fixed, of if it's intended that it's not supported to make concurrent requests to ReadItem? The latter would be a bit of a bummer, we have a lot of requests coming in to the database layer and having to create a client for each of them seems inefficient.

@simorenoh @ealsur - any ideas?

Interesting. This would indicate that the policy's instance is not tied to the request, but shared, which then means that the retry state:
https://github.com/Azure/azure-sdk-for-go/blob/c00d659e25b61d8cab9af614b2c598fe7b7b0734/sdk/data/azcosmos/cosmos_client_retry_policy.go#L178-L180
is wrong. And should be instead part of the request and extracted through req.OperationValue

One alternative is to incorporate the retry counters into pipelineRequestOptions:
type retryContext struct {
        useWriteEndpoint       bool
	retryCount             int
	sessionRetryCount      int
	preferredLocationIndex int
}

type pipelineRequestOptions struct {
	....
        retryContext retryContext
}

And then use that to track across the client retry policy execution.

@calmh We'll fix this. Working on a PR

We'll release the new package on 6/17

Sorry to bump the issue again, just want to say I'm super impressed with the rapid handling and communication here. Top notch, peeps. 🙏

@calmh Please confirm if your issue is resolved with 1.0.3

Yep, seems fine!


Error reading DWI data: "IndexError: list index out of range"

Hello,
Thank you for your work!
I'm trying to use bruker2nifti to convert DWI data, but I get the following error:
Traceback (most recent call last):
  File "//anaconda/bin/bruker2nifti", line 11, in <module>
    sys.exit(main())
  File "//anaconda/lib/python2.7/site-packages/bruker2nifti/parsers/bruker2nii.py", line 91, in main
    study_name=args.study_name)
  File "//anaconda/lib/python2.7/site-packages/bruker2nifti/converter.py", line 58, in __init__
    self._get_scans_attributes()
  File "//anaconda/lib/python2.7/site-packages/bruker2nifti/converter.py", line 75, in _get_scans_attributes
    _study_name = get_subject_name(self.pfo_study_bruker_input).replace(' ', '_')
  File "//anaconda/lib/python2.7/site-packages/bruker2nifti/_getters.py", line 53, in get_subject_name
    visu_pars = bruker_read_files('visu_pars', pfo_study, sub_scan_num=list_scans[0])
IndexError: list index out of range

I installed bruker2nifti using pip, and his is the command line I used (it shows the structure of my bruker data directory):
$ bruker2nifti -i ~/Documents/ferret/data/raw-data/F01_Adult/dwi/10/ -o ~/Desktop/test/
/
    .DS_Store
    acqp
    AdjStatePerScan
    method
    pulseprogram
    spnam0
    spnam23
    spnam26
    uxnmr.par
pdata/
    .DS_Store
    1/
        .DS_Store
        2dseq
        d3proc
        id
        meta
        procs
        reco
        roi
        visu_pars
    2/
        2dseq
        d3proc
        id
        meta
        procs
        roi
        visu_pars

The data I would like to convert is inside /pdata/1/.
I looked into the code, and bruker2nifti looks at some point for orientation data in a variable called VisuParseOrientation, but in my visu_pars the only variable that seems to have an orientation matrix (repeated as many times as there are slices) is VisuCoreOrientation. Maybe that's the problem?
Thanks in advance!

Hi! Thanks for the feedback. I may have improved the output for these cases in the next release.
bruker2nifti  must have as input a Bruker study (the folder with the subfolder numbered from 1 to n). If you want to convert a single study try with bruker2nifti_scan.
Let me know if it works, as the issue you pointed out may be another issue!
Which ParaVisoin version are you using?

... And yes, there is a bug in the CLI anyway. A new version will be soon released. Please use the development version (see wiki to install) or use the GUI of the stable(?) release.
Sorry for the issues!

Thank you Sebastiano!
compiling the development version as indicated in the wiki did the job. Now, when I pass this command $ bruker2nifti -i ~/Documents/ferret/data/raw-data/F01_Adult/dwi/ -o ~/Desktop/test/ the conversion produces .nii.gz files for all my scans \o/
The result is, however, flipped in the superior-inferior axis. Is this related to the conversion or could it be an error during the scanning? Should I fiddle with the Head_supine/prone parameters?
Here's a screenshot of the result:

The small panes on the right show the sup/inf inversion.

Hi Roberto,
This is interesting!
It is not unusual to put the ex-vivo sample upside-down in the scanner, and there may be no way to know it from the parameter files. Of course only swapping sup/inf, will swap left/right, so this will need an inversion of the signs of the RL axis.
Try to play with the Head_supine/prone, changing the default frame_body_as_frame_head in _utils.compute_affine_from_visu_pars, while keeping keep_same_det to True and let me know if changing the default work.
If you can, please send me one image sample or the visu_pars privately, if not having restrictions. I will try, in the near future, to see what I can do to integrate your case.
In the meantime, for your data, there is post-processing workaround to solve the problem using fslorient from FSL.
Should be similar to
import os

cmd = ''' cp {0} {1};
                      fslorient -deleteorient {1};
                      fslswapdim {1} z y -x {1};
                      fslorient -setqformcode 1 {1};
                      fslreorient2std  {1}'''.format(pfi_in, pfi_out)
os.system(cmd)

where pfi = path to file, and where fsl must be installed in your computer.
You can check the fsl commands meaning online. fslswapdim return a warning if it swaps the sign determinant of the q-form.
In case you want to change it manually you can use ITK-snap tools ->reorient image

if i swap the mri data using fsl like that, should i also change the
bves/bvals?
On Tuesday, August 15, 2017, Sebastiano Ferraris<EMAIL_ADDRESS>wrote:

Hi Roberto,
This is interesting!
It is not unusual to put the ex-vivo sample upside-down in the scanner,
and there may be no way to know it from the parameter files. Of course only
swapping sup/inf, will swap left/right, so this will need an inversion of
the signs of the RL axis.
Try to play with the Head_supine/prone, changing the default
frame_body_as_frame_head in _utils.compute_affine_from_visu_pars, while
keeping keep_same_det to True and let me know if changing the default
work.
If you can, please send me one image sample or the visu_pars privately, if
not having restrictions. I will try, in the near future, to see what I can
do to integrate your case.
In the meantime, for your data, there is post-processing workaround to
solve the problem using fslorient from FSL.
Should be similar to
import os
cmd = ''' cp {0} {1};
fslorient -deleteorient {1};
fslswapdim {1} z y -x {1};
fslorient -setqformcode 1 {1};
fslreorient2std  {1}'''.format(pfi_in, pfi_out)
os.system(cmd)
where pfi = path to file, and where fsl must be installed in your computer.
You can check the fsl commands meaning online. fslswapdim return a warning
if it swaps the sign determinant of the q-form.
In case you want to change it manually you can use ITK-snap tools
->reorient image
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/SebastianoF/bruker2nifti/issues/25#issuecomment-322390367,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACNCTLIuBlE5zX5xV8ngX4TUxwOoiWMNks5sYT9PgaJpZM4O2jsa
.

Yes

you are right : )
i'll create another issue. thank you!


[Feature Request] Dropdown component

We really need this!!!!

Currently both Cloud One Common Frontend and Container Security Frontend are waiting on the availability of this component.
It is on their critical path to roll out the next UI release, please consider making this as a high priority feature request.
Thank you.

WIP by @austinhung81

@ultralabed @joyfulelement
Added in https://github.com/trendmicro-frontend/styled-ui/commit/ff5ab2edbc2f45f5dce68f8476893c1423083ea6
It's planned to be released in v0.4.0


UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe6 in position 116: invalid continuation byte

My feature name contains Chinese. It raise error below
viz = dtreeviz(classifier,
               df.drop(label, 1).fillna(-1),
               df[label],
               target_name=label,
               feature_names=df.drop(label, 1).columns,
               class_names=["good", "bad"],  # need class_names for classifier
              fancy=False
              )

---------------------------------------------------------------------------
UnicodeDecodeError                        Traceback (most recent call last)
~/anaconda3/lib/python3.7/site-packages/IPython/core/formatters.py in __call__(self, obj)
    343             method = get_real_method(obj, self.print_method)
    344             if method is not None:
--> 345                 return method()
    346             return None
    347         else:

~/anaconda3/lib/python3.7/site-packages/dtreeviz/trees.py in _repr_svg_(self)
     29
     30     def _repr_svg_(self):
---> 31         return self.svg()
     32
     33     def svg(self):

~/anaconda3/lib/python3.7/site-packages/dtreeviz/trees.py in svg(self)
     33     def svg(self):
     34         """Render tree as svg and return svg text."""
---> 35         svgfilename = self.save_svg()
     36         with open(svgfilename, encoding='UTF-8') as f:
     37             svg = f.read()

~/anaconda3/lib/python3.7/site-packages/dtreeviz/trees.py in save_svg(self)
     46         tmp = tempfile.gettempdir()
     47         svgfilename = os.path.join(tmp, f"DTreeViz_{os.getpid()}.svg")
---> 48         self.save(svgfilename)
     49         return svgfilename
     50

~/anaconda3/lib/python3.7/site-packages/dtreeviz/trees.py in save(self, filename)
     71         cmd = ["dot", f"-T{format}", "-o", filename, dotfilename]
     72         # print(' '.join(cmd))
---> 73         run(cmd, capture_output=True, check=True, quiet=False)
     74
     75         if filename.endswith(".svg"):

~/anaconda3/lib/python3.7/site-packages/graphviz/backend.py in run(cmd, input, capture_output, check, encoding, quiet, **kwargs)
    172
    173     if not quiet and err:
--> 174         _compat.stderr_write_bytes(err, flush=True)
    175
    176     if encoding is not None:

~/anaconda3/lib/python3.7/site-packages/graphviz/_compat.py in stderr_write_bytes(data, flush)
     60         """Encode data str and write to sys.stderr (flush if requested)."""
     61         encoding = sys.stderr.encoding or sys.getdefaultencoding()
---> 62         sys.stderr.write(data.decode(encoding))
     63         if flush:
     64             sys.stderr.flush()

UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe6 in position 116: invalid continuation byte
<dtreeviz.trees.DTreeViz at 0x7facb36a0190>

Interesting. it's not clear what the error is since it's graphviz trying to print an error message.  Can you try finding that .dot file in your temp dir and running dot -Tsvg -o foo.svg dotfilename from the command line?

Hi sir, it raise Error: dot: can't open dotfilename.  How can i find where is the .dot file.

I  update the dtreeviz via conda ~/anaconda3/bin/pip install dtreeviz. It solve my problem.

I find feature_names params raise the problem when there are some chinese in name.

Yes, so look in the temp dir for the dot file and test that.

It raise new error now

findfont: Font family ['Arial'] not found. Falling back to DejaVu Sans.

Warning: /tmp/DTreeViz_47064: syntax error in line 26 near '['

---------------------------------------------------------------------------
FileNotFoundError                         Traceback (most recent call last)
<ipython-input-9-c9356bc28f29> in <module>
      7 viz = get_tree_visualizing(train_x, train_y, features_columns, if_feature_num=False)
      8 # clf = model_training(train_x, train_y)
----> 9 viz.view()

~/anaconda3/lib/python3.7/site-packages/dtreeviz/trees.py in view(self)
     39
     40     def view(self):
---> 41         svgfilename = self.save_svg()
     42         view(svgfilename)
     43

~/anaconda3/lib/python3.7/site-packages/dtreeviz/trees.py in save_svg(self)
     46         tmp = tempfile.gettempdir()
     47         svgfilename = os.path.join(tmp, f"DTreeViz_{os.getpid()}.svg")
---> 48         self.save(svgfilename)
     49         return svgfilename
     50

~/anaconda3/lib/python3.7/site-packages/dtreeviz/trees.py in save(self, filename)
     75         if filename.endswith(".svg"):
     76             # now merge in referenced SVG images to make all-in-one file
---> 77             with open(filename, encoding='UTF-8') as f:
     78                 svg = f.read()
     79             svg = inline_svg_images(svg)

FileNotFoundError: [Errno 2] No such file or directory: '/tmp/DTreeViz_47064.svg'

I

Yes, so look in the temp dir for the dot file and test that.

Hello sir. How can i find what is the dot file path?

Well,Google will be your friend here.  have you tried "where is my temp dir"?  But you don't need to because the error messages telling you precisely where the file is:
FileNotFoundError: [Errno 2] No such file or directory: '/tmp/DTreeViz_47064.svg'

Does /tmp/ sound familiar?

I run dot -Tsvg -o foo.svg dotfilename in /tmp. It raise Error: dot: can't open dotfilename.

Try dot -Tsvg -o /tmp/foo.svg without dotfilename

Did it work from the commandline?


Sample app : Simplify Room + LiveData

Simplify Room + LiveData implementation on the sample app and add a "refresh" button to demionstrate and test LiveData at work when updating the DB

Btw that last check failure was not my fault 😉

Thank you so much @RobbWatershed


"Uncaught TypeError: f.state is not a function" for wordpress 4.7

Getting error after updating wordpress to 4.7. I have attached the log file. Please have a look.
Version used:
2.4.0-beta.1
Using theme_mods or options?
function theme_customize_controls_init() {
	set_theme_mod( 'icon_logo_title', get_bloginfo( 'name' ) );
	set_theme_mod( 'general_front_page', get_option( 'page_on_front' ) );
	set_theme_mod( 'general_posts_page', get_option( 'page_for_posts' ) );
}
add_action( 'customize_controls_init', 'theme_customize_controls_init' );

Attachment
localhost-1482500062170.log.zip

I just added your code in my functions.php file and didn't get any errors...
But why would you want to add that code in the first place?
Doesn't make any sense to me

Solved it temporarily.
Kirki::add_field( 'themename_kirki', array( 	'type'      => 'repeater', 	'settings'  => 'front_page_widget_module_widget', 	'label'     => __( 'Widget Area', 'themename' ), 	'section'   => 'site_front_page_widget_module', 	'priority'  => 100, 	'transport' => 'postMessage', 	'default'   => array(), 	'fields'    => array( 		'widget_name' => array( 			'type'    => 'text', 			'label'   => __( 'Widget Area Name', 'themename' ), 			'default' => '' 		), 		'widget_num' => array( 			'type'    => 'select', 			'label'   => __( 'Number of Widgets per Row', 'themename' ), 			'default' => '1', 			'choices' => array( 				'1' => '1', 				'2' => '2', 				'3' => '3', 				'4' => '4', 				'5' => '5', 				'6' => '6' 			) 		) 	) ) );
It worked on removing the transport variable. Was it because of type was set to repeater?

repeater controls are currently not compatible with postMessage.
I'm marking this as a feature request so we can do it in a future release.

@aristath Repeater with postMessage was working with older WordPress. Now, it produces the api.state is not a function error in customize-controls.js:56.

Currently the repeater control does not support postMessage due to some changes in WP Core.
I'm still trying to figure out a solution to this, but until then I'm pushing a commit that will force repeaters to use refresh. You can still use postMessage in your code if you want, and when we manage to fix this the restriction will be lifted internally.

Closing as duplicate of #1208


Use cookies to perform operations on behalf of the user

In order to set up the user entities, I associated a separate cookie for sending the id_token to the server.
I implemented a separate class for getting specific data associated with the user account (e.g. client id, payload).
The servlets and the DatastoreAccess.java file have been extended to include more functionality (e.g. getting only the groups joined by the user, joining a new group).

Testing and more error checking will be added afterwards.

About the user domain, we don't actually have to verify it in the code since we already included this restriction in the OAuth 2.0 consent screen. The user is able to use only Google accounts that have the domain google.com. If the domain is not google.com than the sign in is incomplete and the request is not sent to the server. Do you think we should also include it on the server side?

About the user domain, we don't actually have to verify it in the code since we already included this restriction in the OAuth 2.0 consent screen. The user is able to use only Google accounts that have the domain google.com. If the domain is not google.com than the sign in is incomplete and the request is not sent to the server. Do you think we should also include it on the server side?

I see, sounds good for now.


Missing

missing H MANWHA ( ReadManwha extension)

missing H MANWHA ( ReadManwha extension)

report this in tachiyomi repo, lol

I already enable nsfw.
what did you mean by report this in tachiyomi?

i dont the link.tachiyomi brng me here to ask some issue.

@zrix20 https://github.com/inorichi/tachiyomi-extensions
report the issue there.

They Fix problem so fast.
Many thanks. =)


epoll test_socketpair_read: explicitly check real and Miri behavior

@bors r+

:pushpin: Commit 9652607c2a6dde5b6eaac7aee11cccc5666d9f53 has been approved by RalfJung
It is now in the queue for this repository.

:hourglass: Testing commit 9652607c2a6dde5b6eaac7aee11cccc5666d9f53 with merge 1ff4796e7f8174d31e17417734daf242446cfca0...

:sunny: Test successful - checks-actions
Approved by: RalfJung
Pushing 1ff4796e7f8174d31e17417734daf242446cfca0 to master...


Add Language: English-Colombia (en-CO)

I have need to create country specific instances of languages and Colombia does not have an english refrence. ResxResourceManager does not recognize this language and will not integrate it for management across all resources.
Is this possible to add?

You can use any language supported by Windows, see e.g. https://msdn.microsoft.com/en-us/library/cc233982.aspx


[BUG] Azure Service Bus "Unable to cast object of type 'Microsoft.Azure.Amqp.Framing.Accepted'"

Library name and version
Azure.Messaging.ServiceBus 7.17.5
Describe the bug
I am experiencing the same issue as reported in #14836 - however that issue is locked, and so I am refiling this bug.
Stacktrace:
System.InvalidCastException: Unable to cast object of type 'Microsoft.Azure.Amqp.Framing.Accepted' to type 'Microsoft.Azure.Amqp.Transaction.Declared'.
   at Microsoft.Azure.Amqp.Transaction.Controller.DeclareAsync(CancellationToken cancellationToken)
   at Azure.Messaging.ServiceBus.Amqp.AmqpTransactionEnlistment.OnCreateAsync(TimeSpan timeout, CancellationToken cancellationToken)
   at Microsoft.Azure.Amqp.Singleton`1.GetOrCreateAsync(TimeSpan timeout, CancellationToken cancellationToken)
   at Microsoft.Azure.Amqp.Singleton`1.GetOrCreateAsync(TimeSpan timeout, CancellationToken cancellationToken)
   at Azure.Messaging.ServiceBus.Amqp.AmqpTransactionManager.EnlistAsync(Transaction transaction, AmqpConnectionScope connectionScope, TimeSpan timeout)
   at Azure.Messaging.ServiceBus.Amqp.AmqpSender.SendBatchInternalAsync(AmqpMessage batchMessage, TimeSpan timeout, CancellationToken cancellationToken)
   at Azure.Messaging.ServiceBus.Amqp.AmqpSender.SendBatchInternalAsync(AmqpMessage batchMessage, TimeSpan timeout, CancellationToken cancellationToken)
   at Azure.Messaging.ServiceBus.Amqp.AmqpSender.<>c.<<SendAsync>b__24_0>d.MoveNext()
--- End of stack trace from previous location ---

Expected behavior
App code appears to be correct and is not throwing exceptions, so the expectation is that the ServiceBus library not throw either.
Actual behavior
Exception is thrown and caught internally, but operations might not be succeeding.
Reproduction Steps
using (var transactionScope = new TransactionScope(TransactionScopeOption.RequiresNew, TransactionScopeAsyncFlowOption.Enabled))
{
	await receiver.SetSessionStateAsync(binaryData, cancellationToken);
	await serviceBusSender.SendMessageAsync(outMessage, cancellationToken); // THROWS HERE! Note: in and out have same session id
	await receiver.CompleteMessageAsync(inMessage, CancellationToken.None);
	transactionScope.Complete();
}

Environment
Azure Container App
Base Image: mcr.microsoft.com/dotnet/aspnet:8.0

We have enabled AzureEventSourceListener, which logs these at the same time as the exceptions:
Forwarding Azure Event: 92, TransactionDischargeException, Azure-Messaging-ServiceBus, transactionId(String)=222d15f3-cb67-441a-a38f-516870a395f6:388, amqpTransactionId(String)=, exception(String)=Azure.Messaging.ServiceBus.ServiceBusException: TransactionID is null or empty Reference:69c73c38-5818-447c-8fdb-ca9f94602a04, TrackingId:781780e6-d9ad-47a2-95ea-dab3b67105aa_G28, SystemTracker:gtm, Timestamp:2024-07-17T16:22:13 (GeneralError). For troubleshooting information, see https://aka.ms/azsdk/net/servicebus/exceptions/troubleshoot.

Forwarding Azure Event: 3, SendMessageException, Azure-Messaging-ServiceBus, identifier(String)={{{REDACTED}}}, exception(String)=System.InvalidCastException: Unable to cast object of type 'Microsoft.Azure.Amqp.Framing.Accepted' to type 'Microsoft.Azure.Amqp.Transaction.Declared'.
   at Microsoft.Azure.Amqp.Transaction.Controller.DeclareAsync(CancellationToken cancellationToken)
   at Azure.Messaging.ServiceBus.Amqp.AmqpTransactionEnlistment.OnCreateAsync(TimeSpan timeout, CancellationToken cancellationToken)
   at Microsoft.Azure.Amqp.Singleton`1.GetOrCreateAsync(TimeSpan timeout, CancellationToken cancellationToken)
   at Microsoft.Azure.Amqp.Singleton`1.GetOrCreateAsync(TimeSpan timeout, CancellationToken cancellationToken)
   at Azure.Messaging.ServiceBus.Amqp.AmqpTransactionManager.EnlistAsync(Transaction transaction, AmqpConnectionScope connectionScope, TimeSpan timeout)
   at Azure.Messaging.ServiceBus.Amqp.AmqpSender.SendBatchInternalAsync(AmqpMessage batchMessage, TimeSpan timeout, CancellationToken cancellationToken)
   at Azure.Messaging.ServiceBus.Amqp.AmqpSender.SendBatchInternalAsync(AmqpMessage batchMessage, TimeSpan timeout, CancellationToken cancellationToken)
   at Azure.Messaging.ServiceBus.Amqp.AmqpSender.<>c.<<SendAsync>b__24_0>d.MoveNext()

Forwarding Azure Event: 89, TransactionInitializeException, Azure-Messaging-ServiceBus, transactionId(String)=222d15f3-cb67-441a-a38f-516870a395f6:388, exception(String)=System.InvalidCastException: Unable to cast object of type 'Microsoft.Azure.Amqp.Framing.Accepted' to type 'Microsoft.Azure.Amqp.Transaction.Declared'.
   at Microsoft.Azure.Amqp.Transaction.Controller.DeclareAsync(CancellationToken cancellationToken)
   at Azure.Messaging.ServiceBus.Amqp.AmqpTransactionEnlistment.OnCreateAsync(TimeSpan timeout, CancellationToken cancellationToken)

@JoeGaggler:  Thanks for reaching out and we regret that you're experiencing difficulties.  Looking over the previous issue and implementation, this appears to be something in the AMQP transport library that Service Bus uses as a dependency.   I've transferred this over to the repository where the Microsoft.Azure.Amqp library is maintained as #262 so that the folks best able to assist have visibility.


perltidy isn't installed when enabled

When using perltidy, it fails if it isn't installed on the host system.
This is problematic in CI:
Example:
https://github.com/docwhat/bashables/actions/runs/9483902974/job/26132129649
# .trunk/out/ppqBs.yaml
  trunk_cli_version: 1.22.1
  title: "Error while executing: tests/test_helper/pseudo-tty.pl"
  report:
    - message: Unable to find binary in PATH
      binary: perltidy
      PATH:
        - /home/runner/.local/share/bats/bin
        - /snap/bin
        - /home/runner/.local/bin
        - /opt/pipx_bin
        - /home/runner/.cargo/bin
        - /home/runner/.config/composer/vendor/bin
        - /usr/local/.ghcup/bin
        - /home/runner/.dotnet/tools
        - /usr/local/sbin
        - /usr/local/bin
        - /usr/sbin
        - /usr/bin
        - /sbin
        - /bin
        - /usr/games
        - /usr/local/games
        - /snap/bin
    - linter:
        command: |

        stdin_path: (none)
        run_from: ""
        timeout: 0
        rerun: ""
        exit_status: exited
        exit_code: 0
        stdout: (none)
        stderr: (none)
      parser: |
        (none)

The commit message for 097a7d3e305964d73e1205638430039e341e93d1 says this was done deliberately.
I can be convinced that we don't need to install a local perl runtime, but the command should be installed at the very least with a custom, trunk-specific PERL5LIB.

I think that this issue is causing the Merge "Check" in app.trunk.io to always fail.
In app.trunk.io I get an error every commit. For example, for docwhat/bashables commit c15f5c6 I get:
perltidy tests/test_helper/pseudo-tty.pl
trunk_cli_version: 1.22.1
title: "Error while executing: tests/test_helper/pseudo-tty.pl"
report:
  - message: Unable to find binary in PATH
    binary: perltidy
    PATH:
      - /snap/bin
      - /home/runner/.local/bin
      - /opt/pipx_bin
      - /home/runner/.cargo/bin
      - /home/runner/.config/composer/vendor/bin
      - /usr/local/.ghcup/bin
      - /home/runner/.dotnet/tools
      - /usr/local/sbin
      - /usr/local/bin
      - /usr/sbin
      - /usr/bin
      - /sbin
      - /bin
      - /usr/games
      - /usr/local/games
      - /snap/bin
  - linter:
      command: |

      stdin_path: (none)
      run_from: ""
      timeout: 0
      rerun: ""
      exit_status: exited
      exit_code: 0
      stdout: (none)
      stderr: (none)
    parser: |
      (none)

At the very least, the docker container or VM used to run Trunk Check should have perltidy and perlcritic pre-installed.

Hi @docwhat! Sorry you're running into this issue. I would expect the pre-installation that you added to work as intended. Can you add a debug step that runs which perltidy to identify the installation path? After that I can look into this a bit more.

Sorry for the confusion. Trunk is working find in GitHub Actions.
The problem I mentioned above is when looking at Failures under "Check" at app.trunk.io.
If you have access to my dashboard, which I give you permission to look at, the URL is https://app.trunk.io/docwhat-github/docwhat/bashables/check/failures?series=main.
I don't know how or where that is run, so I can't pre-install perltidy or perlcritic.

Ah, gotcha. I understand now. That is run as part of nightly check runs. You'll need to add a step to install the prereqs using .trunk/setup-ci/action.yaml in your bashables repo. Let me know if you have any issues getting that set up!

Okay, I made a change above. I'm not sure how to try it locally, so I guess I'll see if that fixes the issue tonight?

We don't have a user-friendly way to run that immediately, but you can follow these steps to test it:

Go to https://app.trunk.io/docwhat-github/docwhat/bashables/check/onboarding
Go through the couple steps to (re-)configure the nightly jobs
Go to the uploads tab, it may take a few minutes to propagate but you'll see the result of the run there, and you should also be able to navigate from there to the actual GH run in the .trunk repo

I just left it over night and I apparently got it right.
Here's the file if anyone else needs it: .trunk/setup-ci/action.yaml

Awesome. Thank you!


chore(subdomain-setup): add note to availability section

Summary

Adds a note about how you can add subdomains as parent zones, if the root domain is listed on the Public Suffix List.
Screenshots (optional)

Documentation checklist

[x] The documentation style guide has been adhered to.

Hi @wdhdev Thanks for raising this!
We actually already linked to PSL from "Add a site" pages here and here. I'll make sure to mention it as well within the DNS docs.


Profile creation: choosing profile to Copy from sometimes unchecks all checkboxes

Create profile
Choose Copy from, select one of the profiles you already have
All the checkboxes get unchecked and there is an error message 🐛

Fixed by 15af44e06f9a4de4dc7f3736001b380c386367d6


build: extract add_swift_library and rename to `add_swift_target_li…

…brary`
Split up the add_swift_library by extracting the tools host handling aspect of
it.  This has a much more limited option set.  Reducing the options further
would allow us to eliminate this and replace it with a wrapper around
add_llvm_library.  Leave the bulk of the logic in place in
add_swift_target_library which can now be simplified on its own.

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

CC: @Rostepher @gottesmm
Let's get the party started!

@gottesmm @llvm-beanz @Rostepher ... okay, this is about as thin of a wrapper over add_llvm_library as I can make due to the new use of gyb in the compiler itself.  Not sure if this is worth it or not, but the first commit definitely is IMO.

Awesome work so far! I'll give this a closer look in the morning.

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - 367c6abafa77458ceeae6c04bec900d5e7d527a4

Build failed
Swift Test OS X Platform
Git Sha - 367c6abafa77458ceeae6c04bec900d5e7d527a4

Build failed
Swift Test Linux Platform
Git Sha - 4179f1572e79e3f38b99ae3ccd02005310f2bff9

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - 4179f1572e79e3f38b99ae3ccd02005310f2bff9

Build failed
Swift Test Linux Platform
Git Sha - 4179f1572e79e3f38b99ae3ccd02005310f2bff9

@swift-ci please test Linux platform

Build failed
Swift Test Linux Platform
Git Sha - 8aed746309542f806cfcaf65392eb9d91e7a14c5

@swift-ci please test Linux platform

Build failed
Swift Test Linux Platform
Git Sha - 8aed746309542f806cfcaf65392eb9d91e7a14c5

19:36:01 failed to demangle witness for associated type 'Iterator' in conformance 'Swift.Array<Commands.ToolName.Type>: Sequence' from mangled name 's16IndexingIteratorVySayxGG'
The failure seems to be a demangling issue?  Not sure I understand how this is breaking (and only on Linux).

CC: @eeckstein
Perhaps Erik has some idea?

Maybe there is some missing build dependency and something didn't get rebuilt.
You can try with a clean build

@swift-ci please clean smoke test Linux platform

@swift-ci please clean test

Build failed
Swift Test Linux Platform
Git Sha - 8aed746309542f806cfcaf65392eb9d91e7a14c5

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - 2128fcb25278d8fbb7050ec179d1d1d1054bad74

Build failed
Swift Test OS X Platform
Git Sha - 8aed746309542f806cfcaf65392eb9d91e7a14c5

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - 9cc15cf4696495ea838a6cee7db78a6e63c5a84f

Build failed
Swift Test OS X Platform
Git Sha - 9cc15cf4696495ea838a6cee7db78a6e63c5a84f

The failure was due to a rebase failure on my part, sorry.

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - 0fdce4c358ad4b3eaa9a3db3c0e4ed9538075f38

Build failed
Swift Test Linux Platform
Git Sha - 0fdce4c358ad4b3eaa9a3db3c0e4ed9538075f38

@swift-ci please test macOS platform

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - 2eb47049c1eb2b9f37927d8d2b0b575b953c7d74

Build failed
Swift Test OS X Platform
Git Sha - 2eb47049c1eb2b9f37927d8d2b0b575b953c7d74

@swift-ci please test Linux platform

Now that _add_swift_library_single is unused, is it safe to just...delete it?


FCL: requests to access node use the protocol of the host page instead of configured value

Problem
If the FCL (using dev-wallet) is used on a host page running with https, then calls to the access node also use https, despite FCL being configured with http.
For example, dapper-web-services runs on localhost using https. It uses the FCL/dev-wallet and the FLOW emulator running locally to allow a user to pay for purchases using Flow tokens. FCL is configured as:
 fcl
    .config()
    .put('accessNode.api', 'http://localhost:8080')
    .put('challenge.handshake', 'http://localhost:8701/flow/authenticate');

When the user attempts to pay for something with their Flow tokens, we call FCL:
  const authorization = fcl.currentUser().authorization;

  const transaction = await fcl.serialize([
    fcl.payer(authorization),
    fcl.proposer(authorization),
    fcl.authorizations([authorization]),
    fcl.transaction`${cadenceTx}`,
  ]);

which pops open the dev-wallet iframe:

The iframe makes requests to the challenge.handshake url on http as expected by the configuration above.

However, when the user clicks "Use this profile", FCL will attempt to make a request to the accessNode.api on https, not http as specified in the configuration:

From what I've seen from tracing through the running code, the url //localhost:8080/access.AccessAPI/GetAccount is passed to fetch, and since the request is coming from the host app (ie. dapper-web-services running on https), it uses https as the scheme instead of http.
Steps to Reproduce
Try to use the dev wallet + flow emulator on an app that is using https instead of http.
Context
This is blocking a "Pay with Flow tokens" POC on dapper-web-services. The POC would allow a user to buy NBA Top Shot moments using Flow tokens when running the Dapper app locally.

Further investigation traced the issue to https://github.com/improbable-eng/grpc-web/blob/master/client/grpc-web-node-http-transport/src/index.ts#L56
this.options.url is correctly set to http://localhost:8080/access.AccessAPI/GetAccount. However, when the code above sets httpOptions, it does not set the protocol.  Line 66 is executed, calling http.request(httpOptions, ...).  The body of http.request looks like the snippet below. TLDR is that it will make the request without the protocol specified, so the browser will append https: since that is the current window protocol.
http.request = function (opts, cb) {
	if (typeof opts === 'string')
		opts = url.parse(opts)
	else
		opts = extend(opts)

	// Normally, the page is loaded from http or https, so not specifying a protocol
	// will result in a (valid) protocol-relative url. However, this won't work if
	// the protocol is something else, like 'file:'
	var defaultProtocol = global.location.protocol.search(/^https?:$/) === -1 ? 'http:' : ''

	var protocol = opts.protocol || defaultProtocol
	var host = opts.hostname || opts.host
	var port = opts.port
	var path = opts.path || '/'

	// Necessary for IPv6 addresses
	if (host && host.indexOf(':') !== -1)
		host = '[' + host + ']'

	// This may be a relative url. The browser should always be able to interpret it correctly.
	opts.url = (host ? (protocol + '//' + host) : '') + (port ? ':' + port : '') + path
	opts.method = (opts.method || 'GET').toUpperCase()
	opts.headers = opts.headers || {}

	// Also valid opts.auth, opts.mode

	var req = new ClientRequest(opts)
	if (cb)
		req.on('response', cb)
	return req
}

I'm going to open up an issue on the grpc-web repo

House keeping, tagging and closing in favour of: #321


[1]    8329 segmentation fault (core dumped)  python for password protected PDFs

In which version did you experience this? Was fixed in 2.0.0

I'm not sure. But after upgrading the error was gone :+1:


Minimum capacity pool size for Azure NetApp Files lowered to 2 TiB

Please update the minimum capacity pool size under "Required infrastructure", to 2 TiB as per recent change:
https://learn.microsoft.com/en-us/azure/azure-netapp-files/whats-new#february-2023

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

ID: 2e4d27a4-b7be-bfea-4dfa-f40f98b1f9b4
Version Independent ID: b0bf6bef-ad05-b5ac-eced-a820e94867bd
Content: Storage FSLogix profile container Azure Virtual Desktop - Azure
Content Source: articles/virtual-desktop/store-fslogix-profile.md
Service: virtual-desktop
GitHub Login: @Heidilohr
Microsoft Alias: helohr

@gvanteylingen
Thanks for your feedback! We will investigate and update as appropriate.

@gvanteylingen
Thanks for reporting this! We have created a PR for this issue and the changes should go live soon.