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

Tests fail: AssertionError: Lists differ

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

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
api

Research direction

Start with tests/test_config.py, especially test_config_file_detection_user at line 110, and reproduce the failure on the reported FreeBSD 13.1 setup. Check how get_configfile_paths() handles the user config path; done means the test passes and returns the expected .config/dwave/dwave.conf path.

Written by the indexing model from the issue text.

Description

======================================================================
FAIL: test_config_file_detection_user (tests.test_config.TestConfigParsing)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/disk-samsung/freebsd-ports/science/py-dwave-cloud-client/work-py39/dwave-cloud-client-0.10.2/tests/test_config.py", line 110, in test_config_file_detection_user
    self.assertEqual(get_configfile_paths(), [configpath])
AssertionError: Lists differ: [] != ['/disk-samsung/freebsd-ports/science/py-d[49 chars]onf']

Second list contains 1 additional elements.
First extra element 0:
'/disk-samsung/freebsd-ports/science/py-dwave-cloud-client/work-py39/.config/dwave/dwave.conf'

- []
+ ['/disk-samsung/freebsd-ports/science/py-dwave-cloud-client/work-py39/.config/dwave/dwave.conf']

Version: 0.10.2
OS: FreeBSD 13.1

Dominant language
Python
Stars
63
Forks
44
Avg merge
2d 9h
Merged PRs (30d)
2

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 dwavesystems/dwave-cloud-client

All issues in dwavesystems/dwave-cloud-client

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.