WEBVTT

00:00:01.330 --> 00:00:03.353 align:center
Okay, we're going to solve another

00:00:03.794 --> 00:00:06.279 align:center
bug on MLflow repository, first with

00:00:06.479 --> 00:00:07.741 align:center
Cloud Code by itself.

00:00:08.462 --> 00:00:10.546 align:center
You can see it's working rather

00:00:10.606 --> 00:00:10.927 align:center
fast.

00:00:10.987 --> 00:00:12.930 align:center
It's actually misidentifying the cause of

00:00:12.990 --> 00:00:13.391 align:center
the bug.

00:00:14.533 --> 00:00:16.256 align:center
It points it to be inside

00:00:16.296 --> 00:00:19.421 align:center
something inside the OpenAI library that

00:00:19.461 --> 00:00:20.964 align:center
is not the correct fix, even

00:00:21.024 --> 00:00:23.649 align:center
though it only consumes 30% of

00:00:23.709 --> 00:00:24.510 align:center
the session tokens.

00:00:25.020 --> 00:00:27.564 align:center
Now with Kawa code having access

00:00:27.604 --> 00:00:30.048 align:center
to the decision history which was

00:00:30.088 --> 00:00:31.810 align:center
done via infer history in Kawa

00:00:31.830 --> 00:00:34.054 align:center
code it gets the right relevant

00:00:34.154 --> 00:00:36.237 align:center
context the decisions that were made

00:00:36.718 --> 00:00:38.901 align:center
previously that are relevant to fixing

00:00:38.941 --> 00:00:41.024 align:center
this bug and even though it

00:00:41.565 --> 00:00:43.688 align:center
takes a little longer it consumes

00:00:43.728 --> 00:00:46.673 align:center
about 49% of the session tokens

00:00:47.374 --> 00:00:49.096 align:center
it does this time arrive at

00:00:49.156 --> 00:00:51.220 align:center
the right fix in patched agent

00:00:51.300 --> 00:00:51.520 align:center
run

00:00:51.980 --> 00:00:55.418 align:center
and this fix was accepted and

00:00:55.458 --> 00:00:57.428 align:center
merged into the repository by the

00:00:57.468 --> 00:00:59.720 align:center
maintainer of the MLflow repository.