Appytown is failing on question 6 about metabase

[bshepherdson]

The big link is broken (at least for me), and I can't see any errors now on loading the main page https://appytown.metabase.com/.

I also don't see any requests for question 6 - has it been removed to prevent the error from bringing down the whole dashboard? If so, where can I see that query and trigger the error?

I do see org.eclipse.jetty.io.EofExceptions while streaming query results in the logs from around when this issue was raised. But the error log indicates that it was executing question 5, which is now working (the stacked bar chart of top-earning developers). I actually still see the same error logs now, even though that question is working.

[paoliniluis]

@bshepherdson the question is now removed, if you access the instance you will be able to see it

[bshepherdson]

Okay, I have visibility now.

This is failing to validate the query because the argument to :sum isn't a number. That's wrong; it's clearly a numeric column (1266, weekly active users) and all the metadata agrees it's :type/BigInteger.

I'm going to try reproducing this locally with a similar CSV upload, model and query.

[bshepherdson]

I can't reproduce this directly. Also if I duplicate the query on the Appytown instance, it works fine.

Looking at those two queries, the obvious difference is that the original broken one uses [:sum [:field 1266 {...}]] and the new working one uses [:sum [:field "weekly_active_users" {...}]]. The latter (using the model's column names rather than Field IDs) is what I'd expect to see for queries against a model.

Hypothesis: This Apps model used to be either a saved question, or a direct table reference, and then its source was changed to the model, but the refs stayed broken.

I'll see if I can reproduce it like that.

[bshepherdson]

No repro with those two paths.

• Changing the data source from the table to the model dropped everything from the rest of the query; the rebuilt aggregation used a correct ref.
• Starting with a SQ and then turning that into a model did keep the ID refs, but the query still works. So that probably was the path but it doesn't repro locally.

Without a repro on master, I'm not sure what else to say here. I think dropping that aggregation and replacing it will fix the Appytown question, and if that doesn't work then a duplicate of the query works fine.