text:
nuke is not a recognized option of aws-nuke

👋 First off, thanks for building this project. The mode of delivery is quite clever and perfect for a project I'm working on. As I've tested this out, I've run across an error with this section of the CF stack template:
- |
if [ "$AWS_NukeDryRun" = "true" ]; then
    for file in $(ls nuke_config_$NukeTargetRegion*) ; do aws-nuke -c $file --force --profile nuke 2>&1 |tee -a aws-nuke.log; done
elif [ "$AWS_NukeDryRun" = "false" ]; then
    for file in $(ls nuke_config_$NukeTargetRegion*) ; do aws-nuke -c $file --force --no-dry-run --profile nuke 2>&1 |tee -a aws-nuke.log; done
else
    echo "Couldn't determine Dryrun flag...exiting"
exit 1
fi

This errors out saying that nuke is not a recognized option of aws-nuke. In searching for other reference material, I don't see that option being used or even part of aws-nuke, and removing it gets rid of the error and leads to successful aws-nuke execution. Am I missing something here?

This is not an app issue !

authors: awsree christophelimpalair


text:
updating the variable to match the module for cluster_name

What does this PR do?
Provides a small fix for a change in cluster_name which has changed in the downstream module
Motivation
I tried to use it and it failed with the following message
│ Error: Unsupported argument
│
│   on main.tf line 148, in module "aws-eks-accelerator-for-terraform":
│  148:   kubernetes_version = local.kubernetes_version
│
│ An argument named "kubernetes_version" is not expected here.
More

[x ] Yes, I have tested the PR using my local account setup  (Provide any test evidence report under Additional Notes)

[ ] Yes, I have added a new example under examples to support my PR

[ ] Yes, I have updated the docs for this feature

[ ] Yes, I have linked to an issue or feature request (applicable to PRs that solves a bug or a feature request)

For Moderators

[ ] E2E Test successfully complete before merge?

Additional Notes

@vara-bonthu
Do we have to worry about this? https://github.com/aws-samples/crossplane-aws-blueprints/blob/95008c6dc85d67da207b22a650beb53370d841d0/bootstrap/terraform/variables.tf#L27
I'm not too familiar with Terraform so I can't tell for sure, but it looks like this variable name should be updated as well?

Yes that need changing as well to cluster_version.
Tomorrow our upstream repo is moving to new org so I will update this bootstrap as well with new source and version etc

source: gharchive/pull-request

authors: imosquera nabuskey vara-bonthu

repo: aws-samples/crossplane-aws-blueprints

license_type: permissive

license_source: github-api


text:
feat: Argo CD lab with App of Apps pattern example

What this PR does / why we need it:
ArgoCD lab should show how Argo CD App of Apps pattern could be implemented to deliver complete set of components from Sample App to specific environment (dev) with specific customisations for that environment.
Which issue(s) this PR fixes:
Fixes #403
Quality checks

[x] My content adheres to the style guidelines
[x] I ran make test or make e2e-test and it was successful

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@candonov @tsahiduek @allamand I believe this PR is now ready to be review

@ybezsonov It look like this branch has conflicts, could you please resolve them?

authors: candonov csantanapr ybezsonov


text:
update: eks-workshop-ide-cfn.yaml managed role too permissive

The admin managed policy is blocked by most organizations. I believe the AWSCloud9Administrator will allow the lab to work the same without conflicting with org SCPs
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes # None
Quality checks

[x ] My content adheres to the style guidelines
[x ] I ran make test module="<module>" it was successful (see https://github.com/aws-samples/eks-workshop-v2/blob/main/docs/automated_tests.md)

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Hey @travis-jorge thanks for raising this PR. Agreed that the role is too permissive, the issue is that mapping the required permissions is a bit more complicated. The IAM permissions will need to account for all API calls to:

Run Cloud9
Complete all content commands (modifying EKS clusters, managing IAM roles and so on)
Running the Terraform for all modules (some examples include creating EFS file systems, AMP workspaces, CloudWatch log groups, CodeCommit repositories, IAM roles and policies and more)

Understanding the required permissions would likely need every lab to be completed while running an IAM profiling tool to record all API calls.

Closing due to no activity

authors: niallthomson travis-jorge


text:
画像生成改善案

[ ] チャットの自動スクロール
[ ] SD activate の must 化 or configurable or SD モデルの有効性を見てメニュー表示の自動切り替え

クリア時に画像1枚目を選択する
デモから遷移 -> 画像生成 -> 違う画面へ遷移 -> 画像生成画面に戻ってくる -> 画像生成処理が勝手に動く
初期画像を適当に設定 -> 初期画像を再度開いて背景色を変えようとして変わらない（画像の背景色が透過されていないため）

別画面（チャット履歴など）に遷移してから戻ってくると履歴が消えて新規チャットになる。クリアで初期化はされるので別画面が見たくなって（過去の履歴の確認など）戻ってきた際はリセットされずに履歴が残っていて続きから生成できると嬉しい。

すべて子 issue として作成してもらったので close

source: gharchive/issue

authors: maekawataiki tbrand wadabee

repo: aws-samples/generative-ai-use-cases-jp


text:
Add rust snippet for SQSBatchResponse

Add a Rust snippet for SQSBatchResponse, I have tried to keep the example as similar to the others as I can, except in Rust it is commonplace to use Result types rather than try catch.
Can I add a github profile? rather than linkedin/twitter for author credits?
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Thanks @klaatu01

repo: aws-samples/serverless-snippets


text:
feat: get cost report script

Issue #, if available:
Description of changes:
Adding a script to grab the cost report for a given hourly time window from an AWS account.
Testing:
Ran script to grab data from my personal dev account:
bash-3.2$ python3 bin/get_cost_report.py 2023-10-20T09:00:00Z 2023-10-20T11:00:00Z
╒════╤════════════════════════════════════════╤══════════════╤══════════════════════╕
│    │ Service                                │         Cost │ TimePeriod           │
╞════╪════════════════════════════════════════╪══════════════╪══════════════════════╡
│  0 │ AWS CloudTrail                         │  0           │ 2023-10-20T09:00:00Z │
├────┼────────────────────────────────────────┼──────────────┼──────────────────────┤
│  1 │ AWS Key Management Service             │  0.350811    │ 2023-10-20T09:00:00Z │
├────┼────────────────────────────────────────┼──────────────┼──────────────────────┤
│  2 │ Amazon DynamoDB                        │  0.0592555   │ 2023-10-20T09:00:00Z │
├────┼────────────────────────────────────────┼──────────────┼──────────────────────┤
│  3 │ Amazon EC2 Container Registry (ECR)    │  0.0229492   │ 2023-10-20T09:00:00Z │
├────┼────────────────────────────────────────┼──────────────┼──────────────────────┤
│  4 │ EC2 - Other                            │  0.136174    │ 2023-10-20T09:00:00Z │
├────┼────────────────────────────────────────┼──────────────┼──────────────────────┤
│  5 │ Amazon Elastic Compute Cloud - Compute │  0           │ 2023-10-20T09:00:00Z │
├────┼────────────────────────────────────────┼──────────────┼──────────────────────┤
│  6 │ Amazon Elastic Container Service       │  4.6608      │ 2023-10-20T09:00:00Z │
├────┼────────────────────────────────────────┼──────────────┼──────────────────────┤
│  7 │ Amazon Elastic File System             │  4.6e-09     │ 2023-10-20T09:00:00Z │
├────┼────────────────────────────────────────┼──────────────┼──────────────────────┤
│  8 │ Amazon GuardDuty                       │  0.00788816  │ 2023-10-20T09:00:00Z │
├────┼────────────────────────────────────────┼──────────────┼──────────────────────┤
│  9 │ Amazon SageMaker                       │ 17.5805      │ 2023-10-20T09:00:00Z │
├────┼────────────────────────────────────────┼──────────────┼──────────────────────┤
│ 10 │ Amazon Simple Notification Service     │  0           │ 2023-10-20T09:00:00Z │
├────┼────────────────────────────────────────┼──────────────┼──────────────────────┤
│ 11 │ Amazon Simple Queue Service            │  0.0042724   │ 2023-10-20T09:00:00Z │
├────┼────────────────────────────────────────┼──────────────┼──────────────────────┤
│ 12 │ Amazon Simple Storage Service          │  0.00577143  │ 2023-10-20T09:00:00Z │
├────┼────────────────────────────────────────┼──────────────┼──────────────────────┤
│ 13 │ Amazon Virtual Private Cloud           │  1.55508     │ 2023-10-20T09:00:00Z │
├────┼────────────────────────────────────────┼──────────────┼──────────────────────┤
│ 14 │ AmazonCloudWatch                       │  0           │ 2023-10-20T09:00:00Z │
├────┼────────────────────────────────────────┼──────────────┼──────────────────────┤
│ 15 │ AWS CloudTrail                         │  0           │ 2023-10-20T10:00:00Z │
├────┼────────────────────────────────────────┼──────────────┼──────────────────────┤
│ 16 │ AWS Key Management Service             │  0.351349    │ 2023-10-20T10:00:00Z │
├────┼────────────────────────────────────────┼──────────────┼──────────────────────┤
│ 17 │ Amazon DynamoDB                        │  0.0598815   │ 2023-10-20T10:00:00Z │
├────┼────────────────────────────────────────┼──────────────┼──────────────────────┤
│ 18 │ Amazon EC2 Container Registry (ECR)    │  0.0229614   │ 2023-10-20T10:00:00Z │
├────┼────────────────────────────────────────┼──────────────┼──────────────────────┤
│ 19 │ EC2 - Other                            │  0.136201    │ 2023-10-20T10:00:00Z │
├────┼────────────────────────────────────────┼──────────────┼──────────────────────┤
│ 20 │ Amazon Elastic Compute Cloud - Compute │  0           │ 2023-10-20T10:00:00Z │
├────┼────────────────────────────────────────┼──────────────┼──────────────────────┤
│ 21 │ Amazon Elastic Container Service       │  4.6608      │ 2023-10-20T10:00:00Z │
├────┼────────────────────────────────────────┼──────────────┼──────────────────────┤
│ 22 │ Amazon Elastic File System             │  4.6e-09     │ 2023-10-20T10:00:00Z │
├────┼────────────────────────────────────────┼──────────────┼──────────────────────┤
│ 23 │ Amazon GuardDuty                       │  0.0055408   │ 2023-10-20T10:00:00Z │
├────┼────────────────────────────────────────┼──────────────┼──────────────────────┤
│ 24 │ Amazon SageMaker                       │ 17.647       │ 2023-10-20T10:00:00Z │
├────┼────────────────────────────────────────┼──────────────┼──────────────────────┤
│ 25 │ Amazon Simple Notification Service     │  0           │ 2023-10-20T10:00:00Z │
├────┼────────────────────────────────────────┼──────────────┼──────────────────────┤
│ 26 │ Amazon Simple Queue Service            │  0.00429     │ 2023-10-20T10:00:00Z │
├────┼────────────────────────────────────────┼──────────────┼──────────────────────┤
│ 27 │ Amazon Simple Storage Service          │  0.00569802  │ 2023-10-20T10:00:00Z │
├────┼────────────────────────────────────────┼──────────────┼──────────────────────┤
│ 28 │ Amazon Virtual Private Cloud           │  1.6129      │ 2023-10-20T10:00:00Z │
├────┼────────────────────────────────────────┼──────────────┼──────────────────────┤
│ 29 │ AmazonCloudWatch                       │  0           │ 2023-10-20T10:00:00Z │
├────┼────────────────────────────────────────┼──────────────┼──────────────────────┤
│ 30 │ AWS CloudTrail                         │  0           │ 2023-10-20T11:00:00Z │
├────┼────────────────────────────────────────┼──────────────┼──────────────────────┤
│ 31 │ AWS Key Management Service             │  0.336489    │ 2023-10-20T11:00:00Z │
├────┼────────────────────────────────────────┼──────────────┼──────────────────────┤
│ 32 │ Amazon DynamoDB                        │  0.00202846  │ 2023-10-20T11:00:00Z │
├────┼────────────────────────────────────────┼──────────────┼──────────────────────┤
│ 33 │ Amazon EC2 Container Registry (ECR)    │  0.0229614   │ 2023-10-20T11:00:00Z │
├────┼────────────────────────────────────────┼──────────────┼──────────────────────┤
│ 34 │ EC2 - Other                            │  0.135965    │ 2023-10-20T11:00:00Z │
├────┼────────────────────────────────────────┼──────────────┼──────────────────────┤
│ 35 │ Amazon Elastic Compute Cloud - Compute │  0           │ 2023-10-20T11:00:00Z │
├────┼────────────────────────────────────────┼──────────────┼──────────────────────┤
│ 36 │ Amazon Elastic Container Service       │  4.6608      │ 2023-10-20T11:00:00Z │
├────┼────────────────────────────────────────┼──────────────┼──────────────────────┤
│ 37 │ Amazon Elastic File System             │  4.6e-09     │ 2023-10-20T11:00:00Z │
├────┼────────────────────────────────────────┼──────────────┼──────────────────────┤
│ 38 │ Amazon GuardDuty                       │  0.0029696   │ 2023-10-20T11:00:00Z │
├────┼────────────────────────────────────────┼──────────────┼──────────────────────┤
│ 39 │ Amazon SageMaker                       │ 15.3753      │ 2023-10-20T11:00:00Z │
├────┼────────────────────────────────────────┼──────────────┼──────────────────────┤
│ 40 │ Amazon Simple Notification Service     │  0           │ 2023-10-20T11:00:00Z │
├────┼────────────────────────────────────────┼──────────────┼──────────────────────┤
│ 41 │ Amazon Simple Queue Service            │  0.002932    │ 2023-10-20T11:00:00Z │
├────┼────────────────────────────────────────┼──────────────┼──────────────────────┤
│ 42 │ Amazon Simple Storage Service          │  0.000466562 │ 2023-10-20T11:00:00Z │
├────┼────────────────────────────────────────┼──────────────┼──────────────────────┤
│ 43 │ Amazon Virtual Private Cloud           │  0.172136    │ 2023-10-20T11:00:00Z │
├────┼────────────────────────────────────────┼──────────────┼──────────────────────┤
│ 44 │ AmazonCloudWatch                       │  0           │ 2023-10-20T11:00:00Z │
├────┼────────────────────────────────────────┼──────────────┼──────────────────────┤
│ 45 │ Total                                  │ 69.6022      │ Total                │
╘════╧════════════════════════════════════════╧══════════════╧══════════════════════╛

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Should add a condition if the time provided is greater than 24 hours. Because fetching the cost within 24 hours will report no data.

The amount of time for the dashboard to populate is indeterminate - if it is not available it will return 0.0 cost.


text:
feature: Group consecutive operations in batch strategy

Issue #, if available:
Description of changes:
Testing done:
Merge Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your pull request.
General

[x] I have read the CONTRIBUTING doc
[x] I used the commit message format described in CONTRIBUTING
[x] I have updated any necessary documentation, including READMEs and API docs (if appropriate)

Tests

[x] I have added tests that prove my fix is effective or that my feature works (if appropriate)
[x] I have checked that my tests are not configured for a specific region or account (if appropriate)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Closing PR since there has been no activity on this for a while. Please feel free to reopen if you wish to continue working on this. Thanks!


text:
App delete UX improvement

ecs-preview app delete requires users to input the application name as a parameter, which is not user friendly because as a user I need to do app ls or app show first to find out the app name if I don't remember. It would be nice to be able to get the current workspace application name automatically. The whole experience would be like:
$ ecs-preview app delete
? Are you sure you want to delete "my-app" from all environment?
$ y

Deleting...

Deleted

related to #523


text:
Heap and Stack metrics for ESP32. Plus naming changes.

Added stack and heap metrics logging to ESP32 demos. Abstracted data type of stack size as on ESP32 it is bytes, but FreeRTOS implementation is usually stack words. Changed variable prefixes from demo to democonfig as per convention.

Description

Checklist:

[ ] I have tested my changes. No regression in existing tests.
[ ] My code is Linted.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/bot run checks

/bot run checks

repo: aws/amazon-freertos

license: MIT


text:
pods will requeue for reconcile if nodes are not managed and requested eni

Issue #, if available:
Description of changes:
Previously, pod events were ignored for pods running on unmanaged nodes. However, since unmanaged nodes can be converted to managed nodes, we need to handle these cases differently. If a pod has requested the ENI resource, indicating a need for a trunk interface, we will requeue the pod so that it receives the necessary trunk interface when the node is managed by vpc-cni
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Thanks for implementing this

LGTM


text:
For serviceexport, targets are built for all ports of instead of just port specified in the serviceimport of backendRefs

This is similar to #241 . The same issue happens for serviceexport too.

workaround:  create a separate K8S service which only contains the ports need to used and create a separate service export object to reference this K8S service

Thanks for the feature request! We will be adding this to our intake for prioritization, but we also try to take in popular feature requests based on :+1::skin-tone-4: from the community.

authors: jansvive liwenwu-amazon


text:
AWS Lambda Serverless - Antiforgery token validation failed. The antiforgery token could not be decrypted.

We're trying to do this with AWS Lambda Serverless and keep running into the error
Microsoft.AspNetCore.Mvc.ViewFeatures.Internal.AutoValidateAntiforgeryTokenAuthorizationFilter: Antiforgery token validation failed. The antiforgery token could not be decrypted.
I suspect it is because the Post is running on a different server?
We've tried the  work-around in web.config and the IgnoreAntiforgeryTokenAttribute work-around.
Anyone else gotten this working?
Any thoughts?

The Antiforgery framework in ASP.NET Core uses its underlying Data Protection framework that generates encryption keys as needed. By default the keys are persisted in memory or the file system. If you use our AWS Systems Manager ASP.NET Core Data Protection Provider package it will use AWS Systems Manager to keep the encryption key in sync for all of the compute environment running the ASP.NET Core application.

You rock (as usual)!


text:
Setup Failed! -5 PubSub example

I recently was able to get my Raspberry Pi to connect to AWS, but I'm new and having trouble connecting my Arduino YUN. I've made sure to follow the instructions for the SDK and that WiFi works but, whenever I run the example PubSub code my serial monitor shows the following output:
AWS IoT SDK Version(dev) 2.2.0-

Setup failed!
-5

I'm unsure as how to fix this issue. My closest understanding is that this is related to SERIAL1_COMMUNICATION_ERROR. I've run the YunSerialTerminal sketch a few times to confirm that the Arduino Serial Monitor can see data from the OpenWRT side.

Hi @tahamir ,
Thank you very much for using AWS IoT Arduino Yun SDK.
The issue you are seeing here is caused by ATmega32u4 not able to receive expected response from AR9331 via Serial1 communication. To help us investigate into the issue, can you provide the following information?
a. Do a ssh into the Linux side of your Yun board and try the following command to get the baud rate configuration:
cat /proc/cmdline
You should be able to see similar output like this (I am testing on my Yun with Linino installed, which has a baud rate configuration of 115.2k):
board=linino-one console=ttyATH0,115200 ...

Yun SDK supports baud rate 250K and 115.2K. You can check out the baud rate on your Linux.
b. Add the following line after this line:
Serial.println(rw_buf);

Check the serial monitor output when you are experiencing the issue.
Thanks,
Liusu

Hi @liuszeng
I sshed into my Yun and applied the command. I got the following output:
root@arduino:~# cat /proc/cmdline
 board=linino-yun console=ttyATH0,250000 mtdparts=spi0.0:256k(u-boot)ro,64k(u-boot-env),14656k(rootfs),1280k(kernel),64k(nvram),64k(art),15936k@0x50000(firmware) rootfstype=squashfs,jffs2 noinitrd mem=64M rootfstype=squashfs,jffs2 noinitrd
root@arduino:~#

So I can confirm the Yun should be running at the right baud rate for AWS.
I also added the Serial.println(rw_buf); line and on my Serial Monitor I got the following output:
AWS IoT SDK Version(dev) 2.2.0-

t@arduino:~/AWS-IoT-Python-Runtime/runtime# 1
/bin/ash: /root: Permission denied
/bin/ash: 1: not found
/bin/ash: /root: Permission denied
/bin/ash: 1: not found
/bin/ash: /root: Permission denied
/bin/ash: 1: not found
/bin/ash: /root: Permission denied
Linux
/

I T

G T

C T

S T

P T

Z T

Y F: No messages.
loop 0 done

P T

Z T

Y 0 0 new message 0
CALLBACK:
new message 0

Y F: No messages.
loop 1 done

Hi @tahamir ,
From the baud rate we can see that your board is configured to have a baud rate of 250K for (console) serial1 communication, which is supported by the SDK. From the provided logs, it seems that you are getting the SDK PubSub sample working, as it is printing out the message published by itself:
...
CALLBACK:
new message 0
...

Did you see  any other issues or error code printed out in your IDE serial monitor?
Thanks,
Liusu

Hi @liuszeng
I took another look at my setup and noticed that the time it worked I was running the code while connected to the internet through ethernet. But the time it didn't work I was connecting through the YUN's onboard WiFi. I reran the code while including the Serial.println(rw_buf); command. I get the following output on my Serial Monitor:
AWS IoT SDK Version(dev) 2.2.0-

Setup failed!
-5

It looks like before any data is put in 'rw_buf' the code fails to run. Does this SDK support using the YUN's onboard WiFi chip?

Hi @tahamir ,
Thank you very much for providing the information.
Can you try the following things?

Verify that your board has outbound internet connectivity when it is on WiFi. You can do this by ssh into the Linux and do a ping.
Reconfigure the WiFi connection and restart (power cycle).

One thing you would need to make sure is to wait until the board it fully set up to run the sample after you reconfigured WiFi and restart the board. It usually takes no more than 90 seconds. During set up, Yun board will spit some boot-up info to stdout (Serial1) that could break the SDK protocol.
Thanks,
Liusu

Hi @tahamir ,
We have not heard from you for a while. We are closing the issue for now. Please feel free to reopen it or start another thread if you have any more questions.
Thanks,
Liusu

Hi @liuszeng ,
I am consistently getting the Setup failed! -5 error.
Here is the output of cat /proc/cmdline on my board:
 board=linino-yun console=ttyATH0,250000 mtdparts=spi0.0:256k(u-boot)ro,64k(u-boot-env),14656k(rootfs),1280k(kernel),64k(nvram),64k(art),15936k@0x50000(firmware) rootfstype=squashfs,jffs2 noinitrd mem=64M rootfstype=squashfs,jffs2 noinitrd

The first 3 lines of my program are:
  Bridge.begin();
  Serial.begin(9600);
  while (!Serial);

I uncommented the line above but get only blank output.
Any help would be much appreciated.
Thanks!
Matthew

authors: liuszeng matthewcarroll tahamir

repo: aws/aws-iot-device-sdk-arduino-yun

license_source: bigquery


text:
Support for event based device reports from IoT SDK

Currently the device reporting to the shadow is time-based. For e.g, the device SDK would 'sync' with the shadow based on a time-interval set using setReportInterval(reportInterval).
However, there may be cases where such time-interval based syncing is not required.
Its possible to turn periodic syncing off by setting reportInterval = 0.
But by doing so, one has to then first manually build the JSON message (including the other headers like version, state, reported ... ) & later may be use --
public void update(String jsonState, long timeout) to update the shadow.
private void sendDeviceReport(long reportVersion, String jsonState) method already does the functionality of building the JSON message & updating the shadow.
It would be beneficial if a similar method is made (public) & is made available to use for event-based reporting.

Hi @chandramoulikv ,
Thanks for your interest in IoT Java SDK. You are correct! The current IoT Java SDK does not have event based reporting. Like you said, the IoT Java sdk exposes the lower implementation of shadow operation which could allow user to implement event based reporting.
We will take your comments as a new feature request and will keep watching for this in the future. If more use cases reported, we will definitely incorporate this feature in the future release.
Also, please feel free to let us know if you have more usage scenario and any other thoughts on IoT SDKs.
Thanks,
Fengyi

Thanks for your interest in AWS IoT Device SDK in Java. We are actively working on SDK development and please let us know if you have more questions and comments. Also, please open another thread if you still have questions.

authors: chandramoulikv fengsongAWS

repo: aws/aws-iot-device-sdk-java


text:
Please apply security updates to public.ecr.aws/lambda/dotnet:6

Hi there,
We are using public.ecr.aws/lambda/dotnet:6 and pushing our images to an ECR that we scan for vulnerabilities using Snyk.  A number of "High" issues are being raised that appear to have been addressed in Amazon security updates, yet there is no sign of a new release of lambda/dotnet:6 - can you rev the image please?
https://security.snyk.io/vuln/SNYK-AMZN2-GLIBC-6745196
https://security.snyk.io/vuln/SNYK-AMZN2-GLIBCALLLANGPACKS-6745289
https://security.snyk.io/vuln/SNYK-AMZN2-GLIBCCOMMON-6745132
https://security.snyk.io/vuln/SNYK-AMZN2-GLIBCMINIMALLANGPACK-6745170
https://security.snyk.io/vuln/SNYK-AMZN2-LIBCRYPT-6745245
https://security.snyk.io/vuln/SNYK-AMZN2-GLIB2-6663608
https://security.snyk.io/vuln/SNYK-AMZN2-LIBNGHTTP2-6745071
Sincerely
Pete

.NET 6 has reached EOL status, and the Lambda team has already marked this runtime as EOL.
I would recommend resolving this as wontfix. In the interim, anybody relying on .NET 6, I would not hold my breath if I were you.

authors: pmcevoy skyzyx

repo: aws/aws-lambda-base-images


text:
Build latest image with conformance tests

Issue #, if available:
Description of changes:
This builds the image with e2e conformance tests and uses helm to install the latest NP image before executing the cyclonus suite
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/hold

repo: aws/aws-network-policy-agent


text:
Access points support in EFS

Hello,
I would like to replace slow EBS storage with EFS filesystem for hundreds of nodes pcluster. Do you support EFS Access points in 2.10.1? I have existing EFS filesystem and would like to create multiple access points (/home, /shared, /app etc) and mount shared on master/compute nodes. Do you plan to have a native support for EFS's POSIX user/permission?
Thanks

Hi Andrei,
unfortunately at the moment ParallelCluster does not offer native support for EFS Access Points. I'm going to mark this as a feature request so that we take this into account when extending EFS functionalities in ParallelCluster.
Until then you could use a custom post-install script to mount an existing EFS with Access Points enabled.
Francesco

Hello Francesco,
Thank you for opening feature request.

ability to include existing access point IDs (fsap-xxx) in the template to mount multiple access points.
ability to create access EFS and access points and create directory permissions/ownership

[efs efscustom]
efs_fs_id = fs-xxxx
fsap_id1 = fsap-xxxx
shared_dir = /home
fsap_id2 = fsap-xxxx
shared_dir = /app

I created custom AMI (2.10.1) to include /home and /shared EFS access points in /etc/fstab. My pcluster create is failing due to nfs_export failure. (cfn-init.log below)
fs-xxxx /home efs _netdev,tls,accesspoint=fsap-0xxxx 0 0
fs-xxxx /shared efs _netdev,tls,accesspoint=fsap-0xxx 0 0
How do I disable creation of EBS volume and NFS exports on master node? I will have EFS access points mounted across master and all compute nodes.
On master instance I see that /home access point but /shared created from EBS volume
/dev/xvdb        20G   45M   19G   1% /shared
127.0.0.1:/     8.0E     0  8.0E   0% /home
/var/log/cfn-init.log
Error executing action `create` on resource 'nfs_export[/home]'
================================================================================

Mixlib::ShellOut::ShellCommandFailed
------------------------------------
execute[exportfs] (/etc/chef/local-mode-cache/cache/cookbooks/nfs/providers/export.rb line 43) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '1'
---- Begin output of exportfs -ar ----
STDOUT:
STDERR: exportfs: /etc/exports [1]: Neither 'subtree_check' or 'no_subtree_check' specified for export "172.31.0.0/16:/shared".
  Assuming default behaviour ('no_subtree_check').
  NOTE: this default has changed since nfs-utils version 1.0.x

exportfs: /etc/exports [2]: Neither 'subtree_check' or 'no_subtree_check' specified for export "172.31.0.0/16:/home".
  Assuming default behaviour ('no_subtree_check').
  NOTE: this default has changed since nfs-utils version 1.0.x

exportfs: /home requires fsid= for NFS export
---- End output of exportfs -ar ----
Ran exportfs -ar returned 1

Cookbook Trace:
---------------
/etc/chef/local-mode-cache/cache/cookbooks/nfs/providers/export.rb:73:in `block in class_from_file'

Resource Declaration:
---------------------
# In /etc/chef/local-mode-cache/cache/cookbooks/aws-parallelcluster/recipes/head_node_base_config.rb

130: nfs_export "/home" do
131:   network node['cfncluster']['ec2-metadata']['vpc-ipv4-cidr-blocks']
132:   writeable true
133:   options ['no_root_squash']
134: end
135:

Sorry for the very late reply.
At the moment it is not possible to disable the shared EBS and to mount an EFS filesystem on top of the /home directory cause this would break ParallelCluster. Such options will be available as part of the next major version (3.0.0) of the product.

Hi, will 3.0.0 have the option to use LustreFS instead of EFS to mount the home?

it is very likely it will

Hi, not sure if this here the right place to ask, but I have the following situation:
I started a cluster using pcluster and I have my data on an EFS volume which I have mounted on the EBM volume. However, when I sbatch jobs the scripts don't seem to be able to access the EFS volume. Is there something else I need to do @demartinofra ?
Thank you a lot

I ended up starting a new pcluster with the efs already mounted using the config file

I would be interested in support for  EFS access points natively.

I have created an internal feature request and we will consider this soon

This feature has been included in ParallelCluster 3.11.0.
See documentation: https://docs.aws.amazon.com/parallelcluster/latest/ug/SharedStorage-v3.html#yaml-SharedStorage-EfsSettings-AccessPointId

authors: OleguerCanal andrei-xdlab demartinofra elgalu francisreyes-tfs gmarciani hanwen-pcluste

repo: aws/aws-parallelcluster


text:
Include version number in SONAME of .so files

To make version management easier in linux, it would be good to set the SONAME for the library. At present there is no version included in .so files:
# objdump -p /usr/lib64/libaws-cpp-sdk-core.so | grep SONAME
  SONAME               libaws-cpp-sdk-core.so

This can be achieved via cmake’s SOVERSION property:
set_property(TARGET bar PROPERTY SOVERSION XXXXX)
The SOVERSION ought to be updated when a binary incompatible change to the library occurs, commonly done in-step with updating the major version of the library:
http://pusling.com/blog/?p=352

That's a fair ask, we'll get that queued up. Thank you

repo: aws/aws-sdk-cpp


text:
Forward trace context to AWS Batch job

Hi,
In my application I have a step where an API call eventually submits a job to Batch. The application performing the task will then call other services and consume other AWS services.
What's the best course of action for the calling application to forward the trace context to the application being used by Batch to perform the job?
I guess I can pass the trace-id as a parameter to the application, but is there a way to explicitly set up the recorder to append segments to that trace?

Hi @Kralizek,
Does the API call an Asp.Net(Core) application? If so, you can follow the implementations as usual and X-Ray's Asp.Net handler will automatically fetch and parse the upstream trace id for you. If not, you may have to manually parse the trace id and pass it to the segment that you create for this application.

authors: Kralizek lupengamzn

repo: aws/aws-xray-sdk-dotnet


text:
Bump BR release version

Issue #, if available:
Description of changes:
Bumping BR version to point to latest release https://github.com/bottlerocket-os/bottlerocket/releases/tag/v1.10.1
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/cherrypick release-0.12

/lgtm
/approve

authors: abhay-krishna mitalipaygude

repo: aws/eks-anywhere-build-tooling


text:
Add containerd.service to containerd tarball

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve

/lgtm

authors: abhay-krishna jaxesn


text:
Bump buildkit rootless image tag to v0.10.1 in Prowjobs

Allgning buildkit tag with the version on the builder base image.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve

repo: aws/eks-anywhere-prow-jobs


text:
Run make release-manifest to generate fluxconfig CRD

Issue #, if available:
Description of changes:
Testing (if applicable):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

what happened to other presubmits?

what happened to other presubmits?

Never mind, my bad, I thought we were running those on all changes (.*). But I think we should run atleast the e2e one on config folder changes because it could catch unmarshalling issues when the eksa-components.yaml manifest is applied.

/lgtm
/approve

repo: aws/eks-anywhere


text:
Update brew to point to latest version

Issue #, if available:
Description of changes:
Testing (if applicable):
Documentation added/planned (if applicable):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm
/approve

/cherrypick release-0.18


text:
feat(jsii): switch to disable reserved words warnings

By default, jsii issues a warning when it encounters a symbol that uses a word that is reserved in one of the supported languages. Practically this creates a tremendous amount of noise for large existing projects.
#1073 proposes to add support for a warning exclusion file, which is probably a better long term solution, but in the meantime, this switch allows opting-out of reserved words warnings in order to save the planet.
Tested by adding --disable-reserved-words-warnings to jsii-calc (which uses many reserved words already).

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

AWS CodeBuild CI Report

Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

When would such a warning actually in an issue?

@nija-at wrote:

When would such a warning actually create an issue, and how would we know?

Since we have thousands of these warnings right now in the CDK (and jsii), it teaches developers to ignore warnings. We should always operate in "treat warnings as errors" mode.

When would such a warning actually create an issue, and how would we know?

Since we have thousands of these warnings right now in the CDK (and jsii), it teaches developers to ignore warnings. We should always operate in "treat warnings as errors" mode.

Clarifying the intention behind my question - If there are hundreds and there are no problems, is this a legit warning? When would such a warning actually bite us or the customer?

@nija-at  - the warning is here to prevent adding more identifies that will be awkward to non-TS users. We can usually work around those issues in code generation, but this will often be at the expense of ergonomics... For example, if you call something namespace, you'll force C# users to consistently type @namespace instead...

Thanks @RomainMuller - makes sense.
This sounds like bad customer experience we should prevent for new APIs and API parameters. We should add the feature to exclude existing 'warnings' and change their behaviour to be an error (that fails the build). I would even say that this is time critical, to raise our bar on customer experience.
Silencing these warnings for all CDK(v1) is only going to delay this work and allow more of these to-be-avoided identifiers to slip through, isn't it?

AWS CodeBuild CI Report

Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

authors: RomainMuller aws-cdk-automation eladb nija-at

repo: aws/jsii


text:
fix(python): duplicated kwargs when field is multi-inherited

When a struct field is inherited from more than one parent (this could
be twice from the same type - in the case of a diamond shape; or from
two distinct parents that declare the same field), the lifted keyword
arguments in python would be duplicated for this field.
This is because the method that performs the keyword argument lifting
did not perform name-based de-duplication, and operates directly on the
"raw" assembly (whereby it must traverse the inheritance tree itself,
as opposed to the Go generator which uses jsii-reflect and has the
field collection done by that library).
Added the necessary de-duplication logic and confirmed the produced code
now looks correct using the exact same test harness as I had introduced
in #2650.
Fixes #2653

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@mergifyio refresh


text:
[DRAFT] fix: Create Generic Pod Filtering in Utils and Collapse Disruption Filtering

Fixes #N/A
Description
How was this change tested?
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Pull Request Test Coverage Report for Build 6882541648

132 of 145 (91.03%)  changed or added relevant lines in 17 files are covered.
19 unchanged lines in 5 files lost coverage.
Overall coverage increased (+0.07%) to 80.083%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/controllers/disruption/types.go
23
26
88.46%

pkg/controllers/state/statenode.go
11
15
73.33%

pkg/utils/node/node.go
31
37
83.78%

Files with Coverage Reduction
New Missed Lines
%

pkg/controllers/disruption/drift.go
1
84.21%

pkg/controllers/disruption/expiration.go
1
90.74%

pkg/controllers/disruption/helpers.go
4
90.21%

pkg/controllers/disruption/pdblimits.go
6
88.24%

pkg/controllers/state/statenode.go
7
83.9%

Totals

Change from base Build 6880524052:
0.07%

Covered Lines:
8347

Relevant Lines:
10423

💛  - Coveralls

Pull Request Test Coverage Report for Build 7353492320

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.2%) to 80.282%

Totals

Change from base Build 7340710562:
0.2%

Covered Lines:
7642

Relevant Lines:
9519

💛  - Coveralls

/hold

/approve
/lgtm

/lgtm
/approve

/unhold
Confirm the logic and everything LGTM

authors: coveralls jonathan-innis njtran

repo: aws/karpenter-core


text:
Examples of generated API client usage?

Do there exist any examples of generated API client code usage? I've been able to generate an API client for some Grafana endpoints, but can't yet figure out how to e.g. configure the API server address.

The Smithy code-generator currently doesn't have an opinionated structure on how endpoints are set or determined for a client. So the base generated client does not generate or register middleware that sets the endpoint. We have a pair GoIntegration plugin on the the SDK side that has an opinionated approach to endpoints (EndpointResolver type that takes a name of a region and returns an SDK specific structure). We then have our generated code based on the service's endpoints description.
See AwsEndpointGenerator and EndpointGenerator for more in depth detail on how we are doing the code generation. ResolveEndpoint is an example of the generated middleware for the service client.
For the SDK's use case we needed to have a per client endpoint resolver and middleware due to our push to move away from a giant endpoints structure, and instead ship endpoints alongside the clients themselves. Depending on your use case you likely don't need this level of complexity.

I would note that smithy-go now supports modeled endpoint resolution, though the feature isn't part of the public IDL docs. That aside I have #458 open to track making smithy-go usable on its own, as of this writing it heavily depends on additional codegen support added in the v2 SDK to produce a working client.

authors: aknuds1 lucix-aws skmcgrail

repo: aws/smithy-go


text:
2024-07-12_01-33-13_master-next_aws-c-s3

Automatically created.

/run

authors: aws-iot-embedded-linux-ci thomas-roos


text:
log4cplus:ERROR could not open file ./kvs log configuration

log4cplus:ERROR could not open file ./kvs log configuration
After running rtsp connection

@RohanK1411 ,
kvs_log_configuration file exists in samples directory. If you are running GStreamer pipeline, you can set the path using the log-config element. Closing. Feel free to reach out if you more questions.

@disa6302, after being able to successfully stream video once from my Raspberry Pi, I am getting an error when I try to run it again.
log4cplus: ERROR Failed to open file ./log/kvs.log
Please let me know what is wrong?

Any solution? I'm experiencing the same problem. I'm using the Gstreamer pipeline but I don't know what to change in kvs_log_configuration


text:
Math.h does not compile on MSVC

There are multiple mismatches between the header declarations and inline definitions on MSVC. See:
https://github.com/awslabs/aws-c-common/blob/master/include/aws/common/math.h#L74
https://github.com/awslabs/aws-c-common/blob/master/include/aws/common/math.msvc.inl#L70

it has been fixed https://github.com/awslabs/aws-c-common/blob/main/include/aws/common/math.msvc.inl#L113

authors: TingDaoK deejaweej

repo: awslabs/aws-c-common


text:
CDK Tutorial Steps Don't Work with cdk-init

I am new to CDK, so I've been trying to follow the tutorial steps found at https://awslabs.github.io/aws-cdk/tutorial.html.  The sequence of commands that is stated amounts to:
mkdir hello-cdk
cd hello-cdk
git init
cdk init --language typescript

When this sequence of commands is run, an error is issued.
`cdk init` cannot be run in a non-empty directory!

Removing the .git directory created from git init allows the cdk init command to run.   This appears to be because cdk init takes the step of creating git init for the user.  Documentation appears out of date.
Version details:
cdk --version
0.21.0 (build 9badc1c)

Running on MacOs Mojave

@rzigweid you are correct. Thanks for reporting. There is no need to manually git init before calling cdk init. @Doug-AWS assigning to you.

The user guide repo has moved. I've updated the doc source there and will update the README to reflect the change.

authors: Doug-AWS eladb rzigweid

repo: awslabs/aws-cdk


text:
Bug fixes

cidr_findry.py:
Error throws a NameGlobal error, modified to the intrinsic Exception instead.
lambda.py:
Inverse logic problem, supplying valid subnet sizes threw errors.
lambda_utils.py:
Left as an 'elif', was generating empty arrays resulting in "not enough information" error later in the code.

+1 for this PR. I've deployed into my account(s) and it works wonderfully.

I fixed these today in a refactor so I'll close this PR now.

repo: awslabs/aws-cidr-finder


text:
Make Codeartifact optional

At this point, when we deploy a seedkit using codeseeder, it deploys AWS Codeartifact domain and AWS Codeartifact Repository by default. This default behavior of creating  AWS Codeartifact will cause an issue in the regions where it is not supported. AWS Codeartifact should be created optionally

PR #6 fixes it.

repo: awslabs/aws-codeseeder


text:
Rely concurrently on multiple S3FileSystem in different regions

I use this as a library. I understand the only way to setup the AWS region is through System.setProperty("aws.region", Region.US_EAST_1.id());
Is there a way to configure it out of through a static variables?
More specifically, I need to use concurrently multiple S3FileSystem, for different buckets in different AWS regions. Though, the region seems to be nedded not only in S3FileSystem setup, but on any later operation:
software.amazon.awssdk.core.exception.SdkClientException: Unable to load region from any of the providers in the chain software.amazon.awssdk.regions.providers.DefaultAwsRegionProviderChain@55044b34: [software.amazon.awssdk.regions.providers.SystemSettingsRegionProvider@406ad6d5: Unable to load region from system settings. Region must be specified either via environment variable (AWS_REGION) or  system property (aws.region)., software.amazon.awssdk.regions.providers.AwsProfileRegionProvider@5486ee92: No region provided in profile: default, software.amazon.awssdk.regions.providers.InstanceProfileRegionProvider@78128dd0: Unable to contact EC2 metadata service.]
	at software.amazon.awssdk.core.exception.SdkClientException$BuilderImpl.build(SdkClientException.java:111) ~[sdk-core-2.28.18.jar:na]
	at software.amazon.awssdk.regions.providers.AwsRegionProviderChain.getRegion(AwsRegionProviderChain.java:70) ~[regions-2.28.18.jar:na]
	at software.amazon.awssdk.awscore.client.builder.AwsDefaultClientBuilder.resolveRegion(AwsDefaultClientBuilder.java:370) ~[aws-core-2.28.18.jar:na]
	at software.amazon.awssdk.utils.AttributeMap$DerivedValue.primeCache(AttributeMap.java:604) ~[utils-2.28.18.jar:na]
	at software.amazon.awssdk.utils.AttributeMap$DerivedValue.get(AttributeMap.java:593) ~[utils-2.28.18.jar:na]
	at software.amazon.awssdk.utils.AttributeMap$Builder.resolveValue(AttributeMap.java:400) ~[utils-2.28.18.jar:na]
	at software.amazon.awssdk.utils.AttributeMap$Builder.internalGet(AttributeMap.java:389) ~[utils-2.28.18.jar:na]
	at software.amazon.awssdk.utils.AttributeMap$Builder.access$1300(AttributeMap.java:201) ~[utils-2.28.18.jar:na]
	at software.amazon.awssdk.utils.AttributeMap$Builder$1.get(AttributeMap.java:403) ~[utils-2.28.18.jar:na]
	at software.amazon.awssdk.services.s3.DefaultS3BaseClientBuilder.lambda$finalizeServiceConfiguration$2(DefaultS3BaseClientBuilder.java:197) ~[s3-2.28.18.jar:na]
	at software.amazon.awssdk.utils.AttributeMap$DerivedValue.primeCache(AttributeMap.java:604) ~[utils-2.28.18.jar:na]
	at software.amazon.awssdk.utils.AttributeMap$DerivedValue.get(AttributeMap.java:593) ~[utils-2.28.18.jar:na]
	at software.amazon.awssdk.utils.AttributeMap$Builder.resolveValue(AttributeMap.java:400) ~[utils-2.28.18.jar:na]
	at software.amazon.awssdk.utils.AttributeMap$Builder.internalComputeIfAbsent(AttributeMap.java:331) ~[utils-2.28.18.jar:na]
	at software.amazon.awssdk.utils.AttributeMap$Builder.putLazyIfAbsent(AttributeMap.java:275) ~[utils-2.28.18.jar:na]
	at software.amazon.awssdk.core.client.config.SdkClientConfiguration$Builder.lazyOptionIfAbsent(SdkClientConfiguration.java:182) ~[sdk-core-2.28.18.jar:na]
	at software.amazon.awssdk.awscore.client.builder.AwsDefaultClientBuilder.finalizeAwsConfiguration(AwsDefaultClientBuilder.java:188) ~[aws-core-2.28.18.jar:na]
	at software.amazon.awssdk.awscore.client.builder.AwsDefaultClientBuilder.finalizeChildConfiguration(AwsDefaultClientBuilder.java:170) ~[aws-core-2.28.18.jar:na]
	at software.amazon.awssdk.core.client.builder.SdkDefaultClientBuilder.asyncClientConfiguration(SdkDefaultClientBuilder.java:237) ~[sdk-core-2.28.18.jar:na]
	at software.amazon.awssdk.services.s3.DefaultS3AsyncClientBuilder.buildClient(DefaultS3AsyncClientBuilder.java:51) ~[s3-2.28.18.jar:na]
	at software.amazon.awssdk.services.s3.DefaultS3AsyncClientBuilder.buildClient(DefaultS3AsyncClientBuilder.java:27) ~[s3-2.28.18.jar:na]
	at software.amazon.awssdk.core.client.builder.SdkDefaultClientBuilder.build(SdkDefaultClientBuilder.java:173) ~[sdk-core-2.28.18.jar:na]
	at software.amazon.awssdk.services.s3.S3AsyncClient.create(S3AsyncClient.java:24264) ~[s3-2.28.18.jar:na]
	at software.amazon.nio.spi.s3.S3ClientProvider.generateClient(S3ClientProvider.java:102) ~[aws-java-nio-spi-for-s3-2.1.0.jar:na]
	at software.amazon.nio.spi.s3.S3FileSystem.client(S3FileSystem.java:416) ~[aws-java-nio-spi-for-s3-2.1.0.jar:na]
	at software.amazon.nio.spi.s3.S3FileSystemProvider.newFileChannel(S3FileSystemProvider.java:826) ~[aws-java-nio-spi-for-s3-2.1.0.jar:na]
	at java.base/java.nio.channels.FileChannel.open(FileChannel.java:309) ~[na:na]
	at java.base/java.nio.channels.FileChannel.open(FileChannel.java:369) ~[na:na]

The library will determine your region based on the standard Java SDK v2 rules. https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/region-selection.html
So the region could be determined from (among other things):

AWS_REGION environment variable or aws.region system variable
AWS_PROFILE envronment variable or aws.profile
metadata endpoints on EC2 or ECR/ EKS containers
Hard coded variables in code.
Information in ~/.aws/config or ~/.aws/credentials

The exact list and order or precedence comes from DefaultAwsRegionProviderChain.
When it comes to accessing S3 buckets, when the Filesystem is created the library will attempt to determine the location of the bucket and create a client for that bucket configured with the correct region. This is important because calls to buckets must be made by the clients from the appropriate regions otherwise the SIGV4 signature will not be accepted.
On the whole, you probably don't need to set the region in your code, rather you can just run with an AWS_PROFILE set or run in an EC2 with an instance profile (role).

Having said that, the newFileChannel implementation is quite new so a bug is not impossible.

All it is doing is making an S3AsyncClient.create(). You could test a small app in your environment to see if you are able to create a client with this single call.

It works if I did not removed System.clearProperty("aws.region"); in the meantime. I'm not considering a piece of software deployed in a specific region (not even some code necessarily deployed in AWS).
Why would I call System.clearProperty("aws.region");? As I understand I need to set aws.region to the bucket region. (Indeed, if I do not set an aws.region, S3AsyncClient.create() will fail.).
Maybe I should understand I can pick any region as:

S3AsyncClient.create() do not need to see the bucket region in aws.region
An S3AsyncClient is cross bucket. Would you confirm an S3AsyncClient is also cross-region? (Hence, aws.region is just informative as long as my runtime is out of AWS infrastructure ; it is not used relatively to the targetted buckets).
In a given JVM, I can freely open S3FileSystems on different buckets, along different regions. I just need to provide some default aws.region for whatever reason.
This may relates to https://github.com/awslabs/aws-java-nio-spi-for-s3/issues/353, my scenario (cross-region, runtime out of AWS) why some default region mechanisms used to exist.

when the Filesystem is created the library will attempt to determine the location of the bucket and create a client for that bucket configured with the correct region.

Well, the stack (and the code with superficial eye) suggests an S3AsyncClient is created on a per-Path basis (e.g. on .newFileChannel), not at S3FileSystem creation.

This is important because calls to buckets must be made by the clients from the appropriate regions otherwise the SIGV4 signature will not be accepted

This makes me feel I'm mostly wrong in my previous comment. Hence questioning: is there room for cross-region S3FileSystem in a single JVM?

It works if I did not removed System.clearProperty("aws.region"); in the meantime. I'm not considering a piece of software deployed in a specific region (not even some code necessarily deployed in AWS).

You do need to have a region specified somewhere either as an environment variable, as part of your AWS profile or in code.

Why would I call System.clearProperty("aws.region");? As I understand I need to set aws.region to the bucket region. (Indeed, if I do not set an aws.region, S3AsyncClient.create() will fail.). (So, my current underatanding is I should wap aws.region dynamically (on each Path) to manage a cross-region scenario).

You may not know the region of a bucket, especially if it is a publicly available data repository. You would usually set your region to the region that your bucket is in but if you are working across buckets in two regions then you can't set two regions so you would select one (it doesn't matter which).

Maybe I should understand I can pick any region as:

S3AsyncClient.create() do not need to see the bucket region in aws.region

You don't have to set aws.region but you DO have to configure a region in one of standard AWS ways. A region is required. S3AsyncClient.create() will use whatever region is found by the DefaultAwsRegionProviderChain.

An S3AsyncClient is cross bucket. Would you confirm an S3AsyncClient is also cross-region? (Hence, aws.region is just informative as long as my runtime is out of AWS infrastructure ; it is not used relatively to the targetted buckets).

It is not cross region. In the library we cache one client per bucket and each client is configured with the region of the bucket.

In a given JVM, I can freely open S3FileSystems on different buckets, along different regions. I just need to provide some default aws.region for whatever reason.

Correct.

This may relates to AWS_REGION is ignored => region is locked to us-east-1 #353, my scenario (cross-region, runtime out of AWS) why some default region mechanisms used to exist.

Partially

This makes me feel I'm mostly wrong in my previous comment. Hence questioning: is there room for cross-region S3FileSystem in a single JVM?

In this lib each bucket is it's own FileSystem therefore to work across two buckets, two FileSystems would be created.

You don't have to set aws.region but you DO have to configure a region in one of standard AWS ways. A region is required. S3AsyncClient.create() will use whatever region is found by the DefaultAwsRegionProviderChain.

This is very clear. I do rely on Set.property('aws.region', 'someRegion') as it is the simpler way in my case to setup DefaultAwsRegionProviderChain. Still, how can I manage buckets in different regions given a single DefaultAwsRegionProviderChain/JVM?

In this lib each bucket is it's own FileSystem therefore to work across two buckets, two FileSystems would be created.

Yes. This is part of the initial question: I need to use concurrently multiple S3FileSystem, for different buckets in different AWS regions.

It is not cross region. In the library we cache one client per bucket and each client is configured with the region of the bucket.

I insist. The stack I provided, and the code as I saw in this library suggest a S3AsyncClient is created on each Path being considered, hence not being  created with S3FileSystem, nor memoized/cache on first use .
I get what's going on:
software.amazon.nio.spi.s3.S3ClientProvider.generateClient(String, S3AsyncClient) relies on a bucketClientCache. Hence, S3AsyncClient seems memoized, but not created with S3FileSystem. Once memoized, we still create another S3AsyncClient on each path:
[S3ClientProvider]

    protected S3AsyncClient generateClient(String bucket) {
        try {
            return generateClient(bucket, S3AsyncClient.create()); // <-- `generateClient` would rely on a cache, but we always create an additional `S3AsyncClient.create()` for location detection.
        } catch (ExecutionException e) {
            throw new RuntimeException(e);
        } catch (InterruptedException e) {
            Thread.currentThread().interrupt();
            throw new RuntimeException(e);
        }
    }

The locationClient is documented with recommend using {@code S3ClientProvider#UNIVERSAL_CLIENT}. Why do we generate a fresh S3AsyncClient then? Quick-read through getBucketLocation suggests we rely on universalClient only if .headBucket failed. Looking at this class, I see: we infer the region only if configuration.endpointUri() == null, as we may get the region from configuration.getRegion().
Hence, I understand:

I hoped I could specify implicitly a region in a S3FileSystem through the URI of public FileSystem newFileSystem(final URI uri, final Map<String, ?> env), but S3FileSystemInfo.endpoint seems not tweakable . Hence .withEndpoint(info.endpoint()) is a no-op in S3FileSystemProvider.getFileSystem.
Even if this was a way forward, there would still be unexpected S3AsyncClient generated unecessarily in software.amazon.nio.spi.s3.S3ClientProvider.generateClient(String) (by unnecessary, I mean we create a S3AsyncClient while it may not be used at all (e.g. if the bucket S3Client is in cache and not closed, or even simpler if the bucket-region is in cache)).
Is there a way to create a S3FileSystem given my own S3NioSpiConfiguration?
I feel I need to setup aws.region only for the regionDetector S3Client, even though I feel the universalClient could do the job.

All-in-all:

One need to have an aws.region defined at all time, due to spurious S3AsyncClient creations
However, this region is not a strong constraint regarding used buckets: the library takes care of inferring the actual bucket region, using the DefaultAwsRegionProviderChain region as the region of the locationClient/bucketRegionDetector.

One reason why we create a client and then potentially fall back on the "universal" client to determine location is because the HeadBucket call must be made with a client in the bucket region whereas any call to GetBucketLocation must be done in us-east-1. GetBucketLocation is deprecated now so we may change the logic.
The approach is convoluted because s3 paths say nothing about region and we can't guarantee that any individual user will have permissions for HeadBucket or GetBucketLocation so we try several approaches.
To make things more efficient, we could add options to configure the library so that it will only attempt connections in one region, or we could have a configuration option to provide a list of region names with bucket names so the library can avoid making the location lookup.

One reason why we create a client and then potentially fall back on the "universal" client to determine location is because the HeadBucket call must be made with a client in the bucket region whereas any call to GetBucketLocation must be done in us-east-1. GetBucketLocation is deprecated now so we may change the logic.

Supposing GetBucketLocation would be dropped, given HeadBucket needs to be done with the proper region, it would be nice to be able to provide the region explicitly, especially in cross-region scenario (like mine). Hence, I understand that in my case, the buckets within the DefaultAwsRegionProviderChain get there region confirmed by HeadBucket ; while the other (cross-region) buckets do rely on GetBucketLocation  (which is deprecated).
The region could also be computed once and for all (to prevent creating S3AsyncClient). This information is currently cached for 15 minutes ; I suppose it is especially relevant for (edge-)case where a bucket is deleted and re-created in a different region (I believe a bucket can not be migrated).
Could the region  be expressed in the URI, like something like s3://<region>:<bucket_name> ? Or rather something following the API endpoint: s3.eu-south-1.amazonaws.com? (As a library-user, I feel comfortable providing myself each bucket region, than relying on automated detection).
Also, as you enabled crossRegion (https://github.com/awslabs/aws-java-nio-spi-for-s3/issues/206), a naive question is: Why not just letting the AsyncClient pick its region?:
    /**
     * Configure the region with which the SDK should communicate.
     *
     *
If this is not specified, the SDK will attempt to identify the endpoint automatically using the following logic:
     *

     *
Check the 'aws.region' system property for the region.

     *
Check the 'AWS_REGION' environment variable for the region.

     *
Check the {user.home}/.aws/credentials and {user.home}/.aws/config files for the region.

     *
If running in EC2, check the EC2 metadata service for the region.

     *

     *
     * @param region the region to be used
     * @return this builder for method chaining.
     */
    S3CrtAsyncClientBuilder region(Region region);

Why not just letting the AsyncClient pick its region?
Unfortunately you can't change the region of a client once it is created. If you could then I agree things would be easier.

Could the region be expressed in the URI, like something like s3://:<bucket_name> ? Or rather something following the API endpoint: s3.eu-south-1.amazonaws.com? (As a library-user, I feel comfortable providing myself each bucket region, than relying on automated detection).

This is mainly because this library is intended to operate as a NIO SPI meaning you can include it on the classpath of any Java application that is reading files using NIO Paths and anytime the application sees an s3 URI then it will automatically switch to using this library as the provider. No changes or recompilation are needed in the original application (it can now read local and S3 files).  So the design idea is that it should "just work" with little (or preferably) no configuration. A URI like s3://<region>:<bucket_name> is not a recognized S3 URI that you can use with any other S3 tool. It also isn't any URI that you can get from any S3 service so I don't know if we can expect people to use this form.
Even S3 bucket ARNs don't have regions so we couldn't use that information either.
A lot of this is due to the legacy of S3 predating AWS regions and even AWS accounts (which is why S3 bucket names must be globally unique and not just unique in the context of an account/ region).

Unfortunately you can't change the region of a client once it is created. If you could then I agree things would be easier.

Why changing the client region? The documentation states that if the client is cross-region, then a first query with wrong region (given DefaultAwsRegionProviderChain ) would return an error, and the region will turn automatically with the adequate region.

If the bucket does not exist in that specific Region, the error response includes the actual Region where the bucket resides. The SDK then uses the correct Region in a second request.

To optimize future requests to the same bucket, the SDK caches this Region mapping in the client.

It even suggests a single cross-region asyncClient could manage different buckets in different regions. This seems confirmed by S3CrossRegionAsyncClient (regarding both caching an redirection).

Interesting. This seems like new behavior than what the client previously did. It also means it behaves more like Boto3. I will try to find some time to investigate this as it would make things simpler.

authors: blacelle markjschreiber


text:
[FEATURE] - Release 1.5

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Create a demo environment for 1.5, destroy demo for 1.4

repo: awslabs/aws-orbit-workbench


text:
Add arpa-related content in Makefile.common

I have added arpa-related content into the Makefile.common.
The proposed additions do not necessarily modify the current user experience for writing and running proofs (in the case where users do not want to use arpa. Furthermore, with my proposed additions, integrating arpa into existing projects will be as simple as following these two steps:

Submodule aws-proof-build-assistant into the CBMC_ROOT directory of the project.
Add project-specific cmake flags to Makefile-project-defines

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

LGTM apart from newline at end-of-file, but let's wait for a review from @markrtuttle or @danielsn or @feliperodri before merging.

authors: ArenBabikian karkhaz

repo: awslabs/aws-templates-for-cbmc-proofs


text:
Use miniver for version resolution.

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

This uses https://github.com/jbweston/miniver to resolve dependencies based on tags.

Hmm, how should we handle the license headers? Should we still copy our header in the miniver files?

Hmm, how should we handle the license headers? Should we still copy our header in the miniver files?

One would need to check what the license for miniver says about that

https://github.com/jbweston/miniver/blob/master/LICENSE
Looks like we can do whatever we want :)

This seems to work now. If I run python setup.py build, the contents of gluonts/_static_version.py is replaced.

authors: jaheba lostella

repo: awslabs/gluon-ts


text:
include DistributionForecast and make plot generic

Issue #, if available:
Description of changes:
Include DistributionForecast and make plot work for all Forecast objects.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Related to #289

Job PR-316/1 is complete.
Docs are uploaded to http://gluon-ts-staging.s3-accelerate.dualstack.amazonaws.com/PR-316/1/index.html

Codecov Report

Merging #316 into master will increase coverage by 40.3%.
The diff coverage is 44.23%.

@@            Coverage Diff             @@
##           master     #316      +/-   ##
==========================================
+ Coverage   40.32%   80.63%   +40.3%
==========================================
  Files         142      142
  Lines        8024     8040      +16
==========================================
+ Hits         3236     6483    +3247
+ Misses       4788     1557    -3231

Impacted Files
Coverage Δ

src/gluonts/model/forecast.py
72.3% <44.23%> (+21.03%)
:arrow_up:

src/gluonts/dataset/artificial/_base.py
36.67% <0%> (+1.43%)
:arrow_up:

src/gluonts/core/exception.py
62.5% <0%> (+2.08%)
:arrow_up:

src/gluonts/model/trivial/constant.py
76.92% <0%> (+11.53%)
:arrow_up:

src/gluonts/kernels/_kernel_output.py
87.09% <0%> (+12.9%)
:arrow_up:

src/gluonts/model/seasonal_naive/_estimator.py
100% <0%> (+14.28%)
:arrow_up:

src/gluonts/model/npts/_estimator.py
100% <0%> (+14.28%)
:arrow_up:

src/gluonts/dataset/artificial/recipe.py
89.21% <0%> (+14.93%)
:arrow_up:

src/gluonts/model/deepar/_estimator.py
100% <0%> (+15.09%)
:arrow_up:

src/gluonts/dataset/stat.py
96.32% <0%> (+15.44%)
:arrow_up:

... and 93 more

Looks good! Thank you

authors: codecov-io lostella szha vafl


text:
Fix QuantileForecast.quantile in case only mean is stored

Issue #, if available: Fixes #2498
Description of changes: There was a bug into the logic that decided whether to do linear interpolation or not, in the edge case where only mean is stored in the forecast object. This fixes it and adds a test.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Please tag this pr with at least one of these labels to make our release process faster: BREAKING, new feature, bug fix, other change, dev setup

What looks weird to me is that we treat mean as a quantile. Shouldn't we just keep them separate?

What looks weird to me is that we treat mean as a quantile. Shouldn't we just keep them separate?

Yes, I agree. Either that or QuantileForecast gets a different name.

repo: awslabs/gluonts


text:
minor tweaks to AWS README

Issue #, if available:
Description of changes: just a few minor doc updates, upgrade to using 1.19
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

a few minor doc updates, upgrade to using 1.19

repo: awslabs/karpenter


text:
Add ModelLayer parameter to Operation struct

Motivation and Context
There is an asymmetry with applying a Layer before and after the operation upgrade procedure. This can be seen in the difference between C and D in the middleware documentation.
This can be rectified by adding a new type parameter to Operation.
Description

Add ModelLayer type parameter to Operation struct.
Add Operation::model_layer method to Operation.
Rename Operation::layer method to Operation::http_layer.
Change Plugin trait to map (ModelLayer, HttpLayer).

This PR has been sitting around for a while. Is it still relevant or can we close it?

authors: Velfi hlbarber

repo: awslabs/smithy-rs


text:
refactor: Make sure code in docs is tested

I also added a section to the dev tutotial, about how to extend the docs

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

I'm running the e2e tests manually against your branch, let's see the result: https://github.com/awslabs/syne-tune/actions/runs/4403996585

One thing is a bit annoying, I don't have a good answer: When I include a part of a file with literalinclude, and then the file is changed, the range may be wrong. It would be great to get some notification to check ranges for included files once they change. But I think this is not easy to do.

End-2-end tests failed for a number of reasons. I am working on this

OK, all end-to-end tests run through now.

One thing is a bit annoying, I don't have a good answer: When I include a part of a file with literalinclude, and then the file is changed, the range may be wrong. It would be great to get some notification to check ranges for included files once they change. But I think this is not easy to do.

Good point, that is a con. But I think the pros still outweigh the cons, so let's try it, and if we run into challenges we can evolve and adapt as needed.

authors: mseeger wesk

repo: awslabs/syne-tune


text:
fix: cyclonedx is only needed for global builds

I've also adjusted what counts as a "global" build - the "all" and "host" modes build global artifacts too, so we should check those.

I was trying to figure out why the tests are failing with "no cyclonedx" even though the tests run fine without them, but then I realized what the issue is. We do the cyclonedx stuff in CI, not in Rust. Our test builds invoke dist build -aglobal, which means they don't actually call cyclonedx at all - but this check is still there.
We should either remove the cyclonedx check altogether, or we should move the command to run it into Rust so that the two sides of this agree with each other.

repo: axodotdev/cargo-dist


text:
Riscv64 support

Add support for riscv64-unknown-linux-gnu

Hey @krsh, thanks for the PR!
Let's do this in stages:

Open a PR with just the changes to src/xtask/codegen and please also include a change to our CI workflow that generates the bindings - https://github.com/aya-rs/aya/blob/3262f85925459bdc636afccadc3ae3fc926dc9ac/.github/workflows/gen.yml#L26

Once merged, I'll trigger the workflow and CI will generate the bindings

Then you can open a final PR to make sure that the generated bindings are included in the right mod.rs/lib.rs.

Lastly, please make sure to run cargo +nightly fmt and cargo +nightly clippy against your patches to make sure the linter is happy!

authors: dave-tucker krsh

repo: aya-rs/aya


text:
Fix load errors for empty (but existent) BTF/BTF.ext sections

Compiling a program using an older version of clang (tested w/ clang 8) for a non-CORE program creates a .BTF and a .BTF.ext section that aya fails to load.

.BTF.ext error: the .BTF.ext section is from an older header and aya isn't checking the hdr_len and instead assumes that the size of its pregenerated struct will work no matter what. This PR fixes this by first loading the data into a "minimal header" and then only loads as much data into the full fledged header as it is allowed to per the spec.
.BTF error: The created section has no types which returns an error at load type saying "type not found". This PR uses the existing "sanitize" method to check if there are any types and if not then it skips the load of the .BTF section as there is no gain in trying to load it.

Looks good, thank you! I'm going to merge once CI passes

Thanks for the quick feedback, I've been really enjoying Aya!


text:
Add support for stack argument

Add support for stack argument
related to https://github.com/aya-rs/aya/pull/659

@tamird
A test case is added to ensure stack_argument works okay.
Any other suggestions?

@tamird @vadorovsky
Any further suggestions?

@tamird

Please test this locally before pinging again.

@tamird
Check about this?

I'm running out of patience with this PR. Every revision is ridden with bugs. I'm inclined to stop reviewing this TBH.

Sorry about that.
From my view, the mainly errors are specify different integeration-ebpf test-case for arm, aarch64 and amd. I would fix it latter.

Would reopen when I get some spare time.

authors: liyan-ah tamird


text:
can the nerf be improved by non-original viewpoint optimization

clueless general question: are only original training image positions used or can the method restore gaps in training image coverage by iteratively inpainting low information viewpoints? i.e. attempt a 360 iteratively from whatever by referencing the training images similar to control-net but using new view points around a pivot.
I'd like to use footage that wasn't shot with nerfs in mind and optimize it this way. Is this what the model does already?
If not what would it take to modify it for this purpose? This scenario seems more universal and useful as a starting point

Hi! So currently in our pipeline, we only edit views that are from the original training image coverage. I definitely think it would help to get training views from low info viewpoints, but the only challenge is that it would require hand-crafted camera positions, as most of the scenes we work on are real-world, unbounded scenes, so its non-trivial to sample cameras randomly. If you would like to do this, the best way to do so would be to create a camera path in the viewer, export those camera paths, and then try to load them into the dataloader to use for training. There isn't an easy way to do this and it would require some code adjustments, but definitely doable if you are familiar with Nerfstudio. Good luck!

If you use the viewer to generate your "pseudo-observations" which you can do by basically setting your framerate to 1 and then picking the cameras you want. Then you can export the json file. Here's how I'd do it:
https://github.com/ayaanzhaque/instruct-nerf2nerf/blob/main/in2n/in2n_pipeline.py#L144
So right here is where I cycle through the list of cameras and load them.
You can load your camera path by doing this:
self.cameras_from_path = get_path_from_json(camera_path)
where camera_path is the directory to the camera file.
Then, just re-write the linked section I gave to this:
# get current camera
current_camera = self.cameras_from_path[current_index].to(self.device)
current_ray_bundle = current_camera.generate_rays(torch.tensor(list(range(1))).unsqueeze(-1))

Just make sure you have enough views in your camera path or else you won't get a good edit. Hopefully this helps!
In terms of the new paper, I think using stable diffusion to generate pseudo-views naively would create more artifacts. But its definitely a cool paper!

wow cool, thank you! I'll give it a shot!

no problem, let me know if you need any help! If you need help using the viewer, check out the nerfstudio docs

authors: ayaanzhaque metonomas


text:
How to disable lsp inline error messages?

Version confirmation

[X] Confirm

Following prerequisites

[X] Confirm

Neovim version
NVIM v0.8.3 Build type: Release LuaJIT 2.1.0-beta3 Compiled by runner@fv-az183-550  Features: +acl +iconv +tui See ":help feature-compile"     system vimrc file: "$VIM/sysinit.vim"   fall-back for $VIM: "/share/nvim"  Run :checkhealth for more info
Operating system/version
wsl2 ubuntu22.04
Terminal name/version
wezterm
$TERM environment variable
No response
Branch info
main (Default/Latest)
Fetch Preferences
SSH (use_ssh = true)
How to reproduce the issue
In some cases, I don't need lsp inline error diagnostic messages. Too many error messages make my codes messy. I can run LspStop to stop LSP, but i prefer to configure the setting to disable error hints and remain lsp functionalities.
How can I disable these error hints?
Expected behavior
N/A
Actual behavior
No response
Additional information
No response

This is not a bug issue.

repo: ayamir/nvimdots


text:
是否支持高亮某一个字符串(全匹配或者忽略大小写匹配)？

Feature description
类似vscode中的highlight words插件，可以高亮某一个字符串.

Additional information
No response

This should be in discussions, transferred.


text:
Now we can specify which field to use in WHERE IN

Now we can specify which field to use in WHERE IN. So we can update
models by custom field.
Use case:
User has some external resources and these resources are loaded into django database more than once. But related data like analytics should be stored once as it is ONE resource, which has TWO instances in our DB - like m2m.
So, we should be able to update all resources at once by one query. For example, we have 1 resource with EXT_RES1, but we have 2 instances in our DB: OUR_RES1(EXT_RES_ID=1), OUR_RES2(EXT_RES_ID=1).
So we should be able to throw a query like UPDATE ... WHERE EXT_RES_ID in (1 ... ).
With this commit we can specify which field to use instead of PK, so we can use EXT_RES_ID and it will do the trick.

Thanks.

authors: aykut iorlas

repo: aykut/django-bulk-update

license: mit


text:
Feature request: CONFIG_BLK_DEV_RBD=m

Please enable CONFIG_BLK_DEV_RBD=m.
This would allow to use ceph via rook on k8s clusters. Running k8s on rock64 clusters seem to be quite popular these days.

Can you prepare a PR. I will merge it then.

Done. Thank you.

Any update?  I'm also interested in running Ceph in my Rock64 k8s cluster.

@ayufan Is it just a matter of adding the modules to the defconfig or are there other things that need to be added to get it working?  If so, I can open a PR.

I accept only modules added to defconfig.
On Tue, Aug 7, 2018 at 5:46 PM, Josh Reichardt notifications@github.com
wrote:

@ayufan https://github.com/ayufan Is it just a matter of adding the
modules to the defconfig or are there other things that need to be added to
get it working? If so, I can open a PR.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ayufan-rock64/linux-build/issues/211#issuecomment-411104247,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACTpQd_QAUDBYdhs0q8dwKJQzWQB9v2yks5uObZYgaJpZM4UeP9A
.

authors: ayufan jmreicha wirr00


text:
Popup window navigation buttons showing errors are not functional

Popup window navigation buttons showing errors are not functional
Tested with Firefox

Thanks for the issue, will check that.

After a little investigation, this is the good time for me to improve the import process reporting (will fix also #14 issue if I understand well).
But this will take some time (ie: not tonight ^^).
In the meantime, I fixed #15 so you could be able to play a bit with Azimutt :smile:
I hope you will enjoy!
And again, thanks for the reports :+1:

I'm closing this issue as it will be addressed in https://github.com/azimuttapp/azimutt/issues/17.
Feel free to reopen if it's different.

authors: PhBastiani loicknuchel

repo: azimuttapp/azimutt


text:
Feat: describe origin command

added describe origin command

It's actually a string and I haven't refactored the origins part of the api to deal with the origin key, hot refactoring coming up kkk

repo: aziontech/azion


text:
Game.ini does not get loaded

I uploaded a Game.ini file from single player since I've read online that this needs to be done but it seems to not work.
I also tried to let the server generate one itself and then edit that file, that also didn't work.
No clue what is causing this but can someone check if it has to do with the container or the Proton layer?

The Game.ini settings work fine on my side. Could you show what your Game.ini looks like? The file should already be present in ./ShooterGame/Saved/Config/WindowsServer/Game.ini. Normally, you just have to add [/script/shootergame.shootergamemode] at the top of the file and your custom options under it.

[/Script/ShooterGame.ShooterGameMode] BabyImprintingStatScaleMultiplier=1 BabyCuddleIntervalMultiplier=0.25 BabyCuddleGracePeriodMultiplier=1 BabyCuddleLoseImprintQualitySpeedMultiplier=1 PerLevelStatsMultiplier_DinoTamed[0]=0.0900000036 PerLevelStatsMultiplier_DinoTamed[1]=1 PerLevelStatsMultiplier_DinoTamed[2]=1 PerLevelStatsMultiplier_DinoTamed[3]=1 PerLevelStatsMultiplier_DinoTamed[4]=1 PerLevelStatsMultiplier_DinoTamed[5]=1 PerLevelStatsMultiplier_DinoTamed[6]=1 PerLevelStatsMultiplier_DinoTamed[7]=1 PerLevelStatsMultiplier_DinoTamed[8]=0.0700000003 PerLevelStatsMultiplier_DinoTamed[9]=1 PerLevelStatsMultiplier_DinoTamed[10]=1 PerLevelStatsMultiplier_DinoTamed_Add[0]=0.0399999991 PerLevelStatsMultiplier_DinoTamed_Add[1]=1 PerLevelStatsMultiplier_DinoTamed_Add[2]=1 PerLevelStatsMultiplier_DinoTamed_Add[3]=1 PerLevelStatsMultiplier_DinoTamed_Add[4]=1 PerLevelStatsMultiplier_DinoTamed_Add[5]=1 PerLevelStatsMultiplier_DinoTamed_Add[6]=1 PerLevelStatsMultiplier_DinoTamed_Add[7]=1 PerLevelStatsMultiplier_DinoTamed_Add[8]=0.0399999991 PerLevelStatsMultiplier_DinoTamed_Add[9]=1 PerLevelStatsMultiplier_DinoTamed_Add[10]=1 PerLevelStatsMultiplier_DinoTamed_Affinity[0]=0.189999998 PerLevelStatsMultiplier_DinoTamed_Affinity[1]=1 PerLevelStatsMultiplier_DinoTamed_Affinity[2]=1 PerLevelStatsMultiplier_DinoTamed_Affinity[3]=1 PerLevelStatsMultiplier_DinoTamed_Affinity[4]=1 PerLevelStatsMultiplier_DinoTamed_Affinity[5]=1 PerLevelStatsMultiplier_DinoTamed_Affinity[6]=1 PerLevelStatsMultiplier_DinoTamed_Affinity[7]=1 PerLevelStatsMultiplier_DinoTamed_Affinity[8]=0.189999998 PerLevelStatsMultiplier_DinoTamed_Affinity[9]=1 PerLevelStatsMultiplier_DinoTamed_Affinity[10]=1 PerLevelStatsMultiplier_DinoWild[0]=1 PerLevelStatsMultiplier_DinoWild[1]=1 PerLevelStatsMultiplier_DinoWild[2]=1 PerLevelStatsMultiplier_DinoWild[3]=1 PerLevelStatsMultiplier_DinoWild[4]=1 PerLevelStatsMultiplier_DinoWild[5]=1 PerLevelStatsMultiplier_DinoWild[6]=1 PerLevelStatsMultiplier_DinoWild[7]=1 PerLevelStatsMultiplier_DinoWild[8]=1 PerLevelStatsMultiplier_DinoWild[9]=1 PerLevelStatsMultiplier_DinoWild[10]=1 PerLevelStatsMultiplier_Player[0]=1 PerLevelStatsMultiplier_Player[1]=1 PerLevelStatsMultiplier_Player[2]=1 PerLevelStatsMultiplier_Player[3]=1 PerLevelStatsMultiplier_Player[4]=1 PerLevelStatsMultiplier_Player[5]=1 PerLevelStatsMultiplier_Player[6]=1 PerLevelStatsMultiplier_Player[7]=1 PerLevelStatsMultiplier_Player[8]=1 PerLevelStatsMultiplier_Player[9]=1 PerLevelStatsMultiplier_Player[10]=1 GlobalSpoilingTimeMultiplier=0 GlobalItemDecompositionTimeMultiplier=0 GlobalCorpseDecompositionTimeMultiplier=1 PvPZoneStructureDamageMultiplier=6 StructureDamageRepairCooldown=180 IncreasePvPRespawnIntervalCheckPeriod=300 IncreasePvPRespawnIntervalMultiplier=2 IncreasePvPRespawnIntervalBaseAmount=59.9999886 ResourceNoReplenishRadiusPlayers=1 ResourceNoReplenishRadiusStructures=1 CropGrowthSpeedMultiplier=1 LayEggIntervalMultiplier=1 PoopIntervalMultiplier=1 CropDecaySpeedMultiplier=1 MatingIntervalMultiplier=0.5 EggHatchSpeedMultiplier=5 BabyMatureSpeedMultiplier=10 BabyFoodConsumptionSpeedMultiplier=1 DinoTurretDamageMultiplier=1 DinoHarvestingDamageMultiplier=3.20000005 PlayerHarvestingDamageMultiplier=1 CustomRecipeEffectivenessMultiplier=1 CustomRecipeSkillMultiplier=1 AutoPvEStartTimeSeconds=0 AutoPvEStopTimeSeconds=0 KillXPMultiplier=1 HarvestXPMultiplier=1 CraftXPMultiplier=1 GenericXPMultiplier=1 SpecialXPMultiplier=1 FuelConsumptionIntervalMultiplier=1 PhotoModeRangeLimit=3000 bDisablePhotoMode=False bIncreasePvPRespawnInterval=True bAutoPvETimer=False bAutoPvEUseSystemTime=False bDisableFriendlyFire=False bFlyerPlatformAllowUnalignedDinoBasing=False bDisableLootCrates=False bAllowCustomRecipes=True bPassiveDefensesDamageRiderlessDinos=True bPvEAllowTribeWar=True bPvEAllowTribeWarCancel=True MaxDifficulty=True bUseSingleplayerSettings=False bUseCorpseLocator=True bShowCreativeMode=False bHardLimitTurretsInRange=True bDisableStructurePlacementCollision=False bAllowPlatformSaddleMultiFloors=False bAllowUnlimitedRespecs=True bDisableDinoRiding=False bDisableDinoTaming=False OverrideMaxExperiencePointsPlayer=0 OverrideMaxExperiencePointsDino=0 MaxNumberOfPlayersInTribe=0 ExplorerNoteXPMultiplier=0.999989986 BossKillXPMultiplier=0.999989986 AlphaKillXPMultiplier=0.999989986 WildKillXPMultiplier=0.999989986 CaveKillXPMultiplier=0.999989986 TamedKillXPMultiplier=0.999989986 UnclaimedKillXPMultiplier=0.999989986 SupplyCrateLootQualityMultiplier=1 FishingLootQualityMultiplier=1 CraftingSkillBonusMultiplier=1 bAllowSpeedLeveling=False bAllowFlyerSpeedLeveling=False
I copied all this from my single player so technically it shouldn't be huge list since most of them are default values.

Issue is fixed, I had my setting too low to notice it took effect.

authors: Jarnooow azixus


text:
upgrade to tdch 1.5.2 with jdbc bundled inside; add network opts to jdbc url

bump up the tdch jar from 1.4.2 to 1.5.2
inject MAX_MESSAGE_BODY=16384000,CHATTER=OFF to jdbc url to improve throughput over network with higher latency
inject avro.mapred.sync.interval=4194304 for avrofile generation with Avro 1.7.7 or above

@ericsun2 I am seeing failing tests. Can you please check them out?

repo: azkaban/azkaban-plugins


text:
Flaky test ExecutorManagerTest.testDispatchFailed

Hi @juhoautio, Can you take a look at below flaky test? I've seen it failed several times during travis build, but not able to reproduce it locally. Thanks!
azkaban.executor.ExecutorManagerTest > testDispatchFailed FAILED
    Wanted but not invoked:
    alerter.alertOnError(
        azkaban.executor.ExecutableFlow@7b304398,
        "Failed to dispatch queued execution derived-member-data because reached azkaban.maxDispatchingErrors (tried 2 executors)",
        contains("Mocked dispatch exception")
    );
    -> at azkaban.executor.ExecutorManagerTest.testDispatchFailed(ExecutorManagerTest.java:348)
    Actually, there were zero interactions with this mock.
        at azkaban.executor.ExecutorManagerTest.testDispatchFailed(ExecutorManagerTest.java:348)

@jamiesjc is this test going to become obsolete after the "AZNewDispatchingLogic"? If yes, I would disable or delete this test to stabilize the travis builds.

Yes, it will become obsolete if we switch to the new dispatching logic.

authors: jamiesjc juhoautio

repo: azkaban/azkaban


text:
【每日一题】– 2019-10-17 - canvas图片为什么要设计成有跨域的安全问题

images 引入了 crossorigin 属性, 通过设置适当的头信息 CORS , 可以从其他站点加载 img 图片, 并用在 canvas 中,就像从当前站点(current origin)直接下载的一样.
尽管没有CORS授权也可以在 canvas 中使用图像, 但这样做就会污染(taints)画布。 只要 canvas 被污染, 就不能再从画布中提取数据, 也就是说不能再调用 toBlob(), toDataURL() 和 getImageData() 等方法, 否则会抛出安全错误(security error).
请问这是为什么？

为了安全，假如没有这个限制那么用户的图片就可能被意外泄漏掉


text:
🛑 Sakai Wolford Bot is down

In b105793, Sakai Wolford Bot (https://sakaibot-discord.uzumekiulee.repl.co/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Sakai Wolford Bot is back up in b00c524 after 5 minutes.

repo: azrielbsi/monitor


text:
🛑 Sukri Online is down

In 318d39c, Sukri Online (https://discord-aklx.onrender.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Sukri Online is back up in 94122d1 after 4 minutes.


text:
Join Windows VM to Active Directory Domain

Creating separate issue for each requirement from Issue # 248
Need Windows VM to join Active Directory Domain.

Adding support as VM extension :
virtual_machine_extensions = {
      microsoft_azure_domainJoin = {
        domain_name = "contoso.com"
        ou_path = ""
        restart = "true"
        #specify the AKV location of the password to retrieve for domain join operation
        domain_join_password_keyvault = {
          keyvault_key = "example_vm_rg1"
          # lz_key = ""
          secret_name = "domain-join-password"
        }
        domain_join_username_keyvault = {
          keyvault_key = "example_vm_rg1"
          # lz_key = ""
          secret_name = "domain-join-username"
        }
      }
    }

repo: aztfmod/terraform-azurerm-caf


text:
Integration - Add support for managed boot diagnostics on VMs, etc. #368

Integration 443

thanks from @jleonelion for the contribution to cloud adoption framework!


text:
🛑 azuma doa: Mailing Service is down

In 91a2e25, azuma doa: Mailing Service (https://azuma-health.tech/health/doa-mailing) was down:

HTTP code: 0
Response time: 0 ms

Resolved: azuma doa: Mailing Service is back up in 66127b4 after 190 days, 3 hours, 11 minutes.

repo: azuma-healthtech-public/uptime-prd


text:
Adding a staffbot button to task assignment

This change adds a staffbot button to tasks on the project management page.
If there is no task assignment, clicking the staffbot button will create a StaffbotRequest for that task. If there is an existing task assignment, it will restaff the task.
This functionality makes it more convenient to use staffbot to recruit workers for a task that doesn't have automatic assignment mechanism.

Coverage decreased (-0.2%) to 93.613% when pulling 82b2946ea7d7618436b4e998d9c0415a0a052011 on restaff-bot-btn into 5cb3497b59d72ca859f7a72d9e51be6aa753a103 on master.

authors: coveralls paopow


text:
TelerikGrid with different data types

Hello,
I am trying to create a GRID for Blazor using the TelerikGrid. I get my list of items that can be tricky. We allow the users to setup User Defined field that can be a bit, decimal, date, int or text and give each on a unique name with the order that they should be displayed. i.e.. Amount1 - decimal - 1, Married - bit - 2, Year - date - 3. When I get the data and want to display it in the grid, I only want to allow them to add a value for each one, but the problem is that they can change the order that these come in. Could be Bit, then decimal, etc..
In my app, I have the following code:
<GridLayoutItem Row="24" Column="2" ColumnSpan="3" RowSpan="4">
    <TelerikGrid Data="@PersonUserFieldList" EditMode="@GridEditMode.Incell" Pageable="true" Width="330px"
            OnUpdate="@UpdatePhone" OnEdit="@EditPhone" OnCreate="@CreatePhone" OnCancel="@CancelPhone">
            <GridColumn Width="100px" Field=@nameof(UserDefinedFieldWithValues.column_name) Title="@TelerikMessages.Name">
                <EditorTemplate Context="ctx">
                    @{
                        var a = ctx as UserDefinedFieldWithValues;
                        if (a.DataType == "bit")
                        {
                            <TelerikCheckBox Class="myCheckBox" Enabled="true" Value="@a.BoolValue" />
                        }
                        if (a.DataType == "nvarchar(-1)")
                        {
                            <TelerikTextBox class="myTextBox1" @bind-Value="@a.TextValue"></TelerikTextBox>
                        }
                        if (a.DataType == "datetime")
                        {
                            <TelerikDatePicker Class="myDatePickerSmall" Min="@Min" Max="@Max" Format="d" DebounceDelay="@DebounceDelay"  @bind-Value="@a.DateValue"/>
                        }
                        if (a.DataType == "int")
                        {
                            <TelerikNumericTextBox Arrows="false" @bind-Value="@a.IntValue"/>
                        }
                        if (a.DataType == "decimal(18,0)")
                        {
                            <TelerikNumericTextBox Arrows="false" @bind-Value="@a.DecimalValue"/>
                        }
                    }
                </EditorTemplate>
            </GridColumn>
    </TelerikGrid>

    @*<TelerikListView Data="@PersonUserFieldList" Pageable="true" PageSize="5">
        <Template>
            @{
                UserDefinedField currItem = context as UserDefinedField;
                if (currItem.DataType == "bool")
                {

                        @currItem.column_name
                        <

                }
            }
        </Template>
    </TelerikListView>*@

</GridLayoutItem>

When I run this, I get the following error:
Microsoft.AspNetCore.Components.Web.ErrorBoundary[0]
System.InvalidOperationException: Object of type 'Telerik.Blazor.Components.TelerikGrid`1[[TimeShareWare.Essentials.Shared.UserDefinedFields.UserDefinedFieldWithValues, TimeShareWare.Essentials.Shared, Version=3.0.0.0, Culture=neutral, PublicKeyToken=null]]' does not have a property matching the name 'ChildContent'.
Sample Date:
BoolValue = null;
column_name = "Amount1";
DataType = "decimal(18,0)';
DateValue = null;
DecimalValue = null;
DisplayOrder = 1;
IntValue = null;
TextValue = null;
UserFieldID = 18,
Visible = true;

Any thoughts on how I can get this to work? I want to put it into a grid or maybe a list view because the users can enter as many of these fields as they would like.

Hey @jwalkerSSC
as I am no expert with Telerik, there is a guideline for that: https://www.telerik.com/blogs/unit-testing-blazor-components-bunit-justmock
Did you add Services.AddTelerikBlazor() also in your unit test?

hey @jwalkerSSC, im going to convert this to a QA discussion.

authors: egil jwalkerSSC linkdotnet

repo: bUnit-dev/bUnit


text:
Get IRenderedFragment/IRenderedComponent from DOM element (IElement)

In certain scenarios (#152), it can make it easier to create test when it is possible to get a component from a DOM element, due to the good DOM query (Find/FindAll) API.
Thus, it should be possible to go from an node to the component that rendered it.
The API could have two methods, GetComponent and GetComponent<TComponent>, and they should return a IRenderedFragment or IRenderedComponent<MyComp>, which is related to the nearest component in the render tree, that rendered the element. E.g.:
var elm = cut.Find("p");
IRenderedFragment componentThatRenderedElm = elm.GetComponent();
IRenderedComponent<MyComp> componentThatRenderedElm = elm.GetComponent<MyComp>();

It should be possible by adding meta information to the DOM tree created by the Htmlizer.cs type, and creating extension methods on INode that reads up the DOM tree until it finds some meta information about the source component. That extension method can then get the renderer and use its methods to find the component instance.
Update
With the current render pipeline, where we generate markup with Htmlizer and then convert to AngleSharp nodes does seems to contain too many compromises when info about the source component should be embedded in the nodes in the dom tree, at least for the variants I've tried, so I will move this item over to the AngleSharpRenderer project, where it will be a completely different store.
I tried adding custom <!--!X--> comments to markup in Htmlizer, but doing so had too much impact on other parts of the system. Another variant added a custom attribute to the first element in a component, the reasoning being that elements are what users query from using Find/FindAll. However, if a component simply contained a markup string, and not calls to "OpenElement", then the components would not get the attribute.

I am not sure about the name of the method. The method should return the component that rendered the element, but calling it GetComponent my lead some to think it will get a component which is a child of the element.
GetOwningComponent, GetSourceComponent, GetRenderingComponent are some other options.

As DOM elwlents are owned by components, elm.GetOwningComponent()

Does anyone know how to go from IRenderedFragment to IElement? Trying to assert css styles and ComputeCurrentStyle only exists on IElement

Would be a nice feature!

authors: egil mrpmorris mycarrysun wardbeyens


text:
Fix Application Configuration Plugin to allow URLs

Now instances of ZnUrl can be used in the configuration and correctly encoded to JSON.

Coverage increased (+6.0e-05%) to 99.542% when pulling 0758734adebe91eaa95e0832fb3ebb75f46b0ca6 on allow_urls_in_configuration into d5b8bfbebc33f3f027c486dc215b322c9014ebed on release-candidate.

authors: coveralls gcotelli

repo: ba-st/Stargate


text:
Update external helpers doc with global injection

This adds documentation for injecting the babelHelpers into window and global.

Looks good! The require("6to5/runtime"); usage wasn't really documented in 3.x so I think it's fine to leave that out. Can you also add a reference to including external-helpers.js from an npm release on your page in a <script> tag and it'll work just the same?

Ok cool this is good.

Great, thank you!

authors: goatslacker sebmck