fix tests and format

Author: dtam

docs/faq.md

@@ -29,7 +29,7 @@ It means that the call to the LLM failed. This is usually triggered for one of t
 1. An API key is not present or not passed correctly to the LLM
 1. The LLM API was passed arguments it doesn't expect. Our recommendation is to use the LiteLLM standard, and pass arguments that conform to that standard directly in the guard callable. It's helpful as a debugging step to remove all other arguments or to try and use the same arguments in a LiteLLM client directly.
 1. The LLM API is down or experiencing issues. This is usually temporary, and you can use LiteLLM or the LLM client directly to verify if the API is working as expected.
-1. You passed a custom LLM callable, and it either doesn't conform to the expected signature or it throws an error during execution. Make sure that the custom LLM callable can be called as a function that takes in a single prompt string and returns a string.
+1. You passed a custom LLM callable, and it either doesn't conform to the expected signature or it throws an error during execution. Make sure that the custom LLM callable can be called as a function that takes in messages kwarg and returns a string.
 
 ## How can I host Guardrails as its own server
 

guardrails/classes/history/inputs.py

@@ -98,7 +98,7 @@ def to_dict(self) -> Dict[str, Any]:
     @classmethod
     def from_interface(cls, i_inputs: IInputs) -> "Inputs":
         deserialized_messages = None
-        if i_inputs.messages:  # type: ignore
+        if hasattr(i_inputs, "messages") and i_inputs.messages:  # type: ignore
             deserialized_messages = []
             for msg in i_inputs.messages:  # type: ignore
                 ser_msg = {**msg}

guardrails/run/async_runner.py

@@ -296,7 +296,7 @@ async def async_prepare(
         """Prepare by running pre-processing and input validation.
 
         Returns:
-            The instructions, prompt, and message history.
+            The messages.
         """
         prompt_params = prompt_params or {}
         if api is None:

guardrails/run/runner.py

@@ -75,7 +75,7 @@ class Runner:
     disable_tracer: Optional[bool] = True
 
     # QUESTION: Are any of these init args actually necessary for initialization?
-    # ANSWER: _Maybe_ prompt, instructions, and messages for Prompt initialization
+    # ANSWER: _Maybe_ messages for Prompt initialization
     #   but even that can happen at execution time.
     # TODO: In versions >=0.6.x, remove this class and just execute a Guard functionally
     def __init__(

tests/integration_tests/test_async_streaming.py

@@ -165,7 +165,12 @@ async def test_async_streaming_fix_behavior_two_validators(mocker):
         max_tokens=10,
         temperature=0,
         stream=True,
-        prompt=prompt,
+        messages=[
+            {
+                "role": "user",
+                "content": prompt,
+            }
+        ],
     )
     text = ""
     original = ""
@@ -211,7 +216,12 @@ async def test_async_streaming_filter_behavior(mocker):
         max_tokens=10,
         temperature=0,
         stream=True,
-        prompt=prompt,
+        messages=[
+            {
+                "role": "user",
+                "content": prompt,
+            }
+        ],
     )
 
     validated = ""