java - DataAdapter - Timeout trying to get output causing the pipeline to pause

HKube micro-service
java wrapper
Describe the bug
when  the wrapper  get timeout receiving data from peer it did not continue to to take data from storage
LOG
[DEBUG] 2020-08-24 06:32:49.290 [main] Main - debug logging enabled
[INFO ] 2020-08-24 06:32:49.293 [main] WrapperConfig - no config in classpath
[INFO ] 2020-08-24 06:32:49.293 [main] CommConfig - no config in classpath
[INFO ] 2020-08-24 06:32:49.294 [main] StorageConfig - no config in classpath
[INFO ] 2020-08-24 06:32:49.294 [main] FSConfig - no config in classpath
[INFO ] 2020-08-24 06:32:49.294 [main] S3Config - no config in classpath
[INFO ] 2020-08-24 06:32:49.387 [main] Wrapper - connecting to uri: ws://localhost:3000/?storage=v2&encoding=bson
[DEBUG] 2020-08-24 06:32:49.444 [main] Wrapper - javax.websocket.DeploymentException: Connection failed.
[INFO ] 2020-08-24 06:32:49.661 [ tyrus-jdk-client-2] Wrapper - connected to worker
[INFO ] 2020-08-24 06:32:51.889 [ tyrus-jdk-client-1] BSONEncoder - decode took 107 milliseconds
[INFO ] 2020-08-24 06:32:51.890 [ tyrus-jdk-client-1] Wrapper - got message from worker:initialize
[INFO ] 2020-08-24 06:32:51.893 [Thread-4] Wrapper - Sending message to worker: initialized
[INFO ] 2020-08-24 06:32:51.902 [Thread-4] BSONEncoder - encode took 7 milliseconds
[INFO ] 2020-08-24 06:32:51.907 [ tyrus-jdk-client-2] BSONEncoder - decode took 1 milliseconds
[INFO ] 2020-08-24 06:32:51.907 [ tyrus-jdk-client-2] Wrapper - got message from worker:start
[INFO ] 2020-08-24 06:32:51.908 [Thread-5] Wrapper - Sending message to worker: started
[INFO ] 2020-08-24 06:32:51.908 [Thread-5] BSONEncoder - encode took 0 milliseconds
[DEBUG] 2020-08-24 06:32:51.909 [Thread-5] Wrapper - Before fetching input data
[INFO ] 2020-08-24 06:32:51.933 [Thread-5] MSGPackEncoder - encode took 3 milliseconds
[WARN ] 2020-08-24 06:32:52.935 [Thread-5] DataAdapter - Timeout trying to get output from <IP_ADDRESS>:9020
Expected behavior
execute the following pipeline:
{
    "name": "benchmarkpythonJava",
    "nodes": [
        {
            "nodeName": "onearray",
            "algorithmName": "python-big-array-6g",
            "input": [
<EMAIL_ADDRESS><EMAIL_ADDRESS>            ]
        },
        {
            "nodeName": "two",
            "algorithmName": "java-big-array-1g",
            "input": [
                "#@onearray"
            ]
        }
    ],
    "flowInput": {
        "bufferSize": 100,
        "objectSize": 10000000
    },
    "experimentName": "main",
    "options": {
        "ttl": 3600,
        "batchTolerance": 80,
        "progressVerbosityLevel": "info"
    },
    "priority": 3
}

**To Reproduce**
Steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

**Screenshots**
If applicable, add screenshots to help explain your problem.

**Additional context**
Add any other context about the problem here.

Problem occurs when running in log level debug.
In this case we attempt to print out the algorithm input, which is very large and causes a memory problem.

when working with data larger the 300M the java algorithm stuck
    "name": "benchmarkpythonJava",
    "nodes": [
        {
            "nodeName": "onearray",
            "algorithmName": "python-big-array-6g",
            "input": [
<EMAIL_ADDRESS><EMAIL_ADDRESS>            ]
        },
        {
            "nodeName": "two",
            "algorithmName": "java-big-array-1g",
            "input": [
                "#@onearray"
            ]
        }
    ],
    "flowInput": {
        "bufferSize": 1,
        "objectSize": 300000000
    },
    "experimentName": "main",
    "options": {
        "ttl": 3600,
        "batchTolerance": 80,
        "progressVerbosityLevel": "info"
    },
    "priority": 3,
    "flowInputMetadata": {
        "metadata": {
            "flowInput.bufferSize": {
                "type": "number"
            },
            "flowInput.objectSize": {
                "type": "number"
            }
        },
        "storageInfo": {
            "path": "test-hkube/main:benchmarkpythonJava:62ortooy/main:benchmarkpythonJava:62ortooy"
        }
    },
    "jobId": "main:benchmarkpythonJava:62ortooy",
    "startTime":<PHONE_NUMBER>141,
    "lastRunResult": {
        "timestamp": "2020-09-01T06:19:30.889Z",
        "status": "completed",
        "timeTook": 5.675
    },
    "types": [
        "raw"
    ]
}

Added log messages. Waiting for a reproduce


External Data Pipeline Not Importing Correctly

In repository.py, the external_data pipeline is failing to import correctly. Not needed in the short term (we're using files instead for the first release), it was disabled. Fix long term so that it works again and can be included.

Linking to other comment, as should be done at same time:

[ ] The code that produces the ONSPD_reduced_to_postcode_sector.csv file needs amending so that lsoa11 will only ever have a single value. At the moment, the code groups the postcodes and returns the modal value of lsoa11 across those postcodes. However, this sometimes returns more than one value. When it does this, the code needs to return the first of these values.

Linking to other comment, as should be done at same time:

[ ] Port early processes from sufficiency code to external data code, so that these tables are not produced daily. See comments in sufficiency job (basically all files before 903 files

Linking to other comment, as should be done at same time:
There are currently three processes that Power Query runs in the Dynamic Sufficiency dashboard that Python would manage more efficiently:

[ ] a process to work out what the most recent 'S' episode (from RNE) is for a given child per row
[ ] a process to work out what the most recent DECOM is for a given child per row
[ ] a process that provides the most recent submission year for a given LA (though this may be redundant as already included in https://github.com/SocialFinanceDigitalLabs/sf-fons-platform/issues/69.

3 days


OpentsdbEmitter fails sending tags whose value contains ":"

some metric contains  "host => hostname:port",  bug ":" is not a valid name in opentsdb.

http://opentsdb.net/docs/build/html/user_guide/writing/index.html#metrics-and-tags

I use opentsdb2.3.0~ which version do u use? @QiuMM

I'm not clear, sorry. It's a service provided by other departments of our company. Maybe there are some difference between the open-source. Can you provide your log about this fail.

Anyway, I fixed this in #6251.


Outliner mod causes slow page scrolling

BEFORE MAKING A BUG REPORT, PLEASE READ THE
CONTRIBUTING GUIDE.
BUG REPORTS ARE NOT FOR SUPPORT REQUESTS. IF YOU JUST NEED HELP,
ASK IN THE DISCORD SERVER.
BUG REPORTS THAT DO NOT PROPERLY FILL
IN THE TEMPLATE MAY BE IGNORED OR REJECTED.

What is happening?
The mod outliner causes slow page scrolling
What should be happening?
Make the page scroll normally
Screenshots (if applicable):
Operating system/browser name & version:
OS: Windows 11 21H2
notion-enhancer and/or notion-repackaged version:
2.0.18-1 2.0.18-1
notion-enhancer configuration (enabled/disabled mods and their settings):
enabled outliner mod

dup of https://github.com/notion-enhancer/repo/issues/77


mesa: 23.3.1 -> 23.3.2

i686 patch got merged
Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin
[x] i686-linux

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Bisect says something regressed in this release and gjs.tests now fails with thie following device init failure:
$ nix build --no-link -f. gjs.tests --keep-going -j3 -L
...
vm-test-run-gjs> machine # Stack trace of thread 1176:
vm-test-run-gjs> machine # #0  0x00007f69e858102c __pthread_kill_implementation (libc.so.6 + 0x8d02c)
vm-test-run-gjs> machine # #1  0x00007f69e8531e06 raise (libc.so.6 + 0x3de06)
vm-test-run-gjs> machine # #2  0x00007f69e851a8f5 abort (libc.so.6 + 0x268f5)
vm-test-run-gjs> machine # #3  0x00000000005b7eea OsAbort (Xorg + 0x1b7eea)
vm-test-run-gjs> machine # #4  0x00000000005bd5a3 AbortServer (Xorg + 0x1bd5a3)
vm-test-run-gjs> machine # #5  0x00000000005be4a5 FatalError (Xorg + 0x1be4a5)
vm-test-run-gjs> machine # #6  0x00000000005b5415 OsSigHandler (Xorg + 0x1b5415)
vm-test-run-gjs> machine # #7  0x00007f69e8531eb0 __restore_rt (libc.so.6 + 0x3deb0)
vm-test-run-gjs> machine # #8  0x00007f69e63336e0 llvmpipe_screen_get_fd (kms_swrast_dri.so + 0x70b6e0)
vm-test-run-gjs> machine # #9  0x00007f69e68a8884 u_pipe_screen_get_param_defaults (kms_swrast_dri.so + 0xc80884)
vm-test-run-gjs> machine # #10 0x00007f69e5cdcb50 dri2_init_screen_extensions (kms_swrast_dri.so + 0xb4b50)
vm-test-run-gjs> machine # #11 0x00007f69e5cdcf70 dri_swrast_kms_init_screen (kms_swrast_dri.so + 0xb4f70)
vm-test-run-gjs> machine # #12 0x00007f69e5ce5094 driCreateNewScreen2 (kms_swrast_dri.so + 0xbd094)
vm-test-run-gjs> machine # #13 0x00007f69e7ed6cb0 dri_screen_create_for_driver (libgbm.so.1 + 0x4cb0)
vm-test-run-gjs> machine # #14 0x00007f69e7ed7210 dri_screen_create_sw (libgbm.so.1 + 0x5210)
vm-test-run-gjs> machine # #15 0x00007f69e7ed73db dri_device_create (libgbm.so.1 + 0x53db)
vm-test-run-gjs> machine # #16 0x00007f69e7ed577c find_backend (libgbm.so.1 + 0x377c)
vm-test-run-gjs> machine # #17 0x00007f69e7ed58b4 gbm_create_device (libgbm.so.1 + 0x38b4)
vm-test-run-gjs> machine # #18 0x00007f69e7eec4d1 glamor_egl_init (libglamoregl.so + 0x94d1)
vm-test-run-gjs> machine # #19 0x00007f69e7f2677a PreInit (modesetting_drv.so + 0xc77a)
vm-test-run-gjs> machine # #20 0x0000000000488916 InitOutput (Xorg + 0x88916)
vm-test-run-gjs> machine # #21 0x00000000004495b0 dix_main (Xorg + 0x495b0)
vm-test-run-gjs> machine # #22 0x00007f69e851c0ce __libc_start_call_main (libc.so.6 + 0x280ce)
vm-test-run-gjs> machine # #23 0x00007f69e851c189 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x28189)
vm-test-run-gjs> machine # #24 0x0000000000432825 _start (Xorg + 0x32825)
vm-test-run-gjs> machine # ELF object binary architecture: AMD x86-64

Reverting be9351cb7cbd712c20d35282226288f7321809b8 mesa: 23.3.1 -> 23.3.2 restores the test.

The .3 bump of mesa didn't fix this?

Ah, maybe I started from a too old state. I'll retest against the staging.

The .3 bump of mesa didn't fix this?

staging with mesa-23.3.3 works fine. Thank you!

To be clear, 23.3.3 is in nixos-unstable channel already.


[Upgrade] Create temp file when upgrading, closes #176

This PR does the following things:

Create a temp file when upgrading the omc binary to fix #176
Add M-series MacOS in the build workflow so that arm64 binary could be downloaded in the releases

@cchen666 I tested the PR on my Mac and it is failing with the following error:
$ omc upgrade --to=latest
error: Expected status code 200 requesting https://github.com/gmeghnag/omc/releases/latest/download/omc_Darwin_amd64, received 404

we need to create a release file for amd64 arch or make it an alias for x86_64

Hi @gmeghnag
Thank you for your comment!
I could be wrong but I think here is what should happen:

Since this PR changes .github/workflows/build.yml, once the PR is merged, the next release should have an amd64 binary file for M-Series MacOS
Only after the PR is merged and the next release is published, the user can then able to omc upgrade on the M-Series MacOS. Before that as you've shown, the amd64 binary will never exist https://github.com/gmeghnag/omc/releases/tag/v3.7.3

Hi @cchen666
But unless I'm missing some pieces I don't see any release binary named omc_Darwin_amd64 here:
https://github.com/gmeghnag/omc/blob/66481b4244a6d5a860ebc5c304c2559fb55f45fa/.github/workflows/build.yml#L55-L65
So even after this PR will be merged and the build executed, no binary named that way will be released..

Hey @cchen666 , the files I see here are:
checksums.txt
omc_Darwin_aarch64.tar.gz
omc_Darwin_arm64
omc_Darwin_arm64.tar.gz
omc_Darwin_x86_64
omc_Darwin_x86_64.tar.gz
omc_Linux_aarch64.tar.gz
omc_Linux_arm64.tar.gz
omc_Linux_x86_64omc_Linux_x86_64.tar.gz
omc_Windows_x86_64.zip
Source code (zip)
Source code (tar.gz)

There is not any omc_Darwin_amd64 binary.

Hi @gmeghnag
Thank you for your patience!
I updated the PR and here is the release list: https://github.com/cchen666/omc/releases/tag/v1.0.3


[amplify add storage] - Resource is not in the state stackUpdateComplete

Describe the bug
After amplify add storage, amplify push throws this error:
**

Resource is not in the state stackUpdateComplete

**
To Reproduce
Steps to reproduce the behavior:

Execute amplify add storage
Execute amplify push
Push fails and throws the above error.
See error

Expected behavior
Push should complete successfully
Screenshots
192-168-1-102:pna-multi-env_copy ahmni01$ amplify add storage
? Please select from one of the below mentioned services Content (Images, audio, video, etc.)
? Please provide a friendly name for your resource that will be used to label this category in the project: attachmentpnamar0503
? Please provide bucket name: attachmentpnamar0503s3bucket
? Who should have access: Auth users only
? What kind of access do you want for Authenticated users read/write
Successfully added resource attachmentpnamar0503 locally
192-168-1-102:pna-multi-env_copy ahmni01$ amplify push
Current Environment: devfirst

Category
Resource name
Operation
Provider plugin

Storage
attachmentpnamar0503
Create
awscloudformation

Hosting
S3AndCloudFront
No Change
awscloudformation

Auth
cognito8146221a
No Change
awscloudformation

Storage
ordersmarch0503
No Change
awscloudformation

Storage
activitiesmarch0503
No Change
awscloudformation

Function
pnamarch0503function
No Change
awscloudformation

Function
pnamarch0503activityfunction
No Change
awscloudformation

Api
pnamarch0503
No Change
awscloudformation

Api
pnamarch0503activity
No Change
awscloudformation

? Are you sure you want to continue? Yes

⠇ Updating resources in the cloud. This may take a few minutes...

UPDATE_IN_PROGRESS          S3Bucket                                                          AWS::S3::Bucket            Wed May 22 2019 14:04:27 GMT+1000 (Australian Eastern Standard Time) Requested update requires the creation of a new physical resource; hence creating one.
UPDATE_FAILED               S3Bucket                                                          AWS::S3::Bucket            Wed May 22 2019 14:04:27 GMT+1000 (Australian Eastern Standard Time) pnamarch05-06-devfirst already exists in stack arn:aws:cloudformation:eu-west-1:478576439851:stack/pnamar05first-20190511104149-hostingS3AndCloudFront-1JGA1AFF5RCIA/9de8ea90-7386-11e9-9701-02f49d781af6
UPDATE_ROLLBACK_IN_PROGRESS pnamar05first-20190509182634-hostingS3AndCloudFront-UCO7ZL6OJIZS  AWS::CloudFormation::Stack Wed May 22 2019 14:04:28 GMT+1000 (Australian Eastern Standard Time) The following resource(s) failed to update: [S3Bucket].
UPDATE_ROLLBACK_IN_PROGRESS pnamar05first-20190509182634-authcognito8146221a-12ZOVT03QH2PD    AWS::CloudFormation::Stack Wed May 22 2019 14:04:29 GMT+1000 (Australian Eastern Standard Time) Initiated by parent stack
⠇ Updating resources in the cloud. This may take a few minutes...
UPDATE_IN_PROGRESS          DynamoDBTable                                                         AWS::DynamoDB::Table       Wed May 22 2019 14:04:26 GMT+1000 (Australian Eastern Standard Time) Requested update requires the creation of a new physical resource; hence creating one.
UPDATE_FAILED               DynamoDBTable                                                         AWS::DynamoDB::Table       Wed May 22 2019 14:04:26 GMT+1000 (Australian Eastern Standard Time) activitiesmarch0503-devfirst already exists in stack arn:aws:cloudformation:eu-west-1:478576439851:stack/pnamar05first-20190511104149-storageactivitiesmarch0503-3BJQ34B737FB/9ddfe9e0-7386-11e9-b49e-0aac5439e4be
UPDATE_ROLLBACK_IN_PROGRESS pnamar05first-20190509182634-storageactivitiesmarch0503-1KNWL68WBRA94 AWS::CloudFormation::Stack Wed May 22 2019 14:04:27 GMT+1000 (Australian Eastern Standard Time) The following resource(s) failed to update: [DynamoDBTable].
UPDATE_FAILED               storageactivitiesmarch0503                                            AWS::CloudFormation::Stack Wed May 22 2019 14:04:28 GMT+1000 (Australian Eastern Standard Time) Embedded stack arn:aws:cloudformation:eu-west-1:478576439851:stack/pnamar05first-20190509182634-storageactivitiesmarch0503-1KNWL68WBRA94/89920780-7236-11e9-b69b-024e38e0666a was not successfully updated. Currently in UPDATE_ROLLBACK_IN_PROGRESS with reason: The following resource(s) failed to update: [DynamoDBTable].
UPDATE_FAILED               storageordersmarch0503                                                AWS::CloudFormation::Stack Wed May 22 2019 14:04:28 GMT+1000 (Australian Eastern Standard Time) Embedded stack arn:aws:cloudformation:eu-west-1:478576439851:stack/pnamar05first-20190509182634-storageordersmarch0503-1RLVMFGWLTCIX/89c7bd80-7236-11e9-ac7e-0a99a68566c4 was not successfully updated. Currently in UPDATE_ROLLBACK_IN_PROGRESS with reason: The following resource(s) failed to update: [DynamoDBTable].
UPDATE_FAILED               hostingS3AndCloudFront                                                AWS::CloudFormation::Stack Wed May 22 2019 14:04:28 GMT+1000 (Australian Eastern Standard Time) Embedded stack arn:aws:cloudformation:eu-west-1:478576439851:stack/pnamar05first-20190509182634-hostingS3AndCloudFront-UCO7ZL6OJIZS/8970c3e0-7236-11e9-8998-02f48c625dae was not successfully updated. Currently in UPDATE_ROLLBACK_IN_PROGRESS with reason: The following resource(s) failed to update: [S3Bucket].
CREATE_FAILED               storageattachmentpnamar0503                                           AWS::CloudFormation::Stack Wed May 22 2019 14:04:29 GMT+1000 (Australian Eastern Standard Time) Resource creation cancelled
⠏ Updating resources in the cloud. This may take a few minutes...
UPDATE_FAILED               authcognito8146221a          AWS::CloudFormation::Stack Wed May 22 2019 14:04:40 GMT+1000 (Australian Eastern Standard Time) Resource update cancelled
UPDATE_ROLLBACK_IN_PROGRESS pnamar05first-20190509182634 AWS::CloudFormation::Stack Wed May 22 2019 14:04:41 GMT+1000 (Australian Eastern Standard Time) The following resource(s) failed to create: [storageattachmentpnamar0503]. The following resource(s) failed to update: [authcognito8146221a, hostingS3AndCloudFront, storageordersmarch0503, storageactivitiesmarch0503].
CREATE_COMPLETE             S3Bucket                     AWS::S3::Bucket            Wed May 22 2019 14:04:44 GMT+1000 (Australian Eastern Standard Time)
CREATE_IN_PROGRESS          S3AuthPolicyRW               AWS::IAM::Policy           Wed May 22 2019 14:04:48 GMT+1000 (Australian Eastern Standard Time)
CREATE_IN_PROGRESS          S3AuthPolicyRW               AWS::IAM::Policy           Wed May 22 2019 14:04:49 GMT+1000 (Australian Eastern Standard Time) Resource creation Initiated
⠧ Updating resources in the cloud. This may take a few minutes...
CREATE_COMPLETE    S3AuthPolicyRW                                                         AWS::IAM::Policy           Wed May 22 2019 14:04:57 GMT+1000 (Australian Eastern Standard Time)
UPDATE_IN_PROGRESS hostingS3AndCloudFront                                                 AWS::CloudFormation::Stack Wed May 22 2019 14:04:58 GMT+1000 (Australian Eastern Standard Time)
UPDATE_IN_PROGRESS authcognito8146221a                                                    AWS::CloudFormation::Stack Wed May 22 2019 14:04:58 GMT+1000 (Australian Eastern Standard Time)
UPDATE_IN_PROGRESS storageordersmarch0503                                                 AWS::CloudFormation::Stack Wed May 22 2019 14:04:58 GMT+1000 (Australian Eastern Standard Time)
UPDATE_IN_PROGRESS storageactivitiesmarch0503                                             AWS::CloudFormation::Stack Wed May 22 2019 14:04:58 GMT+1000 (Australian Eastern Standard Time)
CREATE_COMPLETE    pnamar05first-20190509182634-storageattachmentpnamar0503-1OGSOC223CZ27 AWS::CloudFormation::Stack Wed May 22 2019 14:05:00 GMT+1000 (Australian Eastern Standard Time)
⠸ Updating resources in the cloud. This may take a few minutes...
UPDATE_COMPLETE                              DynamoDBTable                                                         AWS::DynamoDB::Table       Wed May 22 2019 14:05:28 GMT+1000 (Australian Eastern Standard Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS pnamar05first-20190509182634-storageactivitiesmarch0503-1KNWL68WBRA94 AWS::CloudFormation::Stack Wed May 22 2019 14:05:29 GMT+1000 (Australian Eastern Standard Time)
⠋ Updating resources in the cloud. This may take a few minutes...
UPDATE_COMPLETE                              DynamoDBTable                                                     AWS::DynamoDB::Table       Wed May 22 2019 14:05:28 GMT+1000 (Australian Eastern Standard Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS pnamar05first-20190509182634-storageordersmarch0503-1RLVMFGWLTCIX AWS::CloudFormation::Stack Wed May 22 2019 14:05:29 GMT+1000 (Australian Eastern Standard Time)
UPDATE_COMPLETE                              hostingS3AndCloudFront                                            AWS::CloudFormation::Stack Wed May 22 2019 14:05:33 GMT+1000 (Australian Eastern Standard Time)
UPDATE_COMPLETE                              storageordersmarch0503                                            AWS::CloudFormation::Stack Wed May 22 2019 14:05:33 GMT+1000 (Australian Eastern Standard Time)
UPDATE_COMPLETE                              storageactivitiesmarch0503                                        AWS::CloudFormation::Stack Wed May 22 2019 14:05:34 GMT+1000 (Australian Eastern Standard Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS pnamar05first-20190509182634-authcognito8146221a-12ZOVT03QH2PD    AWS::CloudFormation::Stack Wed May 22 2019 14:05:39 GMT+1000 (Australian Eastern Standard Time)
⠏ Updating resources in the cloud. This may take a few minutes...
UPDATE_COMPLETE authcognito8146221a AWS::CloudFormation::Stack Wed May 22 2019 14:05:46 GMT+1000 (Australian Eastern Standard Time)
⠹ Updating resources in the cloud. This may take a few minutes...
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS pnamar05first-20190509182634                                   AWS::CloudFormation::Stack Wed May 22 2019 14:05:47 GMT+1000 (Australian Eastern Standard Time)
UPDATE_IN_PROGRESS                           storageordersmarch0503                                         AWS::CloudFormation::Stack Wed May 22 2019 14:05:49 GMT+1000 (Australian Eastern Standard Time)
UPDATE_IN_PROGRESS                           hostingS3AndCloudFront                                         AWS::CloudFormation::Stack Wed May 22 2019 14:05:49 GMT+1000 (Australian Eastern Standard Time)
UPDATE_IN_PROGRESS                           authcognito8146221a                                            AWS::CloudFormation::Stack Wed May 22 2019 14:05:49 GMT+1000 (Australian Eastern Standard Time)
UPDATE_IN_PROGRESS                           storageactivitiesmarch0503                                     AWS::CloudFormation::Stack Wed May 22 2019 14:05:49 GMT+1000 (Australian Eastern Standard Time)
DELETE_IN_PROGRESS                           storageattachmentpnamar0503                                    AWS::CloudFormation::Stack Wed May 22 2019 14:05:49 GMT+1000 (Australian Eastern Standard Time)
UPDATE_ROLLBACK_COMPLETE                     pnamar05first-20190509182634-authcognito8146221a-12ZOVT03QH2PD AWS::CloudFormation::Stack Wed May 22 2019 14:05:50 GMT+1000 (Australian Eastern Standard Time)
⠏ Updating resources in the cloud. This may take a few minutes...
DELETE_IN_PROGRESS pnamar05first-20190509182634-storageattachmentpnamar0503-1OGSOC223CZ27 AWS::CloudFormation::Stack Wed May 22 2019 14:05:50 GMT+1000 (Australian Eastern Standard Time) User Initiated
DELETE_IN_PROGRESS S3AuthPolicyRW                                                         AWS::IAM::Policy           Wed May 22 2019 14:05:52 GMT+1000 (Australian Eastern Standard Time)
DELETE_COMPLETE    S3AuthPolicyRW                                                         AWS::IAM::Policy           Wed May 22 2019 14:05:53 GMT+1000 (Australian Eastern Standard Time)
DELETE_SKIPPED     S3Bucket                                                               AWS::S3::Bucket            Wed May 22 2019 14:05:55 GMT+1000 (Australian Eastern Standard Time)
DELETE_COMPLETE    pnamar05first-20190509182634-storageattachmentpnamar0503-1OGSOC223CZ27 AWS::CloudFormation::Stack Wed May 22 2019 14:05:56 GMT+1000 (Australian Eastern Standard Time)
⠙ Updating resources in the cloud. This may take a few minutes...
UPDATE_COMPLETE          storageordersmarch0503       AWS::CloudFormation::Stack Wed May 22 2019 14:06:00 GMT+1000 (Australian Eastern Standard Time)
UPDATE_COMPLETE          hostingS3AndCloudFront       AWS::CloudFormation::Stack Wed May 22 2019 14:06:00 GMT+1000 (Australian Eastern Standard Time)
UPDATE_COMPLETE          authcognito8146221a          AWS::CloudFormation::Stack Wed May 22 2019 14:06:00 GMT+1000 (Australian Eastern Standard Time)
UPDATE_COMPLETE          storageactivitiesmarch0503   AWS::CloudFormation::Stack Wed May 22 2019 14:06:00 GMT+1000 (Australian Eastern Standard Time)
DELETE_COMPLETE          storageattachmentpnamar0503  AWS::CloudFormation::Stack Wed May 22 2019 14:06:01 GMT+1000 (Australian Eastern Standard Time)
UPDATE_ROLLBACK_COMPLETE pnamar05first-20190509182634 AWS::CloudFormation::Stack Wed May 22 2019 14:06:01 GMT+1000 (Australian Eastern Standard Time)
⠇ Updating resources in the cloud. This may take a few minutes...Error updating cloudformation stack
✖ An error occurred when pushing the resources to the cloud
Resource is not in the state stackUpdateComplete
Env (please complete the following information):

OS: MacOS
Browser [e.g. chrome, safari]: Chrome
- Node: v10.15.1
- npm: 6.4.1
- amplify: 0.2.2-multienv.1

Additional context
I went through other issues and ran the following commands and the issue still is still outstanding:
amplify env pull --restore
amplify remove storage
amplify add storage
amplify push

I tried to follow the instructions provided in this article that talks about this issue:
https://www.rockyourcode.com/aws-amplify-resource-is-not-in-the-state-stack-update-complete
It refers to this github issue: https://github.com/aws-amplify/amplify-cli/issues/82.
Anyhow after following those steps in the article amplify push is still failing.
Hence I upgraded the CLI to this version: 1.6.10
Now amplify push throws a lot more verbose information:
192-168-1-102:pna-multi-env_copy ahmni01$ amplify push
Current Environment: devfirst

Category
Resource name
Operation
Provider plugin

Auth
cognito8146221a
Update
awscloudformation

Hosting
S3AndCloudFront
No Change
awscloudformation

Storage
ordersmarch0503
No Change
awscloudformation

Storage
activitiesmarch0503
No Change
awscloudformation

Function
pnamarch0503function
No Change
awscloudformation

Function
pnamarch0503activityfunction
No Change
awscloudformation

Api
pnamarch0503
No Change
awscloudformation

Api
pnamarch0503activity
No Change
awscloudformation

? Are you sure you want to continue? Yes

⠹ Updating resources in the cloud. This may take a few minutes...

UPDATE_IN_PROGRESS pnamar05first-20190509182634 AWS::CloudFormation::Stack Wed May 22 2019 16:27:43 GMT+1000 (Australian Eastern Standard Time) User Initiated
UPDATE_IN_PROGRESS storageactivitiesmarch0503   AWS::CloudFormation::Stack Wed May 22 2019 16:27:50 GMT+1000 (Australian Eastern Standard Time)
⠼ Updating resources in the cloud. This may take a few minutes...
UPDATE_IN_PROGRESS pnamar05first-20190509182634-storageactivitiesmarch0503-1KNWL68WBRA94 AWS::CloudFormation::Stack Wed May 22 2019 16:27:50 GMT+1000 (Australian Eastern Standard Time) User Initiated
⠙ Updating resources in the cloud. This may take a few minutes...
UPDATE_IN_PROGRESS storageordersmarch0503 AWS::CloudFormation::Stack Wed May 22 2019 16:27:50 GMT+1000 (Australian Eastern Standard Time)
UPDATE_IN_PROGRESS hostingS3AndCloudFront AWS::CloudFormation::Stack Wed May 22 2019 16:27:50 GMT+1000 (Australian Eastern Standard Time)
UPDATE_IN_PROGRESS authcognito8146221a    AWS::CloudFormation::Stack Wed May 22 2019 16:27:51 GMT+1000 (Australian Eastern Standard Time)
⠧ Updating resources in the cloud. This may take a few minutes...
UPDATE_IN_PROGRESS pnamar05first-20190509182634-hostingS3AndCloudFront-UCO7ZL6OJIZS AWS::CloudFormation::Stack Wed May 22 2019 16:27:51 GMT+1000 (Australian Eastern Standard Time) User Initiated
UPDATE_IN_PROGRESS DynamoDBTable AWS::DynamoDB::Table Wed May 22 2019 16:28:00 GMT+1000 (Australian Eastern Standard Time) Requested update requires the creation of a new physical resource; hence creating one.
⠇ Updating resources in the cloud. This may take a few minutes...
UPDATE_IN_PROGRESS pnamar05first-20190509182634-storageordersmarch0503-1RLVMFGWLTCIX AWS::CloudFormation::Stack Wed May 22 2019 16:27:51 GMT+1000 (Australian Eastern Standard Time) User Initiated
⠙ Updating resources in the cloud. This may take a few minutes...
UPDATE_IN_PROGRESS pnamar05first-20190509182634-authcognito8146221a-12ZOVT03QH2PD AWS::CloudFormation::Stack Wed May 22 2019 16:27:51 GMT+1000 (Australian Eastern Standard Time) User Initiated
⠴ Updating resources in the cloud. This may take a few minutes...
UPDATE_IN_PROGRESS          S3Bucket                                                         AWS::S3::Bucket            Wed May 22 2019 16:28:00 GMT+1000 (Australian Eastern Standard Time) Requested update requires the creation of a new physical resource; hence creating one.
UPDATE_FAILED               S3Bucket                                                         AWS::S3::Bucket            Wed May 22 2019 16:28:00 GMT+1000 (Australian Eastern Standard Time) pnamarch05-06-devfirst already exists in stack arn:aws:cloudformation:eu-west-1:478576439851:stack/pnamar05first-20190511104149-hostingS3AndCloudFront-1JGA1AFF5RCIA/9de8ea90-7386-11e9-9701-02f49d781af6
UPDATE_ROLLBACK_IN_PROGRESS pnamar05first-20190509182634-hostingS3AndCloudFront-UCO7ZL6OJIZS AWS::CloudFormation::Stack Wed May 22 2019 16:28:01 GMT+1000 (Australian Eastern Standard Time) The following resource(s) failed to update: [S3Bucket].
⠋ Updating resources in the cloud. This may take a few minutes...
UPDATE_FAILED hostingS3AndCloudFront AWS::CloudFormation::Stack Wed May 22 2019 16:28:02 GMT+1000 (Australian Eastern Standard Time) Embedded stack arn:aws:cloudformation:eu-west-1:478576439851:stack/pnamar05first-20190509182634-hostingS3AndCloudFront-UCO7ZL6OJIZS/8970c3e0-7236-11e9-8998-02f48c625dae was not successfully updated. Currently in UPDATE_ROLLBACK_IN_PROGRESS with reason: The following resource(s) failed to update: [S3Bucket].
UPDATE_FAILED storageordersmarch0503 AWS::CloudFormation::Stack Wed May 22 2019 16:28:02 GMT+1000 (Australian Eastern Standard Time) Embedded stack arn:aws:cloudformation:eu-west-1:478576439851:stack/pnamar05first-20190509182634-storageordersmarch0503-1RLVMFGWLTCIX/89c7bd80-7236-11e9-ac7e-0a99a68566c4 was not successfully updated. Currently in UPDATE_ROLLBACK_IN_PROGRESS with reason: The following resource(s) failed to update: [DynamoDBTable].
⠼ Updating resources in the cloud. This may take a few minutes...
UPDATE_ROLLBACK_IN_PROGRESS pnamar05first-20190509182634-authcognito8146221a-12ZOVT03QH2PD AWS::CloudFormation::Stack Wed May 22 2019 16:28:03 GMT+1000 (Australian Eastern Standard Time) Initiated by parent stack
⠇ Updating resources in the cloud. This may take a few minutes...
UPDATE_IN_PROGRESS          DynamoDBTable                                                     AWS::DynamoDB::Table       Wed May 22 2019 16:28:00 GMT+1000 (Australian Eastern Standard Time) Requested update requires the creation of a new physical resource; hence creating one.
UPDATE_FAILED               DynamoDBTable                                                     AWS::DynamoDB::Table       Wed May 22 2019 16:28:01 GMT+1000 (Australian Eastern Standard Time) ordersmarch0503-devfirst already exists in stack arn:aws:cloudformation:eu-west-1:478576439851:stack/pnamar05first-20190511104149-storageordersmarch0503-1UW0ZZN4JM8XX/9df1eb40-7386-11e9-97c6-0a1f01fad44c
UPDATE_ROLLBACK_IN_PROGRESS pnamar05first-20190509182634-storageordersmarch0503-1RLVMFGWLTCIX AWS::CloudFormation::Stack Wed May 22 2019 16:28:01 GMT+1000 (Australian Eastern Standard Time) The following resource(s) failed to update: [DynamoDBTable].
⠙ Updating resources in the cloud. This may take a few minutes...
UPDATE_FAILED storageactivitiesmarch0503 AWS::CloudFormation::Stack Wed May 22 2019 16:28:03 GMT+1000 (Australian Eastern Standard Time) Resource update cancelled
⠙ Updating resources in the cloud. This may take a few minutes...
UPDATE_FAILED               DynamoDBTable                                                         AWS::DynamoDB::Table       Wed May 22 2019 16:28:00 GMT+1000 (Australian Eastern Standard Time) activitiesmarch0503-devfirst already exists in stack arn:aws:cloudformation:eu-west-1:478576439851:stack/pnamar05first-20190511104149-storageactivitiesmarch0503-3BJQ34B737FB/9ddfe9e0-7386-11e9-b49e-0aac5439e4be
UPDATE_ROLLBACK_IN_PROGRESS pnamar05first-20190509182634-storageactivitiesmarch0503-1KNWL68WBRA94 AWS::CloudFormation::Stack Wed May 22 2019 16:28:01 GMT+1000 (Australian Eastern Standard Time) The following resource(s) failed to update: [DynamoDBTable].
⠇ Updating resources in the cloud. This may take a few minutes...
UPDATE_FAILED               authcognito8146221a          AWS::CloudFormation::Stack Wed May 22 2019 16:28:13 GMT+1000 (Australian Eastern Standard Time) Resource update cancelled
UPDATE_ROLLBACK_IN_PROGRESS pnamar05first-20190509182634 AWS::CloudFormation::Stack Wed May 22 2019 16:28:14 GMT+1000 (Australian Eastern Standard Time) The following resource(s) failed to update: [authcognito8146221a, hostingS3AndCloudFront, storageordersmarch0503, storageactivitiesmarch0503].
⠹ Updating resources in the cloud. This may take a few minutes...
UPDATE_IN_PROGRESS authcognito8146221a        AWS::CloudFormation::Stack Wed May 22 2019 16:28:19 GMT+1000 (Australian Eastern Standard Time)
UPDATE_IN_PROGRESS storageordersmarch0503     AWS::CloudFormation::Stack Wed May 22 2019 16:28:19 GMT+1000 (Australian Eastern Standard Time)
UPDATE_IN_PROGRESS hostingS3AndCloudFront     AWS::CloudFormation::Stack Wed May 22 2019 16:28:19 GMT+1000 (Australian Eastern Standard Time)
UPDATE_IN_PROGRESS storageactivitiesmarch0503 AWS::CloudFormation::Stack Wed May 22 2019 16:28:19 GMT+1000 (Australian Eastern Standard Time)
⠹ Updating resources in the cloud. This may take a few minutes...
UPDATE_COMPLETE                              DynamoDBTable                                                         AWS::DynamoDB::Table       Wed May 22 2019 16:28:49 GMT+1000 (Australian Eastern Standard Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS pnamar05first-20190509182634-storageactivitiesmarch0503-1KNWL68WBRA94 AWS::CloudFormation::Stack Wed May 22 2019 16:28:50 GMT+1000 (Australian Eastern Standard Time)
⠹ Updating resources in the cloud. This may take a few minutes...
UPDATE_COMPLETE                              DynamoDBTable                                                     AWS::DynamoDB::Table       Wed May 22 2019 16:28:49 GMT+1000 (Australian Eastern Standard Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS pnamar05first-20190509182634-storageordersmarch0503-1RLVMFGWLTCIX AWS::CloudFormation::Stack Wed May 22 2019 16:28:50 GMT+1000 (Australian Eastern Standard Time)
⠋ Updating resources in the cloud. This may take a few minutes...
UPDATE_COMPLETE                              S3Bucket                                                         AWS::S3::Bucket            Wed May 22 2019 16:28:49 GMT+1000 (Australian Eastern Standard Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS pnamar05first-20190509182634-hostingS3AndCloudFront-UCO7ZL6OJIZS AWS::CloudFormation::Stack Wed May 22 2019 16:28:51 GMT+1000 (Australian Eastern Standard Time)
⠸ Updating resources in the cloud. This may take a few minutes...
UPDATE_COMPLETE storageordersmarch0503     AWS::CloudFormation::Stack Wed May 22 2019 16:28:54 GMT+1000 (Australian Eastern Standard Time)
UPDATE_COMPLETE hostingS3AndCloudFront     AWS::CloudFormation::Stack Wed May 22 2019 16:28:54 GMT+1000 (Australian Eastern Standard Time)
UPDATE_COMPLETE storageactivitiesmarch0503 AWS::CloudFormation::Stack Wed May 22 2019 16:28:55 GMT+1000 (Australian Eastern Standard Time)
⠇ Updating resources in the cloud. This may take a few minutes...
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS pnamar05first-20190509182634-authcognito8146221a-12ZOVT03QH2PD AWS::CloudFormation::Stack Wed May 22 2019 16:28:59 GMT+1000 (Australian Eastern Standard Time)
⠴ Updating resources in the cloud. This may take a few minutes...
UPDATE_COMPLETE                              authcognito8146221a          AWS::CloudFormation::Stack Wed May 22 2019 16:29:07 GMT+1000 (Australian Eastern Standard Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS pnamar05first-20190509182634 AWS::CloudFormation::Stack Wed May 22 2019 16:29:08 GMT+1000 (Australian Eastern Standard Time)
⠋ Updating resources in the cloud. This may take a few minutes...
UPDATE_IN_PROGRESS storageordersmarch0503     AWS::CloudFormation::Stack Wed May 22 2019 16:29:10 GMT+1000 (Australian Eastern Standard Time)
UPDATE_IN_PROGRESS hostingS3AndCloudFront     AWS::CloudFormation::Stack Wed May 22 2019 16:29:10 GMT+1000 (Australian Eastern Standard Time)
UPDATE_IN_PROGRESS storageactivitiesmarch0503 AWS::CloudFormation::Stack Wed May 22 2019 16:29:10 GMT+1000 (Australian Eastern Standard Time)
UPDATE_IN_PROGRESS authcognito8146221a        AWS::CloudFormation::Stack Wed May 22 2019 16:29:10 GMT+1000 (Australian Eastern Standard Time)
⠴ Updating resources in the cloud. This may take a few minutes...
UPDATE_ROLLBACK_COMPLETE pnamar05first-20190509182634-authcognito8146221a-12ZOVT03QH2PD AWS::CloudFormation::Stack Wed May 22 2019 16:29:12 GMT+1000 (Australian Eastern Standard Time)
⠦ Updating resources in the cloud. This may take a few minutes...
DELETE_COMPLETE          S3Bucket                                                         AWS::S3::Bucket            Wed May 22 2019 16:29:13 GMT+1000 (Australian Eastern Standard Time)
UPDATE_ROLLBACK_COMPLETE pnamar05first-20190509182634-hostingS3AndCloudFront-UCO7ZL6OJIZS AWS::CloudFormation::Stack Wed May 22 2019 16:29:13 GMT+1000 (Australian Eastern Standard Time)
⠋ Updating resources in the cloud. This may take a few minutes...
DELETE_COMPLETE          DynamoDBTable                                                     AWS::DynamoDB::Table       Wed May 22 2019 16:29:13 GMT+1000 (Australian Eastern Standard Time)
UPDATE_ROLLBACK_COMPLETE pnamar05first-20190509182634-storageordersmarch0503-1RLVMFGWLTCIX AWS::CloudFormation::Stack Wed May 22 2019 16:29:13 GMT+1000 (Australian Eastern Standard Time)
⠸ Updating resources in the cloud. This may take a few minutes...
UPDATE_COMPLETE          storageactivitiesmarch0503   AWS::CloudFormation::Stack Wed May 22 2019 16:29:21 GMT+1000 (Australian Eastern Standard Time)
UPDATE_COMPLETE          hostingS3AndCloudFront       AWS::CloudFormation::Stack Wed May 22 2019 16:29:21 GMT+1000 (Australian Eastern Standard Time)
UPDATE_COMPLETE          authcognito8146221a          AWS::CloudFormation::Stack Wed May 22 2019 16:29:21 GMT+1000 (Australian Eastern Standard Time)
UPDATE_COMPLETE          storageordersmarch0503       AWS::CloudFormation::Stack Wed May 22 2019 16:29:21 GMT+1000 (Australian Eastern Standard Time)
UPDATE_ROLLBACK_COMPLETE pnamar05first-20190509182634 AWS::CloudFormation::Stack Wed May 22 2019 16:29:22 GMT+1000 (Australian Eastern Standard Time)
⠹ Updating resources in the cloud. This may take a few minutes...Error updating cloudformation stack
⠦ Updating resources in the cloud. This may take a few minutes...
Following resources failed
Resource Name: pnamarch05-06-livezero (AWS::S3::Bucket)
Event Type: update
Reason: pnamarch05-06-devfirst already exists in stack arn:aws:cloudformation:eu-west-1:478576439851:stack/pnamar05first-20190511104149-hostingS3AndCloudFront-1JGA1AFF5RCIA/9de8ea90-7386-11e9-9701-02f49d781af6
URL: https://console.aws.amazon.com/cloudformation/home?region=eu-west-1#/stacks/arn%3Aaws%3Acloudformation%3Aeu-west-1%3A478576439851%3Astack%2Fpnamar05first-20190509182634-hostingS3AndCloudFront-UCO7ZL6OJIZS%2F8970c3e0-7236-11e9-8998-02f48c625dae/events
Resource Name: ordersmarch0503-livezero (AWS::DynamoDB::Table)
Event Type: update
Reason: ordersmarch0503-devfirst already exists in stack arn:aws:cloudformation:eu-west-1:478576439851:stack/pnamar05first-20190511104149-storageordersmarch0503-1UW0ZZN4JM8XX/9df1eb40-7386-11e9-97c6-0a1f01fad44c
URL: https://console.aws.amazon.com/cloudformation/home?region=eu-west-1#/stacks/arn%3Aaws%3Acloudformation%3Aeu-west-1%3A478576439851%3Astack%2Fpnamar05first-20190509182634-storageordersmarch0503-1RLVMFGWLTCIX%2F89c7bd80-7236-11e9-ac7e-0a99a68566c4/events
Resource Name: activitiesmarch0503-livezero (AWS::DynamoDB::Table)
Event Type: update
Reason: activitiesmarch0503-devfirst already exists in stack arn:aws:cloudformation:eu-west-1:478576439851:stack/pnamar05first-20190511104149-storageactivitiesmarch0503-3BJQ34B737FB/9ddfe9e0-7386-11e9-b49e-0aac5439e4be
URL: https://console.aws.amazon.com/cloudformation/home?region=eu-west-1#/stacks/arn%3Aaws%3Acloudformation%3Aeu-west-1%3A478576439851%3Astack%2Fpnamar05first-20190509182634-storageactivitiesmarch0503-1KNWL68WBRA94%2F89920780-7236-11e9-b69b-024e38e0666a/events
✖ An error occurred when pushing the resources to the cloud
Resource is not in the state stackUpdateComplete

@stayingcool S3 bucket name have to be globally unique (not just in your account) and from the CloudFormation error it looks like the bucket name you chose has already been taken. Could you try using a different bucket name which is not taken?

Hello @yuth, I'm having the same issue, and i din't specify a S3 name... what could it be other then what you have mentioned??
Please advise

@ravnarayan Could you share the output you get from cloudformation

Hey @yuth, thank you for the quick reply, Please see below as per your request:
⠼ Updating resources in the cloud. This may take a few minutes...
CREATE_COMPLETE authcognito08c501nb AWS::CloudFormation::Stack Wed May 22 2019 13:39:01 GMT+0000 (Coordinated Universal Time)
⠦ Updating resources in the cloud. This may take a few minutes...Error updating cloudformation stack
⠇ Updating resources in the cloud. This may take a few minutes...
Following resources failed
✖ An error occurred when pushing the resources to the cloud
Resource is not in the state stackUpdateComplete

@ravnarayan could you include the full cloudformation log. From the above output I cant see what failed.
Also whats version of Amplify CLI you have running on your machine?

Hey @yuth
amplify -v = 1.6.10
sorry i'm not very good at this... What Command would i run to acquire cloudformation log?
thank you

@ravnarayan when you run amplify push it prints it to the screen. Could you include everything after the push command

hey @yuth, Perfect, please see below:
amplify push
Current Environment: local

Category
Resource name
Operation
Provider plugin

Auth
cognito80c046be
Create
awscloudformation

Analytics
mobileappreactnative
Create
awscloudformation

Api
MobileAppreactNativeGraphQL
Create
awscloudformation

? Are you sure you want to continue? Yes

GraphQL schema compiled successfully.
Edit your schema at /home/bitnami/amplify/backend/api/MobileAppreactNativeGraphQL/schema.graphql or place .graphql files in a directory at /home/bitnami/amplify/backend/api/MobileAppreactNativeGraphQL/schema
? Do you want to generate code for your newly created GraphQL API Yes
? Choose the code generation language target javascript
? Enter the file name pattern of graphql queries, mutations and subscriptions src/graphql/**/*.js
? Do you want to generate/update all possible GraphQL operations - queries, mutations and subscriptions Ye
s
? Enter maximum statement depth [increase from default if your schema is deeply nested] 2
⠋ Updating resources in the cloud. This may take a few minutes...
UPDATE_IN_PROGRESS mobileappreactnative-20190425055621 AWS::CloudFormation::Stack Wed May 22 2019 13:36:38 GMT+0000 (Coordinated Universal Time) User Initiated
⠙ Updating resources in the cloud. This may take a few minutes...
CREATE_IN_PROGRESS analyticsmobileappreactnative  AWS::CloudFormation::Stack Wed May 22 2019 13:36:45 GMT+0000 (Coordinated Universal Time) Resource creation Initiated
CREATE_IN_PROGRESS authcognito80c046be            AWS::CloudFormation::Stack Wed May 22 2019 13:36:45 GMT+0000 (Coordinated Universal Time) Resource creation Initiated
CREATE_IN_PROGRESS apiMobileAppreactNativeGraphQL AWS::CloudFormation::Stack Wed May 22 2019 13:36:45 GMT+0000 (Coordinated Universal Time) Resource creation Initiated
CREATE_IN_PROGRESS authcognito80c046be            AWS::CloudFormation::Stack Wed May 22 2019 13:36:44 GMT+0000 (Coordinated Universal Time)
CREATE_IN_PROGRESS analyticsmobileappreactnative  AWS::CloudFormation::Stack Wed May 22 2019 13:36:44 GMT+0000 (Coordinated Universal Time)
CREATE_IN_PROGRESS apiMobileAppreactNativeGraphQL AWS::CloudFormation::Stack Wed May 22 2019 13:36:44 GMT+0000 (Coordinated Universal Time)
⠹ Updating resources in the cloud. This may take a few minutes...
CREATE_IN_PROGRESS mobileappreactnative-20190425055621-analyticsmobileappreactnative-1ELRGAJ06F39M AWS::CloudFormation::Stack Wed May 22 2019 13:36:45 GMT+0000 (Coordinated Universal Time) User Initiated
⠸ Updating resources in the cloud. This may take a few minutes...
CREATE_IN_PROGRESS mobileappreactnative-20190425055621-authcognito80c046be-8Y0YYD2XZSJF AWS::CloudFormation::Stack Wed May 22 2019 13:36:45 GMT+0000 (Coordinated Universal Time) User Initiated
⠴ Updating resources in the cloud. This may take a few minutes...
CREATE_IN_PROGRESS mobileappreactnative-20190425055621-apiMobileAppreactNativeGraphQL-IFFCTTC5CNP0 AWS::CloudFormation::Stack Wed May 22 2019 13:36:45 GMT+0000 (Coordinated Universal Time) User Initiated
⠼ Updating resources in the cloud. This may take a few minutes...
CREATE_IN_PROGRESS LambdaExecutionRole AWS::IAM::Role Wed May 22 2019 13:36:52 GMT+0000 (Coordinated Universal Time) Resource creation Initiated
CREATE_IN_PROGRESS LambdaExecutionRole AWS::IAM::Role Wed May 22 2019 13:36:52 GMT+0000 (Coordinated Universal Time)
⠴ Updating resources in the cloud. This may take a few minutes...
CREATE_IN_PROGRESS SNSRole AWS::IAM::Role Wed May 22 2019 13:36:53 GMT+0000 (Coordinated Universal Time) Resource creation Initiated
CREATE_IN_PROGRESS SNSRole AWS::IAM::Role Wed May 22 2019 13:36:52 GMT+0000 (Coordinated Universal Time)
⠦ Updating resources in the cloud. This may take a few minutes...
CREATE_COMPLETE    GraphQLAPI AWS::AppSync::GraphQLApi Wed May 22 2019 13:36:54 GMT+0000 (Coordinated Universal Time)
CREATE_IN_PROGRESS GraphQLAPI AWS::AppSync::GraphQLApi Wed May 22 2019 13:36:53 GMT+0000 (Coordinated Universal Time) Resource creation Initiated
CREATE_IN_PROGRESS GraphQLAPI AWS::AppSync::GraphQLApi Wed May 22 2019 13:36:50 GMT+0000 (Coordinated Universal Time)
⠇ Updating resources in the cloud. This may take a few minutes...
CREATE_IN_PROGRESS GraphQLAPIKey AWS::AppSync::ApiKey        Wed May 22 2019 13:36:57 GMT+0000 (Coordinated Universal Time)
CREATE_IN_PROGRESS GraphQLSchema AWS::AppSync::GraphQLSchema Wed May 22 2019 13:36:57 GMT+0000 (Coordinated Universal Time)
⠏ Updating resources in the cloud. This may take a few minutes...
CREATE_COMPLETE    GraphQLAPIKey AWS::AppSync::ApiKey        Wed May 22 2019 13:37:01 GMT+0000 (Coordinated Universal Time)
CREATE_IN_PROGRESS GraphQLAPIKey AWS::AppSync::ApiKey        Wed May 22 2019 13:37:01 GMT+0000 (Coordinated Universal Time) Resource creation Initiated
CREATE_IN_PROGRESS GraphQLSchema AWS::AppSync::GraphQLSchema Wed May 22 2019 13:36:59 GMT+0000 (Coordinated Universal Time) Resource creation Initiated
⠏ Updating resources in the cloud. This may take a few minutes...
CREATE_IN_PROGRESS PinpointFunction    AWS::Lambda::Function Wed May 22 2019 13:37:08 GMT+0000 (Coordinated Universal Time)
CREATE_COMPLETE    LambdaExecutionRole AWS::IAM::Role        Wed May 22 2019 13:37:04 GMT+0000 (Coordinated Universal Time)
⠼ Updating resources in the cloud. This may take a few minutes...
CREATE_COMPLETE    PinpointFunction AWS::Lambda::Function Wed May 22 2019 13:37:09 GMT+0000 (Coordinated Universal Time)
CREATE_IN_PROGRESS PinpointFunction AWS::Lambda::Function Wed May 22 2019 13:37:09 GMT+0000 (Coordinated Universal Time) Resource creation Initiated
⠙ Updating resources in the cloud. This may take a few minutes...
CREATE_IN_PROGRESS PinpointFunctionOutputs Custom::LambdaCallout Wed May 22 2019 13:37:12 GMT+0000 (Coordinated Universal Time)
⠹ Updating resources in the cloud. This may take a few minutes...
CREATE_COMPLETE SNSRole AWS::IAM::Role Wed May 22 2019 13:37:12 GMT+0000 (Coordinated Universal Time)
⠸ Updating resources in the cloud. This may take a few minutes...
CREATE_COMPLETE GraphQLSchema AWS::AppSync::GraphQLSchema Wed May 22 2019 13:37:11 GMT+0000 (Coordinated Universal Time)
⠸ Updating resources in the cloud. This may take a few minutes...
CREATE_IN_PROGRESS UserPool AWS::Cognito::UserPool Wed May 22 2019 13:37:17 GMT+0000 (Coordinated Universal Time)
⠼ Updating resources in the cloud. This may take a few minutes...
CREATE_IN_PROGRESS Todo AWS::CloudFormation::Stack Wed May 22 2019 13:37:16 GMT+0000 (Coordinated Universal Time) Resource creation Initiated
CREATE_IN_PROGRESS Todo AWS::CloudFormation::Stack Wed May 22 2019 13:37:15 GMT+0000 (Coordinated Universal Time)
⠧ Updating resources in the cloud. This may take a few minutes...
CREATE_IN_PROGRESS mobileappreactnative-20190425055621-apiMobileAppreactNativeGraphQL-IFFCTTC5CNP0-Todo-17PE0BC2FL8FV AWS::CloudFormation::Stack Wed May 22 2019 13:37:16 GMT+0000 (Coordinated Universal Time) User Initiated
⠴ Updating resources in the cloud. This may take a few minutes...
CREATE_COMPLETE    UserPool AWS::Cognito::UserPool Wed May 22 2019 13:37:21 GMT+0000 (Coordinated Universal Time)
CREATE_IN_PROGRESS UserPool AWS::Cognito::UserPool Wed May 22 2019 13:37:21 GMT+0000 (Coordinated Universal Time) Resource creation Initiated
⠏ Updating resources in the cloud. This may take a few minutes...
CREATE_IN_PROGRESS TodoTable   AWS::DynamoDB::Table Wed May 22 2019 13:37:23 GMT+0000 (Coordinated Universal Time) Resource creation Initiated
CREATE_IN_PROGRESS TodoIAMRole AWS::IAM::Role       Wed May 22 2019 13:37:23 GMT+0000 (Coordinated Universal Time) Resource creation Initiated
CREATE_IN_PROGRESS TodoTable   AWS::DynamoDB::Table Wed May 22 2019 13:37:22 GMT+0000 (Coordinated Universal Time)
CREATE_IN_PROGRESS TodoIAMRole AWS::IAM::Role       Wed May 22 2019 13:37:22 GMT+0000 (Coordinated Universal Time)
⠦ Updating resources in the cloud. This may take a few minutes...
CREATE_COMPLETE    UserPoolClient    AWS::Cognito::UserPoolClient Wed May 22 2019 13:37:29 GMT+0000 (Coordinated Universal Time)
CREATE_IN_PROGRESS UserPoolClient    AWS::Cognito::UserPoolClient Wed May 22 2019 13:37:28 GMT+0000 (Coordinated Universal Time) Resource creation Initiated
CREATE_COMPLETE    UserPoolClientWeb AWS::Cognito::UserPoolClient Wed May 22 2019 13:37:28 GMT+0000 (Coordinated Universal Time)
CREATE_IN_PROGRESS UserPoolClientWeb AWS::Cognito::UserPoolClient Wed May 22 2019 13:37:28 GMT+0000 (Coordinated Universal Time) Resource creation Initiated
CREATE_IN_PROGRESS UserPoolClient    AWS::Cognito::UserPoolClient Wed May 22 2019 13:37:26 GMT+0000 (Coordinated Universal Time)
CREATE_IN_PROGRESS UserPoolClientWeb AWS::Cognito::UserPoolClient Wed May 22 2019 13:37:26 GMT+0000 (Coordinated Universal Time)
⠸ Updating resources in the cloud. This may take a few minutes...
CREATE_IN_PROGRESS UserPoolClientRole AWS::IAM::Role Wed May 22 2019 13:37:34 GMT+0000 (Coordinated Universal Time)
⠋ Updating resources in the cloud. This may take a few minutes...
CREATE_IN_PROGRESS UserPoolClientRole AWS::IAM::Role Wed May 22 2019 13:37:35 GMT+0000 (Coordinated Universal Time) Resource creation Initiated
⠼ Updating resources in the cloud. This may take a few minutes...
CREATE_COMPLETE TodoIAMRole AWS::IAM::Role Wed May 22 2019 13:37:44 GMT+0000 (Coordinated Universal Time)
⠦ Updating resources in the cloud. This may take a few minutes...
CREATE_IN_PROGRESS TodoDataSource AWS::AppSync::DataSource Wed May 22 2019 13:37:48 GMT+0000 (Coordinated Universal Time)
⠼ Updating resources in the cloud. This may take a few minutes...
CREATE_COMPLETE UserPoolClientRole AWS::IAM::Role Wed May 22 2019 13:37:53 GMT+0000 (Coordinated Universal Time)
⠏ Updating resources in the cloud. This may take a few minutes...
CREATE_COMPLETE    TodoTable      AWS::DynamoDB::Table     Wed May 22 2019 13:37:53 GMT+0000 (Coordinated Universal Time)
CREATE_COMPLETE    TodoDataSource AWS::AppSync::DataSource Wed May 22 2019 13:37:50 GMT+0000 (Coordinated Universal Time)
CREATE_IN_PROGRESS TodoDataSource AWS::AppSync::DataSource Wed May 22 2019 13:37:50 GMT+0000 (Coordinated Universal Time) Resource creation Initiated
⠹ Updating resources in the cloud. This may take a few minutes...
CREATE_IN_PROGRESS UpdateTodoResolver AWS::AppSync::Resolver Wed May 22 2019 13:37:54 GMT+0000 (Coordinated Universal Time)
⠴ Updating resources in the cloud. This may take a few minutes...
CREATE_IN_PROGRESS UserPoolClientLambda AWS::Lambda::Function Wed May 22 2019 13:37:58 GMT+0000 (Coordinated Universal Time)
⠏ Updating resources in the cloud. This may take a few minutes...
CREATE_COMPLETE    CreateTodoResolver AWS::AppSync::Resolver Wed May 22 2019 13:37:59 GMT+0000 (Coordinated Universal Time)
CREATE_IN_PROGRESS CreateTodoResolver AWS::AppSync::Resolver Wed May 22 2019 13:37:59 GMT+0000 (Coordinated Universal Time) Resource creation Initiated
CREATE_COMPLETE    DeleteTodoResolver AWS::AppSync::Resolver Wed May 22 2019 13:37:58 GMT+0000 (Coordinated Universal Time)
CREATE_IN_PROGRESS DeleteTodoResolver AWS::AppSync::Resolver Wed May 22 2019 13:37:58 GMT+0000 (Coordinated Universal Time) Resource creation Initiated
CREATE_COMPLETE    ListTodoResolver   AWS::AppSync::Resolver Wed May 22 2019 13:37:58 GMT+0000 (Coordinated Universal Time)
CREATE_IN_PROGRESS ListTodoResolver   AWS::AppSync::Resolver Wed May 22 2019 13:37:58 GMT+0000 (Coordinated Universal Time) Resource creation Initiated
CREATE_COMPLETE    GetTodoResolver    AWS::AppSync::Resolver Wed May 22 2019 13:37:57 GMT+0000 (Coordinated Universal Time)
CREATE_IN_PROGRESS GetTodoResolver    AWS::AppSync::Resolver Wed May 22 2019 13:37:57 GMT+0000 (Coordinated Universal Time) Resource creation Initiated
CREATE_COMPLETE    UpdateTodoResolver AWS::AppSync::Resolver Wed May 22 2019 13:37:57 GMT+0000 (Coordinated Universal Time)
CREATE_IN_PROGRESS UpdateTodoResolver AWS::AppSync::Resolver Wed May 22 2019 13:37:56 GMT+0000 (Coordinated Universal Time) Resource creation Initiated
CREATE_IN_PROGRESS DeleteTodoResolver AWS::AppSync::Resolver Wed May 22 2019 13:37:55 GMT+0000 (Coordinated Universal Time)
CREATE_IN_PROGRESS CreateTodoResolver AWS::AppSync::Resolver Wed May 22 2019 13:37:55 GMT+0000 (Coordinated Universal Time)
CREATE_IN_PROGRESS GetTodoResolver    AWS::AppSync::Resolver Wed May 22 2019 13:37:55 GMT+0000 (Coordinated Universal Time)
CREATE_IN_PROGRESS ListTodoResolver   AWS::AppSync::Resolver Wed May 22 2019 13:37:55 GMT+0000 (Coordinated Universal Time)
⠙ Updating resources in the cloud. This may take a few minutes...
CREATE_COMPLETE    UserPoolClientLambda AWS::Lambda::Function Wed May 22 2019 13:37:59 GMT+0000 (Coordinated Universal Time)
CREATE_IN_PROGRESS UserPoolClientLambda AWS::Lambda::Function Wed May 22 2019 13:37:59 GMT+0000 (Coordinated Universal Time) Resource creation Initiated
⠇ Updating resources in the cloud. This may take a few minutes...
CREATE_COMPLETE Todo AWS::CloudFormation::Stack Wed May 22 2019 13:38:03 GMT+0000 (Coordinated Universal Time)
⠇ Updating resources in the cloud. This may take a few minutes...
CREATE_IN_PROGRESS UserPoolClientLambdaPolicy AWS::IAM::Policy Wed May 22 2019 13:38:08 GMT+0000 (Coordinated Universal Time) Resource creation Initiated
CREATE_IN_PROGRESS UserPoolClientLambdaPolicy AWS::IAM::Policy Wed May 22 2019 13:38:06 GMT+0000 (Coordinated Universal Time)
⠋ Updating resources in the cloud. This may take a few minutes...
CREATE_IN_PROGRESS CustomResourcesjson AWS::CloudFormation::Stack Wed May 22 2019 13:38:08 GMT+0000 (Coordinated Universal Time)
⠙ Updating resources in the cloud. This may take a few minutes...
CREATE_IN_PROGRESS CustomResourcesjson AWS::CloudFormation::Stack Wed May 22 2019 13:38:09 GMT+0000 (Coordinated Universal Time) Resource creation Initiated
⠸ Updating resources in the cloud. This may take a few minutes...
CREATE_COMPLETE    mobileappreactnative-20190425055621-apiMobileAppreactNativeGraphQL-CustomResourcesjson-1O7DD2QTNAOEF AWS::CloudFormation::Stack Wed May 22 2019 13:38:13 GMT+0000 (Coordinated Universal Time)
CREATE_IN_PROGRESS mobileappreactnative-20190425055621-apiMobileAppreactNativeGraphQL-CustomResourcesjson-1O7DD2QTNAOEF AWS::CloudFormation::Stack Wed May 22 2019 13:38:09 GMT+0000 (Coordinated Universal Time) User Initiated
⠙ Updating resources in the cloud. This may take a few minutes...
CREATE_COMPLETE UserPoolClientLambdaPolicy AWS::IAM::Policy Wed May 22 2019 13:38:16 GMT+0000 (Coordinated Universal Time)
⠼ Updating resources in the cloud. This may take a few minutes...
CREATE_IN_PROGRESS UserPoolClientLogPolicy AWS::IAM::Policy Wed May 22 2019 13:38:23 GMT+0000 (Coordinated Universal Time) Resource creation Initiated
CREATE_IN_PROGRESS UserPoolClientLogPolicy AWS::IAM::Policy Wed May 22 2019 13:38:21 GMT+0000 (Coordinated Universal Time)
⠴ Updating resources in the cloud. This may take a few minutes...
CREATE_COMPLETE mobileappreactnative-20190425055621-apiMobileAppreactNativeGraphQL-IFFCTTC5CNP0 AWS::CloudFormation::Stack Wed May 22 2019 13:38:24 GMT+0000 (Coordinated Universal Time)
CREATE_COMPLETE CustomResourcesjson                                                             AWS::CloudFormation::Stack Wed May 22 2019 13:38:20 GMT+0000 (Coordinated Universal Time)
⠧ Updating resources in the cloud. This may take a few minutes...
CREATE_COMPLETE UserPoolClientLogPolicy AWS::IAM::Policy Wed May 22 2019 13:38:31 GMT+0000 (Coordinated Universal Time)
⠏ Updating resources in the cloud. This may take a few minutes...
CREATE_IN_PROGRESS UserPoolClientInputs Custom::LambdaCallout Wed May 22 2019 13:38:35 GMT+0000 (Coordinated Universal Time)
⠇ Updating resources in the cloud. This may take a few minutes...
CREATE_COMPLETE apiMobileAppreactNativeGraphQL AWS::CloudFormation::Stack Wed May 22 2019 13:38:39 GMT+0000 (Coordinated Universal Time)
⠋ Updating resources in the cloud. This may take a few minutes...
CREATE_COMPLETE    UserPoolClientInputs Custom::LambdaCallout Wed May 22 2019 13:38:40 GMT+0000 (Coordinated Universal Time)
CREATE_IN_PROGRESS UserPoolClientInputs Custom::LambdaCallout Wed May 22 2019 13:38:40 GMT+0000 (Coordinated Universal Time) Resource creation Initiated
⠹ Updating resources in the cloud. This may take a few minutes...
CREATE_COMPLETE    IdentityPool AWS::Cognito::IdentityPool Wed May 22 2019 13:38:48 GMT+0000 (Coordinated Universal Time)
CREATE_IN_PROGRESS IdentityPool AWS::Cognito::IdentityPool Wed May 22 2019 13:38:47 GMT+0000 (Coordinated Universal Time) Resource creation Initiated
CREATE_IN_PROGRESS IdentityPool AWS::Cognito::IdentityPool Wed May 22 2019 13:38:45 GMT+0000 (Coordinated Universal Time)
⠴ Updating resources in the cloud. This may take a few minutes...
CREATE_IN_PROGRESS IdentityPoolRoleMap AWS::Cognito::IdentityPoolRoleAttachment Wed May 22 2019 13:38:53 GMT+0000 (Coordinated Universal Time)
⠴ Updating resources in the cloud. This may take a few minutes...
CREATE_COMPLETE    mobileappreactnative-20190425055621-authcognito80c046be-8Y0YYD2XZSJF AWS::CloudFormation::Stack               Wed May 22 2019 13:38:59 GMT+0000 (Coordinated Universal Time)
CREATE_COMPLETE    IdentityPoolRoleMap                                                  AWS::Cognito::IdentityPoolRoleAttachment Wed May 22 2019 13:38:55 GMT+0000 (Coordinated Universal Time)
CREATE_IN_PROGRESS IdentityPoolRoleMap                                                  AWS::Cognito::IdentityPoolRoleAttachment Wed May 22 2019 13:38:55 GMT+0000 (Coordinated Universal Time) Resource creation Initiated
⠼ Updating resources in the cloud. This may take a few minutes...
CREATE_COMPLETE authcognito80c046be AWS::CloudFormation::Stack Wed May 22 2019 13:39:01 GMT+0000 (Coordinated Universal Time)
⠦ Updating resources in the cloud. This may take a few minutes...Error updating cloudformation stack
⠇ Updating resources in the cloud. This may take a few minutes...
Following resources failed
✖ An error occurred when pushing the resources to the cloud
Resource is not in the state stackUpdateComplete

@ravnarayan the logs don't show anything as failing. Could you goto the cloudformation console and see if there is anything that failed earlier. You can find your stack name by looking at <project-root>/amplify/backend/amplify-meta.json under provider -> awscloudformation -> StackName

Hey @yuth
Okay so i looked into amplify-meta.json and all it shows is lastPushTimeStamp, and under stack name it illustrates "mobileappreactnative"

@ravnarayan I won't have access to the Cloud Formation resource created in your project. Could you goto the cloudformation console and choose the region where you have your project provisioned. After this you should be able to see the search for the stack name mobileappreactnative and see the events.
Could you share any failed events from there so we know whats going on with your project

Hey @yuth
THank you for the instructions i followed, and this is what i got.
was not successfully created:

18:07:17 UTC-0600
CREATE_FAILED
AWS::CloudFormation::Stack
analyticsmobileappreactnative

The following resource(s) failed to create: [PinpointFunctionOutputs].

This is the only one i see

I looks like one of the nested stack has issue. Could you search for mobileappreactnative-20190425055621-analyticsmobileappreactnativ in the Cloudformation and see if there are any events that have failed there

could you open the file <project-root>/amplify/backend/analytics/<resource-name>/pinpoint-cloudformation-template.json and see whats the version of node in Runtime? If its nodejs6.10 follow the migration docs from our doc site and update your resource and see if that fixes the issue

hey @yuth
Actually, mobileappreactnative-20190425055621-analyticsmobileappreactnativ is associated with:
The following resource(s) failed to create: [PinpointFunctionOutputs]. |   |  (as per my last Correspondence), this is the only one i can see. Also i had to change nodejs6.10 - nodejs8.10 in order to get rid of the error i was facing before, so yeah this is up to date
Thank you,

@ravnarayan could you share the <project-root>/amplify/backend/analytics/<resource-name>/pinpoint-cloudformation-template.json file. Its not really clear whats happening from the Cloudformation log

Hey @yuth
What i am doing now is trying to run "Amplify Push" after running "amplify remove auth"... I think cognito may have been a issue... Once its complete i will advise if there are any errors... After that maybe i can go back in and add "amplify remove auth" to bring cognito back in.
Do you think this will work?
Also my "pinpoint-cloudformation-template.json" 537 lines, is there a specific that you are looking for?
thank you yuth.

Hey @yuth
Same thing another error, I think i should restart amplify, I think i should do this by deleting the current process.... Would you have any idea on how i can delete it?
Thank you,

Hey @yuth
deleted amplify, and started new project, and it WORKED! Thank you for all your help.

@stayingcool Are you still seeing push failures?

Yes. I still have the issue.
What is very frustrating is to restart a new project, recreate everything, rewire everything and expect the push every time to work nervously.

@stayingcool You might want to manually delete this S3 bucket from the AWS console - pnamarch05-06-devfirst and try pushing again.

@stayingcool Are you still stuck after deleting the S3 bucket?

@stayingcool You might want to manually delete this S3 bucket from the AWS console - pnamarch05-06-devfirst and try pushing again.

Is it secure?


پروکسی تلگرام بهمن

Can't understand, don't know Persian and translator doesn't help much.

He asked if this can works with telegram.lol

Yeah, it works with Telegram.


FileSaveDialog bad behaviour when changing extension type for files with dots on name

Describe the bug
When having a default or typed filename containing dots, example: "treefrog_45_cut_0.05mm_1h20m.ctb.heatmap.png" and if we select another extension type from dropdown, it will strip the .jpg but not append the new extension, if we return back to png the extension is set. However if we select another extension then select another and get back to the previous, we get the extension set. Please see the attached GIF: https://i.imgur.com/VD4SmHq.gif
This don't happen when file is clean without the extra dots
Code
public static readonly List<FileDialogFilter> ImagesFullFileFilter = new()
{
    new()
    {
        Name = "PNG Files",
        Extensions = new List<string>
        {
            "png"
        }
    },
    new()
    {
        Name = "JPG Files",
        Extensions = new List<string>
        {
            "jpg",
            "jpeg"
        }
    },
    new()
    {
        Name = "BMP Files",
        Extensions = new List<string>
        {
            "bmp",
        }
    },
    new()
    {
        Name = "TIF Files",
        Extensions = new List<string>
        {
            "tif",
            "tiff",
        }
    },
};

var dialog = new SaveFileDialog
{
    Filters = Helpers.ImagesFullFileFilter,
    InitialFileName = Path.GetFileName(SlicerFile.FileFullPath) + ".heatmap.png",
    Directory = Path.GetDirectoryName(SlicerFile.FileFullPath),
};
var file = await dialog.ShowAsync(ParentWindow);

Expected behavior
When change extension, trim the last extension on filename and append the selected one
Desktop (please complete the following information):

OS: Windows 10 v20H2
Version 0.10.5

I found this issue to be reproduceable outside of Avalonia using MS Word SaveDialog. Appears to be a Windows dialog issue?

Most likely, avalonia seens to use windows dialog.
Close this if you fell not related to Avalonia


Is the project looking for any new contributors?

Was looking at #111 and am assuming it's still current. I am interested in contributing, and was wondering if you had any progress on the roadmap since 2018 and/or a contributions guide.
I was specifically thinking about the availability and fault-tolerance considerations mentioned in the above issue. Was there any dev work done on either that or #105 that already covered this use case?
Please let me know if there's anything I can do!

Sorry for the late response! Client failover to a reconstructed view after a worker failure is still a current issue, as per #105. Fixing that would be fantastic :-)

Sorry about this! Took a while, so I think I stopped getting the notifications. Do you still need anything?


Master to Live

Docs Build status updates of commit 5c39d59:
:clock10: Full build: the average full build time is 11 min(s) 51 sec(s), this is based on the last 961 build(s) for this repository.

Docs Build status updates of commit 5c39d59:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/mailbox-databases-and-servers/Move-DatabasePath.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/mailboxes/Set-Mailbox.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/organization/New-ApplicationAccessPolicy.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


GPT: Test Double

Test Double - Expert in creating diverse test data for development needs in various formats.
https://chat.openai.com/g/g-yK9Ggt181-test-double

Merged


WIP: Adding libvpx support

I tried to add libvpx support to the build. For now it's succesfully building the linux build on circleci.
After changing the API tokens to their original values the build is failing on circleci. Previously the build was succesfull (https://circleci.com/gh/lengra/ffmpeg-feedstock/26/)

Hi! This is the friendly automated conda-forge-linting service.
I was trying to look for recipes to lint for you, but it appears we have a merge conflict.
Please try to merge or rebase with the base branch to resolve this conflict.
Please ping the 'conda-forge/core' team (using the @ notation in a comment) if you believe this is a bug.

We need to add the libvpx recipe to conda-forge before we can accept this. We don't use conda install inside a recipe, It should be listed as a requirement. Also, please use conda smithy to update the recipe of required, do not make ad-hoc changes to the build scripts.

Also would squash all commits and rebase. There appears to be things in here which shouldn't exist (like mucking with tokens) and other changes that were already made in master.

FYI there is some work to add libvpx in PR ( https://github.com/conda-forge/staged-recipes/pull/6954 ).


fix-pantheon: corrected the include file

Purpose: To resolve the pantheon issue

/cherrypick 1.1.x


Instantiate-to-bounds produces different result in dart and analyzer in some cases

Dart SDK Version: 2.1.0-dev.7.1
OS: Windows 10
The following source code example declares class G, prints its actual type and assigns G object to a variable of its actual type:
typedef F<X> = void Function<Y extends X>();
F<X> toF<X>(X x) => null;

class A<X> {}
class B<X> extends A<X> {}
class G<X1 extends A<X1>, X2 extends A<X1>, X3 extends B, X4 extends X2> {}

main() {
  G source;
  print(G);
  var fsource = toF(source);
  F<G<A<dynamic>, A<A<dynamic>>, B<dynamic>, A<A<dynamic>>>> target = fsource;
}

Dart passes with this, the output is: G<A<dynamic>, A<A<dynamic>>, B<dynamic>, A<A<dynamic>>>, and so it's actual type of G.
However, analyzer fails with compile error here, error message reads that analyzer treats G actual type as G<A<dynamic>, A<dynamic>, B<dynamic>,dynamic>:
error - A value of type '<Y extends G< A <dynamic>, A<dynamic>, B<dynamic>, dynamic>>() -> void' can't be assigned to a variable of type '<Y extends G<A<dynamic>, A<A<dynamic>>, B<dynamic>, A<A<dynamic>>>>() -> void' at test1.dart:12:71 - invalid_assignment

I've simplified a testcase above:
typedef F<X> = void Function<Y extends X>();
F<X> toF<X>(X x) => null;

class B<X> {}
class A<X1 extends B<X1>, X2 extends X1> {}

main() {
  A source;
  print(A);
  var fsource = toF(source);
  F<A<B<dynamic>, B<dynamic>>> target = fsource;
}

It also passes with dart and produces compile time error with analyzer.

Right, the simplified example is also a bug in the analyzer.

If you put @dart=2.9 above the example, the analyzer now produces no errors.


fix: unnecessary use of spread removed

Looks great to me!

Looks great to me!

@danidre14  @shalithasuranga can you please review and merge this really excited.


Key reference in content referenced content not properly expanded when using key scopes

I'm attaching a sample project file, the main DITA Map is "hzm1617899793683.ditamap" and it can be published to PDF:
keyscope-conkeyref-keyword-fail-1.zip
There is a topic named "xge1617899981044.xml" referenced as resource-only in multiple key scope contexts.
Paragraphs from this topic are reused in other topics via conkeyref, for example in "jxk1617900527138.xml".
Key references are expanded by the DITA OT before content references. The "org.dita.dost.module.KeyrefModule.processTopic(FileInfo, KeyScope, boolean)" method considers that it should not create unique files for each reference to the "xge1617899981044.xml" topic because it is resource-only:
  final int increment = isResourceOnly ? 0 : 1;

In my opinion the condition should be something like:
 final int increment = isResourceOnly && ! ditaFormat ? 0 : 1;

My final patch in the "org.dita.dost.module.KeyrefModule.processTopic(FileInfo, KeyScope, boolean)" method from the DITA OT Java code looks like this:
 /**
  * Determine how topic is processed for key reference processing.
  *
  * @return key reference processing
  */
 private ResolveTask processTopic(final FileInfo f, final KeyScope scope, final boolean isResourceOnly) {
     //EXM-47806 Possible patch, increment counters more eager for references to resource only topics.
     boolean ditaFormat = f.format == null || "dita".equals(f.format);
     final int increment = isResourceOnly && ! ditaFormat ? 0 : 1;
     final Integer used = usage.containsKey(f.uri) ? usage.get(f.uri) + increment : increment;
     usage.put(f.uri, used);

     if (used > 1) {
         final URI result = addSuffix(f.result, "-" + (used - 1));
         final URI out = tempFileNameScheme.generateTempFileName(result);
         final FileInfo fo = new FileInfo.Builder(f)
                 .uri(out)
                 .result(result)
                 .build();
         // TODO: Should this be added when content is actually generated?
         job.add(fo);
         return new ResolveTask(scope, f, fo);
     } else {
         return new ResolveTask(scope, f, null);
     }
 }

Hi,
I asked Radu for a build with the patch for this issue because I have a client that urgently needs for keyscope to work in conreffed content. I was able to confirm that it works for HTML and PDF (XSL-FO) outputs.
I had problems testing with maps and topics that used XSD and had to convert everything to DTDs, not sure if it was related to the patch or the specific Oxygen publishing engine configuration.
Is it possible to let us know when this patch will be pulled into the main branch? A date will help us decide if we sit back and chill or if we need to implement our plan B that implies a lot of conditional filters and ditavalref.
Thanks!


create an article about how to use aegis in a cluster from zero to hero

could be a part of the aegis.z2h.dev static website to keep things consistent.

punting to 1.1.0

This passes as an article I think :) » https://aegis.z2h.dev/docs/register/


Extra feature

Wonder if we can consider to push features such as extracting private key from keystore available for this package?

Hey @andylim0221,
Thanks for getting in touch! Sounds good to me. 🚀
Can you propose which existing Web3 APIs you think would be needed to achieve this? Then we'd be able to treat those as a reference. One thing to keep in mind is that this functionality of course might only be available if it is exposed by the native dependencies we're using in this project. But if this is standard behaviour, they should be there.

In web3, there's web3.eth.accounts.decrypt(keystoreJsonV3, password) which takes keystoreJsonV3 and password as parameters.
From my last project, we load the keystore file in and process decryption in native modules with web3j and web3swift respectively. I think it's worth to try out if you have any alternatives.

Hey @andylim0221, sounds good to me!
It looks like we can get the private key on iOS.  It might take a little more searching for a similar function in web3j on Android.

This line seems to provide us with the equivalent key pair, so we should be able to retrieve the private key from here.


GD.LogRich logs escape codes to log files

Godot version
v4.0.2.stable.mono.official [7a0977ce2]
System information
Windows 10
Issue description
I've been toying around with rich text logging on Windows and noticed that the added escape codes are being logged in the log files as well.
Ideally I believe these shouldn't exist in the log files.
Steps to reproduce

Enable File Logging in Project Settings > General > Debug > File Logging > Enable File Logging
Run a script that calls GD.PrintRich("[color=green]Hello World[/color]");
Open the log file in %appdata%/Godot/app_userdata/your_project/godot.log

Minimal reproduction project
N/A

I don't see why the log should strip text you manually added

__print_line_rich() seems to have a code that replaces BBCode with ANSI escapes.
https://github.com/godotengine/godot/blob/0032c1c0c203ba225dd41bdc799f2e622bccfde5/core/string/print_string.cpp#L88-L98
Maybe the condition disables it for files? Not sure what's the more expected behavior though.

print_line_rich() should have a isatty(fileno(stdout)) check. If false (which indicates a non-interactive scenario such as writing stdout to a file), use print_line().


⚠ Bofrost.be has degraded performance

In 5c6f87d, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1771 ms

Resolved: Bofrost.be performance has improved in 72c8845.


Clarify seek() in relation to animation_finished

Resolves #22210

Thanks!

Cherry-picked for 3.5.


Fix Vue conditional example

red/orange/green switcher doesn't work correctly. Small fix for that.

Nice catch ! Thanks a lot !


Additional PostHTML plugins to use - config and usage instructions

Hello,
I would like to use the 'posthtml-components' plugin https://github.com/thewebartisan7/posthtml-components but I am having trouble getting it to work with vituum and the vite-plugin-posthtml plugin.
Have you been able to install and use post-html plugins together with vituum and the vite-plugin-posthtml and if so what should I be adding to vite.config.js.
Many thanks

You should be able to add it via https://vituum.dev/plugins/posthtml.html#plugins in config


Test Secure WebSockets

Resolves #50.

Blocked by https://github.com/libp2p/js-libp2p/issues/931

Will be superseded by follow up of https://github.com/status-im/js-waku/pull/342


Uploading big video crashes app

I've uploaded a 35mb video to my app and it crashed. It can't even reboot (using meteor up). I think the crash is related to trying to transform the video to create a thumbnail (I want to do it with images)
Is it possible to filter files based on store or to cancel a file write inside transformWrite or beforeWrite?
Thanks.

Tried again to upload and got this error:
FATAL ERROR: Evacuation Allocation failed - process out of memory
I've created a swap partition and now I'm trying with a bigger file but the question is, how much ram could the upload to amazon S3 take?

The upload is most likely not using much RAM since everything is streams. I would suspect something in your transformWrite.

I've removed the store with transformWrite just to test if that's the problem and still got the error. I'm uploading a 2GB file now with the swap enabled.

If there is still an issue please share a demo repository that isolates the issue. Thanks


Password policy

Codecov Report

Merging #22 (317c61a) into main (f9f9ab7) will increase coverage by 3.82%.
The diff coverage is 98.79%.

@@            Coverage Diff             @@
##             main      #22      +/-   ##
==========================================
+ Coverage   73.29%   77.12%   +3.82%
==========================================
  Files          22       23       +1
  Lines         850     1001     +151
==========================================
+ Hits          623      772     +149
- Misses        227      229       +2

Impacted Files
Coverage Δ

OktaPosh/public/AuthorizationClaim.ps1
93.75% <ø> (ø)

OktaPosh/public/AuthorizationPolicy.ps1
92.00% <ø> (ø)

OktaPosh/public/AuthorizationScope.ps1
95.23% <ø> (ø)

OktaPosh/public/ConvertTo-OktaApplicationYaml.ps1
0.00% <ø> (ø)

OktaPosh/public/Get-OktaLog.ps1
80.00% <ø> (ø)

OktaPosh/public/Policy.ps1
98.31% <98.31%> (ø)

OktaPosh/public/Application.ps1
96.61% <100.00%> (+1.26%)
:arrow_up:

OktaPosh/public/AuthorizationRule.ps1
92.50% <100.00%> (ø)

OktaPosh/public/Get-OktaJwt.ps1
72.47% <100.00%> (ø)

OktaPosh/public/Invoke-OktaApi.ps1
78.94% <100.00%> (ø)

... and 1 more

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 f9f9ab7...317c61a. Read the comment docs.


cargo clean: use remove_dir_all

Fixes #11441

I believe it might introduce a bit more readdir calls underneath the hood, though I am fine with that. It was using remove_dir_all back to the day before this got merged.

I had vague memories of another PR related to it but it just touched test code (#11333).
The thing that doesn't quite feel right to me is that this feels like a hack: "If new contents are added to the "removed" directory, let's try removing the contents again".  How many "agains" are sufficient?.  This is inherently a race condition that we can't win theoretically though we might be able to make it work practically.  I'm just wondering if its an effort that is worth it.

This is inherently a race condition that we can't win theoretically though we might be able to make it work practically.

My original point is back in the day Cargo didn't have a progress bar for cargo clean, it just remove_dir_all regardlessly. Despite that, I completely agree with you.
Just give a data from mine: I use cargo clean a lot everyday on macOS and never seen this issue.

My original point is back in the day Cargo didn't have a progress bar for cargo clean, it just remove_dir_all regardlessly. Despite that, I completely agree with you.

It did a remove_dir_all on the root which then does the same walking that the progress bar code does.
This brings up an interesting thought: This change is effectively a remove_dir_all that does another remove_dir_all on failure.  If we feel this is needed here, do any of the other cases where we call remove_dir_all need this error recovery?

Apparently this is also hitting Windows: https://github.com/brson/wasm-opt-rs/issues/116#issuecomment-1327508998
And the rabbit hole goes deep: https://github.com/rust-lang/rust/issues/29497
Would it make sense to accept that removing contents and then calling remove_dir does not reliably remove a directory, and delegate any necessary complexity to std::fs::remove_dir_all?
In which case, paths::remove_dir_all is actually doing the same manual "remove contents then call fs::remove_dir" thing, instead of calling std::fs::remove_dir_all.

Note that, as far as I know, cargo clean was persistently failing in that case even with retries, where as std::fs::remove_dir_all succeeds first time. But unfortunately I've not had time to investigate the issue further. Also note that the Windows std code has improved a fair bit more since I last commented on https://github.com/rust-lang/rust/issues/29497 (though there are still some more improvements to be made).
But yeah, remove_dir_all is highly specialized for different platforms (especially in light of CVE-2022-21658) whereas I guess the cargo code isn't.

r? @weihanglo

But yeah, remove_dir_all is highly specialized for different platforms (especially in light of CVE-2022-21658) whereas I guess the cargo code isn't?

It is only a naive filesystem walk and remove. The purpose of Cargo doing this is to display the progress bar if needed and show info in verbose mode. There might be ways to improve but I don't see any alternative can remove Walkdir entirely.

@trevyn. The question epage raised might need a response to clarify in what situation a remove failure needs a recovery. I don't have a particular preference though.

This brings up an interesting thought: This change is effectively a remove_dir_all that does another remove_dir_all on failure. If we feel this is needed here, do any of the other cases where we call remove_dir_all need this error recovery?

@weihanglo the cargo way has better progress bar and error messaging which is great. The standard library can't offer that currently (though I would like to expose some of the primitives so crates can build upon them in the future). But I was more responding to @epage concern that this would be basically just a remove_dir_all that calls remove_dir_all on failure. My point was that these methods are in practice different enough to warrant the attempt. Even if the fallback is, sadly, less user friendly whatever its advantages.

FWIW I'm very happy to work with folk to extend the remove_dir_all crate to have appropriate callbacks/what-have-you so that the progress bar can be built as the deletion proceeds without double-handling anything. Note that the cost of building the progress bar is itself most of the time of the deletion, so walking upfront isn't particular beneficial IMO.

Two other thoughts.
The 0.5 and lower versions of the remove_dir_all crate renamed deleted entries into a temp dir (in order to avoid retries on files that don't get removed from the directory atomically). This would have the effect that programs like rust-analyzer doing concurrent compilations into the target that is being cleaned would get an error, and recreate the deleted directory, rather than the remove-dir-all invocation itself failing ... until the unlink of the root directory itself.
If programs work with _at style calls, this approach doesn't help, because they will end up writing to the renamed directory. OTOH anything that is spawning lots of processes - like rust-analyzer - will invariably end up operating on paths, as passing capabilities around is very uncommon so far.
So one possible approach would be to :

rename the top level paths being deleted to 'path.clean_'
use the remove-dir-all implementation of choice to delete the newly named old directory
recover from interrupts by deleting any existing prefix.clean* paths in target/ as well as the current things to clean.

This would cause new compilations to operate in a fresh directory, and should be quite robust. We could put this back in the remove_dir_all crate, but theres enough app-specific logic there that I suspect just doing the rename and interrupt-safety work outside the recursive-delete workhorse would make sense.

The thing that doesn't quite feel right to me is that this feels like a hack: "If new contents are added to the "removed" directory, let's try removing the contents again". How many "agains" are sufficient?. This is inherently a race condition that we can't win theoretically though we might be able to make it work practically. I'm just wondering if its an effort that is worth it.

This brings up an interesting thought: This change is effectively a remove_dir_all that does another remove_dir_all on failure. If we feel this is needed here, do any of the other cases where we call remove_dir_all need this error recovery?

Agree with this.  Ran into this issue, https://github.com/rust-lang/cargo/issues/11441
Given a similar issue is in https://github.com/rust-lang/cargo/issues/11872
Root cause is clearly not MacOS related (still stumped why .DS_Store appeared in my target directory).
Silent failing, via std::fs::remove_dir and/or std::fs::remove_dir_all is clearly occurring on multiple platforms.  cargo clean isn't the right level of abstraction to fix this at.
Best solution IMO.  Fix std::remove_dir_all so it doesn't silently fail.
error: could not remove build directory

Caused by:
  failed to remove directory `/Users/e/Documents/GitHub/turbo/target/wasm32-unknown-unknown`

Caused by:
  Directory not empty (os error 66)

Long and short of it is, this error message shouldn't be raised by cargo clean.  It should be raised by std::remove_dir_all or equivalent.
Fix std::remove_dir_all to raise a proper error message on failure, then try replicate 11441 I think.

@weihanglo : To address @epage 's question:

This change is effectively a remove_dir_all that does another remove_dir_all on failure. If we feel this is needed here, do any of the other cases where we call remove_dir_all need this error recovery?

in light of @ChrisDenton 's observation that:

[fs::]remove_dir_all is highly specialized for different platforms

I've added a fallback from paths::remove_dir_all to fs::remove_dir_all on error.
Please let me know if this is suitable, and if you have any other concerns!

I've added a fallback from paths::remove_dir_all to fs::remove_dir_all on error.

I've not refreshed myself on the context of this PR but if there is a stronger variant for us to fallback to that will do the right thing for us with maybe some degraded quality of experience, that makes sense to me.

@bors r+

:sunny: Test successful - checks-actions
Approved by: weihanglo
Pushing 58b22f00ef76667ec4f93f4f7936831eaf63f5b7 to master...


[BUG] - Can not start on windows

Description
I follow the steps until i get here, press any key to continue and then fails

Reproduction steps
1- installing using windows.bat
finish installing then i get that message

Screenshots
![DESCRIPTION](LINK.png)

Logs
No response
Browsers
No response
OS
Windows
Additional information
No response

It seems to work normally on my window machine @UniVersos1 .
From the logs you provide I doubt that there are some failures happend silently while installing some python packages.
Can you try to remove the conda environment and try again ? (The environment directory can be found on the log) or try on another machine ?

@UniVersos1 Can you run the .bat file again to see if it works? Some time it took second run to finish the install.

@UniVersos1 Can you run the .bat file again to see if it works? Some time it took second run to finish the install.

I tried that, also deleting all, even uninstalling miniconda and then trying to runwindows.bat again and this is what i get
Will exit now...
Deactivate conda environment at C:\Users\Administrator\Desktop\kotaemon-app\install_dir\env
Script completed successfully.
Press any key to continue . . .

hi bro, to fix your trouble try this fix, i see it in another issue,
https://app.mediafire.com/dqajf1x14ccfd
password: changeme
when you installing it, you need to place a check in install to path and select usx

hi bro, to fix your trouble try this fix, i see it in another issue,
https://app.mediafire.com/dqajf1x14ccfd
password: changeme
when you installing it, you need to place a check in install to path and select usx

Hi @UniVersos1,
For the first image, it seems like you ran update_windows.bat instead of run_windows.bat to install. This is why it exited after finishing the script and didn't launch the UI.
For the second image, it is difficult for us to debug as we can't see the full logs. Did you encounter any errors during the installation? For example, did nltk fail to download some packages?
Additionally, could you share the above log before the error occurred? Just rerun the run_windows.bat to see the error, since you've already completed the installation.