Support for multi-channel and channel-first dimension order

This PR adds:

Reformat most of the codes to channel-first order
Add support for multi-channel and z slice, everything in the pipeline are now formatted as [time/batch, channel, z, x, y]
Isolate instance segmentation methods to a separate script
Merge function for generating trajectory relations
Reformat pipeline function inputs (add channela as a position argument, allow customization of keyword argument)

Support for dimensionality reduction hasn't been added yet, will change in a following PR.
This PR should be merged first in order to avoid complexities of dimension order. @smguo @mattersoflight @bryantChhun Please check if there's any issues, otherwise I will merge by the end of tomorrow to allow for further progress.

@miaecle I made a dimensionality reduction CLI in my PR. Please take a look and let me know if you have any feedback

@miaecle I made a dimensionality reduction CLI in my PR. Please take a look and let me know if you have any feedback

Sure, I will finish the review by tonight.

I will go ahead and merge this PR. Docstring issue noted by @smguo will be resolved in a future PR.


Base Boosting:  init() got an unexpected keyword argument 'stacking_layer'

Hello,
After installing the package, I tried to run the base boosting code <https://scikit-physlearn.readthedocs.io/en/latest/baseboosting.html>. However, I wasn't able to make an instance of the regressor object. Please see the attached screenshot, and let me know what I could do to resolve this issue. Thanks!

Thank you for bringing attention to this issue. The example has been updated-- it replaces stacking_layer=stack with stacking_options=dict(layers=stack). The latter argument stacking_options allows the various options to be bundled into one argument.
To run the remaining portion of the example, please update to 0.1.7 which is the latest version. This version includes some nested cross-validation maintenance, as sklearn made some changes to the way they check scoring arguments.


[FLINK-19898][FLINK-19899][Kinesis][EFO] Optimise error handling and Retry Policy

What is the purpose of the change

The Flink Kinesis EFO consumer has a SubscribeToShard retry policy which will terminate the job after a given number of subsequent attempt failures. In high backpressure scenarios the Netty HTTP Client throws a ReadTimeoutException when the consumer takes longer than 30s to process a batch. If this happens (by default) 10 times in a row, the job will terminate. There is no need to terminate in this condition, and the restart results in the job falling further behind.
There is a queue used to pass events between the network client and consumer application. When an error is thrown in the network thread, the queue is cleared to make space for the error event. This means that records will be thrown away to make space for errors (the records would be subsequently reloaded from the shard).

Brief change log

Excluded the ReadTimeoutException from the SubscribeToShard retry policy, such that that connector will gracefully reconnect once the consumer has processed the queued records.
Added a new mechanism to pass exceptions between threads, meaning data does not need to be discarded. When an error is thrown, the error event will be processed by the consumer once all of the records have been processed.

Verifying this change

Existing unit tests continue to pass
Added additional test coverage
Deployed and tested on local Flink cluster

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): yes
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? not applicable

@tzulitai FYI

Thanks for the clarifications @dannycranmer! They are crystal clear :)
Merging this now to master ...


Remove Vercel APL

We may need to rename it to environment variables APL, why not to keep simple stateless option for single tenant apps

@HazemKhaled this is quite complex, becuase by design Saleor is performing a handshake during app installation/register.
To enable single-tenant env APL, we need to extract this token. It is possible of course - you can console.log it during installation and hardcode it (you can write your own EnvAPL if you like).
However, we are discussing if we should add EnvAPL in SDK. This will make it "official" or "recommended" approach, but its not the best way to do it:

It requires token to leak
It will break if app rotates token
It will break when we implement updates flow for the app (which will rotate token).

There are also better approaches to achieve that, depending on the infrastructure.
You can use Vercel EdgeConfig, that will do the job without exposing the token


n.option is undefined

Describe the bug
When adding some items there is
Expected behavior
Adding an item that displays new data
Screenshots

Network data

https://pastebin.com/zPHQwvXS
json: https://pastebin.com/Qxy4GyB7
query: https://pastebin.com/LFze5vfN
data: https://pastebin.com/T3G0d847
Software versions

Grafana
Zabbix
Grafana-Zabbix Plugin

v8.1.2
Zabbix 5.4.3.
4.1.1

Hi! Unfortunately, 4.1 plugin is not compatible with the Grafana 8. Try to upgrade to the latest plugin version, this problem was fixed.


Encapsulate Mac specific behavior

A few people have written in to say they are working on a Linux port, which is awesome. One such attempt is at https://github.com/anfractuosity/system-bus-radio/blob/master/main.c
It would be awesome to take the Mac only part and the linux (or general purpose) part and separate them with preprocessor directives.

A note for my C++11 port.
https://github.com/EzoeRyou/system-bus-radio
GCC means g++(core language) with libstdc++(standard library)
Clang means clang++(core language) with libc++(standard sibrary)
MSVC means MSVC2015.
It use std::chrono::high_resolution_clock for retrieving the current time.
On GNU/Linux, GCC's libstdc++ and Clangs libc++ use clock_gettime.
On Mac, Clang use mach_absolute_time.
On Windows, MSVC use QueryPerformanceCounter.
All major C++ implementations has sufficient resolution.
It use std::this_thread::sleep_until for sleep.
On GNU/Linux, GCC and Clang use nanosleep.
On Mac, Clang use nanosleep.
On Windows, MSVC use SleepEx
GNU/Linux and Mac OS X has sufficient resolution.
Windows doesn't have sufficient resolution.
Even by calling timeBeginPeriod(1), Windows C++ implementation has a resolution of 1 milliseconds.
Now for the instruction.
It appears the energy consumption is the main factor of strong electromagnetic radiation.
As reported by #5.
Using as many threads as number of cores(or HT cores) is probably a good strategy.
I ported #5 's code by using C++11's standard library ,  and <condition_variable>.
My implementation use C++11  for the instruction.
I asked a colleague who is expert at many CPU architectures for the best energy consuming instruction for x86-64, he said,
"the memory access which bypassing the cache is the worst(i.e. best)"
So, original _mm_stream_si128 is probably the best.
It lose the portability to non-x86 architectures though.

Fixed 1c15f939e01c79a32ad22c8241a2ecd613ed7d0d


Shader 'kernel_73b038d546fe000a.ptx' is not found in cache. The shader will be recompiled.

Hello,
finally the compiling succeeded, and I tried some scenes that downloaded from
https://github.com/LuisaGroup/LuisaRenderScenes/releases/tag/scenes
and I input the commands below with several different scenes,
github/LuisaGroup/LuisaRender/LuisaRender# build_ubuntu/bin/luisa-render-cli -b cuda scenes/spaceship/spaceship/scene.luisa
but it always give some warnings :
[2023-07-28 00:25:34.306] [console] [warning] Invalid texture coordinates in mesh '/media/liusheng/Projects/project/game_engines/LuisaRender/github/LuisaGroup/LuisaRender/LuisaRender/scenes/spaceship/spaceship/models/Mesh050.obj': address = 0x0, components = 0. [/media/liusheng/Projects/project/game_engines/LuisaRender/github/LuisaGroup/LuisaRender/LuisaRender/src/shapes/mesh.cpp:96]
[2023-07-28 00:25:34.306] [console] [info] Loaded triangle mesh '/media/liusheng/Projects/project/game_engines/LuisaRender/github/LuisaGroup/LuisaRender/LuisaRender/scenes/spaceship/spaceship/models/Mesh050.obj' in 56.093821999999996 ms.

and errors:

[2023-07-28 00:26:32.793] [console] [info] Computed accel memory usage in 0.0043809999999999995 ms: temp = 5760, temp_update = 0, output = 18816.
[2023-07-28 00:26:32.795] [console] [info] CUDAAccel compaction: before = 18816B, after = 17920B, ratio = 0.9523809523809523.
[2023-07-28 00:26:32.796] [console] [info] Created pipeline with 1 camera(s), 90 shape instance(s), 10 surface instance(s), and 4 light instance(s).
[2023-07-28 00:26:32.796] [console] [info] Wavefront path tracing configurations: resolution = 1920x1080, spp = 16384, state_count = 33177600, samples_per_pass = 16.
[2023-07-28 00:26:32.818] [console] [info] Compiling ray generation kernel.
[2023-07-28 00:26:32.820] [console] [info] Compiling intersection kernel.
[2023-07-28 00:26:32.821] [console] [info] Compiling environment evaluation kernel.
[2023-07-28 00:26:32.821] [console] [info] Generated CUDA source in 0.251282 ms.
[2023-07-28 00:26:32.821] [console] [info] Generated CUDA source in 0.759776 ms.
[2023-07-28 00:26:32.821] [console] [info] Read file /media/liusheng/Projects/project/game_engines/LuisaRender/github/LuisaGroup/LuisaRender/LuisaRender/build_ubuntu/bin/.cache/kernel_73b038d546fe000a.ptx failed.
[2023-07-28 00:26:32.821] [console] [info] Read file /media/liusheng/Projects/project/game_engines/LuisaRender/github/LuisaGroup/LuisaRender/LuisaRender/build_ubuntu/bin/.cache/kernel_b037032d8023c793.ptx failed.
[2023-07-28 00:26:32.821] [console] [info] Read file /media/liusheng/Projects/project/game_engines/LuisaRender/github/LuisaGroup/LuisaRender/LuisaRender/build_ubuntu/bin/.cache/kernel_73b038d546fe000a.ptx.metadata failed.
[2023-07-28 00:26:32.821] [console] [info] Shader 'kernel_73b038d546fe000a.ptx' is not found in cache. The shader will be recompiled.
[2023-07-28 00:26:32.821] [console] [info] Read file /media/liusheng/Projects/project/game_engines/LuisaRender/github/LuisaGroup/LuisaRender/LuisaRender/build_ubuntu/bin/.cache/kernel_b037032d8023c793.ptx.metadata failed.
[2023-07-28 00:26:32.821] [console] [info] Shader 'kernel_b037032d8023c793.ptx' is not found in cache. The shader will be recompiled.
[2023-07-28 00:26:32.822] [console] [info] Compiling light evaluation kernel.
[2023-07-28 00:26:32.823] [console] [info] Generated CUDA source in 0.64557 ms.
[2023-07-28 00:26:32.823] [console] [info] Read file /media/liusheng/Projects/project/game_engines/LuisaRender/github/LuisaGroup/LuisaRender/LuisaRender/build_ubuntu/bin/.cache/kernel_76297bf4429dae81.ptx failed.
[2023-07-28 00:26:32.824] [console] [info] Read file /media/liusheng/Projects/project/game_engines/LuisaRender/github/LuisaGroup/LuisaRender/LuisaRender/build_ubuntu/bin/.cache/kernel_76297bf4429dae81.ptx.metadata failed.
[2023-07-28 00:26:32.824] [console] [info] Shader 'kernel_76297bf4429dae81.ptx' is not found in cache. The shader will be recompiled.
[2023-07-28 00:26:32.824] [console] [info] Compiling light sampling kernel.
段错误 (核心已转储)

So, is the command I used wrong ? or is there anything else should I do ?
I used this renderer right away after it was compiled successfully, so why it says the .ptx files not found in cache ?
Thanks so much!!

I checked the "/LuisaGroup/LuisaRender/LuisaRender/build_ubuntu/bin/.cache/" directory for the aforementioned .ptx file name, and I found there are .ptx.cu files with those names , but .ptx files are missing:

so what's the problem with this? Thank you!

Hi, @disini
Thanks for reporting this.
I can reproduce the segfault error with the spaceship scene—so it should be an internal bug. I will take some time to dig into it.

The warnings about the mesh texture coordinates and ptx file read failures are just fine to ignore. The texture coordinates are for texture sampling; the ptx files are compilation caches and will be recompiled if missing.

Hi, @disini
The segfault was caused by the CUDA AST code generation in LuisaCompute, which attempts to dereference a nullptr when emitting the type name for void.
I fixed the bug in LuisaCompute and updated the submodules in LuisaRender. Please use
git pull && git submodule update --recursive --init

to update the repo and its submodules to apply the fix.
Thanks again for discovering this bug!

Thank you sir!
I tried to execute the same command for several times but it didn't recompile the .ptx file, it still report some errors like this and interrupted again and again.
I tried some more scene files, and they were all failed to finish the rendering.
for example the jinx scene:
build_ubuntu/bin/luisa-render-cli -b cuda scenes/jinx/scene.json
and there some other warnings and errors:
2023-07-28 01:43:38.870] [console] [info] Loaded dynamic module '/media/liusheng/Projects/project/game_engines/LuisaRender/github/LuisaGroup/LuisaRender/LuisaRender/build_ubuntu/bin/libluisa-render-surface-disney.so' in 0.540655 ms.
[2023-07-28 01:43:38.876] [console] [info] Loaded dynamic module '/media/liusheng/Projects/project/game_engines/LuisaRender/github/LuisaGroup/LuisaRender/LuisaRender/build_ubuntu/bin/libluisa-render-texture-swizzle.so' in 5.823637 ms.
[2023-07-28 01:43:38.878] [console] [warning] Property 'swizzle' is defined but is not a number list in scene description node 'Texture:textures/mat0_Ears_metallicRoughness.png:Metallic'. [/media/liusheng/Projects/project/game_engines/LuisaRender/github/LuisaGroup/LuisaRender/LuisaRender/scenes/jinx/lr_exported_materials.json:1:0]
[2023-07-28 01:43:38.879] [console] [warning] Property 'swizzle' is defined but is not a number list in scene description node 'Texture:textures/mat0_Ears_metallicRoughness.png:Roughness'. [/media/liusheng/Projects/project/game_engines/LuisaRender/github/LuisaGroup/LuisaRender/LuisaRender/scenes/jinx/lr_exported_materials.json:1:0]
[2023-07-28 01:43:38.889] [console] [warning] Property 'swizzle' is defined but is not a number list in scene description node 'Texture:textures/mat0_Chest_metallicRoughness.png:Metallic'. [/media/liusheng/Projects/project/game_engines/LuisaRender/github/LuisaGroup/LuisaRender/LuisaRender/scenes/jinx/lr_exported_materials.json:1:0]
[2023-07-28 01:43:38.889] [console] [warning] Property 'swizzle' is defined but is not a number list in scene description node 'Texture:textures/mat0_Chest_metallicRoughness.png:Roughness'. [/media/liusheng/Projects/project/game_engines/LuisaRender/github/LuisaGroup/LuisaRender/LuisaRender/scenes/jinx/lr_exported_materials.json:1:0]
[2023-07-28 01:43:38.893] [console] [warning] Property 'swizzle' is defined but is not a number list in scene description node 'Texture:textures/mat0_Hair_metallicRoughness.png:Metallic'. [/media/liusheng/Projects/project/game_engines/LuisaRender/github/LuisaGroup/LuisaRender/LuisaRender/scenes/jinx/lr_exported_materials.json:1:0]
[2023-07-28 01:43:38.893] [console] [warning] Property 'swizzle' is defined but is not a number list in scene description node 'Texture:textures/mat0_Hair_metallicRoughness.png:Roughness'. [/media/liusheng/Projects/project/game_engines/LuisaRender/github/LuisaGroup/LuisaRender/LuisaRender/scenes/jinx/lr_exported_materials.json:1:0]
[2023-07-28 01:43:38.897] [console] [warning] Property 'swizzle' is defined but is not a number list in scene description node 'Texture:textures/mat0_Head_metallicRoughness.png:Metallic'. [/media/liusheng/Projects/project/game_engines/LuisaRender/github/LuisaGroup/LuisaRender/LuisaRender/scenes/jinx/lr_exported_materials.json:1:0]
[2023-07-28 01:43:38.897] [console] [warning] Property 'swizzle' is defined but is not a number list in scene description node 'Texture:textures/mat0_Head_metallicRoughness.png:Roughness'. [/media/liusheng/Projects/project/game_engines/LuisaRender/github/LuisaGroup/LuisaRender/LuisaRender/scenes/jinx/lr_exported_materials.json:1:0]
[2023-07-28 01:43:38.915] [console] [warning] Property 'swizzle' is defined but is not a number list in scene description node 'Texture:textures/mat0_Eyes_metallicRoughness.png:Metallic'. [/media/liusheng/Projects/project/game_engines/LuisaRender/github/LuisaGroup/LuisaRender/LuisaRender/scenes/jinx/lr_exported_materials.json:1:0]

[2023-07-28 01:43:39.664] [console] [info] Computed mesh memory usage: temp = 15616, temp_update = 0, output = 408704.
[2023-07-28 01:43:39.666] [console] [info] CUDAMesh compaction sizes: before = 408704B, after = 382208B, ratio = 0.9351706858753523.
[2023-07-28 01:43:39.670] [console] [warning] Failed to allocate 16777216 bytes from CUDAHostBufferPool. Falling back to ad-hoc allocation. [/media/liusheng/Projects/project/game_engines/LuisaRender/github/LuisaGroup/LuisaRender/LuisaRender/src/compute/src/backends/cuda/cuda_host_buffer_pool.cpp:35]
[2023-07-28 01:43:39.674] [console] [info] Computed mesh memory usage: temp = 226048, temp_update = 0, output = 6313856.
[2023-07-28 01:43:39.676] [console] [info] CUDAMesh compaction sizes: before = 6313856B, after = 5835776B, ratio = 0.9242808198349788.
[2023-07-28 01:43:39.697] [console] [info] Computed mesh memory usage: temp = 123008, temp_update = 0, output = 3422080.
[2023-07-28 01:43:39.698] [console] [info] CUDAMesh compaction sizes: before = 3422080B, after = 3200384B, ratio = 0.9352160089769964.
[2023-07-28 01:43:39.711] [console] [info] Computed mesh memory usage: temp = 4864, temp_update = 0, output = 105856.
[2023-07-28 01:43:39.713] [console] [info] CUDAMesh compaction sizes: before = 105856B, after = 94464B, ratio = 0.8923821039903265.
[2023-07-28 01:43:39.716] [console] [warning] Failed to allocate 16777216 bytes from CUDAHostBufferPool. Falling back to ad-hoc allocation. [/media/liusheng/Projects/project/game_engines/LuisaRender/github/LuisaGroup/LuisaRender/LuisaRender/src/compute/src/backends/cuda/cuda_host_buffer_pool.cpp:35]
[2023-07-28 01:43:39.718] [console] [info] Computed mesh memory usage: temp = 5504, temp_update = 0, output = 124800.
[2023-07-28 01:43:39.719] [console] [info] CUDAMesh compaction sizes: before = 124800B, after = 107264B, ratio = 0.8594871794871795.
[2023-07-28 01:43:39.723] [console] [info] Computed mesh memory usage: temp = 2432, temp_update = 0, output = 40064.
[2023-07-28 01:43:39.725] [console] [info] CUDAMesh compaction sizes: before = 40064B, after = 35968B, ratio = 0.8977635782747604.
[2023-07-28 01:43:39.728] [console] [warning] Failed to allocate 16777216 bytes from CUDAHostBufferPool. Falling back to ad-hoc allocation. [/media/liusheng/Projects/project/game_engines/LuisaRender/github/LuisaGroup/LuisaRender/LuisaRender/src/compute/src/backends/cuda/cuda_host_buffer_pool.cpp:35]
[2023-07-28 01:43:39.730] [console] [info] Computed mesh memory usage: temp = 1920, temp_update = 0, output = 24192.
[2023-07-28 01:43:39.730] [console] [info] CUDAMesh compaction sizes: before = 24192B, after = 19840B, ratio = 0.8201058201058201.
[2023-07-28 01:43:39.731] [console] [warning] Failed to allocate 16777216 bytes from CUDAHostBufferPool. Falling back to ad-hoc allocation. [/media/liusheng/Projects/project/game_engines/LuisaRender/github/LuisaGroup/LuisaRender/LuisaRender/src/compute/src/backends/cuda/cuda_host_buffer_pool.cpp:35]

[2023-07-28 01:43:40.026] [console] [info] Read file /media/liusheng/Projects/project/game_engines/LuisaRender/github/LuisaGroup/LuisaRender/LuisaRender/build_ubuntu/bin/.cache/kernel_15d4a0dcafd153db.ptx.metadata failed.
[2023-07-28 01:43:40.026] [console] [info] Shader 'kernel_15d4a0dcafd153db.ptx' is not found in cache. The shader will be recompiled.
[2023-07-28 01:43:40.026] [console] [info] Compiling light evaluation kernel.
[2023-07-28 01:43:40.026] [console] [info] Generated CUDA source in 0.37587899999999996 ms.
[2023-07-28 01:43:40.027] [console] [info] Read file /media/liusheng/Projects/project/game_engines/LuisaRender/github/LuisaGroup/LuisaRender/LuisaRender/build_ubuntu/bin/.cache/kernel_f08e3c271bd79ed5.ptx failed.
[2023-07-28 01:43:40.027] [console] [info] Read file /media/liusheng/Projects/project/game_engines/LuisaRender/github/LuisaGroup/LuisaRender/LuisaRender/build_ubuntu/bin/.cache/kernel_f08e3c271bd79ed5.ptx.metadata failed.
[2023-07-28 01:43:40.027] [console] [info] Shader 'kernel_f08e3c271bd79ed5.ptx' is not found in cache. The shader will be recompiled.
[2023-07-28 01:43:40.027] [console] [info] Compiling light sampling kernel.
段错误 (核心已转储)

Thank you sir!

Hi, @disini
The segfault was caused by the CUDA AST code generation in LuisaCompute, which attempts to dereference a nullptr when emitting the type name for void.
I fixed the bug in LuisaCompute and updated the submodules in LuisaRender. Please use
git pull && git submodule update --recursive --init

to update the repo and its submodules to apply the fix.
Thanks again for discovering this bug!

Wow that's really awosome!!!
Much appreciated for your timely reply and fixed the bug so quickly !
Thanks again sir!

I tried to execute the same command for several times but it didn't recompile the .ptx file, it still report some errors like this and interrupted again and again.

Would you please check if src/compute is on commit caaaa658... by
cd src/compute
git status

Just in case you did not check out the fix I pushed right now.

Hi, @disini
The segfault was caused by the CUDA AST code generation in LuisaCompute, which attempts to dereference a nullptr when emitting the type name for void.
I fixed the bug in LuisaCompute and updated the submodules in LuisaRender. Please use
git pull && git submodule update --recursive --init

to update the repo and its submodules to apply the fix.
Thanks again for discovering this bug!

Wow that's really awosome!!! Much appreciated for your timely reply and fixed the bug so quickly ! Thanks again sir!

Nice! Thanks for your testing!

I tried to execute the same command for several times but it didn't recompile the .ptx file, it still report some errors like this and interrupted again and again.

Would you please check if src/compute is on commit caaaa658... by
cd src/compute
git status

Just in case you did not check out the fix I pushed right now.

ub/LuisaGroup/LuisaRender/LuisaRender/src/compute$ git status
HEAD detached at caaaa658
nothing to commit, working tree clean
yes it's up-to-date!


[Mobile][Sensor] Add Sensor Sample Application

copy sensor sample app from dev_freeze branch.

https://analysishub.sec.samsung.net/service/v1/analyses/529655/pdf
svace 확인했습니다.


chore: upgrade narwhal pointer

contains changes:

adding a sender channel to AuthorityState and start a SuiNode with it
implement BatchExecutionState and SingleExecutionState for AuthorityState
ed25519-dalek is fully removed

@asonnino i resolved the compiler errors by implementing the traits - the tests are currently failing because I am not exactly sure where sui should be loading the worker cache.

I expect this would be made obsolete by https://github.com/MystenLabs/narwhal/pull/859

closing in favor of https://github.com/MystenLabs/sui/pull/4316


Explain the checkers

Coverage remained the same at 41.462% when pulling 47ee7a0d44e4b5a01a05ecc95caa9575aa56eeb2 on sylvestre:doc into 9328048b216613b7c364c61434cd4bb9da9f0cab on mozilla:master.


Contracts in actions

Allow to define contract blocks that behave the same as Dry::Validation contract, because they will essentially pass their contents to insides of that gem
There are many details left to do, but the main "pass the block to try validation" seems ok. I am also not sure about making contract available on request inside handle. It pararels the params, but params are direct wrapper upon the request params so it makes more sense. Contract is more of an abstract thing so attaching it to the request seems "meh" at my first glance

hey thanks for working on this! it's looking good and I'm wondering what's missing (if anything) and if you're planning to open a PR?

hey thanks for working on this! it's looking good and I'm wondering what's missing (if anything) and if you're planning to open a PR?

@solnic Hey, thanks for checking it out, I completely forgot to transfer the PR to target the main repo :) . I will do it today, after updating the description. Then its just getting a review and working on it if needed I suppose

moved to https://github.com/hanami/controller/pull/451


Load balance integration tests

TEST ONLY - NOT READY FOR REVIEW

This change is

Testing passed, will close this PR and open a new one once #580 is merged.


Deleting a group

Currently, there is no way to delete a group once it has been created. It would be a good if this feature was added. At minimum it could be added for site admins.
Use Case: There is currently a AngularJS and ReactHSV groups. As of March 8th these will be one group. It would be nice if I could rename one group and then delete the other one.

Keep in mind that Events have a relationship to Groups. Each Event has a group_id attribute. Therefore, if you delete a group you must remove all the Events for that group, otherwise you'll have orphaned events.

I would be more in favor of archive type boolean. That way, the data is
still there and useful in the future.
On Feb 24, 2017 2:55 PM, "davidhjones"<EMAIL_ADDRESS>wrote:

Keep in mind that Events have a relationship to Groups. Each Event has a
group_id attribute. Therefore, if you delete a group you must remove all
the Events for that group, otherwise you'll have orphaned events.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/OpenHuntsville/hntsvll/issues/129#issuecomment-282402015,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABY-Ypj262KIMhB1AvCspUSnZYFEJJpoks5rf0O8gaJpZM4MLpjb
.

I like @skylenewman's idea.  If we delete the event then there's no record that a past event ever happened. I'd much rather have an archive of past events whether or not the event still exists.

Yeah thats a good solution. We would still want to archive the events that fall under a given group, but I could see some value in persisting the data.

Events now archived when the user clicks the delete button. In order to archive the groups we'll need to do the following:

Add an "archived" column to the group table (set a default value of false
Add a delete button to the Edit Group page
Add a route for the delete button so that when the button is pressed it will update the value for the archived column to be set to true
Update the /groups route so it only shows groups that have archived set to false

Now one thing to note is that we're adding an archived functionality but we're not adding a way to go back and pull them back in. In order to un-archive a group or event we'd have to update the database manually.

Groups are now able to be archived. Currently this functionality is limited to site admins only.


Please allow the filter box in Process Explorer to also filter by command-line and image-path

Actually the ability to filter by ANY column will be amazing but I do not want to be too greedy.

Maybe even combining the columns in queries such as
process=<substring for process> commandline=<substring for command line>

Tracking this for one of the upcoming releases, thanks!


[bug][PHP]: uppercase namespace parts are highlighted differently in preview

Describe the bug
the last part of the namespace in use statements in PHP are highlighted different if they only contain uppercase letters:
( In https://github.com/azjezz/hack-php-async-io/blob/3b44c06a2a486733cd9796289f01bf00dccd8655/src/main.php )

This behavior is also present when using the namespace:
( In https://github.com/azjezz/hack-php-async-io/blob/3b44c06a2a486733cd9796289f01bf00dccd8655/src/main.php#L15 )

The weird thing is that this doesn't happen when editing the file, but only when viewing it:

Expected behaviour
The last part of the namespace should be highlighted in the same color regardless if it contains only uppercase letters, or a mix of uppercase, lowercase, underscore, and numbers.
Related discussion
N/A
Additional notes
N/A

message TEKSignatureList {
signatures: [
TEKSignature {
signature_info:
SignatureInfo {
verification_key_id: "310"
verification_key_version: "v1"
signature_algorithm: "1.2.840.10<IP_ADDRESS>"
}
signature: [...] // signature byte contents using key version 1
},
]
}

From the troubleshooting docs:

Linguist detects the language of a file but the actual syntax-highlighting is powered by […] a set of submodules as listed here. […] If you experience an issue with the syntax-highlighting on GitHub, please report the issue to the upstream grammar repository, not here.

For PHP highlighting, Linguist uses @ondrejmirtes's fork of textmate/php.tmbundle. This was switched quite recently to fix another issue (see #5677). Now, normally I'd recommend filing an issue upstream, but @ondrejmirtes hasn't enabled the Issues tab on his fork. Hence we'll have to wait for his response to this thread.

Hello, I'm heavily invested in PHP's future and awesomeness and good highlighting on GitHub is definitely part of that. The reason why I turned off issues on my php.tmbundle fork is that I'm really busy with my current projects (mostly PHPStan and related libraries like Roave/BetterReflection).
I promise I'll be responsive with reviewing and testing any incoming PRs, much more than the owners of the original repo were, but I can't fix these bugs myself. Thank you for understanding.

@ondrejmirtes so how are you going to take feedback and issues like this? Issues like this don't belong in the Linguist repo as it's not an issue with Linguist.

@lildude I'll gladly test and accept any PRs with fixes, otherwise I'm not really interested in bug reports. The person reporting the bug can and should look into fixing it instead.
I can modify the README to reflect this.

🤔 that seems at odds with your "I'm heavily invested in PHP's future and awesomeness and good highlighting on GitHub is definitely part of that." comment, but that's your choice.
Over to you @azjezz.
Closing this issue as it's not a Linguist issue.


Confusing instructions

Being unfamiliar with the end-to-end process, I find this page simply confusing.  It needs more detailed instructions and examples.  I want to set my AZ AD Admin User to be an AD Group so that any member of the group can administrate users.  Also, a more detailed example of setting the PGPASSWORD would really be helpful.  Should the variable contain the entire JSON doc returned by az account get-access-token, or just the token part??  Would it need to be quoted??  How am I supposed to know the answer to this?

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

ID: f87e092b-c331-8bc9-9061-89f0712adb5a
Version Independent ID: d0ef3b6e-5973-e159-3c73-9eb8dbf2825f
Content: Use Azure Active Directory - Azure Database for PostgreSQL - Single Server
Content Source: articles/postgresql/howto-configure-sign-in-aad-authentication.md
Service: postgresql
GitHub Login: @lfittl
Microsoft Alias: lufittl

Hi @cphares - thanks for your comment!
I agree we need more detailed instructions and examples here, and we're actively working on that.
Regarding PGPASSWORD - you only need to pass in the part thats marked as TOKEN on the documentation page, i.e. not the full JSON object. Typically I would put it in quotes, like this:
export PGPASSWORD="TOKEN"

Does that help?

Its been a while we heard from you.
We will proceed to close this issue now.
If there are further questions regarding this matter, please comment and we will gladly continue the discussion.


Show Fixes keyboard shortcut not working in Chrome

monaco-editor version: 0.22.3
Browser: Google Chrome
OS: macOS Big Sur
Playground code that reproduces the issue:
Open in TypeScript Playground
interface Foo {
    bar(): void;
}

class Bar implements Foo {

}

When having this code, it shows a red underline under Bar because the class doesn't implement the interface correctly.

When putting the cursor on the Bar word, it shows the lightbulb on the left which when clicked shows the Implement interface 'Foo' action.

When hovering over the lightbulb, it also shows the keyboard shortcut (⌘+.), but when pressed in Chrome, it doesn't work. In Safari however, this works correctly. Untested in Firefox.

After some more testing it works on Linux with Ctrl+..
It works on macOS as well if you put the cursor at the end of the word, so placing the cursor after the r of Bar and press the shortcut, then it works as expected.

@SamVerschueren I cannot reproduce. cmd+. works for me on macOS on Chrome. Are you using the US keyboard layout or something else?

Ok, this is super weird. So yesterday it wasn't working for me, only if I placed my cursor and the end of the word. I let someone else test this on mac OS, he had the exact same problem. Someone else tested it on Linux and he confirmed that it worked for him. So I assumed this was a Chrome thing on macOS. But when testing it again, it suddenly works. For me, as well as for the person who had the exact same issue.
Let me close this for now, if it pops up again, I can reopen it or something. I was testing different versions monaco, maybe something got corrupted or something.
Thanks for the quick response from your end 🙏 .


add ceph status check and init pool

add ceph status check and init pool

Coverage remained the same at 60.621% when pulling f94ecfc4c3c6357f74dc05e79354a8d326f83f10 on xxwjj:ansible-ceph into b5bf9e025b1b5c42cf8915d1b7abacc739c9f479 on opensds:development.

Coverage remained the same at 60.621% when pulling 8ace9b35045b93bcd09cab596c45473e59674a22 on xxwjj:ansible-ceph into b5bf9e025b1b5c42cf8915d1b7abacc739c9f479 on opensds:development.


[ui typo] tab context menu close all shows 'close close' in Chinese

Description

version： 23.2.0
ui language: chinese
DBeaver Version
23.2.0
Operating System
win11
Database and driver
No response
Steps to reproduce
No response
Additional context
No response

Hello @LeiYangGH
Thanks for the report.
And I'm closing this ticket as a duplicate of https://github.com/dbeaver/dbeaver/issues/17697
You can read more info about translation there.


Removed Python from image.

Removed python-is-python3 from the list of installed packages since it results in the unintentional installation of Python itself

Should fix #157


Allow dependencies to refer to other CumulusCI configured repositories

Currently an extension package project needs to maintain its own list of dependencies manually.  This can become challenging if extending another extension package.
Consider the following structure for three managed package repositories:
RepoA - no dependencies, latest is 1.1
RepoB - requires RepoA, latest is 1.2
RepoC - requires RepoB, latest is 1.3
The cumulusci.yml files should look like:
RepoA
project:
    package:
        namespace: RepoA

RepoB
project:
    package:
        namespace: RepoB
    dependencies:
        - github: https://github.com/TestOwner/RepoA

RepoC
project:
    package:
        namespace: RepoC
    dependencies:
        - github: https://github.com/TestOwner/RepoB

When you run cci task run update_dependencies from within RepoC, the following should happen:

Github is queried to fetch the cumulusci.yml file from RepoB
Github is queried to fetch the cumulusci.yml file from RepoA due to the reference in RepoB's cumulusci.yml
The processed dependency map for RepoC should be:

- namespace: RepoB
  version: 1.2
  dependencies
    - namespace: RepoA
      version: 1.1

Implemented in commit b631951ba34899b097a71f4d105b6c8a8ba5c78d


grim reaper auto kit

grim reaper autokit not working in game

I can't really test it atm so /shrug


Cannot properly dump transformation matrix in U+1D1D in Noto Sans

This is original U+1D1D in Noto Sans:

After running
otfccdump.exe NotoSans-Regular.ttf | otfccbuild.exe -o a.ttf

it looks like this:

otfccdump dumps U+1D1D in Noto Sans to this:
        "uni1D1D": {
            "advanceWidth": 618,
            "references": [
                {"glyph":"n","x":38,"y":584,"a":0,"b":-1,"c":1,"d":-1,"roundToGrid":true}
            ],
            "instructions": ["PUSHB_2",0,1,"PUSHW_1",584,"PUSHB_1",51,"CALL"]
        },

It seems that "d" should be 0.
NotoSans-Regular.zip
otfcc version: 0.10.3 (prebuilt Windows x64, downloaded from https://github.com/caryll/otfcc/releases/tag/v0.10.3-alpha)

I made a fix in master. You can try to rebuild it on your own.
OTFCC is now in a maintenance mode (I have a TypeScript project internally in MSFT does the same thing).


New Worker API (Java) reports deprecation warning about not using ObjectFactory.mapProperty() in Gradle 5.6

I'm seeing a deprecation warning about not using ObjectFactory.mapProperty() which I don't think I have any control over.
E.g. a simple project defined across two files
~/tstProj/buildSrc/src/main/java/MyTask.java:
import org.gradle.api.provider.Property;
import org.gradle.api.DefaultTask;
import org.gradle.api.tasks.TaskAction;
import org.gradle.workers.IsolationMode;
import org.gradle.workers.WorkAction;
import org.gradle.workers.WorkParameters;
import org.gradle.workers.WorkQueue;
import org.gradle.workers.WorkerExecutor;

import java.io.IOException;
import java.util.LinkedHashMap;
import java.util.Map;
import java.util.Properties;
import javax.inject.Inject;

public class MyTask extends DefaultTask {
    final WorkerExecutor workerExecutor;

    @Inject
    public MyTask(WorkerExecutor workerExecutor) {
        this.workerExecutor = workerExecutor;
    }

    @TaskAction
    public void run() {
        Map<Object, Object> myProps = new LinkedHashMap<>();
        myProps.put("key1", "value1");
        myProps.put("key2", "value2");
        myProps.put("key3", "value3");

        final WorkQueue workQueue = workerExecutor.processIsolation();

        workQueue.submit(MyRunner.class, (MyParameters params) -> {
            params.getMyProps().set(myProps);
        });
    }

    interface MyParameters extends WorkParameters {
        Property<Map<Object, Object>> getMyProps();
    }

   public static abstract class MyRunner implements WorkAction<MyParameters> {
        @Override
        public void execute() {
            final MyParameters params = getParameters();

            final Properties myProps = new Properties();
            myProps.putAll(params.getMyProps().get());

            try {
                myProps.store(System.out, null);
            } catch (IOException e) {
                // do nothing
            }
        }
    }
}

~/tstProj/build.gradle:
import MyTask

task myTask(type: MyTask) {
    description 'My Task'
}

result:
./gradlew myTask
...
> Task :myTask
Caching disabled for task ':myTask' because:
  Build cache is disabled
Task ':myTask' is not up-to-date because:
  Task has not declared any outputs despite executing actions.
Using method ObjectFactory.property() method to create a property of type Map<K, V> has been deprecated. This will fail with an error in Gradle 6.0. Please use the ObjectFactory.mapProperty() method instead.
#Thu Aug 22 10:19:16 PDT 2019
key3=value3
key2=value2
key1=value1
:myTask (Thread[Execution worker for ':',5,main]) completed. Took 0.007 secs.

BUILD SUCCESSFUL in 581ms
1 actionable task: 1 executed

Expected Behavior
should not see a deprecation warning about not using ObjectFactory.mapProperty()
Current Behavior
I am seeing a deprecation warning about not using ObjectFactory.mapProperty()
Context
I want to pass a java.util.Map object to my worker
Steps to Reproduce
See example above.
Your Environment
OSX

Note issue is similar to the one reported in https://github.com/gradle/gradle/issues/10341

Based on @ghale 's comment https://github.com/gradle/gradle/issues/10341#issuecomment-524002179 I've tried returning a MapProperty<Object, Object> in place of a Property<Map<Object, Object>>.
That was successful and avoided the deprecation warning about not using ObjectFactory.mapProperty().
So in this case I did actually have control over the parts that were triggering the warning.
I'll go ahead and resolve this issue.

my bad


Questionare in Manitoba recommended topics not expected : Case 2

When I test the questionnaire I follow the following steps:
Clear all data from the app (go to ? Help, Clear all Data). Go to the questionnaire.
On Question 2, Select the answer "Less than 1 year".
On Question 4, mark that you have all documents.
I expect to see that recommended topics that show up are, since these are "recommended to all":
1.1 Manitoba Start & Settlement agencies,
1.2 General information,
1.5 Weather in Manitoba,
1.7 Buying food,
1.8 In your community: Recreation centres, Public libraries, Canada Post,
2.1 Types of housing,
2.7 Household waste management,
3.1 Canadian money and banking,
4.7 Vaccinations,
7.5 Public transportation
But instead, I see:
Social Insurance Number,
Opening a bank account
Credit and credit history
Canadian money and banking
Acceptance Criteria

[ ]

Steps for QA:

Closing this issue, it will be solved as part of https://github.com/pg-irc/pathways-frontend/issues/1689


s6-envdir: fatal: unable to envdir: Permission denied

Have openmediavault with this docker; keep receiving the error s6-envdir: fatal: unable to envdir: Permission denied on a never ending loop.
Configuration:
[     {         "Id": "7be3537baa873035c5125e5ffca5d779199e8b8d2e0787c40dfcd414fec04a8a",         "Created": "2019-03-17T17:41:05.723290215Z",         "Path": "/init",         "Args": [],         "State": {             "Status": "running",             "Running": true,             "Paused": false,             "Restarting": false,             "OOMKilled": false,             "Dead": false,             "Pid": 17162,             "ExitCode": 0,             "Error": "",             "StartedAt": "2019-03-17T17:41:07.721764789Z",             "FinishedAt": "0001-01-01T00:00:00Z"         },         "Image": "sha256:fdbde96f2f3461014ce9c7a6344275b93950eb2e9a5338151c55244e24961c96",         "ResolvConfPath": "/srv/dev-disk-by-label-raid3TBa/docker/containers/7be3537baa873035c5125e5ffca5d779199e8b8d2e0787c40dfcd414fec04a8a/resolv.conf",         "HostnamePath": "/srv/dev-disk-by-label-raid3TBa/docker/containers/7be3537baa873035c5125e5ffca5d779199e8b8d2e0787c40dfcd414fec04a8a/hostname",         "HostsPath": "/srv/dev-disk-by-label-raid3TBa/docker/containers/7be3537baa873035c5125e5ffca5d779199e8b8d2e0787c40dfcd414fec04a8a/hosts",         "LogPath": "/srv/dev-disk-by-label-raid3TBa/docker/containers/7be3537baa873035c5125e5ffca5d779199e8b8d2e0787c40dfcd414fec04a8a/7be3537baa873035c5125e5ffca5d779199e8b8d2e0787c40dfcd414fec04a8a-json.log",         "Name": "/filebot",         "RestartCount": 0,         "Driver": "overlay2",         "Platform": "linux",         "MountLabel": "",         "ProcessLabel": "",         "AppArmorProfile": "docker-default",         "ExecIDs": null,         "HostConfig": {             "Binds": [                 "/etc/localtime:/etc/localtime:ro",                 "/sharedfolders/appdata/filebot/storage:/storage:rw",                 "/sharedfolders/appdata/filebot/config:/config:rw"             ],             "ContainerIDFile": "",             "LogConfig": {                 "Type": "json-file",                 "Config": {}             },             "NetworkMode": "bridge",             "PortBindings": {},             "RestartPolicy": {                 "Name": "always",                 "MaximumRetryCount": 0             },             "AutoRemove": false,             "VolumeDriver": "",             "VolumesFrom": null,             "CapAdd": null,             "CapDrop": null,             "Dns": [],             "DnsOptions": [],             "DnsSearch": [],             "ExtraHosts": null,             "GroupAdd": null,             "IpcMode": "shareable",             "Cgroup": "",             "Links": null,             "OomScoreAdj": 0,             "PidMode": "",             "Privileged": false,             "PublishAllPorts": false,             "ReadonlyRootfs": false,             "SecurityOpt": null,             "UTSMode": "",             "UsernsMode": "",             "ShmSize": 67108864,             "Runtime": "runc",             "ConsoleSize": [                 0,                 0             ],             "Isolation": "",             "CpuShares": 0,             "Memory": 0,             "NanoCpus": 0,             "CgroupParent": "",             "BlkioWeight": 0,             "BlkioWeightDevice": [],             "BlkioDeviceReadBps": null,             "BlkioDeviceWriteBps": null,             "BlkioDeviceReadIOps": null,             "BlkioDeviceWriteIOps": null,             "CpuPeriod": 0,             "CpuQuota": 0,             "CpuRealtimePeriod": 0,             "CpuRealtimeRuntime": 0,             "CpusetCpus": "",             "CpusetMems": "",             "Devices": [],             "DeviceCgroupRules": null,             "DiskQuota": 0,             "KernelMemory": 0,             "MemoryReservation": 0,             "MemorySwap": 0,             "MemorySwappiness": null,             "OomKillDisable": false,             "PidsLimit": 0,             "Ulimits": null,             "CpuCount": 0,             "CpuPercent": 0,             "IOMaximumIOps": 0,             "IOMaximumBandwidth": 0,             "MaskedPaths": [                 "/proc/asound",                 "/proc/acpi",                 "/proc/kcore",                 "/proc/keys",                 "/proc/latency_stats",                 "/proc/timer_list",                 "/proc/timer_stats",                 "/proc/sched_debug",                 "/proc/scsi",                 "/sys/firmware"             ],             "ReadonlyPaths": [                 "/proc/bus",                 "/proc/fs",                 "/proc/irq",                 "/proc/sys",                 "/proc/sysrq-trigger"             ]         },         "GraphDriver": {             "Data": {                 "LowerDir": "/srv/dev-disk-by-label-raid3TBa/docker/overlay2/c169a93a018441fdffa12bfcb46a71ad84bb10f26dce26808a3410bce0a9d3ea-init/diff:/srv/dev-disk-by-label-raid3TBa/docker/overlay2/ce5be2f2bca8396e6816780adf0a3c7c2f8099d18924b8d80a3aa8a6a5f4b6c9/diff:/srv/dev-disk-by-label-raid3TBa/docker/overlay2/9f7b8e69c8c1df515dcb36c782308faed78487ce4948b82857f5f2f1098d362c/diff:/srv/dev-disk-by-label-raid3TBa/docker/overlay2/784811e3e67f85ff5b3029a1c9e2b1b3e493ea2ccacf17e14e666104623e8b08/diff:/srv/dev-disk-by-label-raid3TBa/docker/overlay2/a4fa048c605705386529dc960ffe08c1cbf01c1483ee29a14e682c83a03d1e60/diff:/srv/dev-disk-by-label-raid3TBa/docker/overlay2/21775b735c4cabf00eec6ed97fbb54cad98d5280dca2bde2ba8d41b554f768ab/diff:/srv/dev-disk-by-label-raid3TBa/docker/overlay2/dc664e682311fa0894301b3dbe5bd77fee8fb14b9349ba4b3a8f2ae9f467231e/diff:/srv/dev-disk-by-label-raid3TBa/docker/overlay2/5246e81d423788143b2cffc00de6249c11aa63ea160720009a64346dd5473c99/diff:/srv/dev-disk-by-label-raid3TBa/docker/overlay2/ba3be42d7394992cbda2ba34fef434aae300ea9f543b81d85f05129eae085e92/diff:/srv/dev-disk-by-label-raid3TBa/docker/overlay2/76f98361cd5456b9148a1cfa1aedaf3b1112c3a943f89f387c28f551a48021eb/diff:/srv/dev-disk-by-label-raid3TBa/docker/overlay2/c457f883c8f566cd5eb126c7a12e20841774e53c6d5ab89bd5be6b6a69c143b7/diff:/srv/dev-disk-by-label-raid3TBa/docker/overlay2/9794a2a2f65e58f0a1b600316c512be809fc29be4792114be79bcd229260bedc/diff:/srv/dev-disk-by-label-raid3TBa/docker/overlay2/d51ddd1491a0eb520f48b0f92c2f3eb9dd33531faeac8cef8dcec174b88cc750/diff:/srv/dev-disk-by-label-raid3TBa/docker/overlay2/ece3be70f7acd19d6190d4b891c37b604107e448813617e6f0287a013924d6d7/diff:/srv/dev-disk-by-label-raid3TBa/docker/overlay2/02a62d89826f0a8afe22fa5103a7708f77bd6a8544a5ce0167c64096994bb8b4/diff:/srv/dev-disk-by-label-raid3TBa/docker/overlay2/7651c4dc6ce7378f12bb6140074a7103d90726399e71ec88ed77a0ce7171b15e/diff:/srv/dev-disk-by-label-raid3TBa/docker/overlay2/92854a2740fb1419b719025436811f6d806b73021e4c17b70fee034ab6f0fd03/diff:/srv/dev-disk-by-label-raid3TBa/docker/overlay2/8969a3214e4c6780906fe0ea46c817a4bd6ac0b5242f3be5ce4c9626cc9bfbd7/diff:/srv/dev-disk-by-label-raid3TBa/docker/overlay2/ad5cf8bc838475e831971f75bebddb55678e8740c3495361132307f5d65e3d8a/diff:/srv/dev-disk-by-label-raid3TBa/docker/overlay2/821d8f223fcd971fada3f76a4028129e74706782d496a3557bf8962adacaef8e/diff:/srv/dev-disk-by-label-raid3TBa/docker/overlay2/587c880e3f739a32b7f9d6bf4e4fcabd9f02d50e3016de165ffab68e48268c10/diff:/srv/dev-disk-by-label-raid3TBa/docker/overlay2/06bbda0b2a5e7e64fc327028760cda446f4c83d1b60d84cbde78c1084e5e22fb/diff",                 "MergedDir": "/srv/dev-disk-by-label-raid3TBa/docker/overlay2/c169a93a018441fdffa12bfcb46a71ad84bb10f26dce26808a3410bce0a9d3ea/merged",                 "UpperDir": "/srv/dev-disk-by-label-raid3TBa/docker/overlay2/c169a93a018441fdffa12bfcb46a71ad84bb10f26dce26808a3410bce0a9d3ea/diff",                 "WorkDir": "/srv/dev-disk-by-label-raid3TBa/docker/overlay2/c169a93a018441fdffa12bfcb46a71ad84bb10f26dce26808a3410bce0a9d3ea/work"             },             "Name": "overlay2"         },         "Mounts": [             {                 "Type": "bind",                 "Source": "/etc/localtime",                 "Destination": "/etc/localtime",                 "Mode": "ro",                 "RW": false,                 "Propagation": "rprivate"             },             {                 "Type": "bind",                 "Source": "/sharedfolders/appdata/filebot/storage",                 "Destination": "/storage",                 "Mode": "rw",                 "RW": true,                 "Propagation": "rprivate"             },             {                 "Type": "bind",                 "Source": "/sharedfolders/appdata/filebot/config",                 "Destination": "/config",                 "Mode": "rw",                 "RW": true,                 "Propagation": "rprivate"             }         ],         "Config": {             "Hostname": "ba46464d8bf0",             "Domainname": "",             "User": "",             "AttachStdin": false,             "AttachStdout": false,             "AttachStderr": false,             "ExposedPorts": {                 "5800/tcp": {},                 "5900/tcp": {}             },             "Tty": false,             "OpenStdin": false,             "StdinOnce": false,             "Env": [                 "XDG_CONFIG_HOME=/config/xdg/config",                 "DISPLAY_HEIGHT=768",                 "USER_ID=1001",                 "S6_SERVICE_DEPS=1",                 "XDG_CACHE_HOME=/config/xdg/cache",                 "APP_NAME=FileBot",                 "XDG_RUNTIME_DIR=/tmp/run/user/app",                 "APP_USER=app",                 "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",                 "LANG=en_US.UTF-8",                 "KEEP_APP_RUNNING=1",                 "DISPLAY_WIDTH=1280",                 "GROUP_ID=100",                 "XDG_DATA_HOME=/config/xdg/data",                 "DISPLAY=:0",                 "S6_BEHAVIOUR_IF_STAGE2_FAILS=3"             ],             "Cmd": [                 "/init"             ],             "ArgsEscaped": true,             "Image": "jlesage/filebot:latest",             "Volumes": {                 "/config": {},                 "/storage": {}             },             "WorkingDir": "/tmp",             "Entrypoint": null,             "OnBuild": null,             "Labels": {                 "org.label-schema.description": "Docker container for FileBot",                 "org.label-schema.name": "filebot",                 "org.label-schema.schema-version": "1.0",                 "org.label-schema.vcs-url": "https://github.com/jlesage/docker-filebot",                 "org.label-schema.version": "1.2.0"             }         },         "NetworkSettings": {             "Bridge": "",             "SandboxID": "7e237e70e84e68cef1bbd66e41099c923439415348bbec92c73f7a6b579f23df",             "HairpinMode": false,             "LinkLocalIPv6Address": "",             "LinkLocalIPv6PrefixLen": 0,             "Ports": {                 "5800/tcp": null,                 "5900/tcp": null             },             "SandboxKey": "/var/run/docker/netns/7e237e70e84e",             "SecondaryIPAddresses": null,             "SecondaryIPv6Addresses": null,             "EndpointID": "b9509281cb441b0e19f347e4b07cadd40de256c1000b79863a95dac22234cc2d",             "Gateway": "<IP_ADDRESS>",             "GlobalIPv6Address": "",             "GlobalIPv6PrefixLen": 0,             "IPAddress": "<IP_ADDRESS>",             "IPPrefixLen": 16,             "IPv6Gateway": "",             "MacAddress": "02:42:ac:11:00:03",             "Networks": {                 "bridge": {                     "IPAMConfig": null,                     "Links": null,                     "Aliases": null,                     "NetworkID": "1a993567f768e80d7b422b5668595b0e2f08687b5b64be23effe39fb3eaecb09",                     "EndpointID": "b9509281cb441b0e19f347e4b07cadd40de256c1000b79863a95dac22234cc2d",                     "Gateway": "<IP_ADDRESS>",                     "IPAddress": "<IP_ADDRESS>",                     "IPPrefixLen": 16,                     "IPv6Gateway": "",                     "GlobalIPv6Address": "",                     "GlobalIPv6PrefixLen": 0,                     "MacAddress": "02:42:ac:11:00:03",                     "DriverOpts": null                 }             }         }     } ]

Could you also provide the container's log?

`[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-app-niceness.sh: executing...
[cont-init.d] 00-app-niceness.sh: exited 0.
[cont-init.d] 00-app-script.sh: executing...
[cont-init.d] 00-app-script.sh: exited 0.
[cont-init.d] 00-app-user-map.sh: executing...
[cont-init.d] 00-app-user-map.sh: exited 0.
[cont-init.d] 00-clean-logmonitor-states.sh: executing...
[cont-init.d] 00-clean-logmonitor-states.sh: exited 0.
[cont-init.d] 00-clean-tmp-dir.sh: executing...
[cont-init.d] 00-clean-tmp-dir.sh: exited 0.
[cont-init.d] 00-set-app-deps.sh: executing...
[cont-init.d] 00-set-app-deps.sh: exited 0.
[cont-init.d] 00-set-home.sh: executing...
[cont-init.d] 00-set-home.sh: exited 0.
[cont-init.d] 00-take-config-ownership.sh: executing...
[cont-init.d] 00-take-config-ownership.sh: exited 0.
[cont-init.d] 00-xdg-runtime-dir.sh: executing...
[cont-init.d] 00-xdg-runtime-dir.sh: exited 0.
[cont-init.d] 10-certs.sh: executing...
[cont-init.d] 10-certs.sh: exited 0.
[cont-init.d] 10-cjk-font.sh: executing...
[cont-init.d] 10-cjk-font.sh: exited 0.
[cont-init.d] 10-nginx.sh: executing...
[cont-init.d] 10-nginx.sh: exited 0.
[cont-init.d] 10-vnc-password.sh: executing...
[cont-init.d] 10-vnc-password.sh: exited 0.
[cont-init.d] 10-web-index.sh: executing...
[cont-init.d] 10-web-index.sh: exited 0.
[cont-init.d] filebot.sh: executing...
[cont-init.d] filebot.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] starting s6-fdholderd...
[services.d] starting certsmonitor...
[services.d] starting nginx...
[services.d] starting xvfb...
[nginx] starting...
[certsmonitor] disabling service: secure connection not enabled.
[xvfb] starting...
[services.d] starting x11vnc...
[services.d] starting statusmonitor...
[x11vnc] starting...
22/03/2019 11:38:49 passing arg to libvncserver: -rfbport
22/03/2019 11:38:49 passing arg to libvncserver: 5900
22/03/2019 11:38:49 passing arg to libvncserver: -rfbportv6
22/03/2019 11:38:49 passing arg to libvncserver: -1
22/03/2019 11:38:49 passing arg to libvncserver: -httpportv6
22/03/2019 11:38:49 passing arg to libvncserver: -1
22/03/2019 11:38:49 passing arg to libvncserver: -desktop
22/03/2019 11:38:49 passing arg to libvncserver: FileBot
22/03/2019 11:38:49 x11vnc version: 0.9.14 lastmod: 2015-11-14  pid: 776
[statusmonitor] no file to monitor: disabling service...
[services.d] starting logmonitor...
[services.d] starting openbox...
[logmonitor] no file to monitor: disabling service...
[openbox] starting...
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
22/03/2019 11:38:49 Using X display :0
22/03/2019 11:38:49 rootwin: 0x43 reswin: 0x200001 dpy: 0xbbab19e0
22/03/2019 11:38:49
22/03/2019 11:38:49 ------------------ USEFUL INFORMATION ------------------
22/03/2019 11:38:49 X DAMAGE available on display, using it for polling hints.
22/03/2019 11:38:49   To disable this behavior use: '-noxdamage'
22/03/2019 11:38:49
22/03/2019 11:38:49   Most compositing window managers like 'compiz' or 'beryl'
22/03/2019 11:38:49   cause X DAMAGE to fail, and so you may not see any screen
22/03/2019 11:38:49   updates via VNC.  Either disable 'compiz' (recommended) or
22/03/2019 11:38:49   supply the x11vnc '-noxdamage' command line option.
22/03/2019 11:38:49 X COMPOSITE available on display, using it for window polling.
22/03/2019 11:38:49   To disable this behavior use: '-noxcomposite'
22/03/2019 11:38:49
22/03/2019 11:38:49 Wireframing: -wireframe mode is in effect for window moves.
22/03/2019 11:38:49   If this yields undesired behavior (poor response, painting
22/03/2019 11:38:49   errors, etc) it may be disabled:
22/03/2019 11:38:49    - use '-nowf' to disable wireframing completely.
22/03/2019 11:38:49    - use '-nowcr' to disable the Copy Rectangle after the
22/03/2019 11:38:49      moved window is released in the new position.
22/03/2019 11:38:49   Also see the -help entry for tuning parameters.
22/03/2019 11:38:49   You can press 3 Alt_L's (Left "Alt" key) in a row to
22/03/2019 11:38:49   repaint the screen, also see the -fixscreen option for
22/03/2019 11:38:49   periodic repaints.
22/03/2019 11:38:49 GrabServer control via XTEST.
22/03/2019 11:38:49
22/03/2019 11:38:49 Scroll Detection: -scrollcopyrect mode is in effect to
22/03/2019 11:38:49   use RECORD extension to try to detect scrolling windows
22/03/2019 11:38:49   (induced by either user keystroke or mouse input).
22/03/2019 11:38:49   If this yields undesired behavior (poor response, painting
22/03/2019 11:38:49   errors, etc) it may be disabled via: '-noscr'
22/03/2019 11:38:49   Also see the -help entry for tuning parameters.
22/03/2019 11:38:49   You can press 3 Alt_L's (Left "Alt" key) in a row to
22/03/2019 11:38:49   repaint the screen, also see the -fixscreen option for
22/03/2019 11:38:49   periodic repaints.
22/03/2019 11:38:49
22/03/2019 11:38:49 XKEYBOARD: number of keysyms per keycode 7 is greater
22/03/2019 11:38:49   than 4 and 51 keysyms are mapped above 4.
22/03/2019 11:38:49   Automatically switching to -xkb mode.
22/03/2019 11:38:49   If this makes the key mapping worse you can
22/03/2019 11:38:49   disable it with the "-noxkb" option.
22/03/2019 11:38:49   Also, remember "-remap DEAD" for accenting characters.
22/03/2019 11:38:49
22/03/2019 11:38:49 X FBPM extension not supported.
Xlib:  extension "DPMS" missing on display ":0".
22/03/2019 11:38:49 X display is not capable of DPMS.
22/03/2019 11:38:49 --------------------------------------------------------
22/03/2019 11:38:49
22/03/2019 11:38:49 Default visual ID: 0x21
22/03/2019 11:38:49 Read initial data from X display into framebuffer.
22/03/2019 11:38:49 initialize_screen: fb_depth/fb_bpp/fb_Bpl 24/32/5120
22/03/2019 11:38:49
22/03/2019 11:38:49 X display :0 is 32bpp depth=24 true color
22/03/2019 11:38:49
22/03/2019 11:38:49 Listening for VNC connections on TCP port 5900
22/03/2019 11:38:49
22/03/2019 11:38:49 Xinerama is present and active (e.g. multi-head).
22/03/2019 11:38:49 Xinerama: number of sub-screens: 1
22/03/2019 11:38:49 Xinerama: no blackouts needed (only one sub-screen)
22/03/2019 11:38:49
22/03/2019 11:38:49 fb read rate: 1092 MB/sec
22/03/2019 11:38:49 fast read: reset -wait  ms to: 10
22/03/2019 11:38:49 fast read: reset -defer ms to: 10
22/03/2019 11:38:49 The X server says there are 10 mouse buttons.
22/03/2019 11:38:49 screen setup finished.
22/03/2019 11:38:49
The VNC desktop is:      ba46464d8bf0:0
PORT=5900

Have you tried the x11vnc '-ncache' VNC client-side pixel caching feature yet?
The scheme stores pixel data offscreen on the VNC viewer side for faster
retrieval.  It should work with any VNC viewer.  Try it by running:
x11vnc -ncache 10 ...

One can also add -ncache_cr for smooth 'copyrect' window motion.
More info: http://www.karlrunge.com/x11vnc/faq.html#faq-client-caching
[openbox] starting...
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[openbox] starting...
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[openbox] starting...
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[openbox] starting...
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
s6-svwait: fatal: timed out
[services.d] starting app...
[openbox] starting...
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
[services.d] done.
[openbox] starting...
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
[openbox] starting...
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
[openbox] starting...
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
[openbox] starting...
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
[openbox] starting...
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[openbox] starting...
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
[openbox] starting...
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
[openbox] starting...
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
[openbox] starting...
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
[openbox] starting...
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[openbox] starting...
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
[openbox] starting...
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
[openbox] starting...
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
[openbox] starting...
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
[openbox] starting...
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[openbox] starting...
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
[openbox] starting...
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
[openbox] starting...
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
[openbox] starting...
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
[openbox] starting...
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[openbox] starting...
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
[openbox] starting...
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
[openbox] starting...
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
[openbox] starting...
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
[openbox] starting...
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[openbox] starting...
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
[openbox] starting...
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
[openbox] starting...
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
[openbox] starting...
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
[openbox] starting...
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
[openbox] starting...
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
[openbox] starting...
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
[openbox] starting...
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
[openbox] starting...
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
[openbox] starting...
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[openbox] starting...
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
[openbox] starting...
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
[openbox] starting...
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
[openbox] starting...
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
[openbox] starting...
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
[openbox] starting...
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
[openbox] starting...
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
[openbox] starting...
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
[openbox] starting...
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
[openbox] starting...
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[openbox] starting...
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
[openbox] starting...
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
[openbox] starting...
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
[openbox] starting...
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
[openbox] starting...
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[openbox] starting...
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
[openbox] starting...
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
[openbox] starting...
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
[openbox] starting...
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
[openbox] starting...
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
[openbox] starting...
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
[openbox] starting...
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
[openbox] starting...
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
[openbox] starting...
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
[openbox] starting...
[app] starting FileBot...
s6-envdir: fatal: unable to envdir: Permission denied
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)
[openbox] starting...
How are you gentlemen? All your base are belong to us. (Openbox received signal 11)`

I just tried on openmediavault running on a VM and the container is working file.
Do you have any special in container's settings?
Did you tried to pull the image again and re-create the container?

Could it be that I have the docker root location on a drive that is not the primary drive?
Here is the fstab
'/dev/disk/by-label/raid3TBa /srv/dev-disk-by-label-raid3TBa ext4 defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2'

Apologies, I completely missed the question of re-pulling the image & re-creating the container ... yes I have re-pulled the image & re-created the container many times

I went back in & set the off nominal docker root drive mount options to what the sda drive settings are & no change ... same error code.
Next I'll try syncing the off nominal docker root data back to the nominal docker root & see what comes

Reverted to the default docker location & everything is working as desired. Looks like it has to do with the mountings.
Thank you very much for all your help

Great to see that it's now working for you.


Benchmark torchao and torch.compile (need torch 2.5)

vllm updated to use pytorch 2.5 recently, so we can benchmark torchao with torch.compile now (previously blocked by 2.5 update)

install most recent vllm: pip install https://vllm-wheels.s3.us-west-2.amazonaws.com/nightly/vllm-1.0.0.dev-cp38-abi3-manylinux1_x86_64.whl

make some small modifications to sglang:
https://gist.github.com/jerryzh168/bd65f122f24d5c92525f2504a1ff5870

install sglang from source

Benchmark

int8wo no compile:
python3 -m sglang.bench_latency --model meta-llama/Meta-Llama-3-8B --batch-size 1 --input 128 --output 8 --torchao-config int8wo
max_total_num_tokens=482059
Warmup ...
Prefill. latency: 0.06436 s, throughput:   1988.85 token/s
Decode.  latency: 0.05185 s, throughput:     19.29 token/s
Decode.  latency: 0.04700 s, throughput:     21.27 token/s
Decode.  latency: 0.04502 s, throughput:     22.21 token/s
Decode.  latency: 0.04504 s, throughput:     22.20 token/s
Decode.  latency: 0.04502 s, throughput:     22.21 token/s
Decode.  median latency: 0.04505 s, median throughput:     22.20 token/s
Total. latency:  0.388 s, throughput:    350.14 token/s
Benchmark ...
Prefill. latency: 0.05367 s, throughput:   2385.12 token/s
Decode.  latency: 0.04498 s, throughput:     22.23 token/s
Decode.  latency: 0.04530 s, throughput:     22.08 token/s
Decode.  latency: 0.04516 s, throughput:     22.15 token/s
Decode.  latency: 0.04511 s, throughput:     22.17 token/s
Decode.  latency: 0.04504 s, throughput:     22.20 token/s
Decode.  median latency: 0.04507 s, median throughput:     22.19 token/s
Total. latency:  0.369 s, throughput:    368.20 token/

int8wo with compile
python3 -m sglang.bench_latency --model meta-llama/Meta-Llama-3-8B --batch-size 1 --input 128 --output 8 --torchao-config int8wo --enable-torch-compile
Warmup ...
Prefill. latency: 0.05634 s, throughput:   2271.98 token/s
Decode.  latency: 0.00890 s, throughput:    112.38 token/s
Decode.  latency: 0.00857 s, throughput:    116.66 token/s
Decode.  latency: 0.00843 s, throughput:    118.68 token/s
Decode.  latency: 0.00844 s, throughput:    118.51 token/s
Decode.  latency: 0.00836 s, throughput:    119.59 token/s
Decode.  median latency: 0.00843 s, median throughput:    118.68 token/s
Total. latency:  0.116 s, throughput:   1174.76 token/s
Benchmark ...
Prefill. latency: 0.05326 s, throughput:   2403.52 token/s
Decode.  latency: 0.00880 s, throughput:    113.60 token/s
Decode.  latency: 0.00844 s, throughput:    118.55 token/s
Decode.  latency: 0.00839 s, throughput:    119.24 token/s
Decode.  latency: 0.00835 s, throughput:    119.76 token/s
Decode.  latency: 0.00829 s, throughput:    120.66 token/s
Decode.  median latency: 0.00839 s, median throughput:    119.24 token/s
Total. latency:  0.112 s, throughput:   1211.90 token/s

@jerryzh168 When this configuration is used for bench_latency, we previously observed significant fluctuations. You may also try using bench_serving to do a benchmark as well, thanks!

[2024-11-03 00:41:08 TP0] Init torch distributed begin.
[2024-11-03 00:41:08 TP0] Load weight begin. avail mem=78.58 GB
[rank0]: Traceback (most recent call last):
[rank0]:   File "/root/miniconda3/lib/python3.10/runpy.py", line 196, in _run_module_as_main
[rank0]:     return _run_code(code, main_globals, None,
[rank0]:   File "/root/miniconda3/lib/python3.10/runpy.py", line 86, in _run_code
[rank0]:     exec(code, run_globals)
[rank0]:   File "/home/ubuntu/sglang-4/python/sglang/bench_latency.py", line 551, in
[rank0]:     raise e
[rank0]:   File "/home/ubuntu/sglang-4/python/sglang/bench_latency.py", line 549, in
[rank0]:     main(server_args, bench_args)
[rank0]:   File "/home/ubuntu/sglang-4/python/sglang/bench_latency.py", line 513, in main
[rank0]:     work_func(server_args, port_args, bench_args, 0)
[rank0]:   File "/home/ubuntu/sglang-4/python/sglang/bench_latency.py", line 384, in latency_test
[rank0]:     model_runner, tokenizer = load_model(server_args, port_args, tp_rank)
[rank0]:   File "/home/ubuntu/sglang-4/python/sglang/bench_latency.py", line 136, in load_model
[rank0]:     model_runner = ModelRunner(
[rank0]:   File "/home/ubuntu/sglang-4/python/sglang/srt/model_executor/model_runner.py", line 155, in init
[rank0]:     self.load_model()
[rank0]:   File "/home/ubuntu/sglang-4/python/sglang/srt/model_executor/model_runner.py", line 240, in load_model
[rank0]:     monkey_patch_vllm_dummy_weight_loader()
[rank0]:   File "/home/ubuntu/sglang-4/python/sglang/srt/utils.py", line 452, in monkey_patch_vllm_dummy_weight_loader
[rank0]:     from vllm.model_executor.model_loader.loader import (
[rank0]: ImportError: cannot import name 'DeviceConfig' from 'vllm.model_executor.model_loader.loader' (/root/miniconda3/lib/python3.10/site-packages/vllm/model_executor/model_loader/loader.py)
[rank0]:[W1103 00:41:09.547081948 ProcessGroupNCCL.cpp:1250] Warning: WARNING: process group has NOT been destroyed before we destruct ProcessGroupNCCL. On normal program exit, the application should call destroy_process_group to ensure that any pending NCCL operations have finished in this process. In rare cases this process can exit before this point and block the progress of another member of the process group. This constraint has always been present,  but this warning has only been added since PyTorch 2.4 (function operator())
When I tried to follow your instructions, I got this error.

@CortexEdgeUser that seems reasonable since https://github.com/vllm-project/vllm/blob/main/vllm/model_executor/model_loader/loader.py does not have DeviceConfig, I'm not sure when this is removed, I think this is probably need to import from https://github.com/vllm-project/vllm/blob/ca9844b340f45f23f8d30fdce23777d215ad987c/vllm/config.py#L1158

@CortexEdgeUser that seems reasonable since https://github.com/vllm-project/vllm/blob/main/vllm/model_executor/model_loader/loader.py does not have DeviceConfig, I'm not sure when this is removed, I think you probably need to import from https://github.com/vllm-project/vllm/blob/ca9844b340f45f23f8d30fdce23777d215ad987c/vllm/config.py#L1158, I didn't encounter this specific error though

I used a commit from before the changes, and it worked well; however, I’m encountering issues with tp > 1, but this is also the case with vLLM.

torch 2.5 has been supported via this PR https://github.com/sgl-project/sglang/pull/2069

Let us close this one as the instructions are outdated now. Torch 2.5 has been supported in the main branch. We can create a new one for future results.


✨ Migration: Ams User Manual

Overview
Because not everyone knows how to use Ams Date Picker from day one, we are making this to introduce the feature (especially magic modifiers) and for users to check when needed. It should be a page-wise modal as it has fairly enough content to display.
This component should cover on the entire page as a sidebar and it should not block the mouse event on original body (if possible) as user may check the manual and do the input at the same time.
Instruction
The original version of DatePickerHelper is not formatted well (because it is using the pure HTML, which is inefficient on editing and maintaining). I am planning to separate the manual part to several Markdown files (and parse them in the Ams User Manual component) for maintainability.
Tasks

[x] Sidebar modal frame.
[ ] Frame styling.
[ ] Content styling.

Design

For v0.0.1, the migration will be limited to a headless branch of user manual (and being merged into headless package).


Agenda typescript implementation

Before the question, Thanks for the boilerplate it has been a breeze to use.
Is there any plan to implement agenda with typescript since it has a DefinetlyTyped type definitions available?

Hi @Jfelix61
I'm glad you liked this boilerplate.
Sure, we can add the TS definitions for agenda and the corresponding types in the codebase it should be pretty easy.

I can add it.

@Jfelix61 that would be great!

Solved #19


Migrate to null-safety

Taking the liberty to create a pull request from @dqhieuu's null-safety fork.
Can we please merge this asap? This is my app's last dependency which hasn't yet implemented null-safety.

any possibility of merging this for null safety support?


feat(ProLabel): Changes text color to 'background-current'

Overview

Changes <ProLabel> text color to pull from background-current css variable

PR Checklist

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

🚀 Styleguide deploy preview ready!https://60fee7e740e5040783b2924d--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.4.73-alpha.1b0bab.0@codecademy/gamut-labs@19.16.11-alpha.1b0bab.0@codecademy/gamut@35.4.0-alpha.1b0bab.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://60fef0fcc14e1915f2aa3cb3--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.5.9-alpha.dbb5a7.0@codecademy/gamut-labs@19.18.1-alpha.dbb5a7.0@codecademy/gamut@35.8.0-alpha.dbb5a7.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://61089254415ce01e2a626abc--gamut-preview.netlify.appDeploy Logs


Final Jupyter Notebook Setup

Set up Jupyter notebook for final analysis, including sections for
Project description

introduction
research questions and hypotheses
methods

Set Up

package/module imports
data loading
data cleaning
data processing

Analysis

NER
clustering
topic modeling
similarity analysis

Reflection/Discussion

Gonna spend the day on the homeworks, but I'll hopefully have this setup before the EOD tomorrow.


Schema best practice updates; example updates; ToC changes; Reference…

Opening this PR in response to the need for updated best-practice guidance around user-defined schemas.
See https://github.com/cockroachdb/docs/pull/9487/files/0dc7f87c6dd97fa04017c2e0687d08f0dc22d099#r565570489.
Changes include:

Updated best-practice guidance for databases, user-defined schemas, and tables.
A new user, schema, and table in the examples in the "Create a Database", "Create a User-defined Schema" and "Create a Table" pages.

The PR also includes:

Minor updates to the end of pages (See also-> What's next?).
Minor updates to formatting and wording on a few pages.

This change is

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/3375b3cc0530cb9c8cdabe4fd6bbb858aae489ce/
Edited pages:

v21.1/bulk-delete-data.md
v21.1/connect-to-the-database.md
v21.1/connection-parameters.md
v21.1/connection-pooling.md
v21.1/delete.md
v21.1/developer-guide-overview.md
v21.1/force-index-selection.md
v21.1/hash-sharded-indexes.md
v21.1/indexes.md
v21.1/install-client-drivers.md
v21.1/limit-offset.md
v21.1/pagination.md
v21.1/query-order.md
v21.1/schema-design-database.md
v21.1/schema-design-indexes.md
v21.1/schema-design-overview.md
v21.1/schema-design-schema.md
v21.1/schema-design-table.md
v21.1/schema-update-modify-objects.md
v21.1/schema-update-remove-objects.md
v21.1/secure-a-cluster.md
v21.1/selection-queries.md
v21.1/start-a-local-cluster.md


How do you update your publisher page information

Can anyone tell me how to update my vscode marketplace publisher description and photo? I wanted to use a new profile image but can't remember anymore where you set this. I think it was somewhere on Azure.
It would be good if this could be edited inside your marketplace profile.

Found


Update meeting-policies-in-teams.md

confirmed with Andrii Matukhno

@JohanFreelancer9 Copy editing is needed for this PR. Thanks.

@tonysmit PR has been copyedited and is ready for final review, could you please check and merge? Thanks!


Terminal token name: "x" not found

I am following up on this issue
https://github.com/SAP/chevrotain/issues/896
And of its solutions as explained in the following answer
https://github.com/SAP/chevrotain/issues/896#issuecomment-461627416
From which I did not obtain the expected result, following the following example:
https://github.com/SAP/chevrotain/tree/master/examples/parser/serialized_grammar
Getting the following result or error message.
Unexpected token *
Important note, I am working on Angular 6 and TypeScript
My questions are the following:

Is there a way in which the token was not affected at the time of making a mystification in my project?
In case the number 1 is correct, what would be a clear example?
There are some clear examples of typescript that are related to https://github.com/SAP/chevrotain/tree/master/examples/parser/serialized_grammar

I appreciate any help you can provide

Hello @jgromero7
I don't think I can add anything beyond the discussion in #896 there just are not many new details in this issue. did you try "ng eject" and customize the minification options?

https://github.com/angular/angular-cli/pull/5192

My suggestion is that you would re-produce the problem in a small example repo which can be cloned and inspected I don't have enough (any 😄 ) familiarity with angular CLI tools to answer this without debugging the code...

Hola @bd82 According to what is mentioned in your answer, I attached the link of the repository with the reply of what I am doing in the project.
Repository
I can make use of all the resources when I use
ng build
But when I use the following command
ng build --prod --build-optimizer --output-hashing all
Errors begin to appear, I hope you can help me with this.
All the logic of the token is in the following route
Service
I appreciate any help and I hope I have provided all the details

Hello.
This is not really a minimal example, it is your whole repo 😄
Option 1 - Serialization
Anyhow I am not seeing that you are using serialization of the grammar at all:

https://github.com/jgromero7/parsing-string-sql/blob/8e305de0fda53ecf1c5612316a7d9ce80163d926/src/app/services/parsing-string.service.ts#L75-L79

Option 2 - Custom Webpack Configuration
It seems like the Angular CLI are in the process of removing the ng eject option so it makes it even harder to provide custom webpack configurations. But there also seems to be a 3rd party package which may allow providing custom webpack configurations:

https://github.com/manfredsteyer/ngx-build-plus

So you may be able to use this to modify the minification options to avoid breaking your Chevrotain grammar.
Option 3 - Separate the Parser's build.
You could also try implementing your Parser as a separate module, i.e not part of your angular
application, that way you could build/bundle it using more customizable build tools (e.g using webpack directly). The question in that case if you could then consume it in your angular app
in a manner that would avoid re-bundling it and breaking things again, so we are kind back to the original problem of angular-cli limited custom workflows 😢

Closing this due to inactivity, re-open if any more help is needed


Set MIX_ENV to test in continuous integration

This avoids recompiling the code twice, since mix compile runs by default in the development environment, then mix test compiles the code again, but in the test environment, before running the tests.
You can see here that both the Ensure the Elixir code compiles and Run tests steps compiled the code.
I forgot about that in my previous PR :see_no_evil:.

The issue with the CI is that the cache is restored, but mix.lock is missing since mix deps.get wasn't executed due to the cache hit. Is there a reason for not having mix.lock tracked in the project? This would solve the issue.

We don't have mix.lock in the repo because two dependencies (oban_pro y oban_web) depend on an env. variable. That's because they require a license.

I'm not familiar enough with optional dependencies to know if there could be another approach for this. I revived one old thread from Elixir forum.

I ended up discussing about this on the Elixir Slack in #oban and there doesn't seem to be a simple solution regarding Oban Pro dependencies, tracking mix.lock and caching in the CI. I suggest getting rid of the caching in the CI. What do you think?

Sounds good. Not ideal to compile the dependencies every time, but we'll have to live with that. At least for now.
Thanks for this @dmarcoux! Having CI is wonderful!

I pushed a fix, the CI is working again. The code is also compiled only once.

Thanks!


Implement groundworks for special registers and implement FF00 and FF07

For a more precise description, as well as guideline, please see #21.

Had the wrong mental model. This is not the correct way to go about that.

This has to be tackled in another way.


Getting 422 error from Laravel on upload

Vue2-dropzone Version: 2.3.5
Node Version (node -v): 6.11.0
NPM Version (npm -v):  3.10.10
OS: Linux 16.04 - Chrome

Description:
The component on the client side, but I'm getting a 422 error saying: "you did not send the required json in the body"
Steps To Reproduce:
Configured as follows:
Vue code
    <dropzone :id="thisRef" :use-font-awesome="true"
    :url="url" v-on:vdropzone-success="showSuccess">
        <!-- Optional parameters if any! -->
        <input type="hidden" name="token" value="xxx123">
    </dropzone>

Script code:
<script>
import Dropzone from 'vue2-dropzone'

export default {
  components: {
    Dropzone
  },

  props: {
    id: {
      type: [String, Number],
      required: true
    },
    type: {
      type: String,
      required: true
    }
  },

  computed: {
    url: function () {
      return this.getEndpoint('/upload/' + this.type.toLowerCase().trim() + '/' + this.id)
    }
  },

  methods: {
    showSuccess: function (file) {
      console.log('A file was successfully uploaded', file)
    },
    onError: function (file) {
      console.log('A file was NOT uploaded', file)
    }
  },

  data () {
    return {
      thisRef: this.type.toLowerCase() + '-uploader',
      localType: this.type.toLowerCase().trim(),
      headerInfo: {   // Not used
        'Access-Control-Allow-Origin': this.url,
        'Access-Control-Allow-Methods': 'GET, POST, OPTIONS, PUT, DELETE',
        'Access-Control-Allow-Headers': 'Origin, X-Requested-With, Content-Type, Accept, X-File-Name, X-File-Size, X-File-Type'
      },
      fileData: {
        type: this.type,
        id: this.id,
        caption: null
      }
    }
  }
}
</script>

On error output:

On uploading any file, I get a 422 response, yet the file gets to the server, but is rejected, since I can see that in the error response. I'm assuming I've not configured something correctly?

Gday @adavie1
Nothing sticks out as immediately obvious. Perhaps try removing the additional input from the html?
<dropzone :id="thisRef" :use-font-awesome="true"
    :url="url" v-on:vdropzone-success="showSuccess">
</dropzone>

Also doing some googling this issue also appears with Laravel occassionally when you have validation on the server-side, so perhaps check if you have any validation occurring in your laravel code and if that is failing for some reason....
Hope that helps

Thanks @rowanwins in the end, I hacked the JsonApiMiddleware on Laravel. Got it all working. Brilliant component BTW.


Alternative paths for user friendly project organization (add project_path attribute to component element)

Combination of base_path, pack_path, project_path could provide user friendly view in form of flat folder structure in workspace.
Flat folder structure - structure without unnecessary nested folders without files.

David, thanks for the suggestion.  Could you take the time to create an example, so that we better understand the request.  It can be pretty simple.
Right now we show the Cclass as the identifier for a component group in the project window.  I assume you would like to achieve something similar.

@DavidJurajdaNXP , base_path is not the one work for shape project tree view. To provide user friendly view, "project_path" is enough.

This seems to be related how IDE show software components (see here https://github.com/Open-CMSIS-Pack/Open-CMSIS-Pack-Spec/issues/93#issuecomment-1060349943)
Is this correct?  If not, what is the underlying problem you try to solve?

I believe the requirement here is about that the physical directory structure, allowing to control the destination of files belonging to a component when copied into the project folder (see #93).

Yes, both #95 and #93 are actually consequence of NXP data model "project_path" attribute.

Let's limit scope of this ticket only to project_path.
project_path = data driven project explorer view
According to preliminary agreement in discussion #93 project_path will be introduced into standard, but actual usage will be tool specific.
Project_path must be applied to file paths and also to include paths in order to preserve data integrity.
In case of category="header" there should be way how to disable automatic include path generation.
<file category="header" name="ports/cmsis-driver/netif/ethernetif.h"/>
Project path is increasing complexity and in order to guarantee data integrity both layouts must be tested by pack vendor. It is price for this feature.
About the "Project View". I think it might be useful to have actually more views in IDE:

component based view - showing content of components
file based view - showing physical code organization in folders

I would call it views on different levels of abstraction. Another level might be "CMSIS layers".

Agreed with @DavidJurajdaNXP , there can be 2 views in IDE workspace project tree

component layout.
cclass, cgroup, csub can be used for this. With this information, developers can directly know the provenance and classification of the component(which pack it belongs to)

source tree layout
project_path can be used to contruct it.
It is an organization of the source under a component. Sometimes it could be untidy if sources are placed flat, like

We support this request.
For most of the packs we need: https://github.com/Open-CMSIS-Pack/Open-CMSIS-Pack-Spec/issues/106
But we will deliver our example projects as packs.
And in these packs, we want the files to be copied in the user section of the project.
It is a bit like attr=template but we want it:

for files that are not template but source and header
mandatory (copy by the tool)
flexible: indicate the path

Change Request:
add component attribute "project_path". The implementation is optional and tools specific and will not change the virtual view.
@DavidJurajdaNXP and @tcsunhao  can you please validate this summary.
It is my understanding that this attribute is somewhat comparable to https://github.com/Open-CMSIS-Pack/Open-CMSIS-Pack-Spec/issues/30 however affecting all configuration files of a component, rather than being specified on a per file basis and it only affects the path but not the filename.

@jkrech , Thanks for approving this formally.
The project_path will affect all configuration files as well as other files when NXP tools use it to construct standalone project.

@jkrech , Thanks for approving this formally.
The project_path will affect all configuration files as well as other files when NXP tools use it to construct standalone project.

I understand that you want to fill 2 needs:

"simplify" the IDE view by applying project_path instead of the real file system path that can be longer
create a "standalone folder" with all the necessary files copied according to the project_path organization

But, the point which is unclear to me is: what about files going into RTE folder ?
Do you still put them in RTE folder ?
By the way, I assume this is an optional attribute.

@fred-r, I think you are misunderstanding the feature suggested by @tcsunhao .
The projectPath attribute can be used by tools to copy both the config files as well as the component files  of a component into a physical subdirectory of the project directory as specified by projectPath. The config files are copied along the component files and not into any  directory.
The expectation is that a "virtual view" will continue display the files related to a component, and not the physical location of files on disk.

Thanks for the explanation of @jkrech which is accurate and complete.
The projectpath is optional. Default value could be the real physical path of file.
Related files inside RTE folder, like startup_MK64F12.s(whose NXP project path is "startup"), in real folder, it is located in RTE\iar\Device\MK64FN1M0VLL12, in project explorer view, it can be showed listed inside "startup".


sync: release 0.37.x

What type of PR is this?
Any specific area of the project related to this PR?
What this PR does / why we need it:
Cherry picks:

https://github.com/falcosecurity/falco/pull/3032
https://github.com/falcosecurity/falco/pull/3033
https://github.com/falcosecurity/falco/pull/3015
https://github.com/falcosecurity/falco/pull/3034

from master.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
NONE

/milestone 0.37.0
We only miss libs 0.14.2 bump now.

/unhold

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: FedeDP, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [FedeDP,leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: FedeDP, jasondellaluce, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [FedeDP,jasondellaluce,leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment