I was updating the version of reagent for 0.6.0 to 0.8.1 and got the error Cannot read property 'call' of undefined. The error is being thrown by the create-class method in reagent.
Tried adding cljs.create-react-class but that didn't work.
For people landing from search:
I encountered this issue, also during a migration from reagent 0.6.0 to 0.8.1, but I doubt this is version specific.
Working with https://github.com/Gonzih/cljs-electron as a base, at some point, I am able to get the app into a strange state and reagent stops loading correctly. One working method that recovers from the strange state and got cljsbuild working again was by deleting everything that was a compilation output, in particular those in .gitignore (target, resources/public/js, etc.). After removing those files and rerunning lein cljsbuild once the application worked again.
Related
I am new to Foundation. I started working on a project using an older version of Foundation (2018-2019) and I can't seem to install the dependencies I need to run the project locally, such as Gulp and Babel, and several others. For example, here is a screenshot of the errors I've been receiving any time I try to install a dependency.
list of warnings and errors :
This is the first large-scale project I've worked on using many more dependencies than I'm used to. I've seen "Python" listed among the errors but have never used it, so I'm not sure if that should be installed as well.
I tried to install a few different dependencies, some needing Admin privilege and others not. I'm not sure what I'm doing wrong.
We recently upgraded an old rails app from rails 3 to 4.2, along with many other gem updates. Now I can't get my rails app to load any pages. We were on JRuby 9.1.0.0 but upgraded to 9.1.8.0. However, I'm hitting the same problem on both versions.
Once we start tomcat with our latest .war, it runs all the way until I see the INFO: Server startup in 1234ms message. I've added some debug statements in my rails environment / initializers files to follow it through and it is hitting each of them. So once I see the startup message from tomcat, I figured it would be okay. However, it immediately spits out the following message quite a few times:
DEBUG: resetting rack response due exception
Every time I load a URL, it also shows that message in my logs.
I see that it's from this jruby-rack class but I have no idea how to debug or troubleshoot this further.
I assume that something in my configuration is causing a problem or that a class/module is somehow short-circuiting it but I'm not sure how to identify which one it is or isolate the issue.
Does anybody know of a way to get some more verbose logs or ways to figure out where the problem is happening?
Happy to post any config/gemfiles etc if it will help.
After receiving some great help from the #jruby IRC channel, they mentioned the error message was missing the specific exception message. I was using the latest version, v1.1.21 so I just made a hack-build that added some logging to identify my problem further. Turns out it was a runtime error because of some missing config.
I made an issue with jruby-rack and a PR which will hopefully make its way into the next release!
I'm using the skeleton-typescript aurelia skeleton-navigation package, when running gulp bundle it gives me an error that says path must be a string but was undefined
TypeError: Path must be a string. Received undefined
at assertPath (path.js:7:11)
at Object.basename (path.js:801:5)
at exports.writeOutputs (C:\Users\joaoe\Desktop\skeleton-navigation\skeleton-typescript\node_modules\systemjs-builder\lib\output.js:137:23)
at C:\Users\joaoe\Desktop\skeleton-navigation\skeleton-typescript\node_modules\systemjs-builder\lib\builder.js:575:14
at tryCatcher (C:\Users\joaoe\Desktop\skeleton-navigation\skeleton-typescript\node_modules\systemjs-builder\node_modules\bluebird\js\release\util.js:16:23)
at Promise._settlePromiseFromHandler (C:\Users\joaoe\Desktop\skeleton-navigation\skeleton-typescript\node_modules\systemjs-builder\node_modules\bluebird\js\release\promise.js:502:31)
All gulp related files can be found here since there are more than one.
Even the cloned package throw that.
I'm running Node 6.0.0 and tested with 5.9.1, on Windows 10.
There is some property that I need set to be that path ? Seems related to Aurelia pre built tasks, from comments could also be an environment problem.
As I tracked it down, the issues seems to be an ugly combination of node-gyp, Windows and node 6
So install all dependencies needed for node-gyp, following your OS steps as seen at official repo. Unfortunately for now if you are running Windows is likely that you need to install Visual Studio. Then run npm install on the repository and see if there is any error, should be no one now. Then try to gulp bundle it should work now. With downgraded node to 5.11 I was able to run again, I did not test with node 6 but feel free to try.
I realized I never updated Polymer since I first installed with Bower, so I ran bower update on my website's project root and it appeared to update fine, with the exception that it was finding two different versions, 0.3.6 and 0.5.1 I believe. I checked the Github releases section for Polymer and saw that 0.5.1 is the latest stable release so when the option occured I hit 0.5.1. Now when I go to my website on my AppEngine dev server I see this:
Uncaught TypeError: object is not a function
On a bunch of Polymer elements, like
core-collapse.html:59
core-selection.html:77
core-selector.html:78
I'm not sure where I went wrong! Is 0.5.1 not the stabls release? I am very new to terminal stuff so am not sure where to go to try to fix this. Any help would be appreciated! Thanks!
edit: I didn't realize I needed to use /webcomponentsjs/webcomponents.js instead of platform.js now. I'll leave this up in case anyone else is confused in the future!
I'm having the following problem with Hudson after upgrading to 2.1.0:
After successfully creating the doxygen output, the following exception occurs:
Publishing Doxygen HTML results.
The determined Doxygen directory is 'C:/doxy/myDir'.
FATAL: error
hudson.util.IOException2: java.io.IOException: Unconnected pipe
The error did not occur with 2.0.1, unfortunately, downgrading does not work - Hudson tells me, that it can't read the job files anymore.
Does anyone know the best way to deal with this? Is there a simple solution to either make the doxygen plugin work in 2.1.0 or to successfully downgrade to 2.0.1?
Not sure what exactly the problem was, but migrating to the newest Jenkins release and using the HTML report publisher plugin instead of the Doxygen plugin is at least a work