internal relayout method called with undefined

We have observed a relayout failure immediately after this warning:

WARN: Relayout fail. undefined undefined
Non-Error promise rejection captured with value: undefined

coming from: https://github.com/plotly/plotly.js/blob/24b6f75e2d3b58cb1cd9cdd850894720404373d3/src/plot_api/plot_api.js#L1774

I'm not sure which exact circumstances triggered this failure, but the relayout internal function probably should not reject if astr is undefined, as this simply means there is nothing to update (recording the warning seems fine as it helps to diagnose call sites which are not correctly omitting the relayout, but it should not cause the function to fail).

I suggest that this branch should return successfully after logging a warning if astr is undefined / null.

It would also be useful for diagnosing the root cause further if the warning could include a stack trace.

Plotly.js version: 2.26.2

从 src/plot_api/plot_api.js 第 1774 行附近开始，跟踪 astr 的 undefined 或 null 值如何到达内部 relayout 函数。验证警告行为，并确认此路径能够成功完成，而不是被拒绝；考虑 stack trace 将如何帮助诊断，并在定义完成条件之前检查相关的 relayout 行为。