Re: [fossil-users] Ticket 305143bd876f693f446f78d12dbef143c46eec58
Oops. I didn't see this, Richard. Sorry. I'll get this set up now and send you the results. Once I figure out how to get Tcl working. :) On 17 March 2011 01:21, Richard Hipp d...@sqlite.org wrote: On Wed, Mar 16, 2011 at 11:30 AM, Michael Richter ttmrich...@gmail.comwrote: OK, this is the sequence I've tried on my main workstation (Ubuntu 10.04): 1. Delete all fossil-scm.org cookies. 2. Close my browser (Chrome 10.0.648.134). 3. Re-open my browser. 4. Go to fossil-scm.org. 5. Log in. 6. Click on Timeline. Result: you are not logged in. If I repeat this experiment on my backup machine (Windows XP, Chrome 10.0.648.133) I do not have this problem. Curious about that, I tried other browsers (Opera, Firefox) on my main machine again. Again I don't have this problem. The issue seems specific to Chrome under Linux in my case. I have no idea how to proceed from here on however because I can't figure out what could be going wrong that affects only Fossil and nothing else, especially since I killed all cookies related to the fossil-scm.org domain. Any suggestions or ideas on what's next to investigate? The attachment is a Tcl/Tk script that sets up a TCP/IP proxy. Please make it point to http://www.fossil-scm.org/ and then point your Chrome browser at the proxy. Record your traffic. Send me what you see. -- D. Richard Hipp d...@sqlite.org -- Perhaps people don't believe this, but throughout all of the discussions of entering China our focus has really been what's best for the Chinese people. It's not been about our revenue or profit or whatnot. --Sergey Brin, demonstrating the emptiness of the don't be evil mantra. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Ticket 305143bd876f693f446f78d12dbef143c46eec58
On Mon, Mar 21, 2011 at 10:01 AM, Michael Richter ttmrich...@gmail.comwrote: OK, perhaps I'm being as thick as a whale omlette here, but I cannot get this to work at all. First attempt: relay-to was set to www.fossil-scm.org:80, listen was set to 8180. I access http://localhost:8180 and I get ... the SQLite home page, not Fossil's. Tinkering around with various values for relay-to always gets me either SQLite's home page or error messages. What, precisely, should I be setting up in there? Bummer. www.sqlite.org and www.fossil-scm.org use the same IP address. The web server distinguishes between them by looking at the HOST: parameter in the HTTP header. But with the setup above, the HOST: parameter is being set to localhost:8180 which the web server then defaults to SQLite. I'm not sure how to work around that. Anybody else have any ideas on how to eavesdrop on the TCP/IP connection between the web browser and the Fossil web server? On 21 March 2011 21:49, Michael Richter ttmrich...@gmail.com wrote: Oops. I didn't see this, Richard. Sorry. I'll get this set up now and send you the results. Once I figure out how to get Tcl working. :) On 17 March 2011 01:21, Richard Hipp d...@sqlite.org wrote: On Wed, Mar 16, 2011 at 11:30 AM, Michael Richter ttmrich...@gmail.comwrote: OK, this is the sequence I've tried on my main workstation (Ubuntu 10.04): 1. Delete all fossil-scm.org cookies. 2. Close my browser (Chrome 10.0.648.134). 3. Re-open my browser. 4. Go to fossil-scm.org. 5. Log in. 6. Click on Timeline. Result: you are not logged in. If I repeat this experiment on my backup machine (Windows XP, Chrome 10.0.648.133) I do not have this problem. Curious about that, I tried other browsers (Opera, Firefox) on my main machine again. Again I don't have this problem. The issue seems specific to Chrome under Linux in my case. I have no idea how to proceed from here on however because I can't figure out what could be going wrong that affects only Fossil and nothing else, especially since I killed all cookies related to the fossil-scm.org domain. Any suggestions or ideas on what's next to investigate? The attachment is a Tcl/Tk script that sets up a TCP/IP proxy. Please make it point to http://www.fossil-scm.org/ and then point your Chrome browser at the proxy. Record your traffic. Send me what you see. -- D. Richard Hipp d...@sqlite.org -- Perhaps people don't believe this, but throughout all of the discussions of entering China our focus has really been what's best for the Chinese people. It's not been about our revenue or profit or whatnot. --Sergey Brin, demonstrating the emptiness of the don't be evil mantra. -- Perhaps people don't believe this, but throughout all of the discussions of entering China our focus has really been what's best for the Chinese people. It's not been about our revenue or profit or whatnot. --Sergey Brin, demonstrating the emptiness of the don't be evil mantra. -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Ticket 305143bd876f693f446f78d12dbef143c46eec58
On Mon, Mar 21, 2011 at 3:21 PM, Richard Hipp d...@sqlite.org wrote: On Mon, Mar 21, 2011 at 10:01 AM, Michael Richter ttmrich...@gmail.comwrote: OK, perhaps I'm being as thick as a whale omlette here, but I cannot get this to work at all. First attempt: relay-to was set to www.fossil-scm.org:80, listen was set to 8180. I access http://localhost:8180 and I get ... the SQLite home page, not Fossil's. Tinkering around with various values for relay-to always gets me either SQLite's home page or error messages. What, precisely, should I be setting up in there? Bummer. www.sqlite.org and www.fossil-scm.org use the same IP address. The web server distinguishes between them by looking at the HOST: parameter in the HTTP header. But with the setup above, the HOST: parameter is being set to localhost:8180 which the web server then defaults to SQLite. I'm not sure how to work around that. Anybody else have any ideas on how to eavesdrop on the TCP/IP connection between the web browser and the Fossil web server? On 21 March 2011 21:49, Michael Richter ttmrich...@gmail.com wrote: Oops. I didn't see this, Richard. Sorry. I'll get this set up now and send you the results. Once I figure out how to get Tcl working. :) On 17 March 2011 01:21, Richard Hipp d...@sqlite.org wrote: On Wed, Mar 16, 2011 at 11:30 AM, Michael Richter ttmrich...@gmail.com wrote: OK, this is the sequence I've tried on my main workstation (Ubuntu 10.04): 1. Delete all fossil-scm.org cookies. 2. Close my browser (Chrome 10.0.648.134). 3. Re-open my browser. 4. Go to fossil-scm.org. 5. Log in. 6. Click on Timeline. Result: you are not logged in. If I repeat this experiment on my backup machine (Windows XP, Chrome 10.0.648.133) I do not have this problem. Curious about that, I tried other browsers (Opera, Firefox) on my main machine again. Again I don't have this problem. The issue seems specific to Chrome under Linux in my case. I have no idea how to proceed from here on however because I can't figure out what could be going wrong that affects only Fossil and nothing else, especially since I killed all cookies related to the fossil-scm.org domain. Any suggestions or ideas on what's next to investigate? The attachment is a Tcl/Tk script that sets up a TCP/IP proxy. Please make it point to http://www.fossil-scm.org/ and then point your Chrome browser at the proxy. Record your traffic. Send me what you see. -- D. Richard Hipp d...@sqlite.org -- Perhaps people don't believe this, but throughout all of the discussions of entering China our focus has really been what's best for the Chinese people. It's not been about our revenue or profit or whatnot. --Sergey Brin, demonstrating the emptiness of the don't be evil mantra. -- Perhaps people don't believe this, but throughout all of the discussions of entering China our focus has really been what's best for the Chinese people. It's not been about our revenue or profit or whatnot. --Sergey Brin, demonstrating the emptiness of the don't be evil mantra. -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users Use a packet level sniffer like WireShark (http://www.*wireshark*.org) Mark ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Ticket 305143bd876f693f446f78d12dbef143c46eec58
On 21 March 2011 22:21, Richard Hipp d...@sqlite.org wrote: On Mon, Mar 21, 2011 at 10:01 AM, Michael Richter ttmrich...@gmail.comwrote: OK, perhaps I'm being as thick as a whale omlette here, but I cannot get this to work at all. First attempt: relay-to was set to www.fossil-scm.org:80, listen was set to 8180. I access http://localhost:8180 and I get ... the SQLite home page, not Fossil's. Tinkering around with various values for relay-to always gets me either SQLite's home page or error messages. What, precisely, should I be setting up in there? Bummer. www.sqlite.org and www.fossil-scm.org use the same IP address. The web server distinguishes between them by looking at the HOST: parameter in the HTTP header. But with the setup above, the HOST: parameter is being set to localhost:8180 which the web server then defaults to SQLite. I'm not sure how to work around that. Anybody else have any ideas on how to eavesdrop on the TCP/IP connection between the web browser and the Fossil web server? Can you set up a dummy fossil repo on that machine at any other port and give it the account error password check for logging in? As another data point, if I use fossil ui, I have no problem logging in and seeing the timeline properly. The same applies if I run fossil server on a remote machine and connect -- indeed the very same machine I'm having problems with in my official repos. The problem seems to lie specifically in repos that are CGI-enabled. -- Perhaps people don't believe this, but throughout all of the discussions of entering China our focus has really been what's best for the Chinese people. It's not been about our revenue or profit or whatnot. --Sergey Brin, demonstrating the emptiness of the don't be evil mantra. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Ticket 305143bd876f693f446f78d12dbef143c46eec58
On Mon, Mar 21, 2011 at 10:34 AM, Michael Richter ttmrich...@gmail.comwrote: On 21 March 2011 22:21, Richard Hipp d...@sqlite.org wrote: On Mon, Mar 21, 2011 at 10:01 AM, Michael Richter ttmrich...@gmail.comwrote: OK, perhaps I'm being as thick as a whale omlette here, but I cannot get this to work at all. First attempt: relay-to was set to www.fossil-scm.org:80, listen was set to 8180. I access http://localhost:8180 and I get ... the SQLite home page, not Fossil's. Tinkering around with various values for relay-to always gets me either SQLite's home page or error messages. What, precisely, should I be setting up in there? Bummer. www.sqlite.org and www.fossil-scm.org use the same IP address. The web server distinguishes between them by looking at the HOST: parameter in the HTTP header. But with the setup above, the HOST: parameter is being set to localhost:8180 which the web server then defaults to SQLite. I'm not sure how to work around that. Anybody else have any ideas on how to eavesdrop on the TCP/IP connection between the web browser and the Fossil web server? Can you set up a dummy fossil repo on that machine at any other port and give it the account error password check for logging in? Try running the experiment here: http://www.sqlite.org/debug1 As another data point, if I use fossil ui, I have no problem logging in and seeing the timeline properly. The same applies if I run fossil server on a remote machine and connect -- indeed the very same machine I'm having problems with in my official repos. The problem seems to lie specifically in repos that are CGI-enabled. -- Perhaps people don't believe this, but throughout all of the discussions of entering China our focus has really been what's best for the Chinese people. It's not been about our revenue or profit or whatnot. --Sergey Brin, demonstrating the emptiness of the don't be evil mantra. -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Ticket 305143bd876f693f446f78d12dbef143c46eec58
On 21 March 2011 23:30, Richard Hipp d...@sqlite.org wrote: On Mon, Mar 21, 2011 at 11:10 AM, Michael Richter ttmrich...@gmail.comwrote: Try running the experiment here: http://www.sqlite.org/debug1 OK, I can log in and see the timeline properly here. Are you running this through CGI or is this just a fossil server running straight up? It is exactly the same CGI script as runs the native Fossil website. That is very odd. So, I've just now done the following two tests: 1. Went to http://www.sqlite.org/debug1 directly in the browser, logged in, accessed the timeline page. 2. Used sockettee directing to www.sqlite.org:80 and went to http://localhost:8180/debug1, logged in, accessed the timeline page. The first test fails. The timeline view is never logged in while everything else is. The second test succeeds. I can access any page and be logged in. This is getting weirder by the minute. -- Perhaps people don't believe this, but throughout all of the discussions of entering China our focus has really been what's best for the Chinese people. It's not been about our revenue or profit or whatnot. --Sergey Brin, demonstrating the emptiness of the don't be evil mantra. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] fossil ignore-glob bug?
On Mon, Mar 21, 2011 at 9:05 AM, Wilson, Ronald rwils...@harris.com wrote: I have been using the ignore-glob feature for a while now, but it doesn’t seem to be working for some of the files that I think should be covered by the glob. As you can see, the *.suo and *.ncb files in the project root are properly ignored in fossil changes (and fossil clean) but the eur_usd*.sqlite files are not ignored. Is this a mistake in my glob because the filenames have more than one extension in them? Also try: eur_usd.*.sqlite If Fossil is somehow relying on Window's file glob expansion, you might need multiple globs to get them all: eur_usd.*,*.sqlite eur_usd.*,*.*.sqlite eur_usd.*,*.*.*.sqlite ronw ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Ticket 305143bd876f693f446f78d12dbef143c46eec58
On Mon, Mar 21, 2011 at 10:21 AM, Richard Hipp d...@sqlite.org wrote: On Mon, Mar 21, 2011 at 10:01 AM, Michael Richter ttmrich...@gmail.com wrote: First attempt: relay-to was set to www.fossil-scm.org:80, listen was set to 8180. I access http://localhost:8180 and I get ... the SQLite home page, not Fossil's. Tinkering around with various values for relay-to always gets me either SQLite's home page or error messages. What, precisely, should I be setting up in there? Bummer. www.sqlite.org and www.fossil-scm.org use the same IP address. The web server distinguishes between them by looking at the HOST: parameter in the HTTP header. But with the setup above, the HOST: parameter is being set to localhost:8180 which the web server then defaults to SQLite. Though you found a workaround that worked, another would have been to modify the Tcl proxy script to replace localhost with fossil-scm.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] how to revert everything
My last three revisions consists of several folder renames, file renames, file creations, and file deletions. It was a mistake and I want to go back to 4 revisions ago. How can I do this? revert -r doesn't allow me to simply specify the root folder. Thanks, Christian ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] how to revert everything
1. Use fossil ui to find the id for the commit you want (you can use the 10 digit id in the timeline) 2. To use that commit - You can make a branch off of the commit id and check out the branch - You can checkout that commit directly, but the next time you commit a change, you'll get a warning that you're making a fork. I'm not totally sure on Fossil's philosophy about this; use fossil commit -f to force a fork Bill Burdick On Mon, Mar 21, 2011 at 11:05 PM, Christian Pekeler christ...@pekeler.orgwrote: My last three revisions consists of several folder renames, file renames, file creations, and file deletions. It was a mistake and I want to go back to 4 revisions ago. How can I do this? revert -r doesn't allow me to simply specify the root folder. Thanks, Christian ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
