Publish tags that can be consumed by dependabot

As today, merging pull request in main branch triggers the publication of the images in Docker Hub based on the short revision hash (e.g: 220a007 -> 220a007, then d38de20 -> d38de20).
However, our downstream project relies on tags which are created manually (e.g.: 220a007 = 20230214-1).
I believe that once created, pushing the tag triggers the delivery jobs once more to deliver the image in Docker Hub (e.g.: 20230214-1).
Thus we can end up in the current situation where we had a few image updates published on Docker Hub, but w/o the proper tag to be consumed by downstream (e.g.: d006725 != 20230215-1)!
Maybe there is a good reason for this. But I don't see any.
In addition, it might be required for those tags to be semantically formatted (semver) in order to be consumed downstream by dependabot.

@wuan, does this make sense to you?

We selected the <date>-<increment> format originally as those releases combine versions from the upstream projects and semantic versioning will be not that straightforward. Given the low rate of releases we do here I'm not sure if we have an advantage automating the release process.

Thanks you for feedback @wuan

We selected the - format originally as those releases combine versions from the upstream projects and semantic versioning will be not that straightforward.

It makes sense indeed. Maybe Dependabot will not mind if we keep using this format. I'll try.

Given the low rate of releases we do here I'm not sure if we have an advantage automating the release process.

That's a bit the point here, there was a few updates we did not yet propagated downstream:

#18
#21
#28

