Error 500 internal server error when trying to print data table #402
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Reconcile changes from release candidate v1.7.3
using `.try(:first)` resolves by returning `nil` without failing if the requested element does not have the method `.first`, i.e. is empty
Adjusted template to include google analytics in print requests as well as carried over other improvements in header elements
Minor tweaks to the Makefile to remove duplicate variables (`SHORTNAME`) as well as introducing new targets for `check` and `local` for streamlined development tasks
from v1.7.3 ~> v1.7.4
removed `:unit` from test target as that doesn't exist
Organised specific gems into test group as well as locked gem versions to the current ruby version where applicable
Removed incorrect instructions, re-grouped build commands into the assets target, applied the same target where previously invoking manually; finally, updated the test target to use rake test and removed the system test command as it's not required at this moment
set `config.cache_classes=false` to allow Spring to reload assets
set `ENV['API_SERVICE_URL']` to `ENV.fetch('API_SERVICE_URL', nil)` as Rubocop continued to complain
removes auth target, as well as echos for tracking, alongside reassigning NAME instead of REPO where applicable
changes branch name from `dev-infrastructure` to `dev` in response to branch cleanup
…-server-error-fix Error 500 internal server error when trying to print data table
refactored v1.7.4 tag date to reflect latest changes
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR resolves the error reported in ticket #396 by updating the print presenter to use
.try(:first)which resolves by returningnilwithout failing if the requested element does not have the method.first, i.e. is empty or nilAdditional Changes:
SHORTNAME) as well as introducing new targets forcheckandlocalfor streamlined development tasks, alongside removing incorrect and erroneous commands where applicablebin/s-queryfile which is used to resolve the fallback location for the Apache Jena Fuseki s-query file added in this commitdev-infrastructurebranch name todevfollowing branch cleanup