You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bloodhound.apache.org by Wenli Ji <we...@yahoo.com.INVALID> on 2014/06/21 07:19:17 UTC
How to start Bloodhound with Eclipse
Hello,
I am able to deploy Bloodhound 0.7 to Apache. However, we need to change the code a bit to build a quality system to meet the special requirement.
I didn't find any doc of how to setup the debug environment. I tried to follow Trac's doc but didn't make it. I believe there should be something different.
Could anyone help?
Thank you very much.
Wenli
Regards
Re: How to start Bloodhound with Eclipse
Posted by Olemis Lang <ol...@gmail.com>.
Hi !
On 6/21/14, Wenli Ji <we...@yahoo.com.invalid> wrote:
[...]
> No, the breakpoints in theme.py didn't get hit. I added breakpoints for most
> of the functions. However, the breakpoints in SocketServer.py of Python27
> did.
>
> I believe I must missed something here.
>
> I am using PyCharm and start it with Run >> Debug 'Bloodhound'. Bloodhound
> is the project name.
>
I use PyDev in Eclipse so it's more straightforward because with
PyCharm it's still necessary to fall back to PyDev remote debugging
anyways . These links might help you with remote debugging in PyCharm
using PyDev remote debugger .
http://stackoverflow.com/questions/6989965/how-do-i-start-up-remote-debugging-with-pycharm
http://www.jetbrains.com/pycharm/webhelp/remote-debugging.html
http://pydev.org/manual_adv_remote_debugger.html
HTH
--
Regards,
Olemis - @olemislc
Apache(tm) Bloodhound contributor
http://issues.apache.org/bloodhound
http://blood-hound.net
Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/
Featured article:
Re: How to start Bloodhound with Eclipse
Posted by Olemis Lang <ol...@gmail.com>.
Hi !
On 6/21/14, Wenli Ji <we...@yahoo.com.invalid> wrote:
[...]
> No, the breakpoints in theme.py didn't get hit. I added breakpoints for most
> of the functions. However, the breakpoints in SocketServer.py of Python27
> did.
>
> I believe I must missed something here.
>
> I am using PyCharm and start it with Run >> Debug 'Bloodhound'. Bloodhound
> is the project name.
>
I use PyDev in Eclipse so it's more straightforward because with
PyCharm it's still necessary to fall back to PyDev remote debugging
anyways . These links might help you with remote debugging in PyCharm
using PyDev remote debugger .
http://stackoverflow.com/questions/6989965/how-do-i-start-up-remote-debugging-with-pycharm
http://www.jetbrains.com/pycharm/webhelp/remote-debugging.html
http://pydev.org/manual_adv_remote_debugger.html
HTH
--
Regards,
Olemis - @olemislc
Apache(tm) Bloodhound contributor
http://issues.apache.org/bloodhound
http://blood-hound.net
Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/
Featured article:
Re: How to start Bloodhound with Eclipse
Posted by Wenli Ji <we...@yahoo.com.INVALID>.
Hi Dammina,
Everything works now. Thanks a lot for your help.
I will look into the doc and try to debug bh..
Regards,
Wenli
On Sunday, June 22, 2014 11:55 AM, Dammina Sahabandu <dm...@gmail.com> wrote:
Hi,
I just noticed your message(please forward it to the list
dev@bloodhound.apache.org :) ). Its great to hear that you have configured
it properly. However the best method to understand bh is to debug the code
and dig into it. And as bh is built on top of trac may be following the
trac documentation will also help you[2]. And if you want to know any
specific thing about the code or if you get into any trouble while
implementing your requirements please let us know. Our Bloodhound community
is more than happy to help you.
[2] http://trac.edgewall.org/wiki/TracGuide
Thanks.
On Sun, Jun 22, 2014 at 4:52 AM, Dammina Sahabandu <dm...@gmail.com>
wrote:
> Hi,
> I just noticed that you message. Its great to hear that you have
> configured it properly. However the best method to understand bh is to
> debug the code and dig into it. And as bh is built on top of trac may be
> following the trac documentation will also help you[2]. And if you want to
> know any specific thing about the code or if you get into any trouble while
> implementing your requirements please let us know. Our Bloodhound community
> is more than happy to help you.
>
> [2] http://trac.edgewall.org/wiki/TracGuide
>
> Thanks.
> Dammina.
>
>
> On Sun, Jun 22, 2014 at 4:46 AM, Dammina Sahabandu <dm...@gmail.com>
> wrote:
>
>> Hi,
>> Good morning.
>> I noticed that you have created the virtual environment using a different
>> method. This may not solve the issue though. But it would be better to
>> follow the following instructions to create the virtual environment.
>> Follow the following steps;(hope you are using sqlite as your db)
>>
>> 1) cd installer
>> 2) python bloodhound_setup.py --project=sqlite --database-type=sqlite
>> --admin-user=admin --admin-password=adminpasswd
>> 3) cd ..
>> 4) Now you will see the virtual environment created within the checkout
>> directory (bh)
>> 5) Open PyCharm, go to settings/project interpreter/python interpreter
>> and point the created local interpreter to python executable in bh
>> 6) Go to run configuration and change python interpreter accordingly (if
>> its not changed automatically)
>> 7) Add Working Directory (path to checkedout directory)\trac\trac\web
>>
>> Try this and let me know :)
>>
>> HTH
>> Dammina.
>>
>>
>> On Sun, Jun 22, 2014 at 1:36 AM, Wenli Ji <we...@yahoo.com> wrote:
>>
>>> Hi Dammina,
>>>
>>> Following shows the breaks I created for both standalone.py and theme.py
>>> when I use the command 'b'. I think the breakpoints were created
>>> successfully. The breakpoints in standalone was hit when starting the
>>> program. However the breakpoints of theme.py still didn't get hit. I can
>>> log in bloodhound and create tickets without triggering any breakpoints..
>>>
>>> Num Type Disp Enb Where
>>> 1 breakpoint keep yes at
>>> d:\projects\source07\trac\trac\web\standalone.py:150
>>> breakpoint already hit 1 time
>>> 2 breakpoint keep yes at
>>> d:\projects\source07\bloodhound_theme\bhtheme\theme.py:549
>>> 3 breakpoint keep yes at
>>> d:\projects\source07\bloodhound_theme\bhtheme\theme.py:255
>>> 4 breakpoint keep yes at
>>> d:\projects\source07\bloodhound_theme\bhtheme\theme.py:194
>>> 5 breakpoint keep yes at
>>> d:\projects\source07\bloodhound_theme\bhtheme\theme.py:334
>>> 6 breakpoint keep yes at
>>> d:\projects\source07\bloodhound_theme\bhtheme\theme.py:537
>>>
>>> Thanks
>>> Wenli
>>>
>>>
>>> On , Wenli Ji <we...@yahoo.com> wrote:
>>>
>>>
>>> Hi Dammina,
>>>
>>> Good morning...
>>>
>>> I tried pdb, the breakpoints in standalone.py could get hit but not for
>>> theme.py.
>>>
>>> Here is the command: D:\projects\Source07\trac\trac\web>python -m pdb
>>> standalone.py "D:\CAPA\apache-b
>>> loodhound-0.7\installer\bloodhound\environments\main" --port=8000 Single
>>> Instance Only: Yes
>>>
>>> Anything else I can try?
>>>
>>> Thanks
>>> Wenli
>>>
>>>
>>>
>>>
>>> On Saturday, June 21, 2014 10:59 PM, Wenli Ji <we...@yahoo.com>
>>> wrote:
>>>
>>>
>>> Hi Dammina,
>>>
>>> 1) Yes, I can run Bloodhound successfully and access it by starting it
>>> from command line, followed the installation guide online.
>>> 2) Didn't try. Will try it later and let you know.
>>>
>>> Thank you
>>>
>>>
>>> On Saturday, June 21, 2014 9:58 PM, Dammina Sahabandu <
>>> dmsahabandu@gmail.com> wrote:
>>>
>>>
>>> Hi,
>>> Okay then we'll start from the beginning.
>>> 1) Did you run bloodhound successfully in your local environment through
>>> starting it from the command prompt? (Not through IDE)
>>> 2) Did you try debug it using the python debugger (pdb)[1]?
>>>
>>> If you haven't please try to debug using pdb and make sure to put break
>>> point to the theme.py. If it works then the problem is with the IDE
>>> configuration.
>>>
>>> [1] https://docs.python.org/2/library/pdb.html
>>>
>>> HTH
>>> Thanks.
>>> Dammina
>>>
>>>
>>> On Sat, Jun 21, 2014 at 6:25 PM, Wenli Ji <we...@yahoo.com> wrote:
>>>
>>> Hi Dammina,
>>>
>>> Bad news... the breakpoints now could be hit in standalone.py, but still
>>> not in the theme.py...
>>>
>>> Any idea why?
>>>
>>> I attached the screenshot of my configuration.
>>> -- D:\projects\Source07 is the checkout of Bloodhound source code
>>> -- D:\CAPA\apache-bloodhound-0.7 is the folder I extracted Bloodhound
>>> v0.7.
>>>
>>> The virtual environment was created after I ran the following scripts:
>>>
>>> cd apache-bloodhound-<version number>/installer
>>> virtualenv --system-site-packages bloodhound
>>>
>>>
>>> Python.exe was created under D:\CAPA\apache-bloodhound-0.7\installer\bloodhound\Scripts.
>>> So I set it as the Python interpreter.
>>>
>>> Is there anything I could try?
>>>
>>> Thanks
>>> Neil
>>>
>>>
>>> On Saturday, June 21, 2014 8:27 PM, Wenli Ji <we...@yahoo.com>
>>> wrote:
>>>
>>>
>>> Hi Dammina,
>>>
>>> It works now. So great..
>>>
>>> My mistake, I set parameter to the standalone.py under the installation
>>> folder, not the checkout folder. Everything works after I corrected it.
>>>
>>> Thank you...
>>>
>>> One more question, do you know where can I find something like the
>>> design specification so I can quickly understand the code structure? I want
>>> to change/add some fields when creating a ticket.
>>>
>>> Regards,
>>> Wenli
>>>
>>>
>>> On Saturday, June 21, 2014 6:49 PM, Dammina Sahabandu <
>>> dmsahabandu@gmail.com> wrote:
>>>
>>>
>>> Hi wenli,
>>> No. you just need to run bloodhound_setup.py in the installation
>>> directory. However I notice some differences when I compare your
>>> configuration with mine. I have attached my configuration. Please take a
>>> look at it.
>>>
>>> Thanks
>>>
>>>
>>> On Sat, Jun 21, 2014 at 11:19 AM, Wenli Ji <we...@yahoo.com> wrote:
>>>
>>> Shall I need to run python setup.py install
>>> for bloodhound_theme, bloodhound_search, bloodhound_relations, bloodhound_multiproduct
>>> and bloodhound_dashboard, under the checkout?
>>>
>>> Thanks..
>>>
>>>
>>> On Saturday, June 21, 2014 6:04 PM, Wenli Ji <we...@yahoo.com>
>>> wrote:
>>>
>>>
>>> Hi Dammina,
>>>
>>> Yes, I created it followed your instruction. Attached is the
>>> screenshot...
>>>
>>> I just found that the breakpoints get hit in
>>> \apache-bloodhound-0.7\trac\trac\web\wsgi.py
>>>
>>> But not in the theme.py..
>>>
>>> Really weird.
>>>
>>> Thanks
>>> Wenli
>>>
>>>
>>> On Saturday, June 21, 2014 4:04 PM, Dammina Sahabandu <
>>> dmsahabandu@gmail.com> wrote:
>>>
>>>
>>> Hi Wenli,
>>> Yeah its correct. But did you create the run configuration as I
>>> mentioned above?
>>>
>>> Thanks.
>>>
>>>
>>> On Sat, Jun 21, 2014 at 7:59 AM, Wenli Ji <we...@yahoo.com> wrote:
>>>
>>> Hi Dammina,
>>>
>>> No, the breakpoints in theme.py didn't get hit. I added breakpoints for
>>> most of the functions. However, the breakpoints in SocketServer.py of
>>> Python27 did.
>>>
>>> I believe I must missed something here.
>>>
>>> I am using PyCharm and start it with Run >> Debug 'Bloodhound'.
>>> Bloodhound is the project name.
>>>
>>> Thanks
>>> Wenli
>>>
>>>
>>> On Saturday, June 21, 2014 2:45 PM, Dammina Sahabandu <
>>> dmsahabandu@gmail.com> wrote:
>>>
>>>
>>> Hi Wenji,
>>> I'm really glad that you have setup the remote debugging environment.
>>> However, I'm not very clear what is the issue. So can you put a debug point
>>> in ./bloodhound_theme/bhtheme/theme.py and let me know whether it gets hit.
>>>
>>> Thanks.
>>> Dammina
>>>
>>>
>>> On Sat, Jun 21, 2014 at 12:06 PM, Wenli Ji <we...@yahoo.com.invalid>
>>> wrote:
>>>
>>> Hi Dammina,
>>>
>>> I am able to run Bloodhound in PyCharm now. Thanks for your help.
>>>
>>> I start the standalone.py through debug mode, and set lots of
>>> breakpoints in auth.py. Looks like it's used for login/logout. Then I tried
>>> to login from the homepage, but the breakpoints didn't get triggered?
>>>
>>> Is there something special to debug Bloodhound?
>>>
>>> Thanks
>>> Wenli
>>>
>>>
>>> On Saturday, June 21, 2014 2:04 PM, Wenli Ji <we...@yahoo.com.INVALID>
>>> wrote:
>>>
>>>
>>>
>>> Hi Dammina,
>>>
>>> Could you give me the complete instruction? I am very new to Python and
>>> to Bloodhound.
>>>
>>> I am struggling with it for two days... You help is very appreciated..
>>>
>>> Thank you again.
>>>
>>> Wenli
>>> Regards
>>>
>>>
>>>
>>> On Saturday, June 21, 2014 1:44 PM, Dammina Sahabandu <
>>> dmsahabandu@gmail.com> wrote:
>>>
>>>
>>>
>>> Hi Wenji,
>>> Unfortunately, I'm not using eclipse for the debugging purpose. I use
>>> JetBrains PyCharm IDE for that. In our mail Archive there is a thread
>>> name "Good
>>> Python IDE" discussing something similar. I hope it would be better for
>>> you
>>> to go through it. However, here I have given the instructions extracted
>>> from that thread for setting up PyCharm for remote debugging.
>>>
>>> Checkout the project, create virtual env ... as usual.
>>> Choose Open Directory in PyCharm and locate your bloodhound source.
>>> Go to Preferences / Project Interpreters / Python Interpreters, add a
>>> local interpreter and point it to python executable in bh env.
>>> Create a run configuration like this:
>>> Script: /path/to/checkout/bloodhound/trac/trac/web/standalone.py
>>> Script parameters:
>>> /path/to/checkout/bloodhound/installer/bloodhound/environments/main
>>> --port=8000
>>> Single Instance Only: Yes
>>>
>>> And you are ready to write and debug Bloodhound code :)
>>>
>>> HTH.
>>>
>>> Thanks.
>>> Dammina
>>>
>>>
>>>
>>> On Sat, Jun 21, 2014 at 10:49 AM, Wenli Ji <we...@yahoo.com.invalid>
>>> wrote:
>>>
>>> > Hello,
>>> >
>>> > I am able to deploy Bloodhound 0.7 to Apache. However, we need to
>>> change
>>> > the code a bit to build a quality system to meet the special
>>> requirement.
>>> >
>>> > I didn't find any doc of how to setup the debug environment. I tried to
>>> > follow Trac's doc but didn't make it. I believe there should be
>>> something
>>> > different.
>>> >
>>> > Could anyone help?
>>> >
>>> > Thank you very much.
>>> >
>>> > Wenli
>>> > Regards
>>>
>>>
>>>
>>>
>>> --
>>> Dammina Sahabandu.
>>> Committer for ASF (Apache Bloodhound)
>>> Undergraduate Department of Computer Science and Engineering
>>> University of Moratuwa
>>> Sri Lanka.
>>>
>>>
>>>
>>>
>>> --
>>> Dammina Sahabandu.
>>> Committer for ASF (Apache Bloodhound)
>>> Undergraduate Department of Computer Science and Engineering
>>> University of Moratuwa
>>> Sri Lanka.
>>>
>>>
>>>
>>>
>>>
>>> --
>>> Dammina Sahabandu.
>>> Committer for ASF (Apache Bloodhound)
>>> Undergraduate Department of Computer Science and Engineering
>>> University of Moratuwa
>>> Sri Lanka.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> --
>>> Dammina Sahabandu.
>>> Committer for ASF (Apache Bloodhound)
>>> Undergraduate Department of Computer Science and Engineering
>>> University of Moratuwa
>>> Sri Lanka.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> --
>>> Dammina Sahabandu.
>>> Committer for ASF (Apache Bloodhound)
>>> Undergraduate Department of Computer Science and Engineering
>>> University of Moratuwa
>>> Sri Lanka.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>> --
>> Dammina Sahabandu.
>> Committer for ASF (Apache Bloodhound)
>> Undergraduate Department of Computer Science and Engineering
>> University of Moratuwa
>> Sri Lanka.
>>
>
>
>
> --
> Dammina Sahabandu.
> Committer for ASF (Apache Bloodhound)
> Undergraduate Department of Computer Science and Engineering
> University of Moratuwa
> Sri Lanka.
>
--
Dammina Sahabandu.
Committer for ASF (Apache Bloodhound)
Undergraduate Department of Computer Science and Engineering
University of Moratuwa
Sri Lanka.
Re: How to start Bloodhound with Eclipse
Posted by Dammina Sahabandu <dm...@gmail.com>.
Hi,
I just noticed your message(please forward it to the list
dev@bloodhound.apache.org :) ). Its great to hear that you have configured
it properly. However the best method to understand bh is to debug the code
and dig into it. And as bh is built on top of trac may be following the
trac documentation will also help you[2]. And if you want to know any
specific thing about the code or if you get into any trouble while
implementing your requirements please let us know. Our Bloodhound community
is more than happy to help you.
[2] http://trac.edgewall.org/wiki/TracGuide
Thanks.
On Sun, Jun 22, 2014 at 4:52 AM, Dammina Sahabandu <dm...@gmail.com>
wrote:
> Hi,
> I just noticed that you message. Its great to hear that you have
> configured it properly. However the best method to understand bh is to
> debug the code and dig into it. And as bh is built on top of trac may be
> following the trac documentation will also help you[2]. And if you want to
> know any specific thing about the code or if you get into any trouble while
> implementing your requirements please let us know. Our Bloodhound community
> is more than happy to help you.
>
> [2] http://trac.edgewall.org/wiki/TracGuide
>
> Thanks.
> Dammina.
>
>
> On Sun, Jun 22, 2014 at 4:46 AM, Dammina Sahabandu <dm...@gmail.com>
> wrote:
>
>> Hi,
>> Good morning.
>> I noticed that you have created the virtual environment using a different
>> method. This may not solve the issue though. But it would be better to
>> follow the following instructions to create the virtual environment.
>> Follow the following steps;(hope you are using sqlite as your db)
>>
>> 1) cd installer
>> 2) python bloodhound_setup.py --project=sqlite --database-type=sqlite
>> --admin-user=admin --admin-password=adminpasswd
>> 3) cd ..
>> 4) Now you will see the virtual environment created within the checkout
>> directory (bh)
>> 5) Open PyCharm, go to settings/project interpreter/python interpreter
>> and point the created local interpreter to python executable in bh
>> 6) Go to run configuration and change python interpreter accordingly (if
>> its not changed automatically)
>> 7) Add Working Directory (path to checkedout directory)\trac\trac\web
>>
>> Try this and let me know :)
>>
>> HTH
>> Dammina.
>>
>>
>> On Sun, Jun 22, 2014 at 1:36 AM, Wenli Ji <we...@yahoo.com> wrote:
>>
>>> Hi Dammina,
>>>
>>> Following shows the breaks I created for both standalone.py and theme.py
>>> when I use the command 'b'. I think the breakpoints were created
>>> successfully. The breakpoints in standalone was hit when starting the
>>> program. However the breakpoints of theme.py still didn't get hit. I can
>>> log in bloodhound and create tickets without triggering any breakpoints..
>>>
>>> Num Type Disp Enb Where
>>> 1 breakpoint keep yes at
>>> d:\projects\source07\trac\trac\web\standalone.py:150
>>> breakpoint already hit 1 time
>>> 2 breakpoint keep yes at
>>> d:\projects\source07\bloodhound_theme\bhtheme\theme.py:549
>>> 3 breakpoint keep yes at
>>> d:\projects\source07\bloodhound_theme\bhtheme\theme.py:255
>>> 4 breakpoint keep yes at
>>> d:\projects\source07\bloodhound_theme\bhtheme\theme.py:194
>>> 5 breakpoint keep yes at
>>> d:\projects\source07\bloodhound_theme\bhtheme\theme.py:334
>>> 6 breakpoint keep yes at
>>> d:\projects\source07\bloodhound_theme\bhtheme\theme.py:537
>>>
>>> Thanks
>>> Wenli
>>>
>>>
>>> On , Wenli Ji <we...@yahoo.com> wrote:
>>>
>>>
>>> Hi Dammina,
>>>
>>> Good morning...
>>>
>>> I tried pdb, the breakpoints in standalone.py could get hit but not for
>>> theme.py.
>>>
>>> Here is the command: D:\projects\Source07\trac\trac\web>python -m pdb
>>> standalone.py "D:\CAPA\apache-b
>>> loodhound-0.7\installer\bloodhound\environments\main" --port=8000 Single
>>> Instance Only: Yes
>>>
>>> Anything else I can try?
>>>
>>> Thanks
>>> Wenli
>>>
>>>
>>>
>>>
>>> On Saturday, June 21, 2014 10:59 PM, Wenli Ji <we...@yahoo.com>
>>> wrote:
>>>
>>>
>>> Hi Dammina,
>>>
>>> 1) Yes, I can run Bloodhound successfully and access it by starting it
>>> from command line, followed the installation guide online.
>>> 2) Didn't try. Will try it later and let you know.
>>>
>>> Thank you
>>>
>>>
>>> On Saturday, June 21, 2014 9:58 PM, Dammina Sahabandu <
>>> dmsahabandu@gmail.com> wrote:
>>>
>>>
>>> Hi,
>>> Okay then we'll start from the beginning.
>>> 1) Did you run bloodhound successfully in your local environment through
>>> starting it from the command prompt? (Not through IDE)
>>> 2) Did you try debug it using the python debugger (pdb)[1]?
>>>
>>> If you haven't please try to debug using pdb and make sure to put break
>>> point to the theme.py. If it works then the problem is with the IDE
>>> configuration.
>>>
>>> [1] https://docs.python.org/2/library/pdb.html
>>>
>>> HTH
>>> Thanks.
>>> Dammina
>>>
>>>
>>> On Sat, Jun 21, 2014 at 6:25 PM, Wenli Ji <we...@yahoo.com> wrote:
>>>
>>> Hi Dammina,
>>>
>>> Bad news... the breakpoints now could be hit in standalone.py, but still
>>> not in the theme.py...
>>>
>>> Any idea why?
>>>
>>> I attached the screenshot of my configuration.
>>> -- D:\projects\Source07 is the checkout of Bloodhound source code
>>> -- D:\CAPA\apache-bloodhound-0.7 is the folder I extracted Bloodhound
>>> v0.7.
>>>
>>> The virtual environment was created after I ran the following scripts:
>>>
>>> cd apache-bloodhound-<version number>/installer
>>> virtualenv --system-site-packages bloodhound
>>>
>>>
>>> Python.exe was created under D:\CAPA\apache-bloodhound-0.7\installer\bloodhound\Scripts.
>>> So I set it as the Python interpreter.
>>>
>>> Is there anything I could try?
>>>
>>> Thanks
>>> Neil
>>>
>>>
>>> On Saturday, June 21, 2014 8:27 PM, Wenli Ji <we...@yahoo.com>
>>> wrote:
>>>
>>>
>>> Hi Dammina,
>>>
>>> It works now. So great..
>>>
>>> My mistake, I set parameter to the standalone.py under the installation
>>> folder, not the checkout folder. Everything works after I corrected it.
>>>
>>> Thank you...
>>>
>>> One more question, do you know where can I find something like the
>>> design specification so I can quickly understand the code structure? I want
>>> to change/add some fields when creating a ticket.
>>>
>>> Regards,
>>> Wenli
>>>
>>>
>>> On Saturday, June 21, 2014 6:49 PM, Dammina Sahabandu <
>>> dmsahabandu@gmail.com> wrote:
>>>
>>>
>>> Hi wenli,
>>> No. you just need to run bloodhound_setup.py in the installation
>>> directory. However I notice some differences when I compare your
>>> configuration with mine. I have attached my configuration. Please take a
>>> look at it.
>>>
>>> Thanks
>>>
>>>
>>> On Sat, Jun 21, 2014 at 11:19 AM, Wenli Ji <we...@yahoo.com> wrote:
>>>
>>> Shall I need to run python setup.py install
>>> for bloodhound_theme, bloodhound_search, bloodhound_relations, bloodhound_multiproduct
>>> and bloodhound_dashboard, under the checkout?
>>>
>>> Thanks..
>>>
>>>
>>> On Saturday, June 21, 2014 6:04 PM, Wenli Ji <we...@yahoo.com>
>>> wrote:
>>>
>>>
>>> Hi Dammina,
>>>
>>> Yes, I created it followed your instruction. Attached is the
>>> screenshot...
>>>
>>> I just found that the breakpoints get hit in
>>> \apache-bloodhound-0.7\trac\trac\web\wsgi.py
>>>
>>> But not in the theme.py..
>>>
>>> Really weird.
>>>
>>> Thanks
>>> Wenli
>>>
>>>
>>> On Saturday, June 21, 2014 4:04 PM, Dammina Sahabandu <
>>> dmsahabandu@gmail.com> wrote:
>>>
>>>
>>> Hi Wenli,
>>> Yeah its correct. But did you create the run configuration as I
>>> mentioned above?
>>>
>>> Thanks.
>>>
>>>
>>> On Sat, Jun 21, 2014 at 7:59 AM, Wenli Ji <we...@yahoo.com> wrote:
>>>
>>> Hi Dammina,
>>>
>>> No, the breakpoints in theme.py didn't get hit. I added breakpoints for
>>> most of the functions. However, the breakpoints in SocketServer.py of
>>> Python27 did.
>>>
>>> I believe I must missed something here.
>>>
>>> I am using PyCharm and start it with Run >> Debug 'Bloodhound'.
>>> Bloodhound is the project name.
>>>
>>> Thanks
>>> Wenli
>>>
>>>
>>> On Saturday, June 21, 2014 2:45 PM, Dammina Sahabandu <
>>> dmsahabandu@gmail.com> wrote:
>>>
>>>
>>> Hi Wenji,
>>> I'm really glad that you have setup the remote debugging environment.
>>> However, I'm not very clear what is the issue. So can you put a debug point
>>> in ./bloodhound_theme/bhtheme/theme.py and let me know whether it gets hit.
>>>
>>> Thanks.
>>> Dammina
>>>
>>>
>>> On Sat, Jun 21, 2014 at 12:06 PM, Wenli Ji <we...@yahoo.com.invalid>
>>> wrote:
>>>
>>> Hi Dammina,
>>>
>>> I am able to run Bloodhound in PyCharm now. Thanks for your help.
>>>
>>> I start the standalone.py through debug mode, and set lots of
>>> breakpoints in auth.py. Looks like it's used for login/logout. Then I tried
>>> to login from the homepage, but the breakpoints didn't get triggered?
>>>
>>> Is there something special to debug Bloodhound?
>>>
>>> Thanks
>>> Wenli
>>>
>>>
>>> On Saturday, June 21, 2014 2:04 PM, Wenli Ji <we...@yahoo.com.INVALID>
>>> wrote:
>>>
>>>
>>>
>>> Hi Dammina,
>>>
>>> Could you give me the complete instruction? I am very new to Python and
>>> to Bloodhound.
>>>
>>> I am struggling with it for two days... You help is very appreciated..
>>>
>>> Thank you again.
>>>
>>> Wenli
>>> Regards
>>>
>>>
>>>
>>> On Saturday, June 21, 2014 1:44 PM, Dammina Sahabandu <
>>> dmsahabandu@gmail.com> wrote:
>>>
>>>
>>>
>>> Hi Wenji,
>>> Unfortunately, I'm not using eclipse for the debugging purpose. I use
>>> JetBrains PyCharm IDE for that. In our mail Archive there is a thread
>>> name "Good
>>> Python IDE" discussing something similar. I hope it would be better for
>>> you
>>> to go through it. However, here I have given the instructions extracted
>>> from that thread for setting up PyCharm for remote debugging.
>>>
>>> Checkout the project, create virtual env ... as usual.
>>> Choose Open Directory in PyCharm and locate your bloodhound source.
>>> Go to Preferences / Project Interpreters / Python Interpreters, add a
>>> local interpreter and point it to python executable in bh env.
>>> Create a run configuration like this:
>>> Script: /path/to/checkout/bloodhound/trac/trac/web/standalone.py
>>> Script parameters:
>>> /path/to/checkout/bloodhound/installer/bloodhound/environments/main
>>> --port=8000
>>> Single Instance Only: Yes
>>>
>>> And you are ready to write and debug Bloodhound code :)
>>>
>>> HTH.
>>>
>>> Thanks.
>>> Dammina
>>>
>>>
>>>
>>> On Sat, Jun 21, 2014 at 10:49 AM, Wenli Ji <we...@yahoo.com.invalid>
>>> wrote:
>>>
>>> > Hello,
>>> >
>>> > I am able to deploy Bloodhound 0.7 to Apache. However, we need to
>>> change
>>> > the code a bit to build a quality system to meet the special
>>> requirement.
>>> >
>>> > I didn't find any doc of how to setup the debug environment. I tried to
>>> > follow Trac's doc but didn't make it. I believe there should be
>>> something
>>> > different.
>>> >
>>> > Could anyone help?
>>> >
>>> > Thank you very much.
>>> >
>>> > Wenli
>>> > Regards
>>>
>>>
>>>
>>>
>>> --
>>> Dammina Sahabandu.
>>> Committer for ASF (Apache Bloodhound)
>>> Undergraduate Department of Computer Science and Engineering
>>> University of Moratuwa
>>> Sri Lanka.
>>>
>>>
>>>
>>>
>>> --
>>> Dammina Sahabandu.
>>> Committer for ASF (Apache Bloodhound)
>>> Undergraduate Department of Computer Science and Engineering
>>> University of Moratuwa
>>> Sri Lanka.
>>>
>>>
>>>
>>>
>>>
>>> --
>>> Dammina Sahabandu.
>>> Committer for ASF (Apache Bloodhound)
>>> Undergraduate Department of Computer Science and Engineering
>>> University of Moratuwa
>>> Sri Lanka.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> --
>>> Dammina Sahabandu.
>>> Committer for ASF (Apache Bloodhound)
>>> Undergraduate Department of Computer Science and Engineering
>>> University of Moratuwa
>>> Sri Lanka.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> --
>>> Dammina Sahabandu.
>>> Committer for ASF (Apache Bloodhound)
>>> Undergraduate Department of Computer Science and Engineering
>>> University of Moratuwa
>>> Sri Lanka.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>> --
>> Dammina Sahabandu.
>> Committer for ASF (Apache Bloodhound)
>> Undergraduate Department of Computer Science and Engineering
>> University of Moratuwa
>> Sri Lanka.
>>
>
>
>
> --
> Dammina Sahabandu.
> Committer for ASF (Apache Bloodhound)
> Undergraduate Department of Computer Science and Engineering
> University of Moratuwa
> Sri Lanka.
>
--
Dammina Sahabandu.
Committer for ASF (Apache Bloodhound)
Undergraduate Department of Computer Science and Engineering
University of Moratuwa
Sri Lanka.
Re: How to start Bloodhound with Eclipse
Posted by Wenli Ji <we...@yahoo.com.INVALID>.
Hi Dammina,
No, the breakpoints in theme.py didn't get hit. I added breakpoints for most of the functions. However, the breakpoints in SocketServer.py of Python27 did.
I believe I must missed something here.
I am using PyCharm and start it with Run >> Debug 'Bloodhound'. Bloodhound is the project name.
Thanks
Wenli
On Saturday, June 21, 2014 2:45 PM, Dammina Sahabandu <dm...@gmail.com> wrote:
Hi Wenji,
I'm really glad that you have setup the remote debugging environment. However, I'm not very clear what is the issue. So can you put a debug point in ./bloodhound_theme/bhtheme/theme.py and let me know whether it gets hit.
Thanks.
Dammina
On Sat, Jun 21, 2014 at 12:06 PM, Wenli Ji <we...@yahoo.com.invalid> wrote:
Hi Dammina,
>
>I am able to run Bloodhound in PyCharm now. Thanks for your help.
>
>I start the standalone.py through debug mode, and set lots of breakpoints in auth.py. Looks like it's used for login/logout. Then I tried to login from the homepage, but the breakpoints didn't get triggered?
>
>Is there something special to debug Bloodhound?
>
>Thanks
>Wenli
>
>
>
>On Saturday, June 21, 2014 2:04 PM, Wenli Ji <we...@yahoo.com.INVALID> wrote:
>
>
>
>Hi Dammina,
>
>Could you give me the complete instruction? I am very new to Python and to Bloodhound.
>
>I am struggling with it for two days... You help is very appreciated..
>
>Thank you again.
>
>Wenli
>Regards
>
>
>
>On Saturday, June 21, 2014 1:44 PM, Dammina Sahabandu <dm...@gmail.com> wrote:
>
>
>
>Hi Wenji,
>Unfortunately, I'm not using eclipse for the debugging purpose. I use
>JetBrains PyCharm IDE for that. In our mail Archive there is a thread
>name "Good
>Python IDE" discussing something similar. I hope it would be better for you
>to go through it. However, here I have given the instructions extracted
>from that thread for setting up PyCharm for remote debugging.
>
>Checkout the project, create virtual env ... as usual.
>Choose Open Directory in PyCharm and locate your bloodhound source.
>Go to Preferences / Project Interpreters / Python Interpreters, add a
>local interpreter and point it to python executable in bh env.
>Create a run configuration like this:
> Script: /path/to/checkout/bloodhound/trac/trac/web/standalone.py
> Script parameters:
>/path/to/checkout/bloodhound/installer/bloodhound/environments/main
>--port=8000
> Single Instance Only: Yes
>
>And you are ready to write and debug Bloodhound code :)
>
>HTH.
>
>Thanks.
>Dammina
>
>
>
>On Sat, Jun 21, 2014 at 10:49 AM, Wenli Ji <we...@yahoo.com.invalid>
>wrote:
>
>> Hello,
>>
>> I am able to deploy Bloodhound 0.7 to Apache. However, we need to change
>> the code a bit to build a quality system to meet the special requirement.
>>
>> I didn't find any doc of how to setup the debug environment. I tried to
>> follow Trac's doc but didn't make it. I believe there should be something
>> different.
>>
>> Could anyone help?
>>
>> Thank you very much.
>>
>> Wenli
>> Regards
>
>
>
>
>--
>Dammina Sahabandu.
>Committer for ASF (Apache Bloodhound)
>Undergraduate Department of Computer Science and Engineering
>University of Moratuwa
>Sri Lanka.
--
Dammina Sahabandu.
Committer for ASF (Apache Bloodhound)
Undergraduate Department of Computer Science and Engineering
University of Moratuwa
Sri Lanka.
Re: How to start Bloodhound with Eclipse
Posted by Dammina Sahabandu <dm...@gmail.com>.
Hi Wenji,
I'm really glad that you have setup the remote debugging environment.
However, I'm not very clear what is the issue. So can you put a debug point
in ./bloodhound_theme/bhtheme/theme.py and let me know whether it gets hit.
Thanks.
Dammina
On Sat, Jun 21, 2014 at 12:06 PM, Wenli Ji <we...@yahoo.com.invalid>
wrote:
> Hi Dammina,
>
> I am able to run Bloodhound in PyCharm now. Thanks for your help.
>
> I start the standalone.py through debug mode, and set lots of breakpoints
> in auth.py. Looks like it's used for login/logout. Then I tried to login
> from the homepage, but the breakpoints didn't get triggered?
>
> Is there something special to debug Bloodhound?
>
> Thanks
> Wenli
>
>
> On Saturday, June 21, 2014 2:04 PM, Wenli Ji <we...@yahoo.com.INVALID>
> wrote:
>
>
>
> Hi Dammina,
>
> Could you give me the complete instruction? I am very new to Python and to
> Bloodhound.
>
> I am struggling with it for two days... You help is very appreciated..
>
> Thank you again.
>
> Wenli
> Regards
>
>
>
> On Saturday, June 21, 2014 1:44 PM, Dammina Sahabandu <
> dmsahabandu@gmail.com> wrote:
>
>
>
> Hi Wenji,
> Unfortunately, I'm not using eclipse for the debugging purpose. I use
> JetBrains PyCharm IDE for that. In our mail Archive there is a thread
> name "Good
> Python IDE" discussing something similar. I hope it would be better for you
> to go through it. However, here I have given the instructions extracted
> from that thread for setting up PyCharm for remote debugging.
>
> Checkout the project, create virtual env ... as usual.
> Choose Open Directory in PyCharm and locate your bloodhound source.
> Go to Preferences / Project Interpreters / Python Interpreters, add a
> local interpreter and point it to python executable in bh env.
> Create a run configuration like this:
> Script: /path/to/checkout/bloodhound/trac/trac/web/standalone.py
> Script parameters:
> /path/to/checkout/bloodhound/installer/bloodhound/environments/main
> --port=8000
> Single Instance Only: Yes
>
> And you are ready to write and debug Bloodhound code :)
>
> HTH.
>
> Thanks.
> Dammina
>
>
>
> On Sat, Jun 21, 2014 at 10:49 AM, Wenli Ji <we...@yahoo.com.invalid>
> wrote:
>
> > Hello,
> >
> > I am able to deploy Bloodhound 0.7 to Apache. However, we need to change
> > the code a bit to build a quality system to meet the special requirement.
> >
> > I didn't find any doc of how to setup the debug environment. I tried to
> > follow Trac's doc but didn't make it. I believe there should be something
> > different.
> >
> > Could anyone help?
> >
> > Thank you very much.
> >
> > Wenli
> > Regards
>
>
>
>
> --
> Dammina Sahabandu.
> Committer for ASF (Apache Bloodhound)
> Undergraduate Department of Computer Science and Engineering
> University of Moratuwa
> Sri Lanka.
>
--
Dammina Sahabandu.
Committer for ASF (Apache Bloodhound)
Undergraduate Department of Computer Science and Engineering
University of Moratuwa
Sri Lanka.
Re: How to start Bloodhound with Eclipse
Posted by Wenli Ji <we...@yahoo.com.INVALID>.
Hi Dammina,
I am able to run Bloodhound in PyCharm now. Thanks for your help.
I start the standalone.py through debug mode, and set lots of breakpoints in auth.py. Looks like it's used for login/logout. Then I tried to login from the homepage, but the breakpoints didn't get triggered?
Is there something special to debug Bloodhound?
Thanks
Wenli
On Saturday, June 21, 2014 2:04 PM, Wenli Ji <we...@yahoo.com.INVALID> wrote:
Hi Dammina,
Could you give me the complete instruction? I am very new to Python and to Bloodhound.
I am struggling with it for two days... You help is very appreciated..
Thank you again.
Wenli
Regards
On Saturday, June 21, 2014 1:44 PM, Dammina Sahabandu <dm...@gmail.com> wrote:
Hi Wenji,
Unfortunately, I'm not using eclipse for the debugging purpose. I use
JetBrains PyCharm IDE for that. In our mail Archive there is a thread
name "Good
Python IDE" discussing something similar. I hope it would be better for you
to go through it. However, here I have given the instructions extracted
from that thread for setting up PyCharm for remote debugging.
Checkout the project, create virtual env ... as usual.
Choose Open Directory in PyCharm and locate your bloodhound source.
Go to Preferences / Project Interpreters / Python Interpreters, add a
local interpreter and point it to python executable in bh env.
Create a run configuration like this:
Script: /path/to/checkout/bloodhound/trac/trac/web/standalone.py
Script parameters:
/path/to/checkout/bloodhound/installer/bloodhound/environments/main
--port=8000
Single Instance Only: Yes
And you are ready to write and debug Bloodhound code :)
HTH.
Thanks.
Dammina
On Sat, Jun 21, 2014 at 10:49 AM, Wenli Ji <we...@yahoo.com.invalid>
wrote:
> Hello,
>
> I am able to deploy Bloodhound 0.7 to Apache. However, we need to change
> the code a bit to build a quality system to meet the special requirement.
>
> I didn't find any doc of how to setup the debug environment. I tried to
> follow Trac's doc but didn't make it. I believe there should be something
> different.
>
> Could anyone help?
>
> Thank you very much.
>
> Wenli
> Regards
--
Dammina Sahabandu.
Committer for ASF (Apache Bloodhound)
Undergraduate Department of Computer Science and Engineering
University of Moratuwa
Sri Lanka.
Re: How to start Bloodhound with Eclipse
Posted by Wenli Ji <we...@yahoo.com.INVALID>.
Hi Dammina,
Could you give me the complete instruction? I am very new to Python and to Bloodhound.
I am struggling with it for two days... You help is very appreciated..
Thank you again.
Wenli
Regards
On Saturday, June 21, 2014 1:44 PM, Dammina Sahabandu <dm...@gmail.com> wrote:
Hi Wenji,
Unfortunately, I'm not using eclipse for the debugging purpose. I use
JetBrains PyCharm IDE for that. In our mail Archive there is a thread
name "Good
Python IDE" discussing something similar. I hope it would be better for you
to go through it. However, here I have given the instructions extracted
from that thread for setting up PyCharm for remote debugging.
Checkout the project, create virtual env ... as usual.
Choose Open Directory in PyCharm and locate your bloodhound source.
Go to Preferences / Project Interpreters / Python Interpreters, add a
local interpreter and point it to python executable in bh env.
Create a run configuration like this:
Script: /path/to/checkout/bloodhound/trac/trac/web/standalone.py
Script parameters:
/path/to/checkout/bloodhound/installer/bloodhound/environments/main
--port=8000
Single Instance Only: Yes
And you are ready to write and debug Bloodhound code :)
HTH.
Thanks.
Dammina
On Sat, Jun 21, 2014 at 10:49 AM, Wenli Ji <we...@yahoo.com.invalid>
wrote:
> Hello,
>
> I am able to deploy Bloodhound 0.7 to Apache. However, we need to change
> the code a bit to build a quality system to meet the special requirement.
>
> I didn't find any doc of how to setup the debug environment. I tried to
> follow Trac's doc but didn't make it. I believe there should be something
> different.
>
> Could anyone help?
>
> Thank you very much.
>
> Wenli
> Regards
--
Dammina Sahabandu.
Committer for ASF (Apache Bloodhound)
Undergraduate Department of Computer Science and Engineering
University of Moratuwa
Sri Lanka.
Re: How to start Bloodhound with Eclipse
Posted by Dammina Sahabandu <dm...@gmail.com>.
Hi Wenji,
Unfortunately, I'm not using eclipse for the debugging purpose. I use
JetBrains PyCharm IDE for that. In our mail Archive there is a thread
name "Good
Python IDE" discussing something similar. I hope it would be better for you
to go through it. However, here I have given the instructions extracted
from that thread for setting up PyCharm for remote debugging.
Checkout the project, create virtual env ... as usual.
Choose Open Directory in PyCharm and locate your bloodhound source.
Go to Preferences / Project Interpreters / Python Interpreters, add a
local interpreter and point it to python executable in bh env.
Create a run configuration like this:
Script: /path/to/checkout/bloodhound/trac/trac/web/standalone.py
Script parameters:
/path/to/checkout/bloodhound/installer/bloodhound/environments/main
--port=8000
Single Instance Only: Yes
And you are ready to write and debug Bloodhound code :)
HTH.
Thanks.
Dammina
On Sat, Jun 21, 2014 at 10:49 AM, Wenli Ji <we...@yahoo.com.invalid>
wrote:
> Hello,
>
> I am able to deploy Bloodhound 0.7 to Apache. However, we need to change
> the code a bit to build a quality system to meet the special requirement.
>
> I didn't find any doc of how to setup the debug environment. I tried to
> follow Trac's doc but didn't make it. I believe there should be something
> different.
>
> Could anyone help?
>
> Thank you very much.
>
> Wenli
> Regards
--
Dammina Sahabandu.
Committer for ASF (Apache Bloodhound)
Undergraduate Department of Computer Science and Engineering
University of Moratuwa
Sri Lanka.