TypeError: can't pickle _thread.RLock objects

[JeongChanwoo]

I tried transforming it by assigning a model to a class variable and predicting the PAD dynamically.

Since the prophet model file is in the form of storing the model in a class variable, I expected tensorflow to be possible as well.

The model I assigned is a tensorflow based model.

In the model Python file, i saved the model trained in the train process in the class variable model under class.

However, an error occurs in the process of putting the result in the queue after the train.

PAD_ANOMA | Traceback (most recent call last):
PAD_ANOMA |   File "app.py", line 214, in <module>
PAD_ANOMA |     train_model(initial_run=True, data_queue=predicted_model_queue)
PAD_ANOMA |   File "app.py", line 202, in train_model
PAD_ANOMA |     data_queue.put(PREDICTOR_MODEL_LIST)
PAD_ANOMA |   File "<string>", line 2, in put
PAD_ANOMA |   File "/opt/conda/envs/prophet-env/lib/python3.7/multiprocessing/managers.py", line 818, in _callmethod
PAD_ANOMA |     conn.send((self._id, methodname, args, kwds))
PAD_ANOMA |   File "/opt/conda/envs/prophet-env/lib/python3.7/multiprocessing/connection.py", line 206, in send
PAD_ANOMA |     self._send_bytes(_ForkingPickler.dumps(obj))
PAD_ANOMA |   File "/opt/conda/envs/prophet-env/lib/python3.7/multiprocessing/reduction.py", line 51, in dumps
PAD_ANOMA |     cls(buf, protocol).dump(obj)
PAD_ANOMA | TypeError: can't pickle _thread.RLock objects

[sesheta]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[sesheta]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

[sesheta]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

[sesheta]

@sesheta: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.