Fixing apiserver polling frequency

What does this PR do?
The polling frequency of the Node Agent against the DCA is set with kubernetes_metadata_tag_update_freq. This value is used here, we expect an int64 (from the Viper conf).
This value was also used to specify the polling frequency of the DCA against the API Server.
but it was never used until https://github.com/DataDog/datadog-agent/pull/1976 was introduced.
The issue is that it was expecting a Duration
Because of this line https://github.com/DataDog/datadog-agent/blob/866cbc5fa21fb1919587d421fbedf37637a9cabb/pkg/config/config.go#L66
Setting kubernetes_metadata_tag_update_freq to 1m for instance would cause a panic.
Setting it to 1 would set the polling frequency to 1 ns.
This PR introduces apiserver_polling_freq. It speficies the frequency at which the DCA queries the API Server. The Agent's polling frequency is still specified by kubernetes_metadata_tag_update_freq.
This is not a breaking change as the APIServer polling frequency was set to 20 seconds and not customisable prior to #1976, but this has not been released in a stable version.
Therefore, starting from 6.4, the user will be able to configure how often the agent/DCA query the API Server.
Motivation
#1976 helped uncover a bug, this PR aims at fixing the underlying problem.

Super cool catch. Thanks @CharlyF

How does this play with https://github.com/DataDog/datadog-agent/pull/1976/files ?
In a non-DCA scenario, what frequency will the node-agents query the apiserver with?


backdrop-filter: blur not working

Whenever I don't have an opaque background color on my body the backdrop-filter does not render properly:

Unfortunately, there is nothing we can do about this. Possibly when (and if) the project is updated to use winui3. The browser is not aware of the acrylic effect and will treat the background as if it were transparent.

Ahh, understood.
Cheers for the fast reply!

I tried this myself and did not get the same result. Can you link a reproduction so I can check it out?
I could not get a video to work

https://github.com/AidasPa/backdrop-filter-rendering
Here's how it should look (with approximately the same background colors)

and how it looks with vibrancy (comment out the body background-color in the repo)

Here's a really close issue which I have found (solves by setting a background color - which we can't do because vibrancy)
https://github.com/electron/electron/issues/30077

Sorry for the late response. I'd say this can not be fixed by electron-acrylic-window and is an electron issue; there is nothing we can do. Maybe you could use a "virtual background" behind the element using the closest solid color to the window. Feel free to reopen if you have any questions.


Add optimized ReadAll for http responses

What does this PR do?

When the body content length is known it's much faster to pre-allocated the entire buffer once.
When the length is unknown using bytes.NewBuffer + io.Copy is much faster.

Also, added benchmarks to prove the difference.

Why is it important?

When we start using this function in main products it will significantly improve the performance.
Checklist

[x] My code follows the style guidelines of this project
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have added tests that prove my fix is effective or that my feature works

Benchmark
goos: darwin
goarch: arm64
pkg: github.com/elastic/elastic-agent-libs/transport/httpcommon
BenchmarkReadAll/size:_100/unknown_length/io.ReadAll-10                       	    1000	      1232 ns/op	     576 B/op	       3 allocs/op
BenchmarkReadAll/size:_100/unknown_length/bytes.Buffer+io.Copy-10         	    1000	      1219 ns/op	     224 B/op	       4 allocs/op

BenchmarkReadAll/size:_100/known_length/io.ReadAll-10                     	    1000	      1275 ns/op	     576 B/op	       3 allocs/op
BenchmarkReadAll/size:_100/known_length/bytes.Buffer+io.Copy-10           	    1000	      1206 ns/op	     176 B/op	       3 allocs/op

BenchmarkReadAll/size:_102400/unknown_length/io.ReadAll-10                	    1000	     60858 ns/op	  514405 B/op	      24 allocs/op
BenchmarkReadAll/size:_102400/unknown_length/bytes.Buffer+io.Copy-10      	    1000	      9833 ns/op	  106640 B/op	       8 allocs/op

BenchmarkReadAll/size:_102400/known_length/io.ReadAll-10                  	    1000	     44423 ns/op	  514401 B/op	      24 allocs/op
BenchmarkReadAll/size:_102400/known_length/bytes.Buffer+io.Copy-10        	    1000	      9229 ns/op	  106592 B/op	       7 allocs/op

BenchmarkReadAll/size:_1048576/unknown_length/io.ReadAll-10               	    1000	    474003 ns/op	 5241202 B/op	      33 allocs/op
BenchmarkReadAll/size:_1048576/unknown_length/bytes.Buffer+io.Copy-10     	    1000	     81912 ns/op	 1048722 B/op	       8 allocs/op

BenchmarkReadAll/size:_1048576/known_length/io.ReadAll-10                 	    1000	    457693 ns/op	 5241196 B/op	      33 allocs/op
BenchmarkReadAll/size:_1048576/known_length/bytes.Buffer+io.Copy-10       	    1000	     80061 ns/op	 1048674 B/op	       7 allocs/op
PASS
ok  	github.com/elastic/elastic-agent-libs/transport/httpcommon	1.543s

Related issues

Relates https://github.com/elastic/beats/issues/36151

:green_heart: Build Succeeded

Buildkite Build
Commit: 212ef1bd704d76284db8ed457e4e2c1bc609c22d

cc @rdner

❤

https://github.com/golang/go/issues/50774 appears to be the upstream Go issue tracking the inefficiency of io.ReadAll here. Linking it for future reference.
Quoting the explanation of what causes this:

The underlying reason is that ReadAll() uses append to resize its buffer, which goes up by a factor of 1.25 (slightly more in latest Go, but asymptotically the same) each time.
One might measure these alternatives on various axes:
number of bytes allocated and freed
max size of heap required to read a given size
amount of copying while resizing
percentage waste in returned buffer
The current implementation is better on the last one, and much worse on all the others.
append is designed to minimize space wasted at the end of the buffer


Implement encode

This is currently buggy; I can't figure out the checksum to correctly encode any of the test cases.
For example, something that should encode as:
addr1qx2fxv2umyhttkxyxp8x0dlpdt3k6cwng5pxj3jhsydzer3n0d3vllmyqwsx5wktcd8cc3sq835lu7drv2xwl2wywfgse35a3x

instead encodes as
addr1qx2fxv2umyhttkxyxp8x0dlpdt3k6cwng5pxj3jhsydzer3n0d3vllmyqwsx5wktcd8cc3sq835lu7drv2xwl2wywfgug0jhp

Notably they are mostly equal, up to the checksum; I suspect the EOF happens when we still have exactly 5 bits left to read;
If I hard code an extra s (and polymod step) at the end of reading the buffer, it works fine for this test case.
Could use some help figuring this out

Woohoo! fixed the bug!


torchdrug can't be installed on modern releases of python (i.e., py39 and py310)

Currently, there's a limitation on the versions of Python on which torchdrug can be installed
https://github.com/DeepGraphLearning/torchdrug/blob/278bcc8cba914d562bd84d749833f2d67a6c11c1/setup.py#L43
I'm not sure why this is here - most of its dependencies are version agnostic.

Hi! I am not sure if I recall the reason correctly. I guess it's the metaclass (e.g. core.Configurable) we used in the codebase may not be compatible with python 3.9. Maybe we need to dig into python 3.9 to see what's the new mechanism for metaclass.

same situation here. The incompatibility issue make it hard to integrate torchDrug into the workflow. Also, TorchDrug could influence other packages outside the typical scope of a package. For example, the default behavior of logging class is changed after import torchdrug.

Same here.  Would be nice if torchdrug can live with newer python.  Hope also the newer protein library can be compatible too!

Same situation when I used Python 3.10. It will be nice to support new python version

+1

Any progress on this? I would like to use torchdrug bug I cannot use a version of python earlier than 3.10.

Any progress on this? I would like to use torchdrug bug I cannot use a version of python earlier than 3.10 in my current project.

Same issue here +1

Installing from source seems to work
git clone https://github.com/DeepGraphLearning/torchdrug
cd torchdrug
pip install -r requirements.txt
python setup.py install


fix(chatbar): unintentional sends

What this PR does 📖

when typing fast, i get caught up because in uplink, the enter key works on keyup instead of on keydown. This PR makes the enter key work on keydown. Hopefully this results in a nicer typing experience.

testing:

It should prevent extra sends resulting from holding down the enter key.
It should allow one to enter a  newline in a message and release the shift key before the enter key, and not send the message.
this should work with the left and right shift keys and the enter key and numpad enter key.
the arrow key functionality should be unaffected.

Which issue(s) this PR fixes 🔨

Resolve #1315

Special notes for reviewers 🗒
Additional comments 🎤

@stavares843  good job on finding something. should be fixed now.


Download and verify Bitcoin Core: Link to release signatures

guides/raspibolt/raspibolt_10_preparations.md
The hyperlink in "Compare this value with the release signatures. For the Windows v<IP_ADDRESS> setup binaries.." points to the release signatures of Bitcoin Core 0.16.3.
https://bitcoin.org/bin/bitcoin-core-0.16.3/SHA256SUMS.asc
Instead of the release signatures of Bitcoin Core <IP_ADDRESS>.
https://bitcoin.org/bin/bitcoin-core-<IP_ADDRESS>/SHA256SUMS.asc

Thanks, fixed!


Problem with on_xx_complete

Hello, How are you? I hope you're doing well!
I have a problem where 'on_work_complete' executes when I complete a break
Here is what I'm trying to do:

Hi, how are you. I will try to look into detail whats going on, i dont know about the notify plugin, i will try it. In the meantime, whats the failure in this case? Could it be it has something to do with vim.notify VS notify only?

