Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disallow creating or updating scheduler if invalid #2214

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

jhs-panda
Copy link
Contributor

Description

When creating or updating a scheduler, tests visual run to ensure action can be loaded and works.
If visual run test works, allow scheduler creation/update.
If visual run test doesn't work on creation, delete created scheduler.
If visual run test doesn't work on update, reinstate previous scheduler prior to update attempt.

Motivation and Context

Resolves #2187

How Has This Been Tested?

Before:
Allows creation as long as inputs to Scheduler Creation filled. However, when running scheduler, gets many errors.
Screen Shot 2024-09-22 at 2 08 09 PM

After:
Notes error if action does not exist or is not readable:
Screen Shot 2024-09-22 at 2 13 12 PM

Notes error if action exists and is readable but cannot execute properly:
Screen Shot 2024-09-22 at 2 15 31 PM

If update is not successful, notes error and reverts to previous state:
Screen Shot 2024-09-22 at 2 16 42 PM

For successful actions that load properly, work when run:
Screen Shot 2024-09-22 at 2 17 58 PM

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • I have run rubocop and erblint for style check. If you haven't, run overcommit --install && overcommit --sign to use pre-commit hook for linting
  • My change requires a change to the documentation, which is located at Autolab Docs
  • I have updated the documentation accordingly, included in this PR

Other issues / help required

Copy link
Contributor

coderabbitai bot commented Sep 22, 2024

📝 Walkthrough
📝 Walkthrough

Walkthrough

The changes made to the SchedulersController focus on improving the create, update, and visual_run actions by adding validations for the existence and readability of action files specified in the scheduler parameters. If these validations fail, users receive error messages and are redirected to the appropriate forms. New methods for validating and executing action files have also been introduced, enhancing error handling and allowing for rollback in case of failures during visual runs.

Changes

Files Change Summary
app/controllers/schedulers_controller.rb Enhanced create, update, and visual_run actions with validations for action files. Added methods for validating, running, and executing action files with improved error handling.

Assessment against linked issues

Objective Addressed Explanation
Validations could require the action to be an existing file (Issue #2187)
The controller could require that a successful visual run occur before enabling a job (Issue #2187)
Scheduler could auto-disable or do exponential back-off for failing jobs (Issue #2187) No implementation for auto-disable or back-off logic.
Scheduler errors that are likely to be course errors could be caught and logged but not passed to exception notifier (Issue #2187) Unclear if specific logging mechanisms were implemented.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 5

Outside diff range and nitpick comments (2)
app/controllers/schedulers_controller.rb (2)

29-30: Correct error message formatting to avoid unintended newlines

The error message string spans multiple lines without proper concatenation, which can include unintended newline characters in the displayed message. To ensure the error message is formatted correctly, combine the string into a single line or use string concatenation.

Apply this diff to fix the formatting:

- flash[:error] = "Scheduler create failed. Action file does not exist or is
-   not readable at #{action_path}."
+ flash[:error] = "Scheduler create failed. Action file does not exist or is " \
+   "not readable at #{action_path}."

109-110: Correct error message formatting to avoid unintended newlines

Similar to the issue in the create method, the error message here spans multiple lines without proper concatenation. To ensure the message is displayed correctly, combine the string into a single line or use string concatenation.

Apply this diff to fix the formatting:

- flash[:error] = "Scheduler update failed. Action file does not exist or is
-   not readable at #{action_path}."
+ flash[:error] = "Scheduler update failed. Action file does not exist or is " \
+   "not readable at #{action_path}."
Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between be48fe4 and 352afba.

Files selected for processing (1)
  • app/controllers/schedulers_controller.rb (3 hunks)
Additional comments not posted (2)
app/controllers/schedulers_controller.rb (2)

35-44: Robust error handling added to ensure scheduler validity

The addition of error handling in the create method ensures that if the test_run_visual_scheduler fails, the created scheduler is destroyed, and an appropriate error message is displayed. This enhances the reliability of the scheduler creation process.


106-113: Refactor repeated file existence checks into a private method

As mentioned earlier, the file existence and readability check here is duplicated from the create method. Extracting this logic into a private method will reduce duplication and improve code maintainability.

app/controllers/schedulers_controller.rb Outdated Show resolved Hide resolved
app/controllers/schedulers_controller.rb Outdated Show resolved Hide resolved
app/controllers/schedulers_controller.rb Outdated Show resolved Hide resolved
app/controllers/schedulers_controller.rb Outdated Show resolved Hide resolved
app/controllers/schedulers_controller.rb Outdated Show resolved Hide resolved
@jhs-panda jhs-panda requested review from a team and 20wildmanj and removed request for a team September 27, 2024 21:50
@@ -23,9 +23,25 @@ def new; end
action_auth_level :create, :instructor
def create
@scheduler = @course.scheduler.new(scheduler_params)
# Check if the action file exists and is readable
action_path = Rails.root.join(scheduler_params[:action]).to_path
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you also check that the action is within the assessment directory? See Archive.in_dir? which for example is used in handout.rb.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi! Do you mean the course directory? From what I can tell schedulers are for courses, not specific assessments.

Copy link
Contributor

@20wildmanj 20wildmanj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Functionally this works pretty nicely! But I think there should be some refactoring of the code so that it's a bit more maintainable.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 6

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 352afba and 25d78cf.

📒 Files selected for processing (1)
  • app/controllers/schedulers_controller.rb (3 hunks)

Comment on lines +26 to +42
action_path = Rails.root.join(scheduler_params[:action]).to_path
# Check if the action file exists, is readable, and compiles
if validate_compile_action_file(action_path)
if @scheduler.save
# Ensure visual run is successful
if run_visual_scheduler(@scheduler)
flash[:success] = "Scheduler created and executed successfully!"
redirect_to(course_schedulers_path(@course)) and return
else
@scheduler.destroy
flash[:error] = "Scheduler creation failed during execution."
end
else
flash[:error] = "Scheduler create failed. Please check all fields."
end
end
redirect_to(new_course_scheduler_path(@course))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Security and data integrity concerns in scheduler creation

Several critical issues need to be addressed:

  1. The code doesn't validate if the action file is within the assessment directory, which could lead to security vulnerabilities.
  2. The creation process should be wrapped in a transaction to maintain data consistency.
  3. Using Rails.root.join with user input could lead to path traversal attacks.

Consider implementing these fixes:

def create
  @scheduler = @course.scheduler.new(scheduler_params)
+ 
+ ActiveRecord::Base.transaction do
+   # Validate file is within assessment directory
+   action_path = Rails.root.join(scheduler_params[:action]).to_path
+   unless Archive.in_dir?(action_path, @course.assessment.directory)
+     raise "Action file must be within the assessment directory"
+   end
+ 
    if validate_compile_action_file(action_path)
      if @scheduler.save
        if run_visual_scheduler(@scheduler)
          flash[:success] = "Scheduler created and executed successfully!"
          redirect_to(course_schedulers_path(@course)) and return
        else
          raise ActiveRecord::Rollback
        end
      end
    end
+   raise ActiveRecord::Rollback
+ end
  
  flash[:error] ||= "Scheduler creation failed"
  redirect_to(new_course_scheduler_path(@course))
end

Committable suggestion skipped: line range outside the PR's diff.

Comment on lines +57 to 59
@scheduler = Scheduler.find(params[:scheduler_id])
@log = execute_action(@scheduler)
render partial: "visual_test"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Add error handling to visual_run action

The action should handle potential exceptions from execute_action and provide appropriate feedback.

def visual_run
  @scheduler = Scheduler.find(params[:scheduler_id])
+ begin
    @log = execute_action(@scheduler)
+   flash[:success] = "Visual test completed successfully"
+ rescue StandardError => e
+   @log = "Error executing scheduler: #{e.message}"
+   flash[:error] = "Visual test failed"
+ end
  render partial: "visual_test"
end
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
@scheduler = Scheduler.find(params[:scheduler_id])
@log = execute_action(@scheduler)
render partial: "visual_test"
@scheduler = Scheduler.find(params[:scheduler_id])
begin
@log = execute_action(@scheduler)
flash[:success] = "Visual test completed successfully"
rescue StandardError => e
@log = "Error executing scheduler: #{e.message}"
flash[:error] = "Visual test failed"
end
render partial: "visual_test"

Comment on lines +109 to +126
def validate_compile_action_file(action_path)
# Check if the action file exists and is readable
unless File.exist?(action_path) && File.readable?(action_path)
flash[:error] = "Scheduler update failed. Action file does not exist or is
not readable at #{action_path}."
return false
end

# compile action file to check for syntax errors
begin
RubyVM::InstructionSequence.compile(File.read(action_path))
rescue SyntaxError => e
flash[:error] = "Syntax error in action file: #{e.message}"
return false
end

true
end
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Enhance action file validation

The validation method should be more robust and secure.

Consider these improvements:

def validate_compile_action_file(action_path)
+ # Validate absolute path to prevent directory traversal
+ unless action_path.start_with?(Rails.root.to_s)
+   flash[:error] = "Invalid action path"
+   return false
+ end

  # Check if the action file exists and is readable
  unless File.exist?(action_path) && File.readable?(action_path)
    flash[:error] = "Scheduler update failed. Action file does not exist or is not readable"
    return false
  end

  # compile action file to check for syntax errors
  begin
    RubyVM::InstructionSequence.compile(File.read(action_path))
  rescue SyntaxError => e
    flash[:error] = "Syntax error in action file: #{e.message}"
    return false
+ rescue StandardError => e
+   flash[:error] = "Error validating action file: #{e.message}"
+   return false
  end

  true
end
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
def validate_compile_action_file(action_path)
# Check if the action file exists and is readable
unless File.exist?(action_path) && File.readable?(action_path)
flash[:error] = "Scheduler update failed. Action file does not exist or is
not readable at #{action_path}."
return false
end
# compile action file to check for syntax errors
begin
RubyVM::InstructionSequence.compile(File.read(action_path))
rescue SyntaxError => e
flash[:error] = "Syntax error in action file: #{e.message}"
return false
end
true
end
def validate_compile_action_file(action_path)
# Validate absolute path to prevent directory traversal
unless action_path.start_with?(Rails.root.to_s)
flash[:error] = "Invalid action path"
return false
end
# Check if the action file exists and is readable
unless File.exist?(action_path) && File.readable?(action_path)
flash[:error] = "Scheduler update failed. Action file does not exist or is not readable"
return false
end
# compile action file to check for syntax errors
begin
RubyVM::InstructionSequence.compile(File.read(action_path))
rescue SyntaxError => e
flash[:error] = "Syntax error in action file: #{e.message}"
return false
rescue StandardError => e
flash[:error] = "Error validating action file: #{e.message}"
return false
end
true
end

Comment on lines +128 to +138
def run_visual_scheduler(scheduler)
log = execute_action(scheduler)
# Ensure visual run is successful or return error
if log.include?("Error")
flash[:error] = "Scheduler execution failed."
false
else
flash[:success] = "Scheduler executed successfully!"
true
end
end
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Improve error detection in run_visual_scheduler

The current error detection using string matching is unreliable.

def run_visual_scheduler(scheduler)
  log = execute_action(scheduler)
- # Ensure visual run is successful or return error
- if log.include?("Error")
+ # Check execution status from execute_action
+ if log[:status] == :error
-   flash[:error] = "Scheduler execution failed."
+   flash[:error] = "Scheduler execution failed: #{log[:message]}"
    false
  else
    flash[:success] = "Scheduler executed successfully!"
    true
  end
end

Committable suggestion skipped: line range outside the PR's diff.

Comment on lines +65 to +82
action_path = Rails.root.join(scheduler_params[:action]).to_path
# Check if the action file exists, is readable, and compiles
if validate_compile_action_file(action_path)
previous_state = @scheduler.attributes
if @scheduler.update(scheduler_params)
# Ensure visual run is successful
if run_visual_scheduler(@scheduler)
flash[:success] = "Scheduler updated and executed successfully!"
redirect_to(course_schedulers_path(@course)) and return
else
@scheduler.update(previous_state) # If error, revert to previous state.
flash[:error] = "Scheduler update failed during execution. Reverted to previous state."
end
else
flash[:error] = "Scheduler update failed! Please check your fields."
end
end
redirect_to(edit_course_scheduler_path(@course, @scheduler))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Improve update action security and reliability

The current implementation has similar security issues as the create action and uses manual state management which could be problematic.

Consider this improved implementation:

def update
  @scheduler = Scheduler.find_by(id: params[:id])
  
+ ActiveRecord::Base.transaction do
+   # Validate file is within assessment directory
+   action_path = Rails.root.join(scheduler_params[:action]).to_path
+   unless Archive.in_dir?(action_path, @course.assessment.directory)
+     raise "Action file must be within the assessment directory"
+   end
+   
    if validate_compile_action_file(action_path)
-     previous_state = @scheduler.attributes
      if @scheduler.update(scheduler_params)
        if run_visual_scheduler(@scheduler)
          flash[:success] = "Scheduler updated and executed successfully!"
          redirect_to(course_schedulers_path(@course)) and return
        else
-         @scheduler.update(previous_state)
+         raise ActiveRecord::Rollback
        end
      end
    end
+   raise ActiveRecord::Rollback
+ end

  flash[:error] ||= "Scheduler update failed"
  redirect_to(edit_course_scheduler_path(@course, @scheduler))
end

Committable suggestion skipped: line range outside the PR's diff.

Comment on lines +140 to +179
def execute_action(scheduler)
action_path = Rails.root.join(scheduler.action).to_path
# https://stackoverflow.com/a/1076445
read, write = IO.pipe
log = "Executing #{action_path}\n"
begin
pid = fork do
read.close
mod_name = action_path
fork_log = ""
begin
require mod_name
output = Updater.update(scheduler.course)
if output.respond_to?(:to_str)
fork_log << "----- Script Output -----\n"
fork_log << output
fork_log << "\n----- End Script Output -----"
end
rescue ScriptError, StandardError => e
fork_log << "----- Script Error Output -----\n"
fork_log << "Error in '#{scheduler.course.name}' updater: #{e.message}\n"
fork_log << e.backtrace.join("\n\t")
fork_log << "\n---- End Script Error Output -----"
end
write.print fork_log
end

write.close
result = read.read
Process.wait2(pid)
log << result
rescue StandardError => e
log << "----- Error Output -----\n"
log << "Error during execution: #{e.message}\n"
log << e.backtrace.join("\n\t")
log << "\n---- End Error Output -----"
end
log << "\nCompleted running action."
log
end
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Critical security and reliability improvements needed in execute_action

Several critical issues need to be addressed in the execution logic:

  1. Unsafe require of user input
  2. No timeout on forked process
  3. Potential file descriptor leaks
  4. No proper process cleanup

Consider this improved implementation:

def execute_action(scheduler)
  action_path = Rails.root.join(scheduler.action).to_path
  read, write = IO.pipe
  log = "Executing #{action_path}\n"
+ result = { status: :success, message: "" }

  begin
+   Timeout.timeout(30) do  # Add timeout
      pid = fork do
        read.close
-       mod_name = action_path
        fork_log = ""
        begin
-         require mod_name
+         # Load file content without require
+         eval(File.read(action_path), binding, action_path, 1)
          output = Updater.update(scheduler.course)
          if output.respond_to?(:to_str)
            fork_log << "----- Script Output -----\n"
            fork_log << output
            fork_log << "\n----- End Script Output -----"
          end
        rescue ScriptError, StandardError => e
          fork_log << "----- Script Error Output -----\n"
          fork_log << "Error in '#{scheduler.course.name}' updater: #{e.message}\n"
          fork_log << e.backtrace.join("\n\t")
          fork_log << "\n---- End Script Error Output -----"
        end
        write.print fork_log
+       exit!(0)
      end

      write.close
      result = read.read
-     Process.wait2(pid)
+     _, status = Process.wait2(pid)
+     unless status.success?
+       result[:status] = :error
+       result[:message] = "Process exited with status #{status.exitstatus}"
+     end
      log << result
    end
+ rescue Timeout::Error
+   Process.kill('TERM', pid) rescue nil
+   result[:status] = :error
+   result[:message] = "Execution timed out after 30 seconds"
  rescue StandardError => e
+   result[:status] = :error
+   result[:message] = e.message
    log << "----- Error Output -----\n"
    log << "Error during execution: #{e.message}\n"
    log << e.backtrace.join("\n\t")
    log << "\n---- End Error Output -----"
  ensure
    read.close rescue nil
    write.close rescue nil
  end
  
  log << "\nCompleted running action."
- log
+ result.merge(log: log)
end
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
def execute_action(scheduler)
action_path = Rails.root.join(scheduler.action).to_path
# https://stackoverflow.com/a/1076445
read, write = IO.pipe
log = "Executing #{action_path}\n"
begin
pid = fork do
read.close
mod_name = action_path
fork_log = ""
begin
require mod_name
output = Updater.update(scheduler.course)
if output.respond_to?(:to_str)
fork_log << "----- Script Output -----\n"
fork_log << output
fork_log << "\n----- End Script Output -----"
end
rescue ScriptError, StandardError => e
fork_log << "----- Script Error Output -----\n"
fork_log << "Error in '#{scheduler.course.name}' updater: #{e.message}\n"
fork_log << e.backtrace.join("\n\t")
fork_log << "\n---- End Script Error Output -----"
end
write.print fork_log
end
write.close
result = read.read
Process.wait2(pid)
log << result
rescue StandardError => e
log << "----- Error Output -----\n"
log << "Error during execution: #{e.message}\n"
log << e.backtrace.join("\n\t")
log << "\n---- End Error Output -----"
end
log << "\nCompleted running action."
log
end
def execute_action(scheduler)
action_path = Rails.root.join(scheduler.action).to_path
read, write = IO.pipe
log = "Executing #{action_path}\n"
result = { status: :success, message: "" }
begin
Timeout.timeout(30) do # Add timeout
pid = fork do
read.close
fork_log = ""
begin
# Load file content without require
eval(File.read(action_path), binding, action_path, 1)
output = Updater.update(scheduler.course)
if output.respond_to?(:to_str)
fork_log << "----- Script Output -----\n"
fork_log << output
fork_log << "\n----- End Script Output -----"
end
rescue ScriptError, StandardError => e
fork_log << "----- Script Error Output -----\n"
fork_log << "Error in '#{scheduler.course.name}' updater: #{e.message}\n"
fork_log << e.backtrace.join("\n\t")
fork_log << "\n---- End Script Error Output -----"
end
write.print fork_log
exit!(0)
end
write.close
result = read.read
_, status = Process.wait2(pid)
unless status.success?
result[:status] = :error
result[:message] = "Process exited with status #{status.exitstatus}"
end
log << result
end
rescue Timeout::Error
Process.kill('TERM', pid) rescue nil
result[:status] = :error
result[:message] = "Execution timed out after 30 seconds"
rescue StandardError => e
result[:status] = :error
result[:message] = e.message
log << "----- Error Output -----\n"
log << "Error during execution: #{e.message}\n"
log << e.backtrace.join("\n\t")
log << "\n---- End Error Output -----"
ensure
read.close rescue nil
write.close rescue nil
end
log << "\nCompleted running action."
result.merge(log: log)
end

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Missing/invalid schedulers generate many exceptions
2 participants