Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / openbmc/sdbusplus issues and pull requests
#99 - Clarification on declaring sdbusplus::vtable::property getter function.
Issue -
State: closed - Opened by AithaTarun about 1 month ago
- 1 comment
#98 - Issue with async_method_call_timed not respecting timeout
Issue -
State: closed - Opened by ClaudiusJXK about 2 months ago
- 8 comments
#97 - Testcases that use the sd_bus_add_object_vtable mock now fail in CI
Issue -
State: open - Opened by spinler 4 months ago
#96 - about "can_read_multiple_v" in read.hpp
Issue -
State: open - Opened by ClaudiusJXK 4 months ago
- 2 comments
#95 - How to close the file description when a method return it ?
Issue -
State: open - Opened by writePerfectCode 6 months ago
- 8 comments
#94 - Build error for Enum type in aserver.hpp
Issue -
State: open - Opened by jagpalgill 8 months ago
#93 - sdbusplus doesn't support defaults for a set type.
Issue -
State: open - Opened by jagpalgill 8 months ago
#92 - Using sdbusplus consumes too much CPU I/O resources
Issue -
State: closed - Opened by renweihang 10 months ago
- 2 comments
#91 - How to implement get_property in dbus_interface class
Issue -
State: open - Opened by lzx5990 10 months ago
- 2 comments
#90 - Signal multiple property changed
Issue -
State: open - Opened by omarhogni 11 months ago
- 1 comment
#89 - How to delete one object/manager path under a object server
Issue -
State: closed - Opened by yongyuandeconan 11 months ago
- 1 comment
#88 - Sdbusplus allows serializing variant with a contained variant
Issue -
State: open - Opened by edtanous 12 months ago
- 5 comments
#87 - [async] aserver crashes on setting a property with invalid argument
Issue -
State: open - Opened by leiyu-bytedance about 1 year ago
#86 - [async] InterfaceAdded signal not emitted by generated aserver?
Issue -
State: open - Opened by vsytch about 1 year ago
- 3 comments
#85 - [async] Separate stdexec to a separate recipe
Issue -
State: open - Opened by vsytch about 1 year ago
- 1 comment
#84 - Can't building successful
Issue -
State: open - Opened by luacy200820 about 1 year ago
- 6 comments
#83 - Introduce getter for asio::connection in asio::dbus_interface
Issue -
State: open - Opened by jbbjarnason about 1 year ago
- 4 comments
#82 - broken build on ubuntu 22
Issue -
State: closed - Opened by gabonator over 1 year ago
- 1 comment
#81 - Bmcweb compiler failed on sdbusplus
Issue -
State: closed - Opened by TieWay59 over 1 year ago
- 9 comments
#80 - Including Client Binding Headers Clashes with <sys/socket.h>
Issue -
State: open - Opened by kaehnd over 1 year ago
- 1 comment
#79 - return error on property changes ?
Issue -
State: closed - Opened by frsauvage over 1 year ago
- 6 comments
#78 - [RFC] Allow propagating exceptions from server method implementations
Pull Request -
State: closed - Opened by hlounent over 1 year ago
- 4 comments
#77 - Multiple Definitions
Issue -
State: closed - Opened by pointbazaar almost 2 years ago
- 7 comments
#76 - sdbusplus: Failed to compile sdbusplus locally
Issue -
State: closed - Opened by lxwinspur almost 2 years ago
- 3 comments
#75 - Adoption of string_view?
Issue -
State: closed - Opened by vsytch about 2 years ago
- 2 comments
#74 - some compile issue
Issue -
State: closed - Opened by writePerfectCode about 2 years ago
- 1 comment
#73 - sdbusplus build error against c++17
Issue -
State: closed - Opened by vsytch about 2 years ago
- 2 comments
#72 - sdbus++ support for async method calls
Issue -
State: closed - Opened by charles-stracener over 2 years ago
- 5 comments
#71 - sdbusplus + polkit integration
Issue -
State: open - Opened by MarkAEvans over 2 years ago
- 6 comments
#70 - Remove sdbus++-gendir usage from examples and tests
Pull Request -
State: closed - Opened by SCOTT-HAMILTON almost 3 years ago
- 1 comment
#69 - examples not working in master
Issue -
State: closed - Opened by josue0175 about 3 years ago
- 8 comments
#68 - no setup.py file after ninja install
Issue -
State: closed - Opened by victorwang-tw about 3 years ago
- 1 comment
#67 - Question : What should I use
Issue -
State: closed - Opened by frsauvage about 3 years ago
- 2 comments
#66 - CMake support?
Issue -
State: closed - Opened by mrsaleh about 3 years ago
- 3 comments
#65 - Refactor dedup_variant to dedup_variant_t
Issue -
State: closed - Opened by williamspatrick over 3 years ago
- 1 comment
#64 - Issues with examples
Issue -
State: closed - Opened by paulnegz over 3 years ago
- 1 comment
#63 - (Proposition) Closing asio::connection, socket handling
Issue -
State: open - Opened by vsabadazh over 3 years ago
#62 - Properties changed signal
Issue -
State: open - Opened by chandu-tmba over 3 years ago
- 2 comments
#61 - Parallel method calls not getting executed in multiple server threads when using ASIO
Issue -
State: closed - Opened by pramorag over 3 years ago
- 7 comments
#60 - Unexpected conversion for `_` in filename()
Issue -
State: closed - Opened by leiyu-bytedance over 3 years ago
- 18 comments
#60 - Unexpected conversion for `_` in filename()
Issue -
State: closed - Opened by leiyu-bytedance over 3 years ago
- 18 comments
#60 - Unexpected conversion for `_` in filename()
Issue -
State: closed - Opened by leiyu-bytedance over 3 years ago
- 18 comments
#59 - (Question) Unpacking variants in a signal handler, std::bad_variant_access
Issue -
State: closed - Opened by vsabadazh over 3 years ago
- 3 comments
#59 - (Question) Unpacking variants in a signal handler, std::bad_variant_access
Issue -
State: closed - Opened by vsabadazh over 3 years ago
- 3 comments
#59 - (Question) Unpacking variants in a signal handler, std::bad_variant_access
Issue -
State: closed - Opened by vsabadazh over 3 years ago
- 3 comments
#58 - Uncertain on how we can listen to signals
Issue -
State: closed - Opened by Noomaok over 3 years ago
- 2 comments
#58 - Uncertain on how we can listen to signals
Issue -
State: closed - Opened by Noomaok over 3 years ago
- 2 comments
#57 - Support for names of method and signal arguments in DBus introspection
Issue -
State: open - Opened by mkaranki almost 4 years ago
- 3 comments
#57 - Support for names of method and signal arguments in DBus introspection
Issue -
State: open - Opened by mkaranki almost 4 years ago
- 3 comments
#56 - Exit bug
Issue -
State: closed - Opened by furious92 almost 4 years ago
- 1 comment
#56 - Exit bug
Issue -
State: closed - Opened by furious92 almost 4 years ago
- 1 comment
#55 - map of properties constructor should not emit PropertiesChanged signals
Issue -
State: open - Opened by bradbishop almost 4 years ago
- 2 comments
#55 - map of properties constructor should not emit PropertiesChanged signals
Issue -
State: open - Opened by bradbishop almost 4 years ago
- 2 comments
#54 - exceptions: ensure method call exception types are different between internal dbus failures and call returns
Issue -
State: closed - Opened by williamspatrick almost 4 years ago
- 4 comments
#53 - Add method to sdbus++ objects to control all property signals.
Issue -
State: open - Opened by williamspatrick almost 4 years ago
#53 - Add method to sdbus++ objects to control all property signals.
Issue -
State: open - Opened by williamspatrick almost 4 years ago
#52 - message::read doesn't handle multiple enums in a variant
Issue -
State: closed - Opened by jonathan-doman about 4 years ago
- 2 comments
#52 - message::read doesn't handle multiple enums in a variant
Issue -
State: closed - Opened by jonathan-doman about 4 years ago
- 2 comments
#52 - message::read doesn't handle multiple enums in a variant
Issue -
State: closed - Opened by jonathan-doman about 4 years ago
- 2 comments
#51 - Test issue.
Issue -
State: closed - Opened by williamspatrick about 4 years ago
- 3 comments
#51 - Test issue.
Issue -
State: closed - Opened by williamspatrick about 4 years ago
- 3 comments
#50 - Need support for tuple message type
Issue -
State: closed - Opened by manojkiraneda about 4 years ago
- 1 comment
#50 - Need support for tuple message type
Issue -
State: closed - Opened by manojkiraneda about 4 years ago
- 1 comment
#49 - long build directory paths cause sdbusplus compile failures
Issue -
State: closed - Opened by geissonator about 4 years ago
- 1 comment
#49 - long build directory paths cause sdbusplus compile failures
Issue -
State: closed - Opened by geissonator about 4 years ago
- 1 comment
#48 - Add readonly property
Issue -
State: closed - Opened by BrainStone over 4 years ago
- 5 comments
#48 - Add readonly property
Issue -
State: closed - Opened by BrainStone over 4 years ago
- 5 comments
#47 - Build documentation
Issue -
State: closed - Opened by BrainStone over 4 years ago
- 9 comments
#47 - Build documentation
Issue -
State: closed - Opened by BrainStone over 4 years ago
- 9 comments
#46 - undefined reference to `boost::thread_detail::commit_once_region(boost::once_flag&)
Issue -
State: closed - Opened by geissonator over 4 years ago
- 2 comments
#46 - undefined reference to `boost::thread_detail::commit_once_region(boost::once_flag&)
Issue -
State: closed - Opened by geissonator over 4 years ago
- 2 comments
#45 - asio-example.cpp build failed:error: the value of ‘returnWithMsg’ is not usable in a constant expression
Issue -
State: closed - Opened by jxlczjp77 over 4 years ago
- 1 comment
#45 - asio-example.cpp build failed:error: the value of ‘returnWithMsg’ is not usable in a constant expression
Issue -
State: closed - Opened by jxlczjp77 over 4 years ago
- 1 comment
#44 - ‘meson build‘ error happened
Issue -
State: closed - Opened by zzhuang-cancon over 4 years ago
- 1 comment
#44 - ‘meson build‘ error happened
Issue -
State: closed - Opened by zzhuang-cancon over 4 years ago
- 1 comment
#43 - Wait for an object path to be created
Issue -
State: closed - Opened by ytmhub over 4 years ago
- 2 comments
#43 - Wait for an object path to be created
Issue -
State: closed - Opened by ytmhub over 4 years ago
- 2 comments
#42 - Handle time as a native type
Issue -
State: open - Opened by ZhikuiRen over 4 years ago
- 6 comments
#42 - Handle time as a native type
Issue -
State: open - Opened by ZhikuiRen over 4 years ago
- 6 comments
#41 - Build is getting failed with error code 2=“null” and 255=“null” in Windows 10 OS
Issue -
State: closed - Opened by paratsa almost 5 years ago
- 2 comments
#41 - Build is getting failed with error code 2=“null” and 255=“null” in Windows 10 OS
Issue -
State: closed - Opened by paratsa almost 5 years ago
- 2 comments
#40 - Compilation failed
Issue -
State: closed - Opened by wilhelmy almost 5 years ago
- 9 comments
#40 - Compilation failed
Issue -
State: closed - Opened by wilhelmy almost 5 years ago
- 9 comments
#39 - running "make check" have error : ld returned 1 exit status
Issue -
State: closed - Opened by Journey-x about 5 years ago
- 1 comment
#39 - running "make check" have error : ld returned 1 exit status
Issue -
State: closed - Opened by Journey-x about 5 years ago
- 1 comment
#38 - match doesn't process errors from sd_bus_add_match
Issue -
State: open - Opened by fr0st61te about 5 years ago
#38 - match doesn't process errors from sd_bus_add_match
Issue -
State: open - Opened by fr0st61te about 5 years ago
#37 - Are there ASIO unit tests or mock classes anywhere for sdbusplus? Has it been tested in an SMP environment?
Issue -
State: closed - Opened by IAmWilfredSmith over 5 years ago
- 2 comments
#37 - Are there ASIO unit tests or mock classes anywhere for sdbusplus? Has it been tested in an SMP environment?
Issue -
State: closed - Opened by IAmWilfredSmith over 5 years ago
- 2 comments
#36 - sdbusplus::bus::bus Add get_events, get_timeout
Pull Request -
State: closed - Opened by hojalot over 5 years ago
- 1 comment
#36 - sdbusplus::bus::bus Add get_events, get_timeout
Pull Request -
State: closed - Opened by hojalot over 5 years ago
- 1 comment
#35 - Signal property names are not exposed
Issue -
State: closed - Opened by BrainStone over 5 years ago
- 4 comments
#35 - Signal property names are not exposed
Issue -
State: closed - Opened by BrainStone over 5 years ago
- 4 comments
#34 - Docs of the YAML format are not up to date
Issue -
State: closed - Opened by BrainStone over 5 years ago
- 1 comment
#34 - Docs of the YAML format are not up to date
Issue -
State: closed - Opened by BrainStone over 5 years ago
- 1 comment
#33 - Allow compiling library statically
Issue -
State: closed - Opened by BrainStone over 5 years ago
- 5 comments
#33 - Allow compiling library statically
Issue -
State: closed - Opened by BrainStone over 5 years ago
- 5 comments
#32 - Running example calculator crashes with: sd_bus_request_name: org.freedesktop.DBus.Error.InvalidArgs: Invalid argument
Issue -
State: closed - Opened by BrainStone over 5 years ago
- 3 comments
#32 - Running example calculator crashes with: sd_bus_request_name: org.freedesktop.DBus.Error.InvalidArgs: Invalid argument
Issue -
State: closed - Opened by BrainStone over 5 years ago
- 3 comments
#31 - sdbusplus releases
Issue -
State: open - Opened by johang over 5 years ago
- 2 comments