Set a filter on the table view of a workspace with the setting to show only if the column had values less than or equal to a string, which throws an error. Now I cannot access the workspace view without the error being displayed, effectively locking me out of it. Ive tried clearing my cookies and cache, and Im not aware of a way to change the filters from outside of the workspace view. Heres the error readout with some of the settings removed for clarity.
invalid filter: [map[foo:bar] map[fizz:[map[]]]] has invalid type for <= operator: []interface {}
Hey! Thanks for flagging this. Please provide the following:
- which browser are you using? We suggest Chrome!
- Could you share your console logs? In Chrome, right-click → Inspect → Console.
Thanks!
- I generally use firefox, but the bug is also present on Chrome.
- The error logs are quite long and contain many duplicate errors (from automatic retries) but I can dump the unique ones.
- The same as the error in the original message but its tagged as an Apollo GraphQL Error
- Apollo NetworkErrors: undefined
Thanks for this info!
To confirm, you are not able to access your workspace still anymore and the issue happened when you were writing a query for custom charts?
Please let us know, thank you!
Upon attempting to open the workspace view for the project, I am stuck in a loop where it tries to send send a GraphQL query ~4 times, then gives a screen which displays the bug. Individual runs in the project are accessible as are their workspaces, but the combined workspace for the project will give the bug screen. Other project panels which dont attempt to load the workspace table still function ie. I can still open the overview for the project or start a sweep.
As of now I am still unable to view the workspace.
This bug occurred while trying to add filter to the table section of the workspace.
Hey Jamorr - I see - could you share which project and in which team is this taking place?
Hey Jamorr, I am currently looking into this. To confirm, this happened to your project Deformable_Mamba, correct?
I would need you to please send me a video of what you did here:
Set a filter on the table view of a workspace with the setting to show only if the column had values less than or equal to a string, which throws an error.
Else, please tell me exactly what you did so I can repro on my end. What table are you referring to? Are you referring to a table that you logged with wandb.log() or are you referring to a query table you created through query panels on the workspace UI? Or are you referring to the runs table? Please let us know so we can properly repro on our side, or show us please a screenshot of what you are doing in another test workspace.
Let me know, thank you!
I am specifically talking about the “query table you created through query panels on the workspace UI”. Im not sure if I can exactly repro for you but heres what it looks like
instead of
someword if you input []into the textbox it will give this error. NOTE: the value of this column is a map data type with key, value pairs
and then you get stuck. If you need more lmk. What I was hoping for was an easy way to clear the filter from outside the workspace, but I wasn’t able to find one.
Hey Jamorr! Thank you for these detailed instructions. I have tried to repro this on my end but I do not get this error.
Could you please check for me which version of wandb you are on? Could you make sure to upgrade to the latest release (see here)?
This might be an issue related to the SDK version. Please let me know, thank you!
Sure Im on 0.17.5, I upgraded 0.17.7 and these are the results after that:
In the instructions I forgot to mention that you have to hit enter/apply the filter after you type [] to in the select a value drop down. Additionally I was slightly off, I looks like this column is a List/Array of Maps as well.
Hey Jamorr - I was finally able to repro this. This is definitely a bug. I am opening a bug ticket for this on my end now - I will keep you up to date with updates from our teams internally! Thank you so much for pointing this out to us!! 
Hey @jamorr , quick update on the above – this bug should be fixed now in the UI. Please let us know if you still encounter this issue.
Hi @jamorr , the fix was implemented for this issue. Please let me know if you still encounter this issue on your end.
Looks good on my end. Thanks for the update 
@anmolmann
1 Like