Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Persistent Bug - Run Experiment on Web Service. #12

Closed
omarzohdi opened this issue Apr 21, 2016 · 4 comments
Closed

Persistent Bug - Run Experiment on Web Service. #12

omarzohdi opened this issue Apr 21, 2016 · 4 comments

Comments

@omarzohdi
Copy link
Contributor

The current version of Tracelab being converted to a web service has breaking bug. Currently upon running an experiment the web service version fails to run it while the Console version works correctly. There are subtle changes in code as seen in the following code snippet (ConosoleUI.cs).

consoleui

The web service version works by passing a string to the parse line function and executing the application as if the command was input through the console. The following code snippets (TraceLab_UI.aspx.cs, Adaptor.cs) show the code flow from the web page to the previous code snippet (ConsoleUI.cs).

tracelab_ui aspx cs
adaptor

The main bug manifests itself in the following code snippet (ExperimentRunner.cs) upon running the experiment the the m_runnableExperiment.IsEmpty flag returns a value of true. This Skips execution and returns an unsuccessful experiment run.

experimentrunner

@omarzohdi
Copy link
Contributor Author

While tracing the initial application execution, there's a discrepancy in the amount of components found in the directories by the initial component scan. The Following code snippet (TraceLabApplication.cs) shows the Component directories while running the application as a console application:
componentdir_console
The two directories are correct and seem to be loaded into the application correctly. While running application as a web service the result is the same as shown in the following code snippet (TraceLabApplication.cs):

componentsdir_web

However when scanning the actual components the number of components loaded in the applications seems to differ between the two versions. In the console application the number of components in the components collection is 88 as shown in the the following code snippet (TraceLabApplication.cs):

componentcount_console

While in the web application the number of components in the components collection is 6 as shown in the following code snippet (TraceLabApplication.cs):

componentcount_web

This could be the cause of the experiment not running as the components essential for the experiment may be missing.

Note: The only difference between the two applications while debugging is that the TraceLab project and the TraceLabConsole project are both run as Libraries and not as a Window Application and Console application respectively

@omarzohdi
Copy link
Contributor Author

Output Log files when Loading the Component Library on both versions of the application.

ComponentLibraryOutput_Web.txt
ComponentLibraryOutput_Console.txt

@omarzohdi
Copy link
Contributor Author

There seems to be discrepancies in the scan method (ComponentScanner.cs) when loading components between the two versions. The number of directories loaded seem to be different. This could be the issue, or maybe it's nothing. I'm writing this comment as a quick reminded. More testing necessary.

scanmethod

@cebernalc
Copy link

cebernalc commented Mar 26, 2017

Closing this issue since it will be handled in #17 with more information

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants