Javascript 作业完成后更新控制器

我有一个控制器动作，它触发了一个延迟的作业，在执行后有一个钩子，在钩子中触发了另一个延迟的作业

我需要在所有作业完成后渲染视图，并在作业仍在运行时向用户显示微调器

这些工作如下所示：

class DuplicateShipmentJob < ApplicationJob
  after_perform do |job|
    shipment = job.arguments.first[:shipment]
    shipment_ids = Shipment.where(public_id: shipment.public_id).map(&:id)
    bulk_shipment_process = BulkShipmentProcess.new
    bulk_shipment_process.shipment_ids = shipment_ids
    bulk_shipment_process.user = shipment.user

    if bulk_shipment_process.save
      Shipment.where(public_id: shipment.public_id).each do |shipment|
        shipment.bulk_shipment_process_id = bulk_shipment_process.id
      end
      BulkShipmentsProcessor.delay.process_bulk_shipments(args)
    end
   end

 def perform(shipment:, label_count:)
   label_count.times do
     duplicated_shipment = shipment.dup
     duplicated_shipment.package = shipment.package.dup
     duplicated_shipment.save!
   end
  end
 end

class ShipmentsController < ApplicationController
 def replicate_shipment
  @shipment = build_shipment
  @shipment.save!
  DuplicateShipmentJob.perform_later(
    shipment: @shipment,
    label_count: @shipment.create_multiple_shipments.to_i - 1,
  )
  # here i need to wait until the process instance appears in the DB
  @bulk_shipment_process = BulkShipmentProcess.where(id: Shipment.last.bulk_shipment_process_id) 
  redirect_to bulk_shipment_process_path(@bulk_shipment_process)
 end
end

class DuplicateShipmentJob

最好的方法是什么

我在向DB发出ajax请求和设置动作电缆以监听作业结果之间犹豫不决

控制器如下所示：

class DuplicateShipmentJob < ApplicationJob
  after_perform do |job|
    shipment = job.arguments.first[:shipment]
    shipment_ids = Shipment.where(public_id: shipment.public_id).map(&:id)
    bulk_shipment_process = BulkShipmentProcess.new
    bulk_shipment_process.shipment_ids = shipment_ids
    bulk_shipment_process.user = shipment.user

    if bulk_shipment_process.save
      Shipment.where(public_id: shipment.public_id).each do |shipment|
        shipment.bulk_shipment_process_id = bulk_shipment_process.id
      end
      BulkShipmentsProcessor.delay.process_bulk_shipments(args)
    end
   end

 def perform(shipment:, label_count:)
   label_count.times do
     duplicated_shipment = shipment.dup
     duplicated_shipment.package = shipment.package.dup
     duplicated_shipment.save!
   end
  end
 end

class ShipmentsController < ApplicationController
 def replicate_shipment
  @shipment = build_shipment
  @shipment.save!
  DuplicateShipmentJob.perform_later(
    shipment: @shipment,
    label_count: @shipment.create_multiple_shipments.to_i - 1,
  )
  # here i need to wait until the process instance appears in the DB
  @bulk_shipment_process = BulkShipmentProcess.where(id: Shipment.last.bulk_shipment_process_id) 
  redirect_to bulk_shipment_process_path(@bulk_shipment_process)
 end
end

class ShipmentsController

我首先建议将作业存储在数据库中，并在与触发它的用户相关的相关作业上循环，并对其进行标识

提交作业后，触发微调器，然后尝试硬编码一个从数据库检索相关作业的开放循环，并检查其状态是否为“完成”：

        loop do
          status = DelayedJob.find(JOB_ID)
          case status
          when 'DONE' then return true
          when 'PROCESSING' then sleep(10)
          else raise(JobRunFailed, "Job run failed with: #{status}")
          end
        end

，取下微调器并输出所需的相关信息

当然，如果您愿意，也可以在应用程序的前端硬编码开环逻辑

因此，要回顾一下这些步骤：

存储后在数据库中标识相关作业

在此处触发“等待”微调器，在此处重定向到批量装运\u进程\u路径

在标识的作业上循环，直到标记为

完成

或

执行

断开循环后更改相应的接口

---

第3步和第4步可能只是与前端相关的步骤，与

ShipmentsController

没有任何关系。

我首先建议将作业存储在数据库中，并在与触发它的用户相关的相关作业上循环并识别它

提交作业后，触发微调器，然后尝试硬编码一个从数据库检索相关作业的开放循环，并检查其状态是否为“完成”：

        loop do
          status = DelayedJob.find(JOB_ID)
          case status
          when 'DONE' then return true
          when 'PROCESSING' then sleep(10)
          else raise(JobRunFailed, "Job run failed with: #{status}")
          end
        end

，取下微调器并输出所需的相关信息

当然，如果您愿意，也可以在应用程序的前端硬编码开环逻辑

因此，要回顾一下这些步骤：

存储后在数据库中标识相关作业

在此处触发“等待”微调器，在此处重定向到批量装运\u进程\u路径

在标识的作业上循环，直到标记为

完成

或

执行

断开循环后更改相应的接口

---

步骤3和步骤4实际上可能只是与前端相关的步骤，与

ShipmentsController

没有任何关系。

我最终得到了以下解决方案

我将

BulkShipmentProcess

的实例化移动到控制器，保存后，重定向到此实例的

show

操作，并触发第一个作业，将该实例作为作业参数传递

在作业内部，第二个作业被触发，一些属性被分配给

BulkShipmentProcess

实例

在

bulk\u shipping\u process/id

页面上，JS正在轮询DB以获得分配的新属性，并在成功后呈现这些属性

控制器：

class ShipmentsController < ApplicationController
  def replicate_shipment
    @shipment = build_shipment
    @shipment.save!
    @bulk_shipment_process = BulkShipmentProcess.new()
    @bulk_shipment_process.save
    if @bulk_shipment_process.id?
       DuplicateShipmentJob.perform_later(@bulk_shipment_process)
       redirect_to bulk_shipment_process_path(@bulk_shipment_process)
    else
      flash.now[:error] = "error"
      render :new
    end
  end
end

---

我最终得到了以下解决方案

我将

BulkShipmentProcess

的实例化移动到控制器，保存后，重定向到此实例的

show

操作，并触发第一个作业，将该实例作为作业参数传递

在作业内部，第二个作业被触发，一些属性被分配给

BulkShipmentProcess

实例

在

bulk\u shipping\u process/id

页面上，JS正在轮询DB以获得分配的新属性，并在成功后呈现这些属性

控制器：

class ShipmentsController < ApplicationController
  def replicate_shipment
    @shipment = build_shipment
    @shipment.save!
    @bulk_shipment_process = BulkShipmentProcess.new()
    @bulk_shipment_process.save
    if @bulk_shipment_process.id?
       DuplicateShipmentJob.perform_later(@bulk_shipment_process)
       redirect_to bulk_shipment_process_path(@bulk_shipment_process)
    else
      flash.now[:error] = "error"
      render :new
    end
  end
end

---

您可以使用DuplicateShipmentJob.new.perform（）而不是稍后执行。@fidato，我使用

perform later

，因为我希望它异步运行。您可以使用DuplicateShipmentJob.new.perform（）而不是稍后执行。@fidato，我使用

perform later

，因为我希望它异步运行。好主意。我使用

Delayed:：Backend:：ActiveRecord:：Job

。我怎样才能从中获取状态？这是你必须自己去挖掘的东西。也许这是一个好的开始：好主意。我使用

Delayed:：Backend:：ActiveRecord:：Job

。我怎样才能从中获取状态？这是你必须自己去挖掘的东西。也许这是一个好的开始：