And we can expect more (also by design since #29):

#23
#34
#31
#32

I don't mind keep it manual, but automation with something like gtihub-tag action might save us some time in the mid term already.
Said otherwise: do you (or anyone else) see any strong reason I would have missed to keep it manual?

That should be fine.

At the end, my tests have shown that Dependabot is dealing correctly with <date>-<inc>:
Bump leastauthority/magic-wormhole-mailbox from 20221108-1 to 20230214-1 in /ansible/docker/mailbox

Thus, the only reason left to use semver is the automation because I suspect it will likely be much easier to automatically bump 23.5.0 than 20230512-1.
In the meantime, I've found an other annoying problem to consume thos tags downstream: no support for docker-compose (yet)!

At the end, my tests have shown that Dependabot is dealing correctly with -

I think I've missed something there: I bet it will not work for 20230512-1 to 20230512-2.
I suspect the <inc> to not be interpreted as a part of the version, but rather as a flavor (e.g.: debian vs alpine).
Anyway, semver is likely a better choice... If we do something with Dependabot...

Just FYI, but that's usually called "CalVer" (i.e versions like 23.5.0 -- as magic-folder uses too) see https://calver.org/

I've remove the automation part in the title of the issue as it was secondary.
The most important part is to produce tags that can be consume by other processes downstream, starting with dependabot.
Though, once we manually publish one of those new tag (CalVer likely), we will have to pay attention to not brake those downstream process. This is where the automation could help I guess...
I believe the first new tag will have to be manual anyway.
I'm considering doing it with "23.05.0-slim-bullseye" as a first step.
But all things considered, I believe the images should be tagged slightly differently:

I've just pushed 23.2.0 (logs), which did overwrite the latest (as expected from reading the workflow).
But then I've just pushed 23.5.0 (logs), and the latest went back the latest images.
Note for later: we could save some build time if the tag were automatically released (not re-building the images twice).

Also, as for now the digests differs between the images published from main branch and from the tag.
Likely because the creation time differs too.
So I guess we are duplicating images per release...
I believe that automating the release when merging PR into the main branch is the only way we could avoid duplication.

Looks good:

updater | 2023/05/16 13:53:12 INFO <job_663549791> Latest version is 23.5.0
updater | 2023/05/16 13:53:12 INFO <job_663549791> Requirements to unlock own
updater | 2023/05/16 13:53:12 INFO <job_663549791> Requirements update strategy
updater | 2023/05/16 13:53:12 INFO <job_663549791> Updating leastauthority/magic-wormhole-mailbox from 23.2.0 to 23.5.0
updater | 2023/05/16 13:53:12 INFO <job_663549791> Submitting leastauthority/magic-wormhole-mailbox pull request for creation
  proxy | 2023/05/16 13:53:13 [074] GET https://api.github.com:443/repos/la-test/sbx-actions/commits?per_page=100
  proxy | 2023/05/16 13:53:13 [074] * authenticating github api request with token for api.github.com
  proxy | 2023/05/16 13:53:13 [074] 200 https://api.github.com:443/repos/la-test/sbx-actions/commits?per_page=100
updater | 2023/05/16 13:53:14 INFO <job_663549791> Finished job processing
updater | 2023/05/16 13:53:14 INFO Results:
updater | +---------------------------------------------------------------------------+
updater | |                    Changes to Dependabot Pull Requests                    |
updater | +---------+-----------------------------------------------------------------+
updater | | created | leastauthority/magic-wormhole-mailbox ( from 23.2.0 to 23.5.0 ) |
updater | +---------+-----------------------------------------------------------------+

I now have access to the Docker account and I've re-published 'real' tags for 23.2.0 = 20230214-1 images (the previous ones were actually broken due to #38.
But this does not seem to prevent Dependabot to propose PR for older version:

Bumps leastauthority/magic-wormhole-mailbox from 23.5.0 to 20230214-1.

Likely because from a SemVer point of view 20230214 > 23.0.5...

I'd better update the documentation!

I do not see how/what to update after all.

In order to fix the SemVer issue, I've manually tagged a few older versions and remove those last ones from Docker Hub:

221105-1 -> 22.11.0
221108-1 -> 22.11.1
230214-1 -> 23.2.0

I've also remove any every non-release tag released before #28
This repository should now be ready to be easily bumped from downstream.


Importing a freshly created dub project does not work.

When creating a new dub project with 'dub init stuff' (format: json) and then importing it using start intellij-> import project -> /folder/path/to/stuff/ -> import model from external model -> dub -> auto find -> finish.
The application hangs on the startup screen.
dub:  1.1.2.
compiler: dmd 2.072.2
idea: 2016.3.2 community
dlanguage: 1.10
os: windows 10 x64

I think this was an issue with compatibility that's now fixed in latest build.
https://github.com/kingsleyh/DLanguage/releases
should be in plugin repo soon. please test and let us know if there's still a problem


Cortex Update UX

How should we notify user for a new cortex update?
# always check for new update every time we run `cortex` command?
cortex
# and output something like:
cortex v0.1.1 is available, to update please run `cortex update`

cc: @dan-homebrew @louis-jan @hiento09 @namchuai @nguyenhoangthuan99

Close because duplicate of https://github.com/janhq/cortex/issues/1041


[1.X] Update tests/autohat

Can one of the admins verify this patch?

Can one of the admins verify this patch?

@resin-jenkins Ok to test

@resin-jenkins retest this please

@horia-delicoti can you rebase it and see what else this PR needs?
Thanks

@resin-jenkins retest this please


1

The website cannot be opened, please check it. Thank you

The hosted streamlit application experienced brief downtime. The application is back online at https://groqbook.streamlit.app.


⚠ Bofrost.at has degraded performance

In 4230679, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 826 ms

Resolved: Bofrost.at performance has improved in 0297955.


emacs render delay without X

Hello
When running emacs with no X inside extraterm, emacs always waits for nearly 2 seconds to show up, no matter what. This does not happen with any other terminal programs. I also tried disabling bash integration and framing output, or enabling "reduce graphic effects" under general settings.
Here are the numbers, showing time to start the application on same machine, without loading any startup options at all.
Running emacs in KDE Konsole:
time /usr/bin/emacs -nw -Q -e kill-emacs

real    0m0,075s
user    0m0,024s
sys     0m0,004s

Running emacs in Extraterm:
time /usr/bin/emacs -nw -Q -e kill-emacs

real    0m2,362s
user    0m0,015s
sys     0m0,012s

Also I realized this happens if I do not use X Window, when using X window, render times are much better, although not as good as running in another terminal.
time -p /usr/bin/emacs -Q -e "kill-emacs"
real 1.14
user 0.93
sys 0.08

time -p /usr/bin/emacs -nw -Q -e "kill-emacs"
real 2.47
user 0.43
sys 0.09

I do not know how to debug this further. Let me know if I can try anything else.

What exactly do you mean by "no X"? no DISPLAY variable? or Wayland?

Sorry, I meant this:
https://centos.pkgs.org/7/centos-x86_64/emacs-nox-24.3-23.el7.x86_64.rpm.html
Emacs, running without any X window support, clearly shows this problem. When started with X Window support from inside Extraterm, render times are a little bit better, but way more worse than running in any other terminal emulator.
Would running emacs with strace and attaching output help you debug this?

What I see here is that when emacs starts up it displays the top and bottom bars, then waits a couple seconds, and then shows the welcome screen. The other terminal I have here does not act the same. Does this match what you see?
I'm not trying to figure out what the difference is. It could be that emacs is waiting for some response from the terminal and timing out instead.

I just noticed that if you start emacs and then quick hit another key, then it starts up faster. emacs is waiting for some kind of automatic response from the terminal.

Yes, this is the same behaviour I see. Can confirm that when I hit a key, timeout cancels.
Here is the timed out syscall:
strace -o strace.out -ttTC /usr/bin/emacs -Q -e "kill-emacs"
...
10:52:38.706945 rt_sigprocmask(SIG_BLOCK, [INT], [], 8) = 0 <0.000011>
10:52:38.706980 rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 <0.000014>
10:52:38.707017 pselect6(7, [6], [], NULL, {tv_sec=1, tv_nsec=999893766}, {NULL, 8}) = 0 (Timeout) <2.002082>
10:52:40.709265 rt_sigprocmask(SIG_BLOCK, [INT], [], 8) = 0 <0.000120>
10:52:40.709482 rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 <0.000013>
10:52:40.709533 ioctl(6, FIONREAD, [0]) = 0 <0.000015>

That pselect6 call waits for 2 secons. Here is the same strace lines with another terminal:
10:57:23.123340 rt_sigprocmask(SIG_BLOCK, [INT], [], 8) = 0 <0.000008>
10:57:23.123368 rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 <0.000008>
10:57:23.123393 pselect6(6, [5], [], NULL, {tv_sec=1, tv_nsec=996049424}, {NULL, 8}) = 1 (in [5], left {tv_sec=1, tv_nsec=954858531}) <0.041248>
10:57:23.164757 --- SIGIO {si_signo=SIGIO, si_code=SI_KERNEL} ---
10:57:23.164854 rt_sigreturn({mask=[]}) = 1 <0.000129>
10:57:23.165085 rt_sigprocmask(SIG_BLOCK, [INT], [], 8) = 0 <0.000013>
10:57:23.165135 rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 <0.000012>
10:57:23.165174 ioctl(5, FIONREAD, [11]) = 0 <0.000013>

I was hunting this down last night and got much closer to a cause.

Fix released in 0.54.0


launch.json: "${command:pickProcess}" prompts for a process to attach to before running pre-launch tasks

As of VSCode v1.35.1, a launch configuration defined in launch.json that uses "${command:pickProcess}" as its "processId" value - in order to prompt for a process to attach to - does so before running any pre-launch tasks (preLaunchTask property).

Is this by design?
Is there a way to reverse this order?

The reason I want my prelaunch task to run first is twofold:

generally, since my prelaunch task includes building, I want the launch to be aborted if building fails.

specifically, my prelaunch task creates  the process that I then want to attach to.

Taking a step back, my ideal solution would be to have the prelaunch task not only create the process to attach to, but to have the launch configuration automatically attach to it afterwards, but I haven't found a way to do that, given that:

starting the debugger from the command line isn't supported yet - though support is being considered - see #10979

there seems to be no way to populate a launch-configuration property from an arbitrary shell command (you can only call VSCode-internal commands via ${command:...}).

Note: I hit this limitation when trying to debug binary PowerShell modules via an external PowerShell console. I've since realized that the C# debugger automatically attaches to any external process created via a "request": "launch" launch configuration, so launching a PowerShell console that way (with a startup command that imports the binary module) is sufficient.

I too am having this exact same problem.  I would expect my prelaunch task (which stops my remote process, builds and pushes my project to the remote box, then restarts the remote process) to finish executing before picking the process to attach to.
There are easy enough workarounds, but it should be able to work in a one-step process.

@isidorn what is the order of resolving variables and running the prelaunch task?

We first resolve the varialbes and then run the preLaunchTask. Code pointer

Understood re current design, but I think there is a usability issue here:
It doesn't make sense to pick a process first, if the pre-launch task can fail.
I understand that variable resolution coming first is what triggers the untimely prompting, but I wonder if an exception can be made in this case: defer any "${command:pickProcess}" actions until after the pre-launch tasks have run successfully.
If not all cases of untimely prompts can reliably be inferred (given that there can be arbitrary extension-supplied commands such as extension.pickNodeProcess), perhaps an opt-in property could solve the problem.


Signup and Login function created

Congratulations! Users can now sign up and log in successfully! However, it seems that some checks were not successful. I would greatly appreciate it if you could review them once more. Thank you for your hard work and dedication.


pipeline creation error: 500 Internal Server Error

What is your question?

here is the docker log:

here is the docker log:

What's your phantoscope version and os information.
It looks like phantoscope can not connect to operator instance.
Can you get container api-server  detector1 encoder1 ip?

it seems that face_detector1 has sth wrong

No, it's all right.
Can you get you api-server container ip?
What's your os information and phantoscope version ?

phantoscope version: 0.2.0
os information: Linux version 3.10.0-1127.13.1.el7.x86_64
api-server container ip: <IP_ADDRESS>(private)

It seems api-server and operator instance do not exist in the same network.
Could you show me  docker inspect <one of operator instance docker id> Networks fields?

face_detector1:
"Networks": {
"phantoscope_default": {
"IPAMConfig": null,
"Links": null,
"Aliases": [
"8aba6e786d67"
],
"NetworkID": "c49302d059521d6eb8e6fbcea76bbfbdadf6a770e2d2ceb16bb3f99868cb37a3",
"EndpointID": "ca32f425338371fedb7af68d278c0dd7dff6de0f7c627ce29b0f8524f7ff2900",
"Gateway": "<IP_ADDRESS>",
"IPAddress": "<IP_ADDRESS>",
"IPPrefixLen": 16,
"IPv6Gateway": "",
"GlobalIPv6Address": "",
"GlobalIPv6PrefixLen": 0,
"MacAddress": "02:42:ac:12:00:08",
"DriverOpts": null
}
}
api-server:
"Networks": {
"phantoscope_default": {
"IPAMConfig": null,
"Links": null,
"Aliases": [
"api",
"670344051e89"
],
"NetworkID": "c49302d059521d6eb8e6fbcea76bbfbdadf6a770e2d2ceb16bb3f99868cb37a3",
"EndpointID": "176264669d2c536c9f213db5bdfd54cece5f2e41813d793182e9771d15d1929e",
"Gateway": "<IP_ADDRESS>",
"IPAddress": "<IP_ADDRESS>",
"IPPrefixLen": 16,
"IPv6Gateway": "",
"GlobalIPv6Address": "",
"GlobalIPv6PrefixLen": 0,
"MacAddress": "02:42:ac:12:00:05",
"DriverOpts": null
}
}

All right here.
Api-server and operator instances are in the same network.
It's confusing.
I suggest that you can retry it.
Of course, you can docker exec into the api-server and ping the ip of detector1 and encoder1 container to ensure the communication between them not refused by firewall.

I've cleared the environment and repeated all the steps.  I've created example_app and object_example successfully.
but when i run the following script , the API still return info  ' 500 Internal Server Error'.
Can you help me find the script problem?
`export LOCAL_ADDRESS=$(ip a | grep -Eo 'inet (addr:)?([0-9].){3}[0-9]' | grep -Eo '([0-9].){3}[0-9]' | grep -v '<IP_ADDRESS>'| head -n 1)
curl --location --request POST ${LOCAL_ADDRESS}':5000/v1/operator/register'
--header 'Content-Type: application/json'
--data '{
"name": "face_detector",
"addr": "psoperator/face-detector:latest",
"author" :"phantoscope",
"type":"processor",
"description": "detect face in input images",
"version": "0.1.0"
}'
curl --location --request POST ${LOCAL_ADDRESS}':5000/v1/operator/register'
--header 'Content-Type: application/json'
--data '{
"name": "face_encoder",
"addr": "psoperator/face-encoder:latest",
"author" :"phantoscope",
"type":"encoder",
"description": "embedding face img as vector",
"version": "0.1.0"
}'
curl --location --request POST ${LOCAL_ADDRESS}':5000/v1/operator/face_detector/instances/face_detector1'
--header 'Content-Type: application/json'
curl --location --request POST ${LOCAL_ADDRESS}':5000/v1/operator/face_encoder/instances/face_encoder1'
--header 'Content-Type: application/json'
下面这步一直错误
curl --location --request POST ${LOCAL_ADDRESS}':5000/v1/pipeline/face_pipeline'
--header 'Content-Type: application/json'
--data '{
"description":"face img detect and encode",
"processors": [{
"name": "face_detector",
"instance":"face_detector1"
}],
"encoder": {
"name": "face_encoder",
"instance":"face_encoder1"
}
}'`

I have found  a bug of these two operator.
I will fix it today.

I have fix operator image bug.
you should run docker ps -a | grep phantoscope_ | awk '{print $1}' | xargs docker rm -f delete wrong instance
run docker rmi psoperator/face-detector:latest and docker rmi psoperator/face-encoder:latest to delete previous docker images.
Then you could pull new image by yourself or create instances directly.
Thanks for your issue report.

it's ok. thank you !


One folder cannot be used for multiple collections (with filter applied)

steps to reproduce:

checkout the sveltia branch of https://github.com/basa-casa/hugo-admin
hugo server
http://localhost:1313/admin/collections does not display any folder collections (there are a lot) but does display files collections (there are two). both collections have the same filter field but different values (folder or files).

filter:
  field: collection_type
  value: folder

After changing collections all from "folder" to files, each displays in the files collections entries.
Field collections at http://localhost:1313/admin/fields also do not function.

Looks like the filter itself is fine, but the entry listing is confused because folder: data/scms/collections is used for both collections. Fixing.

Let me think about how to fix this... Having a many-to-many relationship will affect many parts of the app. 😅
I’m shipping the fixes for #202 and other issues first.

I’m also checking for other bugs with your setup. One thing I’ve noticed is, on http://localhost:1313/admin/#/collections/admin-pages/entries/collections, the Add menu checkbox doesn’t work as expected.

I have made progress. It’s a major refactoring, so I’ll make sure everything works well.

The fix landed in v0.39.9. I’ll work on remaining hugo-admin compatibility issues later this week.


After training process, how to run dqn_stages with the save_model?

For Turtlebot [ROS 1] Machine Learning: https://emanual.robotis.com/docs/en/platform/turtlebot3/machine_learning/
After training your stages, a model is saved in the save_model directory. For example: If I trained dqn_stage_4 for around 3000 episodes, it saves the trained model in "save_model" folder in several formats such as JSON and h5. Whenever trying to run the dqn_stage_4, it starts from the beginning. If I wanna test my trained model, how can I load the JSON or h5 saved model into code so that I can avoid training from the beginning every time running the code?
@ROBOTIS-David @ROBOTIS-Will

Please refer to #8. Thanks


CircleCI todos

Just making a note of a few things to look at after we get fully running on CircleCI 2.

Cache Android SDKs
Tune worker parameters, see if/how parallelism helps us
Look into resource_class for Android builds: https://circleci.com/docs/2.0/configuration-reference/#resource_class
Adjust NDK cache key since uploading the cache archive is slower than installing the NDK (share across branches? don't cache?)

Currently I'm leaning towards not caching the NDK, as you said it's slower than downloading and extracting the archives.
To add to your list:

[ ] Look into using a custom image with various dependencies set up ahead of time

The custom image could be set up ahead of time with the Android SDKs and NDK, but as you pointed out in the PR keeping the image up to date may be more trouble than it's worth. Some work has already gone into setting up such an image, see the ContainerShip/ folder in this repo.

Once the test APK is built and native libraries are compiled, we may be able to fan out into three separate jobs that run unit tests, integration tests, and end to end tests in parallel, if that speeds up things. For these three, we may be able to use the basic android docker images, installing node on the last two as needed.

resource_class: large
it is working fine on our projects

Re-opening as this is a discussion task.

@grabbou just opened a PR to move over iOS/tvOS tests from Travis to Circle: https://github.com/facebook/react-native/pull/16354

@hramos is Circle CI robust enough that we can actually run the unit and integration tests on tvOS?  At the moment I believe we're just testing that tvOS compiles....


Incorrect default volume on first load

When installing the extension from the Chrome Web Store, the default volume displays as 0.5 instead of 50. This issue only occurs on the first load after installation. Interestingly, when loading the extension as unpacked, the volume displays correctly, which only makes it more confusing.

@sb2bg Fixed? Should be updated in v1.2.6; you may need to click Update in the extensions tab.

Implemented checks for volume load in v1.2.6


The source code tab is not working in Chrome

The source code tab for REST and RPC services of the new UI (dev branch) is not working in Chrome. This issue seems to be related to the ng-click usage in a <select> in AngularJS: http://stackoverflow.com/questions/21051345/select-options-through-ng-click-is-not-working-in-chrome-browser-using-angularjs. I'm working to fix it.

Solved in #29


Image not displaying

Hi guys,
I am new to django ads. I have created a project called mysite and inside that project I have created an app called advertisements.
See the link below.

In my template, the link is working fine. However, the image is not loaded.
The console says Not Found: /advertisement/iphone.jpeg
Can anyone help me?

Ran into a similar issue and the problem seems to be from the JavaScript file. @younganakin were you able to overcome the problem?


Fix: check correctly the attribute we want to set

Related to #58

Codecov Report

Merging #59 into master will not change coverage.
The diff coverage is 0%.

@@           Coverage Diff           @@
##           master      #59   +/-   ##
=======================================
  Coverage   26.42%   26.42%
=======================================
  Files          18       18
  Lines         193      193
=======================================
  Hits           51       51
  Misses        142      142

Impacted Files
Coverage Δ

src/client/updaters/updateTags.js
3.57% <ø> (ø)
:white_check_mark:

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 81d0139...0a24a67. Read the comment docs.

Sorry to insist on this but, is this gonna be merged soon?
Cheers
Jerome

@Atinux any chance this gets merged soon?

Thanks @Atinux. I also saw there is no release since last december. Is it possible to release this on NPM?
Cheers
Jerome

I am working on it actually @jeerbl :)

Very nice of you. Thanks a lot for this!
Jerome


Need Azure Active Directory group claims support

Azure AD has the ability to provide group membership claims in the JWT (or, if there are too many groups, a group.link value that the application can use to obtain a paged list of groups).
I'd like to be able to pass this data along to the proxied application in the X-Forwarded-Groups header.
This looks fairly straightforward. Are there any caveats I should keep in mind when adding this?

It also looks like AAD supports roles claims as well. If it's straightforward, I may add explicit support for that as well.

#347 adds this support.


[Service Bus Client] Client Read-Only Property mockability

Summary
The focus of these changes is to virtualize the read-only properties on Service Bus clients that cannot be set through the constructor so that their values can be mocked during testing.
Last Upstream Rebase
Tuesday, January 26, 11:50am (EST)

Fixes #17602

Fixes #17602

/azp run net - servicebus - tests

/azp run net - servicebus - tests


Compute CMVN with multiprocessing, it takes about 20% of origin time …

…for both global-cmvn and speaker-cmvn.

*Compute CMVN with multiprocessing, it takes about 20% of origin time for both global-cmvn and speaker-cmvn.
(computering time of aishell speaker-cmvn for 8 num_cmvn_workers is about 780s)
We divede entries into many chunks, and each process compute the corresponding chunk, by considering:
1、if each process computes the CMVN of per speaker, it will take a lot of time to restart multi-process;
2、it will use too large number of process when number of speakers is too large, which may not acceptable for user's device.
3、multi-process works for both global-cmvn case and speaker-cmvn case.
*Run cmnv_main.py with CUDA_VISIBLE_DEVICES='', because sub-process will take some gpu memory and it may cause OOM when we use a large number of process.

*Compute CMVN with multiprocessing, it takes about 20% of origin time for both global-cmvn and speaker-cmvn.
(computering time of aishell speaker-cmvn for 8 num_cmvn_workers is about 780s)
We divede entries into many chunks, and each process compute the corresponding chunk, by considering:
1、if each process computes the CMVN of per speaker, it will take a lot of time to restart multi-process;
2、it will use too large number of process when number of speakers is too large, which may not acceptable for user's device.
3、multi-process works for both global-cmvn case and speaker-cmvn case.
*Run cmnv_main.py with CUDA_VISIBLE_DEVICES='', because sub-process will take some gpu memory and it may cause OOM when we use a large number of process. @tjadamlee @Some-random


[joint_storage] impl purgeUncoveredNonserialJointsUnderLock

used to clean up data by system timer every 60s

this is a timely evoked function used by system every 60s


VM debug logging can interfere with tests examining stderr

FAILED: dartk-vm release_x64 standalone_2/io/dart_std_io_pipe_test
Expected: Pass
Actual: RuntimeError

--- Command "vm" (took 25.000780s):
DART_CONFIGURATION=ReleaseX64 out/ReleaseX64/dart --short_socket_write --optimization-counter-threshold=5 --sync-async --ignore-unrecognized-flags --packages=/b/s/w/ir/.packages /b/s/w/ir/tests/standalone_2/io/dart_std_io_pipe_test.dart

exit code:
255

stderr:
Unhandled exception:
Expect.equals(at index 0: Expected <Hello\x0A>, Found: <Attempt:11 waiting for 1 threads to check in\x0AAttempt:12 waiting for 1 threads to check in\x0AAttempt:13 waiting for 1 threads to check in\x0AAttempt:14 waiting for 1 threads to check in\x0AAttempt:15 waiting for 1 threads to check in\x0AAttempt:16 waiting for 1 threads to check in\x0AAttempt:17 waiting for 1 threads to check in\x0AHello\x0A...>) fails.
#0      Expect._fail (package:expect/expect.dart:651:5)
#1      Expect.equals (package:expect/expect.dart:119:9)
#2      checkFileContent (file:///b/s/w/ir/tests/standalone_2/io/dart_std_io_pipe_test.dart:28:10)
#3      test.<anonymous closure>.<anonymous closure> (file:///b/s/w/ir/tests/standalone_2/io/dart_std_io_pipe_test.dart:68:11)
#4      _RootZone.runUnary (dart:async/zone.dart:1379:54)
#5      _FutureListener.handleValue (dart:async/future_impl.dart:129:18)
#6      Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:642:45)
#7      Future._propagateToListeners (dart:async/future_impl.dart:671:32)
#8      Future._completeWithValue (dart:async/future_impl.dart:486:5)
#9      Future._asyncComplete.<anonymous closure> (dart:async/future_impl.dart:516:7)
#10     _microtaskLoop (dart:async/schedule_microtask.dart:41:21)
#11     _startMicrotaskLoop (dart:async/schedule_microtask.dart:50:5)
#12     _runPendingImmediateCallback (dart:isolate/runtime/libisolate_patch.dart:115:13)
#13     _RawReceivePortImpl._handleMessage (dart:isolate/runtime/libisolate_patch.dart:172:5)

--- Re-run this test:
python tools/test.py -m release -n dartk-optcounter-linux-release-x64 standalone_2/io/dart_std_io_pipe_test

@a-siva

I think the actual bug here should not be about the interference: we have a test where we could not enter a safepoint after 17 seconds. This indicates a bug in runtime or in the safepointing mechanism.
If we did not have logging here - we would not know what caused the Timeout.
/cc @a-siva


Fixup require wrapper case handling

This extends the support and coverage for the require wrapper detection and handling.
It also fixes a bug that was being thrown for invalid wrapper detection cases.

Codecov Report

Merging #50 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master      #50   +/-   ##
=======================================
  Coverage   76.03%   76.03%
=======================================
  Files          10       10
  Lines        1106     1106
=======================================
  Hits          841      841
  Misses        265      265

Impacted Files
Coverage Δ

src/asset-relocator.js
83.49% <100%> (ø)
:arrow_up:

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 da8d65a...5bde664. Read the comment docs.

Fast-tracking to release a ncc patch.


Update order details on address change

I want to merge this change because... fetch the order prices from backend on any changes in draft order.

PR intended to be tested with API branch:
Screenshots

Pull Request Checklist

[ ] All visible strings are translated with proper context.
[ ] All data-formatting is locale-aware (dates, numbers, and so on).
[ ] Translated strings are extracted.
[ ] Number of API calls is optimized.
[ ] The changes are tested.
[ ] Data-test are added for new elements.
[ ] Type definitions are up to date.
[ ] Changes are mentioned in the changelog.

Test environment config

API_URI=https://master.staging.saleor.rocks/graphql/

Task linked: SALEOR-1031 Any changes in draft order should fetch the order prices from backend


Run Benchmarks in GitHub Actions

Run Benchmarks in GitHab Actions to detect impact of a PR on the performance.
Probably https://github.com/benchmark-action/github-action-benchmark could be used.

Implemented by https://github.com/riok/mapperly/pull/632


Allow customization of fetch

For my use case, I am trying to set up resolving certain installs of packages through the FileSystem API. With a custom provider, generating the right URLs is straighforward, but I run into Module not found errors once I try to run install, of course (since the files are not accessible via any URL).
It would be great if I could overwrite fetch to give custom responses. This could be global (extending fetchOptions) or tied to the provider. Then, I could for example respond to fetch("my/local/url") by accessing the File System through the FileSystem API, creating a Response object and returning it.
I appreciate the previous changes, by the way, my use case is really coming together thanks to your work! :)

This is a good suggestion, I've put something together in https://github.com/jspm/generator/pull/385, let me know if that can work for you.

That's great, thank you! Should work perfectly for me: I can setFetch with my own implementation where I match the given URL and perform my file system access, or fall back to the default fetch implementation for all other URLs.


Household income filter

User can filter by different household income levels. If they click on a range, only partners or projects that are located in a county with that range should appear.

Done


Telemetry for streaming h2/grpc traffic

Feature request is to improve observability for streaming requests. Two major items:

[ ] monitoring of long requests, by sending intermediate reports
[ ] separating uni/bidi requests in streaming gRPC calls

/assign @kyessenov


Remove call out about region availability

IoT Plug & Play is now available in all region, so this call out is no longer needed.

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

ID: 71773c6a-a8fa-4c14-83ad-9eaad4d37d12
Version Independent ID: 44de9fce-33b0-915e-06c0-4490acd86a87
Content: Connect IoT Plug and Play Preview sample device code to IoT Hub (Windows)
Content Source: articles/iot-pnp/quickstart-connect-pnp-device-c-windows.md
Service: iot-pnp
GitHub Login: @ChrisGMsft
Microsoft Alias: chrisgre

@wickste Thanks for the heads up! The doc will be updated accordingly.

Created the PR and changes will go live once it has been peer reviewed and merged.
We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Command-line parameters with hyphens in matter-controller example ignored on macOS

I'm testing the matter-controller example (here) and encountering an issue with the command-line parameters ble-thread-networkname and ble-thread-operationaldataset.
When I launch the following command:
npm run matter-controller --
--ble
--ble-thread-networkname=<my-ble-threadnetworkname>
--ble-thread-operationaldataset=<my-ble-thread-operationalset>
--pairingcode=<my-pairing-code>

the ble-thread-networkname and ble-thread-operationaldataset parameters are ignored.
To workaround this, I had to modify the source code in ControllerNode.ts by removing the hypens (-) in the variable names.
I changed these lines of code:
https://github.com/project-chip/matter.js/blob/39bacbc009ff4ba55b8fd7bb3df5012669bac553/packages/examples/src/controller/ControllerNode.ts#L102-L103
as follows:
const threadNetworkName = environment.vars.string("blethreadnetworkname");
const threadOperationalDataset = environment.vars.string("blethreadoperationaldataset");

and modified the command to:
npm run matter-controller --
--ble
--blethreadnetworkname=<my-ble-threadnetworkname>
--blethreadoperationaldataset=<my-ble-thread-operationalset>
--pairingcode=<my-pairing-code>

I believe the issue may be more general and related to parameters that contain hyphens (-) between words.
Am I doing something wrong when passing these parameters, or could this be a compatibility issue with macOS?
My setup:

Operating System: macOS Sonoma 14.6.1 (MacBook Pro 2023 - Apple M2 Pro)
Node.js version: v20.17.0

Thats convention ... "-" in the CLI or "_" in env names translate to "." int the "env.get()" calls. See also the examples and the example description

@Apollon77 Sorry, I don't understand.
The readme didn't mention anything about it.
So, what's the correct way to pass argument from CLI?

hm ... in https://github.com/project-chip/matter.js/blob/main/packages/examples/README.md#general-cli-information you can find infos about this - but yes the implicit limitation that _ and - are kind of "forbidden characters" for this tpo work is not included.
Short:
If you like to use --ble-thread-networkname=
Then your code need to use
environment.vars.string("ble.thread.networkname");
to get this value


ticktock stream deployment error

I've set up kafka, mysql, and scdf services & rc on a Kubernetes 1.2 cluster - I used NodePorts instead of LoadBalancer in the scdf service and with that I am about to open the dashboard on localhost. I am stuck at step 10 of the example (http://docs.spring.io/spring-cloud-dataflow-server-kubernetes/docs/1.0.0.RELEASE/reference/htmlsingle/). I am able to register docker:springcloudstream/time-source-kafka:latest as source & docker:springcloudstream/log-sink-kafka:latest sink but deployment of "stream create --name ticktock --definition "time | log" --deploy" is failing with the following exceptions:
2016-08-31T15:00:59.420555172Z Caused by: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target 2016-08-31T15:00:59.420567646Z 	at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:387) ~[na:1.8.0_92-internal] 2016-08-31T15:00:59.420574991Z 	at sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:292) ~[na:1.8.0_92-internal] 2016-08-31T15:00:59.420582081Z 	at sun.security.validator.Validator.validate(Validator.java:260) ~[na:1.8.0_92-internal] 2016-08-31T15:00:59.420588738Z 	at sun.security.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:324) ~[na:1.8.0_92-internal] 2016-08-31T15:00:59.420595581Z 	at sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:229) ~[na:1.8.0_92-internal] 2016-08-31T15:00:59.420602522Z 	at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:124) ~[na:1.8.0_92-internal] 2016-08-31T15:00:59.420609339Z 	at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1491) ~[na:1.8.0_92-internal] 2016-08-31T15:00:59.420616163Z 	... 98 common frames omitted 2016-08-31T15:00:59.420622474Z Caused by: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
Could you please suggest what could be going wrong?

Do you have the correct URI for KUBERNETES_MASTER in your scdf-controller.yml? You can check the current value with kubectl describe pod scdf. It should match the value returned by kubectl cluster-info, look for Kubernetes master is running at .

Yes, the scdf server can connect to the kubernetes master, the mysql test database is also populated when I register the time & log modules. The certification path error comes up when I try to deploy the ticktock stream.

Where do you see this exception? Can you post the complete stacktrace?

In the log of the scdf server replication controller. Here's a link to the complete stacktrace: https://gist.github.com/linusviking/44f2fe38961f3aa88b00c6785cb10b43

I don't recognize the logging pattern - 2016-09-01T10:13:23.166360314Z 2016-09-01 10:13:23.121  INFO - is this a custom build or the docker image from springcloud/spring-cloud-dataflow-server-kubernetes

Yes, I'd built a custom image. I get the same "certification path to requested target not found" with the docker image from springcloud/spring-cloud-dataflow-server-kubernetes. Here's the complete stacktrace: https://gist.github.com/linusviking/a03c274b91e16131423c6750fa911321
The file not found errors at line 191 & 277 were caused when I tried to create the ticktock stream without registering the apps. Errors from line 358 were caused after post registration of the time & log apps.

Is this on a Google Container Engine cluster or some other cluster. Maybe you are missing the necessary CA certificates for Java to use SSL?

I am deploying on a local K8 cluster. Is there a way to disable SSL on the Spring Cloud Dataflow server?

Clearing out old issues - did you ever get this resolved? If not please re-open this issue and post the entire stack trace so we can se where it is coming from.


Animated trisurf with variable number of vertices and ipywidgets

