Release 0.8.0b17

Author: fern-api[bot]

README.md

@@ -190,8 +190,7 @@ response = client.prompts.call_stream(
         "2024-01-15 09:30:00+00:00",
     ),
     source_datapoint_id="string",
-    trace_id="string",
-    trace_parent_log_id="string",
+    trace_parent_id="string",
     batches=["string"],
     user="string",
     prompts_call_stream_request_environment="string",

pyproject.toml

@@ -1,6 +1,6 @@
 [tool.poetry]
 name = "humanloop"
-version = "0.8.0b16"
+version = "0.8.0b17"
 description = ""
 readme = "README.md"
 authors = []

reference.md

@@ -306,15 +306,7 @@ Controls how the model uses tools. The following options are supported:
 <dl>
 <dd>
 
-**trace_id:** `typing.Optional[str]` — Identifier of the Flow Log to which the Log will be associated. Multiple Logs can be associated by passing the same trace_id in subsequent log requests. Use the Flow File log endpoint to create the Trace first.
-    
-</dd>
-</dl>
-
-<dl>
-<dd>
-
-**trace_parent_log_id:** `typing.Optional[str]` — Log under which this Log should be nested. Leave field blank if the Log should be nested directly under root Trace Log. Parent Log should already be added to the Trace.
+**trace_parent_id:** `typing.Optional[str]` — The ID of the parent Log to nest this Log under in a Trace.
 
 </dd>
 </dl>
@@ -719,8 +711,7 @@ response = client.prompts.call_stream(
         "2024-01-15 09:30:00+00:00",
     ),
     source_datapoint_id="string",
-    trace_id="string",
-    trace_parent_log_id="string",
+    trace_parent_id="string",
     batches=["string"],
     user="string",
     prompts_call_stream_request_environment="string",
@@ -867,15 +858,7 @@ Controls how the model uses tools. The following options are supported:
 <dl>
 <dd>
 
-**trace_id:** `typing.Optional[str]` — Identifier of the Flow Log to which the Log will be associated. Multiple Logs can be associated by passing the same trace_id in subsequent log requests. Use the Flow File log endpoint to create the Trace first.
-    
-</dd>
-</dl>
-
-<dl>
-<dd>
-
-**trace_parent_log_id:** `typing.Optional[str]` — Log under which this Log should be nested. Leave field blank if the Log should be nested directly under root Trace Log. Parent Log should already be added to the Trace.
+**trace_parent_id:** `typing.Optional[str]` — The ID of the parent Log to nest this Log under in a Trace.
 
 </dd>
 </dl>
@@ -1141,15 +1124,7 @@ Controls how the model uses tools. The following options are supported:
 <dl>
 <dd>
 
-**trace_id:** `typing.Optional[str]` — Identifier of the Flow Log to which the Log will be associated. Multiple Logs can be associated by passing the same trace_id in subsequent log requests. Use the Flow File log endpoint to create the Trace first.
-    
-</dd>
-</dl>
-
-<dl>
-<dd>
-
-**trace_parent_log_id:** `typing.Optional[str]` — Log under which this Log should be nested. Leave field blank if the Log should be nested directly under root Trace Log. Parent Log should already be added to the Trace.
+**trace_parent_id:** `typing.Optional[str]` — The ID of the parent Log to nest this Log under in a Trace.
 
 </dd>
 </dl>
@@ -2565,15 +2540,7 @@ client.tools.log(
 <dl>
 <dd>
 
-**trace_id:** `typing.Optional[str]` — Identifier of the Flow Log to which the Log will be associated. Multiple Logs can be associated by passing the same trace_id in subsequent log requests. Use the Flow File log endpoint to create the Trace first.
-    
-</dd>
-</dl>
-
-<dl>
-<dd>
-
-**trace_parent_log_id:** `typing.Optional[str]` — Log under which this Log should be nested. Leave field blank if the Log should be nested directly under root Trace Log. Parent Log should already be added to the Trace.
+**trace_parent_id:** `typing.Optional[str]` — The ID of the parent Log to nest this Log under in a Trace.
 
 </dd>
 </dl>
@@ -4304,7 +4271,7 @@ client.datasets.delete(
 <dl>
 <dd>
 
-Update the Dataset with the given ID.
+Move the Dataset to a different path or change the name.
 </dd>
 </dl>
 </dd>
@@ -6092,15 +6059,7 @@ client.evaluators.log(
 <dl>
 <dd>
 
-**trace_id:** `typing.Optional[str]` — Identifier of the Flow Log to which the Log will be associated. Multiple Logs can be associated by passing the same trace_id in subsequent log requests. Use the Flow File log endpoint to create the Trace first.
-    
-</dd>
-</dl>
-
-<dl>
-<dd>
-
-**trace_parent_log_id:** `typing.Optional[str]` — Log under which this Log should be nested. Leave field blank if the Log should be nested directly under root Trace Log. Parent Log should already be added to the Trace.
+**trace_parent_id:** `typing.Optional[str]` — The ID of the parent Log to nest this Log under in a Trace.
 
 </dd>
 </dl>
@@ -6434,7 +6393,7 @@ client.flows.move(
 <dl>
 <dd>
 
-Get a list of all Flows.
+Get a list of Flows.
 </dd>
 </dl>
 </dd>
@@ -6534,6 +6493,26 @@ client.flows.list()
 <dl>
 <dd>
 
+#### 📝 Description
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+Create or update a Flow.
+
+Flows can also be identified by the `ID` or their `path`.
+
+If you provide a commit message, then the new version will be committed;
+otherwise it will be uncommitted. If you try to commit an already committed version,
+an exception will be raised.
+</dd>
+</dl>
+</dd>
+</dl>
+
 #### 🔌 Usage
 
 <dl>
@@ -6622,7 +6601,10 @@ client.flows.upsert(
 <dl>
 <dd>
 
-Log a Flow Trace.
+Log to a Flow.
+
+You can use query parameters `version_id`, or `environment`, to target
+an existing version of the Flow. Otherwise, the default deployed version will be chosen.
 </dd>
 </dl>
 </dd>
@@ -6802,47 +6784,47 @@ client.flows.log()
 <dl>
 <dd>
 
-**trace_id:** `typing.Optional[str]` — ID of the Trace. If not provided, one will be assigned.
+**trace_parent_id:** `typing.Optional[str]` — The ID of the parent Log to nest this Log under in a Trace.
 
 </dd>
 </dl>
 
 <dl>
 <dd>
 
-**trace_parent_log_id:** `typing.Optional[str]` — Log under which this Log should be nested. Leave field blank if the Log should be nested directly under root Trace Log. Parent Log should already be added to the Trace.
+**batches:** `typing.Optional[typing.Sequence[str]]` — Array of Batch Ids that this log is part of. Batches are used to group Logs together for offline Evaluations
 
 </dd>
 </dl>
 
 <dl>
 <dd>
 
-**batches:** `typing.Optional[typing.Sequence[str]]` — Array of Batch Ids that this log is part of. Batches are used to group Logs together for offline Evaluations
+**user:** `typing.Optional[str]` — End-user ID related to the Log.
 
 </dd>
 </dl>
 
 <dl>
 <dd>
 
-**user:** `typing.Optional[str]` — End-user ID related to the Log.
+**flow_log_request_environment:** `typing.Optional[str]` — The name of the Environment the Log is associated to.
 
 </dd>
 </dl>
 
 <dl>
 <dd>
 
-**flow_log_request_environment:** `typing.Optional[str]` — The name of the Environment the Log is associated to.
+**save:** `typing.Optional[bool]` — Whether the request/response payloads will be stored on Humanloop.
 
 </dd>
 </dl>
 
 <dl>
 <dd>
 
-**save:** `typing.Optional[bool]` — Whether the request/response payloads will be stored on Humanloop.
+**trace_id:** `typing.Optional[str]` — ID of the Trace. If not provided, one will be assigned.
 
 </dd>
 </dl>
@@ -6878,10 +6860,27 @@ client.flows.log()
 </dl>
 </details>
 
-<details><summary><code>client.flows.<a href="src/humanloop/flows/client.py">update_trace</a>(...)</code></summary>
+<details><summary><code>client.flows.<a href="src/humanloop/flows/client.py">update_log</a>(...)</code></summary>
 <dl>
 <dd>
 
+#### 📝 Description
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+Update the status, inputs, output of a Flow Log.
+
+Marking a Flow Log as complete will trigger any monitoring Evaluators to run.
+Inputs and output (or error) must be provided in order to mark it as complete.
+</dd>
+</dl>
+</dd>
+</dl>
+
 #### 🔌 Usage
 
 <dl>
@@ -6896,9 +6895,9 @@ from humanloop import Humanloop
 client = Humanloop(
     api_key="YOUR_API_KEY",
 )
-client.flows.update_trace(
-    trace_id="trace_id",
-    status="complete",
+client.flows.update_log(
+    log_id="log_id",
+    trace_status="complete",
 )
 
 ```
@@ -6915,15 +6914,15 @@ client.flows.update_trace(
 <dl>
 <dd>
 
-**trace_id:** `str` — Unique identifier for Trace.
+**log_id:** `str` — Unique identifier of the Flow Log.
 
 </dd>
 </dl>
 
 <dl>
 <dd>
 
-**status:** `TraceStatus` — Status of the Trace. When a Trace is marked as `complete`, no more Logs can be added to it. Monitoring Evaluators will only run on `complete` Traces.
+**trace_status:** `TraceStatus` — Status of the Trace. When a Trace is marked as `complete`, no more Logs can be added to it. Monitoring Evaluators will only run on completed Traces.
 
 </dd>
 </dl>
@@ -6939,7 +6938,15 @@ client.flows.update_trace(
 <dl>
 <dd>
 
-**output:** `typing.Optional[str]` — The output of the Flow Log.
+**output:** `typing.Optional[str]` — The output of the Flow Log. Provide None to unset existing `output` value. Provide either this or `error`.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**error:** `typing.Optional[str]` — The error message of the Flow Log. Provide None to unset existing `error` value. Provide either this or `output`.
 
 </dd>
 </dl>

src/humanloop/core/client_wrapper.py

@@ -16,7 +16,7 @@ def get_headers(self) -> typing.Dict[str, str]:
         headers: typing.Dict[str, str] = {
             "X-Fern-Language": "Python",
             "X-Fern-SDK-Name": "humanloop",
-            "X-Fern-SDK-Version": "0.8.0b16",
+            "X-Fern-SDK-Version": "0.8.0b17",
         }
         headers["X-API-KEY"] = self.api_key
         return headers

src/humanloop/datasets/client.py

@@ -429,7 +429,7 @@ def move(
         request_options: typing.Optional[RequestOptions] = None,
     ) -> DatasetResponse:
         """
-        Update the Dataset with the given ID.
+        Move the Dataset to a different path or change the name.
 
         Parameters
         ----------
@@ -1458,7 +1458,7 @@ async def move(
         request_options: typing.Optional[RequestOptions] = None,
     ) -> DatasetResponse:
         """
-        Update the Dataset with the given ID.
+        Move the Dataset to a different path or change the name.
 
         Parameters
         ----------

src/humanloop/evaluators/client.py

@@ -801,8 +801,7 @@ def log(
         source: typing.Optional[str] = OMIT,
         metadata: typing.Optional[typing.Dict[str, typing.Optional[typing.Any]]] = OMIT,
         source_datapoint_id: typing.Optional[str] = OMIT,
-        trace_id: typing.Optional[str] = OMIT,
-        trace_parent_log_id: typing.Optional[str] = OMIT,
+        trace_parent_id: typing.Optional[str] = OMIT,
         batches: typing.Optional[typing.Sequence[str]] = OMIT,
         user: typing.Optional[str] = OMIT,
         create_evaluator_log_request_environment: typing.Optional[str] = OMIT,
@@ -872,11 +871,8 @@ def log(
         source_datapoint_id : typing.Optional[str]
             Unique identifier for the Datapoint that this Log is derived from. This can be used by Humanloop to associate Logs to Evaluations. If provided, Humanloop will automatically associate this Log to Evaluations that require a Log for this Datapoint-Version pair.
 
-        trace_id : typing.Optional[str]
-            Identifier of the Flow Log to which the Log will be associated. Multiple Logs can be associated by passing the same trace_id in subsequent log requests. Use the Flow File log endpoint to create the Trace first.
-
-        trace_parent_log_id : typing.Optional[str]
-            Log under which this Log should be nested. Leave field blank if the Log should be nested directly under root Trace Log. Parent Log should already be added to the Trace.
+        trace_parent_id : typing.Optional[str]
+            The ID of the parent Log to nest this Log under in a Trace.
 
         batches : typing.Optional[typing.Sequence[str]]
             Array of Batch Ids that this log is part of. Batches are used to group Logs together for offline Evaluations
@@ -938,8 +934,7 @@ def log(
                 "metadata": metadata,
                 "parent_id": parent_id,
                 "source_datapoint_id": source_datapoint_id,
-                "trace_id": trace_id,
-                "trace_parent_log_id": trace_parent_log_id,
+                "trace_parent_id": trace_parent_id,
                 "batches": batches,
                 "user": user,
                 "environment": create_evaluator_log_request_environment,
@@ -1828,8 +1823,7 @@ async def log(
         source: typing.Optional[str] = OMIT,
         metadata: typing.Optional[typing.Dict[str, typing.Optional[typing.Any]]] = OMIT,
         source_datapoint_id: typing.Optional[str] = OMIT,
-        trace_id: typing.Optional[str] = OMIT,
-        trace_parent_log_id: typing.Optional[str] = OMIT,
+        trace_parent_id: typing.Optional[str] = OMIT,
         batches: typing.Optional[typing.Sequence[str]] = OMIT,
         user: typing.Optional[str] = OMIT,
         create_evaluator_log_request_environment: typing.Optional[str] = OMIT,
@@ -1899,11 +1893,8 @@ async def log(
         source_datapoint_id : typing.Optional[str]
             Unique identifier for the Datapoint that this Log is derived from. This can be used by Humanloop to associate Logs to Evaluations. If provided, Humanloop will automatically associate this Log to Evaluations that require a Log for this Datapoint-Version pair.
 
-        trace_id : typing.Optional[str]
-            Identifier of the Flow Log to which the Log will be associated. Multiple Logs can be associated by passing the same trace_id in subsequent log requests. Use the Flow File log endpoint to create the Trace first.
-
-        trace_parent_log_id : typing.Optional[str]
-            Log under which this Log should be nested. Leave field blank if the Log should be nested directly under root Trace Log. Parent Log should already be added to the Trace.
+        trace_parent_id : typing.Optional[str]
+            The ID of the parent Log to nest this Log under in a Trace.
 
         batches : typing.Optional[typing.Sequence[str]]
             Array of Batch Ids that this log is part of. Batches are used to group Logs together for offline Evaluations
@@ -1973,8 +1964,7 @@ async def main() -> None:
                 "metadata": metadata,
                 "parent_id": parent_id,
                 "source_datapoint_id": source_datapoint_id,
-                "trace_id": trace_id,
-                "trace_parent_log_id": trace_parent_log_id,
+                "trace_parent_id": trace_parent_id,
                 "batches": batches,
                 "user": user,
                 "environment": create_evaluator_log_request_environment,