Context menu location is incorrect

Microsoft PowerToys version
0.74.0
Installation method
GitHub, PowerToys auto-update
Running as admin
Yes
Area(s) with issue?
General
Steps to reproduce

Open any project with godot engine 4.1.1 ( I haven't checked other versions, but I think they are similar.)
Just right-click anywhere to open the context menu. Or click the menu dropdown at the top.

✔ Expected Behavior
A context menu will appear where you right-click before power toys 0.74.0 version.

❌ Actual Behavior
A context menu always appears at the top left of the program after power toys 0.74.0 version.

Other Software
Godot Engine v4.1.1 stable.mono.official

This has been fixed in 0.74.1. Please update PowerToys to the latest: https://github.com/microsoft/PowerToys/releases

This has been fixed in 0.74.1. Please update PowerToys to the latest: https://github.com/microsoft/PowerToys/releases

Thank you! I have confirmed that the issue has been resolved. Let's change it to closed status.

Yeah, I know that it is closed. And some apps did revert their behavior. But there are still a lot of those that didn't. How do I fix those? Asking for a lifehack.

Yeah, I know that it is closed. And some apps did revert their behavior. But there are still a lot of those that didn't. How do I fix those? Asking for a lifehack.

As a quick lifehack, you can turn off the Allow popup windows snapping option.
Which apps also cause this behavior?


udemy error

Hi Sir plz check some courses are downloading complete but mostly are giving error after one or two lecture download like this one and its free course you can enroll free with your udemy account
PS C:\Users\HDNLUF037.WIN-IPDLDV1QL5B> youtube-dl --verbose -u<EMAIL_ADDRESS>-p ***** -o '~/MyVideos/%(playli
st)s/%(chapter_number)s - %(chapter)s/%(title)s.%(ext)s' https://www.udemy.com/learn-chi-square-from-beginning-to-advanc
e-level/
[debug] System config: []
[debug] User config: []
[debug] Command-line args: ['--verbose', '-u', 'PRIVATE', '-p', 'PRIVATE', '-o', '~/MyVideos/%(playlist)s/%(chapter_numb
er)s - %(chapter)s/%(title)s.%(ext)s', 'https://www.udemy.com/learn-chi-square-from-beginning-to-advance-level/']
[debug] Encodings: locale cp1252, fs mbcs, out cp437, pref cp1252
[debug] youtube-dl version 2016.04.01
[debug] Python version 3.4.3 - Windows-2012Server-6.2.9200
[debug] exe versions: none
[debug] Proxy map: {}
[udemy:course] Downloading login popup
[udemy:course] Logging in as<EMAIL_ADDRESS>[udemy:course] learn-chi-square-from-beginning-to-advance-level: Downloading webpage
[udemy:course] 807950: Downloading course curriculum
[download] Downloading playlist: 807950
[udemy:course] playlist 807950: Collected 22 video ids (downloading 22 of them)
[download] Downloading video 1 of 22
[udemy] Downloading login popup
[udemy] 4859762: Downloading webpage
[udemy] 4859762: Downloading lecture JSON
[debug] Invoking downloader on 'https://udemy-assets-on-demand.udemy.com/2016-04-01_11-27-47-e11e54116a42f5c68aca2ce97bf
e03b8/WebHD.mp4?nva=20160401202304&token=0201605a909180da9102a'
[download] Destination: C:\Users\HDNLUF037.WIN-IPDLDV1QL5B\MyVideos\807950\NA - NA\Introduction to course.mp4
[download] 100% of 2.89MiB in 00:01
[download] Downloading video 2 of 22
[udemy] 4859868: Downloading webpage
[udemy] 4859868: Downloading lecture JSON
ERROR: Lecture 4859868 is not a video
Traceback (most recent call last):
File "C:\Python34\lib\site-packages\youtube_dl\YoutubeDL.py", line 669, in extract_info
ie_result = ie.extract(url)
File "C:\Python34\lib\site-packages\youtube_dl\extractor\common.py", line 323, in extract
return self._real_extract(url)
File "C:\Python34\lib\site-packages\youtube_dl\extractor\udemy.py", line 199, in _real_extract
'Lecture %s is not a video' % lecture_id, expected=True)
youtube_dl.utils.ExtractorError: Lecture 4859868 is not a video
PS C:\Users\HDNLUF037.WIN-IPDLDV1QL5B>

This issue is already fixed and fix will be incorporated in the next version of youtube-dl.

i updated latest version which you released today
PS C:\Users\vicky> youtube-dl --version
2016.04.01
PS C:\Users\vicky>

fix will be incorporated in the next version of youtube-dl.


Application Crashes using GPU to load.

Having issues with Dropbox, Splice, Playonmac and sometimes Adobe.
GPU: AMD Radeon 580x.

Hi @bennydf123 What OS are you using? Any other details you can provide? Could it be another program you have installed?

OS 14.3.1 The two programs which aren't working are dropbox and splice now. But it's certainly a GPU issue and I'm not sure how other programs could be affecting it when terminal boot shows that no other programs are interfering.

Did you remove the boot-args (agdpmod=pikera) I have in the EFI for the 5700xt?

I'll do that now. In the meantime here is the code for what I got in terminal
benmason@Bens-iMac ~ % /Applications/Splice.app/Contents/MacOS/Splice
[1164:0410/151307.034398:ERROR:crash_report_database_mac.mm(634)] open lock /Users/benmason/Library/Application Support/com.splice.Splice/Crashpad/pending/dc5db180-36e1-440f-a970-ac75c7d5bbc0.dmp: Resource temporarily unavailable (35)
15:13:07.074 [INFO] [pid=1164] ui-main - UI version: 5.0.11
15:13:07.301 [INFO] [pid=1164] ui-main - Connecting to bridge { port_range: [ 56765, 56785 ] }
15:13:07.531 [INFO] [pid=1164] ui-main - Initializing minimal LaunchDarkly client just for auth
sysctl: unknown oid 'sysctl.proc_translated'
15:13:07.741 [INFO] [pid=1164] ui-main - process arch x64
15:13:07.741 [INFO] [pid=1164] ui-main - machine arch x64
15:13:07.741 [INFO] [pid=1164] ui-main - feed url: https://api.splice.com/v2/desktop/darwin/stable/latest?v=5.0.11&architecture=x64
15:13:07.746 [ERROR] [pid=1164] ui-main - Attempting to read flag value before LaunchDarkly has been initialized
15:13:07.761 [INFO] [pid=1164] ui-main - initializing auth0 auth manager
15:13:07.761 [INFO] [pid=1164] ui-main - initializing offline auth manager
(node:1164) Warning: app.proto not found in any of the include paths /Applications/Splice.app/Contents/Resources/app.asar/managers/helper/../../../../../core/proto/
(Use Splice --trace-warnings ... to show where the warning was created)
server created on port 57766
15:13:07.778 [INFO] [pid=1164] ui-main - Splice Helper path: /Applications/Splice.app/Contents/Resources/Splice Helper.app/Contents/MacOS/Splice Helper from /Applications/Splice.app/Contents/Resources/app.asar/managers/helper
Loading Splice Connect module
Splice Connect Module loaded {
connectMethods: [
'startServer',
'setConnectEnabled',
'sendError',
'broadcastGenericMessage',
'triggerStatefulSubscriptions',
'loadSample',
'loadPreset',
'registerPreviousAssetHandler',
'registerNextAssetHandler',
'registerPurchaseAssetHandler',
'registerSessionHandler',
'registerDevicesHandler',
'registerClientConnectHandler',
'registerErrorHandler',
'registerGenericMessageHandler',
'assetPurchased'
]
}
15:13:07.807 [INFO] [pid=1164] ui-main - ConnectManager: initializeSpliceConnect() [Function (anonymous)]
15:13:07.808 [INFO] [pid=1164] ui-main - ConnectManager: Splice Connect SDK Server started
15:13:07.808 [INFO] [pid=1164] ui-main - Starting Splice Helper: "/Applications/Splice.app/Contents/Resources/Splice Helper.app/Contents/MacOS/Splice Helper" -pid 1164 -electronPort 57766
[1164:0410/151308.000249:ERROR:gpu_process_host.cc(962)] GPU process exited unexpectedly: exit_code=9
15:13:08.006 [INFO] [pid=1164] ui-main - VstManager Received Bridge version compatibility update. Is compatible: true
15:13:08.006 [ERROR] [pid=1164] ui-main - initVstConnection(): no port passed in and no saved port!
15:13:08.006 [INFO] [pid=1164] ui-main - UI not ready, enqueueing message...
This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
Error: ENOENT: no such file or directory, scandir '/var/folders/yq/khmf7sv53_56512yxkcdg5g80000gn/T/splice'
15:13:08.113 [INFO] [pid=1164] ui-main - ConnectManager: Splice Connect SDK SessionHandler {
assetType: 'preset',
deviceId: '',
instanceId: '',
state: 1,
doSearch: false
}
15:13:08.113 [INFO] [pid=1164] ui-main - UI not ready, enqueueing message...
15:13:08.113 [INFO] [pid=1164] ui-main - ConnectManager: Splice Connect SDK DevicesHandler { deviceIds: [] }
15:13:08.113 [INFO] [pid=1164] ui-main - UI not ready, enqueueing message...
15:13:08.113 [INFO] [pid=1164] ui-main - ConnectManager: Splice Connect SDK ClientConnectHandler { deviceId: '', instanceId: '', state: 3 }
15:13:08.113 [INFO] [pid=1164] ui-main - UI not ready, enqueueing message...
15:13:08.114 [INFO] [pid=1164] ui-main - Bridge gRPC server created on port 57765
[1164:0410/151308.115750:ERROR:network_service_instance_impl.cc(333)] Network service crashed, restarting service.
15:13:08.166 [INFO] [pid=1164] ui-main - VstManager Received Bridge version compatibility update. Is compatible: false
15:13:08.167 [INFO] [pid=1164] ui-main - UI not ready, enqueueing message...
15:13:08.200 [INFO] [pid=1174] core/main - Initializing client (ui_pid: 1164) (parent_pid: 1164) (build_version: 5.0.11)
15:13:08.200 [INFO] [pid=1174] core/main - Found DAW installation (location: /Applications/Logic Pro X.app) (bits: 64) (filehash: 65e439d37bed580d4d29d3d1980d97ef8e616c72) (name: Logic) (version: 10.7.6 (5754))
15:13:08.200 [INFO] [pid=1174] core/main - Found DAW installation (bits: 64) (filehash: 20aff28c547edcbc87db5b697ec157afccf9fc09) (name: Ableton Live) (version: 11.3.4 (2023-06-27_d83675ef81)) (location: /Applications/Ableton Live 11 Suite.app)
15:13:08.200 [INFO] [pid=1174] core/api-client - API client is configured (machine_id: 4B83F5E2-CF57AADA-ED557829-809EFEC7) (env: default)
15:13:08.201 [INFO] [pid=1174] core/server - Listening on (address: <IP_ADDRESS>:56765)
15:13:08.207 [INFO] [pid=1174] core/main - Helper sent start message to Electron (info: message:"Hello, 56765")
15:13:08.209 [INFO] [pid=1174] core/telemetry - Sending event to bus (action: Client opened) (props: map[])
15:13:08.209 [INFO] [pid=1174] core/main - Watching UI process for exit (parent_pid: 1164)
15:13:08.215 [INFO] [pid=1174] core/server - StreamEvents: stream starting (stream: &{0xc0002d8000})
15:13:08.217 [INFO] [pid=1164] ui-main - Connected to bridge { host: '<IP_ADDRESS>', port: 56765 }
15:13:08.217 [INFO] [pid=1164] ui-main - UI not ready, enqueueing message...
15:13:08.527 [INFO] [pid=1174] core/reachability - Network connected.
15:13:08.527 [WARN] [pid=1174] core/pubsub - Failed to start pubsub, user is not ready
15:13:08.527 [INFO] [pid=1164] ui-main - UI not ready, enqueueing message...
[1164:0410/151308.619897:ERROR:network_service_instance_impl.cc(333)] Network service crashed, restarting service.
info: [LaunchDarkly] LaunchDarkly client initialized
[1164:0410/151308.945173:ERROR:gpu_process_host.cc(962)] GPU process exited unexpectedly: exit_code=9
15:13:08.957 [INFO] [pid=1164] ui-main - Closing auth-only LaunchDarkly client
deactivating splice auth manager
15:13:09.156 [INFO] [pid=1164] ui-main - deactivating offline auth manager
15:13:09.157 [INFO] [pid=1164] ui-main - activating auth0 auth manager
15:13:09.157 [INFO] [pid=1164] ui-main - UI not ready, enqueueing message...
sysctl: unknown oid 'sysctl.proc_translated'
15:13:09.336 [INFO] [pid=1164] ui-main - User-Agent Splice Baelish/darwin/x64/x64 5.0.11/15d8d297/stable
[1164:0410/151309.338202:ERROR:network_service_instance_impl.cc(333)] Network service crashed, restarting service.
sysctl: unknown oid 'sysctl.proc_translated'
15:13:09.545 [INFO] [pid=1164] ui-main - Unable to retrieve access token from stored refresh token FetchError: request to https://auth.splice.com/oauth/token failed, reason: net::ERR_FAILED
at ClientRequest. (/Applications/Splice.app/Contents/Resources/app.asar/node_modules/electron-fetch/lib/index.js:1402:14)
at ClientRequest.emit (events.js:388:22)
at ClientRequest.emit (domain.js:470:12)
at ClientRequest._die (electron/js2c/browser_init.js:105:8391)
at SimpleURLLoaderWrapper. (electron/js2c/browser_init.js:105:7128)
at SimpleURLLoaderWrapper.emit (events.js:376:20)
at SimpleURLLoaderWrapper.emit (domain.js:470:12) {
type: 'system',
errno: 'ERR_FAILED',
code: 'ERR_FAILED'
}
15:13:09.546 [INFO] [pid=1164] ui-main - signin: signing in
(node:1164) electron: The default of nativeWindowOpen is deprecated and will be changing from false to true in Electron 15.  See https://github.com/electron/electron/issues/28511 for more information.
[1164:0410/151309.632840:ERROR:gpu_process_host.cc(962)] GPU process exited unexpectedly: exit_code=9
[1164:0410/151310.213194:ERROR:gpu_process_host.cc(962)] GPU process exited unexpectedly: exit_code=9
[1164:0410/151310.735081:ERROR:gpu_process_host.cc(962)] GPU process exited unexpectedly: exit_code=9
[1164:0410/151311.260198:ERROR:gpu_process_host.cc(962)] GPU process exited unexpectedly: exit_code=9
[1164:0410/151311.736570:ERROR:gpu_process_host.cc(962)] GPU process exited unexpectedly: exit_code=9
15:13:14.601 [INFO] [pid=1164] ui-main - Started auto-update check at 'https://api.splice.com/v2/desktop/darwin/stable/latest?v=5.0.11&architecture=x64' every 3600 sec.
15:13:14.612 [INFO] [pid=1164] ui-main - Checking for update.
[1164:0410/151314.615407:ERROR:network_service_instance_impl.cc(333)] Network service crashed, restarting service.
15:13:15.032 [INFO] [pid=1164] ui-main - Update available.
[1164:0410/151315.338167:ERROR:network_service_instance_impl.cc(333)] Network service crashed, restarting service.
[1164:0410/151315.481023:ERROR:gpu_process_host.cc(962)] GPU process exited unexpectedly: exit_code=9
[1164:0410/151315.767790:ERROR:network_service_instance_impl.cc(333)] Network service crashed, restarting service.
[1164:0410/151316.204263:ERROR:gpu_process_host.cc(962)] GPU process exited unexpectedly: exit_code=9
[1164:0410/151316.204298:FATAL:gpu_data_manager_impl_private.cc(414)] GPU process isn't usable. Goodbye.
zsh: illegal hardware instruction

