TYMorningCoffee

https://en.wikipedia.org/wiki/Pixel_Dungeon is an example of that. The bad forks dont become popular

Did the grumpy gamer mean perforce instead of perform and it got auto 'corrected'?

VMware owns Spring Boot https://en.m.wikipedia.org/wiki/Spring_Boot

Impressive! Can't wait to try Fray out at work.

Click the ying yang looking icon to get an explanation

> 4-7-8 Breathing The 4-7-8 technique involves inhaling for 4 counts, holding for 7, and exhaling for 8. This pattern is repeated several times. Developed by Dr. Andrew Weil, it helps reduce anxiety, manage stress, and promote better sleep by triggering your body's natural relaxation response and slowing your heart rate.

Some setups can run devstral small locally. Have you tried?

Also have you tried any other open weight models as the architect?

Third, as far as I understood, devstral was made with open hands so it might perform better there than aider out of the box.

Finally, I'm looking for local llm only setups for apple silicon 32gb and was considering devstral with open hands.

A lot of commenters point out that there already are many established static checkers that do this. That is not what Uber attempts here.

Uber is not proposing a static checker. They even use sonar qube in their architecture. They propose using an LLM to resolve the leak detected by sonar qube.

This architecture is promising. Large legacy code bases can have static analysis violations in the 1000s which devs never have the time to address. I've seen sonar tube reports that require man years to resolve everything.

These existing tools (spotbugs, findings, sonarqube, null away, checker framework, pmd, etc) provide detection but not resolution. Resolution thru LLM is what Uber proposes.

It's not identifying the leaks. In their architecture they use Sonar qube for the detecting. The LLM provides the fix.

I forgot to clarify dealing with the network bottleneck

Can the inference piece be partitioned over multiple hosts?

Edit: algorithmed or partitioned in a way that overcomes the network bottleneck

Fixed! It was because the table overflowed. This created a scroll bar for the entire page. The entire page scrollbar had a weird interaction with the code block scroll bars. Now that there is no more whole page scroll bar, it works.

I think I tracked it down to the table in the article adding a scroll bar for the entire page. This scrollbar fights with the code blocks scrollbar. I will try to refactor the table to fit in a phone width somehow.

Yes. Sorry about that. Will look into it when I have time.

It depends which OS. Windows yes, Linux no.

It came down to poor logic. I got hung up on it because I got unlucky and couldn't reproduce it with uncaught NPE so I incorrectly concluded that uncaught NPE was a necessary condition.

Oh no I didn't know this can happen with HashMaps too! Something to do with the linked list they use for collisions?

Good point. It should be replaced with an if not empty check.

Ouch. Any idea which problem? Those problems are public: https://ioinformatics.org/page/contests/10

I remember reading that article but being unable to understand it due to my lack of knowledge in the area. I will have to give it another go.

Could you propose to fail the build based on the number of warnings to ensure it doesn't go up?

I did something similar with spotbugs. There were existing warnings I couldn't get time to fix so I configured the maven to fail if it exceed the level at which I enabled it.

This has the unfortunate side effect that if it drops and no one adjusts the threshold then people can add more issues without failing the build.

That's much better. Constant memory. The number of nodes is guaranteed to be less than or equal to the height of the tree.

Have you seen this before in person? It would make a great blog post.

I haven't personally encountered a buggy comparator without a total order.

> Food for thought. I often think to myself that any error or strange behavior or even warnings in a project should be fixed as a matter of principle, as they could cause seemingly unrelated problems. Rarely is this accepted by whoever chooses what we should work on.

I agree. I hate lingering warnings. Unfortunately at the at time of this bug I did not have static analysis tools to detect these code smells.

You're right. That would have been a better choice.

Both! The TreeMap is thread unsafe. The business logic needs to protect against concurrent access to the TreeMap or not use the treemap at all.

Why do you think the article assumes statefile is local? I don't think that assumption was made.

> Python deterministically generating terraform HCL files based on yaml.

That sounds terrible. I'm sorry you had to deal with that.

If they could go back in time, would modules have been good enough?

What's the craziest terraform repo you have seen? Is it okay to mix code (ex: Java) and terraform in a large mono repo?