waitless 1.0.2__tar.gz → 1.0.3__tar.gz

{waitless-1.0.2/waitless.egg-info → waitless-1.0.3}/PKG-INFO

@@ -1,12 +1,12 @@
 Metadata-Version: 2.4
 Name: waitless
-Version: 1.0.2
-Summary: Eliminate explicit waits in UI automation by detecting true UI stability
+Version: 1.0.3
+Summary: Reduce explicit waits in Selenium by evaluating UI stability signals
 Author-email: Dhiraj Das <dhirajdas.666@gmail.com>
 License-Expression: MIT
-Project-URL: Homepage, https://www.dhirajdas.dev/project/waitless
-Project-URL: Documentation, https://www.dhirajdas.dev/project/waitless
-Project-URL: Repository, https://github.com/godhiraj-code/waitless
+Project-URL: Homepage, https://www.dhirajdas.dev
+Project-URL: Documentation, https://github.com/godhiraj-code/waitless#readme
+Project-URL: Repository, https://github.com/godhiraj-code/waitless.git
 Project-URL: Issues, https://github.com/godhiraj-code/waitless/issues
 Keywords: selenium,automation,testing,ui-testing,wait,stability,flaky-tests
 Classifier: Development Status :: 4 - Beta
@@ -36,9 +36,7 @@ Dynamic: license-file
 
 Reduce explicit waits and sleeps by automatically evaluating multiple UI stability signals.
 
-[Watch the demo and read the architecture case study](https://www.dhirajdas.dev/project/waitless) · [Install from PyPI](https://pypi.org/project/waitless/)
 
-![Waitless stability demo](examples/waitless_demo.webp)
 
 ## Installation
 
@@ -53,16 +51,16 @@ from selenium import webdriver
 from selenium.webdriver.common.by import By
 from waitless import stabilize
 
-# Create driver as usual
 driver = webdriver.Chrome()
-
-# Enable automatic stabilization - ONE LINE
 driver = stabilize(driver)
 
-# All interactions now auto-wait for stability
-driver.get("https://example.com")
-driver.find_element(By.ID, "login-button").click()  # ← Auto-waits!
-driver.find_element(By.ID, "username").send_keys("user")  # ← Auto-waits!
+# Navigation, lookups, and common element actions now wait for stability.
+driver.get(
+    "data:text/html,<input id='username'><button id='login-button'>Log in</button>"
+)
+driver.find_element(By.ID, "username").send_keys("user")
+driver.find_element(By.ID, "login-button").click()
+driver.quit()
 ```
 
 ## Why Waitless?
@@ -81,22 +79,23 @@ Automation tests fail because interactions happen while the UI is still changing
 | Approach | Problem |
 |----------|---------|
 | `time.sleep(2)` | Too slow, still fails sometimes |
-| `WebDriverWait` | Only checks one element, misses page-wide state |
+| `WebDriverWait` | Requires an explicit condition at each synchronization point |
 | Retries | Masks the real problem, adds flakiness |
 
 ### The Waitless Solution
 
-Waitless monitors the **entire page** for stability signals:
+Waitless evaluates page-level stability signals:
 
-- ✅ DOM mutation activity (MutationObserver, including **Shadow DOM**)
-- ✅ Pending network requests (XHR/fetch interception)
-- ✅ CSS animations and transitions
-- ✅ Layout stability (element movement)
-- ✅ WebSocket/SSE activity (opt-in)
-- ✅ Framework hooks (React/Angular/Vue, opt-in)
-- ✅ Same-origin iframe load readiness (opt-in; not full child-frame signal injection)
+- DOM mutation activity (MutationObserver, including **Shadow DOM**)
+- Pending network requests (XHR/fetch interception after instrumentation is installed)
+- CSS animations and transitions
+- Layout stability for interactive elements
+- WebSocket/SSE activity (opt-in)
+- Framework hooks (React/Angular/Vue, opt-in)
+- Same-origin iframe load readiness (opt-in; not full child-frame signal injection)
 
-When you interact, waitless ensures the page is truly ready.
+Before supported interactions, Waitless polls until the enabled mandatory signals
+meet their configured thresholds.
 
 ## Configuration
 
@@ -204,14 +203,15 @@ Many apps have background traffic that never stops:
 - Feature flags
 - WebSocket heartbeats
 
-If tests timeout frequently, try:
+If known background traffic exceeds the default, raise the threshold carefully:
 ```python
-config = StabilizationConfig(network_idle_threshold=2)
+config = StabilizationConfig(network_idle_threshold=3)
 ```
 
 ### Wrapped Elements
 
-The stabilized driver returns wrapped elements that auto-wait. They behave like WebElements but:
+The stabilized driver returns wrapped elements that auto-wait before `click()`,
+`send_keys()`, `submit()`, and `clear()`. They behave like WebElements but:
 
 - `isinstance(element, WebElement)` returns `False`
 - Use `.unwrap()` to get the original element if needed
@@ -221,15 +221,14 @@ element = driver.find_element(By.ID, "button")
 original = element.unwrap()  # Gets the real WebElement
 ```
 
-## v1.0.0 New Features
+## Optional Signals
 
 - **WebSocket/SSE Awareness** - Track WebSocket and Server-Sent Events activity
 - **Framework Adapters** - React, Angular, Vue hooks for framework-specific settling
 - **iframe Support** - Monitor same-origin iframes
-- **Performance Benchmarks** - Built-in benchmark suite
+- **Performance benchmarks** - Run the repository benchmark against your environment
 
 ```python
-# Enable new v1.0 features
 config = StabilizationConfig(
     track_websocket=True,         # WebSocket monitoring
     track_sse=True,               # SSE monitoring
@@ -242,10 +241,10 @@ config = StabilizationConfig(
 
 | Metric | Typical Value |
 |--------|---------------|
-| Instrumentation injection | Environment-dependent; run `python -m benchmarks.overhead_test` |
-| Per-poll overhead | Environment-dependent; run the bundled benchmark |
+| Instrumentation injection | Environment-dependent; from a repository checkout, run `python benchmarks/overhead_test.py` |
+| Per-poll overhead | Environment-dependent; run the repository benchmark |
 | Poll interval (default) | 50ms |
-| Typical stabilization | 50-200ms after activity |
+| Stabilization time | Depends on page activity, thresholds, and environment |
 
 ### Navigation Handling
 
@@ -260,12 +259,18 @@ JavaScript, Waitless validates/re-injects instrumentation on the next wait:
 This does not observe routes continuously, and cross-origin iframe internals remain
 outside the browser same-origin boundary.
 
+Because instrumentation is installed after Selenium's synchronous navigation call
+returns, requests that start and finish during navigation are not observed. Requests
+started after instrumentation is installed are tracked.
+
 `find_elements()` keeps Selenium's immediate-empty lookup semantics: after the
 page-stability wait, it performs one lookup and returns `[]` when there are no matches.
+By contrast, `find_element()` retries `NoSuchElementException` until the configured
+timeout after the page-stability wait.
 
 ## Current Limitations
 
-- **Selenium only** - Playwright support planned
+- **Selenium only** - No Playwright integration
 - **Sync only** - No async/await support yet
 - **No Service Workers** - SW network requests not intercepted
 
@@ -294,7 +299,3 @@ See [CHANGELOG.md](CHANGELOG.md) for version history.
 ## License
 
 MIT
-
-## Try It on a Real Flaky Flow
-
-Run Waitless against one Selenium flow that currently uses sleeps or retries, then compare failures and elapsed time before and after. Share a sanitized result in an issue. If it removes a sleep or retry, [star the repository](https://github.com/godhiraj-code/waitless). The [full case study](https://www.dhirajdas.dev/project/waitless) explains the architecture and trade-offs.

{waitless-1.0.2 → waitless-1.0.3}/README.md

@@ -6,9 +6,7 @@
 
 Reduce explicit waits and sleeps by automatically evaluating multiple UI stability signals.
 
-[Watch the demo and read the architecture case study](https://www.dhirajdas.dev/project/waitless) · [Install from PyPI](https://pypi.org/project/waitless/)
 
-![Waitless stability demo](examples/waitless_demo.webp)
 
 ## Installation
 
@@ -23,16 +21,16 @@ from selenium import webdriver
 from selenium.webdriver.common.by import By
 from waitless import stabilize
 
-# Create driver as usual
 driver = webdriver.Chrome()
-
-# Enable automatic stabilization - ONE LINE
 driver = stabilize(driver)
 
-# All interactions now auto-wait for stability
-driver.get("https://example.com")
-driver.find_element(By.ID, "login-button").click()  # ← Auto-waits!
-driver.find_element(By.ID, "username").send_keys("user")  # ← Auto-waits!
+# Navigation, lookups, and common element actions now wait for stability.
+driver.get(
+    "data:text/html,<input id='username'><button id='login-button'>Log in</button>"
+)
+driver.find_element(By.ID, "username").send_keys("user")
+driver.find_element(By.ID, "login-button").click()
+driver.quit()
 ```
 
 ## Why Waitless?
@@ -51,22 +49,23 @@ Automation tests fail because interactions happen while the UI is still changing
 | Approach | Problem |
 |----------|---------|
 | `time.sleep(2)` | Too slow, still fails sometimes |
-| `WebDriverWait` | Only checks one element, misses page-wide state |
+| `WebDriverWait` | Requires an explicit condition at each synchronization point |
 | Retries | Masks the real problem, adds flakiness |
 
 ### The Waitless Solution
 
-Waitless monitors the **entire page** for stability signals:
+Waitless evaluates page-level stability signals:
 
-- ✅ DOM mutation activity (MutationObserver, including **Shadow DOM**)
-- ✅ Pending network requests (XHR/fetch interception)
-- ✅ CSS animations and transitions
-- ✅ Layout stability (element movement)
-- ✅ WebSocket/SSE activity (opt-in)
-- ✅ Framework hooks (React/Angular/Vue, opt-in)
-- ✅ Same-origin iframe load readiness (opt-in; not full child-frame signal injection)
+- DOM mutation activity (MutationObserver, including **Shadow DOM**)
+- Pending network requests (XHR/fetch interception after instrumentation is installed)
+- CSS animations and transitions
+- Layout stability for interactive elements
+- WebSocket/SSE activity (opt-in)
+- Framework hooks (React/Angular/Vue, opt-in)
+- Same-origin iframe load readiness (opt-in; not full child-frame signal injection)
 
-When you interact, waitless ensures the page is truly ready.
+Before supported interactions, Waitless polls until the enabled mandatory signals
+meet their configured thresholds.
 
 ## Configuration
 
@@ -174,14 +173,15 @@ Many apps have background traffic that never stops:
 - Feature flags
 - WebSocket heartbeats
 
-If tests timeout frequently, try:
+If known background traffic exceeds the default, raise the threshold carefully:
 ```python
-config = StabilizationConfig(network_idle_threshold=2)
+config = StabilizationConfig(network_idle_threshold=3)
 ```
 
 ### Wrapped Elements
 
-The stabilized driver returns wrapped elements that auto-wait. They behave like WebElements but:
+The stabilized driver returns wrapped elements that auto-wait before `click()`,
+`send_keys()`, `submit()`, and `clear()`. They behave like WebElements but:
 
 - `isinstance(element, WebElement)` returns `False`
 - Use `.unwrap()` to get the original element if needed
@@ -191,15 +191,14 @@ element = driver.find_element(By.ID, "button")
 original = element.unwrap()  # Gets the real WebElement
 ```
 
-## v1.0.0 New Features
+## Optional Signals
 
 - **WebSocket/SSE Awareness** - Track WebSocket and Server-Sent Events activity
 - **Framework Adapters** - React, Angular, Vue hooks for framework-specific settling
 - **iframe Support** - Monitor same-origin iframes
-- **Performance Benchmarks** - Built-in benchmark suite
+- **Performance benchmarks** - Run the repository benchmark against your environment
 
 ```python
-# Enable new v1.0 features
 config = StabilizationConfig(
     track_websocket=True,         # WebSocket monitoring
     track_sse=True,               # SSE monitoring
@@ -212,10 +211,10 @@ config = StabilizationConfig(
 
 | Metric | Typical Value |
 |--------|---------------|
-| Instrumentation injection | Environment-dependent; run `python -m benchmarks.overhead_test` |
-| Per-poll overhead | Environment-dependent; run the bundled benchmark |
+| Instrumentation injection | Environment-dependent; from a repository checkout, run `python benchmarks/overhead_test.py` |
+| Per-poll overhead | Environment-dependent; run the repository benchmark |
 | Poll interval (default) | 50ms |
-| Typical stabilization | 50-200ms after activity |
+| Stabilization time | Depends on page activity, thresholds, and environment |
 
 ### Navigation Handling
 
@@ -230,12 +229,18 @@ JavaScript, Waitless validates/re-injects instrumentation on the next wait:
 This does not observe routes continuously, and cross-origin iframe internals remain
 outside the browser same-origin boundary.
 
+Because instrumentation is installed after Selenium's synchronous navigation call
+returns, requests that start and finish during navigation are not observed. Requests
+started after instrumentation is installed are tracked.
+
 `find_elements()` keeps Selenium's immediate-empty lookup semantics: after the
 page-stability wait, it performs one lookup and returns `[]` when there are no matches.
+By contrast, `find_element()` retries `NoSuchElementException` until the configured
+timeout after the page-stability wait.
 
 ## Current Limitations
 
-- **Selenium only** - Playwright support planned
+- **Selenium only** - No Playwright integration
 - **Sync only** - No async/await support yet
 - **No Service Workers** - SW network requests not intercepted
 
@@ -264,7 +269,3 @@ See [CHANGELOG.md](CHANGELOG.md) for version history.
 ## License
 
 MIT
-
-## Try It on a Real Flaky Flow
-
-Run Waitless against one Selenium flow that currently uses sleeps or retries, then compare failures and elapsed time before and after. Share a sanitized result in an issue. If it removes a sleep or retry, [star the repository](https://github.com/godhiraj-code/waitless). The [full case study](https://www.dhirajdas.dev/project/waitless) explains the architecture and trade-offs.

{waitless-1.0.2 → waitless-1.0.3}/pyproject.toml

@@ -4,8 +4,8 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "waitless"
-version = "1.0.2"
-description = "Eliminate explicit waits in UI automation by detecting true UI stability"
+version = "1.0.3"
+description = "Reduce explicit waits in Selenium by evaluating UI stability signals"
 readme = "README.md"
 license = "MIT"
 requires-python = ">=3.9"
@@ -38,9 +38,9 @@ dependencies = [
 ]
 
 [project.urls]
-Homepage = "https://www.dhirajdas.dev/project/waitless"
-Documentation = "https://www.dhirajdas.dev/project/waitless"
-Repository = "https://github.com/godhiraj-code/waitless"
+Homepage = "https://www.dhirajdas.dev"
+Documentation = "https://github.com/godhiraj-code/waitless#readme"
+Repository = "https://github.com/godhiraj-code/waitless.git"
 Issues = "https://github.com/godhiraj-code/waitless/issues"
 
 [project.scripts]

{waitless-1.0.2 → waitless-1.0.3}/waitless/__init__.py

@@ -1,8 +1,8 @@
 """
-Waitless - Zero-wait UI automation stabilization library.
+Waitless - Automatic Selenium UI stabilization library.
 
-Eliminate explicit waits and sleeps in UI automation by automatically
-waiting for true UI stability instead of time-based conditions.
+Reduce explicit waits and sleeps by evaluating configurable UI stability
+signals before supported Selenium interactions.
 
 Basic Usage:
     from waitless import stabilize
@@ -36,7 +36,7 @@ Disable:
     driver = unstabilize(driver)  # Back to original behavior
 """
 
-__version__ = '1.0.2'
+__version__ = '1.0.3'
 __author__ = 'Dhiraj Das'
 
 # Public API

{waitless-1.0.2 → waitless-1.0.3}/waitless/__main__.py

@@ -14,7 +14,7 @@ def main():
     """Main CLI entry point."""
     parser = argparse.ArgumentParser(
         prog='waitless',
-        description='Waitless - Zero-wait UI automation stabilization'
+        description='Waitless - Automatic Selenium UI stabilization'
     )
     
     subparsers = parser.add_subparsers(dest='command', help='Available commands')

{waitless-1.0.2 → waitless-1.0.3}/waitless/config.py

@@ -66,7 +66,8 @@ class StabilizationConfig:
                          Options: 'react', 'angular', 'vue'. Default empty (auto-detect off).
                          When specified, waitless will inject framework-specific hooks.
         
-        track_iframes: Whether to inject instrumentation into same-origin iframes.
+        track_iframes: Whether to monitor same-origin iframe load readiness.
+                       This does not inject full child-frame instrumentation.
                        Default False. Cross-origin iframes cannot be accessed.
     """
     

{waitless-1.0.2 → waitless-1.0.3}/waitless/instrumentation.py

@@ -12,7 +12,7 @@ INSTRUMENTATION_SCRIPT = """
     
     window.__waitless__ = {
         _initialized: true,
-        _version: '1.0.1',
+        _version: '1.0.3',
         
         // State tracking
         pendingRequests: 0,
@@ -249,8 +249,16 @@ INSTRUMENTATION_SCRIPT = """
                 xhr.addEventListener('loadend', function() {
                     self._requestEnded(url, 'xhr', xhr.status);
                 });
-                
-                return self._originalXHRSend.apply(this, arguments);
+
+                try {
+                    return self._originalXHRSend.apply(this, arguments);
+                } catch (error) {
+                    // Synchronous failures (for example, send() before open()) do
+                    // not emit loadend. Balance the counter before preserving the
+                    // browser's original exception behavior.
+                    self._requestEnded(url, 'xhr', 'error');
+                    throw error;
+                }
             };
         },
 

{waitless-1.0.2 → waitless-1.0.3/waitless.egg-info}/PKG-INFO

@@ -1,12 +1,12 @@
 Metadata-Version: 2.4
 Name: waitless
-Version: 1.0.2
-Summary: Eliminate explicit waits in UI automation by detecting true UI stability
+Version: 1.0.3
+Summary: Reduce explicit waits in Selenium by evaluating UI stability signals
 Author-email: Dhiraj Das <dhirajdas.666@gmail.com>
 License-Expression: MIT
-Project-URL: Homepage, https://www.dhirajdas.dev/project/waitless
-Project-URL: Documentation, https://www.dhirajdas.dev/project/waitless
-Project-URL: Repository, https://github.com/godhiraj-code/waitless
+Project-URL: Homepage, https://www.dhirajdas.dev
+Project-URL: Documentation, https://github.com/godhiraj-code/waitless#readme
+Project-URL: Repository, https://github.com/godhiraj-code/waitless.git
 Project-URL: Issues, https://github.com/godhiraj-code/waitless/issues
 Keywords: selenium,automation,testing,ui-testing,wait,stability,flaky-tests
 Classifier: Development Status :: 4 - Beta
@@ -36,9 +36,7 @@ Dynamic: license-file
 
 Reduce explicit waits and sleeps by automatically evaluating multiple UI stability signals.
 
-[Watch the demo and read the architecture case study](https://www.dhirajdas.dev/project/waitless) · [Install from PyPI](https://pypi.org/project/waitless/)
 
-![Waitless stability demo](examples/waitless_demo.webp)
 
 ## Installation
 
@@ -53,16 +51,16 @@ from selenium import webdriver
 from selenium.webdriver.common.by import By
 from waitless import stabilize
 
-# Create driver as usual
 driver = webdriver.Chrome()
-
-# Enable automatic stabilization - ONE LINE
 driver = stabilize(driver)
 
-# All interactions now auto-wait for stability
-driver.get("https://example.com")
-driver.find_element(By.ID, "login-button").click()  # ← Auto-waits!
-driver.find_element(By.ID, "username").send_keys("user")  # ← Auto-waits!
+# Navigation, lookups, and common element actions now wait for stability.
+driver.get(
+    "data:text/html,<input id='username'><button id='login-button'>Log in</button>"
+)
+driver.find_element(By.ID, "username").send_keys("user")
+driver.find_element(By.ID, "login-button").click()
+driver.quit()
 ```
 
 ## Why Waitless?
@@ -81,22 +79,23 @@ Automation tests fail because interactions happen while the UI is still changing
 | Approach | Problem |
 |----------|---------|
 | `time.sleep(2)` | Too slow, still fails sometimes |
-| `WebDriverWait` | Only checks one element, misses page-wide state |
+| `WebDriverWait` | Requires an explicit condition at each synchronization point |
 | Retries | Masks the real problem, adds flakiness |
 
 ### The Waitless Solution
 
-Waitless monitors the **entire page** for stability signals:
+Waitless evaluates page-level stability signals:
 
-- ✅ DOM mutation activity (MutationObserver, including **Shadow DOM**)
-- ✅ Pending network requests (XHR/fetch interception)
-- ✅ CSS animations and transitions
-- ✅ Layout stability (element movement)
-- ✅ WebSocket/SSE activity (opt-in)
-- ✅ Framework hooks (React/Angular/Vue, opt-in)
-- ✅ Same-origin iframe load readiness (opt-in; not full child-frame signal injection)
+- DOM mutation activity (MutationObserver, including **Shadow DOM**)
+- Pending network requests (XHR/fetch interception after instrumentation is installed)
+- CSS animations and transitions
+- Layout stability for interactive elements
+- WebSocket/SSE activity (opt-in)
+- Framework hooks (React/Angular/Vue, opt-in)
+- Same-origin iframe load readiness (opt-in; not full child-frame signal injection)
 
-When you interact, waitless ensures the page is truly ready.
+Before supported interactions, Waitless polls until the enabled mandatory signals
+meet their configured thresholds.
 
 ## Configuration
 
@@ -204,14 +203,15 @@ Many apps have background traffic that never stops:
 - Feature flags
 - WebSocket heartbeats
 
-If tests timeout frequently, try:
+If known background traffic exceeds the default, raise the threshold carefully:
 ```python
-config = StabilizationConfig(network_idle_threshold=2)
+config = StabilizationConfig(network_idle_threshold=3)
 ```
 
 ### Wrapped Elements
 
-The stabilized driver returns wrapped elements that auto-wait. They behave like WebElements but:
+The stabilized driver returns wrapped elements that auto-wait before `click()`,
+`send_keys()`, `submit()`, and `clear()`. They behave like WebElements but:
 
 - `isinstance(element, WebElement)` returns `False`
 - Use `.unwrap()` to get the original element if needed
@@ -221,15 +221,14 @@ element = driver.find_element(By.ID, "button")
 original = element.unwrap()  # Gets the real WebElement
 ```
 
-## v1.0.0 New Features
+## Optional Signals
 
 - **WebSocket/SSE Awareness** - Track WebSocket and Server-Sent Events activity
 - **Framework Adapters** - React, Angular, Vue hooks for framework-specific settling
 - **iframe Support** - Monitor same-origin iframes
-- **Performance Benchmarks** - Built-in benchmark suite
+- **Performance benchmarks** - Run the repository benchmark against your environment
 
 ```python
-# Enable new v1.0 features
 config = StabilizationConfig(
     track_websocket=True,         # WebSocket monitoring
     track_sse=True,               # SSE monitoring
@@ -242,10 +241,10 @@ config = StabilizationConfig(
 
 | Metric | Typical Value |
 |--------|---------------|
-| Instrumentation injection | Environment-dependent; run `python -m benchmarks.overhead_test` |
-| Per-poll overhead | Environment-dependent; run the bundled benchmark |
+| Instrumentation injection | Environment-dependent; from a repository checkout, run `python benchmarks/overhead_test.py` |
+| Per-poll overhead | Environment-dependent; run the repository benchmark |
 | Poll interval (default) | 50ms |
-| Typical stabilization | 50-200ms after activity |
+| Stabilization time | Depends on page activity, thresholds, and environment |
 
 ### Navigation Handling
 
@@ -260,12 +259,18 @@ JavaScript, Waitless validates/re-injects instrumentation on the next wait:
 This does not observe routes continuously, and cross-origin iframe internals remain
 outside the browser same-origin boundary.
 
+Because instrumentation is installed after Selenium's synchronous navigation call
+returns, requests that start and finish during navigation are not observed. Requests
+started after instrumentation is installed are tracked.
+
 `find_elements()` keeps Selenium's immediate-empty lookup semantics: after the
 page-stability wait, it performs one lookup and returns `[]` when there are no matches.
+By contrast, `find_element()` retries `NoSuchElementException` until the configured
+timeout after the page-stability wait.
 
 ## Current Limitations
 
-- **Selenium only** - Playwright support planned
+- **Selenium only** - No Playwright integration
 - **Sync only** - No async/await support yet
 - **No Service Workers** - SW network requests not intercepted
 
@@ -294,7 +299,3 @@ See [CHANGELOG.md](CHANGELOG.md) for version history.
 ## License
 
 MIT
-
-## Try It on a Real Flaky Flow
-
-Run Waitless against one Selenium flow that currently uses sleeps or retries, then compare failures and elapsed time before and after. Share a sanitized result in an issue. If it removes a sleep or retry, [star the repository](https://github.com/godhiraj-code/waitless). The [full case study](https://www.dhirajdas.dev/project/waitless) explains the architecture and trade-offs.