400 karma · joined October 22, 2013
I know what a LLM is and I know very well what is Bayesian Optimization. But I don't understand what this library is trying to do.
I am guessing it's tryng to test the model's ability to generate correct and relevant responses to a given input.
But who is the judge ?
But isn’t there already a blackbox measure of overfiting one that focus on how well the model generalizes to new, unseen data, rather than on the model’s complexity. Like Cross-Validation, hold-out validation or bootstrap method.
You can’t force people to test their software correctly unless it’s a regulated field like aviation.
C# introduced:
await foreach (int item in RangeAsync(10, 3))
Console.Write(item + " "); // Prints 10 11 12
So you dont have to type:IAsyncEnumerator<int> e = RangeAsync(10, 3).GetAsyncEnumerator();
try {
while (await e.MoveNextAsync()) Console.Write(e.Current + " ");
} finally {
if (e != null) await e.DisposeAsync();
}public void syncMethod() {
synchronized(lock) {
// some code
}
}they could translate to
public void syncMethod() {
await reentrantLockAsync.lockAsync();
try {
await somecodeAsync();
} finally {
await lock.unlockAsync()
}
}Kafka and Azure EventHub and RedPanda are EventStream system use Retention policy. They can handle very high throughput efficiently but are not transactional and cannot be safely used when data consistency is the priority.
While system like ActiveMQ, Azure service bus, RabbitMQ are transactional message broker each subscriber to a topic has its own mailbox and message are removed from the mailbox when the client acknowledge that the message has been successfully processed. And deleted from the broker when no mailbox still contain the message. They can be used for workflow involving financial transaction (money) and are very safe. But they sometime dont maintain ordering, client might receive message in different order than the publisher put them inside the topic.
Except in the case of shared cache database connections with PRAGMA read_uncommitted turned on, all transactions in SQLite show "serializable" isolation
IF @@ROWCOUNT = 2 BEGIN COMMIT TRANSACTION; END ELSE BEGIN ROLLBACK TRANSACTION; END
to make sure both rows have been updated. so its a lot simpler to explicitly take a lock on the rows.
if your goal is to transfer 10 dollars for account A to account B but only if account A balance is larger than 10 dollars.
You have to update account A to be 10 dollars less
and
you have to update account B to be 10 dollars more.
you can read both account a keep track of current version number for each.
then do
"UPDATE Accounts SET Balance = CASE AccountID WHEN 1 THEN Balance - 10 WHEN 2 THEN Balance + 10 END WHERE (AccountID, version) IN ((1,v1), (2,v2))"
But if using Read Uncommited isolation level I am not sure this UPDATE would actually lock both row until commit.
The problem is your mock need to implement the same isolation level as your real DB and support transaction ...
You could use SQLITE in memory DB to run your test but that would make your test a lot slower I assume.
If your app contain 10 distinct transactions.
you have to test what happen if 2 instances of tx #1 run concurrently.
But also if tx #1 and tx #2 run concurrently.
And also what if tx #1 and tx #3 run concurrently ....
But assuming you do not want to change the default isolation for your transaction or for the whole DB. How do you write unit-test that check your code will work correctly because it's using "select balance from accounts FOR UPDATE"?
It seem to me the only way to really validate this is using tool like TLA+. Or something like https://github.com/microsoft/coyote
Would GPT only with pretraining and no fine tuning be able to behave better when prompt is "let’s think step by step"?
Or this prompt only worked because a fine tuning dataset containing many "let’s think step by step" prompt was used?
-Spark do verify contract using static analysis and proof. -While Ada is not as memory safe as Rust it's a lot more memory safe than popular languages. -Its one of the easiest languages to get compliance with safety standard DO-178C or DO-333 ...
https://learn.microsoft.com/en-us/dotnet/framework/debug-tra...
https://learn.microsoft.com/en-us/azure/cosmos-db/postgresql...