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

[Bug]: Supress or otherwise disable unsupported features when running in CI

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

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript, node.js
Domain
ci-cd, testing

Research direction

Start with the GitHub Actions workflow and test command referenced by the linked run to identify how the application is launched in CI. Then trace which features trigger the UPower and ALSA messages; the issue does not name source files or tests to change. Done means CI no longer emits unsupported-feature errors without disrupting the tests.

Written by the indexing model from the issue text.

Description

bug
Bug Summary

Supress or otherwise disable unsupported features when running in CI

Detailed Description
      ✓ Plays NINE on jacks from a seven (11698ms)
[2200:0315/184219.658853:ERROR:object_proxy.cc(590)] Failed to call method: org.freedesktop.DBus.Properties.Get: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
[2200:0315/184219.659153:ERROR:object_proxy.cc(590)] Failed to call method: org.freedesktop.UPower.GetDisplayDevice: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
[2200:0315/184219.659382:ERROR:object_proxy.cc(590)] Failed to call method: org.freedesktop.UPower.EnumerateDevices: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
[2200:0315/184223.255245:ERROR:object_proxy.cc(590)] Failed to call method: org.freedesktop.DBus.Properties.Get: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
[2200:0315/184223.255494:ERROR:object_proxy.cc(590)] Failed to call method: org.freedesktop.UPower.GetDisplayDevice: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
[2200:0315/184223.255709:ERROR:object_proxy.cc(590)] Failed to call method: org.freedesktop.UPower.EnumerateDevices: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files

Snippet from a GitHub action, https://github.com/cuttle-cards/cuttle/actions/runs/8300861816/job/22719737870?pr=891

GPT added this:

The errors you're seeing are related to two different issues:

org.freedesktop.UPower Errors: These errors are related to the UPower service on Linux, which is used for power management. It seems like the service is not available in your GitHub Actions environment. These errors are usually harmless and can be ignored if you're not doing anything related to power management in your tests.

ALSA lib Errors: These errors are related to the Advanced Linux Sound Architecture (ALSA), which is used for sound on Linux. It seems like the default sound card is not available in your GitHub Actions environment. If your application or tests don't need to play sound, these errors can also be ignored.

If you want to suppress these errors, you can try running your tests with the CI=true environment variable. This is a common convention that some tools use to change their behavior in continuous integration environments.

Current Behavior

No response

Expected Behavior

No response

Steps to Reproduce
Dominant language
JavaScript
Stars
195
Forks
145
Avg merge
2d 2h
Merged PRs (30d)
23

Getting set up

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 cuttle-cards/cuttle

All issues in cuttle-cards/cuttle

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.