GitHub Access Token became invalid

It seems like the GitHub access token used for retrieving details about this repository from GitHub became invalid. This might prevent certain types of inspections from being run (in particular, everything related to pull requests).
Please ask an admin of your repository to re-new the access token on this website.
Completed
Push — master ( 746a07...6b648b )
by
unknown
7s
created

The analysis results of the pull-request Fix when nullResource returned from Transformers are reused. No further analysis is needed in this inspection.
Platform Status: Inspections might take a bit longer than usual at the moment. Please see the status page for more information. x
Bitbucket Status: Bitbucket is reporting issues with pulling code. This may slow down inspections, please check the Bitbucket status page for more information. x
Loading Application Loading...
Test Artifacts Loading
Node #{{ nodeName }}
{{ artifact.name }} {{ artifact.name }} {{ artifact.name }}

SSH Debugging Session

Setting up environment The container is being prepared...
You can SSH into the container with your regular public key using the following command:
ssh {{ sshDetails.login }}@{{ sshDetails.host }} -p {{ sshDetails.port }}
Show valid SSH keys

To connect one of the keys below must be available in your local environment. You can list available keys with ssh-add -L

{{ keys }}

The container will stay up for 30 minutes after the environment was set-up and counts towards your plan's container limit. Please cancel this inspection as soon as you finished debugging to release the container again.

Debugging browser problems? Check out our dedicated doc for more info.

Preparation

Inspection has been canceled - no tasks have been run.

Preparing Execution Plan   Configuration parsed, preparing execution plan...

Analyses
The display is not available anymore since the inspection has already completed.
Currently Running Task

 

{{ subsection.title }}
×

This command was automatically inferred. You can disable inferred commands by adding an override section to your configuration:

build:
    %section%:
        override:
            - your-command

            # or use a "dummy" command like
            - true