Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix bugs in documentation and reenable algolia search #3781

Draft
wants to merge 18 commits into
base: main
Choose a base branch
from

Conversation

MichaelHoepler
Copy link
Contributor

This is the PR for just the changes in the docs.

@MichaelHoepler MichaelHoepler added the th/documentation Theme: Related to documentation, including tutorials and API docs label Apr 11, 2024
@MichaelHoepler MichaelHoepler self-assigned this Apr 11, 2024
Copy link

coderabbitai bot commented Apr 11, 2024

Important

Auto Review Skipped

Auto reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@MichaelHoepler MichaelHoepler marked this pull request as draft April 11, 2024 16:47
@frrist
Copy link
Member

frrist commented Apr 18, 2024

@MichaelHoepler feel free to ping me when this is out of draft for a review.

@MichaelHoepler MichaelHoepler marked this pull request as ready for review April 24, 2024 12:28
@MichaelHoepler
Copy link
Contributor Author

@frrist Did you take a look at the PR?

Copy link
Member

@frrist frrist left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Leaving an early comment (I am still reviewing) please revert all changes that are only adding trailing whitespace to the end of lines. There are quite a few of these and it's causing the diff of the PR to be larger (and harder to review) than need be.

In general, aim to make modifications to the docs only where necessary to keep the PR small and review easy. Right now it's a little hard to tell what's changed.

@@ -354,7 +354,7 @@ bacalhau list
bacalhau list --output json
```

## Logs
## Logs
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

a lot of trailing spaces have been added here and else where, we should avoid this.

@@ -1,5 +1,5 @@
---
sidebar_label: Agent
sidebar_label: Agents
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

keep this singular

# Authorization and authentication flow
# Authorization/authentication flow
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Authentication and Authorization are separate things, so keep the "and"

Comment on lines 112 to 129
```yaml
spec:
engine: Docker
verifier: Noop
publisher: IPFS
docker:
image: ubuntu
entryPoint:
- echo
parameters:
- Hello
- World
outputs:
- name: outputs
path: /outputs
engine: Docker
verifier: Noop
publisher: IPFS
docker:
image: ubuntu
entryPoint:
- echo
parameters:
- Hello
- World
outputs:
- name: outputs
path: /outputs
deal:
concurrency: 1
concurrency: 1
```
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yaml is space sensitive, and it looks like you have made modifications here (I assume they were unintentional) please ensure this yaml is still valid and revert this change if its not.

--network network-type Networking capability required by the job (default "nats")
--network network-type Networking capability required by the job (default None)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

revert this, the default network is nats.

Copy link
Member

@frrist frrist left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am going to pause on reviewing this further. The current PR modifies over 70% of the files making up our docs. It is unreasonable to expect a complete review of a PR this size. Please consider taking the following steps to make this work reviewable:

  • Revert all changes which only modify white space.
  • Separate the work done here into multiple PRs with clear descriptions and motivation for the changes they are making.
  • Separate PRs that change document content from PRs that change document styling.

I am all for making our docs better, but we need to approach making these changes with care, and we can do that by breaking this down into reviewable pieces of work.

On the other hand, if you are confident the changes here are correct and would prefer to merge this now and fail forward - making adjustments in follow on PRs - I am good with that too.

@@ -8,7 +8,7 @@ sidebar_position: 2
This page is an introduction to a landscape analysis of general-purpose compute frameworks.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

revert changes to this file.

@@ -14,14 +14,14 @@ The primary objective of the Bacalhau documentation style guide is to help autho

Our goal is to use conversational tone that is natural, and friendly towards the reader and also ensure that the document's content is simple and easy to follow.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

revert changes to this file

@@ -4,19 +4,19 @@ Welcome to the official API documentation for Bacalhau. This guide provides a de

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

revert changes to this file


Bacalhau authenticates and authorizes users in a multi-step flow.

## Requirements
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is the motivation for changing this file? A lot of this content was helpful, why is it being removed?

Comment on lines +43 to +46
## Notes

- Currently, only images published to public registries are supported. Make sure your image is available in one of them, for example DockerHub or ghcr. Private images can be retrieved from docker hub by [specifying your credentials](../../../setting-up/running-node/quick-start-docker.md#authenticate-with-docker-hub).
- Make sure that the architecture of your image matches the architecture of the nodes in your cluster. Also consider the possibility of using [multi-platform](https://docs.docker.com/build/building/multi-platform/) images.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Currently, only images published to public registries are supported

I don't think this is true. The docker daemon attached to the compute node can pull containers it has credentials to access.

Private images can be retrieved from docker hub by ...

Okay now we walk it back, this is correct, we can fetch private images if credentials are provided


Please fix this section, its confusing.

@@ -70,6 +78,7 @@ Publisher:
Bucket: "my-task-results"
Key: "task123/result.tar.gz"
Endpoint: "https://s3.us-west-2.amazonaws.com"
Compress: true
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

remove

3. **Using naming placeholders**:
3. **Docker job writing a single archived file to S3**:
```bash
bacalhau docker run -p s3://bucket/key,opt=compress=true ubuntu ...
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

cc @wdbaruni I believe we remove compress as an option.

@@ -41,4 +41,4 @@ Utilizing IPFS as an input source in Bacalhau via the CLI is straightforward. Be
bacalhau docker run -i ipfs://QmeZRGhe4PmjctYVSVHuEiA9oSXnqmYa4kQubSHgWbjv72:/data ubuntu ...
```

These commands provide a seamless mechanism to fetch and mount data from IPFS directly into your task's execution environment using the Bacalhau CLI.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

revert this change as it appears nothing changed

@@ -12,7 +12,7 @@ Here are the parameters that you can define for an S3 input source:

- **Bucket** `(string: <required>)`: The name of the S3 bucket where the data is stored.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

revert this change

Comment on lines -14 to +13
export GOLANGVER='1.21'
export GOLANGVER='1.20'
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

revert this change. We are using 1.21

@MichaelHoepler MichaelHoepler marked this pull request as draft April 29, 2024 07:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
th/documentation Theme: Related to documentation, including tutorials and API docs
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants