Working on SBSM test to handle a feedback.
Looking at the art_object for Bhutan (ID 306) via bin/admin
davaz> @app.load_artobject(306).text[0..119] -> <b>views 71,542<br /></b>http://www.youtube.com/watch?v=Q9VKZeHaUIc<br />http://www.youtube.com/watch?v=UQAxme4vLQ4<br / davaz> @app.load_artobject(306).text[120..240] -> ><br /><b>BHUTAN LIVE</b><br />— Bhutan, known as the Land of the Thunder Dragon because of its violent storms, has a pop
This does not look very different from a simpler movie (ID 1763) description
davaz> @app.load_artobject(1763).text[0..119] -> Change Text of movie 1763 at 10:26<br /><br />
Changing the item worked and afterwards (even after a restart of the service) bin/admin shows
davaz> @app.load_artobject(1763).text[0..119] -> Change Text of movie 1763 at 10:26<br /><b>Even more changes at 9.55 on 8.03.2107</b><br />
But after changing the number from 71,542 to 71,544 of visits for Bhutan from bin/admin still reports
davaz> @app.load_artobject(306).text[0..119] -> <b>views 71,542<br /></b>http://www.youtube.com/watch?v=Q9VKZeHaUIc<br />http://www.youtube.com/watch?v=UQAxme4vLQ4<br /
It is weird. Update works if one updates the date field by entering 01.01.1999 (even when it only displays 01.01.99)
Confirmed my suspicion via irb
irb(main):001:0> require 'time'
=> true
irb(main):003:0> Date.parse('01.01.99')
ArgumentError: invalid date
from (irb):3:in `parse'
from (irb):3
from /home/niklaus/.rbenv/versions/2.3.1/bin/irb:11:in `<main>'
irb(main):004:0> Date.parse('01.01.1999')
=> #<Date: 1999-01-01 ((2451180j,0s,0n),+0s,2299161j)>
Pushed commit
Added a reminder for the needed date format with commit Added needed date format
Fixed loading bin/ydimd with commit Fixed loading bin/ydimd
Zeno also wants to fix an error when installing ypdf-writer which reports
Parsing documentation for ypdf-writer-1.3.3 unable to convert "\x93" from ASCII-8BIT to UTF-8 for lib/pdf/writer/object/image.rb, skipping unable to convert "\x93" from ASCII-8BIT to UTF-8 for lib/pdf/writer/object/page.rb, skipping
Looking at the file types, I realll see the weird Non-ISO extended-ASCII text for image.rb and page.rb
file lib/pdf/writer/object/*.rb lib/pdf/writer/object/action.rb: C++ source, ASCII text lib/pdf/writer/object/annotation.rb: C++ source, ASCII text lib/pdf/writer/object/catalog.rb: C++ source, ASCII text lib/pdf/writer/object/contents.rb: C++ source, ASCII text lib/pdf/writer/object/destination.rb: C++ source, ASCII text lib/pdf/writer/object/encryption.rb: C++ source, ASCII text lib/pdf/writer/object/font.rb: C++ source, ASCII text lib/pdf/writer/object/fontdescriptor.rb: C++ source, ASCII text lib/pdf/writer/object/fontencoding.rb: C++ source, ASCII text lib/pdf/writer/object/image.rb: Non-ISO extended-ASCII text lib/pdf/writer/object/info.rb: C++ source, ASCII text lib/pdf/writer/object/outline.rb: C++ source, ASCII text lib/pdf/writer/object/outlines.rb: C++ source, ASCII text lib/pdf/writer/object/page.rb: C++ source, Non-ISO extended-ASCII text lib/pdf/writer/object/pages.rb: C++ source, ASCII text lib/pdf/writer/object/procset.rb: C++ source, ASCII text lib/pdf/writer/object/viewerpreferences.rb: C++ source, ASCII text
Pushed commit Replace non-UTF-8 chars
But I do not think that this commit will change the problem that the ydim reminders have wrong Umlauts in their PDFs.
But now we have the problem that the ydim-html does not start again. I am wondering why netstat -lptu | grep 12375 returns only TCP6 tcp6 0 thinpower:12375 [::]:* LISTEN 23570/ydimd, whereas on fastpower I see for port 80006 tcp 0 0 localhost:8006 *:* LISTEN 23625/ruby231
After downgrading ydim to the olde version 1.0.1 and ydim-html to 1.0.2 the services work again on thinpower. And netstat shows now a TCP 4 connection
tcp 0 0 192.168.0.36:12375 *:* LISTEN 17266/ydimd
Did not find any clue till now. May be the client and server config from ydim got messed up with my changes. Will try to use different names tommorrow.
Pushd commit Added calculation/variant to the DDD export
Continue work. Virbac uses bbmb, but the bbmb does not include any test for the viral modules. Also BBMB requires ydim which uses the rmail gem, which we want to replace everywhere by the mail gem, as it allows easy tests. Done with commit
Pushed commits:
Working on the unit tests of bbmb. Found a seed which breaks a test. See output
bundle exec rake Run options: --seed 10372 # Running: ...............................................................FSSSSSS............................ Finished in 0.548162s, 178.7793 runs/s, 631.2003 assertions/s. 1) Failure: BBMB::Util::TestInvoicer#test_create_invoice [/home/niklaus/git/bbmb/test/util/test_invoicer.rb:74]: Expected: #<OpenStruct unique_id=2> Actual: -UNDEFINED-