app_version | Rails plugin for managing your site 's version number | Plugin library

Have you tried using GIT_BRANCH just like this

You can use any session name you come up with. For example, you might write:

If you want to expand the argument first and then stringify it, you need an extra indirection, try this:

I was missing the App Manager role on the API key as suggested by Paulw11.

After regenerating a new API key with this role, it worked.

Note: App Manager role on the user account is not sufficient and it will not work if you are automating the release part (changelogs, release notes etc.)

One way of achieving this is to split your application into multiple routers as shown in the example for bigger applications in the FastAPI documentation.

Here's an example fitting your case:

Values that are emitted, are only pushed to current subscribers. In your case, it's impossible to have a current subscriber since you are calling next in the constructor of the service.

Late subscribers will not receive prior emissions.

However, you want late subscribers to receive prior emissions, you can use ReplaySubject instead of plain Subject.

audio_service runs your BackgroundAudioTask in a separate isolate. In the README, it is put this way:

Note that your UI and background task run in separate isolates and do not share memory. The only way they communicate is via message passing. Your Flutter UI will only use the AudioService API to communicate with the background task, while your background task will only use the AudioServiceBackground API to interact with the UI and other clients.

The key point there is that isolates do not share memory. If you set a "global" variable in the UI isolate, it will not be set in the background isolate because the background isolate has its own separate block of memory. That is why your global queue variable is null. It is not actually the same variable, because now you actually have two copies of the variable: one in the UI isolate which has been set with a value, and the other in the background isolate which has not (yet) been set with a value.

Now, your background isolate does "later" set its own copy of the queue variable to something, and this happens via the message passing API where you pass the queue from the UI isolate into updateQueue and the background isolate receive that message and stores it into its own copy of the variable in onUpdateQueue. If you were to print out the queue after this point it would no longer be null.

There is also a line in your onStart where you are attempting to set the queue, although you should probably delete that code and let the queue only be set in onUpdateQueue. You should not attempt to access the queue in onStart since your queue won't receive its value until onUpdateQueue. If you want to avoid any null pointer exception before its set, you can initialise the queue in the background isolate to an empty list, and it will eventually get replaced by a non-empty list in onUpdateQueue without ever being null.

I would also suggest you avoid making queue a global variable. Global variables are generally bad, but in this case, it may actually be confusing you into thinking that that queue variable is the same in both the UI and the background isolate when in reality each isolate will have its own copy of the variable perhaps with different values. Thus, your code will be clearer if you make two separate "local" variables. One inside the UI and one inside the background task.

One more suggestion is that you should note that the methods in the message passing API are asynchronous methods. You should wait for the audio service to start before you send messages to it, such as setting the queue. AND you should wait for the queue to be set before you try to play from the queue:

I am answering your question based on my similar experience.

But for accurate result i suggest to use php profiling tools like KCachegrind to find out which part of your code consumes more time to execute.

i Think The problem is With Carbon Which was Mine.

Carbon Object Takes Long time to instantiate (is Slow).

i have refactored my code to not use carbon for date compare (make it in DBMS) and everything speeds up.

I Think Your Problem is, you have fetched a lot of records from DB, and loop over them with foreach :

Not directly. If you look at the API documentation for the EnvVarSource object, you can see that a limited number of fields are supported for the downward API; generally only the metadata fields, the service-account name, the dynamic IP and node information, and the resource limits.

In the context of the file you show, the file path is fixed and you don't need a dynamic lookup. Since each container has an isolated filesystem, it's a little unlikely you'll actually change this path in different deployments, and it will work to just specify that path directly: