tinker | Laravel chatbot the ability to try chatbot | Chat library

I updated laravel to version 8.

I have a problem when I run this method (with the migrate command):

I'm using Laravel 7.3 and need to update to 8 because of plugins needings

I'm reading the documentation but as I'm a noob as in English like in computing I have some errors and problems

First of all, I followed this :

Update the following dependencies in your composer.json file:

I am coding a solution program for leetcode. I have encountered memory read errors and segmentation fault errors which I am unable to resolve. I have tried tinkering with the code to try and remove the errors.
For example: in the numIslands function's last lines, I had tried declaring coordinates as an array rather than a pointer but the results did not change.
*(last + 1) = *(coordinates + 1); does not seem to work at all in the numIslands function. I am totally blank about what to do next.

I built a Net Core 5 Web API in .Net 5 Docker Image and was searching for a way to run create container from that image on ARM v7 Processors like Tinker Board with Debian on it.

Here is a crude example of the type of code I would like to use libtool's libltdl dlpreopening with:

https://github.com/EmmaJaneBonestell/dlopen-sample

I wish to be able to rewrite various projects that use libdl functions ( dlopen, dlsym, etc ), to instead use libtool's libltdl dlpreopening/preloading mechanism. From libtool's documentation, it will instead link the objects at compile time, resulting in truly static executables. It was intended for systems that do not support dynamic loading.

If you use it to compile and link these objects, libtool will run some of its scripts, and create the necessary data structures, and I believe perform mangling and demangling, to allow for duplicate symbol names.

Even after looking at the examples in libtool's source code, reading its entire documentation, and looking at relevant tests from the test-suite (e.g. tests 118 & 120), I've been unable to do so.

Outside of libtool itself, there is essentially no mention of this functionality anywhere I could find. I did manage to see it used in a too-complex-for-me manner in Graphviz, but there's little documentation on that either.

I'm really not much of a programmer, more of a tinkerer. It's easy enough for me to use libltdl for a wrapper for standard dlopen/dlsym.

I think my main issue is figuring out how I can return a proper handle for a preopened object, though I may be doing other things incorrectly.

The documentation states that lt_dlopen can work on preloaded static modules, but it doesn't seem to accept any possible reference to it I could imagine.

I would also prefer not to have to even invoke libtool, but c'est la vie.

I didn't bother including any of what I've tried code wise (on the example) because I've tried such a mess of things that I feel it would really just be confusing to show it.

Current libtool documentation: https://www.gnu.org/software/libtool/manual/libtool.html

I recently performed a rather large update to this web app, and for the most part it went off without a hitch... Until the app tries to send an SMS notification from staging/production.

The upgrade from laravel 7.x to 8.x was quite simple and straightforward. At the same time we also installed Laravel Horizon. Everything went according to plan, and all works fine locally.

When we deploy to staging/production however, queued SMS notifications fail with the following exception:

ReflectionException: Class Http\Adapter\Guzzle6\Client does not exist in /home/forge/dev.example.com/releases/20210609194554/vendor/laravel/framework/src/Illuminate/Container/Container.php:836

Looking in the stack trace we can see that Nexmo is the culprit:

#5 /home/forge/dev.example.com/releases/20210609194554/vendor/nexmo/laravel/src/NexmoServiceProvider.php(150): Illuminate\Foundation\Application->make()

However in our composer.json file we are requiring Guzzle 7 with the following:

"guzzlehttp/guzzle": "^7.3",

It is worth mentioning again at this point, I have no issues sending SMS locally, the main difference between local and staging environments is that locally I use Laravel Valet and Staging uses Laravel Envoyer.

What I've tried so far:

• Changing "guzzlehttp/guzzle": "^7.3" to "guzzlehttp/guzzle": "^6.5|^7.3"
• Running php artisan horizon:purge and php artisan horizon:terminate both manually and in a deployment hook.
• Restarting the laravel horizon daemon on forge.
• trying php artisan queue:restart
• running composer dump-autoload and composer dump-autoload -o
• deleting composer.lock and the vendor/ directory from current/ then running composer install
• Restarting PHP, Nginx, and eventually the entire server :(

and more...

Any help is greatly appreciated

UPDATE Below:

Complete composer.json:

UPDATE: it seems i found a bug. Here the ticket on github i created. David will solve the problem during the day.

I simply tried to follow the Heroku guide to create a simple laravel app (even without db connection) and deploy on a Heroku app. However, it appears that when using Composer 2 there are problems (see log here). Rolling back to Composer 1 is all right. In the Heroku documentation it is indicated that Composer 2 is supported but obviously I am doing something wrong since it gives me an error.

when I push modifications to Heroku i get this error:

Recently, I've been tinkering around with pygame. I noticed that even if I've imported pygame, I can still import pygame.local and pygame.sprite (from... import... to reduce the words I need to type in later). What are the relationships between pygame and pygame.SOMETHING? I thought it was just one pygame module, and now I'm a bit confused. Please give me an explanation or direct me to some articles. Any help would be appreciated!

I'm getting this error while installing Laravel Scout:

Problem 1 - laravel/scout[v9.1.0, ..., 9.x-dev] require illuminate/bus ^8.0 -> found illuminate/bus[v8.0.0, ..., 8.x-dev] but these were not loaded, likely because it conflicts with another require. - Root composer.json requires laravel/scout ^9.1 -> satisfiable by laravel/scout[v9.1.0, 9.x-dev].

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

Here is my composer.json file: