When I run the code it showing Must use import to load ES Module: error message. How can I solve this..?
error code: 'ERR_REQUIRE_ESM'
Now I resolved the issue by downgrading swagger-jsdoc to 6.0.1
Related
Have someone faced any error when trying to integrate DocuSign SDK on Swift iOS application? I have installed the last version of DocuSign (3.0.1) using Cocoapods and it has a dependency of JWT framework (version 3.0.0-beta.11 installed).
I try to run the code but I got this error: No known class method for selector No known class method for selector 'keyFromPemFileWithName:'
It seems there is no method keyFromPemFileWithName inside JWTCryptoSecurity class.
I would appreciate if someone has the answer for this.
I've found 2 ways to solve this issue
1) Force to use an old version of JWS with DocuSign:
pod 'JWT', :git => 'https://github.com/yourkarma/JWT', :commit => 'c4232478d3190a163f76b05c38ec84625e3d785a'
pod 'DocuSignESign'
2) Edit DocuSign framework in order to have a method like that (without passing the file name but the file URL)
I am using sucker_punch gem to send the email in my rails app in the background.It used to work fine, but then I suddenly got this error:
undefined method `async' for #<ActiveJob::QueueAdapters::SuckerPunchAdapter::JobWrapper:0x007f892c6c31a0>
Below is the screenshot of the full error:
I am using sucker_punch version 2.0.1 right now. I have tried to downgrade it and using sucker_punch version 1.6.0 instead, but the error persist.
Any help? Thanks!
Okay I have finally figured it out. In my sucker_punch.rb file, I need to include this:
# config/initializers/sucker_punch.rb
require 'sucker_punch/async_syntax'
This is required for those who are using Sucker Punch version 2.0.0+ with Rails < 5.0.0 as explained here
They've actually changed async syntax.
With newer versions of sucker_punch, you should call async like so:
Model.perform_async
It's mentioned under the Backwards Compatibility heading here
https://github.com/brandonhilkert/sucker_punch
Previously I used to load opal.js, opal-parser.js, opal-jquery.js(version 0.3x). Now I added gem opal and opal-rails(version 0.6.2) instead of js files.
Previously my whole test suit(capybara + rspec) used to passed but after update capybara specs start failing. Sometime it behave wired(i.e passed in firefox but fail in chrome).
One of the example error is
unknown error: Runtime.evaluate threw exception: RangeError: Maximum call stack size exceeded
It is said that there is compatibility issue with opal and rspec.
I will be grateful if someone help me fixing this issue.
I thinks its a known bug in the chrome webdriver:
https://code.google.com/p/chromedriver/issues/detail?id=683
I'm using torquebox 2.0 beta (i.e. jruby on rails). Everything was working fine until I installed the Citier gem. Once I installed the gem, I began to get the following error:
superclass mismatch for class SQLiteAdapter
the full error is included in this gist: Full Trace of Error Message
Does anyone have any suggestions for a workaround or a fix for this error.
Thanks in advance for your help.
'citier' is assuming a certain class hierarchy for SQLiteAdapter and PostgreSQLadapter, and that is clashing with JDBC adapters'. I don't know how to fix it; it might be as simple as removing the inheritance specification from the offending line 17, but maybe not. Either way, you should contact citier's author.
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.