Release 0.8.39

Author: fern-api[bot]

poetry.lock

@@ -3,7 +3,7 @@ name = "humanloop"
 
 [tool.poetry]
 name = "humanloop"
-version = "0.8.40b3"
+version = "0.8.39"
 description = ""
 readme = "README.md"
 authors = []

pyproject.toml

@@ -178,6 +178,7 @@ Controls how the model uses tools. The following options are supported:
 The Prompt configuration to use. Two formats are supported:
 - An object representing the details of the Prompt configuration
 - A string representing the raw contents of a .prompt file
+
 A new Prompt version will be created if the provided details do not match any existing version.
 
 </dd>
@@ -282,14 +283,6 @@ A new Prompt version will be created if the provided details do not match any ex
 <dl>
 <dd>
 
-**log_status:** `typing.Optional[LogStatus]` — Status of a Log. Set to `incomplete` if you intend to update and eventually complete the Log and want the File's monitoring Evaluators to wait until you mark it as `complete`. If log_status is not provided, observability will pick up the Log as soon as possible. Updating this from specified to unspecified is undefined behavior.
-    
-</dd>
-</dl>
-
-<dl>
-<dd>
-
 **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.
 
 </dd>
@@ -587,14 +580,6 @@ Controls how the model uses tools. The following options are supported:
 <dl>
 <dd>
 
-**log_status:** `typing.Optional[LogStatus]` — Status of a Log. Set to `incomplete` if you intend to update and eventually complete the Log and want the File's monitoring Evaluators to wait until you mark it as `complete`. If log_status is not provided, observability will pick up the Log as soon as possible. Updating this from specified to unspecified is undefined behavior.
-    
-</dd>
-</dl>
-
-<dl>
-<dd>
-
 **request_options:** `typing.Optional[RequestOptions]` — Request-specific configuration.
 
 </dd>
@@ -724,6 +709,7 @@ Controls how the model uses tools. The following options are supported:
 The Prompt configuration to use. Two formats are supported:
 - An object representing the details of the Prompt configuration
 - A string representing the raw contents of a .prompt file
+
 A new Prompt version will be created if the provided details do not match any existing version.
 
 </dd>
@@ -772,14 +758,6 @@ A new Prompt version will be created if the provided details do not match any ex
 <dl>
 <dd>
 
-**log_status:** `typing.Optional[LogStatus]` — Status of a Log. Set to `incomplete` if you intend to update and eventually complete the Log and want the File's monitoring Evaluators to wait until you mark it as `complete`. If log_status is not provided, observability will pick up the Log as soon as possible. Updating this from specified to unspecified is undefined behavior.
-    
-</dd>
-</dl>
-
-<dl>
-<dd>
-
 **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.
 
 </dd>
@@ -996,6 +974,7 @@ Controls how the model uses tools. The following options are supported:
 The Prompt configuration to use. Two formats are supported:
 - An object representing the details of the Prompt configuration
 - A string representing the raw contents of a .prompt file
+
 A new Prompt version will be created if the provided details do not match any existing version.
 
 </dd>
@@ -1044,14 +1023,6 @@ A new Prompt version will be created if the provided details do not match any ex
 <dl>
 <dd>
 
-**log_status:** `typing.Optional[LogStatus]` — Status of a Log. Set to `incomplete` if you intend to update and eventually complete the Log and want the File's monitoring Evaluators to wait until you mark it as `complete`. If log_status is not provided, observability will pick up the Log as soon as possible. Updating this from specified to unspecified is undefined behavior.
-    
-</dd>
-</dl>
-
-<dl>
-<dd>
-
 **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.
 
 </dd>
@@ -2690,14 +2661,6 @@ client.tools.call()
 <dl>
 <dd>
 
-**log_status:** `typing.Optional[LogStatus]` — Status of a Log. Set to `incomplete` if you intend to update and eventually complete the Log and want the File's monitoring Evaluators to wait until you mark it as `complete`. If log_status is not provided, observability will pick up the Log as soon as possible. Updating this from specified to unspecified is undefined behavior.
-    
-</dd>
-</dl>
-
-<dl>
-<dd>
-
 **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.
 
 </dd>
@@ -2952,14 +2915,6 @@ client.tools.log(path='math-tool', tool={'function': {'name': 'multiply', 'descr
 <dl>
 <dd>
 
-**log_status:** `typing.Optional[LogStatus]` — Status of a Log. Set to `incomplete` if you intend to update and eventually complete the Log and want the File's monitoring Evaluators to wait until you mark it as `complete`. If log_status is not provided, observability will pick up the Log as soon as possible. Updating this from specified to unspecified is undefined behavior.
-    
-</dd>
-</dl>
-
-<dl>
-<dd>
-
 **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.
 
 </dd>
@@ -3179,14 +3134,6 @@ client.tools.update(id='id', log_id='log_id', )
 <dl>
 <dd>
 
-**log_status:** `typing.Optional[LogStatus]` — Status of a Log. Set to `incomplete` if you intend to update and eventually complete the Log and want the File's monitoring Evaluators to wait until you mark it as `complete`. If log_status is not provided, observability will pick up the Log as soon as possible. Updating this from specified to unspecified is undefined behavior.
-    
-</dd>
-</dl>
-
-<dl>
-<dd>
-
 **request_options:** `typing.Optional[RequestOptions]` — Request-specific configuration.
 
 </dd>
@@ -5779,14 +5726,6 @@ client.evaluators.log(parent_id='parent_id', )
 <dl>
 <dd>
 
-**log_status:** `typing.Optional[LogStatus]` — Status of a Log. Set to `incomplete` if you intend to update and eventually complete the Log and want the File's monitoring Evaluators to wait until you mark it as `complete`. If log_status is not provided, observability will pick up the Log as soon as possible. Updating this from specified to unspecified is undefined behavior.
-    
-</dd>
-</dl>
-
-<dl>
-<dd>
-
 **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.
 
 </dd>
@@ -6883,9 +6822,6 @@ 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.
-
-If you create the Flow Log with a `log_status` of `incomplete`, you should later update it to `complete`
-in order to trigger Evaluators.
 </dd>
 </dl>
 </dd>
@@ -7074,7 +7010,7 @@ client.flows.log(id='fl_6o701g4jmcanPVHxdqD0O', flow={'attributes': {'prompt': {
 <dl>
 <dd>
 
-**log_status:** `typing.Optional[LogStatus]` — Status of the Flow Log. When a Log is updated from `incomplete` to `complete`, it becomes available to Monitoring Evaluators. Flow Logs cannot have an unspecified status: they must start as `incomplete` to allow children to be added. Provide `complete` if you don't intend to add children to the trace.
+**log_status:** `typing.Optional[LogStatus]` — Status of the Flow Log. When a Log is updated from `incomplete` to `complete`, no more Logs can be added to it.
 
 </dd>
 </dl>
@@ -7249,7 +7185,7 @@ client.flows.update_log(log_id='medqa_experiment_0001', inputs={'question': 'Pat
 <dl>
 <dd>
 
-**log_status:** `typing.Optional[LogStatus]` — Status of the Flow Log. When a Flow Log is updated to `complete`, no more Logs can be added to it. Monitoring Evaluators will only run on `complete` Flow Logs.
+**log_status:** `typing.Optional[LogStatus]` — Status of the Flow Log. When a Flow Log is updated to `complete`, no more Logs can be added to it. You cannot update a Flow Log's status from `complete` to `incomplete`.
 
 </dd>
 </dl>
@@ -8447,6 +8383,7 @@ Controls how the model uses tools. The following options are supported:
 The Agent configuration to use. Two formats are supported:
 - An object representing the details of the Agent configuration
 - A string representing the raw contents of a .agent file
+
 A new Agent version will be created if the provided details do not match any existing version.
 
 </dd>
@@ -8551,14 +8488,6 @@ A new Agent version will be created if the provided details do not match any exi
 <dl>
 <dd>
 
-**log_status:** `typing.Optional[LogStatus]` — Status of a Log. Set to `incomplete` if you intend to update and eventually complete the Log and want the File's monitoring Evaluators to wait until you mark it as `complete`. If log_status is not provided, observability will pick up the Log as soon as possible. Updating this from specified to unspecified is undefined behavior.
-    
-</dd>
-</dl>
-
-<dl>
-<dd>
-
 **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.
 
 </dd>
@@ -8722,7 +8651,7 @@ client.agents.update_log(id='ag_1234567890', log_id='log_1234567890', messages=[
 <dl>
 <dd>
 
-**log_status:** `typing.Optional[LogStatus]` — Status of the Flow Log. When a Flow Log is updated to `complete`, no more Logs can be added to it. Monitoring Evaluators will only run on `complete` Flow Logs.
+**log_status:** `typing.Optional[LogStatus]` — Status of the Flow Log. When a Flow Log is updated to `complete`, no more Logs can be added to it. You cannot update a Flow Log's status from `complete` to `incomplete`.
 
 </dd>
 </dl>
@@ -8862,6 +8791,7 @@ Controls how the model uses tools. The following options are supported:
 The Agent configuration to use. Two formats are supported:
 - An object representing the details of the Agent configuration
 - A string representing the raw contents of a .agent file
+
 A new Agent version will be created if the provided details do not match any existing version.
 
 </dd>
@@ -8910,14 +8840,6 @@ A new Agent version will be created if the provided details do not match any exi
 <dl>
 <dd>
 
-**log_status:** `typing.Optional[LogStatus]` — Status of a Log. Set to `incomplete` if you intend to update and eventually complete the Log and want the File's monitoring Evaluators to wait until you mark it as `complete`. If log_status is not provided, observability will pick up the Log as soon as possible. Updating this from specified to unspecified is undefined behavior.
-    
-</dd>
-</dl>
-
-<dl>
-<dd>
-
 **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.
 
 </dd>
@@ -9120,6 +9042,7 @@ Controls how the model uses tools. The following options are supported:
 The Agent configuration to use. Two formats are supported:
 - An object representing the details of the Agent configuration
 - A string representing the raw contents of a .agent file
+
 A new Agent version will be created if the provided details do not match any existing version.
 
 </dd>
@@ -9168,14 +9091,6 @@ A new Agent version will be created if the provided details do not match any exi
 <dl>
 <dd>
 
-**log_status:** `typing.Optional[LogStatus]` — Status of a Log. Set to `incomplete` if you intend to update and eventually complete the Log and want the File's monitoring Evaluators to wait until you mark it as `complete`. If log_status is not provided, observability will pick up the Log as soon as possible. Updating this from specified to unspecified is undefined behavior.
-    
-</dd>
-</dl>
-
-<dl>
-<dd>
-
 **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.
 
 </dd>