Vishal

Results 13 issues of Vishal

#### Summary Include participants in Recent, Saved and Pinned APIs responses. #### Ticket Link Fixes https://mattermost.atlassian.net/browse/MM-44796 #### Release Note ```release-note * Fixed the following 3 APIs to populate the "participants"...

2: Dev Review
3: QA Review
release-note

#### Summary Do not show files, past the set cloud plan's limit. #### Ticket Link JIRA - https://mattermost.atlassian.net/browse/MM-44489 #### Release Note ```release-note * Updated the Files search and get APIs...

2: Dev Review
Do Not Merge
3: QA Review
release-note

#### Summary `Order` field may contain an extra post id in case, `all` or `lastUnreadPostId` is filtered out as per the cloud plan's limit. This extra `Id` then cause this...

2: Dev Review
3: QA Review
release-note

#### Summary Add `Limit` on fetched records #### Ticket Link JIRA - https://mattermost.atlassian.net/browse/MM-45801 #### Release Note ```release-note NONE ```

2: Dev Review
release-note-none

#### Summary Add `First-Inaccessible-File-Time` response-403-header for getFile APIs, which indicates if files are inaccessible due to the cloud plan's limit. #### Ticket Link JIRA - https://mattermost.atlassian.net/browse/MM-44489 Depends on this server...

2: Dev Review
Do Not Merge/Awaiting PR

#### Summary Fix auto-respond message #### Ticket Link JIRA - https://mattermost.atlassian.net/browse/MM-46644 #### Release Note ```release-note NONE ```

2: Dev Review
3: QA Review
CherryPick/Approved
release-note-none

#### Summary Current system is stuck in a cyclic dependency to make the SAML metadata fetch request and saving the config. This allows to fetch the metadata without a need...

3: QA Review
Setup Cloud Test Server
release-note

**Describe the bug** Calling `run` with the Mixtral model - `mistral.mixtral-8x7b-instruct-v0:1` is failing with the following error message: `Could not inference Amazon Bedrock model mistral.mixtral-8x7b-instruct-v0:1 due: An error occurred (ValidationException)...

bug

ALLOWED_PARAMS has `max_tokens` but generation_kwargs was using `max_gen_len`. Closes Issue : https://github.com/deepset-ai/haystack-core-integrations/issues/741

integration:amazon-bedrock

MistralChatAdapter's ALLOWED_PARAMS has `max_tokens` but generation_kwargs is using `max_gen_len`. Because of this discrepancy, `max_tokens` limit is set to the default `512` whenever running the model. - Haystack version: 2.1.2 -...

bug