oceanprotocol / docs Goto Github PK

The dependency gatsby-source-graphql was updated from 2.0.15 to 2.0.16.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

gatsby-source-graphql is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The React App Tutorial is not working, again. I tried it just now. It failed on the final (consume) step. Here's a screenshot of the console log.

Some Ideas

• Maybe we don't need the React App Tutorial any more? Maybe the squid-js examples, the squid-js tests, Tuna, the Commons Marketplace and Pleuston are enough. Let's minimize the amount of stuff we need to maintain.
• The React App Tutorial is specific to squid-js. In fact, there should be a different version of the tutorial for every version of squid-js. In other words, the React App Tutorial source code should live in the squid-js repository and it should be tested as part of the Travis tests. The docs site can pull content from other repositories, so it should be possible. But what version of the tutorial should be shown on the docs site? Should we give readers a squid-js version-selector? The same issue arises with the squid-js API docs, see issue #195. Putting all the squid-js docs and tutorials on their own ReadTheDocs site would be another solution; it lets readers chose the version number.

There have been updates to the gatsby monorepo:

• • The dependency gatsby-image was updated from 2.0.30 to 2.0.31.

• The dependency gatsby-plugin-catch-links was updated from 2.0.11 to 2.0.12.
• The dependency gatsby-plugin-google-analytics was updated from 2.0.15 to 2.0.16.
• The dependency gatsby-plugin-manifest was updated from 2.0.21 to 2.0.22.
• The dependency gatsby-plugin-offline was updated from 2.0.23 to 2.0.24.
• The dependency gatsby-plugin-react-helmet was updated from 3.0.7 to 3.0.8.
• The dependency gatsby-plugin-sharp was updated from 2.0.24 to 2.0.25.
• The dependency gatsby-plugin-sitemap was updated from 2.0.5 to 2.0.6.
• The dependency gatsby-remark-autolink-headers was updated from 2.0.14 to 2.0.15.
• The dependency gatsby-remark-images was updated from 3.0.5 to 3.0.6.
• The dependency gatsby-source-filesystem was updated from 2.0.22 to 2.0.23.
• The dependency gatsby-source-graphql was updated from 2.0.12 to 2.0.13.
• The dependency gatsby-transformer-remark was updated from 2.3.0 to 2.3.1.
• The dependency gatsby-transformer-sharp was updated from 2.1.14 to 2.1.15.
• The dependency gatsby was updated from 2.1.27 to 2.1.28.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the gatsby group definition.

gatsby is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

There have been updates to the gatsby monorepo:

• • The dependency gatsby-plugin-manifest was updated from 2.0.11 to 2.0.12.

• The dependency gatsby was updated from 2.0.65 to 2.0.66.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the gatsby group definition.

gatsby is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

There have been updates to the gatsby monorepo:

• • The dependency gatsby-image was updated from 2.0.24 to 2.0.25.

• The dependency gatsby-plugin-manifest was updated from 2.0.11 to 2.0.12.
• The dependency gatsby was updated from 2.0.66 to 2.0.67.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the gatsby group definition.

gatsby is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

There have been updates to the gatsby monorepo:

• • The dependency gatsby-plugin-offline was updated from 2.0.19 to 2.0.20.

• The dependency gatsby-remark-copy-linked-files was updated from 2.0.7 to 2.0.8.
• The dependency gatsby was updated from 2.0.67 to 2.0.68.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the gatsby group definition.

gatsby is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

There have been updates to the gatsby monorepo:

• • The dependency gatsby-image was updated from 2.0.22 to 2.0.23.

• The dependency gatsby-plugin-offline was updated from 2.0.18 to 2.0.19.
• The dependency gatsby-plugin-react-helmet was updated from 3.0.3 to 3.0.4.
• The dependency gatsby-plugin-sass was updated from 2.0.6 to 2.0.7.
• The dependency gatsby-plugin-sharp was updated from 2.0.14 to 2.0.15.
• The dependency gatsby-remark-prismjs was updated from 3.1.3 to 3.1.4.
• The dependency gatsby-source-filesystem was updated from 2.0.11 to 2.0.12.
• The dependency gatsby was updated from 2.0.64 to 2.0.65.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the gatsby group definition.

gatsby is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

There have been updates to the gatsby monorepo:

• • The dependency gatsby-image was updated from 2.0.30 to 2.0.31.

• The dependency gatsby-plugin-catch-links was updated from 2.0.11 to 2.0.12.
• The dependency gatsby-plugin-google-analytics was updated from 2.0.15 to 2.0.16.
• The dependency gatsby-plugin-manifest was updated from 2.0.21 to 2.0.22.
• The dependency gatsby-plugin-offline was updated from 2.0.23 to 2.0.24.
• The dependency gatsby-plugin-react-helmet was updated from 3.0.7 to 3.0.8.
• The dependency gatsby-plugin-sharp was updated from 2.0.24 to 2.0.25.
• The dependency gatsby-plugin-sitemap was updated from 2.0.5 to 2.0.6.
• The dependency gatsby-remark-autolink-headers was updated from 2.0.14 to 2.0.15.
• The dependency gatsby-remark-images was updated from 3.0.5 to 3.0.6.
• The dependency gatsby-source-filesystem was updated from 2.0.22 to 2.0.23.
• The dependency gatsby-source-graphql was updated from 2.0.12 to 2.0.13.
• The dependency gatsby-transformer-remark was updated from 2.3.0 to 2.3.1.
• The dependency gatsby-transformer-sharp was updated from 2.1.14 to 2.1.15.
• The dependency gatsby was updated from 2.1.27 to 2.1.28.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the gatsby group definition.

gatsby is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

When I dug into the docs build log on Travis, I found the following at the end of a recent build:

> @oceanprotocol/[email protected] deploy /home/travis/build/oceanprotocol/docs
> ./scripts/deploy.sh
/home/travis/.local/lib/python2.7/site-packages/urllib3/util/ssl_.py:354: SNIMissingWarning: An HTTPS request has been made, but the SNI (Server Name Indication) extension to TLS is not available on this platform. This may cause the server to present an incorrect TLS certificate, which can cause validation failures. You can upgrade to a newer version of Python to solve this. For more information, see https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings
  SNIMissingWarning
upload: public/1-1b302df95287306ed48a.js.map to s3://docs.oceanprotocol.com/1-1b302df95287306ed48a.js.map
⋮
upload: public/workbox-v3.6.3/workbox-sw.js to s3://docs.oceanprotocol.com/workbox-v3.6.3/workbox-sw.js
upload: public/workbox-v3.6.3/workbox-sw.js.map to s3://docs.oceanprotocol.com/workbox-v3.6.3/workbox-sw.js.map
/home/travis/.local/lib/python2.7/site-packages/urllib3/util/ssl_.py:354: SNIMissingWarning: An HTTPS request has been made, but the SNI (Server Name Indication) extension to TLS is not available on this platform. This may cause the server to present an incorrect TLS certificate, which can cause validation failures. You can upgrade to a newer version of Python to solve this. For more information, see https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings
  SNIMissingWarning
200 http://www.google.com/webmasters/tools/ping?sitemap=https%3A%2F%2Fdocs.oceanprotocol.com%2Fsitemap.xml
200 http://www.bing.com/webmaster/ping.aspx?siteMap=https%3A%2F%2Fdocs.oceanprotocol.com%2Fsitemap.xml
---------------------------------------------
         ✓ done deployment 
---------------------------------------------
Done. Your build exited with 0.

The only problem seems to be the:

/home/travis/.local/lib/python2.7/site-packages/urllib3/util/ssl_.py:354: SNIMissingWarning: An HTTPS request has been made, but the SNI (Server Name Indication) extension to TLS is not available on this platform. This may cause the server to present an incorrect TLS certificate, which can cause validation failures. You can upgrade to a newer version of Python to solve this. For more information, see https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings
SNIMissingWarning

which occurred twice. Maybe there is some way to use a newer version of Python...

see page https://github.com/oceanprotocol/docs/blob/master/content/concepts/testnets.md
line: 28

Technical Details about the Public Testnets
Details about the Nile Testnet (which is called the "Parity Secret Store Cluster" on that page).

The link returns a 404

Once we have a more stable/LTS version of squid-js, we should let readers choose which version of the squid-js reference docs they want to see, e.g. version 1.0.x LTS or "latest".

This functionality is already available from ReadTheDocs (used for squid-py) and javadoc.io (used for squid-java). ReadTheDocs lets us (the admins) make certain git tags or branches available for readers. ReadTheDocs grabs that specific commit to render the docs in question. I don't know how javadoc.io works.

Add mechanisms for rendering spec from JavaDoc comments.

• create prototype assuming usage and output of https://github.com/allnulled/javadoc
• get final spec as structured data (will be solved over on https://github.com/oceanprotocol/squid-java/issues/46)
• add squid-java as git submodule
• generate page(s) from spec file on site build
• create template for JavaDoc specs

Currently will be just stacked on top so figure out a nice pattern for using the menu on mobile. If nothing helps, just put behind a hamburger

There have been updates to the gatsby monorepo:

• • The dependency gatsby-plugin-offline was updated from 2.0.19 to 2.0.20.

• The dependency gatsby-plugin-react-helmet was updated from 3.0.4 to 3.0.5.
• The dependency gatsby-plugin-sharp was updated from 2.0.15 to 2.0.16.
• The dependency gatsby-remark-copy-linked-files was updated from 2.0.7 to 2.0.8.
• The dependency gatsby-remark-responsive-iframe was updated from 2.0.7 to 2.0.8.
• The dependency gatsby-transformer-remark was updated from 2.1.16 to 2.1.17.
• The dependency gatsby was updated from 2.0.74 to 2.0.75.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the gatsby group definition.

gatsby is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Would be great to get consistent and maintainable flowcharts, diagrams, etc. in Markdown.

Mermaid looks flexible and more importantly, is completely on brand:

• https://github.com/knsv/mermaid

On the Gatsby side of things, this should help:

• https://github.com/rhanekom/gatsby-remark-draw

In the end we would have something like this https://rhanekom.github.io/gatsby-remark-draw-demo/mermaid/

prepend with github.com/ORG/REPO/tree/BRANCH/

There have been updates to the gatsby monorepo:

• • The dependency gatsby-image was updated from 2.0.30 to 2.0.31.

• The dependency gatsby-plugin-catch-links was updated from 2.0.11 to 2.0.12.
• The dependency gatsby-plugin-google-analytics was updated from 2.0.15 to 2.0.16.
• The dependency gatsby-plugin-manifest was updated from 2.0.21 to 2.0.22.
• The dependency gatsby-plugin-offline was updated from 2.0.23 to 2.0.24.
• The dependency gatsby-plugin-react-helmet was updated from 3.0.7 to 3.0.8.
• The dependency gatsby-plugin-sharp was updated from 2.0.24 to 2.0.25.
• The dependency gatsby-plugin-sitemap was updated from 2.0.5 to 2.0.6.
• The dependency gatsby-remark-autolink-headers was updated from 2.0.14 to 2.0.15.
• The dependency gatsby-remark-images was updated from 3.0.5 to 3.0.6.
• The dependency gatsby-source-filesystem was updated from 2.0.22 to 2.0.23.
• The dependency gatsby-source-graphql was updated from 2.0.12 to 2.0.13.
• The dependency gatsby-transformer-remark was updated from 2.3.0 to 2.3.1.
• The dependency gatsby-transformer-sharp was updated from 2.1.14 to 2.1.15.
• The dependency gatsby was updated from 2.1.27 to 2.1.28.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the gatsby group definition.

gatsby is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

It would be nice to have API documentation for squid-js as part of the docs site, if that makes sense.

@kremalicious You're much more familiar with the JavaScript world and the common practices around documenting JavaScript APIs, and you used squid-js when working on Pleuston, so I'll assign this issue to you.

Currently, only the repos on front-page pick up the data added in data/repositories.yml.

Expected

Whenever the <repo> component is used in a markdown document, add data from data/repositories.yml for the respective repository.

There have been updates to the gatsby monorepo:

• • The dependency gatsby-plugin-react-helmet was updated from 3.0.3 to 3.0.4.

• The dependency gatsby-plugin-sass was updated from 2.0.6 to 2.0.7.
• The dependency gatsby-remark-prismjs was updated from 3.1.3 to 3.1.4.
• The dependency gatsby-source-filesystem was updated from 2.0.10 to 2.0.11.
• The dependency gatsby was updated from 2.0.62 to 2.0.63.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the gatsby group definition.

gatsby is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

There have been updates to the gatsby monorepo:

• • The dependency gatsby-plugin-offline was updated from 2.0.19 to 2.0.20.

• The dependency gatsby-remark-copy-linked-files was updated from 2.0.7 to 2.0.8.
• The dependency gatsby was updated from 2.0.67 to 2.0.68.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the gatsby group definition.

gatsby is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

There have been updates to the gatsby monorepo:

• • The dependency gatsby-plugin-react-helmet was updated from 3.0.3 to 3.0.4.

• The dependency gatsby-plugin-sass was updated from 2.0.6 to 2.0.7.
• The dependency gatsby-remark-prismjs was updated from 3.1.3 to 3.1.4.
• The dependency gatsby-source-filesystem was updated from 2.0.10 to 2.0.11.
• The dependency gatsby was updated from 2.0.62 to 2.0.63.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the gatsby group definition.

gatsby is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

set cache to max-age=0

When a new commit happens on a submodule in the tracked branch, docs site needs a commit to master triggering a new build & deploy via Travis.

and I'm not sure how to fix it. Editing config.js won't work.

There have been updates to the gatsby monorepo:

• • The dependency gatsby-image was updated from 2.0.28 to 2.0.29.

• The dependency gatsby-plugin-catch-links was updated from 2.0.9 to 2.0.10.
• The dependency gatsby-plugin-google-analytics was updated from 2.0.12 to 2.0.13.
• The dependency gatsby-plugin-manifest was updated from 2.0.16 to 2.0.17.
• The dependency gatsby-plugin-offline was updated from 2.0.21 to 2.0.22.
• The dependency gatsby-plugin-react-helmet was updated from 3.0.5 to 3.0.6.
• The dependency gatsby-plugin-sass was updated from 2.0.9 to 2.0.10.
• The dependency gatsby-plugin-sharp was updated from 2.0.19 to 2.0.20.
• The dependency gatsby-plugin-sitemap was updated from 2.0.4 to 2.0.5.
• The dependency gatsby-remark-autolink-headers was updated from 2.0.12 to 2.0.13.
• The dependency gatsby-remark-copy-linked-files was updated from 2.0.8 to 2.0.9.
• The dependency gatsby-remark-images was updated from 3.0.2 to 3.0.3.
• The dependency gatsby-remark-prismjs was updated from 3.2.3 to 3.2.4.
• The dependency gatsby-remark-responsive-iframe was updated from 2.0.8 to 2.0.9.
• The dependency gatsby-remark-smartypants was updated from 2.0.7 to 2.0.8.
• The dependency gatsby-source-filesystem was updated from 2.0.19 to 2.0.20.
• The dependency gatsby-source-graphql was updated from 2.0.9 to 2.0.10.
• The dependency gatsby-transformer-remark was updated from 2.2.3 to 2.2.4.
• The dependency gatsby-transformer-sharp was updated from 2.1.12 to 2.1.13.
• The dependency gatsby-transformer-yaml was updated from 2.1.7 to 2.1.8.
• The dependency gatsby was updated from 2.0.114 to 2.0.115.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the gatsby group definition.

gatsby is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

When I put a link to https://docs.oceanprotocol.com/ on its own line in Medium, Medium transforms it into one of these box embed things:

The square image on the right chops off some words. It is probably based on some HTML meta tag. This Medium docs page says they use embed.ly:

https://help.medium.com/hc/en-us/articles/214981378-Embeds

and this embed.ly support page says something about how they choose the image to show:

https://support.embed.ly/hc/en-us/articles/204266025-Why-does-Embedly-choose-the-image-that-it-does-

This is not tolerable:

Somehow remark puts in some <p> when a nested list is used, causing the spacing. So either:

• stop remark from adding those <p>, OR
• hack in a visual fix with CSS only

There have been updates to the gatsby monorepo:

• • The dependency gatsby-plugin-react-helmet was updated from 3.0.3 to 3.0.4.

• The dependency gatsby-plugin-sass was updated from 2.0.6 to 2.0.7.
• The dependency gatsby-remark-prismjs was updated from 3.1.3 to 3.1.4.
• The dependency gatsby-source-filesystem was updated from 2.0.10 to 2.0.11.
• The dependency gatsby was updated from 2.0.62 to 2.0.63.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the gatsby group definition.

gatsby is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The important stuff works but syntax highlighting is a bit funky at the moment. As long as we don't use too much advanced features of Swagger spec, should be fine for our use case. As soon as we hit some limitation we need to revisit and update.

Collecting remaining issues on here:

• solve spec validation errors, see oceanprotocol/aquarius#110
• output all request example fields, get inspiration from
  https://github.com/temando/open-api-renderer & https://github.com/aaronshaf/react-openapi
• make indentation and syntax highlighting consistent for all example fields
• remove hacky path reduction string manipulation (see oceanprotocol-archive/brizo#29 & oceanprotocol/aquarius#114)
• automate spec file updates (#74)
• look into executing API calls (might not be possible until we have aquarius/brizo instance in the cloud somewhere)
• scroll spy for sidebar TOC (highlight active section heading)
• ...

These links should either show something, or simply redirect to first sub-item:

• /concepts/
• /setup/
• /tutorials/

i found some old information on the docs: https://docs.oceanprotocol.com/concepts/architecture/#keeper-contracts

Token Curated Registries (TCRs) - Users create challenges and resolve them through voting to maintain registries.
Ocean Tokens - The intrinsic tokens circulated inside the Ocean Network, which is used when voting within TCRs.
Curated Proofs Market - The core component where people can transact with each other and curate assets through staking with Ocean tokens.

TCR & CPM are not in keeper right now.

There have been updates to the gatsby monorepo:

• • The dependency gatsby-image was updated from 2.0.22 to 2.0.23.

• The dependency gatsby-plugin-offline was updated from 2.0.18 to 2.0.19.
• The dependency gatsby-plugin-react-helmet was updated from 3.0.3 to 3.0.4.
• The dependency gatsby-plugin-sass was updated from 2.0.6 to 2.0.7.
• The dependency gatsby-plugin-sharp was updated from 2.0.14 to 2.0.15.
• The dependency gatsby-remark-prismjs was updated from 3.1.3 to 3.1.4.
• The dependency gatsby-source-filesystem was updated from 2.0.11 to 2.0.12.
• The dependency gatsby was updated from 2.0.64 to 2.0.65.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the gatsby group definition.

gatsby is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

There have been updates to the gatsby monorepo:

• • The dependency gatsby-image was updated from 2.0.32 to 2.0.33.

• The dependency gatsby-plugin-catch-links was updated from 2.0.12 to 2.0.13.
• The dependency gatsby-plugin-google-analytics was updated from 2.0.16 to 2.0.17.
• The dependency gatsby-plugin-manifest was updated from 2.0.23 to 2.0.24.
• The dependency gatsby-plugin-offline was updated from 2.0.24 to 2.0.25.
• The dependency gatsby-plugin-react-helmet was updated from 3.0.8 to 3.0.9.
• The dependency gatsby-plugin-sass was updated from 2.0.10 to 2.0.11.
• The dependency gatsby-plugin-sharp was updated from 2.0.27 to 2.0.28.
• The dependency gatsby-plugin-sitemap was updated from 2.0.8 to 2.0.9.
• The dependency gatsby-remark-autolink-headers was updated from 2.0.15 to 2.0.16.
• The dependency gatsby-remark-copy-linked-files was updated from 2.0.9 to 2.0.10.
• The dependency gatsby-remark-images was updated from 3.0.8 to 3.0.9.
• The dependency gatsby-remark-prismjs was updated from 3.2.4 to 3.2.5.
• The dependency gatsby-remark-responsive-iframe was updated from 2.0.9 to 2.0.10.
• The dependency gatsby-remark-smartypants was updated from 2.0.8 to 2.0.9.
• The dependency gatsby-source-filesystem was updated from 2.0.24 to 2.0.25.
• The dependency gatsby-source-graphql was updated from 2.0.13 to 2.0.14.
• The dependency gatsby-transformer-remark was updated from 2.3.2 to 2.3.3.
• The dependency gatsby-transformer-sharp was updated from 2.1.16 to 2.1.17.
• The dependency gatsby-transformer-yaml was updated from 2.1.9 to 2.1.10.
• The dependency gatsby was updated from 2.1.31 to 2.1.32.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the gatsby group definition.

gatsby is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

There have been updates to the gatsby monorepo:

• • The dependency gatsby-image was updated from 2.0.34 to 2.0.35.

• The dependency gatsby-plugin-google-analytics was updated from 2.0.17 to 2.0.18.
• The dependency gatsby-plugin-manifest was updated from 2.0.24 to 2.0.25.
• The dependency gatsby-plugin-react-helmet was updated from 3.0.10 to 3.0.11.
• The dependency gatsby-plugin-sharp was updated from 2.0.31 to 2.0.32.
• The dependency gatsby-transformer-yaml was updated from 2.1.10 to 2.1.11.
• The dependency gatsby was updated from 2.3.2 to 2.3.3.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the gatsby group definition.

gatsby is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Seems gatsby-source-graphql only gets data on build time, and the refetchInterval is meant for local development. So gatsby-source-graphql can only provide the data we need for the server-rendered pages, and the initial client page.

For continuously updating the repo data without a new build & deploy, the repo component needs to be made into a hybrid component, where a new fetch call is needed updating the info on client side.

The current flow of having to run brizo or aquarius to get the API documentation is a bit cumbersome.

As a quick hack we could just link to some deployed Swagger output from those repos, or look into SwaggerHub https://swagger.io/tools/swaggerhub/

Ideally, we figure out a way how to integrate Swagger with Gatsby, so API docs can be browsed under the docs site.

Horizontal scrolling is hard without a touch screen or a fancy Mac trackpad. So add 2 things:

• custom scrollbar should be bigger on hover so it can be dragged more easily
• when there is an overflow, show clickable left/right arrows at beginning/end of a row

Feels like half the Travis builds are failing because of API errors. Simply restarting those failed builds usually works.

If error occurs, it looks like this:

The GraphQL query from /home/travis/build/oceanprotocol/docs/src/components/Repositories/Repository.jsx failed.
Errors:
  Something went wrong while executing your query. Please include `AE24:722D:20DF2FD:45B79D6:5C07C446` when reporting this issue.
  
  GraphQL request (3:5)
  2:   github {
  3:     organization(login: "oceanprotocol") {
         ^
  4:       repositories(first: 100, privacy: PUBLIC, isFork: false) {

Same happens sometimes when running local dev server, which refetches those GraphQL queries periodically. And if that fails, dev server has to be restarted.

• does API have a rate limit?
• does access token need more scope?

The dependency gatsby-remark-embed-video was updated from 1.6.1 to 1.7.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

gatsby-remark-embed-video is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Redirect to docs.oceanprotocol.com/concepts/wallets/

1. client redirect
2. 301 redirect

The 301 redirect could be done using Cloudflare "page rules" but I wonder it there's a better way, because Cloudflare makes you pay if you want to have lots of page rules.

This issue was suggested by @kremalicious in the comments on pull request #148

There have been updates to the gatsby monorepo:

• • The dependency gatsby-plugin-offline was updated from 2.0.19 to 2.0.20.

• The dependency gatsby-remark-copy-linked-files was updated from 2.0.7 to 2.0.8.
• The dependency gatsby-transformer-remark was updated from 2.1.16 to 2.1.17.
• The dependency gatsby was updated from 2.0.70 to 2.0.71.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the gatsby group definition.

gatsby is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Once everything is live:

• allow indexing of docs.oceanprotocol.com again
• disallow indexing of betadocs.oceanprotocol.com, with some Node env when building the site
• add Twitter Cards/Open Graph/schema.org head tags (done in #63)
• generate sitemap.xml
• ping search engines on every live deployment with updated sitemap

There have been updates to the gatsby monorepo:

• • The dependency gatsby-image was updated from 2.0.25 to 2.0.26.

• The dependency gatsby-plugin-google-analytics was updated from 2.0.8 to 2.0.9.
• The dependency gatsby-plugin-manifest was updated from 2.0.12 to 2.0.13.
• The dependency gatsby-plugin-offline was updated from 2.0.19 to 2.0.20.
• The dependency gatsby-plugin-react-helmet was updated from 3.0.4 to 3.0.5.
• The dependency gatsby-plugin-sharp was updated from 2.0.16 to 2.0.17.
• The dependency gatsby-plugin-sitemap was updated from 2.0.3 to 2.0.4.
• The dependency gatsby-remark-copy-linked-files was updated from 2.0.7 to 2.0.8.
• The dependency gatsby-remark-prismjs was updated from 3.1.4 to 3.2.0.
• The dependency gatsby-remark-responsive-iframe was updated from 2.0.7 to 2.0.8.
• The dependency gatsby-source-filesystem was updated from 2.0.14 to 2.0.16.
• The dependency gatsby-source-graphql was updated from 2.0.7 to 2.0.8.
• The dependency gatsby-transformer-remark was updated from 2.1.20 to 2.2.0.
• The dependency gatsby-transformer-sharp was updated from 2.1.9 to 2.1.10.
• The dependency gatsby-transformer-yaml was updated from 2.1.6 to 2.1.7.
• The dependency gatsby was updated from 2.0.90 to 2.0.91.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the gatsby group definition.

gatsby is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

...to work with the latest squid-js (for keeper contracts v0.8.x).

• Page 1: Setup - updated by pull request #180
• Page 2: Publish flow - updated by pull request #182
• Page 3: Consume flow

Bill and I set up Sphinx to auto-generate some API docs for squid-py, but they're not available online yet. We could use readthedocs.org for that. There are many HTML pages with internal cross-references, special formatting, and other things that would be tricky to transform into a form that Gatsby would like. Most sites on readthedocs.org use the standard readthedocs theme, but it's hard to modify the colors etc. There are other Sphinx themes we could use instead, some of which are designed to be easier to style. I did some googling and found:

• https://sphinx-better-theme.readthedocs.io/en/latest/
• http://www.writethedocs.org/guide/tools/sphinx-themes/

squid-py is probably the only Python library where we'd want to have API docs like that. Aquarius and Brizo are written in Python, but end users will only care about the REST API, and we already have issue #35 to figure out how to get the docs for those REST APIs online.

For Aquarius and Brizo we need to find a way to get the most recent Swagger spec as json into the docs build process. At the moment they simply live as manually copied json files in /data.

Ideally, the json file just sits in the original repository, and is updated automatically during every release process. During docs build process I can then either get it through GitHub GraphQL API, or a normal fetch.

We could also fetch it remotely from somewhere else, a Swagger client is already in the docs site.

IMO the terminology is not totally clear/aligned. I would say:

• A Data owner currently in Ocean is also the Publisher, there is no delegation to a third party
• I would remove the Publisher entry because it's included in the Data owner section
• Marketplace or Tribe is a facilitator allowing to discover assets
  https://docs.oceanprotocol.com/concepts/terminology/

There have been updates to the gatsby monorepo:

• • The dependency gatsby-plugin-react-helmet was updated from 3.0.3 to 3.0.4.

• The dependency gatsby-remark-prismjs was updated from 3.1.2 to 3.1.3.
• The dependency gatsby was updated from 2.0.61 to 2.0.62.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the gatsby group definition.

gatsby is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

tbd