iseed | Frontend project template , with full test | Continuous Deployment library

I encountered the same problem recently (specifically, using Laravel Passport).

We were also making use of mounted secrets, and noticed that every 10-30 minutes our application would hang and time out after 60s (our configured timeout in Cloud Run). One of my colleagues noticed that every time our application started hanging, one of the first things to start failing was the reading of the mounted secret.

I asked about this behaviour in the Google Cloud Community Slack workspace, and one of the Cloud Run PM's replied indicating that they were rolling back a recent implementation change.

I suspect that you encountered the same issue that we did (running our application in GKE also worked fine).

If it's at all possible, switch to mounting your secrets into your environment. This should resolve the issues of your application hanging.

The code is not conforming for two reasons:

• the function result value in aggregate_data is not defined before being referenced.

• in the main program, the pointer component x of the elements of pointers have undefined pointer association status when passed to the aggregate_data procedure, on account of the first actual argument in the calls to associate_pointer not having the TARGET attribute.

(You can call a procedure with a dummy argument that has the TARGET attribute with a corresponding actual argument that does not, but when you do, pointers associated with the dummy argument (such as ptr inside associate_pointer) become undefined when execution of the procedure completes.)

The errors in the program can be corrected by giving the parent variable in the main program the TARGET attribute, and by sticking an appropriate assignment statement prior to the loop in aggregate_data.

Beyond correctness, the only difference between the two loops is in the actual argument passed to aggregate_data - one loop passes an array designated by an allocatable component, one loop passes a array designated by a pointer component. The procedure takes that array argument as an assumed shape array dummy argument without CONTIGUOUS - given typical implementation of assumed shape arrays there's no need for the compiler to do anything different passing pointer vs allocatable.

(If the dummy argument of aggregate_data was explicitly or implicitly contiguous, there may be a need for the compiler to copy the pointer array prior to the call as pointers can be associated with non-contiguous arrays. Allocatable arrays are always contiguous.)

Both loops write their result to an non-target allocatable array of different kind to the actual argument components - so there cannot be any aliasing across the assignment statement.

Neither actual argument is being modified within the loops, so potential aliasing issues associated with the pointer arguments designating the same array in different iterations are moot (besides which, from the compiler's perspective - that's a guarantee that is on the head of the programmer - it doesn't have to care).

All up, I'd expect the same machine instructions to be issued for the two loops. Similar timing is unsurprising.

Results may differ if different work is done in the loops - if aliasing or contiguity comes into play.

Where the approaches will differ is in the data copying required to set the allocatable array components arguments up. But that is (intentionally?) outside that timing regime.

As of Fortran 2003 on (which this code requires), do not use POINTER's unless you need reference semantics.

This is gdb's backtrace, it doesn't say the segmentation fault occurs before main(), but after main(), slightly after queueInit() has been called:

the maddhatter/laravel-fullcalendar dependency need the version 5 of illuminate/support.

So you can't update laravel with this dependency. Moreover, it seems that this project was not updated since 3 years

But a fork exist here.And it works with laravel for 5,6 and 7 https://github.com/nelkasovic/laravel-full-calendar/blob/master/composer.json#L15

int sum1 = A + B; in the do/while loop declares a new sum1 that hides int sum1 = 0; as a result, nothing ever changes the outer sum1 from 0.

change

As far as I see from your stack trace, the command fails to create a views directory (./resources/views/vendor/l5-swagger).

Note: chown -R www-data:root . - this command can create some new problems..

After that command, owner is www-data (but you start artisan commands as serge).

After that command, group is root (but serge may not be part of that group).

You have to verify that your user (serge) has proper permissions there (./resources/views, ./resources/views/vendor).

To check current permissions run: ls -la ./resources, ls -la ./resources/views, and ls -la ./resources/views/vendor (if vendor exists already)

Maybe you need something like: sudo chmod -R serge.www-data (serge - owner, www-data - group)

However, it mostly depends on your specific setup and desired result.