Unable to start container. Error message: No drive letters are avaliable

Have a site running using App Service for Windows Containers. I made some code changes in VS 2019 and republished my container. The app service saw the change and pulled over the new container, but it will not start.
This error is shown repeatedly in the Container Settings log:
07/11/2019 18:04:33.988 INFO - Site: ct35docker - Cancelling pending tasks.
07/11/2019 18:04:33.988 INFO - Site: ct35docker - Creating container image
07/11/2019 18:04:34.049 INFO - Site: ct35docker - Purging after container failed to start
07/11/2019 18:04:34.049 ERROR - Site: ct35docker - Unable to start container. Error message: No drive letters are avaliable
What drive letter is it looking for?

@rdorris Hi, thanks for reaching out to us. Could you please share the document if you are referring to one so that we can address the issue quickly? Thanks.

Probably was the wrong place to post the issue. I'm having a problem in the usage of App Service for Windows Containers. Not a documentation issue.

@rdorris Hi, I am handling this issue to the right person ^^ @SnehaAgrawal-MSFT  Please take a look of this issue. Thanks.

@rdorris Thanks again for your query and reaching out to us through multiple channels. Since we typically try to keep the Azure-Docs channel scoped to feedback directly about the docs. We will now proceed to close this thread here and will continue to work here


Use open range version

Use an open range for the package's version to minimise clashing with other requirements for six from other parent and peer dependencies

Could we please get this merged? I've confirmed that it works and it unblocks using this with recent versions of pyramid. Thanks!


Florida REST URL by GCC Args + NodeJS Florida Script

@timiblossom @ipapapa
I transformed the request into a macro parameter called FLORIDA_REQUEST so we can pass by parameter to the compiler, i did this because i have this file into a server so i can expose the URL and dont need write a proxy, it gives more flexibility to users.
Also added a simple script showing how to pass the CFLAG spaced(with is tricky in C :-) and that NodeJS Script to run Florida. Also added a config file with Florida provider that could serve as sample to other developers.
Cheers,
Diego Pacheco

@shailesh33  DONE, did your changes.

LGTM

Can you please re-submit to Dev branch if that does take you much time?  We are still working on our branching convention and currently Dev is for new changes, not master.  Thanks

sure @timiblossom I will do it later today.

@timiblossom  DONE ( new PR #203) -> https://github.com/Netflix/dynomite/pull/203

@timiblossom
How often you guys push to master?

We will use Gitflow soon - now it is just master, dev and some ad-hoc branches


[Dubbo-5130] complete lfu cache proposal

What is the purpose of the change
fix https://github.com/apache/dubbo/issues/5130
Brief changelog
XXXXX
Verifying this change
XXXXX
Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Make sure there is a GITHUB_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GITHUB issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x] Format the pull request title like [Dubbo-XXX] Fix UnknownException when host config not exist #XXX. Each commit in the pull request should have a meaningful subject line and body.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[x] Run mvn clean install -DskipTests=false & mvn clean test-compile failsafe:integration-test to make sure unit-test and integration-test pass.
[x] If this contribution is large, please follow the Software Donation Guide.

Codecov Report

Merging #5734 into master will decrease coverage by 0.07%.
The diff coverage is 72.56%.

@@             Coverage Diff              @@
##             master    #5734      +/-   ##
============================================
- Coverage     61.43%   61.36%   -0.08%
- Complexity      497      498       +1
============================================
  Files           932      931       -1
  Lines         38098    38060      -38
  Branches       5500     5500
============================================
- Hits          23405    23354      -51
- Misses        12149    12179      +30
+ Partials       2544     2527      -17

Impacted Files
Coverage Δ
Complexity Δ

...a/org/apache/dubbo/cache/support/lfu/LfuCache.java
0% <0%> (ø)
0 <0> (?)

...pache/dubbo/cache/support/lfu/LfuCacheFactory.java
0% <0%> (ø)
0 <0> (?)

...n/java/org/apache/dubbo/common/utils/LFUCache.java
79.61% <79.61%> (ø)
0 <0> (?)

...g/context/properties/DefaultDubboConfigBinder.java
0% <0%> (-100%)
0% <0%> (ø)

.../context/properties/AbstractDubboConfigBinder.java
0% <0%> (-92.31%)
0% <0%> (ø)

...che/dubbo/remoting/transport/mina/MinaChannel.java
39.47% <0%> (-10.53%)
15% <0%> (-1%)

...ng/transport/dispatcher/all/AllChannelHandler.java
62.06% <0%> (-6.9%)
0% <0%> (ø)

.../remoting/transport/netty4/NettyClientHandler.java
57.62% <0%> (-6.78%)
0% <0%> (ø)

.../org/apache/dubbo/remoting/ExecutionException.java
15.78% <0%> (-5.27%)
0% <0%> (ø)

...pache/dubbo/registry/support/AbstractRegistry.java
78.35% <0%> (-2.99%)
0% <0%> (ø)

... and 18 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 60e72bf...e8d07c6. Read the comment docs.

What is the purpose of the change
fix #5130
Brief changelog
XXXXX
Verifying this change
XXXXX
Follow this checklist to help us incorporate your contribution quickly and easily:

[x]  Make sure there is a GITHUB_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GITHUB issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x]  Format the pull request title like [Dubbo-XXX] Fix UnknownException when host config not exist #XXX. Each commit in the pull request should have a meaningful subject line and body.
[x]  Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x]  Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[x]  Run mvn clean install -DskipTests=false & mvn clean test-compile failsafe:integration-test to make sure unit-test and integration-test pass.
[x]  If this contribution is large, please follow the Software Donation Guide.

Hello， I am the developer of dubbo. I see your commits.  Can you get your contact for more information？

@cvictory hi, do you mean something like wechat? my id: arse554321


Remove the black bar from the full screen window

The black bar on the top of the full screen view doesn't serve any apparent purpose. Consider removing it.
Screenshot for reference:

I can only see a black bar at the top on one device that has a notch in its screen (for the front camera). There, this black bar is only visible in vertical mode, and it probably makes sense to have this bar, because otherwise the notch would be making a small part of the document unreadable.
Maybe, more detail about the device where the problem was encountered would be helpful.


test Oracle's vfio-user client with libvfio-user

Current status: the qemu code never receives the response to the initial VFIO_USER_VERSION. Seems to be an issue with assumptions over fd callback handling in qemu, so we're blocked on that getting sorted.

Current status: with my PR against oracle qemu, current libvfio-user master works with the gpio server

Using @jlevon 's PR, Oracle QEMU doesn't handle region capabilities, see https://libvfio-user.slack.com/archives/C01AFGCSPTR/p1607598616185900 for more details.

BAR4 and BAR5 have been removed from SPDK, they're used for MSI-X, I fixed that, see https://libvfio-user.slack.com/archives/C01AFGCSPTR/p1607614872190000 for more details.

After fixing the BAR4/5 problem I hit the following error:
qemu-system-x86_64: -device vfio-user-pci,socket=/var/run/muser/domain/muser0/8/cntrl: vfio VFIO user </var/run/muser/domain/muser0/8/cntrl>: Failed to set up TRIGGER eventfd signaling for interrupt ERR-0: VFIO2
...
/root/src/qemu/hw/vfio/pci.c:591:vfio_msix_vector_release: Object 0x565048818950 is not an instance of type vfio-pci
./orcl.sh: line 3: 225891 Aborted

The first message is a warning, I debugged this a bit and it seems to fail when libvfio-user validates the IRQ:
250     // Ensure irq_set's start and count are within bounds.
251     if ((irq_set->start >= vfu_ctx->irq_count[irq_set->index]) ||
252         (irq_set->start + irq_set->count > vfu_ctx->irq_count[irq_set->index])) {
253         vfu_log(vfu_ctx, LOG_DEBUG, "bad IRQ start/count\n");
254         return -EINVAL;
...
(gdb) p irq_set->start
$10 = 0
(gdb) p irq_set->index
$11 = 3
(gdb) p vfu_ctx->irq_count[irq_set->index]
$12 = 0
(gdb) p irq_set->count
$13 = 1

I'll continue looking into it to see what's wrong.
Regarding the assertion later on, most likely it's related to the IRQ warning earlier on.

I've hacked SPDK and QEMU (https://github.com/tmakatos/spdk/tree/vfio-user and https://github.com/tmakatos/qemu/tree/vfio-user-integration) and the VM boots but it fails to probe the NVMe controller. We still need to fix the FD passing issue, and look at the interrupts problem.

@swapnili is looking at fixing mpqemu to pass file descriptors for DMA regions.

With a few hacks we've got it working (https://libvfio-user.slack.com/archives/C01AFGCSPTR/p1608305848234000?thread_ts=1608223042.228100&cid=C01AFGCSPTR): SPDK now works with mpqemu.


Add ABIs for CoboSafe

Please decode all methods of Cobo safe module
Contract Address: https://rinkeby.etherscan.io/address/0x2563776361bd6334ce4eb1f9edc71ca81a444f54#code
Many Thanks

Is that module only on rinkeby or also in mainnet?

it's only on rinkeby right now, but will be deployed on mainnet after tested thoroughly.

Ok! I'm adding it to rinkeby. So for next time, as long as you start using it after it's on Etherscan/sourcify it will be picked by the service

Indeed, I've just checked and the ABI is already in our service 😉

Thanks a lot!!


Facing OOM error for training and slow training

I have four NVIDIA 1080TI and I'm running the training script by  python train.py configs/car_auto_T3_train_train_config configs/car_auto_T3_train_config --dataset_root_dir KITTI/    with  batch_size=16  and  NUM_GPU=4 . After a few minutes I get OOM error with the following stats:
tensorflow/core/common_runtime/bfc_allocator.cc:929] Stats:
Limit:<PHONE_NUMBER>8
InUse:<PHONE_NUMBER>
MaxInUse:<PHONE_NUMBER>
NumAllocs:                   31169
MaxAllocSize:            732806656

I tried  batch_size=8  also same thing happens but when I chose  batch_size=4  it works and allocates around 8.5 GB of memory on each GPU. I also checked that GPUs are ideal before running the script. Since the default batch size is 4 with 2 GPUs, I have this impression that with 4 GPUs I can have batch size 16. Plus, the time cost in batch size equal to 4 is 298.297750 which is slow for 1717 epoch and will take around 5 days. Is this a normal behavior?

Hi @Farzin-Negahbani, Thanks for your interest. The default batch size is 4 on two GPUs (two samples per GPU). In your case, batch_size=8 and num_gpu=4 should work. Could you help to provide more information? During your training, is there any other process that consumes GPU memory already (when you check using nvidia-smi)? How many threads does your CPU support? Besides the batch_size and num_gpu, are there any other modifications?  Thanks,


pyarrow 10.0.1 is missing libarrow_python.so

Describe the bug, including details regarding any error messages, version, and platform.
Builds with pyarrow as a dependency are not able to build with the most recent release of pyarrow.
The error states the following:
.../libarrow_python.so needed by ..., missing and no know rule to make it
If anyone knows how I can resolve this error so I can support pyarrow10, please let me know!
Component(s)
Python

Can you provide a bit more detail? Do you have a problem running pyarrow itself, or with another package depending on pyarrow? (assuming the second since I see your linked turbodbc PR) Is it when packaging another packge? How did you install pyarrow? etc

I see that pyarrow is installed in the environment when I debug. pip list shows
...
pyarrow            10.0.1
...

Unfortunately, this is for the turbodbc and the issue occurs during the Earthly CI flow which utilizes mamba to install pyarrow. The error occurs when trying to build turbodbc with the following command
 cmake -DBOOST_ROOT=\${CONDA_PREFIX} -DBUILD_COVERAGE=ON -DCMAKE_INSTALL_PREFIX=./dist  -DPYTHON_EXECUTABLE=\$(which python) -GNinja .. && ninja && cmake --build . --target install && cd dist && python setup.py sdist
I'll include the relevant section of the build failed output below
 -- Found PkgConfig: /opt/conda/envs/turbodbc-dev/bin/pkg-config (found version "0.29.2")
              +build *failed* | -- Found /opt/conda/envs/turbodbc-dev/lib/libarrow.so in /opt/conda/envs/turbodbc-dev/lib
              +build *failed* | -- Found the Arrow core library: /opt/conda/envs/turbodbc-dev/lib/libarrow.so
              +build *failed* | -- Found the Arrow Python library: ARROW_PYTHON_LIB_PATH-NOTFOUND
              +build *failed* | -- Detecting unixODBC library
              +build *failed* | --   Found header files at: /opt/conda/envs/turbodbc-dev/include
              +build *failed* | --   Found library at: /opt/conda/envs/turbodbc-dev/lib/libodbc.so
              +build *failed* | CMake Warning (dev) at /opt/conda/envs/turbodbc-dev/share/cmake-3.25/Modules/FindPackageHandleStandardArgs.cmake:438 (message):
              +build *failed* |   The package name passed to `find_package_handle_standard_args` (PkgConfig)
              +build *failed* |   does not match the name of the calling package (Arrow).  This can lead to
              +build *failed* |   problems in calling code that expects `find_package` result variables
              +build *failed* |   (e.g., `_FOUND`) to follow a certain pattern.
              +build *failed* | Call Stack (most recent call first):
              +build *failed* |   /opt/conda/envs/turbodbc-dev/share/cmake-3.25/Modules/FindPkgConfig.cmake:99 (find_package_handle_standard_args)
              +build *failed* |   cmake_scripts/FindArrow.cmake:26 (include)
              +build *failed* |   cpp/turbodbc_arrow/CMakeLists.txt:12 (find_package)
              +build *failed* | This warning is for project developers.  Use -Wno-dev to suppress it.

              +build *failed* | -- Found /opt/conda/envs/turbodbc-dev/lib/libarrow.so in /opt/conda/envs/turbodbc-dev/lib
              +build *failed* | -- Found the Arrow core library: /opt/conda/envs/turbodbc-dev/lib/libarrow.so
              +build *failed* | -- Found the Arrow Python library: ARROW_PYTHON_LIB_PATH-NOTFOUND
              +build *failed* | -- Configuring done

@david-engelmann the way libarrow_python.so is package has changed in 10.0 (it is now part of the python package), so I assume that turbodbc will have to update their build scripts to follow that change.

We need to use pyarrow.get_include(), pyarrow.get_libraries() and pyarrow.get_library_dirs() to find libarrow_python.
See also: https://arrow.apache.org/docs/python/integration/extending.html#c-api

@kou I was able to find the ARROW_PYTHON_SHARED_LIB path but I can't find the ARROW_PYTHON_STATIC_LIB which is the libarrow_python.a.

We need to use pyarrow.get_include(), pyarrow.get_libraries() and pyarrow.get_library_dirs() to find libarrow_python.
See also: https://arrow.apache.org/docs/python/integration/extending.html#c-api

I added those to the setup.py file of turbodbc, you can check it out here.

I've commented on the pull request.


Add builtin target support for STM32H750

Add support for STM32H750
Same as STM32H743 but with only one flash sector of 128K.
Adding a new builtin target because the Keil.STM32H7xx_DFP v3.1.1 CMSIS Pack flash loader is broken for at least this sub-family.
Ref: #1700
Also fix the existing targets stm32h743xx and stm32h723xx which had incorrect sector sizes specified and a bug in reading the security status.

Tested this with a NUCLEO-H753ZI and everything worked as expected


More errors with elaborated descriptions.

Incoming!

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #109. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://nnstreamer.mooo.com/.

:octocat: cibot: @myungjoo, c/src/ml-api-inference-pipeline.c includes bug(s). Please fix incorrect coding constructs in your commit before entering a review process.

:octocat: cibot: @myungjoo, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnstreamer.mooo.com/nnstreamer-api/ci/repo-workers/pr-checker/109-202111231904540.061007976531982-2ecc03358b92a187088bab5dd025cb8efab55ae7/.

:octocat: cibot: @myungjoo, c/src/ml-api-inference-pipeline.c includes bug(s). Please fix incorrect coding constructs in your commit before entering a review process.

:octocat: cibot: @myungjoo, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnstreamer.mooo.com/nnstreamer-api/ci/repo-workers/pr-checker/109-202111241859310.65841102600098-3c4f0b1e7c50b57a4f2b745e1392bd62efcce9a0/.

:octocat: cibot: @myungjoo, c/src/ml-api-inference-pipeline.c includes bug(s). Please fix incorrect coding constructs in your commit before entering a review process.

:octocat: cibot: @myungjoo, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnstreamer.mooo.com/nnstreamer-api/ci/repo-workers/pr-checker/109-202111252011510.36583304405212-a3dc5e5d29337036e3c9808399ba89c8413d36b5/.

:octocat: cibot: @myungjoo, c/src/ml-api-inference-pipeline.c includes bug(s). Please fix incorrect coding constructs in your commit before entering a review process.

:octocat: cibot: @myungjoo, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnstreamer.mooo.com/nnstreamer-api/ci/repo-workers/pr-checker/109-202111261712560.3197169303894-9700b58332444eb926317e9049b380d95021e2f9/.

:octocat: cibot: @myungjoo, c/src/ml-api-inference-pipeline.c includes bug(s). Please fix incorrect coding constructs in your commit before entering a review process.

:octocat: cibot: @myungjoo, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnstreamer.mooo.com/nnstreamer-api/ci/repo-workers/pr-checker/109-202111301902220.1889750957489-514be2c93e2d53a27d7498e2e7b43d26e77a1ba7/.

:octocat: cibot: @myungjoo, c/src/ml-api-inference-pipeline.c includes bug(s). Please fix incorrect coding constructs in your commit before entering a review process.

:octocat: cibot: @myungjoo, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnstreamer.mooo.com/nnstreamer-api/ci/repo-workers/pr-checker/109-202112061701160.77777791023254-256bda3c94c4d21ca511756e0c11e7694c186362/.


Dataset links not working

Is this dataset still available? None of the links mentioned in the ReadMe file are working

Sorry about that. Yes, it is still there. However, it moved recently but the links weren't updated on the SpaceNet page.
The new bucket is: s3://spacenet-dataset/Hosted-Datasets/Urban_3D_Challenge/.
I have reached out to the SpaceNet folks to have this updated on their website.


How to fix this issues "Failed to build flash-attn ERROR: Could not build wheels for flash-attn, which is required to install pyproject.toml-based projects"

When I used the "pip install -r requirements.txt",   then I got the following probem:
"    File "/tmp/pip-build-env-4dcxq614/overlay/lib/python3.9/site-packages/torch/utils/cpp_extension.py", line 1909, in _run_ninja_build
raise RuntimeError(message) from e
RuntimeError: Error compiling objects for extension
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for flash-attn
Failed to build flash-attn
ERROR: Could not build wheels for flash-attn, which is required to install pyproject.toml-based projects"
Note:    environment
Name                    Version                   Build  Channel
_libgcc_mutex             0.1                        main
_openmp_mutex             5.1                       1_gnu
binutils_impl_linux-64    2.38                 h2a08ee3_1
bzip2                     1.0.8                h7b6447c_0
ca-certificates           2023.5.7             hbcca054_0    conda-forge
cuda-nvcc                 11.7.64                       0    nvidia/label/cuda-11.7.0
gcc                       11.2.0              h702ea55_10    conda-forge
gcc_impl_linux-64         11.2.0               h1234567_1
gxx                       11.2.0              h702ea55_10    conda-forge
gxx_impl_linux-64         11.2.0               h1234567_1
kernel-headers_linux-64   2.6.32              he073ed8_15    conda-forge
ld_impl_linux-64          2.38                 h1181459_1
libedit                   3.1.20191231         he28a2e2_2    conda-forge
libffi                    3.3                  h58526e2_2    conda-forge
libgcc-devel_linux-64     11.2.0               h1234567_1
libgcc-ng                 11.2.0               h1234567_1
libgomp                   11.2.0               h1234567_1
libstdcxx-devel_linux-64  11.2.0               h1234567_1
libstdcxx-ng              11.2.0               h1234567_1
libuuid                   1.41.5               h5eee18b_0
ncurses                   6.4                  h6a678d5_0
openssl                   1.1.1o               h166bdaf_0    conda-forge
pip                       23.1.2             pyhd8ed1ab_0    conda-forge
python                    3.9.0                hdb3f193_2
readline                  8.1                  h46c0cb4_0    conda-forge
setuptools                67.7.2             pyhd8ed1ab_0    conda-forge
sqlite                    3.41.2               h5eee18b_0
sysroot_linux-64          2.12                he073ed8_15    conda-forge
tk                        8.6.12               h1ccaba5_0
tzdata                    2023c                h04d1e81_0
wheel                     0.40.0             pyhd8ed1ab_0    conda-forge
xz                        5.4.2                h5eee18b_0
zlib                      1.2.13               h5eee18b_0

Dear @LiZhangMing,
Thanks! For the issue about Flast-Attn, please refer to this repo.
Alternatively, we can use train.py rather than train_fast.py to turn off the flash attention.
Best,
Zhihong


Versions greater than 2.55 are not compatible with minetweaker

I went to update my modpack today, and after testing I've discovered new versions of RFtools prevent  minetweaker from applying changes.  Immediately on entering a word, I'am my in-game chat box shows [Error executing modifications.zs: null].
There is a way to force changes, but not without consequence. Oddly enough, typing minetwekaers [/mt reload command] does seem to manually apply changes, however this isn't normal behaviour and indicates some sort of compatibility error between RFTools and Minetweaker3.  The consequence of manually enabling the scripts is that any attempt to quit to the main menu and then re open the world are met with State errors which prevent the world from being re opened.
Below I have provided several images and logs for reference.
This is the complete log.  It includes client startup, world entry, a screenshot, mt/ reload, world exit, attempts to reload the save, and the State errors.
http://pastebin.com/aR27bwbz
This image shows minetweaker failing to load it's changes on save entry.
http://i40.photobucket.com/albums/e230/SlightlyVisible/IMG1_zps3wokm7se.png

Hmm, strange because latest Pathfinder uses 2.60 and has no problem with Minetweaker... I also don't see how there is anything that I could have done this. Why do you think the problem is with RFTools? I see nothing in the log indicating that?

I believe it's related because this issue only occurs when rftools is present.  All probems vanish on either its removal or replacement with 2.55.  If its not on your end, then is it possible minetweaker is at fault for interacting newer versions of rftools incorrectly?  I'm not sure what other information I could provide.  I can easily replicate the problem, but I suppose that isn't helpful if you can't identify it within the log.

I talked to @Gideonseymour who maintains the FTB Pathfinder mod. He has similar issues but with another mod. I'm guessing that this actually is a problem with MineTweaker and I would report it first to them. Gideon got around the issue by forcing /mt reload at startup.

Closing due to lack of concrete example. Reopen if you have more information related to this.


bump: version 1.2.6 → 1.2.7

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 35.683%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
65

Relevant Lines:
185

💛  - Coveralls


Does not show Max value at all

Hi @RNTop, I'm closing this issue because version 3.0.0 is out. What exactly do you mean it doesn't show Max value?
If it's still a problem with the new version, please open a new issue. I'm committing myself to monitor & develop this library more consistently.


refactor orca->octo in pytorch example

Refactor orca to octo in the examples/06_pytorch_oxe_dataloader.py example, presumably due to renaming of the project for its public release.
The PyTorch dataloader seems to otherwise run smoothly, thanks for sharing!
cc @kpertsch @mees

Thanks for catching this!

The dataset gs://rail-orca-central2/resize_256_256 in the example seems to be missing! Thanks in advance!


[Map] Improve web performances by not calling "createInfoWindow" if unnecessary

Q
A

Bug fix?
no

New feature?
yes

Issues
Fix #...

License
MIT

This afternoon we spoke a bit with @simondaigre, and he told me about InfoWindow performance issues when you have too many of them (and depending your device).
If we have 1.000 InfoWindow, hidden by default and only visible after clicking on a marker, why should be only create the InfoWindow at that time?
This PR introduce lazy-creation of InfoWindow, it should improve web-performances on the user's browsers.
I've used the following PHP code:

       $map = (new Map())
            ->center(new Point(0, 0))
            ->zoom(2)
            ->fitBoundsToMarkers()
            ->options(new GoogleOptions(
                mapId: 'XXX',
            ))
        ;

        for ($i = 0; $i < 1_000; $i++) {
            $map->addMarker(
                new Marker(
                    position: new Point(random_int(-90, 90), random_int(-180, 180)),
                    title: 'Marker ' . $i,
                    infoWindow: new InfoWindow(
                        content: 'Info window ' . $i,
                        opened: $i % 499 === 0
                    )
                )
            );
        }

Benchmarks
I've did some benchmarks for both Google and Leaflet:

with 1.000 markers,
on a Macbook M1 Pro, CPU Throttle x6

Google

Before
 After

connect() takes 936ms instead of ~1,80s, we won ~900ms.
Leaflet

Before
 After

connect() takes ~1s instead of ~1,20s, we won ~200ms

The next steps for performance optimizations are:

Lazyloading markers and infoWindows, in order to keep a good TTFB
Clusters!

I feel like the current implementation could be improved, but i don't think we could/should avoid exposing this internal code.. and the loop seems a bit odd.
Why not having separate create / open methods ?

Let's re-open it later


chore: restore ability to release maintenance version lines

Same as https://github.com/aws/jsii-compiler/pull/998, but for jsii-rosetta
This repo was using an automatic backport feature for repository config. As part of daily upgrades, the projen config would be checked out from main and applied to maintenance branches. However because we also defined the current version in this config, this inadvertently changed the current version for maintenance branches as well! In practice that meant that the release tagging workflow tagged the wrong release lines.
This fix does two things:

Disable the automatic backport of configuration in favor of the new, explicit label based backport feature (see it in action on this PR!)
Add an explicit release line option to the tagging workflow, that will be compared against the detected TypeScript version and fail if they don't match.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

💔 Some backports could not be created

Status
Branch
Result

❌
maintenance/v5.2
An unhandled error occurred. Please see the logs for details

✅
maintenance/v5.3

Manual backport
To create the backport manually run:
backport --pr 1386

Questions ?
Please refer to the Backport tool documentation and see the Github Action logs for details

💚 All backports created successfully

Status
Branch
Result

✅
maintenance/v5.2

✅
maintenance/v5.3

Questions ?
Please refer to the Backport tool documentation and see the Github Action logs for details


Fixed the switch subcommand exit status on Fish

When switching PHP versions using Fish, phpbrew switch exits with a non-zero code even on success:
$ phpbrew list
  php-7.4.0RC2
* php-7.3.10

$ phpbrew switch 7.4.0RC2

$ echo $status
1

$ phpbrew list
* php-7.4.0RC2
  php-7.3.10

$ php -v
PHP 7.4.0RC2 (cli) (built: Sep 21 2019 15:26:11) ( NTS )
Copyright (c) The PHP Group
Zend Engine v3.4.0-dev, Copyright (c) Zend Technologies
    with Zend OPcache v7.4.0RC2, Copyright (c), by Zend Technologies
    with Xdebug v3.0.0-dev, Copyright (c) 2002-2019, by Derick Rethans

Coverage increased (+0.07%) to 41.259% when pulling 8e84aa89a2bfcf422b61db36ddf65b22176c4630 on morozov:fish-switch-exit-status into bceaee1faf158cf2b073be715877e8ba0d71797d on phpbrew:master.

Merging my own PR without a review:

There has been a month without feedback.
None of the maintainers seem to use Fish.
I've been using this patch for a month myself and haven't experienced any issues.


Setup and implement publishing Maven artefacts to MavenCentral and OSSRH

WHAT
In order to have tractusx-edc consumable also on code-level we need to publish all artefacts to MavenCentral. In Eclipse projects that happens through an EF-managed Jenkins instance ("JIPP") that contains signing keys for MavenCentral.
WHY
MavenCentral requires all artefacts to be signed. That is done in Jenkins.
Implementation proposal

remove the publishAllPublicationsToGithubPackagesRepository task
GH Actions triggers Jenkins (through this action)
on releases: the version parameter does not contain the -SNAPSHOT suffix, thus causing it to sync to MavenCentral

OPEN QUESTIONS

what's our publishing schedule? Snapshots on every push to develop? Nightlies?
do we already have a publishing environment set up?
if not: who will open helpdesk issues with EF and OSSRH?
should we host the declarative pipelines in a GitHub repo? (in EDC we do that)

We are allowed to publish to MV directly from GH Actions, without going through Jenkins. Once this EF helpdesk issue is resolved, we can modify our publish workflow


tests: kernel: early_sleep: move to new ztest API

Move tests/kernel/early_sleep/ to use new ztest API.
Signed-off-by: Guo Lixin<EMAIL_ADDRESS>

We have the same issue in #47126 on qemu_cortex_m3.

Hi, @nashif , could you help to review again?

Hi @nashif , could you please re-review this when you get a chance? Thank you!


cant show inserted image

hi,
I use thus code
    {{#if currentFile}}
        Uploading {{currentFile.file.name}}:
        {{progress}}%

    {{else}}
        <input id="fileInput" type="file"/>
    {{/if}}

and that in template helper
   imageFile: function () {
        return InterestIcons.collection.findOne({});
    }

and cant see the uploaded image
Best regards

picture is uploaded server:
Meteor.Files Debugger: [MeteorFileWrite] {name: K8g3CxveXuPCswMhQ, meta:[object Object]} I20160409-22:51:54.725(2)? Meteor.Files Debugger: Received chunk #1 of 1 chunks, file: dance-icon.png I20160409-22:51:54.802(2)? Meteor.Files Debugger: [MeteorFileWrite] {name: K8g3CxveXuPCswMhQ, meta:[object Object]} I20160409-22:51:54.802(2)? Meteor.Files Debugger: Received chunk #-1 of 1 chunks, file: dance-icon.png I20160409-22:51:54.811(2)? Meteor.Files Debugger: The file dance-icon.png (binary) was saved to ~/interests/K8g3CxveXuPCswMhQ.png
on the client:
Meteor.Files Debugger: [insert()] files.coffee:878 Meteor.Files Debugger: Connection established continue() upload files.coffee:884 insert: 121.977ms

Have you subscribed to this data? Please see this example

Also you need to change template to:
    {{#if currentFile}}
        Uploading {{currentFile.file.name}}:
        {{progress}}%
    {{else}}
        <input id="fileInput" type="file"/>
    {{/if}}

    {{#if imageFile}}

    {{/if}}

server
Meteor.publish('files.images.all', function () {     return InterestIcons.collection.find({}); });
client
Router.route('/interests/new', {     name: 'newInterest',     waitOn: function () {         return [Meteor.subscribe('InterestType'),Meteor.subscribe('files.images.all')];     } });

Does my comment about template fix this issue?

unfortunately no .. looks better
I20160409-22:58:32.321(2)? Meteor.Files Debugger: [findOne("Azyz5KMzneroddsWW")] I20160409-22:58:32.322(2)? Meteor.Files Debugger: [download(/cdn/storage/InterestIcons/Azyz5KMzneroddsWW/original/Azyz5KMzneroddsWW.png, original)] W20160409-22:58:32.324(2)? (STDERR) Meteor.Files Debugger: [download(/cdn/storage/InterestIcons/Azyz5KMzneroddsWW/original/Azyz5KMzneroddsWW.png)] [404] File not found

but the image is in filesystem I checked it

Okay, I saw from you previous issue, what you're using path relative to you user (starts with ~)
Could you try to change it to absolute path?

Or even try to keep package's default (for testing purpose)

I have it but I didnt want to publish it ;)

It works right know but It finds only one image but I want to display curently uploaded

Then do something like:
Template.uploadForm.onCreated(function () {
  this.uploadedFile = new ReactiveVar(false);
});

Template.uploadForm.helpers({
  currentFile: function () {
    return Template.instance().currentFile.get();
  },
  uploadedFile: function () {
    return Template.instance().uploadedFile.get();
  }
});

Template.uploadForm.events({
  'change #fileInput': function (e, template) {
    if (e.currentTarget.files && e.currentTarget.files[0]) {
      var file = e.currentTarget.files[0];

      template.currentFile.set(Images.insert({
        file: file,
        onUploaded: function (error, fileObj) {
          if (error) {
            alert('Error during upload: ' + error);
          } else {
            // Two options
            // First (no need for subscription):
            template.uploadedFile.set(fileObj);
            // Second (subscription needed):
            template.uploadedFile.set(InterestIcons.collection.findOne({_id: fileObj._id}));
          }
          template.currentFile.set(false);
        },
        streams: 'dynamic',
        chunkSize: 'dynamic'
      }));
    }
  }
});

I'n off for today, will check you reply tomorrow

I figured it out with similar implementation .. thanks a lot man :)

Solved? Right?

that's right .. thanks for your support :)


[WIP] Implement FFI for GDScript.

Implement simple FFI for the GDScript using libffi.

Adds FFILibrary class.
Adds functions to get writable pointer of the PackedByteArray and copy data from a pointer to a PackedByteArray.
C-struct argument/return types are encoded/decoded to the GDScript Array.

Simple demo - Click to expand
#if defined(_MSC_VER)
    //  Microsoft
    #define EXPORT __declspec(dllexport)
#elif defined(__GNUC__)
    //  GCC
    #define EXPORT __attribute__((visibility("default")))
#else
    #define EXPORT
#endif

#include <stdio.h>
#include <stdlib.h>
#include <string.h>

struct TestStruct {
    int a;
    long b;
    float c;
};

EXPORT struct TestStruct function_a(int p_a, float p_b) {
    struct TestStruct s;
    s.a = p_a;
    s.b = p_a * 10;
    s.c = p_b / 2.0;

    return s;
}

EXPORT float function_b(struct TestStruct p_s, int p_a) {
    float a = p_s.c + p_s.b * 10 + p_s.a * 100 - p_a;
    printf("==== %d %d %f %d = %f ====\n", p_s.a, p_s.b, p_s.c, p_a, a);
    return a;
}

EXPORT void function_c(int p_a, float p_b, char *p_str) {
    printf("==== %d %f %s ====\n", p_a, p_b, p_str);
    memcpy(p_str, "output test", 11);
}

func _test(path):
    # Open library.
    var lib = FFILibrary.new()
    lib.open(path, FFILibrary.ABI_DEFAULT)

    # Bind C-struct type.
    # args: name, element types...
    lib.bind_struct("TestStruct", FFILibrary.TYPE_SINT, FFILibrary.TYPE_SLONG, FFILibrary.TYPE_FLOAT)

    # Bind C-functions.
    # args: return type, name, argument types...
    var function_a = lib.bind_method("TestStruct", "function_a", FFILibrary.TYPE_SINT, FFILibrary.TYPE_FLOAT)
    var function_b = lib.bind_method(FFILibrary.TYPE_FLOAT, "function_b", "TestStruct", FFILibrary.TYPE_SINT)
    var function_c = lib.bind_method(FFILibrary.TYPE_VOID, "function_c", FFILibrary.TYPE_SINT, FFILibrary.TYPE_FLOAT, FFILibrary.TYPE_POINTER)

    # Call function A.
    print(function_a.call(44, 89.6))
    print("should be: ", [44, 440, 44.8])

    # Call function B.
    print(function_b.call([10, 20, 30.5], 233))
    print("should be: ", 997.5)

    # Call function C.
    var s = "Test String".to_utf8_buffer()
    s.push_back(0) # Add terminating zero.
    var ptr = s.unsafe_get_ptr() # Get writable pointer.
    function_c.call(10, 20.5, ptr)
    print(s.get_string_from_utf8())
    print("should be: ", "output test")

Tested (with the aforementioned demo only) on:

macOS x86_64 and ARM64
Windows (MSVC) x86_64 and x86_32
Linux x86_64 and ARM64

TODO:

[ ] Documentation.
[ ] Test all primitive types and nested structures.
[ ] Build flags need to be carefully evaluated and tested on each platform and architecture, since it involves pre-processing and building assembly sources.
[ ] Evaluate thread safety.

This is interesting. I had an idea like this for quite some time but never got around to implementing something.

Neat, missed this so far and will have a look later.
IMO important concern: It might be reasonable to disable this functionality by default in the editor (and editor started projects; similar to how you have to enable/opt-in addons), simply because it could allow malicious code to do all kind of nasty stuff default tool scripts can't do.
Maybe decoupling this here, could be worth having a "Do you trust this source?" kind of banner once certain function calls or classes are used in a project?

IMO important concern: It might be reasonable to disable this functionality by default in the editor (and editor started projects; similar to how you have to enable/opt-in addons), simply because it could allow malicious code to do all kind of nasty stuff default tool scripts can't do.

GDScript can download and run executable or load GDExtension (which can have arbitrary native code) so FFI won't make it more insecure than it already is.

Hm, true.

Maybe decoupling this here, could be worth having a "Do you trust this source?" kind of banner once certain function calls or classes are used in a project?

See https://github.com/godotengine/godot-proposals/issues/5010.

What's the status on this PR? Would love to potentially try to rebase and get a bit more into this feature over the Holidays, as there's sadly not too much activity here.

What's the status on this PR?

Needs testing on various platforms and architectures, it works fine on arm64 and x86-64, but extremely buggy on 32-bit x86, and not tested on any other architectures.


Confusion

The page was bewildering in its profusion. I was expecting a simple explanation (or, even better, a video) of how to upload my Excel spreadsheet into an Azure workspace.

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

ID: 2550031e-4cf6-8d15-84e3-1c2b58951f80
Version Independent ID: 1a927119-0540-dfd9-9435-5c29c014daff
Content: Introduction to Azure Storage - Cloud storage on Azure
Content Source: articles/storage/common/storage-introduction.md
Service: storage
Sub-service: common
GitHub Login: @tamram
Microsoft Alias: tamram

@Zarathrustra Can you please confirm the documentation URL you are referring to?

Thanks Derek for getting back to me.
I've delayed as I have tried to recall/rebuild what I had originally done - but I am not sure which one I did initially stumble on and complain about I'm afraid.
My main gripe is that all the Azure Welcoming info is seemingly generalised, whereas I'm looking for an idiot's way in: a step by step example of going from an Excel spreadsheet to using what I believe is the rich set of Azure AI tools. So: How to do an Azure add-in (I do now know how to do that); to (presumably) uploading an Excel spreadsheet into the Azure workspace; to selecting the input variables to test against chosen output ones; and how to get the results.
I've found some YouTube guides and am attempting to do the above from those. So far, I've only got to including the Azure addin to my spreadsheet.
But given that Azure is seemingly an attempt to get novices to AI to use AI on their spreadsheets, I've not found the Azure info so far very intuitive.
Kind regards, Ian

From: DerekHerman-MSFT @.>
Sent: 21 March 2021 05:19
To: MicrosoftDocs/azure-docs @.>
Cc: Zarathrustra @.>; Mention @.>
Subject: Re: [MicrosoftDocs/azure-docs] Confusion (#72494)
@Zarathrustrahttps://github.com/Zarathrustra Can you please confirm the documentation URL you are referring to?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/72494#issuecomment-803515185, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALY7O3HHJANTFGPSOLIZY6TTEV6XLANCNFSM4ZQWOAYA.

@Zarathrustra
If you let me know which URL you feel this information should be added to I can get your issue over to the proper doc author to look into your feedback.
I'd also recommend posting your questions in https://azure.microsoft.com/en-us/support/community/ since it's not directly related to the documentation and our community team should be able to help.

Hi Derek,
I started with this: Home - Microsoft Azurehttps://portal.azure.com/#home
Microsoft Azurehttps://portal.azure.com/#home
Microsoft is radically simplifying cloud dev and ops in first-of-its-kind Azure Preview portal at portal.azure.com
portal.azure.com
Then, thinking I needed to Setup a place to put my Excel spreadsheet, from what I understood on: How to Import Data from Microsoft Excel to Windows Azure SQL Database - SQL Training Online - Bing videohttps://www.bing.com/videos/search?q=how+do+I+upload+my+Excel+data+into+Azure+Workspace%3F&docid=608000244146503797&mid=8BFBBC02C9B6AE7EA72F8BFBBC02C9B6AE7EA72F&view=detail&FORM=VIRE
[http://www.bing.com/sa/simg/facebook_sharing_2.png]https://www.bing.com/videos/search?q=how+do+I+upload+my+Excel+data+into+Azure+Workspace%3F&docid=608000244146503797&mid=8BFBBC02C9B6AE7EA72F8BFBBC02C9B6AE7EA72F&view=detail&FORM=VIRE
how do I upload my Excel data into Azure Workspace? - Binghttps://www.bing.com/videos/search?q=how+do+I+upload+my+Excel+data+into+Azure+Workspace%3F&docid=608000244146503797&mid=8BFBBC02C9B6AE7EA72F8BFBBC02C9B6AE7EA72F&view=detail&FORM=VIRE
Intelligent search from Bing makes it easier to quickly find what you’re looking for and rewards you.
www.bing.com
I went down the rabbit hole of trying to set up a Database - and got lost and gave up.
Kind regards, Ian

From: DerekHerman-MSFT @.>
Sent: 22 March 2021 20:53
To: MicrosoftDocs/azure-docs @.>
Cc: Zarathrustra @.>; Mention @.>
Subject: Re: [MicrosoftDocs/azure-docs] Confusion (#72494)
@Zarathrustrahttps://github.com/Zarathrustra
If you let me know which URL you feel this information should be added to I can get your issue over to the proper doc author to look into your feedback.
I'd also recommend posting your questions in https://azure.microsoft.com/en-us/support/community/ since it's not directly related to the documentation and our community team should be able to help.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/72494#issuecomment-804386720, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALY7O3CI23ELAHIZPNDROCTTE6U3JANCNFSM4ZQWOAYA.

@Zarathrustra Since it seems you are needing guidance I recommend posting your questions https://azure.microsoft.com/en-us/support/community/
After you have the proper guidance you can create new feedback for the appropriate documentation page. We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Update docs for mozillians.org l10n.

Coverage remained the same at 92.495% when pulling<PHONE_NUMBER>78d3ee545bae1c7b8cc39a65dd3971 on johngian:l10n-docs into e24fde761db5be55eb5bb0b2c5abdb5dd89df614 on mozilla:master.

r+


javax.sql.ConnectionPoolDataSource support

Current HikariCP solution contains of 2 parts

Codegen/Proxy related stuff to wrap java.sql.Connection to something like javax.sql.PooledConnection
Pool management code itself (inc thread syncronization, lifetime management etc)

Some JDBC drivers provide javax.sql.ConnectionPoolDataSource out-of the box. So bytecode generation isn't requred. I propose to split HikariCP for 2 lose-coupled parts:

Codegen/Proxy related stuff to generate javax.sql.DataSource to exact javax.sql.ConnectionPoolDataSource adapter
Pool management code to deal directly with  javax.sql.ConnectionPoolDataSource api.

In this case you can use both parts if JDBC driver doesn't support javax.sql.ConnectionPoolDataSource and only second part otherwise...

@brettwooldridge - With so much obsolete/unused interfaces in javax.sql have you ever considered suggesting improvements to this API or do you think that it's fine the way it is?

I'm sorry, I don't like the idea of splitting the implementation. Ordinary users cannot make an informed choice between the implementations. As I did, user's would need to understand whether their JDBC driver ConnectionPoolDataSource implementation properly resets connection state or not in order to choose it. While this is possible with open source drivers, it is not possible with closed source drivers. And in the end, what is the "win"? The "win" is simply the removal of generated proxies. Frankly, I don't care. It's not worth it to me either in terms of code complexity, or dealing with user issues because they misconfigured their pool. Javassist is practically ubiquitous in server stack dependencies these days, and we haven't had any users clamoring for its removal.

I would like to weight in on that and share recent experience of my own. One of our Java applications use HikariCP and MS SQL JDBC driver. Application just calls stored procedures on MS SQL and returns the result to the user. As mentioned in related mssql-jdbc link above, the driver itself doesn't "reset" the connection before every call. And as mentioned in this ticket, HikariCP doesn't implement ConnectionPoolDataSource API.  Temporary tables are not cleared, SELECT queries use exclusive locking, etc. etc. In short, the experience is terrible and debugging such issues takes forever.
You could say that driver itself should implement connection "reset". Probably, but that would be very inefficient because without Pooling API returned from pooling implementation they don't know when the connection is reused. They would need then to send "reset" after every SQL call. Some older JDBC drivers did exactly that, but I see the trend that now more and more drivers start to rely on ConnectionPoolDataSource API instead, and this is understandable.
That's why I kindly ask to reconsider this issue. Pooling implementation is needed, there is no question about that. The question is how to correctly implement it in HikariCP, so its benefits won't be lost.


fix seed

Coverage decreased (-0.004%) to 84.133% when pulling 491f91f01011574f216a77da5385d0b3b5466625 on itowtips:seed into 002380643bdeace5d048b7c07a3355a9e76e8daf on shirasagi:master.


Disabling a node causes a validation error and the bot cannot be started.

Describe the bug
Disabling a node causes a validation error and the bot cannot be started.
http://g.recordit.co/5bcl5DM0iN.gif

Version
nightly build
Browser

[x] Chrome

OS

[x] macOS

To Reproduce

Create a dialog
insert a send activity as the first node
disable the node
See a validation error appear in the upper right, " end a response: disabled the return type does not match"

Expected behavior
This should not show a validation error.

This is because the disable field is defined as stringExpression for Microsoft.SendActivity type, others are all defined as booleanExpression.
I will submit two PRs in both composer and sdk side.


CritterbaseProxy Fix

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 53.27%. Comparing base (c52684a) to head (c390421).

Additional details and impacted files
@@            Coverage Diff             @@
##              dev    #1267      +/-   ##
==========================================
+ Coverage   53.25%   53.27%   +0.01%
==========================================
  Files         547      547
  Lines       16231    16236       +5
  Branches     2517     2518       +1
==========================================
+ Hits         8644     8649       +5
  Misses       7007     7007
  Partials      580      580

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Improve footer designing

The current footer is also looking awesome. I would like to make it more catchy by adding some animation aligning with theme.

@Varinder-Dhillon0 Please assign me this issue under SWOC24

@Varinder-Dhillon0 I would like to improve the UI of footer, can you assign it to me?

Yes @bj-jiwrajka


TreeView - AccessViolationException on remove an item

Describe the bug
System.AccessViolationException
{"Attempted to read or write protected memory. This is often an indication that other memory is corrupt."}
Steps to reproduce the bug

Steps to reproduce the behavior:
I have a TreeView which its ItemSource binded to a Collection. When i remove an Element in that Collection i got this Exception before i can handle it.
Expected behavior
I had no crash on version 2.3
Screenshots

Version Info

NuGet package version:
Microsoft.UI.Xaml 2.4.0-prerelease.200506001

Windows 10 Version 1909 Build 18363.778

| Desktop                 | yes |

@DehghaniHootan can you please share a repro app ?

@DehghaniHootan can you please share a repro app ?

Sample_app
I find out that when i tried to remove a selected node that exception happen. so first i have to change isSelected to false. (in the sample_app when i hit remove button 2 times i got this exception)

@DehghaniHootan I am unable to repro this. When I hit the remove button twice I get this error which seems to be an app issue since SampleItems seems to be empty.

@ranjeshj don't you have these 3 Companies when you run the app. If not, LoadDataAsync method in TreeViewViewModel.cs does not do its job.

Update: I've been able to reproduce the AccessViolation sometimes (not very often). After updating to the latest WinUI 2.5 prerelease, I wasn't able to reproduce the crashes anymore.
@ranjeshj Should we close this issue?

Thanks @chingucoding. @DehghaniHootan Please give 2.5 prerelease a try. If you still hit the crash, please reopen this issue. Thanks!

@ranjeshj this does appear to be happening with the navigation view as well.
If you try to set the MenuItemSource to a different collection the same exception occurs. If you first set the selected item to null, it allows the items source to be modified.

@Going-Gone I cannot reproduce this on the newest 2.5 preview:

Are you doing anything else or could you upload a repro app?

@Going-Gone I cannot reproduce this on the newest 2.5 preview:

("Change ItemsSource" button assigns a new list to the MenuItemsSource.)
Are you doing anything else or could you upload a repro app?

It appears that with the Top Pane mode, the exception happens, but it doesn't happen with Left pane mode.

It appears that with the Top Pane mode, the exception happens, but it doesn't happen with Left pane mode.

@Going-Gone Thanks! I can repro it now. I can take a look at this issue.

It appears that with the Top Pane mode, the exception happens, but it doesn't happen with Left pane mode.

@Going-Gone Thanks! I can repro it now. I can take a look at this issue.

Awesome, thanks.

Thanks @Going-Gone  and @Felix-Dev. Reopening this issue since we do have a repro.

@ranjeshj I couldn't repoduce this for the TreeView control. @Going-Gone and I above managed to repro an issue in the NavigationView control here which is tracked by issue https://github.com/microsoft/microsoft-ui-xaml/issues/3200. I think you can close this issue here again until someone manages to repro this specific TreeView on the newest WinUI bits again.
Sorry for the confusion.


Support different zones for disk and vm. [userstudy]

it is currently possible using Objects, but it is unclear when setting the a zone parameter, if it applies to the disk zone or the vm zone.

It is currently possible to specify different zones using objects, but the api throws an error:
Invalid value for field 'resource.source': 'https://www.googleapis.com/compute/v1/projects/gcloud-powershell-testing/zones/asia-east1-a/disks/disk-1'. Disk must be in the same zone as the instance. [400]


Adds more detailed telemetry fields

Why this PR?
We want reader of telemetry to have more insight into the state of the feature flag.

Adds additional telemetry fields.
Added the same BytesExtension we have on the provider for Base64Url.
Adds and adjusts unit tests

Visible Changes

FeatureEvaluation events will have new fields:

VariantAssignmentPercentage - The percent of users we expect to be assigned the given variant for the given reason
DefaultWhenEnabled - The DefaultWhenEnabled field
AllocationId - An id that uniquely reflects the state of allocation. Two events with the same AllocationId can expect a given TargetingContext will always give the same result.  **Note- This is instead computed in App Configuration Provider

@zhiyuanliang-ms if you have time could you review this?


chore(Vector3): remove cross method

Replace cross with crossProduct method

rename with BREAKING CHANGE: ?
it looks like a BREAKING CHANGE for Vector3

add BREAKING CHANGE: footer? it looks like a BREAKING CHANGE for Vector3

The cross and crossProduct methods coexist. They are identical, which is easy to confuse users。


annotation and prediction in sampleData/

The images in annotation/ and prediction/ in sampleData/ seems to be the same... Is there a mistake?

@joeyhng No, it is fake predictions.


Add Expectation type for errors with various possibilities

Background
It would be good to have a more general type for returning in errors that captures unexpected results.
Proposed Solution
It could be something along the lines of:
data Expected v =
  Expected
    { expectation :: Expectation
    , expected :: v
    , got :: v
    }

data Expectation =
    LessThan
  | MoreThan
  | Exactly
  | Other Text

Next Action

[ ] Implement something similar to above and trial on ChainValidationError

:100:
Although I'd say that this expectation refers to an ordering, so maybe we'd want something like ExpectedOrdering (although this sounds awful).
Alternatively we might want to keep only the Other Text part :man_shrugging:


[Chat] Check achievements chat parsing

Dreadspire conqueror

Rework parsing of achievement titles:

[ ] Only keep the ones with a title reward
[ ] Map should be Achievement.id -> Title


Puppetboard on PE complains about PuppetDB version

Describe the bug
Running PuppetBoard 4.0.3 on a PE platform causes the puppetboard container to never properly start:
[2022-09-11 10:33:02 +0000] [24] [INFO] Booting worker with pid: 24
INFO:puppetboard.utils:PuppetDB version: 7.11.1-20220809_222149-g0b0b67c
ERROR:puppetboard.utils:The minimum supported version of PuppetDB is 5.2.0
[2022-09-11 10:33:13 +0000] [24] [INFO] Worker exiting (pid: 24)
[2022-09-11 10:33:13 +0000] [25] [INFO] Booting worker with pid: 25
INFO:puppetboard.utils:PuppetDB version: 7.11.1-20220809_222149-g0b0b67c
ERROR:puppetboard.utils:The minimum supported version of PuppetDB is 5.2.0
[2022-09-11 10:33:43 +0000] [25] [INFO] Worker exiting (pid: 25)

Puppetboard version
4.0.3
Environment and installation method

Centos 7 and Docker version 20.10.18, build b40c2f6
Using a profile:

  $tag_name = '3.6.1'  # <--- working
  # $tag_name = '4.0.3' # <--- not working

  include docker

  docker::image { 'ghcr.io/voxpupuli/puppetboard':
    image_tag => $tag_name,
  }

  docker::run { 'puppetboard':
    image => "ghcr.io/voxpupuli/puppetboard:${tag_name}",
    env   => [
      'PUPPETDB_HOST=<IP_ADDRESS>',
      'PUPPETDB_PORT=8080',
      "PUPPETBOARD_PORT=${port}",
    ],
    net   => 'host',
  }

Hi @tuxmea! Thanks for reporting.
I was just hacking something Puppetboard-related so I can fix it immediately. :)

Fixed in v4.0.5.


The Road to v1.0

This is a meta issue/checklist for features and changes wanted for the v1.0 milestone. Things may be added, pushed back or removed.

[x] (app) Add WebGL support detection in player (3f01e0fbef8347cc3e990b58a2f3d41c5f9b6767)
[x] (app) Add user management UI (e524f61)
[x] (app) Add drag-n-drop support for re-ordering media folders (67839cc)
[x] (server) Add user management API endpoints (e524f61)
[x] (server) Retain the same port # between launches? (documented)
[x] (server) Have metaparser use either meta tags or filename automatically (de-prioritized)
[x] (server) Add metadata support for year, genre and ReplayGain (78eb1760fb64ea97a46809fece2e152b6f654bd3)
[x] (server) Media scanner performance improvements (particularly db writes)(5f7171a66db1f99eb7f4e774bd64655e7758b465)
[x] (server) Support password-protected rooms (c2f0be13a82b59d0b7c4e223f88793f628ea3e5f)
[x] (installer) Move licenses to an About screen/page (e9f36a7317daec63fd26815726bf01167dbeb76c)
[x] (installer) Signed packages for macOS and Windows (likely post-1.0 depending on financial goals)

v1.0 has been released! 🎉


Check for zero byte send in ReaderToChannel

Run gofmt on shared/util_test.go to resolve a test failure.
Fixes #2072
Signed-off-by: Sean Christopherson<EMAIL_ADDRESS>

Great, thanks!


Add tests for evaluate

This repo needs test for evaluate() and a CI to run them. This will require several mocks.

Added some tests in test_evaluate, can continue adding as needed.


Mallet

Just wondering if you stumbled across Mallet (https://github.com/SensePost/Mallet/) while you were evaluating the existing tools out there? And if so, why it was not suitable?

Actually, I didn't know about it. I guess I missed it. Thanks!
Anyway, you are more than welcome to try mitm_intercept and suggest features and improvements.


folder structure

please move the contents of  tfc-nusantara-epigraphy/provisional/aditiagunawan into the Sundanese folder, and then delete the aditiagunawan folder.

Dear @arlogriffiths
I see all the files already move to Java11Sundanese. So It should simply delete it from my folder on the computer? How to delete the folder aditiagunawan? Thank you for your help.

Ok. Done.


April webinar

April webinar page featuring Steve's webinar about production metrics.

@Steve-Mcl can you please review the content of the page and make any suggestions for changes.  I have added an item for connecting to an external data service but not sure what example we could use. If you don't think this is a good idea we can delete this.

@iskerrett all approved.
Not sure when you want it merged so will leave for you.


Robot Wrapper

Create a robot wrapper similar to the existing python class containing a model and several data store in a vector achieving the interface between (model,data) and the main algorithms.
@aelkhour Do you have some precise requests?

Not throwing exceptions would be great.
Not making explicit dynamic allocations (using new operator) would be great.

If this conflicts with your development roadmap, then no worries.

Concerning the exceptions, why this precise request?

Our whole code base is supposed to be exception-free. I know this is not currently the case in pinocchio, which is why this is not a hard requirement.

Ok. If you want you can just use the instruction -fno-exceptions with gcc.
I think for lambda user, exceptions are mandatory that why we try to populate our code with them.

Noted, thanks.

It indeed is: please no throw in construction and destruction (just
image what can of torture you are generating on the poor stack when
creating memory with a destruction phase to throw something).
On 02/22/2016 04:44 PM, Antonio El Khoury wrote:

Our whole code base is supposed to be exception-free. I know this is
not currently the case in pinocchio, which is why this is not a hard
requirement.
—
Reply to this email directly or view it on GitHub
https://github.com/stack-of-tasks/pinocchio/issues/108#issuecomment-187237364.

A robot wrapper have been implemented in https://github.com/stack-of-tasks/tsid


Add setting to always launch ShellCheck with the workspace root as cwd

Setting is useWorkspaceRootAsCwd (boolean). The rationale for this is that ShellCheck source directives may be specified as relative to the root of the workspace, which is more compatible with the behaviour of many other editors when used in conjunction with ShellCheck.
For example, Vim might be launched from the root of the workspace, and ShellCheck will be able to follow the source directives consistently by being anchored from the root path under which it was launched. This in turn means the editor doesn't have to always launch ShellCheck under the directory of the file to be linted, and that source directives do not have to be always relative to the location of each individual file.
The setting is disabled by default, in which case the existing behaviour is retained. This is to set ShellCheck's current working directory to that of the file being linted, unless the file has not yet been saved, in which case we fallback to the workspace root directory.

Thanks!


[New Port Request] libosip2-dev

Library name:
libosip2-dev
Library description:
libosip2 header files and static libraries to assist in development of programs wishing to use SIP.
Source repository URL:
https://packages.debian.org/jessie/libosip2-dev
B.R

hey guys
sorry to bother you, buy any updates on these PR requests?

Hi @regexizer, thanks for reporting this.
I've added this port, please update vcpkg and build libosip2.
Thanks.


Add Future#cancel

This issue was originally filed by @seaneagan

Future should allow canceling of callbacks added with Future#then.  Might look like:
void cancel(void onComplete(T value));
example:
future.then(onComplete);
//...
future.cancel(onComplete);

@kwalrath This cancel.

@lrhn in a chat with developers today, one said that having lots of "open" futures slows down apps and is hard to diagnose. Do we have any plans to revisit this, or are there tools devs can use to hunt down these futures and fix their code?

There is no cost to having an "open" future that doesn't do computation. It's just an object, like any other object.
What costs is having computations running, and the ability to cancel that computation is not something that belongs on Future. It's something the computation itself must cooperate with.
There is no easy way to integrate cancelabilty with async functions, so most async functions would not be cancelable. The functions which are cancelable have to be written for that, and they cannot be async functions.
We can help you write such functions. I still recommend using CancelableOperation from package:async or something similar, perhaps building on that class.
import "dart:async";
import "package:async/async.dart";

CancelableOperation<T> runWithCancel<T>(
    Future<T> action(Future<void> onCancel)) {
  var cancel = Completer<void>();
  return CancelableOperation<T>.fromFuture(action(cancel.future), onCancel: () {
    cancel.complete();
    return null;
  });
}

main() {
  var running = runWithCancel<int>((cancelFuture) async {
    bool isCancelled = false;
    cancelFuture.then((_) {
      isCancelled = true;
    });
    int i = 0;
    while (true) {
      if (isCancelled) return -1;
      print(i++);
      await Future.delayed(Duration(milliseconds: 250));
    }
    return 42;
  });
  var timer = Timer(Duration(seconds: 2), running.cancel);
  running.value.then(print).whenComplete(timer.cancel);
}

We still have no current plans to add cancel to Future. It's not the right place for that functionality.

As a Dart user, I think there may be a situation where a cancelable future is very useful.
When using Stream in combination with the async* syntax, it's quite normal to break the flow with a Future at some lines:
Stream<int> load10Data(Future<int> loadAt(int index)) async* {
  for (var i = 0; i < 10; i++) {
    yield await loadAt(i);
  }
}

If await accepts something like CancelableFuture (and forward the cancellation down to the await stack), the loadAt would know when to do a graceful shutdown instead of hanging there. Allowing such syntax will also make StreamTransformer.bind much easier to use, since one would be able to await on Stream#singleWhere in the passed bind function. The literal promise provided by Future may not be a obstruct here if we consider every CancelableFuture as an alternate future timeline, which is cool IMO :)
CancelableOperations will not help here because awaits only work with Futures. Of course, there's nothing stopping a programmer from replace the yield await Future to a yield* Stream call.
But Stream won't solve a bigger problem: since Future is always the first choice for library authors (lightweight and catchable), the lack of a CancelableFuture may accidentally make many cancelable actions to be non-cancelable across 3rd-parth libraries in the future, which is happening in the JavaScript community. IMHO the fetch API in browsers may be a good counterexample for weirdly making network requests non-cancelable, I really hope Dart's ecosystem would go the other way.

@pinyin For what it's worth, you can write:
Stream<int> load10Data(CancelableOperation<int> loadAt(int index)) async* {
  for (var i = 0; i < 10; i++) {
    yield await* loadAt(i).asStream();
  }
}

and it should have the behavior you want when you cancel the load10Data() stream. But that certainly is more cumbersome, and CancelableOperation living outside the core library means that many operations that are notionally cancelable don't "just work" in this way.

Your example of yield await something; where a cancel on the stream would somehow cancel the something operation is hard to define in a consistent way. It is currently completely equivalent to
var tmp = await something; yield tmp;. If cancelling the stream should affect them the same, then it means that cancelling the stream of an async* function should be able to interrupt any await in the body. Interrupting an expression is tricky, because expressions can only complete in two ways: with a value or with a throw. Neither seems right here.
If it completes with a value, then computation will continue with that value. If you have var x = await something; x.update(whatnot); yield x.whatever;, then completing with null will make the code fail badly. Completing with any other value is likely just as bad, because it STILL won't be the correct value that would allow the code to continue without issues. Throwing immediately is also unlikely to be what you want, then you would have to defensively wrap the entire body of any async* function with a catch to avoid it throwing on a cancel.
One alternative is to make it throw an AsyncCancelException and make async* function bodies implicitly catch that and complete the stream normally. That would allow cancelling an async* method at any await, not just at yields.
This was actually considered originally, but was rejected because it made it incredibly hard to reason about the code. Something as simple as:
var res = await allocateResource();
try {
 . ..
} finally {
  res.dispose();
}

(which is perfectly good async code, if allocation throws, nothing happens, if not, the allocated resource is definitely disposed) would not be safe for async* code. If the await cancel-throws after allocating the resource, but before entering the try/finally, then the resource is not disposed correctly.
If any await can throw (or perform any other control flow), independently of the awaited future, then it is practically impossible to write safe code.
That is why the model is that an async* method only checks for cancel at yield statements. A yield is documented as being able to bail out when the stream is cancelled, but it never happens in the middle of another expression, so expression evaluation stays rational and consistent. If you await a future, the result you get is the result of that future, not anything else injected from the side.
The only semantically reasonable option is to make a cancelled future never complete. Sadly, that's too dangerous to allow.  If the future never completes, the method body is stuck at the await, and won't execute finally blocks. Example:
var res = allocateResource();
try {
  while (await res.fetchNextPage()) {
     for (var entry in res.currentPage) yield entry;
  }
} finally {
 await res.dispose();
}

Now, if this async* body was cancelled, and it cancelled the awaited future returned by res.fetchNextPage(), then execution would not continue. It would block at that await.
Which means that the resource is never disposed.
Blocking non-completing futures can already happen by accident, but when it does, it's usually a hard-to-debug error caused by some future accidentally never completing. Allowing it to happen for every await in an async* body is far too scary to contemplate.
This is all an aside from cancelable futures, saying why even if we had them, an async* stream cancel would not cancel an awaited future in the method body anyway.
It also describes some of the issues with canceling futures. If only some futures were cancelable (say, all futures had a cancel method to request a cancel, but no promise that it would do anything), then those futures would still have to figure out how to behave after cancel: complete with a default value/provided value/null (won't work when we have non-null types), throw or block.
All in all, we are not planing to make futures cancelable. The API is all wrong for that.
If we had designed futures differently from the beginning, maybe, and only maybe, would we have had a way to make them cancelable in a meaningful way.

Thanks for the replies & clear explanations.
If making Future cancelable is not an option, would moving CancelableOperation to dart:async be possible? So the problems cannot be solved by cancelable promises, but the need of something that:

is lightweight
represents a cancelable asynchronous operation
resolves to one value
can block async* in some way and can be automatically canceled (as @nex3 demonstrated)
usable in core libraries, especially dart:io, to encourage 3rd-party usage
may still exist.
I'm not sure if it still belongs to this issue, but CancelableOperation seems to be covering most potential use cases for cancelable promsies, except not being in the core libraries.
This may be relevant to https://github.com/dart-lang/sdk/issues/33713.


Add in flags so notification and features don't show for GuestMode

No features for you GuestMode
No notifications for you GuestMode

:+1:

:+1:

:+1:


SyntaxErorr When Module Contains Import Statement

Problem
When a module contains an ES2015 import statement I get a SyntaxError:
ava test.js

/home/booker/Code/ava-test/index.js:1
(function (exports, require, module, __filename, __dirname) { import _ from "lodash";
                                                              ^^^^^^

SyntaxError: Unexpected reserved word

How to reproduce
nvm use 5.0.0
npm install -g ava
npm install ava
npm install lodash

index.js:
import _ from "lodash";

test.js
import test from 'ava';
import sut from "./";

ava

AVA doesn't transpile your code, only your test file.
You probably want https://github.com/sindresorhus/ava/issues/111.

Thanks, @sindresorhus. I'll look into that now.


Remove scss loader dependency

When trying to import this as a Vue component (import DatePicker from 'vue2-slot-calendar') and error is thrown regarding the missing style loader.
This dependency was not found:

* !!vue-style-loader!css-loader?{"minimize":false,"sourceMap":false}!../../vue-loader/lib/style-compiler/index?{"vue":true,"id":"data-v-6fe5cf14","scoped":false,"hasInlineConfig":false}!sass-loader?{"sourceMap":false}!../../vue-loader/lib/selector?type=styles&index=0&bustCache!./Calendar.vue in ./~/vue2-slot-calendar/lib/Calendar.vue

To install it, you can run: npm install --save !!vue-style-loader!css-loader?{"minimize":false,"sourceMap":false}!../../vue-loader/lib/style-compiler/index?{"vue":true,"id":"data-v-6fe5cf14","scoped":false,"hasInlineConfig":false}!sass-loader?{"sourceMap":false}!../../vue-loader/lib/selector?type=styles&index=0&bustCache!./Calendar.vue

This is due to the fact that the Calendar.vue file is uses scss.

you can use these.
'vue2-slot-calendar/lib/calendar.js'
'vue2-slot-calendar/lib/calendar.css'


[WIP] Add Appium tests

This is something I had in my local for a while, I don't think this is ready.
Just wanted to push it see if it can bring any value to the project, and bring some discussions about testing.
How this works
I'm basing the tests on the example project, and do an integration testing using Appium.
npm run compile:test-ios will compile the app
npm run mocha:test-ios will run the test suite for iOS
Unfortunately for some reason map elements are hard to test.
For Callouts.js wanted to check if the marker callout was open but didn't find a way ( I can do that by having some text showing in a Text about the status of the callout ).
So right now the tests are not really interesting but they could be more if we think more about what the view is doing and showing.
NOTES
Android compilation does not seems to be working anymore, had it working before. How do you guys run the example project in local?
TODOS
I put it in those tests on Travis before, but they take a while to run :/, we can cache the compilation to make it faster.
Compilation:

Tests Running:

This is awesome!!! Thank you!!! We'll take a look soon.
Re: the Android compile issues, we've seen that reported a few times, and will look into it.

YASSSSSSSSSS.  @jrichardlai awesome work. Let's definitely figure out a way to get this in!

(iOS) status note here:
I got the test running on Travis ( green yay ), it will take I think max 20 mins for the whole suite to run (right now run with 14mins but was not really a relevant suite), I think for this project it might be acceptable as there should not be a lot of PR's that would go in. I also separated eslint and Appium. Thoughts?
However I upgraded to XCode 8 and seems that there is several issues with Appium (BOO), as Travis supports it I think its better to be on XCode 8 anyways, but will need more investigation to fix the build.

@jrichardlai awesome work. Yeah, we should all be working out of xcode8 if possible, so if things are breaking right now we should fix (separate PR maybe?).

I'm getting this error when running mocha:
[APPIUM]: Error [MJSONWP] Encountered internal error running command: Error: Xcode version [object Object] is not yet supported

Perhaps because i'm on Xcode 8?

Also, the Android build works for me locally.  Maybe try again?

Thanks @lelandrichardson, @spikebrehm for looking at the PR!

LGTM @jrichardlai

@jrichardlai great job. Are you willing to update the PR for the last version of the module and be sure it still runs? 😁
Thanks a bunch  🤗

@jrichardlai  we're trying to cleanup the repo, so I'll close this PR . I got no reply from you on my last message in December  so please ping me if you think you can continue working on it and I'll re-open 🤗


[DOCKER] Unable to find tag latest on docker hub repository

Hello there!
The latest tag is not mandatory but it's recommended and a good practice in Docker repositories.
Regards.

Added the latest tag and we'll be maintaining that from here on out — thanks for the recommendation.


core: pod update

Move the toolbar horizontally
add delete pod

Thanks for your awesome work. Many bugs in my code are fixed in your PR, thanks a lot. However, I fetched this branch and tested, some tiny issues show up on my side but I'm not sure what cause them. Can you help me investigate them?

The size of codeNode fluctuates when editing on its editor.
Even when the cursor is in the editor, the codeNode is selected and draggable by cursor movement. But we are not supposed to enable the drag operator when editing, we intend to only drag the pod by the drag handler we set.
the input index is not correct, it doesn't update after run. Refresh the page, they appear but are even out of order.

@li-xin-yi ok, i will check this

@lihebi @li-xin-yi
I asked @nibilin33 to remove the shadow. It is buggy and is now redundant given now editor borders can be highlighted when focused or in editing. But if you have a reason to use shadow, please let me know.

@lihebi @li-xin-yi I asked @nibilin33 to remove the shadow. It is buggy and is now redundant given now editor borders can be highlighted when focused or in editing. But if you have a reason to use shadow, please let me know.

@forrestbao  Thanks for the advices. I meant to use the box shadow and its color to show which user is dragging or selecting the pod, which are of the same color with the remote cursor. This is also the awareness feature in collaborative editing. I know it may look awkward, but I have no idea how to show the awareness info for dragging/selecting operation of pod in a proper form. Can you give me any suggestion?

@forrestbao Thanks for the advices. I meant to use the box shadow and its color to show which user is dragging or selecting the pod, which are of the same color with the remote cursor. This is also the awareness feature in collaborative editing. I know it may look awkward, but I have no idea how to show the awareness info for dragging/selecting operation upon a pod in a proper form. Can you give me any suggestion?
BTW, in my experimental demo (https://github.com/li-xin-yi/sharing-edited-monaco-flow), I convey the awareness and movement information by setting the pod half-transparent and changing its background color. But it seems not so suitable in our project.

@li-xin-yi  Ah, i didn't notice the shadowing is for dragging indication. Maybe we can use border highlighting, and potentially bolding, for both code editing and dragging?

@li-xin-yi the issues you mentioned fixed

The merging problems seem complex. There is a lot of code that was removed in #61 that got added back in this PR. It's pretty hard to catch what they are. Also, this PR is getting too large to review. This might create additional conflicts with other changes that Xinyi and I are working on.
Maybe let's split this PR into smaller pieces?


Can we transfer the output mesh and texture to FLAME topology?

Hey @FuxiCV,
Thanks for this amazing work.
I tried the repo and got nice results.
Can we transfer the output mesh and texture to FLAME topology ?

perhaps FLAME-fitting is all your need.


Sync 2023a branch with cherry-picked commit from main

Sync 2023a branch with cherry-picked commit from main
Description
Commits are cherry-picked from main.
From close comparing of what is missing from 2023a
https://github.com/opendatahub-io/notebooks/compare/2023a...main
How Has This Been Tested?
No Test needed
Pre-tested on main
Merge criteria:

[x] The commits are squashed in a cohesive manner and have meaningful messages.
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has manually tested the changes and verified that the changes work

The new images, code-server (76ce3a6), RStudio (487af29), and cuda-rstudio(94d2a7a), are currently in incubation mode, and we don't need to push them to the release branch at this time. Could you please exclude them from the sync?

moving the commits doesn't get the content in the RHODS.
as we would need to include them in odh-manifest
which is where we would not include them

Thanks for review
Approving for merge
/approve


Issue with cubit.pyx

I'm trying to run a miner following the documentation. I have already created my coldkey and my hotkey, installed cuda and checked that is available through console, and also installed cubit as described and verified that I'm able to import it. But when I try to run btcli run --cuda to start registration, an error is thrown.
Note that no issue seems to be occurring when I just run btcli run.
The error:
/home/jj/bittensor/bittensor/cubit.pyx:164 in cubit.solve_cuda   [Errno 2] No such file or directory: '/home/jj/bittensor/bittensor/cubit.pyx'  TypeError: an integer is required ⠸ Solving%
Environment:

Linux Ubuntu 18.04
Python 3.9bit
Bittensor Version pulled from master

I'll open you an issue in the cubit repo https://github.com/opentensor/cubit/issues/1


cifar10 data

Hi,
Thanks for the package and note on the code. I am trying to learn from it. I tried to walk through "robustness" application but I do not have the data, cifar-10.
It was noted in the datasets.py in csl.datasets that
You can download the dataset in PyTorch tensor format from
https://www.seas.upenn.edu/~luizf/data/cifar-10.zip

However, the link is already expired. Can you suggest how can I obtain the data?
Thanks,
Mai

Sorry @tsuttaket, for some reason I don't get notified when someone posts an issue here!
I've updated the link to my new domain. Thanks for letting me know!


Do not use jedi package for autocompletion

This results in the following config when executed with repo2docker . locally:

Hopefully, it works in mybinder.

For the interactive disabling of jedi, the following in-cell command can be used:
%config IPCompleter.use_jedi = False

Relevant to:

https://github.com/NSLS-II/playbooks/pull/226
https://github.com/NSLS-II/ophyd/issues/683

Seems to work in mybinder: https://mybinder.org/v2/gh/mrakitin/tutorial-bluesky/no-jedi-anymore?urlpath=lab

Nice work. I opened a PR against your branch with a minor refactor to consider.

Seems to work fine.
It's disappointing we have to disable it though -- the interface looks really nice:

Agreed.


package & function names

Package name:

stellar
ghstar

Function name (current vision is a single, primary function)

ghstar
stars

Current inclination:
stellar::stars()

I love that - "beautiful pint wifebeater". But not such good news otherwise - new name suggestions anyone?

If you want starryeyes you can have it.

I don't mind stellar but the fact that it's taken on CRAN means it's a non-starter. stargazer would have similarly been very appropriate if not already taken.
telescope? (I wouldn't make the connections noted myself)

telescope is good. stella is also available, as is plain old starry, which i admit a preference for over starryeyes, which brings to my mind images of cataracts and the like :cry:, alas.


Minor changes

Put SFML version number in CMakeLists.txt
Fixed typo in sidebar: Weaponry
Fixes #51 and #46

Regarding the failing check, I think SFML version 2.4 is the minimum required because the code uses some functionalities not present in the previous version. Like, sf::text::setFillColor()

Wow - 2 issues! :+1: And disregard the travis checks, they never work (yet.)


drivers: adc: stm32: fix stm32u5 extended calibration

Add Data Memory Barrier during the extended calibration of STM32U5, as it is done in STM32Cube HAL, to avoid sporadic errors during calibration that may result in measures that are offset from real values.
Fixes #78459

Adding DNM tag until approved by @FrankZShen

Approved by @FrankZShen in #78459. Remove DNM and ready for review


Suspected wrong collection type

entries: BTreeSet<Entry>,
should be
entries: Vec<Entry>
in transaction.rs

Or entries: HashSet<WrappedEntry>, where WrappedEntry uses a stable hash code like seq


#[derive(Reflect)] on enum that wraps another enum does not work

Bevy version
Tried: 0.9 and 523072902cecad440b5d2109077e437fcb7580b6
What you did
Deriving Reflect on a simple enum works:
#[derive(Reflect)]
enum Inner {
    Foo,
}

But deriving Reflect on an enum that wraps another enum does not:
#[derive(Reflect)] // <-- the trait `FromReflect` is not implemented for `Inner`
enum Outer {
    Inner(Inner),
}

This should be documented on the Reflect trait via a doc test :)

Should we close this out and open a new issue for the documentation on Reflect (or maybe Enum) to indicate this?

Yes please. Ping me when you've made one and I'll do so.

@alice-i-cecile created #6985


adds auction error/debug event for analytics adapters to subscribe to

Suggested addition to https://github.com/prebid/Prebid.js/pull/5563

Hi @patmmccann ,
After merging there are some analytics failing tests, please check them.

I see sigmoid and prebidanalyticsadapter tests are causing errors and should be expecting 7 events after this change instead of 5 or 6. Does it make sense to just change those to 7?


[Feature] Helm Chart Releases in Artifact Registry

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
I would like to be able to install kuberay via helm from an official artifact registry.
Currently I maintain my own registry based off my kuberay fork
This is not ideal though due to the effort required merging from upstream.
Use case
As a kuberay user I would like to add kuberay as a helm dependency to my application charts.
I.e.
# chart.yaml
apiVersion: v2
name: operators
type: application
version: 0.1.0
dependencies:
  - name: kuberay-apiserver
    version: 0.3.0
    repository: oci://ghcr.io/ray-project/kuberay/helm-chart
  - name: kuberay-operator
    version: 0.3.0
    repository: oci://ghcr.io/ray-project/kuberay/helm-chart

Related issues
No response
Are you willing to submit a PR?

[X] Yes I am willing to submit a PR!

We have a GitHub repo ray/kuberay-helm to host Helm charts since release 0.4.0.
I did the following experiment.

Step 1: Clone https://github.com/itsnashter/helm-chart-dependency
Step 2: Create a file database/requirements.yaml as follows.dependencies:
  - name: kuberay-operator
    version: 0.4.0
    repository: https://ray-project.github.io/kuberay-helm

Step 3: Execute the following commands.helm dependency update ./service/
helm dependency update ./service/
helm dependency update ./application/

helm install myapp ./application/

# KubeRay operator has been created successfully.
kubectl get pods | grep kuberay-operator
# kuberay-operator-d46877b4f-ck6nn     1/1     Running            0             6m26s

thanks, didn't know about this! Closing.


68000: lsr doesn't set XF flag

As an example:
0021f226 e2 8d           lsr.l      #0x1,param_3
0021f228 67 02           beq.b      LAB_0021f22c
0021f22a 4e 75           rts
LAB_0021f22c
0021f22c 2a 20           move.l     -(param_2),param_3
0021f22e e2 95           roxr.l     #0x1,param_3
0021f230 4e 75           rts
Decompiled output:
dword FUN_0021f226(byte xf,dword *param_2,dword param_3)
{
  ulonglong uVar1;

  if (param_3 >> 1 != 0) {
    return param_3 >> 1;
  }
  uVar1 = (ulonglong)param_2[-1] << 1 | (ulonglong)xf;
  return (dword)((uVar1 << 0x20 | uVar1 >> 1) >> 1);
}

It's wrong, because lsr.l should set XF flag, and then be ORed. But decompiled output does require providing XF as an function argument.

Information about lsr.l operand instruction:
Input Objects:
   D5, const:0x0, const:0x1
Result Objects:
   CF, D5, NF, ZF

CF:
C Set according to the last bit shifted out of the operand.
Cleared for a shift count of zero.

And XF:
X Set according to the last bit shifted out of the operand.
Unaffected for a shift count of zero.

It is also requires to change lsl instruction.


zarr-python v3 compatibility

So far the only tested file type is HDF5. Thats the only module that currently works with new zarr python in some way

Also worth noting... zarr 3 doesn't support numcodecs codecs out of the box. There is a pr to help this https://github.com/zarr-developers/numcodecs/pull/524 () but it would mean a change to codec names which causes an incompatibility. For the initial icechunk examples we handle this in virtualizarr but long term it probably belongs here to work standalone.

When this https://github.com/zarr-developers/zarr-python/pull/2425 goes in it should unblock this to work full with zarr python v3.
We will also need to create both numcodecs and zarr v3 codec versions of all the custom kerchunk codecs so that a given dataset can be loaded in either v2 or v3 contexts (say if yuou kerchunk a grib file, then want to convert those references to an icechunk store

create both numcodecs and zarr v3 codec versions of all the custom kerchunk codecs

Is that a subclass in each case, specifying that it is to be bytes->bytes?

Sorry the numcodecs versions exists as they are today. Yes the v3 version would be basically using the numcodecs versions.
Although grib decoder should really be bytes to array i think

This is required upstream: https://github.com/fsspec/filesystem_spec/pull/1734

Also of note: To get this to work with zarr 3, we pass an fsspec ReferenceFilesystem to a zarr RemoteStore. This works fine with remote filesystems (where the references live) that have async implementations (s3, http, etc) but does not work when the references are on filesystem with only a sync implementation (local, etc). The tests heavily depend on the local filesysmte, and im sure many others do as well so it needs to be figured out how the interaction of sync filesystems and the async zarr RemoteStore requirement work out

Grib works as long as read in zarr 2 format.
To be used with zarr 3 the codec needs to be ported over to the new abc.Codec class from zarr

I think one change that should be made for compatibility with zarr 3 and virtualizarr is that the Grib2 codec moves from filters to compressors.

the Grib2 codec moves from filters to compressors

It returns an array, though - this was already pointed out. I think there is an assumption that compressors map to byte->byte codecs.

Ill change it back for now. Will discuss with zarr folks

State of the Union post merge with @moradology and installing latest fsspec and zarr 3
pip install git+https://github.com/fsspec/filesystem_spec

test_grib.py: 1 Failure
test_netcdf.py: 3 Failures
test_hdf.py: 11 Failures
test_df.py: ✅
test_utils.py: 3 Failures
test_fits.py: 5 Failures
test_zarr.py: 2 Failures
test_combine.py: All Failed
test_combine_concat.py: 8 Failures
test_combine_dask.py: 3 Failures
test_xarray_backend.py: 1 Failure

A lot of these are the same errors over and over a again. The hardest part will be maintaining compat for zarr python 2 library which I am not sure if it should be a goal of this PR @martindurant


Netty seems to get stuck on routes with browsers

Using curl you can switch between /ping and /healthcheck and you get expected data.  Curl commands don't use http persistent connections.
Using Chrome or Safari, if you go to /ping and then /healthcheck you get  pong for healthcheck.  Similary if you go to /healthcheck and then /ping you get healthcheck status.
I validated via netstat that Chrome keeps a http persistent connection to Prana.  It turns out that as long as this stays open you get stuck in the routes.  I closed Chrome to the point of killing the process and was able to see the other url (but then got stuck again).

@NiteshKant Can we close this now? We could move to a new version of RxNetty

I hit this issue today. First time trying out Prana and thought it was something I was doing.

I think this was related to the karyon issue: https://github.com/Netflix/karyon/issues/126
which was fixed in 2.2.00-ALPHA1

does anyone have an update for this? I'm regularly hitting this issue.

The issue is fixed in karyon, I guess prana has to pick up the latest version of karyon.

Thank you all for the contribution.  More will be coming, but please see http://ispyker.blogspot.com/2015/10/towards-being-better-about-open-source.html for a bit of context on the status of this project.


Coinbase Pro?

@nicka Just wondering if this can be used with Coinbase Pro (formerly GDAX)?

@danielbayley, I think so. Because the API endpoint didnt change, its still https://api.coinbase.com


Rename ManualWithDocuments

This branch renames ManualWithDocuments and its methods to reflect the language of the domain.
Note that there are still lots of variables (in code and test) that refer to 'documents' instead of 'sections'. I'm intentionally not changing them in this branch as it's a big enough change as it is.

Thanks @chrislo! I'm going to hold off renaming other instances of document and doc in this branch as I'm confident we'll get to them soon enough.


cai i find any document for using the rex

I am fresh man in AEG, please provide a document for the project or tell me a url to know how rex works.

read paper & code

Currently there is no documentation in using rex. For now, the code is the documentation.
Once it's more stable we will have documentation.

please provide a document for the project or tell me a url to know how rex works.

Note that it is not our priority to provide documentation. This is an open source project and everything is provided "as it is". I feel it is an English problem, but if it's not, the way you state your request makes me feel insulted.

I am so sorry to use the wrong words. I just want to have a quick understand about rex.


Let skip --enable-debug=no

We are erroring out when we find a --enable-debug but we don't check if it was a actually an explicit =no to actually avoid the debug symbols.
Signed-off-by: Chmouel Boudjnah<EMAIL_ADDRESS>

actually the debug symbols you want them they get split out into the .Debug. --disable-debug doesn't work? Debug shouldn't be the default though.

Merging this as this avoid a false positive.


ddev xdebug toggle and ddev xdebug status hang if xdebug is enabled and an IDE is listening for xdebug

Expected Behavior
ddev xdebug status and ddev xdebug toggle should "just work" no matter what the situation.
Actual Behavior
If an IDE is listening on port 9003, and xdebug is enabled, both of these hang.
Steps To Reproduce

Start PhpStorm and make it listen.
ddev xdebug on
ddev xdebug status or ddev xdebug toggle will hang

Anything else?
More detail and ideas in

https://github.com/ddev/ddev/pull/6082#issuecomment-2113616515
and following comments, thanks to @GuySartorelli

We can probably safely use php --version | grep -i xdebug for this more safely and prevent this problem.
It would also be trivial to change to XDEBUG_MODE=off php -r 'echo ini_get("xdebug.mode");', which would work for Xdebug 3, it might not be right for Xdebug 2.

Unable to replicate on VSCode. Perhaps we can replace "IDE" with "PHPstorm" in the title and description?
Test

Open DDEV project in VScode
Start Debug listener in VScode
Toggle xdebug in DDEV:

$ ddev xdebug toggle
Building project images...
...
Enabled xdebug

VSCode continues to function

Can open new files
Update files
navigate around menu
enter commands in terminal

DDEV: 1.23.0
VSCode: 1.89.1
VSCode xdebug.php-debug 1.34.0

The problem happens when you:

Enable xdebug
THEN ddev xdebug toggle.

OK,
Test

Create break point
Turn on listener in Vscode
Turn on xdebug

$ ddev xdebug
Enabled xdebug

Confirm breakpoint is it. Continue through to allow page to load.
Toggle xdebug

$ ddev xdebug toggle
Disabled xdebug

No problems.
Turn on xdebug

$ ddev xdebug
Enabled xdebug

Confirm breakpoint is it.
While on breakpoint, toggle xdebug

$ ddev xdebug toggle
Disabled xdebug

Vscode removes debugging info. Site displays as "502 Bad Gateway", but displays correctly on refresh. Things seem to work as expected.

Thanks for the careful testing.  I doubt that this is different between PhpStorm and vscode, but it may very well be different between macOS (where I tested) and Win/WSL2.
In my testing I didn't exercise the website or breakpoints at all. I just ddev xdebug and then ddev xdebug status or ddev xdebug toggle

Just tried on Gitpod to remove the OS variable.
Running ddev xdebug and then ddev xdebug status  then ddev xdebug toggle doesn't seem cause any hangs in the Gitpod VScode or it's terminal.
Can anyone replicate it on Gitpod or Codespaces?


Updates snippet to reflect the correct order of middleware for static…

… asset serving
The current snippet (whitenoise middleware at the top of the middleware list) is incorrect and contradicts what is outlined both in the official documentation for the library and the djangoapp sample provided as part of the Python Azure-Samples.

@BeigeBadger : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off