Changes in subsequent versions

Ray Libraries (Data, Train, Tune, Serve) Ray Serve
1

Hi, I was wondering how may I find the specific changes of ray serve in subsequent versions. I have a properly working ray serve project on versions 1.4.0 to 1.8.0. However versions 1.9.0 and further does not work for me and I get errors like this one:

deployment_def = cloudpickle.loads(serialized_deployment_def)
ModuleNotFoundError: No module named 'my_deployment'

How severe does this issue affect your experience of using Ray?

  • None: Just asking a question out of curiosity
  • Low: It annoys or frustrates me for a moment.
  • Medium: It contributes to significant difficulty to complete my task, but I can work around it.
  • High: It blocks me to complete my task.
2

Hi @Matin_Yousefabadi, public APIs are annotated in their docstring and documented here: Serve: Scalable and Programmable Serving — Ray 1.11.0, they should not change without warning and non-alpha/non-beta public APIs should not change except between major releases (1.X->2.X).

We also publish some release notes on GitHub: Release Ray-1.11.0 · ray-project/ray · GitHub.

Pickling a deployment definition is not considered a public API – are you calling this code directly or is it part of a stack trace in another API call?