(airavata-custos) branch 533 updated (d39752f7f -> 709f619f6)

[la...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

lahirujayathilake pushed a change to branch 533
in repository https://gitbox.apache.org/repos/asf/airavata-custos.git


 discard d39752f7f Scope project and allocation reads to membership by default
 discard f459944f8 Provision registry people the cluster can resolve and log into
 discard e7422580e Remove Slurm access the allocations no longer grant
 discard 01df98036 Deprovision Slurm access when a membership or allocation is deactivated
 discard eabd6fd69 Split gres/gpu into type and name when writing Slurm limits
 discard cd2b63b8e Write only the Slurm associations that differ from the cluster
 discard 1795adc87 Reconcile Slurm associations instead of polling for provisioning
    omit 35b96dc49 Match SLURM GPU usage on the gres/gpu TRES pair
    omit c59fd439b Count SLURM usage from the whole-job TRES total
    omit 30b28cc46 Record SLURM usage correctly and rename the cluster-user lookup
    omit f61768c7d Updated the SLURM job queries in the format slurmrestd accepts
     add 942d48041 Rebrand to new logo/colors and fix dropdown, breadcrumb, and dark mode issues (#553)
     add f31132c59 Bump next from 15.5.18 to 15.5.21 in /web (#557)
     add e1c69ae9d Fix SLURM job listing and usage recording (#542)
     add a2a056e16 Reconcile Slurm associations instead of polling for provisioning
     add f2507db47 Write only the Slurm associations that differ from the cluster
     add 750d4d248 Split gres/gpu into type and name when writing Slurm limits
     add 6b0bf2df0 Deprovision Slurm access when a membership or allocation is deactivated
     add c0f7fea32 Remove Slurm access the allocations no longer grant
     add b96eb4e5b Provision registry people the cluster can resolve and log into
     add 709f619f6 Scope project and allocation reads to membership by default

This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version.  This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:

 * -- * -- B -- O -- O -- O   (d39752f7f)
            \
             N -- N -- N   refs/heads/533 (709f619f6)

You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.

Any revisions marked "omit" are not gone; other references still
refer to them.  Any revisions marked "discard" are gone forever.

No new revisions were added by this update.

Summary of changes:
 web/design-tokens/colors.css                       |  18 ++-
 web/package.json                                   |   2 +-
 web/pnpm-lock.yaml                                 | 145 +++++++++++----------
 .../(portal)/admin/users/management/UsersTable.tsx |   2 +-
 web/src/shared/__tests__/tokens.test.ts            |   6 +-
 5 files changed, 90 insertions(+), 83 deletions(-)