Got blocked when running default geonmaes track.

I got blocked when running default geonmaes track at "index-append".
I duplicated the geonames track directory and modify the data-url to local path. Here is the track.
[root@VM_0_106_centos logs]# esrally list tracks --track-path=~/.rally/benchmarks/tracks/my/geonames

    ____        ____
   / __ \____ _/ / /_  __
  / /_/ / __ `/ / / / / /
 / _, _/ /_/ / / / /_/ /
/_/ |_|\__,_/_/_/\__, /
                /____/

Available tracks:

Name      Description         Documents    Compressed Size    Uncompressed Size    Default Challenge    All Challenges
--------  ------------------  -----------  -----------------  -------------------  -------------------  --------------------------------------------------------------------------------------------------------
geonames  POIs from Geonames  11,920,775   136.5 MB           1.5 GB               append-no-conflicts  append-no-conflicts,append-no-conflicts-index-only,append-sorted-no-conflicts,append-fast-with-conflicts

-------------------------------
[INFO] SUCCESS (took 0 seconds)
-------------------------------

My info:
Rally version: 1.1.0
Invoked command: esrally --target-host=<IP_ADDRESS>:9200 --pipeline=benchmark-only --track-path=~/.rally/benchmarks/tracks/my/geonames
Configuration file:
[meta]
config.version = 17

[system]
env.name = local

[node]
root.dir = /root/.rally/benchmarks
src.root.dir = /root/.rally/benchmarks/src

[source]
remote.repo.url = https://github.com/elastic/elasticsearch.git
elasticsearch.src.subdir = elasticsearch

[benchmarks]
local.dataset.cache = /data/esdata

[reporting]
datastore.type = elasticsearch
datastore.host = <IP_ADDRESS>
datastore.port = 9210
datastore.secure = False
datastore.user =
datastore.password =

[tracks]
default.url = https://github.com/elastic/rally-tracks

[teams]
default.url = https://github.com/elastic/rally-teams

[defaults]
preserve_benchmark_candidate = False

[distributions]
release.cache = true

JVM version: none (run benchmark on my own cluster)
OS version: CentOS 7.5
ElastricSearch version: 5.6.4
Description of the problem including expected versus actual behavior:
When I run esrally --target-host=<IP_ADDRESS>:9200 --pipeline=benchmark-only --track-path=~/.rally/benchmarks/tracks/my/geonames`, esrally get blocked in running "index-append " as follow.
 [root@VM_0_106_centos logs]# esrally --target-host=<IP_ADDRESS>:9200 --pipeline=benchmark-only --track-path=~/.rally/benchmarks/tracks/my/geonames

    ____        ____
   / __ \____ _/ / /_  __
  / /_/ / __ `/ / / / / /
 / _, _/ /_/ / / / /_/ /
/_/ |_|\__,_/_/_/\__, /
                /____/

************************************************************************
************** WARNING: A dark dungeon lies ahead of you  **************
************************************************************************

Rally does not have control over the configuration of the benchmarked
Elasticsearch cluster.

Be aware that results may be misleading due to problems with the setup.
Rally is also not able to gather lots of metrics at all (like CPU usage
of the benchmarked cluster) or may even produce misleading metrics (like
the index size).

************************************************************************
****** Use this pipeline only if you are aware of the tradeoffs.  ******
*************************** Watch your step! ***************************
************************************************************************

[INFO] Racing on track [geonames], challenge [append-no-conflicts] and car ['external'] with version [5.6.4].

[WARNING] merges_total_time is 1387485 ms indicating that the cluster is not in a defined clean state. Recorded index time metrics may be misleading.
[WARNING] merges_total_throttled_time is 21970 ms indicating that the cluster is not in a defined clean state. Recorded index time metrics may be misleading.
[WARNING] indexing_total_time is 314254 ms indicating that the cluster is not in a defined clean state. Recorded index time metrics may be misleading.
[WARNING] refresh_total_time is 537849 ms indicating that the cluster is not in a defined clean state. Recorded index time metrics may be misleading.
[WARNING] flush_total_time is 2216 ms indicating that the cluster is not in a defined clean state. Recorded index time metrics may be misleading.
Running delete-index                                                           [100% done]
Running create-index                                                           [100% done]
Running check-cluster-health                                                   [100% done]
Running index-append                                                           [ 38% done]

^C
---------------------------------
[INFO] SUCCESS (took 694 seconds)
---------------------------------

Steps to reproduce:

download allCountries.zip and generate the document.json.bz2 file following the guide in offical doc;
duplicate the geonames directory: mv ~/.rally/benchmarks/tracks/default/geonames  ~/.rally/benchmarks/tracks/my/geonames;
modify the data-url value to /data/esrally/geonames/document-2.json.bz2 in track.json in the new geonames directory;
run command esrally --target-host=<IP_ADDRESS>:9200 --pipeline=benchmark-only --track-path=~/.rally/benchmarks/tracks/my/geonames

Provide logs:
2019-06-14 11:00:20,112 -not-actor-/PID:15922 elasticsearch WARNING POST http://<IP_ADDRESS>:9200/_bulk [status:400 request:0.038s]
2019-06-14 11:00:20,157 -not-actor-/PID:15922 elasticsearch WARNING POST http://<IP_ADDRESS>:9200/_bulk [status:400 request:0.031s]
2019-06-14 11:00:20,201 -not-actor-/PID:15922 elasticsearch WARNING POST http://<IP_ADDRESS>:9200/_bulk [status:400 request:0.030s]
2019-06-14 11:00:20,248 -not-actor-/PID:15922 elasticsearch WARNING POST http://<IP_ADDRESS>:9200/_bulk [status:400 request:0.032s]
2019-06-14 11:00:20,393 -not-actor-/PID:15922 elasticsearch WARNING POST http://<IP_ADDRESS>:9200/_bulk [status:400 request:0.035s]
2019-06-14 11:00:20,441 -not-actor-/PID:15922 elasticsearch WARNING POST http://<IP_ADDRESS>:9200/_bulk [status:400 request:0.034s]
2019-06-14 11:00:20,486 -not-actor-/PID:15922 elasticsearch WARNING POST http://<IP_ADDRESS>:9200/_bulk [status:400 request:0.031s]
2019-06-14 11:00:20,540 -not-actor-/PID:15922 elasticsearch WARNING POST http://<IP_ADDRESS>:9200/_bulk [status:400 request:0.038s]
2019-06-14 11:00:20,584 -not-actor-/PID:15922 elasticsearch WARNING POST http://<IP_ADDRESS>:9200/_bulk [status:400 request:0.030s]
2019-06-14 11:00:20,638 -not-actor-/PID:15922 elasticsearch WARNING POST http://<IP_ADDRESS>:9200/_bulk [status:400 request:0.039s]
2019-06-14 11:00:20,688 -not-actor-/PID:15922 elasticsearch WARNING POST http://<IP_ADDRESS>:9200/_bulk [status:400 request:0.037s]
2019-06-14 11:00:20,737 -not-actor-/PID:15922 elasticsearch WARNING POST http://<IP_ADDRESS>:9200/_bulk [status:400 request:0.034s]
2019-06-14 11:00:20,785 -not-actor-/PID:15922 elasticsearch WARNING POST http://<IP_ADDRESS>:9200/_bulk [status:400 request:0.034s]
2019-06-14 11:00:20,830 -not-actor-/PID:15922 elasticsearch WARNING POST http://<IP_ADDRESS>:9200/_bulk [status:400 request:0.030s]
2019-06-14 11:00:20,875 -not-actor-/PID:15922 elasticsearch WARNING POST http://<IP_ADDRESS>:9200/_bulk [status:400 request:0.033s]
2019-06-14 11:00:20,921 -not-actor-/PID:15922 elasticsearch WARNING POST http://<IP_ADDRESS>:9200/_bulk [status:400 request:0.032s]
2019-06-14 11:00:20,966 -not-actor-/PID:15922 elasticsearch WARNING POST http://<IP_ADDRESS>:9200/_bulk [status:400 request:0.031s]
2019-06-14 11:00:21,11 -not-actor-/PID:15922 elasticsearch WARNING POST http://<IP_ADDRESS>:9200/_bulk [status:400 request:0.031s]
2019-06-14 11:00:21,15 -not-actor-/PID:15922 elasticsearch WARNING POST http://<IP_ADDRESS>:9200/_bulk [status:400 request:0.002s]
2019-06-14 11:00:21,974 ActorAddr-(T|:43712)/PID:15923 esrally.actor INFO LoadGenerator[6] is ready for the next task.
2019-06-14 11:00:21,974 ActorAddr-(T|:43712)/PID:15923 esrally.actor INFO LoadGenerator[6] reached join point [JoinPoint(4)].
2019-06-14 11:00:22,71 ActorAddr-(T|:43597)/PID:15920 esrally.actor INFO LoadGenerator[3] is ready for the next task.
2019-06-14 11:00:22,72 ActorAddr-(T|:43597)/PID:15920 esrally.actor INFO LoadGenerator[3] reached join point [JoinPoint(4)].
2019-06-14 11:00:22,89 ActorAddr-(T|:43612)/PID:15918 esrally.actor INFO LoadGenerator[1] is ready for the next task.
2019-06-14 11:00:22,89 ActorAddr-(T|:43612)/PID:15918 esrally.actor INFO LoadGenerator[1] reached join point [JoinPoint(4)].
2019-06-14 11:00:22,207 ActorAddr-(T|:37034)/PID:15922 esrally.actor INFO LoadGenerator[5] is ready for the next task.
2019-06-14 11:00:22,208 ActorAddr-(T|:37034)/PID:15922 esrally.actor INFO LoadGenerator[5] reached join point [JoinPoint(4)].
2019-06-14 11:00:29,303 ActorAddr-(T|:44828)/PID:15924 esrally.actor INFO LoadGenerator[7] is exiting due to ActorExitRequest.
2019-06-14 11:00:29,299 ActorAddr-(T|:44988)/PID:15917 esrally.actor INFO LoadGenerator[0] is exiting due to ActorExitRequest.
2019-06-14 11:00:29,302 ActorAddr-(T|:34195)/PID:15921 esrally.actor INFO LoadGenerator[4] is exiting due to ActorExitRequest.
2019-06-14 11:00:29,301 ActorAddr-(T|:43597)/PID:15920 esrally.actor INFO LoadGenerator[3] is exiting due to ActorExitRequest.
2019-06-14 11:00:29,300 ActorAddr-(T|:43612)/PID:15918 esrally.actor INFO LoadGenerator[1] is exiting due to ActorExitRequest.
2019-06-14 11:00:33,787 ActorAddr-(T|:37034)/PID:15922 esrally.actor INFO LoadGenerator[5] is exiting due to ActorExitRequest.
2019-06-14 11:00:33,883 ActorAddr-(T|:41761)/PID:15919 esrally.actor INFO LoadGenerator[2] is exiting due to ActorExitRequest.
2019-06-14 11:00:33,887 ActorAddr-(T|:43712)/PID:15923 esrally.actor INFO LoadGenerator[6] is exiting due to ActorExitRequest

Describe the feature:

Hello,
GitHub issues ideally should be used for reporting verified bugs; it is best to ask questions or report potential issues in https://discuss.elastic.co/c/elasticsearch/rally first, where there are also higher chances of receiving help.
Specifically to your problem, you can observe from the Rally log file that Elasticsearch is returning 400 to the bulk requests issued:
WARNING POST http://<IP_ADDRESS>:9200/_bulk [status:400 request:0.031s]

I'd suggest you take a look in the Elasticsearch logs for more information.
Also note that Rally supports the --on-error=abort parameter which would end the benchmark immediately upon receiving an error.
I am going to close this ticket, feel free to ask further questions in https://discuss.elastic.co/c/elasticsearch/rally.

Hello,
GitHub issues ideally should be used for reporting verified bugs; it is best to ask questions or report potential issues in https://discuss.elastic.co/c/elasticsearch/rally first, where there are also higher chances of receiving help.
Specifically to your problem, you can observe from the Rally log file that Elasticsearch is returning 400 to the bulk requests issued:
WARNING POST http://<IP_ADDRESS>:9200/_bulk [status:400 request:0.031s]

I'd suggest you take a look in the Elasticsearch logs for more information.
Also note that Rally supports the --on-error=abort parameter which would end the benchmark immediately upon receiving an error.
I am going to close this ticket, feel free to ask further questions in https://discuss.elastic.co/c/elasticsearch/rally.

Ok~Thank you.


Update Tau epitope, AT100

Correction of phosphorylation sites.

@cthoyt  let me know if anything else needs to be done.


LG A1 48 not able to turn off anymore after LG update 03.30.14. turn on still fine.

it all happened right after LG software update.  TV will not turn off anymore. also not able to do idle.

I think it is possible LG changed something. Will investigate

Yes, I recently received Software Version 03.30.14 I am currently installing the dev build to try and get you more info.

C:\ProgramData\LGTV Companion

Log.txt

thanks! it really looks like LG has taken action to close down this port. in the recent firmware Will investigate more

Thanks for the effort. Great program. Hope you can fix it soon.
�
From: JPersson77 @.>
Sent: Tuesday, January 17, 2023 4:55 PM
To: JPersson77/LGTVCompanion @.>
Cc: gruan8886 @.>; Author @.>
Subject: Re: [JPersson77/LGTVCompanion] LG A1 48 not able to turn off anymore after LG update 03.30.14. turn on still fine. (Issue #103)
�
thanks! it really looks like LG has taken action to close down this port. in the recent firmware Will investigate more
—
Reply to this email directly, view it on GitHub https://github.com/JPersson77/LGTVCompanion/issues/103#issuecomment-1386304178 , or unsubscribe https://github.com/notifications/unsubscribe-auth/A5J44QBLF56KGFQ4DIV6ZI3WS45NHANCNFSM6AAAAAAT6JU7DM .
You are receiving this because you authored the thread.  https://github.com/notifications/beacon/A5J44QHE62UXXPMKACPWQZ3WS45NHA5CNFSM6AAAAAAT6JU7DOWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTSSUFJLE.gif Message ID: @.*** @.***> >

A fix has been implemented and will be in the next release

great news. Thanks alot .

Same behaviour on C2 42 with software version 03.30.16. Excited to see if next release fixes for this software version as well.

New version is up (v2) so I'm closing this issue. https://github.com/JPersson77/LGTVCompanion/releases


Add better editing UI editing tools

this is for later. closing for now. will create a new issue once v4 is out with the new rewrite.


Merge pull request #2 from alibaba/master

update from pouch

Ⅰ. Describe what this PR did
Ⅱ. Does this pull request fix one issue?

Ⅲ. Describe how you did it
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Added livenessprobe example with hidden parameters

Didn't find any mention about the HTTP/HTTPS  scheme or host definition. Fixed.

This change is

@devin-donnelly @michelleN does it look better now?

I must have been tagged by accident instead of @mikedanese.
While I'm here, thanks for the clarified example @kayrus. I ran it and it worked nicely for me.


Nin: Fix Hollow Nozuchi

Hollow Nozuchi is currently implemented as just another ground dot lasting the same amount of time as doton. This is incorrect- it adds potency to doton.
This may be fixed by having Hollow Nozuchi applying a debuff on the boss, and having it only applicable to certain skills- a skill_allowlist.

Also, it triggers automatically upon using several skills:
"Requires Hakke Mujinsatsu to be executed as a combo action or upon executing Katon, Goka Mekkyaku, or Phantom Kamaitachi.
Effect can only be triggered while Doton is active." (https://na.finalfantasyxiv.com/jobguide/ninja/).
So we should trigger it upon use of these skills, checking for doton to be active as well (via "status effect", as a hack).


Dead Links

This Page: https://docs.microsoft.com/en-us/azure/communication-services/concepts/ui-library/ui-library-overview?pivots=platform-mobile
Has two links to iOS and Android "issues" respectively; both links point to:
iOS: https://github.com/Azure/communication-ui-toolkit-ios-pr/wiki/Known-Issues
Android: https://github.com/Azure/communication-ui-toolkit-android-pr/wiki/Known-Issues
Both links are 404 in GitHub.

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

ID: 577ba291-002f-11ab-78e8-8254ee2a2921
Version Independent ID: c436ebbb-30c3-8dc3-c78f-017210697d83
Content: UI Library overview - An Azure Communication Services concept document
Content Source: articles/communication-services/concepts/ui-library/ui-library-overview.md
Service: azure-communication-services
GitHub Login: @ddematheu2
Microsoft Alias: dademath

@Gryzor Thanks for the feedback! We are currently investigating and will update you shortly.

No problem! Do you know of off the to of your head what the Android link would be?

https://github.com/Azure/communication-ui-library-android/wiki/Known-Issues

@Gryzor Thanks for reaching here! This looks now taken care. We will close this out but if you feel you need more information please just let us know.


Build a ____ event

Description

make a generic event for just building something
you can give people the tools and supplies or just scatter them on the map.
also i reusable so you can ideally get a few challenges out of it

build your own musical chair


Long startup and shutdown on 20.03 BETA

Describe the bug
Very slow boot. And hang on shutdown. something about waiting for rngd
To Reproduce
Steps to reproduce the behavior:
Change channel to 20.03 BETA
update channel: nix-channel --update
nixos-rebuild switch --upgrade
boot.kernelPackages = pkgs.linuxPackages_latest;
Expected behavior
Be able to boot in under 30sec. And shutdown without hangs.
Screenshots

Additional context
After login from sddm. I'm still waiting for gui to start. login to awesome window manager.
All my partition are on nvme m.2 ssd.
I was not having this issue on 19.09. With the same setup.
One other thing I notice. I can only used reboot and shutdown now in root. was not the case in 19.09.
Metadata

system: "x86_64-linux"
host os: Linux 5.5.5, NixOS, 20.03beta216.d31e383c44e (Markhor)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.3.2
channels(root): "nixos-20.03beta216.d31e383c44e"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

I reproduce the boot time issue on 20.03 too.
On a 19.09 I have the following output for rngd (reversed journalctl output) :
-- Reboot --
févr. 22 23:08:33 ely-lenovo rngd[660]: [jitter]: Closing thread 3
févr. 22 23:08:33 ely-lenovo rngd[660]: [jitter]: Closing thread 2
févr. 22 23:08:33 ely-lenovo rngd[660]: [jitter]: Closing thread 1
févr. 22 23:08:33 ely-lenovo rngd[660]: [jitter]: Closing thread 0
févr. 22 23:08:33 ely-lenovo rngd[660]: [jitter]: Shutting down
févr. 22 23:08:33 ely-lenovo rngd[660]: [rdrand]: Shutting down
févr. 22 23:08:33 ely-lenovo rngd[660]: [hwrng ]: Shutting down
févr. 22 12:32:49 ely-lenovo rngd[660]: [pkcs11]: Initialization Failed
févr. 22 12:32:49 ely-lenovo rngd[660]: [pkcs11]: No pkcs11 slots available
févr. 22 12:32:49 ely-lenovo rngd[660]: [jitter]: Initialized
févr. 22 12:32:49 ely-lenovo rngd[660]: [jitter]: Enabling JITTER rng support
févr. 22 12:32:49 ely-lenovo rngd[660]: [jitter]: Unable to obtain AES key, disabling AES in JITTER source
févr. 22 12:32:49 ely-lenovo rngd[660]: [jitter]: Initializing AES buffer
févr. 22 12:32:49 ely-lenovo rngd[660]: [rdrand]: Initialized
févr. 22 12:32:49 ely-lenovo rngd[660]: [rdrand]: Enabling RDSEED rng support
févr. 22 12:32:49 ely-lenovo rngd[660]: [hwrng ]: Initialized
févr. 22 12:32:49 ely-lenovo rngd[660]: Initializing available sources
févr. 22 12:32:49 ely-lenovo systemd[1]: Started Hardware RNG Entropy Gatherer Daemon.

I have the feeling that the rngd daemon is not behaving properly and is causing bootup/shutdowns to be stuck while waiting it.

I haven't seen any boot time increase, but shutdown seems to be waiting about 20 seconds for rngd on my laptop.

Only most recent change to rngd service https://github.com/NixOS/nixpkgs/pull/79833.
Perhaps try reverting it and see if there's a difference (in a controllable environment)

Yeah, if I revert https://github.com/NixOS/nixpkgs/pull/79833, shutdown doesn't have a waiting for process to stop: rngd.
Startup doesn't have an issue on my machine.

The only change seems to be unitConfig.DefaultDependencies = false; for my config at least?

@dayflip one of the changes with 20.03 is the default kernel changed from 4.19 (previous LTS) to 5.5 (current LTS).
As far as "slow boot" is concerned, If there is a kernel-side regression that is causing issues on your hardware, switching to 4.19 would help figuring out where the issue may lie.
boot.kernelPackages = pkgs.linuxPackages_4_19;

That is, assuming you weren't already using Linux 5.5 on NixOS 19.09.

To figure out what's the problem on boot, I suggest:
$ systemd-analyze plot > boot.svg
That allows you to figure out exactly what's starting when and why it waited.

https://github.com/NixOS/nixpkgs/pull/80920 Did it for me, at least for shutdown.

@tokudan i had to convert it to png. to post it here.
From what I can tell. Half sec for display-manager.service and then 8 sec to user-175.slice to load. Then nscd.service took 21 sec. After that. 38.5 sec user-1000.slice. And dev-fuse.device took 19.5 sec.

Don't think this is giving me the full picture. What other stuff can help pin point the long startup?

The graph looks like the slow startup isn't related to rngd, instead being caused by #60900?

From what I can tell. Half sec for display-manager.service and then 8 sec to user-175.slice to load. Then nscd.service took 21 sec. After that. 38.5 sec user-1000.slice. And dev-fuse.device took 19.5 sec.
dhcpcd took 9.8 seconds, then nscd started within 7ms.
Then there's a long delay until the user with uid 1000 logs in and another long wait until fuse becomes active, which I believe is probably the actual issue.
Can you try to mount your dav mountpoint through startup scripts of your user instead of systemd?
At the far end you can see network-interfaces.target is very late and marks the point when all network interfaces are online. Which probably means that your dependencies on the network may slow down the whole boot of the system.
My suggestion would be to try and disable your network mounts (webdav, etc) during boot and see if that changes anything.

Will switching around display manager. I had one thing pop up. With lightdm and gdm.
A start job is running for /sys/subsystem/net/devices/wlp8s0 ( Xmin Xs / 1min 30s)
But this does not pop up with sddm. Witch is odd.
I have not touch this part. Since configuration.nix was made. I mostly only used weird. But still keep wireless stuff for bluetooth.

networking.useDHCP = false;
networking.interfaces.enp10s0.useDHCP = true;
networking.interfaces.wlp8s0.useDHCP = true;

And I have iwd enable. networking.wireless.iwd.enable = true;

So I figure out my issue with boot. It not under 30sec.

Startup finished in 14.828s (firmware) + 4.153s (loader) + 5.459s (kernel) + 2.913s (userspace) = 27.353s
graphical.target reached after 2.910s in userspace

Change I made so far.

networking.useDHCP = false;
#networking.interfaces.enp10s0.useDHCP = true;
#networking.interfaces.wlp8s0.useDHCP = true;

And added connman for my network + iwd for wifi backend.
But there a new issue.

system: "x86_64-linux"
host os: Linux 5.5.5, NixOS, 20.03beta-410.67c24f6f8a7 (Markhor)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.3.2
channels(root): "nixos-20.03beta-410.67c24f6f8a7"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

Now that a reboot or poweroff. I only get this: _
No other info pop up for me. Just _. It does not blinks.


"CMake: build" is repeated twice in the list

Brief Issue Summary
More info:
This issue is reproduced on Windows, Linux, and Mac platforms
Repro steps:

Add a file named main.cpp with the following content:

#include <iostream>
auto main() -> int { std::cout << "hello world" << std::endl; }

Add a file named CMakeLists.txt with the following content:

cmake_minimum_required(VERSION 3.5)
project(Test)
add_executable(Test main.cpp)

Click F1 and run "Task: Configure Task" command
Choosing the "CMake: build"
Re-click "Task: configure task"
Check the list

Expected result:
All commands appear only once
Actual result:
"CMake: build" is repeated twice in the list

CMake Tools Diagnostics
No response
Debug Log
No response
Additional Information
No response

This is expected because we provide the cmake build task by default, so when it is redefined in the launch.json, it will appear twice. Closing.


Mostly typos, grammar and formatting

Mostly tiny typoes, but two more meaningful changes:

The 'introduction' section to the Deque chapter has gone awol. I think it was due to duplicative field declarations at the top of the .md file. I've fixed these, but you'll need to rebuild to see if it's working now?
This is super pedantic and trivial: but I changed the ‘num = 7’ used in your Hot Potato example to 9. When it was ‘7’, I assumed it reflecting the Josephus story (i.e. ‘killing’ every 7th person). Actually your implementation kills every 8th person (or every (n+1)th person). I thought about changing the implementation to actually killing every nth person, but then it was inconsistent with your description of the hot potato algorithm immediately above. I thought it easier to change the number from 7 to remove any potential confusion with the Josephus story.

A few things I didn't change, but might need some attention:

Markdown rendering is broken in a few places. Doesn't seem to be invalid markdown; could there be a bug in the markdown -> HTML library you're using? See example of putting Hexadecimals in number coding:

The Binary Heap section is described as being implemented with the ‘list’ data structure. Should this be renamed to an ‘array’ data structure, given you’ve already addressed lists as an abstract data type (that itself is not, in fact, implemented with an array)?

@robertdapice awesome, massive thanks for these. I'm embarrassed that you found so many typos :( . I'll move the issues you found to new tickets and merge this.


Added BC support for rake < 11. Resolves #1740

No tests, since this is a third-party issue. I ran tests locally with rake 10.5.0 to verify the issue, then patched and ran tests again, where they passed.

Thanks for this! It seems to do the trick. Can you include a changelog entry to the effect of "restores compatibility with Rake 10.x" and reference #1740?

@mattbrictson done

I'm not seeing the changelog edit in your latest commit. Can you double-check you pushed your latest changes? Thanks.

You're right - didn't push it after all. Here you go.

Oops, there is now a conflict preventing me from merging this PR. Looks like it is because you removed the "your contribution here" line from the changelog. Can you resolve the conflicts, please?

@troelskn I'd love to merge this PR so that we can release a new version of Capistrano with this Rake fix. Can you resolve the conflicts when you have a chance so that I can do the merge? Thanks!

Thanks! Merging.


Deregistration of token device on iOS

Describe the bug
We are experiencing a problem receiving web push notifications in a PWA on iOS device. At the moment the device is registered in the PWA we receive all the push notifications. If we then minimize the PWA and receive another notification at that time. Then the device is deregistered at a sudden. Probably because the device token is nog longer recognized by AWS SNS or Firebase.
By te way, this work fine on Android, but not on iOS. We send our web push notifications via AWS SNS with Firebase.
Expected Behavior
We expect te token/device not to be deregistered when receiving a notification while the PWA is minimized. Basically just as it works now with Android devices.
Current Behavior

Reproduction Steps

Possible Solution
No response
Additional Information/Context
No response
AWS .NET SDK and/or Package version used
AWSSDK.SimpleNotificationService 3.7.300.20
Targeted .NET Platform
.NET 7
Operating System and version
iOS 17.1.1

Would it be possible to share reproduction steps and the current behavior you're seeing? Unfortunately right now there isn't enough information for us to investigate the problem.


Task with base OnceQueue causes my celery task invisible.

When i use rabbitmq as my celery broker it works fine. But if i prefer to use redis as celery broker and celery-once broker at same time my OnceQueue task becomes invisible. Worker doesn't receive that task.
By the way, if i remove OnceQueue it works fine too.

Hey @fatihsucu, sorry this issue slipped by my notice.
I haven't experienced this using celery + redis + celery_once. So I'm not really sure how to debug this.
Example code/repo that demonstrates how to replicate would be incredibly helpful to debugging it further.


All \hfill to set alignment of elements in matrices and arrays

If \hfill appears at the beginning or ending of table cells, this can be use to set the <mtd> alignment property.  This would improve the ability to handle specialized layouts in TeX.

==> In Testsuite
LaTeXToMathML/matrices/issue903-1.html
LaTeXToMathML/matrices/issue903-2.html


Enable CachedBatchWriterSuite.testCompressColBatch

This fixes #8329
We use mockito with a spy to essentially do the same thing that we were doing before.

build

build


🐞 [Bug]: Farmerbot complains about invalid or unset relay addresses

What happened?
We have several farmers reporting that they see errors from farmerbot regarding invalid or unset relay addresses associated with node twins, when those twins all have relay.grid.tf set.
Here's one example from a farmer trying to set up the farmerbot for the first time:

Another from a farmer who's been running the bot with a working setup for a while:

One more:

what is the version of the farmerbot used?

It's the latest version.

I don't think it is the latest. Logs from previous versions

Seems indeed resolved by updating to v0.14.12.


Bug 1849176: Revert "Remove unnecessary yum install"

ART builds for golang 1.12 do not include gpgme-devel and
libassuan-devel. Removing caused ART builds to fail.
Run yum install commands before setting the WORKDIR, because
the working directory does not exist in the container until
the COPY directive executes.

/test e2e-gcp
the pod is gone.
Would like to see the build log

/retest

/retest

/lgtm

(patch manager) issue affecting real-world users

/hold
@openshift/openshift-team-storage storage tests are perma-failing on OCP 4.3

/retest

Filed https://bugzilla.redhat.com/show_bug.cgi?id=1884242 to address e2e-gcp failures.
@bparees this PR is needed to fix our ART build for openshift-controller-manger. Build there is currently broken.

@bparees this PR is needed to fix our ART build for openshift-controller-manger. Build there is currently broken.

@adambkaplan looks like you've got all the labels you need other than removing the hold, do you need anything from me?

/hold cancel
@bparees e2e-gcp has been spinning on this one. Will give it another shot.

/retest


[Error] :release-channel-issue "Github API Failed(404) {"message":"Not Found","documentation_url":"https://docs.github.com/rest/reference/repos#get-the-latest-release\"}"]

Cannot install on version 0.9.2

Looks like a release needs to be made.

Sorry for not having investigated this further. I'm looking into it this evening. Thanks for the hint!

Can you please confirm if the issue is solved for you?


State change causing API fetch

Whenever you update any state on the page (like dark mode on the project example) or any other state variable, an new API Fetch call is made.

@celsosa
Is this behaviour happening in the storybook or the library?

I am having this issue in the NPM library @jagnani73

I am having this issue in the NPM library @jagnani73

Can you share some coffee to duplicate the issue @The18thWarrior


Update kamon-bundle, kamon-core, ... to 2.1.20

Updates

io.kamon:kamon-bundle
io.kamon:kamon-core
io.kamon:kamon-prometheus

from 2.1.18 to 2.1.20.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "io.kamon" } ]

labels: library-update, semver-patch

Superseded by #249.


Added features and bug fixes

Added interactive brush to select daterange on histogram page

Added multiple URI support

Fixed bug that occasionally interfered with summary page load

Fixed explanation on stats page

Fixed date range bug that loaded partial timemap after date range stats page

Fixed caching issue that deleted cache after generating a full timemap

Changed Help icon

It's ready to be merged


Generalize handling of chunked array types

Initial attempt to get cubed working within xarray, as an alternative to dask.

[x] Closes #6807, at least for the case of cubed
[x] Tests added
[x] User visible changes (including notable bug fixes) are documented in whats-new.rst
[x] New functions/methods are listed in api.rst
[x] Correct type hints

I've added a manager kwarg to the .chunk methods so you can do da.chunk(manager="cubed") to convert to a chunked cubed.CoreArray, with the default still being da.chunk(manager="dask"). (I couldn't think of a better name than "manager", as "backend" and "executor" are already taken.)
At the moment it should work except for an import error that I don't understand, see below.
Fro cubed to work at all with this PR we would also need:

[x] Cubed to expose the correct array type consistently https://github.com/tomwhite/cubed/issues/123
[x] A cubed version of apply_gufunc https://github.com/tomwhite/cubed/pull/119 - implemented in https://github.com/tomwhite/cubed/pull/149 :partying_face:

To-dos for me on this PR:

[x] Re-route xarray.apply_ufunc through cubed.apply_gufunc instead of dask's apply_gufunc when appropriate,
[x] Add from_array_kwargs to opening functions, e.g. open_zarr, and open_dataset,
[x] Add from_array_kwargs to creation functions, such as full_like,
[x] Add store_kwargs as a way to propagate cubed-specific kwargs when saving to_zarr.

To complete this project more generally we should also:

[ ] Have cubed.apply_gufunc support multiple output arguments https://github.com/tomwhite/cubed/issues/152
[x] Have a top-level cubed.unify_chunks to match dask.array.core.unify_chunks
[ ] Write a test suite for wrapping cubed arrays, which would be best done via #6894
[ ] Generalise xarray.map_blocks to work on cubed arrays, ideally by first rewriting xarray's implementation of map_blocks to use dask.array.map_blocks

cc @tomwhite

I think the manager keyword will also need adding to open_zarr, open_dataset and to_zarr.
I'm interested in trying this out on some of our genomics use cases in sgkit (see https://github.com/pystatgen/sgkit/issues/908), so please let me know when you think it's ready to try @TomNicholas.

This was more abstract than expected

Yeah I was kind of asking whether this was unnecessarily abstract, and if there was a simpler design that achieved the same flexibility.

@TomNicholas it might be good to rebase this now that #7067 is in.

@drtodd13 tagging you here and linking my notes from today's distributed arrays working group meeting for the links and references to this PR.

@drtodd13 mentioned today that ramba doesn't actually require explicit chunks to work, which I hadn't realised. So forcing wrapped libraries to implement an explicit chunks method might be too restrictive. Ramba could possibly work entirely through the numpy array API standard.

ramba doesn't actually require explicit chunks to work

I suspect Arkouda is similar in that this is not a detail the user is expected to worry about. (cc @sdbachman)

I'm making progress with this PR, and now that @tomwhite implemented cubed.apply_gufunc I've re-routed xarray.apply_ufunc to use whatever version of apply_gufunc is defined by the chosen ChunkManager. This means many basic operations should now just work:
In [1]: import xarray as xr

In [2]: da = xr.DataArray([1, 2, 3], dims='x')

In [3]: da_chunked = da.chunk(from_array_kwargs={'manager': 'cubed'})

In [4]: da_chunked
Out[4]:
<xarray.DataArray (x: 3)>
cubed.Array<array-003, shape=(3,), dtype=int64, chunks=((3,),)>
Dimensions without coordinates: x

In [5]: da_chunked.mean()
Out[5]:
<xarray.DataArray ()>
cubed.Array<array-006, shape=(), dtype=int64, chunks=()>

In [6]: da_chunked.mean().compute()
[cubed.Array<array-009, shape=(), dtype=int64, chunks=()>]
Out[6]:
<xarray.DataArray ()>
array(2)

(You need to install both cubed>0.5.0 and the main branch of rechunker for this to work.)
I still have a fair bit more to do on this PR (see checklist at top), but for testing should I:

Dtart making a test_cubed.py file in xarray as part of this PR with bespoke tests,
Put bespoke tests for xarray wrapping cubed somewhere else (e.g. the cubed repo or a new cubed-xarray repo),
Merge this PR without cubed-specific tests and concentrate on finishing the general duck-array testing framework in #6908 so we can implement (b) in the way we actually eventually want things to work for 3rd-party duck array libraries?

I would prefer not to have this PR grow to be thousands of lines by including tests in it, but also waiting for #6908 might take a while because that's also a fairly ambitious PR.
The fact that the tests are currently green for this PR (ignoring some mypy stuff) is evidence that the decoupling of dask from xarray is working so far.

Great work @TomNicholas!
I don't have a strong opinion about the tests, but putting them in a new project to keep xarray changes to a minimum is probably a good idea for the moment.

Thanks @tomwhite - I think it might make sense for me to remove the CubedManager class from this PR and instead put that & cubed+xarray tests into another repo. That keeps xarray's changes minimal, doesn't require putting cubed in any xarray CI envs, and hopefully allows us to merge the ChunkManager changes here earlier.

Places dask is still explicitly imported in xarray
There are a few remaining places where I haven't generalised to remove specific import dask calls either because it won't be imported at runtime unless you ask for it, cubed doesn't implement the equivalent function, that function isn't in the array API standard, or because I'm not sure if the dask concept used generalises to other parallel frameworks.

[ ] open_mfdataset(..., parallel=True) - there is no cubed.delayed to wrap the open_dataset calls in,
[ ] Dataset.__dask_graph__ and all the other similar dask magic methods
[ ] dask_array_ops.rolling - uses functions from dask.array.overlap,
[ ] dask_array_ops.least_squares - uses dask.array.apply_along_axis and dask.array.linalg.lstsq,
[ ] dask_array_ops.push - uses dask.array.reductions.cumreduction

I would like to get to the point where you can use xarray with a chunked array without ever importing dask. I think this PR gets very close, but that would be tricky to test because cubed depends on dask (so I can't just run the test suite without dask in the environment), and there are not yet any other parallel chunk-aware frameworks I know of (ramba and arkouda don't have a chunks attribute so wouldn't require this PR).

I tried opening a zarr store into xarray with chunking via cubed, but I got an error inside the indexing adapter classes
# create example zarr store
orig = xr.tutorial.open_dataset("air_temperature")
orig.to_zarr('air2.zarr')

# open it as a cubed array
ds = xr.open_dataset('air2.zarr', engine='zarr', chunks={}, from_array_kwargs={'manager': 'cubed'})

# fails at this point
ds.load()

```python
---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
File ~/miniconda3/envs/cubed/lib/python3.9/site-packages/tenacity/__init__.py:382, in Retrying.__call__(self, fn, *args, **kwargs)
    381 try:
--> 382     result = fn(*args, **kwargs)
    383 except BaseException:  # noqa: B902
File ~/miniconda3/envs/cubed/lib/python3.9/site-packages/cubed/runtime/executors/python.py:10, in exec_stage_func(func, *args, **kwargs)
8 @retry(stop=stop_after_attempt(3))
9 def exec_stage_func(func, *args, **kwargs):
---> 10     return func(*args, **kwargs)
File ~/miniconda3/envs/cubed/lib/python3.9/site-packages/cubed/primitive/blockwise.py:66, in apply_blockwise(out_key, config)
64     args.append(arg)
---> 66 result = config.function(*args)
67 if isinstance(result, dict):  # structured array with named fields
File ~/miniconda3/envs/cubed/lib/python3.9/site-packages/cubed/core/ops.py:439, in map_blocks..func_with_block_id..wrap(*a, **kw)
438 block_id = offset_to_block_id(a[-1].item())
--> 439 return func(*a[:-1], block_id=block_id, **kw)
File ~/miniconda3/envs/cubed/lib/python3.9/site-packages/cubed/core/ops.py:572, in map_direct..new_func..wrap(block_id, *a, **kw)
571 args = a + arrays
--> 572 return func(*args, block_id=block_id, **kw)
File ~/miniconda3/envs/cubed/lib/python3.9/site-packages/cubed/core/ops.py:76, in _from_array(e, x, outchunks, asarray, block_id)
75 def _from_array(e, x, outchunks=None, asarray=None, block_id=None):
---> 76     out = x[get_item(outchunks, block_id)]
77     if asarray:
File ~/Documents/Work/Code/xarray/xarray/core/indexing.py:627, in CopyOnWriteArray.getitem(self, key)
626 def getitem(self, key):
--> 627     return type(self)(_wrap_numpy_scalars(self.array[key]))
File ~/Documents/Work/Code/xarray/xarray/core/indexing.py:534, in LazilyIndexedArray.getitem(self, indexer)
533     return array[indexer]
--> 534 return type(self)(self.array, self._updated_key(indexer))
File ~/Documents/Work/Code/xarray/xarray/core/indexing.py:500, in LazilyIndexedArray._updated_key(self, new_key)
499 def _updated_key(self, new_key):
--> 500     iter_new_key = iter(expanded_indexer(new_key.tuple, self.ndim))
501     full_key = []
AttributeError: 'tuple' object has no attribute 'tuple'
The above exception was the direct cause of the following exception:
RetryError                                Traceback (most recent call last)
Cell In[69], line 1
----> 1 ds.load()
File ~/Documents/Work/Code/xarray/xarray/core/dataset.py:761, in Dataset.load(self, **kwargs)
758 chunkmanager = get_chunked_array_type(*lazy_data.values())
760 # evaluate all the chunked arrays simultaneously
--> 761 evaluated_data = chunkmanager.compute(*lazy_data.values(), **kwargs)
763 for k, data in zip(lazy_data, evaluated_data):
764     self.variables[k].data = data
File ~/Documents/Work/Code/xarray/xarray/core/parallelcompat.py:451, in CubedManager.compute(self, *data, **kwargs)
448 def compute(self, *data: "CubedArray", **kwargs) -> np.ndarray:
449     from cubed import compute
--> 451     return compute(*data, **kwargs)
File ~/miniconda3/envs/cubed/lib/python3.9/site-packages/cubed/core/array.py:300, in compute(executor, callbacks, optimize_graph, *arrays, **kwargs)
297         executor = PythonDagExecutor()
299 _return_in_memory_array = kwargs.pop("_return_in_memory_array", True)
--> 300 plan.execute(
301     executor=executor,
302     callbacks=callbacks,
303     optimize_graph=optimize_graph,
304     array_names=[a.name for a in arrays],
305     **kwargs,
306 )
308 if _return_in_memory_array:
309     return tuple(a._read_stored() for a in arrays)
File ~/miniconda3/envs/cubed/lib/python3.9/site-packages/cubed/core/plan.py:154, in Plan.execute(self, executor, callbacks, optimize_graph, array_names, **kwargs)
152 if callbacks is not None:
153     [callback.on_compute_start(dag) for callback in callbacks]
--> 154 executor.execute_dag(
155     dag, callbacks=callbacks, array_names=array_names, **kwargs
156 )
157 if callbacks is not None:
158     [callback.on_compute_end(dag) for callback in callbacks]
File ~/miniconda3/envs/cubed/lib/python3.9/site-packages/cubed/runtime/executors/python.py:22, in PythonDagExecutor.execute_dag(self, dag, callbacks, array_names, **kwargs)
20 if stage.mappable is not None:
21     for m in stage.mappable:
---> 22         exec_stage_func(stage.function, m, config=pipeline.config)
23         if callbacks is not None:
24             event = TaskEndEvent(array_name=name)
File ~/miniconda3/envs/cubed/lib/python3.9/site-packages/tenacity/init.py:289, in BaseRetrying.wraps..wrapped_f(*args, **kw)
287 @functools.wraps(f)
288 def wrapped_f(*args: t.Any, **kw: t.Any) -> t.Any:
--> 289     return self(f, *args, **kw)
File ~/miniconda3/envs/cubed/lib/python3.9/site-packages/tenacity/init.py:379, in Retrying.call(self, fn, *args, **kwargs)
377 retry_state = RetryCallState(retry_object=self, fn=fn, args=args, kwargs=kwargs)
378 while True:
--> 379     do = self.iter(retry_state=retry_state)
380     if isinstance(do, DoAttempt):
381         try:
File ~/miniconda3/envs/cubed/lib/python3.9/site-packages/tenacity/init.py:326, in BaseRetrying.iter(self, retry_state)
324     if self.reraise:
325         raise retry_exc.reraise()
--> 326     raise retry_exc from fut.exception()
328 if self.wait:
329     sleep = self.wait(retry_state)
RetryError: RetryError[<Future at 0x7fc0c69be4f0 state=finished raised AttributeError>
</details>

This still works fine for dask.

AttributeError: 'tuple' object has no attribute 'tuple'

This means you're indexing a LazilyIndexedArray with a tuple but you need to wrap that tuple in an Indexer object llke BasicIndexer, VectorizedIndexer etc..

I think it might make sense for me to remove the CubedManager class from this PR and instead put that & cubed+xarray tests into another repo. That keeps xarray's changes minimal, doesn't require putting cubed in any xarray CI envs, and hopefully allows us to merge the ChunkManager changes here earlier.

That sounds like a good plan to me.

Places dask is still explicitly imported in xarray
There are a few remaining places where I haven't generalised to remove specific import dask calls either because it won't be imported at runtime unless you ask for it, cubed doesn't implement the equivalent function, that function isn't in the array API standard, or because I'm not sure if the dask concept used generalises to other parallel frameworks.

[ ]  open_mfdataset(..., parallel=True) - there is no cubed.delayed to wrap the open_dataset calls in,
[ ]  Dataset.__dask_graph__ and all the other similar dask magic methods
[ ]  dask_array_ops.rolling - uses functions from dask.array.overlap,
[ ]  dask_array_ops.least_squares - uses dask.array.apply_along_axis and dask.array.linalg.lstsq,
[ ]  dask_array_ops.push - uses dask.array.reductions.cumreduction

This is a useful list! I hope that we could close the gap for some of these over time.

I would like to get to the point where you can use xarray with a chunked array without ever importing dask. I think this PR gets very close, but that would be tricky to test because cubed depends on dask (so I can't just run the test suite without dask in the environment)

Agreed. I have opened https://github.com/tomwhite/cubed/issues/154 to make it possible to test without a Dask dependency.

dask_array_ops.rolling - uses functions from dask.array.overlap

This is unused, we use sliding_window_view now.

Thanks @dcherian ! Once I copied that explicit indexer business I was able to get serialization to and from zarr working with cubed!
In [1]: import xarray as xr

In [2]: from cubed import Spec

In [3]: ds = xr.open_dataset(
   ...:     'airtemps.zarr',
   ...:     chunks={},
   ...:     from_array_kwargs={
   ...:         'manager': 'cubed',
   ...:         'spec': Spec(work_dir="tmp", max_mem=20e6),
   ...:     }
   ...: )
/home/tom/Documents/Work/Code/xarray/xarray/backends/plugins.py:139: RuntimeWarning: 'netcdf4' fails while guessing
  warnings.warn(f"{engine!r} fails while guessing", RuntimeWarning)
/home/tom/Documents/Work/Code/xarray/xarray/backends/plugins.py:139: RuntimeWarning: 'scipy' fails while guessing
  warnings.warn(f"{engine!r} fails while guessing", RuntimeWarning)

In [4]: ds['air']
Out[4]:
<xarray.DataArray 'air' (time: 2920, lat: 25, lon: 53)>
cubed.Array<array-004, shape=(2920, 25, 53), dtype=float32, chunks=((730, 730, 730, 730), (13, 12), (27, 26))>
Coordinates:
  * lat      (lat) float32 75.0 72.5 70.0 67.5 65.0 ... 25.0 22.5 20.0 17.5 15.0
  * lon      (lon) float32 200.0 202.5 205.0 207.5 ... 322.5 325.0 327.5 330.0
  * time     (time) datetime64[ns] 2013-01-01 ... 2014-12-31T18:00:00
Attributes:
    GRIB_id:       11
    ...

In [5]: ds.isel(time=slice(100, 300)).to_zarr("cubed_subset.zarr")
/home/tom/Documents/Work/Code/xarray/xarray/core/dataset.py:2118: SerializationWarning: saving variable None with floating point data as an integer dtype without any _FillValue to use for NaNs
  return to_zarr(  # type: ignore
Out[5]: <xarray.backends.zarr.ZarrStore at 0x7f34953033c0>

I would like to get to the point where you can use xarray with a chunked array without ever importing dask. I think this PR gets very close, but that would be tricky to test because cubed depends on dask (so I can't just run the test suite without dask in the environment

I just released Cubed 0.6.0 which doesn't have a dependency on Dask, so this should be possible now.

I just released Cubed 0.6.0 which doesn't have a dependency on Dask, so this should be possible now.

Does this mean my comment https://github.com/pydata/xarray/pull/7019#discussion_r970713341 is valid again?

Does this mean my comment https://github.com/pydata/xarray/pull/7019#discussion_r970713341 is valid again?

Yes I think it does @headtr1ck - thanks for the reminder about that.
I now want to finish this PR by exposing the "chunk manager" interface as a new entrypoint, copying the pattern used for xarray's backends. That would allow me to move the cubed-specific CubedManager code into a separate repository, have the choice of chunkmanager default to whatever is installed, but ask explicitly what to do if multiple chunkmanagers are installed. That should address your comment @headtr1ck.

Thanks for the review @dcherian! I agree with basically everything you wrote.
The main problem I have right now is non-reproducible failures as described here

I'm made a bare-bones cubed-xarray package to store the CubedManager class, as well as any integration tests (yet to write). @tomwhite you should have an invitation to be an owner of that repo. It uses the entrypoint in this PR to hook in, and seems to work for me locally :grin:

I'm having problems with ensuring the behaviour of the chunks='auto' option is consistent between .chunk and open_dataset. These problems appeared since vendoring dask.array.core.normalize_chunks. Right now the only failing tests use chunks='auto' (e.g xarray/tests/test_backends.py::test_chunking_consintency[auto] - yes there's a typo in that test's name), anad they fail because xarray decides on different sizes for the automatically-chosen chunks.
What's weird is that all tests pass for me locally but fail on just some of the CI jobs (and which CI jobs is not even consistent apparently???). I have no idea why this would behave differently on only some of the CI jobs, especially after double-checking that array-chunk-size is being correctly determined from the dask config variable within normalize_chunks.

I'm having problems with ensuring the behaviour of the chunks='auto' option is consistent between .chunk and open_dataset

Update on this rabbit hole: This commit to dask changed the behaviour of dask's auto-chunking logic, such that if I run my little test script test_old_get_chunk.py on dask releases before and after that commit I get different chunking patterns:

from xarray.core.variable import IndexVariable
from dask.array.core import normalize_chunks    # import the
import itertools

from numbers import Number
import dask
import dask.array as da
import xarray as xr
import numpy as np

# This function is copied from xarray, but calls dask.array.core.normalize_chunks
# It is used in open_dataset, but not in Dataset.chunk
def _get_chunk(var, chunks):
    """
    Return map from each dim to chunk sizes, accounting for backend's preferred chunks.
    """

    if isinstance(var, IndexVariable):
        return {}
    dims = var.dims
    shape = var.shape

    # Determine the explicit requested chunks.
    preferred_chunks = var.encoding.get("preferred_chunks", {})
    preferred_chunk_shape = tuple(
        preferred_chunks.get(dim, size) for dim, size in zip(dims, shape)
    )
    if isinstance(chunks, Number) or (chunks == "auto"):
        chunks = dict.fromkeys(dims, chunks)
    chunk_shape = tuple(
        chunks.get(dim, None) or preferred_chunk_sizes
        for dim, preferred_chunk_sizes in zip(dims, preferred_chunk_shape)
    )
    chunk_shape = normalize_chunks(
        chunk_shape, shape=shape, dtype=var.dtype, previous_chunks=preferred_chunk_shape
    )

    # Warn where requested chunks break preferred chunks, provided that the variable
    # contains data.
    if var.size:
        for dim, size, chunk_sizes in zip(dims, shape, chunk_shape):
            try:
                preferred_chunk_sizes = preferred_chunks[dim]
            except KeyError:
                continue
            # Determine the stop indices of the preferred chunks, but omit the last stop
            # (equal to the dim size).  In particular, assume that when a sequence
            # expresses the preferred chunks, the sequence sums to the size.
            preferred_stops = (
                range(preferred_chunk_sizes, size, preferred_chunk_sizes)
                if isinstance(preferred_chunk_sizes, Number)
                else itertools.accumulate(preferred_chunk_sizes[:-1])
            )
            # Gather any stop indices of the specified chunks that are not a stop index
            # of a preferred chunk.  Again, omit the last stop, assuming that it equals
            # the dim size.
            breaks = set(itertools.accumulate(chunk_sizes[:-1])).difference(
                preferred_stops
            )
            if breaks:
                warnings.warn(
                    "The specified Dask chunks separate the stored chunks along "
                    f'dimension "{dim}" starting at index {min(breaks)}. This could '
                    "degrade performance. Instead, consider rechunking after loading."
                )

    return dict(zip(dims, chunk_shape))

chunks = 'auto'
encoded_chunks = 100
dask_arr = da.from_array(
    np.ones((500, 500), dtype="float64"), chunks=encoded_chunks
)
var = xr.core.variable.Variable(data=dask_arr, dims=['x', 'y'])

with dask.config.set({"array.chunk-size": "1MiB"}):
    chunks_suggested = _get_chunk(var, chunks)
    print(chunks_suggested)

(cubed) tom@tom-XPS-9315:~/Documents/Work/Code/dask$ git checkout 2022.9.2
Previous HEAD position was 7fe622b44 Add docs on running Dask in a standalone Python script (#9513)
HEAD is now at 3ef47422b bump version to 2022.9.2
(cubed) tom@tom-XPS-9315:~/Documents/Work/Code/dask$ python ../experimentation/bugs/auto_chunking/test_old_get_chunk.py
{'x': (362, 138), 'y': (362, 138)}
(cubed) tom@tom-XPS-9315:~/Documents/Work/Code/dask$ git checkout 2022.9.1
Previous HEAD position was 3ef47422b bump version to 2022.9.2
HEAD is now at b944abf68 bump version to 2022.9.1
(cubed) tom@tom-XPS-9315:~/Documents/Work/Code/dask$ python ../experimentation/bugs/auto_chunking/test_old_get_chunk.py
{'x': (250, 250), 'y': (250, 250)}

(I was absolutely tearing my hair out trying to find this bug, because after the change normalize_chunks became a pure function, but before the change it actually wasn't, so I was trying calling normalize_chunks with the exact same set of input arguments and was still not able to reproduce the bug :angry: )
Anyway what this means is as this PR vendors dask.array.core.normalize_chunks, but the behaviour of dask.array.core.normalize_chunks changed between the version in CI job min-all-deps and the other CI jobs, the single vendored function cannot possibly match both behaviours.
The easiest way to fix this failure should be to upgrade the minimum version of dask to >=2022.9.2 (from 2022.1.1 where it currently is).

We could still achieve the goal of running cubed without dask by making normalize_chunks the responsibility of the chunkmanager

Seems OK to me.
The other option is to xfail the broken tests on old dask versions

I would like to merge this now please! It works, it passes the tests, including mypy. (RTD built the docs but then timed out, don't know what's going on there).
The main feature not in this PR is using parallel=True with open_mfdataset, which is still coupled to dask.delayed - I made #7811 to track that so I could get this PR merged.
If we merge this I can start properly testing cubed with xarray (in cubed-xarray).
@shoyer @dcherian if one of you could merge this or otherwise tell me anything else you think is still required!

(Okay now the failures are from https://github.com/pydata/xarray/pull/7815 which I've separated out, and from https://github.com/pydata/xarray/pull/7561 being recently merged into main which is definitely not my fault :sweat_smile: https://github.com/pydata/xarray/pull/7019/commits/316c63d55f4e2c317b028842f752a40596f16c6d shows that this PR passes the tests by itself.)

@Illviljan thanks for all your comments!
Would you (or @keewis?) be willing to approve this PR now? I would really like to merge this so that I can release a version of xarray that I can use as a dependency for cubed-xarray.

Woooo thanks @dcherian !

👏 Congrats @TomNicholas on getting this in! Such an important contribution. 👏

Thanks for all your hard work on this @TomNicholas!


Circle of the Night bug fixes and Water Elemental

Circle of the Night:

Fix bug that makes wild shape form drop after a few seconds
Implement Water Elemental based off Air Elemental sprite.

Seems it was already fixed. Ignore this!


Create new Docker network coc_network and let Docker services join

Close #28

Create new Docker network coc_network and let Docker services join network.
This is issue also exists for the CoC Frontend (Human-Connection/Clock-of-Change-Frontend#5). If both are merged, Backend and Frontend are in the same network an can access each other.

Perfect! :)


Fix unique rule

The unique rule fix in #4 requires parameters, to fix the issue a colon needed to be added to the end. Sorry I didn't spot this was missing in the previous PR.

@jonathandey it shouldn't after https://github.com/wintercms/storm/commit/f63c515890b939f5e14749a59bea1023f33428c3. Do you have that commit applied locally?

@jonathandey it shouldn't after wintercms/storm@f63c515. Do you have that commit applied locally?

Thanks, @LukeTowers; this does fix the issue! I will close the PR.


[Test] Fix the wrong subsitution of swift-frontend-target in tests

There is no %swift-frontend-target subsitution in test, which is actually %target-swift-frontend. The wrong spelling is actually interpruted by lit as %swift-frontend-target, and surprising didn't break any tests as the last argument from subsitution is -define-availability so it just leads to an very akward availability definition.

@swift-ci please smoke test

@swift-ci please smoke test

That's a hilarious bug.


[Question] Running error report missing package matplotlib

Before asking

[X] I have read the How to ask for help (我已阅读如何寻求帮助指引文档).

Your environment

Linkis version used: 1.1.2
Environment name and version:

cdh-5.14.2
hdp-3.1.5
hive-2.1.1
spark-3.2.1
scala-2.12.2
jdk 1.8.0_121
....

Describe your questions
Running error report missing package matplotlib
Eureka service list

eg:
Some logs info or acctch file

linkis-xxx.log:

<!--日志文字贴到这里-->

log file:

linkis-xxx.log

In the standard environment, you need to install the matplotlib python module, or you can install the anaconda version of python, which contains most of the common python libraries.
标准的环境，需要安装好matplotlib  python模块，或者可以安装python的anaconda版本这里面包含了常见大多数python库。


why not multiply ray step size when volume rendering.

Hi, thanks for this great code.
I have a puzzle, in your code,  https://github.com/apchenstu/mvsnerf/blob/6e0111188ff92b13229482a95a2fb4eaddbc2971/renderer.py#L22
the 'sigma' not multiply step size 'dist', which is different  in Ep(8) in your paper.
By the  way ,the origin NeRF:
https://github.com/yenchenlin/nerf-pytorch/blob/62da0b218b41573535a59ac1a38e9aeb840385a2/run_nerf.py#L275
raw2alpha = lambda raw, dists, act_fn=F.relu: 1.-torch.exp(-act_fn(raw)*dists)
https://github.com/yenchenlin/nerf-pytorch/blob/62da0b218b41573535a59ac1a38e9aeb840385a2/run_nerf.py#L293
alpha = raw2alpha(raw[...,3] + noise, dists)  # [N_rays, N_samples]
Any help will be greatly appreciated!

Do you solve the problem?I have the same question

ok!I get!


Value Error Problem

Hi Silviu,
Thank you very much for your useful code! Does ai_feynman requires the NVIDIA Graphic Card? Are there any other HW/SW requirements?
I am an author of Eureqa: software review you cited in your publication. I tried your code on my PC but at the end the ValueError of fname appeared (the same as KPL-T wrote in Issue#3). I tried to find the possible problem: In the script S_symmetry.py where command torch.cuda.is_available() returns 'False' for me. I don't have NVIDIA Graphic Card, so Cuda can't run on my PC. Could be this hardware the explanation of my problem? Is there any possibility to run you software without NVIDIA GPU?
Thank you in advance.
Renata
The error:
fh = iter(fname)
TypeError: 'int' object is not iterable
...............
During handling of the above exception, another exception occurred:
raise ValueError('fname must be a string, file handle, or generator')
ValueError: fname must be a string, file handle, or generator

Hello Renata,
Thank you for the message and your interest in our code and I am sorry for the late reply. The code is mainly build to run using CUDA, but if that is not found, it should just run on the CPU (although probably much slower at the NN part). However, I found a bug that at a point it was forcing the code to run on CUDA and I fixed it. If the error you got was because of that the code should be working now. I don't think there are any requirements for the code, other than the ones in requirements.txt. Please let me know if you find other bugs or encounter any other issues (we are still adding features to the code, so things could easily break without us realizing immediately).


small fix of the build instructions for the .s files in the examples/ folder; add new lines

Hi. Great project!
I've just tested all examples, and they work on my machine as well (Ubuntu 20.04, CPU: i3-3225).
This PR just makes building them a little bit easier, by just copy/pasting the comment at the top of each example.

Thanks!


ion-datetime does not work when displayFormat="M" and initial value is null

Ionic version:  (check one with "x")
[ ] 1.x (For Ionic 1.x issues, please use https://github.com/ionic-team/ionic-v1)
[ ] 2.x
[x ] 3.x
I'm submitting a ...  (check one with "x")
[x] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:

ion-datetime does not work when displayFormat="M" and initial value is null. When the user selects a different value the model is not changed
See https://plnkr.co/edit/R8h9cw?p=preview
Note that everything works if you set:

displayFormat to smth else, for example "YYYY"
OR
set initial value to a valid datetime ISO string

Expected behavior:

ion-datetime should change its value as expected when the user chooses new value in the picker
Steps to reproduce:

See https://plnkr.co/edit/R8h9cw?p=preview
Related code:
See See https://plnkr.co/edit/R8h9cw?p=preview

Hello! Thank you for opening an issue with us!
This works the same way if you use days instead of months. I believe it works properly with years but not with months or days because at least with years you have the bare minimum of information required to create an actual Date.
I will mark this as something to look at after the initial Ionic v4 release. To help us better understand your requirements, can you reply with a use case for this? Everything I can think of would probably be better handled, for example, by just having a select list where the user picks a month, but you could easily be attempting to accomplish something I am not thinking of, so a use case would be very helpful.
Thank you for using Ionic

The use case is to have a credit card expiration controls - one for month and the other for year.
The month control should allow selecting a value between 1 to 12. Right now it does not work as I described initially unless I provide an initial value

OK, thank you.
A couple of workarounds in the meantime.
I don't know what the UI of your app looks like, but as a user of applications I would rather just enter the expiration date as a single thing as such:
    <ion-item>
      <ion-label>Date:</ion-label>
      <ion-datetime displayFormat="M/YYYY" pickerFormat="M YYYY"></ion-datetime>
    </ion-item>

If this has to be two separate controls for some reason you could also use a couple of selects and build the date from there.
Just some thoughts.

I also thought about single control for the entire expiration date however these to be separate. So this could be either two ion-select or smth else... or i will need to initialize the existing control with some default value. Thank you for the suggestions!

After internal discussions, the issue comes down to the fact that you cannot create a Date without the year. You can start with just the year and default the month to Jan 1st, or take a year and month and default to the first day of the month, etc.
So the only valid generic way to do this would be to have the user supply an initial seed date, which you already have to do.


Text editor plugin parsing issue

I am seeing and issue when Text editor's child plugin name/label contain > character.
I have also reproduced the issue on the Aldryn demo site:
Works fine in "Edit" mode:

However, published page does not work properly:

The button plugin is as simple as it could be:

I believe the issues is that on published pages, for some reason, the text is not escaped anymore, leading to the regular expressions un Text plugin's utils to not match the full placeholder.
Apart from pointing the issue, I was curious - why is this happening only on published pages?

Actually, the edit mode behaves correctly as https://github.com/aldryn/aldryn-bootstrap3/blob/master/aldryn_bootstrap3/templates/aldryn_bootstrap3/plugins/button.html#L23 is not being escaped. You'd have to add the appropriate template tag to {{ instance.label }} like {{ instance.label| escape }}.
I'm wondering what the structure board does, are strings there automatically escabed @divio/django-cms-core ? https://github.com/divio/django-cms/blob/develop/cms/templates/cms/toolbar/plugin.html#L3

@FinalAngel I do not think there is an issue at all on the plugin side. The difference seems to be in the way the placeholder is generated in Text plugin's body.
For example, the placeholder looks like this when viewing in "Edit" mode:

But when looking at published page, the placeholder reads:
 test" title="Link Button - asdf > test" src="/static/cms/img/icons/plugins/link.png">

I am looking at the instance.body in djangocms_text_ckeditor/cms_plugins.py, render function.
Because the > symbol is kept unescaped on the live page, the regular expressions:
OBJ_ADMIN_RE_PATTERN = r']*\bid="plugin_obj_(\d+)"[^>]*/?>'

in the text plugin's utils.py do not work anymore.

This was fixed on djangocms-text-ckeditor 3.2+


update manifest for kernel-5.15.74 rebase

adding new tag lts-v5.15.74-20221108-r1

Expected syntax:
Commit message one-line summary
  Extra paragraphs can be added here.

  Longer description that explains the problem / solution
  or whatever that needs to be said

  It can contain
    multiple lines
    multiple paragraphs
    blank lines
    references

  But each paragraph must be followed by a blank line

  However, you need to keep the 'Tracked-On', 'Change-Id',
  'Signed-off-by', ..., fields in the **lastest** paragraph of
  the commit message.

  Change-Id: I9e58f79c7faf7f0edb9792e8b5322ab161331141
  Tracked-On: https://jira.server.ext/browse/PROJECTA-123
  Signed-off-by: Developer Name<EMAIL_ADDRESS>


fix: stripPrefix middleware with empty resulting path.

What does this PR do?
Add an option to allow to bypass the buggy behavior of the stripPrefix middleware.
Motivation
when the resulting striped path is empty, the path must be empty and not  /
More

[x] Added/updated tests
[x] Added/updated documentation

Should each middleware have its own func ensureLeadingSlash(str string) string?
Is that something that could be provided by a base middleware utility/tools package? just so that we don't end up with one middleware behaving differently?

Should each middleware have its own func ensureLeadingSlash(str string) string?
Is that something that could be provided by a base middleware utility/tools package? just so that we don't end up with one middleware behaving differently?

If we do that, we should have a func (name) that does not mislead about what it actually does :-)

for now I will not factorize.


Using Arc<[T]> instead of Arc<Vec<T>>.

This change is

crates/cairo-lang-language-server/src/ide/completion/completions.rs line 135 at r1 (raw file):

        ResolvedConcreteItem::Module(module_id) => db
            .module_items(module_id)
            .ok()?

Why is it ok to early return here?
Code quote:
 .ok()?

crates/cairo-lang-syntax/src/node/iter.rs line 36 at r1 (raw file):

struct PreorderLayer {
    start: SyntaxNode,
    children: Option<(Arc<[SyntaxNode]>, usize)>,

Why did you add another argument?
does the slice not have a length?
Code quote:
, usize


Added odd.codes

Hey, it's The Librarian from Merveilles. 😺 📙
Just starting to put the website together into something. It's not great, but I'm working on it!
Thanks!

Hey :) It's good to see a PR from you, although your website is too early to be added, make another PR once it has a few more pages.

Hey, no problem 🎃
I still have a lot to learn about web design. Games are my comfort zone.
I'm not giving up though. In fact, I'm just going to keep trying til I get it right!
The reason I was inspired to buy that domain and start posting my work was my acceptance into Merveilles, and I won't truly feel like I belong until I have something worth being accepted into the webring.
I will get better, I'll try again next month!

Looking forward :)


not able to download the nltk data in my macbook

I am trying to download nltk data in my laptop but its always showing error with the server or else timeout
i have have tried many ways but its the same thing ,
while trying in jupyter notebook i am getting this below error:

, can any please help me to solve this as i have a submission to make

The links which you have shared are not opening in my tab, Moreover I saw an error while I was using nltk.download() in the terminal and there should be a pop-up right, but in my system when I give this command, the pop-up does not open it's just loading all the time and when the time-out error comes then the pop-up is been seen , then it does not work

Other users of NLTK have experienced issues connecting to raw.githubusercontent.com pages, primarily users from certain internet providers in India.
See for example this comment: https://github.com/nltk/nltk/issues/3092#issuecomment-1371790700
Some ideas are to use VPNs, change your DNS setting, changing your network, or using mobile hotspot.
I hope it works with any of these solutions. I'm afraid there isn't much we can do about it: it seems like certain DNS has issues with raw.githubusercontent.com, which is out NLTK data host. Here are some other links that may help:

https://community.home-assistant.io/t/dns-issue-unable-to-connect-to-raw-githubusercontent-com/235474
https://github.com/orgs/community/discussions/32889
https://www.debugpoint.com/failed-connect-raw-githubusercontent-com-port-443/

just try those steps here (https://www.nltk.org/data.html)


netscanner: 0.4.1 -> 0.4.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/Chleba/netscanner/releases.
meta.description for netscanner is: Network scanner with features like WiFi scanning, packetdump and more
meta.homepage for netscanner is: https://github.com/Chleba/netscanner
meta.changelog for netscanner is: https://github.com/Chleba/netscanner/releases/tag/v0.4.2
Updates performed

Rust version update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.4.2 with grep in /nix/store/db3nixa9b0rm1w9d0zapbnqd9l8fs6bl-netscanner-0.4.2
found 0.4.2 in filename of file in /nix/store/db3nixa9b0rm1w9d0zapbnqd9l8fs6bl-netscanner-0.4.2

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
netscanner

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/db3nixa9b0rm1w9d0zapbnqd9l8fs6bl-netscanner-0.4.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A netscanner https://github.com/r-ryantm/nixpkgs/archive/97e276a9022d205ccad0a63bb87f03e9861b8361.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/97e276a9022d205ccad0a63bb87f03e9861b8361#netscanner

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/db3nixa9b0rm1w9d0zapbnqd9l8fs6bl-netscanner-0.4.2
ls -la /nix/store/db3nixa9b0rm1w9d0zapbnqd9l8fs6bl-netscanner-0.4.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

netscanner

Maintainer pings
cc @NotAShelf for testing.

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

1 package built:

netscanner


Remove unnecessary 'Back' text passed to back link component, as it's the default now.

When https://github.com/alphagov/govuk-frontend/pull/793 lands we can simplify the guidance around the back link component.

I think we shouldnt remove it from the docs until we know that people can figure out how to configure the Nunjucks macros easily.


How to pass  params out of the object ?

I need pass the param out of the object:
how can I do

Because I want predefine the  params conf , but now I found the params can only define in the object
If use want to  pass conf from file or config name, the fun can get the conf out of the object.

I want user can pass the trial_params from the main fun

Hi,
If your goal is to predefine constants for a part of the search space, you can pass the constants as follows.
import optuna

config = load_your_config()  # e.g., {'booster': 'dart'}

def objective(trial):
    params = {
        'silent': 1,
        'objective': 'binary:logistic',
        'booster': trial.suggest_categorical('booster', ['gbtree', 'gblinear', 'dart'])
                   if 'booster' not in config else config['booster'],
        'lambda': trial.suggest_loguniform('lambda', 1e-8, 1.0)
                  if 'lambda' not in config else config['lambda'],
        'alpha': trial.suggest_loguniform('alpha', 1e-8, 1.0)
                 if 'alpha' not in config else config['alpha']
    }
    score = run_your_experiment(params)
    return score

study = optuna.create_study()
study.optimize(objective, n_trials=10)
print(study.best_trial)

If you want to define the search space outside the objective function, Optuna currently does not support that style.
Please feel free to ask any additional questions.


New color option is missing on some config elements

Documentation Is:

[X] Missing or needed
[ ] Confusing
[ ] Not Sure?

Please Explain in Detail...
After the color option removing from Font object,  in some elements documentation, where font is used, is missing of new color option.
In the types definitions are missing as well.
Your Proposal for Changes
Add all missing options to the documentation and to the types.
I can try to prepare a PR about that (let me know).
Example
For instance, the Title. See below.
Title Configuration
The title configuration is passed into the options.plugins.title namespace. The global options for the chart title is defined in Chart.defaults.plugins.title.

Name
Type
Default
Description

align
string
'center'
Alignment of the title. more...

display
boolean
false
Is the title shown?

position
string
'top'
Position of title. more...

font
Font
defaults.font
See Fonts

padding
number|{top: number, bottom: number}
10
Adds padding above and below the title text if a single number is specified. It is also possible to change top and bottom padding separately.

text
string|string[]
''
Title text to display. If specified as an array, text is rendered on multiple lines.

I can try to prepare a PR about that (let me know).

Go for it!


improve aws tests

Motivation
Fixes

fix invalid parameter for PHP aws requests since weblog name contains a period: ., an illegal queue name character
explicitly set AWS_REGION to us-east-1.

Changes

Workflow

⚠ Create your PR as draft ⚠
Work on you PR until the CI passes (if something not related to your task is failing, you can ignore it)
Mark it as ready for review

Test logic is modified? -> Get a review from RFC owner. We're working on refining the codeowners file quickly.
Framework is modified, or non obvious usage of it -> get a review from R&P team

:rocket: Once your PR is reviewed, you can merge it!
🛟 #apm-shared-testing 🛟
Reviewer checklist

[ ] If PR title starts with [<language>], double-check that only <language> is impacted by the change
[ ] No system-tests internal is modified. Otherwise, I have the approval from R&P team
[ ] CI is green, or failing jobs are not related to this change (and you are 100% sure about this statement)
[ ] A docker base image is modified?

[ ] the relevant build-XXX-image label is present

[ ] A scenario is added (or removed)?

[ ] Get a review from R&P team

i guess it's still in progress? So I converted to draft. If no, please revert 😃

i guess it's still in progress? So I converted to draft. If no, please revert 😃

This is the full PR. Simply ensuring no periods and other special characters make it into the queue name

All system tests ci runs within each tracer's CI has been updated to include the new AWS env variables, can we get this merged?

Ive added info to the AWS authentication error message on how to setup authentication (it uses aws-vault, which is the DD preferred way to deal with AWS auth), should we also add a CLI argument to skip AWS tests? That way if users don't want to deal with AWS auth, and are running tests other than those using AWS within the two suites of INTEGRATIONS / CROSSED TRACING, they can easily skip it? I was thinking --skip-aws


🐞 --progress=plain output verbosity is higher in v0.12.0

What is the issue?
There were some work done to clean up the --progress=plain output to improve clarity in v0.11.x. However, it seems to have regressed in 0.12.0. Now the output displays codegen and introspection steps which can be considered noise in most instances.
Discord discussion: https://discord.com/channels/707636530424053791/1261532210205294702
Dagger version
dagger v0.12.0 (registry.dagger.io/engine) darwin/arm64
Steps to reproduce
Run dagger call mymodule --progress=plain
Log output
No response

Got a fix for this in #8018.
Also noticed that recently the plain progress has started looking quite odd - with spans magically re-appearing after completion. This is fixed in https://github.com/dagger/dagger/pull/7956.


Proposal: Add network ID to container inspect

Network names are not guaranteed to be unique (https://github.com/docker/docker/issues/18864). This is by design (https://github.com/docker/docker/issues/18864#issuecomment-167006094), but currently, it's not possible to identify which network a container is attached to.
I suggest to add the network ID to the output of docker inspect.

/cc @mrjana

I think this is a good idea to use network id instead of name, like network inspect , it uses container-id to differentiate containers.  @thaJeztah  if ok, I can claim this  :smile:

@wenchma I think the idea is to add the network-id to the details / properties. Replacing the name with the ID as "key" would be a breaking change (and a lot more difficult to, e.g. docker inspect --format ... to obtain the IP-address for, for example, the bridge network). Currently, a container cannot join two networks with the same name, so I think we should keep that as-is for now, so only add it to the details/properties of a network.
Would be great though if you can work on it :+1:

So, something like:
  "Networks": {
            "foobar": {
                "NetworkID": "2340984098234204",
                "EndpointID": "5e5cd696f66bfeddea4b26b8466b9bb32b973be10b439e9c6094249fc40d821f",
                "Gateway": "<IP_ADDRESS>",
                "IPAddress": "<IP_ADDRESS>",
                "IPPrefixLen": 16,
                "IPv6Gateway": "",
                "GlobalIPv6Address": "",
                "GlobalIPv6PrefixLen": 0,
                "MacAddress": "02:42:ac:12:00:03"
            }
}

@thaJeztah very glad to work on this. :smile:

Cool, I see API changes were merged

this PR https://github.com/docker/docker/pull/19243 will vendor the docker/engine-api which contains the https://github.com/docker/engine-api/pull/19 .
wait for the #19243

I guess it should be closed by https://github.com/docker/docker/pull/19323

ping @thaJeztah

@vieux you're right, it's merged.


Merge main for Calculation PR

Hey @skeate, this is the first draft to bring your PR closer to HEAD again.
I invested most time into src/compiler/checker.ts and I stumbled over three issues I'm not certain about:

    function getTypeAliasInstantiation(symbol: Symbol, typeArguments: readonly Type[] | undefined, aliasSymbol?: Symbol, aliasTypeArguments?: readonly Type[]): Type {
        const type = getDeclaredTypeOfSymbol(symbol);
        if (type === intrinsicMarkerType && typeArguments) {
            const typeKind = intrinsicTypeKinds.get(symbol.escapedName as string);
            if (typeKind !== undefined && typeArguments.length === 1) {
                return typeKind === IntrinsicTypeKind.NoInfer ? getNoInferType(typeArguments[0]) : getIntrinsicMappingType(symbol, typeArguments[0]);
            }
            if (typeKind !== undefined && typeArguments.length === 2) {
                return getIntrinsicMappingType2(symbol, typeArguments[0], typeArguments[1]);
            }
        }

In TypeScript HEAD they introduced the typeKind === IntrinsicTypeKind.NoInfer condition during my debugging I couldn't even figure out what its used for, I just reintegrated it into the case of typeArguments.length === 1 - maybe the case for two arguments should also contain it?

I just merged the unit tests, but didn't do anything besides npx hereby local... probably needs more work

(todo ... I will just send now, because I don't know if GitHub even handles more than 2k commits, it just loads indefinitely lol)

If you would risk to merge, It would be easier to make further PR's and discussions about the NoInfer question etc.
https://www.totaltypescript.com/noinfer

Another merge conflict again, they just reserved the last TypeFlag bit some days ago before it turns negative (1 << 31).toString(2)... didn't test yet if it still works out:
https://github.com/microsoft/TypeScript/pull/58610

Thank you!


fix null eldest in reset chain, which broke dannytest4

@buoyad / @chrisnojima this should be the fix.


5.1.0

This PR releases 5.1.0.
Note that I chose a minor bump because the set of changes since 5.0.0 includes the addition of an API.
Once this is approved and merged, I will tag and release the package for Rolling.

This PR releases 5.0.0.

5.1.0?

Note that I chose a minor bump because the set of changes since 5.0.0 includes the addition of an API.

I think technically we broke ABI here, but the 5.0.0 release just happened, so minor may be okay.

5.1.0?

Yes, sorry.  Typo, fixed now.

I think technically we broke ABI here, but the 5.0.0 release just happened, so minor may be okay.

I haven't typically been bumping major for ABI breaks (only for API breaks), but I don't feel strongly either way.


"MysqlDatabase" "MysqlUser" Add delete policy

add
"MysqlDatabase" "MysqlUser" Add delete policy
Sometimes deleting these resources is very dangerous, so adding a certain label can reduce data loss

review again。 @cndoit18

review again。 @cndoit18

Is there anything else to deal with? When can it be closed?

Is there anything else to deal with? When can it be closed? @cndoit18

need to wait for CI to pass

Is there anything else to deal with? When can it be closed? @cndoit18

need to wait for CI to pass

It looks like lint failed. Do I need to fix it? @cndoit18

@cndoit18 All ci passed.review again plz.

Hi, please add unit test

unit test is ready.review plz @cndoit18

Does it look conflicting? @cndoit18

Does it look conflicting? @cndoit18

hi, squash your commits, thx


Added login functionality

Functionality can be implemented in a better and efficient way for the same Try implementing jwt tokens


feat: remove all filter chip

Description
Removes the 'all' filter chip to better match with design standards around chips.
Video
https://user-images.githubusercontent.com/26950305/228976495-cd4d9b9e-7067-4877-876f-53e0767bb666.mov
Test plan

Tested locally in iOS and Android
DAppsExplorerScreenFilter.test.tsx updated

Related issues

N/A

Backwards compatibility
Yes

@reedeereed


config for pg4 experiments

                     NUM_TRAIN_TASKS     NUM_SOLVED AVG_NUM_PREDS AVG_TEST_TIME AVG_NODES_CREATED  LEARNING_TIME  NUM_SEEDS
EXPERIMENT_ID
cover-easy-pg3          50.00 (0.00)   50.00 (0.00)   0.00 (0.00)   0.01 (0.01)       0.00 (0.00)   36.32 (1.51)         10
cover-easy-pg4          50.00 (0.00)   50.00 (0.00)   5.00 (0.00)   0.01 (0.00)       6.15 (0.18)   35.89 (1.45)         10
cover-easy-plan-only    50.00 (0.00)   50.00 (0.00)   5.00 (0.00)   0.01 (0.00)       6.86 (0.11)    0.00 (0.00)         10
cover-pg3               50.00 (0.00)  38.60 (11.46)   0.00 (0.00)   0.01 (0.00)       0.00 (0.00)  49.05 (12.25)         10
cover-pg4               50.00 (0.00)   50.00 (0.00)   5.00 (0.00)   0.07 (0.02)       6.62 (1.19)  49.11 (12.87)         10
cover-plan-only         50.00 (0.00)   50.00 (0.00)   5.00 (0.00)   0.07 (0.02)       6.66 (0.32)    0.00 (0.00)         10

I can't approve this because I opened the PR, but consider it approved! let's collect and put all results in the PR description above, and then merge. @wester-is-not-real

actually I want to merge this now so we can run it on supercloud without changing the branch in the config. we can edit the PR description after it's merged.


Remove WithCurrentCulture (Resolves #862)

Don't we still need to chain ConfigureAwait(false) to each async call to avoid dealocks in UI apps?
If that was the case, I would suggest we went with a different approach which is to "#ifdef" the unnecessary code from WithCurrentCulture() out on specific platforms. We could then talk about renaming WithCurrentCulture() to something else, e.g. MakeThisAsyncCallWork() :smile:

Ah, I missed that part. :smile: This was just a desperate effort to try and get the tests passing on my machine. It didn't work. I'll leave the work for later since it's marked as pri1.

Re-openeing. Confirmed with @AndriySvyryd that ConfigureAwait isn't really needed on modern platforms.

P.S. If we do end up bringing this back. I propose we call it .MakeItSo()

:+1: at .MakeItSo() :smile:

:shipit:

Confirmed with @AndriySvyryd that ConfigureAwait isn't really needed on modern platforms.

Not sure what this means. ConfigureAwait is beneficial in all UI contexts, including modern ones.

@StephenCleary This is referring to modern platforms having async entry points/callbacks. And that as long as async methods are only invoked from other async methods ConfigureAwait(false) is not needed to prevent deadlocks.

That's only one purpose of ConfigureAwait(false).
ConfigureAwait(false) documents the code as not needing a context. Also, it is more efficient (when a context is present) - in particular, it prevents performance death by a thousand paper cuts.
And there are still scenarios where sync-over-async is necessary, and there likely will always be (think third-party library extension points / callbacks that are synchronous). ConfigureAwait(false) is still necessary to prevent deadlock in those scenarios.

@StephenCleary We handle those scenarios by offering a sync version of every method. Sync is faster that async even with ConfigureAwait(false) and it doesn't have any deadlock potential.
ConfigureAwait(false) litters the code, it's easy to forget to use it and could cause nonobvious issues where a series of library calls ends up invoking user code that does need context.

Yes, the synchronous versions handle the synchronous scenarios.
There's still the "paper cuts" issue - by that I mean that the general guidance is to not have more than a hundred continuations per second on a UI thread. This can be reached pretty quickly if there's deeply-nested async calls all of which resume on the context.
But it's pretty rare, and probably not worth the clutter that ConfigureAwait(false) would cause; if a user does run into that performance issue, they can call the asynchronous EF APIs outside of a UI context.


delete me

@iskakaushik @cyanglaz Please delete.  I intended to open this in a private fork for tracking a hotfix.


HADOOP-18492: upgrade commons-text to 1.10.0

Description of PR
How was this patch tested?
For code changes:

[x] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
[ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[x] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

+1 LGTM, jenkins pending

that's a bit optimistic for any dependency change. they always look good until the builds/tests run

+1 LGTM, jenkins pending

that's a bit optimistic for any dependency change. they always look good until the builds/tests run

Can't agree more :)

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
1m 13s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+0 :ok:
xmllint
0m  1s

xmllint was not available.

+0 :ok:
shelldocs
0m  1s

Shelldocs was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+0 :ok:
mvndep
15m 20s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
28m 39s

trunk passed

+1 :green_heart:
compile
26m 11s

trunk passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
22m 23s

trunk passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
mvnsite
20m 39s

trunk passed

+1 :green_heart:
javadoc
8m 43s

trunk passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
7m 28s

trunk passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
shadedclient
38m 32s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 33s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
25m 17s

the patch passed

+1 :green_heart:
compile
24m 57s

the patch passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
24m 57s

the patch passed

+1 :green_heart:
compile
22m 15s

the patch passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
22m 15s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
mvnsite
20m 15s

the patch passed

+1 :green_heart:
shellcheck
0m  0s

No new issues.

+1 :green_heart:
javadoc
8m 22s

the patch passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
7m 25s

the patch passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
shadedclient
39m 51s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
1036m 49s

root in the patch passed.

+1 :green_heart:
asflicense
2m 41s

The patch does not generate ASF License warnings.

1329m  4s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5007/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/5007

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient codespell detsecrets xmllint shellcheck shelldocs

uname
Linux 27998e6f7e3f 4.15.0-191-generic #202-Ubuntu SMP Thu Aug 4 01:49:29 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / fc34b37566b0dd9c5a62492433f94113a93ac81c

Default Java
Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5007/1/testReport/

Max. process+thread count
3344 (vs. ulimit of 5500)

modules
C: hadoop-project . U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5007/1/console

versions
git=2.25.1 maven=3.6.3 shellcheck=0.7.0

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

@ashutoshcipher CI build seems to have run ok

@ashutoshcipher CI build seems to have run ok

Yeah, Looks good. I

Just committed #5037 (which is seem as this PR) to trunk and mark 'Contributed by PJ Fanning'. Thanks all for your reviews.


Visual indication for todo with note

When using todolist l , it would be nice to indicate which todo entries have a note attached to it.
Maybe something like a * to indicate that the todo as more information than what is actually shown.

Something like this?

perhaps we put the word [Note] in the todo description, at the beginning?

I like the idea, added a POC. Might need some improvements.
Currently it'll look like the attached screenshot.
N for a note. * for a todo with priority.

this is fixed with #203


Feedback from user

It's terrible to navigate through.  I can't right-click and open details in a new window.  If I navigate backward, all my filters reset.
It would be nice to sort providers by earnings in the past 24 hours, and also how many tasks they've completed.
Add tasks completed historical information for the nodes.
4)Perhaps under historical, you could provide details about past jobs, such as accepted price, core/ram, etc.  Maybe how many jobs were completed in the past 24 hours as well?
The requestors section is pretty dead.  Are those "all time" tasks?  How about 24 hour, 7d, 30d?

https://discord.com/channels/684703559954333727/767706268651094036/1150849079769841714

"having a stats page to "find the best provider for your needs" would be very helpfull. I could advertise machines with a lot of memory for example (and find them). The cluster part (like provider with multiple interconnected machines with high bandwidth and low latency) is for later I think "
https://discord.com/channels/684703559954333727/767706268651094036/1151280223988494366


Questions about model evaluation

I have two questions regarding model evaluation:

Why is the frame to be evaluated (x) multiplied by 100 during call to modelwork function? isn't it affecting data normalization?
Is it supposed the data must be normalized before the call to sr_cnn_eval?

thank you in advance.

I realized that  gen_set class makes the same magnitude scaling to the data during training.


chore(package): update eslint to version 6.5.1

Closes #98

Coverage remained the same at 100.0% when pulling 8f763842d33b045bc0b01e1a026ab88c0456a42e on greenkeeper/eslint-6.5.1 into 2ef90cfd27b274ccf90f5f3bf330637cf14b50ff on master.

:tada: This PR is included in version 2.0.10 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Quick start and the book links on the readme are broken.

Potentially as a result of #81 since that's the only change that has landed since they were working.

Hey @JoshuaBatty, I haven't been able to use the doc from the domain before the linked PR. Also the issue for the domain name is still up: #77. And you can see that the run is sucessfull.

Closing this issue as this is duplicate of #77 and not related to the #81. Feel free to re-open if you think otherwise.