I have followed this instructions to setup the latest version of NEOS:
https://docs.neos.io/cms/installation-development-setup/manual-installation-with-a-web-server
https://docs.neos.io/cms/installation-development-setup/running-the-setup-tool
After i log into the CMS i get the following error:
Xdebug has detected a possible infinite loop, and aborted your script with a stack depth of '256' frames
Exception Code 0
Exception Type Error
Thrown in File Packages/Framework/Neos.Flow/Classes/ObjectManagement/ObjectManager.php
Line 539
My local environment:
PHP Version 7.3.26-1+ubuntu20.04.1+deb.sury.org+1
XDebug 3.0.2
what's going wrong here?
this solves my problem
20-xdebug.ini
[xdebug]
xdebug.max_nesting_level=512
php.ini
max_execution_time = 600
This solves my problem:
"Xdebug has detected a possible infinite loop, and aborted your script with a stack depth of '256' frames"
Add to file:
/etc/php/8.1/apache2/conf.d/20-xdebug.ini
xdebug.max_nesting_level=512
And restart the server
Related
I have been experiencing this for some days now. As I start working in my Vs Code, the terminal server, will suddenly stop working, showing the error message attached in the screenshot.
Please does anyone have any idea how I can fix this.
RangeError: Array buffer allocation failed
at new ArrayBuffer (<anonymous>)
at new Uint8Array (<anonymous>)
at new FastBuffer (node:internal/buffer:959:5)
at createUnsafeBuffer (node:internal/buffer:1062:12)
at Function.allocUnsafeSlow (node:buffer:385:10)
at read (C:\Users\USER\Desktop\food-delivery\node_modules\webpack\lib\serialization\FileMiddleware.js:597:32)
at C:\Users\USER\Desktop\food-delivery\node_modules\webpack\lib\serialization\FileMiddleware.js:657:7
at C:\Users\USER\Desktop\food-delivery\node_modules\graceful-fs\graceful-fs.js:362:16
at FSReqCallback.oncomplete (node:fs:188:23)
PS C:\Users\USER\Desktop\food-delivery>
The Vs Code Screenshot below
It might be related to your node version architecture.
Check your version running the command node -p "process.arch"
In my case, I had the 32 bits version. Installing node 64 bits solved the issue.
I am installing k8s and vsphere CPI/CSI following the instructions located here
My setup:
2x centos 7.7 vSphere VM's (50g hd/16g ram), 1 master & 1 node in k8s cluster.
Made it to the part where I create the storageClass (near the end) when I discovered this github issue exactly. OP of the linked issue just started from scratch and their issue went away, so the report was closed. This has not been the case for me as I've redeployed my k8s cluster from scratch a bunch of times now and always hit this wall. Below is the error if you don't want to check the linked github issue.
Anyone have ideas on what I can try to get past this? I've checked my hd and ram and plenty there.
# kubectl -n kube-system logs pod/vsphere-csi-controller-0 vsphere-csi-controller
I0127 18:49:43.292667 1 config.go:261] GetCnsconfig called with cfgPath: /etc/cloud/csi-vsphere.conf
I0127 18:49:43.292859 1 config.go:206] Initializing vc server 132.250.31.180
I0127 18:49:43.292867 1 controller.go:67] Initializing CNS controller
I0127 18:49:43.292884 1 virtualcentermanager.go:63] Initializing defaultVirtualCenterManager...
I0127 18:49:43.292892 1 virtualcentermanager.go:65] Successfully initialized defaultVirtualCenterManager
I0127 18:49:43.292905 1 virtualcentermanager.go:107] Successfully registered VC "132.250.31.180"
I0127 18:49:43.292913 1 manager.go:60] Initializing volume.volumeManager...
I0127 18:49:43.292917 1 manager.go:64] volume.volumeManager initialized
time="2020-01-27T18:50:03Z" level=info msg="received signal; shutting down" signal=terminated
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x128 pc=0x867dc7]
goroutine 10 [running]:
google.golang.org/grpc.(*Server).GracefulStop(0x0)
/go/pkg/mod/google.golang.org/grpc#v1.23.0/server.go:1393 +0x37
github.com/rexray/gocsi.(*StoragePlugin).GracefulStop.func1()
/go/pkg/mod/github.com/rexray/gocsi#v1.0.0/gocsi.go:333 +0x35
sync.(*Once).Do(0xc0002cc8fc, 0xc000380ef8)
/usr/local/go/src/sync/once.go:44 +0xb3
github.com/rexray/gocsi.(*StoragePlugin).GracefulStop(0xc0002cc870, 0x21183a0, 0xc000056018)
/go/pkg/mod/github.com/rexray/gocsi#v1.0.0/gocsi.go:332 +0x56
github.com/rexray/gocsi.Run.func3()
/go/pkg/mod/github.com/rexray/gocsi#v1.0.0/gocsi.go:121 +0x4e
github.com/rexray/gocsi.trapSignals.func1(0xc00052a240, 0xc000426990, 0xc000426900)
/go/pkg/mod/github.com/rexray/gocsi#v1.0.0/gocsi.go:502 +0x143
created by github.com/rexray/gocsi.trapSignals
/go/pkg/mod/github.com/rexray/gocsi#v1.0.0/gocsi.go:487 +0x107
Ok turns out this SIGSEGV was a bug or something and it was caused by a network timeout, making this error kind of a red herring.
Details: My vsphere-csi-controller-0 pod was (and still is actually) unable to reach the vsphere server which caused the container in the pod to timeout and trigger this SIGSEV fault. The CSI contributers updated some libraries and the fault is now gone but the timeout remains. Timeout appears to be my problem and not related to CSI but that's a new question :)
If you want the details of what was fixed in the CSI check the github link in the question.
I am running an existing C project, and having an error. It was used to have no problem, and I could not fix it even after reading similar issues and trying their solutions.
./autogen.sh
running: aclocal
' is already registered with AC_CONFIG_FILES.
/usr/src/ports/autoconf2.5/autoconf2.5-2.69-3.noarch/src/autoconf2.69/lib/autoconf/status.m4:288: AC_CONFIG_FILES is
expanded from...
configure.ac:890: the top level
autom4te-2.69: /usr/bin/m4 failed with exit status: 1
aclocal-1.15: error: echo failed with exit status: 1
error: while running 'aclocal'
As shown, the "autom4te-2.69" is failing, and I did not see any hints about what to do. I am using "Cygwin" on windows 10.
Any idea about how to fix this?
Thanks in advance!
I'm trying to figure out why an WPF-app won't exit imediately on closing it. Using Process Explorer I hade found out that WerFault.exe is started while exiting which seem to indicate that something crashes during the teardown, perhaps some destructor or dispose that fails. This started happening when I recently switched to VS2015. I am running Windows 8.
My question is: How can I find out what the real problem is? Any way of finding a crash log for WerFault.exe? I have hundreds of destructors and dispose-methods so it's a bit hard to put breakpoints in all of them. Any other way of capturing these kinds of errors in VS?
The exit code is -1073740791 which "indicate a bug in the executed software that causes stack overflow, leading to abnormal termination of the software". But where?
Some more info from the event log:
Faulting module name: ucrtbase.DLL, version: 10.0.10240.16390, time stamp: 0x55a5b718
Exception code: 0xc0000409
Fault offset: 0x0000000000065a4e
You could try enabling user mode dumps:
Create the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps
Within LocalDumps, create a key that is the name of your executable
Within the key you just created, set the values of DumpFolder, DumpCount, DumpType, and CustomDumpFlags as needed (you should definitely set DumpType to 2 for full dumps, otherwise I don't think that enough information will be captured to debug a managed dump).
Once you have done this, whenever your executable crashes a dump file will be created in the folder specified by DumpFolder (or %LOCALAPPDATA%\CrashDumps by default).
I tried to get PHP4 working on WampServer, but whenever I started WampServer, the icon would go to orange but not all the way to green, because Apache wasn't starting.
I've explained how I got it working below. Hopefully this helps someone.
Here's how I got it working:
Install PHP 4.4.9 from http://www.wampserver.com/en/#addons-php
Install Apache 2.0.63 from http://www.wampserver.com/en/#addons-apache
Left click the WampServer tray icon, then Apache→Version→2.0.63, wait a minute, then PHP→Version→4.4.9
Test Apache by opening the command line and running C:\wamp\bin\apache\Apache2.0.63\bin\apache.exe. Fix any error reported, and repeat until you don't get any errors.
Icon→Apache→Service→Install Service
Icon→Restart All Services
In my case, the Apache errors were:
Syntax error on line 22 of C:/wamp/alias/phpmyadmin.conf: The specified IP address is invalid.
Syntax error on line 22 of C:/wamp/alias/sqlbuddy.conf: The specified IP address is invalid.
Syntax error on line 22 of C:/wamp/alias/webgrind.conf: The specified IP address is invalid.
The lines with errors were all the same: Allow from ::1. I commented them out to #Allow from ::1, which seemed to fix the error.
If you have trouble switching back to php5:
Open C:\Wamp\bin\php\php5.4.16\wampserver.conf.
Add the following lines:
$phpConf['apache']['2.4']['LoadModuleName'] = 'php5_module';
$phpConf['apache']['2.4']['LoadModuleFile'] = 'php5apache2_4.dll';
$phpConf['apache']['2.4']['AddModule'] = '';
Exit WampServer then start it again.