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 関数に到達するまでを追跡してください。警告の動作を確認し、この経路が reject されるのではなく正常に完了することを確認してください。stack trace が診断にどのように役立つかを検討し、完了を定義する前に関連する relayout の動作を確認してください。