Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / AtomBuild/atom-build-cargo issues and pull requests

#93 - build-cargo 2.0.0 doesn't work

Issue - State: open - Opened by mabushey over 4 years ago

#92 - Feature request: add `cargo check`

Issue - State: open - Opened by refaelsh over 5 years ago - 1 comment

#91 - Build Target Options Unavailable with Atom 1.17.2

Issue - State: closed - Opened by zyvitski over 7 years ago - 1 comment

#90 - Ability to run `cargo test` with arguments - e.g. run only single test

Issue - State: open - Opened by AndiDog over 7 years ago
Labels: enhancement

#89 - Ensure that cargo clippy is always run with nightly

Issue - State: open - Opened by oli-obk over 7 years ago

#88 - cannot trace to cargo with the correct path

Issue - State: open - Opened by Garfield-Finch almost 8 years ago - 1 comment

#87 - Deprecate this package in favor of implementing languageserver-rust

Issue - State: open - Opened by oli-obk almost 8 years ago
Labels: question

#86 - Add option to disable notifications

Issue - State: open - Opened by bfil almost 8 years ago - 6 comments

#85 - panics with new lines are not matched

Issue - State: open - Opened by colin-kiegel almost 8 years ago - 5 comments

#84 - panics in workspace members are not matched

Issue - State: closed - Opened by colin-kiegel almost 8 years ago - 1 comment

#83 - Cargo check with JSON output

Issue - State: open - Opened by TheStealthReporter almost 8 years ago - 1 comment

#82 - How do I use it?

Issue - State: closed - Opened by fschutt almost 8 years ago - 4 comments

#81 - Deprecated selector in `build-cargo\styles\linter.less`

Issue - State: closed - Opened by Arzte about 8 years ago - 1 comment

#79 - use cargo for passing `--color=always`

Pull Request - State: closed - Opened by oli-obk about 8 years ago

#78 - Can't run default binary

Issue - State: closed - Opened by radix about 8 years ago - 1 comment

#77 - add a setting to use `xargo` instead of `cargo`

Issue - State: closed - Opened by oli-obk about 8 years ago - 1 comment

#76 - Ignore Cargo general messages

Pull Request - State: closed - Opened by alygin about 8 years ago - 4 comments

#75 - Uncaught TypeError: Cannot read property 'charAt' of undefined

Issue - State: closed - Opened by jgrund about 8 years ago - 3 comments

#74 - JSON error format used in cargo clean?

Issue - State: closed - Opened by swsnr about 8 years ago

#73 - "cargo run bin" runs my program three times at once

Issue - State: open - Opened by radix about 8 years ago - 3 comments

#72 - fix cargo update with `--message-format`

Pull Request - State: closed - Opened by oli-obk about 8 years ago - 5 comments

#71 - Error explanation links in std output mode

Pull Request - State: closed - Opened by alygin about 8 years ago - 1 comment

#70 - Fixed parsing of JSON with nested children

Pull Request - State: closed - Opened by alygin about 8 years ago - 2 comments

#69 - complex result json can crash `atom-build`

Issue - State: closed - Opened by oli-obk about 8 years ago
Labels: bug

#68 - Display error explanations in html format

Pull Request - State: closed - Opened by alygin about 8 years ago - 4 comments

#67 - [breaking change] use cargo --message-format for generating json errors

Pull Request - State: closed - Opened by oli-obk about 8 years ago - 2 comments

#66 - Support for new error format in Rust 1.12

Issue - State: closed - Opened by ancwrd1 over 8 years ago - 10 comments

#64 - Building with JSON output prints JSON to output window

Issue - State: open - Opened by randomPoison over 8 years ago - 13 comments

#63 - New error format support

Pull Request - State: closed - Opened by alygin over 8 years ago - 4 comments

#62 - JSON errors parsing enhancement

Pull Request - State: closed - Opened by alygin over 8 years ago - 2 comments

#61 - update to new Rust error format and/or move to json solely

Issue - State: closed - Opened by oli-obk over 8 years ago - 4 comments

#60 - update version

Pull Request - State: closed - Opened by oli-obk over 8 years ago

#59 - Fixed the problem with compile errors within macros

Pull Request - State: closed - Opened by alygin over 8 years ago - 2 comments

#58 - Readme improvement

Pull Request - State: closed - Opened by alygin over 8 years ago - 12 comments

#57 - Support for colored output

Pull Request - State: closed - Opened by alygin over 8 years ago - 11 comments

#56 - support terminal color output

Issue - State: closed - Opened by placrosse over 8 years ago - 7 comments

#55 - Support of a compact backtraces format

Pull Request - State: closed - Opened by alygin over 8 years ago - 1 comment

#54 - Compact backtrace format

Issue - State: closed - Opened by alygin over 8 years ago - 1 comment

#53 - new release?

Issue - State: closed - Opened by colin-kiegel over 8 years ago - 7 comments

#52 - Apply setting on the fly

Pull Request - State: closed - Opened by alygin over 8 years ago - 3 comments

#51 - Fixed source code links in a single-crate project

Pull Request - State: closed - Opened by alygin over 8 years ago

#50 - Apply settings on the fly

Issue - State: closed - Opened by alygin over 8 years ago

#49 - Panic notifications

Pull Request - State: closed - Opened by alygin over 8 years ago - 3 comments

#48 - Fix building multi-crate workspaces in multi-project environment

Pull Request - State: closed - Opened by alygin over 8 years ago

#47 - Fixed regex for panics

Pull Request - State: closed - Opened by alygin over 8 years ago - 1 comment

#46 - Multi-crate projects support

Pull Request - State: closed - Opened by alygin over 8 years ago - 8 comments

#45 - Use notifications for panics

Issue - State: closed - Opened by alygin over 8 years ago - 10 comments

#44 - Should support multi-crate projects and cargo workspaces

Issue - State: closed - Opened by pzol over 8 years ago - 5 comments

#43 - Custom linter messages for Notes, Helps and Panics

Pull Request - State: closed - Opened by alygin over 8 years ago - 3 comments

#42 - Fix unfollowable paths in output messages

Pull Request - State: closed - Opened by alygin over 8 years ago - 2 comments

#41 - File link is invalid when points to the Rust core

Issue - State: closed - Opened by alygin over 8 years ago - 4 comments

#40 - Output parsing enhancement

Pull Request - State: closed - Opened by alygin over 8 years ago - 5 comments

#39 - remove duplication in target generation

Issue - State: closed - Opened by oli-obk over 8 years ago

#38 - Add support for Atom Build warnings

Pull Request - State: closed - Opened by alygin over 8 years ago - 4 comments

#37 - Warnings support

Issue - State: closed - Opened by alygin over 8 years ago - 3 comments

#36 - also match on warnings when running clippy

Pull Request - State: closed - Opened by oli-obk over 8 years ago - 1 comment

#35 - Howto cross build via build-cargo

Issue - State: open - Opened by ephraim over 8 years ago - 10 comments

#34 - extract more information from rustc's json errors

Pull Request - State: closed - Opened by oli-obk over 8 years ago - 1 comment

#33 - add very basic specs

Pull Request - State: closed - Opened by oli-obk over 8 years ago - 1 comment

#32 - Add support for Atom commands and `cargo run --release`

Pull Request - State: closed - Opened by funmaker over 8 years ago - 1 comment

#31 - 'cmd' cannot contain spaces on Windows 10

Issue - State: closed - Opened by wy193777 almost 9 years ago - 3 comments

#30 - Maintainer wanted!

Issue - State: closed - Opened by noseglid almost 9 years ago - 8 comments
Labels: help wanted

#29 - optionally allow the use of json errors instead of regex parsing

Pull Request - State: closed - Opened by oli-obk almost 9 years ago - 3 comments
Labels: enhancement

#28 - Add support for `cargo run --bin`

Pull Request - State: closed - Opened by aloucks almost 9 years ago - 1 comment

#27 - Add support for `cargo check` and `cargo clippy`

Pull Request - State: closed - Opened by hawkw almost 9 years ago - 6 comments

#26 - rustc can produce errors in json format for easy machine processing

Issue - State: closed - Opened by oli-obk almost 9 years ago - 2 comments

#25 - pass full spans down to atom-build so the linter can show it properly

Pull Request - State: closed - Opened by oli-obk almost 9 years ago - 1 comment

#24 - Don't show stack trace info in the cargo test output

Pull Request - State: closed - Opened by nixpulvis almost 9 years ago - 13 comments

#23 - spaces in path to cargo

Issue - State: closed - Opened by Alexey-Ivanensky almost 9 years ago - 9 comments

#22 - [Feature request] Cargo run

Issue - State: closed - Opened by Pzixel about 9 years ago - 2 comments

#21 - bbbbbbbbbbbbbbbbbbbbcb m mmmmmmm,,,

Issue - State: closed - Opened by Pzixel about 9 years ago - 2 comments

#20 - Plugin doesn't work with build-cargo

Issue - State: closed - Opened by noseglid about 9 years ago - 6 comments

#19 - Add build and run commands for examples

Pull Request - State: closed - Opened by muja about 9 years ago - 5 comments

#18 - put every pattern in its own line

Pull Request - State: closed - Opened by oli-obk about 9 years ago - 1 comment

#17 - refactor match patterns

Pull Request - State: closed - Opened by colin-kiegel about 9 years ago - 1 comment

#16 - Handle error spans

Pull Request - State: closed - Opened by AndiDog about 9 years ago - 1 comment

#15 - "No targets found." when executing "build: Select Active Target"

Issue - State: closed - Opened by yasuyuki about 9 years ago - 2 comments

#14 - Build service API 2

Pull Request - State: closed - Opened by noseglid about 9 years ago

#13 - Usage Instructions? Expectations? "No eligible build target."

Issue - State: closed - Opened by MrAndMrsK about 9 years ago - 7 comments

#12 - Allow warnings in build (debug) and bench, add doc

Pull Request - State: closed - Opened by ebkalderon about 9 years ago - 2 comments

#11 - Support for release builds and benchmarks

Pull Request - State: closed - Opened by ebkalderon about 9 years ago - 5 comments

#10 - Compiler warnings result in "Build failed"

Issue - State: closed - Opened by ebkalderon about 9 years ago - 6 comments

#9 - Feature: cargo build --release

Issue - State: closed - Opened by HenryTheCat about 9 years ago - 5 comments

#8 - Enable Backtrace for `cargo run`

Pull Request - State: closed - Opened by colin-kiegel over 9 years ago - 1 comment

#7 - Enable Backtrace for `cargo test`

Pull Request - State: closed - Opened by colin-kiegel over 9 years ago - 3 comments

#6 - add setting for verbose cargo output

Pull Request - State: closed - Opened by oli-obk over 9 years ago - 2 comments

#5 - add `cargo update` to the commands

Pull Request - State: closed - Opened by oli-obk over 9 years ago - 1 comment

#4 - Setting "Path to the cargo binary"

Pull Request - State: closed - Opened by Arekusei over 9 years ago - 1 comment

#3 - Support "cargo clean"

Pull Request - State: closed - Opened by AndiDog over 9 years ago - 1 comment

#2 - Feature: cargo run

Issue - State: closed - Opened by ghost over 9 years ago

#1 - (From noseglid/atom-build#131)

Pull Request - State: closed - Opened by noseglid over 9 years ago