Larry

I will take a look at this issue few days

> Are there any updates or potential timelines for this issue? I am currently busy with some urgent things, it may take a while to locate this problem. If this...

> Thank you for your response. As described in the initial [issue](https://discuss.ray.io/t/new-placement-groups-not-being-created-after-initial-round/7314), I am able to work around the issue by merging sequential tasks together and using node_strategy. That said,...

cc @rkooo567 @scv119 Then I'll take a look at this issue first before this weekend. If there is no result next week you can assign it to someone else.

 The problem is here. After this change it is solved. I will mention PR and supplementary test cases in the past two days.

@jjyao There are too many nested `[]\{}` in this new scheme API. I think it is too complicated and will make it difficult for users to use. **1. for the...

@jjyao I support plan 1 now. I have organized the new format of API and updated it in the ISSUE summary. 

There is an error in your example above. The following is correct. You can use the following。 ``` ray start --head --resources='{"CustomResource3": 1, "CustomResource2": 2}' ``` 

1. There is an extra `}` in this error message and we will fix it. 2. You try to remove the space in the middle. 

I will try to find a Windows environment and use PowerShell to reproduce the issue you encountered. This will take a few days to complete.