Closing all the files in the neovim editor result in the focus shifting from the filesystem to the buffer

Opening the file explorer in neovim will result in the "Bufs" tab being focused instead of the "File" tab sometimes when I close all the buffers in my nvim editor. This seems to happen randomly and there seems to be no explanation as to why this happens.
Setting the source to filesystem seems to fix the problem but is this really the desired behaviour for this plugin?

We would need to have a list of steps to reproduce along with your config to help you troubleshoot this. It definitely sounds like a configuration or confusion about usage type problem.


Data arrangement

I would like to know the data type and the data file how should be arrange.

Hi,
Thanks for taking an interest in the repo. The folder format is:
root/
├── raw_data/
├── filtered/
│   ├── trainA/
│   └── testA/
│   └── valA/
│   └── trainB/
│   └── testB/
│   └── valB/
├── trainA/
├── testA/
├── valA/
├── trainB/
├── testB/
└── valB/

All images should ideally be stored as float32.
An example of the folder format as well as example datasets will be release when the manuscript is publish.
Cheers,
Paul

Thank you so much for your fast reply.
I have further questions
have trainA and trainB  included 2 volumeric samples ? and has the volumetric sample stored as slices? and what extension ends the slice images ?
thank you very much to answer my questions, because I am so confused.

For both A and B volumetric images are used not slices. Their raw files (.tiff) are contained in subfolders in raw_data


Don't use conditionals inside the head

Potential fix for hydration error

Encountered a related issue perhaps when upgrading to svelte5 and using the Head component. THe meta tags are not closing correctly.
It might be related to this nuance https://svelte.dev/docs/svelte/v5-migration-guide#Other-breaking-changes-null-and-undefined-become-the-empty-string where null values are perhaps being converted to empty strings?

Thank you @emileswain! We will investigate.
@stefanoverna Left you details in Basecamp

@stefanoverna Added some tests. One big change at https://github.com/datocms/datocms-svelte/pull/14/files?diff=split&w=1#r1876437362 and other minor cleanup throughout.
@emileswain For now, in here, we'll just patch around it by serializing the head. But I think we should open a new issue with Svelte directly to continue discussing the <svelte:element> issues with a minimal example. I'll do that in a bit and tag you there. TY again for the help here!

@stefanoverna Added some tests. One big change at https://github.com/datocms/datocms-svelte/pull/14/files?diff=split&w=1#r1876437362 and other minor cleanup throughout.
@emileswain For now, in here, we'll just patch around it by serializing the head. But I think we should open a new issue with Svelte directly to continue discussing the <svelte:element> issues with a minimal example. I'll do that in a bit and tag you there. TY again for the help here!

Makes sense, fyi, sorting the seotags so content elements come last, worked as a temporary fix.

Thanks, merged and squashed as https://github.com/datocms/datocms-svelte/commit/ec728a18e9b43b3dc5e2db17861c21d70e119ccb

@emileswain FYI I was trying to replicate this in a fresh minimal example for the Svelte team, but I could not.
Turns out our starter kit just had some old dependencies. Upgrading vite and vite-plugin-svelte fixes the hydration error, both with or without my hacky workaround above. Just FYI. Sorry about that.
If you already implemented  "@datocms/svelte": "^4.0.1",, that should still keep working.

Hmm interesting,I did upgrade those packages as part of my upgrade to
svelt5. Which is when I encountered the issue.
I’ll check my project and see if I still have the problem.
Thanks
E
On Thu, 12 Dec 2024 at 21:18, Roger Tuan @.***> wrote:

@emileswain https://github.com/emileswain FYI I was trying to replicate
this in a fresh minimal example for the Svelte team, but I could not.
Turns out our starter kit just had some old dependencies. Upgrading vite
and vite-plugin-svelte fixes the hydration error, both with or without my
hacky workaround above. Just FYI. Sorry about that.
If you already implemented @.***/svelte": "^4.0.1",, that should
still keep working.
—
Reply to this email directly, view it on GitHub
https://github.com/datocms/datocms-svelte/pull/14#issuecomment-2540032229,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGWUOQ6KDJVPWJCWV3BGLD2FH4TNAVCNFSM6AAAAABTDUIBH2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBQGAZTEMRSHE
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hmm interesting,I did upgrade those packages as part of my upgrade to svelt5. Which is when I encountered the issue.

Dumb question, but did you npm install after upgrading them, and were there any dependency issues? On our starter kit, it wouldn't let me seamlessly upgrade in-place because some dependency conflicts. I had to manually clear node_modules and regenerate the lockfile before the upgrade would go through. I think VScode doesn't always make it clear when the package.json doesn't match the actual installed versions?
(Sorry if that was obvious! Just making sure)

I checked again and noticed that I may have had the component embedded
twice. Once in the page and a second time in the layout. So it might have
been user error on my part. Haven’t had a chance to double check, but might
explain it.
On Mon, 16 Dec 2024 at 18:06, Roger Tuan @.***> wrote:

Hmm interesting,I did upgrade those packages as part of my upgrade to
svelt5. Which is when I encountered the issue.
Dumb question, but did you npm install after upgrading them, and were
there any dependency issues? On our starter kit, it wouldn't let me
seamlessly upgrade in-place because some dependency conflicts. I had to
manually clear node_modules and regenerate the lockfile before the upgrade
would go through. I think VScode doesn't always make it clear when the
package.json doesn't match the actual installed versions?
(Sorry if that was obvious! Just making sure)
—
Reply to this email directly, view it on GitHub
https://github.com/datocms/datocms-svelte/pull/14#issuecomment-2546304861,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGWUOSPZCPERDRZEZAUCHL2F4JCNAVCNFSM6AAAAABTDUIBH2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBWGMYDIOBWGE
.
You are receiving this because you were mentioned.Message ID:
@.***>

No worries. Hopefully the new version and upgrades will still fix it, either way. But if you do run into issues again, please let us know!


Conflicting configuration file location in readme versus dockerfile

The dockerfile expects by default /var/config/sfproxy/sfdbproxy.conf, however the readme states:

It assumes you will have a sfdbconfig.json file cross mounted to /var/config/sfproxy/sfdbconfig.json for the docker container.

The filenames are not the same which can be misleading.

Thanks for the ticket!  I modified the README.  Please let me know if you find anything else!


Folders/dirs not deleting, even when empty

Deleting directories, even when empty, does not work. The directories persist.
Expected Behavior
When selecting a directory and executing a delete, the directory is no longer there after refreshing my client.
Current Behavior
When selecting a directory and executing a delete, the directory is still there after refreshing my client, and persists no matter how many times I try to delete.
Steps to Reproduce (for bugs)

Create a directory
Store something in it
Delete the stored file
Delete the directory
Refresh the client

Screenshots
Deleting empty dirs from the top level

Choose delete

View after the action was executed by the interface

View after refreshing the client

Deleting an empty leaf dir

Choose delete

View after the action was executed by the interface

View after refreshing the client

Context
When we deploy a minio solution for a customer, we test the solution with the client the customer will be using (in this case Veeam) to ensure they have no issues. Then we remove the test data uploaded to the system, and clean everything out ready for the customer to take ownership of their solution.
While cleaning out for our current customer we found that the directories will not successfully be removed. They persist regardless of which client is used to remove them, including the Minio's own web interface.
Your Environment

https://hub.grid.tf/tf-autobuilder/minio:v201028.83658.0-dev.flist

This bug is more complex than it looks. The thing is when a "file" is deleted (since we have versioning enabled by default) the file is actually never deleted, instead it's only marked as deleted. The file history can still be accessed if you try to list files (in that folder) with --versions it will still show all the files with all the revisions.
That's the reason the folder can not be deleted, because actually it's not empty.
I am not quite sure how to handle this atm. I will have to do some research regarding the behavior of the folders when versioning is enabled.

Could folder be marked as deleted (but not actually removed) in the same manner?


glibc: bump the minimum kernel version

I don't think anyone sane is really using kernel < 3.10 nowadays. (At least in a use case with glibc from nixpkgs.)
As another suspect with old kernels, Ubuntu seems to start at 3.13 now.
Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

Part of this was done in PR #188492, but I think this is worth a separate PR.  It's quite an unrelated question to discuss, and much simpler to decide and merge (no packages should be affected).

I'm not aware of anything wrong.  Just that RHEL 6 seemed not relevant anymore, and that's why I thought it possible to do this cleanup and raise kernel versions (RHEL 6 has heavily patched 2.6.32 kernel).


update temperature in gpt_resume_job_description.py

update temperature for generating resume with job description to reduce hallucination.

@feder-cr can you pls merge this to main.


rviz: 10.0.0-1 in 'rolling/distribution.yaml' [bloom]

Increasing version of package(s) in repository rviz to 10.0.0-1:

upstream repository: https://github.com/ros2/rviz.git
release repository: https://github.com/ros2-gbp/rviz-release.git
distro file: rolling/distribution.yaml
bloom version: 0.10.7
previous version for package: 9.1.1-3

rviz2

No changes

rviz_assimp_vendor

No changes

rviz_common
* Install headers to include/${PROJECT_NAME} (#829 <https://github.com/ros2/rviz/issues/829>)
* Remove definition of PLUGINLIB_DISABLE_BOOST. (#821 <https://github.com/ros2/rviz/issues/821>)
* Contributors: Chris Lalancette, Shane Loretz

rviz_default_plugins
* Install headers to include/${PROJECT_NAME} (#829 <https://github.com/ros2/rviz/issues/829>)
* Remove definition of PLUGINLIB_DISABLE_BOOST. (#821 <https://github.com/ros2/rviz/issues/821>)
* Contributors: Chris Lalancette, Shane Loretz

rviz_ogre_vendor
* Fix the build for Ubuntu Jammy arm64. (#828 <https://github.com/ros2/rviz/issues/828>)
* Contributors: Chris Lalancette

rviz_rendering
* Install headers to include/${PROJECT_NAME} (#829 <https://github.com/ros2/rviz/issues/829>)
* Contributors: Shane Loretz

rviz_rendering_tests

No changes

rviz_visual_testing_framework
* Install headers to include/${PROJECT_NAME} (#829 <https://github.com/ros2/rviz/issues/829>)
* Contributors: Shane Loretz

This pull request has been mentioned on ROS Discourse. There might be relevant details there:
https://discourse.ros.org/t/holding-releases-to-perform-rolling-transition-to-new-platforms/24191/13


Rename the new uid option

[x] I have checked that a similar feature request does not already exist.

dev branch has a new option called uid, for differentiating multiple running Scrcpy instances. IMO it should not be called uid, because uid is a common Linux concept, which might be useful in other cases.
For example, with this little change, I can create a secure display on rooted Android 12+ devices (tested in an emulator):
https://github.com/Genymobile/scrcpy/compare/dev...yume-chan:scrcpy:feat/secure-display?expand=1
Unrooted:

Rooted:

Use setUid(2000) instead of 1000 can fix issues like #1606
So, the new option should be renamed, the new name can be instance_id or other more descriptive names.

I renamed from uid to scid: 439a1fd4ed3d7ada4c5098a6d52893dd4e87082a :+1:
(I want to keep the name short, because on some devices app_process segfaults when the total command length exceeds 256)

For example, with this little change, I can create a secure display on rooted Android 12+ devices

Oh, great :+1:

I see that you are doing a lot of R&D work (I'm still working on audio integration), that's awesome :+1:
Do you work on it in the context of ya-webadb?

ya-webadb is my personal open-source side project, which starts at an experiment of WebUSB API. Before that, I had very little experience on C, Java and Android.
I wouldn't say my works on Scrcpy is "for" or "in the context of" that project. I knew and used Scrcpy way before starting ya-webadb. Integration of Scrcpy in ya-webadb is simply because Scrcpy is the best application I know that uses ADB and Android Shell permission.

Thank you for your work anyway, very useful! :+1:


fix incorrect path to trusted root dir

It's not possible to run the example app in development mode (not frozen):
INFO:__main__:my_app 1.8
Traceback (most recent call last):
  File "c:\Projects\tufup-example_aws\src\main.py", line 13, in <module>
    main(sys.argv[1:])
  File "C:\Projects\tufup-example_aws\src\myapp\__init__.py", line 64, in main
    shutil.copy(src=settings.TRUSTED_ROOT_SRC, dst=settings.TRUSTED_ROOT_DST)
  File "C:\Python311\Lib\shutil.py", line 419, in copy
    copyfile(src, dst, follow_symlinks=follow_symlinks)
  File "C:\Python311\Lib\shutil.py", line 256, in copyfile
    with open(src, 'rb') as fsrc:
         ^^^^^^^^^^^^^^^
FileNotFoundError: [Errno 2] No such file or directory: 'C:\\Projects\\tufup-example_aws\\repo\\deploy\\metadata\\root.json'

The TRUSTED_ROOT_SRC did not point to the path specified by repo_settings.py

The problem with that is that main.py doesn't know about the python files in the project root folder. It will have to be something like
if not FROZEN:
    # for development, get the root metadata directly from local repo
    sys.path.insert(0, str(MODULE_DIR.parent.parent))
    from repo_settings import REPO_DIR
    TRUSTED_ROOT_SRC =  REPO_DIR / 'metadata' / 'root.json'

It is of course possible add the project root folder to your python path but I'm thinking it would be nice if it was working right out of the box without any customizations.

Hmm... then I get this
$ python -m src.main
Traceback (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "C:\Projects\tufup-example\src\main.py", line 4, in <module>
    from myapp import main, settings
ModuleNotFoundError: No module named 'myapp'

@RasmusN Sorry about that: you are absolutely right. Using -m would require imports from src.myapp or relative imports, which would break down when running frozen.
On second thought, I guess your sys.path solution would do fine, as proposed above.

Another thing: In order to be able to run repo_init.py I need to add these two lines:
import sys
sys.path.insert(0, 'src/')

I can add them to the PR if you want


XGD_Runtime Error and Loading Video problem

Hello, thank you to everyone who contributed to this project.
When I try it on Jetson nano, the video feels like loading continuously. It plays after 5 seconds, loads again, plays again for 5 seconds, then pauses. I refresh the page but the same problem continue. It also gives errors related to XGD_Runtime on console.
I created the docker image with the command below.
docker build -f jetson-nano.Dockerfile -t "neuralet/smart-social-distancing:latest-jetson-nano" .
Also I tried it on my PC, the result is same. What am i missing ?

Hi,
Thanks for your feedback :)
It's weird. Can you try running the docker without sudo?

yes, but i can't run docker without sudo command.

yes, but i can't run docker without sudo command.
Try:
sudo usermod -aG docker $USER
Then logout/login or reboot.

@memina Is this solved?

I am having the same issue without any display

Hey, we just got around checking these old issues, sorry about the delay.
The issue could be related to processing speed or the old frontend. Considering a few improvements have been done on the former and that we deprecated the old frontend for a new one on react, I presume this has been fixed. (Although the video streaming is still a bit rough around the edges)
Feel free to try to reproduce it if you are still interested and report back If performance is still an issue. Elsewise I'll close this issue in a week :)

Hey, we just got around checking these old issues, sorry about the delay.
The issue could be related to processing speed or the old frontend. Considering a few improvements have been done on the former and that we deprecated the old frontend for a new one on react, I presume this has been fixed. (Although the video streaming is still a bit rough around the edges)
Feel free to try to reproduce it if you are still interested and report back If performance is still an issue. Elsewise I'll close this issue in a week :)


login dropdown is unreadable

in the attached screenshot, note how you can't read the dropdown choices


When displaying the list, it will appear item by item, rather than all on one page

React-native 7.2.1
flashList 1.6.1
When the list is displayed, it will appear item by item instead of all pages. I hope that the first page will not appear item by item when the first page is displayed, which will look very awkward

+1

Is your estimatedItemSize a good average of the components you're using in the renderItem? having this calculation to large can cause this behavior.

The size of the data returned by the back-end cannot be estimated

The size of the data returned by the back-end cannot be estimated

The size of the data returned by the back-end cannot be estimated

Is your estimatedItemSize a good average of the components you're using in the renderItem? having this calculation to large can cause this behavior.

The size of the data returned by the back-end cannot be estimated

Is your estimatedItemSize a good average of the components you're using in the renderItem? having this calculation to large can cause this behavior.

The size of the data returned by the back-end cannot be estimated

estimatedItemSize refers to the height of each of the items that are rendered in the list, not the length of the list.

@CarlMenke is there a way to have estimatedItemSize be dynamic depending on the item index ?


update alpinejs to v3

resolves #718

Are you sure there's no code changes needed? https://alpinejs.dev/upgrade-guide

Are you sure there's no code changes needed? https://alpinejs.dev/upgrade-guide

Oops! You right .. I'll work on it

I made changes for alpine v3 and everything work fine, except this weird problem with Article tag filter and pagination (Forum tag filter/pagination works fine)

After selecting a tag the filter applies but the modal open again and won't close.
After clicking on a page in pagination bar weirdly opens the filter modal.

I really don't know what's the problem here, so if anyone knows why this happens HELP!
https://user-images.githubusercontent.com/60013703/141702649-4a40b665-d2d2-4cd4-91d1-b45de8a8f1a1.mp4

I have pulled this down and am experiencing the same issue. I'll try and take a look later today.
Out of interest, I notice you have used $nextTick in a lot of places. Were you noticing issues without it?

I have pulled this down and am experiencing the same issue. I'll try and take a look later today.
Out of interest, I notice you have used $nextTick in a lot of places. Were you noticing issues without it?

Yes I had issues without $nextTick. In Alpinejs V3 x-init no longer accepts a callback return so I have to use $nextTick.
https://alpinejs.dev/upgrade-guide#x-init-no-callback

Yes I had issues without $nextTick. In Alpinejs V3 x-init no longer accepts a callback return so I have to use $nextTick.
https://alpinejs.dev/upgrade-guide#x-init-no-callback

Thanks, I found the same issues.
Just to give you a general update. The modal issue you were experiencing seems to be related to Livewire. If I remove wire:click then it works as expected.
We're actually going to remove Livewire from that page and bring it more inline with the forum overview. Once I have done this, I'll rebase this PR and see what (if anything) is still not working as expected.
Thank you for your hard work on this. I will need some of the Alpine v3 functionality for the mentions PR I'm working on.

"We're actually going to remove Livewire from that page and bring it more inline with the forum overview"

This exact idea I had when I faced this problem because it appears only with Livewire.

@faissaloux thank you for your work on this. I'm closing this PR, but your hard work is included on https://github.com/laravelio/laravel.io/pull/764


Harvest should be included in ONTAP's application registry

Not possible with read-only user. Closing


fix:  call destroy on v8-to-istanbul converters to free memory

Summary
See https://github.com/istanbuljs/v8-to-istanbul/pull/161

Test plan
Green CI

Codecov Report

Merging #11896 (5ea40eb) into main (341843f) will decrease coverage by 0.00%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main   #11896      +/-   ##
==========================================
- Coverage   68.73%   68.73%   -0.01%
==========================================
  Files         322      322
  Lines       16580    16582       +2
  Branches     4784     4784
==========================================
  Hits        11397    11397
- Misses       5150     5152       +2
  Partials       33       33

Impacted Files
Coverage Δ

packages/jest-reporters/src/CoverageReporter.ts
59.89% <0.00%> (-0.65%)
:arrow_down:

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 341843f...5ea40eb. Read the comment docs.


Incorrect null check after await

After await call, the _editorModelReference is possible to be null and the type should still be IReference<IResolvedNotebookEditorModel> | null other than never.

Maybe a typo: this._editorModelReference was used instead of editorModelReference?
this._editorModelReference was checked in the if above that it's falsy, then it was checked again if it's truthy without changing the variable value. never seems to be the right type in that case.

@usernamehw this function can be called multiple times, and the async task resolve takes a long time to finish, so for all calls the first this._editorModelReference is null and then stop and wait for the promise the resolve. When the promise resolves, the first call continues, and it sets this._editorModelReference to an object; for the second calls, the this._editorModelReference is no longer null ;(

It's a common pitfall of TypeScript's control flow analysis, see Microsoft/TypeScript#9998 (it's opened in 2016!).
TypeScript can't dig into every function to check whether they change any field (due to performance reason), so it assumes all function to have no side effects.

@yume-chan thanks for the pointer, yes it's definitely a limitation of TypeScript.

Closing as upstream


Effect.mapAccum & Array.mapAccum preserve non-emptiness

Type

[ ] Refactor
[x] Feature
[ ] Bug Fix
[ ] Optimization
[ ] Documentation Update

Description

Related

Related Issue #
Closes https://github.com/Effect-TS/effect/issues/3637

flaky Micro > raceAll test

flaky Micro > raceAll test

The latest next-minor has a fix for those tests, if you rebase.


Fixing broken links

Fixing various broken links.

The reason that I used ./module.ipynb not mxnet.io/... because that link is clickable within notebook, say either you view on github or edit in notebook.
we should let the script located in mxnet/docs/ to automatically change these relative paths to the mxnet.io url, instead changing it manually in the notebooks

Hi Mu,
Can we merge these changes now and I will create issue to update build script to change relative paths and track in different task? I am worried about broken links are already live on mxnet.io for our readers and we received many complaints from customers (SAs).
Thanks,
Sandeep


Updating Chrome and Edge paths

I think dploot cannot fetch Chrome (and sometimes Edge) data on newer systems because of the new paths, maybe there are all the information you need in https://github.com/login-securite/DonPAPI/pull/40 ? :)

Hey, new paths have already been added. Can you provide a debug trace of the tool running ?

Hey, debug is sensible data :eyes: but the debug trace prints everything ("Found MasterKey", "Found MSEDGE AppData files for user X") except Chrome related data

But DonPAPI finds the cookies well, I tested both to debug a little

I'll dig on it

After some digging, I've may have found the problem : a dirty break. Fixed in 0fd2b6b232426ff74f22cea10ed88de110c7b8db.
Closing now, but if there is still a problem, anyone can react on this issue


Refactor/move crypto functions

Try out this version of the Stacks Wallet - download extension builds.

Addresses some renaming/organising of the code that @fbwoolf and I thought will make messaging easier to understand.

@kyranjamie @fbwoolf This looks good from my perspective, at least the naming updates and organization around messaging, however I don't feel as though the folder restructuring makes sense.
Previously we had a folder called "extension" which kept all web-extension based code in its own folder, but now we have it in the root of the app.

To me, this is confusing because it blurs the line between the extension code and the react application code. I'd love for that to be clearer.

@kyranjamie @fbwoolf This looks good from my perspective, at least the naming updates and organization around messaging, however I don't feel as though the folder restructuring makes sense.
Previously we had a folder called "extension" which kept all web-extension based code in its own folder, but now we have it in the root of the app.

To me, this is confusing because it blurs the line between the extension code and the react application code. I'd love for that to be clearer.

I think we were going to move the React code into an app folder?

I can make do the app refactor today, let me know.


Updated top scroll button

Earlier the button was Not looking that much good,
it was just a text for TOP
I have updated it to an Up Arrow symbol
With just a minor change of Unicode
Now the Button looks like this :

It will be easier to understand for the users and Looks better Than TOP written on it

@Karamraj , if PR is okay , can u merge it?


Fix ForEach not adding the element to the stack at the start of each loop

Thoth's Gambit was broken since the rewrite as it didn't add the elements it iterates over to the stack at the start of each loop. This is a simple fixed since it was just a case of re-adding a line from the previous implementation.

Thanks!


Creating volume failed on PhotonOS

ESX: VMware ESXi 6.0.0 build-3620759
VM: Photon (photon-custom-hw11-1.0-13c08b6-GA.ova)
DVD Release: 0.7
Docker version: Server Version: 1.11.0
docker volume create -d vmdk --name=v1
Error response from daemon: create v1: Post http://%2Frun%2Fdocker%2Fplugins%2Fvmdk.sock/VolumeDriver.Create: http: ContentLength=24 with Body length 0

ESX Log:
10/06/16 20:47:28 92462 [P1] [INFO   ] *** createVMDK: /vmfs/volumes/Storage1/dockvols/v1.vmdk opts = {u'fstype': u'ext4'}
10/06/16 20:47:29 92462 [P1] [INFO   ] executeRequest 'create' completed with ret=None
10/06/16 20:47:29 92462 [P1] [WARNING] Failed to find VM by uuid=564dabc0-da80-2e80-1174-d92d69585cc4, retrying...
[Errno 104] Connection reset by peer
10/06/16 20:47:30 92462 [P1] [INFO   ] Found VM name=P1, id=564dabc0-da80-2e80-1174-d92d69585cc4
10/06/16 20:47:30 92462 [P1] [INFO   ] *** attachVMDK: /vmfs/volumes/Storage1/dockvols/v1.vmdk to P1 VM uuid = 564dabc0-da80-2e80-1174-d92d69585cc4
10/06/16 20:47:30 92462 [P1] [INFO   ] Attaching /vmfs/volumes/Storage1/dockvols/v1.vmdk as independent_persistent
10/06/16 20:47:30 92462 [P1] [INFO   ] Adding a PVSCSI controller
10/06/16 20:47:32 92462 [P1] [INFO   ] Added a PVSCSI controller, controller_key=1001 pci_slot_number=192
10/06/16 20:47:33 92462 [P1] [INFO   ] Disk /vmfs/volumes/Storage1/dockvols/v1.vmdk successfully attached. controller pci_slot_number=192, disk_slot=0
10/06/16 20:47:33 92462 [P1] [INFO   ] executeRequest 'attach' completed with ret={'ControllerPciSlotNumber': '192', 'Unit': '0'}
10/06/16 20:47:33 92462 [P1] [INFO   ] *** detachVMDK: /vmfs/volumes/Storage1/dockvols/v1.vmdk from P1 VM uuid = 564dabc0-da80-2e80-1174-d92d69585cc4
10/06/16 20:47:33 92462 [P1] [INFO   ] Disk detached /vmfs/volumes/Storage1/dockvols/v1.vmdk
10/06/16 20:47:33 92462 [P1] [INFO   ] executeRequest 'detach' completed with ret=None
10/06/16 20:47:33 92462 [P1] [INFO   ] *** removeVMDK: /vmfs/volumes/Storage1/dockvols/v1.vmdk
10/06/16 20:47:34 92462 [P1] [INFO   ] executeRequest 'remove' completed with ret=None

Plugin log:
2016-10-06 20:47:29.594555275 +0000 UTC [INFO] Attaching volume and creating filesystem fstype=ext4 name=v1
2016-10-06 20:47:32.496573328 +0000 UTC [WARNING] Get device path failed for unit# %s @ PCI slot %s: 0192Error="open /sys/bus/pci/slots/192/address: no such file or directory"
2016-10-06 20:47:32.498475429 +0000 UTC [ERROR] Could not find attached device, removing the volume error="Device not found" name=v1

Issue is different Linux OS versions support different ways of identifying the devices on the PCI bus (in the /sys/bus/ hierarchy). I'll have to check Photon OS and will need to add in alternatives if one approach doesn't apply.

Looked at the VM, scsi0:0 is itself a pvscsi controller. Why did the plugin server try adding a pvscsi controller at scsi1:0?  The vmx for P1 has pci slot number for scsi1:0 set to -1. And the Photon guest has no device except scsi0:0. Curiouser and curiouser.....

Be default Photon OS has LSILogic. I changed it to pvscsi to see if it helps but no luck.
BTW, I had used same OVA for VMworld demo and that worked.

Per issue 541 on Photon the below commands help fix the issue:
tdnf install linux
Upgrading:
linux                                                                         x86_64                       4.4.8-11.ph1                                                 44.60 M
Total installed size: 44.60 M
Is this ok [y/N]:y
Downloading:
linux                                 18821367    100%
Testing transaction
Running transaction
Complete!
Am able to run a container with a vmdk volume:
docker run --rm -it -w /data -v v12:/data busybox sh
Unable to find image 'busybox:latest' locally
latest: Pulling from library/busybox
56bec22e3559: Pull complete
Digest: sha256:29f5d56d12684887bdfa50dcd29fc31eea4aaf4ad3bec43daf19026a7ce69912
Status: Downloaded newer image for busybox:latest
/data #
And /proc/mounts shows this:
/dev/disk/by-path/pci-0000:0b:00.0-scsi-0:0:1:0 /mnt/vmdk/v12 ext4 rw,relatime,data=ordered 0 0
Closing with no changes as this is a Photon specific issue. Photon 1.0 is said to have fixed this issue.

https://github.com/vmware/photon/issues/541


Fix puller being improperly unset when pulling stops.

fixes #26310

About the PR

This pr fixes the bug with people being unable to move while in cuffs if they were previously pulled even if they were no longer being pulled.
Why / Balance

A security cadet should not be able to merge my legs with the ground by simply touching me while I'm in cuffs.
Technical details

When unpulled, the pullableComp has its puller field set to null after the message signifying the pulling has stopped has been sent. Since the component has a field to determine whether its owner is being pulled which is determined by the puller field, systems listening on the event would think that the owner of the component was still being pulled.
As a result, when the message was fired and the SharedCuffableSystem checked whether it should allow the cuffed person to move it thought they were still being pulled and as such didn't allow them to move.
I spent some time trying to determine whether setting the puller to null earlier would have other negative effects, however to my understanding of the code and the systems that listen to the message I believe this is now the correct behavior. Still just in case @metalgearsloth please check this out thanks.
Media

[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog

:cl:

fix: You can now move again if you stop being pulled while in cuffs.

 Please just assume that the commit title is actually the pr title because I am not force pushing to fix it.

Gonna wait for sloth's approval on this, but it looks good to me.


CRI update for sandbox sizing

Background
Today in Kubernetes, sandbox level sizing information is not available through CRI. With 1.23 (see https://github.com/kubernetes/kubernetes/pull/104886), the CRI API is updated to include an optional field in the LinuxPodSandboxConfig field which is part of the RunPodSandbox request. sandbox create request, as seen here: https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/cri-api/pkg/apis/runtime/v1alpha2/api.proto#L334-L335
Having sandbox level resource details at sandbox creation time will have large benefits for sandboxed runtimes. In the case of Kata Containers, for example, this'll allow us to better support SW/HW architectures which don't allow for resource hot plug (memory/CPU), and it'll allow for better queue sizing for virtio devices associated with the sandbox VM.
RFC:
Now that containerd will have access to this information, I am seeking to make this information available for the underlying "OCI runtime." In the case of shim-v2 task API, I'm looking to get this information passed when creating a sandbox, https://github.com/containerd/containerd/blob/45c5298700a81b4b50b73b2125d6f082998bfec7/pkg/cri/server/sandbox_run.go#L59
With sandbox API, this will be a natural fit. From looking at this for task API, we can include this information when making a CreateTaskRequest for a sandbox container. I see a couple of options:
Option 1: include sizing information in the pause containers OCI spec:
Setting up creation of a container (task) using pause container, containerd leaves minimal constraints (just applies minimum CPU shares) in place for the OCI spec.  Since the runtime could know that it is a sandbox create request, if an enlightened runtime is in place, containerd could place the sandbox resources directly into the pause container's spec (for example, have a config option per-runtime on whether we expect to consume sandbox information from the pause container's spec).  The runtime would just use this information for sandbox sizing, and would be required to constrain the in-guest pause container appropriately. The benefit of this approach is that the small changes are contained within the CRI portion of containerd code base, not modifying task request behavior.
Option 2 Include this sizing information as part of  CreateTaskRqeuest options "blob":
We could Marshall this information as part of the options field within CreateTaskRequest for sandbox create requests (ie: https://github.com/containerd/containerd/blob/0d0fb6858971e5dd92cb044a744979ccb1e9635a/api/services/tasks/v1/tasks.pb.go#L53). Task options is used minimally today to set a couple of flags. The existing handling would need refactoring to include details from the CRI request (the linux config resources) in order to properly create the resulting 'blob'. While this wouldn't require a config option, I wasn't confident how viable this refactoring would be, and if the Options field is intended for this kind of usage (as opposed to just runtime flags).

Rebased now that the CRI API changes have been merged. Should be ready for feedback/review.

Seeing failed test on windows side -- will address!
=== FAIL: pkg/cri/server TestSandboxContainerSpec (0.00s)
203
    sandbox_run_test.go:159: TestCase "should return error when entrypoint and cmd are empty"
204
    sandbox_run_test.go:159: TestCase "a passthrough annotation should be passed as an OCI annotation"
205
    sandbox_run_windows_test.go:68: Check username
206
    sandbox_run_windows_test.go:71: Check credential spec
207
    sandbox_run_windows_test.go:74: Check PodSandbox annotations
    ```

Addressed failing tests, which were due to me testing linux specific resources within sandbox_run_test. After moving these to sandbox_run_linux_test, it looks good on my end.

@mikebrow et al --
I pushed an update based on our discussion. Instead of pushing the sandbox resource details into the LinuxResources part of the spec, I introduce new annotation keys for the spec, and pass the applicable fields as part of the annotations within the spec.


[help] How to print text in between [ and ]

When I try to print any text in between [ and ]` it is not printed.
For example, print("[in]") prints an empty line. How could I prevent this from happening?

I have observed that we don't require any escape function or \ if the variable inside {} is an integer.
attempt = 1
log(f"[{attempt}] hello")
log(f"\[{attempt}] hello")

prints:
[1] hello
/[1] hello

Is it a normal case?


Parse JSON Error

I used .responseJSON
        ApiManagement.manager.request(router.getHashCourse).responseJSON {
            response in
            debugPrint(response)
        }

but it return:
FAILURE: Error Domain=NSCocoaErrorDomain Code=3840 "Unable to convert data to string around character 8342." UserInfo={NSDebugDescription=Unable to convert data to string around character 8342.}
But when i use .responseString then I convert the responseString to JSON, it success.
        ApiManagement.manager.request(router.getHashCourse).responseString { response in
            if let data = response.result.value?.dataUsingEncoding(NSUTF8StringEncoding) {
                do {
                    let json = try NSJSONSerialization.JSONObjectWithData(data, options: .AllowFragments) as? [String:AnyObject]
                    print(json)
                } catch {
                    print(error)
                }
            }
        }

Anyone can help me to use .responseJSON, thank so much

Hi @thaoth58,
It appears that NSJSONSerialization is failing to parse your response into JSON. That's why I would debug on your end. In the future, I'd encourage you to ask these types of questions on Stack Overflow. We use our GitHub project for bug reports and feature requests.
Best of luck! 🍻

From our Contribution Guidelines
Asking Questions
We don't use GitHub as a support forum. For any usage questions that are not specific to the project itself, please ask on Stack Overflow instead. By doing so, you'll be more likely to quickly solve your problem, and you'll allow anyone else with the same question to find the answer. This also allows maintainers to focus on improving the project for others.

Thank for your response 👍
But i wonder can we have a function to set the Encoding of the data ? :D

There's no need to set an encoding value because you don't need to convert to a String before using NSJSONSerialization. The NSURLSession already hands you back a complete NSData object from the server which can then be handed directly to NSJSONSerialization. There's no need to transform the NSData into a String before NSJSONSerialization gets it.

Maybe i know the issue :D
My JSON response a string that contains Unicode Character: "\u0110\u0103ng kí thành công vui lòng vào mail \u0111\u1ec3 xác nh\u1eadn."  so that it can't be decoded
So can you help me with this :( Thank so much

Oh, sorry, I know. My server uses charset=ISO-8859-1 :((


CLI enable local http handlers from extensions

CLIR should set this envir var:
WEBSITE_HOSTNAME  = localhost:7071
Where 7071 is the port.
This will enable extensions local http handling, which is used by DTF's 202 hook.
This will mitigate  https://github.com/Azure/azure-webjobs-sdk-script/issues/1658

@ahmelsayed I've added to the next milestone since it should be an easy fix.

I have an issue with Function Proxies running locally through the CLI. I use WEBSITE_HOSTNAME to build the backendUri in proxies.json to avoid having to transform the file across environments. On local, this returns <IP_ADDRESS>:71 and the redirect to the function fails as a result.
It does not appear to be possible to override the value using local.settings.json (duplicate key error) and we don't want to add a custom variable because it creates a management overhead.
Is there a more appropriate variable or approach to use?
If appropriate, I can raise a bug for this. I am posting here first as I can see that there has been some discussion around the variable. Thank you.


[feature] add redimnet

Add ReDimNet as mentioned in https://github.com/wenet-e2e/wespeaker/issues/341

I have actually validated the performance of B2 and B3, the performance are acceptable, but it's hard to validate other bigger models due to the resource limitation ...

Hi,  I was running redimnetb2 with 8x4090 on cnceleb, using your model and config (06025169e6a32cb59e7c9bcdcd74ee4ba321aa93), but my results seem not so good, the results are:

The final acc and final loss are comparable,

and the difference of two exp's config is listed as below:

Is this reasonable? Thanks for your reply。

Unfortunately, I am currently too busy to tune the experiments. I will present the results I have so far below. I believe we can first merge the implementations, as the performance is acceptable given the model's size. I would greatly appreciate any assistance from someone with sufficient resources to help with this implementation.
Main Problems:
The default SphereFace2 loss does not work well for me (it yields worse results than the arc_margin-based approaches).
While large margin fine-tuning is beneficial, its impact is limited.

Redimnet v0 arc_margin
No score norm

AS-Norm

EER
minDCF
EER
minDCF

vox1_O
1.244
1.181
1.128
0.109

vox1_E
1.248
2.008
1.181
0.125

vox1_H
2.172
0.210
2.008
0.186

Redimnet v2 arc_margin
No score norm

AS-Norm

EER
minDCF
EER
minDCF

vox1_O
0.712
0.059
0.718
0.072

vox1_E
0.894
0.095
0.869
0.094

vox1_H
1.621
0.161
1.545
0.149

Redimnet v3 arc_margin
No score norm

AS-Norm

EER
minDCF
EER
minDCF

vox1_O
0.574
0.045
0.537
0.045

vox1_E
0.822
0.095
0.790
0.089

vox1_H
1.576
0.157
1.433
0.140

@wsstriving Hello! Recently, I have been working on reproducing the models from your code and the updated code from the subsequent work of the paper's authors. If the training goes smoothly, I will provide the necessary assistance. My question is: are the results from your code before or after LMF?


finding wallet address

Hi I have installed terracoin via git clone, and have run and updated blocks, my query now is where do I locate the wallet address for my config files?

Sorry this is to report problems with the code, please find help in our Mattermost channel or on our wiki for usage type issues.


Unable to run on CentOS

$ cat /etc/issue
CentOS release 6.7 (Final)
Kernel \r on an \m
$ uname -a
Linux <snip> 2.6.32-573.12.1.el6.x86_64 #1 SMP Tue Dec 15 06:42:08 PST 2015 x86_64 x86_64 x86_64 GNU/Linux
$ bin/docker-machine-driver-kvm
bin/docker-machine-driver-kvm: /usr/lib64/libvirt.so.0: version `LIBVIRT_1.1.1' not found (required by bin/docker-machine-driver-kvm)
bin/docker-machine-driver-kvm: /usr/lib64/libvirt.so.0: version `LIBVIRT_1.0.2' not found (required by bin/docker-machine-driver-kvm)
$ libvirtd --version
libvirtd (libvirt) 0.10.2

Any other info I need to provide in order to isolate issue?
For sure, I know that true way to use this driver is to issue following command, but it doesn't work either:
$ docker-machine create -d kvm myengine0
Error loading driver "kvm": dial tcp: missing address

It looks like the centos 6.x version is too old.  Not sure if RH has been backporting things for it upstream, but the mainline 0.10 release looks to be ~4 years old according to the libvirt.org page.
Not sure what the best course of action is.  Looking at Centos 7, I see it has 1.2.17 libvirt, which is more likely to work (I don't have a physical centos box to test/confirm)  If you're stuck on 6.x, you might consider downloading the source from http://libvirt.org/downloads.html to update it.

Thanks for a quick response! Yup, we're stuck with Centos 6.x :-(
I will test with a newer libvirt and let you know

I have the same issue as a normal user in centos 7:
docker-machine create -d kvm dockerhans1
dial tcp: missing address
When I login as root it works fine and the machine is created
Any ideas ?

@jhmnieuwenhuis you probably haven't wired up group membership to allow your user account access to the libvirt socket.  It depends on the distro, but I think most packaing sets it up as root only, but you can add members to a group (something like "libvirt" to allow access.  Here's an example from my Ubuntu based system:
% ls -l /var/run/libvirt/libvirt-sock
srwxrwx--- 1 root libvirtd 0 Feb 29 17:24 /var/run/libvirt/libvirt-sock=
% groups
daniel adm cdrom sudo dip plugdev lpadmin sambashare docker libvirtd

spot on !!
That solved the issue.
B.t.w. Excellent job on the kvm plugin !!
Regards,
Hans Nieuwenhuis

One other question.
When i create "normal" vm's on centos7 using virt-install i use lvm thin volumes.
I suppose that's not possible when using docker-machine -d kvm ??
Regards,
Hans

That's not currently possible, but could be added.
If you wanted to take a crack at it and submit a PR, I think most of the logic would live within https://github.com/dhiltgen/docker-machine-kvm/blob/master/kvm.go#L654-L670 and perhaps a new command line flag to toggle the behavior.

Well that's not something I am able to do.
My knowledge does not go that far.
I consider myself a student although I am 60 years old and live in the Netherlands.
Due to a serious accident I had to retire from work last year.
I have always been a (project)manager in IT with an interest in programming and document management.
These days I do voluntary work with elderly people, I love to tour on my bike and
to keep my brain in shape I study.
( php, postgresql, symfony, drupal, centos7, kvm and since a week also docker)
My plan is to create a drupal site with all kinds of information on above subjects and on bicycling.
But thanks for the quick responses on my questions.
If I can help by testing something, let me know.
Regards,
Hans

Hi, two more observations

when I run docker-machine upgrade on a kvm machine as a non-root user
it will not work.
error :
chmod /home/hn/.docker/machine/machines/docker1/boot2docker.iso:  operation not  permitted
this file is owned by qemu:qemu

when I use "--kvm-network default"  when creating the kvm machine, there wil be
2 network interfaces created one for source-network default and one for source-network
docker-machines
when i use "--kvm-network docker-machines" there are also two network interfaces created
but they are  both for source-network docker-machines
There where already kvm vm's created on my host before I used docker on it.
They where created using virt-install and using source-network default.

Regards,
Hans

#1 is probably a genuine bug.  I don't usually use upgrade in my workflow, so it may have regressed since I originally wrote the driver.
For #2, the driver could be enhanced to detect this case, but it shouldn't cause any major problems to have two interfaces on the same network.


ComboBox incorrect behavior when using Items property

Using this simple sample, the list is modified at each selection:
<ComboBox>
	<ComboBoxItem>Value 1</ComboBoxItem>
	<ComboBoxItem>Value 2</ComboBoxItem>
	<ComboBoxItem>Value 3</ComboBoxItem>
</ComboBox>

Observed with Uno.UI 1.31.0-dev.94.

in android,the last selected item dispeared! in ios,no item show!

Here the items are of type ComboBoxItem, which is a view.
Since views can only have one parent, when ComboBox.UpdateContentPresenter() sets its _contentPresenter.Content to the SelectedItem, the parent of the item becomes that ContentPresenter, which explains why it's not in the dropdown list anymore.
One option would be to implement in Uno the specifics of CarouselPanel that make the dropdown expand around the selected item (if we want the same behavior as UWP).
If you simply want to display strings in your ComboBox I suggest that you use the ItemsSource attribute instead of creating ComboBoxItems manually.

In android,i can define a ItemTemplate of ComboBox,then the behaviour of ComboBox is well.
In IOS, it's not work still! I define a List as the ItemsSource value,it's still show nothing.
@jeromelaban ,do you know How to deal with it? Thank you!

If you need to set the choices in xaml, you can use the primitives literals as a temporary workaround:
<ComboBox>
    <x:String>Red</x:String>
    <x:String>Green</x:String>
    <x:String>Blue</x:String>
</ComboBox>

Using a list for ItemsSource should work on both on ios & android. And, depending on what type of the list you get, you might need to set the DisplayMemberPath.


Response Content Type

“Response Content Type” has 4 values. Are we supporting all 4 response content types or just application/json? If not is there way of restricting swagger to only show what we support?

Swashbuckle will expose out the media types from each SupportedResponseBodyFormatters & SupportedResponseFormatters from the ApiDescription for each api in Swagger's produces & consumes section.
Is there something more specifically that isn't working?

Hi Merick,
Thank you for you valuable feedback. Based on XMLDocument the response content type will generated right? But I send a response like "application/Json" and "text/Json". Is there any option to hide remaining two ("application/xml" and "text/xml").

In my API I have both the "application/xml" and "text/xml" options so I decided to just hide the control since it really provides no value. You can do this pretty easily by first configuring via something like the following to inject your own custom CSS:
configuration.EnableSwaggerUi( c =>
{
c.InjectStylesheet( typeof( Startup ).Assembly, "Directory.Path.File.Name.css" );
}
Then, in the CSS, you can do something like the following:
.resource .content .response-content-type {
display:none;
}
Note that I think the CSS needs to be an embedded resource, and any changes you make to it while in development will require you to do a build to actually see those changes in the UI.

Again, Swashbuckler respects your WebAPI settings, try just configuring WebAPI to remove the formatters you don't want.
For example, in a little test website, I put this in my WebApiConfig
	public class WebApiConfig
	{
		public static void Register(HttpConfiguration config)
		{
			config.Formatters.Clear();
			config.Formatters.Add(new JsonMediaTypeFormatter());

			// etc etc etc
		}
	}

Thank you for you valuable feedback


SPEC-182: Make it clearer how ASes are supposed to create users

by linkifying the right text. (Also correctly linkify feature profiles!)

LGTM


add bot join server and bot leave server

add bot join server and bot leave server

Hi! Our team will be working on this shortly. Sorry for the delay!


Add Static Code Analyzers to Improve Code Quality

Summary
This PR integrates several static code analyzers into the project to enhance code quality and maintainability. The following analyzers have been added:

SonarAnalyzer.CSharp
Roslynator.Analyzers
AsyncFixer

Details:

SonarAnalyzer.CSharp (v<IP_ADDRESS>892): This analyzer provides a wide range of rules to detect bugs, code smells, and security vulnerabilities in C# code.
Roslynator.Analyzers (v4.3.0): A collection of 500+ analyzers, refactorings, and fixes for C# that help enforce best practices and optimize the codebase.
AsyncFixer (v1.6.0): Focuses on identifying and fixing common issues in asynchronous programming.

After adding analyzers I can see there are a lot of warnings and messages, by the time we can fix them
Please review the changes and provide feedback. This integration aims to foster a healthier codebase and streamline the development process

Thanks, It's very good.


src: fix some grammar

This fixes some grammar in relation to the CoC command.

@all-contributors please add @Rexogamer for translation


test: Add naive test cases for WebGLRenderer

Most of those test cases are pretty naive, but
1 the implementation of WebGLRenderer is probably going to change quite a bit
anyways
2 still better than no tests at all

:rage4: https://travis-ci.org/Famous/engine/jobs/71060554#L2826

I restarted the failed CI build: https://travis-ci.org/Famous/engine/jobs/71060554
GeometryHelp
I'm going to have a look at the GeometryHelper.normalizeVertices test to no longer use randomized values.

landed as 45c9b2c


Fixed issue on rendering checkbox status of tree node

Issue: Checkbox status is always rendered as -

Cause: checked and enabled field are missing when item created from tree data model for rendering.
Therefore, checked field always has unidentified value on rendering time.
(Missing enabled field did not cause issue since unidentified is considered as true for enabled field.)

Before fix:

After fix:

  const disposable = new DisposableStore();

This is overridden in https://github.com/microsoft/azuredatastudio/blob/c23738f9355b5e759b54102400c58af499eae678/src/sql/workbench/api/common/extHostModelViewTree.ts#L163 which adds in the enabled and checked properties - would that not be the appropriate place to do this? That method is pulling those properties from extensionTreeItem which is different than where you're getting it here so what caused the change and do we need to update that logic too in addition if this is still necessary for some reason?

Refers to: src/vs/workbench/api/common/extHostTreeViews.ts:458 in c357ef6. [](commit_id = c357ef6a901a37ce12d8d5eb46ec4d505540883a, deletion_comment = False)

It turned out the return value of exHostTreeView.createTreeNode() was changed 4 days ago, and it made exHostModelViewTree.createTreeNode() add those 2 field to wrong place.

I will update exHostModelViewTree.createTreeNode() to add up those 2 fields to correct place


ImportError: cannot import name 'CoILAgent'

miss init.py in dirve cause the problem.  add the file from coiltraine solve it.
pygame 1.9.4
Hello from the pygame community. https://www.pygame.org/contribute.html
Traceback (most recent call last):
File "multi_gpu_collection.py", line 10, in
from collect import collect
File "/home/wangchangquan/data_aggregation/collect.py", line 29, in
from coil_core import validate_single_model
File "/home/wangchangquan/data_aggregation/coil_core/init.py", line 2, in
from .executer import execute_train, execute_validation, execute_drive, folder_execute
File "/home/wangchangquan/data_aggregation/coil_core/executer.py", line 11, in
from . import train, validate, run_drive
File "/home/wangchangquan/data_aggregation/coil_core/run_drive.py", line 19, in
from drive import CoILAgent
ImportError: cannot import name 'CoILAgent'

Thanks for pointing it out. It is fixed now.


ECS ServicesStable Waiter fails if DescribeServices response does not include deployments

Describe the bug
waiter = ecs_client.get_waiter("services_stable")
waiter.wait(cluster=cluster, services=[service])

The ServicesStable waiter in Boto3 fails for some services with the following error message
"In function length(), invalid type for value: None, expected one of: ['string', 'array', 'object'], received: \"null\""

This appears to happen when the services[*].deployments element is absent from the DescribeServices response
Regression Issue

[ ] Select this option if this issue appears to be a regression.

Expected Behavior
The waiter should wait until the services are stable, and not throw an error
Current Behavior
"errorMessage": "In function length(), invalid type for value: None, expected one of: ['string', 'array', 'object'], received: \"null\"",
    "errorType": "JMESPathTypeError",
    "requestId": "94d7b720-8490-4577-9ce7-93b19726c814",
    "stackTrace": [
       REDACTED
        "  File \"/var/lang/lib/python3.11/site-packages/botocore/waiter.py\", line 55, in wait\n    Waiter.wait(self, **kwargs)\n",
        "  File \"/var/lang/lib/python3.11/site-packages/botocore/waiter.py\", line 348, in wait\n    if acceptor.matcher_func(response):\n",
        "  File \"/var/lang/lib/python3.11/site-packages/botocore/waiter.py\", line 229, in acceptor_matches\n    return expression.search(response) == expected\n",
        "  File \"/var/lang/lib/python3.11/site-packages/jmespath/parser.py\", line 509, in search\n    result = interpreter.visit(self.parsed, value)\n",
        "  File \"/var/lang/lib/python3.11/site-packages/jmespath/visitor.py\", line 94, in visit\n    return method(node, *args, **kwargs)\n",
        "  File \"/var/lang/lib/python3.11/site-packages/jmespath/visitor.py\", line 145, in visit_comparator\n    self.visit(node['children'][0], value),\n",
        "  File \"/var/lang/lib/python3.11/site-packages/jmespath/visitor.py\", line 94, in visit\n    return method(node, *args, **kwargs)\n",
        "  File \"/var/lang/lib/python3.11/site-packages/jmespath/visitor.py\", line 169, in visit_function_expression\n    current = self.visit(child, value)\n",
        "  File \"/var/lang/lib/python3.11/site-packages/jmespath/visitor.py\", line 94, in visit\n    return method(node, *args, **kwargs)\n",
        "  File \"/var/lang/lib/python3.11/site-packages/jmespath/visitor.py\", line 180, in visit_filter_projection\n    if self._is_true(self.visit(comparator_node, element)):\n",
        "  File \"/var/lang/lib/python3.11/site-packages/jmespath/visitor.py\", line 94, in visit\n    return method(node, *args, **kwargs)\n",
        "  File \"/var/lang/lib/python3.11/site-packages/jmespath/visitor.py\", line 259, in visit_not_expression\n    original_result = self.visit(node['children'][0], value)\n",
        "  File \"/var/lang/lib/python3.11/site-packages/jmespath/visitor.py\", line 94, in visit\n    return method(node, *args, **kwargs)\n",
        "  File \"/var/lang/lib/python3.11/site-packages/jmespath/visitor.py\", line 253, in visit_and_expression\n    matched = self.visit(node['children'][0], value)\n",
        "  File \"/var/lang/lib/python3.11/site-packages/jmespath/visitor.py\", line 94, in visit\n    return method(node, *args, **kwargs)\n",
        "  File \"/var/lang/lib/python3.11/site-packages/jmespath/visitor.py\", line 145, in visit_comparator\n    self.visit(node['children'][0], value),\n",
        "  File \"/var/lang/lib/python3.11/site-packages/jmespath/visitor.py\", line 94, in visit\n    return method(node, *args, **kwargs)\n",
        "  File \"/var/lang/lib/python3.11/site-packages/jmespath/visitor.py\", line 171, in visit_function_expression\n    return self._functions.call_function(node['value'], resolved_args)\n",
        "  File \"/var/lang/lib/python3.11/site-packages/jmespath/functions.py\", line 80, in call_function\n    self._validate_arguments(resolved_args, signature, function_name)\n",
        "  File \"/var/lang/lib/python3.11/site-packages/jmespath/functions.py\", line 91, in _validate_arguments\n    return self._type_check(args, signature, function_name)\n",
        "  File \"/var/lang/lib/python3.11/site-packages/jmespath/functions.py\", line 97, in _type_check\n    self._type_check_single(actual[i], allowed_types,\n",
        "  File \"/var/lang/lib/python3.11/site-packages/jmespath/functions.py\", line 111, in _type_check_single\n    raise exceptions.JMESPathTypeError(\n"
    ]

Reproduction Steps
I'm unsure what causes a service to not have the deployments element, the service is deployed using CodeDeploy's Blue/Green deployment
Possible Solution
No response
Additional Information/Context
I believe the line causing the issue is here but I'm unsure what it's trying to achieve by checking deployments
SDK version used
1.35.45
Environment details (OS name and version, etc.)
AWS Lambda, Python 3.11 Runtime

Thanks for reaching out. The line you linked in the waiter model hasn't changed for ~6 years, so I'm not sure if something changed on the with the DescribeServices API that would cause this to no longer work. But per the API documentation it looks like there's no guarantee that deployments would be in the response. \
Generally service teams own and maintain waiter models like this, but if there is an issue with the original implementation then this may be a bug to address here — and should also maybe be reviewed at a cross-SDK level. I'll mark this issue for further review.


Trying to use IoTHubDeviceClient.send_message with a Message throws an exception

Context

Ubuntu 21.10
Python 3.9.7
VirtualEnv is used, thus:

Package             Version
------------------- ---------
azure-iot-device    2.9.0
certifi             2021.10.8
charset-normalizer  2.0.10
deprecation         2.1.0
idna                3.3
janus               1.0.0
packaging           21.3
paho-mqtt           1.6.1
pip                 20.3.4
pkg-resources       0.0.0
pyparsing           3.0.7
PySocks             1.7.1
python-dotenv       0.19.2
requests            2.27.1
requests-unixsocket 0.3.0
setuptools          44.1.1
six                 1.16.0
typing-extensions   4.0.1
urllib3             1.26.8

Description of the issue
I use code mostly copied form the official documentation and try to use IoTHubDeviceClient.send_message with a Message. This throws an exception.
Code sample exhibiting the issue
        msg = azure.iot.device.Message(createDeviceToCloudStati())
        # sollte server-seitig gesetzt werden
        # msg.custom_properties["DeviceId"] = registration_id
        msg.content_encoding = "utf-8"
        msg.content_type = "application/json"
        msg.custom_properties["ver"] = "1"
        msg.custom_properties["type"] = "20"
        # API problem: can only be string? not Message? WTF?
        # https://github.com/Azure/azure-iot-sdk-python/blob/main/azure-iot-device/samples/async-hub-scenarios/send_message.py
        await global_device_client.send_message(msg)

"createDeviceToCloudStati" returns an Array populated with Collections, i.e., should be easily be serializable into JSON.
Console log of the issue
future: <Task finished name='Task-17' coro=<statusHeartbeat() done, defined at /home/andy/Projects/VirtualDevice/virtual_device.py:56> exception=ClientError('Unexpected failure')>
Traceback (most recent call last):
  File "/home/andy/Projects/VirtualDevice/env/lib/python3.9/site-packages/azure/iot/device/iothub/aio/async_clients.py", line 33, in handle_result
    return await callback.completion()
  File "/home/andy/Projects/VirtualDevice/env/lib/python3.9/site-packages/azure/iot/device/common/async_adapter.py", line 91, in completion
    return await self.future
  File "/home/andy/Projects/VirtualDevice/env/lib/python3.9/site-packages/azure/iot/device/common/pipeline/pipeline_stages_mqtt.py", line 271, in _run_op
    self.transport.publish(topic=op.topic, payload=op.payload, callback=on_complete)
  File "/home/andy/Projects/VirtualDevice/env/lib/python3.9/site-packages/azure/iot/device/common/mqtt_transport.py", line 549, in publish
    (rc, mid) = self._mqtt_client.publish(topic=topic, payload=payload, qos=qos)
  File "/home/andy/Projects/VirtualDevice/env/lib/python3.9/site-packages/paho/mqtt/client.py", line 1247, in publish
    raise TypeError(
TypeError: payload must be a string, bytearray, int, float or None.

@andreashappe
We don't currently serialize complex objects that are passed into Message. You must serialize your array of collections.

@cartertinney : ah.. yes, that fixed it, thank you. Small suggestion: could you throw the exception directly in the Message-constructor? That might make usage clearer, I was debugging the wrong area (if it's okay in principle, I can try to create a patch for that).

I can probably do something to that effect. I'll try and slip it into the next release.

perfect! thanks

(I have closed the issue, hopefully this is the correct workflow)


feat: add Home Assistant support using MQTT

@joscha82 this PR adds full support for Home Assistant using MQTT auto-discovery.
The updated README.md contains information about how it can be used, configured and tested.
Here are some screenshots:

Thank you @ahochsteger !
Since I read yesterday that there is a lot of work done even on the developer site of go-e https://github.com/goecharger/go-eCharger-API-v2/issues/67#issuecomment-1078916808 (@ahochsteger there is something with mqtt bevor, did you use this?) and the codebase beside the WS is the in the same direction to have wattpilot and GO-E API in HA. Would this be an idea to integrate wattpilot support into the already existing custom_integration https://github.com/cathiele/homeassistant-goecharger ?
So there is only one integration to have the (mostly) same API of two (mostly) same HW in one integration.
If we could achieve to get the WebSicket working in @cathiele integration, this would be a benefit for all. And we have one mature integration and less work for everyone.
What do you thinking about this approach? @ahochsteger @joscha82 @mk-maddin @cathile
Thank you!

@ahochsteger:
Looks really cool :)
How did you solve the attribute information of "namespace" values like e.g. WiFi Connection Information (property ccw) ?

Some Off Topic - but I think we have a lot of knowledge here together ;)
Is on all your wattpilot devices the default Hotspot (SSID: Wattpilot_ ) active all the time, too?
Did someone find a way (api / app / anything else) to disable the default hotspot/access poin?

Yes, always on! May https://github.com/peterpoetzi has an answer to this? @peterpoetzi ?

Some Off Topic - but I think we have a lot of knowledge here together ;) Is on all your wattpilot devices the default Hotspot (SSID: Wattpilot_ ) active all the time, too? Did someone find a way (api / app / anything else) to disable the default hotspot/access poin?

As far as i know thats not possibe, also i did  not see any property into that direction.
There is an open issue/feature request also on go-e APIv2 Repo here: https://github.com/goecharger/go-eCharger-API-v2/issues/35

Looks really cool :)
Thanks :)

How did you solve the attribute information of "namespace" values like e.g. WiFi Connection Information (property ccw) ?

This did the trick:
class JSONNamespaceEncoder(json.JSONEncoder):
    # See https://gist.github.com/jdthorpe/313cafc6bdaedfbc7d8c32fcef799fbf
    def default(self, obj):
        if isinstance(obj, SimpleNamespace):
            return obj.__dict__
        return super(JSONNamespaceEncoder, self).default(obj)

def utils_value2json(value):
    return json.dumps(value, cls=JSONNamespaceEncoder)

@thecem

Since I read yesterday that there is a lot of work done even on the developer site of go-e goecharger/go-eCharger-API-v2#67 (comment) (@ahochsteger there is something with mqtt bevor, did you use this?)

No I've created a WebSocket-to-MQTT bridge and used that to provide Home Assistant Discovery Configuration via MQTT.

and the codebase beside the WS is the in the same direction to have wattpilot and GO-E API in HA. Would this be an idea to integrate wattpilot support into the already existing custom_integration https://github.com/cathiele/homeassistant-goecharger ? So there is only one integration to have the (mostly) same API of two (mostly) same HW in one integration. If we could achieve to get the WebSicket working in @cathiele integration, this would be a benefit for all. And we have one mature integration and less work for everyone.
What do you thinking about this approach?

Yes, I agree that it would be good to join forces and avoid duplicate work.
I see different approaches here:

Enable direct WebSocket support in homeassistant-goecharger (as you suggested)
Adjust the Websocket-to-MQTT bridge to provide an (almost) go-eCharger compatible MQTT API so homeassistant-goecharger could be easily adopted
Use the MQTT bridge provided by this PR that also provides additional features in a generic way (e.g. translates integer enums to human-readable names and decompose array/object properties into their own properties (e.g. the total power entry of the nrg array is exposed as a separate property nrg_ptotal)
Add Wattpilot support to the fronius integration (either the official Fronius integration or safepay.fronius using HACS)
Use https://github.com/mk-maddin/wattpilot-HA as the native Wattpilot integration for Home Assistant

They all have their pros and cons and may be better for different use cases, e.g.:

The 1st approach targets Home Assistant users and provides an easy way to integrate without the need of extra components (e.g. MQTT server, websocket-to-mqtt bridge).
The 2nd approach may reduce implementation effort, but at the cost of complexity on the user side (requires two additional components: MQTT server + MQTT bridge).
The 3rd approach targets users of different smart home solutions which all are able to integrate MQTT. Translating the values and splitting up complex properties makes it ease to integrate.
The 4th approach makes it easier for users of the fronius ecosystem to get a better out-of-the-box experience.
The 5th approach allows focussed and fast development of a Wattpilot integration for HA without having to take care of other implementations (e.g. go-eCharger or Fronius) at the cost of possible duplicate effort.

I think a good start would be to put the API metadata into the coreof the Wattpilot library (see wattpilot.yaml or API.md - both part of this PR). This would allow to replace the hard-coded parsing of properties with the generic, metadata-driven approach. We can enrich the metadata with additional information and use that to drive all relevant approaches in a generic way (as the MQTT bridge already does).
This way both Wattpilot as well as GO eCharger would be easier to maintain in the future - esp. if firmware updates may introduce new properties.
@joscha82, @thecem, @mk-maddin, @cathiele what do you think?

Absolutely right, I think the most unique and best adoption ist the approach with Wattpilot.yaml and API.md. In may there will be new features for Wattpilot, so we are able to adopt all changes with ease.

@joscha82 it would be great if you could merge this PR since it already contains so much working stuff so others could benefit from it as well :-).
Maybe we can talk about possible future refactorings to bring some functionality I've implemented for the shell and move it to the core library. Esp. the API metadata stuff (using wattpilot.yaml) would be good to have there and I see some ways to greatly simplify the code if it is based on the API metadata instead of hard-coded parsing of properties.

I see different approaches here:

Enable direct WebSocket support in homeassistant-goecharger (as you suggested)
Adjust the Websocket-to-MQTT bridge to provide an (almost) go-eCharger compatible MQTT API so homeassistant-goecharger could be easily adopted
Use the MQTT bridge provided by this PR that also provides additional features in a generic way (e.g. translates integer enums to human-readable names and decompose array/object properties into their own properties (e.g. the total power entry of the nrg array is exposed as a separate property nrg_ptotal)
Add Wattpilot support to the fronius integration (either the official Fronius integration or safepay.fronius using HACS)
Use https://github.com/mk-maddin/wattpilot-HA as the native Wattpilot integration for Home Assistant

They all have their pros and cons and may be better for different use cases, e.g.:

The 1st approach targets Home Assistant users and provides an easy way to integrate without the need of extra components (e.g. MQTT server, websocket-to-mqtt bridge).
The 2nd approach may reduce implementation effort, but at the cost of complexity on the user side (requires two additional components: MQTT server + MQTT bridge).
The 3rd approach targets users of different smart home solutions which all are able to integrate MQTT. Translating the values and splitting up complex properties makes it ease to integrate.
The 4th approach makes it easier for users of the fronius ecosystem to get a better out-of-the-box experience.
The 5th approach allows focussed and independent development of a Wattpilot integration for HA without having to take care of other implementations (e.g. go-eCharger or Fronius) at the cost of possible duplicate effort.

I think a good start would be to put the API metadata into the core of the Wattpilot library (see wattpilot.yaml or API.md - both part of this PR). This would allow to replace the hard-coded parsing of properties with the generic, metadata-driven approach. We can enrich the metadata with additional information and use that to drive all relevant approaches in a generic way (as the MQTT bridge already does). This way both Wattpilot as well as GO eCharger would be easier to maintain in the future - esp. if firmware updates may introduce new properties. @joscha82, @thecem, @mk-maddin, @cathiele, @safepay, what do you think?

I would prefer your mqtt bridge instead  of building a API-compatible eGo Bridge, as your bridge is better suited for most Home Automation Systems (which i assume is the main use-case).
Integration in the existing Fronius Inverter Integration is the wrong direction in my opinion. It is the fronius ecosystem and if Fronius wants to have the wallbox highly integrated, its on their end to adopt/implement their solar API on the wallbox itself.
I also like the native HA Integration but given that mqtt is independent and a good choice for other home automation integrations i  would prefer that direction (also given that HA has nice mqtt autodiscovery-features). But both solutions can live nicely side by side and @mk-maddin integration is a good solution for HA Users who integrate natively without additional (external) dependencies.

@joscha82 it would be great if you could merge this PR since it already contains so much working stuff so others could benefit from it as well :-).
Maybe we can talk about possible future refactorings to bring some functionality I've implemented for the shell and move it to the core library. Esp. the API metadata stuff (using wattpilot.yaml) would be good to have there and I see some ways to greatly simplify the code if it is based on the API metadata instead of hard-coded parsing of properties.

I believe your idea to integrate API Metadata into the core library makes absolutely sense, and makes the included information usable by all consumers of the libary and not only for wattpilotshell.
Also I think it makes sense to divide wattpilotshell into two components: a) the shell (interactive and cmdline) and b) wattpilot2mqtt bridge.
I just found the time to test your pull request and will merge it now. I will also remove the now obsolete dependency on pyreadline and bump version requirement to python >3.10.

Also I think it makes sense to divide wattpilotshell into two components: a) the shell (interactive and cmdline) and b) wattpilot2mqtt bridge.

@joscha82 yes I agree - this makes absolutely sense.


Mixxx misses libmp4 for AAC or MP4 support

Issue description
While building mixxx with the sconsFlag faad=1 ist fails with the massage:

ERROR:root:Unmet dependency: Could not find libmp4, libmp4v2 or the libmp4v2 development headers.

Steps to reproduce
In https://mixxx.org/wiki/doku.php/compiling_on_linux are the libraries faad2 and libmp4 mentioned as requirements. I can install faad2 but didn't find a libmp4 variant. Installing mp4v2 did not solve it.
in my configuration.nix I added:
{ config, pkgs, ... }:
{
  nixpkgs.config = {
    allowUnfree = true;
    packageOverrides = pkgs: ({
      mixxx = pkgs.lib.overrideDerivation pkgs.mixxx (attrs: {
        sconsFlags = [
          "build=release"
          "qtdir=${pkgs.qt4}"
          "faad=1"
        ];
      });
    });
  };
}

Technical details

System: NixOS 17.03.1825.df7e518568 (Gorilla)
Nix version: nix-env (Nix) 1.11.14
Nixpkgs version: 17.03.1825.df7e518568
Sandboxing enabled: true

If building with "faad=1", then you need to provide faad2 and mp4v2 as buildInputs. The package override you provided above would not be sufficient.  What I did was to save the default.nix for mixxx and modify it to directly invoke mkDerivation with the modified sconsFlags and buildInputs, see the following blog post for an example of how to do this: http://sandervanderburg.blogspot.co.uk/2014/07/managing-private-nix-packages-outside.html
The package needs to be modified to take an optional parameter to switch on/off this flag and corresponding dependencies. If I get time, I will assemble a pull request.

@willtim May you provide me your receipt for faad2, mp4v2 and mixxx?

@tasmo, I'm not sure what you mean by receipt? I can put together a pull request for mixxx and some better instructions for building it?


Get redux state before renderToString with current version of loadable-components

Hi,
since getLoadableState was dropped in current version, how to receive redux state before renderToString?
thanks.

Hello @ogheo, in fact it is not the goal of this library. I think you are looking for something like https://github.com/FormidableLabs/react-ssr-prepass


install_dependencies.sh fails if uvcdynctrl not installed

Hello there,
the install_dependencies.sh from http://docs.luxonis.com/_static/install_dependencies.sh fails on line 127 UVC_DYN_INSTALLED=$(dpkg-query -W --showformat='${Status}\n' uvcdynctrl|grep "install ok installed") if uvcdynctrl is not installed on the system.
UVC_DYN_INSTALLED=$(dpkg-query -W --showformat='${Status}\n' uvcdynctrl|grep "install ok installed") returns 1 if it is not installed and with set -e in line 3 the code exists here.

it's an assignment to variable. it shouldn't exit for that. Are you using bash shell ? and can I know the system specs ?

I am getting the same issue on an RPI4B 4GB.If I install uvcdynctrl then I get this error:
CMake Error at cmake/XLink.cmake:26 (message):
  libusb is required
Call Stack (most recent call first):
  CMakeLists.txt:8 (include)

-- Configuring incomplete, errors occurred!
See also "/root/.hunter/_Base/9b4e732/f61e57a/90457df/Build/XLink/Build/XLink-Release-prefix/src/XLink-Release-build/CMakeFiles/CMakeOutput.log".
See also "/root/.hunter/_Base/9b4e732/f61e57a/90457df/Build/XLink/Build/XLink-Release-prefix/src/XLink-Release-build/CMakeFiles/CMakeError.log".
make[2]: *** [CMakeFiles/XLink-Release.dir/build.make:111: XLink-Release-prefix/src/XLink-Release-stamp/XLink-Release-configure] Error 1
make[1]: *** [CMakeFiles/Makefile2:76: CMakeFiles/XLink-Release.dir/all] Error 2
make: *** [Makefile:84: all] Error 2

[hunter ** FATAL ERROR **] Build step failed (dir: /root/.hunter/_Base/9b4e732/f61e57a/90457df/Build/XLink
[hunter ** FATAL ERROR **] [Directory:/tmp/depthai-core/cmake]

------------------------------ ERROR -----------------------------
    https://hunter.readthedocs.io/en/latest/reference/errors/error.external.build.failed.html
------------------------------------------------------------------

CMake Error at /root/.hunter/_Base/Download/Hunter/0.23.320/9b4e732/Unpacked/cmake/modules/hunter_error_page.cmake:12 (message):
Call Stack (most recent call first):
  /root/.hunter/_Base/Download/Hunter/0.23.320/9b4e732/Unpacked/cmake/modules/hunter_fatal_error.cmake:20 (hunter_error_page)
  /root/.hunter/_Base/Download/Hunter/0.23.320/9b4e732/Unpacked/cmake/modules/hunter_download.cmake:623 (hunter_fatal_error)
  /root/.hunter/_Base/Download/Hunter/0.23.320/9b4e732/Unpacked/cmake/modules/hunter_add_package.cmake:53 (hunter_download)
  cmake/depthaiDependencies.cmake:9 (hunter_add_package)
  CMakeLists.txt:134 (include)

-- Configuring incomplete, errors occurred!
See also "/tmp/depthai-core/build/CMakeFiles/CMakeOutput.log".

@themarpe  any idea on this ?

@roni-kreinin regarding your issue - can you install libusb dev library using: sudo apt install libusb-1.0-0-dev
Does that resolve the issue for you?
@saching13 can you try reproducing the OP issue? If it shows up, would be a blocker in those cases.

@themarpe Yes this fixes the issue. I do still get the warning that I shouldn't have uvcdynctrl installed however.

@roni-kreinin great
We are fixing the install_dependencies.sh script, which should address the rest of this issue:)

ou try reproducing the

Yes I aam using bash shell.
OS: Ubuntu 20.04

@NovoG93 the script should be updated now (https://github.com/luxonis/depthai-python/pull/483)
Let us know if it works for you

Closing due to inactivity, if you think this should remain open, please tag me in a comment here.


chore: Add missing SF env vars to Server/config.ts

The type of this PR is: Chore

Description

During https://github.com/artsy/force/pull/12303, 3 news environment variables were added to Salesforce Wrapper, but these variables were not added to Server/config.ts
See this thread for details
cc @artsy/negotiate-devs

Thank you! On V2, we added it on this PR.


Fix Wasm E2E Tests

Description
Marking as R4R to trigger E2Es.
This PR fixes the E2E wasm tests (with the exclusion of the MsgTransfer tests which fail due to ics20-v2)
The Setup logic is moved into SetupSuite and SetupTest, and the ConfigureRelayer fn is finally removed :partying_face:
I added some additional log lines as debugging the hyperspace relayer was quite difficult due to it hanging rather than erroring.

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[ ] Targeted PR against the correct branch (see CONTRIBUTING.md).
[ ] Linked to GitHub issue with discussion and accepted design, OR link to spec that describes this work.
[ ] Code follows the module structure standards and Go style guide.
[ ] Wrote unit and integration tests.
[ ] Updated relevant documentation (docs/).
[ ] Added relevant godoc comments.
[ ] Provide a conventional commit message to follow the repository standards.
[ ] Include a descriptive changelog entry when appropriate. This may be left to the discretion of the PR reviewers. (e.g. chores should be omitted from changelog)
[ ] Re-reviewed Files changed in the GitHub PR explorer.
[ ] Review SonarCloud Report in the comment section below once CI passes.

Been looking at failing wasm e2es with @chatton. It looks to be the merkle path being encoded as base 64 bytes when the SudoMsg is passed to wasm.

Been looking at failing wasm e2es with @chatton. It looks to be the merkle path being encoded as base 64 bytes when the SudoMsg is passed to wasm. This is due to #6633 and #6644 PRs

when running tests locally with older images these tests pass. We'll need to decide how to proceed with this breaking change

oh, this is a contract api breaking change 👀

An attempt was made. https://github.com/cosmos/ibc-go/pull/6644/commits/733539ca62d6cff51d96356bcd098e45e65db2f4

Can we merge this so I can run tests on https://github.com/cosmos/ibc-go/pull/6644? or is there anything else left to do?

@damiannolan think we can merge  when ready, and can look into any failures after your PR gets merged after the fact


Better NPC Highlight: Defaults to slayer highlight color, even if slayer highlighting is disabled

Hey, after the most recent update, it seems that now if an NPC is tagged, and you happen to have a task for it, regardless of the color of the tag you've specifically set for them, it will use the color of the Slayer highlighting, even if you have Slayer highlighting disabled.
Example here: Tagged greater nechs as orange area, and its using the slayer highlight as the color.

Let me know if there's anything else I can provide for this issue.

Should be fixed in latest update


group and subgroup in ToastVisual

Is there plan to add group and subgroup to support adaptive toast template?

Yep, we'll be adding it soon. We still haven't finalized and published the toast schema yet, hence why we haven't updated Extensions.

Group and subgroup has been added to toast notifications with commit 1f1168a25bca70e1d3dfeb4392c79d0f419f1373! More info here: https://blogs.msdn.microsoft.com/tiles_and_toasts/2016/05/23/notificationsextensions-updated-for-anniversary-update-of-windows-10/


fontconfig conflicting definitions when using nixos module

When using fonts.fontconfig.enable = true; to let home manager handle fontconfig configuration, I get the following error:
error: The option `home-manager.users.jerry.fonts.fontconfig.enable' has conflicting definitions, in `/etc/nixos/home/home.nix' and `/nix/store/x82h5sl2gp3y48lj62pnh4ga1ln5bdx3-source/nixos'.
(use '--show-trace' to show detailed location information)

I am using the nixos module to import my home-manager configuration in my configuration.nix, I assume this error is there because nixos has its own fonts.fontconfig.enable setting which has a different definition.
Is it possible to define my fonts in home.packages and let them still be discovered in my system? Manually running fc-cache -f is an option, but this resulted in some packages still not finding my fonts. Maybe fonts.fontconfig can be renamed in home-manager?
For completeness, here is my nixos configuration (home/home.nix is where I want to add the fontconfig setting)

Actually, it is not a conflict with the NixOS fonts.fontconfig.enable option but rather a conflict with the assignment set in the HM NixOS module:
https://github.com/rycee/home-manager/blob/5969551a5cc52f9470b5ff5ca01327bf4bda82c1/nixos/default.nix#L25-L28
The value in the NixOS module should probably be set using mkDefault but for now you can add fonts.fontconfig.enable = lib.mkForce true as a work-around.

Actually, it is not a conflict with the NixOS fonts.fontconfig.enable option but rather a conflict with the assignment set in the HM NixOS module:
https://github.com/rycee/home-manager/blob/5969551a5cc52f9470b5ff5ca01327bf4bda82c1/nixos/default.nix#L25-L28
The value in the NixOS module should probably be set using mkDefault but for now you can add fonts.fontconfig.enable = lib.mkForce true as a work-around.

Thanks for the quick reply!
Using lib.mkForce true works for me. I will leave this issue open in the case you want to make a change in the nixos module. You may also close this issue.


Save current deployment tag for every environment

Store tag of the current deployment in each environment at then end of the deployment pipeline.
This tag is used by the server-sql compatibility test.

This change is

Reviewable status: 1 of 2 files reviewed, 1 unresolved discussion (waiting on @jianglai)

release/cloudbuild-deploy.yaml, line 60 at r1 (raw file):
Previously, jianglai (Lai Jiang) wrote…
Made this a separate step.
The other file only makes up for the lack of symbolic link, and tells us the version of whatever in the live folder.
We can find out this info by looking into the content of the archives, but this file makes it simpler.
The files created here are per-environment and server as the authoritative records of what is currently deployed, which may be different the 'live' release during some of the deployment stages, or after stalled pushes or rollbacks.

My point is that with the nomulus.${ENV}.tag file, you already know what tag production uses, so saving the other file is redundant. But that's only one file, so I don't think it's a big deal.


Java: Support for osx-aarch_64 architecture

Update the build system to generate artifacts for MacOS on ARM64
to support Apple Silicon / M1 machines.

Can someone please review this? @mattklein123

Can you fix DCO please? Also, CI is failing so that will need to be fixed. I can rubber stamp this when fixed but I would prefer if @rmichela could actually take a look. Thank you.

Can you fix DCO please?
Done.

Also, CI is failing so that will need to be fixed

I can rubber stamp this when fixed but I would prefer if @rmichela could actually take a look. Thank you.
👍

Can you fix DCO please?

Done!

Also, CI is failing so that will need to be fixed.

Fixed! (by updating go version in the circle ci config file)

I can rubber stamp this when fixed but I would prefer if @rmichela could actually take a look. Thank you.

👍  thanks! would be great if someone could confirm that the new artifact will be automatically uploaded to maven central with the next release, or if any other configuration changes are needed.

Sorry for the delay. LGTM 🎉

Hey and thanks for this fix.
However, I can't find this on maven: https://repo.maven.apache.org/maven2/io/envoyproxy/protoc-gen-validate/pgv-java-stub/. How could I add it as a dependency in pom.xml?

I'm planning to release to Maven today.

@rmichela rmi
2 days have passed, can you tell me when it will be released? I'm running a project that needs this support version for M1 chip

While waiting from new release version, i change JDK version (gradle version too) in my IDE (intelIJ) which doesn't support aarch_64, it works for me now. That why dependency doesn't add osx-aarch_64 to the end of file.

.


KMP Algorithm for Pattern Searching

Is your feature request related to a problem? Please describe.
KMP Algorithm
Describe the solution you'd like
Implementation using C++
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
Programming language

[ ] C
[ ] C++
[ ] Java
[ ] Python

@Amit366 @Ayush7614, Kindly assign me this issue under LGMSOC

Can I implement in Java? I'm a participant of LGM Soc21.

Can I Implement this Algorithm in python Under LGM"SOC"21


Add the EU/European union flag emoji

In partial fulfillment of the #119 issue.

Coverage increased (+0.3%) to 93.498% when pulling 15bf60c80feff7bb26a864994f6fbd388070efa3 on ankitkariryaa:master into 8cf5fbe0d7c1020b926791f2b342a263ed07bb0f on vdurmont:master.


Question: Composability

Hello!
I building a graph composability structure where the nodes are combined as a list index and each node is a vector store themselves. Could you kindly clarify the under-the-hood mechanism when I query this object (eg. compare and contrast between Doc A and Doc B) and how to alter the query config file in this case?
My use case is as follows
I have there docs as vector stores:-
index1 = GPTSimpleVectorIndex.from_documents(doc1)
index2 = GPTSimpleVectorIndex.from_documents(doc2)
index3 = GPTSimpleVectorIndex.from_documents(doc3)
I then created a list index and further transformed it into a graph:-
graph = ComposableGraph.build_from_indices(
GPTListIndex,
[index1, index2, index3],
index_summaries=[index1_summary, index2_summary, index3_summary],
)
My queries involve a mixture of questions such as querying individual docs (eg. summarise doc1), compare/contrast between pairs or triplets, etc
I was just wondering if there are any specific query_config I need to use and how exactly it works to address the above query use cases?
The current query _config I am using is as follows:-
query_configs = [
{
"index_struct_type": "dict",
"query_mode": "default",
"query_kwargs": {
"similarity_top_k": 1,
# "include_summary": True
}
},
{
"index_struct_type": "list",
"query_mode": "default",
"query_kwargs": {
"response_mode": "tree_summarize",
}
},
]

Hi @Krishnan-9, I think we may have addressed this question in the discord as well - but the idea is that certain index structures might be better for certain use cases (e.g. use simple vector index to query individual docs, use a graph structure to compare/contrast between different documents).
How do you decide which index to use then, given the query?

You can define an "overall" graph to "choose" an index: https://github.com/jerryjliu/llama_index/blob/main/examples/composable_indices/QASummaryGraph.ipynb
You can define each index as a tool, and pass to a langchain agent

Closing issue for now, for more questions please followup in the discord


Server in 'imageRegistryCredentials' of container group should be a valid host name without protocol.

Hello, I am trying to use this workflow to deploy my latest docker image from ACR onto ACI. I am getting the following error:
##[error]Error: The server '$IMAGE_SERVER' in the 'imageRegistryCredentials' of container group 'somevalue-container' is invalid. It should be a valid host name without protocol.

The value of $IMAGE_SERVER is in the format somevalue.azurecr.io

Can you copy and paste your workflow file
@shubham1172

Ah, I lost the erroneous workflow file in my pool of commits! Now it's working, thanks!

I kind off get the same error just that it says The server '' (its empty) in the 'imageRegistryCredentials' etc..
Here is my workflow file:
name: Build and deploy timekeeping app

on:
  push:
    branches: [ master ]

jobs:

  build_and_deploy:

    runs-on: ubuntu-latest

    steps:
    - name: Checkout master branch
      uses: actions/checkout@v2

    - name: Azure authorization
      uses<EMAIL_ADDRESS>      with:
        creds: ${{ secrets.AZURE_CREDENTIALS }}

    - name: Login to private azure container registry
      uses: azure/docker-login@v1
      with:
        login-server: aronmregistry.azurecr.io
        username: ${{ secrets.REGISTRY_USERNAME }}
        password: ${{ secrets.REGISTRY_PASSWORD }}

    - name: Build and push to private azure container registry
      run: |
        docker build -t aronmregistry.azurecr.io/avento-timekeeping-app:latest .
        docker push aronmregistry.azurecr.io/avento-timekeeping-app:latest

    - name: Deploy container to an azure container instance
      uses: 'azure/aci-deploy@v1'
      with:
        resource-group: private-docker-registry
        dns-name-label: avento-timekeeping-app
        image: aronmregistry.azurecr.io/avento-timekeeping-app:latest
        registry-username: ${{ secrets.REGISTRY_USERNAME }}
        registry-password: ${{ secrets.REGISTRY_PASSWORD }}
        name: avento-timekeeping-container
        location: 'west europe'


Modify the upload_id field by Django builtin UUIDField

New in Django 1.8, there is a new field called UUIDField.
Feel free to close this for the consideration of  being compatible with the former edition.

Yes. I'd rather not merge this since that would mean dropping support for Django<1.8.


add firefox alpine

Hi, I'm not sure if you want to merge this (the Dockerfile is still a bit ugly and can probably be improved).
This image is about ~390M smaller than the debian one. :v:

Ah dope!
On Tue, Nov 7, 2017 at 7:57 AM, Christian<EMAIL_ADDRESS>wrote:

Hi, I'm not sure if you want to merge this (the Dockerfile is still a bit
ugly and can probably be improved).
This image is about ~390M smaller than the debian one. ✌
You can view, comment on, or merge this pull request online at:
https://github.com/jessfraz/dockerfiles/pull/307
Commit Summary

add firefox alpine

File Changes

A firefox/alpine/Dockerfile
https://github.com/jessfraz/dockerfiles/pull/307/files#diff-0 (14)

Patch Links:

https://github.com/jessfraz/dockerfiles/pull/307.patch
https://github.com/jessfraz/dockerfiles/pull/307.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jessfraz/dockerfiles/pull/307, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABYNbBr6Ia1N70xWTwMRffKdQNq3G-mmks5s0FOzgaJpZM4QUvui
.

--
Jessie Frazelle
4096R / D4C4 DD60 0D66 F65A 8EFC  511E 18F3 685C 0022 BFF3
pgp.mit.edu http://pgp.mit.edu/pks/lookup?op=get&search=0x18F3685C0022BFF3


Support Portable Class Libraries

I downloaded the source and was able to get it to compile with PCL but had to rework the code not to use Type.FindMembers.

Closed in favor to .NET Standard, see #48


Implement cache purge functionality

Let me know if there's anything you would like to get changed.

Looks good, thanks!


[docs] Add Typescript to CheckboxesGroup demo

[x] I have followed (at least) the PR section of the contributing guide.

TS does not like component={'legend' as 'div'} as a solution although has no problem with component={'fieldset' as 'div'}.  I followed that solution from a previous issue message chain.  I'm not sure why CheckboxesGroup.js is throwing a failure.

yarn docs:typescript:formatted changes  CheckboxesGroup.js so that we are passing in styles as a prop but then removes prop-types.  Lint wants me to keep prop-types in.


Added NetHavoc in Notable Tools

Hi @mittalani, thanks for the contribution. Could you please squash your commit?

Hi @dastergon, I don't have access to squash the commit. Let me know the steps to do it.

I did it from GH, thanks @mittalani


Update docs-reviewer and SIG maintainer nominations. [RELATED #61]

Add new reviewer/maintainer templates to support RFC #61.

The content of the guidelines is unchanged, simply reformatted

You have a conflict between this PR and https://github.com/o3de/sig-docs-community/pull/80/files -- they both edit governance/reviewers-maintainers.md.
I suggest removing changes to that file in this PR. I moved one of your changes in this PR as a suggestion into the other PR, but you may want to check for anymore differences.

There's one duplicate line hat should be removed, otherwise this is all good to go!