stop task creation if task is too long or if debug is TRUE - introduces breaking changes #107
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR expands documentation but more drastically changes behavior of taskscheduler_create:
nchar(task) > 260
Both of these changes were inspired by #106
However, they are breaking changes. Users in the habit of running with
debug = TRUE
to simply 'see the call' might expect it to still run. Not sure if this is desired.Also, I could not replicate the behavior identified in #106. Using an
rscript
of length 102 and 115, I do not see the task being clipped. However, The user did say that the debug print value is not what is actually passed to the TR in the Windows task scheduler. I am on a Mac, so it would be good to see this actually happening. The code that warns the user about long file names has been in place (based on blame) for years, so the OG poster should have been warned.Here is an example. I'm running it after my edits, so you see an error about it failing because of TR length which is not in the original package (current behavior is just a warning)
Created on 2025-04-18 with reprex v2.1.0