dummy_image | JS only dummy image | Runtime Evironment library

Thanks for all your suggestions, in the end I did not find solution to the error but I did come to a solution for the workflow. As AMargheriti pointed out, there's always dataflow templates. By creating a custom template of the code I was able to trigger the flow using a cloud function. Useful documentation is the create dataflow template, the running templates page and lastly this solution because the suggested API on the running templates page does not allow setting a region where to run the template whereas dataflow().projects().locations().templates().launch() does allow this option to be added.

What I am understanding is that you have many images that you want to store in RAM. The first question you need to ask yourself is if you actually need to store them all at the same time? For example, can you read one, do some processing, and then only keep the result of the processing before reading the next image?

When it comes to the actual storage, I do not understand why you need the var1 variable. Isn't image sufficient? If the point of var1 is to have all your images with the same shape, then why cannot you use pad? For example, imageNew = numpy.pad(image, [(0, x - y) for x, y in zip(arr1.shape, image.shape)]).

If you cannot use numpy.pad, then would simply arr1[:image.shape[0], :image.shape[1], :] = image work for you?

If you want to do it with loops, then use numba.

For any children, if they have a set cursor property, that's what's going to apply, regardless of specificity of rules set on parent for that property.

If you want the specificity of two rules to be compared (and the strongest one to apply), they both need to both apply to the same element.

For example:

It is safe to assume that by fitting you mean covering all of the width. This is because

1. You typically do not know the height just by using col-sm-6 or col-md-6 or col-lg-4.
2. There is a huge probability of loss in aspect ratio of the image if you try to resize it according to your own will.

Use for fitting the column. This will fit your image width-wise into the column and will automatically modify the height (keeping the aspect ratio in mind), so you do not have to worry about image getting illogically resized.

The localStorage object stores data with no expiration date. The data will not be deleted when the browser is closed, and will be available the next day, week, or year. you need to forcefully remove the localStorage like

It is rolled back when test is annotated with @Transactional.

1. Does using @Transactional on a test class mean absolutely nothing gets written to the db ? My other tests work fine ! They do more or less the same job.

Please post your other tests for more details.

1. If annotating a test class with @Transactional means there's no control on data persistence, why do people even use it on their tests ?

To prevent filling database with test data.

1. Even if the data is not written to the db, they are persisted, right ? Doesn't calling repository.delete should delete that item from the persistence context ?

Where do you check if an item was deleted from the persistence context?

1. The code that doesn't affect the db (delete) is located in the Service layer. It's called from within the Controller that I'm testing, not the test class. I expected it to work regardless of the fact that test class is annotated with @Transacational or not.

Every method in the test is wrapped with Spring transaction so data may be not committed until the test ends.

Check for detailed answers:

• Should my tests be @Transactional?

• Spring boot test @Transactional not saving

You are base64 decoding the string, using ImageIO to create a BufferedImage, converting it back to a PNG, and re-base64 encoding this result.