Fix `@test_broken` completion test

Open
  • Is something wrong?
#80 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
julia
Domain
cli, testing

Research direction

Start with test/runtests.jl at lines 167-169 and inspect the @test_broken completion test, then compare its behavior with completion used live in the REPL. Reproduce the failure and investigate the referenced pull request context; done means the completion test passes without the broken marker.

Written by the indexing model from the issue text.

Description

good first issue

In order to get https://github.com/JuliaWeb/RemoteREPL.jl/pull/77 unstuck, I had to mark a test as broken: https://github.com/mortenpi/RemoteREPL.jl/blob/7bae7d4d38495b6acfbc535c7326cb97f954b40b/test/runtests.jl#L167-L169

I'm not totally sure what is going wrong, but it's probably a relatively easy fix, as the completion seeming works fine for me live in the REPL

Dominant language
Julia
Stars
148
Forks
17
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from JuliaWeb/RemoteREPL.jl

All issues in JuliaWeb/RemoteREPL.jl

Similar issues

More Julia issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.