Skip to content

devlanes is in beta and not ready for production use.Report an issue

Report a bug

Use this when devlanes does something you did not expect and you want someone to reproduce it. Collect everything while the problem is happening: stopping or restarting the daemon loses most of it.

A coding agent with the devlanes skill can collect this and draft the issue. Ask it to investigate the problem and draft a bug report, read the draft before it is posted, and attach the bundle yourself.

Terminal window
$ devlanes doctor

The doctor checks the daemon, Docker, the proxy, the CA and hostname lookups, prints a fix under each line that is off, and names the version and how devlanes was installed. When a service is the problem, devlanes debug why with the service’s name gives the reasons.

Add the command that goes wrong after the two dashes. The bundle runs it again with full diagnostics, so a start really starts the service.

Terminal window
$ devlanes debug bundle -- start api

It writes an archive with the versions, the doctor’s checks, the status of the lanes, the end of the daemon’s log and the output of that command, and prints where the archive is. Values of variables named like tokens, keys or passwords are replaced, but a secret under another name stays, so read the files before you attach them.

Open a bug report. The form asks for your versions, what happened, the steps, what you expected and the bundle. Add the lines of the project file involved, with secrets removed.

Restart the daemon with a debug level, then do what goes wrong again and make the bundle. The restart stops your services and starts them again.

macOS

Terminal window
$ DEVLANES_LOG=debug devlanes daemon restart

Linux

Terminal window
$ DEVLANES_LOG=debug devlanes daemon restart

Windows

Terminal window
PS> $env:DEVLANES_LOG = "debug"; devlanes daemon restart

Do not open a public issue. Follow the devlanes-run security policy.