henry3260 opened a new issue, #73803:
URL: https://github.com/apache/airflow/issues/73803

   ### Description
   
   Since #72864 and #72862, `GET /ui/next_run_assets/{dag_id}` returns only the
   scheduling assets the caller may read, while `asset_expression` keeps a 
hidden
   slot for each unreadable one. `AssetSchedule.tsx` still derives both the 
total
   and the layout from the returned events, so the UI now changes shape with the
   caller's permissions.
   
   For a Dag scheduled on assets A, B and C, a caller who may read only A sees:
   
   - "1 of 1" instead of "1 of 3" — `scheduledTotal` is `nextRunEvents.length`
     (`AssetSchedule.tsx:124`).
   - The single-asset layout instead of the popover, because of the
     `nextRunEvents.length === 1` branch (`AssetSchedule.tsx:207`).
   - No asset schedule at all if none of the three are readable, because the
     `!nextRunEvents.length` branch falls back to `timetableSummary`
     (`AssetSchedule.tsx:128`).
   
   ### Use case/motivation
   
   _No response_
   
   ### Related issues
   
   _No response_
   
   ### Are you willing to submit a PR?
   
   - [x] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
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]

Reply via email to