-
Notifications
You must be signed in to change notification settings - Fork 4
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
Rails debugging for Manifold #4212
Comments
While investigating this with @carolyncole and @kayiwa, it was discovered that the client was implemented using the Server-Side React framework along with Redux. Redux Actions utilize the Fetch API in order to request JSON data from the API endpoints, however, the URL for these endpoints is forced over the HTTP (rather than tunneled over TLS using HTTPS). This is due to the following Chef template: Manually editing this permits one to ensure that the https://github.com/ManifoldScholar/manifold/blob/master/client/src/config/services/index.js#L15 Without adjusting this, setting the Manifold variable |
Using a fork under my personal account (https://github.com/jrgriffiniii/manifold), I have made progress with the following pull requests:
These support Ruby 3.0.5 releases and integrate Lando for testing. |
Unfortunately, attempting to execute the [...]
An error occurred while loading ./spec/services/search/query_builder_spec.rb.
Failure/Error: raise FormattedAttributes::AlreadyDefinedError, "Already defined #{definition.path.inspect}" unless @definitions.add?(definition)
FormattedAttributes::AlreadyDefinedError:
Already defined "series_title"
# ./app/services/formatted_attributes/configuration.rb:112:in `add!'
# ./app/services/formatted_attributes/configuration.rb:28:in `define!'
# ./app/models/concerns/has_formatted_attributes.rb:66:in `has_formatted_attribute' This seems to be related to the following area of the codebase: An error occurred while loading ./spec/services/search/query_builder_spec.rb.
Failure/Error: mapping.fetch(needle, &block)
KeyError:
key not found: ReadingGroupProject(id: uuid, reading_group_id: uuid, project_...
Did you mean? "reading_group"
# ./app/services/concerns/multi_keyable.rb:153:in `block in fetch'
# ./app/services/concerns/multi_keyable.rb:152:in `fetch'
# ./app/models/concerns/collection_entry.rb:48:in `collector_definition'
# ./app/models/concerns/collection_entry.rb:54:in `collectable_definition'
# ./app/models/concerns/collection_entry.rb:27:in `collectable_associations'
# ./app/models/concerns/reading_group_entry.rb:8:in `block in <module:ReadingGroupEntry>' |
Until the new release of Manifold is completed (currently ManifoldScholar/manifold#3605 is blocking this), it is been decided that progress on this should be deprioritized. |
We are not going to be running manifold ourselves, so we are closing this ticket. |
We are consistently getting a 503 error when following the out-of-the-box installation instructions for Manifold. Manifold is an omnibus solution bundle, meaning it runs its own services including nginx, sidekiq, Rails, cable, logrotate, and others. The error is happening before manifold even reaches any of PUL's own networking tools or infrastructure.
Determine which service(s) cannot communicate with other services within the solution bundle and troubleshoot for installation.
Installed by ansible and then updated with omnibus installation with a run book
The text was updated successfully, but these errors were encountered: