text:
fix bug: Spherical hamonics based render is not correct

revise the SH render formulation

As formula.(5) states,  it seems sdfstudio forgets the direction component in SH-renderer by mistake and the color prior (0.5) is unnecessary

@WANGSSSSSSS Thanks for the PR. SHRenderer is not used in the code base. It's implemented by nerfstudio. Could you open the PR in their repo?

authors: WANGSSSSSSS niujinshuchong

repo: autonomousvision/sdfstudio


text:
test: windows

In an attempt to reproduce the test case presented in #167

We'll need to include some conditionals around what the tests expect for each platform.

source: gharchive/pull-request

repo: autovance/ftp-srv

license: MIT

license_type: permissive

license_source: github-api


text:
obstacle cruise planner is setting zero velocity points behind the suddenly spawned obstacle in the trajectory

Checklist

[X] I've read the contribution guidelines.
[X] I've searched other issues and no duplicate issues were found.
[X] I'm convinced that this is not my fault but a bug.

Description
In the obstacle_cruise_planner module of Autoware, an issue was observed where, upon the sudden appearance of a predicted obstacle on the planned route, the planner incorrectly sets a zero velocity for the trajectory segment behind the obstacle. This behavior deviates from expected handling, where adjustments are made to the trajectory in front of the obstacle.
Video:
https://github.com/autowarefoundation/autoware.universe/assets/45468306/99de723f-0d1c-40b9-bde8-30d1cbb90ed3
Snapshot when the stop wall was set:

As you can see in the video, obstacle_cruise_planner sets zero velocity points far away from the ego in trajectory.
The scenario was tested as part of the planning_control pipeline in the reaction_analyzer (please see for more information.), highlighting the discrepancy in reaction time and trajectory planning when compared to obstacle_stop_planner. You can see the test results which are comparing motion_stop_planner_types in Additional context below.
Expected behavior
When a sudden obstacle is spawned on the route, the obstacle_cruise_planner should dynamically adjust the vehicle's trajectory by reducing speed or stopping in front of the obstacle, ensuring safety and adherence to the planned path without creating impractical or unsafe zero-velocity segments behind the obstacle.
Actual behavior
Upon the introduction of a PredictedObject in front of the vehicle, the obstacle_cruise_planner incorrectly sets a trajectory with zero velocity behind the sudden obstacle. This results in an unrealistic response to obstacles and may compromise the effectiveness of the planning_control pipeline. The warning message indicates a failure to interpolate the obstacle pose, suggesting a problem in trajectory adjustment logic.
Steps to reproduce

Set motion_stop_planner_type obstacle_cruise_planner in default_preset.yaml
Create a route for the ego vehicle by using planning_simulator.launch.xml
Simulate the ego vehicle driving at approximately 40 kph.
Spawn a PredictedObject 15 meters in front of the moving vehicle.

Versions
No response
Possible causes
No response
Additional context
Tests were made in some conditions:

Pipeline:  [obstacle_cruise_planner or obstacle_stop_planner] -> scenario_selector -> motion_velocity_smoother -> planning_validator -> trajectory_follower -> vehicle_cmd_gate
Spawn obstacle if the distance between obstacle and vehicle is below 15 meters.
Wait until all the topics are reacted to the object.

Reaction times for a sudden object:

The results below indicate in milliseconds.

obstacle_cruise_planner:

Node
Test - 1
Test - 2
Test - 3
Test - 4
Test - 5
Test - 6
Test - 7
Test - 8
Test - 9
Test - 10
Test - 11
Test - 12
Test - 13
Test - 14
Test - 15
Min
Max
Mean
Median
StdDev

trajectory_follower
62.8955
54.1983
63.3394
63.4726
83.6868
64.003
72.9368
73.4738
72.9419
72.9625
94.9728
52.9139
53.4631
63.7523
73.9409
52.9139
94.9728
68.1969
64.003
11.0857

vehicle_cmd_gate
63.027
54.5334
63.7026
63.6133
83.8777
64.2321
73.0643
73.6687
73.141
73.2319
95.4233
53.282
53.6138
63.8961
74.2234
53.282
95.4233
68.4354
64.2321
11.1056

motion_velocity_smoother
2050.22
2046.02
1954.43
1951.95
1955.34
2042.6
1952.83
2055.1
1951.57
1950.15
1943.56
1953.21
1958.31
1952.74
1955.94
1943.56
2055.1
1978.26
1954.43
42.5263

planning_validator
2050.43
2046.29
1954.75
1952.31
1955.67
2042.87
1953.19
2055.42
1951.84
1950.42
1943.86
1953.54
1958.63
1953
1956.21
1943.86
2055.42
1978.56
1954.75
42.5089

obstacle_cruise_planner
2146.54
2139.49
2149.69
2244.99
2244.96
2135.31
2142.88
2148.86
2057.46
2150.18
2238.32
2044.22
2045.75
2049.22
2052.21
2044.22
2244.99
2132.67
2142.88
69.3146

scenario_selector
2146.68
2139.61
2149.84
2245.16
2245.27
2135.39
2143.09
2148.96
2057.59
2150.32
2238.45
2044.36
2045.88
2049.32
2052.34
2044.36
2245.27
2132.82
2143.09
69.3403

obstacle_stop_planner use_predicted_objects: true:

Node
Test - 1
Test - 2
Test - 3
Test - 4
Test - 5
Test - 6
Test - 7
Test - 8
Test - 9
Test - 10
Test - 11
Test - 12
Test - 13
Test - 14
Test - 15
Min
Max
Mean
Median
StdDev

obstacle_stop_planner_use_predicted_objects
81.8382
81.9391
83.8632
86.3468
85.1878
83.3875
82.3428
82.2222
84.5927
87.677
84.7681
85.0682
82.829
84.8964
87.0188
81.8382
87.677
84.2652
84.5927
1.78841

scenario_selector
81.9589
82.1994
84.1792
86.5465
85.3413
83.5361
82.4551
82.4014
84.7381
87.8981
85.0498
85.1391
82.9631
85.0295
87.2563
81.9589
87.8981
84.4461
84.7381
1.80323

motion_velocity_smoother
83.9044
84.0764
86.4751
88.8741
89.1653
85.5327
84.8375
84.6506
87.9979
90.7888
87.0837
88.8145
86.0696
87.6334
89.5126
83.9044
90.7888
87.0278
87.0837
2.08446

planning_validator
84.1665
84.4794
86.8335
89.2254
89.3364
85.8473
85.2001
84.8592
88.3685
91.1991
87.4539
89.1279
86.392
87.9206
89.7858
84.1665
91.1991
87.3464
87.4539
2.0879

trajectory_follower
107.754
87.8264
98.0843
108.317
107.828
108.065
88.6004
98.5973
97.9737
108.163
117.404
98.1266
107.861
117.814
98.005
87.8264
117.814
103.361
107.754
8.68018

vehicle_cmd_gate
107.949
87.9589
98.2927
108.564
108.191
108.238
88.8766
98.8386
98.1012
108.342
117.555
98.4378
108.044
118.137
98.2119
87.9589
118.137
103.582
107.949
8.68948

obstacle_stop_planner use_predicted_objects: false:

Node
Test - 1
Test - 2
Test - 3
Test - 4
Test - 5
Test - 6
Test - 7
Test - 8
Test - 9
Test - 10
Test - 11
Test - 12
Test - 13
Test - 14
Test - 15
Min
Max
Mean
Median
StdDev

obstacle_stop_planner
86.8533
83.6418
82.7774
86.5559
85.7587
86.4881
87.1604
86.8174
86.0537
83.0285
84.5305
91.5692
85.014
84.4648
88.1908
82.7774
91.5692
85.927
86.0537
2.15022

scenario_selector
87.135
83.7662
82.9173
86.7101
85.9345
86.6086
87.2528
87.0172
86.2334
83.1774
84.7482
91.7605
85.2001
84.5718
88.4958
82.9173
91.7605
86.1019
86.2334
2.17239

motion_velocity_smoother
90.533
87.0821
86.2301
89.8849
88.4932
89.6786
89.3122
89.2584
88.2903
85.4724
86.8861
94.0338
87.3018
86.7852
91.0562
85.4724
94.0338
88.6866
88.4932
2.13953

planning_validator
90.8006
87.4937
86.4362
90.1673
88.7433
90.0151
89.5907
89.5644
88.5552
85.8178
87.1727
94.4318
87.7218
87.0332
91.4043
85.8178
94.4318
88.9965
88.7433
2.15502

trajectory_follower
121.686
101.488
111.798
121.782
102.148
111.794
92.0036
102.322
111.622
91.7295
102.278
111.838
91.8911
91.7672
101.677
91.7295
121.782
104.522
102.278
9.9253

vehicle_cmd_gate
121.83
101.717
111.982
121.954
102.304
112.017
92.053
102.434
111.869
91.9243
102.436
112.019
92.0356
91.9892
101.878
91.9243
121.954
104.696
102.434
9.93526

@brkay54
The obstacle_cruise_planner has minimum jerk and acceleration constraints for the stop based on the idea that the stop for the larger jerk and acceleration should be done by AEB.
Anyway, I think it would be better to implement a flag to disable them.

Hi, @takayuki5168 thank you for the quick answer. Then, it is expected behavior.

Anyway, I think it would be better to implement a flag to disable them.

After your answer, I looked at the code to find where these constraints were set and I found an if condition here:
https://github.com/autowarefoundation/autoware.universe/blob/81d53740a7f4673bc4c775bb60618708a8d7a94d/planning/obstacle_cruise_planner/src/planner_interface.cpp#L311-L325
I think this is already implemented. I tried to disable this parameter:
https://github.com/autowarefoundation/autoware_launch/blob/c03bd4bdb70117efffc328e5fe6e57426f169b3b/autoware_launch/config/planning/scenario_planning/lane_driving/motion_planning/obstacle_cruise_planner/obstacle_cruise_planner.param.yaml#L27
After disabling this parameter, obstacle_cruise_planner works as we expected. I tested again to be sure about it, here results:

Node
Test - 1
Test - 2
Test - 3
Test - 4
Test - 5
Test - 6
Test - 7
Test - 8
Test - 9
Test - 10
Test - 11
Test - 12
Test - 13
Test - 14
Test - 15
Min
Max
Mean
Median
StdDev

obstacle_cruise_planner
61.0829
59.778
64.9402
60.9953
64.5416
58.5924
61.2187
65.4465
58.2531
58.6755
61.2513
62.0713
62.39
58.3768
58.1821
58.1821
65.4465
61.053
61.0829
2.39521

scenario_selector
61.2408
59.8985
65.2115
61.0872
64.6762
58.691
61.3608
65.5775
58.3899
58.7695
61.3561
62.2505
62.5848
58.5338
58.3239
58.3239
65.5775
61.1968
61.2408
2.41658

motion_velocity_smoother
63.0515
62.0507
67.3218
63.1834
67.7317
60.7671
64.8069
68.4263
60.6618
60.9651
63.2338
65.5009
64.7324
60.982
60.5544
60.5544
68.4263
63.598
63.1834
2.62434

planning_validator
63.3622
62.304
67.6128
63.4663
68.0695
61.0831
65.0504
68.7531
60.9425
61.2335
63.495
65.9171
65.1513
61.2585
60.8284
60.8284
68.7531
63.9018
63.4663
2.64667

trajectory_follower
87.6072
77.7533
97.9342
86.9794
77.6086
87.9109
68.0986
97.6374
87.3483
77.1777
87.7728
97.4444
77.7068
77.1163
87.0026
68.0986
97.9342
84.8732
87.0026
8.51413

vehicle_cmd_gate
87.838
77.9183
98.1974
87.1577
77.9118
88.085
68.2768
97.7869
87.5273
77.3806
88.0014
97.6075
77.9374
77.3294
87.1956
68.2768
98.1974
85.0767
87.1956
8.50809

I guess, it is already implemented, so I am closing the issue. Thank you @takayuki5168 -san!

Ah, right! I forgot that I already implemented it.

source: gharchive/issue


text:
refactor(kinematic_evaluator): rework parameters

Description
Implement the ROS Node configuration layout described in https://github.com/orgs/autowarefoundation/discussions/3371
Tests performed
Package built and launch locally.
Effects on system behavior
More reliable and faster parameter configuration file creation.
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

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

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

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

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

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

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

Hi @TakaHoribe , @djargot, @rej55, @satoshi-ota, @shmpwk, @takayuki5168,  @kimura4,
One approval is needed to merge this PR. Could you please review it?

Since there were no reaction from the CODEOWNERS for over a week, I took over with the review and merging this PR. The PR only affects the documentation anyways.

authors: batuhanbeytekin mitsudome-r


text:
Changing cache location isn't working in tabbyapi, vllm

Hey. I installed this on Linux and changed the model for tabby to 'bullerwins_gemma-2-2b-it-exl2_8.0bpw', and then used the hf dl'er to d/l the model to here.  I've confirmed it was dl'ed to the folder below.
(~/.cache/huggingface/hub/models--bullerwins--gemma-2-2b-it-exl2_8.0bpw)
When I run harbor up tabbyapi I get the error below.
File "/app/backends/exllamav2/model.py", line 216, in init
self.config.prepare()
File "/usr/local/lib/python3.11/dist-packages/exllamav2/config.py", line 166, in prepare
assert os.path.exists(self.model_dir), "Can't find " + self.model_dir
**AssertionError: Can't find /models/hf/bullerwins_gemma-2-2b-it-exl2_8.0bpw**
What step am I missing? Where is the /models/hf folder that its looking for?
Great project. Thx.

Thanks for another report!
Current TabbyAPI integration is indeed a bit strict about the model placement, but it's designed to also be straightforward. Here's a sample set of commands to run the model above:
# 1. Use HuggingFaceDownloader CLI to get the files from the HF Hub
$ harbor hf dl -m bullerwins/gemma-2-2b-it-exl2_8.0bpw -s ./hf

# [Optional] Use "harbor find" to observe the files on local file system
# uses substring match on path for the filter
$ harbor find gemma-2-2b-it-exl2_8.0bpw

# 2. Set model for tabbyapi, using "harbor tabbyapi model"
# Using the same model specifier as for the download - i.e. "user/repo" from HF
harbor tabbyapi model bullerwins/gemma-2-2b-it-exl2_8.0bpw

# 3. Start the TabbyAPI service
harbor up tabbyapi

# [Optional] sample chat completion
# curl is just for portability, there are nicer HTTP clients
curl $(harbor url tabbyapi)/v1/chat/completions -H "Content-Type: application/json" -H "Authorization: Bearer $(harbor config get tabbyapi.api_key)" -d '{
  "model": "hf",
  "messages": [
    {
        "role": "user",
        "content": "How to eat cake?"
    }
  ],
  "max_tokens": 60
}'
# Sample output:
{"id":"chatcmpl-da3f2060ffc04cfa89a9ebd20e2672d3","choices":[{"index":0,"finish_reason":"length","message":{"role":"assistant","content":"Ah, the age-old question! Here's a guide on how to enjoy a piece of cake:\n\n**The Classic Way:**\n\n1. **Present Position:**  Find a comfortable spot, preferably seated or with a cushioned chair. Aim for an upright position to keep your body and posture"},"logprobs":null}],"created":1730025638,"model":"bullerwins_gemma-2-2b-it-exl2_8.0bpw","object":"chat.completion","usage":{"prompt_tokens":14,"completion_tokens":60,"total_tokens":74}}

Closing for now, please feel free to follow up or open a new issue if needed

repo: av/harbor


text:
Pretty game start screen

Please make some procedurally generated effect. Maybe something similar to Matrix effect where pixels fall from the top.

Sparkle effect was added.
I will add a new title image too, so don't close this Issue yet.

repo: avcdsld/pepe-crush


text:
Add Docker container, instructions, and modified server to accommodate.

Hey,
Big fan of your work, hopefully this is a useful contribution.

Thank you for your kind words and for the pull request.

I made a couple of changes to ensure the server defaults to 127.0.0.1 since I don't have TLS configured yet. Please let me know if this breaks the docker build.

It did, but I fixed it. New PR coming in.

Thanks. Pull the latest version. I should have it fixed now.

repo: averagesecurityguy/ptnotes

license_source: bigquery


text:
chore: moved schema components and misc files out

Cleaned up the repo

From now on avid-db will only host raw report and vuln files that are published or in review
moved misc docs, notebooks, and scripts to ../.github (private repo)
moved schema components to ../avid-schema

Q: should I upload public facing markdown files to our gitbook to retain visibility? (Re: project_overview.md)

I consolidated parts of it into the gitbook doc (backend and editorial).
Feel free to add edits to that.
The mission-vision-values part is in https://avidml.org/arva/.
The HF spaces part needs a home, probably in githbook.
On Mon, Jun 26, 2023 at 5:58 PM Nathan Butters @.***>
wrote:

Q: should I upload public facing markdown files to our gitbook to retain
visibility? (Re: project_overview.md)
—
Reply to this email directly, view it on GitHub
https://github.com/avidml/avid-db/pull/12#issuecomment-1608545608, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABNYO4TTRAYD7HMNDJEUI7TXNIV4HANCNFSM6AAAAAAZU3AZQI
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Subho Majumdar, PhD
President, AI Risk and Vulnerability Alliance
subhomajumdar.com http://subhomajumdar.com
I may trust in God; all others must bring data.

Okay, I'll take a look tonight and update tasks I had made.

authors: butterswords shubhobm

repo: avidml/avid-db


text:
Designing and implementing UI of Profile Page #SWoC 2021

The top bar consists of a Profile icon. It could be tapped to open the details of the user like a profile page. I would like to make that as an Animated Overlay which will consist of  name, class of the user with a profile picture
I will be happy to design the profile overlay under SWoC 2021

Assigned to you.. @hareshnayak

Assigned to you.. @hareshnayak

@hareshnayak Should I ask fellow contributors to design the page then you can code or you're going to both design and code?

@hareshnayak Should I ask fellow contributors to design the page then you can code or you're going to both design and code?

I can do both,
Let me send the PR first, if u find that there should be a different approach to it, u may give the design work to someone.
But let me first design n send the PR

I can do both,
Let me send the PR first, if u find that there should be a different approach to it, u may give the design work to someone.
But let me first design n send the PR

Sure Sure

Sure Sure

Design for profile page

Design for profile page

@hareshnayak Once I confirm the Design you can start working on it.. so, wait for me to Confirm the design..

@hareshnayak Once I confirm the Design you can start working on it.. so, wait for me to Confirm the design..

Yes, sure
On Sun, Jan 17, 2021, 19:26 Avinash Kr. Ranjan notifications@github.com
wrote:

@hareshnayak https://github.com/hareshnayak Once I confirm the Design
you can start working on it.. so, wait for me to Confirm the design..
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/avinashkranjan/Friday/issues/8#issuecomment-761816506,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOYWG36RIOV7BHYR3K2SY43S2LT75ANCNFSM4VRVFEBQ
.

Yes, sure
On Sun, Jan 17, 2021, 19:26 Avinash Kr. Ranjan notifications@github.com
wrote:

@hareshnayak https://github.com/hareshnayak Once I confirm the Design
you can start working on it.. so, wait for me to Confirm the design..
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/avinashkranjan/Friday/issues/8#issuecomment-761816506,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOYWG36RIOV7BHYR3K2SY43S2LT75ANCNFSM4VRVFEBQ
.

@avinashkranjan  Please check out the new design

@avinashkranjan  Please check out the new design

@avinashkranjan Please check out the new design

This Looks Good..@hareshnayak Go ahead with this design and start working on it's Implementation..

@avinashkranjan Please check out the new design

This Looks Good..@hareshnayak Go ahead with this design and start working on it's Implementation..

great!

great!

Any Updates @hareshnayak ???

Any Updates @hareshnayak ???

Are you working on this issue or should I assign it to someone else?? @hareshnayak

Are you working on this issue or should I assign it to someone else?? @hareshnayak

@avinashkranjan... If nobody is working on it, Can I take this issue??

@avinashkranjan... If nobody is working on it, Can I take this issue??

Go Ahead @Imadarshsri while you're on it change the Hello, Sir to Hello, Username

Go Ahead @Imadarshsri while you're on it change the Hello, Sir to Hello, Username

Thanks...I will do it...

Thanks...I will do it...

authors: Imadarshsri avinashkranjan hareshnayak purnima143

repo: avinashkranjan/Friday


text:
java.io.FileNotFoundException when calling (load-plugins)

I have built the riemann_flapjack_output in a clean environment and can start Riemann with the jar in the classpath.  However, when I call (load-plugins) in my config I get the following exception:
INFO [2015-09-24 20:26:42,560] SIGHUP handler - riemann.bin - Caught SIGHUP, reloading
INFO [2015-09-24 20:26:42,561] SIGHUP handler - riemann.pubsub - Sweeping transient subscriptions.
INFO [2015-09-24 20:26:42,575] SIGHUP handler - riemann.plugin - walking classpath to find plugins
INFO [2015-09-24 20:26:42,608] SIGHUP handler - riemann.plugin - loading plugin: flapjack
ERROR [2015-09-24 20:26:42,611] SIGHUP handler - riemann.bin - Couldn't reload:
java.io.FileNotFoundException: Could not locate taoensso/carmine__init.class or taoensso/carmine.clj on classpath: , compiling:(riemann_flapjack_output/core.clj:1:1)
        at clojure.lang.Compiler.load(Compiler.java:7142)
        at clojure.lang.RT.loadResourceScript(RT.java:370)
        at clojure.lang.RT.loadResourceScript(RT.java:361)
        at clojure.lang.RT.load(RT.java:440)
        at clojure.lang.RT.load(RT.java:411)
        at clojure.core$load$fn__5066.invoke(core.clj:5641)
        at clojure.core$load.doInvoke(core.clj:5640)
        at clojure.lang.RestFn.invoke(RestFn.java:408)
        at clojure.core$load_one.invoke(core.clj:5446)
        at clojure.core$load_lib$fn__5015.invoke(core.clj:5486)
        at clojure.core$load_lib.doInvoke(core.clj:5485)
        at clojure.lang.RestFn.applyTo(RestFn.java:142)
        at clojure.core$apply.invoke(core.clj:626)
        at clojure.core$load_libs.doInvoke(core.clj:5524)
        at clojure.lang.RestFn.applyTo(RestFn.java:137)
        at clojure.core$apply.invoke(core.clj:626)
        at clojure.core$require.doInvoke(core.clj:5607)
        at clojure.lang.RestFn.invoke(RestFn.java:408)
        at riemann.plugin$load_from_meta.invoke(plugin.clj:43)
        at riemann.plugin$load_from_resource.invoke(plugin.clj:53)
        at riemann.plugin$load_plugins.invoke(plugin.clj:64)
        at riemann.plugin$load_plugins.invoke(plugin.clj:66)
        at riemann.config$eval6961.invoke(alerts.config:25)
        at clojure.lang.Compiler.eval(Compiler.java:6703)
        at clojure.lang.Compiler.load(Compiler.java:7130)
        at clojure.lang.Compiler.loadFile(Compiler.java:7086)
        at clojure.lang.RT$3.invoke(RT.java:318)
        at riemann.config$include.invoke(config.clj:408)
        at clojure.core$map$fn__4245.invoke(core.clj:2559)
        at clojure.lang.LazySeq.sval(LazySeq.java:40)
        at clojure.lang.LazySeq.seq(LazySeq.java:49)
        at clojure.lang.Cons.next(Cons.java:39)
        at clojure.lang.LazySeq.next(LazySeq.java:81)
        at clojure.lang.RT.next(RT.java:598)
        at clojure.core$next.invoke(core.clj:64)
        at clojure.core$dorun.invoke(core.clj:2856)
        at riemann.config$include.invoke(config.clj:404)
        at riemann.config$eval6908.invoke(riemann.config:7)
        at clojure.lang.Compiler.eval(Compiler.java:6703)
        at clojure.lang.Compiler.load(Compiler.java:7130)
        at clojure.lang.Compiler.loadFile(Compiler.java:7086)
        at clojure.lang.RT$3.invoke(RT.java:318)
        at riemann.config$include.invoke(config.clj:408)
        at riemann.bin$reload_BANG_.invoke(bin.clj:27)
        at riemann.bin$handle_signals$fn__11886.invoke(bin.clj:43)
        at riemann.bin.proxy$java.lang.Object$SignalHandler$d8c00ec7.handle(Unknown Source)
        at sun.misc.Signal$1.run(Signal.java:212)
        at java.lang.Thread.run(Thread.java:745)
Caused by: java.io.FileNotFoundException: Could not locate taoensso/carmine__init.class or taoensso/carmine.clj on classpath:
        at clojure.lang.RT.load(RT.java:443)
        at clojure.lang.RT.load(RT.java:411)
        at clojure.core$load$fn__5066.invoke(core.clj:5641)
        at clojure.core$load.doInvoke(core.clj:5640)
        at clojure.lang.RestFn.invoke(RestFn.java:408)
        at clojure.core$load_one.invoke(core.clj:5446)
        at clojure.core$load_lib$fn__5015.invoke(core.clj:5486)
        at clojure.core$load_lib.doInvoke(core.clj:5485)
        at clojure.lang.RestFn.applyTo(RestFn.java:142)
        at clojure.core$apply.invoke(core.clj:626)
        at clojure.core$load_libs.doInvoke(core.clj:5524)
        at clojure.lang.RestFn.applyTo(RestFn.java:137)
        at clojure.core$apply.invoke(core.clj:626)
        at clojure.core$require.doInvoke(core.clj:5607)
        at clojure.lang.RestFn.invoke(RestFn.java:512)
        at riemann_flapjack_output.core$eval6965$loading__4958__auto____6966.invoke(core.clj:1)
        at riemann_flapjack_output.core$eval6965.invoke(core.clj:1)
        at clojure.lang.Compiler.eval(Compiler.java:6703)
        at clojure.lang.Compiler.eval(Compiler.java:6692)
        at clojure.lang.Compiler.load(Compiler.java:7130)
        ... 47 more

Is this dependency supposed to be included in the riemann-flapjack-output jar?  I'm building off eaefacbac79a432d895ed218ec194c419f026002 and am running riemann-0.2.10.

User error, I wasn't using the standalone jar.


text:
WahyuKurniaSariEnam1184001

Pada file ini terdapat 3 fungsi.Webservices () pada  apiurl ='https://pokeapi.co/api/v2/pokemon/pikachu' untuk mengambil dan menampilkan berat pokemon pikachu . Selanjutnya adalah fungsi run() digunakan untuk mengesekusi (). Selanjutnya ada fungsi main() yaitu fungsi thread yang digunakan untuk mengeksekusi fungsi run().

konflik

authors: WahyuKurniaSari awangga


text:
Support for custom python effects

Feature request
To use LedFX v2 there is a flle for custom python effecs ""UDP RGB Stream Listener"" https://hyperion-project.org/forum/index.php?thread/12082-hyperion-as-udp-listener/&postID=41247#post41247
General idea is to use the microphone from Laptop with LedFX installed that the Leds from HyperHDR (connected in RPi with LibreELEC) will react to the music.
Here it's mentioned that this will not work with HyperHDR due to a lack of custom python effects (for Hyperion.ng it will work).
Therefore please add the posibility to also use that files (or add an seperate soluation for LedFX v2).
What problem does this feature solve?
Sound reactive LED behaviour to music
How should this be implemented in your opinion?
Maybe the files from above could be used.

Hi
But in HyperHDR you don't need to do it that way using effects... BTW additionally using effects and the Python environment as an intermediary will only generate additional unnecessary resource use and possibly delay.
Since HyperHDR v18 (https://github.com/awawa-dev/HyperHDR/commit/5fb1be1c4bdbc84becfd964a08cb106482b6c4e5) there is already built-in native UDP listener so you can test it for you purpose and let me know about the results.

ok, I don't know that. Thanks you very much for your efforts and the explanation. I will try it when I got the hardware (currently I didn't have a system to test).

authors: awawa-dev update-freak

repo: awawa-dev/HyperHDR


text:
Invalid argument: idToken has incorrect "iss" (issuer) claim. Expected https://securetoken.google.com/undefined

Facing this error
Invalid argument: idToken has incorrect "iss" (issuer) claim. Expected https://securetoken.google.com/undefined, but got https://securetoken.google.com/

most likely your project id is undefined

Hey @harshmathurx,
As @huangfulei suggested, please check if you pass correct serviceAccount.projectId value to authMiddleware and getTokens

Let me check that

authors: awinogrodzki harshmathurx huangfulei

repo: awinogrodzki/next-firebase-auth-edge


text:
Two Hystrix servers

Why in the examples/hystrix-example.js there are two Hystrix servers created? One is not enough?

Hey @mazzy89, There are two hystrix servers in that example because I use that example file to test turbine integration. Turbine is an aggregation service that combines multiple hystrix streams into one dashboard: https://github.com/Netflix/Turbine/wiki

Thank you @awolden for the explanation

repo: awolden/brakes

license: mit


text:
Amplify Gen2 LLama integration error

Environment information
appy-contest git:(main) ✗ npx ampx info

System:
  OS: macOS 15.0
  CPU: (8) arm64 Apple M1 Pro
  Memory: 134.86 MB / 16.00 GB
  Shell: /bin/zsh
Binaries:
  Node: 20.10.0 - ~/.nvm/versions/node/v20.10.0/bin/node
  Yarn: 1.22.15 - ~/.npm-packages/bin/yarn
  npm: 10.9.0 - ~/.nvm/versions/node/v20.10.0/bin/npm
  pnpm: 6.11.0 - ~/.npm-packages/bin/pnpm
NPM Packages:
  @aws-amplify/auth-construct: 1.5.0
  @aws-amplify/backend: 1.8.0
  @aws-amplify/backend-auth: 1.4.1
  @aws-amplify/backend-cli: 1.4.2
  @aws-amplify/backend-data: 1.2.1
  @aws-amplify/backend-deployer: 1.1.9
  @aws-amplify/backend-function: 1.8.0
  @aws-amplify/backend-output-schemas: 1.4.0
  @aws-amplify/backend-output-storage: 1.1.3
  @aws-amplify/backend-secret: 1.1.4
  @aws-amplify/backend-storage: 1.2.3
  @aws-amplify/cli-core: 1.2.0
  @aws-amplify/client-config: 1.5.2
  @aws-amplify/deployed-backend-client: 1.4.2
  @aws-amplify/form-generator: 1.0.3
  @aws-amplify/model-generator: 1.0.9
  @aws-amplify/platform-core: 1.2.1
  @aws-amplify/plugin-types: 1.5.0
  @aws-amplify/sandbox: 1.2.6
  @aws-amplify/schema-generator: 1.2.5
  aws-amplify: 6.9.0
  aws-cdk: 2.163.1
  aws-cdk-lib: 2.163.1
  typescript: 5.6.3
AWS environment variables:
  AWS_STS_REGIONAL_ENDPOINTS = regional
  AWS_NODEJS_CONNECTION_REUSE_ENABLED = 1
  AWS_SDK_LOAD_CONFIG = 1
No CDK environment variables
npm notice
npm notice New patch version of npm available! 10.9.0 -> 10.9.1
npm notice Changelog: https://github.com/npm/cli/releases/tag/v10.9.1
npm notice To update run: npm install -g npm@10.9.1
npm notice
npm notice
npm notice New patch version of npm available! 10.9.0 -> 10.9.1
npm notice Changelog: https://github.com/npm/cli/releases/tag/v10.9.1
npm notice To update run: npm install -g npm@10.9.1
npm notice

Describe the bug
with this config for a generation in amplify data:
const aiCheckSong = a
  .generation({
    aiModel: a.ai.model("Llama 3.1 405B Instruct"),
    systemPrompt: `You are a helpful assistant that checks, corrects and returns full song names, full composers name  and types.
      Based on the input, you should return the corrected song name, composer and type.
      The song name and type should be included in response only if the input contains a song name,
      Feel free to add the composer if it's not included in the input and you are confident you know it.`,
  })
  .arguments({
    inputName: a.string(),
    inputComposer: a.string(),
  })
  .returns(
    a.customType({
      songName: a.string(),
      songComposer: a.string(),
    })
  )
  .authorization((allow) => allow.publicApiKey());

call from the frontend into api.generation.aiCheckSong will throw an error:
[
{
  "path": [
    "aiCheckSong"
  ],
  "data": null,
  "errorType": "ValidationException:http://internal.amazon.com/coral/com.amazon.bedrock/",
  "errorInfo": null,
  "locations": [
    {
      "line": 2,
      "column": 3,
      "sourceName": null
    }
  ],
  "message": "A custom error was thrown from a mapping template."
}
]

the same set-up works with Antropic Claude 3.5 as the model, and I get the correct formatted object.
Looking at the docs I don't see any limitation of the Llama model.
Reproduction steps
deploy a data api with the setup from above
from FE call the api with:
   const res = await clientPublicApi.generations.aiCheckSong({
      inputName: name,
      inputComposer: composer,
    });
    ```
    both params are strings.

on closer inspection, looks like the models typed in Amplify are note available in "eu-central-1" and the models that we do have, are not in the enum used to complete the model.

in the same ideea, i managed to use the LLama avaialble in eu-central-1 by manualy updating the type in the nodes_modules folder.
But now, I think this model does not support the structured output requested by appsync... I am also attaching the logs from appsync resolver where you can see the post request to bedrock and the error response visible in logs.
CloudWatch Log Events.csv

repo: aws-amplify/amplify-backend


text:
DataStore Save Not Working after adding function to Appsync Resolver Pipeline

Amplify CLI Version
12.0.0
Question
I added a function to the MutationUpdateToDo resolver pipeline and now when I call the DataStore.save function in my app, the changes aren't written to DynamoDB.
I created a Lambda function to validate the user in a multi-tenant environment and am calling it in a request mapping template in an AppSync function I created and added to the pipeline resolver. This is to prevent someone from modifying data that doesn't belong to their associated group from outside the app (groupID is a custom attribute in Cognito and pulled from the JWT Token to compare with the groupID on the row they are trying to access).
Now, when I change the ToDo item in the app, the change does not get written to the DynamoDB table. I understand that modified pipelines aren't really supported with the DataStore, but I think there should be a way to add a function that doesn't modify data, and only authorizes the user to continue, or prevents them from continuing the action, without messing up the DataStore's behavior.
Here is my request mapping template:
`#**
The value of 'payload' after the template has been evaluated
will be passed as the event to AWS Lambda.
*#
$util.log.info("In the Request mapping template!")
{
"operation": "Invoke",
"payload": {
"version": "2018-05-29",
"operation": "Invoke",
"payload": {
"tableName": "$ctx.stash.get('tableName')",
"primaryKey": { "id": "$ctx.args.input.id" },
"groupID": "$ctx.identity.claims.get('custom:currentGroup')"
}
}
}
`
and here is the response mapping template:
## Raise a GraphQL field error in case of a datasource invocation error #if($ctx.error)   $util.error($ctx.error.message, $ctx.error.type) #end $util.log.info("In the response mapping template") #if($context.result) 	$util.log.info($context.result) #else 	$util.log.info("Not a match") 	$util.unauthorized() #end $util.toJson($context.result)
I placed the new function at the beginning of the pipeline. It is working exactly as expected when the updateToDo mutation is called from the AppSync console.
Any suggestions or pointers would be greatly appreciated.

Update: It appears that the DataStore.save isn't working because the currentGroup value is not being retrieved from the claims identity. If I run the mutation in the AppSync console, the claims.identity.custom:currentGroup value is populated. When I edit the ToDo and do a DataStore.save in the app, the resolver is showing the value of the claims.identity.custom:currentGroup = null.
User pool authentication is being used in both cases, so I don't understand why the currentGroup custom attribute isn't available to the resolver.

OK, the AppSync console passes the id token to the AppSync API and therefore the resolvers can access any custom attributes added to the Cognito user pool. Apparently the DataStore passes the access token, which does not contain the custom attributes.
Here is another example where AWS Amplify turns out not to be a good choice when building multi-tenant applications. You can't use the OwnersField with the DataStore and you have to write custom resolvers to implement fine grained security. Now you can't even get the custom attributes for a user without having to query the Coginto user pool EVERY TIME a GraphQL query or mutation request is made to check if the user is allowed to access that data. Given that these issues have existed for a few years now without being rectified, one can only conclude that the architecture of Amplify does not provide a way to solve the multi-tenant app security problem

Hi @defish1962 thanks for raising this issue and apologies for the delay 🙏
You are correct, Amplify does not explicitly support multi-tenant use cases out of the box. It typically requires extra configuration, advanced workflows, and workarounds.
However, the issues you mentioned should be addressable:

the AppSync console passes the id token to the AppSync API and therefore the resolvers can access any custom attributes added to the Cognito user pool. Apparently the DataStore passes the access token, which does not contain the custom attributes.

This is true, but you can configure the graphql_headers of the API category to send the ID token instead. I just tested this to confirm and it does apply to DataStore graphql requests as well.
Amplify.configure({
  ...awsConfig,
  API: {
    ...awsConfig,
    graphql_headers: async () => {
      const session = await Auth.currentSession();
      return {
        Authorization: session.getIdToken().getJwtToken(),
      };
    },
  },
});

You can't use the OwnersField with the DataStore and you have to write custom resolvers to implement fine grained security

DataStore does support custom ownerFields. I just tried with this schema and front end code:
type Todo @model @auth(rules: [{ allow: owner, ownerField: "author" }]) {
  id: ID!
  name: String!
  description: String
  author: String!
}

you can use either the format of sub::username or just the username. Both seem to work and sync just fine for separate users. The records locally will only show the username.
const createTodo = async () => {
    const sub = user.getSignInUserSession()?.getAccessToken().payload.sub;
    console.log(sub);
    try {
      const todo = await DataStore.save(
        new Todo({
          name: "test",
          author: `${sub}::${user.username}`,
        })
      );
      console.log(todo);
    } catch (error) {
      console.error(error);
    }
  };

createTodo request

createTodo response

Hey 👋 , This issue is being closed due to inactivity. If you are still experiencing the same problem and need further assistance, please feel free to leave a comment. This will enable us to reopen the issue and provide you with the necessary support.

authors: AnilMaktala chrisbonifacio defish1962

repo: aws-amplify/amplify-category-api


text:
chore: increase unit test coverage on mapsToTransformer

Description of changes
Adding unit tests
CDK / CloudFormation Parameters Changed
N/A
Issue #, if available
N/A
Description of how you validated changes
Unit tests
Checklist

[x] PR description included
[x] yarn test passes
[x] Tests are changed or added

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

Codecov Report

Merging #1636 (d295786) into main (672c373) will increase coverage by 0.51%.
The diff coverage is 81.38%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff             @@
##             main    #1636      +/-   ##
==========================================
+ Coverage   63.05%   63.56%   +0.51%
==========================================
  Files         361      370       +9
  Lines       21421    21697     +276
  Branches     5094     5176      +82
==========================================
+ Hits        13507    13792     +285
+ Misses       7186     7180       -6
+ Partials      728      725       -3

Impacted Files
Coverage Δ

...ory-api/src/commands/api/add-graphql-datasource.ts
24.76% <0.00%> (ø)

...gory-api/src/force-updates/force-refresh-schema.ts
18.51% <0.00%> (ø)

packages/amplify-category-api/src/index.ts
30.80% <0.00%> (ø)

...vider-utils/awscloudformation/apigw-input-state.ts
88.00% <0.00%> (ø)

...rmation/cdk-stack-builder/apigw-stack-transform.ts
11.49% <0.00%> (ø)

...-api/src/provider-utils/awscloudformation/index.ts
10.76% <0.00%> (ø)

...ormation/service-walkthroughs/apigw-walkthrough.ts
8.84% <0.00%> (ø)

...mation/service-walkthroughs/appSync-walkthrough.ts
15.36% <0.00%> (ø)

...-graphql-auth-transformer/src/utils/validations.ts
87.03% <ø> (ø)

...ansformer/src/graphql-default-value-transformer.ts
97.50% <ø> (ø)

... and 46 more

... and 5 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

authors: alharris-at codecov-commenter


text:
Enable/Disable DynamoDBStreams through Amplify CLI

I want to disable/disable DynamoDBStreams - but can't see where I should set this up in my Amplify project. DynamoDbStreams are enabled by default when I create an api.
Amplify CLI Version
4.20.0
I can see the api//build/stacks/
.json has a specification for Streams StreamSpecification. I can't see where I can put this in as a default value so that they are enabled/disabled at will.
Is there any way to add a new property to amplify/backend/api/<api-name>/parameters.json to achieve this?

@zerox92 this is not possible today, I marked it as an enhancement. There is no escape hatch exist Today, but seems to be a good addition, thanks for coming up with this!

repo: aws-amplify/amplify-cli


text:
Amplify push - Cannot read property 'join' of null

Describe the bug
I currently cannot push using the Amplify CLI, this is the error -
Cannot read property 'join' of null
An error occurred during the push operation: Cannot read property 'join' of null

Amplify CLI Version
4.37.1 (downgraded because new versions have a lot of bugs)
To Reproduce
amplify push
Expected behavior
Amplify push works.
Additional context
I am currently blocked and cannot work on my backend because of this

@idanlo I'm having the same issue, how did you fix it?

@gabrielperales i actually have no idea. Sometimes the environment gets messed up on its own, probably by amplify pull or something. I deleted the amplify folder, pulled from git, ran amplify init and it worked. Weird.

authors: gabrielperales idanlo


text:
Clarify timezone for Lambda recurring schedule

Note: If your question is regarding the AWS Amplify Console service, please log it in the
AWS Amplify Console repository

Which Category is your question related to?
function
Amplify CLI Version
5.3.0
What AWS Services are you utilizing?
Lambda
Provide additional details e.g. code snippets
When I setup a lambda on recurring schedule, the default time amplify cli suggest is current time on my local machine. So I assume then I am setting the lambda's schedule based on my timezone and amplify cli will convert to UTC. For example I set my lambda to run 7:11am MST each day. But then checking the deployed lambda I see the time is not converted to UTC: cron(11 7 * * ? *).
Amplify CLI should be super clear what timezone I'm inputting the time in. It seems to imply it's my timezone because it picked the current time, but turns out it's current time in UTC which is not my current local time.

@hisham thanks for the heads up I mark it as a bug because it is an easy DX change in the prompts, the time given is in UTC as you also figured since that's how Lambda works: https://docs.aws.amazon.com/lambda/latest/dg/services-cloudwatchevents-expressions.html

authors: attilah hisham


text:
feat(amplify-frontend-flutter)

Description of changes:
Adds developer preview functionality for amplify-flutter projects.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@attilah I'm assuming you mean this one:  https://github.com/aws-amplify/amplify-cli/pull/5775

@haverchuck yes.

@attilah I answerd your inline comments in @AaronZyLee 's  initial PR.  I made several of your requested revisions.
You also had two general comments:

Put all the Flutter related E2E tests into 1 test file within the E2E project to make separation easier later and don't spread across categories.
Reorg the plugin source code into src folder with lib output and add TypeScript passthrough compilation, like we have in other some packages like amplify-provider-awscloudformation as an example.

Regarding the first bullet, I decided not to do this because none of the other test files appear organzied by platform.  I think it would be better to reorganzie all of them if needed.
Regarding bullet 2 - as we discussed, this would potentially be a breaking change due to the need to upgrade the graphql-config library to version 3.  This upgrade would break our amplify-codegen package, since the new graphql-config libary uses "include/exclude" instead of "includes/excludes".

authors: attilah haverchuck


text:
Unable to setup CI/CD with GitHub repo that contains amplify.yml via Console

Before opening, please confirm:

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

App Id
N/A
Region
us-east-1, us-east-2
Amplify Hosting feature
Build settings
Describe the bug
When creating a new Amplify App connected to a public GitHub repository, if the repository contains an amplify.yml file the UI hides a checkbox that is otherwise required, this prevents the user from actually submitting the form and set up the app.
See video of me reproducing the issue:
https://user-images.githubusercontent.com/7353869/180239498-b9cdacbd-afb0-48ae-b916-cdb02edc98ed.mp4

In the first part of the video I use a branch that contains an amplify.yml file
In the second part instead I use another branch that doesn't have the file, this time the required checkbox that asks me to acknowledge that I want Amplify to deploy the content of the repo is shown

Expected behavior
Show the Allow AWS Amplify to automatically deploy all files hosted in your project root directory checkbox regardless of whether there's an amplify.yml file in the repo, so the user can continue with the setup flow and deploy the app while connected to a GitHub repo.
Reproduction steps
https://user-images.githubusercontent.com/7353869/180239498-b9cdacbd-afb0-48ae-b916-cdb02edc98ed.mp4
Build Settings
https://github.com/aws-samples/aws-intelligent-route-optimization-tracking/blob/main/amplify.yml

Additional information
N/A

Hi @dreamorosi thank you for raising this issue. We were only able to reproduce this behavior by adding a test phase to the amplify.yml file. Is there also a test phase in your amplify.yml?

Hi @hloriana thank you for the quick feedback.
Is there any workaround or alternative config that would allow me to progress in the setup flow, even if temporarily?
I'm in favor of a proper fix but this is being a blocker for me atm.

Hi @dreamorosi please try these steps:

remove amplify.yml file from your repository (we will add this back after the first deployment)
Create a new Amplify application in the Amplify Console. You will see that Amplify may automatically generate a build script for your app. You can copy and paste the contents of your Amplify.yml file directly into the text editor before you proceed with the first deployment.
After the initial deployment is successful, you can go back and add your amplify.yml file to the root of your repository and push a new commit. This will trigger a new deployment and that should be successful.

Please note the build script you added in step 2 will be saved under build settings for your app in the console. You can delete that if you wish to. However, the amplify.yml file in your repository will take precedence even if you leave that build script in the console.

Closing this as a duplicate of https://github.com/aws-amplify/amplify-hosting/issues/2440

authors: dreamorosi hloriana hloriii

repo: aws-amplify/amplify-hosting


text:
access files from index.html give 403 errors

Before opening, please confirm:

[X] I have checked to see if my question is addressed in the FAQ.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting questions.
[X] I have removed any sensitive information from my code snippets and submission.

App Id
app1943
AWS Region
us-east-1
Amplify Hosting feature
Access control
Question
getting issues in access files inside index html in amazon web host

Hi @jayadhoni 👋🏽 please ensure that you are navigating inside your build output and zipping the contents. If you zip the folder itself, you can run into an access denied error. Please review our documentation for how to manually deploy your application: https://docs.aws.amazon.com/amplify/latest/userguide/manual-deploys.html

authors: hloriana jayadhoni


text:
Api always returns 401 after Amplify Update

Describe the bug
i am facing an issue in which i have an iOS project setup which uses cognito to authenticate users , it logs in successfully but all api's return 401.
I have followed all 11 steps here
and the concerning part is this is happening after i updated amplify to the following
Installing AWSAuthCore 2.25.0 (was 2.14.2)
Installing AWSCognitoIdentityProvider 2.25.0 (was 2.14.2)
Installing AWSCognitoIdentityProviderASF 2.25.0 (was 1.0.1)
Installing AWSCore 2.25.0 (was 2.14.2)
Installing AWSMobileClient 2.25.0 (was 2.14.2)
Installing AWSPluginsCore 1.13.4 (was 1.0.4)
Installing AWSS3 2.25.0 (was 2.14.2)
Installing Amplify 1.13.4 (was 1.0.4)
Installing AmplifyPlugins 1.13.4 (was 1.0.4)
Installing AppSyncRealTimeClient 1.5.0 (was 1.1.6)
The earlier version is also provided above.
If i switch back to the earlier version of amplify plugins it works fine.Can you pls help me out?
Steps To Reproduce
Switch from an older version of amplify mentioned above to the new one also mentioned above

Expected behavior
It should work as it is working in older versions
Amplify Framework Version
2.25.0
Amplify Categories
API, Auth, Storage
Dependency manager
Cocoapods
Swift version
5.1
CLI version
6.0.1
Xcode version
12.5.1
Relevant log output
Api always returns 401 after Amplify Update

Is this a regression? (i.e. was this working before a version upgrade)
its not a regression but yes it is working on an older version
Device
iPhone8
iOS Version
iOS 14
Specific to simulators
No response
Additional context
No response

@lawmicha pls look into this as your help would be highly appreciative.

Hi @iThink32, that link you provided https://github.com/aws-amplify/amplify-cli/issues/3390 is a feature request I opened on the CLI and is to help describe the current experience without the feature, so that is to say if it is open then the use case is not supported out of the box and the steps will get out of date.
Could you let us know what is your use case?  Which plugins are you using? API and Storage? Which services are you using? APIGateway and S3?
How do you expect the APIs to be authenticated?
APIGateway, as followed in those steps, will accept ID token or Access Token. APIPlugin would need to add the correct token. You can also set the authorizationType to None and inject the token yourself https://docs.amplify.aws/lib/restapi/authz/q/platform/ios/#note-related-to-use-access-token-or-id-token
AWSS3StoragePlugin retrieves the Cognito Identity Id and adds its on for private and protected access levels, and does IAM signing. S3 supports user pool token authentication.

@lawmicha to give you additional info , it is related to linking cognito to Storage , for api gateway i had to add an auth scope to make it work due to an escaping issue in the way the Authentication Header is sent from iOS as seen above or aws-amplify/amplify-flutter#471.
If you could tell me how do i do the same for Storage it would help me solve this problem.
Moreover the same access works fine when cli IAM controls are used but not when auth is set to COGNITO_USER_POOLS

@lawmicha i will try the above solution provided i.e NONE and get back to you but to answer your questions
Could you let us know what is your use case?
I am using cognito to sign in users post which i use storage to upload / download files which i want only signed in / authenticated users to access.But as of now it always throws a 403 irrespective of whether im accessing the public or protected bucket and even for authenticated users.
Which plugins are you using?
Auth
Storage
APIGateway
            try Amplify.add(plugin: AWSCognitoAuthPlugin())
            try Amplify.add(plugin: AWSS3StoragePlugin())
            try Amplify.add(plugin: AWSAPIPlugin())

Which services are you using?
APIGateway , Cogntio and S3
How do you expect the APIs to be authenticated?
Cognito only

@lawmicha any update on this? , i agree that the approach you suggested can be used for APIGateway to manually add headers but what about upload/ download , there is no option to add headers manually there

@lawmicha i would request you to pls assign this issue to yourself.
Frankly speaking its been two months and im thinking of considering other options due to the lack to help ive received on all mediums of communication.

@lawmicha thanks for your response but ive tried what you told me earlier but to no luck.
Fortunately i've made it work by the following solution and i will also reason it out.Please correct me if wrong.
In the project's amplifyconfiguration, remove the following line
"defaultAccessLevel": "guest"

The above line is a part of the storage configuration and will finally look like this
    "storage": {
        "plugins": {
            "awsS3StoragePlugin": {
                "bucket": “yourBucket”,
                "region": “yourRegion
            }
        }
    }
    ```

    After this use download and upload using the protected access specifier like

    ```
    let options = StorageUploadDataRequest.Options(accessLevel: .protected,
                                                       targetIdentityId: identityID)
        let uploadOperationTask = Amplify.Storage.uploadData(key: filename,data: data,
                                                             options: options ...

Reason:
The line i has requested to remove to make it work is because it assumes only that role and nothing else can change it even if authenticated.Since the guest role uses the unauth role it will always throw 401 or 403.

@lawmicha the above fix does not work on the lastest version of CLI released a day back i.e 7.4.4
I set the Auth Type to NONE and injected the Authorization Header myself and all api's seem to work fine but storage returns the following
StorageError: Unexpected error occurred with message: Domain: [Amplify.AuthError
Code: [2
LocalizedDescription: [The operation couldn’t be completed. (Amplify.AuthError error 2.)
LocalizedFailureReason: [
LocalizedRecoverySuggestion: [
Recovery suggestion: This should not happen. There is a possibility that there is a bug if this error persists. Please take a look at https://github.com/aws-amplify/amplify-ios/issues to see if there are any existing issues that match your scenario, and file an issue with the details of the bug if there isn't. Issue encountered at:
file: ...StorageError.swift
function: recoverySuggestion
line: 63
StorageError: Unexpected error occurred with message: Domain: [Amplify.AuthError
Code: [2
LocalizedDescription: [The operation couldn’t be completed. (Amplify.AuthError error 2.)
LocalizedFailureReason: [
LocalizedRecoverySuggestion: [
Recovery suggestion: This should not happen. There is a possibility that there is a bug if this error persists. Please take a look at https://github.com/aws-amplify/amplify-ios/issues to see if there are any existing issues that match your scenario, and file an issue with the details of the bug if there isn't. Issue encountered at:
file: ...StorageError.swift
function: recoverySuggestion
line: 63

Can you pls suggest a direction for the same?

Hi @iThink32, thanks for providing the code snippet and details of your issue regarding defaultAccessLevel.
"defaultAccessLevel": "guest" is a configuration value that allows you to specific which access level is used in the Amplify.Storage request when no accessLevel is passed in. Removing this while it defaults to guest does not do anything to the requests (since it will always default to guest). The use case of this configuration value allows you to set it to something else like "defaultAccessLevel": "protected" then your Storage requests will always use the protected access level. By doing this:
let options = StorageUploadDataRequest.Options(accessLevel: .protected,
                                                       targetIdentityId: identityID)

You're explicitly setting the access level to use protected anyways. so keeping "defaultAccessLevel": "guest" will have no impact to your app. You can verify this by adding the defaultAccessLevel back in and making the request with accessLevel protected and should continue to work as you have.

The line i has requested to remove to make it work is because it assumes only that role and nothing else can change it even if authenticated.Since the guest role uses the unauth role it will always throw 401 or 403.

Sorry I didn't quite follow this. When you provision your S3 bucket, you can decide what type of access your users have
? What kind of access do you want for Authenticated users? create/update, read, delete
? What kind of access do you want for Guest users? create/update, read, delete

You can read more about the file access levels here https://docs.amplify.aws/lib/storage/configureaccess/q/platform/ios/

@lawmicha the above fix does not work on the lastest version of CLI released a day back i.e 7.4.4

Can you expand on how this is relevant with the latest version of the CLI? What steps did you do in the CLI to provision your backend?

I set the Auth Type to NONE and injected the Authorization Header myself and all api's seem to work fine but storage returns the following
StorageError: Unexpected error occurred with message: Domain: [Amplify.AuthError

Without more details, we won't be able to debug the issue you are seeing. Would it be possible to provide us with the amplifyconfiguration.json file with the values redacted so that we can see the structure of the configuration, without leaking the actual values here.
What is the calling code for the Storage request?
Do you have a stack trace when you get this error? you can put a breakpoint and view the stack to see which methods are being called. You can copy this and paste it over here as well.

@lawmicha Can you expand on how this is relevant with the latest version of the CLI? What steps did you do in the CLI to provision your backend?

i removed the defaultAccessLevel line from amplifyConfiguration.json in the previous version and used the protectedAccessLevel in both upload and download and it worked fine.

Without more details, we won't be able to debug the issue you are seeing. Would it be possible to provide us with the amplifyconfiguration.json file with the values redacted so that we can see the structure of the configuration, without leaking the actual values here.
Sure , here is the file
{
    "UserAgent": "aws-amplify-cli/2.0",
    "Version": "1.0",
    "api": {
        "plugins": {
            "awsAPIPlugin": {
                "APIOne": {
                    "endpointType": "REST",
                    "endpoint": "https://endpoint",
                    "region": "region",
                    "authorizationType": "NONE"
                },
                .... other apis
            }
        }
    },
    "auth": {
        "plugins": {
            "awsCognitoAuthPlugin": {
                "UserAgent": "aws-amplify/cli",
                "Version": "0.1.0",
                "IdentityManager": {
                    "Default": {}
                },
                "CredentialsProvider": {
                    "CognitoIdentity": {
                        "Default": {
                            "PoolId": "PoolID",
                            "Region": "Region"
                        }
                    }
                },
                "CognitoUserPool": {
                    "Default": {
                        "PoolId": "PoodID",
                        "AppClientId": "AppClientID",
                        "Region": "Region"
                    }
                },
                "Auth": {
                    "Default": {
                        "authenticationFlowType": "USER_SRP_AUTH",
                        "loginMechanisms": [
                            "EMAIL",
                            "PHONE_NUMBER"
                        ],
                        "signupAttributes": [
                            "EMAIL"
                        ],
                        "passwordProtectionSettings": {
                            "passwordPolicyMinLength": 8,
                            "passwordPolicyCharacters": []
                        },
                        "mfaConfiguration": "ON",
                        "mfaTypes": [
                            "SMS"
                        ],
                        "verificationMechanisms": [
                            "EMAIL"
                        ]
                    }
                },
                "S3TransferUtility": {
                    "Default": {
                        "Bucket": "BucketName",
                        "Region": "Region"
                    }
                }
            }
        }
    },
    "storage": {
        "plugins": {
            "awsS3StoragePlugin": {
                "bucket": "BucketName",
                "region": "Region",
                "defaultAccessLevel": "guest"
            }
        }
    }
}

What is the calling code for the Storage request?
        let options = StorageUploadDataRequest.Options(accessLevel: .protected,
                                                       targetIdentityId: identityID)
        let uploadOperationTask = Amplify.Storage.uploadData(key: filename,
                                                             data: data,
                                                             options: options,
                                       progressListener: { (progress) in
            progressHandler?(progress)
        }, resultListener: { (result) in
            switch result {
            case Result.success :
                completion(nil)
            case let Result.failure(error):
                completion(NetworkingError.apiError(description: error.errorDescription))
                print(error)
            }
        })
        return UploadTask(task: uploadOperationTask)

Do you have a stack trace when you get this error? you can put a breakpoint and view the stack to see which methods are being called. You can copy this and paste it over here as well.
A point to be noted , it at times works but if i try it twice or thrice i get the following.Please note this is the complete log after trying three times and failing each time
StorageError: Unexpected error occurred with message: Domain: [Amplify.AuthError
Code: [2
LocalizedDescription: [The operation couldn’t be completed. (Amplify.AuthError error 2.)
LocalizedFailureReason: [
LocalizedRecoverySuggestion: [
Recovery suggestion: This should not happen. There is a possibility that there is a bug if this error persists. Please take a look at https://github.com/aws-amplify/amplify-ios/issues to see if there are any existing issues that match your scenario, and file an issue with the details of the bug if there isn't. Issue encountered at:
file: /Users/nashashank/Documents/brent/Brent-iOS/Pods/Amplify/Amplify/Categories/Storage/Error/StorageError.swift
function: recoverySuggestion
line: 63

StorageError: Unexpected error occurred with message: Domain: [Amplify.AuthError
Code: [2
LocalizedDescription: [The operation couldn’t be completed. (Amplify.AuthError error 2.)
LocalizedFailureReason: [
LocalizedRecoverySuggestion: [
Recovery suggestion: This should not happen. There is a possibility that there is a bug if this error persists. Please take a look at https://github.com/aws-amplify/amplify-ios/issues to see if there are any existing issues that match your scenario, and file an issue with the details of the bug if there isn't. Issue encountered at:
file: /Users/nashashank/Documents/brent/Brent-iOS/Pods/Amplify/Amplify/Categories/Storage/Error/StorageError.swift
function: recoverySuggestion
line: 63

StorageError: Unexpected error occurred with message: Could not retreive AWS credentials, credential value is nil or empty.
Recovery suggestion: This should not happen. There is a possibility that there is a bug if this error persists. Please take a look at https://github.com/aws-amplify/amplify-ios/issues to see if there are any existing issues that match your scenario, and file an issue with the details of the bug if there isn't. Issue encountered at:
file: /Users/nashashank/Documents/brent/Brent-iOS/Pods/Amplify/Amplify/Categories/Auth/Error/AuthError.swift
function: recoverySuggestion
line: 80

StorageError: Unexpected error occurred with message: Could not retreive AWS credentials, credential value is nil or empty.
Recovery suggestion: This should not happen. There is a possibility that there is a bug if this error persists. Please take a look at https://github.com/aws-amplify/amplify-ios/issues to see if there are any existing issues that match your scenario, and file an issue with the details of the bug if there isn't. Issue encountered at:
file: /Users/nashashank/Documents/brent/Brent-iOS/Pods/Amplify/Amplify/Categories/Auth/Error/AuthError.swift
function: recoverySuggestion
line: 80

Stack Trace:

thanks for the details @iThink32

it at times works but if i try it twice or thrice i get the following.Please note this is the complete log after trying three times and failing each time

If it works sometimes, this indicates that your backend is set up correctly with all of the IAM policies and authorization rules in place.  The logs
Could not retreive AWS credentials, credential value is nil or empty.

indicate that this may be related to a similar issue over in https://github.com/aws-amplify/amplify-ios/issues/1501
We'll keep you posted as we investigate further

sure @lawmicha

@iThink32 Please update to the latest release for Amplify and try it with your code and let us know if is now working for you.

You will see we have a fix in for Auth in a recent release.

@brennanMKE  awesome. Cool will try it out and let you know

@brennanMKE updated to the latest version and using the upload download feature from
a few days , as of now it has failed only once, would test it for a few more days and confirm the same but in a gist huge improvement and so far so good

@iThink32 That's a great improvement. We have more improvements on the way. When you do experience an issue please do not hesitate to provide the details in a new issue.

@brennanMKE guys i've discovered two more issues on using s3 a lot in the couple of days

The progress object only returns 0 or 100
i'm using the following callback

Amplify.Storage.uploadData(key: filename,
                                                             data: data,
                                                             options: options,
                                       progressListener: { (progress) in
            progressHandler?(progress)

Since yesterday s3 has become very very slow

@brennanMKE if you want i can create a new issue for the same

@iThink32 Please create new issues so we can triage them.

@brennanMKE  https://github.com/aws-amplify/amplify-ios/issues/1621 pls check this , all details specified there

authors: brennanMKE iThink32 lawmicha

repo: aws-amplify/amplify-ios


text:
Rule IDs

The documentation for rule IDs shows that they represented by [EWI]\d{4}.  Is there anything in the codebase that would prevent a longer rule ID?  For example, E95001.
I was successfully able to run it, but wanted to make sure that crafting longer IDs was not a problem for now and for future.
Thanks!

I don't have any plans on requiring that it only be 4 #s.  We use the first letter to determine the error level, the first number to try classify the error, but past that we really don't care.  I think you should be good to go.  We could also add a test for this to make sure we don't add anything in the future that would break this.

Wonderful news!!  Thanks!

authors: kddejong lingrlongr

repo: aws-cloudformation/cfn-python-lint


text:
Fix issues with spec in wafv2 RegularExpressionList

Issue #, if available:
Fix #1286
Description of changes:

Patch spec to fix an issue with wafv2 RegularExpressionList

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

Confirmed that the spec is wrong and that the new changes will both pass cfn-lint and result in a successful deployment.

@PatMyron are you saying this is wrong too? https://docs.aws.amazon.com/de_de/AWSCloudFormation/latest/UserGuide/aws-properties-wafv2-regexpatternset-regex.html

@kddejong
Resources:
  RegexPatternSet:
    Type: AWS::WAFv2::RegexPatternSet
    Properties:
      Name: Name
      Scope: REGIONAL
      RegularExpressionList:
        - RegexString: RegularExpression

also successfully deploys and now successfully lints, so this is probably fine

authors: PatMyron kddejong


text:
Structuring the organization

This may branch out into other topics/issues to help with keeping discussions scoped correctly, this is a starting place for now.
AWS Control Tower eliminates a lot of the heavy lifting when it comes to setting up a best-practices adopted organization in AWS, and some of this guidance can be found here: https://docs.aws.amazon.com/controltower/latest/userguide/aws-multi-account-landing-zone.html
When you set up a landing zone, AWS Control Tower performs the following actions in your management account on your behalf:

- Creates two AWS Organizations organizational units (OUs): Security, and Sandbox (optional), contained within the organizational root structure.
- Creates two shared accounts in the Security OU: the Log Archive account and the Audit account.
- Creates a cloud-native directory in AWS SSO, with preconfigured groups and single sign-on access.
- Applies 20 mandatory, preventive guardrails to enforce policies.
- Applies two mandatory, detective guardrails to detect configuration violations.
- Preventive guardrails are not applied to the management account.
- Except for the management account, guardrails are applied to the organization as a whole.

https://docs.aws.amazon.com/controltower/latest/userguide/how-control-tower-works.html#how-it-works-setup
Creating accounts and the non-root users to login to user-centric sandbox accounts or shared group project accounts is easy with AWS SSO: https://docs.aws.amazon.com/controltower/latest/userguide/sso.html

There's an opportunity to integrate AWS SSO with other identity sources using SAML, however, it might be advantageous to authenticate users via Slack given community members identities' are tied to a given Slack workspace.  Unfortunately it looks like this is done via OIDC: https://api.slack.com/authentication/sign-in-with-slack.  Maybe some magic/innovation can be done to bridge these technologies?

Because community members have access to AWS Credits for their personal accounts already and there is an opportunity to acquire credits to fund this AWS Organization, we should come up with a rule of what types of workloads can be deployed in this organization.  Some thoughts:

"Production" workloads that host applications / services used by the community or the public built by the community.
Development/test workloads for joint community projects -- ideally tied to/deployed from IaC repos here in Github.
Individual developer specific "sandbox" accounts

Management account setup will require a CC, as far as I know we can use a prepaid/gift CC.  With application of AWS credits and automated monitoring of billing we can ensure that workloads do not exceed any available AWS credits.
For a simple diagram (to do replace with draw.io diagram):
                                        [Management Account]
                                                 |
      [Security OU]           |           [Production OU]          |           [Sandbox OU]
            |                                    |                                  |
[Audit Acc] | [Log Acc]                   [x] | [x] | [x]                    [x] | [x] | [x]

Additional areas worth discussing:

IaC, what can be done, what can't?
What IaC tool should we use?
Additional Guardrails (SCPs/Config Rules)?
?

Just some thoughts on Organization setup and how we can tackle this problem with a layered approach:

Start with single account use - secured using best practise - for people new to AWS Cloud to use to secure their accounts which will be of value to the community right away and is the simplest use-case: setup Org with AWS SSO with users
Expand to more complex use-cases:

Billing Account --> Sandbox (simple layered approach)
Billing Account --> sandbox, dev, devops, production

Need to decide if want to automate or just document as well.  Control Tower has no real IaC automation capability right now so again this may become an additional layer - seems choice is Control Tower vs OrgFormation.

Be sure to also have a look at https://github.com/superwerker/superwerker There are existing solutions out there that do more or less exactly this.

I came across https://github.com/pepperize/cdk-organizations as well, just for completeness. I'm starting with superwerker - wait on a domain to be ready.

The organization is created via superwerker. There's plenty more to do, but we'll follow up in other issues. I've created Workloads_Test and Workloads_Prod OUs. Here's the structure to start with:

authors: aaronbrighton elthrasher tobilg walmsles


text:
Nodejs module update

Closes #86
update workshop content after code update

LGTM 👍

repo: aws-containers/ecsworkshop


text:
Bring in ACK runtime v0.15.2

Regenerates the rds-controller with the latest v0.15.2 runtime.
BREAKING CHANGES:
The DBInstance's Spec.DBSecurityGroupNames field is now renamed to just
Spec.DBSecurityGroups. It continues to be a []*string field but now
the rds-controller correctly handles comparisons for this fields value
with the returned latest observed state.
Includes changes to the generator.yaml file that instructs the
code-generator how to handle the DBSecurityGroups field on DBInstance.
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:
Upgrade to ACK runtime v0.16.5 and aws-sdk-go v1.42.0

Issue #, if available: https://github.com/aws-controllers-k8s/community/issues/1167
Description of changes:

Updates ACK runtime from v0.15.2 to v0.16.5 . This upgrades results in aws-sdk-go upgrade to v1.42.0 and controller-runtime update to v0.11.0 as well
Ignored the empty struct shape RSessionAppSettings and new resource StudioLifecycleConfig in generator.yaml file
Ignored the field RetryStrategy for the resources TrainingJob and HyperparameterTuning job in generator.yaml file; suspect that it may need custom-code/implementation will need further testing.
Ignored the field DeploymentConfig for the resource Endpoint in generator.yaml file; suspect that it may need custom-code/implementation will need further testing.
Updated the mocks to generated from new aws-sdk-go version. Also fixed some underlying bug in creating mocks from Makefile
Removed check for ack-terminal is set to False in test/e2e/tests/test_endpoint.py since the field will now be set to None on requeues instead of back to False
Call customSetOutput in sdkUpdate for ModelPackage to set the synced conditions pkg/resource/model_package/sdk.go
Added unit-tests for new late-initialized field in Notebook

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

Pushing this through so SageMaker can be updated to support the latest runtime
/lgtm

authors: RedbackThomson ryansteakley


text:
Small edits to soak tests

Description
Follow up to #65, we make some small edits to the Soak Tests:

Delete oldest snapshots in the commits/<current_commit_id>/runs/ folder as well as the commits/ folder.
With https://github.com/JasonEtco/create-an-issue/pull/114 merged, we can use the upstream JasonEtco/create-an-issue action again! (This will be broken until the next minor release)

In the long run, e.g. when upstreaming, could we extract all of these tests into an action so that we don't have to update every repo with each change?

Totally! That would be an awesome improvement 😄
I think they are well set up to be made into an action. We saw the translation to the rest of the repos go fairly smoothly, so off the top of my head as an action it would need to know the following:

The commit at which to checkout the current repo
The location on the current repo for each Sample App to build and Soak Test
A unique way to identify each Sample App (Usually "platform framework" + "auto/manual instrumentation")
AWS credentials
The Process executable name and command line command to identify the process (although  maybe we could find this out independently by checking our the diff of actual vs expected processes on a runner)
Whether to include the otlp metrics receiver (for now while some languages don't have them)

And I just realized we should probably make all the Soak Tests use OTEL_EXPORTER_OTLP_ENDPOINT=http://otel:4317 because some using http://, grpc:// or nothing at all.. I added it to this PR but it's not an urgent fix I would say 😄

repo: aws-observability/aws-otel-js


text:
fix: ParamManager cannot provide default SSM & Secrets providers

Issue #, if available: #1280
Description of changes:

It was partially fixed in https://github.com/aws-powertools/powertools-lambda-java/commit/c7aedc4d2a61013450bf472bb7a8285f8cf80e41 with the addition of constructors with no client in parameter
Completed the fix, adding the creation of the Client
Deprecated the generic method to get Providers by passing a class (will be removed in V2)

Checklist

[x] Meet tenets criteria
[x] Update tests
[ ] Update docs
[x] PR title follows conventional commit semantics

Breaking change checklist

RFC issue #:

[ ] Migration process documented
[ ] Implement warnings (if it can live side by side)

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

Codecov Report
Patch coverage: 34.28% and project coverage change: +0.10 :tada:

Comparison is base (a19def3) 79.08% compared to head (9140cf2) 79.18%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@             Coverage Diff              @@
##               main    #1282      +/-   ##
============================================
+ Coverage     79.08%   79.18%   +0.10%
- Complexity      634      639       +5
============================================
  Files            73       73
  Lines          2352     2359       +7
  Branches        256      258       +2
============================================
+ Hits           1860     1868       +8
+ Misses          412      410       -2
- Partials         80       81       +1

Impacted Files
Coverage Δ

...lambda/powertools/parameters/DynamoDbProvider.java
80.32% <8.33%> (-3.01%)
:arrow_down:

.../lambda/powertools/parameters/SecretsProvider.java
65.85% <10.00%> (-0.82%)
:arrow_down:

...azon/lambda/powertools/parameters/SSMProvider.java
87.14% <70.00%> (+6.26%)
:arrow_up:

...zon/lambda/powertools/parameters/ParamManager.java
77.77% <100.00%> (+0.85%)
:arrow_up:

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

authors: codecov-commenter jeromevdl

repo: aws-powertools/powertools-lambda-java


text:
[BUG] Auto-scrolling when not at the bottom

Describe the bug
Usually apps will not keep auto-scrolling when the user has scrolled up. When text output is still being streamed and you want to start reading, you scroll up, but the app will keep scrolling down. So you have to wait until the full output is generated to even start reading.
To Reproduce
Steps to reproduce the behavior:

Create a prompt that results in somewhat larger output, e.g., list top 100 music artists of all time.
Try reading from the beginning while the output is still being generated. You won't be able to.

Expected behavior
The "auto-scrolling" behavior should only occur when the vertical scrollbar is at the bottom already (or doesn't exist yet because the content fits into the viewport).
Environment (required):

macOS version: 13.7.1
Amazon Bedrock Client for Mac version: 1.2.4

Yup, this is annoying for long outputs, essentially making streaming response useless while you wait for full response.

This issue has been addressed in commit 9498218 and released in v1.2.6 (12f6194).
The changes include:

Added anchor-based scroll detection to prevent auto-scrolling when users manually scroll up
Maintained auto-scroll functionality only when at the bottom of the chat
Added layout delay to improve smoothness and prevent flickering

This should resolve the original issue by allowing users to read previous content while new messages are being streamed.
Please update to v1.2.6 or later to get these improvements.
/cc @alxkum @sbhal

Awesome, thank you!
One tiny thing though: it seems like the inner scrollbar gets offset by half whenever you scroll up now and that new arrow-down overlay button appears:

Here's what it looks like when at the bottom:

I'm an macOS 13.7.2

reopening the issue

authors: alxkum didhd sbhal


text:
Update Quantum_Approximate_Optimization_Algorithm.ipynb

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

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

Tests

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

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

Codecov Report
Patch and project coverage have no change.

Comparison is base (1c0819b) 100.00% compared to head (517e5d5) 100.00%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@            Coverage Diff            @@
##              main      #114   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           26        26
  Lines         1028      1028
  Branches       181       159   -22
=========================================
  Hits          1028      1028

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


text:
source .../deactivate is Deprecated

Issue #, if available:
Description of changes:
Testing Done

[ ] Notebook Instance created successfully with the Lifecycle Configuration
[ ] Notebook Instance stopped and started successfully
[ ] Documentation in the script around any network access requirements
[ ] Documentation in the script around any IAM permission requirements
[ ] CLI commands used to validate functionality on the instance
[ ] New script link and description added to README.md

# Provide your commands here
/you/commands/here

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

Hello, is this still an issue? I am able to use source deactivate just fine in the current state. If we do not hear back soon, I will close this PR for inactivity, thank you.

authors: dmlause raybellwaves


text:
MemorySize Limits

When building out Workflow1 it's failing due to MemorySize limits needing to be 3008, according to the returned build errors. I have edited the yaml to enable the maximum allowable by aws upon creation, but the result is the same: a build error due to the 3008 MemorySize req.
I'll continue to track this down and update here, but 'out of the box' (so to speak) it will seemingly fail to build.
If anyone can offer additional insight here, please do!

In workflow1_endpointbuilder/sam-app)/template.yaml the memorysize values need to be 3008 or less. Some are set to the maximum value allowed, and this gives errors once uploaded to aws. Reduce them to 3008 or below to fix.


text:
[BUG] Lambda based Youtube video transcript download seems to be blocked

Describe the bug
Filling out this field will help us investigate the issue efficiently. Providing detailed information allows us to set the appropriate priority. We appreciate your cooperation.
A clear and concise description of what the bug is.
Creating a new Bot including a knowledge base from Youtube transcriptions fails. Error in Frontend: "Failed to detect language: Could not retrieve a transcript for the video https://www.youtube.com/watch?v=Pv0cfsastFs"
This error message is misleading, because what seems to go wrong is not language detection specifically, but the whole transcript API seems to be not usable.
It took me quite some research to have good evidence that AWS owned IP addresses are (currently) blocked from Youtube transcription download. This applies at least to Lambda functions and Cloud9. Tested in us-east-1, eu-central-1 and ap-northeast-1.
To Reproduce
Filling out this field will help us investigate the issue efficiently. Providing detailed information allows us to set the appropriate priority. We appreciate your cooperation.
Steps to reproduce the behavior:

Create a new Bot, adding any arbitrary Youtube URL as part of the knowledge base. After the sync phase is done, it will show you the related error.

Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

Error situation on the Bot overview list:

The problem is caused by youtube-transcript-api library. Issues:

https://github.com/jdepoix/youtube-transcript-api/issues/293
https://github.com/jdepoix/youtube-transcript-api/issues/303

We may remove the youtube feature in the future for KB integration. Thank you for your understanding.

repo: aws-samples/bedrock-claude-chat


text:
Glue Session is Terminating before the Catalog/Manifest file is generated

Describe the bug
DBT Doc generate command is failing as the glue session is terminating after the models check is completed and command fails
Steps To Reproduce

DBT Project available
Execute dbt --debug --log-format text docs generate --profiles-dir profiles --project-dir .

Expected behavior
Glue Session should terminate only after the manifest/catalog files are generated
Screenshots and log output
2:11:28.481422 [debug] [Thread-1  ]: finished collecting timing info
12:11:28.481993 [debug] [Thread-1  ]: Began executing node model.hrs_data_lake.rebooking_previous_year_cost_center
12:11:28.482540 [debug] [Thread-1  ]: finished collecting timing info
12:11:28.483081 [debug] [Thread-1  ]: On model.hrs_data_lake.rebooking_previous_year_cost_center: Close
12:11:28.483605 [debug] [Thread-1  ]: Glue adapter: NotImplemented: close
12:11:28.484617 [debug] [Thread-1  ]: Finished running node model.hrs_data_lake.rebooking_previous_year_cost_center
12:11:28.486135 [debug] [MainThread]: Glue adapter: cleanup called
12:11:28.638774 [info ] [MainThread]: Done.
12:11:28.640883 [debug] [MainThread]: Acquiring new glue connection "generate_catalog"
12:11:28.641580 [info ] [MainThread]: Building catalog
12:11:28.653540 [debug] [ThreadPool]: Acquiring new glue connection "det_cleaned_coe_data_and_ai"
12:11:28.654383 [debug] [ThreadPool]: Opening a new connection, currently in state closed
12:11:28.655957 [debug] [ThreadPool]: Glue adapter: GlueConnection connect called
12:11:28.713079 [debug] [ThreadPool]: Glue adapter: Existing session with status : STOPPING
12:11:28.742260 [debug] [ThreadPool]: Glue adapter: GlueConnection _init_session called
12:11:28.742949 [debug] [ThreadPool]: Glue adapter: GlueConnection session_id : det-dbt-role-DataPlatform-dbt-glue-9aef80ee-db70-47be-af07-a8b625ec42fa
12:11:28.782975 [error] [ThreadPool]: Glue adapter: Error in GlueCursor execute An error occurred (InvalidInputException) when calling the RunStatement operation: Session is not ready, session_id=det-dbt-role-DataPlatform-dbt-glue-9aef80ee-db70-47be-af07-a8b625ec42fa, status=CANCELLING
12:11:28.783619 [error] [ThreadPool]: Glue adapter: Got an error when attempting to open a GlueSession : __init__() missing 2 required positional arguments: 'cmd' and 'message'
12:11:28.784474 [debug] [ThreadPool]: On det_cleaned_coe_data_and_ai: No close available on handle
12:11:28.786027 [debug] [ThreadPool]: Acquiring new glue connection "det_landing_booking_solutions"
12:11:28.787078 [warn ] [MainThread]: Encountered an error while generating catalog: Database Error
  Got an error when attempting to open a GlueSessions: __init__() missing 2 required positional arguments: 'cmd' and 'message'
12:11:28.787507 [debug] [ThreadPool]: Opening a new connection, currently in state closed
12:11:28.788219 [debug] [ThreadPool]: Glue adapter: GlueConnection connect called
12:11:28.834844 [debug] [ThreadPool]: Glue adapter: Existing session with status : STOPPING
12:11:28.862500 [debug] [ThreadPool]: Glue adapter: GlueConnection _init_session called
12:11:28.863223 [debug] [ThreadPool]: Glue adapter: GlueConnection session_id : det-dbt-role-DataPlatform-dbt-glue-9aef80ee-db70-47be-af07-a8b625ec42fa
12:11:28.927459 [error] [ThreadPool]: Glue adapter: Error in GlueCursor execute An error occurred (InvalidInputException) when calling the RunStatement operation: Session is not ready, session_id=det-dbt-role-DataPlatform-dbt-glue-9aef80ee-db70-47be-af07-a8b625ec42fa, status=CANCELLING
12:11:28.928106 [error] [ThreadPool]: Glue adapter: Got an error when attempting to open a GlueSession : __init__() missing 2 required positional arguments: 'cmd' and 'message'
12:11:28.928956 [debug] [ThreadPool]: On det_landing_booking_solutions: No close available on handle
12:11:28.930498 [debug] [ThreadPool]: Acquiring new glue connection "det_landing_itelya"
12:11:28.931252 [warn ] [MainThread]: Encountered an error while generating catalog: Database Error
  Got an error when attempting to open a GlueSessions: __init__() missing 2 required positional arguments: 'cmd' and 'message'
12:11:28.931683 [debug] [ThreadPool]: Opening a new connection, currently in state closed
12:11:28.932415 [debug] [ThreadPool]: Glue adapter: GlueConnection connect called
12:11:28.987260 [debug] [ThreadPool]: Glue adapter: Existing session with status : STOPPING
12:11:29.016899 [debug] [ThreadPool]: Glue adapter: GlueConnection _init_session called
12:11:29.017451 [debug] [ThreadPool]: Glue adapter: GlueConnection session_id : det-dbt-role-DataPlatform-dbt-glue-9aef80ee-db70-47be-af07-a8b625ec42fa
12:11:29.066314 [error] [ThreadPool]: Glue adapter: Error in GlueCursor execute An error occurred (InvalidInputException) when calling the RunStatement operation: Session is not ready, session_id=det-dbt-role-DataPlatform-dbt-glue-9aef80ee-db70-47be-af07-a8b625ec42fa, status=CANCELLING
12:11:29.066930 [error] [ThreadPool]: Glue adapter: Got an error when attempting to open a GlueSession : __init__() missing 2 required positional arguments: 'cmd' and 'message'
12:11:29.067732 [debug] [ThreadPool]: On det_landing_itelya: No close available on handle
12:11:29.069254 [debug] [ThreadPool]: Acquiring new glue connection "prod_data_platform"
12:11:29.070209 [warn ] [MainThread]: Encountered an error while generating catalog: Database Error
  Got an error when attempting to open a GlueSessions: __init__() missing 2 required positional arguments: 'cmd' and 'message'
12:11:29.070585 [debug] [ThreadPool]: Opening a new connection, currently in state closed
12:11:29.071291 [debug] [ThreadPool]: Glue adapter: GlueConnection connect called
12:11:29.110890 [debug] [ThreadPool]: Glue adapter: Existing session with status : STOPPING
12:11:29.142979 [debug] [ThreadPool]: Glue adapter: GlueConnection _init_session called
12:11:29.143556 [debug] [ThreadPool]: Glue adapter: GlueConnection session_id : det-dbt-role-DataPlatform-dbt-glue-9aef80ee-db70-47be-af07-a8b625ec42fa
12:11:29.198718 [error] [ThreadPool]: Glue adapter: Error in GlueCursor execute An error occurred (InvalidInputException) when calling the RunStatement operation: Session is not ready, session_id=det-dbt-role-DataPlatform-dbt-glue-9aef80ee-db70-47be-af07-a8b625ec42fa, status=CANCELLING
12:11:29.199293 [error] [ThreadPool]: Glue adapter: Got an error when attempting to open a GlueSession : __init__() missing 2 required positional arguments: 'cmd' and 'message'
12:11:29.200115 [debug] [ThreadPool]: On prod_data_platform: No close available on handle
12:11:29.201478 [debug] [ThreadPool]: Acquiring new glue connection "prod_landing_crm"
12:11:29.202520 [debug] [ThreadPool]: Opening a new connection, currently in state closed
12:11:29.203144 [warn ] [MainThread]: Encountered an error while generating catalog: Database Error
  Got an error when attempting to open a GlueSessions: __init__() missing 2 required positional arguments: 'cmd' and 'message'
12:11:29.203510 [debug] [ThreadPool]: Glue adapter: GlueConnection connect called
12:11:29.243523 [debug] [ThreadPool]: Glue adapter: Existing session with status : STOPPING
12:11:29.272915 [debug] [ThreadPool]: Glue adapter: GlueConnection _init_session called
12:11:29.273490 [debug] [ThreadPool]: Glue adapter: GlueConnection session_id : det-dbt-role-DataPlatform-dbt-glue-9aef80ee-db70-47be-af07-a8b625ec42fa
12:11:29.332791 [error] [ThreadPool]: Glue adapter: Error in GlueCursor execute An error occurred (InvalidInputException) when calling the RunStatement operation: Session is not ready, session_id=det-dbt-role-DataPlatform-dbt-glue-9aef80ee-db70-47be-af07-a8b625ec42fa, status=CANCELLING
12:11:29.333370 [error] [ThreadPool]: Glue adapter: Got an error when attempting to open a GlueSession : __init__() missing 2 required positional arguments: 'cmd' and 'message'
12:11:29.334149 [debug] [ThreadPool]: On prod_landing_crm: No close available on handle
12:11:29.335231 [warn ] [MainThread]: Encountered an error while generating catalog: Database Error
  Got an error when attempting to open a GlueSessions: __init__() missing 2 required positional arguments: 'cmd' and 'message'
12:11:29.353635 [error] [MainThread]: dbt encountered 5 failures while writing the catalog
12:11:29.354366 [info ] [MainThread]: Catalog written to /tmp/dbt/target/catalog.json
12:11:29.358463 [debug] [MainThread]: Sending event: {'category': 'dbt', 'action': 'invocation', 'label': 'end', 'context': [<snowplow_tracker.self_describing_json.SelfDescribingJson object at 0xffff94f7d580>, <snowplow_tracker.self_describing_json.SelfDescribingJson object at 0xffff94d9e1c0>, <snowplow_tracker.self_describing_json.SelfDescribingJson object at 0xffff95006670>]}
12:11:29.359382 [debug] [MainThread]: Flushing usage events
12:11:29.757419 [debug] [MainThread]: Glue adapter: cleanup called
sys:1: ResourceWarning: unclosed <ssl.SSLSocket fd=9, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=6, laddr=('172.17.0.3', 35068), raddr=('3.67.147.184', 443)>
sys:1: ResourceWarning: unclosed <ssl.SSLSocket fd=6, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=6, laddr=('172.17.0.3', 35734), raddr=('3.67.147.184', 443)>
sys:1: ResourceWarning: unclosed <ssl.SSLSocket fd=11, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=6, laddr=('172.17.0.3', 54878), raddr=('18.198.196.34', 443)>
sys:1: ResourceWarning: unclosed <ssl.SSLSocket fd=10, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=6, laddr=('172.17.0.3', 46734), raddr=('52.29.165.100', 443)>
sys:1: ResourceWarning: unclosed <ssl.SSLSocket fd=13, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=6, laddr=('172.17.0.3', 35108), raddr=('3.67.147.184', 443)>
sys:1: ResourceWarning: unclosed <ssl.SSLSocket fd=14, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=6, laddr=('172.17.0.3', 46754), raddr=('52.29.165.100', 443)>
sys:1: ResourceWarning: unclosed <ssl.SSLSocket fd=15, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=6, laddr=('172.17.0.3', 54588), raddr=('18.159.90.183', 443)>
sys:1: ResourceWarning: unclosed <ssl.SSLSocket fd=16, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=6, laddr=('172.17.0.3', 33282), raddr=('18.159.90.183', 443)>
sys:1: ResourceWarning: unclosed <ssl.SSLSocket fd=12, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=6, laddr=('172.17.0.3', 54892), raddr=('18.198.196.34', 443)>

System information
The output of dbt --version:
Core:
  - installed: 1.2.1
  - latest:    1.3.0 - Update available!
  Your version of dbt-core is out of date!
  You can find instructions for upgrading here:
  https://docs.getdbt.com/docs/installation
Plugins:
  - spark: 1.2.0 - Update available!
  - dbt-glue: 0.2.6

The operating system you're using:
Ubuntu 12
The output of python --version:
Python 3.8.15
Additional context
Profile Info:
hrs-data-lake:
  target: hrs-data-lake
  outputs:
    hrs-data-lake:
      type: glue
      query-comment: This is a glue dbt example
      role_arn: arn:aws:iam::xxxxxx:role/det-dbt-role-DataPlatform
      region: eu-central-1
      workers: 5
      worker_type: G.2X
      idle_timeout: 600
      schema: "det"
      database: "det_landing_data_platform"
      session_provisioning_timeout_in_seconds: 600
      location: "s3a://det-landing-data-lake/data-platform"
      glue_version: "2.0"

@adithyapathipaka were you able to resolve your issue? I too am stuck with a similar issue - https://github.com/aws-samples/dbt-glue/issues/157

@nandubatchu, I made custom fix to the code to resolve the issue. I have to check with the newer version of dbt-glue adaptor

authors: adithyapathipaka nandubatchu

repo: aws-samples/dbt-glue


text:
fix: add platform(linux_amd64)

Issue #, if available:
when deploying on a mac silicon, platform bugs occur.
so, add platform argument (linux_amd64) in docker image
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Thanks for your pull request. The issue has been solved by patching the dockerfile.
See commit: 08a3df8.
If you think changes to the cdk template are still needed to specify the platform, please tell me.

repo: aws-samples/deploy-streamlit-app