Error Message: Could not find jsonapi-parser-0.1.1.beta2 in any of the sources - ruby-on-rails-5

Error showing while I am trying to deploy rails 5 application in AWS server.
Error Message: Could not find jsonapi-parser-0.1.1.beta2 in any of the sources
My local machine is ubuntu and it works perfectly.
Official gemfile page showing 'This version has been yanked, and it is not available for download directly or for other gems that may have depended on it.'
https://rubygems.org/gems/jsonapi/versions/0.1.1.beta5
Now how can I resolve this dependency!

Need to update jsonapi gem:
bundle update jsonapi

Related

Missing config.json stencil CLI

I'm trying to do some work for a client, but cannot get their bigcommerce site running locally. I have installed stencil CLI (v3.1.1) and downloaded the theme from the bigcommerce dashboard (all files). from the root of the theme i ran "stencil init", then "npm i" and "stencil start".
when i run stencil start, it throws an error saying there's no config.json file.
this is the error i get
How do i generate the config.json file?
The only config file I see is config.stencil.json.
I have also tried running "stencil pull" in hopes that it would pull the config, but it throws another error: "not ok -- Error: Could not fetch active theme details for channel 1: Request failed with status code 404"
Stencil-cli version:
3.1.1
Node version:
12
NPM version:
6.14.15
OS:
mac big sur
Stencil 3.1.1 has been deprecated for some time now. I believe the current version is 3.8. As of 4 months ago, anything below 3.5 will not run (https://developer.bigcommerce.com/changelog#publications/required-stencil-cli-version-set-to-3-5-0).
If you don't have a config.json file in your project, you will need to get the one from the client's store. Try downloading their theme again. It should come through.
Edit: It is possibly the case that you need a new API token. Try making a new one for your store. Make sure the following scopes are set:
Themes: Modify
Settings & Information: Modify
Sites & Routes: Read-only (or Modify)
Documentation for creating a new API account: https://support.bigcommerce.com/s/article/Store-API-Accounts#creating

orocommerce install failed you have requested a non-existent parameter "web_backend_prefix"

I done all steps to install orocommerce on azure CentOS and nginx.
So now i got the following error after
$ ./bin/console oro:install --env=prod --timeout=900
"In ParameterBag.php line 102:
You have requested a non-existent parameter "web_backend_prefix".
Have anybody an idea?
How exactly did you get the source code (if GitHub - what repository, tag/branch, if download - what website and version)? Based on the error text it seems like it might be OroPlatform or OroCRM application, not OroCommerce.

Error installing bundle in Mura (Mura newbie)

Just to preface this, I'm a Mura newbie.
I am attempting to create a new site in Mura 6.2 by importing the 'MuraBootstrap3' bundle - https://github.com/blueriver/MuraBootstrap3Bundle .
Once I create the site and import the bundle, I immediately get the following error message:
It appears to be an issue with SQL executing the insert command, but I'm not entirely sure why. Am I missing something in the setup? What am I not doing correctly?
Thanks!
Edit: I should mention that The database has already been setup and my default installation is running just fine.
Guust was correct, however the bundle you're looking for is here:
https://github.com/blueriver/MuraBootstrap3Bundle/blob/6f9e86a15fbd10d4b88b77dd2f5be467ce8f3582/MuraBundle_default_2015_03_30_12_29.zip
The bundle you've downloaded is for Mura 7.
I believe the last version of the bundle for Mura 6.x is the following commit:
https://github.com/blueriver/MuraBootstrap3Bundle/commit/c62e8fcfc8ba25fe1ca1ef186af1898e894a3c8e
This is the file I believe you'll need:
https://github.com/blueriver/MuraBootstrap3Bundle/blob/c62e8fcfc8ba25fe1ca1ef186af1898e894a3c8e/MuraBundle_default_2016_05_03_17_01.zip

osTicket 1.9 LDAP pear issue

I'm following the instructions here: https://github.com/osTicket/core-plugins to install the LDAP plugin for osticket 1.9.2.
I have the download in the correct place however when I run the command:
php make.php hydrate
I get loads of 'could not load...' messages and the main fatal one being:
Problem 1
- The requested package pear-pear/net_ldap2 could not be found in any version, there may be a typo in the package name.
Enabling the plugin within osTicket then works but obvious throws PHP Fatal errors about not finding the ldap files, as you would expect.
Does anyone know how to resolve it?
You need to install the pear package net_ldap2, either via pear or via composer.

Rails 3 in test env won't allow records to save, even with latest sqlite3

I saw this post:
Rails/ActiveRecord/SQLite3: Can't save records in test environment
And after upgrading my sqlite version to the very latest (3.7.17), I am still getting the following error:
ActiveRecord::StatementInvalid: SQLite3::SQLException: near "SAVEPOINT": syntax error: SAVEPOINT active_record_1
Any time I try to create anything at all. If all I do is load my fixtures, everything is fine.
I have confirmed that rails is using the updated sqlite3 version by running "rails db".
In my development environment, I can create objects all day long with no errors (I can even have an object create another object after create).
What is special about my test environment that this is happening? How can I fix it?
Edit:
If I delete my test database, and redo rake:db:create and rake:db:migrate, I still get the same issues.
Doing "rails console test" lets me use the test environment just fine, and I can create objects all day long and see existing fixtures. It's only when I type "rake test:units" that I get the errors... (originally I had errors, but one error was legitimate (I don't know why I wasn't getting it in the development environment, and the adapter error was because apparently you aren't supposed to do "rails console RAILS_ENV="test", so it was looking for an adapter for an envrionment called "RAILS_ENV=test")
Edit: When I type "gem uninstall sqlite3" it uninstalls. When I then type "bundle install" it has a problem reinstalling...working on it now.
/home/jenny/.rvm/rubies/ruby-1.9.3-p0/bin/ruby extconf.rb --with-sqlite3-dir=/usr/local/bin/sqlite3 checking for sqlite3.h... *** extconf.rb failed *** Could not create Makefile due to some reason, probably lack of necessary libraries and/or headers. Check
the mkmf.log file for more details. You may need configuration
options.
If I type "gem install sqlite3" separately, it works just fine, and then "bundle install" it works. However, "rake test:units" has the same errors.
Edit:
When I type "which sqlite3" it prints out "/usr/local/bin/sqlite3"
I wasn't even aware sqlite3 headers were a thing, so I doubt I installed them. I'll try to figure out how to confirm this and see if it helps.
Edit:
I don't see anywhere to download sqlite3 headers on the main site...just source and the precompiled linux binary. There doesn't seem to be a special header in the source, but even if there was, wouldn't it be included in the precompiled binary?
EDIT: link to bundler sqlite3 install error that don't happen when i manually install the gem
http://pastie.org/8063577
EDIT: Not a devise problem. I thought it was, but it turned out I was just creating another object in fixtures, not in the test code.
So, I can create devise User or any other type of object in fixtures all day long, but if I attempt to create one in the unit test, I get the save point error. Same thing for trying to save a fixture in a unit test.
Your problem is most likely related to the fact that you updated your local sqlite but after that you haven't reinstalled your sqlite3 gem.
I'd recommend you follow these steps:
Remove the corresponding line gem 'sqlite3' from your Gemfile
Run bundle install
Run gem uninstall sqlite3
Return the line gem 'sqlite3' to your Gemfile
Run bundle install one more time
If you simply gem uninstall and then bundle install, it will install the same version and dependencies that were recorded in Gemfile.lock. But since you're now using a different and more updated local version, it's safer to allow Bundler to install a new version if needed.