Using WikiJS v2.5.296
Windows Server 2019
I ran the setup for WikiJS and Powershell produced this log. It has been stuck here for about 1 hour now.
Any advice is appreciated.
Related
after following this link link to the react native package v5+ 2022 i always get a build failed, always!! I've tried all my idea and I've also ran out of ideas too, pls seniors, someone help me.
I've tried uninstalling, following manual linking procedures, but no way
I am pretty new to React, sorry if I am asking something stupid. Any help would be highly appreciated :)
ENVIRONMENT
Ubuntu 20.04 in Windows 10 (WSL2)
Node version - v14.1.0
Npm version - v6.14.7
Code editor - VS Code v1.14.0
STEPS I DID
npx create-react-app <app-name>
cd <app-name>
npm start
https://localhost:3000 opens up in browser with default React landing page. Console says '[HMR] Waiting for update signal from WDS...
'
Delete all files in src directory and create empty index.js in src directory.
Output expected: Blank screen
Output: Default landing page of React even if I reload the page.
Struggles I made before asking this question :(
Looked in issues of create-react-app.
Tried troubleshooting create-react-app as mentioned in official docs.
Looked in stackoverflow for similar questions. Found some but none worked, maybe because my dev environment was different from them (WSL2 in Windows 10).
That sounds like a caching issue to me. My guess would be to clear your google chrome cache and try again. If that doesn't work, check your package.json file and make sure that under "scripts": "start" it says "react-scripts start".
Yayy! The issue is resolved.
It was my mistake :(.
All these days, I was trying to access the Windows filesystem from WSL2 and it seemed to be very slow. So I decided to work in the Linux filesystem itself. And everything works fine now. Thanks for helping :)
Description
I am following along with the instructions here: https://www.gatsbyjs.org/tutorial/part-one/
When I start the dev server and make a change to src/pages/index.js it is not hot reloaded in my browser.
Steps to Reproduce
Using gatsby-cli:
gatsby new hello-world https://github.com/gatsbyjs/gatsby-starter-hello-world
cd hello-world
gatsby develop
change the text inside of the div in src/pages/index.js
Expected Result
Page would automatically reload with new text.
Actual Result
Page would not change unless a manual refresh was applied in the browser.
Specs
OS: Ubuntu 18.04.3 LTS running in WSL on Windows 10 Pro
Node: 12.12.0
NPM: 6.11.3
Gatsby CLI: 2.8.8
Gatsby: 2.17.6
Browsers: Chrome 77.0.3865.120, IE 11.1006.17134.0, Firefox 70.0
I've tried multiple browsers with the same result so I ran devtools in firefox and examined the console output when I make a change and I see this error:
The connection to http://localhost:8000/__webpack_hmr was interrupted while the page was loading. client.js:88
[HMR] Update check failed: hotDownloadManifest/</request.onreadystatechange#http://localhost:8000/commons.js:42:16
process-update.js:147
Error: Manifest request to /d528b21bff3fd2caa92d.hot-update.json timed out. bootstrap:41
Firefox can’t establish a connection to the server at http://localhost:8000/__webpack_hmr. client.js:88
I've also looked around on github and here and haven't found a solution to my problem. Any ideas on a workaround, solution, or insight into why this might not be working for me would be greatly appreciated!
I was having same problems. Gatsby Develop hot reload was not working whenever I made changes to files, plus, Gatsby Develop was terribly slow to compile code and get the dev server up and running. I found out that if I create my Gatsby project in Linux directory structure instead of Windows, everything works out good and is blazing fast. So my solution was following.
Create your project in /home/<your_username> directory in WSL. Simply go to /home/<your_username> and make a folder there with mkdir; go to that folder and then run Gatsby create my_project command in that folder.
That way your project will reside in Linux directory structure, making everything run smoothly.
I faced the similar scenario today. Below steps made it work however warning message is persistent in the console.
Delete package.lock.json and node_modules folder
Delete the content present inside C:\Users\\AppData\Roaming\npm and npm-cache
Do a npm i.
Im running gatsby develop on windows. After trying many things, including wsl, npm clenaup etc, I realized that my antivirus sophos was blocking the webpack hot reload socket __webpack_hmr.
All I had to do is to disable the antivirus for a while. ( You are free to uninstall it or maybe change to another one ).
hope it works for you ;)
In Visual studio 2010 with Crystal Report 13 my project worked fine.
After I installed Visual studio 2015 community edition for my personal use. When i opened my project and run in Visual studio 2010 it throws "JavaScript runtime error: ‘bobj’ is undefined".
I surfed some website
http://www.mahadera.com/error-0x800a1391-javascript-runtime-error-bobj-is-undefined/
http://www.aspsnippets.com/Articles/Crystal-Reports-13-Visual-Studio-2010-Issue-with-IIS---bobj-is-undefined-JavaScript-Error-and-Crystal-Report-Viewer-not-displaying.aspx
and I reinstalled and copied aspnet_client folder and paste into project. Eventhough problem not yet solved. I guess the error because i installed VS2015 community edition.
Please help me and im clueless.
We figured out the root cause of the problem. When you installed VS2015, it installed .NET framework 4.6, which is causing the dreaded "bobj not defined" error. Unfortunately, .NET 4.6 wiped out (or overwrote) earlier version of .NET - whatever comes with VS2010 in your case or VS2013 in my case. You can uninstall .NET 4.6 and then "repair" VS2013, which reinstalled .NET 4.5.1 and the problem went away. Unfortunately, repairing VS2015 puts .NET 4.6 right back and the problem reappears.
So the bottom line, you can either have VS2015 - or earlier version of Visual Studio without bobj error; but not both
Don't thank me - thank Steve :)
1) First of all go to your root directory path in my case it is: C:\inetpub\wwwroot\aspnet_client\system_web\4_0_30319
here you will find a folder named "crystalreportviewers13". Copy it paste to the location of your solution.
2)In the head section of the page paste the following javascript refrence:
make sure the src is pointing to your local folder.
after that run your page.
I have the same problem, and this works good for me in VS2015.
Copy:
Solution_Directory\aspnet_client\system_web\4_5_27\crystalreportviewers13
To:
Solution_Directory\aspnet_client\system_web\4_6_81\crystalreportviewers13
I had same issue but now everything work right.
Uninstall framework 4.6.
After uninstalling 4.6, I found VS didn't work. Removing .NET 4.6 uninstalled all of .NET 4.x.
So I had to reinstall 4.0-4.5.x. This was accomplished through Windows Update. I then did a reboot and tried to run a website through VS and found that CR worked correctly.
I hope this will helps.
I think this is finally fixed in SAP Crystal Reports, developer version for Microsoft Visual Studio - Service Pack 16
https://wiki.scn.sap.com/wiki/display/BOBJ/SAP+Crystal+Reports%2C+developer+version+for+Microsoft+Visual+Studio+-+Service+Pack+16+-+Fixed+Issues
Incident 878969 Framework 4.6 causes CR for VS to create a unique folder path to the Crystalreportsviewer13 folder in IIS and IISExpress
More info in the following SAP thread:
https://scn.sap.com/thread/3824701
First of all: a bit of back story (because maybe this is not the best solution I could find). I have a long 6 hour-long course on web technologies this weekend and we will do a bit of NodeJS coding. We were told to bring laptops, but mine broke down a few years ago and all I have is a Nexus 7 tablet and I want to use it to write code (with a USB keyboard). I realize there are a few Android text editors with ssh / ftp support, but I would rather do everything in a browser, for simplicity and better control.
My solution was to use a nodejs file manager with code editing capabilities to write and execute scripts on the same server. I found Scripted, which looks lovely, but after putting it in the root of my cloud app (via git), I keep getting the error 503 Service Unavailable. Trying to install it via ssh using npm install -g scripted will return npm ERR! Error: EACCES, mkdir '/opt/rh/nodejs010/root/usr/lib/node_modules/scripted' (probably because Openshift will not give me write access to referenced configuration files). The server is running nodejs v0.10.25, so could it be a problem that Scripted has only been tested on version up to 0.8.16 ?
I'm a beginner with nodejs and any help is much appreciated. Cheers !