SDK not respecting config file

I am using the describe instances example from the docs with the added log line to get the log file below. This gives incorrect information based off of my ~/.aws/config file. I set up my config file and credentials with the aws-cli tool and set my region to us-east-2. When I run the example describe instance I get my instances from us-east-1. I understand this is the default location but I am specifying where I would like my search to go. The correct functionality is present in the Python SDK and is also described in the Java SDK docs. Is this intentional and something that should be planned for?
My config file is:
[default]
region=us-east-2
output=json

My Python example showing correct region:
import boto3

ec2 = boto3.client('ec2')
response = ec2.describe_instances()
print(response)

What platform/OS are you using?
Ubuntu 18.04
Which version of the SDK?
AWS SDK for C++ with Version:1.7.111
What compiler are you using? what version?
gcc (Ubuntu 7.3.0-27ubuntu1~18.04) 7.3.0
clang version 6.0.0-1ubuntu2 (tags/RELEASE_600/final)
What are your CMake arguments?
cmake -D CMAKE_BUILD_TYPE=Debug -DBUILD_SHARED_LIBS=OFF -DBUILD_ONLY='logs;core;iam;access-management;identity-management;cognito-identity;cognito-idp;s3;kinesis;sts;ec2' -DFORCE_SHARED_CRT=ON -DSIMPLE_INSTALL=ON -DMINIMIZE_SIZE=OFF -DENABLE_TESTING=OFF ./../aws-sdk-cpp
Can you provide a TRACE level log? (sanitize any sensitive information)
[INFO] 2019-06-07 14:48:29.906 Aws_Init_Cleanup [140465506043712] Initiate AWS SDK for C++ with Version:1.7.111
[INFO] 2019-06-07 14:48:29.907 CurlHttpClient [140465506043712] Initializing Curl library
[TRACE] 2019-06-07 14:48:29.913 FileSystemUtils [140465506043712] Checking HOME for the home directory.
[DEBUG] 2019-06-07 14:48:29.913 FileSystemUtils [140465506043712] Environment value for variable HOME is /home/steven
[DEBUG] 2019-06-07 14:48:29.913 FileSystemUtils [140465506043712] Home directory is missing the final / appending one to normalize
[DEBUG] 2019-06-07 14:48:29.913 FileSystemUtils [140465506043712] Final Home Directory is /home/steven/
[INFO] 2019-06-07 14:48:29.913 Aws::Config::AWSConfigFileProfileConfigLoader [140465506043712] Initializing config loader against fileName /home/steven/.aws/config and using profilePrefix = 1
[DEBUG] 2019-06-07 14:48:29.913 Aws::Config::ConfigFileProfileFSM [140465506043712] found profile default
[DEBUG] 2019-06-07 14:48:29.913 Aws::Config::ConfigFileProfileFSM [140465506043712] found region us-east-2
[INFO] 2019-06-07 14:48:29.914 Aws::Config::AWSProfileConfigLoader [140465506043712] Successfully reloaded configuration.
[TRACE] 2019-06-07 14:48:29.914 Aws::Config::AWSProfileConfigLoader [140465506043712] reloaded config at 2019-06-07T14:48:29Z
[TRACE] 2019-06-07 14:48:29.914 FileSystemUtils [140465506043712] Checking HOME for the home directory.
[DEBUG] 2019-06-07 14:48:29.914 FileSystemUtils [140465506043712] Environment value for variable HOME is /home/steven
[DEBUG] 2019-06-07 14:48:29.914 FileSystemUtils [140465506043712] Home directory is missing the final / appending one to normalize
[DEBUG] 2019-06-07 14:48:29.914 FileSystemUtils [140465506043712] Final Home Directory is /home/steven/
[INFO] 2019-06-07 14:48:29.914 Aws::Config::AWSConfigFileProfileConfigLoader [140465506043712] Initializing config loader against fileName /home/steven/.aws/credentials and using profilePrefix = 0
[TRACE] 2019-06-07 14:48:29.914 FileSystemUtils [140465506043712] Checking HOME for the home directory.
[DEBUG] 2019-06-07 14:48:29.914 FileSystemUtils [140465506043712] Environment value for variable HOME is /home/steven
[DEBUG] 2019-06-07 14:48:29.914 FileSystemUtils [140465506043712] Home directory is missing the final / appending one to normalize
[DEBUG] 2019-06-07 14:48:29.914 FileSystemUtils [140465506043712] Final Home Directory is /home/steven/
[TRACE] 2019-06-07 14:48:29.914 FileSystemUtils [140465506043712] Checking HOME for the home directory.
[DEBUG] 2019-06-07 14:48:29.914 FileSystemUtils [140465506043712] Environment value for variable HOME is /home/steven
[DEBUG] 2019-06-07 14:48:29.914 FileSystemUtils [140465506043712] Home directory is missing the final / appending one to normalize
[DEBUG] 2019-06-07 14:48:29.914 FileSystemUtils [140465506043712] Final Home Directory is /home/steven/
[INFO] 2019-06-07 14:48:29.914 ProfileConfigFileAWSCredentialsProvider [140465506043712] Setting provider to read credentials from /home/steven/.aws/credentials for credentials file and /home/steven/.aws/config for the config file , for use with profile default
[DEBUG] 2019-06-07 14:48:29.914 DefaultAWSCredentialsProviderChain [140465506043712] The environment variable value AWS_CONTAINER_CREDENTIALS_RELATIVE_URI is
[DEBUG] 2019-06-07 14:48:29.914 DefaultAWSCredentialsProviderChain [140465506043712] The environment variable value AWS_CONTAINER_CREDENTIALS_FULL_URI is
[DEBUG] 2019-06-07 14:48:29.914 DefaultAWSCredentialsProviderChain [140465506043712] The environment variable value AWS_EC2_METADATA_DISABLED is
[INFO] 2019-06-07 14:48:29.914 EC2MetadataClient [140465506043712] Creating AWSHttpResourceClient with max connections2 and scheme http
[INFO] 2019-06-07 14:48:29.914 CurlHandleContainer [140465506043712] Initializing CurlHandleContainer with size 2
[INFO] 2019-06-07 14:48:29.914 InstanceProfileCredentialsProvider [140465506043712] Creating Instance with default EC2MetadataClient and refresh rate 300000
[INFO] 2019-06-07 14:48:29.914 DefaultAWSCredentialsProviderChain [140465506043712] Added EC2 metadata service credentials provider to the provider chain.
[DEBUG] 2019-06-07 14:48:29.914 Aws::Config::ConfigFileProfileFSM [140465506043712] found profile default
[DEBUG] 2019-06-07 14:48:29.914 Aws::Config::ConfigFileProfileFSM [140465506043712] found access key XXX
[INFO] 2019-06-07 14:48:29.914 Aws::Config::AWSProfileConfigLoader [140465506043712] Successfully reloaded configuration.
[TRACE] 2019-06-07 14:48:29.914 Aws::Config::AWSProfileConfigLoader [140465506043712] reloaded config at 2019-06-07T14:48:29Z
[INFO] 2019-06-07 14:48:29.914 CurlHandleContainer [140465506043712] Initializing CurlHandleContainer with size 25
[TRACE] 2019-06-07 14:48:29.915 AWSClient [140465506043712] Found body, but content-length has not been set, attempting to compute content-length
[DEBUG] 2019-06-07 14:48:29.915 AWSAuthV4Signer [140465506043712] Calculated sha256 6171eb09865e32b0602af0f7957e26573a51f53caaedff02ff88883cb0275885 for payload.
[DEBUG] 2019-06-07 14:48:29.915 AWSAuthV4Signer [140465506043712] Canonical Header String: content-length:43
content-type:application/x-www-form-urlencoded
host:ec2.us-east-1.amazonaws.com
x-amz-api-version:2016-11-15
x-amz-content-sha256:6171eb09865e32b0602af0f7957e26573a51f53caaedff02ff88883cb0275885
x-amz-date:20190607T144829Z

[DEBUG] 2019-06-07 14:48:29.915 AWSAuthV4Signer [140465506043712] Signed Headers value:content-length;content-type;host;x-amz-api-version;x-amz-content-sha256;x-amz-date
[DEBUG] 2019-06-07 14:48:29.915 AWSAuthV4Signer [140465506043712] Canonical Request String: POST
/

content-length:43
content-type:application/x-www-form-urlencoded
host:ec2.us-east-1.amazonaws.com
x-amz-api-version:2016-11-15
x-amz-content-sha256:6171eb09865e32b0602af0f7957e26573a51f53caaedff02ff88883cb0275885
x-amz-date:20190607T144829Z

content-length;content-type;host;x-amz-api-version;x-amz-content-sha256;x-amz-date
6171eb09865e32b0602af0f7957e26573a51f53caaedff02ff88883cb0275885
[DEBUG] 2019-06-07 14:48:29.915 AWSAuthV4Signer [140465506043712] Final String to sign: AWS4-HMAC-SHA256
20190607T144829Z
20190607/us-east-1/ec2/aws4_request
72cd12c13674b5794e2c9440059c181192779d7b542ee62d7d715f4225a1c965
[DEBUG] 2019-06-07 14:48:29.915 AWSAuthV4Signer [140465506043712] Final computed signing hash: fb3954ff7feb4b62a6c9ea553ded4014b46dcf1c8cb8e3dd44df8948563ef38c
[DEBUG] 2019-06-07 14:48:29.915 AWSAuthV4Signer [140465506043712] Signing request with: AWS4-HMAC-SHA256 Credential=AKIAIZDKG54W6YX3B3XQ/20190607/us-east-1/ec2/aws4_request, SignedHeaders=content-length;content-type;host;x-amz-api-version;x-amz-content-sha256;x-amz-date, Signature=fb3954ff7feb4b62a6c9ea553ded4014b46dcf1c8cb8e3dd44df8948563ef38c
[DEBUG] 2019-06-07 14:48:29.915 AWSClient [140465506043712] Request Successfully signed
[TRACE] 2019-06-07 14:48:29.915 CurlHttpClient [140465506043712] Making request to https://ec2.us-east-1.amazonaws.com/
[TRACE] 2019-06-07 14:48:29.915 CurlHttpClient [140465506043712] Including headers:
[TRACE] 2019-06-07 14:48:29.915 CurlHttpClient [140465506043712] authorization: AWS4-HMAC-SHA256 Credential=AKIAIZDKG54W6YX3B3XQ/20190607/us-east-1/ec2/aws4_request, SignedHeaders=content-length;content-type;host;x-amz-api-version;x-amz-content-sha256;x-amz-date, Signature=fb3954ff7feb4b62a6c9ea553ded4014b46dcf1c8cb8e3dd44df8948563ef38c
[TRACE] 2019-06-07 14:48:29.915 CurlHttpClient [140465506043712] content-length: 43
[TRACE] 2019-06-07 14:48:29.915 CurlHttpClient [140465506043712] content-type: application/x-www-form-urlencoded
[TRACE] 2019-06-07 14:48:29.915 CurlHttpClient [140465506043712] host: ec2.us-east-1.amazonaws.com
[TRACE] 2019-06-07 14:48:29.915 CurlHttpClient [140465506043712] user-agent: aws-sdk-cpp/1.7.111 Linux/4.13.0-32-generic x86_64 GCC/7.3.0
[TRACE] 2019-06-07 14:48:29.915 CurlHttpClient [140465506043712] x-amz-api-version: 2016-11-15
[TRACE] 2019-06-07 14:48:29.915 CurlHttpClient [140465506043712] x-amz-content-sha256: 6171eb09865e32b0602af0f7957e26573a51f53caaedff02ff88883cb0275885
[TRACE] 2019-06-07 14:48:29.915 CurlHttpClient [140465506043712] x-amz-date: 20190607T144829Z
[DEBUG] 2019-06-07 14:48:29.915 CurlHandleContainer [140465506043712] Attempting to acquire curl connection.
[DEBUG] 2019-06-07 14:48:29.915 CurlHandleContainer [140465506043712] No current connections available in pool. Attempting to create new connections.
[DEBUG] 2019-06-07 14:48:29.915 CurlHandleContainer [140465506043712] attempting to grow pool size by 2
[INFO] 2019-06-07 14:48:29.915 CurlHandleContainer [140465506043712] Pool grown by 2
[INFO] 2019-06-07 14:48:29.915 CurlHandleContainer [140465506043712] Connection has been released. Continuing.
[DEBUG] 2019-06-07 14:48:29.915 CurlHandleContainer [140465506043712] Returning connection handle 0x55d0e75299e0
[DEBUG] 2019-06-07 14:48:29.915 CurlHttpClient [140465506043712] Obtained connection handle 0x55d0e75299e0
[TRACE] 2019-06-07 14:48:30.086 CurlHttpClient [140465506043712] HTTP/1.1 100 Continue

[TRACE] 2019-06-07 14:48:30.086 CurlHttpClient [140465506043712]

[TRACE] 2019-06-07 14:48:30.270 CurlHttpClient [140465506043712] HTTP/1.1 200 OK

[TRACE] 2019-06-07 14:48:30.270 CurlHttpClient [140465506043712] Content-Type: text/xml;charset=UTF-8

[TRACE] 2019-06-07 14:48:30.270 CurlHttpClient [140465506043712] Content-Length: 6419

[TRACE] 2019-06-07 14:48:30.270 CurlHttpClient [140465506043712] vary: accept-encoding

[TRACE] 2019-06-07 14:48:30.270 CurlHttpClient [140465506043712] Date: Fri, 07 Jun 2019 14:48:30 GMT

[TRACE] 2019-06-07 14:48:30.270 CurlHttpClient [140465506043712] Server: AmazonEC2

[TRACE] 2019-06-07 14:48:30.270 CurlHttpClient [140465506043712]

[TRACE] 2019-06-07 14:48:30.270 CurlHttpClient [140465506043712] 6419 bytes written to response.
[DEBUG] 2019-06-07 14:48:30.270 CurlHttpClient [140465506043712] Returned http response code 200
[DEBUG] 2019-06-07 14:48:30.270 CurlHttpClient [140465506043712] Returned content type text/xml;charset=UTF-8
[TRACE] 2019-06-07 14:48:30.270 CurlHttpClient [140465506043712] Response content-length header: 6419
[TRACE] 2019-06-07 14:48:30.270 CurlHttpClient [140465506043712] Response body length: 6419
[DEBUG] 2019-06-07 14:48:30.270 CurlHttpClient [140465506043712] Releasing curl handle 0x55d0e75299e0
[DEBUG] 2019-06-07 14:48:30.270 CurlHandleContainer [140465506043712] Releasing curl handle 0x55d0e75299e0
[DEBUG] 2019-06-07 14:48:30.270 CurlHandleContainer [140465506043712] Notified waiting threads.
[DEBUG] 2019-06-07 14:48:30.270 AWSClient [140465506043712] Request returned successful response.
[TRACE] 2019-06-07 14:48:30.270 AWSClient [140465506043712] Request successful returning.
[DEBUG] 2019-06-07 14:48:30.272 Aws::EC2::Model::DescribeInstancesResponse [140465506043712] x-amzn-request-id: 9da83eb5-400e-44e6-b8b2-cdbc9a8063a0
[INFO] 2019-06-07 14:48:30.272 CurlHandleContainer [140465506043712] Cleaning up CurlHandleContainer.
[INFO] 2019-06-07 14:48:30.273 CurlHandleContainer [140465506043712] Cleaning up CurlHandleContainer.
[DEBUG] 2019-06-07 14:48:30.273 CurlHandleContainer [140465506043712] Cleaning up 0x55d0e75246e0
[DEBUG] 2019-06-07 14:48:30.273 CurlHandleContainer [140465506043712] Cleaning up 0x55d0e75299e0

Looking into it

A few weeks ago we added a change to address that issue f9b4be3ffe4
We couldn't have that be turned on by default, because that would break existing code and have a surprising effect.
So, we do support loading the region from the config file, but you have to opt-in by specifying the name of the profile you're interested in.
Aws::Client::ClientConfiguration config("default");

Thanks for the help.


Rename deprecated import

Or maybe even destructured?
Haven't tested this, just the package name seems to be outdated

This path is correct. Thanks for double-checking it.

That was quick 🚀👍


docs: fix ADD destination in container-register-disks

What this PR does / why we need it:
With destination set to /disk, it places the image to file /disk. We need to
change it to /disk/ instead, so the image is put under /disk directory.
Special notes for your reviewer:
Release note:

Fixed image destination folder in container register disk docs

/lgtm
/approve
/retest


32 bit compilation

Good morning,
Does Angora support 32-bit targets / builds?
Like:
CC=$ANGORA/bin/angora-clang ./configure --prefix=`pwd`/install --disable-shared "CFLAGS=-m32" "CXXFLAGS=-m32" "LDFLAGS=-m32"

, which fails in my environment, because Angora libs are 64bits:
/usr/bin/ld: ./Angora/bin/lib/libruntime_fast.a(runtime_fast-d39a4de5e860747f.runtime_fast.9lmpyn81-cgu.11.rcgu.o): file class ELFCLASS64 incompatible with ELFCLASS32

Also can't build 32-bit version of Angora with:
cargo build --target=i686-unknown-linux-gnu
cargo build --release --target=i686-unknown-linux-gnu

because the build fails at https://github.com/AngoraFuzzer/Angora/blob/cd5439f383582b30c93def0f712a05ab9284ec25/fuzzer/src/executor/limit.rs#L23
with "expected u32, found u64".
Any option to do that?

Sorry, Angora doesn't support 32bit now. I will improve it in my plan. Thanks for your suggestion.


Bypass Firebase Signature?

Hey all,
For applications that use firebase as their primary analytics, authentication or database service, one might want to use apk-mitm to gather better insight into how these applications work.
Unfortunately, when using the patched APK, a production version of firebase can output:
{
	"error": {
		"code": 403,
		"message": "Requests from this Android client application com.someapp.android are blocked.",
		"status": "PERMISSION_DENIED",
		"details": [{
			"@type": "type.googleapis.com/google.rpc.ErrorInfo",
			"reason": "API_KEY_ANDROID_APP_BLOCKED",
			"domain": "googleapis.com",
			"metadata": {
				"service": "firebaseinstallations.googleapis.com",
				"consumer": "projects/some_project"
			}
		}]
	}
}

In these cases, is there any way to spoof the SHA-1 signature such that firebase accepts requests from the patched application?

I am experiencing the same issue.


vis, vis_video, vis_video_zoom in test.py

Thanks for the great work!
In test.py, there are several argument options:  --vis, --vis_video, --vis_video_zoom. I tried to visualize your work by enabling these options, but no picture nor video was generated.
Could you share more information about these visualization options? Thanks.

When calling test.py with the --vis flag the following error pops up:
***************setup render_glumpy environment succeed ******************
not using render_real depth in par_generate_gt
Traceback (most recent call last):
File "experiments/deepim/deepim_test.py", line 20, in
test.main()
File "experiments/deepim/../../deepim/test.py", line 210, in main
test_deepim()
File "experiments/deepim/../../deepim/test.py", line 203, in test_deepim
pairdb=pairdb,
File "experiments/deepim/../../deepim/core/tester.py", line 521, in pred_eval
flow_gt = par_generate_gt(config, pairdb[idx])
File "experiments/deepim/../../deepim/core/tester.py", line 752, in par_generate_gt
pair_rec["depth_real"], cv2.IMREAD_UNCHANGED
KeyError: 'depth_real'

@Cryptiex The key name might be refactored to depth_observed, since observed is real.

Thanks for the fast reply! Your solution solved my problem. However, another problem now occurs a few lines later:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/IPython/core/interactiveshell.py", line 2882, in run_code
exec(code_obj, self.user_global_ns, self.user_ns)
File "", line 1, in
runfile('/media/deeplearner2/DataSSD/PycharmProjects/mx-DeepIM-master/deepim/test.py', args='--cfg experiments/deepim/cfgs/deepim_flownet_LM_SIXD_v1_ape_RFMx4_8epoch.yaml --gpus 0 --vis', wdir='/media/deeplearner2/DataSSD/PycharmProjects/mx-DeepIM-master')
File "/home/deeplearner/pycharm-2018.2.4/helpers/pydev/_pydev_bundle/pydev_umd.py", line 197, in runfile
pydev_imports.execfile(filename, global_vars, local_vars)  # execute the script
File "/home/deeplearner/pycharm-2018.2.4/helpers/pydev/_pydev_imps/_pydev_execfile.py", line 18, in execfile
exec(compile(contents+"\n", file, 'exec'), glob, loc)
File "/media/deeplearner2/DataSSD/PycharmProjects/mx-DeepIM-master/deepim/test.py", line 214, in
main()
File "/media/deeplearner2/DataSSD/PycharmProjects/mx-DeepIM-master/deepim/test.py", line 210, in main
test_deepim()
File "/media/deeplearner2/DataSSD/PycharmProjects/mx-DeepIM-master/deepim/test.py", line 203, in test_deepim
pairdb=pairdb,
File "/media/deeplearner2/DataSSD/PycharmProjects/mx-DeepIM-master/deepim/core/tester.py", line 521, in pred_eval
flow_gt = par_generate_gt(config, pairdb[idx])
File "/media/deeplearner2/DataSSD/PycharmProjects/mx-DeepIM-master/deepim/core/tester.py", line 767, in par_generate_gt
if config.network.FLOW_I2R:
AttributeError: 'EasyDict' object has no attribute 'FLOW_I2R'

@Cryptiex Emmmm. You could simply change FLOW_I2R terms to True, and delete those FLOW_R2I. I2R means rendered to observed (i.e., imagine to real).

There still seem to be some errors when trying to visualize the testing process. There are like 4-5 undefined config parameters and dict keys. Maybe you can have a closer look at this problem, since this does not seem to be desired behavior of the implementation.
Thanks a lot.

@Cryptiex Now the errors should be gone. However, you still need to add some code to visualize the updated pose (e.g. by using the updated rendered color/depth and the updated pose_est). It should be easy. The visualization is out of scope of this repo.


Find a way to test colors

Does this have something to do with animations rewriting hex css values as rgba

No, it is related to colors in the console.


Issue #355: Add a .editorconfig file.

I'm not convinced, we have symplify/easy-coding-standard which contains php-cs-fixer and php-codesniffer rules for that. Look at https://github.com/php-ai/php-ml/blob/master/ecs.yml

I know and that tool is doing an amazing job.
.editorconfig is for autoconfiguring phpstorm or any other ide.
I'm using it everywhere in conjunction with ecs as well and it's doing a great job.

Ok :+1:, thanks.

Thanks ! 😉❤


[l10n] Add de-CH locale

[x] I have followed (at least) the PR section of the contributing guide.

@lukaselmer We appreciate the effort. However, we aim to support the 100 most used locales (documented here), Switzerland has below 10m people.

@lukaselmer We appreciate the effort. However, we aim to support the 100 most used locales (documented here), Switzerland has below 10m people.


Need get unmasked value

Is there a way to get unmasked value?

@the-darc any way to get this?

For now i'm using value = value.replace(/[^\d\p{L}]/g, ''); but I'm also curious about a proper way to do it.


Frontend: set up App.jsx with Apollo client

Code sampled from Module 21 challenge; implements main GraphQL endpoint

https://github.com/HashemE1999/locus/pull/56


Wording Basic: there might be Basic apps, but not every command line app is a basic app

We really should not upset people by saying - every non docker app is a basic app.
Suggestion: Command Line App

Other suggestions that were kicked around:
cgroups, mesos native, shell app, bash app, native app, non-dockerized-but-still-containerized app...
I recall seeing a clearly stated decision on native app, but of course I can't find it now. I'll post the link when I next see it.

@philipnrmn probably in an archived inVision board...

I'd go further and question whether distinguishing between Docker and non-Docker apps brings any value to the users.
My opinion is that it doesn't.

@philipnrmn : final decision can be found in the team sync meeting minutes.
@aquamatthias I think "Command Line App" is too long for the side bar:

It seems that users don't see any value in filtering applications by “basic” or “docker”. Let's remove the app type filter from the tab pan unless we have validation it will be useful.

+1 until further validation

Fixed by mesosphere/marathon-ui#364


Scan fixes

For some crazy reason we had ZERO tests around scan... even with the high level of code coverage we have...
Question everything. LOL.
This contains tests and fixes for scan.

I'm really, really shocked we missed this one. :\

Yeah, RxJS 4 uses scan in retryWhen tests, so if we have scan broken, I can't properly replicate retryWhen tests. Good to get this fixed asap.


Add required sections to the Readme to comply with the Open Mainframe Project template

https://github.com/openmainframeproject/project-template

Forgot to include closes #34 in the commit message, but commit c261f closes this issue.


Built-in Component Scanner

Adds a built in component scanner to help keep competitive combat more fair.
There's still some work to do here, but this is probably good enough for a first version, and I've optimized the server-side code as much as I can. If anything else weird is seen, let me know. I'll be PR'ing more after this initial PR to further improve the performance/re-organize the file/actually make the tabs usable.

When scanning a player that doesn't has a finished, unconstrained, vehicle I start getting this error.
addons/acf3-server/lua/acf/scanner/scanner_sh.lua:298: attempt to call method 'GetContraption' (a nil value)
stack traceback:
	addons/acf3-server/lua/acf/scanner/scanner_sh.lua:298: in function 'v'
	lua/includes/modules/hook.lua:96: in function <lua/includes/modules/hook.lua:79> (x16)


Add temperature change

Ability to change temperature of a model without changing config files is pretty important feature

I just added a new issue for a new feature that based on your suggestion: #116
If you have a minute take a look at it, would appreciate your feedback.
Closing this issue so the discussion continues there.


refactor: don't convert schema to protobuf just for pre-order traversal of fields

There was a TODO for this


Docker installation option?

Hi
Is there a Docker options available?

No, I don't know anything about Docker


Spring Cloud Gateway appends passed X-Forwarded-For header value to the right instead of to the left

Describe the bug
Call me crazy but apparently Spring Cloud Gateway processing of passed X-Forwarded-For header is broken since at least 2018. If someone would pass their fake IP in X-Forwarded-For header it gets appended at the right of the X-Forwarded-For header instead of left, and then gets passed to the downstream service. This completely breaks trust chain in downstream web server, for example in embedded Tomcat with trusted-proxy and/or internal-proxy configuration.
Steps to reproduce:

Create standard empty Spring Boot application with one endpoint which uses spring-boot-starter-web.

Enable X-Forwarded-For header logging in the embedded Tomcat:
server.tomcat.accesslog.enabled=true
server.tomcat.accesslog.request-attributes-enabled=true
server.tomcat.accesslog.pattern=%h %l %u %t "%r" %s %b "%{X-Forwarded-For}i"

Enable NATIVE forwarding header strategy if you are not running on cloud platform:
server.forward-headers-strategy=NATIVE

And enable RemoteIpValve logging for debugging purposes:
logging.level.org.apache.catalina.valves.RemoteIpValve=DEBUG

Create standard Spring Cloud Gateway application and attach downstream service to it. Expose the endpoint through gateway configuration and Spring Security.

Deploy both applications.

(optional) Add additional Load Balancer in front of the application. On Google Cloud it could be simple GKE Ingress. Don't forget to add load balancer to trusted-proxy list in the downstream application. For me it was:
server.tomcat.remoteip.trusted-proxies=34\\.120\\.174\\.194

Or adjust internal-proxy list if you are using Spring Boot 2.7.x as it doesn't support trusted-proxies:
server.tomcat.remoteip.internal-proxies=34\\.120\\.174\\.194|10\\.\\d{1,3}\\.\\d{1,3}\\.\\d{1,3}|192\\.168\\.\\d{1,3}\\.\\d{1,3}|169\\.254\\.\\d{1,3}\\.\\d{1,3}|127\\.\\d{1,3}\\.\\d{1,3}\\.\\d{1,3}|100\\.6[4-9]{1}\\.\\d{1,3}\\.\\d{1,3}|100\\.[7-9]{1}\\d{1}\\.\\d{1,3}\\.\\d{1,3}|100\\.1[0-1]{1}\\d{1}\\.\\d{1,3}\\.\\d{1,3}|100\\.12[0-7]{1}\\.\\d{1,3}\\.\\d{1,3}|172\\.1[6-9]{1}\\.\\d{1,3}\\.\\d{1,3}|172\\.2[0-9]{1}\\.\\d{1,3}\\.\\d{1,3}|172\\.3[0-1]{1}\\.\\d{1,3}\\.\\d{1,3}|0:0:0:0:0:0:0:1|::1

Call your endpoint with the request header X-Forwarded-For: <IP_ADDRESS>.

Observe RemoteIpValve logs:
Incoming request /v2 with originalRemoteAddr [<IP_ADDRESS>], originalRemoteHost=[<IP_ADDRESS>], originalSecure=[false], originalScheme=[http], originalServerName=[<IP_ADDRESS>], originalServerPort=[9102] will be seen as newRemoteAddr=[<IP_ADDRESS>], newRemoteHost=[<IP_ADDRESS>], newSecure=[true], newScheme=[https], newServerName=[you.loadbalancer.example.com], newServerPort=[443]
Observe Tomcat access logs:
<IP_ADDRESS> - - [22/Mar/2024:07:26:36 +0000] "POST /v2 HTTP/1.1" 200 602924 "<IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>,<IP_ADDRESS>"
Note how fake IP <IP_ADDRESS> took over remoteAddr in Tomcat and additional <IP_ADDRESS> at the end of X-Forwarded-For header.

Now turn off Spring Cloud Gateway and expose your downstream application directly.

Observe correct remoteAddr in Tomcat access logs:
<IP_ADDRESS> - - [22/Mar/2024:11:35:36 +0000] "POST /client/v2 HTTP/1.1" 200 - "<IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>"

Not sure if this ever worked correctly, or maybe this change made header parsing and appending different, but this could be considered serious security issue.

Please report security issues at https://spring.io/security-policy


Consider not re-downloading files when the user deletes them

From conversation with @jhiesey:
i just moved the downloaded .zip file and webtorrent decided to redownload it instead of giving an error like transmission

might be good to not download a file again once it’s been deleted

@feross this is fixed now with the Path missing check, right?

Right -- this is fixed now.


chore: Bump dependencies and golanglint-ci

What this PR does / why we need it:
Bump dependencies and golanglint-ci
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

None

/cc @jcanocan

Needs https://github.com/kubevirt/project-infra/pull/3591 first

/retest-required

/lgtm

/approve


feat: Support ollama's keep_alive request parameter

Is your feature request related to a problem? Please describe.
Ollama unloads models after 5 minutes by default. A new parameter, keep_alive, allows the user to set a custom value.
It would be nice to have an option in the UI where a value for this parameter can be set.
Here is the relevant PR: #2146

That would be useful, indeed.

Is your feature request related to a problem? Please describe. Ollama unloads models after 5 minutes by default. A new parameter, keep_alive, allows the user to set a custom value. It would be nice to have an option in the UI where a value for this parameter can be set.
 Any idea why?

 Any idea why?

Are you running the pre-release version? v0.1.23?

 Any idea why?

Are you running the pre-release version? v0.1.23?

Thanks so much! I was on 0.1.22, but I got it now. It is definitely releasing it based on the timing I indicate with keep_awake, but it doesn't completely release it. if i use a model that uses 1500, it releases down to 500ish based on the timing I indicate. Why doesn't it go down to 0? Is it a bug or is it not expected to? After i use ollama ever on my computer i either have to force cancel it or restart to get it completely out of memory.
Also, even with keep_awake = 0, if I loop a few different models that each run fine on their own, then after a few cycles the usage builds up too much and i get a memory overload crash.
There must be some way to completely remove it from memory after it has been used, isn't there?

Why doesn't it go down to 0? Is it a bug or is it not expected to? After i use ollama ever on my computer i either have to force cancel it or restart to get it completely out of memory.

For me it goes down to ~200MB, it goes up by a few MB for additional models, but not as much as yours. Unfortunately I don't know what is going on here.
Are you running large models?

That's most likely down to how your host system is managing memory caching. Some OSes try to be helpful by keeping things you've just closed resident in memory... y'know just in case you closed it by mistake, or you're going to need it again in a few minutes. There's ways to tune this behaviour but that's out of scope of this project, and probably out of scope for Ollama too.

@zehDonut @justinh-rahb Thanks so much, it is helpful to know that I was barking up the wrong tree. I found a solution that works for me.
Here is the exact situation for anyone else with the same issue. I am bouncing between generating images with stable diffusion and using llava to describe them and then another model to make new image prompts. I need to occasionally kill llama or the ram goes too high and crashes, but the ollama processes need sudo to kill them, so now I am inputting my sudo password into the program on runtime so it can use it to occasionally the ollama process which I find with a combination of nvidia-smi and a regex.

Created PR #721 to support this.


This library assumes a 32-bit processor for all length fields on API.

When compiling for a 64-bit there's a lot of additional casting due to the API definition of all
"uint32_t ul.*Length" parameters
An example is:
AzureIoTProvisioningClient_SetSymmetricKey
AzureIoTResult_t AzureIoTProvisioningClient_SetSymmetricKey( AzureIoTProvisioningClient_t * pxAzureProvClient,
                                                             const uint8_t * pucSymmetricKey,
                                                             uint32_t ulSymmetricKeyLength,
                                                             AzureIoTGetHMACFunc_t xHmacFunction );

Should be:
AzureIoTResult_t AzureIoTProvisioningClient_SetSymmetricKey( AzureIoTProvisioningClient_t * pxAzureProvClient,
                                                             const uint8_t * pucSymmetricKey,
                                                             size_t ulSymmetricKeyLength,
                                                             AzureIoTGetHMACFunc_t xHmacFunction );

List of functions that should change are:

AzureIoTProvisioningClient_GetDeviceAndHub
AzureIoTProvisioningClient_SetRegistrationPayload
AzureIoTProvisioningClient_SetSymmetricKey
AzureIoTProvisioningClient_Init
AzureIoTProvisioningClient - function declaration.

Suggest also changing the structures to use size_t as well, but If there is a requirement not to change the types for the structures eg: uint32_t  ulSymmetricKeyLength; - to size_t ulSymmetricKeyLength then this library can do the conversion to the uint32_t when they are assigned.

Hi @phelter
This was done for parity with FreeRTOS. Example here: https://github.com/FreeRTOS/FreeRTOS-Kernel/blob/b0a8bd8f28d0138b5eb70e8b53da3e9d17ce8d40/include/task.h#L474
I don't see us changing this at all in this SDK but we appreciate the interest!

@danewalton  - You've provided an example which is not relevant to the use case here.  A stackDepth is not a Length.
That's like saying a network port which is a uint16_t - what it is defined on the network layer stack is a size.

This is also  in this repo - ulPort here

In FreeRTOS-Kernel there are the following examples of using size_t:
The most identifiable one is here where config_MESSAGE_BUFFER_LENGTH_TYPE is defined as size_t https://github.com/FreeRTOS/FreeRTOS-Kernel/blob/11c72bc075b49bfdeb73d7e4bd94fd5a7d0a5e77/include/FreeRTOS.h#L994  - This example is a LENGTH_TYPE defined as size_t.
There are 51 other examples in the code with this search FreeRTOS-Kernel
So right now there are 3 different types used for lengths inside the API's
uint32_t
uint16_t
and size_t.
Best practice is to use size_t - since then you don't have to cast when using sizeof(array) or when using strnlen() or strlen() output or other length checking standard C library functions.  Having various different types means the user of your API now needs to cast to the particular type every time it interacts with other functions.  In addition - it provides better packing inside structs for the cases where you include a pointer and size back-to-back since in 64-bit machines identifying the size as a uint32_t instead of a size_t will cause a pack warning, but when using a size_t won't - both will have the same size since there is padding added for a uint32_t anyways.
Please consider fixing since this is an annoyance using this API.  Any *Length parameter that is associated with a pointer or struct size - the best practice is to use a size_t.


can't find module 'pyspark_cassandra'

Start pyspark:
spark-1.6.0-bin-hadoop2.6/bin/pyspark --packages com.datastax.cassandra:cassandra-driver-core:3.0.0,TargetHolding/pyspark-cassandra:0.2.1
...
16/02/23 11:15:18 INFO SparkContext: Added JAR file:/root/.ivy2/jars/TargetHolding_pyspark-cassandra-0.2.1.jar at http://<IP_ADDRESS>:50605/jars/TargetHolding_pyspark-cassandra-0.2.1.jar with timestamp<PHONE_NUMBER>787
...
16/02/23 11:15:18 INFO Utils: Copying /root/.ivy2/jars/TargetHolding_pyspark-cassandra-0.2.1.jar to /tmp/spark-7fa1e67b-cc9b-4898-acbe-bad914be9838/userFiles-8082337d-7ea7-4b24-9818-a8a33f38e3ba/TargetHolding_pyspark-cassandra-0.2.1.jar
16/02/23 11:15:18 INFO SparkContext: Added file file:/root/.ivy2/jars/TargetHolding_pyspark-cassandra-0.2.1.jar at file:/root/.ivy2/jars/TargetHolding_pyspark-cassandra-0.2.1.jar with timestamp<PHONE_NUMBER>876
...

import pyspark_cassandra
Traceback (most recent call last):
File "", line 1, in
zipimport.ZipImportError: can't find module 'pyspark_cassandra'

Could you be so kind as to add a question / remark next time instead of just dropping a stacktrace? Thanks.
I recommend you do take a look at the latest version of pyspark_cassandra: http://spark-packages.org/package/TargetHolding/pyspark-cassandra (0.2.7).

Appreciate the suggestion, however, I get the same outcome.
question/remark : it looks like a bug, so I submitted it. Obviously the question(s) is/are: what's wrong, how can it be resolved, etc etc.

Looks like I had to clear ~/.ivy2/jars/ dir and rerun. However, this presented a different "SyntaxError: invalid syntax". Should I post the error here or start a new Issue?

hi @rookie7799, thanks for the update. Could you give a full stacktrace of the error? Which line in what file is causing the syntax error? Can you provide details about your setup? E.g. what python version are you using?

Sure,
Running on CentOS release 6.6, using python 2.6.6; also, I've changed the params a bit:
/bin/pyspark --packages com.datastax.cassandra:cassandra-driver-core:3.0.0 --jars pyspark-cassandra/target/scala-2.10/pyspark-cassandra-assembly-0.2.7.jar --py-files /root/pyspark-cassandra/python/dist/pyspark_cassandra-0.2.7-py2.6.egg --driver-class-path pyspark-cassandra/target/scala-2.10/pyspark-cassandra-assembly-0.2.7.jar
Calling " import pyspark_cassandra " causes the following error:
Traceback (most recent call last):   File "<stdin>", line 1, in <module>   File "build/bdist.linux-x86_64/egg/pyspark_cassandra/__init__.py", line 24, in <module>   File "build/bdist.linux-x86_64/egg/pyspark_cassandra/context.py", line 16, in <module>   File "/tmp/spark-e7ded847-127d-49f5-8751-d19f958746a7/userFiles-eca454b6-5125-4f29-bb62-cbe99ed325ac/pyspark_cassandra-0.2.7-py2.6.egg/pyspark_cassandra/rdd.py", line 291     k = Row(**{c: row.__getattr__(c) for c in columns})                                        ^ SyntaxError: invalid syntax

This is an issue with python 2.6 which unfortunately isn't supported. I currently don't have any means of testing for this python version.


When the powershell window is closed, the hook will become invalid.

When the powershell window is closed, the hook will become invalid. You need to reset the hook the next time you start powershell. This is too troublesome.

I see you closed the issue, did you resolve it?

echo "Invoke-Expression (&scoop-search --hook)" > "C:\Windows\System32\WindowsPowerShell\v1.0\profile.ps1"
My English is not good. So I didn’t understand the readme at the beginning. I solved it through this method now.
thanks ~


Use backticks to format references to the file name in resolving-a-merge-conflict-using-the-command-line#removed-file-merge-conflicts

Code of Conduct

[X] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?
https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line#removed-file-merge-conflicts
This issue is intended for newcomers to the OS Docs repo! 💛
If you are veteran of the OS Docs repo and are looking for issues to work on, take a look at our help wanted section ✨
What part(s) of the article would you like to see updated?

For example, if you edited a file, such as README.md...

Use backticks to format references to the file names (instead of italics)
Additional information
Style guide reference


Fix CAN Addressing Information for CAN Entities

Description
Fix the bug related to insufficient Addressing Information storing.
How Has This Been Tested?

unit tests
integration tests
review

Process
I know the process and did my best to follow it

Codecov Report

Merging #163 (2a85728) into main (d2d2aac) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main      #163   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           38        42    +4
  Lines         2153      2241   +88
=========================================
+ Hits          2153      2241   +88

Flag
Coverage Δ

integration-tests
87.23% <87.50%> (-0.60%)
:arrow_down:

unit-tests
100.00% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

uds/__init__.py
100.00% <ø> (ø)

uds/packet/abstract_packet.py
100.00% <ø> (ø)

uds/can/__init__.py
100.00% <100.00%> (ø)

uds/can/abstract_addressing_information.py
100.00% <100.00%> (ø)

uds/can/addressing_information.py
100.00% <100.00%> (ø)

uds/can/consecutive_frame.py
100.00% <100.00%> (ø)

uds/can/extended_addressing_information.py
100.00% <100.00%> (ø)

uds/can/first_frame.py
100.00% <100.00%> (ø)

uds/can/flow_control.py
100.00% <100.00%> (ø)

uds/can/frame_fields.py
100.00% <100.00%> (ø)

... and 13 more


Invalid option `--base16'

Tried to call this:
cat shelley_phrase.prv \
   | cardano-address key from-recovery-phrase Shelley \
   | cardano-address key child 1852H/1815H/0H/0/0 --base16

but got error:
Invalid option '--base16'

Usage: cardano-address ((-v|--version) | COMMAND)
  Command-line for address and key manipulation in Cardano.

Is the --base16 still supported? I am using
3.5.0 @ 9fe7084c9c53b9edf3eba34ee8459c896734ac7a
Thanks.

Hi @edwardtam919, there is no --base16 switch in cardano-address (any more).
You can pipe the output through the bech32 utility to get hex. Like this:
cat shelley_phrase.prv \
    | cardano-address key from-recovery-phrase Shelley \
    | cardano-address key child 1852H/1815H/0H/0/0 \
    | bech32


Optimization: only recheck useTickEffect memos when an effect modified state

Due to #20, a useTickEffect's memos are always rechecked after the Initialize and Step phases in case a prior effect modified state. In such a situation, the useTickEffect's memos might now be outdated, so we need to recheck them and rerun the tick effect if they changed. Unfortunately, this step occurs even when we know that no state modifications have occurred. As a result, performance suffers somewhat due to the additional unnecessary render.
Thus, we should optimize the hooks implementation, so that during an Initialize or Step phase, we recheck the useTickEffect memos only if prior effect actually modified some state.

Closed by #28


chore: reformat chart templates

Description
The PR reformats chart templates to common style with more readable blocks and indents.
ConfigMap trivy-operator-policies-config has been deleted, because it does not have any data.
The PR does not change any functionality of the chart.
Similar PRs: https://github.com/apache/airflow/pull/29917 https://github.com/apache/airflow/pull/29941 https://github.com/apache/airflow/pull/30312 https://github.com/minio/minio/pull/16947 https://github.com/apache/superset/pull/23681
Test
The following command prints same (minor differences) output before and after changes:
helm template test deploy/helm

Checklist

[x] I've read the guidelines for contributing to this repository.
[ ] I've added tests that prove my fix is effective or that my feature works.
[ ] I've updated the documentation with the relevant information (if needed).
[ ] I've added usage information (if the PR introduces new options)
[ ] I've included a "before" and "after" example to the description (if the PR is a user interface change).

@dnskr lgtm , just once comment , why you decided to delete the policies.yaml ?

I deleted policies.yaml file, because it contains ConfigMap trivy-operator-policies-config only which is constantly empty.
I mean there are no keys in it and the keys cannot be added through values.

I deleted policies.yaml file, because it contains ConfigMap trivy-operator-policies-config only which is constantly empty. I mean there are no keys in it and the keys cannot be added through values.

this configmap is a place holder for for external rego policies for configAudit reports (empty by default), as built-in policies are used by default.
it is used by our customers and users,  Lets keep it for now.

I'm ok to keep it for now. However, could you please explain how the ConfigMap trivy-operator-policies-config is used by users? I'm asking, because of the following:

The configmap is empty and it's impossible to populate it using Helm and command like helm install ... --set secretKey=secretValue.
There are no resources in the chart which refer to trivy-operator-policies-config, i.e. the configmap is not mounted to any container filesystem and it's not used as the source for environment variable. So, I don't understand how it can be used then.
If the users populate it manually with kubectl edit ..., then the content of the configmap will be overwritten/wiped during next chart release upgrade helm upgrade ....

I found one more empty resource - Secret trivy-operator in config.yaml file.

I agree that its can't be update via helm, however it is used by users who update it with kubectl and hooks on every upgrade.
users also use it via trivy-operator static yaml.
in addition we have plan for it in the future therefore I prefer to keep it

Got it! I returned it back.

@dnskr thank you for the contribution  lgtm 🚀


perf issues with esbuild

Describe the bug
I found that the vite:esbuild plugin is taking very long time when project has a lot of directories / content (I mean it can take minutes, tested on WSL2 & Win)
https://github.com/vitejs/vite/blob/7be0ba5bd6a57d84b5efdc40db5e532299df1507/packages/vite/src/node/plugins/esbuild.ts#L235-L237
Can we not await it on resolveConfig hook ?
Why do we need to retrieve all tsconfig on the project?
Reproduction
https://stackblitz.com/edit/vitejs-vite-pruyxz?terminal=dev
Steps to reproduce
It's hard to reproduce, it needs a lot of directory / content.
I can share a private repository to reproduce or adapt https://github.com/stafyniaksacha/nuxt-compos-bench
System Info
System:
    OS: Linux 5.15 Ubuntu 22.04.2 LTS 22.04.2 LTS (Jammy Jellyfish)
    CPU: (16) x64 AMD Ryzen 9 5900HS with Radeon Graphics
    Memory: 6.31 GB / 15.33 GB
    Container: Yes
    Shell: 5.8.1 - /usr/bin/zsh
  Binaries:
    Node: 18.15.0 - ~/.nvm/versions/node/v18.15.0/bin/node
    Yarn: 1.22.19 - /mnt/c/Program Files/nodejs/yarn
    npm: 9.5.0 - ~/.nvm/versions/node/v18.15.0/bin/npm
  Browsers:
    Chrome: 110.0.5481.177
  npmPackages:
    vite: ^4.2.0 => 4.2.1

hdparm -tT /dev/sda

/dev/sda:
 Timing cached reads:   46682 MB in  2.00 seconds = 23388.97 MB/sec
 Timing buffered disk reads: 362 MB in  0.55 seconds = 663.80 MB/sec

Used Package Manager
pnpm
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Are you sure that it is actually tsconfck that is blocking?
you can run DEBUG=vite:esbuild vite dev  and it is going to log how long it takes vite to initialize tsconfck cache.
Or you can run npx tsconfck@latest find-all .  and tsconfck is going to print all tsconfig.json files in that directory.
For reference, tsconfck  find-all  on my /develop directory returned a list of 2.2k tsconfig.json files after 49s. out of 1.8 million files and directories.
That being said, find -type f -name tsconfig.json .  only takes 3s for the same result, so there definetely is room for optimization here.
It would be great if you could share stats about the size ( number of directories, files, nesting depth) in your project.

I got different result between running via CLI and in my app (which use nuxt 3) but the size is not that huge from your tests
> find . -type f -not -path '.*node_modules/*' | wc -l
7927

Adding console.time inside my node module like:
async function findAll(dir, options) {
  const files = [];
  console.time('findAll')
  for await (const tsconfigFile of findTSConfig(require$$0$4.resolve(dir), options)) {
    files.push(tsconfigFile);
  }
  console.timeEnd('findAll')
  return files;
}

gives: findAll: 1:03.093 (m:ss.mmm)
But using CLI (without having anything in the stack) has much better results:
$ time npx tsconfck@latest find-all .
npx tsconfck@latest find-all .  5.57s user 1.51s system 102% cpu 6.898 total

$ time find . -type f -name tsconfig.json
find . -type f -name tsconfig.json  0.03s user 0.06s system 99% cpu 0.096 total

I've found this stackoverflow topic that speak about libuv thread pool that might be stuck waiting for other read: https://stackoverflow.com/a/59594320/5303877

Awesome @dominikg thanks!
Also, is it necessary to block configResolved hook while initTSConfck hasn't finished?


youtube-dl -netrc not working

Please follow the guide below

You will be asked some questions and requested to provide some information, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your issue (like that [x])
Use Preview tab to see how your issue will actually look like

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2017.05.14. If it's not read this FAQ entry and update. Issues with outdated version will be rejected.

[x ] I've verified and I assure that I'm running youtube-dl 2017.05.14

Before submitting an issue make sure you have:

[x ] At least skimmed through README and most notably FAQ and BUGS sections
[x ] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

[ ] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[x ] Other

The following sections concretize particular purposed issues, you can erase any section (the contents between triple ---) not applicable to your issue

If the purpose of this issue is a bug report, site support request or you are not completely sure provide the full verbose output as follows:
Add -v flag to your command line you run youtube-dl with, copy the whole output and insert it here. It should look similar to one below (replace it with your log inserted between triple ```):
$ youtube-dl -v <your command line>
[debug] System config: []
[debug] User config: []
[debug] Command-line args: [u'-v', u'http://www.youtube.com/watch?v=BaW_jenozKcj']
[debug] Encodings: locale cp1251, fs mbcs, out cp866, pref cp1251
[debug] youtube-dl version 2017.05.14
[debug] Python version 2.7.11 - Windows-2003Server-5.2.3790-SP2
[debug] exe versions: ffmpeg N-75573-g1d0487f, ffprobe N-75573-g1d0487f, rtmpdump 2.4
[debug] Proxy map: {}
...
<end of log>

If the purpose of this issue is a site support request please provide all kinds of example URLs support for which should be included (replace following example URLs by yours):

Single video: https://www.youtube.com/watch?v=BaW_jenozKc
Single video: https://youtu.be/BaW_jenozKc
Playlist: https://www.youtube.com/playlist?list=PL4lCao7KL_QFVb7Iudeipvc2BCavECqzc

Note that youtube-dl does not support sites dedicated to copyright infringement. In order for site support request to be accepted all provided example URLs should not violate any copyrights.

Description of your issue, suggested solution and other information
I am having trouble using the --netrc feature. I have not had any problems with using youtube-dl before until I tried setting up the the .netrc feature. I am usinga linux os
I setup the .netrc file in the folder "/home/my account" and in the .netrc is "machine youtube login<EMAIL_ADDRESS>password "password"" and when I try to run a youtube url I get this.

youtube-dl -v -n https://www.youtube.com/watch?v=8M_ywyGrPD8
[debug] System config: []
[debug] User config: [u'-i', u'-v', u'-u', u'PRIVATE', u'--download-archive', u'Video_Archive', u'-o', u'~/Videos/%(title)s-%(id)s.%(ext)s']
[debug] Custom config: []
[debug] Command-line args: [u'-v', u'-n', u'https://www.youtube.com/watch?v=8M_ywyGrPD8']
Usage: youtube-dl [OPTIONS] URL [URL...]
youtube-dl: error: using .netrc conflicts with giving username/password

I was hoping someone could help me fix "youtube-dl: error: using .netrc conflicts with giving username/password"
I've read the documentation on the youtube-dl website and it said to put "machine youtube login<EMAIL_ADDRESS>password my_youtube_password". The user name and password are all correct and and works when I use the -u -p features.

Did you even read the error message at all? It clearly tells you not to use -n and -u/-p at the same time.


Change to AKSequencer.loadMIDIFile() for issue 115

Re: https://github.com/AudioKit/AudioKit/issues/1155
Getting rid of old tracks using MusicSequenceDisposeTrack seems to be necessary before replacing the sequence with the one generated by the new MIDI file. Repeated calls to AKSequencer.loadMIDIFile() will now remove old tracks, create the new sequence, then build new tracks from the new sequence, which seems like expected default behaviour. I think this addresses the issue.
The other idea (i.e., overlaying a new tracks over the old ones) is a useful idea, and I will add it in the future with a different name (e.g., overlayNewMIDIFile) once I've tested it more thoroughly.
Also, I changed loopEnabled to private because it just keeps track of what the setter methods have done.

Thanks!


Rewrite Server

Depends on #91. Not yet ready to review

@tomaszdurka please review

@tomaszdurka please review

@tomaszdurka please review

@tomaszdurka please review

@tomaszdurka please review

please wait with the review

@tomaszdurka please review

ok then, lgtm

Shall we merge it and you'll create new one?

Yes yes, I am sorry. Busy with another one :) Thank you.


Basech a medal

Maybe it means something like someone has one eye that doesn't work?

Yes, someone that has eyesight issues sues literally or someone that cannot
locate anything. Another way of saying ‘Ke cheuiko?’
On Sat, Aug 12, 2023 at 03:31 John Bent @.***> wrote:

Maybe it means something like someone has one eye that doesn't work?
—
Reply to this email directly, view it on GitHub
https://github.com/tekinged/missing/issues/443, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AF2DJJEIDKT4C4EZTW2H6TLXU5LQJANCNFSM6AAAAAA3N3JKDU
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Or they literally have cataracts.
John, with one eye that doesn't work, that would be BALECH.
Beiusech a medal on the other hand is one with keen eyesight, literally and
figuratively. :)
On Sat, Aug 12, 2023, 10:12 AM Gnalu @.***> wrote:

Yes, someone that has eyesight issues sues literally or someone that
cannot
locate anything. Another way of saying ‘Ke cheuiko?’
On Sat, Aug 12, 2023 at 03:31 John Bent @.***> wrote:

Maybe it means something like someone has one eye that doesn't work?
—
Reply to this email directly, view it on GitHub
https://github.com/tekinged/missing/issues/443, or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AF2DJJEIDKT4C4EZTW2H6TLXU5LQJANCNFSM6AAAAAA3N3JKDU>

.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

—
Reply to this email directly, view it on GitHub
https://github.com/tekinged/missing/issues/443#issuecomment-1675982947,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXYSPXTYNEC556GO3AFCC53XU6TNTANCNFSM6AAAAAA3N3JKDU
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


undefined: driver.ConnBeginTx

I have this error on my windows10 host
github.com/denisenkom/go-mssqldb
....\denisenkom\go-mssqldb\mssql_go18.go:21: undefined: driver.ConnBeginTx
....\denisenkom\go-mssqldb\mssql_go18.go:24: undefined: driver.TxOptions
what should I do to slove this problem!!

What does go version say?
On Fri, Jan 6, 2017, 18:08 radong<EMAIL_ADDRESS>wrote:

I have this error on my windows10 host
github.com/denisenkom/go-mssqldb
....\denisenkom\go-mssqldb\mssql_go18.go:21: undefined: driver.ConnBeginTx
....\denisenkom\go-mssqldb\mssql_go18.go:24: undefined: driver.TxOptions
what should I do to slove this problem!!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/denisenkom/go-mssqldb/issues/206, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAuFseNC1GhMT8QjxkuI8L6jfLmD7NGMks5rPvOggaJpZM4LdTBB
.

I ask because go1.8 beta 1 won't work. Update to the latest and try again.
On Fri, Jan 6, 2017 at 6:28 PM Daniel Theophanes<EMAIL_ADDRESS>wrote:

What does go version say?
On Fri, Jan 6, 2017, 18:08 radong<EMAIL_ADDRESS>wrote:
I have this error on my windows10 host
github.com/denisenkom/go-mssqldb
....\denisenkom\go-mssqldb\mssql_go18.go:21: undefined: driver.ConnBeginTx
....\denisenkom\go-mssqldb\mssql_go18.go:24: undefined: driver.TxOptions
what should I do to slove this problem!!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/denisenkom/go-mssqldb/issues/206, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAuFseNC1GhMT8QjxkuI8L6jfLmD7NGMks5rPvOggaJpZM4LdTBB
.

My go version is "go1.8beta1 windows/amd64"!
what do you mean "up to latest", you code or go compiler!!
I have executed "git pull" command at your directory and excuted "go test",still I can see this error!!

Update to Go beta2 or master, or use go1.7.x.


Add prmindent utility

This works so well. Tested it on my machine on a few files and everything was top notch.
Do you want to merge this now or you would like to add a make flag that also indents every prm in the folder

Seems good. Well for me this is ready for merge. It works exactly as intended.


[fix] Use correct name of kameletbinding

Fixes this error Error from server (NotFound): kameletbindings.camel.apache.org "timer-source" not found

@nicolaferraro

@astefanutti

Thanks!


Could not start application crawly when trying to enter IEx

Having crawly as a dev dependency on mix gives an error if I try to run iex -S mix in my phoenix project:
** (Mix) Could not start application crawly: Crawly.Application.start(:normal, []) returned an error: shutdown: failed to start child: {:ranch_listener_sup, Crawly.API.Router.HTTP}
    ** (EXIT) shutdown: failed to start child: :ranch_acceptors_sup
        ** (EXIT) {:listen_error, Crawly.API.Router.HTTP, :eaddrinuse}

The error :eaddrinuse only happens because I'm already running phoenix in localhost:3000.
Why is crawly trying to reserve port 3000? Also: could we improve the error message to be more clear?

Crawly automatically starts a cowboy http endpoint to allow remote controlling of the Crawly service.
It is probably a good idea to let this as an opt-in feature, to avoid unexpected scenarios like this.

It would be nice to be able to disable this. We found this to be an issue when running tests while also running a dev environment. It can be solved by setting different port in the test environment from what is used in dev, but it seems more appropriate to simply disable remote control.


Compiler doesn't understand NodeJS glob patterns

The globbing pattern for the compiler is currently /path/to/**.js however NodeJS globbing patterns are of the form /path/to/**/*.js. Is there any way to make the compiler understand the NodeJS globbing syntax - and if not throw a warning or error for an invalid globbing pattern?
See chadkillingsworth/closure-compiler-npm#6 and chadkillingsworth/closure-compiler-npm#16.

I thought those were fixed in v20160208. See this test case: https://github.com/google/closure-compiler/blob/master/test/com/google/javascript/jscomp/CommandLineRunnerTest.java#L1221-L1222

NodeJS glob patterns seem to work as intended, see https://github.com/ChadKillingsworth/closure-compiler-npm/issues/16#issuecomment-203501213. I think the bug is in the Gulp plugin.


chore: filter bug

Description
In Binding Filters, labels do not have to have values, they only have to have keys. In the event that there is not value, there is an implication that the value is "" (empty string).
This scenario was overlooked in the checkOverlap function which checks if the binding's filters/annotations have overlap with the objects.
This was causing an error in UDS-Core as a pod was being ignored that contained the same key as the binding but a different value.
export function checkOverlap(record1: Record<string, string>, record2: Record<string, string>) {
  if (Object.keys(record1).length === 0) {
    return true;
  }
  for (const key in record1) {
    if (
      Object.prototype.hasOwnProperty.call(record1, key) &&
      Object.prototype.hasOwnProperty.call(record2, key) &&
      record1[key] === record2[key] // VALUES MUST BE THE SAME
    ) {
      return true;
    }
  }
  return false;
}

For Example:
When(a.ConfigMap)
  .IsCreated()
  .WithLabel("chuck-norris")
  .Mutate(async change => {
    // Try/catch is not needed as a response object will always be returned
    const response = await fetch<TheChuckNorrisJoke>(
      "https://api.chucknorris.io/jokes/random?category=dev",
    );

Related Issue
Fixes #

Relates to #
Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Other (security config, docs update, etc)

Checklist before merging

[x] Test, docs, adr added or updated as needed
[x] Contributor Guide Steps followed

Need to accommodate for AND, when both labels should match. This functionality currently does not
When(a.Pod)
  .IsUpdated()
  .WithLabel("batch.kubernetes.io/job-name")
  .WithLabel("service.istio.io/canonical-name")


Broken link to PrivacyGuides

The link https://www.privacyguides.org/android/overview// shows a blank page, checking console shows that the link is a 404. Removing the two slashes redirects you to the page https://www.privacyguides.org/en/os/android-overview/
The GitHub Page also shows the broken link.
Going to https://www.privacyguides.org/android/overview/ or https://www.privacyguides.org/android/overview// causes a 404 to be shown, but going to https://www.privacyguides.org/android/overview will redirect you to the intended page.

fixed, thanks!


add MappedTable

This is probably really awful snippet but let's learn from mistakes as we did in 30code.
TODO:

Description needs improvement definitely
Typos are probably present, fix them
Code could be prettier
Somehow let user know he can use custom table cells as another component

Updated snippet to include better and more accurate description. Omitted return keywords where possible.
Updated semantics so table now consists of table, thead and tbody elements.
Changed order of tags and updated difficulty to 1.

I am still not sure about footer as it would increase the snippet without too much value. Just same code as in the header. I am open for discussion on this one.

Thanks @meetzaveri 👍 I'll fix this today. And yes @skatcat31 there's 1 extra header, I'll have to see how to generalize this function a bit 😢
The general idea is that people won't render classic  elements but instead they will use their custom components. (I did something similar on my internship). Because of this, I agree that snippets should be generalized as much as possible so they can be applied in many cases.

I've updated my example to include changes proposed by @meetzaveri and @nikolalsvk.
There's another problem that I don't happen to know how to solve. @skatcat31 mentioned that snippets should be generalized as much as possible and I totally agree with that.
This example renders a table with columns id and name, any idea how to generalize this a bit?

              v.id
              v.name

You can use logical or operator like v.id || i. This will evaluate v.id if there or i if not.
So simple generalization on this would be the conditional approach - v.id || i

You can use logical or operator like v.id || i. This will evaluate v.id if there or i if not.
So simple generalization on this would be the conditional approach - v.id || i

I am really stupid 😢

I'm sorry, but I'll have to disagree with using index as a React element key:
// bad

  v.id
  v.name

// good

  v.id
  v.name

There are couple of reasons why you should NEVER use index as the key of a React element. This article describes it nicely https://medium.com/@robinpokorny/index-as-a-key-is-an-anti-pattern-e0349aece318
Also, great example is given in this stackoverflow answer https://stackoverflow.com/a/42775667/4158895

I will have to make similar changes to the footprint of #8.
Meanwhile, as far as keys are concerned, it's obviously preferred to supply ids for them, but if the user doesn't supply anything, there has to be a fallback. The snippet makes it clear that people should pass their own ids, instead of using indexes and I think this is a good enough way to implement this. Having to generate unique keys from the data in any other way would probably make the snippet too verbose.

I will have to make similar changes to the footprint of #8.
Meanwhile, as far as keys are concerned, it's obviously preferred to supply ids for them, but if the user doesn't supply anything, there has to be a fallback. The snippet makes it clear that people should pass their own ids, instead of using indexes and I think this is a good enough way to implement this. Having to generate unique keys from the data in any other way would probably make the snippet too verbose.

Yes @Chalarangelo  fallback is crucial validation in any scenario. That's why we always use index as fallback

Suggestion on generalizing: the snippet needs to do the most general part of the module and let the user supply the integral part. You don't want to format their divs, you only want to get rid of the loop they would have to do otherwise and the boiler plate. individual formatting should be a conscious developer decision because data is unique to each use case. Suggested change with formatter and optional header formatter.
Also I changed the case on the function name because it's not a type/class, which are often the only reason to title case something in programming, but that can be discussed in styling
function mappedTable({ data, headers, format }) {
  return (

        {headers && (

            {headers}

        )}

        {data.map(format}
)}

  );
}

example:
const people = [{ id: 841, name: 'John' }, { id: 241, name: 'Jesse' }];
ReactDOM.render(
  <mappedTable data={people}
    headers = {Object.keys(data[0]).map(key => {key}	})}
    format = {dataPoint =>
ID: {datapoint.id}	Name: {dataPoint.name}
}
  />,
  document.getElementById('root')
);

Now when writing it reads like the following story for the developer:
"I want a mapped table displaying headers of this specific format, and the data formatted this way through map"
The developer no longer has to go about the boilerplate and can create semantic code. That's a win.
Ideally however I'd probably move this to using children for the formatter:
(warning: I have not tested this due to time constraints. I might have borked the logical || for onlyChild condition on passing the formatter or possibly how I'm de-referencing them)
function mappedTable({ data, headers, format }) {
  let onlyChild;
  try{
    onlyChild = React.Children.only(props.children);
  }catch(_){
    onlyChild = false;
  }
  return (

        {!onlyChild && (

            {props.children[0]}

        )}

        {data.map(onlyChild || props.children[1])}

  );
}

const people = [{ id: 841, name: 'John' }, { id: 241, name: 'Jesse' }];

ReactDOM.render(
  <mappedTable data={people}>
    {Object.keys(data[0]).map(key => {key}	})}
    {dataPoint =>
ID: {datapoint.id}	Name: {dataPoint.name}
}
  </mappedTable>,
  document.getElementById('root')
);

Although now it begs the question of "should we do the boilerplate for
 &&
 or should we force the developer to do that too?
function mappedTable({ data, headers, format }) {
  let onlyChild;
  try{
    onlyChild = React.Children.only(props.children);
  }catch(_){
    onlyChild = false;
  }
  return (

      {!onlyChild && props.children[0]}

        {data.map(onlyChild || props.children[1])}

  );
}

const people = [{ id: 841, name: 'John' }, { id: 241, name: 'Jesse' }];

ReactDOM.render(
  <mappedTable data={people}>

{Object.keys(data[0]).map(key => {key}	})}

    {dataPoint =>
ID: {datapoint.id}	Name: {dataPoint.name}
}
  </mappedTable>,
  document.getElementById('root')
);

@skatcat31 From a learning standpoint, this is a very verbose snippet and requires a lot of work on the developer's side. A semi-opinionated component that does some stuff by itself is a lot easier to read and understand, let alone tweak and hack to your liking.
30-seconds projects have always been about teaching by example, while maintaining a balance for simple use-cases. I think that creating a simple table from a data source is just about enough. Same applies to #8, which is a simple list from data. These snippets are targeted at beginners mostly and do not aim to provide a full-fledged component that could be 100+ lines of code.
Meanwhile, I am implementing a collapse component for my next PR. I will try to make it as unopinionated as possible, but in general we have to do some CSS-in-JS to make these work and we have to make components as simple as possible with the least code. There are hundreds of libraries that create lot more robust components, we are not trying to compete with them. We are trying to demistify the ones that people use and give them a decent starting point to implement something they can use.

@Chalarangelo React is an advanced topic in and of itself would be an argument to be made, but that's beside the point 👺(tengu used here to denote personal feeling above what could be considered true)
However 30react.mappedList() is a much more simple concept since lists are a more simple concept. Tables are always verbose because you have more data to display. I would still say it should have a formatter however. If you're using react and don't understand how that a function can be passed...
This is however an introduction to Children and Children.only(). Maybe this one should be an advanced snippet?
If not we could have an archive version of a generic mappedTable so that people who want to click the link in the non advanced version can see how it can be expanded to a more advanced version that can be used in more places with custom formatting at each instance and save them boilerplate?

@Chalarangelo another suggestion:
mappedList, basicList, mappedTable, basicTable may be four snippets that could all show similar, yet different approaches to the same situation(or the basics can link to an archive advanced version with mapping)
I think at this point I'm getting hung up that we're calling them mapped yet have nothing to map?

Mapped referred to mapping data via Array.map to a view. BasicTable and BasicList sound a bit funny to me, honestly, but maybe the naming doesn't do the snippets justice.
We certainly need more advanced versions of snippets, which could be like evolutions of snippets (possibly a very neat website feature where you can see if a snippet has a supercharged version and view it if you want?). However, that early in the project's development, we should stick to very basic implementations to get a feel for everything and then expand onto more advanced ones. Slow and steady wins the race! 😉

so then archived more advanced suggestion it is then(advanced due to concepts in play, not length).

Summary: More advanced versions should be implemented, but not until we have some guidelines and some feedback. Naming for this and #8 seems to be a bit weird, so we kinda need to come up with better names for the basic versions of these snippets. @fejes713 (if you do not have much time to read through the whole thing)

@skatcat31 you know you could just name them DataTable and DataList, that sounds reasonably simple and it literally describes the component - a table/list created from some data.

@Chalarangelo the basic ones or the advanced ones as DataXXXXX?

@skatcat31 basic ones as DataSomething, advanced ones as MappedSomething (or similar).

I'm going to pick this up in a bit, switch it to DataTable and apply the following changes:

Use only one prop, data, a normal array of values.
Render the headers as id and data.
Simplify code to work with said changes.

Revisiting this, I realize we should make this a very simple example of printing out a table from an array of values, which has its use-cases.
I will also PR a second snippet, MappedTable that will render an array of objects, based on a second prop, headers, which will filter the properties of said objects and only render those. This would be a more advanced, more robust version of the snippet, while this would be a dead-simple example of rendering data to the DOM quickly and efficiently.


Jellyfin: Add pagination for get_library_albums and get_library_artists

On my test instance I have ~800 artists and ~400 albums, which get fetched in 2 requests. This works and is fast, but I guess some people will have much bigger libraries and that might be a problem. So add some pagination.
After this PR, i'll be switching get_library_tracks to do similar.

Long term solution we can also investigate if we can leverage something like E-Tag to determine if the library actually changed to speedup syncs even further. Just need to figure out a way how to make that opt-in per provider, maybe just by setting a ProviderFeature. Food for thought (for later) again. Anyways, this looks good!


Auto-deploy production: Vite manifest not found at: /var/task/user/public/build/manifest.json

Bug report

Version<EMAIL_ADDRESS>URL: No
Repository: Yes

Description
Auto-deploy using git push resulting error below:
Illuminate\View\ViewException:
Vite manifest not found at: /var/task/user/public/build/manifest.json (View: /var/task/user/resources/views/welcome.blade.php)

  at /var/task/user/vendor/laravel/framework/src/Illuminate/Foundation/Vite.php:728
  at Illuminate\View\Engines\CompilerEngine->handleViewException(object(ViteManifestNotFoundException), 0)
     (/var/task/user/vendor/livewire/livewire/src/Mechanisms/ExtendBlade/ExtendedCompilerEngine.php:58)
  at Livewire\Mechanisms\ExtendBlade\ExtendedCompilerEngine->handleViewException(object(ViteManifestNotFoundException), 0)
     (/var/task/user/vendor/laravel/framework/src/Illuminate/View/Engines/PhpEngine.php:60)
  at Illuminate\View\Engines\PhpEngine->evaluatePath('/tmp/views/839bcec1d3afebf153f86eee6030524f.php', array('__env' => object(Factory), 'app' => object(Application), 'errors' => object(ViewErrorBag)))
     (/var/task/user/vendor/livewire/livewire/src/Mechanisms/ExtendBlade/ExtendedCompilerEngine.php:22)
  at Livewire\Mechanisms\ExtendBlade\ExtendedCompilerEngine->evaluatePath('/tmp/views/839bcec1d3afebf153f86eee6030524f.php', array('__env' => object(Factory), 'app' => object(Application), 'errors' => object(ViewErrorBag)))
     (/var/task/user/vendor/laravel/framework/src/Illuminate/View/Engines/CompilerEngine.php:72)
  at Illuminate\View\Engines\CompilerEngine->get('/var/task/user/resources/views/welcome.blade.php', array('__env' => object(Factory), 'app' => object(Application), 'errors' => object(ViewErrorBag)))
     (/var/task/user/vendor/livewire/livewire/src/Mechanisms/ExtendBlade/ExtendedCompilerEngine.php:10)
  at Livewire\Mechanisms\ExtendBlade\ExtendedCompilerEngine->get('/var/task/user/resources/views/welcome.blade.php', array('__env' => object(Factory), 'app' => object(Application), 'errors' => object(ViewErrorBag)))
     (/var/task/user/vendor/laravel/framework/src/Illuminate/View/View.php:207)
  at Illuminate\View\View->getContents()
     (/var/task/user/vendor/laravel/framework/src/Illuminate/View/View.php:190)
  at Illuminate\View\View->renderContents()
     (/var/task/user/vendor/laravel/framework/src/Illuminate/View/View.php:159)
  at Illuminate\View\View->render()
     (/var/task/user/vendor/laravel/framework/src/Illuminate/Http/Response.php:69)
  at Illuminate\Http\Response->setContent(object(View))
     (/var/task/user/vendor/laravel/framework/src/Illuminate/Http/Response.php:35)
  at Illuminate\Http\Response->__construct(object(View), 200, array('Content-Type' => 'text/html'))
     (/var/task/user/vendor/laravel/framework/src/Illuminate/Routing/Router.php:918)
  at Illuminate\Routing\Router::toResponse(object(Request), object(View))
     (/var/task/user/vendor/laravel/framework/src/Illuminate/Routing/Router.php:885)
  at Illuminate\Routing\Router->prepareResponse(object(Request), object(View))
     (/var/task/user/vendor/laravel/framework/src/Illuminate/Routing/Router.php:805)
  at Illuminate\Routing\Router->Illuminate\Routing\{closure}(object(Request))
     (/var/task/user/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:144)
  at Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(object(Request))
     (/var/task/user/vendor/laravel/framework/src/Illuminate/Routing/Middleware/SubstituteBindings.php:50)
  at Illuminate\Routing\Middleware\SubstituteBindings->handle(object(Request), object(Closure))
     (/var/task/user/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:183)
  at Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(object(Request))
     (/var/task/user/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/VerifyCsrfToken.php:78)
  at Illuminate\Foundation\Http\Middleware\VerifyCsrfToken->handle(object(Request), object(Closure))
     (/var/task/user/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:183)
  at Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(object(Request))
     (/var/task/user/vendor/laravel/framework/src/Illuminate/View/Middleware/ShareErrorsFromSession.php:49)
  at Illuminate\View\Middleware\ShareErrorsFromSession->handle(object(Request), object(Closure))
     (/var/task/user/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:183)
  at Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(object(Request))
     (/var/task/user/vendor/laravel/framework/src/Illuminate/Session/Middleware/StartSession.php:121)
  at Illuminate\Session\Middleware\StartSession->handleStatefulRequest(object(Request), object(Store), object(Closure))
     (/var/task/user/vendor/laravel/framework/src/Illuminate/Session/Middleware/StartSession.php:64)
  at Illuminate\Session\Middleware\StartSession->handle(object(Request), object(Closure))
     (/var/task/user/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:183)
  at Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(object(Request))
     (/var/task/user/vendor/laravel/framework/src/Illuminate/Cookie/Middleware/AddQueuedCookiesToResponse.php:37)
  at Illuminate\Cookie\Middleware\AddQueuedCookiesToResponse->handle(object(Request), object(Closure))
     (/var/task/user/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:183)
  at Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(object(Request))
     (/var/task/user/vendor/laravel/framework/src/Illuminate/Cookie/Middleware/EncryptCookies.php:67)
  at Illuminate\Cookie\Middleware\EncryptCookies->handle(object(Request), object(Closure))
     (/var/task/user/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:183)
  at Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(object(Request))
     (/var/task/user/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:119)
  at Illuminate\Pipeline\Pipeline->then(object(Closure))
     (/var/task/user/vendor/laravel/framework/src/Illuminate/Routing/Router.php:805)
  at Illuminate\Routing\Router->runRouteWithinStack(object(Route), object(Request))
     (/var/task/user/vendor/laravel/framework/src/Illuminate/Routing/Router.php:784)
  at Illuminate\Routing\Router->runRoute(object(Request), object(Route))
     (/var/task/user/vendor/laravel/framework/src/Illuminate/Routing/Router.php:748)
  at Illuminate\Routing\Router->dispatchToRoute(object(Request))
     (/var/task/user/vendor/laravel/framework/src/Illuminate/Routing/Router.php:737)
  at Illuminate\Routing\Router->dispatch(object(Request))
     (/var/task/user/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php:200)
  at Illuminate\Foundation\Http\Kernel->Illuminate\Foundation\Http\{closure}(object(Request))
     (/var/task/user/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:144)
  at Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(object(Request))
     (/var/task/user/vendor/livewire/livewire/src/Features/SupportDisablingBackButtonCache/DisableBackButtonCacheMiddleware.php:19)
  at Livewire\Features\SupportDisablingBackButtonCache\DisableBackButtonCacheMiddleware->handle(object(Request), object(Closure))
     (/var/task/user/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:183)
  at Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(object(Request))
     (/var/task/user/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/TransformsRequest.php:21)
  at Illuminate\Foundation\Http\Middleware\TransformsRequest->handle(object(Request), object(Closure))
     (/var/task/user/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/ConvertEmptyStringsToNull.php:31)
  at Illuminate\Foundation\Http\Middleware\ConvertEmptyStringsToNull->handle(object(Request), object(Closure))
     (/var/task/user/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:183)
  at Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(object(Request))
     (/var/task/user/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/TransformsRequest.php:21)
  at Illuminate\Foundation\Http\Middleware\TransformsRequest->handle(object(Request), object(Closure))
     (/var/task/user/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/TrimStrings.php:40)
  at Illuminate\Foundation\Http\Middleware\TrimStrings->handle(object(Request), object(Closure))
     (/var/task/user/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:183)
  at Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(object(Request))
     (/var/task/user/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/ValidatePostSize.php:27)
  at Illuminate\Foundation\Http\Middleware\ValidatePostSize->handle(object(Request), object(Closure))
     (/var/task/user/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:183)
  at Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(object(Request))
     (/var/task/user/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/PreventRequestsDuringMaintenance.php:99)
  at Illuminate\Foundation\Http\Middleware\PreventRequestsDuringMaintenance->handle(object(Request), object(Closure))
     (/var/task/user/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:183)
  at Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(object(Request))
     (/var/task/user/vendor/laravel/framework/src/Illuminate/Http/Middleware/HandleCors.php:49)
  at Illuminate\Http\Middleware\HandleCors->handle(object(Request), object(Closure))
     (/var/task/user/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:183)
  at Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(object(Request))
     (/var/task/user/vendor/laravel/framework/src/Illuminate/Http/Middleware/TrustProxies.php:39)
  at Illuminate\Http\Middleware\TrustProxies->handle(object(Request), object(Closure))
     (/var/task/user/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:183)
  at Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(object(Request))
     (/var/task/user/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:119)
  at Illuminate\Pipeline\Pipeline->then(object(Closure))
     (/var/task/user/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php:175)
  at Illuminate\Foundation\Http\Kernel->sendRequestThroughRouter(object(Request))
     (/var/task/user/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php:144)
  at Illuminate\Foundation\Http\Kernel->handle(object(Request))
     (/var/task/user/public/index.php:51)
  at require('/var/task/user/public/index.php')
     (/var/task/user/api/index.php:4)

Here is my vercel.json
{
    "version": 2,
    "framework": null,
    "builds": [
        { "src": "/api/index.php", "use"<EMAIL_ADDRESS>}
    ],
    "routes": [
        {
            "src": "/(.*)",
            "dest": "/api/index.php"
        }
    ],
    "env": {
        "APP_ENV": "production",
        "APP_DEBUG": "true",
        "APP_URL": "https://mydomain.com",
        "VERCEL_DEMO_MODE": "true",
        "APP_CONFIG_CACHE": "/tmp/config.php",
        "APP_EVENTS_CACHE": "/tmp/events.php",
        "APP_PACKAGES_CACHE": "/tmp/packages.php",
        "APP_ROUTES_CACHE": "/tmp/routes.php",
        "APP_SERVICES_CACHE": "/tmp/services.php",
        "CACHE_DRIVER": "array",
        "LOG_CHANNEL": "stderr",
        "SESSION_DRIVER": "cookie",
        "VIEW_COMPILED_PATH": "/tmp/views",
        "SSR_TEMP_PATH": "/tmp/ssr",
        "NODE_PATH": "node"
    }
}

Did I missed something?

add this to your composer.json
"scripts": {
        // .... other laravel default scripts
        "vercel": [
          "npm ci && npm run build"
        ]
}


TypeScript multiline union types incorrect syntax coloring

If the vertical bar character is on the next line, the type is not colored properly.
Here's an example from the LSP spec using the Dark+ theme:

Please always share the text of the code along with screenshots


Mounting /var/run instead of /var/run/docker.sock so we can get the n…

…ew socket after a rolling update of the docker daemon
We mounted /var/run/docker.sock to enable agent interaction with the docker-daemon.
This socket will break if docker live restore (https://docs.docker.com/config/containers/live-restore/) is used for updating the daemon. This leaves the agent in a broken state.
Mounting the whole /var/run-dir solves this issue as recreated sockets become visible to the agent for reconnection.
Signed-off-by: Jochen Mader<EMAIL_ADDRESS>
What this PR does / why we need it:
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[ ] DCO signed
[ ] Chart Version bumped
[ ] Variables are documented in the README.md
[ ] title of the PR contains starts with chart name e.g. [stable/chart]

/ok-to-test

/lgtm


Test with Pandas 1.0.*

Pandas recently updated to version 1.0. There are some backwards incompatible changes. We should run tests with both >=0.24 and 1.0.
@mzy2240 - would you have time for this? If not, it's not urgent, and I could do it sometime in the upcoming weeks.

I will take a look next week. We are preparing the short course recently so really busy.

Tested in Python 3.8 with Pandas 1.0.1. Passed all the tests.


fix: Force dependencies on async to v 3.2.3 - main branch

Fixes #4188
Description
Component Governance alerts like this one recommend:
"Upgrade async...to 3.2.2 to fix the vulnerability." V 3.2.3 is now the latest.
Specific Changes

Testing

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage remained the same at 84.485%

Files with Coverage Reduction
New Missed Lines
%

libraries/botbuilder-lg/src/templateExtensions.ts
1
84.48%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
19909

Relevant Lines:
22316

💛  - Coveralls


Time inefficient collapsing of cubes with auxiliary coordinates

I recently realized that collapsing cubes with additional auxiliary coordinates is quite inefficient concidering the time it takes. (https://github.com/ESMValGroup/ESMValCore/issues/195)
Here is a "simple" example that shows the increasing run time:
import iris
import iris.coord_categorisation
from scipy.stats import linregress

import functools
import time

def timer(func):
    # from https://realpython.com/primer-on-python-decorators/#simple-decorators
    @functools.wraps(func)
    def wrapper_timer(*args, **kwargs):
        start_time = time.perf_counter()
        value = func(*args, **kwargs)
        end_time = time.perf_counter()
        run_time = end_time - start_time
        print(f"Finished {func.__name__!r} in {run_time:.4f} secs")
        return value
    return wrapper_timer

filename = iris.sample_data_path('E1_north_america.nc')
air_temp = iris.load_cube(filename, 'air_temperature')

# removing extra coordinates
air_temp_small = air_temp.copy()

air_temp_small.remove_coord("forecast_reference_time")
air_temp_small.remove_coord("forecast_period")

# adding extra coordinates
air_temp_big = air_temp.copy()

iris.coord_categorisation.add_month_number(air_temp_big,"time","month")
iris.coord_categorisation.add_day_of_year(air_temp_big,"time","doy")

@timer
def Mean_Cube(cube, coords):
    # replacement for a more complex function
    return cube.collapsed(coords, iris.analysis.MEAN)

small_time = Mean_Cube(air_temp_small, "time")
# Finished 'Mean_Cube' in 0.0035 secs
print(small_time)
# ...

big_time = Mean_Cube(air_temp_big, "time")
# Finished 'Mean_Cube' in 2.2839 secs
print(big_time)
# ...

The processing time increases by a factor of ~1000!!!
print(big_time.data - small_time.data)
# = all zeroes!

The content itself is the same.
This does not occur for collapsing along dimensions without auxiliary coordinates.
small_lat = Mean_Cube(air_temp_small, "latitude")
# Finished 'Mean_Cube' in 0.0046 secs
print(small_lat)
# ...

big_lat = Mean_Cube(air_temp_big, "latitude")
# Finished 'Mean_Cube' in 0.0052 secs
print(big_lat)
# ...

Is this an expected (and wanted) behaviour? I have the feeling this increase is substantially larger than what is needed.

I just tried your example.  Quite a lot of the slowdown seems to be because of the 'forecast_period' coordinate, which has lazy points.  If you either remove that coordinate or realise the points, you get a significant speed-up.
Without realising the data, I also found that
mean_cube = air_temp_big.collapsed('time', iris.analysis.MEAN)
print(mean_cube.coord('forecast_period').has_lazy_points())

Gives False
So could the slowdown be because the points are being loaded within collapsed?

I think this may be the offending line.  Dask is only being used to create the new array if the coordinate has bounds.  I reorganised those lines at #3302 and I just tried your example again with my branch.  While the "big" cube is still slower to collapse than the "small" cube, the difference is much less severe.

I've added a test at #3364 so that the correct behaviour for lazy points shouldn't get broken again in future.  I will leave it to others to consider whether there are any other efficiency savings to be made here.
Thanks @BenMGeo for raising this and for providing such a clear and easy-to-use example!

Now fixed, as described above


Make 'tool' schema group configurable per-node

This PR updates all the "tool" group parameters to match our desired per-node configuration settings. Sorry for the huge PR, this touches a lot of files! It's mostly mechanical refactor, but some things to highlight:

This change removes if valid('tool', ...) guards in a lot of places. The _search() refactor (##1222) actually removes the need for this in most cases, since get() will now return the default value for a parameter if the supplied wildcards don't exist. The instances modified in this PR were caught because valid() doesn't accept step/index kwargs.
Some new functionality is included, since the 'path', 'version', and 'licenseserver' parameters were not previously set on a step/index basis. I've added a test that exercises this new functionality.
While most of these parameters use the 'optional' pernode configuration, I made 'input', 'output', and 'report' take in the required setting, since these parameters all refer to files in specific step directories (and find_files resolves them accordingly)
Working on this PR revealed the file-hashing logic needs to be fixed (tracked in #1257), since the hashes are stored in a plain list that maps 1-to-1 with the values in a [file] type. This means we don't have a way to store the hashes for per-node files. Fixing this will require changes to the schema structure, so I'm deferring any fixes until we have a chance to discuss.
TCL manifests still only include the value for a parameter associated with the current step/index. This doesn't break anything even with this PR, since the current show implementations don't access 'show_step'/'show_index' in scripts.

@gadfort thanks for the review!

Bumped schema version
Cleaned up the odd tool driver things you mentioned. There's probably a lot more of those sorts of things, and in particular step/index is set in tons of places I don't think it has to be. I figure those issues can be cleaned up in more focused review of each tool driver at some point.
Daily test run queued, good suggestion: https://github.com/siliconcompiler/siliconcompiler/actions/runs/4146378633
Tracking the input/output thing as another task in issue #1257

Alright, got a daily test run that ultimately timed out, but gave me useful failing tests for a couple Python versions https://github.com/siliconcompiler/siliconcompiler/actions/runs/4147175495/jobs/7173735411#step:4:557.
I pushed fixes for those tests that I verified manually.


TypeError exception while importing SVG

Traceback:
Traceback (most recent call last):
File "MeerK40t.py", line 417, in on_click_import
File "MeerK40t.py", line 332, in load_svg
File "LaserProject.py", line 371, in svg_transform
File "svg_parser.py", line 377, in parse_svg_transform
TypeError: post_cat() takes 2 positional arguments but 7 were given

Should be fixed by https://github.com/meerk40t/meerk40t/commit/aa2f4997e148a0879234cc61e899c2e7c13130aa which should be included int 0.1.3 and in the release package. But this does imply I should find a good set of test SVGs and try them to make sure things at least work.


Use documentation autogenerated from the Python code in place of the hard-coded documentation in the Wiki.

If you look at many of the pages on the Wiki, they contain documentation of code:  e.g. https://github.com/ManiacalLabs/BiblioPixel/wiki/Matrix
Unfortunately, we edit the code and the documentation doesn't keep up.  Also, the formatting isn't so good but we have no way to change it en masse.
We should be using Sphinx to generate all the documentation right from the Python files.  We should be - somehow - pushing that documentation to the Wiki, or linking to that documentation in the Wiki.  We should be deleting all specific documentation of methods from the Wiki, to avoid having to change everything in two places, and always linking to the generated docs as the One Source Of Truth.

This has some more information: http://martin.majlis.cz/integrating-github-with-pypi-travis-ci-readthedocs-and-code-climate/
I'm also agreeing that we might want to push to ReadTheDocs.com.


Webaction runs twice within one activation, and reported as failure when it did not actually fail

Environment details:

K8s Deployment using AWS ESK, 1.29

Steps to reproduce the issue:

Have an incoming HTTP POST from AWS IoT (using HTTP as a Action Rule)
Have a webaction (visible on internet), using python:3.9 action runner
Monitor the failures of the web action.

Provide the expected results and outputs:
Expected output
2024-05-02 08:07:27 aa9313bdf52a490b9313bdf52ac90b6b python:3 warm  170ms      success         dataspace/iot_action:0.0.76:

    "logs": [
        "2024-05-02T08:07:27.203249047Z stdout: Message type is None",
        "2024-05-02T08:07:27.203353817Z stdout: Authenticated with deployment test",
        "2024-05-02T08:07:27.203359561Z stdout: Processing IoT message iot/statusResponse",
        "2024-05-02T08:07:27.203362535Z stdout: Message: {\"location\": {\"latitude\": \"x\", \"locationDescription\": \"\", \"longitude\": \"x\"}, \"tenantName\": \"LoadTest1\"}",
        "2024-05-02T08:07:27.203366872Z stdout: Publishing statusResponse to topic example.fct.iot_test_statusresponse.1",
        "2024-05-02T08:07:27.203369844Z stdout: New keys ['\"1454419940501\"']",
        "2024-05-02T08:07:27.203372379Z stdout: Finished processing",
        "2024-05-02T08:07:27.20337515Z  stdout: returning: {\"headers\": {\"Content-Type\": \"application/json\", \"Connection\": \"close\"}, \"statusCode\": 200, \"body\": \"\\\"OK\\\"\"}"
    ],

Provide the actual results and outputs:
    "logs": [
        "2024-05-02T08:03:35.441164892Z stdout: Message type is None",
        "2024-05-02T08:03:35.441233404Z stdout: Authenticated with deployment test",
        "2024-05-02T08:03:35.44123762Z  stdout: Processing IoT message iot/statusResponse",
        "2024-05-02T08:03:35.441241006Z stdout: Message: {\"location\": {\"latitude\": \"X\", \"locationDescription\": \"Engineering Lab\", \"longitude\": \"X\"}, \"tenantName\": \"LoadTest1\"}",
        "2024-05-02T08:03:35.441244653Z stdout: Publishing statusResponse to topic topic example.fct.iot_test_statusresponse.1",
        "2024-05-02T08:03:35.441247605Z stdout: New keys ['\"1454419850988\"']",
        "2024-05-02T08:03:35.441250359Z stdout: Finished processing",
        "2024-05-02T08:03:35.441253345Z stdout: returning: {\"headers\": {\"Content-Type\": \"application/json\", \"Connection\": \"close\"}, \"statusCode\": 200, \"body\": \"\\\"OK\\\"\"}",
        "2024-05-02T08:05:10.601380606Z stdout: Message type is None",
        "2024-05-02T08:05:10.601398036Z stdout: Authenticated with deployment test",
        "2024-05-02T08:05:10.601401152Z stdout: Processing Stratos message iot/status",
        "2024-05-02T08:05:10.601404588Z stdout: Message: {\"commonName\": \"1454419850988\", .......,
        "2024-05-02T08:05:10.6014228Z   stdout: Publishing status to topic example.fct.iot_test_status.1",
        "2024-05-02T08:05:10.601426211Z stdout: New keys ['\"1454419850988\"']",
        "2024-05-02T08:05:10.601428478Z stdout: Finished processing",
        "2024-05-02T08:05:10.601431725Z stdout: returning: {\"headers\": {\"Content-Type\": \"application/json\", \"Connection\": \"close\"}, \"statusCode\": 200, \"body\": \"\\\"OK\\\"\"}",
        "2024-05-02T08:05:10.604225532Z stderr: The action did not initialize or run as expected. Log data might be missing."
    ],

Additional information you deem important:
It appears that the same activation is capturing the output from two runs. And therefore the second (or first) run is assumed to of failed.
I have tried adding  a sleep into the while loop (thinking it was a timeing issue), but still does it·
https://github.com/apache/openwhisk-runtime-python/blob/1389697e3251ef08a930ed95629379551a8d3c9a/core/python3Action/lib/launcher.py#L54

You might see this if the webaction returned a 50x status code - nginx may be automatically retrying the request and hence running the action again. You can confirm this by checking the nginx logs for the action in question.

Thanks for the suggestion,
I will retry it a few times over the next day, but this is what I see on the access log in nginx:
<IP_ADDRESS> - - [02/May/2024:10:31:17 +0000] [#tid_8daa7a35d7e1b39c3114d4c94d99ae12] POST /api/v1/web/dataspace/iot_package/iot_action HTTP/1.1 200 4 - AHC/2.1 <IP_ADDRESS>:8080
<IP_ADDRESS> - - [02/May/2024:10:31:18 +0000] [#tid_63cd895864243ab89c8ed39fec47d83f] POST /api/v1/web/dataspace/iot_package/iot_action HTTP/1.1 200 4 - AHC/2.1 <IP_ADDRESS>:8080

From reading this it looks like both are returning 200.
I am wondering if AWS do something strange with there HTTP client and send multiple requests over the same connection and dont wait for a reply (only a theory)
I will keep looking at the logs until somthing else comes up :)


Unusual daysShort format for germanlocalization / Mentioned as fixed in #2496

For some reason the three letter version of daysShort is back in version 1.9.0

The fix in #2496 was merged after the release of version 1.9.0.