I'm just getting started with Solr, running it from Tomcat6. I followed all the install instructions and the webapp seems to be running fine. I used curl to to send the sample data from the solr startup example, and the server seems to return what it is supposed to when someting is indexed successfully:
<?xml version="1.0" encoding="UTF-8"?>
<response>
<lst name="responseHeader"><int name="status">0</int><int name="QTime">4</int></lst>
</response>
But when I got to check the index through the admin/stats interface, nothing has made it into the index. It hasn't even regeistered the request??
searcherName : Searcher#5cd73256 main
caching : true
numDocs : 0
maxDoc : 0
reader : SolrIndexReader{this=ec5aba9,r=ReadOnlyDirectoryReader#ec5aba9,refCnt=1,segments=0}
readerDir : org.apache.lucene.store.NIOFSDirectory#/home/tomcat6/solr/data/index
indexVersion : 1266212874907
openedAt : Fri Apr 15 13:46:52 EDT 2011
registeredAt : Fri Apr 15 13:46:52 EDT 2011
warmupTime : 0
I'm really curious at this line: readerDir : org.apache.lucene.store.NIOFSDirectory#/home/tomcat6/solr/data/index
as this doesnt exist on the server, my index is located at /home/myhome/solr/data/index
I configured the solr home through the webapps web.xml env tag. And the proper home is displayed in the main admin screen
Any ideas how I might get my index working?
Thanks ahead of time.
--dm
You probably forgot to commit the new documents, e.g. after adding:
curl http://localhost:8983/solr/update -F stream.body=' <commit />'
Related
Can someone help me figure out why I'm not seeing test results in the junit output xml file.
My cypress.json file is configured like this:
"reporter": "mocha-junit-reporter",
"reporterOptions": {
"testsuitesTitle": true,
"mochaFile": "./cypress/reports/junit.xml"
}
I run these like so:
start-server-and-test start-dev-env http://localhost:4200 cy:run
where start-dev-env is defined thus:
"start-dev-env": "ng serve --proxy-config proxy/dev${ENV_SPECIFIER}.json --live-reload=false",
If I have test failures, I get junit output like so:
<?xml version="1.0" encoding="UTF-8"?>
<testsuites name="Mocha Tests" time="0.0000" tests="0" failures="0">
</testsuites>
The problem is that unless one adds a hash into the file name then later test suites overwrite earlier test suites resulting in loss of information.
So, the cypress.json should look like
"reporter": "mocha-junit-reporter",
"reporterOptions": {
"testsuitesTitle": true,
"mochaFile": "./cypress/reports/junit.[hash].xml"
}
The hash gets replaced with a date-time hash and then you'll have a bunch of test xml files to process.
Just to add to the answer above, if you would like to merge all these multiple junit.[hash].xml created into a single mergedreport.xml report, then you can use this package junit-report-merger which is useful for running it on CI pipeline which usually looks for a single reporter with a command like the one below:
jrm ./cypress/reports/mergedreport.xml "./cypress/reports/junit*.xml"
We decided to use JUnit xml files from our tests and upload them during CI as artifacts to Gitlab.
For elm, I followed https://www.npmjs.com/package/elm-test?activeTab=readme and used
./node_modules/.bin/elm-test --compiler ./node_modules/.bin/elm app/frontend/elm/tests/ --reporter=junit
But it actually does nothing. Output is plain text.
MacBook-Pro-6:enectiva admin$ ./node_modules/.bin/elm-test --compiler ./node_modules/.bin/elm app/frontend/elm/tests/ --reporter=junit
elm-test 0.19.0
---------------
Running 286 tests. To reproduce these results, run: elm-test --fuzz 100 --seed 369554180583103 /Users/admin/go/src/enectiva.cz/enectiva/app/frontend/elm/tests/BareTime/Tests.elm /Users/admin/go/src/enectiva.cz/enectiva/app/frontend/elm/tests/ChartAndControlSet/AllEnergies/Tests.elm /Users/admin/go/src/enectiva.cz/enectiva/app/frontend/elm/tests/ChartAndControlSet/ChartPort/Tests.elm /Users/admin/go/src/enectiva.cz/enectiva/app/frontend/elm/tests/ChartAndControlSet/Data/Tests.elm /Users/admin/go/src/enectiva.cz/enectiva/app/frontend/elm/tests/ChartAndControlSet/SingleEnergy/Tests.elm /Users/admin/go/src/enectiva.cz/enectiva/app/frontend/elm/tests/Disableable/Tests.elm /Users/admin/go/src/enectiva.cz/enectiva/app/frontend/elm/tests/Enectiva/Elm/I18n.elm /Users/admin/go/src/enectiva.cz/enectiva/app/frontend/elm/tests/Enectiva/EntityTree/EntityTree.elm /Users/admin/go/src/enectiva.cz/enectiva/app/frontend/elm/tests/Exports/Tests.elm /Users/admin/go/src/enectiva.cz/enectiva/app/frontend/elm/tests/ExportStatePoller/Tests.elm /Users/admin/go/src/enectiva.cz/enectiva/app/frontend/elm/tests/ExportTemplate/Tests.elm /Users/admin/go/src/enectiva.cz/enectiva/app/frontend/elm/tests/HourFilter/Tests.elm /Users/admin/go/src/enectiva.cz/enectiva/app/frontend/elm/tests/PriceListForm/Tests.elm /Users/admin/go/src/enectiva.cz/enectiva/app/frontend/elm/tests/SelectionState/Tests.elm /Users/admin/go/src/enectiva.cz/enectiva/app/frontend/elm/tests/SourceSelection2/Tests.elm /Users/admin/go/src/enectiva.cz/enectiva/app/frontend/elm/tests/Visibility/Tests.elm
TEST RUN PASSED
Duration: 1049 ms
Passed: 286
Failed: 0
The same with json.
As I see from output from reproduce part, it looks like elm-test did not even notice the reporter flag.
Does anyone have idea for solution?
My bad.
Typo, there should be used report instead of reporter.
When trying to update composer in Windows 10 (before today it was fine). But today i got error like this
Reading C:/Users/Wilson/AppData/Local/Composer/repo/https---packagist.org/p-provider-2013.json from cache
Content-Length mismatch
http://packagist.org could not be fully loaded, package information was loaded from the local cache and may be out of date
Downloading http://packagist.org/p/provider-2017-01%24464ecabe7bed9235d9c8eab9973bf43265f6c91cf94ba8c49425d34dcb54b34e.json
[Composer\Downloader\TransportException]
The "http://packagist.org/p/provider-2017-01%24464ecabe7bed9235d9c8eab9973bf43265f6c91cf94ba8c49425d34dcb54b34e.jso
n" file could not be downloaded (HTTP/1.1 302 Found)
Exception trace:
() at phar://C:/ProgramData/ComposerSetup/bin/composer.phar/src/Composer/Util/RemoteFilesystem.php:373
Composer\Util\RemoteFilesystem->get() at phar://C:/ProgramData/ComposerSetup/bin/composer.phar/src/Composer/Util/RemoteFilesystem.php:101
Composer\Util\RemoteFilesystem->getContents() at phar://C:/ProgramData/ComposerSetup/bin/composer.phar/src/Composer/Repository/ComposerRepository.php:665
Composer\Repository\ComposerRepository->fetchFile() at phar://C:/ProgramData/ComposerSetup/bin/composer.phar/src/Composer/Repository/ComposerRepository.php:577
Composer\Repository\ComposerRepository->loadProviderListings() at phar://C:/ProgramData/ComposerSetup/bin/composer.phar/src/Composer/Repository/ComposerRepository.php:296
Composer\Repository\ComposerRepository->whatProvides() at phar://C:/ProgramData/ComposerSetup/bin/composer.phar/src/Composer/DependencyResolver/Pool.php:204
Composer\DependencyResolver\Pool->computeWhatProvides() at phar://C:/ProgramData/ComposerSetup/bin/composer.phar/src/Composer/DependencyResolver/Pool.php:193
Composer\DependencyResolver\Pool->whatProvides() at phar://C:/ProgramData/ComposerSetup/bin/composer.phar/src/Composer/Installer.php:987
Composer\Installer->processDevPackages() at phar://C:/ProgramData/ComposerSetup/bin/composer.phar/src/Composer/Installer.php:466
Composer\Installer->doInstall() at phar://C:/ProgramData/ComposerSetup/bin/composer.phar/src/Composer/Installer.php:223
Composer\Installer->run() at phar://C:/ProgramData/ComposerSetup/bin/composer.phar/src/Composer/Command/UpdateCommand.php:158
Composer\Command\UpdateCommand->execute() at phar://C:/ProgramData/ComposerSetup/bin/composer.phar/vendor/symfony/console/Command/Command.php:257
Symfony\Component\Console\Command\Command->run() at phar://C:/ProgramData/ComposerSetup/bin/composer.phar/vendor/symfony/console/Application.php:850
Symfony\Component\Console\Application->doRunCommand() at phar://C:/ProgramData/ComposerSetup/bin/composer.phar/vendor/symfony/console/Application.php:193
Symfony\Component\Console\Application->doRun() at phar://C:/ProgramData/ComposerSetup/bin/composer.phar/src/Composer/Console/Application.php:227
Composer\Console\Application->doRun() at phar://C:/ProgramData/ComposerSetup/bin/composer.phar/vendor/symfony/console/Application.php:124
Symfony\Component\Console\Application->run() at phar://C:/ProgramData/ComposerSetup/bin/composer.phar/src/Composer/Console/Application.php:100
Composer\Console\Application->run() at phar://C:/ProgramData/ComposerSetup/bin/composer.phar/bin/composer:54
require() at C:\ProgramData\ComposerSetup\bin\composer.phar:24
Please help. Thanks.
Actually I have added two same plugins with different name like
"kartik-v/yii2-widgets": "*", and "kartik-v/yii2-widget-select2": "#dev"
so the composer give result (HTTP/1.1 302 Found).
Thanks again to Bizley for commenting my question.
I'm trying to create a iso bootable file by grub-mkrescue. But I require to assign the iso's label.
After read the man page, I guess here is a correct command line, but failed.
grub-mkrescue -o "my_arch.iso" -- -volid=MY_ARCH my_iso_dir
It will show error as:
xorriso 1.4.2 : RockRidge filesystem manipulator, libburnia project.
Drive current: -outdev 'stdio:my_arch.iso'
Media current: stdio file, overwriteable
Media status : is blank
Media summary: 0 sessions, 0 data blocks, 0 data, 19.1g free
Added to ISO image: directory '/'='/tmp/grub.ZoYEzy'
xorriso : UPDATE : 613 files added in 1 seconds
xorriso : FAILURE : -as mkisofs: Unrecognized option '-volid=MY_ARCH'
xorriso : UPDATE : 613 files added in 1 seconds
xorriso : aborting : -abort_on 'FAILURE' encountered 'FAILURE'
According the 'info grub-mkrescue' document:
All arguments not explicitly listed as 'grub-mkrescue' options are
passed on directly to 'xorriso' in 'mkisofs' emulation mode. Options
passed to 'xorriso' will normally be interpreted as 'mkisofs' options;
if the option '--' is used, then anything after that will be interpreted
as native 'xorriso' options.
Non-option arguments specify additional source directories. This is
commonly used to add extra files to the image:
The -as mkisofs emulation of xorriso understands
-V MY_ARCH
or
-volid MY_ARCH
but not
-volid=MY_ARCH
Further be aware that you obviously use the intermediate C version of
grub-mkrescue which does not comply to the documentation you quoted.
This version demands '--' as delimiter between grub-mkrescue options
and xorriso -as mkisofs options.
But if you have '--' among the arguments of old grub-mkrescue shell script
or of current grub-mkrescue C program, then you will drop out of mkisofs
emulation. This will earn you an error message
xorriso : FAILURE : Not a known command: 'my_iso_dir'
i am attempting to create my first mule server but i get an error for any external scheme i try and include,
my Config file is as follows (working on Eclipse Indigo with mule standalone 3.2 installation):
<?xml version="1.0" encoding="UTF-8"?>
<mule xmlns="http://www.mulesoft.org/schema/mule/core"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:spring="http://www.springframework.org/schema/beans"
xmlns:http="http://www.mulesoft.org/schema/mule/http"
xmlns:vm="http://www.mulesoft.org/schema/mule/vm"
xmlns:quartz="http://www.mulesoft.org/schema/mule/quartz"
xsi:schemaLocation="
http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-3.0.xsd
http://www.mulesoft.org/schema/mule/core http://www.mulesoft.org/schema/mule/core/3.2/mule.xsd
http://www.mulesoft.org/schema/mule/quartz http://www.mulesoft.org/schema/mule/quartz/current/mule-quartz.xsd
http://www.mulesoft.org/schema/mule/http http://www.mulesoft.org/schema/mule/http/3.2/mule-http.xsd
http://www.mulesoft.org/schema/mule/vm http://www.mulesoft.org/schema/mule/vm/3.2/mule-vm.xsd">
<flow name="ChatListener">
<quartz:inbound-endpoint jobName="eventTimer" repeatInterval="2000">
<quartz:event-generator-job>
<quartz:payload>Poll Chat DB</quartz:payload>
</quartz:event-generator-job>
</quartz:inbound-endpoint>
<component>
<singleton-object class="com.TimeLineListener.ChatListener" />
</component>
<vm:outbound-endpoint path="ChatMsgs" exchange-pattern="one-way"/>
</flow>
<flow name="TimeLineMsgSender">
<composite-source>
<!-- Incoming Chat Msgs -->
<vm:inbound-endpoint path="ChatMsgs" exchange-pattern="one-way"/>
<!-- Incoming SIEM Msgs -->
<vm:inbound-endpoint path="SIEMMsgs" exchange-pattern="one-way"/>
<!-- Incoming NMS Msgs -->
<vm:inbound-endpoint path="NMSMsgs" exchange-pattern="one-way"/>
</composite-source>
<!-- Tested OutPut endpoint -->
<stdio:outbound-endpoint system="OUT"/>
</flow>
</mule>
and the errors i recieve are:
1.
The prefix "stdio" for element "stdio:outbound-endpoint" is not bound. mule-config.xml /ChatTester line 41 XML Problem
2.
cvc-complex-type.2.4.a: Invalid content was found starting with element 'vm:inbound-endpoint'. One of '{"http://www.mulesoft.org/schema/mule/core":abstract-inbound-endpoint}' is expected. mule-config.xml /ChatTester line 31 XML Problem
3.
cvc-complex-type.2.4.a: Invalid content was found starting with element 'quartz:inbound-endpoint'. One of '{"http://www.mulesoft.org/schema/mule/core":description, "http://www.mulesoft.org/schema/mule/core":composite-source, "http://www.mulesoft.org/schema/mule/core":abstract-inbound-endpoint, "http://www.mulesoft.org/schema/mule/core":abstract-message-processor, "http://www.mulesoft.org/schema/mule/core":abstract-outbound-endpoint, "http://www.mulesoft.org/schema/mule/core":response}' is expected. mule-config.xml /ChatTester line 17 XML Problem
any idea what i"m doing wrong?
1.
The prefix "stdio" for element "stdio:outbound-endpoint" is not bound. mule-config.xml /ChatTester line 41 XML Problem
This one is easy: you're missing the stdio namespace declaration.
2.
cvc-complex-type.2.4.a: Invalid content was found starting with element 'vm:inbound-endpoint'. One of '{"http://www.mulesoft.org/schema/mule/core":abstract-inbound-endpoint}' is expected. mule-config.xml /ChatTester line 31 XML Problem
3.
cvc-complex-type.2.4.a: Invalid content was found starting with element 'quartz:inbound-endpoint'. One of '{"http://www.mulesoft.org/schema/mule/core":description, "http://www.mulesoft.org/schema/mule/core":composite-source, "http://www.mulesoft.org/schema/mule/core":abstract-inbound-endpoint, "http://www.mulesoft.org/schema/mule/core":abstract-message-processor, "http://www.mulesoft.org/schema/mule/core":abstract-outbound-endpoint, "http://www.mulesoft.org/schema/mule/core":response}' is expected. mule-config.xml /ChatTester line 17 XML Problem
For these ones: I don't know. Maybe due to the mix of "current" and "3.2" you're using in the namespace locations? Try only with "3.2" instead of current to see if it helps.
Otherwise, nothing visibly crazy in your config :)
Actually, this is a problem of Eclipse and doesn't relate to your configuration. Hope this helps:
"Since Mule’s schemas are not split over multiple schema files, it’s safe to turn off this feature. In Eclipse’s preferences, go to XML > XML Files > Validation and clear the Honour all schema locations check box. Mule config files should now validate without errors again."-MuleSolf Blog.
For more details: http://blogs.mulesoft.org/overcoming-xml-validation-errors-in-eclipse-35/