Ticket 13129

Summary:	Sinfo queries partitions where users can submit jobs
Product:	Slurm	Reporter:	zhuwq <zhuwqvip>
Component:	Other	Assignee:	Jacob Jenson <jacob>
Status:	RESOLVED INVALID	QA Contact:
Severity:	6 - No support contract
Priority:	---
Version:	20.11.8
Hardware:	Linux
OS:	Linux
Site:	-Other-	Slinky Site:	---
Alineos Sites:	---	Atos/Eviden Sites:	---
Confidential Site:	---	Coreweave sites:	---
Cray Sites:	---	DS9 clusters:	---
Google sites:	---	HPCnow Sites:	---
HPE Sites:	---	IBM Sites:	---
NOAA SIte:	---	NoveTech Sites:	---
Nvidia HWinf-CS Sites:	---	OCF Sites:	---
Recursion Pharma Sites:	---	SFW Sites:	---
SNIC sites:	---	Tzag Elita Sites:	---
Linux Distro:	---	Machine Name:
CLE Version:		Version Fixed:
Target Release:	---	DevPrio:	---
Emory-Cloud Sites:	---

Description zhuwq 2022-01-06 02:50:17 MST

How does the user determine which queues can be submitted? We have modified the source code, adding the part_extend parameter to filter the queue when executing sinfo, only printing the queue that the user can submit, but this will affect the performance, do you have a better solution?