v2.0.1

Release Notes

Groups

Resolved Issues

• Fixed: Administrators who aren’t group members may be shown in the Group Moderation table. While they technically have access to the group, their inclusion in the Group Moderators table may cause confusion among members. (588)

Threads

New Features

• PingPong will attempt to generate a thread title while creating a thread. In case the context is not enough, title generation will be retried when subsequent messages are sent. (581)
• The maximum number of thread uploads is now set to 20 for both File Search and Code Interpreter. (585)

Resolved Issues

• Fixed: Document file uploads may be uploaded as both File Search and Code Interpreter resources, regardless of the thread’s capabilities. (592)
• Fixed: Images that are compatible with Code Interpreter may be uploaded as a Code Interpreter resource, regardless of the thread’s capabilities. (592)
• Fixed: When the Code Interpreter file limit is reached, users may still be allowed to select Code Interpreter-compatible images for upload. However, the file upload would still fail, and an informative error message would be displayed to the user. Users are now informed that they can only upload additional .webp images when the document limit is reached in a thread with Code Interpreter capabilities. FileUpload does not allow additional Code Interpreter-compatible image uploads only as Vision attachments because this would confuse users, as they would be unsure which image files are available in Code Interpreter. (592)

Deployment Information

Schema Upgrade	Migration Script	Permissions Update	Task Definition Update	Configuration Update
No	No	No	No	No

Deployment Details

N/A

Related PRs

• Bump werkzeug from 3.0.3 to 3.0.6 in the pip group across 1 directory by @dependabot in #579
• Generate title for conversation when the user starts a thread by @ekassos in #590
• Fix: Do not show admin information in Group Moderators table for users who are not members of a group by @ekassos in #591
• Update file upload limits in threads & other bug fixes by @ekassos in #592

Full Changelog: 468-srv122-web93...472-srv125-web94

v2.0

Release Notes

General

New Features

• Users will see more informative error messages across the app, especially when their request is invalid (e.g. when trying to save an assistant with an empty name). (266)

Assistants

New Features

• Assistants now support up to 100 uploaded documents for File Search, two times the previous limit. (576)
• Users can now set a custom temperature for any assistant. (577)

Groups

New Features

• Moderators will now see an informative warning with next steps in the Manage Group page when a member of their group encounters an error due to Rate Limiting by OpenAI. The warning will be displayed for 7 days after the last Rate Limiting error encountered. (567)
• Users will now see a list of Moderator display names and email addresses in a new "Group Moderators" section in the View Group page. (575)

Resolved Issues

• Fixed: The Export Threads option might not be available for some Moderators, even when they have the necessary permissions. (586)
• Fixed: Manually-added users are always invited as Members. (568)

Threads

New Features

Chat Input UI

• The Chat Input interface has a new look that enables better error and file attachment presentation. (574)

Uploads

• PingPong now validates the number of document and image attachments uploaded in a single thread message. Specifically, PingPong will adhere to OpenAI’s 10 document attachment file count limit and display specific helpers on the upload button to assist users in understanding the upload limits. (556)
• PingPong will now monitor the total number of document attachments uploaded across the entire thread to adhere to OpenAI’s file count limits. Users can conveniently view the total number of File Search and Code Interpreter files uploaded in a popup above the File Upload button, along with the maximum permitted count. When either limit is surpassed, the File Upload button is disabled until some attachments uploaded in the current or previous messages are deleted. (301)
• The File Upload button maintains a separate count for image attachments, enabling users to upload up to 10 image attachments per message. Users can continue uploading image attachments even after reaching the document attachment limit, and vice versa. (556)
• Improvements in attachment management when sending a message enables the upload of up to twice as many document attachments as before. (570)

Sending Messages

• When creating a new thread, PingPong will wait for the thread and message to be successfully created before erasing the user’s input. This modification enables users to rectify errors in their messages without the need to retype and re-upload the entire content. (570)
• When sending a message in an existing thread, PingPong will restore the user's message content if an error occurred before the message was successfully sent to OpenAI and added to the thread history. (574)
• Users no longer need refresh the thread page to get an accurate account of the current thread state after sending a message fails. (574)

Streaming Messages

• In case of a server error from OpenAI while streaming a message response, a new error message prompts users to attempt the request again, or refer to PingPong’s newly launched Status page. (570)
• When a thread response cannot be generated by OpenAI due to Rate Limiting, PingPong will display an informative error message with next steps for users. (567)

Error handling & Support

• Users will see more informative error messages when creating a thread, sending a message, or streaming a response, including specific errors generated by OpenAI. (570)
• Users will now see a list of Moderator display names and email addresses in a new "Group Moderators" table when they click the "Moderators" hyperlink in the Privacy Disclaimer footnote of every thread page. (575)

Resolved Issues

• Fixed: Error messages generated when streaming a thread response might not display properly to users. (567, 570)
• Fixed: Users might be unable to re-upload the same file after deleting it from their uploaded attachments list. (570)
• Fixed: Trying to attach more than 10 files to a single thread message might result in an error when sending that message. (556)
• Fixed: Thread vector stores created by PingPong were not attached as tool resources to the relevant thread. This resulted in OAI creating a second vector store with a set (7 day) expiration date, with threads "locking" after 7 days of inactivity. (573)

Deployment Information

Schema Upgrade	Migration Script	Permissions Update	Task Definition Update	Configuration Update
YES	No	No	No	No

Deployment Details

• Schema Upgrade: New last_rate_limited_at column in Class table.
• Schema Upgrade: New temperature column in Assistants table.

Related PRs

• Patch: Show Export threads option to Moderators in the UI by @ekassos in #566
• Revamp ChatInput's FileUpload & other FileUpload-related fixes and error handling improvements by @ekassos in #570
• Fix: Manually-added users always invited as Members by @ekassos in #568
• Add Rate Limit notice in Threads and Manage Group page by @ekassos in #567
• Fix: Thread-related Vector Stores are not attached to thread by @ekassos in #573
• Temperature in Assistant Manage Page by @ekassos in #577
• Allow up to 100 files to be uploaded when creating or updating an Assistant by @ekassos in #576
• Add Moderator tables in ChatInput and View Group page by @ekassos in #575
• ChatInput Revamp by @ekassos in #574

Full Changelog: 460-srv117-web86...468-srv122-web93

v1.5.1

Release Notes

Groups

New Features

• Users are now required to log in to PingPong before downloading a completed thread export. PingPong will also verify that the requesting user matches the user that initiated the export. (535)
• Any moderator can now initiate a threads export. (535)

Navigation

New Features

