text:
Update Lock, Auth0.js; add setting to use default

Changes
Please describe both what is changing and why this is important. Include:

Endpoints added, deleted, deprecated, or changed
Classes and methods added, deleted, deprecated, or changed
Screenshots of new or changed UI, if applicable
A summary of usage if this is a new feature or change to a public API (this should also be added to relevant documentation once released)

References
Please include relevant links supporting this change such as a:

support ticket
community post
StackOverflow post
support forum thread

Please note any links that are not publicly accessible.
Testing
Please describe how this can be tested by reviewers. Tests must be added for new functionality and existing tests should complete without errors.

[ ] I included manual testing steps above, if applicable
[ ] This change adds unit test coverage
[ ] This change has been tested on the latest version of the platform/language or why not

Checklist

[ ] I read Auth0's general contribution guidelines?
[ ] I read Auth0's code of conduct guidelines
[ ] All existing and new tests complete without errors
[ ] All code quality tools/guidelines in the Contribution guide have been run/followed
[ ] All relevant assets have been compiled as directed in the Contribution guide, if applicable
[ ] All active GitHub CI checks have passed

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@a78b427). Click here to learn what that means.
The diff coverage is 82.75%.

@@            Coverage Diff            @@
##             master     #635   +/-   ##
=========================================
  Coverage          ?   38.41%
  Complexity        ?     1248
=========================================
  Files             ?       51
  Lines             ?     3853
  Branches          ?        0
=========================================
  Hits              ?     1480
  Misses            ?     2373
  Partials          ?        0

Impacted Files
Coverage Δ
Complexity Δ

lib/WP_Auth0_Options.php
73% <ø> (ø)
28 <0> (?)

WP_Auth0.php
22.45% <ø> (ø)
62 <0> (?)

lib/WP_Auth0_LoginManager.php
19.83% <0%> (ø)
121 <0> (?)

lib/WP_Auth0_DBManager.php
24.78% <100%> (ø)
89 <0> (?)

lib/WP_Auth0_Routes.php
86.61% <100%> (ø)
55 <0> (?)

lib/admin/WP_Auth0_Admin_Advanced.php
37.45% <77.77%> (ø)
63 <2> (?)

Continue to review full report at Codecov.

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

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@a78b427). Click here to learn what that means.
The diff coverage is 81.57%.

@@           Coverage Diff            @@
##             master    #635   +/-   ##
========================================
  Coverage          ?   38.5%
  Complexity        ?    1251
========================================
  Files             ?      51
  Lines             ?    3857
  Branches          ?       0
========================================
  Hits              ?    1485
  Misses            ?    2372
  Partials          ?       0

Impacted Files
Coverage Δ
Complexity Δ

WP_Auth0.php
22.45% <ø> (ø)
62 <0> (?)

lib/WP_Auth0_Lock10_Options.php
70.53% <ø> (ø)
61 <0> (?)

lib/admin/WP_Auth0_Admin.php
0% <0%> (ø)
17 <0> (?)

lib/WP_Auth0_LoginManager.php
19.83% <0%> (ø)
121 <0> (?)

lib/WP_Auth0_DBManager.php
25.75% <100%> (ø)
89 <0> (?)

lib/WP_Auth0_Routes.php
86.61% <100%> (ø)
55 <0> (?)

lib/WP_Auth0_Options.php
73.78% <100%> (ø)
31 <3> (?)

lib/WP_Auth0_Options_Generic.php
98.27% <100%> (ø)
27 <0> (?)

lib/admin/WP_Auth0_Admin_Advanced.php
37.23% <72.22%> (ø)
63 <2> (?)

Continue to review full report at Codecov.

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

authors: codecov-io joshcanhelp


text:
Assets and NFT-Data

One of the primary reasons for having an NFT in the first place is to "serve" it's underlying asset through the NFT. The asset is typically a binary file (image, video, 3D-Model, ...).  A major if not the most important functionality in DigitalSoul-Studio is to create, manage and update NFT data, i.e. curate and assign assets to the respective NFTs.
DigitalSoul-NFT revisited (from #4 )

Each NFT is a tuple of (CSN, SLID, ANCHOR). In terms of Database, it is a tuple of (contract_id, slid, anchor)
Within entities of the same contract

Each NFT has 0...M assets.
Each Asset can be assigned to 0...N NFTs

Asset-Upload

Each asset belongs always to the contract, it has been uploaded for and shall not be usable for any other contract
Duplicate assets (in terms of binary files with the same hash) shall not be uploaded twice (the user shall receive a hint it is already uploaded)
The original filename shall be kept internally, but not exposed via public, open APIs.
Assets are uploaded to /srv/app/nftdata and stored with their asset_hash as filename
An asset is (publicly) identified via asset_hash=keccak256([CSN]:keccak256(binaryFile)), so essentially salting the hash of a binary file with the CSN of the contract, the asset is uploaded for

Asset-Serving

There shall be an /asset/0xaaa...bbb endpoint, which serves the binary file as uploaded. 0xaaa...bbb is the asset_hash

Done with #28

Reopening and assigning to @pedrolucasp for File-Upload (outlined below)

Test-Upload:
cujo.jpg

Assuming it belongs to csn=UFCJ, shall the hash according to the formula asset_hash=keccak256([CSN]:keccak256(binaryFile)) should be:

keccak256(cujo.jpg) = 73991d56e952aa7d6f1b4b3f072ee69c3ad5d3a2460ac7fec7469c888f07ff0e
keccak256("UFCJ:73991d56e952aa7d6f1b4b3f072ee69c3ad5d3a2460ac7fec7469c888f07ff0e") = 0bbf8da9310f9ae19e4224dc25a4375d3d412c603467083a3e8dd7540a318d2b

This is available in v0.0.3 (PR #37 )

source: gharchive/issue

repo: authenticvision/digitalsoul

license: MIT

license_type: permissive

license_source: github-api


text:
enhancement: add access_token_expiry_time env variable

What does this PR do?
ACCESS_TOKEN_EXPIRY_TIME env variable can be added in 1h15m15s format.
This setting is used for access_token's and id_token's lifetime.
Default value = 15m (in case of absent value or incorrect value).
May be updated from dashboard interface in Access token section.
Which issue(s) does this PR fix?
Issue
If this PR affects any API reference documentation, please share the updated endpoint references
Update docs PR - url

Thank you @MedvedewEM

source: gharchive/pull-request

authors: MedvedewEM lakhansamani

repo: authorizerdev/authorizer


text:
🛑 Passbolt § automat.passbolt.klub-pratel.cz is down

In f85d326, Passbolt § automat.passbolt.klub-pratel.cz (https://automat.passbolt.klub-pratel.cz) was down:

HTTP code: 502
Response time: 3495 ms

Resolved: Passbolt § automat.passbolt.klub-pratel.cz is back up in 2816ab1.

repo: auto-mat/automat-statuspage


text:
[BUG] Using presets=high_quality fails in tutorial notebook

Bug Report Checklist

[x] I provided code that demonstrates a minimal reproducible example.
[ ] I confirmed bug exists on the latest mainline of AutoGluon via source install.
[x] I confirmed bug exists on the latest mainline of AutoGluon via nightly build.
[ ] I confirmed bug exists on the latest stable version of AutoGluon.

Describe the bug
I am running the time-series tutorial notebook from the documentation, in colab/A100.

Using presets="medium_quality" works fine, but simply changing that single parameter to presets="high_quality" causes the following failure in the prediction step
The node Naive is not in the digraph

Beginning AutoGluon training... Time limit = 600s
AutoGluon will save models to 'autogluon-m4-hourly'
=================== System Info ===================
AutoGluon Version:  1.0.0
Python Version:     3.10.12
Operating System:   Linux
Platform Machine:   x86_64
Platform Version:   #1 SMP PREEMPT_DYNAMIC Sat Nov 18 15:31:17 UTC 2023
CPU Count:          12
GPU Count:          1
Memory Avail:       81.70 GB / 83.48 GB (97.9%)
Disk Space Avail:   169.81 GB / 201.23 GB (84.4%)
===================================================
Setting presets to: high_quality

I suspect this is a simple oversight in the prediction step, since (for diligence' sake) here's the log of models that were trained. Note that Naive is not in the list, so of course it would not be in the digraph:
Models that will be trained: ['SeasonalNaive', 'CrostonSBA', 'NPTS', 'AutoETS', 'DynamicOptimizedTheta', 'AutoARIMA', 'RecursiveTabular', 'DirectTabular', 'DeepAR', 'TemporalFusionTransformer', 'PatchTST']

Expected behavior
Per tutorial, the prediction step should succeed without error.
To Reproduce
See link in intro - this is a tutorial notebook in the repo
Note that I tried this on both the released version 1.0.0 and nightly build -pre. Same error on both
Screenshots / Logs
Included above
Installed Versions
Note that these logs happen to be from the nightly build, but same issue on 1.0.0

INSTALLED VERSIONS
------------------
date                : 2024-03-24
time                : 19:36:17.274823
python              : 3.10.12.final.0
OS                  : Linux
OS-release          : 6.1.58+
Version             : #1 SMP PREEMPT_DYNAMIC Sat Nov 18 15:31:17 UTC 2023
machine             : x86_64
processor           : x86_64
num_cores           : 12
cpu_ram_mb          : 85480.5625
cuda version        : 12.535.104.05
num_gpus            : 1
gpu_ram_mb          : [39924]
avail_disk_size_mb  : 173780

async-timeout       : 4.0.3
autogluon           : None
autogluon.common    : 1.0.0
autogluon.core      : 1.0.0
autogluon.features  : 1.0.0
autogluon.tabular   : 1.0.0
autogluon.timeseries: 1.0.0
boto3               : 1.34.69
catboost            : 1.2.3
fastai              : 2.7.14
gluonts             : 0.14.4
hyperopt            : 0.2.7
imodels             : None
joblib              : 1.3.2
lightgbm            : 4.1.0
lightning           : 2.0.9.post0
matplotlib          : 3.7.1
mlforecast          : 0.10.0
networkx            : 3.2.1
numpy               : 1.25.2
onnxruntime-gpu     : None
orjson              : 3.9.15
pandas              : 2.1.4
psutil              : 5.9.5
pytorch-lightning   : 2.0.9.post0
ray                 : 2.6.3
requests            : 2.31.0
scikit-learn        : 1.4.1.post1
scikit-learn-intelex: None
scipy               : 1.11.4
setuptools          : 67.7.2
skl2onnx            : None
statsforecast       : 1.4.0
statsmodels         : 0.14.1
tabpfn              : None
tensorboard         : 2.15.2
torch               : 2.0.1
tqdm                : 4.66.2
utilsforecast       : 0.0.10
vowpalwabbit        : None
xgboost             : 2.0.3

Interesting. This problem went away once I wiped the colab runtime, not sure why.
If I repro again I will reopen this bug.

repo: autogluon/autogluon


text:
🛑 Ingestion Engine is down

In c8ae34b, Ingestion Engine ($INGESTION_ENDPOINT) was down:

HTTP code: 502
Response time: 73 ms

Resolved: Ingestion Engine is back up in d05f857.

repo: automaticCRM/status-page


text:
test--2-main

Please pull this in!

 Quality gate: Failed
26 Issues

 24 Code issues
 2 Anti-patterns

Details

 Quality gate: Failed
26 Issues

 24 Code issues
 2 Anti-patterns

Details

 Quality gate: Failed
26 Issues

 24 Code issues
 2 Anti-patterns

Details


text:
An option to preserve port numbers in metrics

Is there any way to keep port numbers in metrics instead of converting them to service names (which seems to happen by default)? This would allow aggregation of flows received from exporters that doesn't support bidirectional flows, as well as gathering information based on custom port numbers.

Your request is interesting. I added three new configuration keys in the "Producer" section of the config file to disable the conversion from number to name of ports, protocols and etherType fields. Look at the CONFIG-GUIDE.md file for better explanation.
The only drawback thai I see is that with these options enabled, the db cardinality will increase a lot.

Thank you very much for adding the functionality so promptly. I'm in the middle of testing. Of course cardinality increases, but so far it's within acceptable limits. It seems that I'll be able to replace resource-intensive elk stack with the goflow->gobi->prometheus->grafana flow. It looks promising :)
And one thing that crossed my mind, somehow related. Would it be reasonable to group inbound and outbound flow records into bidirectional flows? In fact, I'm not sure if it is even possible. In theory, matching source and destination addresses and port numbers should be feasible, reducing the number of returned metrics by half. I believe some netflow exporters do this, but rather not the open source ones. Again, however, I'm not exactly sure, would that make sense on the gobi side, or should aggregation like this be left for the prometheus queries.

Hi @innogrey, apologies for the delay.
It's hard to correlate flows without falling in to a specific use case. Could you please describe me your needs more precisely? If we can find a feature that can be useful to anyone, I'll be happy to implement it.
Have you looked over the two examples? May be they aren't close to your use case but they contain several tricks to correlate flows in a bidirectional way, via prom queries.

authors: automixer innogrey

repo: automixer/gobi


text:
3D footprint plots

Currently in the 2D reduced space, the instances in the footprint plots tend to overalp alot. This makes it difficult to see a correlation between the scatter and the footprint plots.
Adding a third dimension (as interactive 3d plot for the html report) could alleviate this problem and give more insights into the cluster of instances.

Introduced in #125

authors: AndreBiedenkapp shukon

repo: automl/CAVE


text:
Strict verification fails with current version of Emacs

When AutoPkg runs the recipe it fails with a strict verification fail
https://github.com/autopkg/48kRAM-recipes/blob/master/Emacs/EmacsForMacOSX.download.recipe

Yes we have this issue als with code signature fails.
EmacsURLProvider: Found URL as https://emacsformacosx.com/emacs-builds/Emacs-27.2-3-universal.dmg
URLDownloader
URLDownloader: Item at URL is unchanged.
URLDownloader: Using existing /srv/autopkg/Cache/local.munki.EmacsForMacOSX/downloads/Emacs_For_Mac_OS_X.dmg
EndOfCheckPhase
CodeSignatureVerifier
CodeSignatureVerifier: Mounted disk image /srv/autopkg/Cache/local.munki.EmacsForMacOSX/downloads/Emacs_For_Mac_OS_X.dmg
CodeSignatureVerifier: Verifying code signature...
CodeSignatureVerifier: Deep verification enabled...
CodeSignatureVerifier: Strict verification enabled...
CodeSignatureVerifier: /private/tmp/dmg.821Tda/Emacs.app: a sealed resource is missing or invalid
CodeSignatureVerifier: file added: /private/tmp/dmg.821Tda/Emacs.app/Contents/MacOS/._Emacs.pdmp
CodeSignatureVerifier: file added: /private/tmp/dmg.821Tda/Emacs.app/Contents/MacOS/libexec-arm64-12/._rcs2log
CodeSignatureVerifier: file added: /private/tmp/dmg.821Tda/Emacs.app/Contents/MacOS/._Emacs-x86_64-10_14.pdmp
CodeSignatureVerifier: file added: /private/tmp/dmg.821Tda/Emacs.app/Contents/MacOS/._Emacs-arm64-12.pdmp
CodeSignatureVerifier: file added: /private/tmp/dmg.821Tda/Emacs.app/Contents/MacOS/libexec-x86_64-10_11/._rcs2log
CodeSignatureVerifier: file added: /private/tmp/dmg.821Tda/Emacs.app/Contents/MacOS/libexec-x86_64-10_14/._rcs2log
CodeSignatureVerifier: file added: /private/tmp/dmg.821Tda/Emacs.app/Contents/MacOS/._Emacs-x86_64-10_11.pdmp
Receipt written to /srv/autopkg/Cache/local.munki.EmacsForMacOSX/receipts/EmacsForMacOSX-receipt-20220105-200706.plist
The following recipes failed:
EmacsForMacOSX.munki
Error in local.munki.EmacsForMacOSX: Processor: CodeSignatureVerifier: Error: Code signature verification failed. Note that all verifications can be disabled by setting the variable DISABLE_CODE_SIGNATURE_VERIFICATION to a non-empty value.

It looks like this was an issue on the developer's end, which is now resolved.
% autopkg run -vvq 'Emacs/EmacsForMacOSX.download.recipe'
Processing Emacs/EmacsForMacOSX.download.recipe...
WARNING: Emacs/EmacsForMacOSX.download.recipe is missing trust info and FAIL_RECIPES_WITHOUT_TRUST_INFO is not set. Proceeding...
EmacsURLProvider
{'Input': {}}
EmacsURLProvider: Found URL as https://emacsformacosx.com/emacs-builds/Emacs-29.4-1-universal.dmg
{'Output': {'url': 'https://emacsformacosx.com/emacs-builds/Emacs-29.4-1-universal.dmg'}}
URLDownloader
{'Input': {'filename': 'EmacsForMacOSX.dmg',
           'url': 'https://emacsformacosx.com/emacs-builds/Emacs-29.4-1-universal.dmg'}}
URLDownloader: No value supplied for prefetch_filename, setting default value of: False
URLDownloader: No value supplied for CHECK_FILESIZE_ONLY, setting default value of: False
URLDownloader: Storing new Last-Modified header: Fri, 02 Aug 2024 21:54:38 GMT
URLDownloader: Storing new ETag header: "603cedb-61eba5faa2380"
URLDownloader: Downloaded ~/Library/AutoPkg/Cache/com.github.48kRAM.autopkg.download.emacsformacosx/downloads/EmacsForMacOSX.dmg
{'Output': {'download_changed': True,
            'etag': '"603cedb-61eba5faa2380"',
            'last_modified': 'Fri, 02 Aug 2024 21:54:38 GMT',
            'pathname': '~/Library/AutoPkg/Cache/com.github.48kRAM.autopkg.download.emacsformacosx/downloads/EmacsForMacOSX.dmg',
            'url_downloader_summary_result': {'data': {'download_path': '~/Library/AutoPkg/Cache/com.github.48kRAM.autopkg.download.emacsformacosx/downloads/EmacsForMacOSX.dmg'},
                                              'summary_text': 'The following '
                                                              'new items were '
                                                              'downloaded:'}}}
EndOfCheckPhase
{'Input': {}}
{'Output': {}}
CodeSignatureVerifier
{'Input': {'input_path': '~/Library/AutoPkg/Cache/com.github.48kRAM.autopkg.download.emacsformacosx/downloads/EmacsForMacOSX.dmg/Emacs.app',
           'requirement': 'identifier "org.gnu.Emacs" and anchor apple generic '
                          'and certificate 1[field.1.2.840.113635.100.6.2.6] '
                          '/* exists */ and certificate '
                          'leaf[field.1.2.840.113635.100.6.1.13] /* exists */ '
                          'and certificate leaf[subject.OU] = "5BRAQAFB8B"',
           'strict_verification': True}}
CodeSignatureVerifier: Mounted disk image ~/Library/AutoPkg/Cache/com.github.48kRAM.autopkg.download.emacsformacosx/downloads/EmacsForMacOSX.dmg
CodeSignatureVerifier: Verifying code signature...
CodeSignatureVerifier: Deep verification enabled...
CodeSignatureVerifier: Strict verification enabled...
CodeSignatureVerifier: /private/tmp/dmg.ITXYhc/Emacs.app: valid on disk
CodeSignatureVerifier: /private/tmp/dmg.ITXYhc/Emacs.app: satisfies its Designated Requirement
CodeSignatureVerifier: /private/tmp/dmg.ITXYhc/Emacs.app: explicit requirement satisfied
CodeSignatureVerifier: Signature is valid
{'Output': {}}
Receipt written to ~/Library/AutoPkg/Cache/com.github.48kRAM.autopkg.download.emacsformacosx/receipts/EmacsForMacOSX.download-receipt-20241224-165107.plist

The following new items were downloaded:
    Download Path
    -------------
    ~/Library/AutoPkg/Cache/com.github.48kRAM.autopkg.download.emacsformacosx/downloads/EmacsForMacOSX.dmg

authors: homebysix stefanj135 undulat

license_source: bigquery


text:
Precommit

Custom and shared processors were updated to be compliant to precommit requirements.

Looks fine, all custom processors show no more errors.

authors: a-vogel jutonium

repo: autopkg/wycomco-recipes


text:
fix(gnss_poser): added local coordinate system in UTM to gnss_poser

Signed-off-by: ataparlar ataparlar@leodrive.ai
Description
In the gnss_poser package, there was no option for working in a local coordinate system for UTM. Added a function to convert.hpp and added "UTMLocal" parameter to the gnss_poser.launch.xml .
Related links
Related with this issue: #1122
Tests performed

Notes for reviewers

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.
[ ] The PR has been properly tested.
[ ] The PR has been reviewed by the code owners.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.
[ ] The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

@mitsudome-r did you hava any chance to review?


text:
One remap is missing, due to which control.py does not work.

The topic
/kraken/control/thruster6pid

has to be remapped to
/kraken/physics_model/forceData6Thruster

and the corresponding four thruster model topics.
References: Comment by @prudhvid
cc @kalyan-kumar @prudhvid @kshitijgoel007 @aniket11bh

@kalyan-kumar My bad. I was talking about this control.py file.

There is some problem in thruster_force_converter, because

/Control node is giving a good data for yaw movement. while /converter is giving a constant output 0 corresponding to the same thrusters as of from /Control node (Check in  rqt graph and data as attached)
-Left part of terminal is from the control.py while right part is from thruster_force_converter

@aniket11bh
As far as I can see, the rqt_graph is exactly as expected by us. This is what is happenning:

IMU value is being taken by the Control node
Some processing happens and the thruster force values are published to /kraken/control/thruster4pid
This is remapped to /kraken/physics_model/forceData4Thruster which is the topic that the simulator takes thruster input from.

The feedback loop is complete. And the basic architecture is setup.
Regarding the data, I am not able to understand what topics each of the terminal screens above correspond to. thruster_force_converter is a package, and not a topic.
cc @kalyan-kumar

@icyflame

'/converter ' is a node which corresponds to 'main.py' in 'thruster_force_converter' package.
Left part of the terminal screen belongs to the data as published by 'control.py' on '/kraken/control/thruster6pid'
Right part of the screen belongs to the data as published by the node '/converter' on '/kraken/physics_model/forceData6Thruster' .
'/converter' which is a node generated by .cpp files (either by 'main.cpp' or by 'ForceConverter.cpp')in 'thruster_force_converter' package


text:
phone-number support

Changes made:

Added a new component for phone number entry. This is the intent moving forward. Everytime a new method is added, the parent component will be the Entry.vue which will contain any common methods and each auth method will have a component of its own with its own logic. The birthdate component will be moved next.
ref is being used for accessing the child's methods.
Until now mutliple IDs were not allowed only if the destination was plio or quiz. Now on, if we are using multiple methods as once, the add button will be disabled as well.

For testing:
sessionId=NEET__62c29f2573d3bb41aa88554d

For SQS, whenever a new data variable needs to logged into BQ, it is being appended to the message and I'm manually adding a new column to the table. For SQS, I'm thinking all the data variables can become an object, so that new variables will become easier to add. For adding a column into the BQ table, I'm not sure how to automate it except to make the data type as JSON. But I guess it's not easy to query such columns.

repo: avantifellows/Portal


text:
MIPS Extending supported instructions

How do I extend the current instruction set in mips?

Take a look at capstone2llvmir library, MIPS module in this case. To support more instructions, their semantics needs to be modeled in LLVM IR = write a routine that takes a Capstone instruction and generates LLVM IR sequence with the same semantics. Also see this discussion. We do not want to have semantics for all the possible instructions, only those that can be represented in C reasonably well (simple and clear code). At the moment, all unhandled instructions are ignored, but we are already working on implementation that will generate pseudo asm calls for them.
What kind of instructions are you interested in? Would pseudo asm calls be enough for you, or do you want complete semantics?

I was thinking of PS2 Mips. I could have sworn I saw a paper by you guys using ps2dev ( A homebrew kit) build and decompile custom elf

You are right. For creating MIPS ELF binaries via GCC, we were using Minimalist PSP homebrew SDK. However, we were interested only in regular MIPS instructions and not in PS2-specific extensions.

Here is the relevant map of instructions that we translate, and those we don't. I'm sure there are many that are simple enough to reasonably represent in LLVM IR and C. As I wrote above, all the others should not be ignored but pseudo asm intrinsic calls should be generated. If you want, you can add semantics for more instructions and send a pull request. But as I also wrote, we are not interested in semantics for complex instructions, so we will not accept PR that would go into implementing such instructions. We can discuss specific instructions (families) that could be added here. And if you are up to it, you can add them, or I can look into it when I will have the time.

Wow thank you so much. I was going to start in a few weeks but this might help me get started sooner

I just merged branch solving #115 and written some info about the translation process on our wiki: https://github.com/avast-tl/retdec/wiki/Capstone2LlvmIr.
The most important change is that unhandled assembly instructions are not ignored anymore. Calls to assembly pseudo functions are auto-generated based on info provided by Capstone. This does not have to be 100% precise, but it is better than nothing. If you have a sample that contain such instructions, try to decompile it with the current master and compare it with the old output. It should be better now, but if you encounter some problems, please report it. I would be very interested how it works on real binaries other than x86 - I did not test it on MIPS much.

I see that you handle unaligned stores (swr/swl) but not unaligned loads (ldl/ldr). It is pretty common in code and would definitely break the decompilation. Any thought on fixing it with an instrincis or something like that?

Feel free to check this as it is based on Capstone as well: https://github.com/nihilus/snowman/tree/master/src/nc/arch/mips

For binaries to test agains use https://github.com/nihilus/snowman-tests

Well, even swr/swl are translated using translatePseudoAsmFncOp0Op1() at the moment. Which is generating a generic pseudo call, which is not ideal. Since loads and stores are pretty important, I will add these instructions (swr/swl, ldl/ldr) to my todo list and look into it - try to write proper translation routines for them if possible.
Thanks for the links, I will look at them.

I went over that Snowman MIPS translation and added semantics for few more MIPS instructions that we were missing. Now we should have pretty much everything that is in Snowman.
However, RetDec translates unaligned load/store instructions (MIPS_INS_LWL, MIPS_INS_LWR, MIPS_INS_SWL, MIPS_INS_SWR, MIPS_INS_LDL, MIPS_INS_LDR, MIPS_INS_SDL, MIPS_INS_SDR) using pseudo function calls (intrinsic-like functions) at the moment. Snowman has full semantics for these. I looked into it and:

It should be possible to translate these reasonably well using load/store instructions and and/or operations.
I'm not sure how beneficial this would be, RetDec would gain knowledge that load/store operation is going on, but user would see potentially confusing bit operations.
In any case, this is not a priority at the moment, and since it would be quite time consuming to model it correctly I decided pseudo functions are good enough for now. If someone comes across a sample where this is a problem, create a dedicated issue.

Contributions extending supported instructions are welcomed, but keep in mind that we don't want to model instructions that are too complicated and their LLVM IR representation would be too complex.

authors: MagnificentS PeterMatula nihilus s3rvac

repo: avast-tl/retdec


text:
Issue #113: Averbis CLI

Added a simple CLI draft

Codecov Report

Merging #114 (d797792) into main (84f0357) will decrease coverage by 6.87%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main     #114      +/-   ##
==========================================
- Coverage   92.03%   85.16%   -6.88%
==========================================
  Files          16       17       +1
  Lines        2008     2170     +162
==========================================
  Hits         1848     1848
- Misses        160      322     +162

Impacted Files
Coverage Δ

cli.py
0.00% <0.00%> (ø)

setup.py
0.00% <ø> (ø)

Continue to review full report at Codecov.

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

authors: codecov-commenter reckart

repo: averbis/averbis-python-api


text:
[Feat]: Amazon Price Tracker:

Is your feature request related to a problem? Please describe.
none
Describe the solution you'd like.
Create a script that allows users to input an Amazon product URL and track its price over time. The script could periodically scrape the product's price and send notifications to the user when the price drops below a certain threshold.
Describe alternatives you've considered.
none
Show us the magic with screenshots
No response
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSoC'23 contributor
[X] I want to work on this issue

/assign

repo: avinashkranjan/Amazing-Python-Scripts


text:
The included example doesn't work

I had to revert 57a8462d5db982c7ff112e46e1f194b39e90819c and 2d12a77ad4cf147964f9c33f852b6bd301a01cf0 to get the example working. I opened a pull request (#11) to fix some of the issues.

This should be fixed and is now tested in CI

authors: avirshup owbear

repo: avirshup/DockerMake


text:
Replace OO-interface of Mojo::JSON with functional interface

As of Mojolicious 5.73 the OO-interface of Mojo::JSON is removed.

Thanks, Mojo::JSON::Pointer also changed the interface.

authors: avkhozov reneeb

repo: avkhozov/test-mojo-session


text:
Add some stacktrace info or some more logs when general error occur

Should stacktrace be printed here?
Otherwise, it will only show 'test 500' in response body and no error info in console or log file.

@dejavuwl as i understand you would be able to see the error in public/log/avored.log file when the 500 error is generate
impl From<std::io::Error> for Error {
    fn from(val: std::io::Error) -> Self {
        error!("there is an issue with creating io error: {val:?}"); // this line will go in the log file.
        Error::Generic("tokio file create folder error ".to_string())
    }

}

Thanks a lot, i found the log in public/log/avored.log.

authors: dejavuwl indpurvesh

repo: avored/avored-rust-cms


text:
Make a solid border a precondition for a valid environmental map

As @irgndsondepp stated the out of bounds checks previously worked by accident because there is always a solid wall in every direction.
We should make a solid border (without gaps) a precondition for a valid environmental map.

Do you suggest to check every environmental map, or would you rather just say everything outside the map array is solid?
What I meant by my comment was that in the test instead of the robot starting in front of a wall, the robot was already inside the wall and tried moving out of the array. So it still couldn't move but the initial position was invalid.
I like the way maps are created and displayed in unit tests and to keep it humanly readable I second adding a check for solid boundaries.
I also added #4 concerning the robot's starting position.

authors: aweisser irgndsondepp

license: mit


text:
Lokalisierung mit @nuxtjs/i18n

https://v8.i18n.nuxtjs.org

https://v8.i18n.nuxtjs.org/guide/lazy-load-translations#basic-usage

Ich habe jetzt ein Projekt bei Transifex für my.awesomeBible erstellt: https://app.transifex.com/awesomebible/myawesomebible/


text:
Reusable apps shouldn't swap the user model

From @febsn on September 3, 2015 13:48
At the moment, django-shop requires swapping in a customized user model. This is not recommended for reusable apps (see https://docs.djangoproject.com/en/dev/topics/auth/customizing/#extending-user).
I suggest creating a separate Customer model that carries all shop-specific data with a nullable OneToOne relationship to the user model. I'll write some tests to demonstrate the functionality and for discussion.
First and foremost: Should I design this for the current deferred model architecture, or already switch to django-swappable models? What are your thoughts?
Copied from original issue: jrief/django-shop#11

I believe that requiring a custom user model is fine, as long as we do not require a specific implementation. IIUC, we only require a user model that has a certain interface. Maybe this should be documented better. However, I am closing this issue for now. We can open a new one if this becomes a problem again.

@febsn proposal has already been implemented with one litte difference: Its a non-nullable 1:1-FK from the Customer to the User. Having a non-nullable key allowed me to keep the programming logic simpler.

authors: jrief rfleschenberg

repo: awesto/django-shop


text:
Custom Transformers only load with absolute path

Describe the bug
To use custom transformers, we can add them to amplify/backend/api/<YOUR_API>/transform.conf.json under the transformers section. The issue is, if the given module doesn't have an absolute path, it will only be loaded if it is located inside of node_modules. If I wrote a custom transformer, and just had it inside my src/ directory, I can't reference it with a relative path, I have to type the absolute path, which is different on each dev machine.
There is a check for an absolute path in the code here. I'm not sure what the reasoning is behind it, but it seems like a strange restriction to not allow the user to make their own transformer without either having to put it into node_modules or provide an absolute path.
For example, transform.conf.json
{
  "transformers": [
    "some-transformer-package",
    "/absolute/path/to/transformer.js",
    "./this/will/not/work/transformer.js"
  ]
}

Amplify CLI Version
4.39.0
Additional context
Also I've found this empty catch here very misleading when trying to debug my custom transformer. It turns out my transformer was failing due to a missing dependency, but this error was never reported, as it just gets swallowed by the empty catch, and the only error output I get is amplify telling me my module can't be imported from my global node_modules.

Hi @half2me 👋 , Thank you for raising this issue.  As @yuth mentioned, this intended use case was to allow publishing custom transformer plugin to npm.
This is a great first issue to work on for a third party contribution.

repo: aws-amplify/amplify-category-api


text:
npm run build works at the CLI but fails when deploying in AWS-Amplify

Environment information
C:\Users\Denise\Documents\amplify-social-room>npx ampx info
System:
  OS: Windows 10 10.0.19045
  CPU: (8) x64 Intel(R) Core(TM) i7-2670QM CPU @ 2.20GHz
  Memory: 1.38 GB / 7.95 GB
Binaries:
  Node: 18.18.0 - C:\Program Files\nodejs\node.EXE
  Yarn: 1.22.22 - ~\AppData\Roaming\npm\yarn.CMD
  npm: 10.8.2 - C:\Program Files\nodejs\npm.CMD
  pnpm: undefined - undefined
NPM Packages:
  @aws-amplify/auth-construct: 1.3.0
  @aws-amplify/backend: 1.2.1
  @aws-amplify/backend-auth: 1.1.3
  @aws-amplify/backend-cli: 1.2.5
  @aws-amplify/backend-data: 1.1.3
  @aws-amplify/backend-deployer: 1.1.0
  @aws-amplify/backend-function: 1.4.0
  @aws-amplify/backend-output-schemas: 1.2.0
  @aws-amplify/backend-output-storage: 1.1.1
  @aws-amplify/backend-secret: 1.1.1
  @aws-amplify/backend-storage: 1.1.2
  @aws-amplify/cli-core: 1.1.2
  @aws-amplify/client-config: 1.3.0
  @aws-amplify/deployed-backend-client: 1.4.0
  @aws-amplify/form-generator: 1.0.1
  @aws-amplify/model-generator: 1.0.5
  @aws-amplify/platform-core: 1.1.0
  @aws-amplify/plugin-types: 1.2.1
  @aws-amplify/sandbox: 1.2.1
  @aws-amplify/schema-generator: 1.2.1
  aws-amplify: 6.6.0
  aws-cdk: 2.157.0
  aws-cdk-lib: 2.157.0
  typescript: 5.6.2
AWS environment variables:
  AWS_NODEJS_CONNECTION_REUSE_ENABLED = 1
  AWS_SDK_LOAD_CONFIG = 1
  AWS_STS_REGIONAL_ENDPOINTS = regional
No CDK environment variables

Data packages
>npm list @aws-amplify/data-construct @aws-amplify/graphql-schema-generator
amplify-vite-react-template@0.0.0 C:\Users\Denise\Documents\amplify-social-room
├─┬ @aws-amplify/backend-cli@1.2.5
│ └─┬ @aws-amplify/schema-generator@1.2.1
│   └── @aws-amplify/graphql-schema-generator@0.9.4
└─┬ @aws-amplify/backend@1.2.1
  └─┬ @aws-amplify/backend-data@1.1.3
    └── @aws-amplify/data-construct@1.10.

Description
'npm run build' runs sucessfully at CLI but fails on AWS Amplify with this error:
172
Completed Backend Build
173
2024-09-11T14:27:11.016Z [INFO]: ## Starting Frontend Build
174
Starting phase: build
175
2024-09-11T14:27:11.017Z [INFO]: # Executing command: npm run build
176
2024-09-11T14:27:11.277Z [INFO]: > amplify-vite-react-template@0.0.0 build
177

tsc && vite build

178
2024-09-11T14:27:14.807Z [INFO]: src/components/Contact/ContactComponent.tsx(5,23): error TS2307: Cannot find module '../../aws-exports.js' or its corresponding type declarations.
179
2024-09-11T14:27:14.885Z [ERROR]: !!! Build failed
180
2024-09-11T14:27:14.885Z [ERROR]: !!! Error: Command failed with exit code 2
181
2024-09-11T14:27:14.885Z [INFO]: # Starting environment caching...
182
2024-09-11T14:27:14.886Z [INFO]: # Uploading environment cache artifact...
183
2024-09-11T14:27:14.950Z [INFO]: # Uploaded environment cache artifact
184
2024-09-11T14:27:14.950Z [INFO]: # Environment caching completed

This may be reproduced by using this github https://github.com/DeniseJames/amplify-social-room to upload and deploy on AWS Amplify.  Unless files in the .gitignore are causing an issue this should be able to run successfully at CLI. I use visual studio code.
Using C:\Users\Denise\Documents\amplify-social-room>npm -v
10.8.2

C:\Users\Denise\Documents\amplify-social-room>node -v
v18.18.0

Hey @DeniseJames, Thanks for raising this. Have you upgraded the @aws-amplify lib version recently?  in the recent Amplify Gen2 version will generate amplify_outputs.json file. can you please check if your src folder and let us know which file does it contain?

@AnilMaktala Thisis my amplify_outputs.json file. My APIs are on east-2, not sure why amplify_outputs chooses east-1:
{
"auth": {
"user_pool_id": "us-east-1_se74eImRp",
"aws_region": "us-east-1",
"user_pool_client_id": "u2j5p2cgq2gqs3ph18m341lhm",
"identity_pool_id": "us-east-1:3eb538d4-e4bd-43d8-a5e1-48f7a4698eea",
"mfa_methods": [],
"standard_required_attributes": [
"email"
],
"username_attributes": [
"email"
],
"user_verification_types": [
"email"
],
"mfa_configuration": "NONE",
"password_policy": {
"min_length": 8,
"require_lowercase": true,
"require_numbers": true,
"require_symbols": true,
"require_uppercase": true
},
"unauthenticated_identities_enabled": true
},
"data": {
"url": "https://s6vxgd7lzbb4to2yptbthleppq.appsync-api.us-east-1.amazonaws.com/graphql",
"aws_region": "us-east-1",
"api_key": "",
"default_authorization_type": "API_KEY",
"authorization_types": [
"AMAZON_COGNITO_USER_POOLS",
"AWS_IAM"
],
"model_introspection": {
"version": 1,
"models": {
"Todo": {
"name": "Todo",
"fields": {
"id": {
"name": "id",
"isArray": false,
"type": "ID",
"isRequired": true,
"attributes": []
},
"content": {
"name": "content",
"isArray": false,
"type": "String",
"isRequired": false,
"attributes": []
},
"createdAt": {
"name": "createdAt",
"isArray": false,
"type": "AWSDateTime",
"isRequired": false,
"attributes": [],
"isReadOnly": true
},
"updatedAt": {
"name": "updatedAt",
"isArray": false,
"type": "AWSDateTime",
"isRequired": false,
"attributes": [],
"isReadOnly": true
}
},
"syncable": true,
"pluralName": "Todos",
"attributes": [
{
"type": "model",
"properties": {}
},
{
"type": "auth",
"properties": {
"rules": [
{
"allow": "public",
"provider": "apiKey",
"operations": [
"create",
"update",
"delete",
"read"
]
}
]
}
}
],
"primaryKeyInfo": {
"isCustomPrimaryKey": false,
"primaryKeyFieldName": "id",
"sortKeyFieldNames": []
}
}
},
"enums": {},
"nonModels": {}
}
},
"version": "1.1"
}

@AnilMaktala I solved the discrepancy by removing aws-exports.js from .gitignore The app deployed

authors: AnilMaktala DeniseJames


text:
Autogenerated files discard previous changes

Describe the bug
Once you use Amplify CLI to add some services, say an API, Amplify will generate a cloudformation-json template to build the stack.
If you are to change something within that template manually and then use the CLI to edit the service, you lose your manual changes
To Reproduce

Add a service through the CLI
Go to the generated cloudformation file
Change something like the description of the stack. Then save.
Use the CLI to edit the service
Go back to your generated cloudformation file, you'll noticed the description you've put earlier has been replaced by the autogenerated one

Expected behavior
I expect Amplify CLI to only target the block it needs to change instead of regenerating the whole file
This is especially painful for team work and code reviewing, especially when we have to inject our customizations directly in the template without going through the CLI

@isbkch  Curious to know which service's CloudFormation you were trying to modify and for which use-case?

repo: aws-amplify/amplify-cli


text:
Feature Request: Provision CodeCommit repository from Amplify project; or, new "Versioning" category

Is your feature request related to a problem? Please describe.
The CLI toolchain works great for the most part, but connecting a newly initialized Amplify project to a CodeCommit repository takes a bit of manual work.
Describe the solution you'd like
I'd like a new category, perhaps called Versioning, that provides a workflow for provisioning a CodeCommit repository using named profiles. This workflow would automatically update package.json to reference the newly provisioned CodeCommit repo, as well as give the option of doing a commit and push on amplify push. Sample workflow:
$ amplify add versioning
$ >Do you have an existing CodeCommit repository? (Y/n)
$ n
$ >Please enter the name of the new CodeCommit repo. (hosting-repo)
$ mycodecommitrepo
$ >Add a reference to the newly provisioned repository to `package.json`? (Y/n)
$ Y

Then, other operations like amplify publish could take additional arguments related to version control.
$ amplify publish -c --versioned --message="modified App.jsx"  -

do git add .,
git commit -m with `--message' argument
if no conflicts: git push and continue with amplify publish operations;
else abort publish with conflict detected warning.

Describe alternatives you've considered
Once the configuration process is completed -- manually provision your CodeCommit repo, manually add to package.json, do a git clone in an empty temporary folder, mv the .git directory to your project's directory, things are mostly smooth sailing. But, since version control and e.g. amplify publish currently have no integration, every amplify publish operation must be followed by a git add, git commit, and git push. It would be nice if amplify publish (for projects with Version category setup) optionally takes a commit message argument and attempts to do a git push before publishing. This would also make it more obvious that you're going to publish changes that conflict with the existing application, since the workflow would see git conflicts before attempting to publish.
Context
Our shop exclusively uses CodeCommit for version control, but extending this proposed category to integrate with other git providers (obviously sans the provisioning step) might make Amplify CLI more useful for shops with pre-existing, non-CodeCommit VCS.

@yuth @jordanranz Upon further reflection, I wonder if there is further opportunity for (unit) testing integration with such a feature. My proposal is flimsy in terms of protection against breaking changes, but if versioning could integrate tests and require that e.g. some or all Jest test suites pass before pushing and publishing, that would greatly reduce the chance of breaking application changes and encourage a future-friendly workflow (e.g. write your tests or your code probably won't pass code review or even a hypothetical .amplifyrc / jest <YourTestingFrameworkHere/> configuration).


text:
Change local amplify project to an already existing one

Please describe which feature you have a question about?
Switching amplify project
Provide additional details
I have a amplify project running locally that is connected to a environment in my aws account, however when creating the project I failed to realize that i could just use my existing project instead
The problem is as follows: In my AWS account i have two apps that have the same name now, one has my frontend deployed from github and is connected to a backend environment called "staging", the project i currently have locally is connected to the other app which has no deployed frontend, but has a backend environment called "dev".
When I now try to swtich my project using amplify init --appId <appId of the app I want to use locally> it will ask me if I want to use an existing enivronemt. Upon choosing "yes" the backend-env that is connected in said app does not show up, instead however my dev backend shows up as the only option. If i choose to create a new env called "staging" I get the "AlreadyExistsException" error.
If the environment already exists then why does it now show up when trying to choose an already existing environment, and how can I fix this?
What AWS Services are you utilizing?
amplify-cli, amplify-vue

Hi @hloriana thanks for responding, I already tried this but this gives me an error saying "You are currently working in the amplify project with Id ..." with the ID of the app that has the "dev" backend

Any idea how to fix this? I'm hesitant to change anything in the team-provider-info.json because I don't want to break anything, if I can fix this problem by changing that file, then what exactly do i need to change in it apart from the appId?

The fix was deleting the entire amplify folder, then pulling again with amplify pull --appId <app Id> --envName <env name>

repo: aws-amplify/amplify-hosting


text:
aws_cognito_identity_pool_id missing in the final aws-exports.js

Before opening, please confirm:

[X] I have checked to see if my question is addressed in the FAQ.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

App Id
NEW_APP
AWS Region
us-east-1
Amplify Hosting feature
Environment variables, Frontend builds
Describe the bug
While documenting the Cognito setup flow for my project documentation I stumbled upon an issue where using CLI for initial setup with social providers fails to include the aws_cognito_identity_pool_id in the final aws-exports.js output.
Below I included the images of choices I made while settings up the environment from scratch.
Funny thing is that last week, when running the wizard,  the final output did include the aws_cognito_identity_pool_id. I didn't document the flow that, but I am sure I was using the social provider auto setup as well, I would it expect to always include the id in the final config object
Expected behavior
Instead of aws-exports looking like this:
const awsmobile = {
  aws_project_region: 'us-east-1',
  aws_cognito_region: 'us-east-1',
  aws_user_pools_id: ':Redacted',
  aws_user_pools_web_client_id: ':Redacted',
  oauth: {
    domain: ':Redacted',
  },
  aws_cognito_username_attributes: ['EMAIL'],
  aws_cognito_social_providers: [],
  aws_cognito_signup_attributes: ['EMAIL'],
  aws_cognito_mfa_configuration: 'OFF',
  aws_cognito_mfa_types: [],
  aws_cognito_password_protection_settings: {
    passwordPolicyMinLength: 8,
    passwordPolicyCharacters: [
      'REQUIRES_LOWERCASE',
      'REQUIRES_UPPERCASE',
      'REQUIRES_NUMBERS',
      'REQUIRES_SYMBOLS',
    ],
  },
  aws_cognito_verification_mechanisms: ['EMAIL'],
}

it should look like (include aws_cognito_identity_pool_id: ':Redacted',:
const awsmobile = {
  aws_project_region: 'us-east-1',
  aws_cognito_region: 'us-east-1',
  aws_user_pools_id: ':Redacted',
  aws_user_pools_web_client_id: ':Redacted',
  aws_cognito_identity_pool_id:
    ':Redacted',
  oauth: {
    domain: ':Redacted',
  },
  aws_cognito_username_attributes: ['EMAIL'],
  aws_cognito_social_providers: [],
  aws_cognito_signup_attributes: ['EMAIL'],
  aws_cognito_mfa_configuration: 'OFF',
  aws_cognito_mfa_types: [],
  aws_cognito_password_protection_settings: {
    passwordPolicyMinLength: 8,
    passwordPolicyCharacters: [
      'REQUIRES_LOWERCASE',
      'REQUIRES_UPPERCASE',
      'REQUIRES_NUMBERS',
      'REQUIRES_SYMBOLS',
    ],
  },
  aws_cognito_verification_mechanisms: ['EMAIL'],
}

Reproduction steps
amplify init
amplify add auth

and afterwards running:
amplify env checkout dev

Build Settings
No response
Log output

# Put your logs below this line

Additional information
No response

Hi @mkbctrl 👋🏽  thanks for raising this issue. I'm transferring this to the Amplify CLI repo for better visibility.

authors: hloriii mkbctrl


text:
chore(release): 0.48.4

0.48.4 (2024-05-28)

Closing PR not changes to be released

authors: amarsjac client-software-ci

repo: aws-deadline/deadline-cloud


text:
feat: Add validation on argocd_applications app name

:bangbang: PLEASE READ THIS FIRST :bangbang:
The direction for EKS Blueprints will soon shift from providing an all-encompassing, monolithic "framework" and instead focus more on how users can organize a set of modular components to create the desired solution on Amazon EKS. We have updated the examples to show how we use the https://github.com/terraform-aws-modules/terraform-aws-eks for EKS cluster and node group creation. We will not be accepting any PRs that apply to EKS cluster or node group creation process. Any such PR may be closed by the maintainers.
We are hitting also the pause button on new add-on creations at this time until a future roadmap for add-ons is finalized. Please do not submit new add-on PRs. Any such PR may be closed by the maintainers.
Please track progress, learn what's new and how the migration path would look like to upgrade your current Terraform deployments. We welcome the EKS Blueprints community to continue the discussion in issue https://github.com/aws-ia/terraform-aws-eks-blueprints/issues/1421
What does this PR do?
Add validation to the var.applications variable used by argocd submodule, which uses the var.argocd_applications variable from the root module. The allowed name of the key is restricted by the same restrictions on kubernetes pod names, since the key is used for the name for the Application object, and the Application uses its name as the prefix of the resulting pod.
🛑 Please open an issue first to discuss any significant work and flesh out details/direction - we would hate for your time to be wasted.
Consult the CONTRIBUTING guide for submitting pull-requests.

Motivation

Resolves https://github.com/aws-ia/terraform-aws-eks-blueprints-addons/issues/87

More

[x] Yes, I have tested the PR using my local account setup (Provide any test evidence report under Additional Notes)
[x] Yes, I have updated the docs for this feature
[ ] Yes, I ran pre-commit run -a with this PR

For Moderators

[ ] E2E Test successfully complete before merge?

Additional Notes
I have tested this locally using the same config that resulted in an error (linked in the related Issue), and I receive the error during the plan phase instead (as intended). Changing the name to test-app passes the validation (also intended).

@catmand00 would you mind opening the same PR in our new addons repo https://github.com/aws-ia/terraform-aws-eks-blueprints-addons when you get a chance - thank you!

repo: aws-ia/terraform-aws-eks-blueprints


text:
chore(maintenance): migrate parameters utility to biome

Summary
Changes

Please provide a summary of what's being changed

This PR migrates the linting and formatting of the Batch Processing utility to use Biome instead of a combination of Eslint and Prettier.

Please add the issue number below, if no issue is present the PR might get blocked and not be reviewed

Issue number: closes #2800

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

Sorry for the double reviews @am29d, I had to fix a couple of Sonar things both here & in the other #2809.
They should both be ready now.


text:
Received 0 SUCCESS signal(s) out of 3. Unable to satisfy 100% MinSuccessfulInstancesPercent requirement

I keep receiving this error the above error along with this error: The following resource(s) failed to create: [ManagerAsg]. . Rollback requested by user. I am unsure of what I should do to deal with this issue.

@alanyee please refer to the new supported mechanism to launch Docker Enterprise on AWS --> https://docs.docker.com/cluster/

authors: alanyee nicolaka

repo: aws-quickstart/quickstart-docker


text:
Added AllowedPattern for RemoteAccessCidr parameter

Issue #, if available:
Description of changes:
Added an AllowedPattern to check the RemoteAccessCidr parameter. It's a required parameter otherwise it will cause an error in CloudFormation
Embedded stack arn:aws:cloudformation:us-east-1:816333157034:stack/vmware-tanzu-application-platform-1-2-ExistingVpcStack-7UAE0RNJB7RV/be9c4d20-0c1e-11ed-b0ef-0ebb957d5521 was not successfully created: The following resource(s) failed to create: [LinuxBastionSshIngressRule, WindowsBastionRdpIngressRule, EKSQSStack].
As remote CIDR is unique to each customer, we cannot provide a secure default without opening remote access to the world.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/do-e2e-tests

Merging per discussion with @satya-dillikar. Thanks @spagno!

Thanks, @spagno for taking care of this.  Thanks @tlindsay42 for merging and push this to AWS QS S3 buckets also.

authors: satya-dillikar spagno tlindsay42


text:
only test against regions supported by cfn-python-lint

Overview
Currently cfn-python-lint exits, instead of raising an exception under some conditions. In these cases exception handling alone doesn't do the job. This PR handles the case where regions defined in tests are not supported by cfn-lint
Testing/Steps taken to ensure quality
executed against various quickstarts.
Notes
Will add a catchall for cfn-lint exiting unexpectedly in a followup pr
Testing Instructions
test against a quickstart that includes an unsupported region like eu-west-3. will provide an error log, but continue to test against all supported regions:
[taskcat] |Queing test => quickstart-fortigate-test-ap-southeast-2
[ERROR  ] :The following regions are not supported by cfn-python-lint and will not be linted {'eu-west-3'}
[ERROR  ] :Lint detected issues for test quickstart-fortigate-test on template quickstart-fortinet-fortigate/templates/create-fortigate.template:
[INFO   ] :    line 39 [W2506] [Check if ImageId Parameters have the correct type] (Parameter FortiGateImageId should be of type
                       [AWS::EC2::Image::Id, AWS::SSM::Parameter::Value<AWS::EC2::Image::Id>])

Previous behavior was to exit 32 with an unformatted error:
[taskcat] |Queing test => quickstart-fortigate-test-ap-southeast-2
Supported regions are ['us-east-1', 'us-east-2', 'us-west-1', 'us-west-2', 'ca-central-1', 'eu-central-1', 'eu-west-1', 'eu-west-2', 'ap-northeast-1', 'ap-northeast-2', 'ap-southeast-1', 'ap-southeast-2', 'ap-south-1', 'sa-east-1']

Missing region fix in https://github.com/awslabs/cfn-python-lint/pull/462

@sshvans sorry, I think test is a bit overloaded in this context. All that will be skipped is the linting, actual taskcat tests will run regardless of linter support.

@sshvans sorry, I think test is a bit overloaded in this context. All that will be skipped is the linting, actual taskcat tests will run regardless of linter support.

Make sense. Thanks! LGTM. 👍

authors: agamzn jaymccon sshvans

repo: aws-quickstart/taskcat


text:
Response with error code 500

Hi Alex,
Thanks for putting this together. I have encountered the following error.
From bitbucket webhook, I get the 500 error code.
I checked the log in cloudwatch, here is the error message:

Can you help point out where I should look? Thanks.
Yang

Hi @yangxxx28 it looks like you are sending a test event that doesn't contain all the information required by the Lambda to connect to the Bitbucket server. Try to test with a real event from Bitbucket.

@alexfrosa I made some code changes to the bitbucket. Here is the webhook event.

I think the event should be able to trigger lambda correctly?

@yangxxx28 the lambda is expecting events of changes to the repo code.

@alexfrosa I did make code changes and pushed to the bitbucket server. Below is the request:
{
"resource": "/",
"path": "/",
"httpMethod": "POST",
"headers": {
"Accept": "/",
"Content-Type": "application/json; charset=UTF-8",
"Host": "t5t3vyclwj.execute-api.ap-southeast-2.amazonaws.com",
"User-Agent": "Atlassian HttpClient 2.1.0 / Bitbucket-7.4.0 (7004000) / Default",
"Via": "1.1 localhost (Apache-HttpClient/4.5.5 (cache))",
"X-Amzn-Trace-Id": "Root=1-5f9231d7-7559a8e27dc3b2fd33409552",
"X-Event-Key": "repo:refs_changed",
"X-Forwarded-For": "52.147.3.51",
"X-Forwarded-Port": "443",
"X-Forwarded-Proto": "https",
"X-Hub-Signature": "sha256=d36d0cf272a14319a926add61d879fcc3ab851e7b24e58a9103f4c0602e5e326",
"X-Request-Id": "13efc8c6-0be4-44f7-949d-5617a5dd31a4"
},
"multiValueHeaders": {
"Accept": [
"/"
],
"Content-Type": [
"application/json; charset=UTF-8"
],
"Host": [
"t5t3vyclwj.execute-api.ap-southeast-2.amazonaws.com"
],
"User-Agent": [
"Atlassian HttpClient 2.1.0 / Bitbucket-7.4.0 (7004000) / Default"
],
"Via": [
"1.1 localhost (Apache-HttpClient/4.5.5 (cache))"
],
"X-Amzn-Trace-Id": [
"Root=1-5f9231d7-7559a8e27dc3b2fd33409552"
],
"X-Event-Key": [
"repo:refs_changed"
],
"X-Forwarded-For": [
"52.147.3.51"
],
"X-Forwarded-Port": [
"443"
],
"X-Forwarded-Proto": [
"https"
],
"X-Hub-Signature": [
"sha256=d36d0cf272a14319a926add61d879fcc3ab851e7b24e58a9103f4c0602e5e326"
],
"X-Request-Id": [
"13efc8c6-0be4-44f7-949d-5617a5dd31a4"
]
},
"queryStringParameters": null,
"multiValueQueryStringParameters": null,
"pathParameters": null,
"stageVariables": null,
"requestContext": {
"resourceId": "06qc5tsqr1",
"resourcePath": "/",
"httpMethod": "POST",
"extendedRequestId": "U1y5rFD5SwMF9fw=",
"requestTime": "23/Oct/2020:01:28:55 +0000",
"path": "/prod",
"accountId": "474830832708",
"protocol": "HTTP/1.1",
"stage": "prod",
"domainPrefix": "t5t3vyclwj",
"requestTimeEpoch": 1603416535442,
"requestId": "06ade38a-518a-4625-828a-aefbb549b162",
"identity": {
"cognitoIdentityPoolId": null,
"accountId": null,
"cognitoIdentityId": null,
"caller": null,
"sourceIp": "52.147.3.51",
"principalOrgId": null,
"accessKey": null,
"cognitoAuthenticationType": null,
"cognitoAuthenticationProvider": null,
"userArn": null,
"userAgent": "Atlassian HttpClient 2.1.0 / Bitbucket-7.4.0 (7004000) / Default",
"user": null
},
"domainName": "t5t3vyclwj.execute-api.ap-southeast-2.amazonaws.com",
"apiId": "t5t3vyclwj"
},
"body": "{"eventKey":"repo:refs_changed","date":"2020-10-23T12:28:54+1100","actor":{"name":"xxx","emailAddress":"xxx@xxxx.xxx.xx","id":266,"displayName":"xxx xxx","active":true,"slug":"xxx","type":"NORMAL","links":{"self":[{"href":"https://bitbucket.xxx.xxx.xx:7990/users/yxio\"}]}},\"repository\":{\"slug\":\"image_python_data_platform\",\"id\":12,\"name\":\"image_python_data_platform\",\"hierarchyId\":\"1756db2651d9f6d65828\",\"scmId\":\"git\",\"state\":\"AVAILABLE\",\"statusMessage\":\"Available\",\"forkable\":true,\"project\":{\"key\":\"ADL\",\"id\":22,\"name\":\"AWS Data Lake","public":false,"type":"NORMAL","links":{"self":[{"href":"https://bitbucket.xxx.xxx.xx:7990/projects/ADL\"}]}},\"public\":false,\"links\":{\"clone\":[{\"href\":\"ssh://git@bitbucket.xxx.xxx.xx:7999/adl/image_python_data_platform.git\",\"name\":\"ssh\"},{\"href\":\"https://bitbucket.xxx.xxx.xx:7990/scm/adl/image_python_data_platform.git\",\"name\":\"http\"}],\"self\":[{\"href\":\"https://bitbucket.xxx.xxx.xx:7990/projects/ADL/repos/image_python_data_platform/browse\"}]}},\"changes\":[{\"ref\":{\"id\":\"refs/heads/master\",\"displayId\":\"master\",\"type\":\"BRANCH\"},\"refId\":\"refs/heads/master\",\"fromHash\":\"993fcd5b758df782d6382a535db9361427757e6a\",\"toHash\":\"ed329b5102bc5ddfb84c97dae4c54320e862fefd\",\"type\":\"UPDATE\"}]}",
"isBase64Encoded": false
}
but the error is still:

Hi @yangxxx28, please check if the Lambda environment variable BITBUCKET_SERVER_URL matches your server URL like https://bitbucket.xxx.xxx.xx:7990. Error 404 means it is not finding the content in the Bitbucket server defined by this environment variable.


text:
Knowing the Way

What is the true path one should follow for VOD? Is it this repo, or is https://github.com/awslabs/video-on-demand-on-aws?

Please use the VOD on AWS solution for running transcoding jobs/transcoding workflows. The repo here is meant to be a tutorial on how to automate MediaConvert jobs. The progress and monitoring tools in this repo can be used in conjunction with your VOD workflows using the VOD on AWS solution.

authors: davidbitton morjoan


text:
feat: New module for Cluster Access Management API on Security

What this PR does / why we need it:
Walkthrough of using Cluster Access Management API replacing aws-auth to provide access to the cluster. The module covers;

Understanding the API
Managing Access
Revoking Cluster Creator access
Migrating aws-auth based identity mappings
Creating granular access

Quality checks

[X] My content adheres to the style guidelines
[ ] 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 @rodrigobersa ! I'm noticing quite a few of the pages have blank terminal sections showing like this:
https://deploy-preview-919--eks-workshop.netlify.app/docs/security/cluster-access-management/managing

Hey @niallthomson !
Yes, I created the whole content o Quip and ported to Git yesterday. I'll fix those issues today.
Also thanks for the tip for the pre-commit fix.

authors: niallthomson rodrigobersa


text:
Don't load all list of Eligible OU's

Describe the bug
When you have lot of OU's the application don't load the full list of OU's
To Reproduce
Steps to reproduce the behavior:

Go to Eligibility policy
Click on OU's
Scroll down
You will not see all the OU's (if you have more then 5)

Expected behavior
See all OU list
Desktop (please complete the following information):

OS: osx 13.5
Browser chrome
Version 115.0.5790.170

Additional context
On aws accounts need to click load more to see all existing OU's look like this is what missing

Not sure how it works for you, but if I understand it right, the problem relies here - https://github.com/aws-samples/iam-identity-center-team/blob/dev/amplify/backend/function/teamgetOUs/src/index.py where the getOUs function is missing pagination and getting values of more than one page (the API returns the first 5 OUs in my case).

I think it works on my side because we don't have more than 5 OUs per "nested" OU.

@tomerr-ma  There is indeed no pagination, than can be improved, but for me it lists more than 5 ous. So probably enough in my case to list them all (nested ous).

@lvthillo thanks for working on this. @tomerr-ma can you confirm that the issue has been fixed by #60

@tawoyinfa
I've just deployed the latest version of TEAM (fc7b6f68) and encountered an issue that causes the UI to crash after a few seconds.
Perhaps brought in by #60, the PR for this Issue.
This is the response to the call that causes the crash
Console: error fetching OUs
{
    "data": {
        "getOUs": null
    },
    "errors": [
        {
            "path": [
                "getOUs"
            ],
            "data": null,
            "errorType": "Lambda:Unhandled",
            "errorInfo": null,
            "locations": [
                {
                    "line": 2,
                    "column": 3,
                    "sourceName": null
                }
            ],
            "message": "'NoneType' object is not iterable"
        }
    ]
}

Lambda logs point to OU pagination:
You specified an invalid value for nextToken. You must get the value from the response to a previous call to the API.

[ERROR] TypeError: 'NoneType' object is not iterable
Traceback (most recent call last):
  File "/var/task/index.py", line 36, in handler
    OUs = listOUs(rootOU[0]['Id'])
  File "/var/task/index.py", line 29, in listOUs
    OUs.extend(getOUs(OU["Id"]))

It appears related to OU pagination: https://github.com/aws-samples/iam-identity-center-team/blob/main/amplify/backend/function/teamgetOUs/src/index.py#L19
A call to list_accounts is made instead of further list_organizational_units_for_parent calls.
I believe this line should instead be:
 response = client.list_organizational_units_for_parent(ParentId=id, NextToken=response["NextToken"])

Happy to open a PR and fix, unless someone gets to it earlier. Just a bit busy the next couple of days.
It might also be worth adding some tests and test coverage requirements to this Solution.
I am not sure how we'd go about this the right way...I am happy to write some if a suggested method is provided.
I do recognise the additional overhead may put people off or be undesirable, so it's a discussion first of all.
As an interesting(?) additional note. The OU that this crashed on didn't actually have additional nested OUs inside, just a lot of accounts. So it seems the NextToken is returned on the ListOrganizationalUnitsForParent even if no child OUs are present.

@andyt10 Yes it should be list_organizational_units_for_parent of course, I made that mistake but for some reason (because of my OU/account structure?) it worked on my organization (with the wrong API call). What if you update that line in your lambda and test again?

What if you update that line in your lambda and test again?
I tested locally before replying here, it returned the list of OUs as expected.

I'm not sure why but it didn't occur to me that I could just edit the lambda in the console and test the full app again till your reply 😄
When I did test this way, the call returned successfully and there were no longer the UI issues.

@andyt10
For me it wasn't failing because I never need the "nextToken" I think. We have 20 OUs or something but they are all in our initial output (without pagination).  I suspect the number of returned OUs in one call might be region-specific.
Still, your last comment below is not super clear to me:
As an interesting(?) additional note. The OU that this crashed on didn't actually have additional nested OUs inside, just a lot of accounts. So it seems the NextToken is returned on the ListOrganizationalUnitsForParent even if no child OUs are present.
Does it still appear with the "fix"?

@lvthillo

Still, your last comment below is not very clear to me:

Apologies for that.
The comment I made was just saying that the NextToken has a value, even if there's no 'next' values to iterate on.
The OU in my AWS Organization that resulted in the error doesn't have any Child OUs, but it reliably always got a NextToken on the ListOrganizationalUnitsForParent call whereas others (also without Child OUs) did not.
The only reason I could think of is it did have a larger number of Accounts inside it (> 30)

Does it still appear with the "fix"?
All OUs in the Organization appear in the TEAM API response, from my cross-checking with the console.

I see you've opened an issue for this, cheers.

Thanks @lvthillo
I can confirm #67 has resolved the issue, and the OU pagination works.
As mentioned above, I don't actually have pages of OUs but I do get a NextToken on one specific OU (that has no children) every time and it seems to handle this case as expected.

authors: andyt10 dimarev-ma lvthillo tawoyinfa tomerr-ma

repo: aws-samples/iam-identity-center-team


text:
the scheduled job failed when the scheduled notebook include modules from same folder

The Scheduled job failed to produce results if the scheduled notebook need to import modules from same folder.
Folder 1
scheduled_notebook
module1.py
module2.py
if my scheduled_notebook needs to read modlue1 and module2 from the same folder, the run will fault with 'Execution using papermill encountered an exception here and stopped: ModuleNotFoundError:.."

Same issue here. Even I put them as site-packages, it still didn't work. Wondering there is a solution.

authors: sunnydgm susuleung

repo: aws-samples/sagemaker-run-notebook


text:
Misleading cloudformation stack name

The statement "From the List of Stacks, select the core stack it should be named something like mod-67b03f2bcecc4faf." is quite misleading as the real name is "serverless-workshop" which is defined in setup section by following guide.
The statement can be found in https://workshop.serverlesscoffee.com/3-web-apps/3-frontends/1-displayapp.html
The stack name was defined in https://workshop.serverlesscoffee.com/0-setup/2-self-hosted.html

This should be fixed now, please reopen if the issue persists

authors: bfreiberg chong-aws

repo: aws-samples/serverless-coffee-workshop


text:
New automatic handling of idle EBS volumes

Issue #, if available:
Description of changes:
Added Trusted Advisor automation to clean up (snapshot and delete) EBS volumes that have not been attached for several day. See README.md for full details.
(miobrien@)
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Underutilized EBS Volumes: Updated copyright in the Cloudformation template; added a warning regarding use of this automation in environments where EBS volumes should not be deleted. Warning appears in the README.md as well as the Description in the CloudFormation template.

repo: aws/Trusted-Advisor-Tools


text:
Invalid sockets not handled in prvSetupConnection

Describe the bug
If SOCKETS_Socket() returns SOCKETS_INVALID_SOCKET prvSetupConnection() will return pdPASS. The MQTT agent will then attempt to connect to a non-existent socket.
System information

STM32
IAR
Windows
v1.4.1
Custom Application

Expected behavior
If SOCKETS_Sockect() returns SOCKETS_INVALID_SOCKET, prvSetupConnection() should return pdFAIL.

Hi @caleb-garrett , you are correct. The MQTT agent should not try to connect if the socket is invalid. We will fix this. Thank yo for pointing this out.

closing this as it is fixed now.

authors: caleb-garrett mradulan

repo: aws/amazon-freertos


text:
[BUG]

Describe the bug
Please first see #3104 as a refrence. Now consider when a force disconnect happens in code (when running), e.g. connected wifi access point is turned off. in this case SOCKETS_Shutdown fails, but SOCKETS_Close does it works correctly. as mentioned in 3104 here, "This matches the shutdown behavior documented here, and is therefore presumably correct. Close actually cleans up the resource, ...".
System information

Hardware board: esp32

Expected behavior
SecureSocketsTransport_Disconnect should return succeessfully if shutdown fails but close succeeds. in fact it should just check for close return value since shutdown  return value is not important.
Solution
i think:
1- SecureSocketsTransport_Disconnect should return closeStatus
2- if 1 is correct, lines below in the function are useless:
       if( ( shutdownStatus != TRANSPORT_SOCKET_STATUS_SUCCESS ) || ( closeStatus != TRANSPORT_SOCKET_STATUS_SUCCESS ) )         {             shutdownStatus = TRANSPORT_SOCKET_STATUS_INTERNAL_ERROR;         }
3- maybe you want to change line below to something else, so it won't be misleading (as user may think the function has failed, although it hasn't)
           LogError( ( "Failed to close connection: SOCKETS_Shutdown call failed. %d", transportSocketStatus ) );
Some notes
@lundinc2 , since you have provided the fix for 3104, you may want to check this
@dipen-1337lab, @jsstrandberg, you may want to check this too.
Regards

@dipen-1337lab

Namaskar @maa1370,

I think you should not set returnStatus to TRANSPORT_SOCKET_STATUS_INTERNAL_ERROR since you do not revert it back to TRANSPORT_SOCKET_STATUS_SUCCESS if SOCKETS_Shutdown() fails.

Yes. Actually, there's no point in setting the returnStatus when SOCKETS_Shutdown() fails because the SOCKETS_Close() always gets called, unconditionally (with reference to my modified code block shared earlier). The success/ failure of SOCKETS_Close() is what really matters. I shall remove that line of code in my application code. Thank you!

I think a problem can only happen if return value of SecureSocketsTransport_Disconnect is used somewhere in code logic to do something special in case disconnect was not successful, and for these cases the return value should be corrected.

The documentation in the transport_secure_sockets.h reads as below for the TransportSocketStatus enum.
TRANSPORT_SOCKET_STATUS_INTERNAL_ERROR,      /**< A call to a system API resulted in an internal error. */

As per my understanding, the TransportSocketStatus enum is provided as an abstraction/ wrapper to the code developer instead of using the actual system API return values, which is a good programming practise. In our context, the TRANSPORT_SOCKET_STATUS_INTERNAL_ERROR return value corresponds to the failure of Shutdown and/ or Close Socket-related APIs.
As long as Close always follows Shutdown ignoring the success/ failure of the latter, I do not feel the need for any code change. Also, as you have rightly mentioned, the User application ought to handle the appropriate return values to avoid an undesired behaviour/ firmware crash.
With that, I would appreciate if Team AFR can provide their say on this discussion.

About LogError if SOCKETS_Shutdown() fails, i think it is somehow misleading as described in first post, and should be at least changed to LogWarn.

Point taken. Thank you, again. Will correct this in my application code as well.
Thanks | Regards,
Dipen

@dipen-1337lab thanks for response.
sorry, you are right, corrected my previous comment (... revert it back to TRANSPORT_SOCKET_STATUS_SUCCESS if SOCKETS_Close succeeds.)

Thanks. It should be correct after #3468 is merged.
feel free to close the issue when you want.


text:
Network Policy Rule on Instance Metadata Endpoint

Hi,
Despite having the following rules in the network policy definition, I've noticed DENY logs. Is there something specific to consider when utilizing the instance metadata endpoint?
Rule:
   # Allow access to instance metadata endpoint
    - ports:
      - port: 80
        protocol: TCP
      to:
      - ipBlock:
          cidr: 169.254.169.254/32
    # Allow internet access
    - ports:
      - port: 443
        protocol: TCP
      to:
      - ipBlock:
          cidr: 0.0.0.0/0
          # Exclude traffic to Kubernetes service IPs and pods
          except:
            - 10.0.0.0/8
            - 172.16.0.0/12
            - 192.168.0.0/16
            - 169.254.169.254/32

Here's an example log entry:
Node: ip-10-0-100-44.ec2.internal;SIP: 10.0.115.28;SPORT: 37758;DIP: 169.254.169.254;DPORT: 80;PROTOCOL: TCP;PolicyVerdict: DENY
Any insights would be appreciated

What is your node agent version? Since I also see you are using except and there was a known issue https://github.com/aws/aws-network-policy-agent/issues/92 which was fixed with v1.0.4. VPC CNI v1.15.1 is released on GitHub: https://github.com/aws/amazon-vpc-cni-k8s/releases/tag/v1.15.1 and contains the agent v1.0.4 image tag.

Hey guys,
@achevuru, I checked. When I describe policyendpoints of the network policy, I can see the IP of the pod in the logs.
@jayanthvn,  I am using the latest version of vpc-cni (v1.15.1) and the agent version is v1.0.4.
Thanks for looking into this with me!

@atilsensalduz not sure if your issue was resolved, but just noting that Network Policy agent v1.0.5 is now available with the latest VPC CNI version, v1.15.3

Hi @jdn5126 , I've updated the vpc-cni version and retested the connectivity, but it's still blocked. Interestingly, when I remove 169.254.169.254/32 from the 'except' block of the 'allow internet' rule, I can access the metadata endpoint. I expected the network policy to allow it with an explicit rule. Any ideas?

@atilsensalduz  Why do we have IMDS IP under except block of the second block>

Ok, I'm referring to IMDS IP being specified both in the allow and except blocks above (i.e.,) the below to block is allowing access to IMDS endpoint over TCP and port 80. So, IMDS endpoint is expected to be allowed for all pods for that port and protocol combo and all other port and protocols will be denied for IMDS anyways. So, we don't need to include IMDS again in the except block for port 443 (in the second to block). Deny always wins...
    - ports:
      - port: 80
        protocol: TCP
      to:
      - ipBlock:
          cidr: 169.254.169.254/32

thanks a bunch @achevuru
"Deny always wins..." I like this quote. I might even consider getting it tattooed! 😄

authors: achevuru atilsensalduz jayanthvn jdn5126

repo: aws/aws-network-policy-agent


text:
Table action buttons should right aligned

Describe the bug
When adding a custom header with action buttons to a Table, the buttons are left aligned. according to the cloudscape style guide, these buttons should be right aligned.
Versions
@aws-northstar/ui@npm:1.1.2
To Reproduce
Code
<Table
      columnDefinitions={columnDefinitions}
      header={
        <Header
          variant="h2"
          info={<Link variant="info">Info</Link>}
          actions={<SpaceBetween direction="horizontal" size="xs">
            <Button disabled={editButtonDisabled}>Secondary button</Button>
            <Button variant="primary">
              Create new tenant
            </Button>
          </SpaceBetween>}
        >
          Tenants
        </Header>}

Expected behavior
Action buttons right aligned
Screenshots

Desktop (please complete the following information):
all
Smartphone (please complete the following information):
all
Additional context
nil

Thanks @adriantadros, Yes, NorthStar renders a Cloudscape Header based  on header props (the content) and actions props. Currently, we do not support info props. If it is required, we can add support on this.

A PR has been created to support more header props. Suggest to use the build-in header so that the counter will be rendered.
After the PR is merged and new version is released, the code can be updated to use build-in header.
<Table
      columnDefinitions={columnDefinitions}
      header='Tenants'
      headerVariant='h2'
      info={<Link variant="info">Info</Link>}
      actions={<SpaceBetween direction="horizontal" size="xs">
            <Button disabled={editButtonDisabled}>Secondary button</Button>
            <Button variant="primary">
              Create new tenant
            </Button>
          </SpaceBetween>}
/>

Thank you

🎉 This issue has been resolved in version @aws-northstar/ui-v1.1.5 🎉
The release is available on:
npm package (@latest dist-tag)
GitHub release
Your semantic-release bot 📦🚀

authors: jessieweiyi mteichtahl

repo: aws/aws-northstar


text:
Upgrade intel cluster checker

Signed-off-by: Tim Lane tilne@amazon.com
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

This PR is currently blocked because by an issue where the cluster checker doesn't recognize the newest Intel python3 version

This PR is currently blocked because by an issue where the cluster checker doesn't recognize the newest Intel python3 version

Upgrading to the latest version of the cluster checker fixed this issue. Ready for review.

repo: aws/aws-parallelcluster


text:
Buffer overflow on init using Msvc address sanitizer

Describe the bug
When initializing the aws api while using the new address sanitizer option in MSVC, I get a trap at this stack:
'Address Sanitizer Error: Global buffer overflow'
 	KernelBase.dll!RaiseException()	Unknown
 	triceLibTest.exe!__vcasan::OnAsanReport(const char * description, const char * report, bool __throw) Line 604	C++
 	triceLibTest.exe!__vcasan::ReportCallback(const char * szReport) Line 325	C++
>	triceLibTest.exe!__asan::ScopedInErrorReport::~ScopedInErrorReport() Line 174	C++
 	triceLibTest.exe!__asan::ReportGenericError(unsigned __int64 pc, unsigned __int64 bp, unsigned __int64 sp, unsigned __int64 addr, bool is_write, unsigned __int64 access_size, unsigned int exp, bool fatal) Line 477	C++
 	triceLibTest.exe!__asan_load4(unsigned __int64 addr) Line 186	C++
 	triceLibTest.exe!hashlittle2(const void * key, unsigned __int64 length, unsigned int * pc, unsigned int * pb) Line 551	C
 	triceLibTest.exe!aws_hash_byte_cursor_ptr(const void * item) Line 976	C
 	triceLibTest.exe!s_hash_for(hash_table_state * state, const void * key) Line 48	C
 	triceLibTest.exe!aws_hash_table_create(aws_hash_table * map, const void * key, aws_hash_element * * p_elem, int * was_created) Line 517	C
 	triceLibTest.exe!aws_hash_table_put(aws_hash_table * map, const void * key, void * value, int * was_created) Line 583	C
 	triceLibTest.exe!s_init_str_to_enum_hash_table(aws_hash_table * table, aws_allocator * alloc, aws_byte_cursor * str_array, int start_index, int end_index, bool ignore_case) Line 200	C
 	triceLibTest.exe!s_headers_init(aws_allocator * alloc) Line 303	C
 	triceLibTest.exe!aws_http_library_init(aws_allocator * alloc) Line 473	C
 	triceLibTest.exe!aws_mqtt_library_init(aws_allocator * allocator) Line 190	C
 	triceLibTest.exe!Aws::Crt::s_initApi(aws_allocator * allocator) Line 40	C++
 	triceLibTest.exe!Aws::Crt::ApiHandle::ApiHandle(aws_allocator * allocator) Line 53	C++

Expected Behavior
aws sdk should initialize under sanitizer address asn mode without buffer overflowing
Current Behavior
Always traps and throws an exception due to the code in lookup3.inl
Reproduction Steps
Exc;lude methods in aws-c-common with a declspec (here's my patch)
diff --git a/include/aws/common/private/lookup3.inl b/include/aws/common/private/lookup3.inl
index 50b269f..d0e8095 100644
--- a/include/aws/common/private/lookup3.inl
+++ b/include/aws/common/private/lookup3.inl
@@ -3,6 +3,12 @@

 #include <aws/common/macros.h>

+#if defined(_WIN32) && __SANITIZE_ADDRESS__
+	#define WIN32_ASN_DECL __declspec(no_sanitize_address)
+#else
+	#define WIN32_ASN_DECL
+#endif
+
 /* clang-format off */

 /*
@@ -200,7 +206,7 @@ and these came close:
  hashlittle() has to dance around fitting the key bytes into registers.
 --------------------------------------------------------------------
 */
-static uint32_t hashword(
+WIN32_ASN_DECL static uint32_t hashword(
 const uint32_t *k,                   /* the key, an array of uint32_t values */
 size_t          length,               /* the length of the key, in uint32_ts */
 uint32_t        initval)         /* the previous hash, or an arbitrary value */
@@ -244,7 +250,7 @@ both be initialized with seeds.  If you pass in (*pb)==0, the output
 (*pc) will be the same as the return value from hashword().
 --------------------------------------------------------------------
 */
-static void hashword2 (
+WIN32_ASN_DECL static void hashword2 (
 const uint32_t *k,                   /* the key, an array of uint32_t values */
 size_t          length,               /* the length of the key, in uint32_ts */
 uint32_t       *pc,                      /* IN: seed OUT: primary hash value */
@@ -309,7 +315,7 @@ acceptable.  Do NOT use for cryptographic purposes.
 -------------------------------------------------------------------------------
 */

-static uint32_t hashlittle( const void *key, size_t length, uint32_t initval)
+WIN32_ASN_DECL static uint32_t hashlittle( const void *key, size_t length, uint32_t initval)
 {
   uint32_t a,b,c;                                          /* internal state */
   union { const void *ptr; size_t i; } u;     /* needed for Mac Powerbook G4 */
@@ -496,7 +502,7 @@ static uint32_t hashlittle( const void *key, size_t length, uint32_t initval)
  * the key.  *pc is better mixed than *pb, so use *pc first.  If you want
  * a 64-bit value do something like "*pc + (((uint64_t)*pb)<<32)".
  */
-static void hashlittle2(
+WIN32_ASN_DECL static void hashlittle2(
   const void *key,       /* the key to hash */
   size_t      length,    /* length of the key */
   uint32_t   *pc,        /* IN: primary initval, OUT: primary hash */
@@ -687,7 +693,7 @@ static void hashlittle2(
  * from hashlittle() on all machines.  hashbig() takes advantage of
  * big-endian byte ordering.
  */
-static uint32_t hashbig( const void *key, size_t length, uint32_t initval)
+WIN32_ASN_DECL static uint32_t hashbig( const void *key, size_t length, uint32_t initval)
 {
   uint32_t a,b,c;
   union { const void *ptr; size_t i; } u; /* to cast key to (size_t) happily */

Possible Solution
We could probably wrap this area with '__declspec(no_sanitize_address)' on windows if this is an ok situation.
Additional Information/Context
No response
AWS CPP SDK version used
1.9.220
Compiler and Version used
Microsoft (R) C/C++ Optimizing Compiler 19.34.31933
Operating System and version
Windows 11 22H2

Could you make a PR with the changes listed above?

authors: TriceyJD jmklix

repo: aws/aws-sdk-cpp


text:
[V4] Change value types on model types to be nullable.

Description
Update the value types for the generated model types and manually written S3 model types to use nullables for value types.
When updating code that was affected by the change I would use the Value property if there was a check like IsSet<name> before accessing the property. In the SDK code itself I used GetValueOrDefault if there was no check. In the tests I generally used Value because the tests were written with the expectation there was a value and if there wasn't a value that would be a bug that shouldn't be hidden by the GetValueOrDefault.
I removed some of the customizations for nullablity but more exists that are tied to collections. I'll remove the rest that make sense to remove as part of that story.
Motivation and Context
This is part of V4 effort to better model behavior and allow users to understand if a value is not set in a service or not.
Testing
Confirmed both the .NET Framework and .NET Solution uber solution files compile. Running all of the tests is delayed till we setup the new CI system for V4.
The PR is kind of large because I wanted the PR to compile which involved pretty much making all of the changes. I broke up the changes into component commits that might make it easier to review.
I did not change collections to use nullables. So we would still use types like List<int> instead of List<int?>. I think the experience if using nullables for all collections would be a pretty bad user experience. I'm going to create a separate story to figure out how to special case the theoretical use case of having collections that could possibly have nullable value types.

For S3, I found a few areas where a non-nullable value type is used. Just going to point them out, I believe some are probably intentional.

ByteRange I believe this is something we created internally, since ScanRange is the closest thing I could find in the model:  Start and End still use the long non-nullable type. Was that intentional?
Expiration -> The POCO uses DateTime for expiryDate and expiryDateUtc
UploadPartRequest -> private bool lastPart
TransferUtilityUploadDirectoryRequest - > private bool disablePayloadSigning.

For S3, I found a few areas where a non-nullable value type is used. Just going to point them out, I believe some are probably intentional.

ByteRange I believe this is something we created internally, since ScanRange is the closest thing I could find in the model:  Start and End still use the long non-nullable type. Was that intentional?
Expiration -> The POCO uses DateTime for expiryDate and expiryDateUtc
UploadPartRequest -> private bool lastPart
TransferUtilityUploadDirectoryRequest - > private bool disablePayloadSigning.

Yes those were intentional because they are not modeled fields from the service they are part of our SDK's logic. I didn't want to change the nullability of fields that are used for SDK logic, just change fields used for serialization.

ByteRange - This was a helper class create the string formatted header value.
Expiration - Similar to ByteRange except used on responses. The constructors make sure there is always a value for the date fields.
lastPart - This is not a modeled fields. The SDK uses it to communicate for subclasses like the encryption client to always communicate when it is the last part.
disablePayloadSigning - Expect, we want the value to default to false to know not to skip disabling payload signing.

authors: normj peterrsongg

repo: aws/aws-sdk-net


text:
When I run the program, the following error appears

{"level":"info","msg":"Couldn't describe resources for region us-east-2: NoCredentialProviders: no valid providers in chain. Deprecated.\n\tFor verbose messaging see aws.Config.CredentialsChainVerboseErrors\n","time":"2021-01-23T17:25:48Z"}

Hi wangfan0524,
It appears you do not have AWS credentials setup on your machine. Please see: https://docs.aws.amazon.com/xray/latest/devguide/xray-daemon.html#xray-daemon-permissions

Hi wangfan0524,
It appears you do not have AWS credentials setup on your machine. Please see: https://docs.aws.amazon.com/xray/latest/devguide/xray-daemon.html#xray-daemon-permissions

repo: aws/aws-xray-daemon


text:
add support to pull image cache from other repo

Issue #, if available:
Description of changes:
This adds support for pulling image cache from additional ecr repos. In our case, this means well pull the cache in prow from the eksa build account, prow jobs.  This should improve the build times slightly, but for a couple of the builds. such as the hook-kernel build, this will greatly improve the time since it will be able to use the cache if nothing change in the code.
That build tho uses multiple build stages.  Our current inline-caching approach only suppports mode=min which means it will only keep the cache for layers that end up in the final image.  There is also a registry option where you can push this cache, and use mode=max to include all stages, to a separate registry/image tag.  When we first implement the inline cache ecr did not support pushing the cache as its own image.  It does now!
This should be pretty safe, worst case is its a cache miss, but I cant think of a case in our flow where this wont continue to work.  Anything building these images that access to the previous latest image with the inline cache should have access to the separate 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
/lgtm

authors: abhay-krishna jaxesn

repo: aws/eks-anywhere-build-tooling


text:
Update release module go.mod

Description of changes:
Just ran go mod tidy to clean it up.
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


text:
Bumped production release number for 1.30

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

/approve
/hold cancel

repo: aws/eks-distro


text:
Generated .tgz file for JavaScript package is not yarn-installable

Describe the bug
When using JSII to generate/package JavaScript packages, the generated filename for the .tgz file is of the form <package-name>@<version>.jsii.tgz for the JavaScript code.  The generated filename for the Python module is, by contrast, <module-name>-<version>.tar.gz.
The JavaScript package file, with the @ sign in the filename is not installable using yarn.  yarn add file:<filename> results in errors during the add/install of the package.
Expected Behavior
Expected behavior is that the .tgz file created by the JavaScript packaging is installable (by filename reference) when using yarn add.
Current Behavior
After building the package file, yarn add fails with messages similar to:
yarn add file:../ncfour/projen-utils/dist/js/projen-utils@0.0.0.jsii.tgz
yarn add v1.22.21
info No lockfile found.
[1/4] Resolving packages...
error Package "file:../ncfour/projen-utils/dist/js/projen-utils" refers to a non-existing file '"/home/tjh/Projects/repos/testing/ncfour/projen-utils/dist/js/projen-utils@0.0.0.jsii.tgz"'.
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.

Reproduction Steps

Build a package using the JSII tools.
Create another project/package and initialize with yarn init
Attempt to install the package into the test project/package using yarn add

Possible Solution
Change the @ character in the generated filename to a - character.
Additional Information/Context
No response
SDK version used
5.3.23
Environment details (OS name and version, etc.)
WSL2 - Ubuntu

I have submitted a PR as a suggested update: https://github.com/aws/jsii/pull/4449 .

I am canceling/closing PR #4449 .
I re-configured my projen projects to use npm rather than yarn ("Classic", v1.x.x) and have found that the package file name works OK when using npm as packageManager.

repo: aws/jsii