text:
Request: Remove dependence on bower

As Ember is moving away from using bower, it would be great if this addon's dependencies could just use npm. Looking through previous commits, it looks like some work was done around this, but as of 3.0.1 running ember install ember-simple-auth-auth0 still adds dependencies to the bower.js file.

Totally agree -- npm/yarn is the way to go.
The good news is that Bower has been fully ousted on the develop branch. The less-good news is there's still one issue (#89) that's blocking us from releasing a new version at the moment. Tricky stuff, but I'm tinkering with a potential workaround.

@XaserAcheron sounds good, thanks!

v3.1.0 is released now, free of Bower dependencies. Should be good to go now!

authors: XaserAcheron andrewcallahan


text:
Please add how to get refresh token

Issue Report
You have to add
extraParameters.Add("scope",  "openid offline_access");
before you call LoginAsync or you will get error "id token not contained in result"
Note the "openid" parameter which is not mentioned anywhere in the documentation.

Sorry for not getting back to you any sooner, these things are always better reported at https://github.com/auth0/auth0-oidc-client-net, which contains the information and documentation for the SDK, beyond just the sample.
However, that doesn't justify the silence here, our sincere apologies.
Noted the feedback, and will see to add something to the docs as your feedback is still valid, even 3 years after reporting it.

source: gharchive/issue

authors: chrisrobertsoncypress frederikprijck

license: MIT

license_type: permissive

license_source: github-api


text:
Synchronous vs Asynchronous

Synchronous
var jwt = require('jsonwebtoken');
var token = jwt.sign({ foo: 'bar' }, 'shhhhh');

Asynchronous
var token = jwt.sign({ foo: 'bar' }, 'shhhhh', function(err, token) {
  console.log(token);
);

I want to know , is it bad to use Synchronous  way , in express js server? is there any benefit with Asynchronous mode? As I think there is no I/O and just CPU usage, So Asynchronous and Synchronous must b same, just syntax is different

If there is no perf difference, why is there an async alternative?

TL;DR; To allow you load keys from filesystem or any other source of ReadStream without blocking event loop. Not to actually perform the signing.
I've been digging into git history and jws implementation to understand why the library provided the async functionality for signing:

Back in 2013, jws implemented streaming for sign/verify: https://github.com/brianloveswords/node-jws/commit/ad80a8ac9fdea2de59b607ea8f556451053af145
In 2015 that was used by this library https://github.com/auth0/node-jsonwebtoken/pull/127 , however, in my opinion, they misunderstood "streaming support" with "async signing".
jws library provides streaming for payload and secret, that way you could load those from the file system or any source that provided a NodeJS stream interface, like we can see in jws: https://github.com/brianloveswords/node-jws/blob/ad80a8ac9fdea2de59b607ea8f556451053af145/test/jws.test.js#L132
On this library we supported both streams until v7.4.3 -> v8.0.0 where we lost compatibility with stream payload ( not known breaking change 🎉 😞, I just updated the migration notes v7 -> v8 ).

Honestly, not sure if that streaming is a desired feature by consumers, we'd need to update the README to make it clear.

@ziluvatar That sounds like some serious coding archaeology... well done! :wink:

license: mit

license_source: bigquery


text:
🛑 Andreas Iten is down

In cc38909, Andreas Iten (https://www.andreasiten.ch) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Andreas Iten is back up in b71b61a.

repo: authentiqdigital/upptime


text:
Specifying environment variables without a prefix

We need to support specifying standard environment variables (e.g. OpenTelemetry).
Right now SpiceDB appends a SPICEDB_ prefix to everything passed in -- rather those values should be specified in the config and the environment variables should reject anything with the prefix.

This is now possible with the new patches field in v1.2.0:
something like:
apiVersion: authzed.com/v1alpha1
kind: SpiceDBCluster
metadata:
  name: dev
spec:
  config:
    datastoreEngine: memory
  secretName: dev-spicedb-config
  patches:
  - kind: Deployment
    patch:
      spec:
        template:
          spec:
            containers:
            - name: dev-spicedb
              env:
                 MY_ENV_VAR: "value"

authors: ecordell jzelinskie

repo: authzed/spicedb-operator


text:
Aggressive postgres instantiation ctx timeout causes intermittent failures in Datastore initialisation

What platforms are affected?
linux
What architectures are affected?
others
What SpiceDB version are you using?
v1.31.0
Steps to Reproduce

Start Spice DB locally with a remote cloud postgres which can take more than 5 second to respond.
Before the initialisation steps can complete the ctx times out very frequently eventhough intermittently

Expected Result
The initialisation should be able to work with slow or remote postgres instances.
It should either be made configurable. Or increased to higher number like 20/30 . As this is the initialisation flow.
The exact line were this is set is below:
https://github.com/authzed/spicedb/blob/4262bfd23266888fdfff5e01a24f76e6d30c98ef/internal/datastore/postgres/postgres.go#L227
Actual Result
The context times out very frequently . An example log below
2024-10-18 15:53:02 {"level":"trace","preshared-keys-count":1,"time":"2024-10-18T10:23:02Z","message":"using gRPC auth with preshared key(s)"} 2024-10-18 15:53:02 {"level":"trace","preshared-key-1-length":13,"time":"2024-10-18T10:23:02Z","message":"preshared key configured"} 2024-10-18 15:53:02 {"level":"info","time":"2024-10-18T10:23:02Z","message":"using postgres datastore engine"} 2024-10-18 15:53:02 {"level":"warn","details-url":"https://spicedb.dev/d/force-custom-plan","plan_cache_mode":"force_custom_plan","time":"2024-10-18T10:23:02Z","message":"defaulting value in Postgres DB URI"} 2024-10-18 15:53:07 {"level":"debug","pgx":{"args":[],"err":"timeout: context deadline exceeded","pid":23643,"sql":"SHOW track_commit_timestamp;","time":645.80925},"time":"2024-10-18T10:23:07Z","message":"Query"} 2024-10-18 15:53:07 {"level":"error","error":"failed to create datastore: timeout: context deadline exceeded","time":"2024-10-18T10:23:07Z","message":"terminated with errors"}

Have added a PR to address the issue. Please do consider. If it needs to be fixed differently please do let me know.
https://github.com/authzed/spicedb/pull/2095

Thanks for reviewing and merging the fix.
Also the workaround of spicedb datastore repair for the pg_dump approach is something we missed when we tried that. Thanks for that information.

repo: authzed/spicedb


text:
🛑 Do Práce na Kole - reg test § test.dopracenakole.cz is down

In b66ed9a, Do Práce na Kole - reg test § test.dopracenakole.cz (https://test.dopracenakole.cz) was down:

HTTP code: 502
Response time: 3930 ms

Resolved: Do Práce na Kole - reg test § test.dopracenakole.cz is back up in 98a84f1 after 17 minutes.

repo: auto-mat/automat-statuspage


text:
🛑 Automat eshop § obchod.auto-mat.cz is down

In 0c5cb3e, Automat eshop § obchod.auto-mat.cz (https://obchod.auto-mat.cz/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Automat eshop § obchod.auto-mat.cz is back up in 326e746.


text:
Fix .label() function in CustomDetectionModel, add Set of Mark

This PR fixes the .label() function in CustomDetectionModel and paves the way for Set of Mark prompting in Autodistill.

Here is some demo code:
from autodistill_gpt_4v import GPT4V
from autodistill.detection import CaptionOntology
from autodistill_segment_anything import SegmentAnything
import supervision as sv

from autodistill.core.custom_detection_model import CustomDetectionModel
import cv2

classes = ["apple", "mango", "banana", "pear", "coconut", "none"]

SAMGPT = CustomDetectionModel(
    detection_model=SegmentAnything(
        CaptionOntology({"apple": "apple", "mango": "mango"})
    ),
    classification_model=GPT4V(
        CaptionOntology({k: k for k in classes}),
        api_key="API_KEY",
        prompt=f"Assign a label to each object. Return a response in 'NUMBER: LABEL' format, new line, etc. You can use the classes {', '.join(classes)}. If a class does not match, say 'None'. Only return the number and label, nothing else.",
    ),
    set_of_mark=True
)

SAMGPT.label("./images", extension=".jpg")

IMAGE = "fruit.jpeg"

results = SAMGPT.predict(IMAGE)

from autodistill.utils import plot
import numpy as np

# print(results)

selected_classes = [i for i in range(len(classes)) if classes[i] != "none"]
results = results[np.isin(results.class_id, selected_classes)]

plot(
    image=cv2.imread("fruit.jpeg"),
    detections=results,
    classes=classes
)

source: gharchive/pull-request

repo: autodistill/autodistill


text:
Tabular Ideas For 2025

Writing down some tabular enhancement ideas I've had towards the end of the year so I don't forget over my vacation :)
Mitigating Overfitting

[ ] Try non-overfitting early stopping LOO-OOF technique

Parallel Fit Mode

[ ] Memory estimate incorrect for RandomForest/ExtraTrees in parallel mode, causing OOM issues. Estimating memory as if 40 estimators instead of total estimators. Should use total estimators instead.
[ ] Can try adjusting memory estimate logic to incorporate available memory when determining cores per fold.
[ ] Add GPU support to parallel mode

Generic Stability Improvements

[ ] Need to add memory estimate for stack/weighted ensemble prior to loading OOF. Need to determine how many model's OOFs are safe to use at a time. Limit to between 5% and 20% of total memory. Debug with Dionis / Helena datasets.

Debugging Improvements

[ ] Compute oracle leaderboard test score for debugging purposes

Other

[ ] Add GPU support to TabPFNMix

@Innixma
I may not be a super-expert, but one more improvement I'd suggest is adding a partial fit/streaming training option for extremely large datasets. This would let AutoGluon train incrementally on data chunks instead of loading everything into memory at once, reducing OOM risks and supporting real-time or streaming scenarios where data arrives continually. This partial fit approach would align well with the existing parallel mode improvements, as it would allow more flexible resource management (CPU/GPU) and seamless scaling when dealing with massive datasets.

One additional imporvement I would like to suggest is adding support for GroupKfold, StratifiedGroupKFold, or more general custom cross-validation strategies.  Currently, Tabular supports groups that are used for K-fold in LeaveOneGroupOut bagging, which can be problematic when the number of groups is large: https://github.com/autogluon/autogluon/issues/2805

One additional improvement I would like to suggest is adding support for GroupKfold, StratifiedGroupKFold, or more general custom cross-validation strategies. Currently, Tabular supports groups that are used for K-fold in LeaveOneGroupOut bagging, but this option does not allow "repeats" and can be problematic when the number of groups is large: https://github.com/autogluon/autogluon/issues/2805

Here are some comments from the top of my head:
Maintenance / Fixes

Better logging and/or an integration into WebUI from AGA to improve UX.
Refactor Tabular fit() docstring/documentation to make it easier for experts to use (and mark expert and non-expert settings). I am explicitly thinking of using expendable boxes as in Admonitions.
Ensure refit works for parallel fit + logic for switching automatically to parallel fit depending on hardware.
Fully supported a scikit-learn interface

Features

GroupKFold and the option to stratify splits based on a custom vector (also for regression) (good callout @wmuhanna)
Missing value indicator as a hyperparameter for non-native nan-handling algorithm
Portfolios with new models via TabRepo 2.0
Per-algorithm feature engineering (following ideas from https://arxiv.org/abs/2407.02112)

Keep this train going!

authors: Innixma Killer3048 LennartPurucker wmuhanna

repo: autogluon/autogluon


text:
Update Issue - Automate_undefined_14594

URL tested: https://accounts.google.com/v3/signin/identifier?continue=https%3A%2F%2Fmail.google.com%2Fmail%2Fu%2F0%2F&emr=1&followup=https%3A%2F%2Fmail.google.com%2Fmail%2Fu%2F0%2F&ifkv=AeZLP98WKaS4-be5URLmdBINMmCYsSNP2yG9-pdJN5l7firuusuDE-bCWZAm_PpPsnyN_o419e6HOA&osid=1&passive=1209600&service=mail&flowName=GlifWebSignIn&flowEntry=ServiceLogin&dsh=S-586477507%3A1734946094475621&ddm=1
Open URL on Browserstack
default description

Property
Value

Browser
Chrome 131.0

Operating System
OS X Ventura

Resolution
1688x792

Screenshot Attached
Screenshot URL

Updated Screenshot Attached


text:
feat(Pipeline): factorize() a pipeline into its possibilities

What does this implement/fix? Explain your changes.
This PR implements a way to quickly factorize a pipeline with choices into individual pipelines where those choices are instead fixed (see image below for example).
The default behavior is to assume we want to create a new child for every child in a Choice and that to create this new pipeline, we just mutate the node and set that as it's only child.
if isinstance(node, Choice):
    possible_choices = [node.mutate(nodes=(child,)) for child in node.children]

There are also avenues for dependancy injection (as there are for things like builders and searchspace parsers). This is because we may allow for custom Node types in the future.
Namely the algorithm works on two assumptions:

There is a predicate factor_by: Callable[[Node], bool] to say if we should split which replaces the isinstance in the snippet above
We update a Node to only refer to a single child with assign_child, this replaces the node.mutate(nodes=(child,)) in the snippet above.

if factor_by(node):
    possible_choices = [assign_child(node.copy(), child) for child in children]

Minimal Example / How should this PR be tested?

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

@LennartPurucker, I've added the features you requested, namely you can now specify a min_depth and max_depth at which factoring will take place. The default behaviour is still to factor everything though.
There's also a test which shows how you can factor by a specific node name which I'll include in the documentation.

repo: automl/amltk


text:
fix(intersection): use constant velocity for smoother reference

fixed the reference velocity to a constant velocity reference as the input to smoother
Signed-off-by: Mamoru Sobue mamoru.sobue@tier4.jp
Description
Changed how to calculate ttc(time-to-colliison) for ego car. The ttc for ego is the predicted passing time for each point on the path, calculated from predicted velocity.
Before this PR ego's predicted velocity was obtained by smoothing this velocity reference.
     x-------------- vmax
    /
   /
  /
v0

So velocity profile was processed doubly toward vmax. As a result velocity profile was underestimated.
In this PR, smoother is applied to constant vmax reference only once.
Related links
Prior PR: https://github.com/autowarefoundation/autoware.universe/pull/1405
Tests performed
The red marker (this polygon is the predicted positions of ego while the object is intersecting with ego's path) does not oscillate a lot.
Before PR:
https://user-images.githubusercontent.com/28677420/187184660-e6d114b2-c609-4b96-b072-4ab35daf41a5.mp4
In this PR:
https://user-images.githubusercontent.com/28677420/187184706-76477161-4aa7-4b90-9434-22032cc55a92.mp4
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.

[X] The PR follows the pull request guidelines.
[X] The PR has been properly tested.
[X] 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.

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

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

checked that the red marker does not oscillate (and passed all related scenario tests)
https://user-images.githubusercontent.com/32741405/188531818-aeaa1586-cc51-4dbb-98f3-6cba40ba55d4.mp4

authors: kyoichi-sugahara soblin


text:
fix(planning): add boolean field so that it can distinguish if the ego will stop

Description
Add boolean field so that it can distinguish if the ego will stop.

Tests performed

[x] PASS CI

Effects on system behavior

Nothing.
Interface changes

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.

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.

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

create another msgs in tier4_planning_msgs.


text:
Promise support on all fields

Hi,
Would be super useful if each field of a record accepted either the type itself or a promise to the type. e.g. given a schema:
type Author {
  id: Int!
  firstName: String
  lastName: String
  posts: [Post] # the list of Posts by this author
}

type Post {
  id: Int!
  title: String
  author: Author
  votes: Int
}

The generated code currently looks like this:
interface IPost {
  __typename: string;
  id: number;
  title: string | null;
  author: IAuthor | null;
  votes: number | null;
}

When using Apollo it would be nice on the server side for the generated IPost interface to look more like:
interface IPost {
  ...
  author: Author | null | Promise<Author | null>;
  ...
}

What would you think of such a change?

sorry, I'm a little confused why it would be a promise. Perhaps I'm missing something.
anyway, in https://github.com/avantcredit/gql2ts/pull/46 i plan to support custom formatting functions, so if you provided something like:
const formatTypeDeclaration = (name: string, type: string) => `${name}: ${type} | Promise<${type}>;

it would definitely be possible
does that work?
I'm hesitant to wrap everything in a promise. that particularly would not work for my use case of this library and I'm sure the use cases of others

Hi Brett,
Your solution for #46 will work great for us!
As for our use case. I'm trying to make objects on the server side that implement these interfaces. Some of the objects that I create can not produce the properties in memory and must make remote calls. e.g. in order to get a post's list of authors I must hit the database.
As such, when I try to implement Post.authors on that type, I can not return the actual type and must return a promise to the type, which prevents me from implementing the generated interfaces. If the generated interface additionally supported Promise<T> then it would be solved!
You could say "well just create a promise to the whole object", but part of the design is that the call for authors should only happen lazily when requested by a particular query.

@eboto i just merged #46 and published it on npm as gql2ts@next
can you make a file like
// overrides.js
const { DEFAULT_TYPE_PRINTER } = require('@gql2ts/language-typescript');

module.exports = {
  default: {
    printType: (type, isNonNull) => {
      const declaration = DEFAULT_TYPE_PRINTER(type, isNonNull);
      return `${declaration} | Promise<${declaration}>`;
    }
  }
}

and run gql2ts as gql2ts {normal parameters} -e ./overrides.js
and let me know if it works for your usecase?

Hey Brett! Thanks for the change. Came across an error while trying it
AssertionError: path must be a string
    at Module.require (module.js:467:3)
    at require (internal/module.js:20:19)
    at run (/app/server/node_modules/gql2ts/dist/index.js:24:28)
    at Object.<anonymous> (/app/server/node_modules/gql2ts/dist/index.js:59:5)

I think this PR will fix the particular problem https://github.com/avantcredit/gql2ts/pull/53

Now I get this error:
Error: Cannot find module '@gql2ts/language-typescript'
    at Function.Module._resolveFilename (module.js:440:15)
    at Function.Module._load (module.js:388:25)
    at Module.require (module.js:468:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (/app/scripts/schema-gen-overrides.js:1:96)

due to the import at the top of overrides.js.
This could be because gql2ts is installed locally, not globally. However I would like to keep it that way.

OK all fixed! This was the final overrides that worked for me:
module.exports = {
  printType: (type, isNonNull) => {
    const declaration = isNonNull ? type : `${type} | null`;
    return `${declaration} | Promise<${type}>`;
  }
};

Giving it a try now for our use case. Thanks for building this. =)

👍 thanks for the PR, planning on adding some testing to the CLI

@eboto just published 1.0.0, can i close this issue?

Yes! Congrats on the big release and thanks for being so responsive & helpful on the issue. Closing it =)

authors: brettjurgens eboto


text:
LOG_TIMEOUT results in arbitrary termination on Windows.

Simply put. LLVMIR2HLL is terminated after LOG_TIMEOUT (retdec-config.py) seconds.
So setting the value to 10 makes the decompilation fail shortly after starting.
Windows 7 Ultimate x64, 96GB RAM.

Hi. LOG_TIMEOUT is an internal setting that is used only when running retdec-decompiler.py with --generate-log, which itself is an internal parameter that should NOT be used by end users (it is not listed when running retdec-decompiler.py --help). Do you use this parameter? If so, simply stop using it an everything should be fine.

As in, the script fails after 300 on windows regardless of the actual status if it's not changed. Which, when working on binaries with a PDB attached, will always fail as it takes too long to analyse ( https://i.imgur.com/mVPiyus.png ). Sidenote; the windows versions doesn't print any output (the stages) until it terminates.

Could you please provide the following information so we can try to reproduce the issue?

Attach the input file that you are trying to decompile. You can ZIP it and upload here.
What command do you use to decompile the file?
Which version of RetDec do you use? E.g. release 3.2 (64b) or a custom build.

repo: avast-tl/retdec


text:
SyntaxError: Cannot use import statement outside a module

I am encountering the above SyntaxError when running ava tests against files which utilize this module. I am using TypeScript + ts-node, which is probably why it complains (see https://github.com/TypeStrong/ts-node/issues/505).
Would it be possible for this module to use a CommonJS require instead of import?

Here's my current workaround (using mockery) until a fix is implemented:
mockery.registerMock('@aveq-research/localforage-asyncstorage-driver', {});

You're right, the NodeJS library code should use require.
I would instead suggest to compile to CommonJS with Babel, as we'd like to use ES6 imports in the original code base.
I've created a PR at #2 that should fix it, but I will wait for @fohletex to check it.

Awesome turnaround time on a PR 👏  looking forward to seeing this release! Thanks for building this helpful module!

Thanks @smithki for this issue. I merged #2 and made a new release to v1.1.0
Have fun! :)

authors: fohletex slhck smithki


text:
[BUG] error when more than one item is drawn

Module Version: v2.0.0
Describe the bug
when the table draws a repeated item, the error occurs and does not add up to the quantity
To Reproduce

Expected behavior
when drawing repeated values that have a formula, the amount should be added
Screenshots

Browser:
App Fvtt
Foundry Version:
9v last version
Game System:
DnD5e

Thank you very much, I'll fix it today.

Bug was much more interesting, thanks for providing screenshots.
Now it should be fixed in https://github.com/averrin/merchant-control/releases/tag/2.1.0
Please reopen the issue if it's not.

authors: averrin rinnocenti

repo: averrin/merchant-control


text:
Binary Search Tree Validation C++

Hi i have added the solution of the above mentioned Problem.
Please Check :)
#354

@avinash201199 Please Check :)

 Why is it showing "Excluded Project" ???
@avinash201199

They are not considering dsa,cp,algorithm repository :(
all the pr will not be considered in hacktoberfest but your contribution will be for lifetime, this will help many students to practice dsa .
Thank you for your contribution :)
you can contribute to other repo


text:
Add new free course in Free courses and certificates

We need to add educba certification course in text section as it has already  been added in .js file.

please assign me this task.


text:
[Feat]: add a python program for sharing file between computers.

Is your feature request related to a problem? Please describe.
add a python program for sharing file between computers.
Describe the solution you'd like.
can share file ussing two computers.
Describe alternatives you've considered.
python
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

@Zedoman shall i work on this?

authors: GriffinAnnshual Zedoman

repo: avinashkranjan/Amazing-Python-Scripts


text:
Web support

This PR depends on #92, which should be merged first.
This resolves #51.
As the URL cannot be changed in Web apps by an external process without restarting the app, attempting to use the stream APIs will result in an UnsupportedError.

@avioli

@avioli

Thank you @hacker1024

Is the package now supporting flutter web?

Is the package now supporting flutter web?

@avioli  please answer this question

I don't think it does. I'm still getting the unsupported error.

I am getting below error
Error: Unsupported operation: As the Web URL cannot be changed without restarting the application, link streams are unimplemented on this platform.

authors: Ahmadre alihabbash avioli daraul hacker1024 kiaxseventh psrcek raviganwal


text:
Adicionar tecnologia ASP NET

Seria interessante um tecnologia ASP NET para poder compartilhar links sobre este assunto.

Pode mandar PR adicionando @pedrofernandesfilho :)

ping @pedrofernandesfilho

@vinicius73, estive estudando um pouco melhor o Git para poder contribuir. E também estava meio corrido por esses dias. Em breve envio PR. Valeu!


text:
Add Embedchain: A useful API tool to create bots

Embedchain: Framework to easily create LLM powered bots over any dataset.
https://github.com/embedchain/embedchain
Suggest adding the following Open source repo as an api tool
Useful for beginners and using less code to generate chatGPT bots.

update: API tools with embedchain #142

repo: awesome-chatgpt/awesome-chatgpt


text:
Glk opaque types

Use structs to represent Glk opaque types, rather than using IntPtr everywhere.
Part of #38.
(@curiousdannii I'd formally request a review but GitHub is being dense again.)

It looks okay, I think. My only concern is whether the new structs will collapse down to IntPtrs for JS interop, or whether they'll be some other object. In other words, whether they're newtypes or wrapper types.
FYI, the supported types for JS interop are listed in a table here: https://learn.microsoft.com/en-us/aspnet/core/client-side/dotnet-interop?view=aspnetcore-7.0#javascript-interop-on-

I've read a little that makes it seem like this kind of record structs are basically newtypes.

I'm not sure in this context. We can do this thing when calling native functions because of how the runtime stores structs (the info that those eight bytes represent, say, a WindowHandle is stored elsewhere, so we can pass a WindowHandle to a native function as if it were a plain IntPtr), but for JS I'd sort of expect it to create a JS object at the transition.
But I guess the WASM/JS implementation of IGlk can unwrap and re-wrap the raw IntPtrs if those are what the JS code expects.

Yes of course! If they won't auto-marshall I can just unwrap them manually. No reason not to merge this PR then.
IntPtrs are only 4 bytes aren't they?

They're the size of a pointer on the platform, so yes, they're 4 bytes on
WebAssembly (at least for now).
Dannii Willis @.***> schrieb am So. 26. Feb. 2023 um
22:28:

Yes of course! If they won't auto-marshall I can just unwrap them
manually. No reason not to merge this PR then.
IntPtrs are only 4 bytes aren't they?
—
Reply to this email directly, view it on GitHub
https://github.com/awlck/frankendrift/pull/40#issuecomment-1445471931,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADC2UMXB2BB7BGHEREY6HLTWZPDGHANCNFSM6AAAAAAVIO3IYA
.
You are receiving this because you authored the thread.Message ID:
@.***>

authors: awlck curiousdannii

repo: awlck/frankendrift


text:
Update to node16 and bump actions core

Hi I'm recreating the PR from here to get rid of the deprecations that are currently shown in GitHub Actions. This should be released until the 31 of May, otherwise every workflow using this action will stop working. See here for the announcement of GitHub.
Issue #, if available:
https://github.com/aws-actions/aws-codebuild-run-build/issues/109
Description of changes:

Updates package.json dep @actions/core to version ^1.10.0
Updates action.yml to node16
Use newest versions of actions themselves

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

[ ] Were any files moved? Moving files changes their URL, which breaks all hyperlinks to the files.

+1 vote to merge this PR and create a new release. TY!

I've released this change in a new version -- v1.0.7
Thanks again!

@taoyong-ty the distributable index.js doesn't seem to be up to date with what should be the current state. In dist/index.js the setOutput function still looks like this:
function setOutput(name, value) {
    command_1.issueCommand("set-output", { name }, value);
}

but the function in @actions/core version 1.10.0 now looks like this:
function setOutput(name, value) {
    const filePath = process.env['GITHUB_OUTPUT'] || '';
    if (filePath) {
        return file_command_1.issueFileCommand('OUTPUT', file_command_1.prepareKeyValueMessage(name, value));
    }
    process.stdout.write(os.EOL);
    command_1.issueCommand('set-output', { name }, utils_1.toCommandValue(value));
}

This causes the warning to still appear. Is there something wrong in the release process? Because the file was at least updated, but not with what is expected.

Ok those were only some formattings from my commit and there is no actual release action. I provided the updated dist/index.js in this PR

authors: patrick-scully-ef snowiow taoyong-ty

repo: aws-actions/aws-codebuild-run-build


text:
Stuck trying to upgrade to Transformer 2

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[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.

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
v16.13.1
Amplify CLI Version
8.0.1
What operating system are you using?
Mac
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
no
Amplify Categories
api
Amplify Commands
push
Describe the bug
Hi, we were trying to upgrade from GraphQL Transformer 1 to 2.
During the initial deploy, we got the error that our security token had expired.
Upon trying to redeploy, we now get this error:
An error occurred during the push operation: ["Index: 0 State: {\"deploy\":\"deploying\"} Message: Parameters: [OpenSearchEBSVolumeGB, OpenSearchStreamBatchSize, OpenSearchAccessIAMRoleName, OpenSearchStreamingLambdaHandlerName, OpenSearchStreamMaximumBatchingWindowInSeconds, OpenSearchInstanceCount, OpenSearchInstanceType, OpenSearchDebugStreamingLambda, OpenSearchStreamingIAMRoleName, OpenSearchStreamingFunctionName, OpenSearchStreamingLambdaRuntime] do not exist in the template"]

Expected behavior
We don't get that error
Reproduction steps
I don't really know how to include this, but:

Upgrade to graphqltransformer2
amplify push
security expiration token error
amplify push

GraphQL schema(s)

# Put schemas below this line

Log output

# Put your logs below this line

Additional information
No response

Hey @CodySwannGT :wave: apologies for the delay here but following up on the email you sent it appears this is now resolved after adjusting the project path(?), and the CLI was copying the Elastic* parameters over from the other environment?
@giulioambrogi are you also encountering the issue where Elastic* parameters are missing after migrating?

Hey @giulioambrogi are you still experiencing this?

Hey @josefaidt.  I started getting this error today.  Amplify version 9.1.0.  We migrated our dev environment to v2 a couple of days ago successfully.  Merged to test and started getting this error.  Can't run amplify push at all and completely stuck.

Managed to solve this with the below steps

download the '#current-cloud-backend.zip' from the deployment s3 bucket.
search and replace 'ElasticSearch' with OpenSearch' in all cloudformation files
had to force the python version to 3.8 as well due to it trying to deploy version 3.6 which AWS does not allow anymore
zip and re-upload/overwrite the '#current-cloud-backend.zip' in the deployment s3 bucket.
run amplify push locally

Hey 👋, Closing this because of inactivity. If you are still experiencing this issue and in need of assistance, please feel free to comment and provide us with any information previously requested by our team members so we can re-open this issue and be better able to assist you.
Thank you!

Experiencing this issue after the amplify pipeline timed out during deployment while adding OpenSearch to our staging environment, it looks like CF continued (the SearchStack exists with a green status), but the amplify S3 bucket does not have the necessary info in it, I keep seeing:
 ["Index: 0 State: {\"deploy\":\"deploying\"} Message: Parameters: [OpenSearchEBSVolumeGB, OpenSearchStreamBatchSize, OpenSearchAccessIAMRoleName, OpenSearchDebugStreamingLambda, OpenSearchStreamingLambdaHandlerName, OpenSearchStreamMaximumBatchingWindowInSeconds, OpenSearchStreamingIAMRoleName, OpenSearchStreamingFunctionName, OpenSearchInstanceCount, OpenSearchStreamingLambdaRuntime, OpenSearchInstanceType] do not exist in the template"]
I can't find any of these terms in the amplify files, I have tried rerunning the pipeline as well as running amplify push --iterative-rollback amplify push --force through the cli with no luck always the same error, it looks like it does not know how to recover.
The environment is stuck in a weird state of half deployed, since the backend finished deploying some things, but not all things, and the frontend did not even start deploying. It would be nice if amplify understood how to recover from these types of timeouts.
Any idea how I can fix this?

@josefaidt Having the same issue after adding @searchable to a model in my dev environment and then merging those changes into staging and amplify pushing that. I'm guessing the original issues occurred because of a network timeout/stability during my push which had my new @searchable in it (the CLI hung and died)?
I checked the current-cloud-backend.zip for both my dev env (working) and staging env (not working) and saw that the staging env is indeed missing all these keys from build/cloudformation-template.json.json:
OpenSearchEBSVolumeGB, OpenSearchStreamBatchSize, OpenSearchAccessIAMRoleName, OpenSearchDebugStreamingLambda, OpenSearchStreamingLambdaHandlerName, OpenSearchStreamMaximumBatchingWindowInSeconds, OpenSearchStreamingIAMRoleName, OpenSearchStreamingFunctionName, OpenSearchInstanceCount, OpenSearchStreamingLambdaRuntime, OpenSearchInstanceType
What should I do here to get my staging env back on track? Is there a way to force re-generate that build/cloudformation-template.json.json file? Should I add the keys manually to my file on staging and zip and upload the current-cloud-backend.zip?

@josefaidt Hey Josef, any pointers from the Amplify team on how to get an environment back from a botched V2 transformer migration as per described by @ssimonsen above? Currently we have some production environments in this corrupted state, where it seems the #current-cloud-backend contains definitions (aka templates) pre-V2 upgrade which is preventing from re-deploying with the above errors.
We have the same issue, and found that replacing the contents of #current-cloud-backend with the latest amplify/backend from the repo and removing all node_module folders work to allow deploying again from the CI/CD pipeline (which does result in CloudFormation stacks getting updated), but we are wary of how this might just be telling Amplify 'the upgrade and deployment went through' and leaving out defined resources from the V2 migration in the environment, so a big unknown-unknown.

@josefaidt @AnilMaktala Having the same issue after adding @searchable to a model in my dev environment and then merging those changes into staging and amplify pushing that. I'm guessing the issue was caused by a network timeout/instability during my push which had my new @searchable in it during which the CLI hung and eventually died?
I checked the current-cloud-backend.zip for both my dev env (working) and staging env (not working) and saw that the staging env is indeed missing all these keys from build/cloudformation-template.json.json:
OpenSearchEBSVolumeGB, OpenSearchStreamBatchSize, OpenSearchAccessIAMRoleName, OpenSearchDebugStreamingLambda, OpenSearchStreamingLambdaHandlerName, OpenSearchStreamMaximumBatchingWindowInSeconds, OpenSearchStreamingIAMRoleName, OpenSearchStreamingFunctionName, OpenSearchInstanceCount, OpenSearchStreamingLambdaRuntime, OpenSearchInstanceType
What should I do here to get my staging env back on track? Is there a way to force re-generate that build/cloudformation-template.json file? Should I add the keys manually to my file on staging and zip and upload the current-cloud-backend.zip?

@ssimonsen This is my situation as well, did you ever recover from it ? Mine is my production environment not working though.

@ibussieres Wish I could tell you there was any easy way to resolve this, I don't remember all the details because I had this issue almost a year ago. The easiest way to recover is to create a new env. For prod, this is obviously difficult, mine was a dev env.
For future iterations, I would recommend always doing the auto deploys from a branch, that way making changes like @searchable won't be impacted by your network connection. Sorry I can't be of more help. Amplify tooling is frustratingly tricky and fickle.

@ibussieres Wish I could tell you there was any easy way to resolve this, I don't remember all the details because I had this issue almost a year ago. The easiest way to recover is to create a new env. For prod, this is obviously difficult, mine was a dev env.
For future iterations, I would recommend always doing the auto deploys from a branch, that way making changes like @searchable won't be impacted by your network connection. Sorry I can't be of more help. Amplify tooling is frustratingly tricky and fickle.

Thanks for the reply.
Funny story, it was deployed from a branch. Didn't prevent the timeout !

@ibussieres I'm very sorry to hear you're also facing this issue. With us it was due to the CLI token expiring in the middle of the V2 migration which left the deployment bucket file in a weird halfway state.
We were able to fix our environments with a very ugly and awkward hack, but it worked and the environments have been fine since.
We took the #current-cloud-backend.zip from another environment (if I remember right, from a V1 environment) and manually, carefully replaced all the references to the environment with the broken/target environment.
After that, it's possible your backend resources (appsync, lambda) might be in a like halfway state between your V1 and V2, which you can address by re-deploying all your resolvers and functions.
For resolvers, do:

Set all your @model directives on the schema.graphql file to be @model(queries: null, mutations: null, subscriptions: null). You can use this regex to find all of them and replace them: @model\([\s\S\n]+?\)
amplify push
Restore the schema @model directives to what you mean them to be
amplify push again. This should re-deploy all resolvers

For lambdas, a simple trick is to add a change to their javascript source file so the amplify CLI picks up the change and marks them for updating. We did it as follows:

Replace exports.handler with exports.handler /**/for all files under amplify/backend/function/ (this is just adding an empty comment which is enough)
Add a comment under any part of the lambda layers you might have
Amplify push and wait for the changes to deploy
Revert the changes (maybe with git reset --hard)
Push again. All lambdas should be updated

Hopefully that would put your environment back in working order. Best of luck. This is a very bad issue on Amplify's part imo.

@josefaidt  @ibussieres I am running into this same issue. I added @searchable to a couple entities, then my token expired mid-push and now my project is broken. Is there a way to fix this?

authors: AnilMaktala CodySwannGT brauliolledo chrislatimer djorgji ibussieres josefaidt mmurraymarsdd ssimonsen

repo: aws-amplify/amplify-category-api


text:
chore: merge main to cdkv2

Description of changes

merge conflicts
changed "amplify-cli-core" in peer dependencies to exact beta version to remove cdkv2 tags from yarn.lock

CDK / CloudFormation Parameters Changed

Issue #, if available

Description of how you validated changes
Checklist

[ ] PR description included
[ ] yarn test passes
[ ] Tests are changed or added
[ ] Relevant documentation is changed or added (and PR referenced)
[ ] New AWS SDK calls or CloudFormation actions have been added to relevant test and service IAM policies
[ ] Any CDK or CloudFormation parameter changes are called out explicitly

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

This has been merged in separate PR.

authors: akshbhu sobolk


text:
feat(generation-transformer): add generation transformer

Description of changes
Amplify GraphQL Generation Transformer
The Amplify GraphQL Generation Transformer is a tool that enables the quick and easy creation of AI-powered Generation routes within your AWS AppSync API. This transformer can be leveraged by using the @generation directive to configure AI models and system prompts for generating content.
Directive Definition
The @generation directive is defined as follows:
directive @generation(
    aiModel: String!,
    systemPrompt: String!,
    inferenceConfiguration: GenerationInferenceConfiguration
) on FIELD_DEFINITION

Features

AI Model Integration: Specify the AI model to be used for generation.
System Prompt Configuration: Define a system prompt to guide the AI's output.
Inference Configuration: Fine-tune generation parameters like max tokens, temperature, and top-p.
Integrates with @auth Directive: Supports existing auth modes like IAM, API key, and Amazon Cognito User Pools.
Resolver Creation: Generates resolvers with tool definitions based on the Query field's return type to interact with the specified AI model.
Bedrock HTTP Data Source Creation: Creates a AppSync HTTP Data Source for Bedrock to interact with the specified AI model.

Examples
Basic Usage
Scalar Type Generation
type Query {
  generateStory(topic: String!): String @generation(
    aiModel: "anthropic.claude-3-haiku-20240307-v1:0",
    systemPrompt: "You are a creative storyteller. Generate a short story based on the given topic."
  )
}

Complex Type Generation
type Recipe {
  name: String!
  ingredients: [String!]!
  instructions: [String!]!
  prepTime: Int!
  cookTime: Int!
  servings: Int!
  difficulty: String!
}

type Query {
  generateRecipe(cuisine: String!, dietaryRestrictions: [String]): Recipe
  @generation(
    aiModel: "anthropic.claude-3-haiku-20240307-v1:0",
    systemPrompt: "You are a professional chef specializing in creating recipes. Generate a detailed recipe based on the given cuisine and dietary restrictions."
  )
}

Advanced Configuration
type Query {
  generateCode(description: String!): String @generation(
    aiModel: "anthropic.claude-3-haiku-20240307-v1:0",
    systemPrompt: "You are an expert programmer. Generate code based on the given description.",
    inferenceConfiguration: {
      maxTokens: 500,
      temperature: 0.7,
      topP: 0.9
    }
  )
}

Limitations

The @generation directive can only be used on Query fields.
The AI model specified must:

be supported by Amazon Bedrock's /converse API
support tool usage

Only the following GraphQL / AppSync scalar types are supported as required properties

Boolean
Int
Float
String
ID
AWSJSON

CDK / CloudFormation Parameters Changed
N/A
Issue #, if available
N/A
Description of how you validated changes

Snapshot tests
E2E tests
Manual testing

Checklist

[x] PR description included
[x] yarn test passes
[x] Tests are changed or added
[ ] ~Relevant documentation is changed or added (and PR referenced)~ Docs PRs are WIP
[x] New AWS SDK calls or CloudFormation actions have been added to relevant test and service IAM policies
[x] Any CDK or CloudFormation parameter changes are called out explicitly

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

----- MARK REVIEW -----


text:
MultiEnv causes dependsOn data in amplify-meta.json to be lost.

Note: If your issue/bug is regarding the AWS Amplify Console service, please log it in the
official AWS Amplify Console forum

Describe the bug
Using Amplify's env checkout, pull or add command loses dependsOn array items.
Consider the use case where your Lambda function needs some information about your Cognito deployment, for this example I picked UserPoolId.
To achieve this you add Cognito's UserPoolId to your Lambda's dependsOn property in amplify-meta.json, and then you reference that in your Lambda's CloudFormation template file as an environment variable so that you can access it in your Lambda function.
Everything works well until you checkout, add or pull an environment which removes your dependsOn item from amplify-meta.json and causes reference errors when pushing:
UPDATE_ROLLBACK_IN_PROGRESS dependsonbug-20190403155855  AWS::CloudFormation::Stack Wed Apr 03 2019 17:33:02 GMT+1100 (Australian Eastern Daylight Time) The following resource(s) failed to update: [functiondependsonbuge1b198d9].
UPDATE_FAILED               functiondependsonbuge1b198d9 AWS::CloudFormation::Stack Wed Apr 03 2019 17:33:00 GMT+1100 (Australian Eastern Daylight Time) Parameters: [authcognitoa6fe1306UserPoolId] do not exist in the template

To Reproduce
Steps to reproduce the behavior:
Losing data to env add:

Run command 'amplify env add test'
Observe missing dependsOn data

Losing data to pull:

Run command 'amplify env pull test'
Observe missing dependsOn data

Losing data to checkout:

Run command 'amplify env checkout test'
Observe missing dependsOn data

Expected behavior
Changes to dependsOn for resources inside amplify-meta.json should be saved to the environment when 'amplify push' is used on that environment.
OR
There should be a way to configure dependencies between CloudFormation template files that MultiEnv supports
Desktop (please complete the following information):

OS: OSX
Browser N/A
CLI version 1.5.0

Steps taken to create the test workspace for reproducing the bug
==== Make a new amplify environment ====
amplify init
? Enter a name for the project dependsOnBug
? Enter a name for the environment test
? Choose your default editor: Visual Studio Code
? Choose the type of app that you're building javascript
? What javascript framework are you using react-native
? Source Directory Path:  src
? Distribution Directory Path: dist
? Build Command:  npm run-script build
? Start Command: npm run-script start
==== Add an Cognito ====
amplify add auth
Using service: Cognito, provided by: awscloudformation
The current configured provider is Amazon Cognito.
Do you want to use the default authentication and security configuration? Yes, use the default configuration.
==== Add an API & Storage ====
amplify add api
? Please select from one of the below mentioned services REST
? Provide a friendly name for your resource to be used as a label for this category in the project: apicaed5a58
? Provide a path (e.g., /items) /items
? Choose a Lambda source Create a new Lambda function
? Provide a friendly name for your resource to be used as a label for this category in the project: dependsonbuge1b198d9
? Provide the AWS Lambda function name: dependsonbuge1b198d9
? Choose the function template that you want to use: CRUD function for Amazon DynamoDB table (Integration with Amazon API Gateway and Amazon DynamoDB)
? Please provide a friendly name for your resource that will be used to label this category in the project: dynamo542a04ca
? Please provide table name: dynamo542a04ca
? What would you like to name this column: test
? Please choose the data type: string
? Would you like to add another column? No
? Please choose partition key for the table: test
? Do you want to add global secondary indexes to your table? No
? Do you want to edit the local lambda function now? No
? Restrict API access No
? Do you want to add another path? No
==== Add some parameters for testing ====
Set dependsonbuge1b198d9-cloudformation-template.json Parameters to
"Parameters": {
		"env": {
			"Type": "String"
		},
		"storagedynamo542a04caName": {
			"Type": "String",
			"Default": "storagedynamo542a04caName"
		},
		"storagedynamo542a04caArn": {
			"Type": "String",
			"Default": "storagedynamo542a04caArn"
		},
		"authcognitoa6fe1306UserPoolId": {
			"Type": "String",
			"Default": "authcognitoa6fe1306UserPoolId"
		}
}

Set dependsonbuge1b198d9-cloudformation-template.json Resources.LambdaFunction.Properties.Environment to
"Environment": {
	"Variables": {
		"ENV": {
			"Ref": "env"
		},
		"UserPoolId": {
			Ref": "authcognitoa6fe1306UserPoolId"
		}
	}
}

Set amplify-meta.json function.dependsonbuge1b198d9.dependsOn[] to
"dependsOn": [
    {
        "category": "storage",
        "resourceName": "dynamo542a04ca",
        "attributes": [
            "Name",
            "Arn"
        ]
    },
    {
        "category": "auth",
        "resourceName": "cognitoa6fe1306",
        "attributes": [
            "UserPoolId"
        ]
    }
]

==== Push to test environment ====
amplify push

@luisvsm You would have to also modify your amplify/backend-config.json file to persist this dependsOn relations to be persisted across multiple environments.

Thanks @kaustavghosh06, just tested and that's sorted my issue.

repo: aws-amplify/amplify-cli


text:
amplify-cli: support separation of bin  and

I tried my patch on another computer with a symlinked dotfile setup and it was unable to find the yarn node_modules due to the __dirname being different from the global folder directory. This is a simpler test (maybe too simple) for whether it was installed by yarn over npm.
In the future it might help to ask if you are using yarn as a flag or question in the CLI. Optionally you can also search both global folders for yarn and npm, ideally only one will return the correct plugins, although it could generate a false positive.
Tested with an npm and yarn global install.
This is the filepath that caused the issue.
globalYarnModulesDirPath => '/Users/dave.garwacke/.config/yarn/global/node_modules',
__dirname => '/Users/dave.garwacke/src/dotfiles/config.dotfile/yarn/global/node_modules/@aws-amplify/cli/src'

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

Looks good. Minor lint nitpick- because of which the testing phase fails in circleci:
lerna ERR! /home/circleci/repo/packages/amplify-cli/src/lib/get-global-prefix.js
lerna ERR!   5:32  error  Trailing spaces not allowed  no-trailing-spaces

@ifyoumakeit
Looks good. Minor lint nitpick- because of which the testing phase fails in circleci:
lerna ERR! /home/circleci/repo/packages/amplify-cli/src/lib/get-global-prefix.js
lerna ERR! 5:32 error Trailing spaces not allowed no-trailing-spaces


text:
Returnhook

Issue #, if available: #748
Description of changes: Adds functionality for callbacks to be implemented by any plugin that amplify supports (both 3rd party and 1st party plugins can be supported with this). This just builds on top of the callback for frontend development and adds support for the categories.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@kaustavghosh06 Fixed. Sorry about that.

How does one access this hook when creating a plugin? Would be great to include it in here Plugins

@derrick3192 We are working on updating the docs but to use it you just need to add this code to your index.js file.
async function onAmplifyCategoryOutputChange(context) {
  //callback code
}

Awesome! Appreciate the replly cheers.


text:
Feature Request: show the Tail (latest) of the function logs in the AWS Amplify console instead of the Head (earliest) of the function logs

Is your feature request related to a problem? Please describe.
It would be more helpful when looking in the AWS Amplify console at the functions list for my project to see the LATEST logs instead of the initial logs as now seen.  Here is what I am currently seeing for my project:

Describe the solution you'd like
I would prefer to see the tail of the logs instead of the head, because stuff that happened most recent is going to be far more important than the initial logs when the project was first created.  Right now it show the first ~1500 lines from when I first build the project 5 months ago, and that is not very helpful.  I am forced to click into cloudwatch to see what I really need.  I would prefer to not have to leave the AWS Amplify console.  Just my 2 cents.

@contractorwolf Thank you for the feedback.  We will add this to our list of feature requests to prioritize.

Seems like it would be an easy change. Plus it would remove the shame of having to see the logs of my initial mistakes from when the project first started, everytime I went there :)

authors: contractorwolf hsspain

repo: aws-amplify/amplify-console


text:
Amplify app build successfuly but dont deploy correctly. It's working perporly for long time.

Before opening, please confirm:

[X] I have searched for duplicate or closed issues and discussions.
[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.

JavaScript Framework
React
Amplify APIs
GraphQL API
Amplify Categories
auth, storage, function, api
Environment information

# Put output below this line

System:
OS: Linux 5.4 Linux Mint 20.2 (Uma)
CPU: (8) x64 Intel(R) Core(TM) i7-1065G7 CPU @ 1.30GHz
Memory: 1.53 GB / 19.36 GB
Container: Yes
Shell: 5.0.17 - /bin/bash
Binaries:
Node: 14.16.0 - ~/.nvm/versions/node/v14.16.0/bin/node
Yarn: 1.22.11 - ~/.nvm/versions/node/v14.16.0/bin/yarn
npm: 6.14.11 - ~/.nvm/versions/node/v14.16.0/bin/npm
Watchman: 20210801.210521.0 - /usr/local/bin/watchman
Browsers:
Chrome: 96.0.4664.45
Firefox: 94.0
npmPackages:
@aws-amplify/api: ^3.2.24 => 3.2.30
@aws-amplify/cli: ^4.45.2 => 4.51.0
@aws-amplify/core: ^3.8.16 => 3.8.22
@babel/core: ^7.13.15 => 7.14.0 (7.9.0)
@babel/plugin-proposal-class-properties: ^7.13.0 => 7.13.0 (7.8.3)
@babel/preset-env: ^7.13.15 => 7.14.1 (7.9.0)
@babel/preset-react: ^7.13.13 => 7.13.13 (7.9.1)
@babel/runtime: ^7.13.9 => 7.14.0 (7.9.0)
@date-io/date-fns: ^1.3.6 => 1.3.13
@material-ui/core: ^4.11.2  => 4.12.3
@material-ui/icons: ^4.11.2 => 4.11.2
@material-ui/lab: ^4.0.0-alpha.57 => 4.0.0-alpha.58
@material-ui/pickers: ^3.2.10 => 3.3.10
@material-ui/styles: ^4.10.0 => 4.11.4
amazon-chime-sdk-component-library-react: ^2.9.1 => 2.9.1
amazon-chime-sdk-js: ^2.16.1 => 2.16.1
ant-design-draggable-modal: 0.0.16 => 0.0.16
autosuggest-highlight: ^3.1.1 => 3.1.1
aws-amplify: ^3.3.21 => 3.3.27
aws-sdk: ^2.854.0 => 2.900.0 (2.785.0)
axios: ^0.19.0 => 0.19.2 (0.21.1)
axios-mock-adapter: ^1.17.0 => 1.19.0
babel-loader: ^8.2.2 => 8.2.2 (8.1.0)
babel-polyfill: ^6.26.0 => 6.26.0
bulma: ^0.9.2 => 0.9.2
bulma-helpers: ^0.3.12 => 0.3.12
chart.js: ^2.9.4 => 2.9.4
classnames: ^2.2.6 => 2.3.1
clean-webpack-plugin: ^4.0.0-alpha.0 => 4.0.0-alpha.0
clsx: ^1.0.4 => 1.1.1
compress.js: ^1.1.2 => 1.1.2
copy-webpack-plugin: ^8.1.1 => 8.1.1
cross-env: ^5.2.0 => 5.2.1
css-loader: ^5.2.1 => 5.2.4 (3.4.2)
cypress: ^7.3.0 => 7.3.0
date-fns: ^2.18.0 => 2.21.1 (1.30.1)
downshift: ^3.2.10 => 3.4.8
echarts: ^4.2.1 => 4.9.0
echarts-for-react: ^2.0.15-beta.0 => 2.0.16
eslint-config-airbnb: ^18.2.1 => 18.2.1
eslint-config-prettier: ^8.3.0 => 8.3.0
eslint-plugin-cypress: ^2.11.3 => 2.11.3
eslint-plugin-import: ^2.22.1 => 2.22.1 (2.20.1)
eslint-plugin-jsx-a11y: ^6.4.1 => 6.4.1 (6.2.3)
eslint-plugin-prettier: ^3.4.0 => 3.4.0
eslint-plugin-react: ^7.21.5 => 7.23.2 (7.19.0)
eslint-plugin-react-hooks: ^4.2.0 => 4.2.0 (1.7.0)
file-loader: ^6.2.0 => 6.2.0 (4.3.0)
gh-pages: ^2.1.1 => 2.2.0
graphql: ^15.4.0 => 15.5.0 (14.0.0, 14.7.0)
graphql-tag: ^2.11.0 => 2.12.4 (2.10.1)
history: ^4.10.0 => 4.10.1
html-webpack-plugin: ^5.3.1 => 5.3.1 (4.0.0-beta.11)
lodash: ^4.17.15 => 4.17.21 (4.17.15, 4.17.20)
material-design-icons: ^3.0.1 => 3.0.1
material-design-icons-iconfont: ^6.1.0 => 6.1.0
material-icons: ^0.5.3 => 0.5.5
material-ui-phone-number: ^2.2.6 => 2.2.6
memo-parser:  0.2.1
mini-css-extract-plugin: ^1.4.1 => 1.6.0 (0.9.0)
moment: ^2.29.1 => 2.29.1
moment-timezone: ^0.5.33 => 0.5.33 (0.5.27)
new-plugin-package:  1.0.0
node-sass: ^4.14.1 => 4.14.1
notistack: ^0.8.8 => 0.8.9
pdf-viewer-reactjs: ^2.1.2 => 2.2.3
prettier: 2.3.0 => 2.3.0 (1.19.1)
prettier-eslint: ^12.0.0 => 12.0.0 (9.0.2)
prettier-eslint-cli: ^5.0.0 => 5.0.1
prettier-plugin-apex: 1.9.1 => 1.9.1
prop-types: ^15.7.2 => 15.7.2
react: ^17.0.1 => 17.0.2 (16.14.0)
react-autosuggest: ^9.4.3 => 9.4.3
react-beforeunload: ^2.5.2 => 2.5.2
react-big-calendar: ^0.30.0 => 0.30.0
react-chartjs-2: ^2.11.1 => 2.11.2
react-dom: ^16.13.1 => 16.14.0
react-draggable: ^4.4.3 => 4.4.3
react-helmet: ^5.2.1 => 5.2.1
react-highlight: ^0.12.0 => 0.12.0
react-idle-timer: ^4.6.4 => 4.6.4
react-jitsi: ^1.0.4 => 1.0.4
react-loadable: ^5.5.0 => 5.5.0
react-material-ui-form-validator: ^2.0.9 => 2.1.4
react-new-window: ^0.1.3 => 0.1.3
react-perfect-scrollbar: ^1.5.2 => 1.5.8
react-quill: ^1.3.3 => 1.3.5
react-redux: ^7.2.2 => 7.2.4
react-resizable: ^1.11.0 => 1.11.1
react-rnd: ^10.3.3 => 10.3.3
react-router-config: ^5.0.1 => 5.1.1
react-router-dom: ^5.2.0 => 5.2.0
react-scripts: ^3.4.1 => 3.4.4
react-select: ^3.0.4 => 3.2.0
react-vis: ^1.11.7 => 1.11.7
recharts: ^1.6.2 => 1.8.5
redux: ^4.0.4 => 4.1.0
redux-logger: ^3.0.6 => 3.0.6
redux-persist: ^6.0.0 => 6.0.0
redux-persist/integration/react:  undefined ()
sass-loader: ^11.0.1 => 11.0.1 (8.0.2)
shortid: ^2.2.14 => 2.2.16
style-loader: ^2.0.0 => 2.0.0 (0.23.1)
styled-components: ^5.3.1 => 5.3.1
styled-components/macro:  undefined ()
styled-components/native:  undefined ()
styled-components/primitives:  undefined ()
styled-system: ^5.1.5 => 5.1.5
swiper: ^4.5.0 => 4.5.1
webpack: ^5.32.0 => 5.36.2 (4.42.0)
webpack-cli: ^4.6.0 => 4.6.0
webpack-dev-server: ^3.11.2 => 3.11.2 (3.11.0)
npmGlobalPackages:
@aws-amplify/cli: 7.5.4
@nestjs/cli: 8.1.4
aws-cdk: 1.132.0
create-js-project: 1.0.0
expo-cli: 4.5.2
ffmpeg-concat: 1.3.3
generator-jhipster-react-native: 4.2.0
generator-jhipster: 7.1.0
gtop: 1.1.1
npm: 6.14.11
react-native-cli: 2.0.1
serve: 12.0.1
typescript: 4.4.4
yarn: 1.22.11

Describe the bug
Our application is a react web application.it was working properly.
I another branch from the main branch we applied Nextjs so all branch's environment deploys failed.
We rolled back this branch and deleted it but didn't fixed it.
We cleared deploy and build cache also created a new environment but didn't resolve it.
Expected behavior
After a successful build, it should deploy correctly.
Reproduction steps
You can redeploy a failed deploy in the build history.
Code Snippet
// Put your code below this line.

Log output

// Put your logs below this line

aws-exports.js
/* eslint-disable */
// WARNING: DO NOT EDIT. This file is automatically generated by AWS Amplify. It will be overwritten.
const awsmobile = {
"aws_project_region": "ca-central-1",
"aws_cognito_identity_pool_id": "ca-central-1:8eb165f8-534b-4542-892b-f620cfc79f8b",
"aws_cognito_region": "ca-central-1",
"aws_user_pools_id": "ca-central-1_upEtyW5jh",
"aws_user_pools_web_client_id": "5of3ee07dfinqeohhg6vkdd6cb",
"oauth": {},
"aws_cognito_login_mechanisms": [
"PREFERRED_USERNAME"
],
"aws_cognito_signup_attributes": [
"EMAIL"
],
"aws_cognito_mfa_configuration": "OFF",
"aws_cognito_mfa_types": [
"SMS"
],
"aws_cognito_password_protection_settings": {
"passwordPolicyMinLength": 8,
"passwordPolicyCharacters": []
},
"aws_cognito_verification_mechanisms": [
"EMAIL"
],
"aws_user_files_s3_bucket": "vidkids-new100528-stage",
"aws_user_files_s3_bucket_region": "ca-central-1",
"aws_appsync_graphqlEndpoint": "https://jklasb3lqvgejftrccq6aguxx4.appsync-api.ca-central-1.amazonaws.com/graphql",
"aws_appsync_region": "ca-central-1",
"aws_appsync_authenticationType": "AMAZON_COGNITO_USER_POOLS",
"aws_cloud_logic_custom": [
{
"name": "VidkidsFilesApi",
"endpoint": "https://kpmroqicea.execute-api.ca-central-1.amazonaws.com/stage",
"region": "ca-central-1"
}
]
};
export default awsmobile;
Manual configuration
No response
Additional configuration
No response
Mobile Device
No response
Mobile Operating System
No response
Mobile Browser
No response
Mobile Browser Version
No response
Additional information and screenshots
2021-11-30T20:15:30 [INFO]: Beginning deployment for application dmzn15fe65z58, branch:main, buildId 0000000044
2021-11-30T20:15:30 [INFO]: Cannot find any generated SSR resources to deploy. If you intend for your app to be SSR, please check your app Service Role permissions. Otherwise, please check out our docs on how to setup your app to be detected as SSG (https://docs.aws.amazon.com/amplify/latest/userguide/server-side-rendering-amplify.html#deploy-nextjs-app)
2021-11-30T20:15:30 [ERROR]: {"code":"7","message":"No ssrResources.json file"}

Hi @MjdBh 👋🏽 Can you check your build settings to make sure the baseDirectory is set to build? If it's set to .next or out then Amplify will treat your app as an SSR app which can cause deployment to fail if your application isn't SSR.

HI, @hloriana  thank you for your response.
Yes, the base directory is correct. we rolled back any changes and didn't change the main branch.
But all environment deploy failed.

@MjdBh try following this FAQ guide to change from SSR to SSG: https://github.com/aws-amplify/amplify-console/blob/main/FAQ.md#convert-an-ssr-app-to-ssg. It should tell Amplify to build a static site and not look for SSR resources to generate.

The problem is it. We didn't change this env to SSR.  we tested on other environments and another branch why why our main branch has this issue.

@MjdBh what is your AppID and region?

@shubhadip I used the following command and it worked for me.

authors: MjdBh hloriana


text:
Redirect setup for static generated + SPA sites

** Please describe which feature you have a question about? **
Rewrites and redirects
** Provide additional details**
The issue #70 should either be opened again and fixed or the workaround should be reflected in the documentation here
I can confirm that setting </index\.html/> => /404.html [404 Rewrite] is resulting in the desired behavior and does not lead to the mentioned side-effect for us.

Hi @FelixRe0 so you are no longer experiencing any issues with your 404 rewrite rule, is that correct?

@Athena96 Yes that's correct. We could not identify any issue yet.

Closing this ticket.  Please let us know if you have further issues.


text:
chore: update CocoaPods to version 1.11.3

Description of changes:
Update CocoaPods to version 1.11.3
Check points: (check or cross out if not relevant)

[ ] Added new tests to cover change, if needed
[x] Build succeeds with all target using Swift Package Manager
[x] All unit tests pass
[x] All integration tests pass
[ ] Documentation update for the change if required
[x] PR title conforms to conventional commit style
[ ] If breaking change, documentation/changelog update with migration instructions

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

Codecov Report

Merging #1695 (1b3f389) into main (7175f6f) will decrease coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #1695      +/-   ##
==========================================
- Coverage   59.09%   59.07%   -0.02%
==========================================
  Files         716      716
  Lines       21856    21856
==========================================
- Hits        12915    12912       -3
- Misses       8941     8944       +3

Flag
Coverage Δ

API_plugin_unit_test
62.51% <ø> (ø)

AWSPluginsCore
71.37% <ø> (+0.07%)
:arrow_up:

Amplify
46.82% <ø> (-0.06%)
:arrow_down:

Analytics_plugin_unit_test
71.76% <ø> (ø)

Auth_plugin_unit_test
78.74% <ø> (ø)

DataStore_plugin_unit_test
75.56% <ø> (-0.02%)
:arrow_down:

Geo_plugin_unit_test
52.12% <ø> (ø)

Predictions_plugin_unit_test
26.81% <ø> (ø)

Storage_plugin_unit_test
58.04% <ø> (ø)

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

Impacted Files
Coverage Δ

...s/AWSHubPlugin/Internal/HubChannelDispatcher.swift
79.41% <0.00%> (-8.83%)
:arrow_down:

...tionSync/AWSIncomingEventReconciliationQueue.swift
57.62% <0.00%> (-1.70%)
:arrow_down:

...eAndLocalSave/ReconcileAndLocalSaveOperation.swift
87.50% <0.00%> (-0.74%)
:arrow_down:

...gin/Sync/InitialSync/ModelSyncedEventEmitter.swift
90.62% <0.00%> (+1.04%)
:arrow_up:

...eCategoryPlugin/Sync/RemoteSyncEngine+Action.swift
23.52% <0.00%> (+5.88%)
:arrow_up:

...e/AWSPluginsCore/Auth/AWSAuthServiceBehavior.swift
87.50% <0.00%> (+12.50%)
:arrow_up:

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more

authors: ameter codecov-commenter

repo: aws-amplify/amplify-ios


text:
incorrect error, mentioning a parameter that is not used while it is used

cfn-lint version: (cfn-lint --version)
cfn-lint 0.25.5
Description of issue.
incorrect error, mentioning a parameter that is not used while it is used
*Additional info
SourceEventTagFilter:
Type: String
.....
Metadata:
AWS::CloudFormation::Interface:
ParameterGroups:
- Parameters:
- SourceEventTagFilter
Label:
default: Event source filtering
It seems that it does not see the resource when used as a parameter

@wjvanroosmalen in your example are you saying the Metadata section is using the Parameter?  You are correct as we aren't checking Metadata to see when a Parameter is used.  That being said is there a valid reason for having a Parameter and only mentioning it in the Metadata section?  It still seems like in this scenario we aren't using the parameter still.

It is A CF template that is a part of multiple CF deployments. I use the parameters as a setting for a change in a DynamoDB table made by a Lambda. The Lambda takes the metadata from the CF template. As a kind op parameter store solution but it gives more flexibility (especially cross-region)
Maybe its a niche situation and I understand why you would want to alarm users using more typical CF templates on this.

Yea I'm not sure I want ot change how that rule works but I do think there are a few options here.

We create a parameter for that rule so you can specify to ignore that rule.  This rule has come up a few times so I think there could be some value here for the work.  There are other dynamic template items that do similar things.
There is a long standing request to allow a YAML developer to specify exceptions with comments.  We haven't gotten far with that request but this has an outstanding issue.

For now you could also disable this rule just for that template to clean it up.

authors: kddejong wjvanroosmalen

repo: aws-cloudformation/cfn-python-lint


text:
add checks for endpoint/endpoints field in status

The endpoint and endpoints field in the Domain.Status struct are filled
in when the domain's endpoint URL or URLs (if VPC endpoints) are
established. Adds an e2e test to verify these fields on the Status
struct are indeed populated, which after adding
requeue_on_success_seconds to the generator.yaml file, is indeed true.
Signed-off-by: Jay Pipes jaypipes@gmail.com
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

/lgtm


text:
Remove DBClusterNotFoundFault as a terminal condition for GlobalCluster.

Issue #, if available: aws-controllers-k8s/community#1027
Description of changes:
Remove DBClusterNotFoundFault as a terminal condition for GlobalCluster.
By submitting this pull request, I confirm that my contribution is made under
the terms of the Apache 2.0 license.

/retest

Thanks @A-Hilaly

authors: A-Hilaly rbranche


text:
Bug: Container definitions failing with Terraform AWS Provider 5.59.0

Expected Behaviour
Container definitions for ECS task should successfully provision
Current Behaviour
│ Error: Provider produced inconsistent final plan
│
│ When expanding the plan for module.unreal_horde.aws_ecs_task_definition.unreal_horde_task_definition to include new values
│ learned so far during apply, provider "registry.terraform.io/hashicorp/aws" produced an invalid new value for
│ .container_definitions: was cty.StringVal(""), but now
│ cty.StringVal("[{\"Command\":null,\"Cpu\":1024,\"CredentialSpecs\":null,\"DependsOn\":null,\"DisableNetworking\":null,\"DnsSearchDomains\":null,\"DnsServers\":null,\"DockerLabels\":null,\"DockerSecurityOptions\":null,\"EntryPoint\":null,\"Environment\":[],\"EnvironmentFiles\":null,\"Essential\":true,\"ExtraHosts\":null,\"FirelensConfiguration\":null,\"HealthCheck\":null,\"Hostname\":null,\"Image\":\"ghcr.io/epicgames/horde-server:latest\",\"Interactive\":null,\"Links\":null,\"LinuxParameters\":null,\"LogConfiguration\":{\"LogDriver\":\"awslogs\",\"Options\":{\"awslogs-group\":\"cgd-unreal-horde-log-group\",\"awslogs-region\":\"us-west-2\",\"awslogs-stream-prefix\":\"ue-horde\"},\"SecretOptions\":null},\"Memory\":4096,\"MemoryReservation\":null,\"MountPoints\":null,\"Name\":\"unreal-horde\",\"PortMappings\":[{\"AppProtocol\":\"\",\"ContainerPort\":5000,\"ContainerPortRange\":null,\"HostPort\":5000,\"Name\":null,\"Protocol\":\"\"}],\"Privileged\":null,\"PseudoTerminal\":null,\"ReadonlyRootFilesystem\":null,\"RepositoryCredentials\":{\"CredentialsParameter\":\"arn:aws:secretsmanager:us-west-2:654654208941:secret:github/credentials-EkuyJy\"},\"ResourceRequirements\":null,\"Secrets\":null,\"StartTimeout\":null,\"StopTimeout\":null,\"SystemControls\":null,\"Ulimits\":null,\"User\":null,\"VolumesFrom\":null,\"WorkingDirectory\":null}]").
│
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.

Possible Solution
Related to https://github.com/hashicorp/terraform-provider-aws/pull/38471
Steps to Reproduce
Run an ECS task deployment with 5.59.0 of the AWS provider
Cloud Game Development Toolkit version
latest

@kylesomers we need to bump ever TF AWS Provider reference from 5.59.0 to 5.60.0. Can we configure dependabot to do this?

Versioning fixed in https://github.com/aws-games/cloud-game-development-toolkit/pull/190

authors: henrykie kylesomers


text:
fix: implement unsubscribeFromCertificateUpdates

Issue #, if available:
Description of changes:
Implements proper certificate request tracking (including unsubscribe) and also removes CSR processing logic which is no longer needed.
Why is this change necessary:
How was this change tested:
Any additional information or context required to review the change:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Merged based on previous 2 approvals. Rebased without changes (except for addition of TODO comment)


text:
chore: integration test with ssl

Issue #, if available:
Description of changes:
Work in progress: Currently, running into crt errors when creating tls context.
Supply HiveMQ with server certs so we can exercise CRT tls setup in integration tests.
Why is this change necessary:
How was this change tested:
Any additional information or context required to review the change:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Error currently running into:
[DEBUG] [2023-03-30T03:32:56Z] [000070000e790000] [tls-handler] - static: certificate and key have been set, setting them up now.
[ERROR] [2023-03-30T03:32:56Z] [000070000e790000] [tls-handler] - static: failed to import certificate and private key with error 0.

Based on results from https://github.com/aws-greengrass/aws-greengrass-mqtt-bridge/pull/120, test should pass after https://github.com/aws-greengrass/aws-greengrass-mqtt-bridge/pull/119 is merged


text:
Switch to using default min-layer-size

We were originally setting a min-layer-size of 0 when building a SOCI index for an image. This was mainly due to the constraint put forth by some registries that disallow pushing manifests without any layers. To remain consistent with the CLI, we should use the default min-layer-size (10 MiB). In the case where an empty index is generated, we will log a warning indicating that we are skipping pushing the empty index and exit gracefully.
We should also update the GitHub pages documentation to reflect the possibility that indexes may no longer be generated for smaller images. (Which is the ideal case anyway)
Related Issue
Resolves: #40
Proposed Changes
Please describe the changes proposed in this pull request. This could include bug fixes, feature enhancements, code refactoring, documentation updates, or any other modifications to the codebase.
Reviewers
Please tag the person or team responsible for reviewing this pull request, using the @ symbol followed by their username.

/do-e2e-tests

repo: aws-ia/cfn-ecr-aws-soci-index-builder


text:
Hook in point for account request in order to provide credentials for other Terraform Providers like AzureAD

Our use case:
We have AWS SSO hooked into Azure AD. When vending an account we would like to create a distribution group to "own the account" before requesting the provisioning of it.
We can 100% do it form Terraform but we need to provide credentials to the Azure AD Provider and this is where we hit the problem. Adding a api_helpers/pre-api-helpers.sh and running it in a different build pipeline; or running in a separate build pipeline external to AFT means the disconnection of the configuration of account provisioning data. So ideally we would like this to be done in the same pipeline. This is probably true of all the AFT pipelines too as we would like to as much as possible in terraform if we can!
Before jinja render we need to be able to set environment variables or run a script which will run az login:
Jinja render point:
https://github.com/aws-ia/terraform-aws-control_tower_account_factory/blob/main/modules/aft-code-repositories/buildspecs/ct-aft-account-request.yml#L54
but we probably want to move this before the hook in point, so that we don't have to run assume role twice:
          JSON=$(aws sts assume-role --role-arn ${AFT_ADMIN_ROLE_ARN} --role-session-name ${ROLE_SESSION_NAME})

The hook in code should look something like:
JSON=$(aws sts assume-role --role-arn ${AFT_ADMIN_ROLE_ARN} --role-session-name ${ROLE_SESSION_NAME})
if [ -d "./terraform_helpers" ]; then
  echo "Found terraform helpers ./terraform_helpers"
  python3 -m venv ./venv
  source ./venv/bin/activate
  pip install -r ./terraform_helpers/python/requirements.txt
  chmod +x ./terraform_helpers/pre-terraform-helpers.sh
  ./terraform_helpers/pre-terraform-helpers.sh
fi

....

for f in *.jinja; do jinja2 $f -D timestamp="$TIMESTAMP" -D provider_region=$CT_MGMT_REGION -D tf_distribution_type=$TF_DISTRIBUTION -D terraform_org_name=$TF_ORG_NAME -D terraform_workspace_name=$TF_WORKSPACE_NAME -D aft_admin_role_arn=$AFT_EXEC_ROLE_ARN >> ./$(basename $f .jinja).tf; done

....

terraform init
....

if [ -d "./terraform_helpers" ]; then
  chmod +x ./terraform_helpers/post-terraform-helpers.sh
  ./terraform_helpers/post-terraform-helpers.sh
fi

We might also want to consider a way to allow pre-terraform-helper.sh to pass in parameters to jinja2 templates for rendering e.g.
add -d pre-terraform-helpers.json which can be generated by pre-terraform-helpers.sh or maybe just add $EXTRA_ARGUMENTS at the end.

Take a look at the account provisioning customizations pipeline.

Additionally, it would be nice to be able to specify additional environment variables and/or commands to be injected into the terraform buildspecs so that we can use 3rd party providers, per what @taliesins is asking. M main use case is to leverage private terraform modules, whether that be on private github or on another private Terraform registry.

@taliesins  thank you for the feature request.
We do have an existing backlog to support custom credential injection for account requests and customization.
@SizZiKe I did add your request into the backlog. Thank you for the call out.

@snebhu3 if you could link to the back log item, we could see the approach you guys want to take. Assuming you going with something conservative like ssm parameters with a prefix path that will be injected as env variables.
I could then implement it myself (or get someone from my team ;>) and send a PR.

@taliesins thanks for the call out, however, we are not accepting pull requests at this time.
We have recorded your request in our feature request backlog.

As of 1.5.0, the customizations pipelines now share a single CodeBuild container for all of the pre-api-helpers / apply-terraform / post-api-helpers stages.
This simplified the process of authenticating to remote systems by persisting configurations and variables across the pre- / apply-terraform / post- stages.
I believe the changes in 1.5.0 meet the needs of this enhancement request, so I'm closing this issue at this time. Please feel free to open new issues with additional feedback as required.

authors: SizZiKe snebhu3 stumins taliesins


text:
added elb addtags action for lb irsa policy

Description
Fixes
ingress  (combined from similar events): Failed deploy model due to AccessDenied: User: arn:aws:sts:::assumed-role/cg-eks-nyx-aws-load-balancer-controller-sa-irsa is not authorized to perform: elasticloadbalancing:AddTags on resource: arn:aws:elasticloadbalancing:us-east-2::targetgroup/k8s-security-/* because no identity-based policy allows the elasticloadbalancing:AddTags action
a lot of users including me still use v4, so I wanted to patch it up and hopefully create a release

thank you for the PR. Unfortunately, we are no longer maintaining v4 and encourage users to upgrade to use the new addons module which has been updated for the the ALB controller

Would it be possible to open-source support to be community-driven for v4 backwards support.
v5 includes a lot of changes that fall out favor for some of us compared to v4
Loved v4 especially the ease with gitops setup - the other gitops module approaches including GitOps Bridge  don't work as smooth/consistent as this module
I hope you and your team can consider this @bryantbiggs thanks again for all the hard work y'all do to make it easy for implementation for you customers!

Would it be possible to open-source support for v4 for it to be community-driven for v4 backwards support.

I'm not sure what you mean by this - it is all open source and publicly available. if someone wanted to create a fork and host it, thats par for the course in open source

So we could push out improvements for v4.32.1+ within these repo for support or would we have to fork out a new repo in general for support?

we are not taking on any additional changes to v4 in this project - so it would be a matter of creating a fork of this repository into your own GitHub account and then making any changes you wish to that fork

authors: bryantbiggs jomakori yunusemrecatalcam

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


text:
Bug: Pydantic is being imported when using Event Handler without validation

Expected Behaviour
I'm using ApiGatewayResolver without enabling validation and it shouldn't import Pydantic. Even if a customer has Pydantic installed, they should not import Pydantic without explicitly enabling validation: app = ApiGatewayResolver(enable_validation=True)
Current Behaviour
Profiling the application with tuna, I can see Pydantic being imported:

Code snippet
from aws_lambda_powertools.event_handler import ApiGatewayResolver

app = ApiGatewayResolver(enable_validation=False)

def lambda_handler(event, context):
    return app.resolve(event, context)

requirements.txt
aws-lambda-powertools==2.27.0
aws-xray-sdk==2.12.1
botocore==1.32.3
fastjsonschema==2.19.0
jmespath==1.0.1
pydantic==1.10.13
python-dateutil==2.8.2
six==1.16.0
tuna==0.5.11
typing_extensions==4.8.0
urllib3==2.0.7
wrapt==1.16.0

Possible Solution
Move these imports to an standalone file or import them only when enable_validation is True.
Steps to Reproduce
1 - Create a file
2 - pip install aws-lambda-powertools[all] tuna
3 - Use the code snippet provided
4 - python -X importtime test.py 2> prof1.log
5 - tuna prof1.log
Powertools for AWS Lambda (Python) version
latest
AWS Lambda function runtime
3.11
Packaging format used
PyPi
Debugging logs
No response

Working at this now

authors: leandrodamascena rubenfonseca

repo: aws-powertools/powertools-lambda-python


text:
[ADDON] - Open Telemetry

Add support for Open Telemetry add-on.
https://github.com/open-telemetry/opentelemetry-helm-charts

Duplicate of #278 . Closing.

repo: aws-quickstart/cdk-eks-blueprints


text:
EMR on EKS AddOn: failed to create the service-linked role due to the name conflict

Describe the bug
EMR on EKS addons try creating service-linked role but it failed if it already exists.
Expected Behavior
Deploy successfully even if the service-linked role already exists.
Current Behavior
If the service-linked role is already created, errors occur as following in an EMR on EKS addon.

Resource handler returned message: "Service role name AWSServiceRoleForAmazonEMRContainers has been taken in this account, please try a different suffix.

Reproduction Steps
After creating the service-linked role by blueprints or other ways, deploy a new blueprint with the EMR on EKS addons.
Possible Solution
Skip creating the service-linked role.
AWS Batch AddOn tries checking if a service-linked role exists before creatring it, but it won't work well because Role.fromName() doesn't check the existance.
Generally, it would be difficult to create only non-existed resources in CDK.
Anyway, service-linked roles are shared resources, so I think it should not be created by blueprints.
Additional Information/Context
No response
CDK CLI Version
2.99.1
EKS Blueprints Version
1.12.0
Node.js Version
v18.16.1
Environment details (OS name and version, etc.)
macOS 12.4
Other information
No response

@youngjeong46 looks like the SLR is using a unique name and the uniqueness check fails. Please advise if there is a workaround at present and looking for the path forward to address.


text:
Updated docs and QS deployment to compatible static release

Issue #, if available:

N/A

Description of changes:

Updated deployment to use static and compatible Chainlink core version 1.12.0
Switched from dockerhub to public ECR
Updated UID from 1000 to 14933 to align with container's UID
Updated documentation for clarity on usage of Chainlink core version 1.12.0

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

authors: dangitsdavid troy-ameigh


text:
我没办法找到build_and_push.sh.lite

我正在测试您的代码，但是我没办法找到构建容器镜像中的脚本 build_and_push.sh.lite，可以帮帮我吗？

那部分代码尚未公开，可以再等一段时间

repo: aws-samples/amazon-ai-with-slack-bot


text:
Pipeline step 'inference-bodyscore' FAILED. Failure message is: PermissionError: [Errno 13] Permission denied

Describe the bug
Trying Sagemaker Local Mode
One step of the pipeline (inference) fails quoting Failure message is: PermissionError: [Errno 13] Permission denied 'filename.json. The step is expected to create a few json files. Note that the directory /opt/ml/processing/output was not automatically created and had to be created manually inside the script. After the step fails, I crosschecked, the json files have been uploaded to the s3. I also confirmed, the json files have 777 permission.
To reproduce

estimator = PyTorch(
    entry_point="train.py",
    source_dir="code",
    role=role,
    # instance_type=instance_type_inference,
    instance_type='local_gpu',
    instance_count=1, #instance_count,
    framework_version='1.8.0',
    py_version='py3',
    output_path=output_path,
    # checkpoint_local_path="/opt/ml/checkpoints",
    # checkpoint_s3_uri=checkpoint_path,
    max_run=4 * 24 * 60 * 60,  # 4days
    metric_definitions=[
       {'Name': 'train:error', 'Regex': 'train Loss: (.*)'},
       {'Name': 'validation:error', 'Regex': 'val Loss: (.*)'}
    ],
    hyperparameters={
        'num_epochs': num_epochs.to_string(),
        'batch_size': batch_size.to_string(),
        'lr': learning_rate.to_string()
    },
    sagemaker_session=sess
)

step_train_model = TrainingStep(
    name="train-bodyscore",
    estimator=estimator,
    inputs={
        "train": TrainingInput(
            s3_data=dataset_path,
        )
    },
)

model_saved_path = step_train_model.properties.ModelArtifacts.S3ModelArtifacts

inference_processor = PyTorchProcessor(
    framework_version="1.8.0",
    role=role,
    # instance_type=instance_type_inference,
    instance_type='local_gpu',
    instance_count=1, #instance_count,
    sagemaker_session=sess
)

inference_args = inference_processor.get_run_args(
    inputs=[
                ProcessingInput(
                    input_name ='models',
                    source=model_saved_path,
                    destination="/opt/ml/processing/models"
                ),
                ProcessingInput(
                    input_name="input-images",
                    source=dataset_path,
                    destination="/opt/ml/processing/input"
                ),
            ],
    outputs=[
                ProcessingOutput(
                    output_name="inference-output",
                    source="/opt/ml/processing/output"
                )
            ],
    code='inference.py',
    source_dir='code',
),

inference_args = inference_args[0]

step_inference = ProcessingStep(
    name="inference-bodyscore",
    processor=inference_processor,
    # step_args=processor_args,
    inputs=inference_args.inputs,
    outputs=inference_args.outputs,
    job_arguments=inference_args.arguments,
    code=inference_args.code,
    # property_files=[evaluation_report]
)

pipeline = Pipeline(
    name="tlnk-bodyscore-pipeline",
    parameters=[
        instance_count,
        instance_type_inference,
        instance_type_processing,
        checkpoint_path,
        output_path,
        dataset_path,
        num_epochs,
        batch_size,
        learning_rate,
        ],
    steps=[
            # step_data_analysis,
            step_train_model,
            step_inference,
            # step_visualize,
            # step_evaluate,
           ],
    sagemaker_session=sess
)

definition = json.loads(pipeline.definition())
print(json.dumps(definition, indent=2))
pipeline.upsert(role_arn=role)

execution = pipeline.start()
# execution.wait()

Logs
7dc4or5zgg-algo-1-ink52 | INFO:__main__:calculated bodyscore: 3
7dc4or5zgg-algo-1-ink52 | permission for file is:  0o777
7dc4or5zgg-algo-1-ink52 exited with code 0
Aborting on container exit...
Pipeline step 'inference-bodyscore' FAILED. Failure message is: PermissionError: [Errno 13] Permission denied: 'filename.json'
Pipeline execution xyzabc FAILED because step 'inference-bodyscore' failed.

Not sure what kind of permission is being denied here. Is it the one to copy the files locally to some place, or something related to aws (though I feel I have given all permissions)

repo: aws-samples/amazon-sagemaker-local-mode


text:
Schema design - Schema samples - Connected Vehicles - Needs Readme

The Connected vehicles example needs a readme.

Completed by @andrea-caldarone. Thanks for your contribution!

repo: aws-samples/aws-dynamodb-examples


text:
deprecated ECR command

https://aws.amazon.com/getting-started/hands-on/build-modern-app-fargate-lambda-dynamodb-python/module-two/  -> Module 2B: Deploy A Service With AWS Fargate - > Step 1: Create a Flask Service -> C: Push the Docker Image to Amazon ECR contains
$(aws ecr get-login --no-include-email)
which according to https://github.com/aws/containers-roadmap/issues/735 has been superseded with
aws ecr get-login-password | docker login --username AWS --password-stdin 123456789012.dkr.ecr.us-east-1.amazonaws.com

This just gives me an error
Error response from daemon: Get https://xxxxxxxxxxx.dkr.ecr.s3-website-eu-west-1.amazonaws.com/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)


text:
Error running the progress-tracker-frontend locally

When running the progress-tracker-frontend locally, getting the following error
Error: ENOENT: no such file or directory, open '/Users/gothamsh/aws-step-functions-progress-tracking/progress-tracker-frontend/.next/BUILD_ID'
    at async open (node:internal/fs/promises:637:25)
    at async Object.readFile (node:internal/fs/promises:1246:14)
    at async setupFsCheck (/opt/homebrew/lib/node_modules/next/dist/server/lib/router-utils/filesystem.js:145:19)
    at async initialize (/opt/homebrew/lib/node_modules/next/dist/server/lib/router-server.js:62:23)
    at async Server.<anonymous> (/opt/homebrew/lib/node_modules/next/dist/server/lib/start-server.js:247:36) {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '/Users/gothamsh/aws-step-functions-progress-tracking/progress-tracker-frontend/.next/BUILD_ID'
}

Pull request merged


text:
ENHANCEMENT: Added AWS Config Aggregator

(enhancement) AWS Config Aggregator is enabled and configured to leverage the Audit account.
Issue #, if available:
https://github.com/aws-samples/landing-zone-accelerator-on-aws-for-cccs-medium/issues/3
Description of changes:

Enables the AWS Config Aggregator in the Audit account.

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

This has been handled in v1.6.0-a

authors: bernardosw-aws oliviergaumond


text:
Where can I found the embedding vector in the OpenSearch Dashboards?

I am confused at founding embedding vector in OpenSearch Dashboards, after I use the code to bulk the text and embedding vector into the OpenSearch
For further information, I found the chunked text in [Query Workbench], but can not found the embedding vector, I woulf be greatful for anyone's help.

You need to create a new index mapping in the admin, Kibana will identify the filed as other, but it will be visibile in the dashboard.

@Jiegenglyu were you able to find the documents in the dashboard? May I close the issue?

authors: Jiegenglyu omerh


text:
Add ability to use Terraform version defined in the service catalog product via TFEnv

Description of changes:

Add ability to define Terraform version via .teraform-version file inside the Service catalog product.
Updated dependencies and runtimes
Add Nix flake

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

Please see our contribution guidelines for this repo.

authors: idealo-ricardo-band smaly-amazon


text:
ESP32 Nimble: prvBTSetAdvData assumes exactly 1 UUID to be advertised

Describe the bug
In iot_ble_hal_gap.c, function prvBTSetAdvData() never uses the xNbServices parameter and assumes there is exactly 1 UUID to be advertised if pxServiceUuid is not NULL.
At the same time, _setAdvData always gives a value to pxServiceUuid and sets xNbServices as 0 if there are no UUIDs to advertise.
This means that trying to advertise 0 UUIDs (e.g. to save advertisement space) does not work. Trying to advertise 2 UUIDs would also not work.
System information

Which hardware board or part numbers? ESP32
IDE used. Does not matter.
Operating System. Does not matter.
Version of Amazon FreeRTOS. master
Project: Custom Application

Expected behavior
The xNBServices should be used to advertise the requested number of UUIDs.
To reproduce
Steps to reproduce the behavior:
Just use a custom advertising callback like the following:
Code to reproduce the bug
void IotBle_SetCustomAdvCb(IotBleAdvertisementParams_t *pAdvParams,
                           IotBleAdvertisementParams_t *pScanParams)
{
  pAdvParams->setScanRsp          = false;
  pAdvParams->includeTxPower      = false;
  pAdvParams->name.xType          = BTGattAdvNameShort;
  pAdvParams->name.ucShortNameLen = IOT_BLE_DEVICE_SHORT_LOCAL_NAME_SIZE;
  pAdvParams->appearance          = IOT_BLE_ADVERTISING_APPEARANCE;
  pAdvParams->minInterval         = IOT_BLE_ADVERTISING_CONN_INTERVAL_MIN;
  pAdvParams->maxInterval         = IOT_BLE_ADVERTISING_CONN_INTERVAL_MAX;
  pAdvParams->serviceDataLen      = 0;
  pAdvParams->pServiceData        = NULL;
  pAdvParams->manufacturerLen     = 0;
  pAdvParams->pManufacturerData   = NULL;
  pAdvParams->pUUID1 = (BTUuid_t *)&_advUUID;
  pAdvParams->pUUID2 = NULL;

  /// use the scan response to fit the full name of the device
  pScanParams->setScanRsp          = true;
  pScanParams->includeTxPower      = false;
  pScanParams->name.xType          = BTGattAdvNameComplete;
  pScanParams->name.ucShortNameLen = 0; // does not matter
  pScanParams->appearance          = IOT_BLE_ADVERTISING_APPEARANCE;
  pScanParams->minInterval         = IOT_BLE_ADVERTISING_CONN_INTERVAL_MIN;
  pScanParams->maxInterval         = IOT_BLE_ADVERTISING_CONN_INTERVAL_MAX;
  pScanParams->serviceDataLen      = 0;
  pScanParams->pServiceData        = NULL;
  pScanParams->manufacturerLen     = 0;
  pScanParams->pManufacturerData   = NULL;
  pScanParams->pUUID1 = NULL;
  pScanParams->pUUID2 = NULL;
}

Additional context
I have a patch that I will post soon as a PR

Hello  matteoscordino,
Thanks for contacting us and providing a fix for potential issue.   We will internally review it and get back to you.
Thanks!

Hi @matteoscordino
Thanks for bringing this up.
I agree there is a deviation here in the port implementation, but the bluetooth core specification (core supplement v8)  page 10 says:
"packet or data block shall not contain more than one instance for each Service UUID data size. If a device has no Service UUIDs of a certain size, 16-, 32-, or 128-bit, the corresponding field in the extended inquiry response or advertising data packet shall be marked as complete with no Service UUIDs. An omitted Service UUID data type shall be interpreted as an empty incomplete-list."
So I think, the packet can have one service UUID each of different types (16, 32 or 128 ) but if there are more than one UUID of a particular type then it should be marked as incomplete type and only the first UUID should be included.
Could you change the pull request accordingly ?

Hi, @matteoscordino .  On the related PR, https://github.com/aws/amazon-freertos/pull/1570 , it looks like one more change was suggested.  Would you have a look?  Thanks.

repo: aws/amazon-freertos


text:
How to integrate coreMQTT(mqtt_demo_mutual_auth.c) with wifi_provisioning(aws_wifi_connect_task.c) on AWS ESP 32??

Hello there guys. Could you please be kind enough to help me out on integrating both demos from the FreeRTOS V202012.00.? Basically I want to send data to AWS using the coreMQTT example using the wifi_provisioning mobile app over BLE.
At this stage, I have (all the time) to hardcode the ssid and password on the aws_clientcredential.h file. Thanks in advance.

Hi @Yoimer,
You can enable WiFi provisioning over BLE by setting the flag IOT_BLE_ENABLE_WIFI_PROVISIONING to 1 as mentioned in this doc: https://docs.aws.amazon.com/freertos/latest/userguide/ble-demo.html#ble-demo-wifi
Please note that you don't need to do step 2: Configure the Network Manager to enable both Bluetooth Low Energy and Wi-Fi. as the coreMQTT  demo runs only on WiFi.
Please follow further instructions in document under To run the demo to provision a wifi credential onto the device. Using network manager APIs, the demo waits for a network to be configured before running the demo entry function. The task aws_wifi_connect_task.c will take care of reconnecting to a provisioned network on device reboot or when the current connection is lost.

Hello @Yoimer,
Did the above response answer your question? We will close this issue if we do not hear back from you.
Thank you

@muneebahmed10 Hello and thanks for your concern. Actually no. I know how to run the wifi_provisioning demo isolated. I'd like to know how to integrate that demo with the rest. I just do not want to keep hardcoding wifi credentials on the tests.
Thanks in advance.

@muneebahmed10 Please if you got time check this out https://github.com/aws/amazon-freertos/issues/3056#issuecomment-806214722. I was able to handle a MQTT and OTA integration but on V202002.00 version. The goal on this version is the same. I want to use the BLE Wifi_Provisioning capabilities.
Thanks again.

@Yoimer
Since the question posted in this forum is already answered in #3056, could we close this issue and keep the other one?

@ravibhagavandas hello. Thanks for commenting. Replying to your question, yes. Please close this issue and let's carry on on #3053. Have a great day.

Thanks, Closing this issue.

authors: Yoimer muneebahmed10 ravibhagavandas