bug in example of the tsconfig.json's guide: https://www.typescriptlang.org/tsconfig/#noImplicitAny

instead of use substr() funtion, i think it have a wrong typo so now the function using is subtr()
it cause unexpected behavior when try to run example

This is an intentionally broken example, as the lack of an annotation is hiding the fact that there's a typo.


Thisyahlen/chore: add plugins for tailwind config

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
21

Relevant Lines:
21

💛  - Coveralls


[Bug] s3 endpoint issue

Bug Report
I'm facing with issue when upload to s3 bucket with moveToDisk() method via Drive if I don't have Endpoint
I see endpoint is optional props, but it required here?

Behavior
Videos still upload success into S3 bucket but it throw errors
Package version

"@adonisjs/drive-s3": "^1.3.2",
Node.js and npm version

Node 18.16.0
Sample Code

Drive config (Because I don't have endpoint)

See #15
I used
  "resolutions": {
    "@aws-sdk/client-s3": "3.190.0",
    "@aws-sdk/lib-storage": "3.190.0"
  }

to make it work.


Updating timezone cli call

The CLIs for improver generally have the ancil files loaded as the last file. This updates the CLI to match the others within the suite.
Testing:

[x] Ran tests and they passed OK
[x] Added new tests for the new feature(s)

This has become a bit of a hacky fix, to make this more robust in the future we should consider altering the interface as per https://github.com/metoppv/improver/issues/1553

No acceptance tests for this CLI in master, although we should consider it.


Add GitLab Pages template alternative

I've had some folks interested in keeping their Collection Builder site private either because it's a work in progress or they haven't sorted out usage rights yet. GitHub Pages are public (even if built from a private repo). GitLab, however, does offer access control for GitLab Pages .

thanks for the suggestion @spswanz !
I have used GitLab Pages in the past, but never documented the option. There are a few things that need to be tweaked in the template for GitLab Pages. I will work on a solution for that soon, either documentation on how to get it working or maybe a mirror set up on GitLab.

@spswanz I added some background and instructions to CB-Docs, https://collectionbuilder.github.io/cb-docs/docs/advanced/gitlab/
I still plan on checking if there is a way to add a template repository to GitLab or better way to share the template modifications.


[Extensibility Bug / Event Request] table 167 Job - OnAfterBillToCustomerNoUpdated

Could you please add the following event?
local procedure BillToCustomerNoUpdated(var Job: Record Job; var xJob: Record Job)
var
    BillToCustomer: Record Customer;
    IsHandled: Boolean;
begin
    if (Job."Bill-to Customer No." = '') or (Job."Bill-to Customer No." <> xJob."Bill-to Customer No.") then
        if Job.JobLedgEntryExist() or Job.JobPlanningLineExist() then
            Error(AssociatedEntriesExistErr, FieldCaption("Bill-to Customer No."), TableCaption);

    // Set sell-to first if it hasn't been set yet.
    if (Job."Sell-to Customer No." = '') and (Job."Bill-to Customer No." <> '') then
        Validate("Sell-to Customer No.", Job."Bill-to Customer No.");

    if Job."Bill-to Customer No." <> '' then begin
        BillToCustomer.Get(Job."Bill-to Customer No.");
        Job."Bill-to Name" := BillToCustomer.Name;
        Job."Bill-to Name 2" := BillToCustomer."Name 2";
        Job."Bill-to Address" := BillToCustomer.Address;
        Job."Bill-to Address 2" := BillToCustomer."Address 2";
        Job."Bill-to City" := BillToCustomer.City;
        Job."Bill-to Post Code" := BillToCustomer."Post Code";
        Job."Bill-to County" := BillToCustomer.County;
        Job."Bill-to Country/Region Code" := BillToCustomer."Country/Region Code";

        IsHandled := false;
        OnUpdateCustOnBeforeAssignIncoiceCurrencyCode(Job, xJob, BillToCustomer, IsHandled);

        if not IsHandled then
            "Invoice Currency Code" := BillToCustomer."Currency Code";
        if "Invoice Currency Code" <> '' then
            Validate("Currency Code", '');

        Job."Customer Disc. Group" := BillToCustomer."Customer Disc. Group";
        Job."Customer Price Group" := BillToCustomer."Customer Price Group";
        Job."Language Code" := BillToCustomer."Language Code";
        UpdateBillToContact(Job."Bill-to Customer No.");
        CopyDefaultDimensionsFromCustomer();
    end else begin
        Job."Bill-to Name" := '';
        Job."Bill-to Name 2" := '';
        Job."Bill-to Address" := '';
        Job."Bill-to Address 2" := '';
        Job."Bill-to City" := '';
        Job."Bill-to Post Code" := '';
        Job."Bill-to County" := '';
        Job."Bill-to Country/Region Code" := '';
        Job."Invoice Currency Code" := '';
        Job."Customer Disc. Group" := '';
        Job."Customer Price Group" := '';
        Job."Language Code" := '';
        Job."Bill-to Contact" := '';
        Job."Bill-to Contact No." := '';
    end;
    OnAfterBillToCustomerNoUpdated(Job, xJob, BillToCustomer); //NEW
end;

[IntegrationEvent(false, false)]
local procedure OnAfterBillToCustomerNoUpdated (var Job: Record; Job: Record Job; xJob: BillToCustomer: Record Customer)
begin
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


gh-xxx: remove the playground from docker compose

In the new docs, we refer to the playground on the website or as a separate container. People seem to use the compose file to create semi-production solutions. This seems cleaner to me.

obsolete.


Enter Model Equations

Summary
Create notebooks and enter the equations for SPM, SPMe, DFN, and Lead Acid. These equations can be used as a reference for whoever is entering the model equations in #72 #73 #74. Actual code examples will be added to these notebooks at a later date

Going to create pull request for this and then create separate issue for lead acid because it is useful to have a reference for the equations.


[Bug] Dashboard will see all Pods from different RayCluster in the same namespace

Search before asking

[X] I searched the issues and found no similar issues.

KubeRay Component
ray-operator
What happened + What you expected to happen
Dashboard will see all Pods from different RayCluster in the same namespace
Reproduction script
TODO
Anything else
No response
Are you willing to submit a PR?

[X] Yes I am willing to submit a PR!

The root cause is that the user specifies the wrong rayStartParams["address"], and the wrong configuration points to the other cluster's head Pod. Maybe we should not expose the parameter for users.

Duplicate with #976. Close this.


Upgrade to .net 4.7.2 and .net core 3 (WIP)

Hi,
I converted all projects to sdk style.
NodeNetwork & -Toolkit are now targeting .net 4.7.2 and .net core 3.
I haven't touched the code or dependencies, except:

upgraded System.Reactive & related packages to 4.2.0
project files and package files
ExampleShaderEditorApp uses .net 4.7.2
ExampleCodeGenApp & ExampleCalculatorApp use .net core 3.0

It is not ready to be deployed because there are several (light) issues:

(critical) ExampleShaderEditorApp does not build: There seems to be some dependency issue with OpenGL.net
Several warnings about not .net core compatible dependencies. Most of them are either false positives or the incompatible code is not used.

All Unit tests are passed, both ExampleCodeGenApp & ExampleCalculatorApp are working without issues.
I think it's a good start. Depending the use case, it might even be ready to use.
Greetings,
Gitii

Hi,
Thanks for your contribution! Last time I checked there were quite some issues with .net core so it's good to see that most of those seem to be resolved. A previous PR (#26) also mentioned problems with the opengl package. The issue might be solvable by using a different package or switching to directx, for which there is probably native support.
I'll look into this more at the end of this month.

Hi,
the biggest issue is OpenGL.Net which seems to have major issues with Net Core 3: https://github.com/luca-piccioni/OpenGL.Net/issues/147. Removing some props of the GL control let the build complete but the control is all black (no exceptions). I have no experience with OpenGL, maybe a different wrapper/binding is a valid solution.
There are other dependencies of NodeNetwork which are not available for Core 3 but can be used anyway (unit tests and 2/3 example apps are working...).
I recommend that you release a beta version and test the water.
There may be newer versions of some dependencies which already support Net Core 3.
I haven't touched those because I wanted to avoid any unwanted side effects (in other words bugs or api changes) when upgrading.
Greetings,
Gitii


gh #220: dsAudio L3 Test Procedure document

Create L3 Test procedure document for dsAudio

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: bhanucbp:x: TB-1993You have signed the CLA already but the status is still pending? Let us recheck it.


Be able to launch arbitrary linux binary

I think this has already been discussed but it would be nice if we could launch arbitrary linux executables from within windows. That way I could launch my favorite shell (or any other binary) without the need to open a bash window or using the bash.exe -c /path/to/binary workaround.
I myself do not use bash but instead use zsh. To be able to launch zsh you can either use bash.exe -c /bin/zsh or put /bin/zsh into your .bashrc. But either way, this still launches a bash process and is super clunky.
Temporary workaround:
I looked into bash.exe and wrote a small Python script that replaces the call to /bin/bash with any binary you like. As far as I can see, the binary name cannot exceed 16 characters but I'm not really sure.
From bash, call it like so:
$ wsl-bashexe-patcher.py /mnt/c/Windows/System32/bash.exe /bin/zsh --output zsh.exe

Cheers,
gegenschall

I agree with you that it is slightly annoying to be forced to go through bash in some cases, but I recently noticed something that mitigates that annoyance a little: it seems that if bash -c "<cmd_line>" is used with a single command for <cmd_line>, bash executes it with an exec (without a prior fork). So at least we don't have an extra bash instance just waiting in the background.
Still, the ability to run any command directly would be interesting for a number of use cases, including of course running other shells where even a transient invocation of bash is not useful, or maybe even setting up a WSL FS with no bash at all in it.

Very cool! @xilun do you think I could convince you to do an outzsh .exe ^.^

@fqpc outbash.exe is basically in the same situation as bash.exe is in that regard, because I add an extra bash call (to be performed by the WSL bash). Now I could do an optimization similar in spirit as the one GNU Bash does, and for example when called like outbash.exe -c "zsh", do an invocation of bash.exe -c "OUTBASH=port zsh" instead of what I do now: bash.exe -c "OUTBASH=port bash -c \"zsh\"". But to do that, I would need to understand more about the command line (for now I just have to escape properly). So this optimisation is not worth it given the work needed and the relatively low value it provides, because like I said the extra bash is only transient, thanks to the GNU bash optim. So without support from WSL to directly run the executable we want, I see no point in removing just an extra transient bash, given for now, without dirty hacks at least, one (at least transient) bash is already mandatory.

It's fine lol, all good =]

Is it possible to set different behaviors based on the file header on Windows? I thought it was all extension based.

@gegenschall Just out of curiosity, do you use tmux? When I use /bin/bash -c /usr/bin/zsh, $SHELL is set to bash, and even though I have run chsh to set my shell to zsh by default, each new tmux window ends up being zsh!

@hut8 echo "export SHELL=\"/bin/zsh\" > ~/.zshenv"
then just bash -c "zsh -i" and you're effectively in a zsh login shell and everything should come up zsh. (for the record i've used chsh too)

@hut8  you may also put in your .tmux.conf set -g default-shell /usr/bin/zsh.

And I configured a task like: %windir%\system32\bash.exe ~ -c zsh  -cur_console:p. Borrowed this tip from https://gist.github.com/MadLittleMods/0e38f03774fb16e8d698175e505f1f3e.

Recent insider builds have added wsl.exe which makes launching an individual Linux binary much easier.  For example:
wsl ls

I should clarify for anyone coming from Google who needs that command line for some reason: I put that last quote in the wrong spot, it should be before the > character.
Not needed for this bug anymore but you never know what a Google result can help with.


Added Sameer Bakshi

Thank you for your valuable contribution!
Make sure to leave a star ⭐ on the repo


matrix-synapse: 1.19.3 -> 1.20.1

Motivation for this change
https://github.com/matrix-org/synapse/releases/tag/v1.20.0
https://github.com/matrix-org/synapse/releases/tag/v1.20.1
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Ported to stable as e7c26a78e640d2a8032665c1f8d8e3f6078ddae5.

1.20 rc1 has a fix for https://github.com/matrix-org/synapse/issues/8220
without which logs are spammed with user directory errors. And crashing the user directory because a server sent an invalid display name.
That could count as a partial denial of service vulnerability 🤷

cc @Ekleog what do you think of it?

@dali99 What do you mean by “crashing the user directory”? I can't find this in the issue you linked.
As for the part about synapse spamming logs… my synapse instance, on which we are fewer than 5 users, logged ~375k log lines yesterday using more or less the nixos-default configuration, without this bug happening (tested by grepping for InvalidTextRepresentation). Would this bug make the behavior significantly worse? Having tracebacks in the logs is something I remember synapse regularly doing (though I guess it happens less nowadays), so unless it'd increase by an order of magnitude I'm not sure it's worth risking backwards-compatibility breakage so close to 20.03 EOL?

