forest
Here are 110 public repositories matching this topic...
Currently if a user wants to determine if a particular operation is supported on a device from the documentation (e.g., in the default.qubit plugin), they will find a bunch of gates/operations/observables listed, but under different names than found in PennyLane. This may be confusing to users. We should state very clearly
-
Updated
Aug 4, 2019 - Java
Implement a function to splice parsed-program objects together in a reasonable way.
It looks like the upcoming sbcl 2.0.1 release includes changes to move certain symbols out of cl:*features* and into sb-impl:+internal-features+ [[1]]. IIUC, any "non-public" features will continue to work (for now), but issue a warning [[2]].
I haven't tested it, but it looks like we use at least one such soon-to-be-deprecated feature, namely avx2. We should figure out what to do about
-
Updated
Mar 19, 2020 - Python
Expected behavior
Server or console should boot without warnings/errors
Actual behavior
Starting rails server or console fire douzen of error logs such as the one below, that are not blocking though.
Failure Logs
Context
- Pac
-
Updated
Apr 8, 2018 - C++
Expected behavior
I should not see deprecation warnings from mongodb driver.
Actual behavior
As soon as the Forest UI loads, in my nodejs server log I can see this deprecation warning:
DeprecationWarning: collection.count is deprecated, and will be removed in a future version. Use collection.countDocuments or collection.estimatedDocumentCount instead
Failure Logs
Describe the bug
The section "usage" in instructions for releases contains wrong name of the RescuerLaApp. It is named "ReacuerLaApp" for both Linux\CentOS\OSX and Windows. That can cause problems for those who aren't familiar with the project.
There are also
Expected behavior
Sequelize should be able to connect to MySQL V8.X.X
Actual behavior
Sequelize can't create a connection to MySQL database with version starting at 8.X.X
Failure Logs
Context
When using
I might be missing it, but I'm looking to be able to specify the domain when using Get-WinADForestInformation instead of it auto-discovering it.
Use case, our parent company maintains it's own AD. I'm not joined, but have a trust between mine and there's. I'm starting documentation of their system for them and want to point your script at them to start.
Appreciate the great work on this sc
-
Updated
Apr 29, 2020 - Python
Hey, guys.
Any chance of adding Laravel documentation soon? Even just a sample Laravel project would help.
I just cannot figure out to start populating my Forest Admin dashboard.
Any guidance would be welcome.
Expected behavior
When editing the content of a record in a "related data" set that triggers a custom action, I would expect the custom response from that action to be rendered as a message in the same manner as is specified at https://doc.forestadmin.com/developer-guide/express-mongoose.html#customizing-response.
Actual behavior
The custom message works for POST requests with th
-
Updated
Feb 7, 2019 - Python
-
Updated
Jun 8, 2019
This would make the docs more discoverable.
The lattices used when creating a device based on the documentation seem to be outdated. For example:
>>> dev_qpu = qml.device('forest.qpu', device='Aspen-0-12Q-A', shots=1000)
File "/anaconda3/lib/python3.7/site-packages/pyquil/api/_devices.py", line 147, in _get_raw_lattice_data
res = get_json(session, f"{config.forest_url}/lattices/{lattice_name}")
File "/anaconda3/lib/py-
Updated
Feb 25, 2020 - MATLAB
The ls and resolve commands shows my .pinset entry as having a size of 60. Let's force it to add units in all cases.
? > ls
. 2.4G QmSc9pcnm4N1QC1u2oSNL6eRgFjxDq2Aex6cGhTkvw91xc
.pinset 60 QmYJmoKWDFh1wmZLATh3fiVzMuhhTyNm9NLGuLEJM7HdNZ
dapps 17.5M QmQN6bA5YEPEaPDUDLq6o9fm24Ye2bbnA4YUT2rBeAR5cm
foo 2.4G QmPkNdFzNFZfM9QixL3ZowBNvveFmufbnRuM36K1SrnmB1-
Updated
Feb 20, 2020 - TeX
(rOpenSci Community Manager here) rOpenSci has rolled out a new service to automatically build and host documentation for all rOpenSci packages: https://ropensci.org/technotes/2019/06/07/ropensci-docs/
I noticed that the MtreeRing images don't render at https://docs.ropensci.org/MtreeRing/ but they render correctly at https://ropensci.github.io/MtreeRing/.
Tagging @jeroen in case you need he
-
Updated
Jul 25, 2018 - Common Lisp
-
Updated
May 29, 2019 - JavaScript
-
Updated
Sep 7, 2017 - Python
Please visit the contributing guidelines to learn more on how to translate Dsforest's documentation into more languages.
Tons of thank you to everyone for your help and support!
Improve this page
Add a description, image, and links to the forest topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the forest topic, visit your repo's landing page and select "manage topics."



#1123 added support for engagement and an encrypted connection with the QPU. While this will be transparent to most users, we should add documentation for power users and to aid in troubleshooting.