Tuesday, September 4, 2018
You've confirmed this succeeds when you perform this same operation
manually? I would wonder if Selenium is somehow generating two click
events, but that's a WAG.
I have tried it manually and It works as it is supposed to ( the form is submitted currently to database).manually? I would wonder if Selenium is somehow generating two click
events, but that's a WAG.
Is there a stack trace you can post?
No, it is the server that raises the error, not the selenium script
Em terça-feira, 4 de setembro de 2018 17:38:06 UTC+1, Hassan Schroeder escreveu:
Em terça-feira, 4 de setembro de 2018 17:38:06 UTC+1, Hassan Schroeder escreveu:
On Tue, Sep 4, 2018 at 8:38 AM, João Bordalo <bordalo...@gmail.com> wrote:
> Problem: When the selenium 'clicks' on the submit button, the server raises
> the following error related to Sqlite:
>
> SQLite3::BusyException: database is locked: commit transaction
You've confirmed this succeeds when you perform this same operation
manually? I would wonder if Selenium is somehow generating two click
events, but that's a WAG.
Is there a stack trace you can post?
--
Hassan Schroeder ------------------------ hassan.s...@gmail.com
twitter: @hassan
Consulting Availability : Silicon Valley or remote
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/8f9b633b-b362-40a4-84dd-05fb61b25bb8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment