samagids
October 3, 2024, 8:52pm
1
Some users already have their scripts and were to load them and run them.
Instead getting a timeout error. Can we increase the timeout from 10s to 40s
here are the errors
Staging template dir Timeout occurred when trying to determine directory size. Size must be computable in less than 10 seconds. Either directory has too many files or the file system is currently slow (if so, please try again later).
travert
October 3, 2024, 9:58pm
2
Hi and welcome!
I think this is a question around the job composer, but I want to confirm that.
If so, you won’t be able to alter those settings as they are hardcoded in the app:
class Filesystem
class << self
attr_accessor :max_copy_safe_dir_size, :max_copy_safe_du_timeout_seconds
def max_copy_safe_dir_size
@max_copy_safe_dir_size ||= 1024*1024*1024
end
def max_copy_safe_du_timeout_seconds
@max_copy_safe_du_timeout_seconds ||= 10
end
end
MAX_COPY_TIMEOUT_MESSAGE = "Timeout occurred when trying to determine directory size. " \
"Size must be computable in less than #{max_copy_safe_du_timeout_seconds} seconds. " \
"Either directory has too many files or the file system is currently slow (if so, please try again later)."
# Returns a http URI path to the cloudcmd filesystem link
def fs(path)
This app is also end of life so we aren’t providing feature additions at the moment as it is being phased out for the Project Manager instead.
samagids
October 4, 2024, 2:43pm
3
Thank you that was helpful.
Creating an empty directory and putting the script inside works. This is because my home directory is more than 1G.
system
April 2, 2025, 2:43pm
4
This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.