APK build Error

Duplicate Check

[X] I have searched the opened issues and there are no duplicates

Describe the bug
PS C:\Users\ajays\mos\Sagebridge\FLET\torrent-searching> flet build apk --verbose
[13:31:14] Flutter bootstrap directory: C:\Users\ajays\AppData\Local\Temp\flet_flutter_build_Lx9dHe3UTw
No additional Flutter dependencies!
[13:31:19] Created Flutter bootstrap project from gh:flet-dev/flet-build-template with ref 0.24.1 ✅
Copying C:\Users\ajays\mos\Sagebridge\FLET\torrent-searching\assets\icon.png to C:\Users\ajays\AppData\Local\Temp\flet_flutter_build_Lx9dHe3UTw\images
Customized app icons and splash images ✅
Run subprocess: ['C:\flutter\flutter\bin\dart.BAT', 'run', 'flutter_launcher_icons']
(   ●  ) Generating app icons (6.4s)
(   ●  ) Generating app icons ⏳...  (1.3s)
(    ● ) Generating app icons ⏳...  Got dependencies in C:\Users\ajays\AppData\Local\Temp\flet_flutter_build_Lx9dHe3UTw.
( ●    ) Generating app icons(10.9s)
Built flutter_launcher_icons:flutter_launcher_icons.
(    ● ) Generating app icons ⏳...    ════════════════════════════════════════════
FLUTTER LAUNCHER ICONS (v0.13.1)
════════════════════════════════════════════
(   ●  ) Generating app icons ⏳...  • Creating default icons Android
(●     ) Generating app icons ⏳...  • Overwriting the default Android launcher icon with a new icon
(    ● ) Generating app icons ⏳...  • Overwriting default iOS launcher icon with new icon
(     ●) Generating app icons ⏳...  Creating Icons for Web...
(    ● ) Generating app icons ⏳...  Creating Icons for Windows...
( ●    ) Generating app icons ⏳...  Creating Icons for MacOS...
(  ●   ) Generating app icons ⏳...
✓ Successfully generated launcher icons
[13:31:42] Generated app icons ✅
Run subprocess: ['C:\flutter\flutter\bin\dart.BAT', 'run', 'flutter_native_splash:create']
(●     ) Generating splash screens (3.4s)
Built flutter_native_splash:create.
(   ●  ) Generating splash screens ⏳...  [Android] Creating default splash images
(●     ) Generating splash screens ⏳... [Android] Creating dark mode splash images
(  ●   ) Generating splash screens ⏳...  [Android] Creating default android12splash images
(  ●   ) Generating splash screens ⏳...  [Android] Creating dark mode android12splash images
(   ●  ) Generating splash screens ⏳...  [Android] Updating launch background(s) with splash image path...
[Android]  - android/app/src/main/res/drawable/launch_background.xml
(    ● ) Generating splash screens ⏳...  [Android]  - android/app/src/main/res/drawable-night/launch_background.xml
[Android]  - android/app/src/main/res/drawable-v21/launch_background.xml
(   ●  ) Generating splash screens ⏳... [Android]  - android/app/src/main/res/drawable-night-v21/launch_background.xml
[Android] Updating styles...
[Android]  - android/app/src/main/res/values-v31/styles.xml
[Android] No android/app/src/main/res/values-v31/styles.xml found in your Android project
[Android] Creating android/app/src/main/res/values-v31/styles.xml and adding it to your Android project
[Android]  - android/app/src/main/res/values-night-v31/styles.xml
[Android] No android/app/src/main/res/values-night-v31/styles.xml found in your Android project
[Android] Creating android/app/src/main/res/values-night-v31/styles.xml and adding it to your Android project
[Android]  - android/app/src/main/res/values/styles.xml
(  ●   ) Generating splash screens ⏳... [Android]  - android/app/src/main/res/values-night/styles.xml
[iOS] Creating  images
( ●    ) Generating splash screens ⏳...  [iOS] Creating dark mode  images
(    ● ) Generating splash screens ⏳...  [iOS] Updating ios/Runner/Info.plist for status bar hidden/visible
(●     ) Generating splash screens ⏳... [Web] Creating images
(  ●   ) Generating splash screens ⏳...  [Web] Creating images
(     ●) Generating splash screens ⏳...  [Web] Creating background images
(  ●   ) Generating splash screens ⏳... [Web] Creating CSS
( ●    ) Generating splash screens ⏳...  [Web] Updating index.html
(●     ) Generating splash screens ⏳...
✅ Native splash complete.
Now go finish building something awesome! 💪 You rock! 🤘🤩
Like the package? Please give it a 👍 here: https://pub.dev/packages/flutter_native_splash
[13:31:53] Generated splash screens ✅
Run subprocess: ['C:\flutter\flutter\bin\dart.BAT', 'run', 'serious_python:main', 'package', 'C:\Users\ajays\mos\Sagebridge\FLET\torrent-searching',
'--mobile', '--platform', 'mobile', '--dep-mappings', 'flet=flet-embed', '--req-deps', 'flet-embed', '--exclude', 'build']
( ●    ) Packaging Python app ⏳...
Built serious_python:main.
(   ●  ) Packaging Python app ⏳...  Running package command
Creating asset directory: C:\Users\ajays\AppData\Local\Temp\flet_flutter_build_Lx9dHe3UTw\app
Copying Python app from C:\Users\ajays\mos\Sagebridge\FLET\torrent-searching to C:\Users\ajays\AppData\Local\Temp\serious_python_temp800c13c7
(  ●   ) Packaging Python app ⏳... Configured mobile platform with sitecustomize.py at C:\Users\ajays\AppData\Local\Temp\serious_python_sitecustomized3b4e387\sitecustomize.py
Installing dependencies [flet-embed==0.24., flet-embed==0.24., aiohttp, SpeechRecognition, appwrite, python-dotenv, logging] with pip command to C:\Users\ajays\AppData\Local\Temp\serious_python_temp800c13c7_pypackages_
Extracting Python distributive from C:\Users\ajays\AppData\Local\Temp\cpython-3.11.6+20231002-x86_64-pc-windows-msvc-shared-install_only.tar.gz to C:\Users\ajays\AppData\Local\Temp\hostpython3.11_ab9c6cff
( ●    ) Packaging Python app ⏳...  Compiling Python sources at C:\Users\ajays\AppData\Local\Temp\serious_python_temp800c13c7
[13:33:18] Deleting Flutter bootstrap directory C:\Users\ajays\AppData\Local\Temp\flet_flutter_build_Lx9dHe3UTw
Error building Flet app - see the log of failed command above.
Run subprocess: ['C:\flutter\flutter\bin\flutter.BAT', 'doctor']
[13:33:25] Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 3.24.4, on Microsoft Windows [Version 10.0.22631.4460], locale en-US)
[√] Windows Version (Installed version of Windows is version 10 or higher)
[√] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[√] Chrome - develop for the web
[√] Visual Studio - develop Windows apps (Visual Studio Build Tools 2019 16.11.41)
[√] Android Studio (version 2024.2)
[√] VS Code (version 1.95.2)
[√] Connected device (3 available)
[√] Network resources
       • No issues found!

PS C:\Users\ajays\mos\Sagebridge\FLET\torrent-searching> flutter doctor --verbose
[√] Flutter (Channel stable, 3.24.4, on Microsoft Windows [Version 10.0.22631.4460], locale en-US)
• Flutter version 3.24.4 on channel stable at C:\flutter\flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision 603104015d (3 weeks ago), 2024-10-24 08:01:25 -0700
• Engine revision db49896cf2
• Dart version 3.5.4
• DevTools version 2.37.3
[√] Windows Version (Installed version of Windows is version 10 or higher)
[√] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
• Android SDK at C:\Users\ajays\AppData\Local\Android\Sdk
• Platform android-34, build-tools 34.0.0
• ANDROID_HOME = C:\Users\ajays\AppData\Local\Android\Sdk
• Java binary at: C:\Program Files\Android\Android Studio\jbr\bin\java
• Java version OpenJDK Runtime Environment (build 21.0.3+-12282718-b509.11)
• All Android licenses accepted.
[√] Chrome - develop for the web
• Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe
[√] Visual Studio - develop Windows apps (Visual Studio Build Tools 2019 16.11.41)
• Visual Studio at C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools
• Visual Studio Build Tools 2019 version 16.11.35325.158
• Windows 10 SDK version 10.0.19041.0
[√] Android Studio (version 2024.2)
• Android Studio at C:\Program Files\Android\Android Studio
• 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 21.0.3+-12282718-b509.11)
[√] VS Code (version 1.95.2)
• VS Code at C:\Users\ajays\AppData\Local\Programs\Microsoft VS Code
• Flutter extension version 3.100.0
[√] Connected device (3 available)
• Windows (desktop) • windows • windows-x64    • Microsoft Windows [Version 10.0.22631.4460]
• Chrome (web)      • chrome  • web-javascript • Google Chrome 130.0.6723.117
• Edge (web)        • edge    • web-javascript • Microsoft Edge 130.0.2849.80
[√] Network resources
• All expected network resources are available.
• No issues found!
PS C:\Users\ajays\mos\Sagebridge\FLET\torrent-searching>
Code sample
Code
[Paste your code here]

To reproduce
PS C:\Users\ajays\mos\Sagebridge\FLET\torrent-searching> flet build apk --verbose
[13:31:14] Flutter bootstrap directory: C:\Users\ajays\AppData\Local\Temp\flet_flutter_build_Lx9dHe3UTw
No additional Flutter dependencies!
[13:31:19] Created Flutter bootstrap project from gh:flet-dev/flet-build-template with ref 0.24.1 ✅
Copying C:\Users\ajays\mos\Sagebridge\FLET\torrent-searching\assets\icon.png to C:\Users\ajays\AppData\Local\Temp\flet_flutter_build_Lx9dHe3UTw\images
Customized app icons and splash images ✅
Run subprocess: ['C:\flutter\flutter\bin\dart.BAT', 'run', 'flutter_launcher_icons']
(   ●  ) Generating app icons (6.4s)
(   ●  ) Generating app icons ⏳...  (1.3s)
(    ● ) Generating app icons ⏳...  Got dependencies in C:\Users\ajays\AppData\Local\Temp\flet_flutter_build_Lx9dHe3UTw.
( ●    ) Generating app icons(10.9s)
Built flutter_launcher_icons:flutter_launcher_icons.
(    ● ) Generating app icons ⏳...    ════════════════════════════════════════════
FLUTTER LAUNCHER ICONS (v0.13.1)
════════════════════════════════════════════
(   ●  ) Generating app icons ⏳...  • Creating default icons Android
(●     ) Generating app icons ⏳...  • Overwriting the default Android launcher icon with a new icon
(    ● ) Generating app icons ⏳...  • Overwriting default iOS launcher icon with new icon
(     ●) Generating app icons ⏳...  Creating Icons for Web...
(    ● ) Generating app icons ⏳...  Creating Icons for Windows...
( ●    ) Generating app icons ⏳...  Creating Icons for MacOS...
(  ●   ) Generating app icons ⏳...
✓ Successfully generated launcher icons
[13:31:42] Generated app icons ✅
Run subprocess: ['C:\flutter\flutter\bin\dart.BAT', 'run', 'flutter_native_splash:create']
(●     ) Generating splash screens (3.4s)
Built flutter_native_splash:create.
(   ●  ) Generating splash screens ⏳...  [Android] Creating default splash images
(●     ) Generating splash screens ⏳... [Android] Creating dark mode splash images
(  ●   ) Generating splash screens ⏳...  [Android] Creating default android12splash images
(  ●   ) Generating splash screens ⏳...  [Android] Creating dark mode android12splash images
(   ●  ) Generating splash screens ⏳...  [Android] Updating launch background(s) with splash image path...
[Android]  - android/app/src/main/res/drawable/launch_background.xml
(    ● ) Generating splash screens ⏳...  [Android]  - android/app/src/main/res/drawable-night/launch_background.xml
[Android]  - android/app/src/main/res/drawable-v21/launch_background.xml
(   ●  ) Generating splash screens ⏳... [Android]  - android/app/src/main/res/drawable-night-v21/launch_background.xml
[Android] Updating styles...
[Android]  - android/app/src/main/res/values-v31/styles.xml
[Android] No android/app/src/main/res/values-v31/styles.xml found in your Android project
[Android] Creating android/app/src/main/res/values-v31/styles.xml and adding it to your Android project
[Android]  - android/app/src/main/res/values-night-v31/styles.xml
[Android] No android/app/src/main/res/values-night-v31/styles.xml found in your Android project
[Android] Creating android/app/src/main/res/values-night-v31/styles.xml and adding it to your Android project
[Android]  - android/app/src/main/res/values/styles.xml
(  ●   ) Generating splash screens ⏳... [Android]  - android/app/src/main/res/values-night/styles.xml
[iOS] Creating  images
( ●    ) Generating splash screens ⏳...  [iOS] Creating dark mode  images
(    ● ) Generating splash screens ⏳...  [iOS] Updating ios/Runner/Info.plist for status bar hidden/visible
(●     ) Generating splash screens ⏳... [Web] Creating images
(  ●   ) Generating splash screens ⏳...  [Web] Creating images
(     ●) Generating splash screens ⏳...  [Web] Creating background images
(  ●   ) Generating splash screens ⏳... [Web] Creating CSS
( ●    ) Generating splash screens ⏳...  [Web] Updating index.html
(●     ) Generating splash screens ⏳...
✅ Native splash complete.
Now go finish building something awesome! 💪 You rock! 🤘🤩
Like the package? Please give it a 👍 here: https://pub.dev/packages/flutter_native_splash
[13:31:53] Generated splash screens ✅
Run subprocess: ['C:\flutter\flutter\bin\dart.BAT', 'run', 'serious_python:main', 'package', 'C:\Users\ajays\mos\Sagebridge\FLET\torrent-searching',
'--mobile', '--platform', 'mobile', '--dep-mappings', 'flet=flet-embed', '--req-deps', 'flet-embed', '--exclude', 'build']
( ●    ) Packaging Python app ⏳...
Built serious_python:main.
(   ●  ) Packaging Python app ⏳...  Running package command
Creating asset directory: C:\Users\ajays\AppData\Local\Temp\flet_flutter_build_Lx9dHe3UTw\app
Copying Python app from C:\Users\ajays\mos\Sagebridge\FLET\torrent-searching to C:\Users\ajays\AppData\Local\Temp\serious_python_temp800c13c7
(  ●   ) Packaging Python app ⏳... Configured mobile platform with sitecustomize.py at C:\Users\ajays\AppData\Local\Temp\serious_python_sitecustomized3b4e387\sitecustomize.py
Installing dependencies [flet-embed==0.24., flet-embed==0.24., aiohttp, SpeechRecognition, appwrite, python-dotenv, logging] with pip command to C:\Users\ajays\AppData\Local\Temp\serious_python_temp800c13c7_pypackages_
Extracting Python distributive from C:\Users\ajays\AppData\Local\Temp\cpython-3.11.6+20231002-x86_64-pc-windows-msvc-shared-install_only.tar.gz to C:\Users\ajays\AppData\Local\Temp\hostpython3.11_ab9c6cff
( ●    ) Packaging Python app ⏳...  Compiling Python sources at C:\Users\ajays\AppData\Local\Temp\serious_python_temp800c13c7
[13:33:18] Deleting Flutter bootstrap directory C:\Users\ajays\AppData\Local\Temp\flet_flutter_build_Lx9dHe3UTw
Error building Flet app - see the log of failed command above.
Run subprocess: ['C:\flutter\flutter\bin\flutter.BAT', 'doctor']
[13:33:25] Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 3.24.4, on Microsoft Windows [Version 10.0.22631.4460], locale en-US)
[√] Windows Version (Installed version of Windows is version 10 or higher)
[√] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[√] Chrome - develop for the web
[√] Visual Studio - develop Windows apps (Visual Studio Build Tools 2019 16.11.41)
[√] Android Studio (version 2024.2)
[√] VS Code (version 1.95.2)
[√] Connected device (3 available)
[√] Network resources
       • No issues found!

Expected behavior
No response
Screenshots / Videos

Captures
[Upload media here]

Operating System
Windows
Operating system details
11
Flet version
0.24.1
Regression
No, it isn't
Suggestions
No response
Logs
Logs
[Paste your logs here]

Additional details
No response

Can you please share your requirements file.

flet==0.24.*
aiohttp
SpeechRecognition
appwrite
python-dotenv
cryptography

Try setting Flet to the latest pre-release version: https://pypi.org/project/flet/#history


[Renderer] Radioactive Acid Glitches out in Opposing Force

The Acid of this room in Opposing Force ends up clipping through the walls. It appears to change depending on where I'm looking or standing so maybe it's an LOD thing. Here's the save file for it.
Glitched Acid Room.zip

That is probably because multiple water entities with different final height but same initial height, same texture and same rendermode are rendered in one batch, causing the unexpected glitch out in your save.

This should have been fixed in https://github.com/hzqst/MetaHookSv/releases/tag/v20230117b

Ooo yep looks like that fixed it! Thank you very much!


Assertion Failed on conditionally rendered panels with size constraints

Hi @bvaughn, first of all thank you for this amazing library. It has been a core feature for my project. In my project, I'm using resizable panels dynamically. As in, there are a set of layouts with size constraints defined in them as well. When I switch between layouts I get an assertion error. I've found out this is due to minSize and maxSize being supplied. Most probably I'm not using them as they should so I would love it if you could shine a light on this.
Here is a repro: https://codesandbox.io/p/sandbox/youthful-jennings-wt9ffk

Thanks for the repro. I will try to take a look sometime soon.

Okay found the problem, my outermost panel group had the same id despite the layout's change. Replacing it with unique ID or crypto.randomUUID() solved the problem. This didn't worked for the sandbox demo I've sent though.
Possibly a check for duplicate id's across re-render could be implemented?

That's interesting. Even with the same id, layouts should be stored uniquely based on the group id and the combination of panel constraints (so if you conditionally rendered panels, they don't clobber each others layouts).
Would you be able to reduce your repro to a failing unit test (in this repo)? That would help me fix it.

Let me try to do that. I'll try open a PR today

Thank you! That would be super helpful.

Solution was found in the PR

Fix published in 2.0.10


How can I match "/" exactly in route.path

I want a route matching  "/" exactly to serve the home page for my website , meanwhile I also want a fallback route as decribed here : https://docs.konghq.com/1.4.x/proxy/#configuring-a-fallback-route
In nginx, I could use location = / , however I can't do this in kong.
I have tried route.path=$/(?!.), but it said path  "should start with: / "
Thus , how can I match "/" exactly in route.path ?

how about: /$

how about: /$

It works. Thanks for your replay.


Beamer-inspired class for slides

Our styling stuff would be put to a nice usage (e.g. colored bullets, etc.) if used in a class for making slides
Steps would involve:

[ ] Specific page masters
[ ] Customized styles

I won't do it. I already have a good bunch of classes and packages to take care of, and SILE is what it is...


Extensible cannot build on stackage-nightly

Even though it only depends on freer-effects for benchmarks, the build system on stackage-nightly doesn't allow it to build until freer-effects is also released.

I was wrong, sorry.

This is still an issue but only for building the benchmarks.

Split off the benchmarks: https://github.com/fumieval/extensible-benchmarks


[Bug]: The error message is displayed under binding section when user switchs between the different environment

Is there an existing issue for this?

[X] I have searched the existing issues

Description
The error message is displayed under binding section when user switchs between the different environment

Steps To Reproduce

go to https://ee-2209.dp.appsmith.com/
login with admin cred
add few datasources
now add few custom envs
Now drag and drop a table and bing it with a data
now switch between the envs the error message is displayed in property pane under table data

Public Sample App
No response
Environment
Deploy Preview
Issue video log
No response
Version
v1.9.43

Tested and found to be fixed in latest dp


WinError 193 when trying to read parquet file from remote HDFS

I am trying to read a parquet file from a remote HDFS like this (in my case only a username but no password is needed):
import dask.dataframe as dd
path = 'hdfs://username@server:port/path-to-file'
df = dd.read_parquet(path, engine='pyarrow')

I'm getting this error:
Traceback (most recent call last):

  File "<ipython-input-40-dc6743263ce3>", line 1, in <module>
    df = dd.read_parquet(path, engine='pyarrow')

  File "C:\Users\My.Name\AppData\Local\Continuum\miniconda3\envs\main\lib\site-packages\dask\dataframe\io\parquet\core.py", line 214, in read_parquet
    fs, _, paths = get_fs_token_paths(path, mode="rb", storage_options=storage_options)

  File "C:\Users\My.Name\AppData\Local\Continuum\miniconda3\envs\main\lib\site-packages\fsspec\core.py", line 398, in get_fs_token_paths
    fs = cls(**options)

  File "C:\Users\My.Name\AppData\Local\Continuum\miniconda3\envs\main\lib\site-packages\fsspec\spec.py", line 52, in __call__
    obj = super().__call__(*args, **kwargs)

  File "C:\Users\My.Name\AppData\Local\Continuum\miniconda3\envs\main\lib\site-packages\fsspec\implementations\hdfs.py", line 50, in __init__
    extra_conf=extra_conf,

  File "C:\Users\My.Name\AppData\Local\Continuum\miniconda3\envs\main\lib\site-packages\pyarrow\hdfs.py", line 38, in __init__
    _maybe_set_hadoop_classpath()

  File "C:\Users\My.Name\AppData\Local\Continuum\miniconda3\envs\main\lib\site-packages\pyarrow\hdfs.py", line 138, in _maybe_set_hadoop_classpath
    classpath = _hadoop_classpath_glob(hadoop_bin)

  File "C:\Users\My.Name\AppData\Local\Continuum\miniconda3\envs\main\lib\site-packages\pyarrow\hdfs.py", line 165, in _hadoop_classpath_glob
    return subprocess.check_output(hadoop_classpath_args)

  File "C:\Users\My.Name\AppData\Local\Continuum\miniconda3\envs\main\lib\subprocess.py", line 411, in check_output
    **kwargs).stdout

  File "C:\Users\My.Name\AppData\Local\Continuum\miniconda3\envs\main\lib\subprocess.py", line 488, in run
    with Popen(*popenargs, **kwargs) as process:

  File "C:\Users\My.Name\AppData\Local\Continuum\miniconda3\envs\main\lib\site-packages\spyder_kernels\customize\spydercustomize.py", line 104, in __init__
    super(SubprocessPopen, self).__init__(*args, **kwargs)

  File "C:\Users\My.Name\AppData\Local\Continuum\miniconda3\envs\main\lib\subprocess.py", line 800, in __init__
    restore_signals, start_new_session)

  File "C:\Users\My.Name\AppData\Local\Continuum\miniconda3\envs\main\lib\subprocess.py", line 1207, in _execute_child
    startupinfo)

OSError: [WinError 193] %1 is not a valid Win32 application

This only happens when trying to read from remote HDFS, local files work fine.
Systeminfo:

Windows 10 64bit
Python 3.7.6
dask-core 2.10.1
fastparquet 0.3.3
pyarrow 0.16.0
snappy 1.1.8
pandas 1.0.1

Hi @Khris777 .  My apologies for the delayed response here.
My guess is that your Windows machine does not have access to HDFS.  Is this possible?
If so, then you probably need to wait for Arrow to make some changes upstream.  Please see https://issues.apache.org/jira/browse/ARROW-7486

Hi.
I can access HDFS just fine using python hdfs or pyhive.
Usually I'm reading the file in binary mode using hdfs and then feed the binary stream to parquet-python which reads it without issues.
Parquet-python is not readily available on conda though so I'm looking for an alternative.
Thanks for linking that Arrow issue, it's probably that.

I just tried fastparquet instead of pyarrow
df = dd.read_parquet(path, engine='fastparquet')

and it threw the exact same error.

I'm not sure how else to help on this issue, other than to point you upstream.  Are you good if we close?

Yes, that's okay, go ahead.


Compatibility Error with Terser (and the simple fix)

When compiling an angular app that uses terser for production use the following error occurs compiling ThreeBox code:
Error: main.1a5fcd07c173571f6663.js from Terser Unexpected token: name (static) [main.1a5fcd07c173571f6663.js:5215,28]     at js_error (C:\Users\Alex\Documents\Lapr5\SPA\node_modules\terser\dist\bundle.min.js:538:11)     at croak (C:\Users\Alex\Documents\Lapr5\SPA\node_modules\terser\dist\bundle.min.js:1251:9)     at token_error (C:\Users\Alex\Documents\Lapr5\SPA\node_modules\terser\dist\bundle.min.js:1259:9)     at unexpected (C:\Users\Alex\Documents\Lapr5\SPA\node_modules\terser\dist\bundle.min.js:1265:9)     at Object.add_parameter (C:\Users\Alex\Documents\Lapr5\SPA\node_modules\terser\dist\bundle.min.js:1736:33)     at binding_element (C:\Users\Alex\Documents\Lapr5\SPA\node_modules\terser\dist\bundle.min.js:1993:29)     at parameter (C:\Users\Alex\Documents\Lapr5\SPA\node_modules\terser\dist\bundle.min.js:1800:17)     at parameters (C:\Users\Alex\Documents\Lapr5\SPA\node_modules\terser\dist\bundle.min.js:1774:25)     at _function_body (C:\Users\Alex\Documents\Lapr5\SPA\node_modules\terser\dist\bundle.min.js:2047:19)     at function_ (C:\Users\Alex\Documents\Lapr5\SPA\node_modules\terser\dist\bundle.min.js:1698:20)
Although I do not know terser's behavior the error is simply resolved by changing the variable 'static' name to another (non-reserved token) name.
The referred variable is located in src/objects/objects.js in the addMethods function.

Just FYI, since a year ago I’m maintaining a new fork from Threebox  with many new features (that is also in production) such as the following:

Update to Three.js v117.
Update to Mapbox-gl-js v1.11.1.
18 examples with new features.
Support for multiple 3D format objects (FBX, GLTF/GLB, Collada, OBJ/MTL).
Support for CSS2D labels supporting rich HTML controls through a new LabelManager.
Support for CSS2D tooltips/title browser-like and mapbox-like.
Support for built-in shadows and real Sun light positioning for a given datetime and lnglat coords.
Support for built-in Raycaster in loaded Object3D and fill-extrusions together.
Support for built-in MouseOver/Mouseout, Selected, Drag&Drop, Drag&Rotate, Wireframe in loadedObjects including events.
Support for GeoJson standard features format import and export in different layers.
Support for Object3D embedded animations, and combined animations on AnimationManager (i.e. translate + embedded).
Support for multi-floor design of spaces.
Support for Non-AABB Non Axes Aligned Bounding Box and real model size.
Support for wireframing on Object3D, removing them from the raycast.
Support for setLayerZoomRange and setLayoutProperty on Custom Layers (not available in Mapbox).
Support for removeLayer considering Object3D.
Support for style change through setStyle and keeping Object3D.
Support for partial and full dispose of Mapbox, Three and Threebox resources and memory.
Support for Object3D auto-centering, bounding box and floor projection.
Optimization for loading thousands of objects through cache.
Optimization of Camera perspective to have Raycast with pixel-precision level.
Available as npm package


Extend IDL syntax to support service inheritance

Add syntax for inheritance in service definitions, e.g.:
service Foo
{
    Result foo(Param);
}

service Bar : Foo
{
    Result bar(Param);
}

In the AST a service base is represented as Maybe Type, the same way
as struct bases are represented. The parser validates that only a
concrete service or an instance of a generic service is used as a
base.

Done. Diff ignoring whitespaces for easier review.

We agreed previously to put support for this experimental syntax behind a switch that people have to explicitly opt into, in part because we don't have a full design yet for how service inheritance gets exposed in comm/gRPC. I realize that in practice someone is unlikely to get bitten by this but I think that we should stick with what the group decided as the best practice for this kind of experimental syntactic IDL extension.

Added --enable-service-inheritance switch to enable support for the new syntax. Support for codegen of services with inheritance is separately guarded by RPC codegen switches based on which templates support inheritance (initially neither gRPC nor Comm do).
E:\oss\bond\compiler (service-inheritance)
λ dist\build\gbc\gbc.exe c# tests\schema\service.bond
gbc.exe: user error (Use --enable-service-inheritance to enable service inheritance syntax.)

E:\oss\bond\compiler (service-inheritance)
λ dist\build\gbc\gbc.exe c# --comm tests\schema\service.bond
gbc.exe: user error (Use --enable-service-inheritance to enable service inheritance syntax.)

E:\oss\bond\compiler (service-inheritance)
λ dist\build\gbc\gbc.exe c# --enable-service-inheritance --comm tests\schema\service.bond
gbc.exe: user error (Service inheritance is not supported in Comm codegen.)

E:\oss\bond\compiler (service-inheritance)
λ dist\build\gbc\gbc.exe c# --enable-service-inheritance --grpc tests\schema\service.bond
gbc.exe: user error (Service inheritance is not supported in gRPC codegen.)

Chad, is there anything else you want me to change?


Is GHAS trial available only for enterprise accounts?

Code of Conduct

[x] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?
https://docs.github.com/en/enterprise-cloud@latest/billing/managing-billing-for-github-advanced-security/setting-up-a-trial-of-github-advanced-security
What part(s) of the article would you like to see updated?
This doc currently mentions "enterprise account" without disambiguation.
As a user who's a member of a GitHub Enterprise Cloud org, I think my user account is an enterprise account. And I think the GHEC org I'm a member of is also an enterprise account. And I'm aware that GitHub also offers a separate thing explicitly called an enterprise account.
An owner of a GHEC org may arrive at this page thinking their org is an enterprise account, and find that they can't follow the instructions. Their apparent options, at that point, will be to contact Sales, contact Support, or stop trying to buy GitHub Advanced Security.
If GHAS is available only for enterprise accounts, please make that clear in the docs and suggest how a user without an enterprise account should proceed.
Additional information
The problem I'm hoping to address is confusion resulting from ambiguous product name choices. This would affect any GHEC customer who wishes to try GHAS in their GHEC org and is unaware that their enterprise accounts are not enterprise accounts.

Thanks for the opening this issue, @solvaholic! I'll get this triaged for review ✨

Hi @solvaholic, docs team first responder here 👋
This looks like an improvement request. Please open an issue in the github/docs-content repo, using the 'improve existing docs' template, so we can plan and track the work. Thank you!


Terrain Classification through Transfer learning

hey @UppuluriKalyani
I am Darsh Agrawal , a fellow contributor and I  would like to contribute by using Transfer learning and create a model to help various agencies label captured terrain images like mountains, coast , desserts etc . By using transfer learning we can use pre trained models like RESNET or Efficientnet and hyperparameter tune them for terrain classification for better accuracy when compared to traditional CNN models.

it is already merged


Bug: Firmware Revision Characteristic Errors After Latest NodeJS Update

Describe the Bug
Everything seems to be working fine, I just got the following errors in the log
To Reproduce
Configure a bot with the latest version of node.
Expected Behavior
No error.
Relevant Log Output
19/09/2023, 23:47:08] [SwitchBot] Total SwitchBot Devices Found: 2
[19/09/2023, 23:47:08] [SwitchBot] Speaker: Soundbar this.platform.version, FirmwareRevision: 2.1.1
[19/09/2023, 23:47:08] [SwitchBot] Speaker: Soundbar setFirmwareRevision: 2.1.1
[19/09/2023, 23:47:08] [SwitchBot] Total IR Devices Found: 1
[19/09/2023, 23:47:08] [SwitchBot] Restoring existing accessory from cache: Coffee Maker DeviceID: XXX
[19/09/2023, 23:47:08] Soundbar EFF0 is running on port 37645.
[19/09/2023, 23:47:08] Please add [Soundbar EFF0] manually in Home app. Setup Code: 502-10-970
[19/09/2023, 23:47:08] [@switchbot/homebridge-switchbot] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service Battery. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.
[19/09/2023, 23:47:08] [@switchbot/homebridge-switchbot] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service Switch. Adding anyway.. See https://homebridge.io/w/JtMGR for more info.

Config for homebridge-switchbot
{
            "name": "SwitchBot",
            "credentials": {
                "token": "XXX",
                "secret": "XXX",
                "notice": "Keep your token a secret!"
            },
            "options": {
                "devices": [
                    {
                        "deviceId": "XXX",
                        "configDeviceType": "Bot",
                        "connectionType": "OpenAPI",
                        "bot": {
                            "mode": "switch",
                            "deviceType": "switch"
                        }
                    }
                ],
                "irdevices": [
                    {
                        "deviceId": "Soundbar",
                        "configRemoteType": "Speaker",
                        "connectionType": "OpenAPI",
                        "external": true
                    }
                ]
            },
            "_bridge": {
                "username": "0E:B1:4E:29:AD:AA",
                "port": 38561,
                "model": "SwitchBot"
            },
            "platform": "SwitchBot"
        }

Screenshots
No response
Device and Model
hub mini, bot
Node.js Version
v18.18.0
NPM Version
v10.1.0
Homebridge Version
v1.6.1
Homebridge Switchbot Plugin Version
v2.9.0
Homebridge Config UI X Plugin Version
v4.50.5
Operating System
Raspbian

Wouldn't worry about it.

I'm getting the same error and it's causing my Homebridge to go on a reboot loop. Won't start with it.
[25/09/2023, 12:31:08] [@switchbot/homebridge-switchbot] This plugin generated a warning from the characteristic 'Firmware Revision': Characteristic not in required or optional characteristic section for service Battery. Adding anyway.. See https://homebridge.io/w/JtMGR for more info. [25/09/2023, 12:31:08] TypeError: Cannot read properties of undefined (reading 'updateCharacteristic')     at Lock.updateHomeKitCharacteristics (/var/lib/homebridge/node_modules/@switchbot/homebridge-switchbot/src/device/lock.ts:554:36)     at Lock.openAPIRefreshStatus (/var/lib/homebridge/node_modules/@switchbot/homebridge-switchbot/src/device/lock.ts:360:14)     at processTicksAndRejections (node:internal/process/task_queues:95:5)     at Lock.refreshStatus (/var/lib/homebridge/node_modules/@switchbot/homebridge-switchbot/src/device/lock.ts:265:7)
I had to go back to 2.8.2.

Haven't had much time to look at this. When I do, I will let you know when I have a new beta out for testing.

I have the same problem as @GeorgeeNico but I had to downgrade to 2.8.1. I still get the warnings on 1.8.1 but no boot loop.

I have the same issue. Updated and stuck in restart loop. Downgraded to 2.8 and it works fine. I tried other combinations of updates too like downgrading Homebridge UI and Homebridge to other versions but it also broke Homebridge.
Just seems something in 2.9 breaks things. Will stay on 2.8 until a fix is implemented.

Can you all try the latest beta:

Click here to find out how to install Beta
And report back.

Works! Well done.

Works! Well done.

Awesome, I will get a release out soon.

v2.9.1 has been released


Failed to parse LUT

If I run the following example:
from wsidicom import WsiDicom, WsiDicomWebClient

url = 'https://idc-external-006.uc.r.appspot.com/dcm4chee-arc/aets/DCM4CHEE/rs'
study_uid = '2.16.7<IP_ADDRESS>6.20190905094928'
series_uid = '2.16.7<IP_ADDRESS>6.20190905094928.20190905102252'

client = WsiDicomWebClient.create_client(url)

slide = WsiDicom.open_web(client, study_uid, series_uid)

I get this error:
ERROR:root:Failed to parse LUT
Traceback (most recent call last):
  File "/home/patrick/virtualenvs/histomics/src/wsidicom/wsidicom/optical.py", line 106, in from_ds
    return cls(ds.PaletteColorLookupTableSequence)
  File "/home/patrick/virtualenvs/histomics/src/wsidicom/wsidicom/optical.py", line 62, in __init__
    self.table = self._parse_lut(self._lut_item)
  File "/home/patrick/virtualenvs/histomics/src/wsidicom/wsidicom/optical.py", line 156, in _parse_lut
    parsed_tables[color] = self._parse_color(table)
ValueError: could not broadcast input array from shape (65536,) into shape (0,)

That example is located here.

Thanks, I have also noticed that the LUT parsing fails on this example. I did wrap the parsing in a try-except block, setting the LUT to None if it failed to parsed. I have not yet had time to check if it is the LUT parser that is wrong (likely) or the LUT in the dataset.
I know that the LUT parser in the current release does not cover the standard properly. It will be replaced once I merge this branch.

I can no longer access the slim example. Do you have the lut sequences so that I can test them?

Unfortunately, I do not have them :slightly_frowning_face:. They are fixing the slim example, hopefully we'll be able to access it again soon.

Closing this for now. I think the LUT would have been parsed OK with the new parser, but I cant find the slide on IDC.


⚠ Bofrost.de has degraded performance

In b0cee51, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 2264 ms

Resolved: Bofrost.de performance has improved in 58ad77b after 44 minutes.


Firefox: add aarch64 widevine support

We recently pushed an update to widevine-cdm that enables support for aarch64. For chromium, the enableWideVine flag downloads the widevine-cdm package and enables it, therefore the changes for aarch64 widevine will work for chromium out of the box. Firefox however has a different approach to enabling widevine, when a user enables drm from withing FF, it download widevine from Google directly, but only x64 binaries, because Google only publishes those directly.
So what would the ideal system be to enable widevine on Firefox through the widevine-cdm package, that only thing in FF that needs to be done is MOZ_GMP_PATH needs to be set as well as a few preferences. Refer to this: https://gist.github.com/psanford/1f70a0838c308d28478cf27a9b55c43d?permalink_comment_id=5165332#gistcomment-5165332

@RossComputerGuy could you ping the firefox maintainers, I don't know how to.

CC @lovesegfault @mweinelt


Advanced Netherite compatibility

Advanced netherite materials being able to be used in the mod.

That looks interesting! Basic support for new materials are easy to add through extensions, but it looks like a big part of this mod is the accented netherite with other materials. Forgero deals very poorly with generating anything but a clean palette, so that might be a challenge.
This would make for an interesting addition to the palette system, by extending it to support material accents as well. It would be an interesting way to add more depth to existing materials as well, so it could be interesting to look into.

y e s

Done


Fix Action

Adds the dependencies required to build. Runs the action on all code changes instead of just on main

grr ffmpeg
Thanks :p


Set Volume is not implemented in Browser platform

I use this plugin for browser platform. When I try to set volume, after play function , I see in the  browser's log

I can confirm that this function here, setVolumeForComplexAsset, is not implemented in browser platform.
I tested with cordova 8.0.0, chrome/safari browser and ionic 3.20.0

I came here to confirm that it is not implemented.. that's pretty weird ..


InvokeMember fails in combination with enums backed by an ushort

This reproduces with the following sample project and .NET Framework 4.7:
using System;
using System.Reflection;

namespace TestProject
{
    class Program
    {
        static void Main(string[] args)
        {
            var result = typeof(Convert).InvokeMember("ToInt64", BindingFlags.IgnoreCase | BindingFlags.Static | BindingFlags.Public | BindingFlags.InvokeMethod, null, null, new object[] { SomeEnum.A });
            Console.WriteLine(result);
        }
    }

    enum SomeEnum : ushort
    {
        A = 0x01,
        B = 0x02
    }
}

As exception we get: System.Reflection.AmbiguousMatchException: 'Ambiguous match found.'
We have found a workaround by using:
var convertedEnum = Convert.ChangeType(SomeEnum.A, Enum.GetUnderlyingType(typeof(SomeEnum)));
var result = typeof(Convert).InvokeMember("ToInt64", BindingFlags.IgnoreCase | BindingFlags.Static | BindingFlags.Public | BindingFlags.InvokeMethod, null, null, new object[] { convertedEnum });

But it still looks like this may be an issue with the .NET Framework? It does work correctly when the enum is backed by any other underlying type than ushort.

Thanks for this report @fvanheeswijk. I believe this is by-design.
This is happening because the following two overloads on Convert are considered ambiguous
public static long ToInt64(ushort val) { ... }
public static long ToInt64(char val) { ... }

Those overloads are both applicable because you are passing in an enum member and there is a conversion from that enum to both char and ushort. In addition, the runtime cannot decide if char is better than ushort in that case because there are conversions between the two types.
The workaround you are using is how I would chose to address this issue as well.
I am going to close this for now. Feel free to reactivate!


Characters (encoding) not supported

Hi,
I encounter an issue on Windows with my differents tests, it's the same problem with all examples gotk3.
All characters are replaced by square, see this screenshot.
The strings are in Latin alphabet like "yes / no ...."

Do you have an idea to solve this problem ?
go1.9.2 windows/amd64
Windows 7
GTK 3.22.26
Thanks.

Problem resolved with the dependency libpangowin32-1.0-0.dll


Create a plugin Avalonia framework POC

Here is the link to the corresponding Issue https://github.com/morganstanley/ComposeUI/issues/60.
Please, note - there are not changes to src - all the changes only modify code and prototypes within Tryouts folder.
The main solution  to run for this POC is MorganStanley.ComposeUI.Prototypes.ThemeChangerPrototype.sln

None of the files seem to have the license header, please add them

None of the files seem to have the license header, please add them

Added license headers to all the relevant files.


[v2.7] Connection error with Android 13

Describe the bug
Hello, I am writing because we have BLE connection problems in some Android 13 devices. I want to emphasize that these problems are only occurring since the release of android version 13 and that only occur in some models of cell phones, in most models everything works correctly.
As you can see in the attached log, these mobiles only manage to connect once in two times (some of them fail to connect the first time, the second time works, the third doesn't work, etc.; and other devices connect the 1st, 3rd, ... and fail to connect the 2nd, 4th, ...). When they don't connect, they show the error bt_att: Invalid len 2 for code 0x0e continously until a disconnection is made.
We are working with nordic nrf52840 and zephyr 2.7.3 but it is not working either with 2.7.99 or 2.5.0 and we can not move to the last version for now.
I also added a sniffer trace when this occur.
Thank you
Expected behavior
The device connects through BLE.
Impact
Uncertainty about how many devices are affected.
Logs and console output

connection_error.pcapng (remove the leading .log)
Environment (please complete the following information):

Zephyr 2.7.3 (also 2.7.99 and 2.5.0)

@xeanhort could you please try to reproduce with the latest main branch?

Also @xeanhort, what platform/board are you running Zephyr on?

@carlescufi we sre using a custom board, with the nrf52840.
This board worked for a long time (~june) with several phones, but we are finding that lately some Android 13 are failing with this strange behaviour. In fact, we first detected the issue with a OnePlus 8T that was working for several months and, right after its update to Android 13, it started to fail (also with older FW versions it keet failing).
We have the test with the main branch scheduled, but it might take some time to migrate everything.

@xeanhort can you try disabling CONFIG_BT_GATT_READ_MULTIPLE? The failing opcode is BT_ATT_OP_READ_MULT_REQ which is a new feature (so it makes sense it starts failling only on recent android stack versions).

@jori-nordic We disabled this flag but it keeps failing. Nevertheless, now we are having different behavior.

The project configuration:

Now we are receiving different messages when the connection fails:

Phone 1 (Realme GT Neo2):

This phone keeps the same behavior: when it connects it shows the new log messages (Unhandled ATT), and the odd connection it works (like before).
Attached sniffer file with the new connection process:
connection_error_config_multiple_disabled.pcapng (remove the leading .log)

Phone 2 (OnePlus 8T):

This phone was working half of the times, but now it always fails (it never connects). The log messages are the same (Unhandled ATT).

Thank you

@Thalley any thoughts on this?

Hmm, the unhandled request is still BT_ATT_OP_READ_MULT_REQ. Weird that it continues to attempt to read using that, since we clearly respond with BT_ATT_ERR_NOT_SUPPORTED.
For the first issue, it is Android being incorrect, as it uses BT_ATT_OP_READ_MULT_REQ with a single handle (thus len = 2). The core spec clearly states that at least 2 handles shall be used:

This is clearly a bug in Android, and we should close it here


Allow user to disable script editor and use external editor instead

Fixes: #73702

The main question is what is the use case for disabling the script editor. There seems to be conflicted use cases:

Disabling all scripting functionality (e.g. for teachers who want to teach students with only nodes/inspector/animations/premade custom nodes but no scripting initially). That's what the current implementation was intended for.
Hiding the script editor because users want to use an external editor, and thus remove the internal editor from the interface. This is what this PR seems to allow, but breaks the above requirement.

While checking the PR and revising it according to your suggestions, I noticed that this PR has many hidden problems.

The current PR added FEATURE_EDITOR_SCRIPT that breaks compatibility.
If I move FEATURE_EDITOR_SCRIPT to the bottom, I will need to tweak many other places because the current implementation does not consider that a main feature could have many sub-main features.

I'll take more time to rethink how the problem could be solved elegantly. Because I have a full-time job to do, it will take a little longer to complete, at least not until 4.1 is released.

While reviewing the PR and making revisions based on your suggestions, I noticed several underlying issues with this PR. Should I relocate FEATURE_EDITOR_SCRIPT to the bottom, it would require adjustments in many other places, as the current implementation does not account for the possibility of a main feature having multiple sub-main features.
I will need more time to reconsider how to solve the problem in an elegant manner. Given my full-time job, it will take a little longer to complete, at the very least, not before the release of 4.1. My current idea is to solve the issue by utilizing an array or other suitable mechanisms. That's all I can think of.


TPDMDEV-195 - v1.0 Education Organization Updates

Changes look good now, @vimayya We'll need a ticket at some point to clean up the work done as part of https://tracker.ed-fi.org/browse/ODS-4018, since the ed org sub types that work was done for were removed as part of this PR.


Error sending message: AmqpProtocolError: com.microsoft:timeout:The operation did not complete within the allotted timeout of 00:01:00.

After 6 months with no problems using node-amqp10 (version 3.2.2) in production last Friday suddenly errors occurred when sending messages to ASB topics.
The problem is that the errors occur on sender level (on errorReceived ) and not on when calling send (rejected promise). My code:
...
let topicSender = amqpTopicClient.createSender(topicSend).then((sender) => {
    sender.on('errorReceived', function(tx_err) {
        if (tx_err.condition && (tx_err.condition == 'amqp:link:detach-forced')) {
            amqpTopicClient.disconnect().then(function () {
                sender = null;
                logger.info(`Disconnected due to timeout (${topicSend})`);
            });
        }
        else {
            logger.error(`${queueSend} ===> TX ERROR: `, tx_err);
        }
    });
    done(null, sender);
    return null;
});

and sending the messages with:
topicSender.send(message).then(function(state) {
    // this can be used to optionally track the disposition of the sent message
    logger.info(`Message ${message.properties.messageId} sent.`);
    logger.info(`result ` + util.inspect(state));
})
.error(function(error) {
    logger.error('send error: ', error);
});

The .error (promise rejection) is never called and my problem is that in the 'errorReceived' event I do not have info about the message that failed.  Restarting the app solved the problem at first, but right now another queue/topic starts throwing the same error (with the same trackingId).
Any idea what the best way is to handle this problem?

@gjr-qm Hi, can you confirm that your SenderLink callback policy (policy.callback) is 'sent(orSenderCallbackPolicies.OnSent`)?  As you can see here, if that is the case then the sent message will resolve as soon as we send the message, rather than waiting for disposition (or errors) to occur.

We're creating the AMQPClient like this:
new AMQPClient(Policy.ServiceBusTopic)

I didn't check before, but the default of policy.callback is OnSettle if I'm correct? I do think that is the case because the promise (.then) is never resolved. My hope was that the timeout would result in a rejection of the promise, so we could handle it in the .error part of the code.

@gjr-qm hm yes, it should indeed reject if it receives that error. I wonder if you're receiving disposition and then receiving an error? Could you potentially post some logs for a reproduction of this case? I'll look into seeing if there's a bug on our side.

@gjr-qm in particular it would be incredibly helpful to see if you are in fact getting a disposition before the error occurs.

I will dive into the logs. At the moment our queues are running fine again and of course, we don't run with full debug logs during normal operation. But I think I can reconstruct the important parts from the normal logs. As far as I can see we were not getting any disposition on the faulty queue. Looks like the timeout error on the queue is the only thing we're getting.
Back to the logs...

I've been going through a lot of log files and didn't find any send promise rejected. So I think the conclusion is that de client emits an errorReceived but no disposition (or send error) occurs.

Maybe a stack trace helps?
AmqpProtocolError: com.microsoft:timeout:The operation did not complete within the allotted timeout of 00:01:00. The time allotted to this operation may have been a portion of a longer timeout. For more information on exception types and proper exception handling, please refer to http://go.microsoft.com/fwlink/?LinkId=761101 TrackingId:8b93a7aeeccf45c7b8ec1077f7bb2ed8_G58, SystemTracker:gateway6, Timestamp:2/27/2017 8:42:18 AM
    at Object.utilities.wrapProtocolError (/bundle/bundle/programs/server/npm/npm-container/node_modules/amqp10/lib/utilities.js:273:12)
    at SenderLink.Link._detached (/bundle/bundle/programs/server/npm/npm-container/node_modules/amqp10/lib/link.js:207:37)
    at SenderLink._detached (/bundle/bundle/programs/server/npm/npm-container/node_modules/amqp10/lib/sender_link.js:210:41)
    at SenderLink.Link._detachReceived (/bundle/bundle/programs/server/npm/npm-container/node_modules/amqp10/lib/link.js:192:8)
    at Session._processDetachFrame (/bundle/bundle/programs/server/npm/npm-container/node_modules/amqp10/lib/session.js:337:45)
    at Session._processFrame (/bundle/bundle/programs/server/npm/npm-container/node_modules/amqp10/lib/session.js:304:61)
    at Connection._processFrameEH (/bundle/bundle/programs/server/npm/npm-container/node_modules/amqp10/lib/session.js:186:49)
    at Connection.emit (events.js:117:20)
    at Connection._receiveAny (/bundle/bundle/programs/server/npm/npm-container/node_modules/amqp10/lib/connection.js:431:16)
    at Connection._receiveData (/bundle/bundle/programs/server/npm/npm-container/node_modules/amqp10/lib/connection.js:362:8)
    at [object Object].<anonymous> (/bundle/bundle/programs/server/npm/npm-container/node_modules/amqp10/lib/connection.js:521:10)
    at [object Object].emit (events.js:95:17)
    at CleartextStream.<anonymous> (/bundle/bundle/programs/server/npm/npm-container/node_modules/amqp10/lib/transport/tls_transport.js:28:48)
    at CleartextStream.emit (events.js:95:17)
    at CleartextStream.<anonymous> (_stream_readable.js:765:14)
    at CleartextStream.emit (events.js:92:17)

This morning the error appeared again. I restarted the system with DEBUG=amqp10:se* to get sender and session debug info. Is that ok, or should I choose a different debug target? I was afraid a full debug (amqp*) would be an overkill for this problem...

@gjr-qm I usually do a full amqp*, if you feel like that's too much info you might do session*/sender*/link*

Our system is running with the new debug config now. No errors so far...
Now let's hope the error surfaces again soon because I prefer a fix rather than concluding (again) that this was another Azure/MS hickup.
I'll close this one for now and will reopen it when the error pops up again.
@mbroadst: thanks again for your help/support!

Last week (and tonight) the error occurred again...
I had to clean up the logs, because we have quite a few topics and queues and there was only one that went wrong.
Here are the important parts of the log:
last correct send
Thu, 02 Mar 2017 10:48:56 GMT amqp10:session Transitioning from UNMAPPED to BEGIN_SENT due to sendBegin
Thu, 02 Mar 2017 10:48:56 GMT amqp10:session processing frame:  @begin(17) [remoteChannel=1 nextOutgoingId=1 incomingWindow=5000 outgoingWindow=100 handleMax=255 offeredCapabilities=null desiredCapabilities=null properties={}]
Thu, 02 Mar 2017 10:48:56 GMT amqp10:session Transitioning from BEGIN_SENT to MAPPED due to beginReceived
Thu, 02 Mar 2017 10:48:56 GMT amqp10:session On BEGIN_RCVD, setting params to (1,5000,100,255)
Thu, 02 Mar 2017 10:48:56 GMT amqp10:link undefined:0: Transitioning from DETACHED to ATTACHING due to sendAttach
Thu, 02 Mar 2017 10:48:56 GMT amqp10:link attach CH=1, Handle=0
Thu, 02 Mar 2017 10:48:56 GMT amqp10:session processing frame:  @attach(18) [name='faulty.topic.write_xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx' handle=0 role=true sndSettleMode=2 rcvSettleMode=0 source=@source(40) [address='localhost' durable=0 expiryPolicy='session-end' timeout=0 dynamic=false dynamicNodeProperties={} distributionMode=null filter={} defaultOutcome=null outcomes=null capabilities=null] target=@target(41) [address='faulty.topic.write' durable=0 expiryPolicy='session-end' timeout=0 dynamic=false dynamicNodeProperties={} capabilities=null] unsettled=null incompleteUnsettled=null initialDeliveryCount=null maxMessageSize=10000 offeredCapabilities=null desiredCapabilities=null properties={}]
Thu, 02 Mar 2017 10:48:56 GMT amqp10:link faulty.topic.write_xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx:0: Transitioning from ATTACHING to ATTACHED due to attachReceived
Thu, 02 Mar 2017 10:48:56 GMT amqp10:link faulty.topic.write_xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx: attached CH=[1=>0], Handle=[0=>0]
Thu, 02 Mar 2017 10:48:56 GMT amqp10:link:sender canSend(0,5000) = false
Thu, 02 Mar 2017 10:48:56 GMT amqp10:session processing frame:  @flow(19) [nextIncomingId=1 incomingWindow=5000 nextOutgoingId=1 outgoingWindow=100 handle=0 deliveryCount=0 linkCredit=1000 available=0 drain=null echo=false properties=null]
Thu, 02 Mar 2017 10:48:56 GMT amqp10:session New Incoming Window (known id): 5000 = 1 + 5000 - 1
Thu, 02 Mar 2017 10:48:56 GMT amqp10:link:sender setting credits (1000,5000)
Thu, 02 Mar 2017 10:48:56 GMT amqp10:link:sender canSend(1000,5000) = true
Thu, 02 Mar 2017 10:48:56 GMT amqp10:link:sender sending:  { applicationProperties:
   { MessageTime: '10:48:56' },
  properties:
   { messageId: '13f2bc041463417da10a45a3bca9cf4f',
     contentType: 'text/xml' },
  body: <Buffer ...> }
Thu, 02 Mar 2017 10:48:56 GMT amqp10:session processing frame:  @disposition(21) [role=true first=1 last=null settled=true state=@accepted(36) [] batchable=null]

timeout
Thu, 02 Mar 2017 10:58:56 GMT amqp10:session processing frame:  @detach(22) [handle=0 closed=true error=@error(29) [condition='amqp:link:detach-forced' description='The link \'G35:7010626:faulty.topic.write_xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx\' is force detached by the broker due to errors occurred in publisher(link307686). Detach origin: AmqpMessagePublisher.IdleTimerExpired: Idle timeout: 00:10:00. TrackingId:23a8c62f000057e70004b1e658b7f898_G35_B2, SystemTracker:yyyyyyy:Topic:faulty.topic.write, Timestamp:3/2/2017 10:58:57 AM' info=null]]
Thu, 02 Mar 2017 10:58:56 GMT amqp10:link faulty.topic.write_xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx:0: Transitioning from ATTACHED to DETACHING due to detachReceived
Thu, 02 Mar 2017 10:58:56 GMT amqp10:link faulty.topic.write_xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx:0: Transitioning from DETACHING to DETACHED due to detached
Thu, 02 Mar 2017 10:58:56 GMT amqp10:session detached(faulty.topic.write_xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx): AmqpProtocolError: amqp:link:detach-forced:The link 'G35:7010626:faulty.topic.write_xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx' is force detached by the broker due to errors occurred in publisher(link307686). Detach origin: AmqpMessagePublisher.IdleTimerExpired: Idle timeout: 00:10:00. TrackingId:23a8c62f000057e70004b1e658b7f898_G35_B2, SystemTracker:yyyyyyy:Topic:faulty.topic.write, Timestamp:3/2/2017 10:58:57 AM
Thu, 02 Mar 2017 10:58:56 GMT amqp10:link faulty.topic.write_xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx:0: Transitioning from DETACHED to REATTACHING due to reattach
Thu, 02 Mar 2017 10:58:56 GMT amqp10:link Attempting to reattach faulty.topic.write_xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
Thu, 02 Mar 2017 10:58:56 GMT amqp10:link attach CH=1, Handle=0

here's where it goes wrong
Thu, 02 Mar 2017 11:07:06 GMT amqp10:session Transitioning from UNMAPPED to BEGIN_SENT due to sendBegin
Thu, 02 Mar 2017 11:07:06 GMT amqp10:session processing frame:  @begin(17) [remoteChannel=1 nextOutgoingId=1 incomingWindow=5000 outgoingWindow=100 handleMax=255 offeredCapabilities=null desiredCapabilities=null properties={}]
Thu, 02 Mar 2017 11:07:06 GMT amqp10:session Transitioning from BEGIN_SENT to MAPPED due to beginReceived
Thu, 02 Mar 2017 11:07:06 GMT amqp10:session On BEGIN_RCVD, setting params to (1,5000,100,255)
Thu, 02 Mar 2017 11:07:06 GMT amqp10:link undefined:0: Transitioning from DETACHED to ATTACHING due to sendAttach
Thu, 02 Mar 2017 11:07:06 GMT amqp10:link attach CH=1, Handle=0
Thu, 02 Mar 2017 11:07:35 GMT amqp10:session processing frame:  @transfer(20) [handle=0 deliveryId=575 deliveryTag=<Buffer 3f f2 cc 83 af a1 a3 49 b9 a9 79 4a d0 73 22 22> messageFormat=0 settled=null more=false rcvSettleMode=null state=null resume=null aborted=null batchable=true]
Thu, 02 Mar 2017 11:08:06 GMT amqp10:session processing frame:  @attach(18) [name='faulty.topic.write_b741de1a-e4b2-45fc-b7b0-e3193e0d2ae6' handle=0 role=true sndSettleMode=2 rcvSettleMode=0 source=null target=null unsettled=null incompleteUnsettled=null initialDeliveryCount=null maxMessageSize=10000 offeredCapabilities=null desiredCapabilities=null properties={}]
Thu, 02 Mar 2017 11:08:06 GMT amqp10:link faulty.topic.write_b741de1a-e4b2-45fc-b7b0-e3193e0d2ae6:0: Transitioning from ATTACHING to ATTACHED due to attachReceived
Thu, 02 Mar 2017 11:08:06 GMT amqp10:link faulty.topic.write_b741de1a-e4b2-45fc-b7b0-e3193e0d2ae6: attached CH=[1=>0], Handle=[0=>0]
Thu, 02 Mar 2017 11:08:06 GMT amqp10:link:sender canSend(0,5000) = false
Thu, 02 Mar 2017 11:08:06 GMT amqp10:session processing frame:  @detach(22) [handle=0 closed=true error=@error(29) [condition='com.microsoft:timeout' description='The operation did not complete within the allotted timeout of 00:01:00. The time allotted to this operation may have been a portion of a longer timeout. For more information on exception types and proper exception handling, please refer to http://go.microsoft.com/fwlink/?LinkId=761101 TrackingId:8b93a7aeeccf45c7b8ec1077f7bb2ed8_G58, SystemTracker:gateway6, Timestamp:3/2/2017 11:08:06 AM' info=null]]
Thu, 02 Mar 2017 11:08:06 GMT amqp10:link faulty.topic.write_b741de1a-e4b2-45fc-b7b0-e3193e0d2ae6:0: Transitioning from ATTACHED to DETACHING due to detachReceived
Thu, 02 Mar 2017 11:08:06 GMT amqp10:link faulty.topic.write_b741de1a-e4b2-45fc-b7b0-e3193e0d2ae6:0: Transitioning from DETACHING to DETACHED due to detached
Thu, 02 Mar 2017 11:08:06 GMT amqp10:session detached(faulty.topic.write_b741de1a-e4b2-45fc-b7b0-e3193e0d2ae6): AmqpProtocolError: com.microsoft:timeout:The operation did not complete within the allotted timeout of 00:01:00. The time allotted to this operation may have been a portion of a longer timeout. For more information on exception types and proper exception handling, please refer to http://go.microsoft.com/fwlink/?LinkId=761101 TrackingId:8b93a7aeeccf45c7b8ec1077f7bb2ed8_G58, SystemTracker:gateway6, Timestamp:3/2/2017 11:08:06 AM
Thu, 02 Mar 2017 11:08:06 GMT amqp10:link faulty.topic.write_b741de1a-e4b2-45fc-b7b0-e3193e0d2ae6:0: Transitioning from DETACHED to REATTACHING due to reattach
Thu, 02 Mar 2017 11:08:06 GMT amqp10:link Attempting to reattach faulty.topic.write_b741de1a-e4b2-45fc-b7b0-e3193e0d2ae6
Thu, 02 Mar 2017 11:08:06 GMT amqp10:link attach CH=1, Handle=0

After that, every minute the system tries to reattach @attach(18) again, but it never succeeds. Restarting the application solves the problem, attaching to the faulty topic is no problem.
What is the best way to handle this error? Because the send promise is never resolved or rejected and the error occurs on the link (and not in the send function).

As I said before, the strange thing is that the application ran without this problem for over 6 months. We didn't change anything and suddenly this error pops up. I think there must be something that has changed on the Azure side...

@gjr-qm there is definitely some change in the server. We're tracking a reattachment issue over on #295. You might want to try out using the case in the issue295 branch, as I have pushed some fixes there related to link reattachment.
As far as I can tell from the logs you've provided this looks very much like a problem on Microsoft's end. The exception being thrown is related to a remote operation failing to complete in the allotted time, and the link to their documentation indicates changes in e.g. OperationTimeout which would be a remotely configured parameter. I suggest reaching out to Microsoft to see if they have been seeing any similar error reports.
Regarding reattachment failing, what seems to be happening there is that you have no link credit:
Thu, 02 Mar 2017 11:08:06 GMT amqp10:link faulty.topic.write_b741de1a-e4b2-45fc-b7b0-e3193e0d2ae6:0: Transitioning from ATTACHING to ATTACHED due to attachReceived
Thu, 02 Mar 2017 11:08:06 GMT amqp10:link faulty.topic.write_b741de1a-e4b2-45fc-b7b0-e3193e0d2ae6: attached CH=[1=>0], Handle=[0=>0]
Thu, 02 Mar 2017 11:08:06 GMT amqp10:link:sender canSend(0,5000) = false

But its unclear how you got to that state. I believe you're at very least missing logs for amqp10:link:sender/amqp10:link:receiver, it might be better to initially try amqp*.

@mbroadst thanks for your response again!
I'll try amqp* for the logging. Btw, is it possible to get milliseconds in the log time stamp? Our log uses milliseconds because a lot can happen within a second these days...
This error is very frustrating because it happens at random times and we don't have an automated solution to handle it at the moment. We have to continuously keep an eye on the logs now in our production environment.
I think we try a temporary solution and disconnect the topic when the error occurs. Then reconnect and send the message again (after some time has elapsed?). Do you think this can work?
I hope so because every time I restart the application things seem to work again.
Of course, we have to register the message as pending, because the error occurs on the link and not in the send function itself. Or will node-amqp10 handle this with the internal pending messages?
Still strange that the promise there is never resolved or rejected. Could that be an omission in node-amqp10?

@gjr-qm I don't see an easy way in node-debug to enable millisecond logging unfortunately, but you could manually modify the code and console.log whatever you want.

This error is very frustrating because it happens at random times and we don't have an automated solution to handle it at the moment. We have to continuously keep an eye on the logs now in our production environment.

Yes I understand this very well, it's very difficult for me to debug without being able to reproduce the problem locally myself :)

I think we try a temporary solution and disconnect the topic when the error occurs. Then reconnect and send the message again (after some time has elapsed?). Do you think this can work?

Well this is basically what the driver does itself, it processes detachment of the link and then attempts reattachment. Somewhere in that process the credit is being screwed up, and subsequent operations are stalled until they are able to send again. Internally in node-amqp10 there already is a pendingSends array, which in your case is probably filling up with promises until there is enough credit to send messages (and this never happens, thus leading to a stall).
Having said that, when a link is detached currently all pendingSends/unconfirmedSends are rejected out of hand with a force:detach error - so that should be enough to keep things moving along.  It will be very crucial for you to figure out exactly why you are running out of credit in order to solve this problem.

Hmmm, didn't think of the credits being a possible source of the problem. And after looking through the code and logs, I still can't see that it could be.
I create the client like this: new AMQPClient(Policy.Utils.RenewOnSettle(1, 1, Policy.ServiceBusQueue)). In the application code, there is no reference to credits or credit. And the successful send log entries look like this:
amqp10:link:sender canSend(0,5000) = false
amqp10:session processing frame:  @flow(19) [nextIncomingId=1 incomingWindow=5000 nextOutgoingId=1 outgoingWindow=100 handle=0 deliveryCount=0 linkCredit=1000 available=0 drain=null echo=false properties=null]
amqp10:session New Incoming Window (known id): 5000 = 1 + 5000 - 1
amqp10:link:sender setting credits (1000,5000)
amqp10:link:sender canSend(1000,5000) = true

So every send (after attach) starts with 0 credits, but then 1000 credits are added. The difference between a successful send and one that is failing is that with the former a @flow(19) frame is processed while with the latter a @detach(22) follows the canSend(0,5000).

@gjr-qm if you take a look at the log section I pasted above (and what you referred to right at the end of your last comment here), the message is: canSend(0,5000). That message is generated here, and is essentially (<link-credit>, <incoming-window>) - so this means in that particular case you have no credit at all, and that looks suspiciously close to the failures cases in your above presented log.

@mbroadst, I was mistaken in my previous post about how we create the client. This is how we create it:
let amqpTopicClient = new AMQPClient(Policy.ServiceBusTopic);.
I just did some testing and I think you're wrong about the credits. Here's the full log for a succesful send:
Mon, 06 Mar 2017 22:09:23 GMT amqp10:client connecting to<EMAIL_ADDRESS>Mon, 06 Mar 2017 22:09:23 GMT amqp10:transport:tls Connecting to xxxx.servicebus.windows.net:5671 via TLS
Mon, 06 Mar 2017 22:09:23 GMT amqp10:connection Transitioning from DISCONNECTED to START due to connect
Mon, 06 Mar 2017 22:09:23 GMT amqp10:connection Sending Header 414d515003010000
Mon, 06 Mar 2017 22:09:23 GMT amqp10:connection Transitioning from START to IN_SASL due to connected
Mon, 06 Mar 2017 22:09:23 GMT amqp10:connection Rx: 414d515003010000
Mon, 06 Mar 2017 22:09:23 GMT amqp10:sasl Server SASL Version: 414d515003010000 vs 414d515003010000
Mon, 06 Mar 2017 22:09:23 GMT amqp10:connection Rx: 0000003f02010000005340c03201e02f04b3000000074d53534243425300000005504c41494e00000009414e4f4e594d4f55530000000845585445524e414c
Mon, 06 Mar 2017 22:09:23 GMT amqp10:sasl Sending asb-topic.send:xfWANSfRiWkCuLhzBYKQKsoPzVHWWXtNmca2oRAHqDc=
Mon, 06 Mar 2017 22:09:23 GMT amqp10:framing sending frame:  @sasl-init(65) [mechanism='PLAIN' initialResponse=<Buffer 00 68 72 6d 6c 2e 72 65 70 6f 72 74 2e 77 72 69 74 65 2e 73 65 6e 64 00 78 66 57 41 4e 53 66 52 69 57 6b 43 75 4c 68 7a 42 59 4b 51 4b 73 6f 50 7a 56 48 ...> hostname=null] : 0000005c02010000005341c04f03a305504c41494ea0440068726d6c2e7265706f72742e77726974652e73656e6400786657414e53665269576b43754c687a42594b514b736f507a5648575758744e6d6361326f5241487144633d40
Mon, 06 Mar 2017 22:09:23 GMT amqp10:connection Rx: 0000001a02010000005344c00d025000a00857656c636f6d6521
Mon, 06 Mar 2017 22:09:23 GMT amqp10:connection Sending Header 414d515000010000
Mon, 06 Mar 2017 22:09:23 GMT amqp10:connection Transitioning from IN_SASL to HDR_SENT due to success
Mon, 06 Mar 2017 22:09:23 GMT amqp10:connection Rx: 414d515000010000
Mon, 06 Mar 2017 22:09:23 GMT amqp10:connection Server AMQP Version: 414d515000010000 vs 414d515000010000
Mon, 06 Mar 2017 22:09:23 GMT amqp10:connection Transitioning from HDR_SENT to HDR_EXCH due to validVersion
Mon, 06 Mar 2017 22:09:23 GMT amqp10:framing sending frame:  @open(16) [containerId='conn1488838163364' hostname='xxxx.servicebus.windows.net' maxFrameSize=4294967295 channelMax=65535 idleTimeout=120000 outgoingLocales='en-US' incomingLocales='en-US' offeredCapabilities=null desiredCapabilities=null properties={}] :<PHONE_NUMBER>000000005310c0560aa111636f6e6e31343838383338313633333634a120676974702d617362612e736572766963656275732e77696e646f77732e6e657470ffffffff60ffff700001d4c0a305656e2d5553a305656e2d55534040c10100
Mon, 06 Mar 2017 22:09:23 GMT amqp10:connection Transitioning from HDR_EXCH to OPEN_SENT due to sendOpen
Mon, 06 Mar 2017 22:09:23 GMT amqp10:connection Rx:<PHONE_NUMBER>000000005310c03a0aa12435346532313734383238373134353037393161373563626666646538616530375f473539407000010000601387700003a9804040404040
Mon, 06 Mar 2017 22:09:23 GMT amqp10:connection Transitioning from OPEN_SENT to OPENED due to openReceived
Mon, 06 Mar 2017 22:09:23 GMT amqp10:connection Connected with params { maxFrameSize=65536, channelMax=4999, idleTimeout=120000 }
Mon, 06 Mar 2017 22:09:23 GMT amqp10:connection Setting heartbeat check timeout to 15000
Mon, 06 Mar 2017 22:09:23 GMT amqp10:client connected
Mon, 06 Mar 2017 22:09:23 GMT amqp10:session Transitioning from UNMAPPED to BEGIN_SENT due to sendBegin
Mon, 06 Mar 2017 22:09:23 GMT amqp10:framing sending frame:  @begin(17) [remoteChannel=null nextOutgoingId=1 incomingWindow=100 outgoingWindow=100 handleMax=4294967295 offeredCapabilities=null desiredCapabilities=null properties={}] : 0000001f02000001005311c012084052015264526470ffffffff4040c10100
Mon, 06 Mar 2017 22:09:23 GMT amqp10:connection Rx:<PHONE_NUMBER>000000005311c0140860000152017000001388526452ff4040c10100
Mon, 06 Mar 2017 22:09:23 GMT amqp10:session processing frame:  @begin(17) [remoteChannel=1 nextOutgoingId=1 incomingWindow=5000 outgoingWindow=100 handleMax=255 offeredCapabilities=null desiredCapabilities=null properties={}]
Mon, 06 Mar 2017 22:09:23 GMT amqp10:session Transitioning from BEGIN_SENT to MAPPED due to beginReceived
Mon, 06 Mar 2017 22:09:23 GMT amqp10:session On BEGIN_RCVD, setting params to (1,5000,100,255)
Mon, 06 Mar 2017 22:09:23 GMT amqp10:client mapped
Mon, 06 Mar 2017 22:09:23 GMT amqp10:link undefined:0: Transitioning from DETACHED to ATTACHING due to sendAttach
Mon, 06 Mar 2017 22:09:23 GMT amqp10:link attach CH=1, Handle=0
Mon, 06 Mar 2017 22:09:23 GMT amqp10:framing sending frame:  @attach(18) [name='asb-topic_cfd3faf7-9dd7-4b88-969c-1af1059f9c16' handle=0 role=false sndSettleMode=2 rcvSettleMode=0 source=@source(40) [address='localhost' durable=0 expiryPolicy='session-end' timeout=0 dynamic=false dynamicNodeProperties={} distributionMode=null filter={} defaultOutcome=null outcomes=null capabilities=null] target=@target(41) [address='asb-topic' durable=0 expiryPolicy='session-end' timeout=0 dynamic=false dynamicNodeProperties={} capabilities=null] unsettled={} incompleteUnsettled=false initialDeliveryCount=1 maxMessageSize=10000 offeredCapabilities=null desiredCapabilities=null properties={}] : 000000b802000001005312c0ab0ea13668726d6c2e7265706f72742e77726974655f63666433666166372d396464372d346238382d393639632d316166313035396639633136434250025000005328c0260ba1096c6f63616c686f737443a30b73657373696f6e2d656e644342c1010040c10100404040005329c02807a11168726d6c2e7265706f72742e777269746543a30b73657373696f6e2d656e644342c1010040c101004252018000000000000027104040c10100
Mon, 06 Mar 2017 22:09:23 GMT amqp10:connection Rx: 000000b502000000005312c0a80ea13668726d6c2e7265706f72742e77726974655f63666433666166372d396464372d346238382d393639632d316166313035396639633136434150025000005328c0260ba1096c6f63616c686f737443a30b73657373696f6e2d656e644342c1010040c10100404040005329c02807a11168726d6c2e7265706f72742e777269746543a30b73657373696f6e2d656e644342c10100404040408000000000000027104040c10100
Mon, 06 Mar 2017 22:09:23 GMT amqp10:session processing frame:  @attach(18) [name='asb-topic_cfd3faf7-9dd7-4b88-969c-1af1059f9c16' handle=0 role=true sndSettleMode=2 rcvSettleMode=0 source=@source(40) [address='localhost' durable=0 expiryPolicy='session-end' timeout=0 dynamic=false dynamicNodeProperties={} distributionMode=null filter={} defaultOutcome=null outcomes=null capabilities=null] target=@target(41) [address='asb-topic' durable=0 expiryPolicy='session-end' timeout=0 dynamic=false dynamicNodeProperties={} capabilities=null] unsettled=null incompleteUnsettled=null initialDeliveryCount=null maxMessageSize=10000 offeredCapabilities=null desiredCapabilities=null properties={}]
Mon, 06 Mar 2017 22:09:23 GMT amqp10:link asb-topic_cfd3faf7-9dd7-4b88-969c-1af1059f9c16:0: Transitioning from ATTACHING to ATTACHED due to attachReceived
Mon, 06 Mar 2017 22:09:23 GMT amqp10:link asb-topic_cfd3faf7-9dd7-4b88-969c-1af1059f9c16: attached CH=[1=>0], Handle=[0=>0]
Mon, 06 Mar 2017 22:09:23 GMT amqp10:link:sender canSend(0,5000) = false
Mon, 06 Mar 2017 22:09:23 GMT amqp10:session processing frame:  @flow(19) [nextIncomingId=1 incomingWindow=5000 nextOutgoingId=1 outgoingWindow=100 handle=0 deliveryCount=0 linkCredit=1000 available=0 drain=null echo=false properties=null]
Mon, 06 Mar 2017 22:09:23 GMT amqp10:session New Incoming Window (known id): 5000 = 1 + 5000 - 1
Mon, 06 Mar 2017 22:09:23 GMT amqp10:link:sender setting credits (1000,5000)
Mon, 06 Mar 2017 22:09:23 GMT amqp10:link:sender canSend(1000,5000) = true

As you can see there is always the sender canSend(0,5000) = false, followed by a @flow(19) that results in setting the credits to 1000. The log above is when we connect with the default (Policy.ServiceBusTopic) policy and then just send a message. No additional settings or whatsoever.
I agree with you that the error is caused by changes on the Azure side that were made about two weeks ago (before that we never had this problem).
Still looking for a (temporary) solution that takes care of handling this error. As said before right now we have to watch the logs all the time, restart the application and resend the messages that went wrong.
As far as Microsoft support goes: we don't have a support contract with Microsoft and my experiences are not so good. That's why i try to solve it this way first.

Oops, missed a few lines from the log. Here are the lines following the canSend(1000,5000) = true:
Mon, 06 Mar 2017 22:09:23 GMT amqp10:link:sender sending:  {
  applicationProperties: {
    MessageTime: '22:09:23'
  },
  properties: {
    messageId: '17ad1b2f280d4d218842e561ffef29f3',
    contentType: 'text/xml'
  },
  body: <Buffer blahblah ...>
}
Mon, 06 Mar 2017 22:09:23 GMT amqp10:framing sending frame:  @transfer(20) [handle=0 deliveryId=1 deliveryTag=<Buffer 31> messageFormat=0 settled=false more=false rcvSettleMode=0 state=null resume=false aborted=false batchable=false] : blahblah
Mon, 06 Mar 2017 22:09:23 GMT amqp10:connection Rx:<PHONE_NUMBER>000000005315c00b0641520140410053244540
Mon, 06 Mar 2017 22:09:23 GMT amqp10:session processing frame:  @disposition(21) [role=true first=1 last=null settled=true state=@accepted(36) [] batchable=null]

@gjr-qm Oh I see, sorry we were missing the other context in your previous logs. Yes you will get a canSend = false when you locally run out of credit - I thought you were getting that message after you completed the flow. My mistake.
I'm looking back on the issue here: can you confirm that you are getting an errorReceived every time this happens? Where are you getting that from? The connection or something else? That is very curious...

We're getting the error from the sender: sender.on('errorReceived', function(tx_err) {}

And yes when the topic goes 'faulty' the error persists. Every minute the sender attaches again, but the flow frame never gets in because of a timeout.

@gjr-qm Ah! Then I think this does look like a problem in our implementation. The spec tells us:
When an error occurs at a link endpoint, the endpoint MUST be detached with appropriate error information supplied in the error field of the detach frame. The link endpoint MUST then be destroyed. If any input (other than a detach) related to the endpoint either via the input handle or delivery-ids be received, the session MUST be terminated with an errant-link session-error. Since the link endpoint has been destroyed, the peer cannot reattach, and MUST resume the link in order to restore communication. In order to disambiguate the resume request from a pipelined re-attach the resuming attach performative MUST contain a non-null value for its unsettled field. Receipt of a pipelined attach MUST result in the session being terminated with an errant-link session-error.

So I actually think maybe the remote side is doing the right thing. It actually looks like when we receive these errors we need to close down the whole session, and reattempt a new connection to the server (or at least a new session).  I'll need some time to think about the implementation, but it shouldn't be too long.
Thanks for sticking with me here :)

Thank YOU for sticking with me! :)
I got really frustrated and was almost at the point of going back to a polling system. This is because our partners use Java and the standard Microsoft products (Navision) and couldn't do AMQP. And they don't have problems as far as I know.
Thanks again for the support you provide on node-amqp10!

@gjr-qm Is there any way you can provide me with the SB namespace name, and the topic name? I'm working through this issue presently with Microsoft. Perhaps you could email it to me, or DM me on the gitter channel?

@gjr-qm
Here was the response, looks like a bug on Microsoft's side:
"We have identified the bug in the service. For certain operations the timeout is not set appropriately, which could cause the operation to be stuck and subsequent calls to fail. The workaround is to create a new amqp connection that is likely handled by a different machine. If that does not work, the customer would need to contact the SB support to get the issue mitigated. The fix will be available in next deployment."

@mbroadst thanks! Now I wonder of course when the next deployment is scheduled (and we can get some sleep). Do you know MS schedule for this?

@gjr-qm sorry no, I think you'll have to speak to MS about that

Guess Microsoft fixed the bug since everything runs smooth again.
@mbroadst thanx again for your quick responses and help!


Add enableForeignLayersCaching option (for remote Docker repos)

The option "Enable Foreign Layers Caching" (enableForeignLayersCaching) for remote Docker repos is available in the UI, but missing from the Terraform provider.
Because many other type-specific options are also missing, I would suggest you add an option to directly provide a JSON for typeSpecific map that would be passed to the Artifactory API as-is (without validation). This way you will no longer have to maintain and keep type-specific options up-to-date with the Artifactory API.

You are right about repo specific features being unavailable. I am more in favor of implementing a docker repo correctly and can take this up right away.

You'll be happy to know this is moving up the priority list


Offer Mac OS key bindings option

MacOS can't use Ctrl with keybindings (e.g. Ctrl+Click). Offer a setting for MacOS which changes this to Command key. https://api.jquery.com/event.metakey/

Published in v9.5.0.


[GLUTEN-1245][VL][Feat]  Add VeloxParquetFileFormat to support parquet write in velox backend.

What changes were proposed in this pull request?

Add VeloxParquetFileFormat to offload Parquet write to native and use Velox parquet writer to write parquet file.
Remove Dwrf file format

How was this patch tested?
Add unit test

@jinchengchenghh @rui-mo Do you have any further comment?


Javascript / CSS: Album carousel doesn’t scroll left/right (sometimes)

This bug is intermittent and really hard to reproduce. If you use the four red navigation buttons when Django serves the tarot_key template, and the web visitor continuously reveals the album carousel and clicking-dragging left/right, eventually it will get stuck. Refreshing the page seems to resolve the issue until eventually the scroll left/right gets stuck again.
I figure the problem may  be somewhere in the Javascript at /tarot_juicer/static/js/carousel.js
It would be easiest  to see the problem I describe in action however I do not have a live public test case demonstrating the issue. For you to test and view the issue in my prod environment, I'll grant you access permissions which will happen after I hire you.

I just rigorously tested the carousel and I can't replicate this bug. It appears it's been resolved. Marking this Issue as closed.


systemd service for Betterlock fails with dbus-daemon errors

Is there an existing issue for this?

[X] I have searched the existing issues

Operating system
Arch linux: 6.0.2-arch1-1
Installation method
Package Manager (from OS)
Betterlockscreen & Dependency-Versions
Betterlockscreen: version: v4.0.4 (dunst: true, feh: true)
i3lock: version 2.13.c.4 © 2010 Michael Stapelberg, © 2015 Cassandra Fox, © 2021 Raymond Li
Version: ImageMagick 7.1.0-51 Q16-HDRI x86_64 20499 https://imagemagick.org
Copyright: (C) 1999 ImageMagick Studio LLC
License: https://imagemagick.org/script/license.php
Features: Cipher DPC HDRI Modules OpenCL OpenMP(4.5)
Delegates (built-in): bzlib cairo djvu fontconfig freetype heic jbig jng jp2 jpeg jxl lcms lqr ltdl lzma openexr pangocairo png raqm raw rsvg tiff webp wmf x xml zip zlib
Compiler: gcc (12.2)
dunst version: 1.9.0
feh version 3.9.1
Compile-time switches: curl exif inotify help magic stat64 verscmp xinerama
[B] Betterlockscreen

Bug description
When I try to enable the systemd service for Betterlockscreen:
systemctl enable betterlockscreen@$USER
The status of the service shows the following:
○<EMAIL_ADDRESS>- Lock screen when going to sleep/suspend
     Loaded: loaded<EMAIL_ADDRESS>enabled; preset: disabled)
     Active: inactive (dead)

Oct 20 11:48:47 machina systemd[1]: Starting Lock screen when going to sleep/suspend...
Oct 20 11:48:47 machina betterlockscreen[641]: Failed to open connection to "session" message bus: Using X11 for dbus-daemon autolaunch was disabled at compile time, set your DBUS_SESSION_BUS_ADDRESS instead
Oct 20 11:48:47 machina betterlockscreen[639]: Failed to communicate with dunst, is it running? Or maybe the version is outdated. You can try 'dunstctl debug' as a next debugging step.
Oct 20 11:48:47 machina betterlockscreen[627]: [B] Betterlockscreen
Oct 20 11:48:47 machina betterlockscreen[627]: [*] Running prelock...
Oct 20 11:48:47 machina betterlockscreen[627]: [*] Locking screen... (FAILSAFE MODE)
Oct 20 11:48:47 machina betterlockscreen[627]: [*] Running postlock...
Oct 20 11:48:48 machina systemd[1]<EMAIL_ADDRESS>Deactivated successfully.
Oct 20 11:48:48 machina systemd[1]: Started Lock screen when going to sleep/suspend.

I have checked, dunst is running and the DBUS_SESSION_BUS_ADDRESS is set as well.
Steps to reproduce

install betterlockscreen from aur
run systemctl enable betterlockscreen@$USER

Relevant log output
No response

What desktop or window-manager are you using?
Sounds like some kind of wrong / missing system-configuration or environment context for Betterlockscreen (https://bbs.archlinux.org/viewtopic.php?id=217281)
Also you are running into failsafe so you should run the update-command before and check your config.

@SebTM same here on bspwm. I did run -u with an image. betterlockscreen --lock works perfectly fine, show image and no dunst errors.
After I suspend, I am immediately shown lockscreen (without an image), then computer suspends. After unsuspending - no lockscreen.
Same 2 errors as op has.

This solution didn't help. Probably because lightdm Xsession wrapper already does that

Could you maybe retry it with the current state of the next branch?

I have the same issue, I tried the next branch and seem to get a different error now.
○<EMAIL_ADDRESS>- Lock screen when going to sleep/suspend
     Loaded: loaded<EMAIL_ADDRESS>enabled; preset: disabled)
     Active: inactive (dead)

Jan 20 11:23:53 sim-15p-arch betterlockscreen[370749]: Failed to open connection to "session" message bus: Using X11 for dbus-daemon autolaunch was disabled at compile time, set your DBUS_SESSION_BUS_ADDRESS instead
Jan 20 11:23:53 sim-15p-arch betterlockscreen[370747]: Failed to communicate with dunst, is it running? Or maybe the version is outdated. You can try 'dunstctl debug' as a next debugging step.
Jan 20 11:23:53 sim-15p-arch betterlockscreen[370735]: [B] Betterlockscreen
Jan 20 11:23:53 sim-15p-arch betterlockscreen[370735]: [*] Running prelock...
Jan 20 11:23:53 sim-15p-arch betterlockscreen[370735]: [*] Locking screen... (FAILSAFE MODE)
Jan 20 11:23:53 sim-15p-arch betterlockscreen[370751]: Authorization required, but no authorization protocol specified
Jan 20 11:23:53 sim-15p-arch betterlockscreen[370751]: i3lock: Could not connect to X11, maybe you need to set DISPLAY?
Jan 20 11:23:53 sim-15p-arch betterlockscreen[370735]: [*] Running postlock...
Jan 20 11:23:54 sim-15p-arch systemd[1]<EMAIL_ADDRESS>Deactivated successfully.
Jan 20 11:23:54 sim-15p-arch systemd[1]: Started Lock screen when going to sleep/suspend.

Betterlockscreen version:
v4.0.3.r44.g5cb876d-1
> betterlockscreen -v
Betterlockscreen: version: v4.0.4 (dunst: true, feh: true)
i3lock: version 2.13.c.4 © 2010 Michael Stapelberg, © 2015 Cassandra Fox, © 2021 Raymond Li
Version: ImageMagick 7.1.0-57 (Beta) Q16-HDRI x86_64 20701 https://imagemagick.org
Copyright: (C) 1999 ImageMagick Studio LLC
License: https://imagemagick.org/script/license.php
Features: Cipher DPC HDRI Modules OpenCL OpenMP(4.5)
Delegates (built-in): bzlib cairo djvu fontconfig freetype heic jbig jng jp2 jpeg jxl lcms lqr ltdl lzma openexr pangocairo png raqm raw rsvg tiff webp wmf x xml zip zlib
Compiler: gcc (12.2)
dunst version: 1.9.0
feh version 3.9.1
Compile-time switches: curl exif inotify help magic stat64 verscmp xinerama
[B] Betterlockscreen

the DISPLAY variable is correctly set to :0 and betterlockscreen -l locks the screen just fine.
I use startx + bspwm + dunst on arch linux (betterlockscreen-git modified to use the next branch), dunstctl commands work normally.

Hi! I have the same issue. Is there any update on it? Btw, worked perfectly on betterlockscreen AUR, but not with betterlockscreen/next


bug(MatAutocompleteTrigger): callback applied to closed EventEmitter runs outside of the Angular Zone on outside click

Is this a regression?

[ ] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
No response
Description
The callback applied to the closed EventEmitter seems to run outside of the Angular Zone when closed is emitted via "outside click"
Reproduction
https://stackblitz.com/edit/components-issue-83t6vu?file=src/app/autocomplete.component.ts
Steps to reproduce:

click inside input - should open panel and disable button
click outside panel to close it - expect button to be enabled, but remains disabled

Expected Behavior
clicking outside the panel to close the panel should have disabled the button
Actual Behavior
the button remains disabled
Environment

Angular: 13.3.0
CDK/Material: 13.3.0
Browser(s): Chrome
Operating System (e.g. Windows, macOS, Ubuntu): macOS

looks like the root cause comes from _subscribeToClosingActions() when the pipe switchMaps to this.panelClosingActions. since this.panelClosingActions is implemented as a getter, it gets evaluated when we're outside of Angular Zone (when firstStable emits).


apply the fix (SpotBugs)

Pull Request
Pull Request Checklist
Please follow the following steps before opening this PR.
PRs that do not complete the checklist will be subject to denial for
missing information.

[x] I have checked the pull request page for upcoming
or merged features/bug fixes.
[x] I have read JDA's contributing guidelines.

Pull Request Information
Check and fill in the blanks for all that apply:

[x] My PR fixes a bug, error, or other issues with the library's codebase.

Description

Set sourceCompatibility (and targetCompatibility) to Java 1.8
Remove unnecessary LinkedList (changed to ArrayList)

LinkedList.get: O(n), ArrayList.get: O(1)

Fix impossible downcast like this.userPermissions = (Permission[]) userPermissions.toArray();
Set inner classes to 'static'
SessionData: override hashCode() (https://stackoverflow.com/questions/2265503)

@Chew Could you review this pull request?


Setup multi-page react website

Initial thoughts on page structure:

/ Home (Brands the website itself, variation on Render except content is flat)
/edit Editor (form) See #9
/display Display (avoid 'render'). Pieces could be renamed from MainPage, after code layout is decided. To avoid nesting imports, all custom or form logic could be in one file.
/about About - keep this minimal maybe and link to repo or docs site.
/showcase Showcase - Collected designs.
/terms Terms of use. See #2

If content is mostly static, they should still be react pages for the menu.

See if the original example repo that uses react router has options
otherwise
https://reacttraining.com/react-router/web/example/basic
This is important for forms - use Link attribute and params to get to custom page from a form

Also see https://vegibit.com/create-a-navbar-component-in-react/

See Bulma hero tutorial (full screen section) for how to use navbars

Do you need help with this one?

Thanks @mundane140 yes that would be great
I haven't used React Router before but I think it's the direction to go, so you're welcome to set that up, even with placeholder content for each page covered in the first comment.
I've used Bulma so far so would like to keep using that for all the pages.
Regarding the structure - there's just one form page needed - don't worry about separate Editor vs Display pages. I now use &showForm=0 to make showing the form false, which hides the editor part of the form.
The showcase badge can be a list of URLs which point to the homepage form but with parameters.
e.g./showcase.html
# Showcase

## Own

Some of my favorite pages I've made:

- [fizz](/?title=fizz)

## Community

Instant webpage pages created by other people. If you want to add your own, fork the project, add a line and submit a PR!

- [foo](/?title=Foo) by Johnny
- [bar](/title=Bar) by Jane

Hey, I still need some context. I have completed the basic project setup procedure.
By a multi-page website do you mean you need something to replace the existing single page for 'instant website'?
I have added some stateless components as pages, a routes component as per react-router docs.
I'll open a draft PR with same changes.

Hi, thanks the basic structure looks good.
Oh I just remembered a thought from a while back regarding the homepage.
The homepage in the multi page view should be static - it will look like the current homepage but will be frozen on configured values e.g. "title: Instant Website". And then it will have a button saying "Make your own" which links to the "Edit" page which allows editing.
I need to add the button on the frontend but the use of showForm=0 means that no Display page is needed as the Edit page can become a Display view effectively by hiding the form inputs.

I could add a route which renders the edit/display component on the same page depending on a state variable.

When you want to display the page, the route will show the display component.
When you want the user to edit the page contents, the route will show the edit component.

Thanks. That's a great idea I like that layout and labelling
. I was thinking of having the form pop out the bottom as it currently does but having it switch between the edit and display views is nice and compact.
You can use the existing showForm variable which currently works but has no button. Rename the variable to showEditor if you prefer.
https://instant-website.netlify.app/?title=Test&showForm=1
https://instant-website.netlify.app/?title=Test&showForm=0
Also the edit/display part would be better in a separate PR to the existing multi-page PR, to make it easier to review.

Since this view will longer be on the homepage, it could be
#  Frozen home
/

# Custom page as edit and display modes
/custom?edit=1
/custom?edit=0

Unless you can think of something better than /custom that doesn't say edit or view since that will be param based

BTW I am curious how you discovered my site / repo? Or ideas about where it can get attention like on a blog post or featured on a list of react projects

I was just scourging through issues on GitHub. I have experience working with react and related tools so was looking for projects looking for some help with the same. Aa Nd here I am. 😅

Here's what I understood so far

I could do something like this

Routes
Home page

/
/home

Demo page

/demo (If we are using separate routes for demo and edit features)
/demo/0 or /view/0 or custom/0 (if we are using URL params for demo and edit features)

Edit page

/view
/demo/1 or /view/1 or custom/0

Thanks. I'll have a think and send something back as a full spec of drawings and routes.

Roger that.

@mundane140 Thanks for your patience. Here's a design of all the screens.

Resolved by #46 on develop


Add pragma directive

It is sometimes be necessary to include a non-inclusive term, for instance, because an external library uses it as a parameter name, or because it is in the name of a branch in another repo that I do not control the name of.
I would like to be able to flag such lines with an indication for blocklint that I know about them and don't want to be warned.
This is particularly relevent when using blocklint as part of a CI/CD pipeline where output from blocklint is treated as an error.
This PR adds a directive: "blocklint: pragma", that instructs blocklint to ignore any lint on a line containing that suffix.
Included are tests demonstrating how this can be used.

Thanks for the great work!


EthStorage Devs Meeting #43 Agenda

Meeting Info

Aug 8, 2023, 10:00 UTC+8
Duration: 60 minutes
Meeting link
Anyone can comment on the agenda where they would like this to be discussed.

Agenda

Protocol/App/Research progress
TBA

RPC: es-node merged
4844 devnet intergration

Test plan doc - in progress
Devnet node setup - in progress
Dockercompose - DL Todo

Miner

Fix/merge/split mining pull requests: in progress (reviewing: part 3)
ES-node command to create data file before start: to review

Migrate current dApp to 4844

Convert blob-utils into js version - testing

I will give a talk about EthStorage ESP grant report https://docs.google.com/presentation/d/1zxbSTlIwe8ylifeS9bK0lKDRl5ALJfCm8lKCGbB98H0/edit?usp=sharing

[ ] explore op fault proof code
[ ]  study Arbitrum's new challenge protocol
explore Arbitrum's fraud proof code, especially how to do WASM compilation - pending

plan to make a simple hostio demo written in golang and compile it into wasm, using go to call it

EthStorage -- sync

implementation: done

unit test (done)

performance test & integration test (ongoing, metrics pr will be send today)

galileo maintain

faucet issue (done)

explorer issue (ongoing)

EthStorage Protocol ZK proof generation: Nova step circuit: https://github.com/ethstorage/zk-decoder-nova/tree/main/decoder_nova_partial
Recursive proof: IPA and Halo2
just started studying zkWASM

Recording: https://drive.google.com/file/d/1HVO60ONk_VXAd_aLIzFcjNLSTDvszOX_/view?usp=drive_link


fix(curriculum): step 11 implict return fix

Checklist:

[x] I have read and followed the contribution guidelines.
[x] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #55851

I'm not sure we have reached a consensus on this.
But no matter what, we should update the description to include information about the callback. Please refer back to the issue for the text.

@lasjorg thanks. Updated PR.

@moT01 updated PR.

The code from the issue isn't passing:
const dataArrIndex = taskData.findIndex((item) => {
  item.id === currentTask.id;
})

Something might be missing from that regex, but I didn't look at it too hard to find it. Do you want to take a look at that @gagan-bhullar-tech? Thanks. Or let me know what I am missing.

My bad. I'll take another look.


#227 unset curl handle after it has been closed

Resolves issue 227 (making request objects reusable)

@nategood Please merge this.


Everything Unavailable

So it seems that its unable to locate anything. Troubleshooting with the character limit fixes did nothing. Wondering if an update to the game moved stuff around or another issue I as a novice am unable to fix?
Edit: I double checked the file paths and all are correct.

Hi @PrismShift
Did you ever get this working?