manifoldcf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Wright (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CONNECTORS-1196) Proposal to update Manifold Crawler UI
Date Wed, 22 Mar 2017 11:44:42 GMT

    [ https://issues.apache.org/jira/browse/CONNECTORS-1196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15936165#comment-15936165
] 

Karl Wright commented on CONNECTORS-1196:
-----------------------------------------

I just got another odd failure, this time for the Kafka connector.  The connector itself seems
to have thrown a RuntimeException when displaying the status of the output connection (a different
problem which I'll chase down shortly).  After that, however, the UI proceeded as it should
have, but failed with this error:

{code}
    [junit] Testcase: createConnectionsAndJob(org.apache.manifoldcf.agents.output.kafka.NavigationHSQLDBUI):
   Caused an ERROR
    [junit] stale element reference: element is not attached to the page document
    [junit]   (Session info: chrome=56.0.2924.87)
    [junit]   (Driver info: chromedriver=2.28.455520 (cc17746adff54984afff480136733114c6b3704b),platform=Windows
NT 6.1.7601 SP1 x86_64) (WARNING: The server did not provide any stacktrace information)
    [junit] Command duration or timeout: 10 milliseconds
    [junit] For documentation on this error, please visit: http://seleniumhq.org/exceptions/stale_element_reference.html
    [junit] Build info: version: '3.3.1', revision: '5234b325d5', time: '2017-03-10 09:10:29
+0000'
    [junit] System info: host: 'B3NGYY1', ip: '10.222.203.174', os.name: 'Windows 7', os.arch:
'amd64', os.version: '6.1', java.version: '1.8.0_05'
    [junit] Driver info: org.openqa.selenium.chrome.ChromeDriver
    [junit] Capabilities [{applicationCacheEnabled=false, rotatable=false, mobileEmulationEnabled=false,
networkConnectionEnabled=false, chrome={chromedriverVersion=2.28.455520 (cc17746adff54984afff480136733114c6b3704b),
userDataDir=C:\Users\kawright\AppData\Local\Temp\scoped_dir7164_5}, takesHeapSnapshot=true,
pageLoadStrategy=normal, databaseEnabled=false, handlesAlerts=true, hasTouchScreen=false,
version=56.0.2924.87, platform=XP, browserConnectionEnabled=false, nativeEvents=true, acceptSslCerts=true,
locationContextEnabled=true, webStorageEnabled=true, browserName=chrome, takesScreenshot=true,
javascriptEnabled=true, cssSelectorsEnabled=true, unexpectedAlertBehaviour=}]
    [junit] Session ID: ad8a9f10369d041042a1078ce3d52a31
    [junit] org.openqa.selenium.StaleElementReferenceException: stale element reference: element
is not attached to the page document
    [junit]   (Session info: chrome=56.0.2924.87)
    [junit]   (Driver info: chromedriver=2.28.455520 (cc17746adff54984afff480136733114c6b3704b),platform=Windows
NT 6.1.7601 SP1 x86_64) (WARNING: The server did not provide any stacktrace information)
    [junit] Command duration or timeout: 10 milliseconds
    [junit] For documentation on this error, please visit: http://seleniumhq.org/exceptions/stale_element_reference.html
    [junit] Build info: version: '3.3.1', revision: '5234b325d5', time: '2017-03-10 09:10:29
+0000'
    [junit] System info: host: 'B3NGYY1', ip: '10.222.203.174', os.name: 'Windows 7', os.arch:
'amd64', os.version: '6.1', java.version: '1.8.0_05'
    [junit] Driver info: org.openqa.selenium.chrome.ChromeDriver
    [junit] Capabilities [{applicationCacheEnabled=false, rotatable=false, mobileEmulationEnabled=false,
networkConnectionEnabled=false, chrome={chromedriverVersion=2.28.455520 (cc17746adff54984afff480136733114c6b3704b),
userDataDir=C:\Users\kawright\AppData\Local\Temp\scoped_dir7164_5}, takesHeapSnapshot=true,
pageLoadStrategy=normal, databaseEnabled=false, handlesAlerts=true, hasTouchScreen=false,
version=56.0.2924.87, platform=XP, browserConnectionEnabled=false, nativeEvents=true, acceptSslCerts=true,
locationContextEnabled=true, webStorageEnabled=true, browserName=chrome, takesScreenshot=true,
javascriptEnabled=true, cssSelectorsEnabled=true, unexpectedAlertBehaviour=}]
    [junit] Session ID: ad8a9f10369d041042a1078ce3d52a31
    [junit]     at java.lang.reflect.Constructor.newInstance(Constructor.java:408)
    [junit]     at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:216)
    [junit]     at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:168)
    [junit]     at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:638)
    [junit]     at org.openqa.selenium.remote.RemoteWebElement.execute(RemoteWebElement.java:274)
    [junit]     at org.openqa.selenium.remote.RemoteWebElement.getAttribute(RemoteWebElement.java:126)
    [junit]     at org.apache.manifoldcf.core.tests.SeleniumTester.hasClass(SeleniumTester.java:472)
    [junit]     at org.apache.manifoldcf.core.tests.SeleniumTester.selectValue(SeleniumTester.java:439)
    [junit]     at org.apache.manifoldcf.agents.output.kafka.NavigationHSQLDBUI.createConnectionsAndJob(NavigationHSQLDBUI.java:106)
{code}

The line it failed on was:

{code}
    testerInstance.selectValue("connectionname","MyRepositoryConnection");
{code}

... while setting up a job.


> Proposal to update Manifold Crawler UI
> --------------------------------------
>
>                 Key: CONNECTORS-1196
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-1196
>             Project: ManifoldCF
>          Issue Type: Improvement
>          Components: Framework core
>    Affects Versions: ManifoldCF next
>            Reporter: Kishore Kumar
>            Assignee: Kishore Kumar
>             Fix For: ManifoldCF next
>
>         Attachments: Bandwidth Report.png, Index.jsp.png, List Repository.png, Report.png,
View.png
>
>
> Hi,
> I have been working on a new User Interface for ManifoldCF.
> This UI is based on Bootstrap, jQuery and some other opensource scripts.
> Only the index.jsp will be loaded once and other page are rendered using AJAX call, making
it more responsive and modern.
> Please find the attached screenshots.
> *Backward compatibility:*
> Since most of our tab comes from connectors, those tabs will be displayed as it is with
no immediate attention required. (see sample screenshot attached)
> *What next?*
> In future we can add Charts to our reports where ever applicable, so that it will be
more user friendly & informative for end users.
> Can make use of Web socket to notify exception or error to users as Notifications.
> *Browser compatibility*
> Has been tested with most latest browser and IE10, will try to add support for IE8 with
acceptable degradation.
> Any suggestion, concern much appreciated.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message