Closed prjemian closed 1 year ago
Notebook demo_dynamic_limits_2motor
still has last two RE()
cells broken. Needs to be fixed.
Totals | |
---|---|
Change from base Build 4683819136: | 0.1% |
Covered Lines: | 832 |
Relevant Lines: | 1039 |
Tortured by this CI error when trying to finalize the docs publishing:
Artifact github-pages has been successfully uploaded!
Run actions/deploy-pages@v1
Artifact exchange URL: https://pipelines.actions.githubusercontent.com/qITsYfE3pBuyISswz73JHlMnKbvmJUKdKGHkY3ZtbBUQy60Ril/_apis/pipelines/workflows/4683321555/artifacts?api-version=6.0-preview
Creating Pages deployment with payload:
{
"artifact_url": "https://pipelines.actions.githubusercontent.com/qITsYfE3pBuyISswz73JHlMnKbvmJUKdKGHkY3ZtbBUQy60Ril/_apis/pipelines/1/runs/362/artifacts?artifactName=github-pages&%24expand=SignedContent",
"pages_build_version": "5288035dbb70a13b5f2083811acf53ec3c525b25",
"oidc_token": "***"
}
Error: Creating Pages deployment failed
Error: HttpError: Invalid environment node id
at /home/runner/work/_actions/actions/deploy-pages/v1/webpack:/deploy-pages/node_modules/@octokit/request/dist-node/index.js:86:1
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at createPagesDeployment (/home/runner/work/_actions/actions/deploy-pages/v1/webpack:/deploy-pages/src/api-client.js:116:1)
at Deployment.create (/home/runner/work/_actions/actions/deploy-pages/v1/webpack:/deploy-pages/src/deployment.js:58:1)
at main (/home/runner/work/_actions/actions/deploy-pages/v1/webpack:/deploy-pages/src/index.js:30:1)
Error: TypeError: Converting circular structure to JSON
--> starting at object with constructor 'TLSSocket'
| property '_httpMessage' -> object with constructor 'ClientRequest'
--- property 'socket' closes the circle
start a new branch and build a working docs publishing workflow
Placed will archive by 2023-09-01 notice on https://github.com/BCDA-APS/use_bluesky repo
@rodolakis Ready for review
View the published documentation: https://bcda-aps.github.io/bluesky_training/
@stevehenke : This is a re-arrangement (and consolidation) of the various documentation we have. Ultimately, these docs will also connect with other documentation in apstools, bluesky, ophys, hklpy, and others as the place where we describe those docs. That's the plan.
Note these related issues should become part of this PR as well:
@rodolakis @keenanlang Thanks for the approvals.