Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

custom ranges not working #57

Open
BrianLenzo opened this issue Aug 18, 2016 · 1 comment
Open

custom ranges not working #57

BrianLenzo opened this issue Aug 18, 2016 · 1 comment

Comments

@BrianLenzo
Copy link

I am trying to use the custom ranges feature and every way I try, I can't get it working.

I tried using the tags, dates, and commits. Each produces the same error (below).

Running this command: grunt changelog:dist:a2f5c3901c5:056c9dc7397

Produces

Security context: 27A25599 <JS Object>
    2: getChanges(aka getChanges) [myworkspace\node_modules\grunt-changelog\tasks\changelog.js:~76] [pc=34EC8F64] (this=27A08099 <undefined>,log=19F9852D <an Object with map 3DFA1E19
>,regex=19AC1FD1 <JS RegExp>)
    3: getChangelog(aka getChangelog) [myworkspace\node_modules\grunt-changelog\tasks\changelog...

FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - process out of memory

I am running 0.3.2 of grunt-changelog and both of those commits do exist in my repo. I am able to run grunt-changelog if I omit any before or after options either in the config or on command line, so it works without that stuff.

@MozilaIP
Copy link

MozilaIP commented Aug 2, 2017

Have the same issue. Running git log command from console runs OK, but task fails with same message as above

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

No branches or pull requests

2 participants