Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Broken Build #7935

Closed
ChaseKnowlden opened this issue Oct 14, 2021 · 1 comment
Closed

Broken Build #7935

ChaseKnowlden opened this issue Oct 14, 2021 · 1 comment
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug

Comments

@ChaseKnowlden
Copy link
Contributor

Environment data

  • VS Code version: 1.61.1
  • Jupyter Extension version (available under the Extensions sidebar): 2021.9.1101343141
  • Python Extension version (available under the Extensions sidebar): 2021.10.1336267007
  • OS (Windows | Mac | Linux distro) and version: Windows 10 19043
  • Python and/or Anaconda version: 3.10.0
  • Type of virtual environment used (N/A | venv | virtualenv | conda | ...): venv
  • Jupyter server running: Local | Remote | N/A | ...: Local

Expected behaviour

Should Compile

Actual behaviour

Type Assignment Error

Steps to reproduce:

  1. npx gulp prePublishNonBundle

Logs

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! jupyter@2021.10.100 build-ipywidgets-compile: tsc -p ./src/ipywidgets && rimraf ./out/tsconfig.tsbuildinfo && node ./src/ipywidgets/scripts/copyfiles.js

@ChaseKnowlden ChaseKnowlden added the bug Issue identified by VS Code Team member as probable bug label Oct 14, 2021
@ChaseKnowlden ChaseKnowlden changed the title Fix Broken Build Broken Build Oct 14, 2021
@rchiodo
Copy link
Contributor

rchiodo commented Oct 18, 2021

Should be fixed now

@rchiodo rchiodo closed this as completed Oct 18, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 20, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug
Projects
None yet
Development

No branches or pull requests

3 participants