blender/blender
148
473
Fork 695
Code Issues 6.7k Pull Requests 897 Projects 18 Wiki Activity

Extensions Platform: beta launch #119521

New Issue
Closed
opened 2024-03-15 15:24:42 +01:00 by Dalai Felinto · 7 comments
Dalai Felinto commented 2024-03-15 15:24:42 +01:00
Owner
Copy Link

Although the extensions platform alpha release is finished there are still a few tasks we want to tackle before 4.2 Beta.

Show-stoppers

Blender:

  • None.

Server-side:

Documentation:

  • Provide guidance for where extensions should store presets (existing conventions for add-ons may not make sense).
  • Document the process of bundling extensions in a "System" repository.
  • Create a task with all 4.1 add-ons and their status (checkbox if tested, comment if not working): extensions/automation-scripts#1
  • Update user manual add-ons part + remove references to extensions being experimental and 4.2.
  • Update https://developer.blender.org/docs/
  • Release Notes needs love.

Bugs:

  • None.

Bugs to investigate

  • The preset operator uses eval() to apply a preset, therefore if you use __package__ it returns the package where the operator lives. Document how this can be solved.
  • Search could include extension author and maintainer.

Good to have

Blender:

  • Flag third-party Python modules Blender includes (so their wheel is never installed). #123189
  • Support dragging multiple .zip with multiple extensions.
  • Handle add_ons core preferences #121830
  • Install from disk from the menu could pre-search for the extension name, so its settings can be set.
  • Renaming a module should rename the directory #123683
  • Support for repositories blocklist, proposal #124954

Archived (done) tasks)

  • Support clearing a repository lock held by other session #122135
  • Including wheels on [build.generated] when using --split-platforms #124242
  • Dropping a URL from an unknown repository shows a button "Add Repository..." which works but does not close the popup, see: #124098. 11b1919bcf
  • Dropping an extension from the filesystem can detect and set the remote repository as default (if the ZIP file is associated with a remote repository).
  • The build & validate sub-commands should validate tags as well #123986
  • Panel expand button is non-functional when zoomed in #123807
  • Blender let me install an incompatible extension #123677
  • Add-ons in local repositories do not install wheels #123645
  • Figure out how to handle wheels and System add-ons (related: #123645)
  • Don't save repository when Install from Disk (from the UI) #123710
  • Bring back the button to visit the website inside the extension description #123689
  • Using the wrong URL for extensions #123706
  • Separate Enabled/Disabled/Available in separate sections (separated by Labels) #123660
  • Error when installing from disk #123676
  • Error (briefly) when I first get data from the server #123681
  • Change repository URL or access token should "Check for Updates" #123682
  • Setting the default theme manually breaks the Extension UI #123657
  • Helper operator to convert the 4.1 user preferences to 4.2 #122303
  • Create a bundle with the 4.1 add-ons as extensions #122147
  • Support version range and platforms from the download URLs
  • Bring add-ons tab back #122735, PR !123420.
  • Install (to Remote Repository) from Disk #122302
  • Fix error message when trying to install an unsupported package #123241
  • First time dialogs and setups #120665
  • Throw error if trying to install extension containing .git/.svn/...
  • blender_version_max should be non-inclusive: infrastructure/extensions-website#183
  • Portable bundle #122512
    • Support "System" repositories dc9430c480.
    • Prevent conflicts between User/System extensions 939e4b2efc.
    • Support read-only system repositories. a24add4a66
  • Extension support bpy.utils.register_submodule_factory #122769 6450141a18.
  • Check for Update operator should be active for Local Repositories (the operator, NOT the property) - in this case it works more like a refresh.
  • Sub-panels in popups don't work when zoomed in/out #122411.
  • Easy installer for legacy add-ons !122727
  • Support new permissions schema on manifest
    • server_generate
    • build_package
    • validate
    • support old schema for now
  • Extension UI cleanup (patch by Pablo) !122726
  • Stop using LZMA #122710
  • Pop-over to filter extensions based on their tags.
  • API for screen-casting
  • The undocumented (advanced) Online Local Repositories should point to a .json, not to a folder.
  • New welcome message with URL + Allow Online Access !122511
  • Update install via dragging URL to support "Allow Online Access" when offline.
  • Remove splashscreen messages (exception: --offline-mode message)
  • Status bar extensions/offline info:
  • Populate bpy.context.window_manager.extensions_update
  • Show Available Updates on status bar !122413
  • Update Listing automatically when visiting Preferences > Extensions
  • Only show offline mode if launched with --offline-mode !122392.
  • Pass 'platform' as part of the query infrastructure/extensions-website#74 !122229
  • Check for Update on startup is only working for blender_org? (issues redoing this one, can add this item back if it's a problem).
  • Dragging to install an extension from a disabled repository fails silently #120303
  • Support "secret" option for remote repositories to pass access tokens to servers.
    171319d9ef.
  • Allow Online Access and --offline-mode).
    See PR !121994. (57c023d580)
  • Add trailing slash to extensions URL: https://extensions.blender.org/api/v1/extensions/ to avoid unnecessary redirect. (f7f23541f0)
  • Show add-ons specific permissions on Blender. e0b47f78e8
  • Local cache still stores .zip files. (blender/blender-addons-contrib@a1b0f1b1f4)
  • Disabling "Local Cache" should remove local cache when running an update. (blender/blender-addons-contrib@a1b0f1b1f4)
  • Removing an extension should remove it's local cache. (blender/blender-addons-contrib@a1b0f1b1f4)
  • Add-ons fail to enable silently when installed from disk (e.g., visibility handler).
  • Investigate why visibility handler doesn't work as extension (it works if you Install as Legacy Add-on).
  • Investigate why Co doesn't work as extension (it works if you extract the .py and Install as Legacy Add-on).
  • Installing an Extension via dragging has no feedback #119500
  • Custom directory potential issue #119481 (f64f3e8524)
  • Stop with the bl_info warning (0b13d1f31a).
  • Extensions UI still showing even when Developers Extra is disabled (0d2c4df346).
  • Uninstalling a theme extension should remove it #120289
  • Mode "Show Development Utilities" to its own Experimental Flag.
  • Filter option to show only Update Available #120609
  • Splashscreen and Available Extensions Update #120612
  • Repository option to "Check for Updates on Startup" #120613
  • Unify install from disk (installing legacy add-on should go via install from disk as well).
  • Archive addons_contribs (wait with this… ).
  • Open devtalk Beta feedback thread.
  • Support for bundling wheels (.whl) in packages #119681
Although the extensions platform [alpha release is finished](https://devtalk.blender.org/t/extensions-platform-alpha-launch/33342) there are still a few tasks we want to tackle before 4.2 Beta. ## Show-stoppers Blender: - *None.* Server-side: * [x] Back-end tasks: https://projects.blender.org/infrastructure/extensions-website/issues/70 Documentation: - [ ] Provide guidance for where extensions should store presets (existing conventions for add-ons may not make sense). - [ ] Update user manual add-ons part + remove references to extensions being experimental and 4.2. - [ ] Update https://developer.blender.org/docs/ - [ ] [Release Notes](https://developer.blender.org/docs/release_notes/4.2/python_api/#extensions) needs love. - [x] Document the process of bundling extensions in a "System" repository. - [x] Create a task with all 4.1 add-ons and their status (checkbox if tested, comment if not working): https://projects.blender.org/extensions/automation-scripts/issues/1 - [ ] Update user manual add-ons part + remove references to extensions being experimental and 4.2. - [ ] Update https://developer.blender.org/docs/ - [ ] [Release Notes](https://developer.blender.org/docs/release_notes/4.2/python_api/#extensions) needs love. ## Bugs: - *None.* ## Bugs to investigate - [ ] The [preset operator](https://projects.blender.org/blender/blender/src/branch/main/scripts/startup/bl_operators/presets.py) uses eval() to apply a preset, therefore if you use `__package__` it returns the package where the operator lives. Document how this can be solved. - [ ] Search could include extension author and maintainer. ## Good to have Blender: - [ ] Flag third-party Python modules Blender includes (so their wheel is never installed). #123189 - [ ] Support dragging multiple .zip with multiple extensions. - [ ] Handle add_ons core preferences #121830 - [ ] Install from disk from the menu could pre-search for the extension name, so its settings can be set. - [ ] Renaming a module should rename the directory #123683 - [ ] Support for repositories `blocklist`, proposal #124954 ## Archived (done) tasks) - [x] Support clearing a repository lock held by other session #122135 - [x] Including wheels on [build.generated] when using --split-platforms #124242 - [x] Dropping a URL from an unknown repository shows a button "Add Repository..." which works but does not close the popup, see: #124098. 11b1919bcfe3a81283f3e81223ddc4dcc0525a0f - [x] Dropping an extension from the filesystem can detect and set the remote repository as default (if the ZIP file is associated with a remote repository). - [x] The `build` & `validate` sub-commands should validate tags as well #123986 - [x] Panel expand button is non-functional when zoomed in #123807 - [x] Blender let me install an incompatible extension #123677 - [x] Add-ons in local repositories do not install wheels #123645 - [x] Figure out how to handle wheels and System add-ons (related: #123645) - [x] Don't save repository when Install from Disk (from the UI) #123710 - [x] Bring back the button to visit the website inside the extension description #123689 - [x] Using the wrong URL for extensions #123706 - [x] Separate Enabled/Disabled/Available in separate sections (separated by Labels) #123660 - [x] Error when installing from disk #123676 - [x] Error (briefly) when I first get data from the server #123681 - [x] Change repository URL or access token should "Check for Updates" #123682 - [x] Setting the default theme manually breaks the Extension UI #123657 - [x] Helper operator to convert the 4.1 user preferences to 4.2 #122303 - [x] Create a bundle with the 4.1 add-ons as extensions #122147 - [x] [Support version range and platforms from the download URLs](https://projects.blender.org/infrastructure/extensions-website/issues/190) - [x] Bring add-ons tab back #122735, PR !123420. - [x] Install (to Remote Repository) from Disk #122302 - [x] Fix error message when trying to install an unsupported package #123241 - First time dialogs and setups #120665 - [x] Improved error messages: !123242 - [x] [Throw error if trying to install extension containing .git/.svn/...](https://projects.blender.org/infrastructure/extensions-website/issues/175#issuecomment-1212781) - [x] `blender_version_max` should be non-inclusive: https://projects.blender.org/infrastructure/extensions-website/issues/183 - [x] Portable bundle #122512 - [x] Support "System" repositories dc9430c48039bda36c1ba052f00c20e554f6aef0. - [x] Prevent conflicts between User/System extensions 939e4b2efcb3d8a2d4481341866ef0fb2e6d4aa6. - [x] Support read-only system repositories. a24add4a669a9281fcde4e7bfc3fbb2ac1093e18 - [x] Extension support `bpy.utils.register_submodule_factory` #122769 6450141a188567eadcf544e1f0cd08ea66fcf033. - [x] Check for Update operator should be active for Local Repositories (the operator, NOT the property) - in this case it works more like a refresh. - [x] Sub-panels in popups don't work when zoomed in/out #122411. - [x] Easy installer for legacy add-ons !122727 - [x] [Support new permissions schema on manifest](https://projects.blender.org/infrastructure/extensions-website/issues/166) - [x] server_generate - [x] build_package - [x] validate - [x] support old schema for now - [x] Extension UI cleanup (patch by Pablo) !122726 - [x] Stop using LZMA #122710 - [x] Pop-over to filter extensions based on their tags. - [x] API for screen-casting - [x] The undocumented (advanced) Online Local Repositories should point to a .json, not to a folder. - [x] New welcome message with URL + Allow Online Access !122511 - [x] Update install via dragging URL to support "Allow Online Access" when offline. - [x] Remove splashscreen messages (exception: --offline-mode message) - [x] Status bar extensions/offline info: - [x] Populate bpy.context.window_manager.extensions_update - [x] Show Available Updates on status bar !122413 - [x] Update Listing automatically when visiting Preferences > Extensions - [x] Only show offline mode if launched with --offline-mode !122392. - [x] Pass 'platform' as part of the query https://projects.blender.org/infrastructure/extensions-website/issues/74 !122229 - [x] Check for Update on startup is only working for blender_org? (issues redoing this one, can add this item back if it's a problem). - [x] Dragging to install an extension from a disabled repository fails silently #120303 - [x] Support "secret" option for remote repositories to pass access tokens to servers. 171319d9efa8ae2d159533c0d485e5a0c2a9afc6. - [x] Allow Online Access and `--offline-mode`). See PR !121994. (57c023d5809e3e14811eb4faf10c0b2158da20a2) - [x] Add trailing slash to extensions URL: `https://extensions.blender.org/api/v1/extensions/` to avoid unnecessary redirect. (f7f23541f097873b640d1a4b74d599b021c09c9b) - [x] Show add-ons specific permissions on Blender. e0b47f78e8aaf9eefd816441eaa7086ce0acf259 - [x] Local cache still stores `.zip` files. (blender/blender-addons-contrib@a1b0f1b1f4ee807c09f278de2c08ff0a1afe8821) - [x] Disabling "Local Cache" should remove local cache when running an update. (blender/blender-addons-contrib@a1b0f1b1f4ee807c09f278de2c08ff0a1afe8821) - [x] Removing an extension should remove it's local cache. (blender/blender-addons-contrib@a1b0f1b1f4ee807c09f278de2c08ff0a1afe8821) - [x] Add-ons fail to enable silently when installed from disk (e.g., [visibility handler](https://extensions.blender.org/approval-queue/visibility-handler/)). - [x] Investigate why [visibility handler](https://extensions.blender.org/approval-queue/visibility-handler/) doesn't work as extension (it works if you Install as Legacy Add-on). - [x] Investigate why [Co](https://extensions.blender.org/approval-queue/co/) doesn't work as extension (it works if you extract the .py and Install as Legacy Add-on). - [x] Installing an Extension via dragging has no feedback #119500 - [x] Custom directory potential issue #119481 (f64f3e852416698d97c959f8ada10a5ccd44af6a) - [x] Stop with the `bl_info` warning (0b13d1f31a8c8e47def16abcc42f8c210fd50fce). - [x] Extensions UI still showing even when Developers Extra is disabled (0d2c4df346195ca7bff706ebfc9e85449f5d0c6a). - [x] Uninstalling a theme extension should remove it #120289 - [x] Mode "Show Development Utilities" to its own Experimental Flag. - [x] Filter option to show only Update Available #120609 - [x] Splashscreen and Available Extensions Update #120612 - [x] Repository option to "Check for Updates on Startup" #120613 - [x] ~~Unify install from disk (installing legacy add-on should go via install from disk as well).~~ - [x] Archive addons_contribs (wait with this… ). - [x] Open devtalk Beta feedback thread. - [x] Support for bundling wheels (`.whl`) in packages #119681
image.png
16 KiB
image.png
Dalai Felinto added the
Type
To Do
 label 2024-03-15 15:24:42 +01:00
Dalai Felinto added this to the Python API project 2024-03-15 15:24:45 +01:00
Demeter Dzadik commented 2024-05-21 21:46:04 +02:00
Member
Copy Link

Small things I noticed, let me know if I should make separate reports for any or all:

  • On the Submit page, the "guidelines" link is 404. Seems fixed.
  • Add-on preferences are a separate, disconnected box.
  • At first I wanted to add my add-on as a local repository, so I wouldn't have to zip it up and re-install it every time I work on it. But when I did this, the add-on's checkbox to enable it was grayed out.
  • When trying to use the Add Local Repository operator and then browsing a directory, the operation gets cancelled. It only works by typing/pasting in the directory path. I think this is happening because the file selector is in a pop-up panel, which is not a permanent UI element, so it disappears after choosing a directory, cancelling the operator.

Update: I tried 4.2 again after some time, and all of my issues seem to have been addressed. I'm really happy with how this project is going, great job guys.

Small things I noticed, let me know if I should make separate reports for any or all: - ~~On the [Submit](https://extensions.blender.org/submit/) page, the "guidelines" link is 404.~~ Seems fixed. - ~~Add-on preferences are a separate, disconnected box.~~ - ~~At first I wanted to add my add-on as a local repository, so I wouldn't have to zip it up and re-install it every time I work on it. But when I did this, the add-on's checkbox to enable it was grayed out.~~ - ~~When trying to use the Add Local Repository operator and then browsing a directory, the operation gets cancelled. It only works by typing/pasting in the directory path. I think this is happening because the file selector is in a pop-up panel, which is not a permanent UI element, so it disappears after choosing a directory, cancelling the operator.~~ Update: I tried 4.2 again after some time, and all of my issues seem to have been addressed. I'm really happy with how this project is going, great job guys.
image.png
67 KiB
2024-05-21 21-40-33.mp4
75 KiB
image.png
104 KiB
image.png image.png
Nika Kutsniashvili commented 2024-05-22 04:59:28 +02:00
Contributor
Copy Link

Add-on preferences are now a separate, disconnected box. This means the visual distinction between two different add-ons is now the same as the visual distinction between one add-on, and its own preferences. I suspect this was not intentional.

This was the case for add-ons too, and it's weird.
Is it possible to use proper panels for add-ons instead of weird boxes? Regular panels with headers and content like properties and modifiers. Than add-on preferences can be a subpanel which is opened by default

> Add-on preferences are now a separate, disconnected box. This means the visual distinction between two different add-ons is now the same as the visual distinction between one add-on, and its own preferences. I suspect this was not intentional. This was the case for add-ons too, and it's weird. Is it possible to use proper panels for add-ons instead of weird boxes? Regular panels with headers and content like properties and modifiers. Than add-on preferences can be a subpanel which is opened by default
👍 1
David Friedli commented 2024-05-23 16:41:07 +02:00
Copy Link

Hey there, i've noticed that automatic installation of bundled wheel files (added in#119681) seemingly doesn't work for extensions from local repositories. Is that expected behaviour?

Hey there, i've noticed that automatic installation of bundled wheel files (added inhttps://projects.blender.org/blender/blender/issues/119681) seemingly doesn't work for extensions from local repositories. Is that expected behaviour?
Dalai Felinto commented 2024-05-23 18:29:03 +02:00
Author
Owner
Copy Link

Hey there, i've noticed that automatic installation of bundled wheel files (added in#119681) seemingly doesn't work for extensions from local repositories. Is that expected behaviour?

Please report as a bug so we can investigate this further. It is supposed to work, but we will need more details from you. Feel free to reference me and campbell on it (@dfelinto + @ideasman42).

> Hey there, i've noticed that automatic installation of bundled wheel files (added inhttps://projects.blender.org/blender/blender/issues/119681) seemingly doesn't work for extensions from local repositories. Is that expected behaviour? Please report as a bug so we can investigate this further. It is supposed to work, but we will need more details from you. Feel free to reference me and campbell on it (@dfelinto + @ideasman42).
michael campbell commented 2024-06-16 15:37:08 +02:00
Copy Link

71,098 addon developers rely on Jacque Lucke's Blender extension for VSCode. Could Blender take over it's maintenance, as it no longer works with the new extension system, and Jacque no longer maintains it.

Maybe a checkbox in preferences to switch to extension mode, so addon developers can optionally continue maintaining legacy addons for users who are on older blender versions.

71,098 addon developers rely on Jacque Lucke's Blender extension for VSCode. Could Blender take over it's maintenance, as it no longer works with the new extension system, and Jacque no longer maintains it. Maybe a checkbox in preferences to switch to extension mode, so addon developers can optionally continue maintaining legacy addons for users who are on older blender versions.
👍 1 ❤️ 1
Campbell Barton commented 2024-07-15 02:30:54 +02:00
Owner
Copy Link

@dfelinto there was a proposal for locking in this task:

  • Users should not be locked out of updating extensions
    • If the lock is from the same session, just show a info/warning about waiting/trying later.
    • If the lock is from another session, popup asking if users want to delete lock (and manually try again).
    • (related: Extensions: lock is held by other session #122135)None.

I've committed support to "Force Unlock" a repository and removed the text above, but it works differently to the steps you've listed.

  • The option to force unlock a repository is available in the repository popover.
  • This option is typically greyed out, the tooltip includes the reasons, currently they are:
    • The repository is not locked.
    • The repository is locked by this blender session.
  • Force unlocking shows a confirm/cancel popup (defaulting to cancel) with some information including the age of the lock and it's location.
  • Any operation on a locked repository notes that the repository can be unlocked via the repositories popover.

This is mainly as a way to prevent users having to manually navigate into the directory and delete it themselves.

Supporting this seems risky:

If the lock is from another session, popup asking if users want to delete lock

Since users often click "OK" to these kinds of messages and in this case clicking through could lead to repository corruption. Further, this should be an exceptional case, if this is happening often I think we would be better off investigating why that is - and ways to reduce the risk of Blender leaving the repository locked.

Besides that, implementing the steps proposed isn't trivial as users would probably expect the dialog to continue with whatever action requires the lock after force-unlocking. This is something Blender's UI doesn't support without some fairly awkward operator logic. This has been done for the drag & drop UI, implementing this for locking would require something similar for all actions that manipulate the repository (including drag & drop). In short, I don't think it's practical to implement this without UI development that focuses on better supporting this use-case.

It's probably best any larger changes to user interactions on a locked repository are handled as design tasks.

@dfelinto there was a proposal for locking in this task: > - [ ] Users should not be locked out of updating extensions > - If the lock is from the same session, just show a info/warning about waiting/trying later. > - If the lock is from another session, popup asking if users want to delete lock (and manually try again). > - (related: Extensions: lock is held by other session #122135)*None.* I've committed support to "Force Unlock" a repository and removed the text above, but it works differently to the steps you've listed. - The option to force unlock a repository is available in the repository popover. - This option is typically greyed out, the tooltip includes the reasons, currently they are: - The repository is not locked. - The repository is locked by this blender session. - Force unlocking shows a confirm/cancel popup (defaulting to cancel) with some information including the age of the lock and it's location. - Any operation on a locked repository notes that the repository can be unlocked via the repositories popover. This is mainly as a way to prevent users having to manually navigate into the directory and delete it themselves. ---- Supporting this seems risky: > If the lock is from another session, popup asking if users want to delete lock Since users often click "OK" to these kinds of messages and in this case clicking through could lead to repository corruption. Further, this should be an exceptional case, if this is happening often I think we would be better off investigating why that is - and ways to reduce the risk of Blender leaving the repository locked. Besides that, implementing the steps proposed isn't trivial as users would probably expect the dialog to continue with whatever action requires the lock after force-unlocking. This is something Blender's UI doesn't support without some fairly awkward operator logic. This has been done for the drag & drop UI, implementing this for locking would require something similar for all actions that manipulate the repository (including drag & drop). In short, I don't think it's practical to implement this without UI development that focuses on better supporting this use-case. ---- It's probably best any larger changes to user interactions on a locked repository are handled as design tasks.
Dalai Felinto commented 2024-07-18 16:31:53 +02:00
Author
Owner
Copy Link

Closing this for now since Extensions is now officially released :)

Closing this for now since Extensions is now officially released :)
Blender Bot added the
Status
Archived
 label 2024-07-18 16:32:01 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
Interest
Alembic

  
Interest
Animation & Rigging

  
Interest
Asset System
Asset datablocks, libraries, browser and shelf

  
Interest
Audio

  
Interest
Automated Testing

  
Interest
Blender Asset Bundle

  
Interest
BlendFile

  
Interest
Collada

  
Interest
Compatibility
Backward and forward compatibility

  
Interest
Compositing

  
Interest
Core

  
Interest
Cycles

  
Interest
Dependency Graph

  
Interest
Development Management

  
Interest
EEVEE

  
Interest
Freestyle

  
Interest
Geometry Nodes

  
Interest
Grease Pencil

  
Interest
ID Management

  
Interest
Images & Movies

  
Interest
Import Export

  
Interest
Line Art

  
Interest
Masking

  
Interest
Metal

  
Interest
Modeling

  
Interest
Modifiers

  
Interest
Motion Tracking

  
Interest
Nodes & Physics

  
Interest
OpenGL

  
Interest
Overlay

  
Interest
Overrides

  
Interest
Performance

  
Interest
Physics

  
Interest
Pipeline, Assets & IO

  
Interest
Platforms, Builds & Tests

  
Interest
Python API

  
Interest
Render & Cycles

  
Interest
Render Pipeline

  
Interest
Sculpt, Paint & Texture

  
Interest
Text Editor

  
Interest
Translations

  
Interest
Triaging

  
Interest
Undo

  
Interest
USD

  
Interest
User Interface

  
Interest
UV Editing

  
Interest
VFX & Video

  
Interest
Video Sequencer

  
Interest
Viewport & EEVEE

  
Interest
Virtual Reality

  
Interest
Vulkan

  
Interest
Wayland
Wayland windowing on Unix

  
Interest
Workbench

  
Interest: X11

Xorg/X11 windowing

  
Legacy
Asset Browser Project

Archived

  
Legacy
Blender 2.8 Project

Archived

  
Legacy
Milestone 1: Basic, Local Asset Browser

Archived

  
Legacy
OpenGL Error

Archived

  
Meta
Good First Issue

  
Meta
Papercut

  
Meta
Retrospective

  
Meta
Security
Related to security, https://wiki.blender.org/wiki/Process/Vulnerability_Reports

  
Module
Animation & Rigging

  
Module
Core

  
Module
Development Management

  
Module
Grease Pencil

  
Module
Modeling

  
Module
Nodes & Physics

  
Module
Pipeline, Assets & IO

  
Module
Platforms, Builds & Tests

  
Module
Python API

  
Module
Render & Cycles

  
Module
Sculpt, Paint & Texture

  
Module
Triaging

  
Module
User Interface

  
Module
VFX & Video

  
Module
Viewport & EEVEE

  
Platform
FreeBSD

  
Platform
Linux

  
Platform
macOS

  
Platform
Windows

  
Severity
High

  
Severity
Low

  
Severity
Normal

  
Severity
Unbreak Now!

  
Status
Archived

  
Status
Confirmed

  
Status
Duplicate

  
Status
Needs Info from Developers

  
Status
Needs Information from User

  
Status
Needs Triage

  
Status
Resolved

  
Type
Bug

  
Type
Design

  
Type
Known Issue

  
Type
Patch

Archived

  
Type
Report

Archived

  
Type
To Do

No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset System
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Viewport & EEVEE
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Asset Browser Project
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Module
Viewport & EEVEE
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Severity
High
Severity
Low
Severity
Normal
Severity
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Python API
Assignees
Clear assignees
No Assignees
6 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#119521
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?