i tried to fix this issue but seems my way is not correct. the error is:
Could not find androidx.databinding:viewbinding:7.0.3.
Required by:
project :app
any solution?
Related
I am trying to use RailsAdmin and am getting an Uninitialized Constant TableNameX error. I did indeed misspell TableNameX originally.
I figured that if I went and changed all the mis-spelled spots the problem would resolve itself. It hasn't, so I seem to be missing a spot--but my searches within Eclipse are not turning anything up!
Which folder/folder would RailsAdmin be reading from?
What does your trace look like?
Also have you looked into /config/initializers/rails_admin.rb to see if your TableNameX is there and you simply forgot to change it? :)
P.S: And don't forget to restart the server, initializers only run once at the server bootup.
`':' while scanning a simple key at line 16 column 1(Psych::SyntaxError)
I'm working on a Rails application tutorial and have had the above error come up several times. When I was getting this error it seemed to only be a problem if I used one particular terminal window. I have since restarted the computer and now it is a problem regardless of what I do.
I went to the project on github and copied the information in 'secrets.yml' into my file in case that was the issue but doesn't help. In fact I'm not sure if that is even the file causing the problem because when I shift the code in that file and save it I still get the same error; at those times it points to a line that is now blank in the 'secrets.yml'
Update.
now I am getting this when i run this command
rails generate simple_form:install --foundation
-bash: $: command not found.
only change I did was start the code in 'secrets.yml' lower down, and i added a secret key to my .bash_profile, as it was suggested in tutorial and I had not done it before, and thought that might be the problem.
Update 2
shut down terminal and tied again and getting the original problem "psyche Error" Yes, thank you for your feedback, I too, although not sure why, suspect it is to do with the 'secret' file or could it be changes the tutorial told me to make to my .bash_profile. The instructions were not very clear, wondering if that is where I messed up. If that is so then I would not know how to fix that.
The Psych gem is the wrapper around libyaml and used within Ruby's YAML class, so it's not surprising you think it could be the 'secrets.yml'; a YAML config file. I'd stay the course and find what isn't being formatted correctly.
I run my rspec and most of the test were failed. I got the same error for them, which is:
Failure/Error: Unable to find matching line from backtrace
ActiveRecord::StatementInvalid:
PG::ConnectionBad: PQsocket() can't get socket descriptor: BEGIN
I found a question that is similar to my problem, but there is no answer yet and I also tried the solution from this link, but it didn't make any differences for me. I opened my test console and run some simplest queries and it worked.
There may be a problem with pg: '0.18.1'. I tried reverting to 0.18.0, and I believe the problem has gone away.
I'll open up an issue on the repo after testing a bit more locally.
I added this issue on the pg repo.
EDIT: I was wrong.
What did in fact help though, was installing the spring-commands-rspec gem. I think what it ended up doing for me was caching it in a state where it worked. Although it could also just as easily cache it in a state where it didn't.
I don't know if the issues are linked- but I found that by using the local unix socket file instead of localhost that the issue seemed to go away for the linked question; perhaps it might help you too?
"Rake spec" failing most tests, but "rails s" working fine on Diaspora source
I was getting the same error, and some other errors like PG::UnableToSend: socket not open. Seemed to error at random times. I traced it down and it was actually due to a model having an improper belongs_to association. This might not apply to you but hopefully it helps someone.
I had:
belongs_to :user, class_name: User
When it should have been:
belongs_to :user, class_name: 'User'
Somehow that one line was breaking all of my PG sockets connections.
May not have any bearing on rspec, but throwing this out there just in case. I fought this for weeks and for me it was the way passenger spawns new processes. I just had to add this
# Rails -- prepared statements incompatible with faster spawn methods.
PassengerSpawnMethod conservative
to the \etc\apache2\mods-available\passenger.conf
https://www.phusionpassenger.com/library/indepth/ruby/spawn_methods/
I had installed 'pg', '0.20.0', by downgrading to 0.19.0 it worked for me.
I've found a couple of other related questions but none of the answers are working for me as I'm using a Windows machine to develop.
Everything is configured and setup correctly as far as I know and right now the only problem I'm getting is the following: http://i.imgur.com/v3BLS.png
Seeing that I'm a windows user, I've installed ImageMagick and ran the which identify command to give me the identify path to place in my development.rb:
Paperclip.options[:command_path] = "/c/Program Files/ImageMagick-6.7.1-Q16/identify"
Anyone have an idea why I am getting this error still?
EDIT: Might the fact that my file variable is called photo_1 have anything to do with it? Should I just use photo instead?
I guess the problem is the command path.
Contrary to what you did, it should point to a folder not a precise binary.
Try:
Paperclip.options[:command_path] = "c:\Program Files\ImageMagick-6.7.1-Q16\"
This is the only solution which saved my day after trying all the above and a lot more
Image file is not recognized by the 'identify' command. (heroku)
I am working in Rails 3. If I run my application in IE8, I am getting the following error:
"Internet Explorer has encountered a problem and needs to close. We are sorry for the inconvenience."
I tried few technical solutions but they didn't work.
Afterwards I removed prototype.js and the error was removed. If I include prototype.js again, the error gets displayed again.
Strange! What could be the solution?
give a try to Prototype 1.7RC3, it fixed a problem for me. Maybe it will help you too.