summaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAgeFilesLines
* Bump to 3.11.1Tristan Sloughter2019-06-011-1/+1
|
* Merge pull request #2075 from tsloughter/tmpl-usageFred Hebert2019-05-311-1/+11
|\ | | | | add support for usage message after template is done
| * add support for usage message after template is doneTristan Sloughter2019-05-131-1/+11
| |
* | back to git-based versioningTristan Sloughter2019-05-301-1/+1
| |
* | Bump to 3.11.0Tristan Sloughter2019-05-301-1/+1
| |
* | bug when reread_config from OTP 17Anders Wei2019-05-281-1/+1
| |
* | Update src/rebar_prv_shell.erlTristan Sloughter2019-05-271-1/+1
| | | | | | Co-Authored-By: Fred Hebert <mononcqc@ferd.ca>
* | add support for reading in environment variables from a fileTristan Sloughter2019-05-271-0/+43
| |
* | Do not apply overrides to a root application.Fred Hebert2019-05-191-4/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | Overrides should apply to a layer below where they are declared. This patch makes it so if the project root is an application (i.e. it isn't 'root' and therefore not an umbrella project), we omit applying overrides in rebar_app_discover. This in turn required changing a bunch of tests, because all the tests worked with the idea that all overrides applied to all apps to validate that they get inherited properly. The changes re-structure the cases so they are written with an umbrella app, demonstrating that the changes stick.
* | Remove pre-17 namespaced types workaroundFred Hebert2019-05-141-14/+0
| |
* | Make test suite pass on OTP-22Fred Hebert2019-05-141-1/+1
| | | | | | | | | | - fix some bad typespec - bump the meck version for good fortune
* | add support for git ref and file content as app versionTristan Sloughter2019-05-123-5/+36
|/
* format hex packages in a nice/human wayPierre Fenoll2019-05-062-12/+15
| | | | Signed-off-by: Pierre Fenoll <pierrefenoll@gmail.com>
* Merge pull request #2054 from tolbrino/fix-parallel-edoc-testFred Hebert2019-04-181-3/+3
|\ | | | | Fix duplicate module naming in edoc test suite data
| * Fix duplicate module naming in edoc test suite dataTino Breddin2019-04-161-3/+3
| |
* | Merge pull request #2035 from ankhers/lint_app_fileFred Hebert2019-04-161-0/+31
|\ \ | |/ |/| Add basic linting for .app file
| * An empty list on applications key should not be treated as missingJustin Wood2019-04-161-2/+2
| |
| * Change wording in application linting to be more clearJustin Wood2019-04-161-1/+1
| |
| * Add basic linting for .app fileJustin Wood2019-03-191-0/+31
| | | | | | | | | | This currently just checks for the existence of the description and applications keys and that the applications list has kernel and stdlib in it.
* | Back to git-based versioningTristan Sloughter2019-04-161-1/+1
| |
* | Bump to 3.10.0Tristan Sloughter2019-04-161-1/+1
| |
* | support dialyzer plt location and prefix in cli argsTristan Sloughter2019-04-061-24/+27
| |
* | Merge pull request #2048 from jkakar/jkakar/quieter-test-outputFred Hebert2019-04-051-5/+25
|\ \ | | | | | | rebar3 eunit: Hide slowest tests profile output by default
| * | rebar_prv_eunit: Hide slowest tests profile output by defaultJamu Kakar2019-04-041-5/+25
| | |
* | | Merge pull request #2040 from ferd/max-au-rebar_compiler_parallelFred Hebert2019-04-042-5/+74
|\ \ \ | | | | | | | | Enable parallel build
| * | | Fix Parallel CompilationFred Hebert2019-03-292-5/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch does two things: 1. it broadens the interface for the compiler module so that non-first-file modules can possibly be parallelized. This is done by dynamically switching on `[ListOfFiles]`, which remains sequential as before, or `{[SeqPriority], [Parallel]}`, which divides regular files between higher priority ones and those that can be in parallel 2. implements this mechanism in the rebar compiler, based on the erl file digraph. If a file has an in-neighbour, it is depended on by another file. The mechanism therefore makes it so all files that have dependants get compiled in their strict relative sequential order first, and then the undepended-on files get compiled together in parallel. By running: ./rebar3 ct --suite test/rebar_compile_SUITE.erl --case \ recompile_when_parse_transform_inline_changes --repeat 50 the previous iteration of this would rapidly fail, and this one succeeds every time.
| * | | Enable parallel buildMaxim Fedorov2019-03-281-1/+55
| | | | | | | | | | | | | | | | | | | | Support for parallel compilation of *.erl file was dropped before 3.0 release. However, our tests for a project containing ~500 source files show substantial gain, lowering compilation time from 58 seconds to 18 on a MacBook Pro 15" (4 cores, 8 threads), and to just 10 seconds on Xeon-D machine.
* | | | Catch errors in writing the package cacheBenedikt Reinartz2019-04-041-1/+5
| | | |
* | | | Merge pull request #2037 from Kuroneer/kuroneer/fix-deps-commandFred Hebert2019-04-032-78/+108
|\ \ \ \ | |_|/ / |/| | | Fix rebar3 deps command
| * | | Use maps syntax for OTP 17 in deps cmdJose M Perez2019-04-021-2/+2
| | | |
| * | | Refactor deps command to show lock vs config fileJose M Perez2019-04-012-34/+108
| | | | | | | | | | | | | | | | | | | | | | | | Deps command shows an * if the local state of the dependencies do not match the config file, highlighting the differences between the lock file and the config file if there are any.
| * | | Make deps command check needs_update for every depJose M Perez2019-03-271-71/+27
| |/ / | | | | | | | | | | | | deps command was printing an * even when deps were updated, this commit makes it call rebar_fetch:needs_update/2 for each of them
* | | Attempt at support sys_config_src in shellFred Hebert2019-03-224-30/+119
|/ /
* | Handle incorret app info in escriptizeTino Breddin2019-03-221-5/+10
| |
* | Fix provider hook handling for escriptizeTino Breddin2019-03-221-7/+8
|/ | | | | | | | Previously all escriptize hooks from all apps in the project were executed, which could lead to issue in case of dependencies on artifacts which are created by these hooks. Now the behaviour is similar to the handling of other non-global hooks.
* Remove ignored hex_core artifact from repoPiotr Bober2019-03-181-678/+0
|
* Fix handling of transient locks during upgradeFred Hebert2019-03-151-2/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We currently have a problem in the handling of locks in the `upgrade <app>` command when a transitive dependency switches supervision trees. If we start with: A / \ B1 C | D | E And upgrade to: A / \ B2 C | | E D by calling `rebar3 upgrade b`, we would expect the ugprade command to do so directly. However we are currently left with the following lock file: A / \ B2 C | D | E This is _not_ critical since on the next run, the lock file is fixed automatically through an install-deps sequence. However, this is a jarring state in which to leave a project. The reason is that we proceed the following way to handle an upgrade: 1. pick the name of the chosen app, and unlock it if it's at the level 0 2. grab a list of all its current children (and their own) and unlock them 3. do the same for all the other unlocked dependencies 4. pass this new lock internal format to the get-deps provider in upgrade mode 5. take the result and save it to the lock file. What's interesting is that right now this yields invalid locks at step 3, because we have removed the lock on B1, but not on E (which we don't yet know is going to be a new child of the next B version until we fetch it) In step 4, we fetch dependencies, and in there we compare the pre-upgrade locks and fetch structure with those expected in the current lock state, and rebuild everything. The fix in this commit adds a check there where if the app is in the current lock set at a level deeper than the current one, the lock is forced to be refreshed as if it were not there. This lock would get refreshed on a blank run anyway since the current lock set would start empty (rather than pre-populated by `upgrade`), and the level-order traversal ensures that the locks remain safe in all cases. Fixes #2030
* Back to git-based versioningFred Hebert2019-03-141-1/+1
|
* Bump to 3.9.1Fred Hebert2019-03-141-1/+1
|
* Fix fetching of private packages from orgs on hex repos (#2020)Bryan Paxton2019-03-0727-21/+8498
| | | | | | | | | | | | | - vendor in hex_core at v0.5.0 - Change where repo_name should be the org and not the parent - Changed rebar_utils:url_append_path/2 to not explicitly add a '?', this is returned in the Query chunk by http_uri:parse/1 (e.g., "?foo=bar") - update organization_merging test to expect the sub-repo as the repo_name - Add tests for rebar_utils:url_append_path/2 - Stop referencing/setting "organization" in config and use new organization settings (api_repository and repo_organization) - Do not set (assume) the read key is valid for any/every repo - Set repo_organization and api_repository to org - Update tests to check for new config opts
* Abort when file:consult/1 returns an errorBryan Paxton2019-02-201-3/+13
| | | | | | - Modified rebar_hex_repos:auth_config/1 to abort on error except in the case of enoent, in which we return an empty map. - added auth_config_errors test to test/rebar_pkg_repos_SUITE
* Add plugin version to the output of rebar3 plugin listJustin Wood2019-02-071-2/+2
|
* back to git-based versioningFred Hebert2019-02-051-1/+1
|
* Bump to 3.9.0Fred Hebert2019-02-051-1/+1
|
* Support setting shell hot code loading blacklistsFred Hebert2019-02-041-1/+4
| | | | | | | | | | | | | | | | | | by default, all apps except internal rebar3 ones can be blacklisted. Some months ago, someone added support for configurable lists within rebar3 itself using the .app env. This PR re-exports that functionality from the rebar.config file, so that one can set something like: {shell, [ {app_reload_blacklist, [cowboy, ranch]} ]}. Which will allow to prevent applications that often crash when being reloaded from doing so. For example, cowboy and ranch processes can be stuck in an accept call for multiple reloads in dev, which ends up causing large failures.
* Merge pull request #2011 from ferd/release-switch-in-shellFred Hebert2019-02-041-6/+27
|\ | | | | Add --relvsn and --relname to rebar3 shell
| * Add --relvsn and --relname to rebar3 shellFred Hebert2019-01-311-6/+27
| | | | | | | | | | | | | | Allows to select one of many releases conditionally. Default behaviour should be unchanged from existing one. Can filter on only the version or only the name, or both.
* | Fix handling of updated files in extra_src_dirsFred Hebert2019-02-011-24/+50
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This change fixes cases where changes in .hrl files would not be picked up in .erl files that are in extra source directories (such as those defined with `extra_src_dirs` or modules in the test/ directory during a CT or Eunit run). The problem was due to the way the Directed Acyclic Graph (DAG) of dependencies between files was being loaded and stored by the compiler modules. Prior to this fix, a single DAG would be used for all runs. On a regular run, the prior DAG is loaded from disk, re-checked, and if changed, it would get re-written to disk with the changes deciding what to re-compile. However, whenever extra source directories were specified, a second run would be done which swaps target directories around in the compiler modules. Bug 1: this second run was done without properly tracking the private .hrl files (in src/), so the changes were invisible. This has been fixed by re-adding the paths. The problem is that the DAG handling is self-contained; just invoking it was sufficient to get it loaded and rewritten to disk. But since runs with extra src dirs were done on different sets, the compilation of extra src dirs would be done with bad historical data (all the modules in src/ are dropped, all those in test/ are re-added); this DAG was then written to disk once again, polluting the next non-extra run. This is bug 2, and it is fixed by adding an optional label to each run so that a regular or extra compile round can be distinguished, each tracking their own files in their own DAG. A single test (and a lot of diffing) were sufficient for this.
* | Unhang logger when swapping the TTY in shellFred Hebert2019-01-311-1/+23
|/ | | | | | | | | | | | | | | | | Starting with OTP-21.2.3, some output appears to be sent to the shell while we're taking down the TTY, which ends up stalling the whole log flow for the default handler. I don't have proof but suspect this is due to the system logging going directly from the ERTS runtime to the logger, which may be trigger when we kill the TTY driver. This patch makes it so whenever we detect that logger is active, we save the default config, disable the default logger, and only then we can kill the TTY driver. Once the driver is started and all the group leaders have been rewritten, the default logger is re-added. This all takes place _before_ the logger configuration is updated as part of booting apps, and the change should be fully backwards compatible.
* Use double quotes in git shell command on WindowsAmelia Bellamy-Royds2019-01-241-2/+2
| | | | | | | | Partially reverts commit f52a115ea9d66c812f68200383d769ac300a2828 Fixes #2003 Needs tests to prevent a future regression.
generated by cgit v1.1 at 2024-12-26 06:21:45 +0000