Reuses the existing flowFile - if its value is found
to be the name of an existing project, that project
is set as the active one.
If it is not the name of an existing project, it is
ignored.
* Call fsync() before closing file
* Fix race condition in tests due to incorrect stub.
The startFlows() function wasn't really being stubbed, so it was still being called. But there was no corresponding call to stopFlows().
In later tests, the check in Flows.init() was throwing the "Cannot init without a stop" error.
* Test coverage for fsync() calls
For issue #1478
* Revert "Fix race condition in tests due to incorrect stub."
This reverts commit 4f71d7851b.
* Fix race condition in tests due to incorrect stub.
The startFlows() function wasn't really being stubbed, so it was still being called. But there was no corresponding call to stopFlows().
In later tests, the check in Flows.init() was throwing the "Cannot init without a stop" error.
* Fix intermittent test failure in Exec node.
Occasionally, the error text on stderr will come in more than one piece. The test only worked correctly if a single message was received.
* fix bug where savesettings did not honor local settings variables
* don't create lib/flows on read; It's already created in localfilesystem.init and in saveLibraryEntry -
so removed call to promiseDir, and added a return of [] if accessing a folder which did not exist.
This is important because else when settings.readOnly is true, it still creates folders.
* Fix a CI failure where path passed to getLibraryEntry is empty;
treat this case as meaning it was wanting a folder, and return empty if the folder dioes not exist
* Add a test for getLibraryEntry( type, '/' ) as called by node-red
* change newsettings to camelCase newSettings
* Flow lib now adheres to pretty flow file, ui also adheres to this as well
* added settings mock object in flows_spec get api test
* reverted api changes, fixed parse of flow only
* try spell flows correctly
Closes#819
If a flow file is found to be zero-bytes:
If there is a non-empty backup, restore the backup and resolve
If there is no backup or it is also empty, resolve empty flow
If a flow file is found to be invalid json:
Log and resolve empty flow
The tests still use it in places - particular localfilesystem tests,
but those tests need to be redone with sinon stubbing in place and
not rely on real fs operations.
