Skip to content
#

forest

Here are 110 public repositories matching this topic...

kalzoo
kalzoo commented Dec 19, 2019

#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.

pennylane
appleby
appleby commented Jan 26, 2020

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

mettiu
mettiu commented Jul 25, 2019

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

Twizty1
Twizty1 commented Nov 27, 2019

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

tannerwelsh
tannerwelsh commented Apr 27, 2018

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

antalszava
antalszava commented Mar 31, 2020

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
olizilla
olizilla commented Jul 3, 2018

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
stefaniebutland
stefaniebutland commented Jun 13, 2019

(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

Improve this page

Add a description, image, and links to the forest topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the forest topic, visit your repo's landing page and select "manage topics."

Learn more

You can’t perform that action at this time.