backupmanager | Simple laravel package to backup/restore files and database | Continuous Backup library

Inside the FtpManager.downloadFolder function, I see recursive calls to the same downloadFolder method with an await. Your Maximum call stack exceeded error could come from there, since your initial call will need to keep everything in memory while traversing all subdirectories.

Instead of awaiting everything recursively, you could setup a queue system, with an algorithm like this:

• Add the current folder to a queue
• While that queue is not empty:
  • Get the first folder in the queue (and remove it from it)
  • List all entries in it
  • Download all files
  • Add all subfolders to the queue

This allows you to download a lot of folders in a loop, instead of using recursion. Each loop iteration will run independently, meaning that the result of the root directory download won't depend on the deeeeeep file tree inside it.

There are plenty of queue manager modules for NodeJS, which allow you to have concurrency, timeouts, etc. One I've used in the past is simply named queue. It has a lot of useful features, but will require a little more work to implement in your project. Hence, for this answer, I used no external queue module, so that you can see the logic behind it. Feel free to search for queue, job, concurrency...

I wanted to implement that logic directly into your own code, but I don't use Typescript, so I thought I'd make a simple folder copy function, which uses the same logic.

Note: For simplicity, I've not added any error handling, this is just a proof of concept! You can find a demo project which uses this here on my Github.

Here is how I've done it:

Try to wrap your forms with

There are a couple of problems here...

First, your connector configurations are incorrect. On broker 1 you're using this:

While i found no direct way to change the language of the device using code, you could just use an Intent instead of doing all that implementation above.

The error was Notepad++ kept a wierd copy of the file C:\Windows\System32\inetsrv\config\applicationHost.config on the server.

Opened it in regular notepad, and saw other content and fixed it: (Probably has something to do with the system file is locked etc)

As suggested by @VaclavTurecek the problem was that the Service Fabric Nuget packages were a version ahead of the runtime installed on the server (in this case my local machine). Updating via the Web Platform Installer has resolved the problem.

The -f option of tar is the destination file for the archive; it can be anywhere you want, i.e., you can change

-cvpzf "backup_$dcreate.tar.gz"

to

-cvpzf "plugins/backups/backup_$dcreate.tar.gz"

if you want your new archive to be created in plugins/backups/

I found my problem, this came from firebase I disable in debug mode: I had added this to disable it but this was problem for this bug