I tried to remove notify, but still it doesn't want to call 'on_break_complete' like it's not there.

I think there is a problem right now if you put the same time on Break that on Work, could you try put different numbers there to see if callbacks are working good from your side.
I plan to make a fix on that but just to be sure thats just the issue. Didnt expect to have same time on those fields, hehe.

You are right!, when I changed their values it starts to work correctly


Switch to the HDF5-based v1 format for serialization.

@jkanche I changed the format of the QC results, the message handler on the main thread will need to be updated.

Needs a bit of testing.


Guide on Creating ARM64 Android GSI Images for UTM

Since Android images have been removed from UTM, there should at least be a guide on how to create your own. I looked everywhere, but it seems that everyone is using the x86 version of it with no information whatsoever about how to create an ARM64 image.
The lack of resources on building an ARM64 Android GSI image makes it difficult for users who want to run Android on ARM-based systems using UTM. It would be incredibly helpful to have a comprehensive guide that covers the following aspects:

Prerequisites: Tools and software needed for building the image.
Downloading the Android Source: Steps to obtain the necessary Android files.
Building the GSI Image: Detailed instructions on the build process.
Configuration Settings: Recommended configurations for UTM compatibility.
Testing the Image: How to test the created image in UTM.

If anyone has experience or can contribute to this guide, it would greatly benefit the community. Thank you for considering this request!

yes i need run android 10-14 on utm with my ipad

They've been removed because Android isn't supported because we don't support GPU acceleration which android requires to do anything useful. Even if you get it working, it is so slow that it's worthless.

someone was test lineageOS 21 on utm hv, but idk to make it and succesfull


Possible to define Navigator Stack 'type' in Action call?

react-native-router-flux v3.26
react-native v0.26

Is it possible to pass in the way I want the navigator to handle the stack in the Action call?
For example calling Action.index({  type: 'push' }) would render the welcome component by pushing it to the stack. However calling Action.index( type: 'replace' }) would render the welcome component but would replace instead of pushing.
Basically I would like to control how the Navigator stack is controlled on the link level instead of the scene level.

That's exactly how it currently works - have you tried it and it's not working?

I tried it put then it seems to call the action, so if I pass it with 'push' you can see the stack animation for push and then it replaces it. I will try again and post a GIF. Thanks


Improve font-size for new lead h1

Description

Adds line break to the new tagline to improve readability
Improves the font-sizing on smaller screens to make the <h1/> stand out more

Think we could follow this up with a clean up of that leading hero section too, as it doesn't scream "home page" to me at the moment.

Think we could follow this up with a clean up of that leading hero section too, as it doesn't scream "home page" to me at the moment.

What elements would make it feel more like a 'home page' to you?
It's definitely open to revision. The current layout follows a standard hero structure with a headline, brief description, CTAs, supporting visuals (the video), and social proof, but happy to explore any suggestions!

What elements would make it feel more like a 'home page' to you?

Think we can emphasise the H1 better, it's currently styled the same as our other headers on that page, and reads very formal/enterprisey/boring.
If you consider:

https://buildship.com/
https://n8n.io/
https://posthog.com/
https://about.gitlab.com/

All of these have more emphasis on the single sales-pitch tag line


Slider control is not working in Chrome for .mp4 video hosted on aws S3

Be sure to search for your issue before opening a new one.
Current Behavior

While moving slider control (inbuild controls={true} and input type="range" both) in chrome is not working.
state = {
loaded: 0.22060537477940495
loadedSeconds: 7.125333
played: 0
playedSeconds: 0}
After mouseUp, slider reaches to start (played: 0, and playedSeconds: 0) ;
Expected Behavior

Slider should work in chrome as smooth as it's working in Safari and Firefox.
Environment

URL attempting to play: .mp4 hosted on AWS s3
Browser: Chrome
Operating system: MacOS mojave , Version: 10.14.6

Solved it, by setting range attribute in headers.
ref:-https://stackoverflow.com/questions/3303029/http-range-header


add support for monitoring capabilities

User story
As a wis2node operator, I need to monitor

the services provided by the wis2node to be able to intervene in case a service has an issue
the incoming data in terms of the number of data from the configured data sources (stations or processes) and compare with an expected baseline. I need to be able to communicate to relevant teams issues regarding the decrease in incoming data or gaps with the baseline.
the workflow inside the wis2box. I need to be able to identify errors in the processing chain and reproduce them so that I can involve the relevant team for fixes.
tracking of metrics of data processing (passes, failures, logs)

Acceptance criteria

[ ] acceptance criteria 1
[ ] acceptance criteria 2
[ ] acceptance criteria 3

Definition of done

[ ] unit/functional tests added/updated
[ ] documentation updated
[ ] live demonstration provided

From meeting 2022-03-10:
Types of monitoring:

service/healthcheck monitoring (uptime/behaviour)

WAF
MQTT
API

internal wis2box workflow
status of incoming data (number of messages)
state of publishing
absolute counts as first pass (can deal with KPIs in later phase)

Initial capability implemented in #168 -- thanks @maaikelimper !


feat: visual distinction between instructions and code

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #45352

Following up on https://github.com/freeCodeCamp/freeCodeCamp/issues/45352#issuecomment-1064096301

Darkened border color of upper and lower jaws
Added Monaco selected line border color

Okay I implemented your suggestion. Ready for review and merge :+1:

Thank you for making the requested changes.


add completion supports to istioctl namespace and experimental

Add completion supports to istioctl namespace and experimental.
$ istioctl -i <tab><tab>
hellobaby          istio-system          kube-public                metallb-system
default               istio-demo            kube-system
$ istioctl -i istio-system -n <tab><tab>
hellobaby          istio-system          kube-public                metallb-system
default               istio-demo            kube-system
$ istioctl x describe service <tab><tab>
go-proxy   go-server  nginx
$ istioctl x describe pod <tab><tab>
debian-77dc9c5f4f-vrwj5                httpbin-66cdbdb6c5-l58q7               nginx-74f5bd857c-9hh2c

[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[X] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[X] Does not have any user-facing changes. This may include CLI changes, API changes, behavior changes, performance improvements, etc.

@silenceshell: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
4ae8783810f9289e9d950749f320448fcd7931cf
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@silenceshell: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
4ae8783810f9289e9d950749f320448fcd7931cf
link
/test lint_istio

gencheck_istio
4ae8783810f9289e9d950749f320448fcd7931cf
link
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@silenceshell: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_istio
4ae8783810f9289e9d950749f320448fcd7931cf
link
/test gencheck_istio

lint_istio
96bcb450e78887ffb37aee717d6d40dda49965f3
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@silenceshell: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
96bcb450e78887ffb37aee717d6d40dda49965f3
link
/test lint_istio

gencheck_istio
96bcb450e78887ffb37aee717d6d40dda49965f3
link
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@silenceshell: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_istio
96bcb450e78887ffb37aee717d6d40dda49965f3
link
/test gencheck_istio

lint_istio
9d87cf345f98733c173515ffbe19c8c062f4aa44
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@silenceshell: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
9d87cf345f98733c173515ffbe19c8c062f4aa44
link
/test lint_istio

gencheck_istio
9d87cf345f98733c173515ffbe19c8c062f4aa44
link
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@silenceshell: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
9d87cf345f98733c173515ffbe19c8c062f4aa44
link
/test lint_istio

gencheck_istio
9d87cf345f98733c173515ffbe19c8c062f4aa44
link
/test gencheck_istio

integ-multicluster-k8s-tests_istio
9d87cf345f98733c173515ffbe19c8c062f4aa44
link
/test integ-multicluster-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@silenceshell: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-multicluster-tests_istio
bc3d8d69f5ab412004374137f412448342f60309
link
/test integ-pilot-multicluster-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@silenceshell: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-multicluster-tests_istio
bc3d8d69f5ab412004374137f412448342f60309
link
/test integ-pilot-multicluster-tests_istio

integ-security-multicluster-tests_istio
bc3d8d69f5ab412004374137f412448342f60309
link
/test integ-security-multicluster-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@silenceshell: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-multicluster-tests_istio
bc3d8d69f5ab412004374137f412448342f60309
link
/test integ-security-multicluster-tests_istio

integ-pilot-multicluster-tests_istio
bc3d8d69f5ab412004374137f412448342f60309
link
/test integ-pilot-multicluster-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

I believe we do need to add some release note text for this change.

I believe we do need to add some release note text for this change.

Thanks, I have removed the release-note-none label.

@silenceshell: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-mc-k8s-tests_istio
8d2e27bcce96cbbeded0f4589985949171d1b3f1
link
/test integ-telemetry-mc-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@silenceshell: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-mc-k8s-tests_istio
8d2e27bcce96cbbeded0f4589985949171d1b3f1
link
/test integ-telemetry-mc-k8s-tests_istio

release-notes_istio
178b8915d6a11ff4237736e0d932b7b3c2f4a964
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@silenceshell: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-mc-k8s-tests_istio
8d2e27bcce96cbbeded0f4589985949171d1b3f1
link
/test integ-telemetry-mc-k8s-tests_istio

release-notes_istio
178b8915d6a11ff4237736e0d932b7b3c2f4a964
link
/test release-notes_istio

lint_istio
178b8915d6a11ff4237736e0d932b7b3c2f4a964
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@silenceshell: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-mc-k8s-tests_istio
8d2e27bcce96cbbeded0f4589985949171d1b3f1
link
/test integ-telemetry-mc-k8s-tests_istio

release-notes_istio
178b8915d6a11ff4237736e0d932b7b3c2f4a964
link
/test release-notes_istio

lint_istio
178b8915d6a11ff4237736e0d932b7b3c2f4a964
link
/test lint_istio

analyze-tests_istio
178b8915d6a11ff4237736e0d932b7b3c2f4a964
link
/test analyze-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@silenceshell: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
178b8915d6a11ff4237736e0d932b7b3c2f4a964
link
/test lint_istio

analyze-tests_istio
178b8915d6a11ff4237736e0d932b7b3c2f4a964
link
/test analyze-tests_istio

release-notes_istio
4f7c424dcc5bfa8f7f3b2dbe8ae3b2d32ffc5b2f
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@silenceshell: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
4cfc387b19a4e7d16a432576c12f8d07dcb51cc6
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@silenceshell: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
a38a38f58556123091a46bddd202f9365212f320
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@silenceshell: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
8ab39161f8eb6ad6c2540bfc4eea4d2c2c99fb46
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@silenceshell: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
b9f34758a1cd7df59d774d500398190fe5d8af9a
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@silenceshell: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-mc-k8s-tests_istio
cbf1d4d71cb79e6bb419a1e8328c6b203a1d978b
link
/test integ-telemetry-mc-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@silenceshell: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-mc-k8s-tests_istio
cbf1d4d71cb79e6bb419a1e8328c6b203a1d978b
link
/test integ-telemetry-mc-k8s-tests_istio

integ-security-multicluster-tests_istio
cbf1d4d71cb79e6bb419a1e8328c6b203a1d978b
link
/test integ-security-multicluster-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@silenceshell: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-multicluster-tests_istio
3fe36981dcbc9c67e61e506b0546079a14c01666
link
/test integ-pilot-multicluster-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@shamsher31 Would you please to review this PR? This is similar to #33367 .

@silenceshell: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
88fe7aca565ee8f982eff119d5a8169b6bc2a2d2
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

/retest


auto-generated lists - more that one group

Is your feature request related to a problem? Please describe.
First, for auto-generated lists, it would be great if more than group could be specified:
Describe the solution you'd like
I would like to create an email list "Club wide distribution" which includes all the groups that the list should include. Likewise, it would be helpful if more than one type could be specified of who in the groups the list applies to.

Submitted by @cloudadikt extracted from https://github.com/ColinRobbins/scm-helper/issues/53


Kitchen tests failing on creating /etc/sudoers.d/kitchen

Greetings, I am getting the following error when running kitchen tests with the latest version of kitchen-docker (1.7.0):
Step 8 : RUN echo 'kitchen ALL=(ALL) NOPASSWD:ALL' >> /etc/sudoers.d/kitchen  ---> Running in 6231397dcf8f /bin/sh: /etc/sudoers.d/kitchen: No such file or directory
On another box running version 1.5.0 of kitchen-docker, this problem does not exist as the RUN echo '#{username} ALL=(ALL) NOPASSWD:ALL' >> /etc/sudoers.d/#{username} is not in the docker.rb file.
As a workaround, I've deleted this line from my docker.rb file. This is on a CentOS 5 docker container. I have not tested against any other docker OS containers.
Thanks,
Jonathan

We could add a test for the sudoers directory prior to running that line.

Works for me. However, I don't fully understand the need for writing to this file if you're writing to /etc/sudoers already. Could you elaborate on that?

I'm getting the same, on ubuntu 10.04:
      Step 7 : RUN echo kitchen:kitchen | chpasswd
        ---> Running in 77abbcfba4ef
        ---> 635dd16f6e5f
       Removing intermediate container 77abbcfba4ef
       Step 8 : RUN echo 'kitchen ALL=(ALL) NOPASSWD:ALL' >> /etc/sudoers
        ---> Running in bc6b2bbe6626
        ---> 5b84667c8f50
       Removing intermediate container bc6b2bbe6626
       Step 9 : RUN echo 'kitchen ALL=(ALL) NOPASSWD:ALL' >> /etc/sudoers.d/kitchen
        ---> Running in 27eb705f5b7b
        ---> 0e9a05c25706
       Removing intermediate container 27eb705f5b7b
       Successfully built 0e9a05c25706
       e2d225bff003657e050ccda26da669bf2ebe0e7a463094603a57d15fcb4e95b2
       [{
...
       sudo: /etc/sudoers.d/kitchen is mode 0644, should be 0440
       >>> /etc/sudoers.d/README: /etc/sudoers.d/kitchen near line 18 <<<
       sudo: parse error in /etc/sudoers.d/README near line 18

       sudo: no valid sudoers sources found, quitting

Looks to have been introduced here: https://github.com/portertech/kitchen-docker/commit/03b2a30d66a7a35ad9f2c5b16511651de6390deb
From the README inside the sudoers.d directory on Ubuntu 12.04:

As of Debian version 1.7.2p1-1, the default /etc/sudoers file created on
installation of the package now includes the directive:
#includedir /etc/sudoers.d
...
Note that there must be at least one file in the sudoers.d directory (this
one will do), and all files in this directory should be mode 0440.

I believe that older CentOS versions didn't have the sudoers.d logic at all.
I can confirm that downgrading to 1.5.0 solves this particular problem.
Out of curiosity, why was the sudoers.d method introduced?

Also confirmed that /etc/sudoers.d does not exist in Cent5, and does in Cent6.

I can confirm I'm currently seeing this on ubuntu 12.04
-----> Creating <default-ubuntu-1204>...
       Sending build context to Docker daemon  2.56 kB
       Sending build context to Docker daemon
       Step 0 : FROM ubuntu:12.04
        ---> f959d044ebdf
       Step 1 : RUN dpkg-divert --local --rename --add /sbin/initctl
        ---> Running in f81f842d9775
       Leaving 'local diversion of /sbin/initctl to /sbin/initctl.distrib'
        ---> 3c2f332f2047
       Removing intermediate container f81f842d9775
       Step 2 : RUN ln -sf /bin/true /sbin/initctl
        ---> Running in 3b40f99a4021
        ---> aab0df78640c
       Removing intermediate container 3b40f99a4021
       Step 3 : ENV DEBIAN_FRONTEND noninteractive
        ---> Running in 3679ec52a771
        ---> 6204a11c5de1
       Removing intermediate container 3679ec52a771
       Step 4 : RUN apt-get update
        ---> Running in a51fff60e496
       Hit http://archive.ubuntu.com precise Release.gpg
        ...
       Get:31 http://archive.ubuntu.com precise-security/universe i386 Packages [145 kB]
       Fetched 28.9 MB in 44s (654 kB/s)
       Reading package lists...
        ---> c0219b03987c
       Removing intermediate container a51fff60e496
       Step 5 : RUN apt-get install -y sudo openssh-server curl lsb-release
        ---> Running in 68e62dcfff57
       Reading package lists...
       Building dependency tree...
       Reading state information...
       The following extra packages will be installed:
        ...
       Suggested packages:
        ...
       The following NEW packages will be installed:
        ...
       The following packages will be upgraded:
         python2.7-minimal
       1 upgraded, 54 newly installed, 0 to remove and 9 not upgraded.
       Need to get 12.4 MB of archives.
       After this operation, 34.9 MB of additional disk space will be used.
       Get:1 http://archive.ubuntu.com/ubuntu/ precise-updates/main libsqlite3-0 amd64 3.7.9-2ubuntu1.1 [349 kB]
        ...
       Get:55 http://archive.ubuntu.com/ubuntu/ precise/main ssh-import-id all 2.10-0ubuntu1 [6598 B]
       debconf: delaying package configuration, since apt-utils is not installed
       Fetched 12.4 MB in 14s (862 kB/s)
        ...
       Processing triggers for libc-bin ...
       ldconfig deferred processing now taking place
        ---> e2523991a2e1
       Removing intermediate container 68e62dcfff57
       Step 6 : RUN useradd -d /home/kitchen -m -s /bin/bash kitchen
        ---> Running in 423a5001b6cf
        ---> 44f551f6494b
       Removing intermediate container 423a5001b6cf
       Step 7 : RUN echo kitchen:kitchen | chpasswd
        ---> Running in b2bb47768da3
        ---> 5d927be264b1
       Removing intermediate container b2bb47768da3
       Step 8 : RUN echo 'kitchen ALL=(ALL) NOPASSWD:ALL' >> /etc/sudoers
        ---> Running in 2a1e6a8146a2
        ---> 63dc8108e171
       Removing intermediate container 2a1e6a8146a2
       Step 9 : RUN echo 'kitchen ALL=(ALL) NOPASSWD:ALL' >> /etc/sudoers.d/kitchen
        ---> Running in 885a960552df
        ---> 10b518f69700
       Removing intermediate container 885a960552df
       Step 10 : RUN curl -L https://www.opscode.com/chef/install.sh | bash
        ---> Running in 89816ff9d43e
         % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                        Dload  Upload   Total   Spent    Left  Speed
100 18378  100 18378    0     0  39025      0 --:--:-- --:--:-- --:--:-- 57431
       Downloading Chef  for ubuntu...
       downloading https://www.opscode.com/chef/metadata?v=&prerelease=false&nightlies=false&p=ubuntu&pv=12.04&m=x86_64
         to file /tmp/install.sh.9/metadata.txt
       trying wget...
       url	https://opscode-omnibus-packages.s3.amazonaws.com/ubuntu/12.04/x86_64/chef_12.0.3-1_amd64.deb
       md5	e849cf61d3e3fd37224c11f9902aa536
       sha256	a8e9c78cc9b9a17a32b9b4ae1650b8b6454b4f0abd611048d099a659ca5de28f
       downloaded metadata file looks valid...
       downloading https://opscode-omnibus-packages.s3.amazonaws.com/ubuntu/12.04/x86_64/chef_12.0.3-1_amd64.deb
         to file /tmp/install.sh.9/chef_12.0.3-1_amd64.deb
       trying wget...
       Comparing checksum with sha256sum...
       Installing Chef
       installing with dpkg...
       Selecting previously unselected package chef.
       (Reading database ... 9171 files and directories currently installed.)
       Unpacking chef (from .../chef_12.0.3-1_amd64.deb) ...
       Setting up chef (12.0.3-1) ...
       Thank you for installing Chef!
        ---> dc77ed109c39
       Removing intermediate container 89816ff9d43e
       Successfully built dc77ed109c39
       Warning: '-privileged' is deprecated, it will be replaced by '--privileged' soon. See usage.
       cd7c225ebb1af3299bc3291afc68b431c8ed8660159326c061d84cea9ab081e9
       [{
           "AppArmorProfile": "",
           "Args": [
        "-D",
        "-o",
        "UseDNS=no",
        "-o",
        "UsePAM=no",
        "-o",
        "PasswordAuthentication=yes",
        "-o",
        "UsePrivilegeSeparation=no",
        "-o",
        "PidFile=/tmp/sshd.pid"
           ],
           "Config": {
        "AttachStderr": false,
        "AttachStdin": false,
        "AttachStdout": false,
        "Cmd": [
            "/usr/sbin/sshd",
            "-D",
            "-o",
            "UseDNS=no",
            "-o",
            "UsePAM=no",
            "-o",
            "PasswordAuthentication=yes",
            "-o",
            "UsePrivilegeSeparation=no",
            "-o",
            "PidFile=/tmp/sshd.pid"
        ],
        "CpuShares": 0,
        "Cpuset": "",
        "Domainname": "",
        "Entrypoint": null,
        "Env": [
            "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
            "DEBIAN_FRONTEND=noninteractive"
        ],
        "ExposedPorts": {
            "22/tcp": {}
        },
        "Hostname": "cd7c225ebb1a",
        "Image": "dc77ed109c39",
        "MacAddress": "",
        "Memory": 0,
        "MemorySwap": 0,
        "NetworkDisabled": false,
        "OnBuild": null,
        "OpenStdin": false,
        "PortSpecs": null,
        "StdinOnce": false,
        "Tty": false,
        "User": "",
        "Volumes": null,
        "WorkingDir": ""
           },
           "Created": "2015-02-10T23:50:35.881680058Z",
           "Driver": "aufs",
           "ExecDriver": "native-0.2",
           "HostConfig": {
        "Binds": null,
        "CapAdd": null,
        "CapDrop": null,
        "ContainerIDFile": "",
        "Devices": [],
        "Dns": null,
        "DnsSearch": null,
        "ExtraHosts": null,
        "IpcMode": "",
        "Links": null,
        "LxcConf": [],
        "NetworkMode": "bridge",
        "PortBindings": {
            "22/tcp": [
                {
                    "HostIp": "",
                    "HostPort": ""
                }
            ]
        },
        "Privileged": true,
        "PublishAllPorts": false,
        "RestartPolicy": {
            "MaximumRetryCount": 0,
            "Name": ""
        },
        "SecurityOpt": null,
        "VolumesFrom": null
           },
           "HostnamePath": "/mnt/sda1/var/lib/docker/containers/cd7c225ebb1af3299bc3291afc68b431c8ed8660159326c061d84cea9ab081e9/hostname",
           "HostsPath": "/mnt/sda1/var/lib/docker/containers/cd7c225ebb1af3299bc3291afc68b431c8ed8660159326c061d84cea9ab081e9/hosts",
           "Id": "cd7c225ebb1af3299bc3291afc68b431c8ed8660159326c061d84cea9ab081e9",
           "Image": "dc77ed109c39a8156c9a02a67ca69c467abae0049fb4411df23fe0df4d9c4f69",
           "MountLabel": "",
           "Name": "/tender_pike",
           "NetworkSettings": {
        "Bridge": "docker0",
        "Gateway": "<IP_ADDRESS>",
        "IPAddress": "<IP_ADDRESS>",
        "IPPrefixLen": 16,
        "MacAddress": "02:42:ac:11:00:6e",
        "PortMapping": null,
        "Ports": {
            "22/tcp": [
                {
                    "HostIp": "<IP_ADDRESS>",
                    "HostPort": "49165"
                }
            ]
        }
           },
           "Path": "/usr/sbin/sshd",
           "ProcessLabel": "",
           "ResolvConfPath": "/mnt/sda1/var/lib/docker/containers/cd7c225ebb1af3299bc3291afc68b431c8ed8660159326c061d84cea9ab081e9/resolv.conf",
           "State": {
        "Error": "",
        "ExitCode": 0,
        "FinishedAt": "0001-01-01T00:00:00Z",
        "OOMKilled": false,
        "Paused": false,
        "Pid": 8879,
        "Restarting": false,
        "Running": true,
        "StartedAt": "2015-02-10T23:50:36.239977741Z"
           },
           "Volumes": {},
           "VolumesRW": {}
       }
       ]
       Finished creating <default-ubuntu-1204> (2m25.75s).
-----> Converging <default-ubuntu-1204>...
       Preparing files for transfer
       Preparing dna.json
       Resolving cookbook dependencies with Berkshelf 3.2.3...
       Removing non-cookbook files before transfer
       Preparing data_bags
       Preparing environments
       Preparing validation.pem
       Preparing client.rb
       sudo: /etc/sudoers.d/kitchen is mode 0644, should be 0440
       Transferring files to <default-ubuntu-1204>
       sudo: /etc/sudoers.d/kitchen is mode 0644, should be 0440
       Starting Chef Client, version 12.0.3
       Creating a new client identity for default-ubuntu-1204 using the validator key.
        ...

       Running handlers:
       Running handlers complete
       Chef Client finished, 26/28 resources updated in 8.338013181 seconds
       Finished converging <default-ubuntu-1204> (0m19.53s).

also seeing issues running centos5 containers. Centos5 doesn't have /etc/sudoers.d nor does the version of sudo on cent5 support it.
:+1:  for testing first, but also note that some platforms don't support includes.

seeing the same as @brandocorp on ubuntu-12.04
sudo: /etc/sudoers.d/kitchen is mode 0644, should be 0440

This should be resolved for centos5, can't speak for ubuntu-12.04

Closing issue due to inactivity. Please open a new issue if there is still a problem. Thanks!


Godot 3.2 export android

Godot version:
Godot 3.2.dev commit id:0239d8bd9fa03965439aac2482d18746f807bd00
OS/device including version:
Linux Manjaro
Issue description:
I don't know if this is an issue or not, simply I don't know how to test the new android export. I follow the documentation instruction, but Godot doesn't create the android project template. I attach some screenshot to better understand.

Tell me the template is missing but I have installed all templates.

It's a bug or is intended to do this for now? How can I test the new android export for some feedback?
Steps to reproduce:
Look the screenshot
Minimal reproduction project:

The templates have to be exactly match for your version of Godot, so if you compiled from master yourself, you also need to compile the templates. And I think there might be something wrong with creation of android templates right now. I was not able to compile it myself few days ago. Everything looked like it's going all right, but there was no templates in the folder after all. Looks like #28498 has something to do with this.

@freemanfromgodotengine They are now in another folder (not copied to /bin anymore).

You can find the generated apk in godot/platform/android/java/build/outputs/apk

@erammos I can't find the .apk there on /android/java although the folder should be correct. Don't know what I'm doing wrong.

I can't find the .apk there on /android/java although the folder should be correct. Don't know what I'm doing wrong.

Btw, i can't export the gradle project from "Install Android Build Template", I get the same error "Android build template is missing", although i have installed the template

Well I have managed to solve that issue. You have to take everything in godot/platform/android/java/  (except the Build folder), zip them in a file named as "android_source.zip" and  last copy-paste it in your templates folder 3.2.dev

There is no android_source.zip on godot server so it won't work. Apk file won't going to work. Zipping java  folder works but it does not work on android phone, i.e crashes( might be some other bug).

There is no android_source.zip on godot server so it won't work. Apk files won't going to work. Zipping java folder works but it does not work on android phone, i.e crashes( might be some other bug).

Maybe the engine libs are missing in java folder... you have to compile the engine first (scons platform = android )

I did copy pasted lib folder in android_source.

If it crashes, your best option is to run adb logcat and open an issue with the log.

I do not have the android_source.zip file in my templates folder and I can still build for android perfectly fine, for oculus quest and a normal android device @erammos


Philips impress wall light small

Can you please add device Impress wall light small. The one in the app is the "normal/big" one not the small.
See attachment for details.
Device ID 1742930P7
Thnx!

Hi @EmielPijn, thanks for your request. I put it on the todo list :)

Added

Wow, that was fast. Thnx!!

Hi Johan, I tried adding the light today but it is not working. I get the message "There is no Homey app found for this device. The device is added as simple zigbee device." See attachment(it is in dutch but that's what it said).
Did I something wrong? Or is there a bug or something?


2.6.0 image is just a plain raspbian, nothing preconfigured

Just installed the 2.6.0 image, should be ready configured but the /root directory does not contain any adsb-receiver folder. You need to perform the quick install guide, get it from GIT, run install.sh and so on. Basically what you receive in 2.6.0 image is just raspbian jesssie and that's it.

check the pi users home directory not roots.
/home/pi/adsb-receiver


OLS-833: Bump-up sentence transformer library

Description
Bump-up sentence transformer library
Type of change

[ ] Refactor
[ ] New feature
[ ] Bug fix
[ ] CVE fix
[ ] Optimization
[ ] Documentation Update
[ ] Configuration Update
[x] Bump-up dependent library
[ ] Bump-up library or tool used for development (does not change the final image)

Related Tickets & Documents

Related Issue #OLS-833

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 92.29%. Comparing base (e2af104) to head (6e5ba06).
Report is 12 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1281      +/-   ##
==========================================
- Coverage   94.75%   92.29%   -2.46%
==========================================
  Files          57       57
  Lines        2441     2441
==========================================
- Hits         2313     2253      -60
- Misses        128      188      +60

see 10 files with indirect coverage changes

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/hold

/retest


fix(curriculum): Update if statement explanation for RPG game step 76

Checklist:

[x] I have read and followed the contribution guidelines.
[x] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #53429

Overview

Delete step 77
Update description and test of step 76

Hi @altsun !
We just merged in another PR here that addresses the same issue.
As a result, we are going to close this one


Generate access tokens for the autograder

When starting an autograder run, the user has to provide an access token. This is pretty annoying.
Instead, we can generate an OAuth token (client_id hardcoded to "autograder") when the user hits the "autograde" button, and pass this to the autograder instead.

After this, we won't need to fill out a form for autograding all or a single submission. We can just hit a button instead.

Resolved in #913


Support discarding nullable discriminated fields if discriminator match is not found

Initial Checks

[X] I have searched Google & GitHub for similar requests and couldn't find anything
[X] I have read and followed the docs and still think this feature is missing

Description
I have an app config which is basically a list of configs, which will get matched up to some workflows that will get run when a CLI command is executed:
# Reduced example

class ToolsCLIConfig(BaseModel):
    config_targets: list[Annotated[ConfigTargetConfig, Field(..., discriminator="type")]]

ConfigTargetConfig: TypeAlias = (
    AWSCodeArtifactPIPConfigTarget
    | AWSCodeArtifactNPMConfigTarget
)

class AWSCodeArtifactPIPConfigTarget(BaseModel):
    type: Literal["AWS_CODEARTIFACT_PIP"] = "AWS_CODEARTIFACT_PIP"
    authenticator: AWSCodeArtifactAuthenticatorConfig
    repository: str

class AWSCodeArtifactNPMConfigTarget(BaseModel):
    type: Literal["AWS_CODEARTIFACT_NPM"] = "AWS_CODEARTIFACT_NPM"
    authenticator: AWSCodeArtifactAuthenticatorConfig
    repository: str

The current situation is, if we add a new ConfigTargetConfig (say AWSCodeArtifactYarnConfigTarget), and push the updated config to the clients, clients running on the older version will break, effectively rendering a new capability as a breaking change.
What we want to happen, is for the new ConfigTargetConfig whose type doesn't match any of the available types, to be discarded and not appear in the list.
Perhaps a different form of types.Discriminator could be added which would allow the callable to return a sentinel value indicating the field should be dropped, and only allow that discriminator to be used as part of nullable fields?
If there already is a way to achieve this, please do tell me.
Affected Components

[ ] Compatibility between releases
[X] Data validation/parsing
[ ] Data serialization - .model_dump() and .model_dump_json()
[ ] JSON Schema
[ ] Dataclasses
[X] Model Config
[X] Field Types - adding or changing a particular data type
[ ] Function validation decorator
[X] Generic Models
[ ] Other Model behaviour - model_construct(), pickling, private attributes, ORM mode
[ ] Plugins and integration with other tools - mypy, FastAPI, python-devtools, Hypothesis, VS Code, PyCharm, etc.

Hmm, this reminds me a bit of https://github.com/pydantic/pydantic/issues/8394

Going to close this as a duplicate, as I think this is basically asking for an omittable annotation as explained in the other issue. That being said, I'll come up with a workaround for you in the meantime 👍

I think this example might be somewhat helpful, but I'd agree there's no clean way to achieve this right now: https://docs.pydantic.dev/latest/concepts/json/#partial-json-parsing

from pydantic import BaseModel, ValidationError, field_validator, Field, WrapValidator
from pydantic_core import PydanticUseDefault
from typing import Literal, TypeAlias, Any, final
from typing_extensions import Annotated

class Dog(BaseModel):
    type: Literal['dog'] = 'dog'

class Cat(BaseModel):
    type: Literal['cat'] = 'cat'

Pet: TypeAlias = Dog | Cat

# new type
class Fish(BaseModel):
    type: Literal['fish'] = 'fish'

def default_on_error(v, handler) -> Any:
    try:
        return handler(v)
    except ValidationError:
        raise PydanticUseDefault()

@final
class _UnrecognizedType: ...

_UnrecognizedTypeDefault: Any = _UnrecognizedType()

class Model(BaseModel):
    pets: list[
        Annotated[Pet, Field(default=_UnrecognizedTypeDefault, discriminator='type'), WrapValidator(default_on_error)]
    ]

    @field_validator('pets', mode='after')
    def remove_nulls(cls, v) -> list[Pet]:
        return [x for x in v if x is not _UnrecognizedTypeDefault]

print(repr(Model(pets=[Cat(), Dog(), Fish()])))
#> Model(pets=[Cat(type='cat'), Dog(type='dog')])

Hey @sydney-runkle, thanks for looking into this. Agreed, the proposal you linked to would solve this issue.
Here's what we ended up going with in the meantime after discussing internally:
class ToolsCLIConfig(BaseModel, extra="ignore"):
    aws_codeartifact_pip_config_targets: list[AWSCodeArtifactPIPConfigTarget]
    aws_codeartifact_npm_config_targets: list[AWSCodeArtifactNPMConfigTarget]

    @property
    def config_targets(self: Self) -> list[ConfigTargetConfig]:
        return self.aws_codeartifact_pip_config_targets + self.aws_codeartifact_npm_config_targets

ConfigTargetConfig: TypeAlias = (
    AWSCodeArtifactPIPConfigTarget
    | AWSCodeArtifactNPMConfigTarget
)

class AWSCodeArtifactPIPConfigTarget(BaseModel):
    type: Literal["AWS_CODEARTIFACT_PIP"] = "AWS_CODEARTIFACT_PIP"
    authenticator: AWSCodeArtifactAuthenticatorConfig
    repository: str

class AWSCodeArtifactNPMConfigTarget(BaseModel):
    type: Literal["AWS_CODEARTIFACT_NPM"] = "AWS_CODEARTIFACT_NPM"
    authenticator: AWSCodeArtifactAuthenticatorConfig
    repository: str


fix promise tests

Previously, the unit test for Promise.add wasn't testing the correct method. This change resolves that problem and modifies add rejection so that it behaves as described in the documentation.

@Theodus in the future the comment you have
Previously, the unit test for Promise.add wasn't testing the correct method. This change resolves that problem and modifies add rejection so that it behaves as described in the documentation.

can you put that in the commit message body?

@SeanTAllen sure, I'll do that in the future.


House number inside buildings

Hey,
in my area a lot of buildings are tagged with their address as part of the building. But I always have to click on the building to see if there is an address added. Like in this example it's Schrödingers houses, some have an adress others not:

Is it possible to modify the inside of the shape of buildings to see directly the house number or if there is an adress already added. Maybe an example how it could look like:

Thanks!

Yes, @edpop is working on this 👍
This will be a wonderful feature once it's ready..
See discussion on #3840 and #1524


Problem with "Back To Top" Option in Footer of all pages

I can work on this, can you assign this to me and can you give a little bit of description about the issue.
Thank you

Go ahead @rko0211


Get self-host server from CSC

Waiting from email reply.

CSC has gotten back to us and created a waterloorocketry group. In addition, team files can be found in `/users/uwrocketryteam.
The following users have been made "club representitives", allowing them to manage access to the team account and group:
@QuantumManiac
@PCModeActivate
@KavinSatheeskumar
@Darth-Raazi
Please reach out to them if you need access to the team account for yourself.


Bug 2108054: Add ReadGenericWithUnstructured

And change ApplyDirectly + StaticResourceController to use it.
This allows StaticResourceController.RelatedObjects() to process unknown
types as Unstructured, like PrometheusRules.

/lgtm


"latest" in new documentation navbar is invisible

On https://datasette.readthedocs.io/en/latest/

Compare with https://datasette.readthedocs.io/en/0.45/

Some custom CSS should fix it.

.wy-side-nav-search > div.version {
    margin-top: -.4045em;
    margin-bottom: .809em;
    font-weight: normal;
    color: rgba(255,255,255,0.3);
}

Fix can go here: https://github.com/simonw/datasette/blob/ee0ef016523a765b6ef6eaa43cad9ad568f78ae4/docs/_static/css/custom.css#L1-L3

Fixed https://datasette.readthedocs.io/en/latest/


[BEAM-10460] Limit SparkPortableExecutionTest to a single thread.

Starting up multiple Spark clusters at a time uses a lot of memory. Also, using a thread pool (even an artificially limited thread pool) is closer to the actual usage of JobInvocation than direct executor service, which assigns work back to the calling thread.
R: @kennknowles

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

R: @angoenka

Can the jobs share a cluster concurrently?

Might want to confirm deflaking. Merging despite my question because if it helps that's great.

Can the jobs share a cluster concurrently?

For a normal cluster, yes. But I'm not sure if there's a way to do this with a "local" (embedded) cluster.


Reserved Properties are not working

In my application I am using the property ${http.port}
When I deployed the application, I override the property by setting 7777.
My application is now unreachable.
https://github.com/mulesoft/docs-hosting/blob/latest/cloudhub-2/modules/ROOT/pages/ch2-manage-props.adoc

Hello Sebastian,
I checked the info with the Support team, and they confirmed that http.port and https.port cannot be overridden in CloudHub or CloudHub 2. If you can override them, it means there is product bug.
Please feel free to submit a Support ticket to address this issue.
Thank you!


⚠ Turnos 24x7 has degraded performance

In 13b7db1, Turnos 24x7 (https://reservas.alternativasinteligentes.com/) experienced degraded performance:

HTTP code: 200
Response time: 1192 ms

Resolved: Turnos 24x7 performance has improved in 3296bd4.


feat: add TS 5 support

Closes #5871

the eslint peer dep was updated here, but still makes sense to bump our dev deps as well 👍


New docs website

Now [09/14/2024] netly.docs.kezero.com website is offline and not acessible, this reason that's why is going be hard deployment of new website version.
The new website version is working fine but Docusauros can't build it static because generated markdown conflict with docusauros (i don't know why). I tried deploy website on vercel, render.
New website

This website have included content of version 3.1.x api and manual, use drop down with 4.0.0 and select 3.1.0
Old website

Currently this website is working on render since of [09/18/2024], using Free version over Docker and Docs branch, Working at netly.docs.kezero.com

When will version 4.0 be ready

Neatly 4.0 is almost ready. The only thing left is to perform unit tests for HTTP, RUDP, and WebSocket. While I’ve already found and fixed some bugs during personal usage, it’s essential to cover all possible use cases and validate behavior with automated tests.
The delay isn’t due to a lack of time but rather a lack of motivation. I want to ensure the version is stable and reliable before the official release. So, Neatly 4.0 will be released as soon as all tests pass successfully.


URL double port fix

As detailed in #35731, if a specified domain for a route contains a port, and Laravel's server is also run under a non-standard port, Laravel's port will be added to that specified domain, resulting in an invalid URL.

I don't think the domain field was ever meant to have a port in it? The port is not part of a "hostname", which is what the domain is meant to be. Is there not a separate way to specify the port?

That the port is not part of the hostname is a valid point that I address in the accompanying issue that I created; you are completely right. Using the domain attribute in this sense is abusing its purpose.
However, there's no facility to accommodate this difference in ports otherwise, and I cannot think of any reason (aside from naming) why this field shouldn't be used in this way.

Hm, not sure I want to merge this on a patch release. I'm still a little unclear on why you need this. Can you just assign your local sites different domains in your /etc/hosts file?

Sure, I could adjust my hosts file, but that wouldn't change that my applications are running under different ports. In the end the hosts file is just a bunch of aliases for hostnames to IP adresses, but not for hostnames to an IP address + port.
It might just be an edge case, but I think this should be part of Laravel. It's backward compatible in that it would previously generate wrong URLs anyway, but patches this issue in a simple way.
Alternatively, I see two ways: either don't allow this specification of a port and throw an exception or add a different facility in the UrlGenerator and RouteRegistrar.


Feat/error page routing

This PR creates a page for NOT FOUND error code.
Issue
#170
Mockups

 1920px

 1440px

 Tablet

 Mobile

@AnjaMis @lolottetheclash
Changes have been made in governance component, could you please re-open this PR and merge it if everything is OK ? 🙏


ci(android_intent_plus): Remove Java installation step

Description
According to Github documentation macos-13 machine should already have Java 17 installed: https://github.com/actions/runner-images/blob/main/images/macos/macos-13-Readme.md#java
Thus, I am curious if we can drop installation step in order to save a few seconds during workflow runs. In case this PR doesn't fail I will open similar ones for other plugins workflows.
Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (please indicate that with a ! in the title as explained in Conventional Commits).
[x] No, this is not a breaking change.

Checked one of previous runs and it looks like removed step was doing nothing already, so we are not saving time here, but just dropping some redundant code.


Blocked Plug-in

Since I upgraded on Mavericks, Google Music won't play any music.
I have a "Blocked Plug-in" icon on both the title of the song and at the left of the buttons to control the music.

I've updated and reinstalled AFP, and also reinstalled Radian Player, but I can't get it to work :(

@eliasgomezsainz It’s currently broken, not sure why. See the discussion in #668 – though it doesn’t contain a solution.

I also have this issue now.

me too


17 - Allow importing modules that are not from language core

Should resolve https://github.com/abingham/jupyter-elm-kernel/issues/17

Thanks for putting this together. I had been thinking a bit about the best way to let users specify dependencies, and this PR is probably the best way, at least for now.

Sorry for letting this sit for so long! I totally forgot about it. I'll try to be more responsive in the future.


update colorschemes

new colorschemes

wildcharm: dual background contrast colorscheme, vibrant and playful, at least one popular AI thinks it is.
retrobox: port/variation of gruvbox
sorbet: inspired by cold colorschemes like nord/iceberg
zaibatsu: liberally inspired by the so-called "neo-tokyo", "neon-noir", "cyberpunk", "vaporware", etc. a e s t h e t i c, as well as popular colorschemes like dracula, tokyonight, or onedark.

updated colorschemes

lunaperche
quiet
habamax

Thx to @romainl, @neutaaaaan

Hmm, speaking of CODEOWNERS, GitHub doesn't seem to like how it is used:

@brammool @chrisbra, the doc clearly says that it should contain the names of people with write permissions, which is clearly not the case for most people in that file.
Are they notified anyway, even if they are outsiders?

yeah I have noticed in the past and wondered if it really helps. You could test it out by creating a dummy PR against e.g. runtime/colors/blue.vim	and see if you get notified.
But even if this doesn't work, it at least is (yet another) way to know whom to notify

About the colorschemes: Any comments on including these?  I like to keep the number of distributed colorschemes small, so that users are not overwhelmed.  They should be quite different.
About CODEOWNERS: I don't know why github requires write access.  Is that configurable somewhere?

I've noticed an inconsistency between a few colorschemes. Some colorschemes contain highlight groups that are defined by 3rd party plugins (e.g. fugitive, ALE, etc.), or syntax files (e.g. vimOper, elixirOperator, javaScript*, etc.), while others don't. Is that by accident? IMO, all distributed colorschemes should provide the same highlight groups.
Should filetype-specific highlight groups like vimOper, elixirOperator etc. even be defined in a colorscheme? If this becomes a common theme, the colorschemes will grow very quickly once users start adding filetype-specific highlight groups to each colorscheme (there are over 500 different syntax files, each one defining several syntax groups). I can understand the reasoning behind it but I feel like they will quickly become unmaintainable.
I thought the purpose of a colorscheme file was to define only general highlight groups (like :h highlight-default and :h group-names).

@bfrg Yes, the fact that some have those specific groups and some don't is definitely an accident. I agree, non-default highlight groups have nothing to do here.
@habamax can we talk about lunaperche and habamax?

Sure, we can, @romainl. Let's remove it, though it wouldn't be the colorschemes I, as an author, aimed to create anymore.

They should be quite different

@brammool while the work done last year indirectly did a lot to improve variety between the older colorschemes, most of them use rather aggressive or dull colors, with little thought given to the overall balance and feel. This cannot be fixed without drastically altering them, much beyond what we already had to do to ensure they'd behave properly in different environments.
This is the main reason why retrobox, sorbet, zaibatsu and wildcharm (as well as quiet, habamax and lunaperche, that already ship as part of the runtime) exist. Those newer colorschemes are based on styles popular within the larger vim colorscheme ecosystem in terms of palette and general feel, and aim to round out the current set of colorschemes.
And as they are specified rather exhaustively, it's viable for an end user to pick one and, through the use of autocommands, use it as a "platform" for their own modifications, without having to understand too much about colorschemes, or being forced to shlep many files around.

I've noticed an inconsistency between a few colorschemes. Some
colorschemes contain highlight groups that are defined by 3rd party
plugins (e.g. fugitive, ALE, etc.), or syntax files (e.g. vimOper,
elixirOperator, javaScript*, etc.), while others don't. Is that by
accident? IMO, all distributed colorschemes should provide the same
highlight groups.
Should filetype-specific highlight groups like vimOper,
elixirOperator etc. even be defined in a colorscheme? If this
becomes a common theme, the colorschemes will grow very quickly once
users start adding filetype-specific highlight groups to each
colorscheme (there are over 500 different syntax files, each one
defining several syntax groups). I can understand the reasoning behind
it but I feel like they will quickly become unmaintainable.
I thought the purpose of a colorscheme file was to define only general
highlight groups (like :h highlight-default and :h group-names).

Hopefully only the default highlight groups need to be defined.  If for
some syntax file this doesn't work that is an indication that there is
something wrong.  This can be how the default groups are used in a
syntax file, or perhaps the set of default groups is not quite right.  I
see that "vimOper" links to "Operator" and "Operator" is not used for
anything else.  So why not define highlighting for "Operator"?
--
Facepalm statement #4: "3000 year old graves?  That's not possible, it's only
2014!"
/// Bram Moolenaar -- @.*** -- http://www.Moolenaar.net   \
///                                                                      \
\\        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

FWIW, Operator is linked to Statement in syntax/syncolor.vim and linked to in 480+ places under syntax/.
In my opinion, everything under :help highlight-groups is fair game, as well as any other group that is used by Vim out of the box, without necessarily being documented in that section. Like… the following list, taken from syntax/syncolor.vim:
SynLink String		Constant
SynLink Character	Constant
SynLink Number		Constant
SynLink Boolean		Constant
SynLink Float		Number
SynLink Function	Identifier
SynLink Conditional	Statement
SynLink Repeat		Statement
SynLink Label		Statement
SynLink Operator	Statement
SynLink Keyword		Statement
SynLink Exception	Statement
SynLink Include		PreProc
SynLink Define		PreProc
SynLink Macro		PreProc
SynLink PreCondit	PreProc
SynLink StorageClass	Type
SynLink Structure	Type
SynLink Typedef		Type
SynLink Tag		Special
SynLink SpecialChar	Special
SynLink Delimiter	Special
SynLink SpecialComment	Special
SynLink Debug		Special

or debugPC and debugBreakpoint, which are underdocumented.

Sure, we can, @romainl. Let's remove it, though it wouldn't be the colorschemes I, as an author, aimed to create anymore.

That's precisely why I won't submit Apprentice or Malotru for inclusion.

I've mentionned that during a private conversation with @habamax already, but I think getting rid of all the custom links is a bad idea.
Anything that ships with the runtime is fair game in my opinion, and if some elements end up being highlighted in a way that feels semantically misleading, and the issue isn't clearly with the syntax file itself, then this ought to be fixed in the colorscheme.
There will always be such instances of awkward highlighting because of design decisions that work perfectly fine in the context the author was initially thinking about, but don't pan out when editing specific filetypes.
Shell scripts will never not look like a clown got food poisoning. DiffRemoved inherits its color from the Special group for some reason, but there's no guarantee of Special being red.
Those discrepancies and issues just pile up as more work goes into refining a colorscheme. It's unavoidable.
Some of the older colorschemes rewire minor groups pretty liberally. I can only assume this is because the original authors had similar issues within the small subset of filetypes they worked with. This shouldn't have been allowed to happen.
Case by case overrides is the only way to address this.

DiffRemoved inherits its color from the Special group for some reason, but there's no guarantee of Special being red.

I think you're talking about diffRemoved which is defined in syntax/diff.vim. And I agree, this syntax group is an exception. Most users will expect a red foreground. It is different from DiffRemoved which is used in diff-mode where most users will expect it to have a red background. I'm sure there are more exceptions where neither of the highlight groups mentioned in :h group-names fit well. Maybe that list should be extended?
Currently, there are 5 different group names for the Preprocessor. Most colorschemes I've seen use the same color for all 5 groups. Likewise, there are different group names for for/while loops, conditionals, labels and exceptions. The colorschemes I've seen will all highlight them as Statement. But then, on the other hand, there is only Underline. Where is Bold and Italic? Similarly, there's one highlight group called Error, but Warning and Info are missing. Maybe a few more group names could be added so that syntax files can link to them? OTOH, html and many doc file like markdown, rst, asciidoc, latex etc. use different headings. html uses h1 to h6, the other formats use something similar. But Vim provides only one highlight group that is useful and that is Title. A few more default names could be added. Then other syntax files could link against them and colorschemes would adopt these names.
Most other highlight groups that I can see, for example, in the colorscheme habamax, I would expect them to be defined in after/syntax/<filetype>.vim. For example:
hi! link javaScriptFunction Statement
hi! link javaScriptIdentifier Statement

I use the exact same javascript links. But since I want this behavior for every colorscheme, I have put these links in after/syntax/javascript.vim.
I really wonder how other editors solve all this.

That's precisely why I won't submit Apprentice or Malotru for inclusion.

@romainl Is Apprentice broken when you remove certain links? Maybe after/colors/<colorscheme>.vim should be automatically sourced once a specific colorscheme is loaded, similar to after/ftplugin/<filetype>.vim? I know this is already possible with autocommand and the ColorScheme event but working with files is easier and it is already done for filetype and syntax files.

Some housekeeping would be nice, but more groups would not help this particular situation, as overrides would inevitably happen regardless. Colorschemes are as much about aesthetics as they are about shaping up your interpretation of the underlying semantics.
Similarly, I don't see how throwing more files into the runtime to handle the exceptions could help. That's just shuffling the solution around for the sake of correctness, whilst making the whole thing harder to grasp for an end user.

I'll include this now, as there are no relevant objections.  There are always remarks about what looks good or bad to some users.  We will keep improving this over time.


improve tag image

Improve tag image so that it can refresh image in cluster.
Signed-off-by: Xian Chaobo<EMAIL_ADDRESS>

ping @aluzzardi @vieux @abronan

I don't see the improvement here.

@vieux
I think Engine.RefreshImages() should not be a public function. It should not be called in docker api. If all the three API (docker tag\docker commit\docker build)  do as the following way, it will be  become a private function.
docker api ---> cluster api ---> engine api  ---> dockerclient api

I don't known if it's meaningful, waiting for your reply. Tks
/cc @aluzzardi @abronan

@jimmyxian I agree, it's an improvment regarding the quality of the code, not the feature.
LGTM

ping @vieux
Modified by the comment. check again, thks

I think I'm the one who suggested this, but now I'm having second thoughts.
I'm worried that the more we don't rely on proxy and use our own implementation, the more things will break since we need to re-implement them every time.
I realized this with ps: We don't proxy ps (we can't), and realized --filter doesn't work and since docker 1.6 they added --filter label=k=v which we needed to add.
I don't know if this is the path we want to take.
@vieux ?

@aluzzardi I have the same concerns.

Perhaps we should address these in 0.4 with #748

@aluzzardi Agree, using proxy can reduce a lot of work in our swarm. If we implement in swarm, Docker API changes, we also have to change it in swarm.
@aluzzardi @vieux  Shall I close this one?

I think so yeah


Make "1.0.0" Default Branch

In preparation for the 1.0.0 release, and to assist with PRs being automatically targetted to the 1.0.0 branch (especially since PRs to master aren't accepted), I propose that it would make a lot of sense to make 1.0.0 the default branch until it has been merged to master.  Thoughts?

I was thinking about this earlier today and agree. I was initially concerned about any confusion that might arise, but if people are coming to GitHub, they might as well see the latest version of the library.
Setting 1.0.0 as the default branch and updating the version number to 1.0.0.dev


[Non-breaking] Support allowlist where whitelist presently used

This is a minimal change to allow the use of allowlist where whitelist is presently used.
It does not deprecate the existing whitelist options, which is being discussed in #150, but it gives users the immediate option to remove the use of whitelist from their own configuration.
The changes are implemented using a very simple alias in the yargs argument parser configuration, which is low risk.

Hi @jamesreggio, thanks for your pull request!
I notice that the build is failing. I think it has to do with yargs and how it handles aliases instead of alias, though I haven't looked too closely at that yet.
I am interested in pushing allowlist, possibly today (just got back from vacation 😄). However, I am concerned that if we do this as a pure alias for whitelist then we do have to make a (sorta) breaking change if we introduce https://github.com/IBM/audit-ci/issues/151, which I currently really like.
I think the path forward is to just have one command: allowlist, which handles the role of whitelist, path-whitelist, and advisories(?) combined, since they are mutually exclusive formatting it should be safe to do!

Hi again,
Thanks again for pushing. I think I want to go another route with the implementation of allowlist than what is currently here. I pushed #154, consider reviewing if you'd like! It is a non-breaking change, adds "allowlist" and supports the other keywords ["whitelist", "advisories", and "path-whitelist"].
Thanks!

#154 has been released as v3.1.0


Install cloudflared via Cloudflare Package Repository

⚠⚠⚠ Since we do not accept all types of pull requests and do not want to waste your time. Please be sure that you have read pull request rules:
https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md#can-i-create-a-pull-request-for-uptime-kuma
Tick the checkbox if you understand [x]:

[x] I have read and understand the pull request rules.

Description
This changes the base image to intsall cloudflared via the Cloudflare Package Repository.  This apt repo provides the package for amd64, arm64 and armv7, removing the need for a seperate download script or adding a new arch as a workaround.
The --insecure option of curl is required as buster's ca-certificates are too old to validate the server.  It can be removed if bullseye or bookworm are upgraded to instead.
Type of change
Please delete any options that are not relevant.

Other

Checklist

[x] My code follows the style guidelines of this project
[ ] I ran ESLint and other linters for modified files
[x] I have performed a self-review of my own code and tested it
[ ] I have commented my code, particularly in hard-to-understand areas
(including JSDoc for methods)
[x] My changes generate no new warnings
[ ] My code needed automated testing. I have added them (this is optional task)

Screenshots (if any)
Please do not use any external image service. Instead, just paste in or drag and drop the image here, and it will be uploaded automatically.

Seems like a good opportunity to upgrade to Bullseye. Raspberry Pi OS has been on bullseye for more than a year now. The underlying issue with uv_gettimeofday has documented solutions so it should not be a consideration anymore.

It would be great to do that, though I'd prefer it in a separate PR (or go in before this so I can remove the --insecure).
I think alpine should update at the same time.

Seems like a good opportunity to upgrade to Bullseye. Raspberry Pi OS has been on bullseye for more than a year now. The underlying issue with uv_gettimeofday has documented solutions so it should not be a consideration anymore.

Yes, it will be updated in 2.0.
See https://github.com/louislam/uptime-kuma/pull/2720

Update to the latest version of Debian (as Raspberry users can't use it directly, will try to provide a guide to update libseccomp2: https://github.com/sdr-enthusiasts/Buster-Docker-Fixes)


Missing spaces in function app create warning message

Add spaces
https://github.com/Azure/azure-cli/blob/ea5496bf7ee188da599dd3b009fc63d24967154a/src/azure-cli/azure/cli/command_modules/appservice/custom.py#L2337-L2339
Current output looks like
that uses a consumption plan has been successfullycreated but is not active until content is published usingAzure Portal

@balag0 This is fixed


probably corrected a small typo in the log output

 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.


FEATURE REQUEST: Set and hide "not interested" in search

Have a button during search and new & updated for "Not Interested". Then, those programs will always be filtered out during search and new & updated so they don't show up again. Also need the ability to remove an item from that list to reverse the setting.

This will be made available in the next release:

This is available as of v2<IP_ADDRESS>0


Travis CI: sudo is deprecated and Xenial is default distro

The sudo: tag is fully deprecated on Travis CI and Xenial is the default Linux distro.

Reference issue

What does this implement/fix?

Simplify by removing out-of-date configuration.
Additional information

Looks ok to me, merging. Thank you @cclauss


Warning: Invalid hook call. when starting nextjs project

What version of Turborepo are you using?
1.4.2
What package manager are you using / does the bug impact?
Yarn v1
What operating system are you using?
Windows
Describe the Bug
Warning: Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:

You might have mismatching versions of React and the renderer (such as React DOM)
You might be breaking the Rules of Hooks
You might have more than one copy of React in the same app

Expected Behavior
I have a different react package installed in other apps dir.
Nextjs with React 18.2.0 and other apps with React 18.0.0
To Reproduce
{
  "name": "app-name",
  "version": "0.0.0",
  "private": true,
  "workspaces": {
    "packages": [
      "packages/*",
      "apps/*"
    ],
    "nohoist": [
      "**/react",
      "**/react/**",
      "**/react-dom",
      "**/react-dom/**",
      "**/react-native",
      "**/react-native/**",
      "**/@react-native-*",
      "**/@react-native-*/**",
      "**/react-native-*",
      "**/react-native-*/**",
      "**/*react-navigation/native*",
      "**/*react-navigation/native*/**",
      "**/expo",
      "**/expo/**",
      "**/@expo",
      "**/@expo/**",
      "**/expo-*",
      "**/expo-*/**",
      "**/metro-*",
      "**/metro-*/**"
    ]
  },
  "scripts": {
    "build": "turbo run build",
    "dev": "turbo run dev --no-cache --parallel",
    "lint": "turbo run lint",
    "format": "prettier -w .",
    "commit": "cz"
  },
  "devDependencies": {
    "commitizen": "^4.2.5",
    "cz-conventional-changelog": "^3.3.0",
    "eslint": "^8.21.0",
    "eslint-config-cktidy": "*",
    "husky": "^8.0.1",
    "lint-staged": "^13.0.3",
    "prettier": "^2.7.1",
    "turbo": "^1.4.2"
  },
  "engines": {
    "npm": ">=8.0.0",
    "node": ">=16.0.0"
  },
  "lint-staged": {
    "*.{js,jsx,ts,tsx}": [
      "eslint --fix"
    ],
    "*.{html,scss,css,vue}": [
      "prettier -w"
    ]
  },
  "config": {
    "commitizen": {
      "path": "cz-conventional-changelog"
    }
  }
}

Normally install with yarn and using yarn workspace

Hey @cktsun1031 could you provide a reproduction repo? This doesn't sound like an issue with turbo - but I'd be happy to take a look if you could isolate the problem and provide a sample reproduction.

I can solve the issue by unifying the react version of every projects inside apps.
Actually this is not efficient for managing monorepos.
I dont know how to solve it while i am using yarn workspaces

You should be able to use different version of react in your apps as long as they're each being deployed individually and don't interdepend on each other. However, this issue often arrises when using different copies of react between an app and a package (or, more generalized, when something depends on something else and they use two different copies of react).
There are many ways to fix this - don't bundle a copy of react with your packages, use peer dependencies, etc.
Since this isn't a problem with Turborepo itself I'm going to close this one.


MacOS Target not working on Windows

WSL command seems to only work in specific cases
There probably is an issue with the tmpPath being loaded

Added enhancement #4


Yarn did not allocate pod by GpuType

Hi, guys.
I saw the code that YARN can allocate pod by GpuType. But it didn't happen, when I set gpu type in cluster-configuration.yaml and initialized the gpu type in jobconfig.
here is part of my cluster-configuration.yaml
{
DEBUGGPU:
mem: 192
gpu:
type: DEBUGGPU
count: 8
cpu:
vcore: 24
os: ubuntu16.04
- hostname: debug
hostip: <IP_ADDRESS>
machine-type: DEBUGGPU
#sshport: PORT (Optional)
#username: username (Optional)
#password: password (Optional)
k8s-role: worker
pai-worker: "true"
}
and my jobconfig:
{
"jobName": "jobName_4",
"image": "<IP_ADDRESS>:5000/pai-images/pai.run.mxnet:v1.1",
"gpuType": "DEBUGGPU",
"killAllOnCompletedTaskNumber": 1,
"retryCount": 0,
"taskRoles": [
{
"name": "demo4pai",
"taskNumber": 1,
"cpuNumber": 2,
"memoryMB": 8196,
"gpuNumber": 0,
"command": "sleep 1800"
}
],
}

The GPU type scheduling is partially supported in PAI.  If there has free specific-type GPU available, PAI will schedule the job to the specific type GPU,  If no free specific-type GPU available, this will request will be ignored.
It will very be helpful if you can provide the job log for us to analysis your issue.

Taskrole level platformSpecificParameters will inhert framework level platformSpecificParameters if taskrole level platformSpecificParameters is null. So the taskNodeGpuType is right configured.
However, I found that you did not request any gpu, i.e. "gpuNumber": 0, so, in this case, the gpu type will just be ignored (because you said you do not need any gpu). Thus, the DEBUGGPU node may or may not be allocated for your job.
You can try to increase the gpuNumber to 1.
It will very be helpful if you can provide the job log for us to analysis your issue.

Hi, that log just for one job I submitted, actually no matter how much gpunumber is, the job will not be in the DEBUGGPU type machine.

Hi, please get the job by click:

Open you job view: (url like: http://{******88}/view.html?jobName={your job name}
click "Go to application Tracking Page" to open the application view (url like: http://:8088/cluster/app/application__***
click the log of the application log, you will see AllDebug.log, AllError.log ..
Then you can get the allDebug log.

https://github.com/Microsoft/pai/pull/1562


OS/400 avoids using NOFOLLOW_LINKS

What does this PR do?
Skips using NOFOLLOW_LINKS file open option when running on OS/400.
Checklist

[x] This is an enhancement of existing features, or a new feature in existing plugins

[x] I have updated CHANGELOG.asciidoc
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] Added an API method or config option? Document in which version this will be introduced
[ ] I have made corresponding changes to the documentation

[ ] This is a bugfix

[ ] I have updated CHANGELOG.asciidoc
[ ] I have added tests that would fail without this fix

[ ] This is a new plugin

[ ] I have updated CHANGELOG.asciidoc
[ ] My code follows the style guidelines of this project
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] I have updated supported-technologies.asciidoc
[ ] Added an API method or config option? Document in which version this will be introduced
[ ] Added an instrumentation plugin? Describe how you made sure that old, non-supported versions are not instrumented by accident.

[ ] This is something else

[ ] I have updated CHANGELOG.asciidoc

looks good. Add a changelog entry and we just need user confirmation it works

User has just confirmed it works, so if there are no further actions needed here I think I'll merge it later today.


tridactyl-native: 1.16.3 -> 1.17.0

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/tridactyl-native/versions.
meta.description for tridactyl-native is: '"Tridactyl native messaging host application"'.
meta.homepage for tridactyl-native is: '"https://github.com/tridactyl/tridactyl"
Compare changes on GitHub

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 1.17.0 with grep in /nix/store/qzc52i807rfncsdi05y17paaypqvcl2n-tridactyl-native-1.17.0

directory tree listing: https://gist.github.com/29180407563adc893eae4a1bcb13c339

du listing: https://gist.github.com/a671671ff98b9d39247363d5eab27d1a

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

4 total rebuild path(s)
1 package rebuild(s)
1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
tridactyl-native

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/qzc52i807rfncsdi05y17paaypqvcl2n-tridactyl-native-1.17.0 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A tridactyl-native https://github.com/r-ryantm/nixpkgs/archive/ecf15298872774e29e6890112e061d36ceed5f73.tar.gz

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

cc @timokau for testing.

The output is correct, since this is not actually the full tridactyl addon but just the native messenger part.


"Django Image Cropping" and "Django Autocomplete Light" are conflicting in the admin interface.

"Django Image Cropping" (IC) and "Django Autocomplete Light" are conflicting in the admin interface.
This is a jquery problem.
This is what I think the issue is

Both use Form Assets (the Media class).

DAL here
IC here
Now keep in mind, that django is keeping the relative order but intersect the assets. See here. I am not sure by what algorithm the order is defined but here is one of the problems. This also means, that the order in which IC and DAL are included in the django settings is not the solution.

IC and DAL both use jquery and both "patching" jquery with some plugin.

IC does this in jquery.Jcrop.js.
DAL does this in here.

Here is the problem
The files are loaded in this order:
image_cropping/js/jquery.Jcrop.min.js
autocomplete_light/jquery.init.js
image_cropping/image_cropping.js
autocomplete_light/jquery.post-setup.js

Why is this a problem?
This is what happens:

image_cropping/js/jquery.Jcrop.min.js is patching jquery
autocomplete_light/jquery.init.js is replacing temporary the jQuery-variable. See here.
image_cropping/image_cropping.js is trying to call $(...).Jcrop which results in an error.
Finally autocomplete_light/jquery.post-setup.js is switching jQuery back.

Now what can we do?
Maybe we can streamline loading js-files on python-side.
Or we can streamline the execution of js files and do not use and immediately invoked function expression, but execute the code once it is loaded.
I am not sure, but I think replacing the jQuery-variable is no good idea. If we can find a different solution here, I think it would be the most easy fix.

I have also opened an issue over at image cropping some days ago, but I think the issue is on this side.

I'm all for removal jquery.init.js if anybody wants to make a pull request about it.

What about offering an alternative autocomplete implementation in a webcomponent that autoloads and does not depend on jquery ?
https://oss.yourlabs.me/autocomplete-light/
Implemented in #1170
Can we then close this issue ?