Hello hello,
first off, I like the library, nice work so far! However, I encountered something I want to do, but can't.
I have a timeseries of 3D density data, and I want to make animated contours/isosurfaces/density plots (same concept, different jargon). I make the surfaces with scikit-image's marching cubes. And of course I want to plot them with ipyvolume. Plotting a single using plot_trisurf works just fine. The trouble comes with animating the whole thing.
The surfaces have a different number of vertices and triangles, so I can't use the build-in animation capabilities. Instead, I elected to do the animation controls with ipywidgets (also because they're shiny).
The first thing I tried was to create all Meshes first, setting their visible to False, and making the animation loop toggle the correct one. This works for small cases, but uses way to much memory on the JS side to work for my case.
The next attempt was to create the appropriate Mesh on change, but I haven't found a way to remove the previous Mesh (and after drawing 10 on top of each other my memory craps out).
So, my questions: is there a convenient way to 1) animate trisurf's with different numbers of vertices (#90); or 2) remove specific Meshes from the figure; or 3) clear all meshes from the figure without modifying the scene limits or the camera?
Keep up the good work, ipyvolume is one of the three 3D plotting libraries I found with a quick search (next to Mayavi (pain to install/doesn't work on Py3) and Plot.ly)! And I like yours better so far :)
PS. Maybe good to add, I also tried setting the Mesh's .x, .y, .z and .triangles attributes, but that didn't propagate to the picture.

Hi Peter,
thanks for your positive words!
Note that there is a (ipyvolume.plot_isosurface)[http://ipyvolume.readthedocs.io/en/latest/api.html#ipyvolume.pylab.plot_isosurface] function, but it does exactly what you do with skimage.
Indeed it is related to #90, and a good example of why some interpolation is needed.
The memory usage is indeed the reason why I did the interpolation for the Scatter object, for the Mesh, there is still some work to be done.
To remove all meshes, you can do:
fig = ipv.gcf()
meshes = list(fig.meshes) # not sure what happens when you close before removing
fig.meshes = []
for mesh in meshes:
 mesh.close()

To remove a specific mesh:
fig = ipv.gcf()
meshes = list(fig.meshes) # make a copy, otherwise we modify in place, which traitlets won't detect
meshes.remove(some_mesh)
fig.meshes = meshes

I'll continue the discussion in #90 for the interpolation, please subscribe to that if you want to follow up.
Could you open a new issue for the issue in the PS?

Hi,
thanks for the quick reply. Unfortunately I'm not near my computer with either ipyvolume or my data, so I can't try things yet.
I'll give things a whirl, make a minimal example for the PS, and try to get back to you the second week of January.
Happy holidays :)

I think this is solved (see referenced PR), if not open again please.

Great, thanks for the feedback


updated data files to include fields with welsh translations

When you have a minute, I'd like a second opinion on the field-names please.

Oh I see, it's Welsh for 'name'. I would stick with the established pattern name-cy unless we have new advice on translations.


Finalizing setup (double confirm is it got anything missing)

Hi. And sorry if asking silly question..
As picture i share. After i finish final setup,this is all i get. It is normal or am i missing something?
I only get: luma3ds updater, Fbi, and hb launcher only..and my homebrew got nothing new app or tool.
Cos I thought luma3ds is an app.😆
Thanks,
And sorry for inconvenience cause.

And i using n3ds and after all step my device become 11.0.0-33j
Thanks

Yes. You're fine. You ended the guide. Congratz!

Ok.. thank you very much.. 👍
Good job for giving clear guide.. thanks..


Support creating new factories with different dependencies

In angular 1.3 the source for the factory provider is as follows:
function factory(name, factoryFn, enforce) {
  return provider(name, {
    $get: enforce !== false ? enforceReturnValue(name, factoryFn) : factoryFn
  });
}

enforceReturnValue shadows the factoryFn from being exposed, which prevents doing something like:
module.config(function($provide, $injector, myFactoryProvider) {
  $provide.factory('myNewCoexistingFactory', function(){
    var newDependencies = {oldDependency: $injector.get('newDependency')};
    return $injector.invoke(myFactoryProvider.$get, null, newDependencies);
  });
});

I'd like it if factory passed something like {$get: ..., $factoryFn: factoryFn} to provider.
Is this an acceptable change? If so I'd be happy to submit a pull request.
Thanks.

Hi, sorry for taking this long to answer. Do you understand that this has the potential that you will end up with multiple instances of myFactory, and that this has implications to Angular flat injector/services are singletons mechanism? A simpler solution would be to decorate oldDependency (even when that would change it for all services that depend on this)
I am leaning towards making this a non-issue

Agree with @lgalfaso here. The solution with the current DI is to register a custom factory function as a service, inject this function into your objects and invoke the registered factory function to get different object instances on each call.
My call here would be to close this one as "won't fix".

I agree with @lgalfaso and @pkozlowski-opensource. Also, no answer from OP.


WIP: Evals

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
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.

is this referring to model evals? like https://github.com/openai/evals


Add Reaper

#107  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @rbro112 and the rest of your teammates on  Graphite


Umbrella header for module 'Realm' does not include header '/core/realm.h'

Goals
Updated Realm Swift to 10.5.2. Trying to build our project with it.
Expected Results
Project builds without errors or warnings concerning Realm library.
Actual Results
A warning about umbrella  header is displayed: /:1:1: Umbrella header for module 'Realm' does not include header '/core/realm.h'

Steps for others to Reproduce
Just build any swift project with Realm pod having inhibit_all_warnings! and use_modular_headers! settings in Podfile.
Podfile
platform :ios, '11.0'

source 'https://github.com/CocoaPods/Specs.git'

inhibit_all_warnings!
use_modular_headers!

target 'Mobile-Mos.ru' do

  pod 'Firebase/Crashlytics'
  pod 'Firebase/Analytics'
  pod 'Socket.IO-Client-Swift', '< 16'
  pod 'gRPC-Swift', '1.0.0-alpha.20'

  pod 'Stencil'
  pod 'FLAnimatedImage'
  pod 'Kingfisher'
  pod 'YandexMapsMobile', '4.0.0-full'
  pod 'YandexMobileAds'
  pod 'YandexMobileMetricaPush'
  pod 'CardIO'

  pod 'Pulley'
  pod 'AXPhotoViewer/Core', :git => 'https://github.com/OneSman7/AXPhotoViewer.git', :branch => 'resources_bundle'
  pod 'AXPhotoViewer/Kingfisher', :git => 'https://github.com/OneSman7/AXPhotoViewer.git', :branch => 'resources_bundle'
  pod 'JTAppleCalendar', '~> 7.0'
  pod 'Chatto', :git => 'https://github.com/badoo/Chatto.git', :commit => '79f9e4091c23788a70421d434d966e223f205dea'
  pod 'ChattoAdditions', :git => 'https://github.com/badoo/Chatto.git', :commit => '79f9e4091c23788a70421d434d966e223f205dea'

  target 'Mobile-Mos.ruTests' do
      inherit! :search_paths
  end

end

post_install do |installer|

    pods_project = installer.pods_project

    # Determining minimal deployment target

    deployment_target_key = 'IPHONEOS_DEPLOYMENT_TARGET'
    deployment_targets = pods_project.build_configurations.map{ |config| config.build_settings[deployment_target_key] }
    minimal_deployment_target = deployment_targets.min_by{ |version| Gem::Version.new(version) }

    puts 'Minimal deployment target is ' + minimal_deployment_target
    puts 'Setting each pod deployment target to ' + minimal_deployment_target

    # Removing arm64 arch for simulator until all libraries support it

    simulator_excluded_archs_key = 'EXCLUDED_ARCHS[sdk=iphonesimulator*]'
    simulator_excluded_archs_value = 'arm64'
    aggregate_targets_names = installer.aggregate_targets.map{ |target| target.name }.to_set

    puts 'Removing arm64 arch for simulator'

    # Updating pods targets build configurations settings

    pods_project.targets.each do |target|
      target.build_configurations.each do |config|
        config.build_settings[deployment_target_key] = minimal_deployment_target
        unless aggregate_targets_names.include?(target.name)
          config.build_settings.delete(simulator_excluded_archs_key)
          config.build_settings[simulator_excluded_archs_key] = simulator_excluded_archs_value
        end
      end
    end

    # Updating aggregate targets Xcode Configuration (.xcconfig) files

    installer.aggregate_targets.each do |aggregate_target|
      aggregate_target.xcconfigs.each do |config_name, config_file|
        config_file.attributes.delete(simulator_excluded_archs_key)
        config_file.attributes[simulator_excluded_archs_key] = simulator_excluded_archs_value
        xcconfig_path = aggregate_target.xcconfig_path(config_name)
        config_file.save_as(xcconfig_path)
      end
    end

    Dir.glob(installer.sandbox.target_support_files_root + "Pods-*/*.sh").each do |script|
        flag_name = File.basename(script, ".sh") + "-Installation-Flag"
        folder = "${TARGET_BUILD_DIR}/${UNLOCALIZED_RESOURCES_FOLDER_PATH}"
        file = File.join(folder, flag_name)
        content = File.read(script)
        content.gsub!(/set -e/, "set -e\nKG_FILE=\"#{file}\"\nif [ -f \"$KG_FILE\" ]; then exit 0; fi\nmkdir -p \"#{folder}\"\ntouch \"$KG_FILE\"")
        File.write(script, content)
    end

end

Code Sample
NA
Version of Realm and Tooling
ProductName:	macOS
ProductVersion:	11.2.1
BuildVersion:	20D74
/Applications/Xcode.app/Contents/Developer
Xcode 12.4
Build version 12D4e
/usr/local/bin/pod
1.10.1
(not in use here)
/bin/bash
GNU bash, version 3.2.57(1)-release (arm64-apple-darwin20)
carthage not found
(not in use here)
/usr/bin/git
git version 2.24.3 (Apple Git-128)

I don't see Realm in the podfile. Was is added through some other means?

Sorry, it is added as other pod dependency like this s.dependency 'RealmSwift' Maybe it is important.

I found a similar issue which I did not spot at first.
https://github.com/realm/realm-cocoa/issues/7113

Hi @OneSman7 we will try to reproduce this and get back to you as soon as possible.

I have the same problem. The realm.h is missing,  and got the error
:0: error: unexpected input file: /Users /StorageManager.Swift
Command CompileSwiftSources failed with a nonzero exit code

Hi @Arrcuas can you please clean the pod cache and then try a clean pod install (pod deintegrate and then pod install). Also clean the project and derived data associated to it before building it again.

thank you diana, I solved the. problem the file was .Swift and not .swift..
this little mistake took me 2 hours of search xD
Am Di., 23. Feb. 2021 um 12:08 Uhr schrieb dianaafanador3 <
<EMAIL_ADDRESS>
Hi @Arrcuas https://github.com/Arrcuas can you please clean the pod
cache and then try a clean pod install (pod deintegrate and then pod
install). Also clean the project and derived data associated to it before
building it again.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/realm/realm-cocoa/issues/7119#issuecomment-784121821,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AS5E3ILMOZMVTC7MWY7KICDTAOEDXANCNFSM4XU7L2HA
.

Hey @Arrcuas I'm so sorry, i didn't notice the error, if you have any more issues, do not doubt to ask.

Copied from #7154
I did a bit of investigation and the realm.h header was introduced with realm-core 10.4.0 (https://github.com/realm/realm-cocoa/pull/7063), which was the version updated to in 10.5.2. The Headers subspec is including "include/**/Realm.h". I'm guessing that is doing a case insensitive match and pulling in the core header into the project incorrectly.
Does this need to use ** in the include path for these headers?

Hi @cltnschlosser thanks for the info, and taking the time to investigate this. We're checking why this warning is happening and any extra info is helpful.

I'm going to close this, in favour of https://github.com/realm/realm-cocoa/issues/7113
Duplicate of #7113


bug: Fix docker images, fetch wasmvm version from go.mod directly

Overview
Currently the wasmvm version is hardcoded.
Proposal
Similar to how osmosis builds the docker images: https://github.com/osmosis-labs/osmosis/blob/main/Dockerfile, fetch build the docker images with more dynamic wasmvm version

Fixed


Default value is wrong

As you can see in https://github.com/Azure/azure-cosmos-dotnet-v3/blob/master/Microsoft.Azure.Cosmos/src/ConnectionPolicy.cs the default value is 6 second.

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

ID: 17f88dfd-aa88-e817-8884-e2fd96c15110
Version Independent ID: 7dba7648-4f99-e9a0-0c13-bf258ce92510
Content: CosmosClientOptions.RequestTimeout Property (Microsoft.Azure.Cosmos) - Azure for .NET Developers
Content Source: xml/Microsoft.Azure.Cosmos/CosmosClientOptions.xml
Service: cosmos-db
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

This issue has been transferred to the repository where the Microsoft.Azure.Cosmos library is maintained as #4084.


Facade for plugins

Coverage increased (+0.09%) to 83.691% when pulling 473bb5e56ab6654626d6912f16064ea75e4cbf8c on add/facade-for-plugins into bb234cfdbcbcbd32851c6c7cd385e744db7d1a51 on master.

Coverage increased (+0.09%) to 83.691% when pulling 4b4ec2b9eddb97171e6e3f90c074a791ba470ab9 on add/facade-for-plugins into bb234cfdbcbcbd32851c6c7cd385e744db7d1a51 on master.

Coverage increased (+0.09%) to 83.691% when pulling 49a6e9122036169b8d786222762212a3bd401721 on add/facade-for-plugins into bb234cfdbcbcbd32851c6c7cd385e744db7d1a51 on master.

🆗

Coverage increased (+0.2%) to 83.784% when pulling 5281ba809d5cfe1e7ccf7b506782122a1da82913 on add/facade-for-plugins into bb234cfdbcbcbd32851c6c7cd385e744db7d1a51 on master.

Coverage increased (+0.2%) to 83.784% when pulling 5281ba809d5cfe1e7ccf7b506782122a1da82913 on add/facade-for-plugins into bb234cfdbcbcbd32851c6c7cd385e744db7d1a51 on master.

Coverage increased (+0.2%) to 83.784% when pulling 5281ba809d5cfe1e7ccf7b506782122a1da82913 on add/facade-for-plugins into bb234cfdbcbcbd32851c6c7cd385e744db7d1a51 on master.

Сосквошь коммиты
Проверь интеграционно, что ничего не сломал
Еще раз перепроверь добавленную функциональность

/ok

Coverage increased (+0.2%) to 83.784% when pulling 4642f4d6b5a79ff246c6307b783894731f9cc64f on add/facade-for-plugins into bb234cfdbcbcbd32851c6c7cd385e744db7d1a51 on master.

/cc @sipayRT @j0tunn @tormozz48 @rostik404
guys, I really need one more ok from one of you =)

/ok

Coverage increased (+0.2%) to 83.784% when pulling 3ff356636c7e6e3a8dfb67d6576eff738c7b3d5e on add/facade-for-plugins into bb234cfdbcbcbd32851c6c7cd385e744db7d1a51 on master.

Coverage increased (+0.09%) to 83.784% when pulling 9bf0cd12d914eb779cea748894fde69578fc62bc on add/facade-for-plugins into c970c52d1e80241ffa69cabe6df73c945d1113a5 on master.

guys, I really need one more ok from one of you

тебе @tormozz48 поставил :ok уже давно

оо точно, тогда завтра с утра еще раз все внимательно проверю, протестирую еще раз каждую опцию руками, сосквошу коммиты и прогоню интеграционно

Coverage increased (+0.09%) to 83.784% when pulling 1f20205834c2a87ba8324777bedeae7aab54cec4 on add/facade-for-plugins into c970c52d1e80241ffa69cabe6df73c945d1113a5 on master.

Coverage increased (+0.09%) to 83.784% when pulling 1f20205834c2a87ba8324777bedeae7aab54cec4 on add/facade-for-plugins into c970c52d1e80241ffa69cabe6df73c945d1113a5 on master.

Coverage increased (+0.09%) to 83.784% when pulling 1f20205834c2a87ba8324777bedeae7aab54cec4 on add/facade-for-plugins into c970c52d1e80241ffa69cabe6df73c945d1113a5 on master.

/cc @j0tunn @SevInf

Coverage increased (+0.1%) to 83.799% when pulling 1813a7a32616acc0a47f135c90913339840578fd on add/facade-for-plugins into c970c52d1e80241ffa69cabe6df73c945d1113a5 on master.

Coverage increased (+0.1%) to 83.799% when pulling 1813a7a32616acc0a47f135c90913339840578fd on add/facade-for-plugins into c970c52d1e80241ffa69cabe6df73c945d1113a5 on master.

Coverage increased (+0.1%) to 83.95% when pulling faec51b375abb550e13e17a90347d9eb6ca5877f on add/facade-for-plugins into 3eae59032adefcacb23a45a38222a33517ba54e4 on master.

/cc @j0tunn @sipayRT

Coverage increased (+0.1%) to 83.985% when pulling 9bc435dbed3f75c68bc26177309b9d1c134bdf33 on add/facade-for-plugins into 3eae59032adefcacb23a45a38222a33517ba54e4 on master.

Coverage increased (+0.1%) to 83.985% when pulling<PHONE_NUMBER>4823b0ffc36582509a487c13b179ae on add/facade-for-plugins into 3eae59032adefcacb23a45a38222a33517ba54e4 on master.

Coverage increased (+0.1%) to 83.985% when pulling<PHONE_NUMBER>4823b0ffc36582509a487c13b179ae on add/facade-for-plugins into 3eae59032adefcacb23a45a38222a33517ba54e4 on master.

Coverage increased (+0.1%) to 83.985% when pulling<PHONE_NUMBER>4823b0ffc36582509a487c13b179ae on add/facade-for-plugins into 3eae59032adefcacb23a45a38222a33517ba54e4 on master.

Coverage increased (+0.1%) to 83.985% when pulling<PHONE_NUMBER>4823b0ffc36582509a487c13b179ae on add/facade-for-plugins into 3eae59032adefcacb23a45a38222a33517ba54e4 on master.

/ok

/ok

Coverage increased (+0.1%) to 83.985% when pulling ab7ea60d747132ced7f39e783d91f4145b48c343 on add/facade-for-plugins into 712ce38b282e521f560c4281c0e9efd673fc5921 on master.

Coverage increased (+0.1%) to 83.985% when pulling ab7ea60d747132ced7f39e783d91f4145b48c343 on add/facade-for-plugins into 712ce38b282e521f560c4281c0e9efd673fc5921 on master.

Coverage increased (+0.1%) to 83.985% when pulling ceaea7f457ab6285e0dd754dfb518106d6ea3e80 on add/facade-for-plugins into 712ce38b282e521f560c4281c0e9efd673fc5921 on master.


Semantic versioning

I've been releasing these 0.7.N versions for years now. I suggest we rebrand the current version as 1.0 and start doing decent semantic versioning. How about that?

Hi! So, seems that 0.8 branch will never be merged into master ?
Speaking frankly, I'm very glad that 1.0 will be based on time-proven 0.7.x !
Cheers!

Yeah, that branch is outdated. It has proven hard to decided what 0.8 would actually include. There have been a bunch of breaking changes that we've considered implementing but never actually done it.
I've felt that when we include breaking changes, we should do it once and for good, so that we don't break people's code all the time. On the other hand, after 1.0 we can use semantic versioning properly so your app won't break randomly when breaking changes are introduced.
Up to the current version (0.7.94) we've kept Bacon.js very much backward-compatible and I think this could be version 1.0.

I've felt that when we include breaking changes, we should do it once and for good, so that we don't break people's code all the time.

One approach that other big JS projects (Node, React, Angular) have adopted is releasing new major versions on a regular, scheduled basis (about once a year for the projects I listed), but making each major version only introduce a few breaking changes.
The major advantage of this approach is that the migration instructions from one major version to another are minimal and don't require too much time/effort from the users. That makes it more likely that programmers will jump onto the new version, and then you don't have to face the major user issues that, for example, plagued the AngularJS 1 to Angular 2 change.

IMO, the next major Bacon.js may include some speed improvements from Kefir (or inspired by).
So, if one does remember node / io.js codebase split and latter merge that thing could be theoretically possible. )

Just released 1.0.0


Make background thread stoppable

Hi,
Current version of LevelDB has detached background thread that can't be stopped and each environment calls std::abort() in destructor.
This behavior prevents using of LevelDB in plugin dlls that can be started and stopped when main application still runs.
I think it is better to allow background thread to finish tasks in queue and then exit, when environment is being destroyed. That will make database loadable and unloadable.

Thank you for the clear explanation!
We may be willing to consider a PR that fixes this problem, depending on the complexity it introduces in the codebase.
If we end up not accepting the fix, you can still use it in your own codebase. LevelDB is designed to work with custom Env implementations. The ones supplied in the project are intended to be good enough for most cases, and can be used as starting points when you need to write your own.

Hi. Just wondering if this might make it work? We are using C api.
Use leveldb_create_default_env(); to create a default env. Then remove the environment with ```leveldb_env_destroy(leveldb_env_t*)`` which would correctly destroy the Env object?
And then this could be repeated?
The problem I see that could occur, is the BackgroundMainThread may close during operations? Like compaction?
Im still learning my way thought leveldb, so let me know if I have this all wrong.


Fix typo

a -> an

@changeworld : Thanks for your contribution! The author, @ggailey777, has been notified to review your proposed change.

Merging the typo fix.
@changeworld Thanks


Make the server stoppable

I got the following case: I run soundworks in an environment where I use test cases. I can start the server within this environment, but I haven't found an option to stop it, which leads to an endless running test which has to be force quit.
It would be nice to have a function exposed which offers the stop task of the server to provide a better interface from the outside. This could also be helpful, if soundworks is embedded as a sub service within a bigger installation.

Yes that's a good point, I think such functionality could also be very helpful for some client-side use cases.
To be honest, I won't dig into that with soundworks#v2, and I guess the quick and dirty way right now is to kill the process programmatically when your tests are done (i.e. using process.exit or process.kill).
However that's something which is definitely in the todo list for the v3, while I can't give any deadline for that as I first have to release this version properly. Also as soundworks clients and server are now (in v3) instances instead of POJO singletons it should be more easy to implement and much more consistent.
Let's keep this open as a reminder !

Yes, Mocha e.g. supports this with the --exit flag (if anyone else needs this), which is working for this.
This was also more an idea for v3. Thanks

Added await server.close() in v3.3.0 (Finally...)

Nice job @b-ma! Thanks for letting me know and keep up the good work


feat: upgrade the generate app to be Angular 12 #600

Thanks for the PR!
I saw that e2e tests were removed from the default CLI template, though I would prefer to keep it here as an option as this generator is oriented towards enterprise apps which needs e2e tests most of the time.
I'll merge this in the ng12 work branch in the meanwhile, so I can also have a look at why the tests are failing (probably related to e2e removal).

Protector e2e is removed from angular 12 version. That's why I removed it.

Yes, saw that. I'll use your PR as a basis to make it optional in the next release 🙂

ok, thanks, let me know how can I contribute more or do you have any other interesting angular project to contribute?


Make nitropy aware its running in a qube; have it prompt user for device reassignation after changing bootloader mode

As of today per current documentation:

QubesOS usb proxy deploys udev rules
When updating firmware, nk switch from normal to bootloader mode, bootloader mode to normal mode
When switching between modes, qubesos usage is not considered, and pynitrokey/nitropy (confusing) timeout

Desired:

nitropy detecting qubesos usage and prompting user to reassign dongle from qubes usb proxy widget from dom0 to qube where nitropy is called instead of doing a timeout

This is confusing mostly every not so technical users.
Example: https://matrix.to/#/!pAlHOfxQNPXOgFGTmo:matrix.org/$7gcke5HYUNvD2gX9xZJ3lMN3CUU5-1QAFmy0iri5WZ0?via=matrix.org&via=nitro.chat&via=envs.net

this is done in the new Version 2.3.1


Successfully pub/sub with mros2-esp32 using Seeed Studio XIAO ESP32S3

I tried mros2-esp32 on Seeed Studio XIAO ESP32S3, so I'll report on it. This is not an Issues report.
Verification requested by Seeed Studio.

Seeed Studio XIAO ESP32S3. ( ESP-IDF v5.4-dev-1832-g23e4823f17 )
NVIDIA Jetson Orin Nano Developer Kit. ( NVIDIA Jetpack 6.0 first production release / Ubuntu 22.04.4 LTS )
mros2-esp32 : Latest version as of August 2, 2024
mros2-host-examples : Latest version as of August 2, 2024
ROS 2 Humble Hawksbill

The communication log is attached.

Commands used in Seeed Studio XIAO ESP32S3

. $HOME/esp/esp-idf/export.sh
idf.py set-target esp32s3
idf.py menuconfig
idf.py build
sudo chmod 666 /dev/ttyACM0
idf.py -p /dev/ttyACM0 flash
idf.py -p /dev/ttyACM0 monitor

Seeed Studio XIAO ESP32S3 menuconfig settings

This is superb!! Could you also include XIAO ESP32S3 and XIAO ESP32C6 to the supported boards in the readme of this repo? Thank you so much!!!!

@meilily : Thank you for your message here. Unfortunately, I am not a contributor and cannot rewrite the Readme.
@takasehideki , @s-hosoai : Takase-san and Hosoai-san, I would appreciate it if you could consider this matter.

https://x.com/seeedstudio/status/1826175627063603496?s=46&t=4HGyVKsDUAlfHEv_mPnMUw

@meilily
The mros2-esp32 project has been listed in the top README!

Thank you so much!


MM-41266: Welcome message action frontend

Summary
This PR implements the frontend counterpart of #1036. Read the description of that PR for a bit of context.
Feel free to review this PR by commit. I've tried to make them self-explanatory, but here's some big-picture context:

The first 5 commits add/adapt external functions or components for the needs of the actions modal. Just some prep work.
The next 3 commits implement all the boilerplate regarding client functions, redux for the modal show/hide actions, and the needed types.
The actual work comes then in:

https://github.com/mattermost/mattermost-plugin-playbooks/commit/36b898415819c4dabeae5c450b88e6b8c2b452f4, that implements the modal component and all of its subcomponents (I've tried to keep components length at a minimum)
https://github.com/mattermost/mattermost-plugin-playbooks/commit/cc7113c9cb6578ca2ec2ae76e91b454ad5d385ee, that connects it all up registering the modal as a root component and registering the menu entry in the channel header menu to open it
https://github.com/mattermost/mattermost-plugin-playbooks/commit/a944fabc477105b1fcc2de04db46dff44a282eb5, that slightly changes the logic to process the CHANNEL_VIEWED websocket event for all channels that have a welcome message action enabled, instead that doing so only for playbook runs.

Although this branch is independent from #1036's branch, we should only merge it when that one's merged.
Ticket Link
https://mattermost.atlassian.net/browse/MM-41266
Checklist

[ ] Telemetry updated Covered by https://mattermost.atlassian.net/browse/MM-41801
[ ] Gated by experimental feature flag
[ ] Unit tests updated

Latest commits address feedback received during the Actions meeting. Namely:

Add a placeholder to the welcome message textbox. @justinegeffen, do you think the copy is good? See the first screenshot to see it in context, but the sentence is "Define a message to welcome users joining the channel".
Remove the chevron to expand/collapse the trigger body. Visible in all screenshots.
Preview the markdown for regular members, who cannot edit the message, leaving the textbox in edit mode by default for channel admins. See the screenshots in the table.

Placholder screenshot

Previewing for regular members

Channel admin
Regular member

@abhijit-singh, this is ready for review now :)

@gbochora, Shota is out, can you take a look at this PR instead? Thanks!

/update-branch


suggestion from user perspective: doc update on varData composite

Hey all, I had a particularly large string I was modelling, in the test dataset it was 750+ characters long and it was naturally failing using sample uint8 (255 length) varDataEncoding composite.
I wasn't sure why at first because my initial faulty thought was variable length data also meant unfixed length data as well, but of course reasoning through the composite definition and generated code you can get the true picture.
Could be a useful note in the docs for others who make a similar sort of mistake.

I've updated the samples to use uint16 to make cut and paste easier.
Do you think we should generate an error or truncate to the maximum size? I'm interested what others think to?

I vote document in the example and generate an error. I prefer to know
explicitly if my data "breaks" the model so to speak.
On Tuesday, February 23, 2016, Martin Thompson<EMAIL_ADDRESS>wrote:

I've updated the samples to use uint16 to make cut and paste easier.
Do you think we should generate an error or truncate to the maximum size?
I'm interested what others think to?
—
Reply to this email directly or view it on GitHub
https://github.com/real-logic/simple-binary-encoding/issues/333#issuecomment-187942520
.

--
Thanks,
-Andre

Generate an error, nothing more annoying than silent data corruption.

@tmontgomery Do you think the C++ should do a similar check?

C++ has a better option. Simply expose the length type in the put calls, I think.

The issues comes from encoding and not the reverse. If the size is > 255 and the type is uint8 then the memcpy will be for the wrong length.

I understand. The "put" methods on var data are for encoding. By making the length argument the same type as the schema VarDataEncoding length field, the compiler can warn/error on truncation.

Great.


Spelling correction

Suggest spellings based on Levenshtein distance. This includes a quick fix.
Some tweaks that are possible:

Don't suggest spellings from the global scope. The main value seems to be for the tests trying to do new number(), which probably doesn't happen much in the real world.
Only report 100 suggestions and stop afterwards. If your program has more than 100 unknown symbols, it's probably missing some libraries, not full of typos.
Lower the threshold slightly to 0.6 * source.length from 0.7 * source.length. This would prevent 2-character suggestions entirely (currently they can add one letter) and restrict 3-character suggestions to adding one letter (currently they can also substitute one letter).

Performance seems to be about the same based on timing jake runtests on a 2 Ghz CPU. If I add the 100-error cutoff or stop suggestions from global scope, then I think there won't be any concerns about performance anyway.
Fixes #15333

I added a 100-error cutoff for the spelling suggestions.

@RyanCavanaugh @DanielRosenwasser feel like looking at a whole bunch of spelling corrections?

Some of these are so off (e.g. Couldn't find any - did you mean NaN?), it might be adding an extra heuristic here. One I had in mind is that the two have to start with the same lower-cased letter.

Left some subjective comments
My overall impression is a case-insensitive edit distance of 2 (if the string is long enough - use a lower threshold for shorter strings) is probably where we should stop. The value-add here comes when you "can't see" the spelling error (fileName / filename, getColisions / getCollisions, setLength / setLenth, etc) and changes farther than 2 are much more likely to be "seeable".

All right, the suggestions are now much higher precision. Want to take another look?
I decided to fix #15565, too, instead of blacklisting String et al outright. Imagine all the people out there haplessly writing Sting and Nubmer.

Now that the spelling suggestions are in order, can I get a review of the implementation?

No, I didn't mean for it to be part of the API. I forgot about the public/private halves of the file. I'll move it to the private side.


PS: After switch bug

After switching from one particle system type to another the particles are not show correctly.
It is probably the best idea to rework the particle system in generell and reuse the system designed for asciimon.

Done with commit: c08333576f03ed54785e88765e368f67fdc073e2


Thoughts on syntax consistency across languages

I'm curious to your thoughts about consistency across languages in terms of common syntactic elements. For example, function definitions vim are not highlighted, but they are orange in ruby and go. Yet, internal vim function names are highlighted orange, but in go they are blue. This inconsistency would be easy to fix, but I'm curious if you are opposed to receiving PRs to improve this consistency or whether you don't agree in principle. Thanks!

I submitted #32 to fix.

As I've been trying to normalize the syntax highlighting across several languages, I'm torn on whether or not function invocations should be highlighted. What do you think? To give a concrete example, here is a screenshot of Go code normalized using your guidelines (as I have interpreted them):

And here is an alternate version where I experimented with highlighting function invocations and changing variable definitions to green to make them easy to spot:

I would be very appreciative of your opinion on the matter.

As a first step, I re-organized whole highlighting rules in b688907.
Because your changes and mine affect too wide range, I can't merge them...really sorry :cry:

After much thought, I carefully resolved conflicts and merged your changes (#32) to the latest files. In the process, I modified some definitions in terms of consistency:

jsDestructuringBlock should be highlighted as Normal (same as other variables)

jsFuncArgs, jsVariableDef should be highlighted as Normal (same as other languages)

jsTemplateExpression should be highlighted as Normal (because it should be highlighted as same as normal expressions)
// Example: `foo` should be highlighted as `Normal`
`${foo['bar']}`

Feel free to reopen the issue if there are any problems.

Ah I forgot to reply your suggestion, sorry...

From a legibility point of view, it makes it much easier to read code. The only problem is if I use cyan for this function invocation, then there is too much cyan, which require tweaking maybe the color of variable definitions to green perhaps as shown in the alternate version above.

As I said in this comment, at the moment, I think that current highlightings have enough readability so using less colors is better. But I am hesitating about which one is really good.

Feel free to reopen the issue or create new one if you find new inconsistencies.


Release pumphistory-merged.json IOB fix to master

As soon as we merge https://github.com/openaps/oref0/pull/555 to dev we'll also want to merge it to master and do a patch release.

Cherry-picked the #555 commit from dev to master instead.