Skip to content

Conversation

@hesreallyhim
Copy link
Contributor

@hesreallyhim hesreallyhim commented Apr 2, 2025

Description of changes

Saw this Issue reporting a broken discord link and figured I'd put together a quick fix.

This link - https://discord.gg/rahcMUU5XV - still seems to work, but i think it's from a different owner/inviter. 🤷

  • Also, I added .python-version to .gitignore because I like to use it for pyenv.
  • Also, I checked off an item on the docs main README TODO's because I think it's completed.
  • Also, when I ran yarn to install, and then yarn dev to run the docs, it made some auto-changes to package.json and next-env.d.ts. Yarn pins the package manager version to the package.json, which would explain the first change.

I also noticed that it looks like the instructions are still using yarn 1 (aka yarn-classic), which is no longer really standard. yarn >=2 made a big change to a plug'n'play type system using corepack. I would recommend we consider switching that over.

Test plan

How are these changes tested?

I ran the docs site locally and verified the broken discord links.

  • Tests pass locally with pytest for python, yarn test for js, cargo test for rust

Documentation Changes

Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the docs repository?

@github-actions
Copy link

github-actions bot commented Apr 2, 2025

Reviewer Checklist

Please leverage this checklist to ensure your code review is thorough before approving

Testing, Bugs, Errors, Logs, Documentation

  • Can you think of any use case in which the code does not behave as intended? Have they been tested?
  • Can you think of any inputs or external events that could break the code? Is user input validated and safe? Have they been tested?
  • If appropriate, are there adequate property based tests?
  • If appropriate, are there adequate unit tests?
  • Should any logging, debugging, tracing information be added or removed?
  • Are error messages user-friendly?
  • Have all documentation changes needed been made?
  • Have all non-obvious changes been commented?

System Compatibility

  • Are there any potential impacts on other parts of the system or backward compatibility?
  • Does this change intersect with any items on our roadmap, and if so, is there a plan for fitting them together?

Quality

  • Is this code of a unexpectedly high quality (Readability, Modularity, Intuitiveness)

.gitignore Outdated
testdata

# Python version
.python-version
Copy link
Contributor Author

Choose a reason for hiding this comment

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

should i remove?

Copy link
Contributor

Choose a reason for hiding this comment

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

yes please

Copy link
Contributor Author

Choose a reason for hiding this comment

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

👍

"typescript": "latest"
}
},
"packageManager": "yarn@1.22.22+sha512.a6b2f7906b721bba3d67d4aff083df04dad64c399707841b7acf00f6b133b7ac24255f2652fa22ae3534329dc6180534e98d17432037ff6fd140556e2bb3137e"
Copy link
Contributor Author

Choose a reason for hiding this comment

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

should i remove?

Copy link
Contributor

Choose a reason for hiding this comment

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

yes please

Copy link
Contributor Author

Choose a reason for hiding this comment

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

👍 i wasn't sure what to do here because the docs just say to yarn install but yarn is no longer recommended as a global dependency, i ended up just using npm to build it.

"typescript": "latest"
}
},
"packageManager": "yarn@1.22.22+sha512.a6b2f7906b721bba3d67d4aff083df04dad64c399707841b7acf00f6b133b7ac24255f2652fa22ae3534329dc6180534e98d17432037ff6fd140556e2bb3137e"
Copy link
Contributor

Choose a reason for hiding this comment

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

yes please

.gitignore Outdated
testdata

# Python version
.python-version
Copy link
Contributor

Choose a reason for hiding this comment

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

yes please

- [ ] swag element in light/dark mode. eg the graphic on the index route
- [ ] turn on algolia once indexed
- [ ] turn back on "edit on github" button when public
- [x] turn back on "edit on github" button when public
Copy link
Contributor

Choose a reason for hiding this comment

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

can we keep the PR about discord links? a lot of the features todo are ood, so we'd want to refresh the whole thing at some point

Copy link
Contributor Author

Choose a reason for hiding this comment

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

yeah for sure... it was just one of those things i caught and wanted to quick-fix but it's better to keep the PR focused

@hesreallyhim hesreallyhim requested a review from jairad26 April 8, 2025 19:30
jeffchuber pushed a commit that referenced this pull request Apr 23, 2025
## Description of changes

This is just closing the loop on #4130 , which seems to have gotten out
of sync with my local branch, so the revision requests I was responding
to weren't getting pushed up, so I'll just close that one. Also, I
noticed that in the meantime @jeffchuber already merged a PR #4286 with
my changes, the only difference being that this adds a link to the
channel. 🤷

So this is a really trivial PR, just making it so that I can close out
the other one and maybe you like this minuscule enhancement.
@jairad26

Co-authored-by: Really Him <hesereallyhim@proton.me>
@hesreallyhim
Copy link
Contributor Author

This branch got borked. See #4363

Inventrohyder pushed a commit to Inventrohyder/chroma that referenced this pull request Aug 5, 2025
## Description of changes

This is just closing the loop on chroma-core#4130 , which seems to have gotten out
of sync with my local branch, so the revision requests I was responding
to weren't getting pushed up, so I'll just close that one. Also, I
noticed that in the meantime @jeffchuber already merged a PR chroma-core#4286 with
my changes, the only difference being that this adds a link to the
channel. 🤷

So this is a really trivial PR, just making it so that I can close out
the other one and maybe you like this minuscule enhancement.
@jairad26

Co-authored-by: Really Him <hesereallyhim@proton.me>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants