Elasticity | A framework based on the Scheduler-Agent-Supervisor pattern | Job Scheduling library

I am getting an error message:

It is doable through the AWS Console or AWS CLI, but not through Terraform, based on a quick test.

Changing the volume_size parameter from 10 to 20 in an aws_instance definition such as the one below caused a destroy/re-create of the instance. Using terraform 0.15.0

If you need to keep managing the instance with Terraform, consider the option of (1) performing the modification outside of Terraform (aws console or CLI) and (2) importing the modified resource back into terraform.

In the second section of the answer I describe a simple example of re-importing into Terraform the state of the aws_instance modified through the console. Disclaimer: do this at your own risk and after suitable testing in a non-production environment. Read carefully the warnings in the documentation for the terraform import command

Looks like collision behavior doesn't like .ellipse type when the views are positioned exactly on top of each other.

Running your code a few times gives different results (as expected)... sometimes, all 5 views end up in a full vertical stack, other times it ends up with some overlap, and other times (after waiting a few seconds) the views settle with a couple visible and the others way below the bottom of the view - I've seen their y-positions get to > 40,000.

I made a few modifications to your code to see what's happening...

I added more views and gave each one a shape layer showing the ellipse bounds.

Then, instead of starting with them all at identical positions, I created a couple "rows" so it looks like this:

Then, on each tap, I reset the original positions and toggle the UIDynamicItemCollisionBoundsType between ellipse and rectangle, and then call addAnimatorAndBehaviors() again.

Here's how it looks on sample .ellipse run:

and on sample .rectangle run:

As we can see, the .ellipse bounds are being used.

Here's the code I used to play with this:

Instead of @span you should insert the range of columns the \cmidrule is supposed to span:

Changing the parameter names is a bit messy, but you can do the do.call() syntax to build a named list. You can also use formalArgs() to get the names of the arguments of your function

So you could do something like

Use a collections.Counter:

You need to put your return statement outside of your loop.

I think placing return inside your loop is exiting the function entirely, which is why the first result is being generated. From datamentor.io, "If it is not the last statement of the function, it will prematurely end the function bringing the control to the place from which it was called."

Did you find the example in the documentation here: http://www.pymunk.org/en/latest/pymunk.html#pymunk.Body.velocity_func ?

1. You need to define a custom velocity function somewhere, and then set it on the body you want it. So preferably you define it before you create the bodies. In this function you can call the existing default velocity function (pymunk.Body.update_velocity) if you want, but that is not a requirement. It depends on if you want to write all code to update velocity of the body yourself, or if you want to just modify it a bit with the existing code as a base. Since you only want to modify the damping I think its easiest to call the default function.

2. When you call the default v function you can send in the same gravity unmodified as you get it in your custom function.

3. dt is the delta time. I see now the docs could be improved here, I will make a note. So the dt is the same value as the dt sent to space.step(dt) function in your simulation loop.

All in all, I think something like this would do (you just need to adjust the calculation of modified_damping to the logic you want):

So it took me some time, and I am not 100% sure still of why it works because I think im finding the JavaScript angles system a bit tricky, but: