Filter user id for authentication

[peterpeterparker]

Motivation

Currently, there is no option to filter the list of users by User ID in the Authentication section. This makes it challenging to quickly locate specific users.

What to Do

Add a filter option to the Authentication page that allows users to filter by User ID.

The filter should be placed in a "Filter" popover, following a similar UI/UX pattern as the actions on the Functions and Datastore pages.

[red-apple38]

Can I take the issue?

[peterpeterparker]

Sure, go for it @red-apple38 👍

[tinkerer-shubh]

would love to pick this up! @peterpeterparker

[peterpeterparker]

Sure @tinkerer-shubh, go for it 👍

[tinkerer-shubh]

hey @peterpeterparker,I’ve implemented a filter option for the auth page but it’s still a work in progress. When I try to test it in dev mode, I can’t seem to sign in and get this error:   Canister called ic0.trap with message: <Canister error message

this is what's happening: You have been signed out because your Mission Control could not be certified.

Not sure if I’m missing something—any ideas?

https://internetcomputer.org/docs/references/execution-errors#trapped-explicitly

[peterpeterparker]

Hi @tinkerer-shubh ,

Did you run the local development environment as described in the HACKING.md ?

1. You need Docker
2. In one terminal, run

npm run emulator

3. In another terminal, run

npm run dev

[tinkerer-shubh]

yup I did but still the error message stays. there's a longer error that appears which I am not able to look at properly or copy cause it appears and goes too fast(this is in the browser).

also, on the PR checks, the docker checks did not run but I do have docker installed.

[peterpeterparker]

When you start npm run emulator, is there any issue? i.e. do you see any errors in the log or everything seems fine?

I suspect the default backend to fail at deploying the default modules, which don't happen in my local environment because I keep iterating and building those.

[tinkerer-shubh]

I think I found a band-aid fix for this, this was the error msg:

Canister called ic0.trap with message: 'juno.cdn.storage.error.missing_releases_description'

I did some digging with my buddy claude and found this as the root cause (could be totally wrong tho):

The console canister validates that assets uploaded to the "releases" collection have a description matching the pattern change=\d+;version=[^;]+$ (e.g., "change=123;version=1.0.0"). During emulator startup, the CLI uploads assets without providing this required description format.

this was the fix and it's working for now :)

Modified src/console/src/cdn/assert.rs to skip description validation in development mode when no description is provided:

// Skip description validation in development mode (when description is None or empty) // This allows the emulator to work without requiring proper release descriptions if description.is_some() && !description.as_ref().unwrap().is_empty() { assert_releases_description(description)?; }

[peterpeterparker]

Haaaaa you are right. main contains features - and new assertions - that are not compatible with the latest Docker image, which itself will be upgraded, once new features are released.

That's why you needed the workaround, well played 👍.

I understand that you are unblocked but, I'll still try to find a temporary solution.

[peterpeterparker]

Main should be good now. I temporary disabled the new asseration in #1670. Thanks for the ping about it!