niea_11
My understanding is that it's best effort because even if you control the seed/temperature, the model version and hardware specs you still have floating point math that will introduce rounding differences
an article explaining this in detail : https://news.ycombinator.com/item?id=45200925
https://www.reuters.com/technology/nvidia-is-sued-by-authors...
(The original video is in french but it has an autodubbed english track)
AISLE demonstrated in the last few weeks that small (weak per the author) models can find the openBSD bug (when pointed at the code). And apparently did several runs with the same results. Was gpt oss hallucinating on all those runs?
And what separates a strong model from a weak one? Is qwen3.5 27b weak?
Don't trust who says that weak models can find the OpenBSD SACK bug. I tried it myself. What happens is that weak models hallucinate (sometimes causally hitting a real problem) that there is a lack of validation of the start of the window (which is in theory harmless because of the start < end validation) and the integer overflow problem without understanding why they, if put together, create an issue. It's just pattern matching of bug classes on code that looks may have a problem, totally lacking the true ability to understand the issue and write an exploit. Test it yourself, GPT 120B OSS is cheap and available.
BTW, this is why with this bug, the stronger the model you pick (but not enough to discover the true bug), the less likely it is it will claim there is a bug. Stronger models hallucinate less, so they can't see the problem in any side of the spectrum: the hallucination side of small models, and the real understanding side of Mythos
I don't believe this is specific to the US. The agent at the border always has the last decision on whether you can enter the country even if you have a valid visa and travel documents.
Senate bill targets requires online companies to report drug activity
Something like this :
magnet:?xt=urn:btih:BSXYFTH5VCJLB32DYS2FPTJUB2IVNKUS&dn=Fedora-Astronomy_KDE-Live-x86_64-37Microsoft did something similar before (without a vm) called Static Typescript : https://www.microsoft.com/en-us/research/publication/static-...
I always read it as being about empathy. Explaining that sometimes a person's action probably have subjectively valid reasons that we should try to understand, or at least try to accept.
I read the gp comment's quote the same way that's why I shared this one.
The so-called ‘psychotically depressed’ person who tries to kill herself doesn’t do so out of quote ‘hopelessness’ or any abstract conviction that life’s assets and debits do not square. And surely not because death seems suddenly appealing. The person in whom Its invisible agony reaches a certain unendurable level will kill herself the same way a trapped person will eventually jump from the window of a burning high-rise. Make no mistake about people who leap from burning windows. Their terror of falling from a great height is still just as great as it would be for you or me standing speculatively at the same window just checking out the view; i.e. the fear of falling remains a constant. The variable here is the other terror, the fire’s flames: when the flames get close enough, falling to death becomes the slightly less terrible of two terrors. It’s not desiring the fall; it’s terror of the flames. And yet nobody down on the sidewalk, looking up and yelling ‘Don’t!’ and ‘Hang on!’, can understand the jump. Not really. You’d have to have personally been trapped and felt flames to really understand a terror way beyond falling.
I think they're planning to move it next to the like button to make it more visible.
Do you have the names of the authors of the first one?
A lazy google search didn't mention the commission of two reports
Twitter is now an editorial media and no longer a social media platform
More info here : https://www.codegram.com/case-studies/github-skyline/
NNCP: Lossless Data Compression with Neural Networks
Playstation is made by Sony Interactive Entertainment so they probably have different directives/rules
But the freebsd license isn't listed in this page : https://doc.dl.playstation.net/doc/ps5-oss/index.html
So I'm not sure if the first page is correct.
For PS4, the freebsd license was listed here : https://doc.dl.playstation.net/doc/ps4-oss/index.html
Curtailment of nuclear power due to periods of extreme heat has had the effect of reducing European nuclear power output by approx. 0.1% since the year 2000. For France specifically, which with its many inland river-sited plants has been the worst hit country, the corresponding figure is approximately 0.15%
There are other lookup mechanisms, (didn't check them all) but they only retrieve environment/static values (this one [2] for example retrieves kubernetes attributes). I think the jndi one is the only one that load and execute code.
Edit : I think my understanding of the docs is incorrect so ignore the next paragraph
From the documentation [3], I have the impression that these variables should be evaluated only when loading the pattern layout configuration. But in reality they are also evaluated when formatting the final log message (log.info(...)).
I agree that the input should be sanitized but only if the formatting behavior is a bug and was not intentional.
One possible explanation for the current situation, is that developers assumed that all lookup mechanism will retrieve only static values (env variables for example).
And then another dev introduced the jndi lookup which execute code, but no one noticed the impact on the already existing behavior (evaluation variable when formatting the final msg).
Edit
1: https://github.com/apache/logging-log4j2/blob/9df31f73b62ba2...
2: https://github.com/apache/logging-log4j2/blob/c2b07e37995004...