Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Migrate from custom tracing to APSW built-in tracing

Open
#5 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
python, sqlite
Domain
databases

Research direction

Start by locating the custom tracing implementation used by sqlite-minutils and sqlite-utils, then read the linked APSW execution-tracing example. The work is complete when the custom tracing system is migrated to APSW's built-in tracing without losing the existing tracing behavior.

Written by the indexing model from the issue text.

Description

sqlite-minutils (and sqlite-utils) has it's own tracing system, that with the change to APSW is no longer necessary. APSW example: https://rogerbinns.github.io/apsw/example.html#tracing-execution

Dominant language
Python
Stars
3
Forks
3
PR merge metrics
No merged PRs in 30d

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.

More from AnswerDotAI/apswutils

All issues in AnswerDotAI/apswutils

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.