Conversation
|
👋 Hey, looks like you've updated some demos! 🐘 Don't forget to update the Please hide this comment once the field(s) are updated. Thanks! |
Your preview is ready 🎉!You can view your changes here
|
Not all qml instances were changed.
There was a problem hiding this comment.
What happened to this demo specficially? Seems like GH regards the change here to be over the whole file. Is there any file encoding thing changed here?
There was a problem hiding this comment.
Hi @JerryChen97, broadly speaking, the only changes I should have made are:
- import pennylane as qml -> import pennylane as qp
- qml.XYZ -> qp.XYZ
I do not know why ensemble_multi_qpu is so unhappy. Let me investigate.
There was a problem hiding this comment.
Yeah similar issues happened in the past actually. I couldn't find the exactly link to PR's but from my memory they used to be file encoding difference.
JerryChen97
left a comment
There was a problem hiding this comment.
Mind try these on those weird file changes? It should be a typical line ending mutation issue and hopefully adding newline="" prevents Python from normalizing the line endings
There was a problem hiding this comment.
Probably a formatting error. It's easier for me to just delete this file from the PR than to remedy it here.
|
Hey @andrijapau , would you mind approving this PR if you are OK with it? @JerryChen97 and I want to see if it suffices or if a Content approval is required. Thanks :) |
I'd prefer if someone from Content could take over for review - I have my hands full over in PennyLane 😓 |
Removed 'Getting Started' category from metadata.
Because demos/metadata_schemas has not been updated
Before submitting
Please complete the following checklist when submitting a PR:
Ensure that your tutorial executes correctly, and conforms to the
guidelines specified in the README.
Remember to do a grammar check of the content you include.
All tutorials conform to
PEP8 standards.
To auto format files, simply
pip install black, and thenrun
black -l 100 path/to/file.py.When all the above are checked, delete everything above the dashed
line and fill in the pull request template.
Title:
Summary:
Relevant references:
Possible Drawbacks:
Related GitHub Issues:
If you are writing a demonstration, please answer these questions to facilitate the marketing process.
GOALS — Why are we working on this now?
Eg. Promote a new PL feature or show a PL implementation of a recent paper.
AUDIENCE — Who is this for?
Eg. Chemistry researchers, PL educators, beginners in quantum computing.
KEYWORDS — What words should be included in the marketing post?
Which of the following types of documentation is most similar to your file?
(more details here)