Request for expedited manual review - ragsuite-amd snap(deadline : september 13 2025)

store-requests classic-confinement
1

Hello Snapcraft team,

I have recently uploaded the snap RAGSUITE-AMD v0.2.0+rev7 (ragsuite-amd) to the Snap Store. The automated review failed due to disk space limits in the review environment, and the snap is now pending manual review.

We are preparing for a public release on September 13, 2025, and the snap store availability is a critical part of our launch plan.

The application has been tested locally and installs successfully with --dangerous. The upload and build process has completed successfully — we just need the manual review to be processed so that we can publish in time for our deadline.

We tired to split the snaps but it is not possible. Because the App is not that much consuming but the Torch+Rocm Library is consuming that much. We are not able to optimze that.

Please help us optimize our Snap confinement setup, as the current size is around 20GB. Until AMD reduces the size of their ROCm libraries, it will not be possible for us to minimize it further. Additionally, we require permanent auto-connect permissions for the following interfaces:

  • opengl
  • hardware-observe
  • process-control

I would be grateful if the manual review could be prioritized to meet our launch timeline.

Thank you for your help and for supporting our release!

Snap name: ragsuite-amd Version: 0.2.0+rev7 Publisher: Felamity Technologies LLP Deadline: September 13, 2025

— Nafize Ahamed Felamity Technologies LLP

2

This request has been added to the queue for review by the @reviewers team.

3

Hey @nafizeahamed

Your snap is now passing automatic review. Regarding the snap size, we should have independent content snaps for Torch and Rocm so that they can be reused by any consuming snap. I don’t know if there is any effort in that direction already.

For the requested auto-connections:

  • opengl: auto-connects by default, so there is nothing to do with it
  • hardware-observe: it makes sense to me as it would be needed to detect which GPUs are available
  • process-control: Could you pleas clarify why it is needed? I don’t see any trivial reason

Thanks

4

Can you please expand upon your launch plan?

Whilst I’m grateful these are being expedited, the original request stated:

And it doesn’t make sense to keep skipping processes for an external deadline that should have been hit last month. I appreciate business doesn’t always go to plan and the technicals here are more annoying than most given the somewhat arbitary filesize issue, but people will rightfully question the justification that seems to be the same with changing dates twice now.

5

@James-Carroll Sorry for the confusion, James. The product was indeed released on the Snap Store in August as planned. However, we’ve since made some important improvements, which is why we’re re-releasing. Our goal is to ensure customers don’t need to install a separate snap for Torch + ROCm—we’re including that functionality directly in our package to provide a smoother experience.

6

Thanks for helping us mate…

process-control – this is required because our application needs a process supervisor (managing worker processes, restarting them if they hang). Without it won’t be able to send signals to other processes within the snap. Threading concepts has been applied - That’s why it is much needed.

7

Hey @nafizeahamed !

Sorry for the long delay in my response. I think opengl and hardware-observe makes sense for the snap. Regarding, process-control, I don’t think its need is obvious enough to the user and I would prefer to let the user decide (using then manual-connection). The snapped application can always use snapctl is-connected to check if the interface is connected and prompt the user if it is not.