JackHopkins

5 ms·

1.
by JackHopkins 3y ago
Can't you replay pending requests? How can you mitigate the issue of differing side effects generated by the new / old versions?
2.
by JackHopkins 3y ago
Cool! why is it crucial to keep old versions of code, and what are the risks of running outdated code?
3.
by JackHopkins 3y ago
Thanks - what is your sweet spot use-case do you think? I've built a few GraphQL projects in the past, so I'm curious where you fit into the ecosystem?
4.
by JackHopkins 3y ago
This is really cool, nice work! How does this differ from Apollo Federation? I'm a bit confused here, because you have integrations with AF too - is this competitive, or is this a more vertically-integrated solution? Cheers!
5.
by JackHopkins 3y ago
What is the order of the cost of the workflow function?
6.
by JackHopkins 3y ago
This is really cool! Am I right in thinking that the cost for running this program is equivalent to all of the dependency execution durations? i.e no busy waiting?
7.
Tanuki: Alignment-as-Code for LLM Applications(github.com)
8 points by JackHopkins 3y ago|1 comments
8.
by JackHopkins 3y ago
Hey everyone, I'm a main contributor of Tanuki (formerly MonkeyPatch). The purpose of Tanuki is to reduce the time to ship your LLM projects, so you can focus on building what your users want instead of MLOps. You define patched functi
9.
by JackHopkins 3y ago
I understand the point. I would ideally like an association with monkey-patching something as that is relevant to the behaviour of the package. However, not so similar that it shadows the technique of monkey-patching!
10.
by JackHopkins 3y ago
Yeah this is fair. I’m not attached to a simian theme if we’re ditching specific association to monkey-patching something. Or indeed, a ‘patching’ theme for that matter. A new name is definitely in order. I will think about it over the week
11.
by JackHopkins 3y ago
I do get the point and the difference from the classical monkey-patching. I like the stub ideas though!
12.
by JackHopkins 3y ago
Good to know, we'll make it more clear in the docs! To answer regarding these 2 areas, 1) The data for finetuning currently is saved on disk for low latency reading and writing. Both test statements and datapoints from the function exe
13.
by JackHopkins 3y ago
Do any other names jump out at you as preferable?
14.
by JackHopkins 3y ago
Thoughts on something like PyMonkeyPatch? GorillaPatch?
15.
by JackHopkins 3y ago
Don't get me wrong, I do appreciate the criticism of the current naming! It does seem to create some unwanted friction of using or talking about the library, I was just trying to explain the thought process and ideate on top of it but
16.
by JackHopkins 3y ago
Great question! That is one of the ideas that we have on the roadmap and seems quite exciting to us. The general feasibility of switching the function execution over from a LLM to synthesised code depends on the specific use-case and if a d
17.
by JackHopkins 3y ago
Yeah I definitely agree on the latter point, it does look odd. PyMonkeyPatch?
18.
by JackHopkins 3y ago
The IDEs shouldn't complain if the function has a docstring (which all the MP functions should have as that's the instruction that is executed) and the @patch decorator, atleast the ones we have tried it with have liked the syntax
19.
by JackHopkins 3y ago
PyMonkeyPatch? MonkeyPatch.py? I would quite like a short and distinctive name!
20.
by JackHopkins 3y ago
This is a solid point, at the end of the day creating confusion with the name wasn't the goal in any way as there already are 100s of (often overlapping) terms floating around in this scene. I appreciate the critique and we'll hav
21.
by JackHopkins 3y ago
The big one is a Typescript implementation. Other than that, the plan is to support other models (e.g Llama) that can be fine-tuned. Finally, other persistence layers like S3 and Redis, to support running on execution targets (like AWS Lamb
22.
by JackHopkins 3y ago
The python package (and repo) is called ‘monkeypatch.py’ for the avoidance of confusion.
23.
by JackHopkins 3y ago
Heya, no worries - I’m glad to share it. MonkeyPatch ensures reliability through what we call ‘test-driven alignment’, in which the tests that reference the patched functions are guaranteed to pass. The more align ‘tests’ you create, the mo
24.
by JackHopkins 3y ago
Check out the ‘function_modeler’. Currently it’s OpenAI only, but local models are on the immediate roadmap. https://github.com/monkeypatch/monkeypatch.py/blob/master/sr...
25.
by JackHopkins 3y ago
Thanks a lot. I’d really appreciate any feedback you have on the design!
26.
by JackHopkins 3y ago
The package is called ‘monkeypatch.py’ on GitHub and PyPi.
27.
by JackHopkins 3y ago
The specific package name on GitHub and PyPi is ‘monkeypatch.py’ for the avoidance of doubt!
28.
by JackHopkins 3y ago
Monkeypatch (as I understand it) means to modify code at runtime. This library modifies functions at runtime to use an LLM as an execution target - I thought it was an apt (if admittedly cheeky) name! Appreciate the critique regardless.
29.
by JackHopkins 3y ago
Native support for OS LLMs is on the roadmap - the main challenge is to figure out how to manage the knowledge distillation for local models. It’s a top priority (along with typescript support), so check back in a few weeks? Right now any ‘
30.
by JackHopkins 3y ago
(As I understand it) monkey-patch means to modify code in runtime. I thought the naming was relevant because by adding ‘@monkey.patch’ to an unimplemented function, this library gives it an implementation at runtime.

More ›