• New Issue and Maintenance banners will communicate important status updates from our new status page (https://pingpong-hks.statuspage.io/). (565)

Threads

Resolved Issues

• Fixed: Users who no longer have permissions to view and interact with a previously published assistant should not be able to continue a conversation in an existing thread. (560)
• Fixed: A thread might fail to load when the thread name generation fails due to rate limits. (562)

Known Issues

• Trying to attach more than 10 files to a single thread message might result in an error when sending that message. (556)
  Workaround: Upload files in batches over multiple messages.

Deployment Information

Schema Upgrade	Migration Script	Permissions Update	Task Definition Update	Configuration Update
No	No	No	No	YES

Deployment Details

• Configuration Update: presigned_url_expiration is replaced by download_link_expiration and defines how long the download token emailed to the user will be valid for.

Related PRs

• Fix: Users should not be able to interact with assistants they no longer have permissions to view by @ekassos in #561
• Fix: generate_name might be rate-limited by @ekassos in #563
• Add status embed for incidents and maintenance by @ekassos in #565
• Require user auth to download data export by @ekassos in #564

Full Changelog: 456-srv114-web83...460-srv117-web86

v1.5

Release Notes

Admin Page

New Features

• The sidebar panel on the Admin Page showing various system and usage statistics has been redesigned. Users can now scroll trough the list of statistics. (558)

Groups

New Features

• A redesigned interface for inviting users simplifies the process of manually adding users to a PingPong group. (554)
• The new interface for inviting users supports email formats specified in RFC5322 and other email-related RFCs. (491)
• After entering a list of emails separated by new lines or commas, PingPong will now verify emails entered and match them with existing PingPong users. Invalid emails have to be corrected or deleted before adding new members to a group. (287, 289)
• A display name can now be specified for new members before adding them to a group. An editable display name is automatically added when the email address format specifies one. (491)
• Encountering an error when inviting a specific user to a group will no longer invalidate the entire request, requiring all users to be invited again. A confirmation screen details which users have been successfully invited and displays any errors encountered for individual users. (554)

Threads

Known Issues

• Trying to attach more than 10 files to a single thread message might result in an error when sending that message. (556)
  Workaround: Upload files in batches over multiple messages.

Deployment Information

Schema Upgrade	Migration Script	Permissions Update	Task Definition Update
No	No	No	No

Deployment Details

N/A

Related PRs

• Add New Users workflow revamp by @ekassos in #554
• Fix: Formatting for Admin Stats by @ekassos in #558
• Patch: Do not check for deliverability when adding users by @ekassos in #559

Full Changelog: 453-srv112-web81...456-srv114-web83

v1.4.4

Release Notes

Admin Page

New Features

• A new sidebar panel on the Admin Page allows administrators to view various system and usage statistics. (555)

Threads

New Features

• Thread names are now generated after the user has sent a third message in the conversation to allow for more informative titling. Untitled threads will appear as "New Conversation" in the UI. (553)
• A new thread titling generation prompt should lead to more succinct titles and better performance. The model used has also been upgraded from gpt-3.5-turbo to gpt-4o-mini for increased performance. (553)

Deployment Information

Schema Upgrade	Migration Script	Permissions Update	Task Definition Update
YES	No	No	No

Deployment Details

• DB Schema Upgrade: eebdd27edf02 -> 8e800c07b278, Threads: New user message count column and make name nullable

Related PRs

• Regenerate title for chat thread when we have more information by @ekassos in #553
• Add usage statistics in Admin page sidebar by @ekassos in #555

Full Changelog: 451-srv110-web79...453-srv112-web81

v1.4.3

Release Notes

Groups — Creating & Managing

Resolved Issues

• Thread Exports might fail to get generated for some users. (549)

Breaking Changes

• Because of the deprecated uvicorn.workers module, the server task definitions need to be updated on ECS before deployment. (547)

Related PRs

• Update uvicorn dependency by @ekassos in #547
• Fix: Missing get_file_search_files_assistant after #543 by @ekassos in #551

Full Changelog: 449-srv108-web79...451-srv110-web79

v1.4.2

Release Notes

Assistants

Resolved Issues

• Fixed: An assistant prompt containing multiple backticks (`) might lead to an error when saving the assistant. (404)

Canvas Integration

New Features

• Account disconnects and other audit-worthy actions by users are now documented in the server logs. (539)

Logging In & Navigation

New Features

• New simplifications of the log in workflow should make it easier for users to log in. When users use an expired link to log in to PingPong, a new log in link will be sent to their email. (489)

Threads

New Features

• Users can now see information about files they upload to a thread right below the message they attached them to.
• Users can now delete individual files they uploaded to a thread after they send a message from the new in-line file information interface.

Related PRs

• Update rollup and workflows by @jnu in #542
• Canvas Sync: Log disconnects and other audit-worthy actions by users by @ekassos in #539
• Way to see and manage thread-specific file uploads by @ekassos in #543
• Finalize user log-in flow by @ekassos in #546

Full Changelog: 445-srv105-web76...449-srv108-web79

v1.4.1

Release Notes

Assistants

New Features

• Moderators can now edit any assistant they have access to, including publishing and deleting said assistants in private groups. (496)

Known Issues

• An assistant prompt containing multiple backticks (`) might lead to an error when saving the assistant. (404)
  Workaround: Replace backticks with other marks in the assistant prompt before saving.

Groups

Resolved Issues

• Fixed: The Export Threads instructions popup might provide the wrong expiration time for the generated Export Threads download link.

Notes

• Thread Exports now feature a new format, with shorted user id hashes and the message id column no longer included. Please re-export your threads if you would like to make comparisons between Thread Exports.

Related PRs

• Fix: Export Threads popup might provide the wrong expiration time by @ekassos in #533
• Adjust Export Threads format by @ekassos in #537
• Allow Moderators edit any assistant they have access to by @ekassos in #534

Full Changelog: 442-srv102-web75...445-srv105-web76

v1.4

Release Notes

About Page

New Features

• The Support form on the About page now includes a clear disclaimer that the form is meant for app feedback and bug reports. (530)

Assistants

Known Issues

• An assistant prompt containing multiple backticks (`) might lead to an error when saving the assistant. (404)
  Workaround: Replace backticks with other marks in the assistant prompt before saving.

Groups

New Features

• Institutional and Root Administrators can now request an export of all threads in CSV format in a Group. The export will be delivered in the Admin's email with a link to download the file that will remain active for 12 hours. Export files are deleted after the download links expire. (452)

Resolved Issues

• Fixed: Users might be unable to delete groups when there is no API key set. (501)
• Fixed: In the Users list, the user role box for users with the Administrator role might appear empty when viewed by users with the Administrator role. This issue does not affect users without the Administrator role. (512)

Threads

Resolved Issues

• Fixed: Threads with incomplete runs might fail to load. (472)
• Fixed: Threads where the model incorrectly returns empty annotations might fail to load. (517)
• Fixed: Thread timestamps for last edits might be inaccurate. (383)

Related PRs

• Fix: Threads with empty annotations might fail to load by @ekassos in #525
• Fix: Users might be unable to delete groups when there is no API key set by @ekassos in #528
• OAI Thread API: Handle incomplete run status by @ekassos in #526
• Fix: Thread timestamps are updated when the associated assistant is updated by @ekassos in #529
• Add disclaimer about the type of help we can offer by @ekassos in #530
• Fix: Role not displaying correctly for administrators by @ekassos in #527
• Allow for CSV export of thread data by @ekassos in #519

Full Changelog: 435-srv97-web70...442-srv102-web75

v1.3.3

Release Notes

Assistants

Known Issues

• An assistant prompt containing multiple backticks (`) might lead to an error when saving the assistant. (404)
  Workaround: Replace backticks with other marks in the assistant prompt before saving.

Groups

Known Issues

• Users might be unable to delete groups when there is no API key set. (501)
  Workaround: Set an API key for the group before deleting it.
• In the Users list, the user role box for users with the Administrator role might appear empty when viewed by users with the Administrator role. This issue does not affect users without the Administrator role. (512)

Logging In & Navigation

Resolved Issues

• Fixed: Logging out might lead users to the login page with the /logout page as the forward destination. (514)

Threads

Resolved Issues

• Fixed: Thread Archives might fail to load when filtering for a specific group. (495)
• Fixed: Thread Archives or Recent Threads might fail to load all threads. (495)

Known Issues

• Threads with incomplete runs might fail to load. (472)
  Workaround: Start a new thread.
• Threads where the model incorrectly returns empty annotations might fail to load. (517)
  Workaround: Start a new thread.
• Thread timestamps for last edits might be inaccurate. (383)

Notes

• Thread Archives or Recent Threads might take longer to load than users might be used to, especially if they have access to a large number of threads.

Related PRs

• New workflow to push images on staging from PRs by @ekassos in #518
• Test-On-Staging: More granular control by @ekassos in #521
• Bump vite from 5.4.3 to 5.4.6 in /web/pingpong in the npm_and_yarn group across 1 directory by @dependabot in #520
• Fix: Logging out might lead users to the login page with the /logout page as the forward destination by @ekassos in #523
• Fix lock file by @jnu in #524

Full Changelog: 432-srv97-web67...435-srv97-web70