commit psql 16 changes to schema #1031
cooperkaAnnotations
10 errors and 14 warnings
|
Tests:
spec/system/forms/form/form_status_and_version_spec.rb#L13
form status and version display and changes changing status via index page
Failure/Error: <%= javascript_pack_tag("application") %>
ActionView::Template::Error:
Shakapacker can't find application.js in /home/runner/work/nemo/nemo/public/packs-test/manifest.json. Possible causes:
1. You forgot to install javascript packages or are running an incompatible javascript runtime version
2. Your app has code with a non-standard extension (like a `.jsx` file) but the extension is not in the `extensions` config in `config/shakapacker.yml`
3. You have set compile: false (see `config/shakapacker.yml`) for this environment
(unless you are using the `bin/shakapacker -w` or the `bin/shakapacker-dev-server`, in which case maybe you aren't running the dev server in the background?)
4. webpack has not yet FINISHED running to reflect updates.
5. You have misconfigured Shakapacker's `config/shakapacker.yml` file.
6. Your webpack configuration is not creating a manifest.
Your manifest contains:
{}
[Screenshot Image]: /home/runner/work/nemo/nemo/tmp/capybara/failures_r_spec_example_groups_form_status_and_version_display_and_changes_changing_status_via_index_page_884.png
|
|
Tests:
spec/system/forms/form/form_status_and_version_spec.rb#L117
form status and version display and changes changing version when live should enqueue the render form xml job for odk
Failure/Error: <%= javascript_pack_tag("application") %>
ActionView::Template::Error:
Shakapacker can't find application.js in /home/runner/work/nemo/nemo/public/packs-test/manifest.json. Possible causes:
1. You forgot to install javascript packages or are running an incompatible javascript runtime version
2. Your app has code with a non-standard extension (like a `.jsx` file) but the extension is not in the `extensions` config in `config/shakapacker.yml`
3. You have set compile: false (see `config/shakapacker.yml`) for this environment
(unless you are using the `bin/shakapacker -w` or the `bin/shakapacker-dev-server`, in which case maybe you aren't running the dev server in the background?)
4. webpack has not yet FINISHED running to reflect updates.
5. You have misconfigured Shakapacker's `config/shakapacker.yml` file.
6. Your webpack configuration is not creating a manifest.
Your manifest contains:
{}
[Screenshot Image]: /home/runner/work/nemo/nemo/tmp/capybara/failures_r_spec_example_groups_form_status_and_version_display_and_changes_changing_version_when_live_should_enqueue_the_render_form_xml_job_for_odk_54.png
|
|
Tests:
spec/system/forms/form/form_status_and_version_spec.rb#L126
form status and version display and changes changing the name of the form when live should enqueue
Failure/Error: <%= javascript_pack_tag("application") %>
ActionView::Template::Error:
Shakapacker can't find application.js in /home/runner/work/nemo/nemo/public/packs-test/manifest.json. Possible causes:
1. You forgot to install javascript packages or are running an incompatible javascript runtime version
2. Your app has code with a non-standard extension (like a `.jsx` file) but the extension is not in the `extensions` config in `config/shakapacker.yml`
3. You have set compile: false (see `config/shakapacker.yml`) for this environment
(unless you are using the `bin/shakapacker -w` or the `bin/shakapacker-dev-server`, in which case maybe you aren't running the dev server in the background?)
4. webpack has not yet FINISHED running to reflect updates.
5. You have misconfigured Shakapacker's `config/shakapacker.yml` file.
6. Your webpack configuration is not creating a manifest.
Your manifest contains:
{}
[Screenshot Image]: /home/runner/work/nemo/nemo/tmp/capybara/failures_r_spec_example_groups_form_status_and_version_display_and_changes_changing_the_name_of_the_form_when_live_should_enqueue_167.png
|
|
Tests:
spec/system/forms/form/form_status_and_version_spec.rb#L135
form status and version display and changes changing the name of the form when paused should not enqueue
Failure/Error: <%= javascript_pack_tag("application") %>
ActionView::Template::Error:
Shakapacker can't find application.js in /home/runner/work/nemo/nemo/public/packs-test/manifest.json. Possible causes:
1. You forgot to install javascript packages or are running an incompatible javascript runtime version
2. Your app has code with a non-standard extension (like a `.jsx` file) but the extension is not in the `extensions` config in `config/shakapacker.yml`
3. You have set compile: false (see `config/shakapacker.yml`) for this environment
(unless you are using the `bin/shakapacker -w` or the `bin/shakapacker-dev-server`, in which case maybe you aren't running the dev server in the background?)
4. webpack has not yet FINISHED running to reflect updates.
5. You have misconfigured Shakapacker's `config/shakapacker.yml` file.
6. Your webpack configuration is not creating a manifest.
Your manifest contains:
{}
[Screenshot Image]: /home/runner/work/nemo/nemo/tmp/capybara/failures_r_spec_example_groups_form_status_and_version_display_and_changes_changing_the_name_of_the_form_when_paused_should_not_enqueue_460.png
|
|
Tests:
spec/system/forms/form/form_status_and_version_spec.rb#L145
form status and version display and changes live, pause, increment version, go live should enqueue the job
Failure/Error: <%= javascript_pack_tag("application") %>
ActionView::Template::Error:
Shakapacker can't find application.js in /home/runner/work/nemo/nemo/public/packs-test/manifest.json. Possible causes:
1. You forgot to install javascript packages or are running an incompatible javascript runtime version
2. Your app has code with a non-standard extension (like a `.jsx` file) but the extension is not in the `extensions` config in `config/shakapacker.yml`
3. You have set compile: false (see `config/shakapacker.yml`) for this environment
(unless you are using the `bin/shakapacker -w` or the `bin/shakapacker-dev-server`, in which case maybe you aren't running the dev server in the background?)
4. webpack has not yet FINISHED running to reflect updates.
5. You have misconfigured Shakapacker's `config/shakapacker.yml` file.
6. Your webpack configuration is not creating a manifest.
Your manifest contains:
{}
[Screenshot Image]: /home/runner/work/nemo/nemo/tmp/capybara/failures_r_spec_example_groups_form_status_and_version_display_and_changes_live__pause__increment_version__go_live_should_enqueue_the_job_33.png
|
|
Tests:
spec/system/forms/form/form_status_and_version_spec.rb#L24
form status and version display and changes changing status and version via edit page
Failure/Error: <%= javascript_pack_tag("application") %>
ActionView::Template::Error:
Shakapacker can't find application.js in /home/runner/work/nemo/nemo/public/packs-test/manifest.json. Possible causes:
1. You forgot to install javascript packages or are running an incompatible javascript runtime version
2. Your app has code with a non-standard extension (like a `.jsx` file) but the extension is not in the `extensions` config in `config/shakapacker.yml`
3. You have set compile: false (see `config/shakapacker.yml`) for this environment
(unless you are using the `bin/shakapacker -w` or the `bin/shakapacker-dev-server`, in which case maybe you aren't running the dev server in the background?)
4. webpack has not yet FINISHED running to reflect updates.
5. You have misconfigured Shakapacker's `config/shakapacker.yml` file.
6. Your webpack configuration is not creating a manifest.
Your manifest contains:
{}
[Screenshot Image]: /home/runner/work/nemo/nemo/tmp/capybara/failures_r_spec_example_groups_form_status_and_version_display_and_changes_changing_status_and_version_via_edit_page_672.png
|
|
Tests:
spec/system/responses/display_logic_spec.rb#L257
response form display logic display_if logic condition on qing group should hide group members until conditions met
Failure/Error: <%= javascript_pack_tag("application") %>
ActionView::Template::Error:
Shakapacker can't find application.js in /home/runner/work/nemo/nemo/public/packs-test/manifest.json. Possible causes:
1. You forgot to install javascript packages or are running an incompatible javascript runtime version
2. Your app has code with a non-standard extension (like a `.jsx` file) but the extension is not in the `extensions` config in `config/shakapacker.yml`
3. You have set compile: false (see `config/shakapacker.yml`) for this environment
(unless you are using the `bin/shakapacker -w` or the `bin/shakapacker-dev-server`, in which case maybe you aren't running the dev server in the background?)
4. webpack has not yet FINISHED running to reflect updates.
5. You have misconfigured Shakapacker's `config/shakapacker.yml` file.
6. Your webpack configuration is not creating a manifest.
Your manifest contains:
{}
[Screenshot Image]: /home/runner/work/nemo/nemo/tmp/capybara/failures_r_spec_example_groups_response_form_display_logic_display_if_logic_condition_on_qing_group_should_hide_group_members_until_conditions_met_536.png
|
|
Tests:
spec/system/responses/display_logic_spec.rb#L279
response form display logic display_if logic condition on qing all_met conditions should all need to be met
Failure/Error: <%= javascript_pack_tag("application") %>
ActionView::Template::Error:
Shakapacker can't find application.js in /home/runner/work/nemo/nemo/public/packs-test/manifest.json. Possible causes:
1. You forgot to install javascript packages or are running an incompatible javascript runtime version
2. Your app has code with a non-standard extension (like a `.jsx` file) but the extension is not in the `extensions` config in `config/shakapacker.yml`
3. You have set compile: false (see `config/shakapacker.yml`) for this environment
(unless you are using the `bin/shakapacker -w` or the `bin/shakapacker-dev-server`, in which case maybe you aren't running the dev server in the background?)
4. webpack has not yet FINISHED running to reflect updates.
5. You have misconfigured Shakapacker's `config/shakapacker.yml` file.
6. Your webpack configuration is not creating a manifest.
Your manifest contains:
{}
[Screenshot Image]: /home/runner/work/nemo/nemo/tmp/capybara/failures_r_spec_example_groups_response_form_display_logic_display_if_logic_condition_on_qing_all_met_conditions_should_all_need_to_be_met_172.png
|
|
Tests:
spec/system/responses/display_logic_spec.rb#L300
response form display logic display_if logic condition on qing any_met only one condition should need to be met
Failure/Error: <%= javascript_pack_tag("application") %>
ActionView::Template::Error:
Shakapacker can't find application.js in /home/runner/work/nemo/nemo/public/packs-test/manifest.json. Possible causes:
1. You forgot to install javascript packages or are running an incompatible javascript runtime version
2. Your app has code with a non-standard extension (like a `.jsx` file) but the extension is not in the `extensions` config in `config/shakapacker.yml`
3. You have set compile: false (see `config/shakapacker.yml`) for this environment
(unless you are using the `bin/shakapacker -w` or the `bin/shakapacker-dev-server`, in which case maybe you aren't running the dev server in the background?)
4. webpack has not yet FINISHED running to reflect updates.
5. You have misconfigured Shakapacker's `config/shakapacker.yml` file.
6. Your webpack configuration is not creating a manifest.
Your manifest contains:
{}
[Screenshot Image]: /home/runner/work/nemo/nemo/tmp/capybara/failures_r_spec_example_groups_response_form_display_logic_display_if_logic_condition_on_qing_any_met_only_one_condition_should_need_to_be_met_855.png
|
|
Tests:
spec/system/forms/form_item/skip_logic_form_spec.rb#L35
skip logic form fields admin mode with existing skip rule read-only mode
Failure/Error: <%= javascript_pack_tag("application") %>
ActionView::Template::Error:
Shakapacker can't find application.js in /home/runner/work/nemo/nemo/public/packs-test/manifest.json. Possible causes:
1. You forgot to install javascript packages or are running an incompatible javascript runtime version
2. Your app has code with a non-standard extension (like a `.jsx` file) but the extension is not in the `extensions` config in `config/shakapacker.yml`
3. You have set compile: false (see `config/shakapacker.yml`) for this environment
(unless you are using the `bin/shakapacker -w` or the `bin/shakapacker-dev-server`, in which case maybe you aren't running the dev server in the background?)
4. webpack has not yet FINISHED running to reflect updates.
5. You have misconfigured Shakapacker's `config/shakapacker.yml` file.
6. Your webpack configuration is not creating a manifest.
Your manifest contains:
{}
[Screenshot Image]: /home/runner/work/nemo/nemo/tmp/capybara/failures_r_spec_example_groups_skip_logic_form_fields_admin_mode_with_existing_skip_rule_read_only_mode_254.png
Shared Example Group: "correct behavior" called from ./spec/system/forms/form_item/skip_logic_form_spec.rb:184
|
|
Tests
Your workflow is using a version of actions/cache that is scheduled for deprecation, actions/cache@v2. Please update your workflow to use the latest version of actions/cache to avoid interruptions. Learn more: https://github.blog/changelog/2024-09-16-notice-of-upcoming-deprecations-and-changes-in-github-actions-services/
|
|
Tests
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v2, actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
Tests
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/cache@v2, actions/setup-node@v1, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Tests:
app/javascript/components/Filters/model.js#L132
Unexpected console statement
|
|
Tests:
app/javascript/components/conditions/ConditionSetFormField/ConditionFormField/component.js#L69
Unexpected console statement
|
|
Tests:
app/javascript/components/conditions/ConditionSetFormField/ConditionFormField/component.js#L110
Unexpected console statement
|
|
Tests:
app/javascript/components/conditions/ConditionSetFormField/ConditionFormField/model.js#L146
Unexpected console statement
|
|
Tests:
app/javascript/packs/enketo.js#L43
Unexpected console statement
|
|
Tests:
app/javascript/packs/enketo.js#L57
Unexpected alert
|
|
Tests:
app/javascript/packs/enketo.js#L80
Unexpected console statement
|
|
Tests:
app/javascript/packs/enketo.js#L91
Unexpected alert
|
|
Tests:
app/javascript/packs/enketo.js#L94
Unexpected console statement
|
|
Tests:
spec/system/search/response_search_spec.rb#L84
response search with more complex data search filters submit date searches
Skipped: Temporarily disabled with xscenario
|
|
Tests
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|