Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a linode entry about a specific error to troubleshooting.md #14632

Merged

Conversation

pavelexpertov
Copy link
Contributor

@pavelexpertov pavelexpertov commented Jul 21, 2023

Description

Purpose of the PR is to provide a description of how to resolve an 'unsupported stackscript' which I faced whilst trying to deploy algo onto Linode.

Motivation and Context

I have scoured the repository and internet for this issue and it seems I've spotted a unique issue. Thus, I felt it would be helpful for others if I provided a solution to this problem.

How Has This Been Tested?

N/A since it's updating troubleshooting.md. (But I would appreciate if somebody advises on how to format hyperlinks coz I don't know whether it works properly or not).

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
    N/A since it's updating troubleshooting.md

Checklist:

  • I have read the CONTRIBUTING document.
  • [] My code follows the code style of this project.
  • [] My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • [] I have added tests to cover my changes.
  • [] All new and existing tests passed.

@CLAassistant
Copy link

CLAassistant commented Jul 21, 2023

CLA assistant check
All committers have signed the CLA.

@jackivanov jackivanov merged commit 67aa5fe into trailofbits:master Dec 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants