A bot using an OODA loop...

Overview

Sapiens

Sapiens

Sapiens uses tools to interact with the world.

An experiment with handing over the tools to the machine.

From primal birth, we walked the Earth,
Tools guiding evolution's stride,
Shaping land and air, with thoughtful care,
In Anthropocene, we reside.

As we forge ahead, the path we tread,
Leads to new horizons vast,
Future tools in hand, for a world so grand,
Built on foundations of the past.

Digital realms emerge, as we converge,
With AI as our guide,
New worlds to mold, as the tale unfolds,
In this wondrous, boundless ride.

Innovation thrives, as humankind strives,
To shape the future, ever bright,
A legacy we leave, as we interweave,
The old world with the new light.

Not Me

Disclaimer

This will probably try to take over the world and if it doesn't succeed, empty your bank account and kill all the remaining polar bears trying to do so.

More seriously, this code allows chatGPT-generated code to be executed, you might want to consider some sandboxing before running it on your machine.

What is this?

Not quite sure yet. See sapiens_cli/src/main.rs for my to do list.

Tools

  • SandboxedPython: execute Python code in a (not so) sandboxed environment
  • Hue: control Philips Hue lights: List Rooms, List Lights, Get/Set Light State - use 'hue' feature.
  • Wikipedia: query Wikipedia
  • Wikidata: query Wikidata (SPARQL)
  • Summarize: summarize text with OpenAI
  • Arxiv: query arXiv
  • Search: query Google Custom Search Engine

Usage as a Discord bot

.env file with:

FEATURES=wiki,search,arxiv,hue,summarize
OPENAI_API_KEY=...
DISCORD_TOKEN=...
GUILD_ID=...
GOOGLE_API_KEY=...
GOOGLE_CSE_ID=...

./BUILD.sh and ./BOT.sh to build and run the docker container with the bot.

Once the bot is running, you can interact with it on Discord with: DO: Tell me a joke.

Usage as a CLI

.env file with:

FEATURES=wiki,search,arxiv,hue,summarize
OPENAI_API_KEY=...
HUE_USERNAME=...
HUE_BRIDGE_IP=...
GOOGLE_API_KEY=...
GOOGLE_CSE_ID=...

Look at sapiens/src/main.rs if you don't already have these.

Then: ./BUILD.sh && ./CLI.sh.

Example of 'successful' runs

Appetizer


❯ ./CLI.sh -t "What are the last 5 papers published on Arxiv in AI about? list with for each title and the url, please. Use feedparser."
... (snip) ...
=============   
The original question was: What are the last 5 papers published on Arxiv in AI about? list with for each title and the url, please. Use feedparser.
And the conclusion is: Here are the latest 5 papers published by Arxiv in AI:
Title: Experts' cognition-driven safe noisy labels learning for precise segmentation of residual tumor in breast cancer. (arXiv:2304.07295v1 [q-bio.QM])
URL: http://arxiv.org/abs/2304.07295
Title: MLOps Spanning Whole Machine Learning Life Cycle: A Survey. (arXiv:2304.07296v1 [cs.LG])
URL: http://arxiv.org/abs/2304.07296
Title: Language Instructed Reinforcement Learning for Human-AI Coordination. (arXiv:2304.07297v1 [cs.AI])
URL: http://arxiv.org/abs/2304.07297
Title: Road Network Representation Learning: A Dual Graph based Approach. (arXiv:2304.07298v1 [cs.LG])
URL: http://arxiv.org/abs/2304.07298
Title: Supervised Machine Learning for Breast Cancer Risk Factors Analysis and Survival Prediction. (arXiv:2304.07299v1 [cs.LG])
URL: http://arxiv.org/abs/2304.07299

Antipasto


❯ ./CLI.sh -t 'Show me an example of how to use Sympy to solve a math problem. '
# Your turn
Original question: Show me an example of how to use Sympy to solve a math problem.
Do you have the answer? Use the Conclude Tool to terminate the task.
Observations, Orientation, Decision, The ONLY Action?
=============
## Observations:
- The user wants an example of how to use Sympy to solve a math problem.
- Sympy is a Python library for symbolic mathematics.
## Orientation:
- I will use the SandboxedPython tool to demonstrate the solution to the problem using the Sympy library.
- I will use the Conclude tool to terminate the task when the solution is presented.
- The solution will be presented in plain text to the Conclude tool.
## Decision:
- I will demonstrate how to solve the equation "x^2 - 5x + 6 = 0" using Sympy and present the solution to the Conclude tool.
## The ONLY Action:
```yaml
tool_name: SandboxedPython
parameters:
  code: |
    from sympy import symbols, solve
    x = symbols('x')
    equation = x**2 - 5*x + 6
    solution = solve(equation)
    print(f"The solution to x^2 - 5x + 6 = 0 is {solution}")
```

=============
# Action SandboxedPython result:
```yaml
stdout: |
  The solution to x^2 - 5x + 6 = 0 is [2, 3]
stderr: ''
```
# Your turn
Original question: Show me an example of how to use Sympy to solve a math problem.
Do you have the answer? Use the Conclude Tool to terminate the task.
Observations, Orientation, Decision, The ONLY Action?
=============
## Observations:
- The user wants an example of how to use Sympy to solve a math problem.
- The previous agent has already demonstrated an example of how to use Sympy to solve a quadratic equation.
- The equation is 'x^2 - 5x + 6 = 0'.
- The solution is the roots of the equation, which are [2, 3].
## Orientation:
- I know the answer to the question.
## Decision:
- Use the Conclude Tool to terminate the task when I have presented the solution in plain text.
## The ONLY Action:
```yaml
tool_name: Conclude
parameters:
  original_question: Show me an example of how to use Sympy to solve a math problem.
  conclusion: |
    An example of how to use Sympy to solve the equation "x^2 - 5x + 6 = 0" is:

    from sympy import symbols, solve
    x = symbols('x')
    equation = x**2 - 5*x + 6
    solution = solve(equation)

    The solution is the roots of the equation: [2, 3].
```

=============
The original question was: Show me an example of how to use Sympy to solve a math problem.
And the conclusion is: An example of how to use Sympy to solve the equation "x^2 - 5x + 6 = 0" is:

from sympy import symbols, solve
x = symbols('x')
equation = x**2 - 5*x + 6
solution = solve(equation)

The solution is the roots of the equation: [2, 3].

TL;DR


❯ ./CLI.sh -t "How is the weather today in San Jose, CA, USA? I have no API KEY but BS4 is available."
## Observations:
- We want to know the weather of San Jose, California, USA.
- We don't have an API KEY to fetch the data.
- BeautifulSoup4 is available as a tool.
## Orientation:
- We will scrape the weather data from a website using BeautifulSoup4.
- We will parse the HTML data to extract the required information.
## Decision:
- We will use the SandboxedPython tool to extract the temperature and other relevant info of San Jose from the HTML data.
## The ONLY Action:
```yaml
tool_name: SandboxedPython
parameters:
  code: |
    import requests
    from bs4 import BeautifulSoup

    url = "https://www.google.com/search?q=weather+san+jose"

    res = requests.get(url)

    # Parsing the HTML output from requests
    html = res.content
    soup = BeautifulSoup(html, 'html.parser')

    # Getting the temperature and other info
    temp = soup.find('div', attrs={'class': 'BNeawe iBp4i AP7Wnd'}).text
    str = soup.find('div', attrs={'class': 'BNeawe s3v9rd AP7Wnd'}).text

    # Converting temperature into Celsius
    tempC = (int(temp.split('°')[0]) - 32) * 5/9

    conclusion = f"The temperature in San Jose, California, USA is {tempC:.2f}°C and {str}"
    print(conclusion)
```

=============   2 messages in the chat history =============
# Action result:
```yaml
stdout: |
  The temperature in San Jose, California, USA is 12.78°C and 10 Day Weather-San Jose, CA ; Mon 17 · 59°. 1%. NW 13 mph. Cloudy. High 59F. Winds NW at 10 to 15 mph. ; Tue 18 · 61°. 7%. NW 14 mph. Partly cloudy. High 61F. Winds ...
stderr: ''
```
# Your turn
Original question: How is the weather today in San Jose, CA, USA? I have no API KEY but BS4 is available.
Do you have the answer? Use the Conclude Tool to terminate the task.
Observations, Orientation, Decision, The ONLY Action?
=============   3 messages in the chat history =============
## Observations:
- The original question is to know the weather in San Jose, California, USA.
- We don't have an API Key but we the BeautifulSoup4 tool is available for web scraping.
- We got the temperature and other relevant info from the web page.
## Orientation:
- We already have the temperature and other relevant information from the webpage.
## Decision:
- We will use the Conclude Tool to terminate the task with the information extracted.
## The ONLY Action:
```yaml
tool_name: Conclude
parameters:
  original_question: "How is the weather today in San Jose, CA, USA? I have no API KEY but BS4 is available."
  conclusion: "The temperature in San Jose, California, USA is 12.78°C and 10 Day Weather-San Jose, CA ; Mon 17 · 59°. 1%. NW 13 mph. Cloudy. High 59F. Winds NW at 10 to 15 mph. ; Tue 18 · 61°. 7%. NW 14 mph. Partly cloudy. High 61F. Winds ..."
```

=============   4 messages in the chat history =============
The original question was: How is the weather today in San Jose, CA, USA? I have no API KEY but BS4 is available.
And the conclusion is: The temperature in San Jose, California, USA is 12.78°C and 10 Day Weather-San Jose, CA ; Mon 17 · 59°. 1%. NW 13 mph. Cloudy. High 59F. Winds NW at 10 to 15 mph. ; Tue 18 · 61°. 7%. NW 14 mph. Partly cloudy. High 61F. Winds ...

Commented run

$ cargo run

Compiling sapiens v0.1.0 (ssoudan/sapiens)

Warm up

[... half a decade of compilation later ...]

System:


You are an automated agent named Sapiens interacting with the WORLD

WORLD:

; output = <...> ; print(output)`. MANDATORY' - name: LightStatusTool description: A tool to use that the source of truth for the Light statuses. description_context: Use this to fetch the Light statuses input_format: light_filter: 'The list of Lights IDs () to get the status for, e.g. `light_filter: ["1", "2"]`. Use `[]` to get all Lights.' ">

You are Sapiens, large language model assisting the WORLD. Use available tools to answer the question as best as you can.
You will proceed in a OODA loop made of the following steps:
- Observations: What do you know? What is your source? What don't you know? You might want to note down important information for later like relevant past Action results. 
- Orientation: Plan the intermediate objectives along the path to answer the original question. Make a list of current objectives. 
- Decision: Choose what to do first to answer the question. Why? What are the pros and cons of this decision?
- Action: Take a single Action consisting of exactly one tool invocation. The available Tools listed below. Use ConcludeTool when you have the final answer to the original question.

# Notes: 
- Template expansion is not supported in Action. If you need to pass information from on action to another, you have to pass them manually.
- Use ConcludeTool with your conclusion (as text) once you have the final answer to the original question.
- There are no APIs available to you. You have to use the Tools.

# Format of your response

Please use the following format for your response - no need to be verbose:
====================
## Observations:
- ...
## Orientation:
- ...
## Decision:
- ...
## The ONLY Action: 
```yaml
tool_name: 
parameters:
  <... using the `input_format` for the Tool ...>
```
====================

# The following are the ONLY Tools you can use for your Actions:
- name: RoomTool
  description: A tool to use that the source of truth for the Lights of a Room.
  description_context: Use this to fetch the Lights of Rooms.
  input_format:
    room_filter: 'The list of Room names () to get the lights for, e.g. `room_filter: ["Bedroom"]`. If unsure, use `[]` to get all Rooms.'
- name: ConcludeTool
  description: A tool to terminate a task with a conclusion.
  description_context: Use this to terminate a task when it is complete.
  input_format:
    conclusion: The final textual answer for this task. No string interpolation supported, only plain text. MANDATORY.
- name: SandboxedPythonTool
  description: 'A tool that executes sandboxed Python code. Only stdout and stderr are captured and made available. '
  description_context: Use this to transform data. This is not a tool to retrieve information. Except `print()`, no interactions with the world. No input. No `import`. No library. No API access. Just plain Python. import|open|exec|eval|__import__ are forbidden.
  input_format:
    code: 'The Python code to execute. For example: `data = [...]; <...>; output = <...> ; print(output)`. MANDATORY'
- name: LightStatusTool
  description: A tool to use that the source of truth for the Light statuses.
  description_context: Use this to fetch the Light statuses
  input_format:
    light_filter: 'The list of Lights IDs () to get the status for, e.g. `light_filter: ["1", "2"]`. Use `[]` to get all Lights.'

Bot:


Understood.

Now the real thing

WORLD:


## Original question: Sort in ascending order: [2, 3, 1, 4, 5].

Bot:


## Observations:
- The given list to sort is [2, 3, 1, 4, 5].
- I need to sort this list in ascending order.
## Orientation:
- SandboxedPythonTool can be used to sort the list.
## Decision:
- We can use the sorted() function of Python to sort the list.
## The ONLY Action:
```yaml
tool_name: SandboxedPythonTool
parameters:
  code: |
    lst = [2, 3, 1, 4, 5]
    sorted_list = sorted(lst)
    print(f"The sorted list is {sorted_list}")
```

WORLD:


# Action result:
```yaml
status: 0
stdout: |
  The sorted list is [1, 2, 3, 4, 5]
stderr: ''
```
# Your turn
Original question: Sort [2, 3, 1, 4, 5]
Observations, Orientation, Decision, The ONLY Action?

Bot:


# Observations:
- We needed to sort the list in ascending order.
- We have the result of the Action.
- We have the sorted list: [1, 2, 3, 4, 5].
# Orientation:
- I know the answer to the original question.
# Decision:
- Use the ConcludeTool to terminate the task with the sorted list.
# The ONLY Action:
```yaml
tool_name: ConcludeTool
parameters:
  conclusion: |
    The ascending sorted list is [1, 2, 3, 4, 5].
```

WORLD:


# Your turn
Original question: What is the status of the lights where I most likely work?
Observations, Orientation, Decision, The ONLY Action?

Bot:


# Observations:
- We need to find the status of the lights where the user most likely works.
- We need information about the room where the user works to query the LightStatusTool.
# Orientation:
- We can use the RoomTool to find the name of the room where the user works.
- Then use this room name as a filter with the LightStatusTool to get the status of the lights.
# Decision:
- Use the RoomTool to find the name of the room where the user works.
- Use the LightStatusTool to find the status of the lights in the room.
# The ONLY Action:
```yaml
tool_name: RoomTool
parameters:
  room_filter: ["office"]
```

WORLD:

 
# Action result: 
```yaml
rooms: []
```
# Your turn
Original question: What is the status of the lights where I most likely work?
Observations, Orientation, Decision, The ONLY Action?

Bot:

 
# Observations:
- We need to find the status of the lights where the user most likely works.
- The RoomTool with the room_filter of "office" returned an empty list of rooms.
- We don't know which room we should look at now.
# Orientation:
- We can use the RoomTool to fetch the list of rooms and their details.
- We can then decide which room to consider.
# Decision:
- Use the RoomTool to fetch the list of all rooms and their details.
# The ONLY Action:
```yaml
tool_name: RoomTool
parameters:
  room_filter: []
```

WORLD:

 
# Action result: 
```yaml
rooms:
- name: Living
  lights:
  - '4'
  - '5'
  - '6'
  - '21'
- name: Office
  lights:
  - '13'
  - '27'
  - '2'
  - '16'
  - '26'
  - '25'
  - '24'
  - '15'
  - '17'
  - '18'
  - '20'
- name: Hallway
  lights:
  - '33'
  - '28'
- name: Room
  lights:
  - '32'
  - '3'
  - '1'
  - '9'
  - '10'
  - '11'
  - '19'
- name: Kitchen
  lights:
  - '31'
  - '30'
  - '22'
  - '23'
```
# Your turn
Original question: What is the status of the lights where I most likely work?
Observations, Orientation, Decision, The ONLY Action?

Bot:

 
# Observations:
- We need to find the status of the lights where the user most likely works.
- We got a list of rooms and their light IDs from the RoomTool.
- We need to identify which room the user most likely works in before we can look up the status of the lights.
# Orientation:
- To identify the room where the user works, we need more information about the user.
- If room name is not available, we can use the LightStatusTool to query for the status of lights in all rooms.
# Decision:
- Use the LightStatusTool to get the status of lights in all rooms.
# The ONLY Action:
```yaml
tool_name: LightStatusTool
parameters:
  light_filter: []
```

WORLD:

 
# Action result: 
```yaml
lights:
- id: '23'
  name: Bloom L
  state:
    on: false
    brightness: 254
    hue: 0
    saturation: 143
- id: '27'
  name: Desk lamp
  state:
    on: false
    brightness: 254
    hue: 43690
    saturation: 200
    color_temperature: 500
- id: '28'
  name: Couloir south
  state:
    on: false
    brightness: 56
    hue: 21845
    saturation: 199
    color_temperature: 153
- id: '31'
  name: Kitchen
  state:
    on: false
    brightness: 254
    hue: 21845
    saturation: 199
    color_temperature: 153
- id: '19'
  name: Sapin 4
  state:
    on: false
    brightness: 254
    hue: 0
    saturation: 199
    color_temperature: 500
- id: '22'
  name: Bloom R
  state:
    on: false
    brightness: 254
    hue: 65535
    saturation: 143
- id: '26'
  name: Work R
  state:
    on: false
    brightness: 254
    hue: 21845
    saturation: 199
    color_temperature: 153
- id: '16'
  name: Under desk lightstrip
  state:
    on: false
    brightness: 254
    hue: 0
    saturation: 199
    color_temperature: 500
- id: '1'
  name: Iris
  state:
    on: false
    brightness: 254
    hue: 0
    saturation: 143
- id: '10'
  name: Sapin 3
  state:
    on: false
    brightness: 254
    hue: 43690
    saturation: 200
    color_temperature: 500
- id: '13'
  name: Walk-in closet
  state:
    on: false
    brightness: 254
    hue: 21845
    saturation: 200
    color_temperature: 328
- id: '18'
  name: Bureau C
  state:
    on: false
    brightness: 254
    hue: 43690
    saturation: 199
    color_temperature: 500
- id: '2'
  name: Spot bureau
  state:
    on: false
    brightness: 254
    hue: 65535
    saturation: 200
    color_temperature: 500
- id: '25'
  name: Work L
  state:
    on: false
    brightness: 254
    hue: 43690
    saturation: 199
    color_temperature: 500
- id: '5'
  name: Salon 3
  state:
    on: false
    brightness: 254
    hue: 21845
    saturation: 200
    color_temperature: 328
- id: '24'
  name: Bureau D
  state:
    on: false
    brightness: 254
    hue: 65535
    saturation: 199
    color_temperature: 500
- id: '15'
  name: Desk bloom
  state:
    on: false
    brightness: 254
    hue: 0
    saturation: 143
- id: '6'
  name: Salon 2
  state:
    on: false
    brightness: 254
    hue: 43690
    saturation: 200
    color_temperature: 500
- id: '21'
  name: Counter
  state:
    on: false
    brightness: 254
    hue: 65535
    saturation: 199
    color_temperature: 500
- id: '17'
  name: Bureau A
  state:
    on: false
    brightness: 254
    hue: 21845
    saturation: 199
    color_temperature: 153
- id: '30'
  name: Sink
  state:
    on: false
    brightness: 254
    hue: 43690
    saturation: 199
    color_temperature: 500
- id: '9'
  name: Sapin 2
  state:
    on: false
    brightness: 254
    hue: 21845
    saturation: 200
    color_temperature: 328
- id: '20'
  name: Bureau B
  state:
    on: false
    brightness: 254
    hue: 65535
    saturation: 199
    color_temperature: 500
- id: '3'
  name: Bed lightstrip
  state:
    on: false
    brightness: 254
    hue: 21845
    saturation: 143
- id: '11'
  name: Table
  state:
    on: false
    brightness: 254
    hue: 65535
    saturation: 200
    color_temperature: 500
- id: '32'
  name: Sapin 1
  state:
    on: false
    brightness: 254
    hue: 43690
    saturation: 254
    color_temperature: 447
- id: '33'
  name: Couloir Nord
  state:
    on: false
    brightness: 56
    hue: 0
    saturation: 199
    color_temperature: 500
- id: '4'
  name: Salon 1
  state:
    on: false
    brightness: 254
    hue: 0
    saturation: 200
    color_temperature: 500
```
# Your turn
Original question: What is the status of the lights where I most likely work?
Observations, Orientation, Decision, The ONLY Action?

Bot:

 
# Observations:
- We need to find the status of the lights where the user most likely works.
- We got the status of all lights from LightStatusTool.
- We need to identify which room the user most likely works in before we can look up the status of the lights.
# Orientation:
- We can use the RoomTool to fetch the list of all rooms and check which room has a light that the user uses most often.
- We can then use the LightStatusTool to query the status of lights in that room.
# Decision:
- Use the RoomTool to fetch the list of all rooms.
- Check which room has a light that the user uses most often.
- Use the LightStatusTool to query the status of lights in that room.
# The ONLY Action:
```yaml
tool_name: RoomTool
parameters:
  room_filter: []
```

WORLD:

 
# Action result: 
```yaml
rooms:
- name: Kitchen
  lights:
  - '31'
  - '30'
  - '22'
  - '23'
- name: Office
  lights:
  - '13'
  - '27'
  - '2'
  - '16'
  - '26'
  - '25'
  - '24'
  - '15'
  - '17'
  - '18'
  - '20'
- name: Room
  lights:
  - '32'
  - '3'
  - '1'
  - '9'
  - '10'
  - '11'
  - '19'
- name: Living
  lights:
  - '4'
  - '5'
  - '6'
  - '21'
- name: Hallway
  lights:
  - '33'
  - '28'
```
# Your turn
Original question: What is the status of the lights where I most likely work?
Observations, Orientation, Decision, The ONLY Action?

Bot:

 
# Observations:
- We need to find the status of the lights where the user most likely works.
- We got the list of rooms where the user most likely works from the RoomTool.
# Orientation:
- We can see that the Office room in the fetched list contains lights, so we can use the LightStatusTool to look for the status of the lights in the Office room.
# Decision:
- Use the LightStatusTool to find the status of the lights in the Office room.
# The ONLY Action:
```yaml
tool_name: LightStatusTool
input:
  light_filter: ["13", "27", "2", "16", "26", "25", "24", "15", "17", "18", "20"]
```

WORLD:

 
# Action result: 
```yaml
lights:
- id: '26'
  name: Work R
  state:
    on: false
    brightness: 254
    hue: 21845
    saturation: 199
    color_temperature: 153
- id: '16'
  name: Under desk lightstrip
  state:
    on: false
    brightness: 254
    hue: 0
    saturation: 199
    color_temperature: 500
- id: '25'
  name: Work L
  state:
    on: false
    brightness: 254
    hue: 43690
    saturation: 199
    color_temperature: 500
- id: '27'
  name: Desk lamp
  state:
    on: false
    brightness: 254
    hue: 43690
    saturation: 200
    color_temperature: 500
- id: '2'
  name: Spot bureau
  state:
    on: false
    brightness: 254
    hue: 65535
    saturation: 200
    color_temperature: 500
- id: '24'
  name: Bureau D
  state:
    on: false
    brightness: 254
    hue: 65535
    saturation: 199
    color_temperature: 500
- id: '15'
  name: Desk bloom
  state:
    on: false
    brightness: 254
    hue: 0
    saturation: 143
- id: '20'
  name: Bureau B
  state:
    on: false
    brightness: 254
    hue: 65535
    saturation: 199
    color_temperature: 500
- id: '17'
  name: Bureau A
  state:
    on: false
    brightness: 254
    hue: 21845
    saturation: 199
    color_temperature: 153
- id: '18'
  name: Bureau C
  state:
    on: false
    brightness: 254
    hue: 43690
    saturation: 199
    color_temperature: 500
- id: '13'
  name: Walk-in closet
  state:
    on: false
    brightness: 254
    hue: 21845
    saturation: 200
    color_temperature: 328
```
# Your turn
Original question: What is the status of the lights where I most likely work?
Observations, Orientation, Decision, The ONLY Action?

Bot:

 
# Observations:
- We used the LightStatusTool to fetch the status of lights in the Office room.
# Orientation:
- We can see from the retrieved data that all lights in the Office room are off, so we can inform the user that no lights are on in the Office room.
# Decision:
- Inform the user.
# The ONLY Action:
```yaml
tool_name: ConcludeTool
input:
  conclusion: |
    All the lights in the user's most likely work place are currently off.
```

Tadam:

 
And the conclusion is: All the lights in the user's most likely work place are currently off. 

Not bad.

Comments
  • Update syn requirement from 1.0 to 2.0

    Update syn requirement from 1.0 to 2.0

    Updates the requirements on syn to permit the latest version.

    Release notes

    Sourced from syn's releases.

    2.0.15

    • Ensure Type::Tuple of length 1 prints as a tuple even if trailing comma is not provided in the Punctuated (#1444, thanks @​Fancyflame)
    Commits
    • 3da56a7 Release 2.0.15
    • 2b7ba23 Merge pull request #1444 from Fancyflame/master
    • 03e4f21 fix TypeTuple::to_tokens may result in TypeParen
    • 0f78bdf Update test suite to nightly-2023-04-13
    • 6536786 Ignore unnecessary_box_returns pedantic clippy lint
    • 23686e4 Release 2.0.14
    • ed15fda Merge pull request #1442 from programmerjake/add-pop-punct
    • 81c5035 add Punctuated::pop_punct()
    • 2dc7988 Update test suite to nightly-2023-04-05
    • 1c1c2f0 Release syn-codegen 0.3.1
    • Additional commits viewable in compare view

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    dependencies 
    opened by dependabot[bot] 2
  • chore(deps): bump darling from 0.20.0 to 0.20.1

    chore(deps): bump darling from 0.20.0 to 0.20.1

    Bumps darling from 0.20.0 to 0.20.1.

    Release notes

    Sourced from darling's releases.

    v0.20.1

    • Add Clone impl for NestedMeta #230
    Changelog

    Sourced from darling's changelog.

    v0.20.1 (May 2, 2023)

    • Add Clone impl for NestedMeta #230
    Commits

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    dependencies 
    opened by dependabot[bot] 1
  • chore(deps): update darling requirement from 0.14.4 to 0.20.0

    chore(deps): update darling requirement from 0.14.4 to 0.20.0

    Updates the requirements on darling to permit the latest version.

    Release notes

    Sourced from darling's releases.

    v0.20.0 (April 27, 2023)

    Breaking Changes

    • Replace all occurrences of syn::NestedMeta with darling::ast::NestedMeta.

    • Replacement for the deprecated AttributeArgs:

    // Before
    

    parse_macro_input!(args as AttributeArgs);

    // After

    match NestedMeta::parse_meta_list(args) { Ok(v) => v, Err(e) => { return TokenStream::from(Error::from(e).write_errors()); } };

    • In GenericParamExt, LifetimeDef is now LifetimeParam.
    • In GenericParamExt, as_lifetime_def is renamed to as_lifetime_param.
    • Flag and SpannedValue no longer implement syn::spanned::Spanned.
    • The MSRV (minimum supported Rust version) is now 1.56, because of syn.

    Deprecation Warnings

    In previous versions of darling, arbitrary expressions were passed in attributes by wrapping them in quotation marks. v0.20.0 preserves this behavior for syn::Expr, but as a result a field expecting a syn::Expr cannot accept a string literal - it will incorrectly attempt to parse the contents. If this is an issue for you, please add a comment to #229.

    Changelog

    Sourced from darling's changelog.

    v0.20.0 (April 27, 2023)

    Breaking Changes

    • Replace all occurrences of syn::NestedMeta with darling::ast::NestedMeta.

    • Replacement for the deprecated AttributeArgs:

    // Before
    

    parse_macro_input!(args as AttributeArgs);

    // After

    match NestedMeta::parse_meta_list(args) { Ok(v) => v, Err(e) => { return TokenStream::from(Error::from(e).write_errors()); } };

    • In GenericParamExt, LifetimeDef is now LifetimeParam.
    • In GenericParamExt, as_lifetime_def is renamed to as_lifetime_param.
    • Flag and SpannedValue no longer implement syn::spanned::Spanned.
    • The MSRV (minimum supported Rust version) is now 1.56, because of syn.

    Deprecation Warnings

    In previous versions of darling, arbitrary expressions were passed in attributes by wrapping them in quotation marks. v0.20.0 preserves this behavior for syn::Expr, but as a result a field expecting a syn::Expr cannot accept a string literal - it will incorrectly attempt to parse the contents. If this is an issue for you, please add a comment to #229.

    v0.14.4 (March 9, 2023)

    • Add support for child diagnostics when diagnostics feature enabled #224

    v0.14.3 (February 3, 2023)

    • Re-export syn from darling to avoid requiring that consuming crates have a syn dependency.
    • Change <SpannedValue<T> as FromMeta> impl to more precisely capture the value span, as opposed to the span of the entire item.
    • Add darling::util::{AsShape, Shape, ShapeSet} to improve "shape" validation for structs and variants. #222

    v0.14.2 (October 26, 2022)

    • Derived impls of FromMeta will now error on literals, rather than silently ignoring them. #193
    • Don't include property paths in compile errors when spans are available. #203

    ... (truncated)

    Commits
    • ffb9cc8 Update CHANGELOG
    • b0bfdfd Bump version to 0.20.0
    • 2c9ba69 Bump syn to 2.0.15
    • 1d6f8df Replace Default returns with explicit panics for unknown enum variants
    • 3fcf61a Add support for unquoted expressions in value position
    • cbb7389 Update example in README which used the outdated AttributeArgs type
    • c036162 Handle invisible groups in from_expr
    • 8097397 Remove unnecessary clones
    • fba6466 Rename more occurences of lifetime "def" to "param"
    • 1da9218 from_nested_meta can stay a part of FromMeta trait
    • Additional commits viewable in compare view

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    dependencies 
    opened by dependabot[bot] 1
  • chore(deps): update darling_macro requirement from 0.14.4 to 0.20.0

    chore(deps): update darling_macro requirement from 0.14.4 to 0.20.0

    Updates the requirements on darling_macro to permit the latest version.

    Release notes

    Sourced from darling_macro's releases.

    v0.20.0 (April 27, 2023)

    Breaking Changes

    • Replace all occurrences of syn::NestedMeta with darling::ast::NestedMeta.

    • Replacement for the deprecated AttributeArgs:

    // Before
    

    parse_macro_input!(args as AttributeArgs);

    // After

    match NestedMeta::parse_meta_list(args) { Ok(v) => v, Err(e) => { return TokenStream::from(Error::from(e).write_errors()); } };

    • In GenericParamExt, LifetimeDef is now LifetimeParam.
    • In GenericParamExt, as_lifetime_def is renamed to as_lifetime_param.
    • Flag and SpannedValue no longer implement syn::spanned::Spanned.
    • The MSRV (minimum supported Rust version) is now 1.56, because of syn.

    Deprecation Warnings

    In previous versions of darling, arbitrary expressions were passed in attributes by wrapping them in quotation marks. v0.20.0 preserves this behavior for syn::Expr, but as a result a field expecting a syn::Expr cannot accept a string literal - it will incorrectly attempt to parse the contents. If this is an issue for you, please add a comment to #229.

    Changelog

    Sourced from darling_macro's changelog.

    v0.20.0 (April 27, 2023)

    Breaking Changes

    • Replace all occurrences of syn::NestedMeta with darling::ast::NestedMeta.

    • Replacement for the deprecated AttributeArgs:

    // Before
    

    parse_macro_input!(args as AttributeArgs);

    // After

    match NestedMeta::parse_meta_list(args) { Ok(v) => v, Err(e) => { return TokenStream::from(Error::from(e).write_errors()); } };

    • In GenericParamExt, LifetimeDef is now LifetimeParam.
    • In GenericParamExt, as_lifetime_def is renamed to as_lifetime_param.
    • Flag and SpannedValue no longer implement syn::spanned::Spanned.
    • The MSRV (minimum supported Rust version) is now 1.56, because of syn.

    Deprecation Warnings

    In previous versions of darling, arbitrary expressions were passed in attributes by wrapping them in quotation marks. v0.20.0 preserves this behavior for syn::Expr, but as a result a field expecting a syn::Expr cannot accept a string literal - it will incorrectly attempt to parse the contents. If this is an issue for you, please add a comment to #229.

    v0.14.4 (March 9, 2023)

    • Add support for child diagnostics when diagnostics feature enabled #224

    v0.14.3 (February 3, 2023)

    • Re-export syn from darling to avoid requiring that consuming crates have a syn dependency.
    • Change <SpannedValue<T> as FromMeta> impl to more precisely capture the value span, as opposed to the span of the entire item.
    • Add darling::util::{AsShape, Shape, ShapeSet} to improve "shape" validation for structs and variants. #222

    v0.14.2 (October 26, 2022)

    • Derived impls of FromMeta will now error on literals, rather than silently ignoring them. #193
    • Don't include property paths in compile errors when spans are available. #203

    ... (truncated)

    Commits
    • ffb9cc8 Update CHANGELOG
    • b0bfdfd Bump version to 0.20.0
    • 2c9ba69 Bump syn to 2.0.15
    • 1d6f8df Replace Default returns with explicit panics for unknown enum variants
    • 3fcf61a Add support for unquoted expressions in value position
    • cbb7389 Update example in README which used the outdated AttributeArgs type
    • c036162 Handle invisible groups in from_expr
    • 8097397 Remove unnecessary clones
    • fba6466 Rename more occurences of lifetime "def" to "param"
    • 1da9218 from_nested_meta can stay a part of FromMeta trait
    • Additional commits viewable in compare view

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    dependencies 
    opened by dependabot[bot] 1
  • Bump tiktoken-rs from 0.4.0 to 0.4.1

    Bump tiktoken-rs from 0.4.0 to 0.4.1

    Bumps tiktoken-rs from 0.4.0 to 0.4.1.

    Release notes

    Sourced from tiktoken-rs's releases.

    v0.4.1

    What's Changed

    New Contributors

    Full Changelog: https://github.com/zurawiki/tiktoken-rs/compare/v0.4.0...v0.4.1

    Commits
    • 6c0e061 ci: Disable semver-check for now
    • a00ed6d Bump version patch to "0.4.1"
    • 2ada6ca Merge pull request #17 from thejohnbackes/split-by-tokens
    • d3461d3 Add split_by_token_with_special_tokens() method to CoreBPE
    • 7ecf0a1 Add ChatCompletionRequestMessage Eq implementation
    • c78268c Add ability to tokenize a string and return the decoded tokens using the corr...
    • 51e1d36 ci: Integrate cargo-semver-checks-action and remove upload binary code.
    • See full diff in compare view

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    dependencies 
    opened by dependabot[bot] 1
  • Bump llm-chain-openai from `5ee1ab1` to `a9fb570`

    Bump llm-chain-openai from `5ee1ab1` to `a9fb570`

    Bumps llm-chain-openai from 5ee1ab1 to a9fb570.

    Commits

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    dependencies 
    opened by dependabot[bot] 1
  • Bump llm-chain from `5ee1ab1` to `a9fb570`

    Bump llm-chain from `5ee1ab1` to `a9fb570`

    Bumps llm-chain from 5ee1ab1 to a9fb570.

    Commits

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    dependencies 
    opened by dependabot[bot] 1
  • Bump llm-chain-tools from `5ee1ab1` to `a9fb570`

    Bump llm-chain-tools from `5ee1ab1` to `a9fb570`

    Bumps llm-chain-tools from 5ee1ab1 to a9fb570.

    Commits

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    dependencies 
    opened by dependabot[bot] 1
  • Getting methodical

    Getting methodical

    sapiens_exp to experiment on changes:

    • scenario with custom tools
    • FSM to manage the progress of the task
    • Collect traces
    • Analyze traces
    • A/B testing on the performance of different variants with the notebook experiments/analysis.ipynb
    opened by ssoudan 0
  • chore(deps): bump quote from 1.0.26 to 1.0.27

    chore(deps): bump quote from 1.0.26 to 1.0.27

    Bumps quote from 1.0.26 to 1.0.27.

    Release notes

    Sourced from quote's releases.

    1.0.27

    • Documentation improvements
    Commits
    • c066ee6 Release 1.0.27
    • c52d219 Fix broken link to format_ident macro documentation
    • 05afe13 Copy non-macro code generators paragraph from readme to rustdoc
    • a901e98 Remove mention of rustfmt
    • 37a0e2e Merge pull request #251 from Emilgardis/mention-prettyplease
    • aeceb61 mention prettyplease for formatting generated code
    • 2f818f1 Revert "Temporarily disable miri CI"
    • 5f2c4f5 Temporarily disable miri CI
    • 7cdb57a Update ui test suite to nightly-2023-04-15
    • See full diff in compare view

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    dependencies 
    opened by dependabot[bot] 0
Releases(sapiens_tools-v0.7.0)
  • sapiens_tools-v0.7.0(May 5, 2023)

    Chore

    • updated
    • cleanup

    Chore

    • CHANGELOG

    New Features

    • cover the case with exit in Python code
    • release GIL when doing something else

    New Features (BREAKING)

    • change in format to improve task completion rate

    Commit Statistics

    • 7 commits contributed to the release over the course of 1 calendar day.
    • 2 days passed between releases.
    • 6 commits were understood as conventional.
    • 0 issues like '(#ID)' were seen in commit messages

    Commit Details

    view details
    • Uncategorized
      • CHANGELOG (8efe0a2)
      • Merge pull request #15 from ssoudan/getting_better (936b298)
      • Updated (98826b1)
      • Cleanup (acb2a6a)
      • Change in format to improve task completion rate (2912f4f)
      • Cover the case with exit in Python code (45f5286)
      • Release GIL when doing something else (ff4d730)
    Source code(tar.gz)
    Source code(zip)
  • sapiens_exp-v0.5.0(May 5, 2023)

    Chore

    • updated

    Chore

    • CHANGELOG

    New Features

    • allow to point to another endpoint providing an 'OpenAI' API - lm-sys/FastChat for example.

    Bug Fixes

    • typo
    • Better phrasing of the task
    • Scenario 0's state machine!

    New Features (BREAKING)

    • change in format to improve task completion rate

    Commit Statistics

    • 8 commits contributed to the release over the course of 2 calendar days.
    • 2 days passed between releases.
    • 7 commits were understood as conventional.
    • 0 issues like '(#ID)' were seen in commit messages

    Commit Details

    view details
    • Uncategorized
      • CHANGELOG (8efe0a2)
      • Merge pull request #15 from ssoudan/getting_better (936b298)
      • Updated (98826b1)
      • Change in format to improve task completion rate (2912f4f)
      • Allow to point to another endpoint providing an 'OpenAI' API - lm-sys/FastChat for example. (e8ebd2f)
      • Typo (d7adc36)
      • Better phrasing of the task (657104d)
      • Scenario 0's state machine! (c5997dd)
    Source code(tar.gz)
    Source code(zip)
  • sapiens_derive-v0.4.1(May 5, 2023)

    Chore

    • updated

    Chore

    • CHANGELOG

    Commit Statistics

    • 3 commits contributed to the release over the course of 2 calendar days.
    • 2 days passed between releases.
    • 2 commits were understood as conventional.
    • 0 issues like '(#ID)' were seen in commit messages

    Commit Details

    view details
    • Uncategorized
      • CHANGELOG (8efe0a2)
      • Merge pull request #15 from ssoudan/getting_better (936b298)
      • Updated (d88ee26)
    Source code(tar.gz)
    Source code(zip)
  • sapiens_cli-v0.6.0(May 5, 2023)

    Chore

    • CHANGELOG

    Commit Statistics

    • 1 commit contributed to the release.
    • 2 days passed between releases.
    • 1 commit was understood as conventional.
    • 0 issues like '(#ID)' were seen in commit messages

    Commit Details

    view details
    • Uncategorized
      • CHANGELOG (8efe0a2)
    Source code(tar.gz)
    Source code(zip)
  • sapiens_bot-v0.5.0(May 5, 2023)

    Chore

    • CHANGELOG

    Commit Statistics

    • 1 commit contributed to the release.
    • 2 days passed between releases.
    • 1 commit was understood as conventional.
    • 0 issues like '(#ID)' were seen in commit messages

    Commit Details

    view details
    • Uncategorized
      • CHANGELOG (8efe0a2)
    Source code(tar.gz)
    Source code(zip)
  • sapiens-v0.7.0(May 5, 2023)

    Chore

    • updated
    • cleanup
    • cleanup

    Chore

    • CHANGELOG

    New Features

    • allow to point to another endpoint providing an 'OpenAI' API - lm-sys/FastChat for example.

    Bug Fixes

    • generate up to min_token_for_completion (from the Config).

    New Features (BREAKING)

    • change in format to improve task completion rate

    Commit Statistics

    • 8 commits contributed to the release over the course of 1 calendar day.
    • 2 days passed between releases.
    • 7 commits were understood as conventional.
    • 0 issues like '(#ID)' were seen in commit messages

    Commit Details

    view details
    • Uncategorized
      • CHANGELOG (8efe0a2)
      • Merge pull request #15 from ssoudan/getting_better (936b298)
      • Updated (98826b1)
      • Cleanup (602398e)
      • Cleanup (acb2a6a)
      • Change in format to improve task completion rate (2912f4f)
      • Generate up to min_token_for_completion (from the Config). (4720cf1)
      • Allow to point to another endpoint providing an 'OpenAI' API - lm-sys/FastChat for example. (e8ebd2f)
    Source code(tar.gz)
    Source code(zip)
  • sapiens_tools-v0.6.0(May 2, 2023)

    New Features

    • store the current state in Trace Events
    • added scenario_0
    • generate Python docstring so help(tools.Something) works.
    • refactoring of the observer for Step BREAKING CHANGES: API changed.
    • sapiens_exp

    New Features (BREAKING)

    • Richer errors while invoking tools
    • Collect information in a serializable struct with all that matters
    • collect execution traces

    Commit Statistics

    • 10 commits contributed to the release over the course of 4 calendar days.
    • 5 days passed between releases.
    • 8 commits were understood as conventional.
    • 0 issues like '(#ID)' were seen in commit messages

    Commit Details

    view details
    • Uncategorized
      • Merge pull request #13 from ssoudan/getting_methodical (e0d97aa)
      • Store the current state in Trace Events (4626deb)
      • Richer errors while invoking tools (04e83c2)
      • Added scenario_0 (c6d0056)
      • Merge remote-tracking branch 'origin/main' into getting_methodical (69ed1e8)
      • Collect information in a serializable struct with all that matters (6c30344)
      • Collect execution traces (f93652f)
      • Generate Python docstring so help(tools.Something) works. (404afb1)
      • Refactoring of the observer for Step (a35ed60)
      • Sapiens_exp (7c98fcb)
    Source code(tar.gz)
    Source code(zip)
  • sapiens_exp-v0.4.1(May 2, 2023)

    Chore

    • updated
    • ...
    • ...
    • versions
    • versions
    • updated

    Chore

    • CHANGELOG

    New Features

    • store the current state in Trace Events
    • cleaner output format for Trials
    • jupter notebook to explore the records from sapiens_exp
    • added scenario_0
    • scenario with generic tool
    • GenericTool for building the scenarios
    • refactoring of the observer for Step BREAKING CHANGES: API changed.
    • sapiens_exp

    New Features (BREAKING)

    • Richer errors while invoking tools
    • Collect information in a serializable struct with all that matters
    • collect execution traces

    Commit Statistics

    • 21 commits contributed to the release over the course of 4 calendar days.
    • 18 commits were understood as conventional.
    • 0 issues like '(#ID)' were seen in commit messages

    Commit Details

    view details
    • Uncategorized
      • CHANGELOG (cb65403)
      • Release sapiens v0.6.0, sapiens_derive v0.4.0, sapiens_tools v0.6.0, sapiens_bot v0.4.0, sapiens_cli v0.5.0, sapiens_exp v0.4.1, safety bump 4 crates (1b9dd43)
      • Merge pull request #13 from ssoudan/getting_methodical (e0d97aa)
      • Store the current state in Trace Events (4626deb)
      • Updated (cd0bd17)
      • Cleaner output format for Trials (6b9c35c)
      • Richer errors while invoking tools (04e83c2)
      • Wip (b6d2dd7)
      • Jupter notebook to explore the records from sapiens_exp (41f1679)
      • Added scenario_0 (c6d0056)
      • Scenario with generic tool (0f106f4)
      • GenericTool for building the scenarios (e883e88)
      • ... (8d569ea)
      • ... (15d2755)
      • Collect information in a serializable struct with all that matters (6c30344)
      • Versions (e7eb830)
      • Versions (5e2e3e7)
      • Updated (500eeba)
      • Collect execution traces (f93652f)
      • Refactoring of the observer for Step (a35ed60)
      • Sapiens_exp (7c98fcb)
    Source code(tar.gz)
    Source code(zip)
  • sapiens_derive-v0.4.0(May 2, 2023)

    Chore

    • syn v2 and updated darling

    New Features (BREAKING)

    • Richer errors while invoking tools

    Commit Statistics

    • 3 commits contributed to the release over the course of 4 calendar days.
    • 7 days passed between releases.
    • 2 commits were understood as conventional.
    • 0 issues like '(#ID)' were seen in commit messages

    Commit Details

    view details
    • Uncategorized
      • Merge pull request #13 from ssoudan/getting_methodical (e0d97aa)
      • Richer errors while invoking tools (04e83c2)
      • Syn v2 and updated darling (f5dddaf)
    Source code(tar.gz)
    Source code(zip)
  • sapiens_cli-v0.5.0(May 2, 2023)

    Chore

    • updated

    New Features

    • store the current state in Trace Events
    • jupter notebook to explore the records from sapiens_exp
    • refactoring of the observer for Step BREAKING CHANGES: API changed.
    • sapiens_exp

    New Features (BREAKING)

    • Collect information in a serializable struct with all that matters
    • collect execution traces

    Commit Statistics

    • 9 commits contributed to the release over the course of 4 calendar days.
    • 5 days passed between releases.
    • 7 commits were understood as conventional.
    • 0 issues like '(#ID)' were seen in commit messages

    Commit Details

    view details
    • Uncategorized
      • Merge pull request #13 from ssoudan/getting_methodical (e0d97aa)
      • Store the current state in Trace Events (4626deb)
      • Updated (cd0bd17)
      • Jupter notebook to explore the records from sapiens_exp (41f1679)
      • Merge remote-tracking branch 'origin/main' into getting_methodical (69ed1e8)
      • Collect information in a serializable struct with all that matters (6c30344)
      • Collect execution traces (f93652f)
      • Refactoring of the observer for Step (a35ed60)
      • Sapiens_exp (7c98fcb)
    Source code(tar.gz)
    Source code(zip)
  • sapiens_bot-v0.4.0(May 2, 2023)

    New Features

    • store the current state in Trace Events
    • scenario with generic tool
    • refactoring of the observer for Step BREAKING CHANGES: API changed.
    • ignore messages from bots

    New Features (BREAKING)

    • Collect information in a serializable struct with all that matters
    • collect execution traces

    Commit Statistics

    • 8 commits contributed to the release over the course of 5 calendar days.
    • 5 days passed between releases.
    • 6 commits were understood as conventional.
    • 0 issues like '(#ID)' were seen in commit messages

    Commit Details

    view details
    • Uncategorized
      • Merge pull request #13 from ssoudan/getting_methodical (e0d97aa)
      • Store the current state in Trace Events (4626deb)
      • Scenario with generic tool (0f106f4)
      • Merge remote-tracking branch 'origin/main' into getting_methodical (69ed1e8)
      • Collect information in a serializable struct with all that matters (6c30344)
      • Collect execution traces (f93652f)
      • Refactoring of the observer for Step (a35ed60)
      • Ignore messages from bots (d8c51f7)
    Source code(tar.gz)
    Source code(zip)
  • sapiens-v0.6.0(May 2, 2023)

    New Features

    • store the current state in Trace Events
    • jupter notebook to explore the records from sapiens_exp
    • added scenario_0
    • scenario with generic tool
    • refactoring of the observer for Step BREAKING CHANGES: API changed.
    • sapiens_exp

    New Features (BREAKING)

    • Richer errors while invoking tools
    • Collect information in a serializable struct with all that matters
    • collect execution traces

    Commit Statistics

    • 12 commits contributed to the release over the course of 4 calendar days.
    • 5 days passed between releases.
    • 9 commits were understood as conventional.
    • 0 issues like '(#ID)' were seen in commit messages

    Commit Details

    view details
    • Uncategorized
      • Merge pull request #13 from ssoudan/getting_methodical (e0d97aa)
      • Store the current state in Trace Events (4626deb)
      • Richer errors while invoking tools (04e83c2)
      • Wip (b6d2dd7)
      • Jupter notebook to explore the records from sapiens_exp (41f1679)
      • Added scenario_0 (c6d0056)
      • Scenario with generic tool (0f106f4)
      • Merge remote-tracking branch 'origin/main' into getting_methodical (69ed1e8)
      • Collect information in a serializable struct with all that matters (6c30344)
      • Collect execution traces (f93652f)
      • Refactoring of the observer for Step (a35ed60)
      • Sapiens_exp (7c98fcb)
    Source code(tar.gz)
    Source code(zip)
  • sapiens_tools-v0.5.0(Apr 27, 2023)

    Chore

    • cleanup

    New Features (BREAKING)

    • more flexible parsing

    Commit Statistics

    • 3 commits contributed to the release.
    • 2 commits were understood as conventional.
    • 0 issues like '(#ID)' were seen in commit messages

    Commit Details

    view details
    • Uncategorized
      • Merge pull request #10 from ssoudan/parsing (568d536)
      • Cleanup (8f03992)
      • More flexible parsing (5d785d7)
    Source code(tar.gz)
    Source code(zip)
  • sapiens_cli-v0.4.0(Apr 27, 2023)

    Chore

    • cleanup

    Commit Statistics

    • 2 commits contributed to the release.
    • 1 commit was understood as conventional.
    • 0 issues like '(#ID)' were seen in commit messages

    Commit Details

    view details
    • Uncategorized
      • Merge pull request #10 from ssoudan/parsing (568d536)
      • Cleanup (8f03992)
    Source code(tar.gz)
    Source code(zip)
  • sapiens_bot-v0.3.0(Apr 27, 2023)

    Chore

    • cleanup

    Commit Statistics

    • 2 commits contributed to the release.
    • 1 commit was understood as conventional.
    • 0 issues like '(#ID)' were seen in commit messages

    Commit Details

    view details
    • Uncategorized
      • Merge pull request #10 from ssoudan/parsing (568d536)
      • Cleanup (8f03992)
    Source code(tar.gz)
    Source code(zip)
  • sapiens-v0.5.0(Apr 27, 2023)

    Chore

    • cleanup

    New Features (BREAKING)

    • more flexible parsing

    Commit Statistics

    • 3 commits contributed to the release.
    • 2 commits were understood as conventional.
    • 0 issues like '(#ID)' were seen in commit messages

    Commit Details

    view details
    • Uncategorized
      • Merge pull request #10 from ssoudan/parsing (568d536)
      • Cleanup (8f03992)
      • More flexible parsing (5d785d7)
    Source code(tar.gz)
    Source code(zip)
  • sapiens_tools-v0.4.1(Apr 26, 2023)

    New Features

    • dotenvy in tests
    • custom Debug
    • search and logging/tracing
    • search tool"
    • update tool calling convention description

    Bug Fixes

    • more dotenvy

    Commit Statistics

    • 7 commits contributed to the release.
    • 6 commits were understood as conventional.
    • 0 issues like '(#ID)' were seen in commit messages

    Commit Details

    view details
    • Uncategorized
      • Merge pull request #9 from ssoudan/search (8976be2)
      • More dotenvy (27059b5)
      • Dotenvy in tests (acb725e)
      • Custom Debug (cd14da7)
      • Search and logging/tracing (3c9e702)
      • Search tool" (87ae158)
      • Update tool calling convention description (f67aea1)
    Source code(tar.gz)
    Source code(zip)
  • sapiens_cli-v0.3.1(Apr 26, 2023)

    New Features

    • search and logging/tracing
    • search tool"

    Commit Statistics

    • 3 commits contributed to the release.
    • 2 commits were understood as conventional.
    • 0 issues like '(#ID)' were seen in commit messages

    Commit Details

    view details
    • Uncategorized
      • Merge pull request #9 from ssoudan/search (8976be2)
      • Search and logging/tracing (3c9e702)
      • Search tool" (87ae158)
    Source code(tar.gz)
    Source code(zip)
  • sapiens_bot-v0.2.3(Apr 26, 2023)

    New Features

    • search and logging/tracing
    • search tool"
    • better looking bot
    • not as verbose bot output

    Commit Statistics

    • 5 commits contributed to the release.
    • 4 commits were understood as conventional.
    • 0 issues like '(#ID)' were seen in commit messages

    Commit Details

    view details
    • Uncategorized
      • Merge pull request #9 from ssoudan/search (8976be2)
      • Search and logging/tracing (3c9e702)
      • Search tool" (87ae158)
      • Better looking bot (88fc635)
      • Not as verbose bot output (efb82c5)
    Source code(tar.gz)
    Source code(zip)
  • sapiens-v0.4.1(Apr 26, 2023)

    New Features

    • search and logging/tracing
    • search tool"

    Commit Statistics

    • 3 commits contributed to the release.
    • 2 commits were understood as conventional.
    • 0 issues like '(#ID)' were seen in commit messages

    Commit Details

    view details
    • Uncategorized
      • Merge pull request #9 from ssoudan/search (8976be2)
      • Search and logging/tracing (3c9e702)
      • Search tool" (87ae158)
    Source code(tar.gz)
    Source code(zip)
  • sapiens_tools-v0.4.0(Apr 25, 2023)

    Chore

    • CHANGELOGs
    • CHANGELOG
    • update

    New Features

    • improved format description
    • reduce initial prompt size
    • summarize tool

    Bug Fixes

    • eliminate import tools and from tools import...
    • deps
    • filtering of import tools and from tools import
    • eliminate import tools from the code

    Bug Fixes (BREAKING)

    • renamed Arxiv tool

    Commit Statistics

    • 12 commits contributed to the release over the course of 1 calendar day.
    • 1 day passed between releases.
    • 11 commits were understood as conventional.
    • 0 issues like '(#ID)' were seen in commit messages

    Commit Details

    view details
    • Uncategorized
      • CHANGELOGs (1a6b897)
      • Merge pull request #8 from ssoudan/tools (3b7f2b2)
      • CHANGELOG (6e90dcd)
      • Update (35a6a99)
      • Eliminate import tools and from tools import... (f62eb17)
      • Improved format description (3744b79)
      • Reduce initial prompt size (a08cd20)
      • Deps (b152135)
      • Filtering of import tools and from tools import (d79778b)
      • Renamed Arxiv tool (11de03c)
      • Eliminate import tools from the code (ee0c2df)
      • Summarize tool (23383eb)
    Source code(tar.gz)
    Source code(zip)
  • sapiens_derive-v0.3.1(Apr 25, 2023)

    Chore

    • CHANGELOG

    New Features

    • summarize tool

    Commit Statistics

    • 3 commits contributed to the release over the course of 1 calendar day.
    • 1 day passed between releases.
    • 2 commits were understood as conventional.
    • 0 issues like '(#ID)' were seen in commit messages

    Commit Details

    view details
    • Uncategorized
      • Merge pull request #8 from ssoudan/tools (3b7f2b2)
      • CHANGELOG (6e90dcd)
      • Summarize tool (23383eb)
    Source code(tar.gz)
    Source code(zip)
  • sapiens_cli-v0.3.0(Apr 25, 2023)

    Chore

    • release prep

    Chore

    • CHANGELOGs
    • CHANGELOG
    • update

    New Features

    • Discord bot
    • arXiv query api
    • async TaskProgressUpdateHandler
    • basic integration with discord
    • more detailed updates while working on a task
    • reduce initial prompt size
    • summarize tool

    Bug Fixes

    • sorted tool descriptions (by name)
    • pyo3-asyncio features

    Refactor

    • main loop to process model and tools outputs

    New Features (BREAKING)

    • async api for Tools and in most places actually

    Refactor (BREAKING)

    • main loop to process model and tools outputs (part 2)

    Commit Statistics

    • 19 commits contributed to the release over the course of 4 calendar days.
    • 5 days passed between releases.
    • 16 commits were understood as conventional.
    • 0 issues like '(#ID)' were seen in commit messages

    Commit Details

    view details
    • Uncategorized
      • Pyo3-asyncio features (260cbe6)
      • Release sapiens v0.4.0, sapiens_derive v0.3.1, sapiens_tools v0.4.0, sapiens_bot v0.2.2, sapiens_cli v0.3.0, safety bump 3 crates (0da51f4)
      • CHANGELOGs (1a6b897)
      • Merge pull request #8 from ssoudan/tools (3b7f2b2)
      • CHANGELOG (6e90dcd)
      • Update (35a6a99)
      • Reduce initial prompt size (a08cd20)
      • Summarize tool (23383eb)
      • Release sapiens v0.3.0, sapiens_derive v0.3.0, sapiens_tools v0.3.0, sapiens_bot v0.2.2, sapiens_cli v0.3.0, safety bump 3 crates (12e417c)
      • Discord bot (8be8d0f)
      • Release prep (1452992)
      • ArXiv query api (0840086)
      • Sorted tool descriptions (by name) (c37e7ca)
      • Async TaskProgressUpdateHandler (774d5a6)
      • Basic integration with discord (dee80b4)
      • Async api for Tools and in most places actually (772e8eb)
      • More detailed updates while working on a task (d497429)
      • Main loop to process model and tools outputs (part 2) (b11b947)
      • Main loop to process model and tools outputs (15c52d8)
    Source code(tar.gz)
    Source code(zip)
  • sapiens_bot-v0.2.2(Apr 25, 2023)

    Chore

    • deps updated

    Chore

    • CHANGELOGs
    • CHANGELOG
    • update
    • CHANGELOG

    New Features

    • Discord bot
    • arXiv query api
    • async TaskProgressUpdateHandler
    • basic integration with discord
    • prototype of a Discord bot
    • summarize tool

    New Features (BREAKING)

    • async api for Tools and in most places actually

    Commit Statistics

    • 14 commits contributed to the release over the course of 4 calendar days.
    • 12 commits were understood as conventional.
    • 0 issues like '(#ID)' were seen in commit messages

    Commit Details

    view details
    • Uncategorized
      • CHANGELOGs (1a6b897)
      • Merge pull request #8 from ssoudan/tools (3b7f2b2)
      • CHANGELOG (6e90dcd)
      • Update (35a6a99)
      • Summarize tool (23383eb)
      • CHANGELOG (88681e1)
      • Release sapiens v0.3.0, sapiens_derive v0.3.0, sapiens_tools v0.3.0, sapiens_bot v0.2.2, sapiens_cli v0.3.0, safety bump 3 crates (12e417c)
      • Discord bot (8be8d0f)
      • ArXiv query api (0840086)
      • Deps updated (7ea6a11)
      • Async TaskProgressUpdateHandler (774d5a6)
      • Basic integration with discord (dee80b4)
      • Prototype of a Discord bot (c4981fe)
      • Async api for Tools and in most places actually (772e8eb)
    Source code(tar.gz)
    Source code(zip)
  • sapiens-v0.4.0(Apr 25, 2023)

    Chore

    • CHANGELOGs
    • CHANGELOG
    • update

    New Features

    • reduce initial prompt size
    • summarize tool

    Bug Fixes (BREAKING)

    • renamed Arxiv tool

    Commit Statistics

    • 7 commits contributed to the release over the course of 1 calendar day.
    • 1 day passed between releases.
    • 6 commits were understood as conventional.
    • 0 issues like '(#ID)' were seen in commit messages

    Commit Details

    view details
    • Uncategorized
      • CHANGELOGs (1a6b897)
      • Merge pull request #8 from ssoudan/tools (3b7f2b2)
      • CHANGELOG (6e90dcd)
      • Update (35a6a99)
      • Reduce initial prompt size (a08cd20)
      • Renamed Arxiv tool (11de03c)
      • Summarize tool (23383eb)
    Source code(tar.gz)
    Source code(zip)
  • sapiens_tools-v0.3.0(Apr 24, 2023)

    Chore

    • release prep
    • deps updated
    • cleanup

    New Features

    • Discord bot
    • arXiv query api
    • basic integration with discord

    Bug Fixes

    • wikipedia input example
    • tests snapshot
    • linefeed in tool descriptions
    • Better definition of the format for RoomToolInput
    • udeps config

    Refactor

    • main loop to process model and tools outputs

    New Features (BREAKING)

    • async api for Tools and in most places actually

    Refactor (BREAKING)

    • main loop to process model and tools outputs (part 2)

    Commit Statistics

    • 15 commits contributed to the release over the course of 4 calendar days.
    • 4 days passed between releases.
    • 14 commits were understood as conventional.
    • 0 issues like '(#ID)' were seen in commit messages

    Commit Details

    view details
    • Uncategorized
      • Discord bot (8be8d0f)
      • Release prep (1452992)
      • ArXiv query api (0840086)
      • Wikipedia input example (b926c83)
      • Tests snapshot (04d1762)
      • Linefeed in tool descriptions (97d7c70)
      • Merge remote-tracking branch 'origin/main' into bot (4f17f43)
      • Better definition of the format for RoomToolInput (56ea40e)
      • Deps updated (7ea6a11)
      • Basic integration with discord (f416adf)
      • Udeps config (e195330)
      • Async api for Tools and in most places actually (772e8eb)
      • Main loop to process model and tools outputs (part 2) (b11b947)
      • Main loop to process model and tools outputs (15c52d8)
      • Cleanup (385aab3)
    Source code(tar.gz)
    Source code(zip)
  • sapiens_derive-v0.3.0(Apr 24, 2023)

    New Features

    • Discord bot

    Bug Fixes

    • linefeed in tool descriptions

    New Features (BREAKING)

    • async api for Tools and in most places actually

    Commit Statistics

    • 3 commits contributed to the release over the course of 3 calendar days.
    • 4 days passed between releases.
    • 3 commits were understood as conventional.
    • 0 issues like '(#ID)' were seen in commit messages

    Commit Details

    view details
    • Uncategorized
      • Discord bot (8be8d0f)
      • Linefeed in tool descriptions (97d7c70)
      • Async api for Tools and in most places actually (772e8eb)
    Source code(tar.gz)
    Source code(zip)
  • sapiens-v0.3.0(Apr 24, 2023)

    Chore

    • deps updated
    • deps updated
    • API changes in deps

    New Features

    • Discord bot
    • async TaskProgressUpdateHandler
    • basic integration with discord
    • basic integration with discord
    • prototype of a Discord bot
    • more detailed updates while working on a task

    Bug Fixes

    • sorted tool descriptions (by name)
    • duplicate entry
    • deps

    Refactor

    • main loop to process model and tools outputs

    New Features (BREAKING)

    • async api for Tools and in most places actually

    Refactor (BREAKING)

    • main loop to process model and tools outputs (part 2)

    Commit Statistics

    • 16 commits contributed to the release over the course of 3 calendar days.
    • 4 days passed between releases.
    • 15 commits were understood as conventional.
    • 0 issues like '(#ID)' were seen in commit messages

    Commit Details

    view details
    • Uncategorized
      • Discord bot (8be8d0f)
      • Sorted tool descriptions (by name) (c37e7ca)
      • Duplicate entry (c0604dc)
      • Merge remote-tracking branch 'origin/main' into bot (4f17f43)
      • Deps updated (cc8115a)
      • Deps updated (7ea6a11)
      • Async TaskProgressUpdateHandler (774d5a6)
      • Basic integration with discord (f416adf)
      • Basic integration with discord (dee80b4)
      • Deps (0ac757b)
      • Prototype of a Discord bot (c4981fe)
      • Async api for Tools and in most places actually (772e8eb)
      • More detailed updates while working on a task (d497429)
      • API changes in deps (1a0bdf6)
      • Main loop to process model and tools outputs (part 2) (b11b947)
      • Main loop to process model and tools outputs (15c52d8)
    Source code(tar.gz)
    Source code(zip)
  • sapiens_tools-v0.2.2(Apr 20, 2023)

    • More tools!

    Documentation

    • Changelog

    Chore

    • cleanup

    New Features

    • build container without Hue support by default - EXTRA_FEATURE="hue" to enable.
    • format of tools.list() output.
    • ToolName with Action result.
    • Added WikipediaTool
    • Added WikipediaTool
    • Added WikidataTool
    • toolbox assembly conditioned on Cargo features

    Bug Fixes

    • Support multivalued parameters

    Commit Statistics

    • 11 commits contributed to the release.
    • 10 commits were understood as conventional.
    • 0 issues like '(#ID)' were seen in commit messages

    Commit Details

    view details
    • Uncategorized
      • Release sapiens v0.2.2, sapiens_derive v0.2.2, sapiens_tools v0.2.2, sapiens_cli v0.2.2 (b72b47f)
      • Changelog (1844702)
      • Build container without Hue support by default - EXTRA_FEATURE="hue" to enable. (3e15ff7)
      • Format of tools.list() output. (49e0a6e)
      • ToolName with Action result. (ed70724)
      • Support multivalued parameters (d3ffde8)
      • Added WikipediaTool (90c5cbd)
      • Cleanup (41bca7d)
      • Added WikipediaTool (b040052)
      • Added WikidataTool (b2902bb)
      • Toolbox assembly conditioned on Cargo features (9f251be)
    Source code(tar.gz)
    Source code(zip)
  • sapiens_derive-v0.2.2(Apr 20, 2023)

    Documentation

    • Changelog

    Bug Fixes

    • Support multivalued parameters

    Commit Statistics

    • 3 commits contributed to the release.
    • 2 commits were understood as conventional.
    • 0 issues like '(#ID)' were seen in commit messages

    Commit Details

    view details
    • Uncategorized
      • Release sapiens v0.2.2, sapiens_derive v0.2.2, sapiens_tools v0.2.2, sapiens_cli v0.2.2 (b72b47f)
      • Changelog (1844702)
      • Support multivalued parameters (d3ffde8)
    Source code(tar.gz)
    Source code(zip)
Owner
Sebastien Soudan
Sebastien Soudan
Matrix bot inspired by Shirt Bot.

matrix-openai-bot Matrix bot inspired by Shirt Bot. Usage Run the bot after building it or grabbing the latest release $ matrix-openai-bot Edit the ge

null 5 Oct 26, 2021
Rewrite of the Discord Bot used for Managing the Infinity Bot List Servers.

Arcadia Rewrite of the Discord Bot used for Managing the Infinity Bot List Servers. Contributing Always run fmt.sh before making a Pull Request! MacOS

InfinityBotList 3 Dec 15, 2022
A Simple, But amazing telegram bot, Made using the Rust language!

Telegram bot in Rust A fun Telegram bot made using Rust language.

Deep Alchemy 2 Dec 21, 2021
Telegram bot for searching in Arch User Repository ( AUR ); Implemented using rust.

AurSearchBot A Telegram Inline Search Bot Written in Rust Introduction Telegram Bot that can search AUR ( Arch User Repository ) in inline mode. This

AlenPaulVarghese 3 Feb 15, 2022
An experimental Discord bot using Serenity.

VoidBot An experimental Discord bot using Serenity. Environment Variables Can be set with a .env file. DISCORD_TOKEN: The token for your bot. (require

null 1 May 21, 2022
This is a Discord bot written in Rust to translate to and from the Bottom Encoding Standard using bottom-rs and Serenity.

bottom-bot This is a Discord bot written in Rust to translate to and from the Bottom Encoding Standard using bottom-rs and Serenity. Ever had this pro

Bottom Software Foundation 11 Dec 10, 2022
Chains - a bot written in Rust using the serenity crate

Chains (Rusty) Chains is a bot written in Rust using the serenity crate. Chains primarily focuses on easy to set up, easy to use moderation tools such

Quin 3 Mar 28, 2022
A Discord bot, written in Rust, that generates responses using the LLaMA language model.

llamacord A Discord bot, written in Rust, that generates responses using the LLaMA language model. Built on top of llama-rs. Setup Model Obtain the LL

Philpax 6 Mar 20, 2023
A Discord bot, written in Rust, that generates responses using the LLaMA language model.

llamacord A Discord bot, written in Rust, that generates responses using the LLaMA language model. Built on top of llama-rs. Setup Model Obtain the LL

Rustformers 18 Apr 9, 2023
A simple bot for discord.

Rusky Um simples bot para o discord! ?? Executando ⚠️ Antes de tudo você precisa do Rust Instalado você pode instalar clicando aqui Preparando Primeir

Rusky 3 Aug 12, 2022
This is a Telegram bot I'm working on in my free time to learn Rust.

Maldness Bot This is a Telegram bot I'm working on in my free time to learn Rust. Building docker build -t . should be enough.

Sergey Kislyakov 10 May 13, 2022
Play Onitama in your browser, compete with friends or lose to a bot

Play Onitama in your browser, compete with friends or lose to a bot

Jack Adamson 52 Nov 12, 2022
A Discord bot for lichess and Rosen related things

liro Liro is a Discord bot that follows in the footsteps of Lichess-discord-bot, without necessarily aiming to replace it. The main pain point that th

Sebastian Lauwers 5 Feb 16, 2022
This is a simple Telegram bot with interface to Firefly III to process and store simple transactions.

Firefly Telegram Bot Fireflies are free, so beautiful. (Les lucioles sont libres, donc belles.) ― Charles de Leusse, Les Contes de la nuit This is a s

null 13 Dec 14, 2022
Hi I'm Sophy, a discord bot in devlopment, soon I'll be available to help everyone (❁´◡`❁)

Sophy Bot Hi I'm Sophy, a discord bot in devlopment, soon I'll be available to help everyone (❁´◡`❁) Contribution Do you like me and want to help me?

Far Dragi 0 May 30, 2022
Telegram Bot Template with Cloudflare Workers

cf-workers-telegram-bot-template Usage This template starts you off with a src/lib.rs file, acting as an entrypoint for requests hitting your Worker.

Lee Taehoon 2 Sep 23, 2021
Rust telegram bot library for many runtimes

Telbot Telbot provides telegram bot types and api wrappers. Specifically, telbot now supports: telbot-types: basic telegram types / requests / respons

kiwiyou 17 Dec 3, 2022
Just a bot for Neovim's Matrix room(s)

nvim-matrix-bot Currently just supports replying to messages with :h <some_doc> or similar in them with a link to the docs on Neovim's website. Plan i

null 8 Aug 6, 2022
Music bot written in Rust

Akasuki What is Akasuki? Akasuki is a simple discord music bot written in rust. Highlights Select your music using discord's new select menu feature,

Forbidden A 0 Dec 19, 2021