mirror of
https://github.com/sourcegraph/sourcegraph.git
synced 2026-02-06 19:21:50 +00:00
Code AI platform with Code Search & Cody
79226578ec
Right now, we use the default scanner split function, which is `bufio.SplitLines`. This removes the trailing newline and any preceding `\r` before it, then returns the remainder of the token. `PipeOutput` then puts the newline back by invoking `fmt.Fprintln`. This has the positive effect that we essentially normalise `\r\n` and `\n` into `\n`, but the negative effect that every line of output becomes newline-terminated, even if it's a final line that doesn't include a newline. This matters because this output is then used for output variables when executing batch specs, which means that something like `echo -n hi` will end up with an extraneous newline, even though `echo -n` has only written two bytes to stdout. Instead, let's set the split function to one that splits by line, but _retains_ the newline, and then we can write it to the piped writer(s) with `fmt.Fprint` directly. The one tradeoff here is that I haven't reimplemented the `\r` swallowing that `bufio.SplitLines` does. In practice, I don't believe we ever actually used this behaviour: Docker _may_ return extraneous `\r` bytes when running with TTY mode enabled, but we never enable that when executing batch specs, and if the user's container actually outputs `\r` we should actually retain it, rather than trying to filter their output. Fixes #36562. |
||
|---|---|---|
| .buildkite | ||
| .github | ||
| .vscode | ||
| client | ||
| cmd | ||
| dev | ||
| doc | ||
| docker-images | ||
| enterprise | ||
| hacktoberfest | ||
| internal | ||
| lib | ||
| migrations | ||
| monitoring | ||
| schema | ||
| third-party-licenses | ||
| ui/assets | ||
| .dockerignore | ||
| .editorconfig | ||
| .eslintignore | ||
| .eslintrc.js | ||
| .gitattributes | ||
| .gitignore | ||
| .golangci.yml | ||
| .graphqlrc.yml | ||
| .hadolint.yaml | ||
| .mailmap | ||
| .mocharc.js | ||
| .percy.yml | ||
| .prettierignore | ||
| .stylelintignore | ||
| .stylelintrc.json | ||
| .tool-versions | ||
| .trivyignore | ||
| .yarnrc | ||
| babel.config.js | ||
| buf.gen.yaml | ||
| buf.work.yaml | ||
| CHANGELOG.md | ||
| CODENOTIFY | ||
| CONTRIBUTING.md | ||
| doc.go | ||
| go.mod | ||
| go.sum | ||
| graphql-schema-linter.config.js | ||
| gulpfile.js | ||
| jest.config.base.js | ||
| jest.config.js | ||
| LICENSE | ||
| LICENSE.apache | ||
| LICENSE.enterprise | ||
| lighthouserc.js | ||
| package.json | ||
| postcss.config.js | ||
| prettier.config.js | ||
| README.md | ||
| renovate.json | ||
| SECURITY.md | ||
| sg.config.yaml | ||
| shell.nix | ||
| svgo.config.js | ||
| tsconfig.all.json | ||
| tsconfig.eslint.json | ||
| tsconfig.json | ||
| yarn.lock | ||
Sourcegraph is a fast and featureful code search and navigation engine.
Features
- Fast global code search with a hybrid backend that combines a trigram index with in-memory streaming.
- Code intelligence for many languages via the Language Server Index Format.
- Enhances GitHub, GitLab, Phabricator, and other code hosts and code review tools via the Sourcegraph browser extension.
- Integration with third-party developer tools via the Sourcegraph extension API.
Try it now
Sourcegraph has three editions:
- Sourcegraph Cloud lets you search over the open-source ecosystem plus your private code. Search strings, search patterns, search symbols and find references across your entire codebase and the open-source world.
- Sourcegraph Enterprise lets you run your own Sourcegraph instance in your own environment.
- Sourcegraph OSS is an open-source version of Sourcegraph that provides the core functionality of Sourcegraph (code search, code browsing, basic code navigation), but lacks more advanced features (enterprise authentication, repository permissions, admin controls, advanced code navigation, etc.)
Source code for all three editions is contained in this repository. See the License section for more details.
More:
- Install the open-source browser extension to add Sourcegraph-like powers to your code review and code host.
- File feature requests and bug reports in our issue tracker.
- Visit about.sourcegraph.com for more information about features, use cases, and organizations that use Sourcegraph.
Self-hosted installation
Sourcegraph Enterprise (free up to 10 users)
The fastest way to run Sourcegraph self-hosted is with the Docker container. See the quickstart installation guide. There are also several additional ways of running a production instance.
Sourcegraph OSS
- Go through Quickstart to install
sgand dependencies - Start the development environment in OSS mode:
sg start oss
Sourcegraph should now be running at https://sourcegraph.test:3443.
For detailed instructions and troubleshooting, see the local development documentation.
Development
Refer to the Developing Sourcegraph guide to get started.
Documentation
The doc directory has additional documentation for developing and understanding Sourcegraph:
- Project FAQ
- Architecture: high-level architecture
- Database setup: database best practices
- Go style guide
- Documentation style guide
- GraphQL API: useful tips when modifying the GraphQL API
- Contributing
License
This repository contains both OSS-licensed and non-OSS-licensed files. We maintain one repository rather than two separate repositories mainly for development convenience.
All files in the enterprise and client/web/src/enterprise fall under LICENSE.enterprise.
The remaining files fall under the Apache 2 license. Sourcegraph OSS is built only from the Apache-licensed files in this repository.