shivaam commented on PR #70159: URL: https://github.com/apache/airflow/pull/70159#issuecomment-5099052818
A modal makes sense for keeping context, but I’m concerned about putting a potentially large, paginated slot collection inside it. Fetching all slots would also recreate the request-volume problem we removed. Could we instead keep a lightweight route containing only the slots table, with an explicit “View slots” action and clear back navigation? That said, I’m also fine with a modal if that’s the preferred direction. The main thing I’d like to preserve is somewhere users can inspect the Dag runs and not-created slots associated with a backfill. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