The user directory background process, crashes, and immediately retries, not processing any updates, of course immediately crashing again. repeat multiple times per second. When the user directory crashes that means new users the server sees won't be processed, which means the user directory won't show them to you when you search for their usernames when you want to invite them or otherwise.
@Ekleog in the past 24 hours my synapse has logged 10 027 118 lines.  And that is with a log level changed up from nixos default INFO to WARN. With this specific traceback occuring 2-4 times per second at the error log level.
I have a suspicion that this bug is also what's causing my synapse to idle at 70% CPU.
As for where this is described in the issue I linked:

User directory gets stuck

The main issue is that the error path seems to continue throwing errors and stops making progress.

Thank you for your feedback!
I… guess this is worth backporting to 20.03, then? My problem with this is, reading the backwards-compatibility issue, it looks like clients that are even just 5 months old are currently incompatible with the new synapse release…
I guess I'll just yell at synapse in my head again and we can backport the update to 20.03, as FluffyChat doesn't look widely-used… if that's also the way you feel, @Ma27?

Tbh I deferred the debate to this thread since I don't have a strong opinion about it (all of my systems are already using a recent version of release-20.09).
However we have people here experiencing this issue and I actually established a backport-by-default policy for matrix-synapse about a year ago, so I'm fine with it and would take care of it now.
While some clients seem to have issues with v1.20.0 now, we shouldn't forget that (1) the client violated the protocol and (2) the most famous example (fluffychat) has fixed the issue already[1].
[1] https://github.com/matrix-org/synapse/issues/6766#issuecomment-614828363

Ported to 20.03 as 760c6ec78cd6d8d658266ac28434a3b04a9e4cbb now.


Unable to close "Show Scrollback Buffer" window in split mode

Bug description
When we are using Split Mode with the "Show Scrollback Buffer" => the cross to close the window is hidden
From Benjamin by email

Canceling this issue in favor of #722

Reopening

Will be available in a few hours

Available inside the latest beta release : /https://testflight.apple.com/join/QSrBK59z


feat(theme): use guardian theme

pull in theme and completely remove all theme files and styling from this repo
cleanup old deps and plugins (removed jekyll-assets and jekyll-git_metadata, as well as compass)
reference latest up-to-date github pages deps and use github-pages gem directly
remove deprecated travis ci file
slight modifications were performed within the 2019-01-14-A-Tale-of-Performance---Javascript,-Rust,-and-WebAssembly.md post to use proper variable interpolation, but it appears some whitespace was also touched by my IDE

Edit: I reverted the removal of the .travis.yml file as it appears as thought we still rely on that CI pipeline to build our blog... I don't want to mess with overhauling the build within this branch, but I can re-work things in a new branch (either making use of Buildkite or just having GitHub handle the build for us).


Meet GitHub's Recommended Community Standards

As indicated on the Community page for the botbuilder-dotnet repo, we don't yet meet the recommended standards for public GitHub projects.
For the dotnet and js repos we're currently missing the following:

[ ] Code of Conduct
[ ] Contributing guide
[ ] Issue Templates
[ ] PR templates

We should have a discussion and decide what we want to use going forward.
There are a plethora of more mature projects that have Issue and PR Templates (TypeScript and VS Code) that we can draw inspiration from. We could also look at the botbuilder-tools repo and a (somewhat) simpler issue template in the v3 repo.

I like what vscode and typescript are doing.  vscode has a well structure repo regarding almost all of the above dimensions
Top line page:  https://github.com/Microsoft/vscode
Code of conduct:  https://github.com/Microsoft/vscode/blob/master/CODE_OF_CONDUCT.md
Contributing guide:  https://github.com/Microsoft/vscode/blob/master/CONTRIBUTING.md
Issues:  vscode & typescript gives choices for the type of issue that could be logged
https://github.com/Microsoft/vscode/issues/new/choose
Bugs:  https://github.com/Microsoft/vscode/issues/new?template=bug_report.md
Feature request:  https://github.com/Microsoft/vscode/issues/new?template=feature_request.md
Questions:  https://github.com/Microsoft/vscode/issues/new?template=question.md

Majority of related repos include some language around contribution and code of conduct that is standard MS style.
If we decided to follow VSCode structure, we need to bring all BotBuilder and BotFramrwork related repos to the same levels
https://github.com/Microsoft/BotBuilder
https://github.com/microsoft/botbuilder-tools
https://github.com/Microsoft/botbuilder-java
https://github.com/Microsoft/botbuilder-js
https://github.com/Microsoft/botbuilder-dotnet
https://github.com/Microsoft/botbuilder-python
https://github.com/Microsoft/Botbuilder-samples https://github.com/Microsoft/BotFramework-WebChat
https://github.com/microsoft/botframework-emulator

rename our 'doc' folder to 'docs'

For the CONTRIBUTING.md we should be sure to convey our expectations for PRs; some of them being usage of the linters like TSLint and StyleCop, and that unit tests are also attached to PRs.
We should also decide if we want community members to file a corresponding issue for every PR (some large projects/communities do set that as a requirement to have a discussion before a PR even gets broached).

This is done. All our repos have been updated but we should take another pass to make sure everything is correct so leaving this issue open.

Closing due to lack of activity. Let's create new issues for any one off improvements we need to make.


Use go-proxyproto in fallbacks

Use go-proxyproto to format Proxy Protocol in VLESS and Trojan fallbacks. After changing to go-proxyproto, the Proxy Protocol in the fallbacks will support more protocols, such as Unix Socket.

Codecov Report

Merging #1418 (06fe5dd) into master (7413246) will increase coverage by 0.04%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master    #1418      +/-   ##
==========================================
+ Coverage   39.63%   39.67%   +0.04%
==========================================
  Files         598      598
  Lines       35041    34985      -56
==========================================
- Hits        13887    13881       -6
+ Misses      19637    19586      -51
- Partials     1517     1518       +1

Impacted Files
Coverage Δ

proxy/trojan/server.go
0.43% <0.00%> (+0.04%)
:arrow_up:

proxy/vless/inbound/inbound.go
0.46% <0.00%> (+0.05%)
:arrow_up:

app/router/command/errors.generated.go
0.00% <0.00%> (-100.00%)
:arrow_down:

transport/internet/kcp/dialer.go
80.39% <0.00%> (-3.93%)
:arrow_down:

app/router/command/command.go
36.92% <0.00%> (-3.08%)
:arrow_down:

transport/internet/kcp/connection.go
71.82% <0.00%> (-0.56%)
:arrow_down:

common/task/periodic.go
75.60% <0.00%> (+4.87%)
:arrow_up:

Continue to review full report at Codecov.

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

please support Unix Socket.

It has been open 120 days with no activity. Remove stale label or comment or this will be closed in 5 days

Remove stale label


Update CI/CD builder image

I updated the version here to one that is tied to an actual commit ID in the builders repo.
I thought about updating this PR with some code that would automatically pull the latest builder image instead of using a hardcoded one, but I will move that into a separate PR to fast-track this.


gazeta.pl

Match found in https://hosts.ubuntu101.co.za/hosts:
czat.gazeta.pl
kuchnia.gazeta.pl
metro.gazeta.pl
poczta.gazeta.pl
sklep.gazeta.pl
sport.gazeta.pl
wyborcza.gazeta.pl
from wiki:
Gazeta.pl - Polish internet portal, mass information and entertainment medium with an extensive user community and a wide group of thematic websites, tools and services that meet everyday needs: information, advice, exchange of opinions, communication, entertainment, filling time.
The websites of the Gazeta.pl group are visited by 11.14 million users per month.
Gazeta.pl is available via traditional www, mobile version and via the application for mobile devices and smart TV.
The publisher of Gazeta.pl portal is Agora SA.

czat.gazeta.pl ==> forum.gazeta.pl
kuchnia.gazeta.pl ==> ugotuj.to
metro.gazeta.pl ==> avanti24.pl
poczta.gazeta.pl ==> auth.gazeta.pl
sklep.gazeta.pl ==> www.gazeta.pl
sport.gazeta.pl ==> sport.pl
wyborcza.gazeta.pl ==> wyborcza.pl
Not whitelisting.


Improve performance/reduce allocs of bytespipe

Creates a fixedBuffer type that is used to encapsulate functionality
for reading/writing from the underlying byte slices.
Uses lazily-loaded set of sync.Pools for storing buffers that are no
longer needed so they can be re-used.
benchmark                     old ns/op     new ns/op     delta
BenchmarkBytesPipeWrite-8     138469        48985         -64.62%
BenchmarkBytesPipeRead-8      130922        56601         -56.77%

benchmark                     old allocs     new allocs     delta
BenchmarkBytesPipeWrite-8     18             8              -55.56%
BenchmarkBytesPipeRead-8      0              0              +0.00%

benchmark                     old bytes     new bytes     delta
BenchmarkBytesPipeWrite-8     66903         1649          -97.54%
BenchmarkBytesPipeRead-8      0             1             +Inf%

Signed-off-by: Brian Goff<EMAIL_ADDRESS>

ping @aaronlehmann

I'm not sure, but won't pools map uncontrollably grow?

LGTM


Snippet link in readme is broken

Hey, the snippet link in the README is a 404. Just wanted to let you know.
curl -L git.io/snippet >> ~/.config/fish/config.fish

Thanks for the report, the snippet is no longer necessary, since I think it
can be expected that users have fish version >2.3 (except for Ubuntu, where
they will have to add a PPA).
I'll put up a new one just in case and fix it when I get access to my
computer. Thanks!
On 3 Aug 2016 3:13 PM, "Oskar"<EMAIL_ADDRESS>wrote:

Hey, the snippet link in the README is a 404. Just wanted to let you know.
curl -L git.io/snippet >> ~/.config/fish/config.fish
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

That should do it (:


[BAT]Bug fix

Coverage decreased (-0.05%) to 54.827% when pulling 3c64ae340ea2d99ce77f2fffc0b861d3f7512d39 on ywk253100:170808_bug_fix into 49f52ef8f8a55401d004b19f0335fb0b285b37dc on vmware:master.


[master] Bump Mesos to nightly master 7bfec08

High-level description
This is a routine bump to the latest Mesos and mesos-modules.
Related JIRA Issues
Checklist for all PRs

[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain here:
[x] Read the DC/OS contributing guidelines
[x] Followed relevant code rules Rules for Packages and Systemd

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[x] Changelog:
https://github.com/apache/mesos/compare/a5d6635b351d1b357e9fcc396b155cccfad6aae5...7bfec082b83bb898c3c45457d2967685d90b663f
https://github.com/dcos/dcos-mesos-modules/compare/0ed50a4d16dc560554f3abe843f2e0af4f52fcba...23f9313b6c2c4ca7973092c69342033f23c2342a

[ ] Test Results: [link to CI job test results for component]

[ ] Code Coverage (if available): [link to code coverage report]

Closed in lieu of https://github.com/dcos/dcos/pull/4402


Question: How would you make a batch file that would auto add WUA files for decompression?

Converted my games to WUA format and wanting to try take the icon and background files and use them for stuff but that requires they be decompressed to access them.
Any way I could create a batch file that would just auto decompress every WUA file in a directory?
Tried to make it myself but the majority of my command line knowledge left me about 20 years ago.
Thank you in advance for your time, much appreciated.
Off-topic: Now that I think about it, Cemu could probably start using them itself and make its own mock up of the Wii U interface with them.

The for loop in batch files is a little... unwieldy for users of any other shell script language (like me). If I'm reading https://ss64.com/nt/for.html right, it's something like:
FOR %%x IN (*.wua) DO zarchive "%%x" "%%~nx"

That should take, e.g. 1.wua and pop it in a folder called "1".

above is not quite working. Any way you can add a wildcard option to zarchive so we can just do zarchive . and decompress all WUAs in the directory?


Cant download packages from NuGet on Visual Studio 2022 v17.8.5

Impact
I'm unable to use NuGet.org
Describe the bug
Hi. I cant download packages from NuGet, im getting an errors like below in screenshot:

This is result of "dotnet nuget verify" command:
C:\Users\sabina\Desktop>dotnet nuget verify "system.data.sqlclient.4.8.6.nupkg" -v d
X.509 certificate chain validation will use the default trust store selected by .NET for code signing.
X.509 certificate chain validation will use the default trust store selected by .NET for timestamping.

Verifying System.Data.SqlClient.4.8.6
C:\Users\sabina\Desktop\system.data.sqlclient.4.8.6.nupkg
Signature Hash Algorithm: SHA256

Signature type: Author
Verifying the author primary signature with certificate:
  Subject Name: CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US
  SHA1 hash: F25C45D17C53D4E0D1DC9FB9DFD0731FCF904B77
  SHA256 hash: 566A31882BE208BE4422F7CFD66ED09F5D4524A5994F50CCC8B05EC0528C1353
  Issued by: CN=DigiCert Trusted G4 Code Signing RSA4096 SHA384 2021 CA1, O="DigiCert, Inc.", C=US
  Valid from: 27.07.2023 04:00:00 to 18.10.2026 03:59:59
trace:       Subject Name: CN=DigiCert Trusted G4 Code Signing RSA4096 SHA384 2021 CA1, O="DigiCert, Inc.", C=US
trace:       SHA1 hash: 7B0F360B775F76C94A12CA48445AA2D2A875701C
trace:       SHA256 hash: 46011EDE1C147EB2BC731A539B7C047B7EE93E48B9D3C3BA710CE132BBDFAC6B
trace:       Issued by: CN=DigiCert Trusted Root G4, OU=www.digicert.com, O=DigiCert Inc, C=US
trace:       Valid from: 29.04.2021 04:00:00 to 29.04.2036 03:59:59
trace:             Subject Name: CN=DigiCert Trusted Root G4, OU=www.digicert.com, O=DigiCert Inc, C=US
trace:             SHA1 hash: DDFB16CD4931C973A2037D3FC83A4D7D775D05E4
trace:             SHA256 hash: 552F7BDCF1A7AF9E6CE672017F4F12ABF77240C78E761AC203D1D9D20AC89988
trace:             Issued by: CN=DigiCert Trusted Root G4, OU=www.digicert.com, O=DigiCert Inc, C=US
trace:             Valid from: 01.08.2013 17:00:00 to 15.01.2038 16:00:00
Timestamp: 27.10.2023 04:01:10
Verifying author primary signature's timestamp with timestamping service certificate:
  Subject Name: CN=DigiCert Timestamp 2023, O="DigiCert, Inc.", C=US
  SHA1 hash: 66F02B32C2C2C90F825DCEAA8AC9C64F199CCF40
  SHA256 hash: D2F6E46DED7422CCD1D440576841366F828ADA559AAE3316AF4D1A9AD40C7828
  Issued by: CN=DigiCert Trusted G4 RSA4096 SHA256 TimeStamping CA, O="DigiCert, Inc.", C=US
  Valid from: 14.07.2023 04:00:00 to 14.10.2034 03:59:59
trace:       Subject Name: CN=DigiCert Trusted G4 RSA4096 SHA256 TimeStamping CA, O="DigiCert, Inc.", C=US
trace:       SHA1 hash: B6C8AF834D4E53B673C76872AA8C950C7C54DF5F
trace:       SHA256 hash: 281734D4592D1291D27190709CB510B07E22C405D5E0D6119B70E73589F98ACF
trace:       Issued by: CN=DigiCert Trusted Root G4, OU=www.digicert.com, O=DigiCert Inc, C=US
trace:       Valid from: 23.03.2022 04:00:00 to 23.03.2037 03:59:59
trace:             Subject Name: CN=DigiCert Trusted Root G4, OU=www.digicert.com, O=DigiCert Inc, C=US
trace:             SHA1 hash: A99D5B79E9F1CDA59CDAB6373169D5353F5874C6
trace:             SHA256 hash: 33846B545A49C9BE4903C60E01713C1BD4E4EF31EA65CD95D69E62794F30B941
trace:             Issued by: CN=DigiCert Assured ID Root CA, OU=www.digicert.com, O=DigiCert Inc, C=US
trace:             Valid from: 01.08.2022 04:00:00 to 10.11.2031 03:59:59
trace:                   Subject Name: CN=DigiCert Assured ID Root CA, OU=www.digicert.com, O=DigiCert Inc, C=US
trace:                   SHA1 hash: 0563B8630D62D75ABBC8AB1E4BDFB5A899B24D43
trace:                   SHA256 hash: 3E9099B5015E8F486C00BCEA9D111EE721FABA355A89BCF1DF69561E3DC6325C
trace:                   Issued by: CN=DigiCert Assured ID Root CA, OU=www.digicert.com, O=DigiCert Inc, C=US
trace:                   Valid from: 10.11.2006 04:00:00 to 10.11.2031 04:00:00

Signature type: Repository
Service index: https://api.nuget.org/v3/index.json
Owners: dotnetframework, Microsoft
Verifying the repository countersignature with certificate:
  Subject Name: CN=NuGet.org Repository by Microsoft, O=NuGet.org Repository by Microsoft, L=Redmond, S=Washington, C=US
  SHA1 hash: 68FC37CCC293766A607DBC26A26DF371B0249328
  SHA256 hash: 5A2901D6ADA3D18260B9C6DFE2133C95D74B9EEF6AE0E5DC334C8454D1477DF4
  Issued by: CN=DigiCert SHA2 Assured ID Code Signing CA, OU=www.digicert.com, O=DigiCert Inc, C=US
  Valid from: 16.02.2021 04:00:00 to 16.05.2024 03:59:59
trace:       Subject Name: CN=DigiCert SHA2 Assured ID Code Signing CA, OU=www.digicert.com, O=DigiCert Inc, C=US
trace:       SHA1 hash: 92C1588E85AF2201CE7915E8538B492F605B80C6
trace:       SHA256 hash: 51044706BD237B91B89B781337E6D62656C69F0FCFFBE8E43741367948127862
trace:       Issued by: CN=DigiCert Assured ID Root CA, OU=www.digicert.com, O=DigiCert Inc, C=US
trace:       Valid from: 22.10.2013 17:00:00 to 22.10.2028 16:00:00
trace:             Subject Name: CN=DigiCert Assured ID Root CA, OU=www.digicert.com, O=DigiCert Inc, C=US
trace:             SHA1 hash: 0563B8630D62D75ABBC8AB1E4BDFB5A899B24D43
trace:             SHA256 hash: 3E9099B5015E8F486C00BCEA9D111EE721FABA355A89BCF1DF69561E3DC6325C
trace:             Issued by: CN=DigiCert Assured ID Root CA, OU=www.digicert.com, O=DigiCert Inc, C=US
trace:             Valid from: 10.11.2006 04:00:00 to 10.11.2031 04:00:00
Timestamp: 09.01.2024 18:41:28
Verifying repository countersignature's timestamp with timestamping service certificate:
  Subject Name: CN=DigiCert Timestamp 2023, O="DigiCert, Inc.", C=US
  SHA1 hash: 66F02B32C2C2C90F825DCEAA8AC9C64F199CCF40
  SHA256 hash: D2F6E46DED7422CCD1D440576841366F828ADA559AAE3316AF4D1A9AD40C7828
  Issued by: CN=DigiCert Trusted G4 RSA4096 SHA256 TimeStamping CA, O="DigiCert, Inc.", C=US
  Valid from: 14.07.2023 04:00:00 to 14.10.2034 03:59:59
trace:       Subject Name: CN=DigiCert Trusted G4 RSA4096 SHA256 TimeStamping CA, O="DigiCert, Inc.", C=US
trace:       SHA1 hash: B6C8AF834D4E53B673C76872AA8C950C7C54DF5F
trace:       SHA256 hash: 281734D4592D1291D27190709CB510B07E22C405D5E0D6119B70E73589F98ACF
trace:       Issued by: CN=DigiCert Trusted Root G4, OU=www.digicert.com, O=DigiCert Inc, C=US
trace:       Valid from: 23.03.2022 04:00:00 to 23.03.2037 03:59:59
trace:             Subject Name: CN=DigiCert Trusted Root G4, OU=www.digicert.com, O=DigiCert Inc, C=US
trace:             SHA1 hash: A99D5B79E9F1CDA59CDAB6373169D5353F5874C6
trace:             SHA256 hash: 33846B545A49C9BE4903C60E01713C1BD4E4EF31EA65CD95D69E62794F30B941
trace:             Issued by: CN=DigiCert Assured ID Root CA, OU=www.digicert.com, O=DigiCert Inc, C=US
trace:             Valid from: 01.08.2022 04:00:00 to 10.11.2031 03:59:59
trace:                   Subject Name: CN=DigiCert Assured ID Root CA, OU=www.digicert.com, O=DigiCert Inc, C=US
trace:                   SHA1 hash: 0563B8630D62D75ABBC8AB1E4BDFB5A899B24D43
trace:                   SHA256 hash: 3E9099B5015E8F486C00BCEA9D111EE721FABA355A89BCF1DF69561E3DC6325C
trace:                   Issued by: CN=DigiCert Assured ID Root CA, OU=www.digicert.com, O=DigiCert Inc, C=US
trace:                   Valid from: 10.11.2006 04:00:00 to 10.11.2031 04:00:00

Successfully verified package 'System.Data.SqlClient.4.8.6'.

Repro Steps
...
Expected Behavior
...
Screenshots
...
Additional Context and logs
...

@erdembayar

@sabinaqurbanova
Thank you for creating this issue.

Could please share dotnet --version details and VS version?
Could you please check code repository root has a nuget.config file in it?
If yes then does it have trustedSigners section in it?
Or check your detault one %AppData%\NuGet\NuGet.config
Could you please run otnet nuget verify system.security.accesscontrol.4.7.0.nupkg -v d from C:\Program Files (x86)\Microsoft SDKs\NuGetPackages\system.security.accesscontrol\4.7.0 and share with us?

Alternatively you can create issue with https://learn.microsoft.com/en-us/visualstudio/ide/how-to-report-a-problem-with-visual-studio?view=vs-2022 where it picks up necessary ambient information during feedback creation.

"dotnet --version" result:

C:\Users\sabina>dotnet --version
8.0.101

content of "%AppData%\NuGet\NuGet.config" is:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <packageSources>
    <add key="nuget.org" value="https://api.nuget.org/v3/index.json" protocolVersion="3" />
  </packageSources>
</configuration>

i ddnt understand what u mean with: "Could you please check code repository root has a nuget.config file in it?", what means "code repository root"?

result of "dotnet nuget verify":

C:\Program Files (x86)\Microsoft SDKs\NuGetPackages\system.security.accesscontrol\4.7.0\system.security.accesscontrol.4.7.0.nupkg
Signature Hash Algorithm: SHA256

Signature type: Author
Verifying the author primary signature with certificate:
  Subject Name: CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US
  SHA1 hash: F404000FB11E61F446529981C7059A76C061631E
  SHA256 hash: 3F9001EA83C560D712C24CF213C3D312CB3BFF51EE89435D3430BD06B5D0EECE
  Issued by: CN=DigiCert SHA2 Assured ID Code Signing CA, OU=www.digicert.com, O=DigiCert Inc, C=US
  Valid from: 26.02.2018 04:00:00 to 27.01.2021 16:00:00
trace:       Subject Name: CN=DigiCert SHA2 Assured ID Code Signing CA, OU=www.digicert.com, O=DigiCert Inc, C=US
trace:       SHA1 hash: 92C1588E85AF2201CE7915E8538B492F605B80C6
trace:       SHA256 hash: 51044706BD237B91B89B781337E6D62656C69F0FCFFBE8E43741367948127862
trace:       Issued by: CN=DigiCert Assured ID Root CA, OU=www.digicert.com, O=DigiCert Inc, C=US
trace:       Valid from: 22.10.2013 17:00:00 to 22.10.2028 16:00:00
trace:             Subject Name: CN=DigiCert Assured ID Root CA, OU=www.digicert.com, O=DigiCert Inc, C=US
trace:             SHA1 hash: 0563B8630D62D75ABBC8AB1E4BDFB5A899B24D43
trace:             SHA256 hash: 3E9099B5015E8F486C00BCEA9D111EE721FABA355A89BCF1DF69561E3DC6325C
trace:             Issued by: CN=DigiCert Assured ID Root CA, OU=www.digicert.com, O=DigiCert Inc, C=US
trace:             Valid from: 10.11.2006 04:00:00 to 10.11.2031 04:00:00
Timestamp: 15.11.2019 13:52:52
Verifying author primary signature's timestamp with timestamping service certificate:
  Subject Name: CN=Symantec SHA256 TimeStamping Signer - G3, OU=Symantec Trust Network, O=Symantec Corporation, C=US
  SHA1 hash: A9A4121063D71D48E8529A4681DE803E3E7954B0
  SHA256 hash: C474CE76007D02394E0DA5E4DE7C14C680F9E282013CFEF653EF5DB71FDF61F8
  Issued by: CN=Symantec SHA256 TimeStamping CA, OU=Symantec Trust Network, O=Symantec Corporation, C=US
  Valid from: 23.12.2017 04:00:00 to 23.03.2029 03:59:59
trace:       Subject Name: CN=Symantec SHA256 TimeStamping CA, OU=Symantec Trust Network, O=Symantec Corporation, C=US
trace:       SHA1 hash: 6FC9EDB5E00AB64151C1CDFCAC74AD2C7B7E3BE4
trace:       SHA256 hash: F3516DDCC8AFC808788BD8B0E840BDA2B5E23C6244252CA3000BB6C87170402A
trace:       Issued by: CN=VeriSign Universal Root Certification Authority, OU="(c) 2008 VeriSign, Inc. - For authorized use only", OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US
trace:       Valid from: 12.01.2016 04:00:00 to 12.01.2031 03:59:59
trace:             Subject Name: CN=VeriSign Universal Root Certification Authority, OU="(c) 2008 VeriSign, Inc. - For authorized use only", OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US
trace:             SHA1 hash: 3679CA35668772304D30A5FB873B0FA77BB70D54
trace:             SHA256 hash:<PHONE_NUMBER>A57125DE8CEFEA610DDF2FA078B5C8067F4E828290BFB860E84B3C
trace:             Issued by: CN=VeriSign Universal Root Certification Authority, OU="(c) 2008 VeriSign, Inc. - For authorized use only", OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US
trace:             Valid from: 02.04.2008 05:00:00 to 02.12.2037 03:59:59
debug: author primary signature's timestamp

Signature type: Repository
Service index: https://api.nuget.org/v3/index.json
Owners: dotnetframework, Microsoft
Verifying the repository countersignature with certificate:
  Subject Name: CN=NuGet.org Repository by Microsoft, O=NuGet.org Repository by Microsoft, L=Redmond, S=Washington, C=US
  SHA1 hash: 8FB6D7FCF7AD49EB774446EFE778B33365BB7BFB
  SHA256 hash: 0E5F38F57DC1BCC806D8494F4F90FBCEDD988B46760709CBEEC6F4219AA6157D
  Issued by: CN=DigiCert SHA2 Assured ID Code Signing CA, OU=www.digicert.com, O=DigiCert Inc, C=US
  Valid from: 10.04.2018 04:00:00 to 14.04.2021 16:00:00
trace:       Subject Name: CN=DigiCert SHA2 Assured ID Code Signing CA, OU=www.digicert.com, O=DigiCert Inc, C=US
trace:       SHA1 hash: 92C1588E85AF2201CE7915E8538B492F605B80C6
trace:       SHA256 hash: 51044706BD237B91B89B781337E6D62656C69F0FCFFBE8E43741367948127862
trace:       Issued by: CN=DigiCert Assured ID Root CA, OU=www.digicert.com, O=DigiCert Inc, C=US
trace:       Valid from: 22.10.2013 17:00:00 to 22.10.2028 16:00:00
trace:             Subject Name: CN=DigiCert Assured ID Root CA, OU=www.digicert.com, O=DigiCert Inc, C=US
trace:             SHA1 hash: 0563B8630D62D75ABBC8AB1E4BDFB5A899B24D43
trace:             SHA256 hash: 3E9099B5015E8F486C00BCEA9D111EE721FABA355A89BCF1DF69561E3DC6325C
trace:             Issued by: CN=DigiCert Assured ID Root CA, OU=www.digicert.com, O=DigiCert Inc, C=US
trace:             Valid from: 10.11.2006 04:00:00 to 10.11.2031 04:00:00
Timestamp: 03.12.2019 20:41:56
Verifying repository countersignature's timestamp with timestamping service certificate:
  Subject Name: CN=Symantec SHA256 TimeStamping Signer - G3, OU=Symantec Trust Network, O=Symantec Corporation, C=US
  SHA1 hash: A9A4121063D71D48E8529A4681DE803E3E7954B0
  SHA256 hash: C474CE76007D02394E0DA5E4DE7C14C680F9E282013CFEF653EF5DB71FDF61F8
  Issued by: CN=Symantec SHA256 TimeStamping CA, OU=Symantec Trust Network, O=Symantec Corporation, C=US
  Valid from: 23.12.2017 04:00:00 to 23.03.2029 03:59:59
trace:       Subject Name: CN=Symantec SHA256 TimeStamping CA, OU=Symantec Trust Network, O=Symantec Corporation, C=US
trace:       SHA1 hash: 6FC9EDB5E00AB64151C1CDFCAC74AD2C7B7E3BE4
trace:       SHA256 hash: F3516DDCC8AFC808788BD8B0E840BDA2B5E23C6244252CA3000BB6C87170402A
trace:       Issued by: CN=VeriSign Universal Root Certification Authority, OU="(c) 2008 VeriSign, Inc. - For authorized use only", OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US
trace:       Valid from: 12.01.2016 04:00:00 to 12.01.2031 03:59:59
trace:             Subject Name: CN=VeriSign Universal Root Certification Authority, OU="(c) 2008 VeriSign, Inc. - For authorized use only", OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US
trace:             SHA1 hash: 3679CA35668772304D30A5FB873B0FA77BB70D54
trace:             SHA256 hash:<PHONE_NUMBER>A57125DE8CEFEA610DDF2FA078B5C8067F4E828290BFB860E84B3C
trace:             Issued by: CN=VeriSign Universal Root Certification Authority, OU="(c) 2008 VeriSign, Inc. - For authorized use only", OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US
trace:             Valid from: 02.04.2008 05:00:00 to 02.12.2037 03:59:59
debug: repository countersignature's timestamp

Finished with 4 errors and 4 warnings.
error: NU3037: The author primary signature validity period has expired.
error: NU3028: The author primary signature's timestamping certificate is not trusted by the trust provider.
warn : NU3028: The author primary signature's timestamp found a chain building issue: The revocation function was unable to check revocation because the revocation server could not be reached. For more information, visit https://aka.ms/certificateRevocationMode.
warn : NU3028: The author primary signature's timestamp found a chain building issue: RevocationStatusUnknown: The revocation function was unable to check revocation for the certificate.
error: NU3037: The repository countersignature validity period has expired.
error: NU3028: The repository countersignature's timestamping certificate is not trusted by the trust provider.
warn : NU3028: The repository countersignature's timestamp found a chain building issue: The revocation function was unable to check revocation because the revocation server could not be reached. For more information, visit https://aka.ms/certificateRevocationMode.
warn : NU3028: The repository countersignature's timestamp found a chain building issue: RevocationStatusUnknown: The revocation function was unable to check revocation for the certificate.

Package signature validation failed.

@sabinaqurbanova
It looks like there is problem with Timestamp server certificate.

i ddnt understand what u mean with: "Could you please check code repository root has a nuget.config file in it?", what means "code repository root"?

The term "code repository root" refers to the top-level directory of a code repository where all the files and folders related to a project are stored. In version control systems like Git, the repository root is the starting point of your project's file structure and includes all the branches, tags, and commits that constitute the project's history.
Open Windows’ “manage computer certificates” app, and go to the certificates in the “trusted root certificate authorities” folder. There I can find that same “DigiCert Assured ID Root CA” and "VeriSign Universal Root Certification Authority" with same details as your log. When I open it and look at the details, I see the signature algorithm is SHA1 and the thumbprint matches the SHA1 hash that the dotnet nuget verify command above output.
You can use powershell script too, then thumbprints should match SHA1 from your log, see redmarked ones 0563B8630D62D75ABBC8AB1E4BDFB5A899B24D43, 3679CA35668772304D30A5FB873B0FA77BB70D54, if you're missing them then you need to manually install them using pem/pfx file:
Get-ChildItem -Path Cert:\CurrentUser\Root | Where-Object {$_.Subject -like "*DigiCert Assured ID Root CA*"} | Select-Object
Get-ChildItem -Path Cert:\CurrentUser\Root | Where-Object {$_.Subject -like "*VeriSign Universal Root Certification Authority*"} | Select-Object Thumbprint

@sabinaqurbanova
It looks like there is problem with Timestamp server certificate.

i ddnt understand what u mean with: "Could you please check code repository root has a nuget.config file in it?", what means "code repository root"?

The term "code repository root" refers to the top-level directory of a code repository where all the files and folders related to a project are stored. In version control systems like Git, the repository root is the starting point of your project's file structure and includes all the branches, tags, and commits that constitute the project's history.
Open Windows’ “manage computer certificates” app, and go to the certificates in the “trusted root certificate authorities” folder. There I can find that same “DigiCert Assured ID Root CA” and "VeriSign Universal Root Certification Authority" with same details as your log. When I open it and look at the details, I see the signature algorithm is SHA1 and the thumbprint matches the SHA1 hash that the dotnet nuget verify command above output.
You can use powershell script too, then thumbprints should match SHA1 from your log, see redmarked ones 0563B8630D62D75ABBC8AB1E4BDFB5A899B24D43, 3679CA35668772304D30A5FB873B0FA77BB70D54, if you're missing them then you need to manually install them using pem/pfx file from respective root cert provider:

Get-ChildItem -Path Cert:\CurrentUser\Root | Where-Object {$_.Subject -like "*DigiCert Assured ID Root CA*"} | Select-Object Thumbprint

Get-ChildItem -Path Cert:\CurrentUser\Root | Where-Object {$_.Subject -like "*VeriSign Universal Root Certification Authority*"} | Select-Object Thumbprint

thanks, verisign cert which u mentioned has fixed my problem.

@sabinaqurbanova
Thank you for letting us know, based on your feedback we're closing this issue.


amplify v7.5.5 push fails with: "Parameters: [analyticsEssPinpointId, analyticsEssPinpointRegion] do not exist in the template" after override migration

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
14.15.3
Amplify CLI Version
7.5.5 - I'm unable to install latest due to https://github.com/aws-amplify/amplify-cli/issues/9223
What operating system are you using?
Mac
Amplify Categories
analytics
Amplify Commands
push
Describe the bug
I'm trying to do amplify push, and the thing prompts me to do the override migration, which I select yes for. The push then fails with:
UPDATE_FAILED      functionEssDynamoStreamFn       AWS::CloudFormation::Stack Mon Dec 06 2021 11:29:17 GMT-0700 (Mountain Standard Time) Parameters: [analyticsEssPinpointId, analyticsEssPinpointRegion] do not exist in the template
Expected behavior
amplify push should work
Reproduction steps
Is it a pinpoint specific issue? I don't know. And I'm unable to see if latest cli fixes this due to https://github.com/aws-amplify/amplify-cli/issues/9223 where push also fails there.
GraphQL schema(s)

# Put schemas below this line

Log output

# Put your logs below this line

Additional information
No response

Hi @hisham
Apologies for the incovenience. We have a PR which will fix the deployment bucket issue : https://github.com/aws-amplify/amplify-cli/pull/9215
For the other issue , I am investigating it.
If possible can you send your amplify folder after redacting any secret info from it.

Sure I just sent it to<EMAIL_ADDRESS>thanks!

Hi @hisham
It seems like a problem with EssDynamoStreamFn. According to amplify-meta.json , this function dependsOn analytics but if you check function parameters.json for this , this function itself doesn't know  it depends on analytics.
function-parameters.json
  "permissions": {
    "api": {
      "randomAPI": [
        "create",
        "read",
        "update",
        "delete"
      ]
    },
    "auth": {
      "randomauth": [
        "read"
      ]
    },
    "storage": {
      "randomstorage": [
        "create",
        "read",
        "update"
      ]
    }
  },

As you can see analytics is missing and its present in amplify-meta.json.
    "RandomFn": {
      "build": true,
      "providerPlugin": "awscloudformation",
      "service": "Lambda",
      "dependsOn": [
        {
          "category": "api",
          "resourceName": "randomAPI",
          "attributes": [
            "GraphQLAPIIdOutput",
            "GraphQLAPIEndpointOutput"
          ]
        },
        {
          "category": "auth",
          "resourceName": "randomauth,
          "attributes": [
            "UserPoolId"
          ]
        },
        {
          "category": "storage",
          "resourceName": "randostorage",
          "attributes": [
            "BucketName"
          ]
        },
        {
          "category": "analytics",
          "resourceName": "randomanalytics",
          "attributes": [
            "Id",
            "Region"
          ]
        },
        {
          "category": "function",
          "resourceName": "randomlayer",
          "attributes": [
            "Arn"
          ]
        }

For the workaround , Can you go to amplify update function and try giving this function access to analytics .
If it was working before , can you also check if this function was depending on analytics (check in function-parameters.json) before in  #current-cloud-backend.
Ill also try to reproduce this from an older version with its a regression?

yes , Just try removing the section from backendConfig.json and amplifyMeta.json and try push again?

yes I ended up removing the analytics dependsOn for EssDynamoStreamFn from amplify-meta.json, and the push now worked.

Good to know it worked.
Closing this issue , if you get stuck on it again , feel free to ping and ill reopen this again


Make an interface for storing data

We need to store data:

characters per second per user
whether a channel has this enabled
currency

We should store these in memory (using a global dictionary) for now, but in a separate module so it's easy to drop in a database later.

Actually making this a class rather than global functions would probably work better

I've set up a database module with a class that holds user data and channel data