[pull] main from HeyPuter:main #34
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| description: Type the version of Puter you were using when you encountered the bug | ||
| label: Puter version | ||
| description: Type the version of Puter you were using when you encountered the bug. This is not required. If you can't access the version, then continue without adding the version number. | ||
| placeholder: Click the profile button on the top-right, then "Settings". The version number will be printed at the bottom |
This commit also adds a new check to verify that the app which owns the entity being edited matches. Previously this was not necessary because a read on the same entity would have always performed the same check and caused this operation to stop early. (now that an app may have permission to read entities created by other apps, this is no longer the case.)
* attempt to fix turnstile auth
Permission endpoints would trigger 500 errors in cases where the request did not have correct types for values in the request body. This migrates all of these endpoints to use the new `validate_fields` function, which is intended to make validation of fields clearer and more consistent.
The vitest test suite can import different states of the same module, so this value was very helpful in determining that this was happening and eventually the cause.
* chore: add typedefs for puter.js * types: fix puter-js type exports
This bug took a long time to diagnose, so I also made an async/await wrapper around #postMessageWithCallback called #postMessageAsync so that similar promise resolving errors are less likely here in the future.
This commit adds methods to request standard directories like the Desktop, Documents, Pictures, or Videos directory. Additionally, the message displayed when permission for these directories is requested is easier to read.
It calls requestPermission on the UI module. The method on the UI model needs to still exist because the UI module is tightly-coupled with IPC. A refactor of the IPC mechanism on the puter.js side could solve this.
* fix: togetherAi metering * npm: publish new readme * Revert "fix: togetherAi metering" This reverts commit 2b3eb76.
* Add dashboard UI and routing support Introduces a new Dashboard UI component with sidebar navigation and user options. Updates backend routing to redirect /dashboard to the root path. Integrates dashboard mode detection and initialization in the GUI, including responsive styles and logic to open the dashboard or desktop as appropriate. * Improve dashboard user menu and UI behavior Added support for multiple logged-in users, session saving for temporary users, and improved context menu options in the dashboard. Updated CSS for user button state and adjusted font size for signup terms. Changed dashboard initialization to use UIDashboard instead of UIWindow. * Add dynamic apps section to dashboard UI * Add specific class for dashboard apps section * Refactor dashboard tabs into modular components * Update style.css * Add Developers menu and improve signup window behavior Added a 'Developers' menu item to the dashboard linking to developer.puter.com. Updated login and signup window logic to ensure the signup window opens centered and dominant, improving user experience when transitioning from login to signup. * Update UIWindowLogin.js * Refactor apps tab UI and improve app card interaction
* Add 'Open in AI' option to item context menus * Add new AI-related English translations
Added README.md for the Puter GUI with details on structure, development, contributing, and resources.
Bumps [qs](https://github.com/ljharb/qs) to 6.14.1 and updates ancestor dependency [express](https://github.com/expressjs/express). These dependencies need to be updated together. Updates `qs` from 6.13.0 to 6.14.1 - [Changelog](https://github.com/ljharb/qs/blob/main/CHANGELOG.md) - [Commits](ljharb/qs@v6.13.0...v6.14.1) Updates `express` from 4.21.2 to 4.22.1 - [Release notes](https://github.com/expressjs/express/releases) - [Changelog](https://github.com/expressjs/express/blob/v4.22.1/History.md) - [Commits](expressjs/express@4.21.2...v4.22.1) --- updated-dependencies: - dependency-name: qs dependency-version: 6.14.1 dependency-type: indirect - dependency-name: express dependency-version: 4.22.1 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
There was a configuration parameter for this but it isn't being used and has the incorrect name in `config.js`. I decided to keep the old check here anyway because having support to configure a lower size limit could come in handy. I set the limit to 2MiB through the following logic: - largest icon size I've ever heard of is 512px - 512*512*4 (4 color channels) is 1048576 (1MiB) - increase to next MiB just to be safe
* model naming singularity * model singularity pt2 * Remove incorrect assumption check which breaks openrouter:openai/gpt-5-image
Based on a stack trace from production and manual static analysis, it appears that a race condition occurs within hashing_stream intermittently. The conditions that cause this issue might be heavy backpressure. The source stream emits the 'end' event before stream.Transform's transform callback has had a chance to process all of the chunks, which results in an incorrect order in calling methods on the `typeof crypto.createHash()` object. It would appear that `source.pipe(stream)` is not able to propagate errors from Transform because the chain was simply broken and upload would get stuck (if this was indeed the cause of upload getting stuck, which seems likely but not conclusive)
Introduces thumbnail generation for image files during upload operations. Thumbnails are generated client-side if enabled via the `generateThumbnails` option, and are included in file metadata and operation payloads. This enhances file previews and user experience in the file system.
* Add README for Puter localization and setup This README provides an overview of Puter, including installation instructions, system requirements, and support information. * Update README.od.md --------- Co-authored-by: Nariman Jelveh <nj@puter.com>
Bumps [qs](https://github.com/ljharb/qs) and [body-parser](https://github.com/expressjs/body-parser). These dependencies needed to be updated together. Updates `qs` from 6.13.0 to 6.14.1 - [Changelog](https://github.com/ljharb/qs/blob/main/CHANGELOG.md) - [Commits](ljharb/qs@v6.13.0...v6.14.1) Updates `body-parser` from 1.20.3 to 1.20.4 - [Release notes](https://github.com/expressjs/body-parser/releases) - [Changelog](https://github.com/expressjs/body-parser/blob/master/HISTORY.md) - [Commits](expressjs/body-parser@1.20.3...1.20.4) --- updated-dependencies: - dependency-name: qs dependency-version: 6.14.1 dependency-type: indirect - dependency-name: body-parser dependency-version: 1.20.4 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
Introduced a new translation key 'captcha_required' with the message 'Please complete the CAPTCHA verification' in the English locale file.
* Improve UI for App Deployment Options in Dev Center - Added CSS styling for deployment option cards - Implemented active state switching between deployment methods with guardrails - Abstracted saveEditApp for reuse across Deploy and Edit tabs - Added error handling for invalid URLs in the Deploy tab * updated mode's description and fixed function's error * updated by npm install * Revert "updated by npm install" This reverts commit 82cd962. * in url mode the deploy button is enabled by default
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
15 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot]
Can you help keep this open source service alive? 💖 Please sponsor : )