This is an extreme example, but on small screens, particularly when there's a lot of text in the form, the feedback form looks like this:

I've added scroll bars to the whole form in master as a temporary fix but we should address this

The current jib-* tasks are still using PipelineResource. They should be updated (new version) to use params (for image) and results (for the generated image digest)

/kind feature

It is not surprising that deep and shallow scan show different results. Shallow scan only looks at column names. Deep scan looks at a sample of the data. I've even noticed that two different runs of deep scan show different results as sample rows are different. This is the challenge with not scanning all of the data. Its a trade-off between performance/cost and accuracy. There is no right answer.

Need to add logic to batch these api requests and combine the result - https://github.com/vinaygaba/JetpackCompose.app/blob/master/gatsby-node.js#L68