Develop Reference

System limit for number of file watchers reached - create-react-app production deploy on Heroku

I am using create-react-app which is continuously deployed to Heroku.The last 2 deploys failed on Heroku and it threw this error
2022-02-27T23:29:12.758222+00:00 heroku[web.1]: Process running mem=647M(125.4%)
2022-02-27T23:29:12.781765+00:00 heroku[web.1]: Error R14 (Memory quota exceeded)
2022-02-27T23:29:33.512810+00:00 heroku[web.1]: Process running mem=674M(130.3%)
2022-02-27T23:29:33.535558+00:00 heroku[web.1]: Error R14 (Memory quota exceeded)
2022-02-27T21:22:01.870428+00:00 app[web.1]: Error from chokidar (/app/src): Error: ENOSPC: System limit for number of file watchers reached, watch '/app/src/routes.ts'
2022-02-27T21:22:01.870532+00:00 app[web.1]: Error from chokidar (/app/src): Error: ENOSPC: System limit for number of file watchers reached, watch '/app/src/setupTests.ts'
...
And there are.
I haven't changed any config since it was working correctly. A few hours of research couldn't help me as there were only post about the same problem but related to npm start, which is solved by increasing max_user_watches.

Assuming this is purely a React application it should use virtually no memory.
Build a production release and serve it as static files. Nothing needs to happen server-side other than serving up those files. The easiest way to do that for a create-react-app application on Heroku us to use the mars/create-react-app-buildpack:
This buildpack deploys a React UI as a static web site. The Nginx web server provides optimum performance and security for the runtime.
Configure your application to use this buildpack:
heroku buildpacks:set mars/create-react-app
Then redeploy.

React Native Project BUILDS Succesfull(with deprecated warning) and opens in my emulator, but keeps loading forever

I used yarn to install the packages, Im using typescript, my index is JS.
I'm getting a white screen with the load symbol on the emulator..
Thanks for the ones helping
Here's what Im getting:
info Running jetifier to migrate libraries to AndroidX. You can disable it using "--no-jetifier" flag.
(node:41396) Warning: Accessing non-existent property 'padLevels' of module exports inside circular dependency
(Use `node --trace-warnings ...` to show where the warning was created)
Jetifier found 1123 file(s) to forward-jetify. Using 4 workers...
info JS server already running.
info Installing the app...
> Task :app:installDebug
09:49:22 V/ddms: execute: running am get-config
09:49:22 V/ddms: execute 'am get-config' on 'emulator-5554' : EOF hit. Read: -1
09:49:22 V/ddms: execute: returning
Installing APK 'app-debug.apk' on 'Pixel_2_API_28(AVD) - 9' for app:debug
09:49:22 D/app-debug.apk: Uploading app-debug.apk onto device 'emulator-5554'
09:49:22 D/Device: Uploading file onto device 'emulator-5554'
09:49:22 D/ddms: Reading file permision of C:\Users\Daniel\CalcSol\android\app\build\outputs\apk\debug\app-debug.apk as: rwx------
09:49:22 V/ddms: execute: running pm install -r -t "/data/local/tmp/app-debug.apk"
09:49:24 V/ddms: execute 'pm install -r -t "/data/local/tmp/app-debug.apk"' on 'emulator-5554' : EOF hit. Read: -1
09:49:24 V/ddms: execute: returning
09:49:24 V/ddms: execute: running rm "/data/local/tmp/app-debug.apk"
09:49:24 V/ddms: execute 'rm "/data/local/tmp/app-debug.apk"' on 'emulator-5554' : EOF hit. Read: -1
09:49:24 V/ddms: execute: returning
Installed on 1 device.
Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.2/userguide/command_line_interface.html#sec:command_line_warnings
BUILD SUCCESSFUL in 29s
141 actionable tasks: 2 executed, 139 up-to-date
info Connecting to the development server...
info Starting the app on "emulator-5554"...
Starting: Intent { cmp=com.calcsol/.MainActivity }'''

You can try:
Delete node_modules and re-install
Go to your android folder and delete the file .idea
In Android Studio: file > Invalidate Caches / Restart and select 'Invalidate and Restart'

Zeit asking me for "mysql2" dependency, but I have it installed

I'm trying to make a project work on zeit hosting. I'm using Node with Express and Sequelize with mysql2.
When I try to run the app in zeit, it give me the following errors:
-------------------------------------------------------
Duration: 425.50 ms Billed Duration: 500 ms Memory Size: 3008 MB Max Memory Used: 96 MB
RequestId: 2923134e-be9b-4223-96c7-dce58b5a0b19 Process exited before completing request
Error: Please install mysql2 package manually
-------------------------------------------------------
I have mysql2 installed on my project, and the app runs perfectly fine in localhost. What could be causing this?
I have tried to add node_modules on the github repo, and also tried to unninstall mysql2 and reinstall it as global, but both didn't work.
I just don't know if this problem is caused by some code error or some mistake related to the way I uploaded the files.
Here's the Github repo, you can check the project running on localhost normally.
https://github.com/vitorlimadev/employee_management_system

This is a known bug with ncc that has a workaround.
let db = new Sequelize({
dialect: 'mysql',
dialectModule: require('mysql2')
});
See this comment: https://github.com/vercel/ncc/issues/345#issuecomment-487404520

npm install hanging due to possible incorrect url

When I run npm install --verbose The installation hangs at:
npm http fetch GET 200 https://na.artifactory.swg-devops.com/artifactory/api/npm/wcp-cos-de-npm-virtual/chai-as-promised 1533ms
⸨ ░░░░░░░░░░░░░░░░⸩ ⠙ loadDep:tstest: sill pacote range manifest for chai-as-promised#^7.1.1 fetched in 1558ms
I pasted the url ttps://na.artifactory.swg-devops.com/artifactory/api/npm/wcp-cos-de-npm-virtual/chai-as-promised into my browser and was prompted with a login. Is it possible I have the wrong URL set? If not that what could be causing this to hang?
I also tried running npm install --registry=https://registry.npmjs.org/ --verbose but it hangs here:
npm http fetch GET 200 https://registry.npmjs.org/chai-as-promised 25ms (from cache)
⸨ ░░░░░░░░░░░░░░░░⸩ ⠙ loadDep:tstest: sill pacote range manifest for chai-as-promised#^7.1.1 fetched in 50ms

You need to authenticate your npm client first.
See the heading Authenticating the Npm Client in this link
https://www.jfrog.com/confluence/display/RTF/Npm+Registry

npm config set loglevel info and then run npm i again
then restart the system.

Trying to use meteor up on digital ocean

I have a digital ocean droplet that I am trying to deploy the most basic of meteor apps to, but I am getting a failing response. Any idea why this is happening?
UPDATE: added entire output
Anderss-iMac:microscope-deploy anderskitson$ mup deploy
Meteor-UP : Production Quality Meteor Deployments
--------------------------------------------------
Bundling Started: /Users/anderskitson/sites/microscope
Started TaskList: Deploying App
[bray.anderskitson.ca] uploading bundle
[bray.anderskitson.ca] uploading bundle: SUCCESS
[bray.anderskitson.ca] setting up env vars
[bray.anderskitson.ca] setting up env vars: SUCCESS
[bray.anderskitson.ca] invoking deployment process
[bray.anderskitson.ca] invoking deployment process: FAILED
-----------------------------------STDERR-----------------------------------
Warning: Permanently added 'bray.anderskitson.ca,162.243.52.235' (RSA) to the list of known hosts.
npm WARN package.json http-proxy#1.0.0 No repository field.
npm http GET https://registry.npmjs.org/fibers
npm http 304 https://registry.npmjs.org/fibers
stop: Unknown instance:
bash: line 46: wait-for-mongo: command not found
-----------------------------------STDOUT-----------------------------------
> fibers#1.0.1 install /opt/meteor/tmp/bundle/programs/server/node_modules/fibers
> node ./build.js
`linux-x64-v8-3.14` exists; testing
Binary is fine; exiting
fibers#1.0.1 node_modules/fibers
meteor start/running, process 10373
wait for mongo(5 minutes) to initiaze
----------------------------------------------------------------------------
Completed TaskList: Deploying App

I ran into same problem and I figured out that this command wasn't fired really well
sudo npm install -g forever userdown wait-for-mongo
and I manually did that so I can see wait-for-mongo a valid command,
see if that helps you too.