Evals

[0x4007]

We need to make evals to benchmark accuracy

"Search for Braintrust AI"

[0x4007]

rfc @transitive-bullshit

[transitive-bullshit]

https://www.braintrust.dev

[Keyrxng]

ideal and looks op, just what I was talking about here ubiquity-os-marketplace/command-ask#32

[sshivaditya2019]

/start

[ubiquity-os-beta]

Warning

You have reached your max task limit. Please close out some tasks before assigning new ones.

[0x4007]

[!WARNING]
You have reached your max task limit. Please close out some tasks before assigning new ones.

This should list the tasks you're currently working on. I've seen it work before so perhaps it's broken

[ubiquity-os-beta]

A new workroom has been created for this task. Join chat

[ubiquity-os-beta]

Passed the deadline and no activity is detected, removing assignees: @sshivaditya2019.

[sshivaditya2019]

@0x4007, could you please assign me this issue? Also, could you add a time estimate? I think it should about a day.

[ubiquity-os-beta]

@sshivaditya2019 the deadline is at Sun, Dec 15, 1:18 AM UTC

[ubiquity-os-beta]

Important

• Be sure to link a pull-request before the first reminder to avoid disqualification.
• Reminders will be sent every 2 days and 8 hours if there is no activity.
• Assignees will be disqualified after 4 days and 16 hours of inactivity.

[sshivaditya2019]

@0x4007 @gentlementlegen, the linked PR has been merged, shouldn't the issue be closed as well?

[gentlementlegen]

@sshivaditya2019 technically it should but there was no closing event here somehow. Your pull-request targets command-ask and this issue references text-conversation-rewards how are these related?

[sshivaditya2019]

@sshivaditya2019 technically it should but there was no closing event here somehow. Your pull-request targets command-ask and this issue references text-conversation-rewards how are these related?

I think the issue was made in the wrong place. But that should not matter right ? I have previously merged PRs which had linked issue in a another repo.

[gentlementlegen]

It only works when you target the main branch of the repo where the issue is located I think?

@0x4007 I let you take action on this