Bump certifi from 2022.12.7 to 2023.7.22 in /include/json/docs/mkdocs#22
Closed
dependabot[bot] wants to merge 1 commit into
Closed
Bump certifi from 2022.12.7 to 2023.7.22 in /include/json/docs/mkdocs#22dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [certifi](https://github.com/certifi/python-certifi) from 2022.12.7 to 2023.7.22. - [Commits](certifi/python-certifi@2022.12.07...2023.07.22) --- updated-dependencies: - dependency-name: certifi dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
the
dependencies
Contributor
Author
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
dependabot
Bot
deleted the
dependabot/pip/include/json/docs/mkdocs/certifi-2023.7.22
branch
frstrtr
added a commit
that referenced
this pull request
Jun 4, 2026
…plete type (#22/#39) Two cross-platform compile failures on PR #63 (neither is LINK_GROUP:RESCAN): Windows (C1083 leveldb/db.h in c2pool_storage): the c2pool_storage OBJECT lib compiles storage/sharechain_storage.cpp which pulls core/leveldb_store.hpp -> <leveldb/db.h>, but it deliberately does not link core (SCC break), so the leveldb include dir never reached it. On Conan/MSVC that dir propagates only via the leveldb::leveldb imported target. Add ${LEVELDB_LIBRARIES} to c2pool_storage so it carries the usage requirement itself (Linux found db.h on the default system path, hence the platform-specific failure). macOS (incomplete type core::INetwork at socket.hpp:174): make_socket() dynamic_casts to INetwork* and calls weak_from_this(), both requiring a complete type, but socket.hpp only forward-declared it (full def was in factory.hpp, which includes socket.hpp — a cycle). Extract INetwork into core/inetwork.hpp, included by socket.hpp and factory.hpp. AppleClang/MSVC diagnose the incomplete non- dependent type at template-parse time where GCC tolerated it.
frstrtr
added a commit
that referenced
this pull request
Jun 4, 2026
…#39) macOS arm64 link failed: undefined Boost.Log symbols (open_record, push_record_move, get_logging_enabled, trivial::logger::get) from payout_manager.cpp.o and merged_mining.cpp.o. Both TUs include <core/log.hpp> (LOG_* -> Boost.Log trivial). Their OBJECT libs deliberately do not link core (SCC break), so they no longer inherit cores PUBLIC Boost::log/Boost::log_setup. They fell back to the legacy ${Boost_LIBRARIES} variable, which does not reliably resolve the log component through ld64 static archives on AppleClang arm64; GCC/MSVC tolerated it. Fix: name Boost::log/Boost::log_setup imported targets explicitly on c2pool_payout and c2pool_merged_mining, same fix class as the ratified c2pool_storage/leveldb usage-requirement carry. CMake-only, no coin tree touched. Linux x86_64 re-verified green.
frstrtr
added a commit
that referenced
this pull request
Jun 4, 2026
sharechain_storage.cpp.o was the remaining arm64 undefined-symbol source
(run 26944904869). It includes <core/log.hpp> (LOG_* -> Boost.Log trivial)
but the OBJECT-SCC break means c2pool_storage does not link core, so it
fell back to legacy ${Boost_LIBRARIES} which ld64 will not resolve. Name
Boost::log + Boost::log_setup explicitly, same carry pattern already
applied to c2pool_payout and c2pool_merged_mining.
frstrtr
added a commit
that referenced
this pull request
Jun 4, 2026
…JECT libs (#22/#39) Both libs use Boost.Log internally (tracker.cpp, adjustment_engine.cpp) but do not link core after the OBJECT-lib SCC break, so ld64 on AppleClang arm64 fails to resolve Boost.Log symbols. Carry Boost::log + Boost::log_setup explicitly, same pattern as c2pool_storage/c2pool_payout/c2pool_merged_mining.
frstrtr
added a commit
that referenced
this pull request
Jun 4, 2026
…#63) * ci: convert core archive SCC to per-archive OBJECT libraries (#22/#39) Flip the 9 first-party STATIC archives in the core link SCC (core, pool, sharechain, ltc, ltc_coin, c2pool_storage, c2pool_payout, c2pool_hashrate, c2pool_merged_mining) to OBJECT libraries, replacing the GNU-ld-only LINK_GROUP:RESCAN band-aid with a linker-agnostic shape (MSVC/AppleClang). Break the core<->{payout,hashrate,merged_mining} cycle acyclically: core propagates those three as INTERFACE deps so every consumer pools their objects (core/web_server.o references their symbols), while they no longer link core (header-only access via the global src/ include) -- CMake rejects non-STATIC SCC cycles. c2pool_difficulty stays a STATIC leaf outside the SCC with its core link dropped so its archive does not absorb core OBJECT files. core_util/btclibs stay STATIC. Retire all 4 LINK_GROUP:RESCAN sites; OBJECT transitive propagation lets consumers fall back to core+ltc. Source-level dissolution of core web_server deps deferred to V37. * ci: make core target_link_libraries all-keyword (PUBLIC) for OBJECT SCC The OBJECT-lib boundary (de25cd2) added a keyword-signature target_link_libraries(core INTERFACE ...) in src/c2pool/CMakeLists.txt while src/core/CMakeLists.txt still used the plain signature, which CMake rejects (all uses on a target must be all-keyword or all-plain). Convert core core_util/btclibs and Boost/yaml/json/leveldb link calls to PUBLIC, matching the OBJECT-library propagation intent (consumers pool cores objects and need its usage requirements). * ci: add pool as 6th direct-named OBJECT-SCC lib (#22/#39) The five-lib enumeration (c2pool_hashrate, c2pool_merged_mining, c2pool_payout, c2pool_storage, ltc_coin) was incomplete: pool owns pool::parse_net_error (src/pool/node.cpp) and is reachable only transitively, so its objects did not propagate into the exe/test links. Name pool directly alongside the other OBJECT sets on c2pool, c2pool_enhanced, test_ltc_node, ltc_pool_test per the ratified direct-naming pattern. CMake-only; no coin-tree or source changes. Canonical Conan build links 100% green. * ci: fix Win/macOS OBJECT-lib build — leveldb usage req + INetwork complete type (#22/#39) Two cross-platform compile failures on PR #63 (neither is LINK_GROUP:RESCAN): Windows (C1083 leveldb/db.h in c2pool_storage): the c2pool_storage OBJECT lib compiles storage/sharechain_storage.cpp which pulls core/leveldb_store.hpp -> <leveldb/db.h>, but it deliberately does not link core (SCC break), so the leveldb include dir never reached it. On Conan/MSVC that dir propagates only via the leveldb::leveldb imported target. Add ${LEVELDB_LIBRARIES} to c2pool_storage so it carries the usage requirement itself (Linux found db.h on the default system path, hence the platform-specific failure). macOS (incomplete type core::INetwork at socket.hpp:174): make_socket() dynamic_casts to INetwork* and calls weak_from_this(), both requiring a complete type, but socket.hpp only forward-declared it (full def was in factory.hpp, which includes socket.hpp — a cycle). Extract INetwork into core/inetwork.hpp, included by socket.hpp and factory.hpp. AppleClang/MSVC diagnose the incomplete non- dependent type at template-parse time where GCC tolerated it. * ci: carry Boost.Log usage req on payout/merged_mining OBJECT libs (#22/#39) macOS arm64 link failed: undefined Boost.Log symbols (open_record, push_record_move, get_logging_enabled, trivial::logger::get) from payout_manager.cpp.o and merged_mining.cpp.o. Both TUs include <core/log.hpp> (LOG_* -> Boost.Log trivial). Their OBJECT libs deliberately do not link core (SCC break), so they no longer inherit cores PUBLIC Boost::log/Boost::log_setup. They fell back to the legacy ${Boost_LIBRARIES} variable, which does not reliably resolve the log component through ld64 static archives on AppleClang arm64; GCC/MSVC tolerated it. Fix: name Boost::log/Boost::log_setup imported targets explicitly on c2pool_payout and c2pool_merged_mining, same fix class as the ratified c2pool_storage/leveldb usage-requirement carry. CMake-only, no coin tree touched. Linux x86_64 re-verified green. * ci: carry Boost.Log usage req on c2pool_storage OBJECT lib (#22/#39) sharechain_storage.cpp.o was the remaining arm64 undefined-symbol source (run 26944904869). It includes <core/log.hpp> (LOG_* -> Boost.Log trivial) but the OBJECT-SCC break means c2pool_storage does not link core, so it fell back to legacy ${Boost_LIBRARIES} which ld64 will not resolve. Name Boost::log + Boost::log_setup explicitly, same carry pattern already applied to c2pool_payout and c2pool_merged_mining. * ci: carry Boost.Log usage req on c2pool_hashrate/c2pool_difficulty OBJECT libs (#22/#39) Both libs use Boost.Log internally (tracker.cpp, adjustment_engine.cpp) but do not link core after the OBJECT-lib SCC break, so ld64 on AppleClang arm64 fails to resolve Boost.Log symbols. Carry Boost::log + Boost::log_setup explicitly, same pattern as c2pool_storage/c2pool_payout/c2pool_merged_mining.
frstrtr
added a commit
that referenced
this pull request
Jun 5, 2026
CMake link fix (CI family 2). HashrateTracker vardiff API (set_difficulty_bounds/set_target_time_per_mining_share/enable_vardiff/ set_difficulty_hint/get_current_difficulty/record_mining_share_submission/ difficulty_changed_since/get_current_hashrate) is defined in src/c2pool/hashrate/tracker.cpp and built into the c2pool_hashrate OBJECT library, but the btc executable target did not name it directly. OBJECT-lib objects are only pulled into the final link when named directly on the consuming target (#22/#39); core+stratum_server.cpp references were therefore unresolved at link. Matches the test-target precedent. Family 1 (ltc::coin in shared core) still outstanding; full link verification pending that fix.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps certifi from 2022.12.7 to 2023.7.22.
Commits
8fb96ed2023.07.22afe7722Bump actions/setup-python from 4.6.1 to 4.7.0 (#230)2038739Bump dessant/lock-threads from 3.0.0 to 4.0.1 (#229)44df761Hash pin Actions and enable dependabot (#228)8b3d7ba2023.05.0753da240ci: Add Python 3.12-dev to the testing (#224)c2fc3b1Create a Security Policy (#222)c211ef4Set up permissions to github workflows (#218)2087de5Don't let deprecation warning fail CI (#219)e0b9fc5remove paragraphs about 1024-bit roots from READMEYou can trigger a rebase of this PR by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.