Please test Typo 3.99.1 gem

Ruby Apps Typo
21

Only the first one returned true - the others give “The system cannot
find the path specified.” message.

On 7/6/06, Scott L. [email protected] wrote:

is status == true?

I have rails & mongrel & sqlite3-ruby all set up on Windows, and it

You can change the port this way:
algorithms if anyone has one.
the

takes 3+ hours from the time I upload a gem until it’s usable.

I’m getting a ‘404 Not found’ error when running 'sudo get
Typo

http://rubyforge.org/mailman/listinfo/typo-list

Cheers,
[email protected]

–
Cheers,

Kevin

22

Thanks. The absolute/relative path thing is a bug, and I’ll fix it for
the
next release.

I’m not sure what’s up with the test failure. I’ll look into it tonight
and
see what’s up.

Scott

23

Okay, thanks. I’ll have to do a bit of digging to find the right way to
silence Rake under Windows. Anyone know this off the top of their
heads?

Scott

24

Hmm. All tests passed, but the installer reported that tests failed.
Can
you try this?

cd /path/to/typo
irb
status = system(“rake test”)

is status == true?

status = system(“rake test > /dev/null”)

is status == true?

status = system(“rake test > /dev/null 2> /dev/null”)

is status == true?

I suspect that the problem is the last ‘2> /dev/null’ under Windows.

Scott

25

Interesting. I seem to remember something about DOS having a
special-case
handler for /dev/null (or was it /dev/nul – it was DOS).

It looks like I’m going to have to find (or write) a system() wrapper
that
knows about Windows. Does this work:

system(‘rake test > nul:’)

how about adding 2> nul: ?

Scott

26

The test thing is because /dev/null doesn’t exist in Windows. I get
the same error if I run “echo ‘hello’ > /dev/null” in a command prompt
window.

However, if I “mkdir dev” then run the above again, it works. To
Windows, /dev/null is a path with posix separators and it tries to
find <current_drive>:\dev\ and write to the file “null”.

On 7/6/06, Scott L. [email protected] wrote:

On 7/6/06, Juan Lupión [email protected] wrote:

I found that the path must be an absolute path. 'typo install
** Invoke test:units (first_time)
** Invoke environment
“test/unit/configuration_test.rb”
“test/unit/theme_test.rb” “test/unit/trackback_test.rb”
** Invoke test:functionals (first_time)
“test/functional/theme_controller_test.rb”
“test/functional/admin/themes_controller_test.rb”

/Users/juan/Sites/typo/config/…/vendor/rails/activerecord/lib/active_record/transactions.rb:118:in

`create’
/Users/juan/Sites/typo/config/…/vendor/rails/activerecord/lib/active_record/validations.rb:724:in

save!' rake aborted! invoke’
/usr/local/lib/ruby/gems/1.8/gems/rake-0.7.1/bin/rake:7

Typo-list mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/typo-list

–
Cheers,

Kevin

27

File them against the trunk for now. I’ll recategorize as needed :-).

Scott

28

Thanks so much for all the time you’ve put into this. I appreciate
it more than I can say.

The install went flawlessly.

I’ve found some problems with the release, should I file them against
the release, or against trunk.

Matt

29

That’s still sort of a bug, but it’ll have to wait until after 4.0.0
:-).

Scott

30

never mind. I was trying to add an article before I saved the config

Matt

31

I would join Matt and probably everyone else who follows Typo and the
mailing list in congratulating you for your hard work, Scott. You are
saving the entire Typo-sphere!

32

irb(main):001:0> system(“rake test >nul: 2>nul:”)
=> true

That worked on XP SP2 just a second ago. Earlier today I was on 2003
server.

On 7/6/06, Scott L. [email protected] wrote:

Windows, /dev/null is a path with posix separators and it tries to

3.99.1

** Execute db:test:prepare

“test/unit/magnolia_test.rb”
Loaded suite /usr/local/lib/ruby/gems/1.8/gems/rake-
** Execute test:functionals
“test/functional/admin/article_preview_test.rb”
“test/functional/admin/users_controller_test.rb”

/Users/juan/Sites/typo/config/…/vendor/rails/activerecord/lib/active_record/transactions.rb:84:in

`create’
/Users/juan/Sites/typo/config/…/vendor/rails/activerecord/lib/active_record/base.rb:1392:in

`save!’

/usr/local/lib/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:387:in

[email protected]
http://rubyforge.org/mailman/listinfo/typo-list

–
Cheers,

Kevin

33

It’s also worth noting that the FCGI protocol != HTTP even remotely.

That said, there is no reason you can’t speak HTTP on a UNIX domain
socket.
The telnet packaged with the BSDs has been able to connect to named
sockets
for a while now. The difference in overhead doesn’t seem like it would
be
significant enough to warrant that though.

34

Okay. That looks easy enough. I’ll add it to 3.99.2, when I have a
chance.

Scott

35

Yeah. The only real advantage that I can see is better namespace
control–it’s easy to see that /home/bob/typo.http is unique and
controller
by bob, while TCP port 4623 is more trouble-prone.

However, I haven’t seen a single web server that can proxy onto unix
domain
sockets, or a web browser that can use them. So running Typo over HTTP
over
unix domain sockets is kind of pointless right now.

Scott