id
int64 0
5.38k
| issuekey
stringlengths 4
16
| created
stringlengths 19
19
| title
stringlengths 5
252
| description
stringlengths 1
1.39M
| storypoint
float64 0
100
|
|---|---|---|---|---|---|
290 | CLOV-1665 | 03/13/2015 12:43:55 | as a user I want to use Clover-for-Scala in Eclipse | Integration of Clover-for-Scala with Eclipse. Tasks: * plug into *.scala text editors * show scala classes in the 'Coverage Explorer' * intercept compilation of Scala code (!) Challenge: simultaneous updates of clover.db by Scalac and Javac (similarly as for Groovy in IDE) Out of scope: * test optimization for Scala | 40 |
291 | CLOV-1666 | 03/13/2015 12:48:29 | as a user I want to run test optimization for Scala tests | It should be possible to perform test optimization for Scala test classes. Integrations: * Ant (?) * Maven * SBT * IDEA (?) * Eclipse (?) | 40 |
292 | CLOV-1667 | 03/13/2015 12:58:33 | as a user I want to see smart names for classes and functions in reports | The point is that Scala code is being translated to a bytecode containing various "cryptic" names. For instance, "overloaded operators" have "$op" in method's name. Think how to reasonably represent methods, functions, inline classes, anonymous functions, case classes, traits etc etc in HTML report at least (XML / JSON are less important). | 20 |
293 | CLOV-1668 | 03/13/2015 13:25:11 | Clover installs instrumented-jars in local Maven repo, in place of non-instrument ones | I'm not sure if this has been reintroduced or something else is wrong, since the CLOVKB claims it is not the case: https://confluence.atlassian.com/display/CLOVERKB/Maven+is+deploying+instrumented+jars (I _am_ using the {{instrument}} goal - followed by {{log}} and {{check}}) In the below, you can see that, e.g., {{target/clover/magnolia-module-diff-1.7-SNAPSHOT-clover-tests.jar}} gets copied to {{.../magnolia-module-diff-1.7-SNAPSHOT-tests.jar}} (without {{-clover}} qualifier!) This seems to happen for ~all artifacts except the "main" jar. (test jar, assemblies, etc..). In this case, the situation is saved by the "real" install plugin that gets executed later and overwrites those wrong artifacts. However, if we use the (newish) {{installAtEnd}} feature of the {{maven-install-plugin}}, then this doesn't happen, and we end up with instrumented jars in place of the non-instrumented ones, which has tons of ugly consequences. See for yourself with the snippet:{code:xml} <build> <pluginManagement> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-install-plugin</artifactId> <configuration> <installAtEnd>false</installAtEnd> </configuration> </plugin> </plugins> </pluginManagement> </build> {code} Why is Clover installing anything, anyway ? Shouldn't it just _attach_ the instrumented jars (and only those) to the build, and let Maven do the rest ? {noformat} [INFO] --- maven-clover2-plugin:4.0.2:check (instrument-and-check) @ magnolia-module-diff --- [INFO] [INFO] --- maven-install-plugin:2.5.2:install (default-install) @ magnolia-module-diff --- [INFO] Installing /Users/gjoseph/Dev/magnolia/git/enterprise/diff/target/clover/magnolia-module-diff-1.7-SNAPSHOT-clover.jar to /Users/gjoseph/.m2/repository/info/magnolia/magnolia-module-diff/1.7-SNAPSHOT/magnolia-module-diff-1.7-SNAPSHOT-clover.jar [INFO] Installing /Users/gjoseph/Dev/magnolia/git/enterprise/diff/pom.xml to /Users/gjoseph/.m2/repository/info/magnolia/magnolia-module-diff/1.7-SNAPSHOT/magnolia-module-diff-1.7-SNAPSHOT.pom [INFO] Installing /Users/gjoseph/Dev/magnolia/git/enterprise/diff/target/magnolia-module-diff-1.7-SNAPSHOT-bundle.zip to /Users/gjoseph/.m2/repository/info/magnolia/magnolia-module-diff/1.7-SNAPSHOT/magnolia-module-diff-1.7-SNAPSHOT-bundle.zip [INFO] Installing /Users/gjoseph/Dev/magnolia/git/enterprise/diff/target/magnolia-module-diff-1.7-SNAPSHOT-bundle.tar.gz to /Users/gjoseph/.m2/repository/info/magnolia/magnolia-module-diff/1.7-SNAPSHOT/magnolia-module-diff-1.7-SNAPSHOT-bundle.tar.gz [INFO] Installing /Users/gjoseph/Dev/magnolia/git/enterprise/diff/target/magnolia-module-diff-1.7-SNAPSHOT-tests.jar to /Users/gjoseph/.m2/repository/info/magnolia/magnolia-module-diff/1.7-SNAPSHOT/magnolia-module-diff-1.7-SNAPSHOT-tests.jar [INFO] Installing /Users/gjoseph/Dev/magnolia/git/enterprise/diff/target/clover/magnolia-module-diff-1.7-SNAPSHOT-clover-bundle.zip to /Users/gjoseph/.m2/repository/info/magnolia/magnolia-module-diff/1.7-SNAPSHOT/magnolia-module-diff-1.7-SNAPSHOT-bundle.zip [INFO] Installing /Users/gjoseph/Dev/magnolia/git/enterprise/diff/target/clover/magnolia-module-diff-1.7-SNAPSHOT-clover-bundle.tar.gz to /Users/gjoseph/.m2/repository/info/magnolia/magnolia-module-diff/1.7-SNAPSHOT/magnolia-module-diff-1.7-SNAPSHOT-bundle.tar.gz [INFO] Installing /Users/gjoseph/Dev/magnolia/git/enterprise/diff/target/clover/magnolia-module-diff-1.7-SNAPSHOT-clover-tests.jar to /Users/gjoseph/.m2/repository/info/magnolia/magnolia-module-diff/1.7-SNAPSHOT/magnolia-module-diff-1.7-SNAPSHOT-tests.jar [INFO] [INFO] <<< maven-clover2-plugin:4.0.2:instrument (instrument-and-check) < [clover]install @ magnolia-module-diff <<< [INFO] [INFO] --- maven-clover2-plugin:4.0.2:instrument (instrument-and-check) @ magnolia-module-diff --- [INFO] [INFO] --- maven-clover2-plugin:4.0.2:log (instrument-and-check) @ magnolia-module-diff --- [INFO] Clover Version 4.0.2, built on October 13 2014 (build-943) [...] [INFO] Coverage check PASSED [INFO] [INFO] --- maven-install-plugin:2.5.2:install (default-install) @ magnolia-module-diff --- [INFO] Installing /Users/gjoseph/Dev/magnolia/git/enterprise/diff/target/magnolia-module-diff-1.7-SNAPSHOT.jar to /Users/gjoseph/.m2/repository/info/magnolia/magnolia-module-diff/1.7-SNAPSHOT/magnolia-module-diff-1.7-SNAPSHOT.jar [INFO] Installing /Users/gjoseph/Dev/magnolia/git/enterprise/diff/pom.xml to /Users/gjoseph/.m2/repository/info/magnolia/magnolia-module-diff/1.7-SNAPSHOT/magnolia-module-diff-1.7-SNAPSHOT.pom [INFO] Installing /Users/gjoseph/Dev/magnolia/git/enterprise/diff/target/magnolia-module-diff-1.7-SNAPSHOT-bundle.zip to /Users/gjoseph/.m2/repository/info/magnolia/magnolia-module-diff/1.7-SNAPSHOT/magnolia-module-diff-1.7-SNAPSHOT-bundle.zip [INFO] Installing /Users/gjoseph/Dev/magnolia/git/enterprise/diff/target/magnolia-module-diff-1.7-SNAPSHOT-bundle.tar.gz to /Users/gjoseph/.m2/repository/info/magnolia/magnolia-module-diff/1.7-SNAPSHOT/magnolia-module-diff-1.7-SNAPSHOT-bundle.tar.gz [INFO] Installing /Users/gjoseph/Dev/magnolia/git/enterprise/diff/target/magnolia-module-diff-1.7-SNAPSHOT-tests.jar to /Users/gjoseph/.m2/repository/info/magnolia/magnolia-module-diff/1.7-SNAPSHOT/magnolia-module-diff-1.7-SNAPSHOT-tests.jar [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ {noformat} | 1 |
294 | CLOV-1672 | 03/30/2015 10:56:50 | Ensure that Clover JAR is readable by Ant 1.9.0-1.9.1 | Ant 1.9.0/1.9.1 have a bug related with zip64 file handling: _central directory zip64 extended information extra field's length doesn't match central directory data. Expected length 0 but is 16_ While this bug has been fixed in Ant 1.9.2, it should be still possible to produce such Clover JAR file that it will be readable by buggy Ant versions as well. Ensure that new Clover 4.0.5 (and further versions) will be compatible. | 3 |
295 | CLOV-1675 | 03/31/2015 20:32:32 | Grails Clover Plugin compatibility with Grails 2.4.5, 2.5.0 | New Grails versions have been released recently: * 2.4.5 24/Mar/15 * 2.5 24/Mar/15 Make Grails Clover Plugin compatible with them. | 5 |
296 | CLOV-1679 | 04/15/2015 09:19:43 | MavenIntegrator shall not add arguments if they are already present in original command | This applies to: * build phases * Clover's properties Current problems: 1) The "clean" phase can be doubled For example if original command has: {noformat} mvn clean test {noformat} it becomes: {noformat} mvn clean clean clover2:setup test clover2:aggregate clover2:clover ... {noformat} 2) User cannot override default values of Clover properties For example if a property is already defined: {noformat} mvn test -Dmaven.clover.licenseLocation=/my/clover.license {noformat} MavenIntegrator adds a second one with it's own value: {noformat} mvn test -Dmaven.clover.licenseLocation=/my/clover.license -Dmaven.clover.licenseLocation=/tmp/clover.license {noformat} | 1 |
297 | CLOV-1682 | 04/20/2015 10:12:37 | Repository pollution protection reports a custom classifier under Maven 2.2.x | *Problem:* Probably bug in Maven, needs further investigation. Running "clean clover2:instrument" on a simple project (no additional plugins) with repository pollution protection enabled causes a build failure. {noformat} maven-clover2-plugin-hg\src\it\pollutionProtection>mvn clean clover2:instrument -Dmaven.clover.repositoryPollutionProtection=true [INFO] Scanning for projects... [INFO] snapshot com.atlassian.maven.plugins:maven-clover2-plugin:4.0.4-SNAPSHOT: checking for updates from atlassian-internal [INFO] ------------------------------------------------------------------------ [INFO] Building Unnamed - com.atlassian.maven.plugins.sample:clover-pollution-protection:jar:1.0-SNAPSHOT [INFO] task-segment: [clean, clover2:instrument] [INFO] ------------------------------------------------------------------------ [INFO] [clean:clean {execution: default-clean}] [INFO] Deleting directory f:\Work\maven-clover2-plugin-hg\src\it\pollutionProtection\target [INFO] Preparing clover2:instrument [INFO] snapshot com.atlassian.clover:clover:4.0.4-SNAPSHOT: checking for updates from atlassian-internal [INFO] [clover2:instrumentInternal {execution: default-instrumentInternal}] [INFO] ------------------------------------------------------------------------ [ERROR] BUILD ERROR [INFO] ------------------------------------------------------------------------ [INFO] Clover's repository pollution protection is enabled. Your build produces an artifact (com.atlassian.maven.plugins.sample:clover-pollution-protection:jar:tests:1.0-SNAPSHOT) with a custom classi fier. As Maven does not support multiple classifiers for an artifact, appending second 'clover' classifier may not be handled correctly. You can: - remove a custom classifier or - configure Clover to not append the '-clover' classifier to fix it. You can also disable pollution protection (-Dmaven.clover.repositoryPollutionProtection=false) if you know that it doesn't affect your build. {noformat} Adding extra logging showed that it fails because a custom 'tests' classifier is used during a build - see XXXXXXXXXX below. {noformat} maven-clover2-plugin-hg\src\it\pollutionProtection>mvn clean clover2:instrument [INFO] Scanning for projects... [INFO] snapshot com.atlassian.maven.plugins:maven-clover2-plugin:4.0.4-SNAPSHOT: checking for updates from atlassian-internal [INFO] ------------------------------------------------------------------------ [INFO] Building Unnamed - com.atlassian.maven.plugins.sample:clover-pollution-protection:jar:1.0-SNAPSHOT [INFO] task-segment: [clean, clover2:instrument] [INFO] ------------------------------------------------------------------------ [INFO] [clean:clean {execution: default-clean}] [INFO] Preparing clover2:instrument [INFO] snapshot com.atlassian.clover:clover:4.0.4-SNAPSHOT: checking for updates from atlassian-internal [INFO] [clover2:instrumentInternal {execution: default-instrumentInternal}] [INFO] XXXXXXXXXX CLASSIFIER= com.atlassian.maven.plugins.sample:clover-pollution-protection:jar:tests:1.0-SNAPSHOT [INFO] Clover Version 4.0.4, built on April 15 2015 (build-dev) [INFO] Loaded from: d:\Data\.m2\repository\com\atlassian\clover\clover\4.0.4-SNAPSHOT\clover-4.0.4-SNAPSHOT.jar [INFO] Clover: Developer License registered to Atlassian. [INFO] Creating new database at 'f:\Work\maven-clover2-plugin-hg\src\it\pollutionProtection\target\clover\clover.db'. [INFO] Processing files at 1.8 source level. [INFO] Clover all over. Instrumented 1 file (1 package). [INFO] Elapsed time = 0,077 secs. (12,987 files/sec, 64,935 srclines/sec) [INFO] Clover Version 4.0.4, built on April 15 2015 (build-dev) [INFO] Loaded from: d:\Data\.m2\repository\com\atlassian\clover\clover\4.0.4-SNAPSHOT\clover-4.0.4-SNAPSHOT.jar [INFO] Clover: Developer License registered to Atlassian. [INFO] Updating existing database at 'f:\Work\maven-clover2-plugin-hg\src\it\pollutionProtection\target\clover\clover.db'. [INFO] Processing files at 1.8 source level. [INFO] Clover all over. Instrumented 1 file (1 package). [INFO] 1 test method detected. [INFO] Elapsed time = 0,016 secs. (62,5 files/sec, 562,5 srclines/sec) [INFO] [resources:resources {execution: default-resources}] [WARNING] Using platform encoding (Cp1250 actually) to copy filtered resources, i.e. build is platform dependent! [INFO] skip non existing resourceDirectory f:\Work\maven-clover2-plugin-hg\src\it\pollutionProtection\src\main\resources [INFO] Copying 1 resource [INFO] [compiler:compile {execution: default-compile}] [INFO] Compiling 1 source file to f:\Work\maven-clover2-plugin-hg\src\it\pollutionProtection\target\clover\classes [INFO] [resources:testResources {execution: default-testResources}] [WARNING] Using platform encoding (Cp1250 actually) to copy filtered resources, i.e. build is platform dependent! [INFO] skip non existing resourceDirectory f:\Work\maven-clover2-plugin-hg\src\it\pollutionProtection\src\test\resources [INFO] [compiler:testCompile {execution: default-testCompile}] [INFO] Compiling 1 source file to f:\Work\maven-clover2-plugin-hg\src\it\pollutionProtection\target\clover\test-classes [INFO] [surefire:test {execution: default-test}] [INFO] Surefire report directory: f:\Work\maven-clover2-plugin-hg\src\it\pollutionProtection\target\clover\surefire-reports ------------------------------------------------------- T E S T S ------------------------------------------------------- Running ATest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.168 sec Results : Tests run: 1, Failures: 0, Errors: 0, Skipped: 0 [INFO] [jar:jar {execution: default-jar}] [INFO] Building jar: f:\Work\maven-clover2-plugin-hg\src\it\pollutionProtection\target\clover\clover-pollution-protection-1.0-SNAPSHOT-clover.jar [INFO] [install:install {execution: default-install}] [INFO] Installing f:\Work\maven-clover2-plugin-hg\src\it\pollutionProtection\target\clover\clover-pollution-protection-1.0-SNAPSHOT-clover.jar to d:\Data\.m2\repository\com\atlassian\maven\plugins\sam ple\clover-pollution-protection\1.0-SNAPSHOT\clover-pollution-protection-1.0-SNAPSHOT-clover.jar [INFO] [clover2:instrument {execution: default-cli}] [INFO] XXXXXXXXXX CLASSIFIER= com.atlassian.maven.plugins.sample:clover-pollution-protection:jar:1.0-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESSFUL [INFO] ------------------------------------------------------------------------ {noformat} What's interesting, running the same test but with clover2:setup not only does not fails a build (because repository pollution protection does not fail due to custom classifier if no 'clover' is used), but the artifact produced does NOT have the 'tests' classifier: {noformat} maven-clover2-plugin-hg\src\it\pollutionProtection>mvn clean clover2:setup verify [INFO] Scanning for projects... [INFO] snapshot com.atlassian.maven.plugins:maven-clover2-plugin:4.0.4-SNAPSHOT: checking for updates from atlassian-internal [INFO] ------------------------------------------------------------------------ [INFO] Building Unnamed - com.atlassian.maven.plugins.sample:clover-pollution-protection:jar:1.0-SNAPSHOT [INFO] task-segment: [clean, clover2:setup, verify] [INFO] ------------------------------------------------------------------------ [INFO] [clean:clean {execution: default-clean}] [INFO] Deleting directory f:\Work\maven-clover2-plugin-hg\src\it\pollutionProtection\target [INFO] snapshot com.atlassian.clover:clover:4.0.4-SNAPSHOT: checking for updates from atlassian-internal [INFO] [clover2:setup {execution: default-cli}] [INFO] XXXXXXXXXX CLASSIFIER= com.atlassian.maven.plugins.sample:clover-pollution-protection:jar:1.0-SNAPSHOT [INFO] Clover Version 4.0.4, built on April 15 2015 (build-dev) [INFO] Loaded from: d:\Data\.m2\repository\com\atlassian\clover\clover\4.0.4-SNAPSHOT\clover-4.0.4-SNAPSHOT.jar [INFO] Clover: Developer License registered to Atlassian. [INFO] Creating new database at 'f:\Work\maven-clover2-plugin-hg\src\it\pollutionProtection\target\clover\clover.db'. [INFO] Processing files at 1.8 source level. [INFO] Clover all over. Instrumented 1 file (1 package). [INFO] Elapsed time = 0,057 secs. (17,544 files/sec, 87,719 srclines/sec) [INFO] Clover Version 4.0.4, built on April 15 2015 (build-dev) [INFO] Loaded from: d:\Data\.m2\repository\com\atlassian\clover\clover\4.0.4-SNAPSHOT\clover-4.0.4-SNAPSHOT.jar [INFO] Clover: Developer License registered to Atlassian. [INFO] Updating existing database at 'f:\Work\maven-clover2-plugin-hg\src\it\pollutionProtection\target\clover\clover.db'. [INFO] Processing files at 1.8 source level. [INFO] Clover all over. Instrumented 1 file (1 package). [INFO] 1 test method detected. [INFO] Elapsed time = 0,011 secs. (90,909 files/sec, 818,182 srclines/sec) [INFO] [resources:resources {execution: default-resources}] [WARNING] Using platform encoding (Cp1250 actually) to copy filtered resources, i.e. build is platform dependent! [INFO] skip non existing resourceDirectory f:\Work\maven-clover2-plugin-hg\src\it\pollutionProtection\src\main\resources [INFO] Copying 1 resource [INFO] [compiler:compile {execution: default-compile}] [INFO] Compiling 1 source file to f:\Work\maven-clover2-plugin-hg\src\it\pollutionProtection\target\classes [INFO] [resources:testResources {execution: default-testResources}] [WARNING] Using platform encoding (Cp1250 actually) to copy filtered resources, i.e. build is platform dependent! [INFO] skip non existing resourceDirectory f:\Work\maven-clover2-plugin-hg\src\it\pollutionProtection\src\test\resources [INFO] [compiler:testCompile {execution: default-testCompile}] [INFO] Compiling 1 source file to f:\Work\maven-clover2-plugin-hg\src\it\pollutionProtection\target\test-classes [INFO] [surefire:test {execution: default-test}] [INFO] Surefire report directory: f:\Work\maven-clover2-plugin-hg\src\it\pollutionProtection\target\surefire-reports ------------------------------------------------------- T E S T S ------------------------------------------------------- Running ATest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.155 sec Results : Tests run: 1, Failures: 0, Errors: 0, Skipped: 0 [INFO] [jar:jar {execution: default-jar}] [INFO] Building jar: f:\Work\maven-clover2-plugin-hg\src\it\pollutionProtection\target\clover-pollution-protection-1.0-SNAPSHOT.jar [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESSFUL [INFO] ------------------------------------------------------------------------ {noformat} It affects Maven 2.2.x. Does not occur in Maven 2.1.x or Maven 3.x. Summarizing, it seems that forking a parallel build life cycle causes that an artefact's classifier changes from empty to 'tests': * with clover2:instrument: {noformat} [INFO] [clover2:instrumentInternal {execution: default-instrumentInternal}] [INFO] XXXXXXXXXX CLASSIFIER= com.atlassian.maven.plugins.sample:clover-pollution-protection:jar:tests:1.0-SNAPSHOT ... [INFO] [clover2:instrument {execution: default-cli}] [INFO] XXXXXXXXXX CLASSIFIER= com.atlassian.maven.plugins.sample:clover-pollution-protection:jar:1.0-SNAPSHOT {noformat} * with clover2:setup: {noformat} [INFO] [clover2:setup {execution: default-cli}] [INFO] XXXXXXXXXX CLASSIFIER= com.atlassian.maven.plugins.sample:clover-pollution-protection:jar:1.0-SNAPSHOT {noformat} *Workaround:* * use clover2:setup instead of clover2:instrument to avoid forking life cycle or * use different Maven version or * disable the protection | 3 |
298 | CLOV-1683 | 04/21/2015 10:52:34 | Grails Clover Plugin compatibility with Grails 3.x | Grails 3 has been released (3.0 GA on 31/Mar/15). It uses the Gradle build tool instead of Gant, thus we may need to have Gradle support as well. It has also various changes in API. Implement support for Grails 3 in the Grails Clover Plugin. | 5 |
299 | CLOV-1743 | 05/29/2015 21:24:01 | OutOfMemoryError while flushing coverage data | {noformat} 29-May-2015 12:53:08 ERROR: java.lang.OutOfMemoryError flushing coverage for recorder /media/ephemeral0/bamboo-working-dir/BAM-CLOVER344-UT/components/bamboo-core/target/clover/clover.dbbjv36u_ia9lwdsf: Java heap space 29-May-2015 12:53:08 Exception in thread "CloverFlushThread" java.lang.OutOfMemoryError: Java heap space 29-May-2015 12:53:08 at java.util.zip.DeflaterOutputStream.<init>(DeflaterOutputStream.java:56) 29-May-2015 12:53:08 at com.cenqua.clover.util.FileUtils.createDeflateOutputStream(FileUtils.java:468) 29-May-2015 12:53:08 at com.cenqua.clover.FileBasedGlobalCoverageRecording.write(FileBasedGlobalCoverageRecording.java:39) 29-May-2015 12:53:08 at com.cenqua.clover.GlobalRecordingWriteStrategy$1.write(GlobalRecordingWriteStrategy.java:9) 29-May-2015 12:53:08 at com.cenqua.clover.BaseCoverageRecorder.write(BaseCoverageRecorder.java:108) 29-May-2015 12:53:08 at com.cenqua.clover.FixedSizeCoverageRecorder.write(FixedSizeCoverageRecorder.java:56) 29-May-2015 12:53:08 at com.cenqua.clover.BaseCoverageRecorder.flush(BaseCoverageRecorder.java:302) 29-May-2015 12:53:08 at com.cenqua.clover.BaseCoverageRecorder.flush(BaseCoverageRecorder.java:271) 29-May-2015 12:53:08 at com.cenqua.clover.BaseCoverageRecorder$CloverFlushThread.run(BaseCoverageRecorder.java:155) 29-May-2015 12:55:48 ERROR: java.lang.OutOfMemoryError flushing coverage for recorder /media/ephemeral0/bamboo-working-dir/BAM-CLOVER344-UT/components/bamboo-core/target/clover/clover.dbdozy2b_ia9lwcia: Java heap space 29-May-2015 12:55:48 Exception in thread "CloverFlushThread" java.lang.OutOfMemoryError: Java heap space 29-May-2015 12:56:03 ERROR: java.lang.OutOfMemoryError flushing coverage for recorder /media/ephemeral0/bamboo-working-dir/BAM-CLOVER344-UT/components/bamboo-api/target/clover/clover.dbjcsfjm_ia9lwcij: Java heap space 29-May-2015 12:56:03 Exception in thread "CloverFlushThread" java.lang.OutOfMemoryError: Java heap space {noformat} | 2 |
300 | CLOV-1758 | 06/23/2015 22:52:57 | Support JDK9 by Clover | * As per [https://adtmag.com/articles/2015/05/08/oracle-java.aspx|https://adtmag.com/articles/2015/05/08/oracle-java.aspx] we can expect to have the "feature complete" version before December, 2015. Clover should be ready till then. | 20 |
301 | CLOV-1761 | 07/02/2015 07:32:23 | Add support for Eclipse Mars 4.5 version | Add support for new Eclipse Mars (June 2015) https://adtmag.com/articles/2015/06/30/eclipse-release-train.aspx | 1 |
302 | CLOV-1766 | 07/08/2015 13:57:36 | Eclipse Mars 4.5 does not load platform:/ resources properly | Clover uses "platform:/" URIs to load standard Eclipse icons from eclipse-core such as a package icon, a folder icon etc. Eclipse Mars is buggy and does not always fetch these resources, as a consequence we don't see proper icons on a toolbar. Fix: bundle new icons in Clover-for-Eclipse plugin and replace "platform:/" references by new icons using local URIs. Note: try aligning look of new icons with ADG and Clover's HTML reports. | 2 |
303 | CLOV-1775 | 07/24/2015 15:08:06 | Rename maven-clover2-plugin artifactId to clover-maven-plugin | {panel:title=Decision|titleBGColor=#205081|bgColor=#59afe1} We are currently working on renaming Maven Clover2 Plugin according to the naming convention recommended by the Apache Maven project. Due to a fact that this is a major breaking change, forcing customers to modify their POMs, CI build plans etc, it will be done in the nearest major Clover release (currently planned for end of 2015) and appropriate migration guides will be prepared. New plugin name will be: *clover-maven-plugin* {panel} *Problem reported:* According the Maven's Plugin Naming Convention, Clover's plugin artifactID violates the Apache Maven Trademark. The artifactId should be clover2-maven-plugin. I would even suggest removing the 2 from the artifactId. [Plugin Naming Convention and Apache Maven Trademark|https://maven.apache.org/guides/plugin/guide-java-plugin-development.html] *Scope of the change:* _Before release_ (/) investigate if we can use clover-maven-plugin or must use cloverX-maven-plugin - _will be renamed to clover-maven-plugin_ (/) decide if major Clover release will be numbered 4.1.0 -or 5.0.0- (as per [Semantic Versioning|http://semver.org]) (/) prepare migration message in maven-clover2-plugin pom.xml for versions 4.0.x, similarly as it was done for Clover Core (com.cenqua.clover:clover:3.3.0) - _message added in pom in 4.0.6_ (/) rename maven-clover2-plugin artifactId for 4.1.0 / -5.0.0- , update integration tests (/) prepare migration guide for Clover 4.1 / -5.0- Release Notes (/) update Clover's Tutorial (Moneybags bundled in clover-ant.zip) -> see also CLOV-1827 _After release_ See CLOV-1828. | 3 |
304 | CLOV-1776 | 07/27/2015 06:46:26 | Instrumentation error on certain projects since 4.0.5 build of Clover. | Instrumentation error on certain projects since 4.0.5 build of Clover. Making it a blocker as we can't run Clover on certain projects any longer. {code} build 27-Jul-2015 13:46:14 [INFO] Processing files at 1.8 source level. build 27-Jul-2015 13:46:17 [INFO] Instrumentation error build 27-Jul-2015 13:46:17 java.util.NoSuchElementException build 27-Jul-2015 13:46:17 at java.util.ArrayDeque.getFirst(ArrayDeque.java:324) build 27-Jul-2015 13:46:17 at com.atlassian.clover.instr.java.JavaRecognizer.headIdentifiersStack(JavaRecognizer.java:113) build 27-Jul-2015 13:46:17 at com.atlassian.clover.instr.java.JavaRecognizer.pushIdentifierToHeadStack(JavaRecognizer.java:109) build 27-Jul-2015 13:46:17 at com.atlassian.clover.instr.java.JavaRecognizer.primaryExpressionPart(JavaRecognizer.java:3368) build 27-Jul-2015 13:46:17 at com.atlassian.clover.instr.java.JavaRecognizer.postfixExpression(JavaRecognizer.java:5047) build 27-Jul-2015 13:46:17 at com.atlassian.clover.instr.java.JavaRecognizer.unaryExpressionNotPlusMinus(JavaRecognizer.java:5007) build 27-Jul-2015 13:46:17 at com.atlassian.clover.instr.java.JavaRecognizer.unaryExpression(JavaRecognizer.java:4867) build 27-Jul-2015 13:46:17 at com.atlassian.clover.instr.java.JavaRecognizer.multiplicativeExpression(JavaRecognizer.java:4817) build 27-Jul-2015 13:46:17 at com.atlassian.clover.instr.java.JavaRecognizer.additiveExpression(JavaRecognizer.java:4787) build 27-Jul-2015 13:46:17 at com.atlassian.clover.instr.java.JavaRecognizer.shiftExpression(JavaRecognizer.java:4754) build 27-Jul-2015 13:46:17 at com.atlassian.clover.instr.java.JavaRecognizer.relationalExpression(JavaRecognizer.java:4706) build 27-Jul-2015 13:46:17 at com.atlassian.clover.instr.java.JavaRecognizer.equalityExpression(JavaRecognizer.java:4673) build 27-Jul-2015 13:46:17 at com.atlassian.clover.instr.java.JavaRecognizer.andExpression(JavaRecognizer.java:4654) build 27-Jul-2015 13:46:17 at com.atlassian.clover.instr.java.JavaRecognizer.exclusiveOrExpression(JavaRecognizer.java:4635) build 27-Jul-2015 13:46:17 at com.atlassian.clover.instr.java.JavaRecognizer.inclusiveOrExpression(JavaRecognizer.java:4616) build 27-Jul-2015 13:46:17 at com.atlassian.clover.instr.java.JavaRecognizer.logicalAndExpression(JavaRecognizer.java:4597) build 27-Jul-2015 13:46:17 at com.atlassian.clover.instr.java.JavaRecognizer.logicalOrExpression(JavaRecognizer.java:4578) build 27-Jul-2015 13:46:17 at com.atlassian.clover.instr.java.JavaRecognizer.conditionalExpression(JavaRecognizer.java:4549) build 27-Jul-2015 13:46:17 at com.atlassian.clover.instr.java.JavaRecognizer.conditionalExpression2(JavaRecognizer.java:5558) build 27-Jul-2015 13:46:17 at com.atlassian.clover.instr.java.JavaRecognizer.annMemberValue2(JavaRecognizer.java:5528) build 27-Jul-2015 13:46:17 at com.atlassian.clover.instr.java.JavaRecognizer.annMemberValuePair(JavaRecognizer.java:5465) build 27-Jul-2015 13:46:17 at com.atlassian.clover.instr.java.JavaRecognizer.annotation2(JavaRecognizer.java:1509) build 27-Jul-2015 13:46:17 at com.atlassian.clover.instr.java.JavaRecognizer.annotation(JavaRecognizer.java:667) build 27-Jul-2015 13:46:17 at com.atlassian.clover.instr.java.JavaRecognizer.packageDefinition(JavaRecognizer.java:593) build 27-Jul-2015 13:46:17 at com.atlassian.clover.instr.java.JavaRecognizer.compilationUnit(JavaRecognizer.java:540) build 27-Jul-2015 13:46:17 at com.atlassian.clover.instr.java.Instrumenter.instrument(Instrumenter.java:212) build 27-Jul-2015 13:46:17 at com.atlassian.clover.instr.java.Instrumenter.instrument(Instrumenter.java:125) build 27-Jul-2015 13:46:17 at com.atlassian.clover.CloverInstr.execute(CloverInstr.java:76) build 27-Jul-2015 13:46:17 at com.atlassian.clover.CloverInstr.mainImpl(CloverInstr.java:54) build 27-Jul-2015 13:46:17 at com.atlassian.maven.plugin.clover.internal.instrumentation.AbstractInstrumenter.instrumentSources(AbstractInstrumenter.java:197) build 27-Jul-2015 13:46:17 at com.atlassian.maven.plugin.clover.internal.instrumentation.AbstractInstrumenter.instrument(AbstractInstrumenter.java:72) build 27-Jul-2015 13:46:17 at com.atlassian.maven.plugin.clover.CloverInstrumentInternalMojo.execute(CloverInstrumentInternalMojo.java:289) build 27-Jul-2015 13:46:17 at com.atlassian.maven.plugin.clover.CloverSetupMojo.execute(CloverSetupMojo.java:31) build 27-Jul-2015 13:46:17 at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132) build 27-Jul-2015 13:46:17 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) build 27-Jul-2015 13:46:17 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) build 27-Jul-2015 13:46:17 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) build 27-Jul-2015 13:46:17 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) build 27-Jul-2015 13:46:17 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) build 27-Jul-2015 13:46:17 at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) build 27-Jul-2015 13:46:17 at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120) build 27-Jul-2015 13:46:17 at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:347) build 27-Jul-2015 13:46:17 at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:154) build 27-Jul-2015 13:46:17 at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584) build 27-Jul-2015 13:46:17 at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213) build 27-Jul-2015 13:46:17 at org.apache.maven.cli.MavenCli.main(MavenCli.java:157) build 27-Jul-2015 13:46:17 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) build 27-Jul-2015 13:46:17 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) build 27-Jul-2015 13:46:17 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) build 27-Jul-2015 13:46:17 at java.lang.reflect.Method.invoke(Method.java:483) build 27-Jul-2015 13:46:17 at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) build 27-Jul-2015 13:46:17 at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) build 27-Jul-2015 13:46:17 at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) build 27-Jul-2015 13:46:17 at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) build 27-Jul-2015 13:46:17 [INFO] {code} | 2 |
305 | CLOV-1779 | 08/05/2015 16:40:06 | Groovy code with Generics throw NPEs | Starting with Clover version 4.0.1 when running JUnit tests against clover instrumented code I am getting a null pointer exception when attempting to call this method: {code:java} // in DateUtil.groovy static <T extends Date> T copy(T date) { (T) date?.clone() } {code} It seems like something has changed with the instrumentation. Either of these two other variations of this same code *doesn't* have this problem: {code:java} static Date copy(Date date) { date?.clone() } static def copy(def date) { date?.clone() } {code} Here's the top of the stacktrace: {noformat} java.lang.NullPointerException at com.sun.beans.TypeResolver.resolve(TypeResolver.java:203) at com.sun.beans.TypeResolver.resolve(TypeResolver.java:218) at com.sun.beans.TypeResolver.resolveInClass(TypeResolver.java:96) at java.beans.FeatureDescriptor.getParameterTypes(FeatureDescriptor.java:387) at java.beans.MethodDescriptor.setMethod(MethodDescriptor.java:116) at java.beans.MethodDescriptor.<init>(MethodDescriptor.java:72) at java.beans.MethodDescriptor.<init>(MethodDescriptor.java:56) at java.beans.Introspector.getTargetMethodInfo(Introspector.java:1205) at java.beans.Introspector.getBeanInfo(Introspector.java:426) at java.beans.Introspector.getBeanInfo(Introspector.java:173) at groovy.lang.MetaClassImpl$15.run(MetaClassImpl.java:3244) at java.security.AccessController.doPrivileged(Native Method) at groovy.lang.MetaClassImpl.addProperties(MetaClassImpl.java:3242) at groovy.lang.MetaClassImpl.initialize(MetaClassImpl.java:3225) at org.codehaus.groovy.reflection.ClassInfo.getMetaClassUnderLock(ClassInfo.java:222) at org.codehaus.groovy.reflection.ClassInfo.getMetaClass(ClassInfo.java:253) at org.codehaus.groovy.runtime.metaclass.MetaClassRegistryImpl.getMetaClass(MetaClassRegistryImpl.java:255) at org.codehaus.groovy.runtime.InvokerHelper.getMetaClass(InvokerHelper.java:859) at org.codehaus.groovy.runtime.callsite.CallSiteArray.createCallStaticSite(CallSiteArray.java:72) at org.codehaus.groovy.runtime.callsite.CallSiteArray.createCallSite(CallSiteArray.java:159) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116) at com.surescripts.common.DateUtilTest.clone_NonNullValue(DateUtilTest.groovy:16) {noformat} | 3 |
306 | CLOV-1780 | 08/13/2015 08:32:59 | Add migration message in maven-clover2-plugin POM | (/) investigate if we can use clover-maven-plugin or must use cloverX-maven-plugin -> it would be great to have just clover- instead of cloverX- to avoid changing a number in future (?) decide if major Clover release will be numbered 4.1.0 or 5.0.0 (as per Semantic Versioning) -> it may affect whether it will be named clover4- or clover-5 (/) prepare migration message in maven-clover2-plugin pom.xml for versions 4.0.x, similarly as it was done for Clover Core (com.cenqua.clover:clover:3.3.0) -> deliver in Clover 4.0.6, 4.0.7, ... to be considered: (x) prepare a fork of the plugin and release under two names since 4.0.6? (x) add an extra migration warning printed by the clover2:setup / clover2:instr goal? | 2 |
307 | CLOV-1784 | 09/18/2015 15:05:28 | Extend interfaces to manipulate test optimization | Interface to manipulate test optimization: * to reorganize optimized test sets * to manipulate content the test optimization snapshot file | 2 |
308 | CLOV-1785 | 09/19/2015 18:47:18 | Extend database format to handle statements and methods in a file | Allow better modelling of file-level statements and methods so that we can better support languages like Ruby which support top-level scripting constructs. Example: {code:java} session.enterFile(..); session.enterMethod(...); // top-level-method, not inside a class ... // some statements ... session.exitMethod(); ... session.addStatement(...); // top-level-statement, not inside a class or a method ... session.exitFile(); {code} Some preparation have been already done for Java 8 (Clover 3.2). Things to be checked: * how our code calculates the start/end line/col range for a statement/method outside a class * how it calculates code metrics for a file having top-level statements/methods * how it handles exclusion filters (statement/method regexp) * how it handles nested entities (method-in-method etc) Things to be implemented: * take into account these top-level statements/methods in reporting ** show in XML / HTML / PDF / JSON ** render lines ** show in tables etc Out of scope: * test optimization Note: Looking at how Clojure is written, for any Clojure file there would only ever be one FileInfo containing lots of StatementInfos and MethodInfos but no ClassInfos. | 3 |
309 | CLOV-1787 | 09/19/2015 18:55:01 | Rename ClassInfo to TypeInfo | ClassInfo is just OK for Java and Groovy (we have classes). But we also have enums, interfaces and annotations! And in other languages we also have closures (Groovy), traits (Groovy, Scala) etc. Thus the name ClassInfo does not suit well for other languages. Rename ClassInfo to something better. TypeInfo might be better. | 1 |
310 | CLOV-1788 | 09/19/2015 20:36:51 | Make session.enterClass() more language-independent | Clean up InstrumentationSession.enterClass(..., boolean isInterface, boolean isEnum, boolean isAnnotation) so that it instead takes a LanguageConstruct to indicated what it is which is then embedded in ClassInfo. This divorces this part of the API from Java allowing us to model languages like Scala who have things like traits, singleton objects, etc. This may require a separate LanguageConstruct-like type (TypeConstruct ?) as it will likely need to be smarter than LanguageConstruct and be able to answer some basic questions Clover may need to ask e.g. {code:java} if (!typeInfo.getConstruct().isAbstract(typeInfo)) { //Java interfaces and annotations are always abstract, Scala trait is sometimes abstract, ... //include in the report } {code} The example above is a bit fake because surely we could determine if a TypeInfo is abstract by traversing it but there may be situations where we need to ask similar questions. | 3 |
311 | CLOV-1789 | 09/19/2015 20:41:14 | Add possibility to add custom properties for code elements | Introduce a base interface to ClassInfo, MethodInfo, PackageInfo, FileInfo, StatementInfo, BranchInfo which allows API clients to add arbitrary properties to the model. They values should be raw types, possible Serializable objects too. This should allow instrumentation providers better answer questions Clover may have about the model they've produced. Something like: interface CustomInfo - getProperties(): Map<String, Object> - setProperty(String, Object) - getProperty(String) interface FileInfo extends ..., CustomInfo interface TypeInfo extends ..., CustomInfo interface MethodInfo extends ..., CustomInfo interface BranchInfo extends ..., CustomInfo interface StatementInfo extends ..., CustomInfo | 2 |
312 | CLOV-1790 | 09/19/2015 20:43:37 | Rename StatementInfo to ExpressionInfo | Rename StatementInfo to ExpressionInfo in the API. Java is the odd one out here. Scala, Clojure etc all have expressions as there basic unit of execution. A statement is an expression with no result. | 1 |
313 | CLOV-1793 | 09/21/2015 12:42:04 | Drop Grails 1.3 | * remove legacy code (if any) | 2 |
314 | CLOV-1794 | 09/21/2015 12:42:48 | Drop Eclipse 3.6 and 3.7 | * compile against eclipse 4.2 * fix deprecation warnings etc * remove legacy code (if any) * bump version numbers in feature name | 1 |
315 | CLOV-1795 | 09/23/2015 14:19:46 | Remove --style from Command line processors | {{--style}} argument has been deprecated in 4.1.0 it should be removed in next major version 4.2.0. Scope: * remove HtmlReporter#Style * update docs i necessary * cleanup all TODO CLOV-1795 | 0.5 |
316 | CLOV-1797 | 09/25/2015 13:04:53 | Support for IDEA 14.1.5 | It should work but let's be sure. http://blog.jetbrains.com/idea/2015/09/intellij-idea-14-1-5-update-is-out/ | 0.5 |
317 | CLOV-1804 | 10/07/2015 07:36:42 | Add support for Eclipse Mars.1 | Eclipse Mars.1 was released on 01.10. Make sure Clover is compatible by: * smoke testing * adding new version to Eclipse versions matrix. | 0.5 |
318 | CLOV-1808 | 10/15/2015 08:23:50 | StringIndexOutOfBoundsException in CloverStartup.evaluateDaysLeft | Clover fails to decode the license key. Stacktrace: {noformat} Caused by: java.lang.StringIndexOutOfBoundsException: String index out of range: 47 at java.lang.String.charAt(String.java:646) at com.atlassian.clover.CloverStartup.evaluateDaysLeft(CloverStartup.java:334) at com.atlassian.clover.CloverStartup.loadLicense(CloverStartup.java:122) at com.atlassian.clover.CloverStartup.loadLicense(CloverStartup.java:26) at com.atlassian.clover.CloverInstr.mainImpl(CloverInstr.java:45) at com.atlassian.maven.plugin.clover.internal.instrumentation.AbstractInstrumenter.instrumentSources(AbstractInstrumenter.java:196) at com.atlassian.maven.plugin.clover.internal.instrumentation.AbstractInstrumenter.instrument(AbstractInstrumenter.java:71) at com.atlassian.maven.plugin.clover.CloverInstrumentInternalMojo.execute(CloverInstrumentInternalMojo.java:290) at com.atlassian.maven.plugin.clover.CloverSetupMojo.execute(CloverSetupMojo.java:30) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager. java:134): .. 11 more {noformat} | 1 |
319 | CLOV-1817 | 10/22/2015 14:09:41 | Fix colors of test passed / failed / error icons in Eclipse | Currently we use dark blue color for a failed test. It's not contrast enough compared to the green one. Furthermore, we use a red background for a "FAIL" status label, which is not consistent. Also, a green background used for a "PASS" label is different from the green dot in the icon. Current colors used: green-pass, blue-fail, red-error are the same as in Eclipse's JUnit view. Consider also changing a dot to three different figures to make it accessible for color-blinded people. For instance: * light green circle - pass * dark blue triangle - fail * red square - error | 0.5 |
320 | CLOV-1823 | 10/23/2015 13:32:32 | Test optimization in Eclipse Mars 4.5.1 keeps running one test | Steps to reproduce: * rebuild a project, clean database and optimization snapshot * two times on 'run optimized' button, for the first time it runs all test, for the second time it runs one test (and should none) | 0.5 |
321 | CLOV-1825 | 10/26/2015 10:40:38 | Add more debug logging for clover2:aggregate | Currently, it's not known why a project has no child databases and what user can do with it. | 0.5 |
322 | CLOV-1827 | 10/28/2015 15:32:20 | Update Clover Tutorial | * use source=1.6 instead of 1.4 * download required JARs (build*.xml) * do not require env.GROOVY_HOME set to 1.7 * rename 'test' to 'test.run' * remove cloverjunitlib.xml * convert unit tests to JUnit4 * simplify goals * use clover-maven-plugin | 1 |
323 | CLOV-1834 | 11/03/2015 23:04:34 | Instrumentation failure of an annotation inside the catch clause | Clover is failing to instrument below section of java 7 code {code} try { innerStream.close(); } catch (@SuppressWarnings("unused") final IOException e) { // ignore } {code} This is a perfectly valid java 7 syntax but clover instrumentation fails at @SuppressWarnings("unused") annotation. | 1 |
324 | CLOV-1835 | 11/05/2015 08:17:46 | Unicode 0x200B (zero-width whitespace) causes instrumentation failure | JDK 6 implements Unicode 4.0. In this version of Unicode, the zero-width whitespace character (0x200B) is being treated as a whitespace. JDK 7 implements Unicode 6.0. In this version of Unicode, the zero-width whitespace has been reclassified to the 'format character' group (other characters in this group are, for example, left-/right- text direction markers). Thus, Java compiler in JDK 6 allows to use 0x200B as a normal whitespace character, e.g. separating symbols. The Java compiler since JDK 7 silently ignores the 0x200B, which means that it cannot be used to separate symbols anymore. However you can put this character virtually in any place, e.g.: {code:java} void this<200B>Is<200B>MyMethod(); {code} Clover fails on parsing the 200B character: {noformat} Xyz.java:287:90:unexpected char: 0x200B at com.atlassian.clover.instr.java.Instrumenter.instrument(Instrumenter.java:166) at com.atlassian.clover.CloverInstr.execute(CloverInstr.java:76) at com.atlassian.clover.CloverInstr.mainImpl(CloverInstr.java:54) at ... {noformat} *Planned fix:* * Ignore 200B characters in Java 7+. Treat 200B character as space in Java 6. * Question: Shall it be based on source level setting or the JDK detected? * Question: which other control characters needs to be ignored by Clover? * Question: which other whitespace characters (other than space, \t, \n, \r) shall be recognized by Clover parser? *Workaround:* Remove all 200B character occurrences from the source code. | 2 |
325 | CLOV-1841 | 11/26/2015 09:40:23 | Prepare feature analysis of JCov tool | Analyse https://wiki.openjdk.java.net/display/CodeTools/jcov and publish on https://confluence.atlassian.com/display/CLOVER/Comparison+of+code+coverage+tools | 2 |
326 | CLOV-1846 | 12/01/2015 11:26:15 | IntelliJ Plugin should ask for rebuilding project after changing exclusions | Currently it doesn't always ask which sometime may lead to {{ClassNotFoudException}} h2. Preconditions IntelliJ IDEA with Clover installed h2. Repro steps # Clean project and coverage db # Exclude some class with context menu # Run tests # Wait for exception h2. Expected result # Clean project and coverage db # Exclude some class with context menu # Clover asks user for rebuilding the project. | 1 |
327 | CLOV-1847 | 12/03/2015 08:37:01 | IntelliJ Plugin should not use UI thread to generate Cloud report | Currently Clover generates Cloud report in UI thread, it can take couple of seconds with bigger projects causing whole UI to freeze. Let's try to move it back to background somehow. | 2 |
328 | CLOV-1848 | 12/03/2015 13:19:10 | Add IntelliJ 15.0.2 to test matrix | Add IntelliJ 15.0.2 to test matrix after it being released. Currently there was RC released. | 0.5 |
329 | CLOV-1855 | 12/07/2015 10:33:15 | Drop support for IntelliJ IDEA 11.x | Scope: * drop support for IntelliJ IDEA 11.x * refactor deprecated code * remove IntelliJ 11.x from test matrix * update plugin.xml to tell correct minimal version of IntelliJ IDEA which is supported. | 1 |
330 | CLOV-1856 | 12/07/2015 10:35:24 | IntelliJ IDEA plugin with version 4.1.1 shows wrong supported version | Site for Clover on IntelliJ plugin page indicates Clover 4.1.1 supports Idea 9x however it's not true. Update plugin.xml to show correct version. https://plugins.jetbrains.com/plugin/?id=132 | 0.5 |
331 | CLOV-1884 | 02/12/2016 06:07:02 | CloverCompilerAdapter should look for Javac.compileList also in super classes | It may happen that user will wrap or subclass the Apache's Javac field. In such case, Clover won't be able to find and set this field and break the build. The CloverCompilerAdapter should look it up in a class hierarchy. We can use Apache's FieldUtils for this purpose. | 1 |
332 | CLOV-1951 | 06/15/2016 11:14:15 | Support Eclipse 4.6 Neon | Make Clover-for-Eclipse compatible with Eclipse Neon. Problems found so far: 1. Running optimised tests throws an exception (/) {code:java} eclipse.buildId=4.6.0.I20160525-2000 java.version=1.8.0_51 java.vendor=Oracle Corporation BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_US Framework arguments: -product org.eclipse.epp.package.java.product -product org.eclipse.epp.package.java.product -product org.eclipse.epp.package.java.product Command-line arguments: -os macosx -ws cocoa -arch x86_64 -product org.eclipse.epp.package.java.product -product org.eclipse.epp.package.java.product -data file:/Users/mparfianowicz/.eclipse-4.6-workspace/ -product org.eclipse.epp.package.java.product org.eclipse.ui Error Tue Jun 14 15:51:17 CEST 2016 Unhandled event loop exception org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException) at org.eclipse.swt.SWT.error(SWT.java:4533) at org.eclipse.swt.SWT.error(SWT.java:4448) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:185) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4024) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3700) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:687) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610) at org.eclipse.equinox.launcher.Main.run(Main.java:1519) Caused by: java.lang.NullPointerException at com.atlassian.clover.eclipse.testopt.views.actions.SavingsNotificationContributionItem$1$1.run(SavingsNotificationContributionItem.java:33) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182) ... 23 more {code} 2. Deprecated API (/) SubProgressMonitor in org.eclipse.core.runtime has been deprecated ViewerSorter in org.eclipse.jface.viewers has been deprecated setSorter(ViewerSorter) in StructuredViewer has been deprecated Main(PrintWriter,PrintWriter,boolean) in Main has been deprecated 3. Code incompatibility (/) CoverageAnnotationModel is not abstract and does not override abstract method getAnnotationIterator() in IAnnotationModel | 3 |
333 | CLOV-1953 | 06/21/2016 05:33:35 | Clover does not instrument all nodes in Groovy AST | Problem was reproduced in Groovy 2.4.3 and 2.4.4: https://answers.atlassian.com/questions/39141626/why-is-clover-showing-green-on-gray https://answers.atlassian.com/questions/39141622/incomplete-clover-coverage-in-grails-2.5-integration-testing | 5 |
334 | CLOV-1956 | 06/21/2016 14:17:27 | Fix Ant 1.9.7 double quotes | Ant prior to version 1.9.7 incorrectly handled arguments containing white space characters (they were being passed as separate arguments). For this reason, we put various paths (e.g. path to a license file) in double quotes. This has been fixed in Ant 1.9.7. However, as a consequence it does not strip double-quotes now, so paths are interpreted literally - with quotes. We need a fix on Clover side, but at the same time to keep compatibility with older Ant versions. Consider adding proper flag for Clover-for-Ant tasks (e.g. "withQuotes=true"). See also: * BAM-10740 * BAM-17201 | 2 |
335 | CLOV-1960 | 06/29/2016 11:27:19 | Instrument Groovy traits and show code coverage for them | *Current status* Groovy 2.3 introduced traits - a code construct for composition of behaviours: * http://docs.groovy-lang.org/latest/html/documentation/core-traits.html Currently Clover handles them like an interface - it records the class name in a database but it does not instrument the class, so it shows no code coverage in reports for them. Side note: Clover's reports by default do not show classes containing no executable code (empty classes, plain enums, interfaces with no default methods, traits) - you can show them by setting [showEmpty=true|https://confluence.atlassian.com/display/CLOVER/clover-report] parameter. *Proposed improvement* Instrument Groovy traits like normal classes or enums. Side note: Groovy 2.5 will probably not introduce interfaces with default methods (like in Java 8). * http://docs.groovy-lang.org/next/html/documentation/#_interface *Technical obstacles* * method '$CLV_R$' is private but should be public in a trait * method 'com_atlassian_clover.CoverageRecorder $CLV_R$()' must not be static; only fields may be static in a trait * field '$CLV_R$' is not 'public static final' in a trait | 8 |
0 | COMPASS-167 | 09/12/2016 02:16:50 | Re-implement "open ranges" behavior in reactified schema view | For MongoDB World, we've implemented a behavior in the query builder on "number" minicharts to create open ranges, e.g. {{\{"$lt": 20\}}} instead of {{\{"$gt": 15, "$lt": 20\}}} (special request from Dana for the demo). The behavior was to click-drag the selection box over the edge of the chart to trigger the open range, while still allowing closed ranges when dragging close to the edge. !open_closed_ranges_query_builder.gif|width=600! This behavior got lost in the transition to the React version of the schema in the 1.4.0-beta cycle. We want to re-implement it, and also add subtle visual feedback that indiciates to the user that they have reached/passed the threshold between open/close ranges (e.g. a faded background to the side when switching to open range). The implementation for this behavior is available in the old code base, but it needs to be adjusted to the new query builder code. Code Snippets: - Detection of mouse outside chart in the old code base: https://github.com/10gen/compass/blob/1.3-releases/src/app/minicharts/d3fns/many.js#L89-L98 ({{openLeft}}, {{openRight}} boolean flags) - Code in the old Query Builder to handle open ranges: https://github.com/10gen/compass/blob/1.3-releases/src/app/minicharts/querybuilder.js#L292-L306 (probably not relevant, just adding for completeness). - Somewhere in here we need to add the "outside chart" detection and construct the open query, and pass it to the {{setRangeValue}} action, see below. https://github.com/10gen/compass/blob/master/src/internal-packages/schema/lib/d3/many.js#L85-L108 - New Query Builder action {{setRangeValue}} already supports open ranges, just need to be called correctly: https://github.com/10gen/compass/blob/f05b3acf40fe9e56691aedd83cd7d970a9a84420/src/internal-plugins/query/lib/store/query-store.js#L564-L593 Acceptance criteria: * add "outside chart" implementation for minicharts * call {{setRangeValue}} in query store | 3 |
1 | COMPASS-65 | 10/04/2016 17:06:38 | CRUD: Improve Date Editing | - Add help section explaining types that can be converted to dates. Format example MUST be one of yyyy-mm-dd, yyyy-mm-ddThh:MM:SS, yyyy-mm-ddThh:MM:SS.SSS. Note: Date formats were expanded to a much larger set by using the Date constructor in COMPASS-919. - Render the dates in the same format that can be accepted: yyyy-mm-ddThh:MM:SS.SSS | 3 |
2 | COMPASS-115 | 10/08/2016 20:15:19 | As a developer I want to show dates in server time and not local (laptop) time | h5. Story As a developer, I want Compass to show date values in server time and not converted to the local (laptop) time so that I confirm that my application is saving dates correctly. h5. User anecdote More details: With the current Compass implementation, I thought my App inserts dates with an offset of +1 day and I spent a lot of time trouble-shooting until I used the mongo shell and realized the dates are correct but Compass shows it converted to local time. h5. Product Acceptance Criteria * Have a menu option(s) to Show Dates as server time or local time * Default to server time | 5 |
3 | COMPASS-265 | 11/02/2016 15:29:49 | Find in Page | Electron now has the bindings so "Find in Page" (Cmd+F) is accessible to us: https://github.com/atom/electron/blob/master/docs/api/web-contents.md#webcontentsfindinpagetext-options Note: this will involve UI for the search input, prev/next/close buttons. | 5 |
4 | COMPASS-273 | 11/03/2016 14:42:41 | Field names should be available in doc validation pane | When using the GUI document validation rule builder, it would be a lot simpler to use if it allowed you to select from the existing document field names rather than having to type them in. Acceptance Criteria: - Use the react-select component index field names (COMPASS-540) to wire it up to the field store (COMPASS-727) - Add functional tests for adding field names to Document Validation - Update existing enzyme tests to account for these changes | 5 |
5 | COMPASS-274 | 11/03/2016 15:03:41 | Converting type names to numbers in doc validation rule builder makes JSON less readable | I created doc validation rules using type names (see attached) but Compass then converts them to the numeric equivalent in the JSON output and the rule that's added to MongoDB. It would be simpler for people to understand the rules if Compass kept the name instead. {code:title=rules.js|borderStyle=solid} { "name": { "$type": 3 }, "name.first": { "$type": 2 }, "name.last": { "$type": 1 }, "social.twitter": { "$type": 4 } } db.getCollectionInfos({name:"people"}) [ { "name" : "people", "type" : "collection", "options" : { "validator" : { "name" : { "$type" : 3 }, "name.first" : { "$type" : 2 }, "name.last" : { "$type" : 1 }, "social.twitter" : { "$type" : 4 } }, "validationLevel" : "strict", "validationAction" : "error" }, "info" : { "readOnly" : false }, "idIndex" : { "v" : 2, "key" : { "_id" : 1 }, "name" : "_id_", "ns" : "clusterdb.people" } } ] {code} Scope of the ticket: - change type value to its string alias - change tests to reflect this | 2 |
6 | COMPASS-290 | 11/07/2016 02:17:49 | Make sure all version comparisons use semver | For server version comparisons (e.g. all 3.4-only features) we should use a library that can handle version numbers correctly, e.g. the "semver" package. Otherwise, we might run into issues with release candidates or other unusual version strings. Simple string comparison fails in these cases: {code} > '3.4.0' > '3.4.0-rc3' false {code} But semver can handle this correctly: {code} > semver.gt('3.4.0', '3.4.0-rc3') true {code} One place where this happens: https://github.com/10gen/compass/blob/d244de57b322ae4b3142c13220dec5191fafe0b9/src/internal-packages/crud/lib/component/editable-value.jsx#L73 Need to find all other places where we use simple string comparisons for versions. | 3 |
7 | COMPASS-302 | 11/08/2016 23:44:32 | When the user wants to execute an empty query, pop up a warning box that this is not ideal | Broken off from COMPASS-291 and should be implemented after that. Show a modal popup to warn the user when they try to run an empty explain {} because that is potentially very expensive on the database and we already know the result: a collection scan. Acceptance Criteria: - When the user enters an empty query (or uses the default empty query) and hits apply, a modal window should appear with a warning text and 2 buttons, cancel/continue. Only when the user presses continue should the explain be executed. | 1 |
8 | COMPASS-374 | 11/17/2016 15:36:38 | Make schema/query timings visible to the user | - Dictate to the user the definition performance: "You may think this was slow because you were also on a hangout" - Don't want to think UI bugs/performance in Compass mean Server is slow - We track these as metrics but don't expose to user - Time to sample on server|analyze|render|$sample used - If sample time on server slow (use ms value for slow queries from profiler?) - recommend viewing the explain plan to make it faster - green|yellow|red color indication like mocha's slowms? | 1 |
9 | COMPASS-457 | 11/28/2016 05:39:07 | Improve the Windows installer icon | Presumably the installer icon should use the MongoDB leaf, not something that looks a bit like a black Christmas present box. !Screen Shot 2016-11-28 at 4.36.12 pm.png|width=50%! Windows builds are available on Evergreen, e.g. https://evergreen.mongodb.com/task/10gen_compass_testing_windows_64_compile_0ebd7009f7403340abb53f6691bf0325793bd8e5_16_11_28_04_14_13 | 1 |
10 | COMPASS-506 | 12/04/2016 03:36:55 | Clear recent connections list from connect view | Or remove individual connections. | 3 |
11 | COMPASS-632 | 01/11/2017 03:36:36 | Support collation on Create Database & Collection dialogs | Introduced in MongoDB 3.4: https://docs.mongodb.com/master/release-notes/3.4/#collation-and-case-insensitive-indexes MongoChef claims full collation support which Compass cannot today: http://3t.io/blog/what-is-new-in-mongochef-4-5/ | 5 |
12 | COMPASS-723 | 01/28/2017 10:39:28 | Increase ssh tunnel connection timeouts | We have a user in intercom complaining that he gets ssh timeouts, when RoboMongo connects to the instance ok. Currently, the timeout is [hardcoded to 5 seconds|https://github.com/mongodb-js/connection-model/blob/2002a3df39658665ac9d6713ace525bd35bb2dcb/lib/model.js#L703-L705] in the connection-model. Increase to 30 seconds to account for geo latency. | 1 |
13 | COMPASS-820 | 02/27/2017 06:10:10 | Static assets all live under ./static | This will improve the Windows installation experience in two ways: 1. Installation assets to be decompressed before installation begins 2. Installation assets trigger less activity like to be disrupted by a virus scanner - Make a new {{./static}} directory - Move {{./src/app/{images,styles}}} and HTML files into {{./static}} - Update all image references in the app and hadron-build to point at {{./static}} - Update hadron-build to write {{./src/compiled-less}} to{{./static}} - Add {{./static}} to the {{asar.upack}} option in {{hadron-build/commands/release.js}} (they don’t need to be packed) Also consider updating any timing code to use [~lucas.hrabovsky] suggestion: https://github.com/nolanlawson/marky h3. References - [N1 ./static|https://github.com/nylas/N1/tree/master/static] - [N1’s bootloader.js|https://github.com/nylas/N1/blob/master/static/index.js] - [Atom ./static|https://github.com/atom/atom/tree/master/static] - [Atom’s advanced bootloader.js|https://github.com/atom/atom/blob/master/static/index.js] If all goes well, this will negate https://jira.mongodb.org/browse/COMPASS-415 | 3 |
14 | COMPASS-851 | 03/06/2017 07:32:12 | Investigate Kerberos Authentication if the username contains @ | From COMPASS-745, it looks like Kerberos and X.509 are also likely to double-encode their auth-component in the same way LDAP does. This ticket should: 1. Confirm if this is true, e.g. with https://docs.mongodb.com/v3.2/tutorial/control-access-to-mongodb-with-kerberos-authentication/ 2. If so, add a regression test in connection-model. 3. Remove all redundant {{encodeURIComponent}} calls, including in comments to make it clearer that {{url.format}} already handles this even better than we could ([git blame|https://github.com/nodejs/node/blame/v6.3.1/lib/url.js#L557] reveals it has been [optimised for more performance|https://github.com/nodejs/node/commit/db9128135f382e22202d900263e872d8b48f0050]). | 2 |
15 | COMPASS-909 | 03/14/2017 15:35:24 | Rename collection | As the comments below indicate there are several feature requests to rename a collection. This can be achieved in the node driver by calling the [rename|http://mongodb.github.io/node-mongodb-native/2.2/api/Collection.html#rename] command on particular collection. The goal of this ticket is to add the UI element, probably an extra option in the sidebar next to ever collection field to edit and call the rename command on the selected collection. Acceptance Criteria: * add {{rename}} to data-service (https://github.com/mongodb-js/data-service) * include unit tests for rename in data-service * make UI element (On the sidebar) that can be clicked to produce a modal for renaming collection * add enzyme tests for the above element * add store action to rename collection that calls the above data-service method * add unit tests for the above store action | 5 |
16 | COMPASS-931 | 03/20/2017 07:53:05 | Spike: Research if/how Compass can be "kerberized" | Reported by Barclays (00430436). When connecting to a Kerberos authenticated MongoDB deployment using Compass, we must supply the password from the Compass UI. Ideally, Compass should use the context of the logged in user and hence a password should not be needed unless a different context/user is needed to connect to the MongoDB deployment. This is how "kerberized" applications usually behave, and while the current implementation works, it's unusual and unexpected for users used to work in a kerberos environment. | 3 |
17 | COMPASS-1014 | 04/07/2017 12:06:40 | Unable to Enter Line Breaks in Strings | User reporting on Intercom that they are unable to create line breaks in Strings in the Documents tab. "\n" is getting escaped and we already override the Enter key functionality. Need to allow \n or provide a CTRL+Enter or similar to allow line breaks. | 3 |
18 | COMPASS-1083 | 04/28/2017 17:58:30 | LUUID/NUUID/BinData support for filters | Please see comments. | 3 |
19 | COMPASS-1099 | 05/03/2017 19:01:09 | Move Databases DDL to External Plugin | Move the databases-ddl internal package to the new compass-databases-ddl repo. - Move all code from internal-packages/database-ddl to 10gen/compass-databases-ddl - Use the khaos template to generate the plugin and make necessary changes to the template if problems arise. - Move all databases-ddl tests from Compass to the compass-databases-ddl repo - Add compass-databases-ddl to the compass-lite and compass-enterprise distribution configs in the package.json in Compass (for now) - Remove internal-packages/databases-ddl | 8 |
20 | COMPASS-1100 | 05/03/2017 19:07:22 | Move Database Plugin to External Plugin | Move the database internal package to the new compass-collections-ddl repo. - Move all code from internal-packages/database to 10gen/compass-collections-ddl - Use the khaos template to generate the plugin and make necessary changes to the template if problems arise. - Move all Database tests from Compass to the compass-collections-ddl repo - Add compass-collections-ddl to the compass-lite and compass-enterprise distribution configs in the package.json in Compass (for now) - Remove internal-packages/database | 8 |
21 | COMPASS-1102 | 05/03/2017 19:39:30 | Move Explain to external package | Move the explain internal package to the new compass-explain repo. - Move all code from internal-packages/explain to 10gen/compass-explain - Use the khaos template to generate the plugin and make necessary changes to the template if problems arise. - Move all Validation tests from Compass to the compass-explain repo - Add compass-explain to the compass-lite and compass-enterprise distribution configs in the package.json in Compass (for now) - Remove internal-packages/explain | 5 |
22 | COMPASS-1237 | 06/09/2017 17:03:49 | Add Installation Drive Destination Selection to Install Workflow on Windows | A customer reported in [this coversation|https://app.intercom.io/a/apps/p57suhg7/respond/inbox/unassigned/conversations/10247108756] a desire to select to which drive Compass is installed. I then tested the workflow on a Windows 10 machine and was unable to select the drive to which I was installing. I believe the ability to select the destination drive for the install to be a desirable addition to the workflow. | 8 |
23 | COMPASS-1337 | 07/06/2017 08:58:47 | Make Doc Validation's Editable Component reusable across plugins | Currently the Editable component resides in Doc Validation but it is a generic component that can be used throughout Compass. It will be pulled over to Compass after COMPASS-1303 is done. The work remaining is: - Remove the Editable component from [Doc Validation|https://github.com/10gen/compass-document-validation] and use the version from Compass via the appRegistry lifecycle methods - Remove any !important flags in the {{editable.less}} file as it shouldn't be required anymore. Acceptance criteria: - Make sure Doc Validation UI remains the same - Make sure Charts UI remains the same | 3 |
24 | COMPASS-1404 | 07/12/2017 18:18:58 | Hook into Server Description Changed Events | Currently deployment awareness listens to only topology description changed events, which does not cover the case when connected to a standalone instance. If a standalone server goes into an unknown state, the topology type remains as single according to the SDAM specification even though the server description becomes unknown. Therefore, we must also listen to these events when connected in standalone mode and fire the same changes as the existing topology related events. - Change https://github.com/10gen/compass-deployment-awareness/blob/master/src/stores/index.js to also listen to 'serverDescriptionChanged` events and trigger with an overwritten 'unknown' state instead of keeping the same 'single' type. The read state and write state stores should handle this accordingly. | 3 |
25 | COMPASS-1629 | 08/01/2017 18:55:26 | Cross-realm Kerberos Support | From CS-26551. After a bit of initial investigation, imagine this breaking out into 3 tasks: - COMPASS-1629: Spike: Research additional options needed to support cross-realm kerberos via the connect dialog - Add additional Kerberos options to connect dialog - Kerberos Cross-Realm testing backend setup {quote} Compass RC1 - Internal Server Error With (Cross Realm) Kerberos @ Connect Time Debug Console Shows: {code} POST http://localhost:29017/api/v1/token 500 (Internal Server Error)Request.end @ client.js:1016Model.extend.create @ token.js:69(anonymous function) @ token.js:119Item.run @ browser.js:64drainQueue @ browser.js:34_super.bugsnag @ bugsnag.js:149(anonymous function) @ bugsnag.js:624 bugsnag.js:239 [Bugsnag] Invalid API key 'undefined' bugsnag.js:239 [Bugsnag] Invalid API key 'undefined' {code} Note in the java driver we would have to do something along the following, would this be something that node driver can expose to compass? {code} MongoCredential gssAPICred = MongoCredential .createGSSAPICredential(KERBEROS + "@WINDOWSREALM.COM") .withMechanismProperty("REALM", "LINUXREALM.COM") .withMechanismProperty("CANONICALIZE_HOST_NAME", true); {code} {quote} | 3 |
26 | COMPASS-1735 | 08/15/2017 04:09:04 | Map Cmd-R (Ctrl-R) to reloading data only, Cmd-Shift-R app reload | This request has been made many times, e.g. this intercom conversation: https://app.intercom.io/a/apps/p57suhg7/respond/inbox/conversation/11245082354 Based on email discussion with Sam, Dana, Fred (see below), let's make the following changes: Cmd-R (Ctrl-R on Windows/Linux) should reload data only. No app refresh. Behavior: - always trigger a reload of the sidebar, and - if the user is on the instance level databases view: refresh the list of databases - if the user is on the instance level RTSS view, reset the view - if the user is on the database level collections view: refresh the list of collections - if the user is on one of the collection level tabs, additionally execute the following action: -- Documents tab: reload the documents (like the dedicated Refresh button) -- Schema tab: execute a new schema sampling with the same query -- Explain tab: execute a new explain plan with the same query -- Indexes tab: refresh indexes -- Document validation: reload validation rules Cmd-Shift-R (Ctrl-Shift-R on Windows/Linux) should reload the app (behavior that is Cmd-R today). | 5 |
27 | COMPASS-1764 | 08/18/2017 09:14:29 | Compass handles the crazy keys document series | h4. Usage/steps to reproduce {code} # Generate the document python3 mkbson.py # Import the document mongorestore -d perf -c crazy_keys raw_crazy_keys.bson {code} Then navigate to the {{perf.crazy_keys}} collection in Compass. An extended set of documents can be created and imported into MongoDB with this script relatively easily, on my local machine I already have the following numbers of keys and preliminary results: 32^3=32,768 48^3=110,592 64^3=262,144 (slow, ~5-10s) 80^3=512,000 (slow, ~30s) 96^3=884,736 140^3=2,744,000 (Compass 1.9.x betas crash with a memory exception) h4. Proposed solution - cap at 100k fields #intellectualhonesty - let the data drive your decision. Thus Compass, most likely in [mongodb-schema|https://github.com/mongodb-js/mongodb-schema], should stop scanning at about 100k fields (configurable as other optimizations are found) in a document and report this Easter egg in the GUI (originally this was Issue 2 in COMPASS-1901). h4. Acceptance criteria * A mongoimport -able version of these documents, perhaps with easier to understand names like crazy_keys_512000 (might be already done by COMPASS-1766, if so drop up to 2 story points) * Cap field or schema processing at 100k fields, reporting this somehow, e.g. with properties such as "totalFieldCount", "analyzedFieldCount" (working titles to capture the semantic, change the syntax as needed). * Message displaying this scenario, e.g. "100,000 fields limit reached, remaining N fields are not displayed" * Appropriate unit tests h4. Out of scope * Anything in the schema/indexes/document validation tabs (such as the react-select dropdown to choose an index name), this is just about the Documents Tab. h4. Background So I let Friday afternoon get to me and challenged myself to create a document with ~2.7 million keys. After about 3 minutes, Compass crashes. The mongo shell is still doing something in CPU-land after 8 minutes so far. On different data sets, such as documents with ~500,000 fields (i.e. COMPASS-1766), Compass takes ~30 seconds or more to render, or crashes (COMPASS-1764). Would explicitly limiting Compass to say 100,000 fields with a message like "Compass cannot render documents with more than 100,000 fields" seem reasonable? Yes but only when the user gets down to the 100,001st field. For documents under 100k fields, is a loading spinner enough? (i.e. ~6 seconds, so should not need a progress bar?). Proposed Solutions: Potentially push to the GPU? Otherwise just drop to {{Loading...}} text. | 5 |
28 | COMPASS-1766 | 08/21/2017 04:36:16 | Investigate Compass CRUD render times with increasing numbers of keys | # Use the script on COMPASS-1764, mgeneratejs or similar to generate documents with 50,100,200,400,800,1600,3200,6400,12800,25000,50000,100000 top-level fields # Report results - Measure time to render and chart it ## is it a straight line? is it exponentially slower each time? ## is there a cut off point where it just hangs? | 2 |
29 | COMPASS-1788 | 08/23/2017 07:13:35 | Generalize "Show N more fields" to clone mode | Repeat the work as for Edit mode COMPASS-1787, but applied to Clone document mode. | 3 |
30 | COMPASS-1802 | 08/27/2017 15:23:28 | Move Indexes Interal Package to External Plugin | Move the Indexes internal plugin to an external one under 10gen/compass-indexes | 5 |
31 | COMPASS-1803 | 08/27/2017 15:24:17 | Move Explain Internal Plugin to External One | Move the explain plan internal plugin to an external one at mongodb-js/compass-explain-plan Acceptance Criteria: - Create mongodb-js/compass-explain-plan repo - Generate the plugin from the new template. - Move over Components - Move from Reflux to Redux. - Refactor Components to be Pure for use with Cloud | 8 |
32 | COMPASS-1805 | 08/27/2017 15:26:05 | Move Collection Internal Plugin to External Plugin | Move the collection internal plugin to external one at 10gen/compass-collection | 5 |
33 | COMPASS-1901 | 09/04/2017 03:43:01 | Implement CRUD loading spinners/ripples/animations | Add loading spinners in places known to be slow. h4. Scenario 1. Visit data.mongodb.parts 2. Open mercedes.laps_31k_x_4k5 dataset, documents tab (Issue 1, Issue 2) 3. Click "Show 1000 more fields" 4. Double click on a field (after the first 25) to edit it, rendering the 1025 fields (or 2025 or more if the user went further) can take a long time (Issue 3) h4. Issue 1 Fetching data from the server can take an unbounded amount of time (e.g. server never responds, server under a DDoS attack, rogue queries, etc). !Thinking about remaining bottlenecks post disable chartView and COMPASS-1786.png|thumbnail! Solution: Reuse the existing loading spinner for loading more documents: !Network activity loading spinner.png|thumbnail! h4. Issue 2 See COMPASS-1764 Example with 110,592 fields (48^3): !perf.crazy_keys_48.png|thumbnail! h4. Issue 3 As rendering can take a long time, the naive fix here is to let the user know it can take a long time with a rendering/loading text or spinner, depending on whether the UI is locked. Aside: Longer term, getting field-based updates to work would allow the user to project only the fields they care about and then update just those fields, but there are no current plans to implement this. Aside 2: This issue only affects edit mode, where the user has double-clicked on the specific field they wish to edit. Specifically clone, loading, cancel, update success and delete can all drop back to rendering just 25 fields, as they have no specific requirement to maintain the user's current context, and so are not affected. Aside 3: Table view (COMPASS-652) if it got filtering of fields may also resolve this, as might adding a filter fields box into CRUD itself. | 3 |
34 | COMPASS-2282 | 11/06/2017 20:58:33 | As a user I want to execute a query without leaving my keyboard | As a user I want to execute a query without leaving my keyboard so I can be more agile and not have to use the mouse. | 3 |
35 | COMPASS-2299 | 11/13/2017 11:46:30 | User Provides DNS Wildcard for CSP | Allow the user to enter a DNS wildcard value to add to the CSP. Acceptance Criteria: - User selects a CSP directive. - Use may enter multiple DNS wildcard values for the directive. | 5 |
36 | COMPASS-2300 | 11/13/2017 11:48:12 | Compass Stores User Provided CSP | Compass persists the user provided CSP. Acceptance Criteria: - Clicking on save will persist the CSP to disk (user data dir). - On plugin initialization the CSP is loaded from disk (user data dir). | 5 |
37 | COMPASS-2301 | 11/13/2017 11:50:11 | Make Application index.html a Template | Make the Compass index.html a template. Acceptance Criteria: - Make template with area to insert a CSP into the meta tags. - Compass generates a new html file to load via browserWindow.loadURL() on start up from the template and the user saved CSP. | 5 |
38 | COMPASS-2381 | 11/30/2017 07:57:05 | As a user I would like visual feedback when executing queries | As a user I would like visual feedback when executing queries so that I can tell that the operation was sent to the server and is currently in progress (remove uncertainty). From Joe: In Compass (all versions up to 1.10.1.0) long running queries give no feedback when running or when completed. As a result you have to spot the number of results changing to determine if a query is complete. I have attached a screen capture demonstrating this. Sorry about the background noise on the video. I was in an airport lounge :-) | 3 |
39 | COMPASS-2406 | 12/15/2017 11:47:31 | As a user I am confused between when the reset button takes the place of the Analyze button | As a user I am confused between when the reset button takes the place of the Analyze button and I find myself hitting refresh by mistake when I really want to analyze. | 1 |
40 | COMPASS-2470 | 01/23/2018 19:41:30 | Compass app quits when last window is closed on macOS | On Compass 1.11.1, the whole Compass app quits when the last window is closed. This creates friction if the user intends to create a new window/connection - they are forced to search for and open Compass again. On macOS, it is customary for the app to stay open even when there are no running windows or sessions; quitting is an explicit step by the user rather than implicit by the developer. For reference, Slack does not quit if the last window is closed. | 1 |
41 | COMPASS-2553 | 02/20/2018 14:15:41 | Create Auto Update Plugin | Create the auto update plugin. Acceptance Criteria: - Create the repo - Generate the plugin from the template. | 2 |
42 | COMPASS-2554 | 02/20/2018 14:16:46 | Create Auto Update Component | Create the Auto Update Component Acceptance Criteria: - Create the component. - Component displays if update available - Component displays new version number. - Component displays release notes. | 5 |
43 | COMPASS-2590 | 03/05/2018 16:13:04 | Write a ECMAScript generator | Write a custom visitor that can visit the AST produced by COMPASS-2589 Support literals, arithmetic, etc. without any BSON-specific support. No need for assignments/functions/anything higher-order. | 3 |
44 | COMPASS-2591 | 03/05/2018 16:14:35 | Expand ECMAScript visitor to objects/arrays | Resulting language is basically JSON without any BSON-specific objects. | 3 |
45 | COMPASS-2592 | 03/05/2018 16:16:02 | Expand ECMAScript visitor to BSON type constructors | Add support for each BSON type, but not built-in methods or utils. Can be split into smaller tickets for each subtype if multiple people are working on it at the same time. | 3 |
46 | COMPASS-2593 | 03/05/2018 16:19:36 | Expand ECMAScript visitor to language-specific built-in types | dates, regex, etc. | 3 |
47 | COMPASS-2602 | 03/05/2018 16:40:14 | Expand Java generator to BSON object built-in functions | Expand the bson objects so that the functions in the `supports` column of the 'Export to Language Spec' tables. Can be split into smaller tickets for each subtype if multiple people are working on it at the same time. | 3 |
48 | COMPASS-2612 | 03/07/2018 19:30:43 | Pretty print generated code | ace editor is taking the generated code and just pastes in as is without formatting it properly. this ticket is meant to figure out formatting on setValue as well as setting up ability to change syntax highlighting / formatting based on output language | 5 |
49 | COMPASS-2621 | 03/09/2018 11:22:08 | Add BSON type constructors to python symbol table | Add python template to the symbol table for each BSON constructor. Blocked by COMPASS-2727 | 3 |
50 | COMPASS-2622 | 03/09/2018 11:23:23 | Add BSON constants or utils to Python symbol table | Add python template to the symbol table for each BSON constant/util. Blocked by COMPASS-2727 and needs to be done after COMPASS-2621 | 5 |
51 | COMPASS-2623 | 03/09/2018 11:26:06 | Add BSON object built-in functions to Python symbol table | Add python template to the symbol table for each BSON object method. Blocked by COMPASS-2727. Has to be done after COMPASS-2621 | 5 |
52 | COMPASS-2626 | 03/09/2018 11:59:17 | Expand C# generator to BSON type constructors | Add C# template to the symbol table for each BSON constructor. Blocked by COMPASS-2727 | 3 |
53 | COMPASS-2627 | 03/09/2018 11:59:29 | Add BSON object built-in functions to C# symbol table | Add C# template to the symbol table for each BSON object method. Blocked by COMPASS-2727 and needs to happen after COMPASS-2626 | 5 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.