service | Service encapsulates an object which executes a bit of code | Code Editor library

Based on the comments.

The issue was that t2.micro instance was used. The instance has only 1 vCPu and 1GB of ram. This was not enough to run 5 docker containers. Changing instance type to t2.large with 8GB ram and 2 vCPUs solved the problem.

docker-compose allows to specify cpu and memory limits. Maybe you can set them up to keep your containers resource requirements in check.

You function getTab seems not right, you are currently trying to query on the url. Not on the query options. The following function should work.

The error messages states that the service account does not have the permission compute.disks.list.

What permissions does the role roles/resourcemanager.organizationViewer have?

You can find the cost per resource in the cost management tab in the Azure portal then in cost analysis

You could also see the amount of messages in the service bus metrics tab, just filter by incoming messages and there you will see them, this metric is available only for 30 days so you won't be able to see previous months metrics unless you saved them in a storage account or any SIEM.

Only some user claims provided by the IDS will be passed into the User.claims collection. You need to explicitly map those additional claims in the client application, using code like:

In your situation, how about the following modification? I thought that when setValues is used instead of appendRow, the process cost will be able to be reduced a little. Ref

TCP/IP connections are designed to be long-lived streaming connections (built on top of the out-of-order, no-guarantee, packet-based IP protocol).

That means that is.read(bytes) does exactly what the spec says it will: It will wait until at least 1 byte is available, OR the 'end of stream' signal comes in. As long as neither occurs (no bytes arrive, but the stream isn't closed), it will dutifully block. Forever if it has to.

The solution is to either [A] pre-send the size of the file, and then adjust the loop to just exit once you've received that amount of bytes, or [B] to close the stream.

To close the stream, close the socket. It kinda sounds like you don't wanna do that (that you are multiplexing multiple things over the stream, i.e. that after transfering a file, you may then send other commands).

So, option A, that sounds better. However, option A has as a prerequisite that you know how many bytes are going to come out of inputStream. If it's a file, that's easy, just ask for its size. If it's streamed data, that would require that, on the 'upload code side', you first stream the whole thing into a file and only then stream it over the network which is unwieldy and potentially inefficient.

If you DO know the size, it would look something like (and I'm going to use newer APIs here, you're using some obsolete, 20 year old outdated stuff):

Starting with 6.4 RC5 (which is the version you run as of this writing and should provide this in your original post):

The collection of thymeleaf user interface template pages are no longer found in the context root of the web application resources. Instead, they are organized and grouped into logical folders for each feature category. For example, the pages that deal with login or logout functionality can now be found inside login or logout directories. The page names themselves remain unchecked. You should always cross-check the template locations with the CAS WAR Overlay and use the tooling provided by the build to locate or fetch the templates from the CAS web application context.

https://apereo.github.io/cas/development/release_notes/RC5.html#thymeleaf-user-interface-pages

Please read the release notes and adjust your setup.

All templates are listed here: https://apereo.github.io/cas/development/ux/User-Interface-Customization-Views.html#templates

You have to make the property overridable, so make it virtual: