-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: karma-runner/karma
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v2.0.4
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: karma-runner/karma
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v2.0.5
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 10 commits
- 20 files changed
- 6 contributors
Commits on Jun 21, 2018
-
Configuration menu - View commit details
-
Copy full SHA for 7b66e18 - Browse repository at this point
Copy the full SHA 7b66e18View commit details
Commits on Jun 22, 2018
-
Configuration menu - View commit details
-
Copy full SHA for ad820a1 - Browse repository at this point
Copy the full SHA ad820a1View commit details
Commits on Jul 11, 2018
-
Configuration menu - View commit details
-
Copy full SHA for 850a90b - Browse repository at this point
Copy the full SHA 850a90bView commit details -
fix: remove circular reference in Browser
After migrating the the `browser.js` file to ES2015, the `Browser` class has now fields with circular references (like `emitter`), which breaks the Karma JSON reporters available starting with Karma 2.0.1. This commit removes the circular dependencies by adding a `toJSON()` method to the `Browser` class, which produces a similar result to the browser object before the migration. Fixes #3075
Configuration menu - View commit details
-
Copy full SHA for 518cb11 - Browse repository at this point
Copy the full SHA 518cb11View commit details
Commits on Jul 12, 2018
-
fix(middleware): Obey the Promise API.
Rather than catching and discarding the error if no error handler is passed, let the promise package chain it. This allows use to have a .catch() follow the then().
Configuration menu - View commit details
-
Copy full SHA for 93ba05a - Browse repository at this point
Copy the full SHA 93ba05aView commit details
Commits on Jul 16, 2018
-
Configuration menu - View commit details
-
Copy full SHA for a701732 - Browse repository at this point
Copy the full SHA a701732View commit details
Commits on Jul 17, 2018
-
refactor(filelist): rename promise -> lastCompletedRefresh and remove…
… unused promise (#3060)
Configuration menu - View commit details
-
Copy full SHA for 7617279 - Browse repository at this point
Copy the full SHA 7617279View commit details
Commits on Jul 23, 2018
-
fix(browser): ensure browser state is EXECUTING when tests start (#3074)
* fix(browser): ensure browser state is EXECUTING when tests start Browser state is EXECUTING when it actually started to execute tests. This state change is triggered by client on actual tests execution start. Introduced an additional browser state CONFIGURING The CONFIGURING state means that the browser is not just CONNECTED for tests, but someone has requested tests execution (and provided a config file). But the provided config file is not yet processed, configuration is not applied or the tests execution is not yet started and we have not received the first event from the remote browser, so the browser object is not yet at EXECUTING state. Refactored browser state names: renamed READY -> CONNECTED Fixes #1640
Configuration menu - View commit details
-
Copy full SHA for dc7265b - Browse repository at this point
Copy the full SHA dc7265bView commit details
Commits on Jul 24, 2018
-
Configuration menu - View commit details
-
Copy full SHA for 02dc1f4 - Browse repository at this point
Copy the full SHA 02dc1f4View commit details -
Configuration menu - View commit details
-
Copy full SHA for 0018947 - Browse repository at this point
Copy the full SHA 0018947View commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v2.0.4...v2.0.5