Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

modified logic so we can preserve the image EXIF data if sidecar fails #597

Merged

Conversation

alex-phillips
Copy link
Contributor

No description provided.

…ecar extraction fails and throws an exception
Copy link
Member

@ildyria ildyria left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me, but untested.

@alex-phillips
Copy link
Contributor Author

Hard to tell why this failed on some. Do you guys have any more information?

@d7415
Copy link
Contributor

d7415 commented May 24, 2020

Hard to tell why this failed on some. Do you guys have any more information?

Looks like it's getting 500 codes back from 3 of the the tests.

There were 3 failures:

1) Tests\Feature\PhotosTest::testUpload

Expected status code 200 but received 500.

Failed asserting that 200 is identical to 500.

/home/travis/build/LycheeOrg/Lychee/vendor/laravel/framework/src/Illuminate/Testing/TestResponse.php:185

/home/travis/build/LycheeOrg/Lychee/tests/Feature/Lib/PhotosUnitTest.php:26

/home/travis/build/LycheeOrg/Lychee/tests/Feature/PhotosTest.php:37

2) Tests\Feature\PhotosTest::test_upload_2

Expected status code 200 but received 500.

Failed asserting that 200 is identical to 500.

/home/travis/build/LycheeOrg/Lychee/vendor/laravel/framework/src/Illuminate/Testing/TestResponse.php:185

/home/travis/build/LycheeOrg/Lychee/tests/Feature/Lib/PhotosUnitTest.php:26

/home/travis/build/LycheeOrg/Lychee/tests/Feature/PhotosTest.php:37

/home/travis/build/LycheeOrg/Lychee/tests/Feature/PhotosTest.php:201

3) Tests\Feature\RSSTest::testRSS_1

Expected status code 200 but received 500.

Failed asserting that 200 is identical to 500.

/home/travis/build/LycheeOrg/Lychee/vendor/laravel/framework/src/Illuminate/Testing/TestResponse.php:185

/home/travis/build/LycheeOrg/Lychee/tests/Feature/Lib/PhotosUnitTest.php:26

/home/travis/build/LycheeOrg/Lychee/tests/Feature/RSSTest.php:60

@alex-phillips
Copy link
Contributor Author

Is there a way to run these tests locally so I could see the actual 500 error? It looks like the test script is checking for a Travis environment.

@ildyria
Copy link
Member

ildyria commented May 24, 2020

you can do make test locally if you did composer install (thus without the --no-dev).
If you add $response->dump() before the problematic assert to see what the response look like.

If you have APP_DEBUG=true you will see the error content.

@codecov-commenter
Copy link

Codecov Report

Merging #597 into master will decrease coverage by 0.19%.
The diff coverage is 27.27%.

@alex-phillips
Copy link
Contributor Author

@tmp-hallenser Hopefully this new logic addresses what you were talking about by it not falling back to the proper metadata. Let me know what you think!

@sonarcloud
Copy link

sonarcloud bot commented May 24, 2020

Kudos, SonarCloud Quality Gate passed!

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities (and Security Hotspot 0 Security Hotspots to review)
Code Smell A 0 Code Smells

No Coverage information No Coverage information
2.5% 2.5% Duplication

@tmp-hallenser tmp-hallenser merged commit 32c87f8 into LycheeOrg:master May 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants