Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
williamzeng0
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
31.
▲
Sweep (YC S23) is hiring a Founding Engineers to build a code generation bot
(ycombinator.com)
1 points
by
williamzeng0
2y ago
32.
▲
Sweep (YC S23) is hiring a Founding ML engineer to build an AI developer
(ycombinator.com)
1 points
by
williamzeng0
2y ago
33.
▲
by
williamzeng0
3y ago
This is great! I see it also supports an 'ignore' parameter.
34.
▲
by
williamzeng0
3y ago
That sounds great, I'm going to see how Sweep does on this issue: https://github.com/sweepai/sweep/issues/3333
35.
▲
by
williamzeng0
3y ago
I appreciate the sentiment! Makes a ton of sense.
36.
▲
by
williamzeng0
3y ago
Thank you for checking! That works, we could just override the key logic to check the source code (I'm guessing it's easily accessible)
37.
▲
by
williamzeng0
3y ago
This is great, thanks for the suggestion! We've just updated our docs and code with this change: https://github.com/sweepai/sweep/pull/3332
38.
▲
by
williamzeng0
3y ago
The version input makes sense, I could also see some developers disliking that ux because of it's verbosity. But to deliberately invalidate you have to make a manual effort in either case.
39.
▲
by
williamzeng0
3y ago
Thread safety is a big issue with ours, we'll run into issues when two different processes attempt to write to the same location, or we'll get a bad read. This is a better solution for large scale workloads. Ours is more meant for
40.
▲
by
williamzeng0
3y ago
file.mtime. (file last modified) is an awesome way to key the cache.
41.
▲
by
williamzeng0
3y ago
+1, we considered traversing the function's dependencies to key the cache on (not just the initial function source code), but decided to leave this in a as a constraint. Otherwise we also blowing up the cache when we didn't want i
42.
▲
by
williamzeng0
3y ago
Making the __dict__ opt-in makes it a lot more user-friendly at the expense of a little verbosity. That makes sense. These tips make sense, we often use named args in our function calls (not using them has caused so many bugs), but we don&#
43.
▲
by
williamzeng0
3y ago
100%, invalidation needs to be fast or you're not really saving time. I'm curious about calling a global function, what's the use case for that?
44.
▲
by
williamzeng0
3y ago
It does feel like diskcache is for performance gains in production rather than dev time gains. It seems like it would be bothersome to quickly invalidate the cache in case of a bad write.
45.
▲
by
williamzeng0
3y ago
Diskcache works well, we just wanted a dependency free version that we had more control over (easier cache key deletion). I think you'd have to write a custom hashing function for diskcache to use the function source code as a key. I&#
46.
▲
by
williamzeng0
3y ago
Unfortunately it doesn't, we typically don't expect to handle high load with this cache and actually disable it in production with another envvar. Sometimes caching can actually be slower for certain functions, because just perfor
47.
▲
by
williamzeng0
3y ago
I think the marginal gain would be a lot less for Jupyter notebooks, but I've definitely rerun individual cells and wasted time there before. I think it could help if you forget to save the output of a function within a single cell lik
48.
▲
Show HN: File-based cache for slow Python functions
(docs.sweep.dev)
73 points
by
williamzeng0
3y ago
|
57 comments
49.
▲
by
williamzeng0
3y ago
This is great, thanks for making it!
50.
▲
by
williamzeng0
3y ago
In our benchmarks, open source models still have a long way to go (just breaking past the GPT 3.5 barrier now). We're excited to move to open source models when they're ready, but right now they simply aren't there yet. Even
51.
▲
The Slowest GitHub PRs in Recorded History
(graphite.dev)
2 points
by
williamzeng0
3y ago
|
0 comments
52.
▲
Escaping containers using the Dirty Pipe vulnerability
(securitylabs.datadoghq.com)
1 points
by
williamzeng0
3y ago
|
0 comments
53.
▲
Speeding Up Deployments with Lazy Image Streaming
(blog.replit.com)
2 points
by
williamzeng0
3y ago
|
0 comments
54.
▲
82% of Open-Source Projects Suffer from Tool Rot
(trunk.io)
2 points
by
williamzeng0
3y ago
|
0 comments
55.
▲
Nth Fibonacci number in O(log n)
(kukuruku.co)
2 points
by
williamzeng0
3y ago
|
0 comments
56.
▲
A Versatile East Asian Chili
(peppergeek.com)
2 points
by
williamzeng0
3y ago
|
0 comments
57.
▲
Game where you guess the correlation coefficient
(guessthecorrelation.com)
1 points
by
williamzeng0
3y ago
|
1 comments
58.
▲
by
williamzeng0
3y ago
Nice to see this open source :)
59.
▲
by
williamzeng0
3y ago
I'm really excited about E2B. Axilla looks great too! :)
60.
▲
by
williamzeng0
3y ago
We have that! You can directly append to our system prompt here to customize Sweep https://github.com/sweepai/sweep/blob/main/sweep.yaml
More ›