• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

LFDT-Panurus / panurus / 36674900936
85%

Build:
DEFAULT BRANCH: main
Ran 30 Sep 2026 05:54AM UTC
Jobs 0
Files 0
Run time –
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

pending completion
36674900936

push

github

AkramBitar
fix(selector): make the declared fetcher strategies selectable and configurable

FetcherStrategy declared five strategies while the registry held one, so four
of the five constants could not be passed to NewFetcherProvider at all -- and
passing one panicked, since an unregistered strategy took the panic branch. No
configuration key reached the parameter either: the dig SDK hard-coded
sherdlock.Mixed, so the exported constants documented an option nobody could
set and the panic was unreachable in production.

Declare only the strategies that exist, and register all of them. Lazy and
Eager have working implementations in this very file -- the lazy and cached
fetchers the mixed fetcher already composes -- so they become selectable.
Listener is dropped: nothing in the tree implements listening for token store
insert events, and inventing it is a feature rather than this cleanup. Cached
is dropped too, because it and Eager would both resolve to NewCachedFetcher,
and one behaviour needs one name; Eager is the name the code already uses for
that fetcher, in mixedFetcher.eagerFetcher and in the eager metrics label.
Neither removed constant could be used without panicking, so no working caller
can depend on it.

NewFetcherProvider now returns an error for an unrecognized strategy instead of
panicking, naming the accepted values so a misspelled configuration value is
diagnosable, and treats the empty strategy as the default. A new
token.selector.fetcherStrategy key carries the choice, alongside the three
fetcherCache* knobs that tune the cache the parameter selects; it is returned
verbatim by GetFetcherStrategy, empty meaning "use the fetcher default", the
way 0 already does for those knobs, because validation belongs to the fetcher
that owns the set of strategies. The dig provider propagates the error, so a
bad value fails container installation like an unknown token.selector.driver
does rather than taking the process down.

While wiring that provider: it logg... (continued)
Source Files on build 36674900936
Detailed source file information is not available for this build.
  • Back to Repo
  • Github Actions Build #36674900936
  • fb8736ce on github
  • Prev Build on main (#36569751760)
  • Next Build on main (#36692392983)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc