- Date: 2026-05-15 local
- Hardware: SimpleAir RevE powered through the Joulescope JS220 current path from a 3.7 V bench source. The JS220 voltage sense can still report the bench source when the target current path is switched off.
- Instrument: Joulescope JS220
u/js220/005920, firmware 1.3.0, FPGA 1.3.3, MCP driver 2.1.0 - Firmware revision:
82f8ae0 - Scope: current draw and power during cold boot, first SEN66 duty-cycle measurement, post-boot nominal operation, no-RTT power-audit firmware variants, and retained RAM firmware-event tracing
- Status: Measured and complete with explicit physical limitations
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
| # vllm-qwen35-toolfix.patch | |
| # | |
| # What this patches: | |
| # 8 vLLM source files (~1.3 KLOC of changes) baked into the local image | |
| # ghcr.io/juanqui/vllm-qwen35-toolfix:0.19.1rc1.dev328-g18013df6a, on top | |
| # of the upstream vllm/vllm-openai:cu130-nightly base. | |
| # | |
| # Origin (per /mnt/nvme2/experiments/2026-04-23-qwen36-27b-fp8-bench/journal/{14,15}*.md): | |
| # - PR #35687 min_new_tokens allow-list -> config/model.py, | |
| # entrypoints/openai/{chat_completion,completion}/protocol.py |
Findings (root cause)
- Supabase invite emails default to ConfirmationURL (…/auth/v1/verify?token=…&type=invite&redirect_to=…). After verification, Supabase redirects to your site with tokens in the URL hash (#access_token=…). That requires client-side handling; otherwise no session/cookie is set and users land unauthenticated on your homepage.
- Your app has a server route at app/auth/confirm/route.ts that expects token_hash and type query params and calls supabase.auth.verifyOtp({ type, token_hash }) to set cookies server-side—but the current invite link doesn’t hit that route and uses token (not token_hash).
- Net: there’s a mismatch between the link Supabase sends and how your app expects to finalize auth; you’re not processing the hash fragment, so the invite appears to “do nothing”.
What “should” happen
- Either: handle the hash fragment client-side (getSessionFromUrl) and then sync to server cookies; or: bypass the hash entirely by customizing the email invite link to point directly at your server ro
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
| ## Task | |
| Your task is to deeply and thoroughly research all of the aspects, requirements, challenges, and best practices for moving our family from the United States to Australia (ideally Sydney area). | |
| I have already compiled a list of reports that we need to generate. Please refer to `## Reports` below which indicates all the reports we have to generate as well as the answers that need to be contained in each of them. | |
| When writing each report, make sure you: | |
| 1. Include a section titled `## Recommendation` which contains the research-backed recommendation for our family. | |
| 2. All the other sections outside of `## Recommendation` need to be informational and not specific to our family. |
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
| # Task - Implement a dynamic LoRa power tuning algorithm | |
| Your task is to implement a dynamic LoRa power tuning algoirithm that automatically determines the optimal LoRa radio transmit power to use in order to balance both reliable signal reception by the gateway and power effeciency of our sensor. | |
| ## Requirements | |
| - Our STM32WL5M is configured for for RFO_LP with a maximum power output of 15dBm. We should never exceed 15dBm. | |
| - The lowst possible power setting is 0dBm. | |
| - Power can be increased in increments of 1dBm. | |
| - At boot, we should start with a power of 8dBm. |
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
| # LeakyRF Custom Definition | |
| template: | |
| - sensor: | |
| - name: "LeakyRF 24h Water Usage" | |
| unique_id: leakyrf_24h_water_usage | |
| unit_of_measurement: "gal" | |
| state_class: "measurement" | |
| device_class: "water" | |
| state: > |
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
| INFO - V (27014) wifi: | |
| INFO - scan specific ssid=Wokwi-GUEST | |
| INFO - | |
| INFO - V (27081) wifi: | |
| INFO - start max timer | |
| INFO - | |
| INFO - D (27241) wifi: |
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
| M561 ; clear any bed transform | |
| G29 S2 ; Clear bed height map | |
| ; Probe 2-points | |
| M401 ; Deploy probe - deployprobe.g | |
| G30 P0 X20 Y200 Z-9999 ; Center Left | |
| G30 P1 X340 Y200 Z-9999 S2 ; Center Right | |
| M402 ; Retract Probe - retractprobe.g |
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
| 0x45b1fDcA7aa4acF6957c464815E3708B0aB7354a |
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
| "use strict"; | |
| var request = require('request'); | |
| // request login | |
| request({ | |
| url: 'https://home.nest.com/user/login', | |
| method: 'POST', | |
| headers: { | |
| 'user-agent': 'Nest/2.1.3 CFNetwork/548.0.4', |
NewerOlder