stan-dev / stan-dev/bayesplot

Error: polygon edge not found when using bayesplot

Open
#283 8 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
R
Stars
442
Forks
93
Avg merge
3h 11m
Merged PRs (30d)
1

Description

Hi there!

Thanks for maintaining bayesplot!

I've got a bit of a funny issue that I was wondering if you have encountered with bayesplot. I find that sometimes, but not always, GitHub actions fails building a vignette when calling a function from bayesplot, giving the error:

Quitting from lines 469-474 (get_started.Rmd) 
  Error: processing vignette 'get_started.Rmd' failed with diagnostics:
  polygon edge not found
  --- failed re-building ‘get_started.Rmd’

(GH action line here: https://github.com/greta-dev/greta/runs/5233369273?check_suite_focus=true#step:11:245)

This is occurring at this line of the vignette:

https://github.com/greta-dev/greta/blob/master/vignettes/get_started.Rmd#L469-L473

Having a look around, it initially appeared that there was an issue with fonts: https://community.rstudio.com/t/ggplot2-polygon-edge-not-found/116475/4 - however, taking a look at your code it doesn't seem that there are custom fonts loaded, so I'm not sure why this is happening.

In any case, please do feel free to close this issue, I just thought in case you've come across this before, if you have any tips on how to resolve this!

Cheers!

Contributor guide

Open the contributing guide

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.

Research direction

Start with vignettes/get_started.Rmd around lines 469-474 and inspect the GitHub Actions run linked in the report. Reproduce the intermittent vignette build failure and determine whether it depends on the plotting call or the build environment. Done means the vignette builds reliably in the affected workflow, with the cause and resolution documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, r
Domain
ci-cd, data-visualization
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.