5x400s

2026-06-08T00:00:00+00:00
As fit as a cow.</p>
Third rep had a stitch that I could only walk off; came back during the fourth. Finished with a little pride on the final fifth.</p>
Need better hydration. Didn't eat well today to cover this effort, but it's a good measure of where I am.</p>
Body aches from some HITT weekend house cleaning.</p>
Stat</th> Value</th></tr></thead>
Distance</td> 4.02 km</td></tr>
Duration</td> 23:25</td></tr>
Pace</td> 5:49 /km</td></tr>
Elevation Gain</td>
13 m</td></tr> </tbody></table>
Heart Rate Zones</h2>
---
config:
  themeVariables:
    xyChart:
      plotColorPalette: "#555555,#FF8200,#56CC3C,#4090D4,#AAAAAA"
      backgroundColor: "transparent"
---
        
xychart horizontal
    title "Time in Heart Rate Zones (%)"
    x-axis ["Zone 5 Maximum", "Zone 4 Threshold", "Zone 3 Aerobic", "Zone 2 Easy", "Zone 1 Warm Up"]
    y-axis "%" 2 --> 100
    bar [6.8, 0.0, 0.0, 0.0, 0.0]
    bar [0.0, 27.2, 0.0, 0.0, 0.0]
    bar [0.0, 0.0, 31.9, 0.0, 0.0]
    bar [0.0, 0.0, 0.0, 3.9, 0.0]
    bar [0.0, 0.0, 0.0, 0.0, 30.3]
</pre>


Toronto - Easy Run
2026-06-08T00:00:00+00:00
Warm-up prior to intervals.</p>
Stat</th> Value</th></tr></thead>

Distance</td> 1.27 km</td></tr>
Duration</td> 7:50</td></tr>
Pace</td> 6:10 /km</td></tr>
Elevation Gain</td> 11 m</td></tr>
</tbody></table>
Heart Rate Zones</h2>

---
config:
  themeVariables:
    xyChart:
      plotColorPalette: "#555555,#FF8200,#56CC3C,#4090D4,#AAAAAA"
      backgroundColor: "transparent"
---
        
xychart horizontal
    title "Time in Heart Rate Zones (%)"
    x-axis ["Zone 5 Maximum", "Zone 4 Threshold", "Zone 3 Aerobic", "Zone 2 Easy", "Zone 1 Warm Up"]
    y-axis "%" 2 --> 100
    bar [0.0, 0.0, 0.0, 0.0, 0.0]
    bar [0.0, 0.0, 0.0, 0.0, 0.0]
    bar [0.0, 0.0, 9.4, 0.0, 0.0]
    bar [0.0, 0.0, 0.0, 11.4, 0.0]
    bar [0.0, 0.0, 0.0, 0.0, 79.2]
</pre>


Toronto - Easy Run
2026-06-01T00:00:00+00:00
Encountered a very loud dog that looked like it was going to attack me while the leash was a bit too slack, and I had to jump onto the road. Shouty driver was shouty before he realized my predicament. Took a bit to get back into the run and relax. 🤷‍♂️</p>
Good weather, but didn't stretch. Right leg was hyper extending because the back of the knee was paining a bit - nothing new that I haven't experienced before.</p>
Stat</th> Value</th></tr></thead>

Distance</td> 7.49 km</td></tr>
Duration</td> 40:02</td></tr>
Pace</td> 5:21 /km</td></tr>
Elevation Gain</td> 50 m</td></tr>
</tbody></table>
Heart Rate Zones</h2>

---
config:
  themeVariables:
    xyChart:
      plotColorPalette: "#555555,#FF8200,#56CC3C,#4090D4,#AAAAAA"
      backgroundColor: "transparent"
---
        
xychart horizontal
    title "Time in Heart Rate Zones (%)"
    x-axis ["Zone 5 Maximum", "Zone 4 Threshold", "Zone 3 Aerobic", "Zone 2 Easy", "Zone 1 Warm Up"]
    y-axis "%" 2 --> 100
    bar [0.0, 0.0, 0.0, 0.0, 0.0]
    bar [0.0, 3.6, 0.0, 0.0, 0.0]
    bar [0.0, 0.0, 29.0, 0.0, 0.0]
    bar [0.0, 0.0, 0.0, 17.4, 0.0]
    bar [0.0, 0.0, 0.0, 0.0, 49.9]
</pre>


Toronto - Easy Run
2026-05-31T00:00:00+00:00
Felt very unfit despite a looong warmup and stretch. Need to make that training plan and build up fatigue in the legs again.</p>
Ice cream for a job well done at the end.</p>
Stat</th> Value</th></tr></thead>

Distance</td> 7.82 km</td></tr>
Duration</td> 43:02</td></tr>
Pace</td> 5:30 /km</td></tr>
Elevation Gain</td> 56 m</td></tr>
</tbody></table>
Heart Rate Zones</h2>

---
config:
  themeVariables:
    xyChart:
      plotColorPalette: "#555555,#FF8200,#56CC3C,#4090D4,#AAAAAA"
      backgroundColor: "transparent"
---
        
xychart horizontal
    title "Time in Heart Rate Zones (%)"
    x-axis ["Zone 5 Maximum", "Zone 4 Threshold", "Zone 3 Aerobic", "Zone 2 Easy", "Zone 1 Warm Up"]
    y-axis "%" 2 --> 100
    bar [0.0, 0.0, 0.0, 0.0, 0.0]
    bar [0.0, 0.0, 0.0, 0.0, 0.0]
    bar [0.0, 0.0, 8.8, 0.0, 0.0]
    bar [0.0, 0.0, 0.0, 18.1, 0.0]
    bar [0.0, 0.0, 0.0, 0.0, 73.2]
</pre>


Fun Running
2026-05-25T00:00:00+00:00
Went harder for fun, I guess. Didn't feel like it, but wanted to see what was in the engine.</p>
Shoes were tightened a bit much and the t-shirt I wore isn't as breathable.</p>
Felt good, all things considered.</p>
Stat</th> Value</th></tr></thead>

Distance</td> 5.01 km</td></tr>
Duration</td> 26:23</td></tr>
Pace</td> 5:16 /km</td></tr>
Elevation Gain</td> 40 m</td></tr>
</tbody></table>
Heart Rate Zones</h2>

---
config:
  themeVariables:
    xyChart:
      plotColorPalette: "#555555,#FF8200,#56CC3C,#4090D4,#AAAAAA"
      backgroundColor: "transparent"
---
        
xychart horizontal
    title "Time in Heart Rate Zones (%)"
    x-axis ["Zone 5 Maximum", "Zone 4 Threshold", "Zone 3 Aerobic", "Zone 2 Easy", "Zone 1 Warm Up"]
    y-axis "%" 2 --> 100
    bar [0.0, 0.0, 0.0, 0.0, 0.0]
    bar [0.0, 8.8, 0.0, 0.0, 0.0]
    bar [0.0, 0.0, 74.6, 0.0, 0.0]
    bar [0.0, 0.0, 0.0, 4.2, 0.0]
    bar [0.0, 0.0, 0.0, 0.0, 12.4]
</pre>


Auto-resolve Jujutsu conflicts with your AI agent
2026-05-25T00:00:00+00:00
With Jujutsu, I've been able to work in multiple workstreams more efficiently than before. This means that if I'm working on multiple things, there is a higher likelihood of something going stale while I wait for a review or touch multiple files.
Dealing with conflicts aren't so bad these days</a>, however if I can automate the easy ones, why not?</p>
This is the prompt I've been using with my agent whenever I have a list of changes that have conflicts and don't need me to participate actively on it.</p>
Using the jj version control system, fix the conflicts that are in the changesets from `<start_rev>` to `<end_rev>`. Keep trying until there are no more "(conflict)" in the changesets between those two IDs.</span></span></code></pre>


Toronto - Easy Run
2026-05-17T00:00:00+00:00
So many excuses to use!</p>

Muscle pain from bowling (with style) during the week. Used the massage gun to get a warmup started, but it's still a bit touchy.</li>
Poor sleep from growing heat overnight.</li>
Stupidly hot outside right now with a heatwave in-progress.</li>
Made a few wrong turns trying to find the most shaded route.</li>
</ul>
I miss the cold already.</p>


  
</div>




  
</div>


Stat</th> Value</th></tr></thead>

Distance</td> 3.47 km</td></tr>
Duration</td> 21:00</td></tr>
Pace</td> 6:03 /km</td></tr>
Elevation Gain</td> 17 m</td></tr>
</tbody></table>
Heart Rate Zones</h2>

---
config:
  themeVariables:
    xyChart:
      plotColorPalette: "#555555,#FF8200,#56CC3C,#4090D4,#AAAAAA"
      backgroundColor: "transparent"
---

xychart horizontal
    title "Time in Heart Rate Zones (%)"
    x-axis ["Zone 5 Maximum", "Zone 4 Threshold", "Zone 3 Aerobic", "Zone 2 Easy", "Zone 1 Warm Up"]
    y-axis "%" 2 --> 100
    bar [0.0, 0.0, 0.0, 0.0, 0.0]
    bar [0.0, 0.0, 0.0, 0.0, 0.0]
    bar [0.0, 0.0, 24.3, 0.0, 0.0]
    bar [0.0, 0.0, 0.0, 22.7, 0.0]
    bar [0.0, 0.0, 0.0, 0.0, 53.0]
</pre>


Sporting Life 10K 2026
2026-05-10T00:00:00+00:00
Better route, colder day, worse roads.</p>
Stat</th> Value</th></tr></thead>

Distance</td> 10.14 km</td></tr>
Duration</td> 1:33:42</td></tr>
Pace</td> 9:14 /km</td></tr>
Elevation Gain</td> 43 m</td></tr>
</tbody></table>
Heart Rate Zones</h2>

---
config:
  themeVariables:
    xyChart:
      plotColorPalette: "#555555,#FF8200,#56CC3C,#4090D4,#AAAAAA"
      backgroundColor: "transparent"
---
        
xychart horizontal
    title "Time in Heart Rate Zones (%)"
    x-axis ["Zone 5 Maximum", "Zone 4 Threshold", "Zone 3 Aerobic", "Zone 2 Easy", "Zone 1 Warm Up"]
    y-axis "%" 2 --> 100
    bar [0.0, 0.0, 0.0, 0.0, 0.0]
    bar [0.0, 0.0, 0.0, 0.0, 0.0]
    bar [0.0, 0.0, 0.9, 0.0, 0.0]
    bar [0.0, 0.0, 0.0, 5.0, 0.0]
    bar [0.0, 0.0, 0.0, 0.0, 94.1]
</pre>


jj presentation - cheat sheet
2026-05-08T00:00:00+00:00
jj presentation - cheat sheet</h1>
A throwaway Calculator app in mobile/android/fenix/.../calculator/</code> provides the demo material. Re-run between demos to reset:</p>
bash artifacts/jj-demo-setup.sh</span></span></code></pre>The starting stack</h2>
@  wip small fixes (absorb me)    ← uncommitted: two 1-line fixes</span></span>
○  E: Add equals and clear logic</span></span>
○  D: Add operator buttons and tighten outer padding   ← split target</span></span>
○  C: Add digit buttons                                ← absorb target #2</span></span>
○  B: Add CalculatorViewModel with display state       ← absorb target #1</span></span>
○  A: Add CalculatorScreen scaffold</span></span>
◆  main</span></span></code></pre>
The wip change contains two unrelated 1-line edits:</p>

CalculatorViewModel.kt</code>: MutableStateFlow("")</code> → MutableStateFlow("0")</code></li>
CalculatorScreen.kt</code>: Arrangement.spacedBy(4.dp)</code> → 8.dp</code> in DigitRow</code></li>
</ul>
Each line was last touched in a different commit, so absorb can route them.</p>

Demo 1 - jj split</code></h2>
Commit D bundles two unrelated changes: an operator-row feature (across both .kt files) and a one-line outer-padding tweak. Split them apart.</p>
jj edit  <D's change id>     # or: jj edit @--   if wip is on top of E</span></span>
jj split</span></span></code></pre>
The diff editor opens with all of D's hunks. Keep just the operator-row hunks in the first commit, leave the padding tweak for the second. Save -> two commits. Re-describe the second:</p>
jj describe -m "DEMO: Tighten outer padding"</span></span></code></pre>
jj log -r main..</code> shows D replaced by two narrowly-scoped commits.</p>
Demo 2 - jj absorb</code></h2>
Back to top of stack, with the wip fixes uncommitted:</p>
jj edit @         # if you're not already there</span></span>
jj diff           # show the two tiny hunks</span></span>
jj absorb</span></span></code></pre>
Output:</p>
Absorbed changes into 2 revisions:</span></span>
  <C>  DEMO: Add digit buttons</span></span>
  <B>  DEMO: Add CalculatorViewModel with display state</span></span></code></pre>
jj log</code> to show the wip change is gone, its hunks now live in B and C where they belong. No interactive picking, no commit reordering.</p>
Demo 3 - jj rebase</code></h2>
Show the "pull a commit out of the middle of the stack" superpower. Without conflicts first, move D after E:</p>
jj rebase -r <D> --insert-after <E></span></span></code></pre>
D pops up to the top of the stack, E sinks below it, descendants auto-rebase. No conflict because D and E touch disjoint lines.</p>
(Reset before the next demo if you want a clean log.)</p>
Demo 4 - Conflicts via rebase</h2>
Try the rebase that can't</em> clean up automatically: move E (which adds
OperatorRow(...)</code>-adjacent equals/clear UI) to before C (which adds the
digit buttons that E's diff context relies on).</p>
jj rebase -r <E> --insert-before <C></span></span></code></pre>
jj reports:</p>
New conflicts appeared in 2 commits:</span></span>
  <C> (conflict) DEMO: Add digit buttons</span></span>
  <E> (conflict) DEMO: Add equals and clear logic</span></span></code></pre>
jj log</code> shows the two affected commits marked ×</code>. The stack stays in place - this is the killer property: conflicts are first-class state, not a mode you have to escape from</strong>. You can keep working, look at sibling commits, run jj diff</code>, etc.</p>
To resolve:</p>
jj new <E>                 # step onto a child of the first conflicted commit</span></span>
jj resolve --list          # see the conflicted paths</span></span>
jj resolve                 # opens the configured merge tool</span></span>
                           # or edit conflict markers in place, then `jj squash`</span></span></code></pre>
After resolving E, the second conflict (in C) often resolves automatically
because jj re-propagates the resolution down the stack.</p>

Useful surrounding commands</h2>

jj log -r 'main..@'</code> - just the demo stack</li>
jj op log</code> - every operation you've run; jj op restore <id></code> to undo anything</li>
jj diff -r <change></code> - show one commit's diff</li>
jj evolog -r <change></code> - history of one logical change as you've reshaped it</li>
</ul>


Jujutsu for git users (WIP)
2026-05-08T00:00:00+00:00
Basics</h2>
You can use jj</code> with any git repository that you have - it's optional to use. So if you start using jj</code> but don't like it, you can go back to using git</code> commands without a problem.</p>
We can start off with</p>

The @</code> sign tells you where you currently are - it's your working copy.</li>
new</code>

In Jujutsu, you have an empty new working commit with jj new</code> you never have an uncommitted set, you keep working on it until your next new</code> or move to a different commit. In git, as you start working you are in a dirty/uncommitted state, you finalize your set at the end.</li>
</ul>
</li>
describe</code>

Similar to git commit - except that you commit at the end. With describe, you can do it at anytime - while you're planning out work, during some changes, or to finalize it. It's a</li>
</ul>
</li>
edit</code>

You can edit a previous item with work on top of it. It's like an interactive rebase.</li>
Git does not have that. You would need to make another branch and/or cherry-pick some changes.</li>
</ul>
</li>
rebase</code>

Rebases never fail - they are first class citizen to VCS.</li>
You can get conflicts, but you aren't required to fix it to move on.</li>
It's fast - it applies all the rebased changes in-memory before it writes it to disk - this means that Android Studio doesn't keep indexing while things are happening.</li>
</ul>
</li>
op log</code>

Gives you a record of what you did. This is unlike the git reflog</code>, where a rebase would show you twenty entries in there. You can restore to anywhere here.</li>
Another way to use undo</code> or redo</code>.</li>
</ul>
</li>
</ul>
Advanced or mozilla-central workflows</h2>

absorb</code></li>
Handling conflicts.</li>
split</code></li>
No branches.</li>
moz-phab patch</code></li>
workspaces</code></li>
</ul>


Toronto - Easy Run
2026-05-06T00:00:00+00:00
More of a fun run. Better than two days ago with the massage gun to help with the warmup.</p>
Cooler weather and didn't wait too late before I depleted my energy stores.</p>
Stat</th> Value</th></tr></thead>

Distance</td> 7.62 km</td></tr>
Duration</td> 40:56</td></tr>
Pace</td> 5:22 /km</td></tr>
Elevation Gain</td> 50 m</td></tr>
</tbody></table>
Heart Rate Zones</h2>

---
config:
  themeVariables:
    xyChart:
      plotColorPalette: "#555555,#FF8200,#56CC3C,#4090D4,#AAAAAA"
      backgroundColor: "transparent"
---
        
xychart horizontal
    title "Time in Heart Rate Zones (%)"
    x-axis ["Zone 5 Maximum", "Zone 4 Threshold", "Zone 3 Aerobic", "Zone 2 Easy", "Zone 1 Warm Up"]
    y-axis "%" 2 --> 100
    bar [0.0, 0.0, 0.0, 0.0, 0.0]
    bar [0.0, 0.0, 0.0, 0.0, 0.0]
    bar [0.0, 0.0, 15.8, 0.0, 0.0]
    bar [0.0, 0.0, 0.0, 29.4, 0.0]
    bar [0.0, 0.0, 0.0, 0.0, 54.8]
</pre>


Toronto - Easy Run
2026-05-04T00:00:00+00:00
Tired run. Toe is still prickly.</p>
Stat</th> Value</th></tr></thead>

Distance</td> 5.55 km</td></tr>
Duration</td> 30:02</td></tr>
Pace</td> 5:25 /km</td></tr>
Elevation Gain</td> 41 m</td></tr>
</tbody></table>
Heart Rate Zones</h2>

---
config:
  themeVariables:
    xyChart:
      plotColorPalette: "#555555,#FF8200,#56CC3C,#4090D4,#AAAAAA"
      backgroundColor: "transparent"
---
        
xychart horizontal
    title "Time in Heart Rate Zones (%)"
    x-axis ["Zone 5 Maximum", "Zone 4 Threshold", "Zone 3 Aerobic", "Zone 2 Easy", "Zone 1 Warm Up"]
    y-axis "%" 2 --> 100
    bar [0.0, 0.0, 0.0, 0.0, 0.0]
    bar [0.0, 0.0, 0.0, 0.0, 0.0]
    bar [0.0, 0.0, 28.1, 0.0, 0.0]
    bar [0.0, 0.0, 0.0, 20.1, 0.0]
    bar [0.0, 0.0, 0.0, 0.0, 51.8]
</pre>


Toronto - Base
2026-04-30T00:00:00+00:00
Prickly without half a toenail. Kept it short as I've failed to be consistent again.</p>
Stat</th> Value</th></tr></thead>

Distance</td> 5.48 km</td></tr>
Duration</td> 30:01</td></tr>
Pace</td> 5:29 /km</td></tr>
Elevation Gain</td> 37 m</td></tr>
</tbody></table>
Heart Rate Zones</h2>

---
config:
  themeVariables:
    xyChart:
      plotColorPalette: "#555555,#FF8200,#56CC3C,#4090D4,#AAAAAA"
      backgroundColor: "transparent"
---
        
xychart horizontal
    title "Time in Heart Rate Zones (%)"
    x-axis ["Zone 5 Maximum", "Zone 4 Threshold", "Zone 3 Aerobic", "Zone 2 Easy", "Zone 1 Warm Up"]
    y-axis "%" 2 --> 100
    bar [0.0, 0.0, 0.0, 0.0, 0.0]
    bar [0.0, 0.0, 0.0, 0.0, 0.0]
    bar [0.0, 0.0, 34.1, 0.0, 0.0]
    bar [0.0, 0.0, 0.0, 28.7, 0.0]
    bar [0.0, 0.0, 0.0, 0.0, 37.2]
</pre>


Gmail filters based on X-Phabricator-Stamps header
2026-04-23T00:00:00+00:00
I want Phabricator emails to have a Gmail label so I can know which patches had me as a reviewer that then had follow-up comments from other folks.</p>
This is useful for me when I review a patch and then I need to respond back to discussions in a more timely manner in comment threads that I've created.</p>
It's difficult to do this today similar to Bugzilla Gmail filters</a> because there are fewer identifiers that the more simplistic Gmail filter parameters can help with.</p>
Today I learnt that there is an X-Phabricator-Stamps</code> header in those Phabricator emails that let's you identify you as a the reviewer in a patch. So using that information, I wrote the Google script</a> below to run every minute and avoid re-processing the same email twice.</p>
A couple variables were added to the top and some console.logs are sprinkled around for my own debugging.</p>

Code</summary>
var</span> REVIEWER</span> =</span> "</span>jonalmeida</span>"</span>;</span></span>
var</span> LABEL_NAME</span> =</span> "</span>Phabricator/Comments</span>"</span>;</span></span>
var</span> BODY_MATCH</span> =</span> "</span>commented on this revision.</span>"</span>;</span></span>
var</span> SENDER</span> =</span> "</span>phabricator@mozilla.com</span>"</span>;</span></span>
</span>
/**</span></span>
 * Run once manually to install the per-minute trigger.</span></span>
 */</span></span>
function</span> install</span>(</span>)</span> {</span></span>
  uninstall</span>(</span>)</span>;</span></span>
  ScriptApp</span>.</span>newTrigger</span>(</span>'</span>processInbox</span>'</span>)</span></span>
  .</span>timeBased</span>(</span>)</span></span>
  .</span>everyMinutes</span>(</span>1</span>)</span></span>
  .</span>create</span>(</span>)</span>;</span></span>
}</span></span>
</span>
/**</span></span>
 * Run once manually to remove the trigger.</span></span>
 */</span></span>
function</span> uninstall</span>(</span>)</span> {</span></span>
  ScriptApp</span>.</span>getProjectTriggers</span>(</span>)</span>.</span>forEach</span>(</span>function</span>(</span>t</span>)</span> {</span></span>
    ScriptApp</span>.</span>deleteTrigger</span>(</span>t</span>)</span>;</span></span>
  }</span>)</span>;</span></span>
  PropertiesService</span>.</span>getScriptProperties</span>(</span>)</span>.</span>deleteProperty</span>(</span>'</span>lastRun</span>'</span>)</span>;</span></span>
}</span></span>
</span>
/**</span></span>
 * Every run, we try to avoid processing the same email twice because</span></span>
 * there is no API trigger to run a script on every new email received.</span></span>
 */</span></span>
function</span> processInbox</span>(</span>)</span> {</span></span>
  var</span> props</span> =</span> PropertiesService</span>.</span>getScriptProperties</span>(</span>)</span>;</span></span>
  var</span> lastRun</span> =</span> parseInt</span>(</span>props</span>.</span>getProperty</span>(</span>'</span>lastRun</span>'</span>)</span> ||</span> '</span>0</span>'</span>)</span>;</span></span>
  var</span> now</span> =</span> Math</span>.</span>floor</span>(</span>Date</span>.</span>now</span>(</span>)</span> /</span> 1000</span>)</span>;</span></span>
</span>
  //</span> On first run, look back 2 minutes</span></span>
  if</span> (</span>lastRun</span> ===</span> 0</span>)</span> {</span></span>
    lastRun</span> =</span> now</span> -</span> 120</span>;</span></span>
  }</span></span>
</span>
  var</span> label</span> =</span> GmailApp</span>.</span>getUserLabelByName</span>(</span>LABEL_NAME</span>)</span>;</span></span>
  if</span> (</span>!</span>label</span>)</span> {</span></span>
    label</span> =</span> GmailApp</span>.</span>createLabel</span>(</span>LABEL_NAME</span>)</span>;</span></span>
  }</span></span>
</span>
  console</span>.</span>log</span>(</span>"</span>last run: </span>"</span> +</span> lastRun</span>)</span>;</span></span>
  var</span> threads</span> =</span> GmailApp</span>.</span>search</span>(</span>"</span>from:</span>"</span> +</span> SENDER</span> +</span> "</span> after:</span>"</span> +</span> lastRun</span>)</span>;</span></span>
  console</span>.</span>log</span>(</span>"</span>threads to process: </span>"</span> +</span> threads</span>.</span>length</span>)</span>;</span></span>
  for</span> (</span>var</span> i</span> =</span> 0</span>;</span> i</span> <</span> threads</span>.</span>length</span>;</span> i</span>++</span>)</span> {</span></span>
    var</span> thread</span> =</span> threads</span>[</span>i</span>]</span>;</span></span>
    var</span> messages</span> =</span> thread</span>.</span>getMessages</span>(</span>)</span>;</span></span>
    console</span>.</span>log</span>(</span>"</span>messages to process: </span>"</span> +</span> messages</span>.</span>length</span>)</span>;</span></span>
    for</span> (</span>var</span> j</span> =</span> 0</span>;</span> j</span> <</span> messages</span>.</span>length</span>;</span> j</span>++</span>)</span> {</span></span>
      if</span> (</span>hasReviewerStamp</span>(</span>messages</span>[</span>j</span>]</span>)</span>)</span> {</span></span>
        thread</span>.</span>addLabel</span>(</span>label</span>)</span>;</span></span>
        console</span>.</span>log</span>(</span>thread</span>.</span>getFirstMessageSubject</span>(</span>)</span>)</span>;</span></span>
        break</span>;</span></span>
      }</span></span>
    }</span></span>
  }</span></span>
</span>
  props</span>.</span>setProperty</span>(</span>'</span>lastRun</span>'</span>,</span> String</span>(</span>now</span>)</span>)</span>;</span></span>
}</span></span>
</span>
function</span> hasReviewerStamp</span>(</span>message</span>)</span> {</span></span>
  var</span> raw</span> =</span> message</span>.</span>getRawContent</span>(</span>)</span>;</span></span>
  var</span> match</span> =</span> raw</span>.</span>match</span>(</span>/</span>^</span>X-Phabricator-Stamps:</span>\s</span>*</span>(</span>.</span>+</span>)</span>$</span>/</span>m</span>)</span>;</span></span>
  if</span> (</span>!</span>match</span>)</span> {</span></span>
    return</span> false</span>;</span></span>
  }</span></span>
</span>
  var</span> stamps</span> =</span> match</span>[</span>1</span>]</span>.</span>trim</span>(</span>)</span>.</span>split</span>(</span>/</span>\s</span>+</span>/</span>)</span>;</span></span>
  return</span> (</span>stamps</span>.</span>indexOf</span>(</span>"</span>reviewer(@</span>"</span> +</span> REVIEWER</span> +</span> "</span>)</span>"</span>)</span> ></span> -</span>1</span>)</span> &&</span> raw</span>.</span>indexOf</span>(</span>BODY_MATCH</span>)</span> ></span> -</span>1</span>;</span></span>
}</span></span>
</span>
/**</span></span>
 * For debugging - see the list of labels you can search which</span></span>
 * differs from what is used in the Gmail UI filter.</span></span>
 */</span></span>
function</span> listAllLabels</span>(</span>)</span> {</span></span>
  console</span>.</span>log</span>(</span>"</span>All labels</span>"</span>)</span>;</span></span>
  var</span> labels</span> =</span> GmailApp</span>.</span>getUserLabels</span>(</span>)</span>;</span></span>
  for</span> (</span>var</span> i</span> =</span> 0</span>;</span> i</span> <</span> labels</span>.</span>length</span>;</span> i</span>++</span>)</span> {</span></span>
    console</span>.</span>log</span>(</span>labels</span>[</span>i</span>]</span>.</span>getName</span>(</span>)</span>)</span>;</span></span>
  }</span></span>
}</span></span></code></pre></details>


Toronto Running
2026-04-19T00:00:00+00:00
Arrived too late for the group run, and made my way to the bakery right after the bit of the trail I wanted to do.</p>
Stat</th> Value</th></tr></thead>

Distance</td> 5.01 km</td></tr>
Duration</td> 25:52</td></tr>
Pace</td> 5:10 /km</td></tr>
Elevation Gain</td> 29 m</td></tr>
</tbody></table>
Heart Rate Zones</h2>

---
config:
  themeVariables:
    xyChart:
      plotColorPalette: "#555555,#FF8200,#56CC3C,#4090D4,#AAAAAA"
      backgroundColor: "transparent"
---

xychart horizontal
    title "Time in Heart Rate Zones (%)"
    x-axis ["Zone 5 Maximum", "Zone 4 Threshold", "Zone 3 Aerobic", "Zone 2 Easy", "Zone 1 Warm Up"]
    y-axis "%" 2 --> 100
    bar [0.0, 0.0, 0.0, 0.0, 0.0]
    bar [0.0, 0.0, 0.0, 0.0, 0.0]
    bar [0.0, 0.0, 40.4, 0.0, 0.0]
    bar [0.0, 0.0, 0.0, 25.7, 0.0]
    bar [0.0, 0.0, 0.0, 0.0, 33.9]
</pre>


Toronto Running
2026-04-19T00:00:00+00:00
Warm-up run without a stretch because I'm lazy today morning.</p>
Stat</th> Value</th></tr></thead>

Distance</td> 2.5 km</td></tr>
Duration</td> 12:22</td></tr>
Pace</td> 4:57 /km</td></tr>
Elevation Gain</td> 19 m</td></tr>
</tbody></table>
Heart Rate Zones</h2>

---
config:
  themeVariables:
    xyChart:
      plotColorPalette: "#555555,#FF8200,#56CC3C,#4090D4,#AAAAAA"
      backgroundColor: "transparent"
---

xychart horizontal
    title "Time in Heart Rate Zones (%)"
    x-axis ["Zone 5 Maximum", "Zone 4 Threshold", "Zone 3 Aerobic", "Zone 2 Easy", "Zone 1 Warm Up"]
    y-axis "%" 2 --> 100
    bar [0.0, 0.0, 0.0, 0.0, 0.0]
    bar [0.0, 0.4, 0.0, 0.0, 0.0]
    bar [0.0, 0.0, 49.3, 0.0, 0.0]
    bar [0.0, 0.0, 0.0, 25.7, 0.0]
    bar [0.0, 0.0, 0.0, 0.0, 24.6]
</pre>


Toronto - Easy Run
2026-04-18T00:00:00+00:00
Unfit and kept it short. Legs are fine, but my upper body is tight.</p>
Stat</th> Value</th></tr></thead>

Distance</td> 3.81 km</td></tr>
Duration</td> 20:00</td></tr>
Pace</td> 5:15 /km</td></tr>
Elevation Gain</td> 35 m</td></tr>
</tbody></table>
Heart Rate Zones</h2>

---
config:
  themeVariables:
    xyChart:
      plotColorPalette: "#555555,#FF8200,#56CC3C,#4090D4,#AAAAAA"
      backgroundColor: "transparent"
---

xychart horizontal
    title "Time in Heart Rate Zones (%)"
    x-axis ["Zone 5 Maximum", "Zone 4 Threshold", "Zone 3 Aerobic", "Zone 2 Easy", "Zone 1 Warm Up"]
    y-axis "%" 2 --> 100
    bar [0.0, 0.0, 0.0, 0.0, 0.0]
    bar [0.0, 1.4, 0.0, 0.0, 0.0]
    bar [0.0, 0.0, 34.3, 0.0, 0.0]
    bar [0.0, 0.0, 0.0, 18.9, 0.0]
    bar [0.0, 0.0, 0.0, 0.0, 45.4]
</pre>


Use Android Studio for resolving conflicts in Jujutsu
2026-03-25T00:00:00+00:00
You can use JJ's built-in editor for conflict resolutions, but I've found it difficult to follow. A recommendation from co-workers was to use Meld</a> and that has worked quite well once I (begrudingly) accepted that I needed to download another single-purpose app.</p>
Today, another co-worker Andrey Zinovyev</a> found out that we can use Android Studio's (IntelliJ IDEA's really) built-in merge tool to resolve the three-way merge. This is more convenient for me since I spend most of my time here already, so using it as a general purpose merge editor for my work projects is quite nice.</p>
[</span>ui</span>]</span></span>
merge-editor</span> =</span> "</span>studio</span>"</span></span>
</span>
[</span>merge-tools</span>.</span>studio</span>]</span></span>
merge-args</span> =</span> [</span>"</span>merge</span>"</span>,</span> "</span>$left</span>"</span>,</span> "</span>$right</span>"</span>,</span> "</span>$base</span>"</span>,</span> "</span>$output</span>"</span>]</span></span>
program</span> =</span> "</span>/Users/jalmeida/Applications/Android Studio Nightly.app/Contents/MacOS/studio</span>"</span></span></code></pre>
Presto!</p>


  
</div>


Create new revisions in Jujutsu with multiple heads
2026-03-22T00:00:00+00:00
It was one of those "ah ha!" moments for me when I finally used it. Chris Krycho covers the concept of megamerges</a> with this diagram:</p>
       m --- n</span></span>
      /       \</span></span>
a -- b -- c -- [merge] -- [wip]</span></span>
      \       /</span></span>
       w --- x</span></span></code></pre>
I've found a more realistic example that best relates to my natural workflow: implementing feature (A) benefitted from having the changes of another tooling patch upgrade (B), that lead to discovering and fixing a bug (C).</p>
      (B)</span></span>
       m ----- n</span></span>
      /         \           (A)</span></span>
a -- b --------- [merge] --- y -- z</span></span>
      \                     /      \                (C)</span></span>
        -------------------         ----- [merge] -- w -- x</span></span>
        \                                /</span></span>
          -------------------------------</span></span></code></pre>
In this case, trying to separate these into distinct streams of work is quite logically, but we also don't need to leave them unlinked so that they can benefit from each other.</p>
This is what my jj log</code> ended up looking like:</p>
@  oppmsuvz </span>jxxxxxxxxxxxx@gmail.com</span> 2026-03-22</span> 00:34:10</span> firefox@</span> 05259417</span></span>
│  </span>Bug xxxxxxx - Simplify the tests</span></span>
○  </span>ultowtnr </span>jxxxxxxxxxxxx@gmail.com</span> 2026-03-22</span> 00:34:04</span> 100c4cce</span></span>
│  </span>Bug xxxxxxx - Include private flag in ShareData</span></span>
○    </span>lorusmuo </span>jxxxxxxxxxxxx@gmail.com</span> 2026-03-21</span> 20:19:30</span> 905b0460</span></span>
├─╮  </span>(empty)</span> (no description set)</span></span>
│ ○  </span>sumqskuu </span>jxxxxxxxxxxxx@gmail.com</span> 2026-03-21</span> 04:22:00</span> 92f6028b</span></span>
│ │  </span>Add a new secret settings fragment</span></span>
│ ○  </span>oylmprpu </span>jxxxxxxxxxxxx@gmail.com</span> 2026-03-21</span> 04:22:00</span> 18931825</span></span>
│ │  </span>Create a new feature for receiving and sending commands.</span></span>
│ ○  </span>xrnnoonu </span>jxxxxxxxxxxxx@gmail.com</span> 2026-03-21</span> 04:21:48</span> 618020c7</span></span>
╭─┤  </span>(empty)</span> (no description set)</span></span>
│ ○  </span>rqlyqqzx </span>jxxxxxxxxxxxx@gmail.com</span> 2026-03-19</span> 17:20:20</span> c9b5323c</span></span>
│ │  </span>Bug xxxxxxx - Part 2: Create new android gradle module skill</span></span>
│ ○  </span>txvozpwz </span>jxxxxxxxxxxxx@gmail.com</span> 2026-03-19</span> 17:20:13</span> cee18510</span></span>
├─╯  </span>Bug xxxxxxx - Part 1: Add new gradle example module</span></span>
◆  pwsnmryn </span>vxxxxxxxxxxxx@gmail.com</span> 2026-03-18</span> 13:21:47</span> main@</span>origin </span>fa20ce29</span></span>
│  </span>Bug xxxxxxx - Make my feature work for everyone</span></span>
~</span></span></code></pre>
When I need to submit these, [moz-phab][1</a> has support for specifying revset ranges with moz-phab start_rev end_rev</code>. However, I can also use jj rebase -s <rev> -d main@origin</code> to put out some try pushes to validate they still work separately - so far, no conflicts in this step.</p>


Use |mach try --no-push| for a configuration dry run
2026-03-22T00:00:00+00:00
I wanted to see what the generated try configuration would be for a new preset I made and did this by submitting real try pushes (with empty</code> so they don't execute resources). What I was looking for was "dry run" in the help files, but I recently discovered it to be --no-push</code>.</p>
$</span> jj</span> try-push</span> -</span>-preset</span> fenix</span> -</span>-no-push</span> #</span> 'fenix' as an example preset</span></span>
Artifact</span> builds</span> enabled,</span> pass</span> -</span>-no-artifact</span> to</span> disable</span></span>
Commit</span> message:</span></span>
Fuzzy</span> (preset:</span> fenix</span>)</span> query</span>=</span>'</span>build-apk-fenix-debug&query=</span>'</span>s</span>i</span>g</span>n</span>i</span>n</span>g</span>-</span>a</span>p</span>k</span>-</span>f</span>e</span>n</span>i</span>x</span>-</span>d</span>e</span>b</span>u</span>g</span>&</span>query</span>=</span>'</span>build-apk-fenix-android-test-debug&query=</span>'</span>s</span>i</span>g</span>n</span>i</span>n</span>g</span>-</span>a</span>p</span>k</span>-</span>f</span>e</span>n</span>i</span>x</span>-</span>a</span>n</span>d</span>r</span>o</span>i</span>d</span>-</span>t</span>e</span>s</span>t</span>-</span>d</span>e</span>b</span>u</span>g</span>&</span>query</span>=</span>'</span>test-apk-fenix-debug&query=</span>'</span>u</span>i</span>-</span>t</span>e</span>s</span>t</span>-</span>a</span>p</span>k</span>-</span>f</span>e</span>n</span>i</span>x</span>-</span>a</span>r</span>m</span>-</span>d</span>e</span>b</span>u</span>g</span>&</span>query</span>=</span>^</span>s</span>o</span>u</span>r</span>c</span>e</span>-</span>t</span>e</span>s</span>t</span> '</span>fenix&query=</span>'</span>g</span>e</span>n</span>e</span>r</span>a</span>t</span>e</span>-</span>b</span>a</span>s</span>e</span>l</span>i</span>n</span>e</span>-</span>p</span>r</span>o</span>f</span>i</span>l</span>e</span>-</span>f</span>i</span>r</span>e</span>b</span>a</span>s</span>e</span>-</span>f</span>e</span>n</span>i</span>x</span></span>
</span>
mach</span> try</span> command:</span> `</span>./mach</span> try</span> -</span>-preset</span> fenix</span> -</span>-no-push</span>`</span></span>
</span>
Pushed</span> via</span> `</span>mach</span> try</span> fuzzy</span>`</span></span>
Calculated</span> try_task_config.json:</span></span>
{</span></span>
    "</span>parameters</span>"</span>:</span> {</span></span>
        "</span>optimize_target_tasks</span>"</span>:</span> false</span>,</span></span>
        "</span>try_task_config</span>"</span>:</span> {</span></span>
            "</span>disable-pgo</span>"</span>:</span> true</span>,</span></span>
            "</span>env</span>"</span>:</span> {</span></span>
                "</span>TRY_SELECTOR</span>"</span>:</span> "</span>fuzzy</span>"</span></span>
            }</span>,</span></span>
            "</span>tasks</span>"</span>:</span> [</span></span>
                "</span>build-apk-fenix-android-test-debug</span>"</span>,</span></span>
                "</span>build-apk-fenix-debug</span>"</span>,</span></span>
                "</span>generate-baseline-profile-firebase-fenix</span>"</span>,</span></span>
                "</span>source-test-android-detekt-detekt-fenix</span>"</span>,</span></span>
                "</span>source-test-android-l10n-lint-l10n-lint-fenix</span>"</span>,</span></span>
                "</span>source-test-android-lint-fenix</span>"</span>,</span></span>
                "</span>source-test-buildconfig-buildconfig-fenix</span>"</span>,</span></span>
                "</span>source-test-ktlint-fenix</span>"</span>,</span></span>
                "</span>source-test-mozlint-android-fenix</span>"</span>,</span></span>
                "</span>test-apk-fenix-debug</span>"</span>,</span></span>
                "</span>ui-test-apk-fenix-arm-debug</span>"</span>,</span></span>
                "</span>ui-test-apk-fenix-arm-debug-smoke</span>"</span></span>
            ],</span></span>
            "</span>use-artifact-builds</span>"</span>:</span> true</span></span>
        }</span></span>
    },</span></span>
    "</span>version</span>"</span>:</span> 2</span></span>
}</span></span></code></pre>
Here, jj try-push</code> is my quick alias around ./mach try</code> for personal simplicity with my workflow.</p>


Toronto - Easy Run
2026-03-20T00:00:00+00:00
Burpy run, felt some sloshing inside of me for the first few kms.</p>
Quite happy that the legs are walking up. Did a slow 2K warmup around the block and didn't feel any early tightness. Should include this is my pre-run workout during training season.</p>
Stat</th> Value</th></tr></thead>

Distance</td> 8.16 km</td></tr>
Duration</td> 45:08</td></tr>
Pace</td> 5:32 /km</td></tr>
Elevation Gain</td> 44 m</td></tr>
</tbody></table>
Heart Rate Zones</h2>

---
config:
  themeVariables:
    xyChart:
      plotColorPalette: "#555555,#FF8200,#56CC3C,#4090D4,#AAAAAA"
      backgroundColor: "transparent"
---

xychart horizontal
    title "Time in Heart Rate Zones (%)"
    x-axis ["Zone 5 Maximum", "Zone 4 Threshold", "Zone 3 Aerobic", "Zone 2 Easy", "Zone 1 Warm Up"]
    y-axis "%" 2 --> 100
    bar [0.0, 0.0, 0.0, 0.0, 0.0]
    bar [0.0, 0.0, 0.0, 0.0, 0.0]
    bar [0.0, 0.0, 8.5, 0.0, 0.0]
    bar [0.0, 0.0, 0.0, 22.4, 0.0]
    bar [0.0, 0.0, 0.0, 0.0, 69.0]
</pre>


Don't credit Claude for patches that you submit for code review
2026-03-14T00:00:00+00:00
Spicy topic, right?</p>
I haven't used Claude Code nearly as much as I could to be honest, but enough to have an opinion on it.</p>
Adding credits or notifying the reviewers that you used an AI agent was useful for a few reasons:</p>

This patch was written with support from an agent, and it might be useful context during a code review from a human (e.g. asking them to take extra care on the correctness of the patch).</li>
To be a good citizen and say where the work originated from.</li>
</ol>
Doing this now for those reasons seems unproductive. In the same order as the above, I'd say:</p>

What you submit for review shouldn't matter how it came to be, even if it was a script someone else wrote that generated the updated files for you to check-in. You</em> are submitting those changes with your name and therefore should take responsibility for what is submitted. If Claude generated slop, it was you that submitted it without vetting it and it put your name on it, so your code is slop.</li>
There is more hostility online when you use AI tools. I can understand the frustration that some folks have had, but not everyone is abusing the tools and causing harm. It's hard to avoid being lumped into the same bucket, and being open about your workflow puts a target on your back, unfortunately.</li>
</ol>
Maybe this is comes across as obvious for others, but it wasn't for me, and I needed to ramble somewhere.</p>


Toronto - Easy Run
2026-03-12T00:00:00+00:00
Chilly. Ran fast to stay warm.</p>
New baseball park construction almost done.</p>


  
</div>


Stat</th> Value</th></tr></thead>

Distance</td> 8.18 km</td></tr>
Duration</td> 45:00</td></tr>
Pace</td> 5:30 /km</td></tr>
Elevation Gain</td> 53 m</td></tr>
</tbody></table>
Heart Rate Zones</h2>

---
config:
  themeVariables:
    xyChart:
      plotColorPalette: "#555555,#FF8200,#56CC3C,#4090D4,#AAAAAA"
      backgroundColor: "transparent"
---

xychart horizontal
    title "Time in Heart Rate Zones (%)"
    x-axis ["Zone 5 Maximum", "Zone 4 Threshold", "Zone 3 Aerobic", "Zone 2 Easy", "Zone 1 Warm Up"]
    y-axis "%" 2 --> 100
    bar [0.0, 0.0, 0.0, 0.0, 0.0]
    bar [0.0, 1.8, 0.0, 0.0, 0.0]
    bar [0.0, 0.0, 26.1, 0.0, 0.0]
    bar [0.0, 0.0, 0.0, 24.1, 0.0]
    bar [0.0, 0.0, 0.0, 0.0, 48.1]
</pre>


Toronto - Easy Run
2026-03-08T00:00:00+00:00
Body is a bit stiff and didn't feel fluid, but managed to get through it. Overdressed a little, though it wasn't a problem.</p>
Stat</th> Value</th></tr></thead>

Distance</td> 8.06 km</td></tr>
Duration</td> 45:01</td></tr>
Pace</td> 5:35 /km</td></tr>
Elevation Gain</td> 54 m</td></tr>
</tbody></table>
Heart Rate Zones</h2>

---
config:
  themeVariables:
    xyChart:
      plotColorPalette: "#555555,#FF8200,#56CC3C,#4090D4,#AAAAAA"
      backgroundColor: "transparent"
---

xychart horizontal
    title "Time in Heart Rate Zones (%)"
    x-axis ["Zone 5 Maximum", "Zone 4 Threshold", "Zone 3 Aerobic", "Zone 2 Easy", "Zone 1 Warm Up"]
    y-axis "%" 2 --> 100
    bar [0.0, 0.0, 0.0, 0.0, 0.0]
    bar [0.0, 0.0, 0.0, 0.0, 0.0]
    bar [0.0, 0.0, 15.7, 0.0, 0.0]
    bar [0.0, 0.0, 0.0, 28.7, 0.0]
    bar [0.0, 0.0, 0.0, 0.0, 55.6]
</pre>


My Firefox for Android local build environment
2026-03-05T00:00:00+00:00
The Firefox for Android app has always had a complicated build process - we're cramping a complex cross-platform browser engine and all the related components that make it work on Android into one package. In its current form, it lives in the Firefox mono-repo at mozilla-central</code> (now mozilla-firefox</code> using the git repository).</p>
I wanted to document my "artifact-mode" environment here since it's worked quite successfully for me for many years with minor changes.</p>

NOTE:</strong> After a fresh clone of the mono-repo, don't forget to first run and follow the prompts of ./mach bootstrap</code> .</p>
</blockquote>
mozconfig</h2>
My mozconfig</code> below is enabled for artifact mode, but occasionally I switch between various configurations. You can see those commented out, with these few extra notes:</p>

I like to separate out my objdirs to avoid cache pollution between the different build types. I think you can get away without needing to specify this and an objdir for your build type and arch will be generated.</li>
sccache</code> speeds up the native portion of full builds after the first slow one, but it's a hit or miss if you fetch from the remote repository but don't need to rebuild as often.</li>
I don't care to manually run the clobber step, and I don't truly appreciate why that isn't always automatically done.</li>
Emilio's mozconfig manager</a> looks like a better solution, however my needs are very simple.</li>
</ul>
#</span> Build GeckoView/Firefox for Android:</span></span>
ac_add_options</span> -</span>-enable-application=mobile/android</span></span>
</span>
#</span> Targeting the following architecture.</span></span>
#</span> For regular phones, no --target is needed.</span></span>
#</span> For x86 emulators (and x86 devices, which are uncommon):</span></span>
#</span> ac_add_options --target=i686</span></span>
#</span> For newer phones or Apple silicon</span></span>
ac_add_options</span> -</span>-target=aarch64</span></span>
#</span> For x86_64 emulators (and x86_64 devices, which are even less common):</span></span>
#</span> ac_add_options --target=x86_64</span></span>
</span>
#</span> sccache will significantly speed up your builds by caching</span></span>
#</span> compilation results. The Firefox build system will download</span></span>
#</span> sccache automatically.</span></span>
#</span> This only works for non-artifact builds.</span></span>
#</span>ac_add_options --with-ccache=sccache</span></span>
</span>
#</span> Enable artifact builds; manager-mode.</span></span>
ac_add_options</span> -</span>-enable-artifact-builds</span></span>
</span>
#</span> Write build artifacts to..</span></span>
</span>
#</span># Full build dir</span></span>
#</span>mk_add_options MOZ_OBJDIR=./objdir-droid</span></span>
#</span>mk_add_options MOZ_OBJDIR=./objdir-desktop</span></span>
</span>
#</span># Artifact builds</span></span>
mk_add_options</span> MOZ_OBJDIR=./objdir-frontend</span></span>
</span>
#</span> Automatic clobbering; don't ask me.</span></span>
mk_add_options</span> AUTOCLOBBER=</span>1</span></span></code></pre>JAVA_HOME</h2>
Sometimes you might find yourself needing to run a (non-mach) command in the terminal. Those typically will need to invoke some parts of gradle for an Android build, so it's best to make sure those are using the same JDK as the bootstrapped one in the mono-repo. This avoids weird build errors where something that compiles in one place isn't working in another (like Android Studio).</p>
The location for the JDKs are typically in ~/.mozbuild/jdk/</code>, and if you've between around for ~6 months you end up with multiple versions after every JDK bump:</p>
$</span> ls</span> -</span>l</span> ~/.mozbuild/jdk/</span></span>
drwxr-xr-x@</span> -</span> jalmeida</span> 15</span> Apr</span>  2025</span> jdk-17.0.15+6</span></span>
drwxr-xr-x@</span> -</span> jalmeida</span> 15</span> Jul</span>  2025</span> jdk-17.0.16+8</span></span>
drwxr-xr-x@</span> -</span> jalmeida</span> 21</span> Oct</span>  2025</span> jdk-17.0.17+10</span></span>
drwxr-xr-x@</span> -</span> jalmeida</span> 20</span> Jan</span> 09:00</span> jdk-17.0.18+8</span></span>
drwxr-xr-x@</span> -</span> jalmeida</span> 26</span> Feb</span> 15:04</span> mozboot</span></span>
</span></code></pre>
You can find some way to point your latest JDK to one location or you can be lazy like me and pick the latest version to assign as your JAVA_HOME</code> property by adding this to your shell's RC file:</p>
export</span> JAVA_HOME</span>=</span>"</span>$(</span>ls</span> -</span>1dr</span> -</span>-</span> $</span>HOME</span>/.mozbuild/jdk/jdk-</span>*</span> |</span> head</span> -</span>n</span> 1</span>)</span>/Contents/Home</span>"</span></span></code></pre>Android Studio</h3>
UPDATE:</strong> With D286123</a> landed, this should no longer be necessary! 🎉</p>
Similarly for Android Studio, let's do the same so that environment is identical. Head to, Settings | Build, Execution, Deployment | Build Tools | Gradle, and ensure that "Gradle JDK" path is set to JAVA_HOME</code>.</p>
Lately, the default seems to be for it to follow GRADLE_LOCAL_JAVA_HOME</code> which is a property we can't easily override, so we have to manually set this ourselves.</p>


  
</div>
Using the same Android SDK also helps speed things up and avoids source confusion. You can typically find it in ~/.mozbuild/android-sdk-macosx</code> and update it at Settings | Languages & Frameworks | Android SDK.</p>


  
</div>
Debugging</h2>
This section is for miscellaneous build error situations that come-up, but assuming mach build</code> work and there are no known Android build changes, my solution has typically always been the same.</p>
For example, the other day I fetched another engineers patch to test out locally1</a></sup> as part of reviewing it where I faced the error message below:</p>

Execution failed for task ':components:feature-pwa:compileDebugKotlin'.</summary>
FAILURE: Build failed with an exception.</span></span>
</span>
* What went wrong:</span></span>
Execution failed for task ':components:feature-pwa:compileDebugKotlin'.</span></span>
> A failure occurred while executing org.jetbrains.kotlin.compilerRunner.GradleCompilerRunnerWithWorkers$GradleKotlinCompilerWorkAction</span></span>
   > Internal compiler error. See log for more details</span></span>
</span>
* Try:</span></span>
> Run with --info or --debug option to get more log output.</span></span>
> Run with --scan to generate a Build Scan (powered by Develocity).</span></span>
> Get more help at https://help.gradle.org.</span></span>
</span>
* Exception is:</span></span>
org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':components:feature-pwa:compileDebugKotlin'.</span></span>
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.lambda$executeIfValid$1(ExecuteActionsTaskExecuter.java:135)</span></span>
	at org.gradle.internal.Try$Failure.ifSuccessfulOrElse(Try.java:288)</span></span>
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeIfValid(ExecuteActionsTaskExecuter.java:133)</span></span>
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:121)</span></span>
	at org.gradle.api.internal.tasks.execution.ProblemsTaskPathTrackingTaskExecuter.execute(ProblemsTaskPathTrackingTaskExecuter.java:41)</span></span>
	at org.gradle.api.internal.tasks.execution.FinalizePropertiesTaskExecuter.execute(FinalizePropertiesTaskExecuter.java:46)</span></span>
	at org.gradle.api.internal.tasks.execution.ResolveTaskExecutionModeExecuter.execute(ResolveTaskExecutionModeExecuter.java:51)</span></span>
	at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:57)</span></span>
	at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:74)</span></span>
	at org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:36)</span></span>
	at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.executeTask(EventFiringTaskExecuter.java:77)</span></span>
	at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:55)</span></span>
	at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:52)</span></span>
	at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:209)</span></span>
	at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:204)</span></span>
	at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:66)</span></span>
	at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:59)</span></span>
	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:166)</span></span>
	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:59)</span></span>
	at org.gradle.internal.operations.DefaultBuildOperationRunner.call(DefaultBuildOperationRunner.java:53)</span></span>
	at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter.execute(EventFiringTaskExecuter.java:52)</span></span>
	at org.gradle.execution.plan.DefaultNodeExecutor.executeLocalTaskNode(DefaultNodeExecutor.java:55)</span></span>
	at org.gradle.execution.plan.DefaultNodeExecutor.execute(DefaultNodeExecutor.java:34)</span></span>
	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:355)</span></span>
	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:343)</span></span>
	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.lambda$execute$0(DefaultTaskExecutionGraph.java:339)</span></span>
	at org.gradle.internal.operations.CurrentBuildOperationRef.with(CurrentBuildOperationRef.java:84)</span></span>
	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:339)</span></span>
	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:328)</span></span>
	at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.execute(DefaultPlanExecutor.java:459)</span></span>
	at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.run(DefaultPlanExecutor.java:376)</span></span>
	at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64)</span></span>
	at org.gradle.internal.concurrent.AbstractManagedExecutor$1.run(AbstractManagedExecutor.java:47)</span></span>
Caused by: org.gradle.workers.internal.DefaultWorkerExecutor$WorkExecutionException: A failure occurred while executing org.jetbrains.kotlin.compilerRunner.GradleCompilerRunnerWithWorkers$GradleKotlinCompilerWorkAction</span></span>
	at org.gradle.workers.internal.DefaultWorkerExecutor$WorkItemExecution.waitForCompletion(DefaultWorkerExecutor.java:289)</span></span>
	at org.gradle.internal.work.DefaultAsyncWorkTracker.lambda$waitForItemsAndGatherFailures$2(DefaultAsyncWorkTracker.java:130)</span></span>
	at org.gradle.internal.Factories$1.create(Factories.java:33)</span></span>
	at org.gradle.internal.work.DefaultWorkerLeaseService.lambda$withoutLocks$2(DefaultWorkerLeaseService.java:344)</span></span>
	at org.gradle.internal.work.ResourceLockStatistics$1.measure(ResourceLockStatistics.java:42)</span></span>
	at org.gradle.internal.work.DefaultWorkerLeaseService.withoutLocks(DefaultWorkerLeaseService.java:342)</span></span>
	at org.gradle.internal.work.DefaultWorkerLeaseService.withoutLocks(DefaultWorkerLeaseService.java:326)</span></span>
	at org.gradle.internal.work.DefaultWorkerLeaseService.withoutLock(DefaultWorkerLeaseService.java:331)</span></span>
	at org.gradle.internal.work.DefaultAsyncWorkTracker.waitForItemsAndGatherFailures(DefaultAsyncWorkTracker.java:126)</span></span>
	at org.gradle.internal.work.DefaultAsyncWorkTracker.waitForItemsAndGatherFailures(DefaultAsyncWorkTracker.java:92)</span></span>
	at org.gradle.internal.work.DefaultAsyncWorkTracker.waitForAll(DefaultAsyncWorkTracker.java:78)</span></span>
	at org.gradle.internal.work.DefaultAsyncWorkTracker.waitForCompletion(DefaultAsyncWorkTracker.java:66)</span></span>
	at org.gradle.api.internal.tasks.execution.TaskExecution$3.run(TaskExecution.java:260)</span></span>
	at org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:29)</span></span>
	at org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:26)</span></span>
	at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:66)</span></span>
	at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:59)</span></span>
	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:166)</span></span>
	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:59)</span></span>
	at org.gradle.internal.operations.DefaultBuildOperationRunner.run(DefaultBuildOperationRunner.java:47)</span></span>
	at org.gradle.api.internal.tasks.execution.TaskExecution.executeAction(TaskExecution.java:237)</span></span>
	at org.gradle.api.internal.tasks.execution.TaskExecution.executeActions(TaskExecution.java:220)</span></span>
	at org.gradle.api.internal.tasks.execution.TaskExecution.executeWithPreviousOutputFiles(TaskExecution.java:203)</span></span>
	at org.gradle.api.internal.tasks.execution.TaskExecution.execute(TaskExecution.java:170)</span></span>
	at org.gradle.internal.execution.steps.ExecuteStep.executeInternal(ExecuteStep.java:105)</span></span>
	at org.gradle.internal.execution.steps.ExecuteStep.access$000(ExecuteStep.java:44)</span></span>
	at org.gradle.internal.execution.steps.ExecuteStep$1.call(ExecuteStep.java:59)</span></span>
	at org.gradle.internal.execution.steps.ExecuteStep$1.call(ExecuteStep.java:56)</span></span>
	at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:209)</span></span>
	at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:204)</span></span>
	at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:66)</span></span>
	at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:59)</span></span>
	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:166)</span></span>
	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:59)</span></span>
	at org.gradle.internal.operations.DefaultBuildOperationRunner.call(DefaultBuildOperationRunner.java:53)</span></span>
	at org.gradle.internal.execution.steps.ExecuteStep.execute(ExecuteStep.java:56)</span></span>
	at org.gradle.internal.execution.steps.ExecuteStep.execute(ExecuteStep.java:44)</span></span>
	at org.gradle.internal.execution.steps.CancelExecutionStep.execute(CancelExecutionStep.java:42)</span></span>
	at org.gradle.internal.execution.steps.TimeoutStep.executeWithoutTimeout(TimeoutStep.java:75)</span></span>
	at org.gradle.internal.execution.steps.TimeoutStep.execute(TimeoutStep.java:55)</span></span>
	at org.gradle.internal.execution.steps.PreCreateOutputParentsStep.execute(PreCreateOutputParentsStep.java:50)</span></span>
	at org.gradle.internal.execution.steps.PreCreateOutputParentsStep.execute(PreCreateOutputParentsStep.java:28)</span></span>
	at org.gradle.internal.execution.steps.RemovePreviousOutputsStep.execute(RemovePreviousOutputsStep.java:68)</span></span>
	at org.gradle.internal.execution.steps.RemovePreviousOutputsStep.execute(RemovePreviousOutputsStep.java:38)</span></span>
	at org.gradle.internal.execution.steps.BroadcastChangingOutputsStep.execute(BroadcastChangingOutputsStep.java:61)</span></span>
	at org.gradle.internal.execution.steps.BroadcastChangingOutputsStep.execute(BroadcastChangingOutputsStep.java:26)</span></span>
	at org.gradle.internal.execution.steps.CaptureOutputsAfterExecutionStep.execute(CaptureOutputsAfterExecutionStep.java:69)</span></span>
	at org.gradle.internal.execution.steps.CaptureOutputsAfterExecutionStep.execute(CaptureOutputsAfterExecutionStep.java:46)</span></span>
	at org.gradle.internal.execution.steps.ResolveInputChangesStep.execute(ResolveInputChangesStep.java:39)</span></span>
	at org.gradle.internal.execution.steps.ResolveInputChangesStep.execute(ResolveInputChangesStep.java:28)</span></span>
	at org.gradle.internal.execution.steps.BuildCacheStep.executeWithoutCache(BuildCacheStep.java:189)</span></span>
	at org.gradle.internal.execution.steps.BuildCacheStep.lambda$execute$1(BuildCacheStep.java:75)</span></span>
	at org.gradle.internal.Either$Right.fold(Either.java:176)</span></span>
	at org.gradle.internal.execution.caching.CachingState.fold(CachingState.java:62)</span></span>
	at org.gradle.internal.execution.steps.BuildCacheStep.execute(BuildCacheStep.java:73)</span></span>
	at org.gradle.internal.execution.steps.BuildCacheStep.execute(BuildCacheStep.java:48)</span></span>
	at org.gradle.internal.execution.steps.StoreExecutionStateStep.execute(StoreExecutionStateStep.java:46)</span></span>
	at org.gradle.internal.execution.steps.StoreExecutionStateStep.execute(StoreExecutionStateStep.java:35)</span></span>
	at org.gradle.internal.execution.steps.SkipUpToDateStep.executeBecause(SkipUpToDateStep.java:75)</span></span>
	at org.gradle.internal.execution.steps.SkipUpToDateStep.lambda$execute$2(SkipUpToDateStep.java:53)</span></span>
	at org.gradle.internal.execution.steps.SkipUpToDateStep.execute(SkipUpToDateStep.java:53)</span></span>
	at org.gradle.internal.execution.steps.SkipUpToDateStep.execute(SkipUpToDateStep.java:35)</span></span>
	at org.gradle.internal.execution.steps.legacy.MarkSnapshottingInputsFinishedStep.execute(MarkSnapshottingInputsFinishedStep.java:37)</span></span>
	at org.gradle.internal.execution.steps.legacy.MarkSnapshottingInputsFinishedStep.execute(MarkSnapshottingInputsFinishedStep.java:27)</span></span>
	at org.gradle.internal.execution.steps.ResolveIncrementalCachingStateStep.executeDelegate(ResolveIncrementalCachingStateStep.java:49)</span></span>
	at org.gradle.internal.execution.steps.ResolveIncrementalCachingStateStep.executeDelegate(ResolveIncrementalCachingStateStep.java:27)</span></span>
	at org.gradle.internal.execution.steps.AbstractResolveCachingStateStep.execute(AbstractResolveCachingStateStep.java:71)</span></span>
	at org.gradle.internal.execution.steps.AbstractResolveCachingStateStep.execute(AbstractResolveCachingStateStep.java:39)</span></span>
	at org.gradle.internal.execution.steps.ResolveChangesStep.execute(ResolveChangesStep.java:64)</span></span>
	at org.gradle.internal.execution.steps.ResolveChangesStep.execute(ResolveChangesStep.java:35)</span></span>
	at org.gradle.internal.execution.steps.ValidateStep.execute(ValidateStep.java:62)</span></span>
	at org.gradle.internal.execution.steps.ValidateStep.execute(ValidateStep.java:40)</span></span>
	at org.gradle.internal.execution.steps.AbstractCaptureStateBeforeExecutionStep.execute(AbstractCaptureStateBeforeExecutionStep.java:76)</span></span>
	at org.gradle.internal.execution.steps.AbstractCaptureStateBeforeExecutionStep.execute(AbstractCaptureStateBeforeExecutionStep.java:45)</span></span>
	at org.gradle.internal.execution.steps.AbstractSkipEmptyWorkStep.executeWithNonEmptySources(AbstractSkipEmptyWorkStep.java:136)</span></span>
	at org.gradle.internal.execution.steps.AbstractSkipEmptyWorkStep.execute(AbstractSkipEmptyWorkStep.java:66)</span></span>
	at org.gradle.internal.execution.steps.AbstractSkipEmptyWorkStep.execute(AbstractSkipEmptyWorkStep.java:38)</span></span>
	at org.gradle.internal.execution.steps.legacy.MarkSnapshottingInputsStartedStep.execute(MarkSnapshottingInputsStartedStep.java:38)</span></span>
	at org.gradle.internal.execution.steps.LoadPreviousExecutionStateStep.execute(LoadPreviousExecutionStateStep.java:36)</span></span>
	at org.gradle.internal.execution.steps.LoadPreviousExecutionStateStep.execute(LoadPreviousExecutionStateStep.java:23)</span></span>
	at org.gradle.internal.execution.steps.HandleStaleOutputsStep.execute(HandleStaleOutputsStep.java:75)</span></span>
	at org.gradle.internal.execution.steps.HandleStaleOutputsStep.execute(HandleStaleOutputsStep.java:41)</span></span>
	at org.gradle.internal.execution.steps.AssignMutableWorkspaceStep.lambda$execute$0(AssignMutableWorkspaceStep.java:35)</span></span>
	at org.gradle.api.internal.tasks.execution.TaskExecution$4.withWorkspace(TaskExecution.java:297)</span></span>
	at org.gradle.internal.execution.steps.AssignMutableWorkspaceStep.execute(AssignMutableWorkspaceStep.java:31)</span></span>
	at org.gradle.internal.execution.steps.AssignMutableWorkspaceStep.execute(AssignMutableWorkspaceStep.java:22)</span></span>
	at org.gradle.internal.execution.steps.ChoosePipelineStep.execute(ChoosePipelineStep.java:40)</span></span>
	at org.gradle.internal.execution.steps.ChoosePipelineStep.execute(ChoosePipelineStep.java:23)</span></span>
	at org.gradle.internal.execution.steps.ExecuteWorkBuildOperationFiringStep.lambda$execute$2(ExecuteWorkBuildOperationFiringStep.java:67)</span></span>
	at org.gradle.internal.execution.steps.ExecuteWorkBuildOperationFiringStep.execute(ExecuteWorkBuildOperationFiringStep.java:67)</span></span>
	at org.gradle.internal.execution.steps.ExecuteWorkBuildOperationFiringStep.execute(ExecuteWorkBuildOperationFiringStep.java:39)</span></span>
	at org.gradle.internal.execution.steps.IdentityCacheStep.execute(IdentityCacheStep.java:46)</span></span>
	at org.gradle.internal.execution.steps.IdentityCacheStep.execute(IdentityCacheStep.java:34)</span></span>
	at org.gradle.internal.execution.steps.IdentifyStep.execute(IdentifyStep.java:44)</span></span>
	at org.gradle.internal.execution.steps.IdentifyStep.execute(IdentifyStep.java:31)</span></span>
	at org.gradle.internal.execution.impl.DefaultExecutionEngine$1.execute(DefaultExecutionEngine.java:64)</span></span>
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeIfValid(ExecuteActionsTaskExecuter.java:132)</span></span>
	... 30 more</span></span>
Caused by: org.jetbrains.kotlin.gradle.tasks.FailedCompilationException: Internal compiler error. See log for more details</span></span>
	at org.jetbrains.kotlin.gradle.tasks.TasksUtilsKt.throwExceptionIfCompilationFailed(tasksUtils.kt:22)</span></span>
	at org.jetbrains.kotlin.compilerRunner.GradleKotlinCompilerWork.run(GradleKotlinCompilerWork.kt:112)</span></span>
	at org.jetbrains.kotlin.compilerRunner.GradleCompilerRunnerWithWorkers$GradleKotlinCompilerWorkAction.execute(GradleCompilerRunnerWithWorkers.kt:75)</span></span>
	at org.gradle.workers.internal.DefaultWorkerServer.execute(DefaultWorkerServer.java:68)</span></span>
	at org.gradle.workers.internal.NoIsolationWorkerFactory$1$1.create(NoIsolationWorkerFactory.java:64)</span></span>
	at org.gradle.workers.internal.NoIsolationWorkerFactory$1$1.create(NoIsolationWorkerFactory.java:61)</span></span>
	at org.gradle.internal.classloader.ClassLoaderUtils.executeInClassloader(ClassLoaderUtils.java:100)</span></span>
	at org.gradle.workers.internal.NoIsolationWorkerFactory$1.lambda$execute$0(NoIsolationWorkerFactory.java:61)</span></span>
	at org.gradle.workers.internal.AbstractWorker$1.call(AbstractWorker.java:44)</span></span>
	at org.gradle.workers.internal.AbstractWorker$1.call(AbstractWorker.java:41)</span></span>
	at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:209)</span></span>
	at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:204)</span></span>
	at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:66)</span></span>
	at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:59)</span></span>
	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:166)</span></span>
	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:59)</span></span>
	at org.gradle.internal.operations.DefaultBuildOperationRunner.call(DefaultBuildOperationRunner.java:53)</span></span>
	at org.gradle.workers.internal.AbstractWorker.executeWrappedInBuildOperation(AbstractWorker.java:41)</span></span>
	at org.gradle.workers.internal.NoIsolationWorkerFactory$1.execute(NoIsolationWorkerFactory.java:58)</span></span>
	at org.gradle.workers.internal.DefaultWorkerExecutor.lambda$submitWork$0(DefaultWorkerExecutor.java:176)</span></span>
	at org.gradle.internal.work.DefaultConditionalExecutionQueue$ExecutionRunner.runExecution(DefaultConditionalExecutionQueue.java:194)</span></span>
	at org.gradle.internal.work.DefaultConditionalExecutionQueue$ExecutionRunner.access$700(DefaultConditionalExecutionQueue.java:127)</span></span>
	at org.gradle.internal.work.DefaultConditionalExecutionQueue$ExecutionRunner$1.run(DefaultConditionalExecutionQueue.java:169)</span></span>
	at org.gradle.internal.Factories$1.create(Factories.java:33)</span></span>
	at org.gradle.internal.work.DefaultWorkerLeaseService.lambda$withLocksAcquired$0(DefaultWorkerLeaseService.java:269)</span></span>
	at org.gradle.internal.work.ResourceLockStatistics$1.measure(ResourceLockStatistics.java:42)</span></span>
	at org.gradle.internal.work.DefaultWorkerLeaseService.withLocksAcquired(DefaultWorkerLeaseService.java:267)</span></span>
	at org.gradle.internal.work.DefaultWorkerLeaseService.withLocks(DefaultWorkerLeaseService.java:259)</span></span>
	at org.gradle.internal.work.DefaultWorkerLeaseService.runAsWorkerThread(DefaultWorkerLeaseService.java:127)</span></span>
	at org.gradle.internal.work.DefaultWorkerLeaseService.runAsWorkerThread(DefaultWorkerLeaseService.java:132)</span></span>
	at org.gradle.internal.work.DefaultConditionalExecutionQueue$ExecutionRunner.runBatch(DefaultConditionalExecutionQueue.java:164)</span></span>
	at org.gradle.internal.work.DefaultConditionalExecutionQueue$ExecutionRunner.run(DefaultConditionalExecutionQueue.java:133)</span></span>
	... 2 more</span></span>
</span></code></pre></details>
The full trace was long and didn't seem related to a code failure in the module itself. So I employed the solution, which is always the same:</p>

./mach build</code></li>
In Android Studio, File > Sync Project with Gradle Files.</li>
</ol>
Yup, that's all. Very simple and boring.</p>

^{1</sup>
With Jujutsu, this is the moz-phab command I use which has made it easier to manage review patches: moz-phab patch <patch-id> --no-branch --apply-to main@origin</code></p>
</div>}
  Comments</h3>
  With an account on the Fediverse or Mastodon, you can respond to this post</a>. Since Mastodon is decentralized, you can use your existing account hosted by another Mastodon server or compatible platform if you don't have an account on this one. Known non-private replies are displayed below.</p>
  
Learn how this was implemented from the original source here.</a></p>
Jonathan Almeida

5x400s

Toronto - Easy Run

Toronto - Easy Run

Toronto - Easy Run

Fun Running

Auto-resolve Jujutsu conflicts with your AI agent

Toronto - Easy Run

Sporting Life 10K 2026

jj presentation - cheat sheet

Jujutsu for git users (WIP)

Advanced or mozilla-central workflows</h2>

`absorb</code></li>`
`Handling conflicts.</li>`
`split</code></li>`
`No branches.</li>`
`moz-phab patch</code></li>`
`workspaces</code></li> </ul>`

Toronto - Easy Run

Toronto - Easy Run

Toronto - Base

Gmail filters based on X-Phabricator-Stamps header

Toronto Running

Toronto Running

Toronto - Easy Run

Use Android Studio for resolving conflicts in Jujutsu

Create new revisions in Jujutsu with multiple heads

Use |mach try --no-push| for a configuration dry run

Toronto - Easy Run

Don't credit Claude for patches that you submit for code review

Toronto - Easy Run

Toronto - Easy Run

My Firefox for Android local build environment

Jonathan Almeida

5x400s

Toronto - Easy Run

Toronto - Easy Run

Toronto - Easy Run

Fun Running

Auto-resolve Jujutsu conflicts with your AI agent

Toronto - Easy Run

Sporting Life 10K 2026

jj presentation - cheat sheet

Jujutsu for git users (WIP)

Advanced or mozilla-central workflows</h2> absorb</code></li> Handling conflicts.</li> split</code></li> No branches.</li> moz-phab patch</code></li> workspaces</code></li> </ul>

Toronto - Easy Run

Toronto - Easy Run

Toronto - Base

Gmail filters based on X-Phabricator-Stamps header

Toronto Running

Toronto Running

Toronto - Easy Run

Use Android Studio for resolving conflicts in Jujutsu

Create new revisions in Jujutsu with multiple heads

Use |mach try --no-push| for a configuration dry run

Toronto - Easy Run

Don't credit Claude for patches that you submit for code review

Toronto - Easy Run

Toronto - Easy Run

My Firefox for Android local build environment

Debugging</h2> This section is for miscellaneous build error situations that come-up, but assuming mach build</code> work and there are no known Android build changes, my solution has typically always been the same.</p>

Advanced or mozilla-central workflows</h2>

`absorb</code></li>`
`Handling conflicts.</li>`
`split</code></li>`
`No branches.</li>`
`moz-phab patch</code></li>`
`workspaces</code></li> </ul>`
