@scrutinizerci Profile picture

scrutinizer ci

@scrutinizerci

Continuous Inspection Service

Similar User
Packagist photo

@packagist

ReactPHP photo

@reactphp

Matthias Noback @matthiasnoback@mastodon.social photo

@matthiasnoback

Lorna Mitchell photo

@lornajane

Jordi Boggiano photo

@seldaek

Bernhard Schussek (see webmozart.bsky.social) photo

@webmozart

Christophe Coevoet photo

@Stof70

Nicolas Grekas 💙💛 photo

@nicolasgrekas

SensioLabs Tech photo

@SensioLabsTech

SymfonyLive photo

@symfony_live

@lsmith@mastodon.green (he/him) photo

@lsmith

KNP Labs photo

@KNPLabs

Tideways Profiler photo

@tideways

Konstantin Kudryashov photo

@everzet

Paweł Jędrzejewski photo

@pjedrzejewski

scrutinizer ci Reposted
Tweet Image 1
Tweet Image 2

This should be fixed now, do you maybe have a link to an inspection so we can investigate?


Significantly simplifying the way how you can debug browser-based tests on Scrutinizer - check it out scrutinizer-ci.com/blog/simple-de…


will add more details to your support request


sorry, we should have kept you updated on progress, we still have an internal ticket open on your request


it seems like there was a routing problem this morning, this has been fixed, do you still see this?


scrutinizer ci Reposted

As one of our beta testers uses @scrutinizerci and so do we,koalamon now supports the continuous inspection platform

Tweet Image 1

You can still configure all OSS tools like ESLint/JSHint manually (2/2)


We prepare the release of our new Javascript analysis engine (checks: { javascript: { }}) will be tmply unavailable (1/2)


Boosting your productivity - view Scrutinizer analysis results right inside GitHub with our Chrome extension - scrutinizer-ci.com/blog/analysis-…


@heiglandreas thanks for the report, this should be fixed now


@tim_bezhashvyly you might still get a false-positive if variadics are used in a dependency that was analyzed and cached with the old code


@tim_bezhashvyly we deployed this last year, it might still be that some cached data is false


@tim_bezhashvyly yes, we have confirmed the issue, and it's fixed in our dev version already, will soon also reach production


@tim_bezhashvyly thanks, I've created an internal issue to check up on this


@tim_bezhashvyly those issues are mostly outdated unfortunately - do you still see this in your code somewhere?


@tim_bezhashvyly do you maybe have a link to a false-positive related to variadics, so we can have a look?


@AlberteAtWork sorry for the hiccup, there was a problem on the frontend servers, we have provisioned some backups which are taking over now


Loading...

Something went wrong.


Something went wrong.