Zayd

Hi! Your assessment is correct, this is a bug in how the feature is documented vs how it works. With the current sequencing of guard runs, validator params are serialized/deserialized...

Hi @vishal-ushur I'll look into this!

some fixes https://github.com/guardrails-ai/competitor_check/pull/3#pullrequestreview-1986563679 https://github.com/guardrails-ai/nsfw_text/pull/1#pullrequestreview-1986564085 https://github.com/guardrails-ai/gibberish_text/pull/1

We're looking at this, and we think that we can get rebuff to work in one of the following ways 1. add the github release to the pyproject 2. add...

@msintaha sweet yes the rebuff validator fix is merged, but I haven't validated it yet. Should be able to try again, otherwise I'll validate it later tonight. For huggingface models,...

Thanks for the PR! I’m a big fan of this change in theory but I do have a few follow ups 1. I think we lose a lot by losing...

I also love the suggestion of having lists of url regexes that are allowed/blocked

I like the `socket.getaddrinfo()` idea, but unfortunately that doesn't tell us whether an HTTP endpoint is open. I think it would be good to combine this approach with the HEAD...

can you please paste the contents of the file located at /usr/local/lib/python3.10/dist-packages/guardrails/hub/init.py?

Hi! Can you please try with v 0.4.2 and see if that yields the same issue? I did mess with related logic in 0.4.3 which came out on Tuesday