Skip to content

Update lock-dependencies to scrub CDN references#392

Open
asnare wants to merge 7 commits into
mainfrom
fix/lock-dependencies
Open

Update lock-dependencies to scrub CDN references#392
asnare wants to merge 7 commits into
mainfrom
fix/lock-dependencies

Conversation

@asnare

@asnare asnare commented Jun 23, 2026

Copy link
Copy Markdown
Contributor

This PR updates the lock-dependencies target so that it also scrubs mirror information from the url = references: these refer to the PyPI CDN.

This change is needed because some mirrors/proxies also rewrite the CDN URLs: without this change uv.lock refers to environment-specific URLs instead of PyPi.

In addition to the Makefile changes, the locks have been refreshed.

@asnare asnare self-assigned this Jun 23, 2026
@asnare asnare requested a review from a team as a code owner June 23, 2026 13:56
@asnare asnare added the bug Something isn't working label Jun 23, 2026
@asnare asnare added this to UCX Jun 23, 2026
@asnare asnare added dependencies Pull requests that update a dependency file internal do not show this PR in changelog labels Jun 23, 2026
@asnare asnare moved this to Ready for Review in UCX Jun 23, 2026
@databrickslabs databrickslabs deleted a comment from CLAassistant Jun 23, 2026
@github-actions

github-actions Bot commented Jun 23, 2026

Copy link
Copy Markdown

✅ 40/40 passed, 2 skipped, 1m58s total

Running from acceptance #475

@codecov

codecov Bot commented Jun 23, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 80.15%. Comparing base (e5fee48) to head (17fcfeb).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #392   +/-   ##
=======================================
  Coverage   80.15%   80.15%           
=======================================
  Files          17       17           
  Lines        2474     2474           
  Branches      403      403           
=======================================
  Hits         1983     1983           
  Misses        364      364           
  Partials      127      127           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@CLAassistant

Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

asnare added a commit to databrickslabs/pytester that referenced this pull request Jun 24, 2026
## Changes

This PR works around a behaviour change introduced by Databricks SDK
v0.102.0 that causes unit tests to fail if they are using the `Config`
class. Specifically, during `__init__()` the `Config()` class now
performs a HTTP request against the host, and retries for 5 minutes if
the host does not exist.

Unit tests typically fill in a bogus host, which was fine previously
because initialising `Config` was inert and didn't trigger network
calls. Now that it does, some sort of workaround (such as
monkey-patching) is required.

Incidental change:

- Dependency-management for the project was out-of-date, and stopped
working because the lockfile referred directly to an internal PyPi proxy
that is no longer intended for use. As such the plumbing for locking
dependencies was updated, and the lockfile regenerated.

### Linked issues

Tests, same as: databrickslabs/blueprint#331
For `Makefile`, same as: databrickslabs/blueprint#392

### Tests

- updated unit tests
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working dependencies Pull requests that update a dependency file internal do not show this PR in changelog

Projects

Status: Ready for Review

Development

Successfully merging this pull request may close these issues.

2 participants