Jelly module throwing internal server error - kohana

The Jelly module throws a 500 internal error. I have no idea why it does this and how to solve this.
When I remove jelly module folder from the server or simply rename any of the Jelly module files, the error disappears (Kohana throws an error because Jelly Class is not found which is normal).
I don't understand why Jelly would throw an internal error, it just does not make any sense!
(The error does not come from the folders and files permissions. I made sure that they're all 755 and 644).
(Everything works fine locally - WAMP server)
Thank you.

Check you're on the latest version of Jelly.
Check all your files for syntax errors. If you don't get an error page returned from Kohana it's probably because you've crashed php in some way.
Sorry if this doesn't help, please post more code/debug info.

Thank your for your answers. The problem was solved somehow. I have no idea what happened.
It seemed to work when I removed send_headers() in the bootstrap but it really annoyed me because I needed it.
Then I replaced Request::instance($_SERVER['PATH_INFO']) by Request::instance() in the echo in the bootstrap and it worked...
More info about the error logs there: http://forum.kohanaframework.org/comments.php?DiscussionID=6322&page=1

Related

An unknown server-side error occurred while processing the command. Original error: Cannot read properties of undefined (reading 'match')

I just started mobile automation testing and I'm trying to write tests for android on Android Studio with Appium, however I think I just did something wrong in configuration process. I was getting some other errors and these are the things I've done so far.
set ANDROID_HOME path
set JAVA_HOME path
updated node version
After doing these I've started appium server and tried again. I was able to communicate with the emulator but something is still off.
run command
appium-doctor and flutter doctor seems fine though.
appium-doctor
flutter doctor
And this is the exact error message I get.
this
Any help is appreciated. Thanks in advance.
I solved the case a while ago, thought could help someone. The problem was the first config I copied from another how-to source. It was trying to use appium-flutter-driver and I assume therefore there was a code snippet like this:
'appium:automationName': 'Flutter'
Which wasn't working because I was trying to run it with appium-flutter-finder. I don't exactly know what happened there but when I looket it up from appium's guide and did the default config they gave there the problem is gone. Which is:
'appium:automationName': 'Appium'

"cannot find module npm-cli.js"

I've been at this for hours, and I've tried endless things and reinstalled NodeJS so, so many times.
I'm on Win10. I cannot run npm, it seems to have some PATH error I cannot get around this:
Error: Cannot find module 'C:\Program
Files\nodejs\node_modules\npm\bin\node_modules\npm\bin\npm-cli.js'
This path looks screwy, I know. I've removed any roaming entries in the PATH var for nodejs or npm. Only
C:\Program Files\nodejs
remains at this point.
Is there any real solution that works for Win10 every time?
I'll do anything at this point. I've tried so, so many things that I found here or a dozen other sites.
I'm not trying to do anything special. I just want to run npm at the command line successfully--update itself, check itself, anything. No matter how it's invoked, I get the error above.
I mean, what should the PATH look like? How can I make this thing happy?
Thanks for any help.

Error: Cannot find module './dist-tools/transform.js' from '/opt/atlassian/pipelines/agent/build/node_modules/aws-sdk'

Hi so we have something interesting happening in our builds.
Nothing regarding the gulp build script changed from our side for one of our projects. But suddenly today when we try to do a pipeline build on one of our repositories we get the following stacktrace error:
Error: Cannot find module './dist-tools/transform.js' from '/opt/atlassian/pipelines/agent/build/node_modules/aws-sdk'
at /opt/atlassian/pipelines/agent/build/node_modules/resolve/lib/async.js:128:35
at load (/opt/atlassian/pipelines/agent/build/node_modules/resolve/lib/async.js:147:43)
at onex (/opt/atlassian/pipelines/agent/build/node_modules/resolve/lib/async.js:172:17)
at /opt/atlassian/pipelines/agent/build/node_modules/resolve/lib/async.js:13:69
at FSReqWrap.oncomplete (fs.js:152:21)
Has anyone come accross this before? (we are using node 10.17 for our builds)
We tested the same code from our local builds and get the exact same issue. It seems that something in the aws-sdk package changed?
Since this error suddenly appeared this morning, we looked at our aws-sdk package and updated it to the latest version (2.643.0), but we still get the same error. No code that uses the aws-sdk package has changed.
Also seeing this as of this morning. I find this somewhat sus (adding dist-tools to npmignore).
https://github.com/aws/aws-sdk-js/commit/98c40e64cb7d60927c6a0cec49592fc1fcaa59d7
I wonder if pulling the package directly from GH would resolve.
UPDATE:
I've got a convo going on over here about this https://github.com/aws/aws-sdk-js/issues/3159
We downgraded to the previous version and our issue went away.

jhipster project is broken after upgrade

My jhipster project was working fine before. Past two days it is acting funny. There is some version changes causing these issues.
Initially I got the following error in console, when I tried navigating to different page :
NavigationError(id: 2, url: '/ext-task-group-list', error:
InvalidCharacterError: String contains an invalid character)
In an effort to try to fix this problem, I ran
jphister upgrade
the upgrade is successful. However, mvnw command is not starting the server. Instead it is compiling the project and comes out successfully.
Couldnt find any resource in the net.
Anyone have fix for these two issues, pls share.
Start by doing a mvnw -X to see all the debug errors. That will give you more detail that you can go by

ReferenceError: Can't find variable: require node.js

I have tried the related solutions for this problem (eg. add the dependencies through 'package.json' and run npm install) but unfortunately they didn't solve it. Problem is when I run the code from the accepted answer from the following discussion:
Node.js, Ajax sending and receiving Json
everything works fine. the Ajax-call works and I get the result with the data. But in the console I get the error.
'ReferenceError: Can't find variable: require' (Globale code — requesthandle.js:2ReferenceError: Can't find variable: require)
Any ideas which could be the problem here? Thank you!
This is the code I am using:
requesthandle.js (server side, by executing node requesthandle.js) ==>
http://i67.tinypic.com/24zbyma.png
and
list.html (by visiting mydomain/list.html)
http://i65.tinypic.com/mwp3md.png
Found the solution.. overlooked the fact I included the requesthandle.js in my list.html / client-side code. Thank you for your help Arpit Solanki! Seems your first remark included the solution: I was using it frontend by mistake..

Resources