deploy-to-sfdx Source Push errors aren't visible.

I'm attempting to deploy https://github.com/muenzpraeger/salesforce-einstein-platform-apex to a scratch org with the direct deploy button.

It gives me the following output:

Finished. You have deployed the app to your scratch org!

7 ) Removed temp files and cleaned up. 6 ) Generated a login url: https://momentum-data-1744-dev-ed.cs100.my.salesforce.com/secur/frontdoor.jsp?sid=00D0q0000000001!ARwAQC32j9otrbvI.NotMyRealSessionId_mqN0XVw2JA66bNuGsBH2chbh 5 ) Apex tests: . 4 ) Pushed source files. 3 ) Successfully created scratch org: 00D0q0000000001EAU, username: test-s97bv57q1234@muenzpraeger-_rené_winkelmeyer.net. 2 ) Successfully cloned https://github.com/muenzpraeger/salesforce-einstein-platform-apex. 1 ) Didn't find a .salesforcedx.yaml file. Using defaults: assign-permset: false permset-name: delete-scratch-org: false run-apex-tests: false scratch-org-def: config/project-scratch-def.json show-scratch-org-url: true

Which gave every indication that the deployment was successful. Yet when I log into my new ~~scratch~~ burner org I don't see any of the expected metadata from the source repo.

I've discussed it with @muenzpraeger, and the theory is that his source requires a Winter '17 org. My ~~scratch~~ burner orgs are currently being created on Summer '17.

I tried deploying to my burner org from the CLI directly and got the following errors:

PROJECT PATH ERROR ──────────── ───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────── N/A No COMPONENT named markup://lightning:accordionSection found : [markup://c:EinsteinPlaygroundIntroduction] N/A No COMPONENT named markup://lightning:accordionSection found : [markup://c:EinsteinPlayground, markup://c:EinsteinPlaygroundIntroduction]

René commented that these will be the Winter '17 specific components.

So a couple of observations:

These errors aren't visible when using the deploy button.
There is no mechanism in force:source:push to block the deployment if the target org doesn't have the required API version. Raised this on the Success community.