log-viewer | 💻View terminal logs in browser | Command Line Interface library

I've been trying to install lorisleiva/laravel-search-string but I keep on getting this error. Need this library for the search functionality. Even composer update gives the same error. (just the problem 2 in case of update). I have added the composer.json down below as well. Hope this will okay. Need some guidance.

I'm trying to update from 5.8 to any version 6 Laravel. I've updated the PHP code, but the composer update is problematic for me. I've tried composer update, composer update --with-dependencies, composer install.

Composer isn't something I work with often. Any help is very appreciate! How do I decipher the composer error message to an actionable task? Is there a command that will install the dependencies for Laravel 6?

The error message after composer update:

I'm currently working on a website, which triggers a net::ERR_HTTP2_PROTOCOL_ERROR 200 error on Google Chrome. I'm not sure exactly what can provoke this error, I just noticed it pops out only when accessing the website in HTTPS. I can't be 100% sure it is related, but it looks like it prevents javascript to be executed properly.

For instance, the following scenario happens :

1. I'm accessing the website in HTTPS

2. My Twitter feed integrated via https://publish.twitter.com isn't loaded at all

3. I can notice in the console the ERR_HTTP2_PROTOCOL_ERROR

4. If I remove the code to load the Twitter feed, the error remains

5. If I access the website in HTTP, the Twitter feed appears and the error disappears

Google Chrome is the only web browser triggering the error: it works well on both Edge and Firefox. (NB: I tried with Safari, and I have a similar kcferrordomaincfnetwork 303 error)

I was wondering if it could be related to the header returned by the server since there is this '200' mention in the error, and a 404 / 500 page isn't triggering anything.

Thing is the error isn't documented at all. Google search gives me very few results. Moreover, I noticed it appears on very recent Google Chrome releases; the error doesn't pop on v.64.X, but it does on v.75+ (regardless of the OS; I'm working on Mac tho).

Any clue at this point to investigate would be gladly appreciated !

Thanks in advance.

Tristan

Edit 1 : Might be related to Website OK on Firefox but not on Safari (kCFErrorDomainCFNetwork error 303) neither Chrome (net::ERR_SPDY_PROTOCOL_ERROR)

Edit 2 : Findings from further investigations are the following :

• error doesn't pop on the exact same page if server returns 404 instead of 2XX
• error doesn't pop on local with a HTTPS certificate
• error pops on a different server (both are OVH's), which uses a different certificate
• error pops no matter what PHP version is used, from 5.6 to 7.3 (framework used : Cakephp 2.10)

Edit 3 : As requested, below is the returned header for the failing ressource, which is the whole web page. Even if the error is triggering on each page having a HTTP header 200, those pages are always loading on client's browser, but sometimes an element is missing (in my exemple, the external Twitter feed). Every other asset on the Network tab has a success return, except the whole document itself.

Google Chrome header (with error) :

Firefox header (without error) :

A curl --head --http2 request in console returns the following success :

I'm using Django (2, 2, 4, 'final', 0) within a docker, but I'm able to bash inside to open or execute whatever is required. But I can't debug. (How to debug in Django, the good way? states some methods, none work for me)

Within my views.py I'm having various functions, for instance this here.

I recently discovered a vulnerability in a package that I like to use in my Laravel projects. The package is a log viewer for Laravel: https://github.com/ARCANEDEV/LogViewer.

I put in an issue about the vulnerability and the owner said I can put in a Pull Request to try and rectify the issue, and I feel I could at least try.

My question is: is there a way to use the version of the package with my Pull Request in a testing environment, as if I were installing it via Composer?

Essentially, away from actual unit tests, is there a way to test run a package in a project?

Updates given research and available answers

After much Googling and reading of answers I tried the following:

• Fork the repo I'm looking to make a pull request for. The fork is here: https://github.com/blorange2/LogViewer
• Clone this forked repo onto my local machine and switch to the branch that's compatible with my current version of Laravel (which is v4.5 for Laravel 5.6)
• Update the composer.json in my local project to have a repositories array

It happens from the time to time on Chrome-based Chrome-based and Firefox browsers (fully updated versions, clean installs, also in incognito modes), on some (but not all) Windows machines.

Example of called URL is https://2.base.maps.api.here.com/maptile/2.1/maptile/2f447c1cac/normal.day/11/1071/663/256/png8?xnlp=CL_JSMv3.0.17.0&app_id=*********&app_code=******&lg=pol&criticality=major%2Ccritical

The status of the connection is "Pending" (but 200 OK) for 30 secs, then ends with no response (still 200 OK). But the console is reporting net:ERR_SPDY_PROTOCOL_ERROR 200 OK.

As a result tiles aren't loaded, map does not work as expected. The license is commercial (not freemium one).

A log from chrome://net-export/ and parsed by netlog-viewer, contains descriptions like this:

I'm updating some packages with composer. I'm using Laravel5.6 in my project.

The one that I'm trying is PHPStan to version 0.10.7. My current version is 0.9.2.

When I try to update, it shows a success message, but when checking the outdate packages output, it is still OUTDATED.

Using composer why-not phpstan/phpstan 0.10.7 gave me the following output:

I have problem with access to adminer in my docker container with laravel 5/mysql app. I got error :

I have a ASP.NET project with a plug-in architecture. I have a strongly named dll dependency in my reference chain, that both the app and the plug-in are dependent on. I'd really like to be able to use some older plug-ins that were compiled against an older version of the dependency dll when the app is updated with new dependency dll.

Currently when I call Assembly.GetTypes() I'm getting a ReflectionTypeLoadException with 5 LoaderExceptions of type FileLoadException, all complaining about the same dll. (There are a lot more dlls in the system, both strongly and weakly named, perhaps dependency chains cause the duplication in LoaderExceptions?)

https://docs.microsoft.com/en-us/dotnet/framework/configure-apps/redirect-assembly-versions

I tried adding to my web.config file.