I have been running on some problems since the last update (6.38.1). docpad seems to be broken on macosx the command "docpad run" or "docpad watch" returns the error (on the browser)
Error 15 (net::ERR_SOCKET_NOT_CONNECTED): Error unknown
when i try to access
http://localhost:9778
but "docpad server" works without problems, so maybe the error is the liverload module or other module for development... i'm not able to isolate this problem.
does anyone has the same problem and maybe a solution to share? i'm about to leave docpad because of this error :(
Related
Getting the following error message when calling composer install.
Fatal error: Declaration of Composer\IO\BaseIO::hasAuthentication($repositoryName) must be compatible with Composer\IO\IOInterface::hasAuthentication(string $repositoryName) in phar:///usr/local/psa/var/modules/composer/composer.phar/src/Composer/IO/BaseIO.php on line 20
This is occurring in our dev environment when we run the gitlab pipeline to build and deploy in our CI/CD pipeline. No changes have been made to this process that has been running flawlessly for years. My guess is that something has changed in the composer base code library in the last few days.
Anyone else having this same issue? Or does anyone have a clue on how to fix this issue?
The first step in the TC build process is to run "yarn install" in the directory: D:\TeamCity\Agent\work\MyApp
this is successfull up until: [4/4] Rebuilding all packages...
at which point this error is thrown:
```[Step 1/5] error An unexpected error occurred: "D:\\TeamCity\\Agent\\work\\MyApp\\node_modules\\#babel\\runtime-corejs2\\node_modules\\core-js: UNKNOWN: unknown error, open 'D:\\TeamCity\\Agent\\temp\\buildTmp\\yarn--1592234614361-0.5350564069819825\\yarn'"```
From what I can tell here, its trying to open the temp folder, but cant? or cant find it?
This does not happen consistently. It seems to be random, or whenever there is an extended time between builds. We cannot determine a common pattern. To fix it, we just re-run the build.
We have tried 'yarn install --verbose' and 'yarn install --force' the former showed nothing usefull on output, and --force was a guess at best.
I'm hoping someone can give a bit more context as to exactly what that error might mean.
Screenshot of the error
I tried to run an incompletely installed program and then received this error. Is there anyway to solve this without the official installer? As far as I understand it, it's missing some registry entries. Can I fix this using information from the error log below?
The error log :
https://pastebin.com/VL5ps2hw
Thanks
When I try to run the software, I get this error as well:
Error Number:5. Error Source: mscorlib. This is error in paint 1.
When I run the 'make' command at the terminal window to build vein-lte 1.3, I encounter a fatal error at applications/commons/ApplicationBase.cc: 18:0.
There seem to be an issue with including the header Operationalbase.h in ApplicationBase.h.
It complains that there is no such file or directory. The error is originating from the inet folder.
I really need help with resolving this.
Cheers.
I want to isntall winexe on Ubuntu 13.1 32bit version.
I did exactly after this guide: Winexe - aldeid
If I execute the command "make basics bin/winexe" there occurs the following error:
Compiling ../librpc/idl/atsvc.idl
/usr/include/stdc-predef.h:0: error: Syntax error near '3'
Failed to parse ../librpc/idl/atsvc.idl at ./../pidl/pidl line 608.
make: *** [idl] Error 1
I have absolutely no idea how to fix this.
I would be even satisfied with a solution suggestion to this problem.
Thank you.
make "CPP=gcc -E -ffreestanding" basics bin/winexe works around this error.
I found "another" way to isntall winexe.
ubuntu forum
The Donwload-Links to the static version (just unzip and run winexe) are working at the moment (on some other pages they didn't).
I still don't know why the error above occurs, if anybody knows it, please tell me anyway. I am still interessted.
VERY IMPORTANT EDIT: After restart winexe gives put an Internal Error signal 11
So I still need a solution for winexe. Either to isntall the verision from git or to fix this error.
EDIT nummber 2: OK, why am I sking questions if I answer them by myself?
The installation form the quide mentiond in my question qorks fine on Ubuntu 12 LTS and winexe-static-version is also ok if you don't make typing errors as I did.