Segments section is broken

Dear Metabase,
I have an issue with Segments. I try to modify a segment for Google Analytics. It crash and since then I have the following message when I click on Segments :

Unexpected input given to normalize. Expected type to be “object”, found “string”.

First time, this issue occured was under Metabase 0.36.4.
I’ve update Metabase from 0.36.4 to 0.36.6 but nothing change.
Debugging info :

{
“browser-info”: {
“language”: “en-US”,
“platform”: “Win32”,
“userAgent”: “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.121 Safari/537.36”,
“vendor”: “Google Inc.”
},
“system-info”: {
“file.encoding”: “Cp1252”,
“java.runtime.name”: “Java™ SE Runtime Environment”,
“java.runtime.version”: “1.8.0_221-b11”,
“java.vendor”: “Oracle Corporation”,
“java.vendor.url”: “http://java.oracle.com/”,
“java.version”: “1.8.0_221”,
“java.vm.name”: “Java HotSpot™ 64-Bit Server VM”,
“java.vm.version”: “25.221-b11”,
“os.name”: “Windows Server 2016”,
“os.version”: “10.0”,
“user.language”: “en”,
“user.timezone”: “Europe/Paris”
},
“metabase-info”: {
“databases”: [
“googleanalytics”,
“sqlserver”,
“mysql”,
“postgres”,
“h2”
],
“hosting-env”: “unknown”,
“application-database”: “postgres”,
“application-database-details”: {
“database”: {
“name”: “PostgreSQL”,
“version”: “12.2”
},
“jdbc-driver”: {
“name”: “PostgreSQL JDBC Driver”,
“version”: “42.2.8”
}
},
“run-mode”: “prod”,
“version”: {
“tag”: “v0.36.6”,
“date”: “2020-09-15”,
“branch”: “release-0.36.x”,
“hash”: “cb258fb”
},
“settings”: {
“report-timezone”: “Europe/Brussels”
}
}
}

Best regards

Hi @nico8
I have been able to reproduce this - I have a lot more details in the issue and a workaround to return the segment interface:
https://github.com/metabase/metabase/issues/13362 - upvote by clicking :+1: on the first post

Thanks @flamber
Workaround is based on issue #10844

Work-around
Manually go and edit the Segment and give the Custom Expression a name.
Visit the URL /admin/datamodel/segment/X , where X is the ID of the failing metric.

Unfortunately, it is not possible to consult all the existing segments :

If you don’t know the ID of the metric, then you can find it by clicking “Browse Data” in top-menu, “Learn about our data” top-right > “Segments” left-side > click the segment and check the URL, which will look like /reference/segments/X .

@nico8
The workaround is listed on the second line of the issue - not the related issue.
Workaround to restore Segment interface is to manually archive the segment via the application database table segment.archived

Outch read github issue too quick :crazy_face:
Thanks !

1 Like