Skip to content

LAION-AI/Open-Assistant

main
Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
Code

Latest commit

Bumps
[@next/bundle-analyzer](https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer)
from 13.4.4 to 13.4.7.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/vercel/next.js/releases"><code>@​next/bundle-analyzer</code>'s
releases</a>.</em></p>
<blockquote>
<h2>v13.4.7</h2>
<h3>Core Changes</h3>
<ul>
<li>Route Module Updates Redux: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/51373">#51373</a></li>
<li>Lock down server IPC address: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/51378">#51378</a></li>
<li>Revert &quot;Route Module Updates Redux&quot;: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/51409">#51409</a></li>
<li>Fix bundling of Server Actions: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/51367">#51367</a></li>
<li>Fix pnpm lock: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/51503">#51503</a></li>
<li>router: add layout and other file supports to parallel routes: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/51413">#51413</a></li>
<li>Next Build Turbo POC: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/49942">#49942</a></li>
<li>add edge rendering for app dir for Turbopack: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/50830">#50830</a></li>
<li>Fix shared action module in two layers: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/51510">#51510</a></li>
<li>Revert &quot;Next Build Turbo POC (<a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/49942">#49942</a>)&quot;:
<a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/51538">#51538</a></li>
<li>Fix font styles on react dev overlay: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/51518">#51518</a></li>
<li>fix typo in x-next-revalidate-tag-token header: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/51432">#51432</a></li>
<li>Add docs links to RSC errors: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/51557">#51557</a></li>
<li>Moved new line to warnOnce call: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/51552">#51552</a></li>
<li>Update id env prefix: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/51588">#51588</a></li>
<li>router: support layout/special files as direct children of parallel
routes: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/51604">#51604</a></li>
<li>use env var to switch next.js to turbopack mode: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/51353">#51353</a></li>
<li>Revert &quot;add edge rendering for app dir for Turbopack&quot;: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/51617">#51617</a></li>
<li>Ensure upgrade request has request meta: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/51590">#51590</a></li>
<li>Revert &quot;Fix standalone not found&quot;: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/51506">#51506</a></li>
</ul>
<h3>Documentation Changes</h3>
<ul>
<li>docs: Add streaming AI example.: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/51382">#51382</a></li>
<li>docs: remove copy mentioning appDir as an experimental feature: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/51403">#51403</a></li>
<li>examples: update <code>with-supabase</code> example to App Router:
<a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/51335">#51335</a></li>
<li>Fix typo in image alt: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/51487">#51487</a></li>
<li>docs: add better examples to <code>next/image</code> docs.: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/51457">#51457</a></li>
<li>Go directly to caching section: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/51501">#51501</a></li>
<li>fix(typo): add missing word: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/51490">#51490</a></li>
<li>fix(typo): add missing comma: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/51489">#51489</a></li>
<li>Remove duplicate bullet point in app router migration docs: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/51440">#51440</a></li>
<li>fix: missing come: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/51437">#51437</a></li>
<li>Linted MDX: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/51530">#51530</a></li>
<li>docs: Fix typo: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/51517">#51517</a></li>
<li>Migrate validate links script from next-site and setup GitHub
action: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/51365">#51365</a></li>
<li>Remove extra word in env key error: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/51512">#51512</a></li>
<li>Remove duplicate word in 11-draft-mode.mdx: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/51580">#51580</a></li>
<li>Broken link at 01-static-and-dynamic-rendering.mdx: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/51582">#51582</a></li>
<li>refactor tests for readability: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/51051">#51051</a></li>
</ul>
<h3>Example Changes</h3>
<ul>
<li>Upgrade with-redux example to app router: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/49994">#49994</a></li>
</ul>
<h3>Misc Changes</h3>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/vercel/next.js/commit/4e5fef4f36b27fb7d3ae2b06ce4c53347e96363f"><code>4e5fef4</code></a>
v13.4.7</li>
<li><a
href="https://github.com/vercel/next.js/commit/6dd06dbe4dafdc4679d940b5b5d004acdbf113a6"><code>6dd06db</code></a>
v13.4.7-canary.4</li>
<li><a
href="https://github.com/vercel/next.js/commit/c30f21fa7713015057d06067ee5c7f5270c98fff"><code>c30f21f</code></a>
v13.4.7-canary.3</li>
<li><a
href="https://github.com/vercel/next.js/commit/3d23faa6cda08507ab96c2fe6576b9621372e17e"><code>3d23faa</code></a>
v13.4.7-canary.2</li>
<li><a
href="https://github.com/vercel/next.js/commit/a3ef99acd9805dded24214c21ac9149952af73a7"><code>a3ef99a</code></a>
v13.4.7-canary.1</li>
<li><a
href="https://github.com/vercel/next.js/commit/cbb69b2cfc19d95cf914250f7c20d4d9a42e8bc5"><code>cbb69b2</code></a>
v13.4.7-canary.0</li>
<li><a
href="https://github.com/vercel/next.js/commit/ce4aa787e8fade5f8214817f8ad9db02ca807a95"><code>ce4aa78</code></a>
v13.4.6</li>
<li><a
href="https://github.com/vercel/next.js/commit/019ed1c39b255e7ed0176e94add52b1e7685063e"><code>019ed1c</code></a>
v13.4.6-canary.8</li>
<li><a
href="https://github.com/vercel/next.js/commit/c59c39a431c641aeef76f08d4048c1e039174f6f"><code>c59c39a</code></a>
v13.4.6-canary.7</li>
<li><a
href="https://github.com/vercel/next.js/commit/dde67aec5aa8d9df499152d1194b826cf86e967d"><code>dde67ae</code></a>
v13.4.6-canary.6</li>
<li>Additional commits viewable in <a
href="https://github.com/vercel/next.js/commits/v13.4.7/packages/next-bundle-analyzer">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=@next/bundle-analyzer&package-manager=npm_and_yarn&previous-version=13.4.4&new-version=13.4.7)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)


</details>

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
b9a6e99

Git stats

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
May 31, 2023 20:51
May 23, 2023 15:04
June 13, 2023 11:41
May 23, 2023 15:04
June 5, 2023 10:44
May 23, 2023 15:04
June 5, 2023 10:44
December 13, 2022 06:24
January 1, 2023 13:35

Open-Assistant

GitHub Repo stars Docs GitHub Workflow Status GitHub Workflow Status GitHub Workflow Status GitHub Workflow Status GitHub Workflow Status GitHub Workflow Status GitHub Workflow Status GitHub Workflow Status GitHub release (latest by date) Translate

Table of Contents


What is Open Assistant?

Open Assistant is a project meant to give everyone access to a great chat based large language model.

We believe that by doing this we will create a revolution in innovation in language. In the same way that stable-diffusion helped the world make art and images in new ways we hope Open Assistant can help improve the world by improving language itself.

Useful Links

How To Try It Out

Chatting with the AI

The chat frontend is now live here. Log in and start chatting! Please try to react with a thumbs up or down for the assistant's responses when chatting.

Contributing to Data Collection

The data collection frontend is now live here. Log in and start taking on tasks! We want to collect a high volume of quality data. By submitting, ranking, and labelling model prompts and responses you will be directly helping to improve the capabilities of Open Assistant.

Running the Development Setup Locally (without chat)

You do not need to run the project locally unless you are contributing to the development process. The website link above will take you to the public website where you can use the data collection app and the chat.

If you would like to run the data collection app locally for development, you can set up an entire stack needed to run Open-Assistant, including the website, backend, and associated dependent services, with Docker.

To start the demo, run this in the root directory of the repository (check this FAQ if you have problems):

docker compose --profile ci up --build --attach-dependencies

Note: when running on MacOS with an M1 chip you have to use: DB_PLATFORM=linux/x86_64 docker compose ...

Then, navigate to http://localhost:3000 (It may take some time to boot up) and interact with the website.

Note: If an issue occurs with the build, please head to the FAQ and check out the entries about Docker.

Note: When logging in via email, navigate to http://localhost:1080 to get the magic email login link.

Note: If you would like to run this in a standardized development environment (a "devcontainer") using vscode locally or in a web browser using GitHub Codespaces, you can use the provided .devcontainer folder.

Running the Development Setup Locally for Chat

You do not need to run the project locally unless you are contributing to the development process. The website link above will take you to the public website where you can use the data collection app and the chat.

Also note that the local setup is only for development and is not meant to be used as a local chatbot, unless you know what you are doing.

If you do know what you are doing, then see the inference folder for getting the inference system up and running, or have a look at --profile inference in addition to --profile ci in the above command.

The Vision

We are not going to stop at replicating ChatGPT. We want to build the assistant of the future, able to not only write email and cover letters, but do meaningful work, use APIs, dynamically research information, and much more, with the ability to be personalized and extended by anyone. And we want to do this in a way that is open and accessible, which means we must not only build a great assistant, but also make it small and efficient enough to run on consumer hardware.

The Plan

We want to get to an initial MVP as fast as possible, by following the 3-steps outlined in the InstructGPT paper
  1. Collect high-quality human generated Instruction-Fulfillment samples (prompt + response), goal >50k. We design a crowdsourced process to collect and reviewed prompts. We do not want to train on flooding/toxic/spam/junk/personal information data. We will have a leaderboard to motivate the community that shows progress and the most active users. Swag will be given to the top-contributors.
  2. For each of the collected prompts we will sample multiple completions. Completions of one prompt will then be shown randomly to users to rank them from best to worst. Again this should happen crowd-sourced, e.g. we need to deal with unreliable potentially malicious users. At least multiple votes by independent users have to be collected to measure the overall agreement. The gathered ranking-data will be used to train a reward model.
  3. Now follows the RLHF training phase based on the prompts and the reward model.

We can then take the resulting model and continue with completion sampling step 2 for a next iteration.

Slide Decks

Vision & Roadmap

Important Data Structures

How You Can Help

All open source projects begin with people like you. Open source is the belief that if we collaborate we can together gift our knowledge and technology to the world for the benefit of humanity.

Check out our contributing guide to get started.