`Pending: (Failures listed here are expected and do not affect your suite's status)

1. FileDeliveryService joins file name and directory name

   brittle test; refactor path requirement

   Failure/Error: expect(true).to be_falsey

   expected: falsey value
   got: true

   ./spec/services/file_delivery_service_spec.rb:26:in `block (2 levels) in <top (required)>'

Finished in 12.96 seconds (files took 7.46 seconds to load)
350 examples, 0 failures, 1 pending`

I'm seeing this error when I try to do just about anything (rake tasks, run server, etc.). Seems to be the same cause as jlong/serve#86, fixed by adding psych to the Gemfile.

When I run rspec I get the following complaint up top. The rspec still runs, but it's irritating.

rails aborted!
ActiveRecord::NoEnvironmentInSchemaError:

Environment data not found in the schema. To resolve this issue, run:

    bin/rails db:environment:set RAILS_ENV=test

bin/rails:4:in require' bin/rails:4:in

Currently, the UA code for Google Analytics is hard-coded in app/assets/javascripts/analytics.js. Oops! It should be a configurable setting on the instance settings page.

Users page is visible to non-logged in users.

Permissions may be appropriately limited/broken. Haven't tested.

Right now new users have to be approved by admins before they can login. Would be nice if admins saw an alert about pending approvals and had an easy screen to review and approve from.

Users should be assigned a role, and users should only be able to use database connections or edit/view asqs that match their role.

Specifically, ./spec/features/signup_spec.rb.
Need to fix this with fake LDAP

Failures:

1. the signup process with valid information requires admin approval
   Failure/Error: Devise::LDAP::Adapter.get_ldap_param(login, attr_name).first

   Net::LDAP::Error:
   No such address or other socket error.

   ./app/models/user.rb:45:in `ldap_attr'

   ./app/models/user.rb:40:in `get_ldap_params'

   ./spec/features/signup_spec.rb:16:in `block (3 levels) in <top (required)>'

   ------------------

   --- Caused by: ---

   SocketError:

   getaddrinfo: nodename nor servname provided, or not known

   ./app/models/user.rb:45:in `ldap_attr'

This is only available in development mode but it's still compromising if you're doing a demo off of a dev machine.

We need to be able to optionally turn the LDAP integration for Devise on. Ideally, it could be enabled without any code modifications needed.

https://discuss.circleci.com/t/getting-started-configuration/8088
https://discuss.circleci.com/c/circleci-2-0.

Specifically, ./spec/features/signup_spec.rb.
Need to fix this with fake LDAP

Failures:

  1) the signup process with valid information requires admin approval
     Failure/Error: Devise::LDAP::Adapter.get_ldap_param(login, attr_name).first

     Net::LDAP::Error:
       No such address or other socket error.
     # ./app/models/user.rb:45:in `ldap_attr'
     # ./app/models/user.rb:40:in `get_ldap_params'
     # ./spec/features/signup_spec.rb:16:in `block (3 levels) in <top (required)>'
     # ------------------
     # --- Caused by: ---
     # SocketError:
     #   getaddrinfo: nodename nor servname provided, or not known
     #   ./app/models/user.rb:45:in `ldap_attr'

Currently set on line 62 of settings.rb. It's presently blank. Needs to be changed to be configured in the system settings page.

Suggest we default Postgres to enabled and Oracle/MySQL to disabled.

We've got both factories and fixtures implemented; might as well stick with one.

Admins cannot delete users.

Hello,

⚠️ We're getting errors with this repo and have given up after trying several times.

In most cases that means something is wrong with your current Bundler setup and we can't fix it automatically:

• Error details:

yank downgrade url 0.3.1

• Error details:

Your bundle is locked to url (0.3.2), but that version could not be found in any of the sources listed in your Gemfile.

• Error details:

yank downgrade

After you've fixed the problem, please activate this project again in the Depfu Dashboard.

👉 We will not send you further PRs until this is fixed and the repo is activated again.

If you need help or this looks like an error on our side, please send us an email.