Matt Chung

icon indicating a website link http://blog.mattchung.me icon indicating an email [email protected]

icon company Crossbill icon location Seattle, WA icon location Founder and CEO of Crossbill. Ex-AWS (Route53 and EC2 Networking). Computer scientist, musician, writer, and proud father.

Results 10 comments of Matt Chung

Fix flake8-docstrings failures

Taking a look at this

Token example does not work

Hey @haizaar , what version are you running? I'm going to try and reproduce.

Token example does not work

Thanks @haizaar for reporting this. I'm able to reproduce the issue: ``` python File "/Users/mattchung/Development/github3.py/github3/decorators.py", line 61, in auth_wrapper raise error_for(r) github3.exceptions.AuthenticationFailed: 401 Requires username/password authentication ``` It is possible,...

Updated documentation for cloud_files.md

I'm reviewing why Travis CI however I'm not sure how documentation could cause the tests to fail.

Chapter Assignments

Chapter 5

Cloudfiles sync_folder_to_container() does not remove non existent source files

Cancelled first pull request since it was destined for "master" branch instead of "working"

AppId mismatch failure in preview build of backend used across apps

We are running into the same exact issue and have provided build logs in AWS support case ID: 173089142200287 Like others, we have temporarily pinned the Amplify CLI Version to...

AppId mismatch failure in preview build of backend used across apps

For anybody else who is afflicted with this issue, providing a little update from our case that we cut with AWS: > ... They have picked the issue and are...

AppId mismatch failure in preview build of backend used across apps

So continuing to push the internal ticket and there is a fix (see below) that just got merged in. Essentially, once it's (i.e. 12.13.x) rolled out, you will be able...

AppId mismatch failure in preview build of backend used across apps

I am confirming that the issue is now fixed in 12.13.1. Last night, I went ahead with the following two changes: 1. Reverted pinning 12.12.6 and resetting the AWS Amplify...