Did you find a solution to the problem?

SOLVED!!
For this release for the hack to load up as is (without wifi solved in other threads in the post) add the following boot args. amfi=0x80 and ipc_control_port_options=0 which fixes any apps using Electron as a build (this promted the error message exit_code=9 and didn't engage hardware acceleration).


Unable to get release build from GitHub Actions.

Hi,
I've been having trouble getting an annotated tag pushed to my GitHub repo to produce a non -SNAPSHOT build.
To test it I've just cloned the https://github.com/jgitver/jgitver-github-actions repo as https://github.com/Yaytay/jgitver-github-actions/, then created an annotated tag and pushed it to GitHub.
The result was a SNAPSHOT version (https://github.com/Yaytay/jgitver-github-actions/runs/6441328564?check_suite_focus=true).
The first time may have been wrong because I pushed the tag twice (because I didn't have Actions enabled in GitHub on the first try) so I did it again: https://github.com/Yaytay/jgitver-github-actions/runs/6441347845?check_suite_focus=true
This time a tag of v2.0.2 led to a jgitver giving a version of v2.0.1!
Using a lightweight tag has the same effect as an annotated tag - tag v2.0.4 created version 2.0.4-SNAPSHOT despite "git describe" saying "v2.0.4".
What do I need to do to get jgitver to work nicely in GitHub Actions?
Thanks

@Yaytay looking at the git log of your builds it looks like execution occured without the tags

update the checkout action parameters so that it extracts tags & enough commits to find the tags.

Sorry I misunderstood your problem.
Hi, I reproduced on https://github.com/jgitver/jgitver-github-actions

new commit to add README.md
tag with lightweight tag v2.1 => 2.1.0-SNAPSHOT as expected
tag with annotated tag v2.2 => 2.2.0-SNAPSHOT this is not what occurs locally

This need further investigation.

Hi,
Were you able to dig into this further?
Thanks.

I have the same issue and this works for me:
steps:
    - uses: actions/checkout@v3
    - name: Checkout
      run: git fetch --depth=1 origin +refs/tags/*:refs/tags/*

I noticed that the checkout doesn't retrieve the tags as annotated but as lightweight
before:
     [echo] used version: 0.0.5-SNAPSHOT
     [echo] version calculated: 0.0.5-SNAPSHOT
     [echo] dirty: false
     [echo] head_committer_name: Pedro Lopes
     [echo] head_commiter_email<EMAIL_ADDRESS>     [echo] head_commit_datetime: Sat Jun 25 16:14:11 2022 +0100
     [echo] git_sha1_8: 4851d347
     [echo] branch_name:
     [echo] head_tags: 0.0.5
     [echo] head_annotated_tags:
     [echo] head_lightweight_tags: 0.0.5
     [echo] base_tag: 0.0.5
     [echo] all_tags: 0.0.5
     [echo] all_annotated_tags:
     [echo] all_lightweight_tags: 0.0.5
     [echo] all_version_tags: 0.0.5
     [echo] all_version_annotated_tags:
     [echo] all_version_lightweight_tags: 0.0.5

after the change:
     [echo] used version: 0.0.6
     [echo] version calculated: 0.0.6
     [echo] dirty: false
     [echo] head_committer_name: Pedro Lopes
     [echo] head_commiter_email<EMAIL_ADDRESS>     [echo] head_commit_datetime: Sat Jun 25 16:59:19 2022 +0100
     [echo] branch_name:
     [echo] head_tags: 0.0.6
     [echo] head_annotated_tags: 0.0.6
     [echo] head_lightweight_tags:
     [echo] base_tag: 0.0.6
     [echo] all_tags: 0.0.6,0.0.5
     [echo] all_annotated_tags: 0.0.6,0.0.5
     [echo] all_lightweight_tags:
     [echo] all_version_tags: 0.0.6,0.0.5
     [echo] all_version_annotated_tags: 0.0.6,0.0.5
     [echo] all_version_lightweight_tags:

Interestingly I've got one project where:
    - name: Checkout completely
      uses: actions/checkout@v3
      with:
        fetch-depth: 0

is sufficient, and another that needs:
    - name: Checkout completely
      uses: actions/checkout@v3
      with:
        fetch-depth: 0

    - name: Checkout with tags
      run: git fetch --depth=1 origin +refs/tags/*:refs/tags/*

I wonder whether we could get something added to actions/checkout to force the full download of tags?

Did one of you ask the question on the actions/checkout project ?

I haven't.

This problem is related with https://github.com/actions/checkout/issues/882
That why needs manually to do git fetch --tags --force origin  to JGitVer works correctly with annotated tags.

My workaround is
- name: Checkout
  uses: actions/checkout@v3
  with:
    # we don't know what commit the last tag was
    fetch-depth: 0
- run: git fetch --tags --force origin # WA: https://github.com/actions/checkout/issues/882


Lost connectivity on Reboot

I am testing dovesnap on a VM (Debian GNU/Linux 11 (bullseye)).
I followed the instructions on the readme page in the wiki and used the install script (install.sh) while having the $giturl be 'https://github.com/IQTLabs/dovesnap.git'.
Everything worked beautifully.
Here is info on the docker conatiners..
CONTAINER ID   IMAGE                               COMMAND                  CREATED         STATUS                   PORTS
      NAMES
90a5ada21202   busybox                             "sleep 1h"               5 minutes ago   Up 5 minutes
      testcon2
4806fe876f03   busybox                             "sleep 1h"               5 minutes ago   Up 5 minutes
      testcon
561f17afe562   iqtlabs/faucetconfrpc:v0.22.38      "faucetconfrpc_serve…"   4 hours ago     Up 4 hours (healthy)     <IP_ADDRESS>:59999->59999/tcp, :::59999->59999/tcp
      dovesnap-faucetconfrpc-1
31ee48114f1a   iqtlabs/dovesnap:v1.0.10            "/dovesnap --debug -…"   4 hours ago     Up 4 hours
      dovesnap-plugin-1
41dee2328f22   c65sdn/gauge:1.0.36                 "/usr/local/bin/entr"   4 hours ago     Up 4 hours               9302-9303/tcp, <IP_ADDRESS>:6654->6653/tcp, :::6654->6653//
tcp   dovesnap-gauge-1
d962983b7c78   iqtlabs/faucet-certstrap:v0.22.38   "sh gen_faucetconfrp"   4 hours ago     Exited (0) 4 hours ago
      dovesnap-faucet_certstrap-1
4d422c94d58d   c65sdn/faucet:1.0.36                "/usr/local/bin/entr…"   4 hours ago     Up 4 hours               <IP_ADDRESS>:6653->6653/tcp, :::6653->6653/tcp, 9302/tcp
      dovesnap-faucet-1
31f510496cd4   iqtlabs/openvswitch:v2.17.2         "/usr/bin/supervisor"   4 hours ago     Up 4 hours (healthy)
      dovesnap-ovs-1
------------------
REPOSITORY                 TAG        IMAGE ID                                                                  CREATED        SIZE
iqtlabs/faucet-certstrap   v0.22.38   sha256:3ce6613c2133c96501742ae33a639d523765f89f9adcb07c152af885097f8c1c   8 hours ago    11.9MB
iqtlabs/faucetconfrpc      v0.22.38   sha256:4081d8478679e11160cc13bcdfa888f1974dbf0f015c034b82954220995f7461   12 hours ago   606MB
c65sdn/gauge               1.0.36     sha256:ff176320d4ecfbc76567183d3b947cae4517406849175c89e126dfa0842b9698   3 weeks ago    96.3MB
c65sdn/faucet              1.0.36     sha256:e4c1b93df948421eea55fe6e02867ac990a5baf0964bd531cac26eecb434137b   3 weeks ago    96.3MB
iqtlabs/openvswitch        v2.17.2    sha256:1264140dc89ac33e4dbf18289aba9f0cde9b99980f96604b77eaab745cde2be2   3 weeks ago    536MB
iqtlabs/dovesnap           v1.0.10    sha256:a40581e370caaf40a47e9838767e735cb9bf2b1af60023142dde4817cea444f6   4 weeks ago    194MB
busybox                    latest     sha256:62aedd01bd8520c43d06b09f7a0f67ba9720bdc04631a8242c65ea995f3ecac8   5 weeks ago    1.24MB

It passed the ping test to the internet..
david@dovetest:~$ docker exec -t testcon ping -c3 <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>): 56 data bytes
64 bytes from <IP_ADDRESS>: seq=0 ttl=57 time=35.290 ms
64 bytes from <IP_ADDRESS>: seq=1 ttl=57 time=34.258 ms
64 bytes from <IP_ADDRESS>: seq=2 ttl=57 time=34.083 ms

And it could even ping another docker test container..
david@dovetest:~$ docker exec -t testcon ping -c3 testcon2
PING testcon2 (<IP_ADDRESS>): 56 data bytes
64 bytes from <IP_ADDRESS>: seq=0 ttl=64 time=1.144 ms
64 bytes from <IP_ADDRESS>: seq=1 ttl=64 time=0.064 ms
64 bytes from <IP_ADDRESS>: seq=2 ttl=64 time=0.165 ms

But on Reboot is when the problems occur. When I recreate the testcon containers, they are now unable to ping the internet or each other.
david@dovetest:~$ docker exec -t testcon ping -c3 <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>): 56 data bytes

--- <IP_ADDRESS> ping statistics ---
3 packets transmitted, 0 packets received, 100% packet loss
david@dovetest:~$ docker exec -t testcon ping -c3 testcon2
PING testcon2 (<IP_ADDRESS>): 56 data bytes

--- testcon2 ping statistics ---
3 packets transmitted, 0 packets received, 100% packet loss

In order to get it to work again, I have to remove the docker network 'mynet' and then add it back again. When I add the 'testcon' docker containers, they can now ping each other and the internet.
Not sure why connectivity is not surviving on a Reboot, maybe it is an 'iptables' issue.

Thanks very much for using dovesnap! It looks like there are two issues - the IP address for the OVS bridge is not restored after a reboot, and the accompanying NAT rule is not restored either. I will fix this. Thanks for the report.

I found some potential issues, around OVS not maintaining interface config over reboots, and released version 1.1.1.
Please would you try this version - but beforehand, please do both a "docker system prune" and a "docker volume prune" to ensure you have all the right versions.
If you still see the problem, please do a "docker exec -ti dovesnap_ovs_1 ovs-vsctl list-br" which will get you a bridge name, and then a "docker exec -ti dovesnap_ovs_1 ovs-ofctl dump-flows " and send me the results? "docker logs dovesnap_plugin_1" would be helpful also.

I have tested it with the previous scenario and everything is working very well.
I did notice a strange occurrence on a test that I did after a Reboot.

After the containers are created, 'faucet.yaml' shows :
dps:
  mynet:
    description: OVS Bridge odsbr33116
    dp_id: 1
    egress_pipeline: false
    hardware: Open vSwitch
    interfaces:
      1:
        acls_in: []
        description: /testcon 0f88e
        native_vlan: 100
      2:
        acls_in: []
        description: /testcon2 9c65b
        native_vlan: 100
      3:
        acls_in: []
        description: /maintest f9d6e
        native_vlan: 100
<PHONE_NUMBER>:
        acls_in: []
        description: OVS Port default gateway
        native_vlan: 100

After a Reboot and the (re)start of the docker container 'maintest' only.
docker start maintest
'faucet.yaml' now shows :
dps:
  mynet:
    description: OVS Bridge odsbr33116
    dp_id: 1
    egress_pipeline: false
    hardware: Open vSwitch
    interfaces:
      1:
        acls_in: []
        description: /maintest f9d6e
        native_vlan: 100
      2:
        acls_in: []
        description: /testcon2 9c65b
        native_vlan: 100
      3:
        acls_in: []
        description: /maintest f9d6e
        native_vlan: 100
<PHONE_NUMBER>:
        acls_in: []
        description: OVS Port default gateway
        native_vlan: 100

I noticed that 'maintest' now shows at port 1 & 3 in 'faucet.yaml'.
Even though it shows like this, the container is still able to ping external IPs. And when I add the 'testcon' containers, they overwrite positions 2 & 3 in 'faucet.yaml' but they still work.
I wanted to share my test results.

Thanks for testing! If you have time, would you be able to send me:
docker logs dovesnap_plugin_1
After reboot, but before start maintest.
Then, start maintest, and then:
docker logs dovesnap_plugin_1
again?

After reboot, but before start maintest.
time="2022-07-19T22:27:12Z" level=info msg="flag: debug: true"
time="2022-07-19T22:27:12Z" level=info msg="flag: default_ofcontrollers: "
time="2022-07-19T22:27:12Z" level=info msg="flag: faucetconfrpc_addr: faucetconfrpc"
time="2022-07-19T22:27:12Z" level=info msg="flag: faucetconfrpc_client: faucetconfrpc"
time="2022-07-19T22:27:12Z" level=info msg="flag: faucetconfrpc_connretries: 5"
time="2022-07-19T22:27:12Z" level=info msg="flag: faucetconfrpc_keydir: /faucetconfrpc"
time="2022-07-19T22:27:12Z" level=info msg="flag: faucetconfrpc_port: 59999"
time="2022-07-19T22:27:12Z" level=info msg="flag: mirror_bridge_in: "
time="2022-07-19T22:27:12Z" level=info msg="flag: mirror_bridge_out: "
time="2022-07-19T22:27:12Z" level=info msg="flag: stack_mirror_interface: "
time="2022-07-19T22:27:12Z" level=info msg="flag: stack_priority1: "
time="2022-07-19T22:27:12Z" level=info msg="flag: stacking_interfaces: "
time="2022-07-19T22:27:12Z" level=info msg="flag: status_auth_ips: <IP_ADDRESS>/8,::1/128"
time="2022-07-19T22:27:12Z" level=info msg="flag: status_port: 9401"
time="2022-07-19T22:27:12Z" level=info msg="flag: trace: false"
time="2022-07-19T22:27:12Z" level=info msg="Initializing dovesnap"
time="2022-07-19T22:27:12Z" level=debug msg="Stacking interfaces: []"
time="2022-07-19T22:27:12Z" level=debug msg="Docker Engine ID 2Y7Y:QJTK:3FB3:GS6Q:7OXF:UET7:HMI5:22NR:5VB2:Y74W:PVTV:JVT3:"
time="2022-07-19T22:27:12Z" level=debug msg="Certificates loaded"
time="2022-07-19T22:27:12Z" level=debug msg="Connecting to RPC server: faucetconfrpc:59999"
time="2022-07-19T22:27:12Z" level=debug msg="Connected to RPC server"
time="2022-07-19T22:27:12Z" level=info msg="Connected to open vswitch"
time="2022-07-19T22:27:12Z" level=warning msg="No stacking interface defined, not stacking DPs or creating a stacking bridge"
time="2022-07-19T22:27:12Z" level=info msg="restoring network {NetworkName:mynet BridgeName:odsbr9b903 BridgeDpid:0x1 BridgeDpidUint:1 BridgeVLAN:100 MTU:1500 PreAllocate"
time="2022-07-19T22:27:12Z" level=error msg="Bridge interface odsbr9b903 exists but is down, recreating network"
time="2022-07-19T22:27:12Z" level=debug msg="resourceManager() pending 0, received serial 1, {Operation:recreatedownbridge NewNetworkState:{NetworkName:mynet BridgeName:o"
time="2022-07-19T22:27:12Z" level=info msg="Deleting network ID 9b90396efbfce3d3e0159e91164fd5319c1bdf357895e0ec3f75e84af2b862b6 bridge "
time="2022-07-19T22:27:12Z" level=debug msg="FAILED: [--db=unix:/var/run/openvswitch/db.sock del-br ], ovs-vsctl: no bridge named \n"
time="2022-07-19T22:27:12Z" level=error msg="mustHandleDeleteNetwork failed: exit status 1"
time="2022-07-19T22:27:12Z" level=info msg="New Docker driver created"
time="2022-07-19T22:27:12Z" level=info msg="Getting ready to serve new Docker driver"
time="2022-07-19T22:27:12Z" level=debug msg="Fail to initialize firewalld: Failed to connect to D-Bus system bus: dial unix /var/run/dbus/system_bus_socket: connect: no s"
time="2022-07-19T22:27:12Z" level=debug msg="/usr/sbin/iptables, [--wait -I POSTROUTING -t nat -s <IP_ADDRESS>/16 -j MASQUERADE]"
time="2022-07-19T22:27:12Z" level=debug msg="/usr/sbin/iptables, [--wait -P FORWARD ACCEPT]"
time="2022-07-19T22:27:12Z" level=debug msg="network ID: 9b90396efbfce3d3e0159e91164fd5319c1bdf357895e0ec3f75e84af2b862b6"
time="2022-07-19T22:27:12Z" level=debug msg="existing ports on odsbr9b903: []"
time="2022-07-19T22:27:12Z" level=debug msg="setFaucetConfigFile {dps: {mynet: {dp_id: 1, description: OVS Bridge odsbr9b903, hardware: Open vSwitch, egress_pipeline: fal"
panic: sync: negative WaitGroup counter

goroutine 25 [running]:
sync.(*WaitGroup).Add(0xb09693?, 0x1?)
        /usr/local/go/src/sync/waitgroup.go:80 +0xda
sync.(*WaitGroup).Done(...)
        /usr/local/go/src/sync/waitgroup.go:105
dovesnap/ovs.mustHandleCreateNetwork.func1()
        /go/src/dovesnap/ovs/driver.go:555 +0x85
dovesnap/ovs.mustHandleCreateNetwork(_, {{0xb14e97, 0x12}, {{0xc00035bc70, 0x5}, {0xc00035bcf4, 0xa}, {0xc00035bcba, 0x3}, 0x1, ...}, ...})
        /go/src/dovesnap/ovs/driver.go:666 +0x1ce9
dovesnap/ovs.(*Driver).resourceManager(0xc000396780)
        /go/src/dovesnap/ovs/driver.go:1043 +0x825
created by dovesnap/ovs.NewDriver
        /go/src/dovesnap/ovs/driver.go:1257 +0x8ac
time="2022-07-19T22:27:12Z" level=info msg="flag: debug: true"
time="2022-07-19T22:27:12Z" level=info msg="flag: default_ofcontrollers: "
time="2022-07-19T22:27:12Z" level=info msg="flag: faucetconfrpc_addr: faucetconfrpc"
time="2022-07-19T22:27:12Z" level=info msg="flag: faucetconfrpc_client: faucetconfrpc"
time="2022-07-19T22:27:12Z" level=info msg="flag: faucetconfrpc_connretries: 5"
time="2022-07-19T22:27:12Z" level=info msg="flag: faucetconfrpc_keydir: /faucetconfrpc"
time="2022-07-19T22:27:12Z" level=info msg="flag: faucetconfrpc_port: 59999"
time="2022-07-19T22:27:12Z" level=info msg="flag: mirror_bridge_in: "
time="2022-07-19T22:27:12Z" level=info msg="flag: mirror_bridge_out: "
time="2022-07-19T22:27:12Z" level=info msg="flag: stack_mirror_interface: "
time="2022-07-19T22:27:12Z" level=info msg="flag: stack_priority1: "
time="2022-07-19T22:27:12Z" level=info msg="flag: stacking_interfaces: "
time="2022-07-19T22:27:12Z" level=info msg="flag: status_auth_ips: <IP_ADDRESS>/8,::1/128"
time="2022-07-19T22:27:12Z" level=info msg="flag: status_port: 9401"
time="2022-07-19T22:27:12Z" level=info msg="flag: trace: false"
time="2022-07-19T22:27:12Z" level=info msg="Initializing dovesnap"
time="2022-07-19T22:27:12Z" level=debug msg="Stacking interfaces: []"
time="2022-07-19T22:27:12Z" level=debug msg="Docker Engine ID 2Y7Y:QJTK:3FB3:GS6Q:7OXF:UET7:HMI5:22NR:5VB2:Y74W:PVTV:JVT3:"
time="2022-07-19T22:27:12Z" level=debug msg="Certificates loaded"
time="2022-07-19T22:27:12Z" level=debug msg="Connecting to RPC server: faucetconfrpc:59999"
time="2022-07-19T22:27:12Z" level=debug msg="Connected to RPC server"
time="2022-07-19T22:27:12Z" level=info msg="Connected to open vswitch"
time="2022-07-19T22:27:12Z" level=warning msg="No stacking interface defined, not stacking DPs or creating a stacking bridge"
time="2022-07-19T22:27:12Z" level=info msg="restoring network {NetworkName:mynet BridgeName:odsbr9b903 BridgeDpid:0x1 BridgeDpidUint:1 BridgeVLAN:100 MTU:1500 PreAllocate"
time="2022-07-19T22:27:12Z" level=debug msg="resourceManager() pending 0, received serial 1, {Operation:create NewNetworkState:{NetworkName:mynet BridgeName:odsbr9b903 Br"
time="2022-07-19T22:27:12Z" level=debug msg="network ID: 9b90396efbfce3d3e0159e91164fd5319c1bdf357895e0ec3f75e84af2b862b6"
time="2022-07-19T22:27:12Z" level=debug msg="existing ports on odsbr9b903: []"
time="2022-07-19T22:27:12Z" level=debug msg="setFaucetConfigFile {dps: {mynet: {dp_id: 1, description: OVS Bridge odsbr9b903, hardware: Open vSwitch, egress_pipeline: fal"
time="2022-07-19T22:27:12Z" level=debug msg="{NetworkState:{NetworkName:mynet BridgeName:odsbr9b903 BridgeDpid:0x1 BridgeDpidUint:1 BridgeVLAN:100 MTU:1500 PreAllocatePor"
time="2022-07-19T22:27:12Z" level=info msg="{\"Version\":1,\"Time\":1658269632,\"Msg\":{\"NetworkState\":{\"NetworkName\":\"mynet\",\"BridgeName\":\"odsbr9b903\",\"Bridge"
time="2022-07-19T22:27:12Z" level=debug msg="resourceManager() completed serial 1, {Operation:create NewNetworkState:{NetworkName:mynet BridgeName:odsbr9b903 BridgeDpid:0"
time="2022-07-19T22:27:12Z" level=info msg="New Docker driver created"
time="2022-07-19T22:27:12Z" level=info msg="Getting ready to serve new Docker driver"
time="2022-07-19T22:27:15Z" level=debug msg="new portDesc for odsbr9b903"
time="2022-07-19T22:29:46Z" level=debug msg="Get capabilities request"

Then, start maintest, and then:
time="2022-07-19T22:29:46Z" level=debug msg="Get capabilities request"
time="2022-07-19T22:40:57Z" level=debug msg="Create endpoint request: &{NetworkID:9b90396efbfce3d3e0159e91164fd5319c1bdf357895e0ec3f75e84af2b862b6 EndpointID:b4327f229f1b"
time="2022-07-19T22:40:57Z" level=debug msg="Create endpoint response: &{Interface:0xc000405ce0}"
time="2022-07-19T22:40:57Z" level=debug msg="resourceManager() pending 0, received serial 2, {Operation:reserveport NewNetworkState:{NetworkName: BridgeName: BridgeDpid: "
time="2022-07-19T22:40:57Z" level=debug msg="existing ports on odsbr9b903: []"
time="2022-07-19T22:40:57Z" level=debug msg="Join endpoint request &{NetworkID:9b90396efbfce3d3e0159e91164fd5319c1bdf357895e0ec3f75e84af2b862b6 EndpointID:b4327f229f1b16d"
time="2022-07-19T22:40:57Z" level=debug msg="Join endpoint response &{NetworkID:9b90396efbfce3d3e0159e91164fd5319c1bdf357895e0ec3f75e84af2b862b6 EndpointID:b4327f229f1b16"
time="2022-07-19T22:40:57Z" level=debug msg="resourceManager() completed serial 2, {Operation:reserveport NewNetworkState:{NetworkName: BridgeName: BridgeDpid: BridgeDpid"
time="2022-07-19T22:40:57Z" level=debug msg="resourceManager() pending 0, received serial 3, {Operation:join NewNetworkState:{NetworkName: BridgeName: BridgeDpid: BridgeD"
time="2022-07-19T22:40:57Z" level=debug msg="about to inspect b4327f229f1b16d32b436f2048b31ac158dbbcbd8737d93e55b97d3f836652b2 on {NetworkName:mynet BridgeName:odsbr9b903"
time="2022-07-19T22:40:57Z" level=debug msg="about to inspect network 9b90396efbfce3d3e0159e91164fd5319c1bdf357895e0ec3f75e84af2b862b6"
time="2022-07-19T22:40:57Z" level=debug msg="about to inspect container b4327f229f1b16d32b436f2048b31ac158dbbcbd8737d93e55b97d3f836652b2"
time="2022-07-19T22:40:57Z" level=debug msg="returned {ContainerJSONBase:0xc0002042c0 Mounts:[] Config:0xc000387a40 NetworkSettings:0xc00010e800}"
time="2022-07-19T22:40:57Z" level=info msg="Adding /maintest (pid 42600) MAC 12:40:fb:f3:51:9c on odsbr9b903 DPID 1 OFPort 1 to Faucet"
time="2022-07-19T22:40:57Z" level=debug msg="container network settings: &{IPAMConfig:<nil> Links:[] Aliases:[f5fa3ec57798] NetworkID:9b90396efbfce3d3e0159e91164fd5319c1b"
time="2022-07-19T22:40:57Z" level=debug msg="[]"
time="2022-07-19T22:40:57Z" level=debug msg="setFaucetConfigFile {dps: {mynet: {interfaces: {1: {description: /maintest f5fa3, native_vlan: 100, acls_in: []},}},}}"
time="2022-07-19T22:40:57Z" level=debug msg="{NetworkState:{NetworkName:mynet BridgeName:odsbr9b903 BridgeDpid:0x1 BridgeDpidUint:1 BridgeVLAN:100 MTU:1500 PreAllocatePor"
time="2022-07-19T22:40:57Z" level=info msg="{\"Version\":1,\"Time\":1658270457,\"Msg\":{\"NetworkState\":{\"NetworkName\":\"mynet\",\"BridgeName\":\"odsbr9b903\",\"Bridge"
time="2022-07-19T22:40:57Z" level=debug msg="resourceManager() completed serial 3, {Operation:join NewNetworkState:{NetworkName: BridgeName: BridgeDpid: BridgeDpidUint:0 "
time="2022-07-19T22:41:00Z" level=debug msg="portDesc for odsbr9b903 updated"

After creating this test, I am back to having the previous problem, where I can not ping an external IP.
david@dovetest:~$ docker exec -t maintest ping -c3 <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>): 56 data bytes

--- <IP_ADDRESS> ping statistics ---
3 packets transmitted, 0 packets received, 100% packet loss

I will check to see what is different from the previous test. I did do a 'git pull' as of 1 hour ago.

I apologize for the delay - I have been looking into some other issues. I will update you this week.

Update - we have upgraded to OVS 3, which has major updates to ovsdb handling. I'll test again now that this has been upgraded and released.


Training with images with no label

Dear team,
Thanks for your awesome work. I have been experimenting with my custom dataset, and I was wondering whether I can train with some images without boxes/labels. It throws a size mismatch error when concatenating tensors for creating refpoint_embed (in deformable_transformer.py) if an image with no label/ no box is concatenated. The reason for including images without labels/boxes is that there are some objects that can easily be mistaken for an object ( for example, blueberry muffin with chocolate muffin). So I want to give some images with chocolate muffin but without box/label so that the network can learn that. Would that be possible with DINO? If it's possible, how can I modify my target dataset without boxes/labels ?
Thank you!

#38
It should work out of the box with negative example images (those with no labeled bounding boxes in them). I was able to train with a 1:1 negative to positive imagery ratio. There is likely some issue with the imagery data you are using and not the fact that some imagery does not have labels within it.
"When there is no target in the current sample, DINO should have the ability to classify all targets as no obj, so there will be loss_cls that need to be backward. In the code, It can be seen that the authors have done a lot of clever detailings on this kind of samples to prevent this special case from raising errors in distributed mode."

Thanks for your comment! I keep getting an error in loss function here:
indices = self.matcher(outputs_without_aux, targets)
when calculating cost bbox here
cost_bbox = torch.cdist(out_bbox, tgt_bbox, p=1)

Is there specific input format required for negative samples? I was giving empty bbox (tensor with length 0) and empty label (also tensor with length 0 ) but it throws error like above.

Although I gave empty bboxes with shape (0,4) and labels with shape (0), it would throw an error in prepare_for_cdn function here.
known = [(torch.ones_like(t["labels"])).cuda() for t in targets]
batch_size = len(known)
known_num = [sum(k) for k in known]
if int(max(known_num)) == 0:

since known_num has length 0, it throws an error. Should I replace no label with background label index?


Change in behaviour with GrepperOperator

I've set up the following mappings, as suggested by the documentation:
nmap gs  <plug>(GrepperOperator)
xmap gs  <plug>(GrepperOperator)

Up to and including commit c244743 the behaviour when using those mappings is as outlined in the documentation. That is, the motion selection is used to populate the search prompt.
Beginning with commit 7640a44, the behaviour changes. The search query appears to be executed as soon as the mapping is used, bypassing the presentation of the search prompt to the user. This causes problems in my use case, where git grep is the default search tool. If I'm in a file that is not part of a git repo and I use those mappings, git grep is executed by default, and the search will always return zero results.
I'm running the latest nightly build of neovim, and haven't had the chance to see if the issue is present in vim as well.
Thanks for your help!

Oops, I refactored the code a bit and used the wrong default value in this case.
Thanks for reporting!

You're welcome, thanks for resolving it so quickly!


[DO-NOT-MERGE] will it work

What changes were proposed in this pull request?

Why are the changes needed?

Does this PR introduce any user-facing change?

How was this patch tested?

Was this patch authored or co-authored using generative AI tooling?

@WweiL mind filing a JIRA please?

Oops... thanks guys!


docs: add PD Scheduler config file

Signed-off-by: lilin90<EMAIL_ADDRESS>
What have you changed? (mandatory)
Add the document: PD Scheduler Configuration
Does this PR affect documentation (docs/docs-cn) update? (mandatory)
Relevant.
Does this PR affect tidb-ansible update? (mandatory)
No.

@rleungx @CaitinChen PTAL

@breeswish @CaitinChen PTAL

@lilin90  Thanks    @breeswish  PTAL

why delete docs/tikv-storage-configuration.md file

@Connor1996 Because it's a duplicated copy of docs/tikv-storage-config.md.


Add ability to change CWD behavior

I've been wanting script to "track" with whatever file I have open (may have multiple projects open). Basically, script's default behavior of using the first project directory as CWD was not meeting my needs. I found that there is interest in extending this capability from others as well (ref: #248, #543), so I decided to try my hand at it.
script gets a new setting for 'Default CWD Behavior' which is an enum with three string options:

First project directory - If there is a project directory open it uses the first path
Project directory of the script- Uses helper method to determine the project directory for the active editor (if there is one)
Directory of the script - This is my desired behavior which is to set CWD to the directory of the active editor

Note: For the config I wanted to use the enum options demonstrated in https://atom.io/docs/api/v1.6.0/Config:

config:
someSetting:
type: 'string'
default: 'foo'
enum: [
{value: 'foo', description: 'Foo mode. You want this.'}
{value: 'bar', description: 'Bar mode. Nobody wants that!'}
]

but for some reason, when I tried this, the items in the Settings' drop-down menu were blank/invisible (although they worked properly in terms of operation).

__Tested on Windows only!__

Thanks for the pr! I'll try to close view this on Monday

Heyo! I'm not sure what the state of this is - are you still interested @avonmoll? Is this looking good after the recent commits @nixel2007?

Hey, @rgbkrk
I think, it can be merged. One small sync function can't ruin the whole world.

Oh God, I've forgotten to merge this, sorry!

:ship: 3.11.0


Text 2 text

Change the API to accept Text() in the skipButtonText and doneButtonText.
That's what I needed, maybe someone else also needs it.

I'll fix the tests and submit again


react-hook-form upgrades

use <Controller/> when using custom component
Previously when we designed component we were using direct setValue to set value but since react-hook-form@v6 there's a better way to do this
as of now functionality will work just fine and due to time constraint this I'm keeping this as low priority but if anyone wants to take this up feel free to do it
Advantages

:sparkles: this will auto perform unregister event automatically when component is unmounted
No need to trigger validation manually

use <FormProvider/> with utility hooks to avoid passing form instance
This way we can avoid prop passing and each component can be very independent also this will avoid value setup gotchas and avoid react-gbus
Advantages

Performance improvement due to less complex code
No pub/sub necessary
Set any form control value from anywhere in form context
utilize watch method to avoid pub/sub wherever possible

References

https://react-hook-form.com/api#Controller
https://react-hook-form.com/migrate-v5-to-v6/
https://react-hook-form.com/api#useFormContext

Checklist

[x] textbox*
[x] datepicker*
[x] rich-textarea (quill)*
[x] phone-number*
[x] radio*
[ ] recaptcha*
[x] select-async*
[x] select*
[x] wkt-multi*
[x] icon-checkbox (species group, habitat picker)
[x] dropzone
[ ] group picker
[x] location + lat + lng

* marked ones are genric and is in src/components/form

Closing since components are migrated to take advantage of <Controller/> component wherever possible


Connection descriptor store is not shared across brokers

The MQTT spec calls for terminating existing clients with the same ClientID on CONNECT:
If the ClientId represents a Client already connected to the Server then the Server MUST disconnect the existing Client.

This is currently implemented using the ConnectionDescriptorStore however it's not shared between brokers so connection from a client to another broker within the cluster will violate this part of the spec.
We either need to decide to implement the spec correctly or document non-compliance so users can be aware.

@liangyepianzhou This will introduce more workload on the metadata server since the connection can create and close frequently. My opinion is to use one broker to handling the MQTT topic under a namespace, this means all the topics under a namespace are maintained by one broker, so we don't need to share something between MQTT brokers. So that we can guarantee client ID uniqueness under a namespace.

@codelipenghui this eliminates a large benefit of using Pulsar over a traditional broker which is high availability if this was to be enforced.
At the end of the day MQTT sessions are designed to be long lived. So for well behaved clients it shouldn't be a problem. Could always introduce QoS quotas for number of connection establishments if load on the metadata API is of concern.

Another problem with not sharing and/or storing the session is that the subscription info will be lost if the client connects to another broker or the broker restarts. This is particularly an issue when using cleanSession=0. This info could be stored in metadata store and fetched from a local cache for performance reason.

Another problem with not sharing and/or storing the session is that the subscription info will be lost if the client connects to another broker or the broker restarts. This is particularly an issue when using cleanSession=0. This info could be stored in metadata store and fetched from a local cache for performance reason.

Hi, we have supported this already.

@codelipenghui this eliminates a large benefit of using Pulsar over a traditional broker which is high availability if this was to be enforced.
At the end of the day MQTT sessions are designed to be long lived. So for well behaved clients it shouldn't be a problem. Could always introduce QoS quotas for number of connection establishments if load on the metadata API is of concern.

Hi @josephglanville
As merged #560 and #565, we have supported this in MoP cluster.


Per branch builds

I would like per branch (or per commit) builds to allow users not familiar with the command line node, npm etc... to be able to try out features and fixes before they get merged.
I suggest we switch CI environments to http://circleci.com because it can serve up build artifacts. This is similar to https://github.com/tmcw/docbox (see the demo docs https://67-53007065-gh.circle-artifacts.com/0/tmp/circle-artifacts.NCC9T6a/index.html#our-api)
I'm also open to other suggestions if anyone is aware of any other services/tools.
Does anybody have any thoughts on this?

I would like per branch (or per commit) builds to allow users not familiar with the command line node, npm etc... to be able to try out features and fixes before they get merged.

I think one could even be able to configure this in Travis.
I like CircleCI too. No opinions there.
BTW. I usually publish the files for new releases to https://github.com/maputnik/website so they are on the online version of Maputnik.

I looked to see if travis can serve up artifacts, but couldn't find that anywhere.

I looked to see if travis can serve up artifacts, but couldn't find that anywhere.

Oh you can. But you need a S3 bucket:
https://github.com/maputnik/desktop/blob/master/.travis.yml#L7-L10

We are most of the way there now, Circle CI builds to the artifacts directory and you can get a link via the artifacts for a particular build see https://circleci.com/gh/orangemug/editor/4#artifacts/containers/0 for an example.
We just need to enable circle CI on the main repo, as its currently only enabled on my fork (@lukasmartinelli you should have a request to for perms via github)
The next stage is posting that link to the pull request comments via the github API.

Hey @lukasmartinelli could you enable circleCI if you have the time. It would really help to quickly review pull requests like #161.

@orangemug no problem! Is there an issue out there for automating deployments with Travis? And, out of curiosity, is editor.openmaptiles.org pulling from the same source or is that updated separately?

@pjsier moving the convo from the other issue #164. So with the circleci (a slight hack but works great) we have per branch builds. See above
I would also like per tag builds to a the maputnik/website repo. The reason being that I always want a user to be able to revert to the previous version if we make a mistake. The number of devs on the project is quite small at the moment and I don't want non-developers to be stuck without a editor for days at a time.
I have no knowledge of editor.openmaptiles.org maybe @klokan knows???
Please feel free to raise a ticket for the auto deploy

CircleCI and hence per branch builds are now enabled. You need to be logged in to see the build. You can see an example at https://circleci.com/gh/maputnik/editor/1


Load credentials from secrets for Kinesis connectors

Motivation
Support loading awsCredentialPluginParam from secrets for kinesis connectors to avoid leaking of sensitive information with best efforts.
Modifications
Load kinesis configs with IOConfigUtils.loadWithSecrets().
Verifying this change
This change is already covered by existing tests and this PR also adds tests to confirm both loading credentials from plaintext config object and secrets work as expected.

@fantapsody thanks for your contribution. For this PR, do we need to update docs?


Pixart Homework

Level of Completeness: 5
Comfort Level: 4
This was much easier the 2nd time around.

Good work on this assignment :+1:  Let me know if you have any questions or comments for htis assignment.


Fixed #31936 -- Fixed __in lookup on key tranforms for JSONField.

This resolves an issue on databases without a native JSONField (MariaDB, MySQL, SQLite, Oracle), where values must be wrapped.
Thanks Sébastien Pattyn for the report.
ticket-31936

@sebastienpattyn93 Can you confirm that this patch fixes your issue?

buildbot, test on oracle.

buildbot, test on oracle.

@adamchainz Thanks :+1: Patch updated.

buildbot, test on oracle.


False Negative for Hibernate Validator CVE-2014-3558

False negative on library hibernate-validator-5.0.3.Final.jar - reported as cpe:/a:hibernate:hibernate_validator:5.0.3
<dependency>
   <groupId>org.hibernate</groupId>
   <artifactId>hibernate-validator</artifactId>
   <version>5.0.3.Final</version>
</dependency>

Should be reported as CVE-2014-3558.
Not sure though if the Vulnerable software and versions configuration at NVD is the issue.

This is an interesting false positive due to the data in the NVD entry. The only good solution I can think of is to parse the description to enhance the "x.x.x before x.x.x, x.x.x before x.x.x, ...". This is a somewhat common description so it may help make other CVEs more accurate.

The patches put in place resolve this issue. A longer term plan was opened as issue #646.  Again, thanks for pointing this issue out.


Friends

Closes #59
I expect an email as rc parameter.
I return string-array of all emails related to the email as a json object. If instead their entire accounts are supposed to be sent this can be easily fixed but it seems like sending too much information.
Maybe a test case should be written for this issue.
The user himself is included in the list of related emails maybe this isn't wanted.

This is sort of similar to finding friends of friends (a common graph problem):
USER -> FRIEND -> FRIEND

But with a change in relationships and node labels:
USER -> COLLECTION <- FRIEND

Notice that we only want the first level here, i.e. only users that are members of the same collections. We don't care about USER -> COLLECTION <- FRIEND -> COLLECTION <- FRIEND or longer chains...

I think there is a way to get the value directly. Look in User class in
Graph.java, should be something similar there
On 1 Dec 2016 17:32, "Drullan"<EMAIL_ADDRESS>wrote:

@Drullan commented on this pull request.
In src/main/java/se/lth/cs/connect/routes/Account.java
https://github.com/emenlu/connect/pull/60:

           		if(it.next().getId()==res2.get(j).getId()){

           			found=true;

           			break;

           		}

           	}

           	if(!found){

           		total.add(res2.get(j));

           	}

        	}

   	}

   	Iterator<GrNode> it = total.iterator();

   	String[] ret = new String[total.size()];

   	int i=0;

   	while(it.hasNext()){

   		ret[i]=it.next().getProperty("email").toString().split("= ")[1];

because apparently proptery.toString() replies property = "email" and I
only want the email. So i split it out.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/emenlu/connect/pull/60, or mute the thread
https://github.com/notifications/unsubscribe-auth/AFu5Wd07djBM2PsteKM1sQcrHq3j5y39ks5rDvaqgaJpZM4LAX5s
.

Current coverage is 17.05% (diff: 6.25%)

Merging #60 into master will decrease coverage by 19.36%

@@             master        #60   diff @@
==========================================
  Files            16         15     -1
  Lines          1057       1067    +10
  Methods           0          0
  Messages          0          0
  Branches        116        117     +1
==========================================
- Hits            385        182   -203
- Misses          623        874   +251
+ Partials         49         11    -38

Powered by Codecov. Last update 0d2356c...743e768


Fixed #26822: Don't keep database clones when using keepdb option if new migrations are non applied

When using --keepdb option, cloned databases created with --parallel option are not recreated or updated, which make them out-to-date as soon as we add a new migration in the project.
This patch forces the cloned databases to be recreated if they are out-to-date.
Second try after #6884 for issue https://code.djangoproject.com/ticket/26822

Wouldn't it be more appropriate to run migrate on these database instead of re-creating them?

@aaugustin A first try from one of our discussions at DjangoUnderTheHood! I tried to avoid touching any public API.
We were discussing about getting the result from the migrate command in db.backends.base.creation.BaseDataCreation.create_test_db, and pass it as a return value to be used in test.utils.setup_databases, on connection.creation.clone_test_db call.
This solution had 2 issues:

It's not possible to return a data structure, like a dict, from a management command,
We break the db.backends.base.creation.BaseDataCreation.create_test_db API, which is documented.

The one proposed is using some code used in showmigrations management command to detect if we need to rebuild the clones.
This is not the ideal solution, which would be to apply the missing migrations to the cloned databases (not sure it's trivial to achieve, as we don't have a connection on these cloned databases), but it's still better than the current situation imho.

That could be the ideal solution @charettes.
I'm just not sure how to deal with connections in these environments (what is exactly _nodb_connection for mysql/postgresql, can I use it to migrate? Should I initialize a new connection in sqlite3 context?).
And I just realized that I was checking the unapplied migrations from self.connection, but the default connection will always have them applied at that point...

@romgar, are you still working on this PR? Is this still something we'd like to go forward with?

@LuRsT I don't have time to work on it anymore, sorry...

Closing due to inactivity.


[feature request] TV & EPG Support

Kore is an awesome controller for Kodi, thanks to all contributors for their efforts!
It would be nice, if TV (with EPG) would also be supported among Music, TV Series, Music and Applications.

I don't have PVR/TV hardware to use with Kodi, so someone else will need to do this...

:( is there someone among the devs who could do it? Or maybe there is a way to setup some dummy PVR thingy?
Would donating a USB DVB-T receiver to you be an option?

Thanks for the offer, but i don't think that would be a good option.
I guess that sooner or later, someone will come along and add support for it.

ok, I hope you're right ;)

Being taken care of.

Is this still being taken cared of? It's been a while.

included in 2.0.0 ... awesome! thank you!


gurobi version

Hello,
Thank you for developing such a nice tool. I wonder if it is possible to run it with Gurobi version 10? Currently, it is throwing an error.
Best

I changed the gurobipy version and it is working.
Best


Twap: Make timeDelta for calculation in miliseconds

Background
Currently all of our time deltas in the TWAP code cast time durations to their integer representations, which is in nanoseconds.
Having nanoseconds precision is very unnecessary as Tendermint forces every block time to be at least 1ms since the last, and because this costs us in precision for the Arithmetic accumulator, which we have to think about.
I suggest we make a helper method in types, for taking the difference of two times, and then rounding to the nearest milisecond, and then dividing by 10**6.
This will help save us on precision, as we start working towards overflow handling in the TWAP logic, and thinking about max spot price precisions.
Acceptance Criteria

[ ] Implementation of previously mentioned

Hi @ValarDragon can we achieve this by doing something simple like this;
x/gamm/twap/types/utils.go

func SpotPriceTimesDuration(sp sdk.Dec, timeDelta time.Duration) sdk.Dec {
	deltaMilliSecond := timeDelta.Milliseconds()
	return sp.MulInt64(int64(deltaMilliSecond))
}

func AccumDiffDivDuration(accumDiff sdk.Dec, timeDelta time.Duration) sdk.Dec {
	deltaMilliSecond := timeDelta.Milliseconds()
	return accumDiff.QuoInt64(int64(deltaMilliSecond))
}


Ability to process multiple files at the same time

Is there any way to use this tool on a bunch of files at the same time?

Using a loop to iterate through files and call the utility for each file is redundant as it loads the weights again for each file.
Creating a LaughRemover Object and using the remove_laughs method solves issue 1 but it's still inefficient as it feeds a single audio sample to the model at each time step.

A way to process multiple files at the same time via batching and possibly a package might be a great help for data science projects that need to process whole dataests.

Added PR. I have only fixed issue 1 mentioned above, I have to work on the second point by implementing the padding.
While working on this, also had two issues:

Because of the dependence on soundfile, which depends on libsndfile, , mp3 files can't be loaded. See this.
Why does the laugh_remover function return rc? I have left the return statement in the PR I submitted but I don't see it being used anywhere where the function is called.

Why does the laugh_remover function return rc? I have left the return statement in the PR I submitted but I don't see it being used anywhere where the function is called.

Probably just leftover. Feel free to put up a PR to remove it.

Padding

I think let's close this as you've implemented a great first iteration. If you want open a second issue to track (2)


Drop nncp ctlplane routes

These ctlplane routes were originally added as part of [1], and since then they required various adjustment due to one or the other issues. It was pointed out these routes shouldn't be needed for the use case it was originally added for, so let's drop these.
[1] https://github.com/openstack-k8s-operators/install_yamls/pull/481
Related-Issue: OSPRH-6307

Both baremetal and non-baremetal job works fine


Update Links for LXP Packs

The LXP packs under requirements only include 9B and 9C, not 10 or 11 ( as described here: https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/language-packs-known-issue ) for Oct and Nov cumulative updates respectively. Also, the article doesn't do a great job explaining difference between FODs, LXPs, Language Packs...etc. It is unclear if they are all needed, or how to grab the latest LXP for yourself ( Say in this case where the documentation is unable to be updated constantly with new, fresh links for new LXPs)

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

ID: a8d3194d-974c-f014-cd0a-6ec611952281
Version Independent ID: 52951f02-174b-a688-bca0-4f93cc6f7e8b
Content: Install language packs on Windows 10 VMs in Windows Virtual Desktop - Azure
Content Source: articles/virtual-desktop/language-packs.md
Service: virtual-desktop
GitHub Login: @Heidilohr
Microsoft Alias: helohr

Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

This article was updated with additional LXPs recently, so this issue is no longer relevant. #please-close


Improvements

Hi Sebastian,
As promised in #5, here is a revised PR. This time, I separated it into 3 commits:

The first commit contains the refactoring to using strum and strum_macros.
The second commit contains the additional filter using a blacklist of product ids (currently only one).
The last one, adds the MX 10.0N related stuff (just an additional const and the README.md change).

Cheers
-Fritz

hey Fritz!
Indeed I didn't got alerted for the PR, will enable notifications now, so thx for the mail.
PR looks good and cleans up the enum portion quite a bit.
Will create the table in the repo and then link to it instead of the issue being the origin of that information.


rsocket-js can not work in browser

rsocket-js can not work in borwser

Expected Behavior

Actual Behavior

Steps to Reproduce

import { RSocketClient } from 'rsocket-core';
import RSocketWebsocketClient from 'rsocket-websocket-client';

async function createClient(options) {
  const client = new RSocketClient({
    setup: {
      dataMimeType: 'text/plain',
      keepAlive: 1000000, // avoid sending during test
      lifetime: 100000,
      metadataMimeType: 'text/plain',
    },
    transport: new RSocketWebsocketClient({
      host: options.host,
      port: options.port,
    }),
  });

  return client.connect();
}

async function run() {
  const rsocket = await createClient({
    host: '<IP_ADDRESS>',
    port: 9898,
  });
//....
}

await run();

Possible Solution

Your Environment

RSocket version(s) used:
Other relevant libraries versions (eg. netty, ...):
Platform (eg. JVM version (javar -version) or Node version (node --version)):
OS and version (eg uname -a):

Hi @sudongyuer ,
Can you provide any more details about what build tooling/versions you are working with? For instance, are you using Webpack, Browserify, or something else?
I was able to create a minimal proof of concept using the current version of rsocket-js (0.0.27) + create-react-app (which uses webpack) without issue, so I suspect that this issue may be relative to the build tooling you are using, or the environment you are developing in.
Working example with CRA, for reference: https://github.com/viglucci/rsocket-js-examples/tree/main/examples/create-react-app

i use vite 2.6.4 , vue3.2.16

Thanks for your reply, i think you should remove  hasBufferModule code, because i saw so many issue about this problem,and i remove hasBufferModule code, it works(so many project use vite), user don't need to care about this problem, makes it works is very improtant

Thanks for the additional information. I don't use Vue much, and haven't used Vite at all, so I'll need to look a bit more into this to see what the best solution could be.

OK peace and love🥶

@sudongyuer I was able to get this working in Vite by providing configuration a polyfill for buffer using feross/buffer.
npm i buffer

// vite.config.js

import { defineConfig } from 'vite'
import vue from '@vitejs/plugin-vue'

// https://vitejs.dev/config/
export default defineConfig({
  resolve: {
    fallback: {
      'buffer': require.resolve('buffer/')
      // ^--- provide buffer polyfill
    }
  },
  plugins: [
    vue()
  ]
})

{
  "name": "my-vue-app",
  "version": "0.0.0",
  "scripts": {
    "dev": "vite",
    "build": "vite build",
    "serve": "vite preview"
  },
  "dependencies": {
    "buffer": "^6.0.3",
    "rsocket-core": "0.0.27",
    "rsocket-websocket-client": "0.0.27",
    "vue": "^3.2.16"
  },
  "devDependencies": {
    "@vitejs/plugin-vue": "^1.9.3",
    "vite": "^2.6.4"
  }
}

Can you please give this a try in your project and let us know  how it works for you?

A full working example can be found here: https://github.com/viglucci/rsocket-js-examples/tree/main/examples/vite-vue

Thanks very much～It works ,but i think it's not the best way to resolve it,should resolve it in this libary,what do you think about

Thanks for confirming the workaround.
For a long-term fix: we are working on a pretty substantial rewrite in #158, where we are also looking to improve compatibility in browser environments. Because of that, and the available workaround, I don't think there will be much need or appetite to address this in the current version.
I think I would recommend closing #196 in favor of our planned improvements in #158 .


TypeSpec: .NET JSON serialization/deserialization for enums -- add generation of a custom converter?

When defining an enum type in TypeSpec, e.g.
enum Foo {
  first,
  second
}

The C# emitter generates a nice "enum-like class" that looks something like (partial):
public partial readonly struct Foo : IEquatable<Foo>
{
    private readonly string _value;

    public Foo(string value)
    {
        _value = value ?? throw new ArgumentNullException(nameof(value));
    }
    ...
    public static Foo First { get; } = new Foo(...);
    public static Foo Second { get; } = new Foo(...);
    ...
    public override string ToString() => _value;
}

Older versions of .NET don't automatically support System.Json.Text.Serialization capabilities for non-property / private fields, so calling System.Json.Text.Serialization.JsonSerializer.Serialize(new Foo("hello")) will not serialize the value string as intended. And subsequent deserialization will of course not be able to reflect the original object.
I think it's fairly easy to address this, fortunately. If the emitter can first create a customer converter (FooConverter.cs):
internal class FooConverter : JsonConverter<Foo>
{
    public override Foo Read(ref Utf8JsonReader reader, Type _, JsonSerializerOptions __) => new Foo(reader.GetString());
    public override void Write(Utf8JsonWriter writer, Foo value, JsonSerializerOptions _) => writer.WriteStringValue(value.ToString());
}

...and then the generated enum-like struct/class is attributed:
[JsonConverter(typeof(FooConverter))]
public partial readonly struct Foo: IEquatable<Foo>
{
...

...then I think everything ends up happy. This is possible now for emitter consumers via doing the above in custom code, but it'd be nice if were auto-generated.

Cross-link to progenitor report: https://github.com/Azure/azure-sdk-for-net/issues/35963

FYI the public serialization is an ongoing feature developing in Azure.Core, here is a PR for it: https://github.com/Azure/azure-sdk-for-net/pull/35946
Once this is finalized, we will update our SDK to make sure every model in the SDK will implement the new Azure.IJsonSerializable which allows you to write a generic converter (we may or may not provide a factory method to do that - this is not discussed yet)
But nevertheless, I believe this public serialization feature will solve this issue and currently we should not do anything until the public serialization is ready.

Related feature request: https://github.com/Azure/azure-sdk-for-net/issues/16977


Revert "[WFLY-17153] Remove warning message WFLYWELD0052 in hibernate quickstart"

This can be reverted. In the module jakarta.security.enterprise.api it is already reverted

Thanks @Skyllarr and @jasondlee


Privacy Badger Blocking Site to load

Prequisite :
User have Privacy Badger Plugin Installed
Expected :
Site load without error
Current result:

Solving:
Disabling privacy badger enabled the sites,
but the errors should tells user to turn off instead to re-login

I can add a warning but in no way can I detect if privacy badger is installed. I had this issue myself and it's annoying but there is nothing I can do due to how browser plugins work.


docker log is full of FutureWarnings

Hi guys,
I sometimes check the logs of my docker container (for example why it is taking so long for my home-assistant instance to start 😛).
It provides a little more info than just the errors in the log overview of HA itself.
The FutureWarning messages also don't show in the HA logs, so it is not a big deal, but I was just wondering if you have seen the warnings and this is just to keep the deprecation of these language features on the radar.
In my log I see the following:
2020-04-15 15:03:33 INFO (MainThread) [homeassistant.components.websocket_api.http.connection.1826167664] Connection closed by client
/usr/local/lib/python3.7/site-packages/Plugwise_Smile/Smile.py:303: FutureWarning: The behavior of this method will change in future versions. Use specific 'len(elem)' or 'elem is not None' test instead.
  if data.find(locator):
/usr/local/lib/python3.7/site-packages/Plugwise_Smile/Smile.py:383: FutureWarning: The behavior of this method will change in future versions. Use specific 'len(elem)' or 'elem is not None' test instead.
  elif appliance.find(".//actuator_functionalities/thermostat_functionality"):
2020-04-15 15:03:47 INFO (MainThread) [custom_components.plugwise-beta.climate] Updating climate...
/usr/local/lib/python3.7/site-packages/Plugwise_Smile/Smile.py:303: FutureWarning: The behavior of this method will change in future versions. Use specific 'len(elem)' or 'elem is not None' test instead.
  if data.find(locator):
/usr/local/lib/python3.7/site-packages/Plugwise_Smile/Smile.py:383: FutureWarning: The behavior of this method will change in future versions. Use specific 'len(elem)' or 'elem is not None' test instead.
  elif appliance.find(".//actuator_functionalities/thermostat_functionality"):
2020-04-15 15:04:49 INFO (MainThread) [custom_components.plugwise-beta.climate] Updating climate...
/usr/local/lib/python3.7/site-packages/Plugwise_Smile/Smile.py:303: FutureWarning: The behavior of this method will change in future versions. Use specific 'len(elem)' or 'elem is not None' test instead.
  if data.find(locator):
/usr/local/lib/python3.7/site-packages/Plugwise_Smile/Smile.py:383: FutureWarning: The behavior of this method will change in future versions. Use specific 'len(elem)' or 'elem is not None' test instead.
  elif appliance.find(".//actuator_functionalities/thermostat_functionality"):
2020-04-15 15:05:50 INFO (MainThread) [custom_components.plugwise-beta.climate] Updating climate...
/usr/local/lib/python3.7/site-packages/Plugwise_Smile/Smile.py:303: FutureWarning: The behavior of this method will change in future versions. Use specific 'len(elem)' or 'elem is not None' test instead.
  if data.find(locator):
/usr/local/lib/python3.7/site-packages/Plugwise_Smile/Smile.py:383: FutureWarning: The behavior of this method will change in future versions. Use specific 'len(elem)' or 'elem is not None' test instead.
  elif appliance.find(".//actuator_functionalities/thermostat_functionality"):
2020-04-15 15:06:50 INFO (MainThread) [custom_components.plugwise-beta.climate] Updating climate...
/usr/local/lib/python3.7/site-packages/Plugwise_Smile/Smile.py:303: FutureWarning: The behavior of this method will change in future versions. Use specific 'len(elem)' or 'elem is not None' test instead.
  if data.find(locator):
/usr/local/lib/python3.7/site-packages/Plugwise_Smile/Smile.py:383: FutureWarning: The behavior of this method will change in future versions. Use specific 'len(elem)' or 'elem is not None' test instead.
  elif appliance.find(".//actuator_functionalities/thermostat_functionality"):
2020-04-15 15:07:51 INFO (MainThread) [custom_components.plugwise-beta.climate] Updating climate...
/usr/local/lib/python3.7/site-packages/Plugwise_Smile/Smile.py:303: FutureWarning: The behavior of this method will change in future versions. Use specific 'len(elem)' or 'elem is not None' test instead.
  if data.find(locator):
/usr/local/lib/python3.7/site-packages/Plugwise_Smile/Smile.py:383: FutureWarning: The behavior of this method will change in future versions. Use specific 'len(elem)' or 'elem is not None' test instead.
  elif appliance.find(".//actuator_functionalities/thermostat_functionality"):
2020-04-15 15:08:52 INFO (MainThread) [custom_components.plugwise-beta.climate] Updating climate...

Every time the component updates the data, the warning is triggered.
The python version in my docker container is: 3.7.7
Again, this has no priority whatsoever, but just to put this on the list 😉.
Keep up the great work!

@wburgers note there is still some work in progress by @bouwew so 0.1.23 should be available soon-ish with one of the next plugwise-beta releases


Set the data retention for all GA properties to the max (14 months)

Need
We want to be able to see year-over-year trends. Let's make sure all properties and all environments are set to keep the data for as long as possible which is 14 months for the free version.
https://support.google.com/analytics/answer/7667196?hl=en
Approach

Enumerate all sites with a list of checkboxes below
Set the data retention for each site.

Properties

[x] AnVIL Portal

[x] Prod
[x] Staging

[x] AnVIL Catalog

[x] Prod
[x] Staging

[x] AnVIL DX

[x] Prod
[x] Staging

[x] NCPI Catalog

[x] Prod
[x] Staging

[x] HCA Portal + DX

[x] Prod
[x] Staging

[x] Lungmap DX

[x] Prod
[x] Staging

@MillenniumFalconMechanic @NoopDog Done!


Curifactory --store-full runs may not grab all artifacts if they are previously cached

Describe the bug
Curifactory does not appear to store previously cached artifacts if --store-full is run on an experiment a second time with overwrite specified for one more more stages. Instead only the artifacts from the overwritten stages appear to make it into the store-full folder.
To Reproduce
Steps to reproduce the behavior:

Run a --store-full run of curifactory for an experiment
Overwrite one stage of the experiment and run --store-full again
Observe that not all artifacts are included in the second store full run folder

Expected behavior
I would expect all artifacts needed to reproduce the run to be included in the store full folder to be included unless otherwise excluded specifically by the user.

Closing, this turned out to be a separate issue where a cacher inside a stage was using a get_path with a default track=True and returning that path to a stage-level FileRefCacher that had track=False


Stake delegation system tests

Having top-ups implemented we need to execute system tests covering all possible stake delegation scenarios.
Depending on the progress on #1898, tests should be performed using KEEP token dashboard or directly against smart contracts.

[x] Grantee can delegate a stake
[x] Managed grantee can delegate a stake
[x] Owner of liquid tokens can delegate a stake
[x] Stake delegation can be canceled within the initialization period by a grantee directly on the staking contract, tokens are deposited to the escrow
[x] Stake delegation can be canceled within the initialization period by a managed grantee directly on the staking contract, tokens are deposited to the escrow
[x] Stake delegation can be canceled within the initialization period by an operator directly on the staking contract, tokens are returned to the owner's account
[x] Stake can be undelegated by grantee directly on the staking contract
[x] Stake can be undelegated by a managed grantee directly on the staking contract
[x] Stake can be undelegated by liquid tokens owner directly on the staking contract
[x] Tokens staked from the grant are deposited in the escrow after recovering them from the delegation
[x] Staked, liquid tokens are sent back to the owner after recovering them from the delegation
[x] Tokens can be withdrawn from escrow according to grant's unlocking schedule:

[x] permissive staking policy
[x] adaptive staking policy

[x] It is possible to top-up existing delegation from tokens deposited in the escrow
[x] It is possible to top-up existing delegation from tokens from a grant
[x] It is possible to top-up existing delegation from tokens from a managed grant
[x] It is possible to top-up existing delegation from liquid tokens
[x] It is possible to top-up delegation initiated from escrow with tokens from a grant
[x] It is not possible to delegate from grant to already used operator whose stake has been canceled
[x] It is not possible to redelegate from the escrow to already used operator whose stake has been canceled
[x] Tokens deposited in the escrow can be redelegated to a new operator
[x] Stake redelegated from the escrow can be canceled
[x] Tokens deposited in the escrow from a redelegated stake can be withdrawn
[x] Stake from liquid tokens can be transferred to new staking contract with a bridge:

[x] with payback
[x] without payback

[x] Stake from a grant can be transferred to new staking contract with a bridge

[x] with payback
[x] without payback

[x] Stake from a managed grant can be transferred to new staking contract with a bridge

[x] with payback
[x] without payback

(more...)

Scripts executed during testing are located in: https://github.com/keep-network/local-setup/tree/wip-test-staking-bridge/e2e/wip/staking


API: CategoricalIndex for value_counts

Closes https://github.com/pydata/pandas/issues/10704
Changes Categorical.value_counts to return
a Series with a CategoricalIndex. Previously
the Series and an Index.
Just some random observations on the convenience of working with categoricals:
The code here could be simplified if

Categorical.categories was always a Categoricalndex
We were consistent about whether NaN is allowed in .categories

I thought that 1. would be a good idea, but I'm going back on it now. I can see how it'd be useful for Categorical.categories to be a more specific type like DatetimeIndex. For 2, I'd personally I'll always keep NaN out of my categories, but I could be missing a use case where it's needed.

Categorical.categories was always a Categoricalndex

This seems slightly redundant to me. Both the categorical and the categorical index would hold an array of codes, and the categorical index would hold on to a normal index as its categories anyways.

For 2, I'd personally I'll always keep NaN out of my categories, but I could be missing a use case where it's needed

Agreed.

Categorical.categories was always a Categoricalndex

I would rather say: is never a CategoricalIndex. As the index should reflect the dtype of the categories, which is never a Categorical?

BTW, why would you want a CategoricalIndex (as the categories)? Is there a specific use case you have in mind where you need it?

BTW, why would you want a CategoricalIndex

I was wanting to reindex the Series of counts with all the categories to include the zero counts, counts.reindex(self.categories).

I wasn't really able to simplify the code at all. I need that cat_idx to get from keys that are present(non-zero count) and from there to all categories.

Thanks to Jeff, the change is much simpler now.

lgtm.


JSON Comments (JSON 5)

Describe the feature in as much detail as possible.
Simple, it would be great if this project would support JSON 5 (https://json5.org/), which has both comment support and doesn't choke on trailing commas.

Duplicate of https://github.com/nlohmann/json/issues/348. Please see also https://github.com/nlohmann/json#comments-in-json.


Prepare for release with Boost 1.86

Seeing that the last Boost release with changes in GIL was Boost 1.80.0 in August 2022 and seeing that some fixes and features have landed on the develop branch during that time, it is probably a good time to perform the next true merge of develop into master to prepare for the next release of GIL / Boost.
Steps:

[x]  Merge (@mloskot?)
[x]  Build locally before git push (optional, because the CI should catch any errors)
[x]  Push
[x]  Review CI status
[x]  Collect release notes to RELEASES.md (see #749)
[x]  Copy release notes to https://github.com/boostorg/website/ (https://github.com/boostorg/website/pull/844)

Changes
Below is an initial log of commits that will get merged from current develop into master for release with Boost 1.86 (as of 30 June 2024):
git log origin/master..develop --reverse --pretty=format:" | %cs | [%h](http://github.com/boostorg/gil/commit/%H) | %s |" | nl | sed -E 's/^\s/\|/g'

#
Date
Hash
Subject

1
2022-08-10
8465d5463
ci: partially replace Ubuntu 18.04 on GHA with Ubuntu 20.04 (#716)

2
2022-08-12
1f89d622e
ci: replace macOS 10.15 with macOS 11 in CI pipelines (#717)

3
2022-10-05
135edcfad
docs: Support newer version of Sphinx (#719)

4
2022-10-06
3f7daa99b
docs: Fix HTML syntax

5
2022-11-14
1df8c2407
ci: Update actions/checkout in GitHub Actions workflows to v3 (#720)

6
2023-02-07
712b827ed
fix: Convolution in convolve_2d (#723)

7
2023-02-07
d6e67f38c
fix: Normalize Gaussian 2D kernel. (#725)

8
2023-02-21
8f4cdcbcc
fix: Fixed custom color converter in dynamic_factory and added corresponding (#726)

9
2023-02-22
ecea33a90
fix: Make locator.hpp self contained (#729)

10
2023-03-16
eabd679f6
fix: Documentation (#731)

11
2023-10-01
e24c87fde
ci: ubuntu-18.04 environment is deprecated (#738)

12
2023-12-25
3a4d45443
ci: update actions/checkout in GitHub Actions workflows to v4 (#739)

13
2023-12-25
822c19ee7
ci: fix Python package in coverage workflow (#740)

14
2024-01-27
322c4e2e1
Updated Boost.Filesystem usage. (#741)

15
2024-04-18
2c3ee866b
Portable minmax Win32-API workaround #744 (#745)

16
2024-05-10
4fec872fe
feat: Guard boost::filesystem usage (#743)

17
2024-05-13
abb561a22
fix: Wrong buffer size in path string conversion functions (#746)

18
2024-05-17
481b6e7c1
feat: add tell() and error() functions to istream + ostream devices (#747)

(If this looks familiar, then because it was shamelessly copied from #667, the issue for the Boost 1.80 release.)
Timeline
According to the calender on https://www.boost.org/community/index.html the following dates are relevant for the release:

Date
Subject
Description

2024-06-24
Boost 1.86.0 closed for new libraries and breaking changes
Release branch is closed for new libraries and breaking changes to existing libraries. Still open for bug fixes and other routine changes to all libraries without release manager review.

2024-07-03
Boost 1.86.0 closed for major changes
Release closed for major code changes. Still open for serious problem fixes and docs changes without release manager review.

2024-07-10
Boost 1.86.0 closed for beta
Release closed for all changes

2024-07-17
Boost 1.86.0 beta
Beta posted for download.

2024-07-18
Boost 1.86.0 open for bug fixes
Release open for bug fixes and documentation updates. Other changes by permission of a release manager.

2024-08-07
Boost 1.86.0 closed
Release closed for all changes

2024-08-14
Boost 1.86.0 release
Release posted for download.

We are already past the first date in that list, but a first glance at the commit list above shows no obvious breaking changes, so it probably is still fine. There are still a few days left before the beta is closed for major changes, so we should still be able to get the changes from develop in right in time before the beta.

Preparing for merge
git switch develop
cd libs/gil
../../b2 cxxstd=14 test

All tests passed.

Merge
$ git merge --no-ff develop
Merge made by the 'ort' strategy.
 .azure-pipelines.yml                                             | 71 -----------------------------------------------------------------------
 .ci/azure-pipelines/steps-check-cmake.yml                        |  9 ---------
 .ci/azure-pipelines/steps-cmake-build-and-test.yml               | 51 ---------------------------------------------------
 .ci/azure-pipelines/steps-install-boost.yml                      | 41 -----------------------------------------
 .ci/azure-pipelines/steps-install-conan.yml                      | 17 -----------------
 .ci/azure-pipelines/steps-install-gcc.yml                        | 18 ------------------
 .github/workflows/ci.yml                                         | 48 +++++++++++++++++++++++++++++++-----------------
 .github/workflows/coverage.yml                                   |  5 ++---
 .github/workflows/docs.yaml                                      |  2 +-
 CMakeLists.txt                                                   | 26 ++++++++++++++++++++++----
 README.md                                                        |  8 ++++----
 RELEASES.md                                                      | 23 +++++++++++++++++++++++
 doc/_static/boost.css                                            | 19 +++++++++++++++++++
 doc/_templates/layout.html                                       |  3 +++
 doc/design/dynamic_image.rst                                     |  6 +++---
 doc/io.rst                                                       |  6 ++++--
 include/boost/gil/detail/math.hpp                                |  2 +-
 include/boost/gil/extension/dynamic_image/image_view_factory.hpp | 20 ++++++--------------
 include/boost/gil/extension/histogram/std.hpp                    |  4 ++--
 include/boost/gil/extension/io/tiff/detail/read.hpp              |  6 +++---
 include/boost/gil/histogram.hpp                                  | 12 ++++++------
 include/boost/gil/image_processing/convolve.hpp                  |  2 +-
 include/boost/gil/image_processing/histogram_equalization.hpp    |  8 ++++----
 include/boost/gil/image_processing/histogram_matching.hpp        |  8 ++++----
 include/boost/gil/image_processing/numeric.hpp                   | 15 ++++++++++-----
 include/boost/gil/io/device.hpp                                  | 33 ++++++++++++++++++++++++++++++++-
 include/boost/gil/io/path_spec.hpp                               | 23 +++++++++++++++--------
 test/core/image_processing/convolve_2d.cpp                       | 93 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 test/core/image_processing/simple_kernels.cpp                    | 17 ++++++++++-------
 test/extension/dynamic_image/image_view_factory.cpp              | 67 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 test/extension/io/png/png_file_format_test.cpp                   |  6 +++---
 31 files changed, 369 insertions(+), 300 deletions(-)
 delete mode 100644 .azure-pipelines.yml
 delete mode 100644 .ci/azure-pipelines/steps-check-cmake.yml
 delete mode 100644 .ci/azure-pipelines/steps-cmake-build-and-test.yml
 delete mode 100644 .ci/azure-pipelines/steps-install-boost.yml
 delete mode 100644 .ci/azure-pipelines/steps-install-conan.yml
 delete mode 100644 .ci/azure-pipelines/steps-install-gcc.yml

Merge of develop to master pushed.
/cc @striezel @sdebionne

Thank you.
The merge happened before the beta is closed, so people will have the chance to test these changes when the beta is posted for download. :)
By the way, the CI on the master branch passed, so I marked the task "Review CI status" as done.

I think this issue has been complete, hasn't it? And, thanks to your priceless help @striezel, we are good to be released with Boost 1.86, aren't we?
https://github.com/boostorg/gil/milestones/Boost 1.86 still lists numerous open PR-s/issues but those are drafts or unfinished work, so those will be moved to another milestone.

I think that I also have some open PRs / drafts which are older than 1-2 years.
I will have a look at them and close them if I think they will be never finished.

@marco-langer We all have unfinished projects out there, so please don't worry about closing any of your PR-s. If we keep them open, that may catch an eye of a contributor who would be interested to pick up and continue any unfinished work.

I think this issue has been complete, hasn't it? And, thanks to your priceless help @striezel, we are good to be released with Boost 1.86, aren't we?

Yes, the issue is completed and GIL bsically is in a good shape for the release of Boost 1.86.0. I'll close the issue.

https://github.com/boostorg/gil/milestones/Boost 1.86 still lists numerous open PR-s/issues but those are drafts or unfinished work, so those will be moved to another milestone.

Maybe. The Boost 1.86.0 beta is closed for changes (in my timezone it's already 2024-07-10) and will be posted for download next week.
However, there will still be a few weeks time after that for bugfixes and documentation changes. Maybe some of the issues of that milestone will get fixed during that time. In that case another true merge from develop to master branch would be required. For example, I still would like to get the changes from #751 into Boost 1.86.0, because there are some awkward typos in there. :laughing:

My apologies for no reaction, summer holidays period is not the best time for attending releases.

 I think all the important stuff (that is, bugfixes and features) got merged in time before the 1.86 release. And for the rest there's always the next release.


type inference algorithm confused by wrong code

When compiled with elm-reactor (0.18), the following incorrect code crashes the compiler:
type alias Name =
  { first : String }

something : List a -> a
something data =
  Name "n/a"

Output:
elm-make: It looks like something went wrong with the type inference algorithm.

Unable to generalize a type variable. It is not unranked.

Please create a minimal example that triggers this problem and report it to
<https://github.com/elm-lang/elm-compiler/issues>
elm-make: thread blocked indefinitely in an MVar operation

With the development branch I am seeing:
-- TYPE MISMATCH ------------------------------------------------------ temp.elm

Something is off with the body of the `something` definition:

6|   Name "n/a"
     ^^^^^^^^^^
This `Name` call produces:

    Name

But the type annotation on `something` says it should be:

    a

So it should be fixed in the next release. Thanks for the report!


Add Support for Emulating Pre-Populated Volumes

Could we update this section to include a way to emulate volume pre-populating? While we cannot pre-populate volumes the way Docker Linux containers can, we can emulate that stage by using a temporary container. I've written up a detailed description here but, basically, we run a temp container that mounts both the file with the files we want copied into the volume and the volume. In the temp container, we copy the contents of the folder into the equivalent folder for the volume in the container. Now, the volume has been populated and can be attached to other containers in the future.

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

ID: 2b8233b4-c7d6-111a-9bb1-5dae2da7a96c
Version Independent ID: b4674f08-a39e-2b28-291f-0331744d66df
Content: Persistent storage in containers
Content Source: virtualization/windowscontainers/manage-containers/persistent-storage.md
Service: windows-server
Sub-service: windows-containers
GitHub Login: @cwilhit
Microsoft Alias: lizross

We hugely appreciate your contribution, feedback, and support to our technical documentation.
We’ve phased out GitHub Issues on this repository as the feedback mechanism for content and have replaced it with a new feedback system. For more information see, Content User Feedback. As part of this rollout, we are migrating your issue where our team will use your comments to improve the documentation experience. Unfortunately, this does mean you won't be able to access this issue after the migration is complete.
All issues will be migrated by Thursday 29th August 2024.
Once again, thank you for your valuable feedback, we hope you’ll continue to contribute using our new feedback system.


JSON/JSONB Support

Do you support Postgre's JSON/JSONB data type?

Hey there @psykomo. We've identified one issue with working with JSON/B where the compatibility tests don't pass.
There's also some awkwardness since we treat JSON as a string. We're planning to add a new null.Bytes and null.JSON type to our null package so that we have much better support for this, and the null.JSON type will have marshal/unmarshal helpers just to make it nice.
Other than the types being correct, what else were you thinking in terms of support for this data type?

A typical use case would be to specify a custom type to be used as the unmarshal target.

@mackross So, we have a new set of JSON types that are correct now in the dev branch.
In my current line of thinking your use case is not possible, at least not without some custom type abilities which we currently lack.
We now use proper JSON types in the dev branch, and support easy marshal/unmarshal operations via helpers:
https://github.com/vattle/sqlboiler/blob/a86e794b617b1e5566ae9394b62c404107b378a0/boil/types/json.go#L20
This looks like as much functionality we'll get for the meantime until we hear enough asks for a custom type system.

Hi @mackross and @psykomo -- we've released V2 which includes the JSON types you've requested. See here for release notes: https://github.com/vattle/sqlboiler/releases/tag/v2.0.0
Thanks.


vscode-extensions.github.vscode-pull-request-github: switch to stable version

Description of changes
Similar to https://github.com/NixOS/nixpkgs/pull/221446, except in this case the extension immediately doesn't work because it requires an insider version of VS Code. This changes it to the latest release from https://github.com/microsoft/vscode-pull-request-github/releases.
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

[x] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 223943 run on x86_64-linux 1

1 package built:

vscode-extensions.github.vscode-pull-request-github


Conflict types

I have remark version 15.0.1, and remarkIns version 1.1.0. I can't get rid of the error below, except by using any.
I will be grateful if you help.
async function renderToHtml(markdown: string): Promise {
const out = await remark()
.use(html, { sanitize: true })
.use(gfm)
.use(remarkIns) <-- error
.process(markdown);
return String(out);
}
Error:
No overload matches this call.
Overload 1 of 3, '(preset?: Preset | null | undefined): Processor<Root, undefined, undefined, Root, string>', gave the following error.
Type 'Plugin<void[], Root>' has no properties in common with type 'Preset'.
Overload 2 of 3, '(list: PluggableList): Processor<Root, undefined, undefined, Root, string>', gave the following error.
Argument of type 'Plugin<void[], Root>' is not assignable to parameter of type 'PluggableList'.
Overload 3 of 3, '(plugin: Plugin<[], Root, Root>, ...parameters: [] | [boolean]): Processor<Root, Root, Root, Root, string>', gave the following error.
Argument of type 'Plugin<void[], Root>' is not assignable to parameter of type 'Plugin<[], Root, Root>'.
The 'this' types of each signature are incompatible.
Type 'Processor<undefined, undefined, undefined, undefined, undefined>' is not assignable to type 'Processor<void, Root, void, void>'.
Types of property 'use' are incompatible.
Type '{ <Parameters_1 extends unknown[] = [], Input extends string | Node | undefined = undefined, Output = Input>(preset?: Preset | null | undefined): Processor<undefined, undefined, undefined, undefined, undefined>; <Parameters_1 extends unknown[] = [], Input extends string | Node | undefined = undefined, Output = Input...' is not assignable to type '{ <PluginParameters extends any[] = any[], Input = Root, Output = Input>(plugin: Plugin<PluginParameters, Input, Output>, ...settings: [boolean] | PluginParameters): UsePlugin<...>; <PluginParameters extends any[] = any[], Input = Root, Output = Input>(tuple: [...] | [...]): UsePlugin<...>; (presetOrList: Preset | P...'.
Types of parameters 'preset' and 'plugin' are incompatible.
Type 'Plugin<any, any, any>' has no properties in common with type 'Preset'.ts(2769)

Thanks for reporting the issue.
May I request you to try remark version 14.0.3, if you report no problem with it, I will deep into remark version 15.0.1, which changes effect the remark-ins.


feat: allow javascript_include_tag options to vite_client_tag

Description 📖
This allows passing options such as nonce, which some browsers require if CSP is set (Firefox).
Background 📜
With CSP set in Rails, Firefox would fail to load the vite client tag without a nonce set.
The Fix 🔨
vite_client_tag now accepts an options hash that is passed to javascript_include_tag, much like vite_javascript_tag.
Co-authored-by: Wil Hall<EMAIL_ADDRESS>

Thanks Mikey and Wil!


from master on Sept 25

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

advocates/aaron-schlesinger.yml
:white_check_mark:Succeeded
View

advocates/bryan-hughes.yml
:white_check_mark:Succeeded
View

advocates/cecil-phillip.yml
:white_check_mark:Succeeded
View

advocates/media/profiles/aaron-schlesinger.png
:white_check_mark:Succeeded
View

advocates/media/profiles/bernd-verst.png
:white_check_mark:Succeeded
View

advocates/media/profiles/bryan-hughes.jpg
:white_check_mark:Succeeded
View

advocates/media/profiles/mike-james.png
:white_check_mark:Succeeded
View

advocates/media/profiles/paul-decarlo.png
:white_check_mark:Succeeded
View

advocates/mike-james.yml
:white_check_mark:Succeeded
View

advocates/paul-decarlo.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Add full support for H615B

Can only power on / off through Home Assistant. Brightness / colour control unavailable.
Full control available through the Govee app and through Google Home.

I added a pull request for the H615 strips of different lengths which were missing (B/C/D) in #51

Thanks! Merged