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

fix(team): profile import crashes on a bad field and the secret scrubber misses pwd / private_key

Closed
#1,564 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
72/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
dart, flutter
Domain
database, desktop

Research direction

Start with lib/core/team/team_profile.dart, especially TeamProfileCodec.decode at lines 129–133 and _secretKey at line 25. Check the profile import and export tests, then add cases for invalid field types and the listed secret keys. Done means invalid rows are skipped and counted, and those keys are scrubbed in driver options and connection string queries.

Written by the indexing model from the issue text.

Description

bug core P2 stability

Problem

TeamProfileCodec.decode (lib/core/team/team_profile.dart:129-133) uses unchecked casts (item['port'] as int?, item['host'] as String?, username, databaseName, authSource, extensionId). A hand-edited or version-skewed file throws TypeError (not TeamProfileFormatException) and the whole import fails instead of skipping the bad row.

The secret scrubber _secretKey (:25) is pass(word|phrase)?|secret|token|api_?key and misses pwd, private_key / privateKey, credential(s), access_key, signature. Such keys in driverOptions or in the connection-string query survive export and import.

Expected

  • Type-check each field (pattern matching), skip invalid rows and report how many were skipped.
  • Extend the key pattern (and add tests for pwd, privateKey, private_key, accessKey, credentials).
Dominant language
Dart
Stars
23
Forks
1
Avg merge
49m
Merged PRs (30d)
496

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

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 QueryaHub/Querya-Desktop

All issues in QueryaHub/Querya-Desktop

Similar issues

More Dart issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.