Improve deploy-from token id eerror validations

Is your feature request related to a problem? Please describe.
The default options for deploy from token-id fail requiring the usage of exotic flags and variables with no user feedbasck about this.
autonomy deploy from-token 1 keys.json --kubernetes
Building service deployment using token ID: 1
Fetching service metadata using chain type local
Error: Error connecting to the RPC

This should inform you that you need to set a variable at least, at best it shouldnt fail by default.
Describe the solution you'd like
Describe alternatives you've considered
Additional context

The error log says that the local chain is being used
Fetching service metadata using chain type local

And you don't need to export env var for using a local chain.
If you're using other chains like goerli or mainnet it does mention that you need to export an environment variable
autonomy mint --use-goerli protocol packages/valory/protocols/acn/ --key ~/_key
Error: RPC URL cannot be `None`, Please set the environment variable for goerli chain using `GOERLI_CHAIN_RPC` environment variable

and
autonomy mint --use-ethereum protocol packages/valory/protocols/acn/ --key ~/_key
Error: RPC URL cannot be `None`, Please set the environment variable for ethereum chain using `ETHEREUM_CHAIN_RPC` environment variable


Add event to organization that owns it

Please do work for this task in a branch called issue-XXX.

Done in branch issue-173 since this branch was behind by a lot of commits.


Revert /tmp to tmpfs

Podman really needs /tmp to be tmpfs, to detect and
handle reboots. Although there are (at this time) no
reboots involved in CI testing, it's still important
for CI hosts to reflect something close to a real-world
environment. And, there is work underway to check /tmp:
https://github.com/containers/podman/pull/22141
This PR removes special-case Fedora code that was
disabling a tmpfs /tmp mount. History dates back to
PR #30 back in 2020.
Some of the image-build code in this repo performs
reboots and relies on persistent tmp files, so you'll
note a flurry of /tmp -> /var/tmp changes.
And, as a drive-by, document the Windows Chocolatey
install command. Link to Best Practices, and explain
why we disregard some of those.
Signed-off-by: Ed Santiago<EMAIL_ADDRESS>

Retried three times, it's not a flake:
�[0;32m    win-server-wsl:  - golang - golang not installed. The package was not found with the source(s) listed.�[0m

Any Windows experts know what's going on with Chocolaty and Golang?

The git flake resolved itself, now it's back to golang failing. There's one difference which I think might be important, having to do with versions vs no-versions:
git flake:
win-server-wsl: Unable to resolve dependency: \
    Unable to find a version of 'git.install' that is compatible with 'git 2.44.0 constraint: \
    git.install (= 2.44.0)'.

go failure:
win-server-wsl: golang not installed. The package was not found with the source(s) listed.
(no version string at all)

Maybe the git flake was like a dnf cache delay, where packages just weren't refreshed in repos? git 2.44 is a month old, but maybe it only just got built for windows today. And maybe the golang problem is that golang just got completely removed from the chocolate thing?

@containers/podman-maintainers I give up. This needs a Windows expert.

@l0rd Any ideas?

YAY! Passed after enough retries!

20240326t173017z-f39f38d13
20240320t153921z-f39f38d13 ⇑ (built in #337)

debian
prior-fedora
fedora
fedora-aws
rawhide

base
13
38-1.6
39-1.5
?
41-0

kernel
6.7.9-2
6.7.9-100
6.7.10-200
6.7.9-200
6.9.0-0.rc0.20240322git8e938e398669.14

6.9.0-0.rc0.20240318gitf6cef5f8c37f.10 ⇑

aardvark-dns
1.4.0-5
1.10.0-1
1.10.0-1
1.10.0-1
1.10.0-1

netavark
1.4.0-4
1.10.3-1
1.10.3-1
1.10.3-1
1.10.3-3

1.10.3-2 ⇑

buildah
1.33.5+ds1-4+b1
1.34.0-1
1.35.1-1
1.35.0-1
1.35.0-1

1.33.5+ds1-4 ⇑

conmon
2.1.10+ds1-1+b1
2.1.10-1
2.1.10-1
2.1.10-1
2.1.10-1

container-selinux
?
2.230.0-1
2.230.0-1
2.230.0-1
2.230.0-1

2.228.1-1 ⇑

containers-common
?
1-89
1-99
1-99
0.58.0-4

0.58.0-1 ⇑

criu
3.17.1-3
3.18-1
3.19-2
3.19-2
3.19-4

crun
1.14.4-1
1.14.4-1
1.14.4-1
1.14.4-1
1.14.4-1

golang
2:1.22~3
1.21.8-1
1.21.8-1
1.21.8-1
1.22.1-1

gvisor-tap-vsock
?
0.7.3-1
0.7.3-1
0.7.3-1
0.7.3-2

nmap-ncat
7.94+git20230807.3be01efb1+dfsg-3+b1
7.93-2
7.94-1
7.94-1
7.94-1

passt
2024-03-20
2024-03-20
2024-03-20
2024-03-20
2024-03-20

2024-02-20 ⇑

podman
4.9.3+ds1-1+b1
4.9.3-2
4.9.3-1
4.9.3-1
5.0.0~rc6-2

4.9.3+ds1-1 ⇑

runc
1.1.12+ds1-2
1.1.12-1
1.1.12-1
1.1.12-1
1.1.12-3

skopeo
1.13.3+ds1-2+b1
1.15.0-1
1.15.0-1
1.14.2-1
1.14.2-2

1.13.3+ds1-2 ⇑
1.14.2-1 ⇑

slirp4netns
1.2.1-1+b1
1.2.2-1
1.2.2-1
1.2.2-1
1.2.2-2

systemd
255.4-1+b1
253.17-1
254.10-1
254.10-1
255.4-1

253.15-2 ⇑

tar
1.34+dfsg-1.2+deb12u1
1.34-8
1.35-2
1.35-2
1.35-3

@l0rd Any ideas?

Packages golang and git are available from the default source (community.chocolatey.org) and the community services were operational yesterday. The troubleshooting guide suggests to check the source but we use the default one so that doesn't look to be the problem. Adding --debug --verbose --noop to the choco install command may help to get more information next time.
Anyway chocolately scripting best practices suggest to use a slightly different command to install packages:
-- choco install -y --allow-downgrade --execution-timeout=300 $pkg
++ choco upgrade $pkg1 -y --source="'https://community.chocolatey.org/api/v2'" --allow-downgrade --execution-timeout=300

I don't think that this has anything to do with the problems above though.

/approve
/lgtm

/hold
Let's not merge until we see if this works. My two Podman PRs with these VMs have stuck in CI, twice. I don't know if it's a Cirrus problem or a problem with the VMs.

@cevich there's something broken somewhere. "Build for debian" is consistently hanging, not even getting started. So is Validate f39. AFAICS there is no indication of why they won't run. How can I debug this?

How can I debug this?

They're stuck in 'scheduled' mode.  Off-hand, these are container-based Cirrus-CI compute-based tasks.  We're not out of credits :thinking:  It's running now, so only thing I can think of is: Some kind of Cirrus-CI hiccup.

Not sure what you mean by "it's running now". Maybe you're referring to "this PR, the /tmp-tmpfs one in automation_images, is running now"? If so, that has nothing to do with anything. The not-running thing is two podman PRs using images I built yesterday. The running-now thing is maybe this PR (the one on which I'm commenting), which I re-pushed in desperation. Maybe yesterday's VMs didn't work because of the Windows outage. I dunno. I'll see what happens in a few minutes.

20240327t142743z-f39f38d13
20240102t155643z-f39f38d13 ⇑

debian
prior-fedora
fedora
fedora-aws
rawhide

base
13
38-1.6
39-1.5
?
41-0

40-0 ⇑

kernel
6.7.9-2
6.7.10-100
6.7.10-200
6.7.10-200
6.9.0-0.rc1.17

aardvark-dns
1.4.0-5
1.10.0-1
1.10.0-1
1.10.0-1
1.10.0-1

1.9.0-1 ⇑
1.9.0-1 ⇑
1.9.0-1 ⇑

netavark
1.4.0-4
1.10.3-1
1.10.3-1
1.10.3-1
1.10.3-3

1.9.0-1 ⇑
1.9.0-1 ⇑
1.9.0-1 ⇑

buildah
1.33.7+ds1-1
1.34.0-1
1.35.1-1
1.35.0-1
1.35.0-1

1.32.2+ds1-1 ⇑
1.33.2-1 ⇑
1.33.2-1 ⇑
1.33.2-1 ⇑
1.33.2-1 ⇑

conmon
2.1.10+ds1-1+b1
2.1.10-1
2.1.10-1
2.1.10-1
2.1.10-1

2.1.6+ds1-1 ⇑
2.1.8-2 ⇑
2.1.8-2 ⇑
2.1.8-2 ⇑
2.1.8-2 ⇑

container-selinux
?
2.230.0-1
2.230.0-1
2.230.0-1
2.230.0-1

2.226.0-1 ⇑
2.226.0-1 ⇑
2.226.0-1 ⇑
2.226.0-1 ⇑

containers-common
?
1-89
1-99
1-99
0.58.0-5

1-95 ⇑
1-95 ⇑
1-101 ⇑

criu
3.17.1-3
3.18-1
3.19-2
3.19-2
3.19-4

3.19-2 ⇑

crun
1.14.4-1
1.14.4-1
1.14.4-1
1.14.4-1
1.14.4-1

1.12-1 ⇑
1.12-1 ⇑
1.12-1 ⇑
1.12-1 ⇑
1.12-1 ⇑

golang
2:1.22~3
1.21.8-1
1.21.8-1
1.21.8-1
1.22.1-4

2:1.21~2 ⇑
1.20.12-1 ⇑
1.21.5-1 ⇑
1.21.5-1 ⇑
1.21.5-1 ⇑

gvisor-tap-vsock
?
0.7.3-1
0.7.3-1
0.7.3-1
0.7.3-2

0.7.1-1 ⇑
0.7.1-1 ⇑
0.7.1-1 ⇑
0.7.1-1 ⇑

nmap-ncat
7.94+git20230807.3be01efb1+dfsg-3+b1
7.93-2
7.94-1
7.94-1
7.94-1

7.94+git20230807.3be01efb1+dfsg-2 ⇑

7.93-3 ⇑
7.93-3 ⇑
7.93-4 ⇑

passt
2024-03-26
2024-03-20
2024-03-26
2024-03-20
2024-03-26

2023-12-04 ⇑
2023-12-04 ⇑

2023-12-04 ⇑
2023-12-04 ⇑

podman
4.9.3+ds1-1+b1
4.9.3-2
4.9.4-1
4.9.3-1
5.0.0-1

4.7.2+ds1-2 ⇑
4.7.2-1 ⇑
4.8.2-1 ⇑
4.8.1-1 ⇑
4.8.1-1 ⇑

runc
1.1.12+ds1-2
1.1.12-1
1.1.12-1
1.1.12-1
1.1.12-3

1.1.10+ds1-1 ⇑
1.1.8-1 ⇑
1.1.8-1 ⇑
1.1.8-1 ⇑
1.1.9-1 ⇑

skopeo
1.13.3+ds1-2+b1
1.15.0-1
1.15.0-1
1.14.2-1
1.14.2-2

1.13.3+ds1-2 ⇑
1.14.0-1 ⇑
1.14.0-1 ⇑
1.14.0-1 ⇑
1.14.0-1 ⇑

slirp4netns
1.2.1-1+b1
1.2.2-1
1.2.2-1
1.2.2-1
1.2.2-2

1.2.1-1 ⇑

1.2.2-1 ⇑

systemd
255.4-1+b1
253.17-1
254.10-1
254.10-1
255.4-1

255.2-3 ⇑

255.1-1 ⇑

tar
1.34+dfsg-1.2+deb12u1
1.34-8
1.35-2
1.35-2
1.35-3

1.35+dfsg-2 ⇑

1.35-2 ⇑

Not sure what you mean by "it's running now"

Oh my bad, I assumed those links were tasks in this repo.  I see they're in podman.  I just saw a re-push and now the replacement tasks are running over there.  This still seems like it was some temporary Cirrus-infra. hiccup.

BTW: I would strongly recommend testing these images beyond just podman CI.  Esp. buildah and skopeo.

@cevich nope, still broken. (That link right is to a podman debian-13 job, it is entirely gray, nothing happening on it whatsoever). Help please.

nope, still broken.

Gah!  Hmmmm :thinking:

Debian grub changed. Not by much, but apparently enough to cause a boot failure.

debian
prior-fedora
fedora
fedora-aws
rawhide

grub2-common
2.12-1+b1
2.06-116
2.06-118
2.06-118
2.06-119

2.12~rc1-12 ⇑

2.06-110 ⇑

Cause (not root): Boot failure

[0m[30m[47mWelcome to GRUB!

[0m[37m[40m[0m[30m[40m[2J[01;01H[0m[37m[40m[H[J[1;1Herror: file `/boot/grub/x86_64-efi/bli.mod' not found.

error: file `/boot/grub/x86_64-efi/bli.mod' not found.

IIRC, we're using a custom /usr/bin/version_find_latest for debian (see base_images/debian_base-setup.sh), could that somehow be involved?
Clearly the base-image is bootable (since cache-image stage is using it and not failing).  So it must be something going wrong there.  Anything jump out at you in the build logs?

I have reinstated the rm -rf /var/tmp/automation_images because, without it, all cache jobs fail:
==> fedora: Uploading /tmp/cirrus-ci-build/ => /var/tmp/automation_images
==> fedora: Upload failed: scp: /var/tmp/automation_images/SECURITY.md: Permission denied

Oh look, there's a new pasta (03-26) (only on some hosts)

20240328t122402z-f39f38d13
20240320t153921z-f39f38d13 ⇑ (built in #337)

debian
prior-fedora
fedora
fedora-aws
rawhide

base
13
38-1.6
39-1.5
?
41-0

kernel
6.7.9-2
6.7.10-100
6.7.10-200
6.7.10-200
6.9.0-0.rc1.20240326git928a87efa423.17

6.7.9-100 ⇑

6.7.9-200 ⇑
6.9.0-0.rc0.20240318gitf6cef5f8c37f.10 ⇑

grub2-common
2.06-13+deb12u1
2.06-116
2.06-118
2.06-118
2.06-119

2.12-1 ⇑
2.06-114 ⇑

aardvark-dns
1.4.0-5
1.10.0-1
1.10.0-1
1.10.0-1
1.10.0-1

netavark
1.4.0-4
1.10.3-1
1.10.3-1
1.10.3-1
1.10.3-3

1.10.3-2 ⇑

buildah
1.33.7+ds1-1
1.35.1-1
1.35.2-1
1.35.0-1
1.35.0-1

1.33.5+ds1-4 ⇑
1.34.0-1 ⇑
1.35.1-1 ⇑

conmon
2.1.10+ds1-1+b1
2.1.10-1
2.1.10-1
2.1.10-1
2.1.10-1

container-selinux
?
2.230.0-1
2.230.0-1
2.230.0-1
2.230.0-1

2.228.1-1 ⇑

containers-common
?
1-89
1-99
1-99
0.58.0-5

0.58.0-1 ⇑

criu
3.17.1-3
3.18-1
3.19-2
3.19-2
3.19-4

crun
1.14.4-1
1.14.4-1
1.14.4-1
1.14.4-1
1.14.4-1

golang
2:1.22~3
1.21.8-1
1.21.8-1
1.21.8-1
1.22.1-4

1.22.1-1 ⇑

gvisor-tap-vsock
?
0.7.3-1
0.7.3-1
0.7.3-1
0.7.3-2

nmap-ncat
7.94+git20230807.3be01efb1+dfsg-3+b1
7.93-2
7.94-1
7.94-1
7.94-1

passt
2024-03-26
2024-03-20
2024-03-26
2024-03-20
2024-03-26

2024-02-20 ⇑

2024-03-20 ⇑

2024-03-20 ⇑

podman
4.9.3+ds1-1+b1
4.9.3-2
4.9.4-1
4.9.3-1
5.0.0-1

4.9.3+ds1-1 ⇑

4.9.3-1 ⇑

5.0.0~rc6-2 ⇑

runc
1.1.12+ds1-2
1.1.12-1
1.1.12-1
1.1.12-1
1.1.12-3

skopeo
1.13.3+ds1-2+b1
1.15.0-1
1.15.0-1
1.14.2-1
1.14.2-2

1.13.3+ds1-2 ⇑
1.14.2-1 ⇑

slirp4netns
1.2.1-1+b1
1.2.2-1
1.2.2-1
1.2.2-1
1.2.2-2

systemd
255.4-1+b1
253.17-1
254.10-1
254.10-1
255.4-1

253.15-2 ⇑

tar
1.34+dfsg-1.2+deb12u1
1.34-8
1.35-2
1.35-2
1.35-3

Moved to draft until #342 merges.

20240401t112841z-f39f38d13
20240328t140922z-f39f38d13 ⇑ (built in #342)

debian
prior-fedora
fedora
fedora-aws
rawhide

base
13
38-1.6
39-1.5
?
41-0

kernel
6.7.9-2
6.7.10-100
6.7.11-200
6.7.10-200
6.9.0-0.rc1.20240329git317c7bc0ef03.20

6.7.10-200 ⇑

6.9.0-0.rc1.20240326git928a87efa423.17 ⇑

grub2-common
2.06-13+deb12u1
2.06-116
2.06-118
2.06-118
2.06-119

aardvark-dns
1.4.0-5
1.10.0-1
1.10.0-1
1.10.0-1
1.10.0-1

netavark
1.4.0-4
1.10.3-1
1.10.3-1
1.10.3-1
1.10.3-3

buildah
1.33.7+ds1-1
1.35.1-1
1.35.2-1
1.35.0-1
1.35.2-2

1.35.0-1 ⇑

conmon
2.1.10+ds1-1+b1
2.1.10-1
2.1.10-1
2.1.10-1
2.1.10-1

container-selinux
?
2.230.0-1
2.230.0-1
2.230.0-1
2.230.0-1

containers-common
?
1-89
1-99
1-99
0.58.0-5

criu
3.17.1-3
3.18-1
3.19-2
3.19-2
3.19-4

crun
1.14.4-1
1.14.4-1
1.14.4-1
1.14.4-1
1.14.4-5

1.14.4-1 ⇑

golang
2:1.22~3
1.21.8-1
1.21.8-1
1.21.8-1
1.22.1-4

gvisor-tap-vsock
?
0.7.3-1
0.7.3-1
0.7.3-1
0.7.3-2

nmap-ncat
7.94+git20230807.3be01efb1+dfsg-3+b1
7.93-2
7.94-1
7.94-1
7.94-1

passt
2024-03-26
2024-03-26
2024-03-26
2024-03-26
2024-03-26

podman
4.9.4+ds1-1
4.9.3-2
4.9.4-1
4.9.3-1
5.0.0-1

4.9.3+ds1-1+b1 ⇑

runc
1.1.12+ds1-2
1.1.12-1
1.1.12-1
1.1.12-1
1.1.12-3

skopeo
1.13.3+ds1-2+b1
1.15.0-1
1.15.0-1
1.15.0-1
1.14.2-2

1.14.2-1 ⇑

slirp4netns
1.2.1-1+b1
1.2.2-1
1.2.2-1
1.2.2-1
1.2.2-2

systemd
255.4-1+b1
253.17-1
254.10-1
254.10-1
255.4-1

tar
1.34+dfsg-1.2+deb12u1
1.34-8
1.35-2
1.35-2
1.35-3

[package versions are unchanged.  This must not merge until https://github.com/containers/podman/pull/22207 merges.

@edsantiago Did you test this out on all the other repos as well? skopeo, common, image, storage...
I think this has the risk to break on other repos as well and catching it only on the next (maybe urgent) update would be painful.

I will start opening PRs now on other repos.

repo
status

podman
pass

buildah
pass

skopeo
pass (except for blue-robot)

c-image
pass

c-storage
pass

c-common
fails lint, for reasons unlikely to be my fault

aardvark
FAIL integration - apparently a flake. Also fails all blue-robots

netavark
FAIL - some expected (nc bug), some not (integration)

Thanks @edsantiago, I comfortable merging then. I assume you want the podman PR merged first?

Thanks for all your efforts on this @edsantiago and @Luap99 :smiley:


Allow soft-complex->double coercion to run without gil

It'll only need the GIL on failure (which it can get) and "power of" type maths is the soft of thing that people are likely already doing in nogil blocks
Fixes https://github.com/cython/cython/issues/5274
This is the last of the fixes for things that I broke in 3.0.0b1 I believe

@scoder Can I tag this as the last remaining fix for significant regressions in Cython3b1.


Wiki is empty

Thanks for opening this issue! I'm planning to write these up over the long weekend. The guides will include screenshots.

Finished the MTA guide. Don't want this holding up the release since TAs are familiar with the software at this point. Deferring to the indefinite future.


Fixed Holes in Barriers and Wall Clipping

Updated:
-init_ritual_chamber.json to fix holes in laser-barriers and some clipping in one of the walls

This looks good to me!


[Bug] Full-width display not working for individual tweets

When the "full width display" for content is active, this is not honored for showing individual tweets:
View from the timeline:

View on the tweet itself:

ref: https://twitter.com/ESYudkowsky/status/1686093032301486080

+1
I'd also VERY much like full width to work on profile views & profile views with replies.

I don't usually use my timeline and I'm normally just reading Elon at https://twitter.com/elonmusk/with_replies


Volume Calculation Module

Space carving looks like an interesting theorem... link here,
http://citeseerx.ist.psu.edu/viewdoc/summary?doi=<IP_ADDRESS>.250 , http://stackoverflow.com/questions/7161209/determine-the-volume-of-an-object-from-pictures is a stack overflow question on the topic

Look at calculating volume by point cloud: changes in pixels can be used to calculate changes in height, then perform shitty integration to determine more accurate volume.

http://stackoverflow.com/questions/20314556/generating-point-cloud-from-many-2d-images
Point cloud question; top comment has some good papers and stuff.

Stuff we're discovered so far: RANSAC is solvable by opencv, with some proper set up, so I'm inclined towards that.
WE can also use a program called Visual SFM http://ccwu.me/vsfm/ that I think can create 3d reconstructions and be used to test our stuff, at least as a baseline. Need to sit down and diagram this out super hard as well, though... Do that when we have time soon.

Was just looking at CONOPS, doesn't look like this is technically still necessary

True, though I think it's worth keeping around and working on as a long-term part of the project since they'll probably re-introduce volume calculation in the future (though it makes me wonder if the only reason they had it last time was because of the company sponsoring the software).


AIY Project Vision Kit doesn't work

Hi,
I have tried the example for my Vision Kit, but it doesn't work. I have followed the guideline from:
https://blog.hackster.io/teething-troubles-for-the-new-aiy-projects-vision-kit-625ed4e9287a
$ cat /proc/cpuinfo | grep Revision
Revision	: 9000c1
$ sudo systemctl stop joy_detection_demo.service
$ sudo rmmod aiy_vision
rmmod: ERROR: Module aiy_vision is not currently loaded
$ sudo rmmod adc
rmmod: ERROR: Module aiy_adc is not currently loaded
Does it mean that there is error in booting the system? I have used the SD Image of 03/01/2018.
Many thanks for your help!
Matthew

Could you please share which example code did you try to run and which error message did you get?

Please reopen if you can provide requested details.

Hello,
I have exactly the same problem, do you have a solution?
Thank's


Simplify if x then True else y to x || y

Stumbled across it in my (old, shameful) code the other day, but the following simplifications could be added:
if foo then
    True
else
    bar

to
foo || bar

and similarly
if too then
    bar
else
    False

to
foo && bar

Should be easy to implement if you agree they should be, but don't want to put time into it if you disagree.  :smile:

Hmm, this is interesting. I like it, but I'd love some more external opinions (adding new kinds of simplifications to this existing rule can bother some people).
One thing though, I'm thinking that maybe the rule shouldn't do anything if there are comments anywhere inside the if, as the developer may have split it on purpose for readability purposes. What do you think?

I agree that not swallowing comments would probably be a good idea; if it's commented, presumably it's that way for readability and not developer oversight.  Though that would make it more of a challenge to implement, I would think?  Unless there's a clever way to check for comments in elm-syntax?  I assume you have to make a comment visitor to save all the locations and then pass that context to the expression visitor?

I assume you have to make a comment visitor to save all the locations and then pass that context to the expression visitor?

Yes exactly 👌 in practice I think that keeping the starting line numbers for each comment would be enough.

Yes exactly ok_hand in practice I think that keeping the starting line numbers for each comment would be enough.

Awesome, I actually need to do this for another rule, so I appreciate the input.  :rofl:

I'm also thinking that if you have an else if, in the second branch, this rule should not report anything
The example from the original comment:
if foo then
    True
else
    bar
--> turns into
foo || bar

With an else if
if foo then
    True
else if otherCondition then
    bar
else
    baz
--> would turn into
foo ||
    if otherCondition then
		bar
    else
	    baz

and I think this looks a bit odd.
I imagine the same thing to happen if in the second branch you have a let expression or case expression, because that would look quite odd and therefore not a likely improvement.

That seems reasonable to me.  It's only the base case that seems clearly made simpler by it.

Should this rule be part of the Simply rule?

We'd also need to check if one branch is a recursive call to not remove TCO by fixing to || or &&.


docs: changed bunx create-vite to bun create vite

#15629
Description
Documentation fix changing bunx to bun
What is the purpose of this pull request?

[ ] Bug fix
[ ] New Feature
[X] Documentation update
[ ] Other

@patak-dev


[AutoDiff] Improve leak checking test robustness.

Make testWithLeakChecking no longer stateful.
Without this patch, some leak-checking tests can impact the leak count
of other unrelated tests (perhaps due to concurrent testing).

@swift-ci Please test tensorflow

@swift-ci Please test tensorflow macOS

Thanks @pschuh for the idea!


Update version and history info for 'az quantum' extension 0.14.0

This checklist is used to make sure that common guidelines for a pull request are followed.


fix(EMI-2053): Hide register by signal on auction screen

This PR resolves EMI-2053
Description
This PR hides the Register By signal on the auction screen
it also fixes an issue with the data where some auctions have undefined as a price in rails
Screenshots
Register By signal fix

Before
After

Android

iOS

undefined issue

Before
After

PR Checklist

[X] I have tested my changes on iOS and Android.
[X] I hid my changes behind a feature flag, or they don't need one.
[X] I have included screenshots or videos, or I have not changed the UI.
[X] I have added tests, or my changes don't require any.
[X] I added an app state migration, or my changes do not require one.
[X] I have documented any follow-up work that this PR will require, or it does not require any.
[X] I have added a changelog entry below, or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

hide Register By signal on Auction screen + fix undefined on auction artwork rail cards - mrsltun

iOS user-facing changes

Android user-facing changes

Dev changes

Need help with something? Have a look at our docs, or get in touch with us.

This PR contains the following changes:

Cross-platform user-facing changes (hide Register By signal on Auction screen + fix undefined on auction artwork rail cards - mrsltun)

  Generated by :no_entry_sign: dangerJS against dd5bf74b599aec2adf394e63585c975f344a3edc


bend: 0.2.34 -> 0.2.36

Changelog: https://github.com/HigherOrderCO/Bend/blob/main/CHANGELOG.md#0236---2024-07-04
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

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

1 package built:

bend


Changing namespace separate so as to not conflict with virtual topic consumer prefix wildcards

There are some receive endpoints that we define as follows:
var host = cfg.Host(hostSettings);
cfg.ReceiveEndpoint(host, rcvCfg =>
{
    rcvCfg.Consumer<IConsumer<SecurityGroupChanged>>(context);
    rcvCfg.Consumer<IConsumer<UserChanged>>(context);
    rcvCfg.Consumer<IConsumer<InstanceUserChanged>>(context);
    rcvCfg.Consumer<IConsumer<InstanceChanged>>(context);
});

So more pub sub style. The problem, however, is that MassTransit generates the following virtual topic and associated consumer queue, as an example:
VirtualTopic.REFS.Platform.Instances.Interfaces.DomainEvents.SecurityGroupChanged
Consumer.endpoint-EC2AMAZ-KFCBO2P-REFS.Platform.Instances-ab4yyyn5ihfq6krjbdmjtt17dn.VirtualTopic.REFS.Platform.Instances.Interfaces.DomainEvents.SecurityGroupChanged
The default virtual destination defaults, which MassTransit is expecting are as follows:
VirtualTopic.> (this matches all topics prefixed with VirtualTopic.)
Consumer.*.VirtualTopic.> <-- this is the issue
The . is a path separator in ActiveMQ. The * wildcard only matches a single path. There is no good documentation that points to this, but we tested this by hand with ActiveMQ to validate that. As such, that generated consumer name has the namespace of the .NET type using . as the separator, which also being the ActiveMQ path separator, causes the consumer queue prefix match to fail. Hence this long explanation for a one character change.

I think I understand, but just to be clear. Is the behavior of pub/sub currently broken, or is this more of a visual convenience. I can see the benefit of the change, but not sure I get the resulting impact to people already using MT with ActiveMQ.

Actually, after playing around with unit tests, this change is not doing what I thought it was going to do, it's not changing the right thing. In the name of the consume queue, Consumer.endpoint-EC2AMAZ-KFCBO2P-REFS.Platform.Instances-ab4yyyn5ihfq6krjbdmjtt17dn is the problematic part, the end is fine. REFS.Platform.Instances is specifically where the issue is. That is the name of our EXE. The ConsumeTopology.CreateTemporaryQueueName() method is generating this and is using Char.IsLetterOrDigit to filter out characters. Turns out that . is valid because it is a decimal char. So if your EXE is named without a period, everything is fine. If it does have one, you hit this issue with pub/sub. I've made an updated, reverting my previous change and overriding that method in the ActiveMqConsumeTopology class.

That IsLetterOrDigit always screws me dang it.

Do you need anything else from me on this one?

No, I think it's ready to go, I just need to get around to pulling it into the code.

Not really fond of the way you removed the '.' from the string, wouldn't have done it that way, but it's fine.


Custom view modifier for poster images

It's not actually less code, but it does remove duplication...

Not to self: move them to views/modified with a relevant file name when using them in more than 1 file.
I’ll merge that because it’s a good example and foundation for me to build on other part of the apps!


ghcWithPackages: rename withLLVM to useLLVM

useLLVM is what we are using in the GHC derivations already -- for
better or for worse -- so we should rename the argument here for
consistency which we are free to do as this is purely internal at the
moment (with overriding being impossible).

Motivation for this change
Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

@ofborg build tests.haskell


Can't open /home/chronos/user/Downloads/crouton

I'm typing in "sudo sh -e ~/Downloads/crouton -t xfce" after typing in shell and I'm getting that error. I want to download Linux so I can play Undertale, but it doesn't seem to be working. Help?

@Aarca -
Please make sure you've actually downloaded 'crouton' and placed it in ~/Downloads
You can get it from here - https://goo.gl/fd3zc
-DennisL


reference: Added markdown example (with image support).

As the title suggest, this pull request aims to add a simple markdown viewer example to reference examples section.
Rationale:
a) Markdown package does not have any example code in the references section and b) even the existing code elsewhere (e.g., in TheIDE) does not demonstrate the following features of plugin/md package:

Basic way of handling and displaying (local) images.
Copying the resulting qtf data to clipboard so that it can be used elsewhere.

A screenshot of the example, displaying Bobcat's README file.

Please review.

Good idea! Markdown reference is definitly need, as markdown is very popular text file format.


Add command to install the Azure CLI

fixed with https://github.com/Microsoft/vscode-azurecli/pull/18


Report Sidekiq jobs that call other jobs

Is your feature request related to a problem? Please describe.
The New Relic Ruby agent cannot accurately report on Sidekiq jobs that call other jobs.
For example, if I invoke the following code using OutsideJob.perform_later, InsideJob would be the name of the transaction, and OutsideJob would not appear as a transaction or as a segment within another transaction.
class OutsideJob < ApplicationJob
  queue_as :high

  def perform
    NewRelic::Agent::Tracer.start_transaction_or_segment(name: 'OutsideJob', category: :background) do
      puts "OutsideJob: start"
      InsideJob.perform_now
      puts "OutsideJob: finish"
    end
  end
end

class InsideJob < ApplicationJob
  queue_as :high

  def perform
    puts "InsideJob: start"
    sleep 1
    puts "InsideJob: finish"
  end
end

Feature Description
Sidekiq jobs that call other Sidekiq jobs are reported to New Relic.
Using the scenario above as an example, OutsideJob will be used as the root of a non-web transaction and InsideJob will be a segment/span nested within the OutsideJob transaction.
Describe Alternatives
If someone encounters this problem, try using custom instrumentation to set the correct transaction name. We suggest you explore:

add_transaction_tracer
NewRelic::Agent::Tracer.start_transaction_or_segment

However, we have not tested these APIs with this scenario, so YMMV.
Additional context
Internal - Slack
Priority
TBD

May be related to: https://github.com/newrelic/newrelic-ruby-agent/issues/2195

This issue is scoped to setting up an integration test for this particular scenario once the work in #2195 is complete.

Related to: https://github.com/newrelic/newrelic-ruby-agent/issues/2835


Barcode Scan on iOS is in developing?

Sorry, but I'm not an iOS developer. I need someone to help with this.

Duplicated #6


[WIP] container

finish docker-compose and the containerization of the entire app. Right now only the db launches a postgresDB container.

fixed in edbb781b8c7b60296a5db7f9b46027fc35d1e305


Revert "KOGITO-3055  Refactor Quarkus Extension (#688)"

This reverts commit bece507d
Many thanks for submitting your Pull Request :heart:!
Please make sure that your PR meets the following requirements:

[ ] You have read the contributors guide
[ ] Pull Request title is properly formatted: KOGITO-XYZ Subject
[ ] Pull Request title contains the target branch if not targeting master: [0.9.x] KOGITO-XYZ Subject
[ ] Pull Request contains link to the JIRA issue
[ ] Pull Request contains link to any dependent or related Pull Request
[ ] Pull Request contains description of the issue
[ ] Pull Request does not include fixes for issues other than the main ticket

jenkins retest this please

jenkins retest this

Revert no more needed, fixed by https://github.com/kiegroup/kogito-runtimes/pull/727


When opening the map from iPhone's FB app, the screen is too crowded

The app does not recognise that it is a small display. One needs to use a real browser, even on phones.
But why? Is there a way to fix this?

The issue is that FB has its own browser, but lacking some capabilities proper browsers have.

Maybe it's rendered larger that device screen and shrunk down?
In the viewport meta tag we do not seem to have width=device-width

Does the recent update have an effect?


Would be great to include odds data into the predictions?

Hi,
Awesome project! I was going to do something similar myself but searched first and this looks like it ticks most of the boxes.
One thing is missing though: we need to test whether the model can make money when we bet on the predictions.
To do this we need to back test the model by comparing it's odds predictions with bookie odd, and then simulating a bet whenever bookie odds are greater than model odds.
I am more than happy to help out or just fork and do it myself but wondering if you had any ideas on this before?
I am more than happy to collaborate properly and share ideas over email or another method of messaging/comms.
Let me know what you think :-)

Hi!
I apologize for not responding for a long time, but lately, I've had little
time for projects like this. I'm glad you like my repo :)
If I understood you correctly, you want to predict betting odds instead of
which team will win the match, is that right?
I like this idea, it's worth a try, you can go ahead if you want. I
definitely encourage you to fork it.
I'm not sure that this way we'll be able to build a model that will "earn
money" I think we would rather need to equip the model with "better data"
form different sources like e.g. data from transfermarkt.
I have many ideas, unfortunately, time is not on my side, haha :D
Anyway, I encourage you to develop the repo :)
If you have any questions, feel free to ask. The code was written "quickly"
rather than "clean code".
czw., 7 mar 2024 o 18:11 andyg303 @.***> napisał(a):

Hi,
Awesome project! I was going to do something similar myself but searched
first and this looks like it ticks most of the boxes.
One thing is missing though: we need to test whether the model can make
money when we bet on the predictions.
To do this we need to back test the model by comparing it's odds
predictions with bookie odd, and then simulating a bet whenever bookie odds
are greater than model odds.
I am more than happy to help out or just fork and do it myself but
wondering if you had any ideas on this before?
I am more than happy to collaborate properly and share ideas over email or
another method of messaging/comms.
Let me know what you think :-)
—
Reply to this email directly, view it on GitHub
https://github.com/msoczi/football_predictions/issues/4, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVCOFYDRIP5EBU43FL7U2CTYXCNS7AVCNFSM6AAAAABELMM4B6VHI2DSMVQWIX3LMV43ASLTON2WKOZSGE3TIMZUGY4DKMI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


On selecting menu Item from the side menu TabBar gets disappear?

I have burger button (menu button) in almost all vc and my main screen is tabBarController. Currently I'm getting the side menu when tapping on the Button .On choosing a menu, it shows the desired vc but the bottom tab bar is not there which was there before i select menu item. I want to have the bottom tabbar in entire pages also in pages from the side menu. I.'m using SWRevealViewController for burger menu
How can I acheive this? Please help me.
The code I'm using in didSelectRowAtIndexPath is:
if indexPath.row == 1 {
let vc = storyboard?.instantiateViewController(withIdentifier: "FeedScreenVC") as! FeedScreenVC
let nav = UINavigationController.init(rootViewController: vc)
self.revealViewController().pushFrontViewController(nav, animated: true)
}

You  have to push your tab bar controller with the correct selected item not the controller.

@iDevelopper sorry didn't get you. Can you please share in more detail :)

@iDevelopper
cssFeed.zip

Only the rearVC has been modified to push the tab bar controller instead of a new instantiated controller.
cssFeed.zip


Improve exact total count

1. Why is this change necessary?
As discussed with @OliverSkroblin in Slack: When searching for entities and using TOTAL_COUNT_MODE_EXACT, the EntitySearcher uses SQL_CALC_FOUND_ROWS which is very slow for large results.
Using a separate COUNT() query is at least an order of magnitude faster.
2. What does this change do, exactly?
Uses separate COUNT() query to calculate the exact total of an entity search instead of using SQL_CALC_FOUND_ROWS and an additional FOUND_ROWS() query.
3. Describe each step to reproduce the issue or behaviour.
Open any view that has more than 100.000 elements and compare the time to see the view (without caching) to a normal view with ~1.000 Elements
4. Please link to the relevant issues (if any).
5. Checklist

[x] I have written tests and verified that they fail without my change
[x] I have squashed any insignificant commits
[x] I have created a changelog file with all necessary information about my changes
[x] I have written or adjusted the documentation according to my changes
[x] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/NEXT-15399
Please use this issue to track the state of your pull request.

Hey : )
We've just set your PR to “Scheduled”.
This means our initial screening is passed.
Your PR will now be reviewed and tested before being put trough our internal extended testsuite and review process.
We will keep you informed wether something has to be done by you or when the PR is merged : )
If you have any questions feel free to ask.

Hey @maximilianruesch, thanks for the PR : )


nokogiri version should be upgraded in Gemfile.lock

Github shows the following error:

We found a potential security vulnerability in one of your dependencies.
The nokogiri dependency defined in Gemfile.lock has a known critical severity security vulnerability in version range < 1.8.1 and should be updated.

As the library is only used to generate the site itself (which is part of the repository) this is not remotely exploitable. But seems wise to bump it anyway in case there is some interaction.

Could be duplicate of #480.

#480 upgrades nokogiri to 1.8.1, so it should be a fix for this issue.

Can be closed?

Can be closed?


Fix confirmation screen

You probably want to squash your commits

One more thing that came to mind reviewing this PR. This component can actually be a web3 UI component as preRegisteredCallback and registeredCallbackFn can support an optimistic UI for ENS, we just need to add a registrationFailed prop and that will allow the UI to update instantly when the user submits a TX but rollback and inform the user that the transaction actually failed.


Refresh specs for for

This adds two new compile errors

@seven1m  I took the liberty of merging this one without approval: it's mostly just importing this file from another repository (and adding the NATFIXME blocks), so it doesn't change any behaviour of our code.


Why BUILD.bazel over BUILD?

https://github.com/thundergolfer/the-one-true-bazel-monorepo/blob/7a11ce0e890efc997b384414430a94c2384072f0/fruit_sorting/BUILD.bazel
I think using BUILD is the best as it is consistent with the official doc. I understand if it may have a syntax highlighting issue depending on what you use but that should be the syntax highlighting plug-in issue that it should recognize BUILD as a Bazel file.

Sorry for late reply,
Both work, but I'm used to BUILD.bazel because during a migration we had other build files lying around causing conflicts.
I can change it.

Closed by 677259a


Switch Kyber reference implementation to match the FIPS-203 draft

Done in https://github.com/cryspen/libcrux/pull/122.


Check line endings in CI

When reviewing https://github.com/QCoDeS/Qcodes/pull/1524/ I realized that it will probably be useful make the CI enforce consistent line endings all over the project.

Hopefully a related question: why do we not use .gitattributes that checks out and checks in with \n on all systems?

I don't have any experience with it but that seems like a reasonable thing to try out

I used it in the previous projects. It really removes this line-end hassle for the given repository, regardless of what the global git settings are.
Just to be clear, i think running a linter is also useful. The only thing i don't know is what the overlap with mypy and codacy there is.

I don't think there is any overlap with mypy. Codacy uses pylint under the hood. But it does not expose this setting which is off by default

Seems like a good idea. Shouldn't we just get this in?


when I run your code, the following errors appeared. Can you help me.

Traceback (most recent call last):
File "I:/DDAG-master/train_ddag.py", line 479, in
main()
File "I:/DDAG-master/train_ddag.py", line 442, in main
wG = train(epoch, wG, trainloader)
File "I:/DDAG-master/train_ddag.py", line 284, in train
for batch_idx, (input1, input2, label1, label2) in enumerate(trainloader):
File "C:\ProgramData\Anaconda3\lib\site-packages\torch\utils\data\dataloader.py", line 279, in iter
return _MultiProcessingDataLoaderIter(self)
File "C:\ProgramData\Anaconda3\lib\site-packages\torch\utils\data\dataloader.py", line 719, in init
w.start()
File "C:\ProgramData\Anaconda3\lib\multiprocessing\process.py", line 112, in start
self._popen = self._Popen(self)
File "C:\ProgramData\Anaconda3\lib\multiprocessing\context.py", line 223, in _Popen
return _default_context.get_context().Process._Popen(process_obj)
File "C:\ProgramData\Anaconda3\lib\multiprocessing\context.py", line 322, in _Popen
return Popen(process_obj)
File "C:\ProgramData\Anaconda3\lib\multiprocessing\popen_spawn_win32.py", line 89, in init
reduction.dump(process_obj, to_child)
File "C:\ProgramData\Anaconda3\lib\multiprocessing\reduction.py", line 60, in dump
ForkingPickler(file, protocol).dump(obj)
OSError: [Errno 22] Invalid argument
Traceback (most recent call last):
File "", line 1, in
File "C:\ProgramData\Anaconda3\lib\multiprocessing\spawn.py", line 105, in spawn_main
exitcode = _main(fd)
File "C:\ProgramData\Anaconda3\lib\multiprocessing\spawn.py", line 115, in _main
self = reduction.pickle.load(from_parent)
_pickle.UnpicklingError: pickle data was truncated

I suppose that you need to config your code environment. I did not check it on windows.


Fix type of Setter for close listener

Can one of the admins verify this patch?

this is ok to test


Bug: Remove visualisation/ from #includes in cpp

There is no visualisation folder.

Ha! Good spot. I used to have visualisation as the project name, which generates a visualisation folder. Thanks.

Instead of removing visualisation from the #include statement, I will prefer to change it to qvisualisation.


Still working with new version?

Says undefined in the image container

Working like it should, don't see undefined anywhere. Care to post a screenshot?

Sorry, i solve it as i could.
i had to change line 51:
return "

" + caption + "

";
for this:
return "

" + caption + "

";
otherwise, the href property returns undefined for me.
Thanks for your answer and sorry for change your code for my porpouse.
Grettings
Ibsen.

Sounds like you have a different HTML structure than what's proposed in the readme. For that, you do have to change the javascript code.
Closing this for now as that's neither an issue nor a constructive idea.


Entities: Make InitializeState support Async operations

I have a requirement to create initial Entity state from an external source (db, blob, etc).
However currently, the override to create initial state for an Entity does not support async operations, forcing me to do syncronous calls.
Suggestion
protected override async Task<T> InitializeStateAsync(TaskEntityOperation operation)
{
     //perform async operations
}

Thread is also blocked in my initializeState because async operation is not supported

Thanks @jviau. Would this pattern still work with this method signature?
protected override async Task<T> InitializeStateAsync(TaskEntityOperation operation)
{
     //perform async operations
}

as I need to return T not void (as the entity inherites from TaskEntity<T>) and it looks like the base class will store the returned value in the base.State property.
Full Code Example
public class T : TaskEntity<T>
{
    public void MyMethod() { }

    [Function(nameof(T))]
    public static Task RunEntityAsync([EntityTrigger] TaskEntityDispatcher dispatcher)
    {
        return dispatcher.DispatchAsync<WorkflowStateDurableEntity>();
    }

    protected override T InitializeState(TaskEntityOperation operation)
    {
        //inject EnsureInitializeAsync pattern here?
        T state = new();
        return state;
    }
}

Also worth noting, an additional alternative would be to use the functions based syntax which would allow the populating of the state inside the DispatchAsync()

@gorillapower
Yes, returning default(T) would be fine there. InitializeState is just a convenience method for populating state when there is none. I updated my sample to show that.
You could also set it in InitializeState and then populate its contents in InitializeAsync.


THRIFT-3143: Add nodets support

These changes should be backwards compatible since it only adds new functionality and doesn't touch existing functionality.

One of the tests failed because of a lisp test. Not related to my changes.

Hi @jeking3 I added nodets to cross test suite

You can run the cross test locally if you use the docker build container.  First you prepare the environment:
user@ubuntu:~/thrift$ docker pull thrift/thrift-build:ubuntu-bionic
user@ubuntu:~/thrift$ docker run -v $(pwd):/thrift/src:rw -it thrift/thrift-build:ubuntu-bionic /bin/bash
root@8d4584e2e789:/thrift/src# ./bootstrap.sh
root@8d4584e2e789:/thrift/src# ./configure
root@8d4584e2e789:/thrift/src# make precross

Next you can run a specific combination of tests:
root@8d4584e2e789:/thrift/src# test/test.py --retry-count 5 --skip-known-failures --server cpp --client nodets

That will help you prepare your next pull request for success.

OK, I tried locally with cpp,java,nodejs servers and clients.
The cross tests with above languages passed.
@jeking3 If there is no other failure, can we merge this?

There are still 41 failing cross tests:
===============================================================================
*** Following 41 failures were unexpected ***:
If it is introduced by you, please fix it before submitting the code.
===============================================================================
server-client:          protocol:         transport:               result:
c_glib-nodets           binary            buffered-ip              failure(timeout)
c_glib-nodets           multi-binary      buffered-ip              failure(timeout)
d-nodets                binary            buffered-ip              failure(1)
go-nodets               binary            buffered-ip              failure(timeout)
java-nodets             binary            buffered-ip              failure(timeout)
java-nodets             multi-binary      buffered-ip              failure(timeout)
hs-nodets               binary            buffered-ip              failure(timeout)
py-nodets               accel-binary      buffered-ip              failure(timeout)
py-nodets               binary            buffered-ip              failure(timeout)
py3-nodets              accel-binary      buffered-ip              failure(timeout)
py3-nodets              binary            buffered-ip              failure(timeout)
cpp-nodets              binary            buffered-ip              failure(timeout)
cpp-nodets              multi-binary      buffered-ip              failure(timeout)
rb-nodets               accel-binary      buffered-ip              failure(timeout)
rb-nodets               binary            buffered-ip              failure(timeout)
csharp-nodets           binary            buffered-ip              failure(timeout)
netcore-nodets          binary            buffered-ip              failure(timeout)
perl-nodets             multi-binary      buffered-ip              failure(timeout)
perl-nodets             binary            buffered-ip              failure(timeout)
erl-nodets              binary            buffered-ip              failure(timeout)
rs-nodets               binary            buffered-ip              failure(timeout)
rs-nodets               multi-binary      buffered-ip              failure(timeout)
nodets-c_glib           binary            buffered-ip              failure(1)
nodets-cl               binary            buffered-ip              failure(1)
nodets-d                binary            buffered-ip              failure(1)
nodets-go               binary            buffered-ip              failure(1)
nodets-hs               binary            buffered-ip              failure(1)
nodets-py               binary-accel      buffered-ip              failure(1)
nodets-py               binary            buffered-ip              failure(1)
nodets-java             binary            buffered-ip              failure(64)
nodets-nodejs           binary            buffered-ip              failure(1)
nodets-cpp              binary            buffered-ip              failure(64)
nodets-py3              binary-accel      buffered-ip              failure(1)
nodets-py3              binary            buffered-ip              failure(1)
nodets-php              binary-accel      buffered-ip              failure(255)
nodets-php              binary            buffered-ip              failure(255)
nodets-csharp           binary            buffered-ip              failure(64)
nodets-lua              binary            buffered-ip              failure(timeout)
nodets-rs               binary            buffered-ip              failure(1)
nodets-perl             binary            buffered-ip              failure(111)
nodets-nodets           binary            buffered-ip              failure(timeout)
===============================================================================

The nodets uses nodejs as a basis so known failures for nodejs probably applies to nodets as well.
I will check if there are any that nodejs doesn't fail.

I did some improvements to the tests script so most timeouts are fixed.
the erl-nodets and d-nodets tests fail but their nodejs counterparts are in known_failures.Linux.json so they should be added as well.
There is one test that I couldn't figure out: In hs-nodets test, the client logs that all the tests are successful and it does call connection.end(). However it still times out for some reason...

Hi @jeking3 I have a green build but I had to disable hs-nodets test.
If it is OK with you, can we merge this PR and then I can take a deeper look into the test with my colleagues?

Thanks for merging it.
Here is the necessary info (the cross test covers the following cases):

nodets
since: 0.12.0 (next release, I guess)
lang/lib levels: Min: TypeScript 3.1.6
Low level transports: Socket
Transport wrappers: TLS
Protocols: binary
Servers: Simple


Truncate files if they exist prior to extraction from archive (#1245)

Both failing GH actions has never passed. Merging


Update tim-huckaby.yml

Docs Build status updates of commit 25c84c5:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

rd/tim-huckaby.yml
:white_check_mark:Succeeded

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


Labs: show a list of "where you are the most outliery" per CCG

https://gist.github.com/sebbacon/d32c2fef3d0686a08ebe24804ed7b868

Idea:

Use analyses like the above to find a list of chemicals which have the most outliery behaviour
For each of those, create a custom "labs" measure
Similar analyses to find interesting measures

Numerator: section; denominator: astropu
See also Helen's outlierish analyses

Custom measures for some of these for 99P:
https://gist.github.com/sebbacon/6674e9ce9f08e88eb1c5ee96b15ab6d6

See also #890 (outliers by practice)

now live https://github.com/ebmdatalab/openprescribing/pull/3435


Fix some existing and add missing translations to Swedish localization

Some strings in Swedish localization were in English, some were missing. This pull request fixes that.

I'm Swedish, I approve of this. 👍

Thank you! I'll add it in 4.1.0


feat(linter) eslint plugin unicorn: no useless spread

Tasks:

[x] Add approprite error message
[x] clean up code

Nice! 1 more correctness rule.


cabal.project support

I think it was nice if get-tested supported the extraction of the tested-with stanzas of multiple Cabal files; In particular those listed as packages in a cabal.project file. What I have in mind is something similar to the following:

Make the Cabal file an optional input on the CLI.
If no Cabal file was given, look for a cabal.project file in the current directory and its parents.
Resolve the Cabal files in the packages stanza of the cabal.project file.
Extract the get-tested stanzas of the packages.
Output the union of the collected stanzas. Or output a separate entry for each file (e.g. <file>: <listed versions>)

I think most of the work can be done by using cabal-install-parsers, but the real question is if that is useful feature.
Personally I think it would be useful for mono-repos like https://github.com/dhall-lang/dhall-haskell to keep the tested-with stanzas in sync with what was actually tested in the CI.

I'd rather avoid depending on cabal-install-parsers, its maintainer has a rather disparaging attitude towards users.

With @julianG's new cabal.project parser we might be able to avoid depending on cabal-install-parsers.

With @julianG's new cabal.project parser we might be able to avoid depending on cabal-install-parsers.

I am excited to see that getting merged too, but cabal-install-parser does also some more things like discovering the cabal.project file.
Given that cabal-install-parser appears to be relatively stable (and so you might not need to get in contact with the maintainer), would it really be that bad to depend on that library?


Weird image

Hey, this is a nice library!
When trying to use this, I somehow get a weird image rendered from this (see attached screenshot). Actually, this would be a portrait photo. Any idea?
Thanks!
Leonard

I'm having the same problem. Did you solve it?


[WIP] ENH: add skip_by_annotation to notch_filter

Partial fix for #10447
This adds a skip_by_annotation for notch filtering

Is there a way to make the length of the notch filter shorter @larsoner ? Even though I have implemented this, it's pretty useless for my data since the ISI is around 300-500 ms. Alternatively, would it make sense to concatenate the segments before filtering?

You can set filter_length to something other than 'auto', but assuming you want to use 'auto' (which is a good choice generally) then you probably need to extend the transition bands for the filter, which would knock out more frequency content...

Thanks for the suggestion! That sounds fair, so I changed the PR status to MRG again.


Update sha pointers to master brances for standard, coreclr, corefx, and core-setup

cc @dotnet/source-build-contrib

@Priya91 @bartonjs Do you guys have any ideas about what is missing for this error:
https://ci.dot.net/job/dotnet_source-build/job/master/job/RHEL7.2_Release_prtest/47/consoleFull
/mnt/resource/j/workspace/dotnet_source-build/master/RHEL7.2_Release_prtest/src/corefx/src/Native/Unix/System.Security.Cryptography.Native/pal_ssl.cpp(547,9): error G8EDBB558: use of undeclared identifier 'SSL_CTX_set_alpn_select_cb' [/mnt/resource/j/workspace/dotnet_source-build/master/RHEL7.2_Release_prtest/repos/corefx.proj]

It looks like ALPN support was introduced in OpenSSL 1.0.2. It looks like only RHEL 7.4 includes this. RHEL 7.2 and 7.3 include version 1.0.1* only.

That may be true but the corefx build I thought was detecting this and only building the new ALPN code if it was supported on the machine it is building on.

@weshaggard Not sure.  It looks to me like things should be defensive enough: https://github.com/dotnet/corefx/search?utf8=✓&q=HAVE_OPENSSL_ALPN&type=
I mean, technically it's probing for SSL_get0_alpn_selected and calling SSL_CTX_set_alpn_select_cb; but those should have come together.
It's also weird if it didn't error up on 533: https://github.com/dotnet/corefx/blob/2bd69b97b763e0acdfa082eed1a281a5f5afffa5/src/Native/Unix/System.Security.Cryptography.Native/pal_ssl.cpp#L533

I believe the error was using #ifdef instead of #if in pal_ssl.cpp. @janvorli fixed this in PR today dotnet/corefx#25014


Implement new separate api for cast, validate and transform

Pull Request Test Coverage Report for Build edd534853ab4d37441a87346f90a72038489f863-PR-27
Details

-10 of 72 (86.11%)  changed or added relevant lines in 3 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.9%) to 88.043%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

lib/result.ex
6
7
85.71%

lib/type.ex
6
7
85.71%

lib/tarams.ex
50
58
86.21%

Files with Coverage Reduction
New Missed Lines
%

lib/type.ex
1
84.62%

Totals

Change from base Build 71b27c2a3bcf62551e5adb310cb3536c8f19e964:
-0.9%

Covered Lines:
243

Relevant Lines:
276

💛  - Coveralls


Routes incorrectly use hostname from Listener

Stub bug report that needs further investigation and proper replication steps. Briefly, the route generated from this HTTPRoute should not have the tls9443.kong.example hostname, as that's not in its rules. It's somehow coming from an unrelated TLS Listen in the Gateway. Found in 2.7, need to validate if it's still happening for the current nightlies.
    {
      "response_buffering": true,
      "hosts": [
        "tls9443.kong.example"
      ],
      "regex_priority": 0,
      "https_redirect_status_code": 426,
      "preserve_host": true,
      "path_handling": "v0",
      "headers": null,
      "created_at":<PHONE_NUMBER>,
      "updated_at":<PHONE_NUMBER>,
      "strip_path": true,
      "id": "df37c9f6-49a0-5ba9-bac7-932dc09786ce",
      "snis": null,
      "paths": [
        "/echo"
      ],
      "service": {
        "id": "f998693d-c386-5bbf-aea2-aeae52bced58"
      },
      "sources": null,
      "destinations": null,
      "tags": null,
      "methods": null,
      "name": "httproute.default.echo.0.0",
      "protocols": [
        "http",
        "https"
      ],
      "request_buffering": true
    },

apiVersion: gateway.networking.k8s.io/v1beta1
kind: HTTPRoute
metadata:
  annotations:
    konghq.com/strip-path: "true"
  creationTimestamp: "2022-11-11T20:13:31Z"
  generation: 11
  name: echo
  namespace: default
  resourceVersion: "199603"
  uid: 7519c73c-7522-4989-9dd7-d8526c17a5c3
spec:
  parentRefs:
  - group: gateway.networking.k8s.io
    kind: Gateway
    name: kong
  rules:
  - backendRefs:
    - group: ""
      kind: Service
      name: echo
      port: 80
      weight: 200
    - group: ""
      kind: Service
      name: echo2
      port: 80
      weight: 100
    matches:
    - path:
        type: PathPrefix
        value: /echo

apiVersion: v1
items:
- apiVersion: gateway.networking.k8s.io/v1beta1
  kind: Gateway
  metadata:
    annotations:
      konghq.com/gatewayclass-unmanaged: kong/kong-proxy
    creationTimestamp: "2022-11-11T19:01:48Z"
    generation: 15
    name: kong
    namespace: default
    resourceVersion: "199586"
    uid: 072e882e-0e34-4d0b-9fe9-50c458863303
  spec:
    addresses:
    - type: IPAddress
      value: <IP_ADDRESS>
    gatewayClassName: kong
    listeners:
    - allowedRoutes:
        namespaces:
          from: Same
      name: http
      port: 80
      protocol: HTTP
    - allowedRoutes:
        namespaces:
          from: Same
      name: tcp
      port: 8888
      protocol: TCP
    - allowedRoutes:
        namespaces:
          from: Same
      name: stream9000
      port: 9000
      protocol: TCP
    - allowedRoutes:
        namespaces:
          from: Same
      hostname: tls9443.kong.example
      name: stream9443
      port: 9443
      protocol: TLS

Tried with current main branch, the problem still exists.


fixing build fail caused by merging of an old PR #81

Yesterday 3 week old PR #81 got merged. The repo had a conflict back then when the PR was raised causing build failures. Although I fixed that immediately back then but due to the changes that got merged yesterday, new PRs are having failed build checks. I am fixing those build fails in this PR. There's not much in this PR. Please review

LGTM merging


How do I customize Control buttons?

How on earth do I customize control buttons?? I need to use custom arrow icons to switch slides back and forth, I am trying to wrap my icons around provided  and  but it is still a button with Icon on it, not the Icon itself.

I'm looking for info on this as well. How would you replace the ButtonFirst button with a FontAwesome Icon?

Issues are intended to be bugs or feature requests, so we ask you to not use issues to ask questions.
We have a Stack Overflow  section for questions in regard to how to accomplish certain tasks. We ask that you move questions there.


Don't forget to set your cpu to performance mode

Since i just spent quite some time wondering why my benchmarks were the opposite of what they should be, a reminder to check your cpu governor. Setting mine to perf mode was crucial.

precommit doesn't like the github flavored markdown note boxes :/

Looks like it still works when escaped.


translate strict-mode.md

please ignore the locks files ( yarn.lock / package-locks.json ) ..

Hi @3imed-jaberi, please revert any commit that edit other files than strict-mode.md.
Or create a new PR with only strict-mode.md been edited. If you feel like it. Thanks ❤

Okey , nchlh in the future. Thank you ❤

Amazing job mashallah 🎉


Alternative attachment

Description

Motivation and Context

How Has This Been Tested?

Checklist:

[ ] I have submitted a CLA form
[ ] If applicable, I have updated the documentation accordingly.
[ ] If applicable, I have added tests to cover my changes.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: hanskroner:x: quanvo87You have signed the CLA already but the status is still pending? Let us recheck it.

Codecov Report

Merging #72 into master will increase coverage by 0.18%.
The diff coverage is 93.1%.

@@            Coverage Diff             @@
##           master      #72      +/-   ##
==========================================
+ Coverage   87.35%   87.53%   +0.18%
==========================================
  Files          12       12
  Lines         609      634      +25
==========================================
+ Hits          532      555      +23
- Misses         77       79       +2

Flag
Coverage Δ

#SwiftSMTP
87.53% <93.1%> (+0.18%)
:arrow_up:

Impacted Files
Coverage Δ

Sources/SwiftSMTP/Mail.swift
98.38% <100%> (-0.03%)
:arrow_down:

Sources/SwiftSMTP/Attachment.swift
97.84% <92.3%> (-2.16%)
:arrow_down:

Continue to review full report at Codecov.

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


Added a test for the reviewers list

I just couldnt get the testing working with the server mocking the github call.

LGTM


[LOC] Invalid link in an article

There is an invalid link in an article.
Repro steps:

Go to https://docs.microsoft.com/en-us/sharepoint/administration/assign-a-category-page-and-a-catalog-item-page-to-a-term
Search for "Create and manage terms in a term set" link
click on the link

Actual results:
Link does not work
Expected results:
Link should work
GH article:
https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/blob/live/SharePoint/SharePointServer/administration/assign-a-category-page-and-a-catalog-item-page-to-a-term.md

@OfficeGlobal Thank you for submitting feedback and contributing to the docs. We are currently investigating this.

Thank you for submitting feedback. We understand that this issue has been resolved.
Please feel free to re-open this issue if there is a specific area of the docs that we can improve or make better. Thank you.


Ensure Documentation front-end code is correct

Looking at the code for this page https://sonarwhal.com/docs/developer-guide/rules/index.html
I believe each section of content that has an h2 heading should be wrapped in its own section element. @aarongustafson can you confirm this is the correct approach for these pages?
Also seeing a blockquote element in there but not sure if it is just a placeholder for now, but that should be removed if the content there isn't intended as a pull out quote or quotation.
If the list items at the top of the page are intended to be steps, should probably be an ordered list.

Removing the duplicate h1 heading issue here in favor of #96, hopefully when we get the layout adjusted back to the original proposal, we can remove the duplicate h1 elements.


swap-branches-on-compare should not appear when there's nothing to compare

Description

How to replicate the issue + URL
https://github.com/refined-github/refined-github/compare
Extension version
23.4.10
Browser(s) used
Chrome

Waiting for https://github.com/refined-github/github-url-detection/pull/169


Project missing in environment

Thanks for providing hatch-pip-compile, it looks really useful but I am having a strange problem. Somehow the project itself is not installed in the default environment if it has type "pip-compile" as opposed to "virtual". So in my pyproject.toml I have:
[tool.hatch.env]
requires = ["hatch-pip-compile"]

[tool.hatch.envs.default]
type = "pip-compile"
[tool.hatch.envs.default.scripts]
upgrade-all = "pip-compile --upgrade {args}"
upgrade-pkg = "pip-compile --upgrade-package {args}"

and running hatch run python -c "import name_of_my_package" it doesn't find the package. Also hatch run pip list doesn't show it. Maybe I am missing something obvious here 🤔 .

Hey @FlorianWilhelm thank you for reporting this, I actually noticed this the other day. I believe this is caused by using pip-sync underneath all of this to manage the environment. I will get a fix out to this soon (today hopefully).

Alright, I've gotten this resolved in v0.2.2. hatch-pip-compile is still in early days so thank you for filing an issue and making this better for everyone. Please let me know if you encounter any other issues 🤝

Thanks, that was really fast! It works.


Line numbers are misaligned on several Sphinx themes

A change in Sphinx (https://github.com/sphinx-doc/sphinx/pull/7482) combined with a change in Pygments (#1477) has led to a wrong alignment of line numbers.
This happens with Pygments 2.7+ and Sphinx 3.1+.
See https://github.com/sphinx-doc/sphinx/issues/8254 for details including screenshots.
So far, I've found these Sphinx themes to be affected:

https://sphinx-themes.github.io/sphinx-themes.org/sample-sites/default-alabaster/
https://sphinx-themes.github.io/sphinx-themes.org/sample-sites/default-classic/
https://sphinx-themes.github.io/sphinx-themes.org/sample-sites/default-haiku/
https://sphinx-themes.github.io/sphinx-themes.org/sample-sites/default-nature/
https://sphinx-themes.github.io/sphinx-themes.org/sample-sites/default-pyramid/
https://sphinx-themes.github.io/sphinx-themes.org/sample-sites/default-sphinxdoc/

https://sphinx-themes.github.io/sphinx-themes.org/sample-sites/astropy-sphinx-theme/
https://sphinx-themes.github.io/sphinx-themes.org/sample-sites/flask-sphinx-themes/
https://sphinx-themes.github.io/sphinx-themes.org/sample-sites/groundwork-sphinx-theme/
https://sphinx-themes.github.io/sphinx-themes.org/sample-sites/insipid-sphinx-theme/
https://sphinx-themes.github.io/sphinx-themes.org/sample-sites/jupyter-sphinx-theme/
https://sphinx-themes.github.io/sphinx-themes.org/sample-sites/karma-sphinx-theme/
https://sphinx-themes.github.io/sphinx-themes.org/sample-sites/logilab-sphinx-themes/
https://sphinx-themes.github.io/sphinx-themes.org/sample-sites/mozilla-sphinx-theme/
https://sphinx-themes.github.io/sphinx-themes.org/sample-sites/python-docs-theme/
https://sphinx-themes.github.io/sphinx-themes.org/sample-sites/renku-sphinx-theme/
https://sphinx-themes.github.io/sphinx-themes.org/sample-sites/solar-theme/
https://sphinx-themes.github.io/sphinx-themes.org/sample-sites/sphinx-celery/
https://sphinx-themes.github.io/sphinx-themes.org/sample-sites/sphinx-documatt-theme/

I'm not sure whether this should be fixed in Sphinx or in Pygments (or both?), but I found out that disabling this chunk of CSS (which comes from Pygments) seems to fix the problem for most themes (I didn't try all, though):
td.linenos pre {
    color: #000000;
    background-color: #f0f0f0;
    padding: 0 5px 0 5px;
}

I'm not sure I see the bug. I've been changing it here: https://github.com/pygments/pygments/commit/b6fb70f88a4bf270a36515e958fdf124a70543ad, to the output you see there, and I'd like to understand how that output is causing issues? Is Pygments on its own inconsistent with spacing, or is it just in conjunction with Sphinx and Sphinx expecting a particular class/tag?

I'm not sure I see the bug.

But you see the misalignment?
You might not consider the colors a bug, but the misalignment definitely is, isn't it?
I'm not saying that it's necessarily a bug in Pygments, but it is a bug somewhere!

I've been changing it here: b6fb70f, to the output you see there, and I'd like to understand how that output is causing issues?

Does https://github.com/sphinx-doc/sphinx/issues/8254#issuecomment-714434470 explain the issues sufficiently?

Is Pygments on its own inconsistent with spacing, or is it just in conjunction with Sphinx and Sphinx expecting a particular class/tag?

I don't know, I've only ever used Pygments in conjunction with Sphinx.
How would I test Pygments on its own?

(Note that Sphinx can always just override some CSS if that's causing trouble.)

I don't think so. At least not in a general way that un-breaks all affected themes.
Sphinx (in its basic.css) cannot overwrite the vertical padding, because it is defined by the theme, which basic.css or course has no knowledge of.
Only each individual theme knows its correct vertical padding, therefore the problem can only be fixed by the theme, and not by Sphinx.
I'm willing to fix my own theme (https://github.com/mgeier/insipid-sphinx-theme/pull/21), but I think it would be better to simply not break all those themes in the first place.
Again, I'm not saying the bug is necessarily in Pygments. If you know a way to fix this in Sphinx in a generic way, please let me know!

I agree it looks broken, I'm just saying I'm not sure if this qualifies as a bug if 2.6/2.7 kind of works with Sphinx 3.0 (as in, the output is not mismatched). It looks like there were (implicit) assumptions on both sides about how things are supposed to work, and something is broken now :)
Let me try raw Pygments output first. I'm fairly certain that did look correct. If it does indeed look correct, the next step will be to figure out how it violates Sphinx' assumptions.
To test Pygments on your own, you can simply run pygmentize, using the HTML formatter. That's how the test files were generated in the first place.

It looks fine with Pygments "standalone". The colors for the linenos class are expected, as the bug was that line numbers were not properly colored (it was hardcoded.) The original style for linenos was to have 10 px padding on the right. I've changed it now to be 5px padding on the left and right, but not specify a top/bottom margin. I hope that this does not break Sphinx themes in the same way. Can you give 0d28e2b7a20ec2bf0025115844647c8e5b88e70b a try, please?

Thanks @Anteru, this indeed fixes the alignment problem!
As you mentioned, this changes the colors though, which I think most theme authors would consider a bug.

The colors for the linenos class are expected, as the bug was that line numbers were not properly colored (it was hardcoded.)

What was hardcoded?
Before Pygments 2.7, Pygments had no influence on the colors of the line numbers in Sphinx AFAICT.

The original style for linenos was to have 10 px padding on the right. I've changed it now to be 5px padding on the left and right,

OK, I don't really have an opinion on this.
Sphinx currently has additional padding on the parent element:
https://github.com/sphinx-doc/sphinx/blob/0476e1cea93b587e3c0ab295aa20b2b9f0f81a34/sphinx/themes/basic/static/basic.css_t#L734-L736
I'm not sure whether that's too much if Pygments also adds padding.

but not specify a top/bottom padding.

That's great!

It looks fine with Pygments "standalone".

Could you please provide an example pygmentize invocation including line numbers, to make sure we are talking about the same thing?

The line number colors were hardcoded previously and didn't match the theme. The original CSS for them was background-color: #f0f0f0; padding-right: 10px; no matter what theme you used. If the fix I wrote works for Sphinx, I'll get a 2.7.1 out with it (forcing the padding to 0 was not intentional.)
For pygmentize, use pygmentize -f html -O linenos=True,full=True path/to/a/file

that's probably the main reason you're affected now, because Pygments properly inlines them now

OK, thanks, that explains a lot!
I was wondering why this suddenly appeared out of the blue ...
Thanks for the pygmentize command, that's very helpful!
I've added the style to the options (-O linenos=True,full=True,style=friendly) to compare a few styles.
It looks like the "solarized" style (solarized-light and solarized-dark) is the only one that bothers to customize the line numbers:
https://github.com/pygments/pygments/blob/3e1b79c82d2df318f63f24984d875fd2a3400808/pygments/styles/solarized.py#L121-L122
https://github.com/pygments/pygments/blob/3e1b79c82d2df318f63f24984d875fd2a3400808/pygments/styles/solarized.py#L133-L134
All other styles seem to just take the default:
https://github.com/pygments/pygments/blob/3e1b79c82d2df318f63f24984d875fd2a3400808/pygments/style.py#L179-L183
Are there any plans to choose proper colors for the other styles?
I think the line number colors should definitely be overridden by Sphinx when using the table feature, which is currently the default, because the Pygments colors simply make no sense at all in that case.
Sphinx 4 will switch by default to inline (see https://github.com/sphinx-doc/sphinx/pull/7942), where the Pygments colors might make sense, but only  if the styles actually select meaningful colors!

Yes, but there's history again here. All styles used to use the same colors, and it was plain broken for solarized. A PR was made to implement a way to fix it, and for solarized, it was fixed properly, but the other styles continue to use the default (which seems ok as nobody was complaining about other styles than solarized being broken -- it seems likely nobody was using line numbers with a dark style.)
I'm happy to accept a PR to fix all other styles, but it doesn't seem high priority. Sphinx is of course free to override things, and frankly that's what I'd expect from a downstream user of Pygments. On the Pygments side, we have to be "self consistent", i.e. Pygments output needs to work, and if someone else is applying styling on top, they need to be able to override anything Pygments is doing as otherwise we'll be constrained by all downstream users -- which we may not even know.
My plan for this weekend is to release 2.7.1 with the padding fix (as I mentioned, fixing the padding to 0 was not intentional), but when it comes to colors you need to find a solution in Sphinx. My suggestion would be to use !important where it matters. If you have ideas for a better long-term solution I'm all ears -- I could imagine that Sphinx would supply it's own theme to Pygments for instance.

Sphinx is of course free to override things, and frankly that's what I'd expect from a downstream user of Pygments.

I've just suggested exactly that in https://github.com/sphinx-doc/sphinx/pull/8333.
However, this affects only the table layout.
As mentioned above, the Pygments colors would probably make sense in the inline layout, so maybe I'll try to add some colors to the other styles, but I'm not promising anything.
If somebody else wants to update the colors, please go ahead!

I could imagine that Sphinx would supply it's own theme to Pygments for instance.

Well there is already a sphinx style (SphinxStyle) and apparently a PyramidStyle: https://github.com/sphinx-doc/sphinx/blob/3.x/sphinx/pygments_styles.py.
But I think it is a very good feature of Sphinx to not be limited to a single style and to allow arbitrary Pygments styles.

If you have ideas for a better long-term solution I'm all ears

The long-term plan for Sphinx is to drop table layout anyway, so this will become irrelevant within the next year.
But for a bright future with the inline layout it would be nice to get updated colors in all styles that still use the defaults. This way, Sphinx wouldn't need to override them.

Sure, but that's further out. You may want to file an issue for themes where the default colors just don't work at all, maybe someone picks it up in the meantime.
I'm closing this bug as resolved, 2.7.2 will remove the vertical padding rule, so please update Sphinx to use <2.7 || >= 2.7.2.


Getters for start and stop buttons in upload manager

Good day!
Nice addon.
Please restore getters for buttons in upload manager or provide some functions to change their visibility, icons and etc. In my case I starting download automatically and don't need to see start/stop buttons at all.

Sorry.
Found getter for layout which is containing buttons.


Fix layer name.

Hello @adamac . We finally switched to github.  That would be great. Thanks in advance.

Can one of the admins verify this patch?

I re-pushed your change to a new PR. Kept your name in the Signed-off. Cheers!


Upgrade mbedtls to 2.7.9 or better

We've fallen behind in keeping up with the various fixes in the crypto library and as of 2/11/19 we're about 3 stable versions behind to get to 2.7.9.
Of note is a fix to handling for MBEDTLS_PLATFORM_CALLOC/FREE_MACRO which can be worked around by setting MBEDTLS_PLATFORM_STD_CALLOC/FREE instead, but that should be updated to use the macro definitions as documented for MBEDTLS_PLATFORM_MEMORY when we upgrade to 2.7.9 or better.
Related to #1457: We may move directly to 2.16.0 instead as the new long-term support branch mbedTLS has marked.

Hello, we are already working on this as part of https://github.com/Microsoft/openenclave/pull/1486
and tests passed https://github.com/Microsoft/openenclave/compare/master...vlaza:ISSUE-1456

@vlaza Didn't know you were actively working on this since I split it out of #1456. I needed to take a look at the MBEDTLS_PLATFORM_CALLOC/FREE_MACRO issue so spent a bit of time on this. This PR looks identical to yours except for the updated comments in config.h detailing the choice to keep the use of MBEDTLS_PLATFORM_STD_CALLOC/FREE. It has also passed Sandbox tests.
GitHub doesn't appear to correctly compare mbedtls_2.7.9 correctly with your fork, so can you pull the branch and diff against your private?


Enhancement Request: Support for languages like verilog using begin/end pair.

Hi boyw,
It is a extremely nice and useful plugin.
I have started using it everywhere. The hl-paran-mode is the most useful one.
Is it possible to support other parens also - like begin/end pair in verilog/vhdl.
Can we define all the parenthesis pairs using a variable that can be highlighted.

Good point. Sure it is possible. I'll try to update later.

for verilog - it is *.v or *.sv
for vdhl it is *.vhd


Drop python 3.6 and 3.7 which are past end of life upstream

Cherry-picked from #8, I'm doing things progressively so it's reviewable.

@stdedos I think it could be merged even with the negative coverage change.

@stdedos could you review this, please :) ? The CI is red because of an indirect coverage changes that I think we can ignore.

@stdedos could you review this, please :) ? The CI is red because of an indirect coverage changes that I think we can ignore.

Yeah, this seems to be the problem:

https://app.codecov.io/gh/pylint-dev/pylint-pytest/pull/23/indirect-changes
I'd be nice to figure out why is this happening, but it is definitely not a priority - given the benefits of this PR.
"I am not reviewing this" since it's not scheduled to go in yet.
Otherwise all looks golden to me and it is approved 💚

Plan is:

New bugfix on Monday 13.11
Merge https://github.com/pylint-dev/pylint-pytest/pull/15
Merge whatever else minor comes in (like https://github.com/pylint-dev/pylint-pytest/pull/25, https://github.com/pylint-dev/pylint-pytest/pull/26)
New bugfix on Monday 20.11
Questions
Start https://github.com/pylint-dev/pylint-pytest/milestone/2
New b/rc asap

Question:

Can https://github.com/pylint-dev/pylint-pytest/pull/24 become thinner? I could consider it for v1
Can https://github.com/pylint-dev/pylint-pytest/issues/12 be fixed for v1? I lost track on what was the pylint issue 😅

Can https://github.com/pylint-dev/pylint-pytest/pull/24 become thinner? I could consider it for v1

We can remove the drop of python 3.6 / 3.7 (probably)

Can https://github.com/pylint-dev/pylint-pytest/issues/12 be fixed for v1? I lost track on what was the pylint issue 😅

Need to support 3.12 maybe something else

Can #24 become thinner? I could consider it for v1

We can remove the drop of python 3.6 / 3.7 (probably)

I'd consider it for v1 - but it doesn't have to wait "the usual" 1w-period.
So next week we release master, and a thin #24 afterwards

Hey, I tried dropping the removal of python 3.6 / 3.7 and simply adding python 3.12, but this is non trivial (https://github.com/pylint-dev/pylint-pytest/actions/runs/7010519218/job/19071209667?pr=24). It's been nearly two months since the release of python 3.12 / pylint 3.0 and python 3.6 / 3.7 have been EOL for a long time, maybe we could just drop EOL interpreters and release 2.X serie, what do you think ?

See this issue in vscode/pylint : https://github.com/microsoft/vscode-pylint/issues/460 for example

Thank you for trying ❤
Sadly, my OSS time has been near-zero these days.
I will make it my first priority to merge these.

No problem. This one is ready the coverage drop is acceptable imo.

Thank you @Pierre-Sassoulas for all your contributions and patience 😁 🙏


希望任务计算处理框架支持 运行在 spark on yarn模式、flink on yarn 模式  或者MR

Contribution guidelines

[X] I've read the contribution guidelines and wholeheartedly agree

I want to suggest an idea and checked that ...

[X] ... to my best knowledge, my idea wouldn't break something for other users
[X] ... the documentation does not mention anything about my idea
[ ] ... there are no open or closed issues that are related to my idea

Affected Module
Feature (Default)
Description
希望的是将数据能够计算后存储在hadoop/hive 与clickhouse 仓库中，能够通过spark /flink/ MR 复杂计算后，将数据刷写在clickhouse 做OLPAP应用
Use Cases
No response
Screenshots / Mockups
No response

Message that will be displayed on users' first issue


GeoJSON.readFeatures missing from documentation

https://openlayers.org/en/latest/apidoc/module-ol_format_GeoJSON-GeoJSON.html
readFeatures is missing from the documentation (and possibly other methods).

We are currently reworking the API docs to use TypeDoc instead of JSDoc. When done, this and other issues with the API docs should be fixed.

Fixed, see:
https://openlayers.org/en/master/apidoc/module-ol_format_GeoJSON-GeoJSON.html


Josue/orb updates

This PR completes part of 8276 and 8647
For tagging, i believe no authentication is necessary because the -checkout command would be use before the tag-repo command would be use and looking at the circleci docs about the -checkout command this is what i saw about authentication : This command will automatically add the required authenticity keys for interacting with GitHub and Bitbucket over SSH

Build is failing

Builds are going to fail since not all job implementations are in main.


Test issue 4

qazxswedcvfrtgbnhy

fgdgdf

@simple-issues-bot not found

@pkarpovich close this issue

@simple-issues-bot close this issue


Service provider auto discovery support not working

The service provider auto discovery is not registering the proper provider.
It registers the TmdbServiceProviderLaravel5 provider instead of TmdbServiceProvider.
This prevent the API from working because the Tmdb\Client singleton is not setup.
Registering the provider manually fix the problem.

you will never get a response my friend believe me !
they will never fix it or merge your pull request
this project is dead someone else needs to maintain it

@SquareBeard Thank you for the report and the steps to fix the issue. I think the auto discovery should work correctly after applying #55.
@laravelish Don't despair! ;) Pull-requests are still welcome and we will do our best to review them.


Bare Metal Updates

Remove AU1 from FAQ and Feature Matrix
Add Bare Metal RAID config KB

This was corrected in one of the later commits.
On Sep 30, 2016, at 8:03 AM, Stephen Veit <notifications<EMAIL_ADDRESS>wrote:
@srveit commented on this pull request.

In Servers/configuring-raid-on-bare-metal-servers.mdhttps://github.com/CenturyLinkCloud/PublicKB/pull/1260#pullrequestreview-2321338:

@@ -0,0 +1,119 @@

+{{{
+"title": "Configure the RAID controller on Bare Metal servers",
+"date": "09-30-2016",
+"author": "Joe Nguyen & Bryan Friedman",
+"attachments": [],
+"contentIsHTML": false,
+"sticky": false
+}}}
+
+
+### Description
+
+This will only apply to Bare Metal server types where configurable RAID/JBOD is supported. For additional information on which server support this feature refer to our Bare Metal FAQ.
Add the filename instead of link

You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/CenturyLinkCloud/PublicKB/pull/1260#pullrequestreview-2321338, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AOfnbl3uNykOeYPrVXyYTd--OO65UMcPks5qvQiQgaJpZM4KKUHY.


Need way to change something in the root path

Library Affected:
sw-build
Browser & Platform:
all browsers
Issue or Feature Request Description:
My server maps /assets to /static and so I need a way to replace assets with static. rootDirectory doesn't work as it only accepts actual paths that exist.

Cf. replacePrefix in sw-precache.

+1

cc @jeffposnick @addyosmani
Using names from this suggestion, modifyUrlPrefix seems like a better name than replacePrefix, stripPrefix and stringPrefixMulti.
modifyUrlPrefix: {
  '/assets': '/static',
  '/dist/app': ''
}

Replace prefix is dropped and forces developer to define an empty string, stripPrefix and stringPrefixMulti are just morphed into the key value approach above.

I'm strongly in favor of just implementing modifyUrlPrefix instead of the trio of original versions of this from sw-precache. Looking at GitHub codesearch, usage of the older versions is low/not there and I don't see this breaking a huge number of folks. Having a migration path for the few that do need this should be sufficient.


Use const enum for the token types

Fix #1712

Current coverage is 100% (diff: 100%)

Merging #1721 into master will not change coverage

@@           master   #1721   diff @@
=====================================
  Files           1       1
  Lines        4005    3988    -17
  Methods         0       0
  Messages        0       0
  Branches      699     699
=====================================
- Hits         4005    3988    -17
  Misses          0       0
  Partials        0       0

Powered by Codecov. Last update 0e34a1f...fefc3dd


Angular 14 Update

Any Date when this project will get the update to Angular 14?
Thanks in advance

Hi @jahusa02, it's on the road and will be released very very soon
(In the meantime, you can force install of v2.4.2, since it's actually compatible with Angular 14)

Thanks!!!

:tada: This issue has been resolved in version 3.0.0 :tada:
The release is available on:

v3.0.0
GitHub release

Your semantic-release bot :package::rocket:

Awesome, thanks!


Propagate error messages from jupyter to the user.

For #7392
Propagate error messages to the user

Codecov Report

Merging #7585 into master will decrease coverage by 0.96%.
The diff coverage is 58.66%.

@@            Coverage Diff             @@
##           master    #7585      +/-   ##
==========================================
- Coverage   58.69%   57.73%   -0.97%
==========================================
  Files         492      492
  Lines       21963    21626     -337
  Branches     3528     3526       -2
==========================================
- Hits        12891    12485     -406
- Misses       8267     8327      +60
- Partials      805      814       +9

Impacted Files
Coverage Δ

src/client/datascience/types.ts
100% <ø> (ø)
:arrow_up:

...ractive-window/interactiveWindowCommandListener.ts
60.3% <ø> (ø)
:arrow_up:

...rc/client/datascience/errorHandler/errorHandler.ts
55.88% <0%> (-8.01%)
:arrow_down:

...ent/datascience/jupyter/jupyterExecutionFactory.ts
72.09% <0%> (-3.52%)
:arrow_down:

.../datascience/interactive-common/interactiveBase.ts
6.22% <0%> (-0.03%)
:arrow_down:

src/client/common/utils/localize.ts
93.92% <100%> (+0.03%)
:arrow_up:

src/client/datascience/jupyter/jupyterExecution.ts
52% <64.06%> (-5.24%)
:arrow_down:

...nt/datascience/jupyter/invalidNotebookFileError.ts
0% <0%> (-75%)
:arrow_down:

.../client/datascience/jupyter/jupyterConnectError.ts
0% <0%> (-66.67%)
:arrow_down:

...science/jupyter/jupyterKernelPromiseFailedError.ts
0% <0%> (-50%)
:arrow_down:

... and 43 more

Continue to review full report at Codecov.

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


Irradiance Model Results

Here are some overviews of the results from Pseudo-irradiance model training
Detailed Description
The models are trained with batches of 256 (Batch of 8 accumulated 32 times), and 256km areas around random PV sites.
Current Issues
The loss drops dramatically quickly then stays flat, regardless of batch norm, number of examples, channels, etc.
Current (May 2nd) best model is located here

Plots from May 2nd model Validation for batch 1: