search for: do_request

I''m heading out of town, but had a quick thought I wanted to share. Rather then using ambiguous named request helpers in controller specs like "do_request", I''ve been using more readable helpers like "post_create". For example... describe ProjectController do def post_create post :create, ... end before do end it "creates a new project" do Project.should_receive(:create).with(....) post_cre...

...0mA) > [...] > bLength = 0x09 > bDescriptorType = 0x21 > bDescriptorSubType = 0x10 >> RAW dump: >> 0x00 | 0x09, 0x21, 0x10, 0x01, 0x21, 0x01, 0x22, 0x90, >> 0x08 | 0x02 > > This looks reasonable. > > What about this? > > usbconfig -u 4 -a 2 do_request 0x81 0x06 0x2200 0 0x100 > > One thing I noticed about the report descriptor that NUT returned: it has extra zero bytes. > > For instance, these lines: > > 0.157417 Report Descriptor: (656 bytes) => 05 00 84 00 09 00 04 00 a1 00 01 00 09 00 > 0.157431 24 00 a1 00 00 00 8...

...simple? :) I''ve created a couple spec helper methods to refactor some of the common code...for example, require_login_and_correct_user creates two specifications: one for when the user isn''t logged in, and one when the user is logged in but requests someone else''s book. do_request automatically calls do_get/post/put/delete depending on what''s implemented. Here''s all the code: books_controller.rb: http://pastie.caboo.se/29469 books_controller_spec.rb: http://pastie.caboo.se/29470 spec_helper.rb: http://pastie.caboo.se/29471 The specs just feel somewhat un...

>> >> The output was also not as big as you made it out to be. > > Well, I didn't expect the driver to fail *that* badly :-) > > Assuming the UPS is still at /dev/ugen4.2, can you try the following command? (Probably needs to be run as root, with the driver stopped.) > > usbconfig -u 4 -a 2 dump_curr_config_desc Here is output of the command. Thank you for

We had a query yesterday about the VDDK plugin and making it actually obey the weird "Multithreading Considerations" rules in the VDDK documentation (https://vdc-download.vmware.com/vmwb-repository/dcr-public/8f96698a-0e7b-4d67-bb6c-d18a1d101540/ef536a47-27cd-481a-90ef-76b38e75353c/vsphere-vddk-671-programming-guide.pdf) This patch is my attempt to implement this. The idea is that the

...ndpoint 0 ??????? bLength = 0x0007 ??????? bDescriptorType = 0x0005 ??????? bEndpointAddress = 0x0081? <IN> ??????? bmAttributes = 0x0003? <INTERRUPT> ??????? wMaxPacketSize = 0x0008 ??????? bInterval = 0x000c ??????? bRefresh = 0x0000 ??????? bSynchAddress = 0x0000 usbconfig -u 0 -a 5 do_request 0x81 0x06 0x2200 0 0x100 ?datanas: ~# usbconfig -u 0 -a 5 do_request 0x81 0x06 0x2200 0 0x100 REQUEST = <0x05 0x84 0x09 0x04 0xa1 0x01 0x09 0x24 0xa1 0x00 0x85 0x28 0x09 0xfe 0x79 0x01 0x75 0x08 0x95 0x01 0x15 0x00 0x26 0xff 0x00 0xb1 0x03 0x85 0x29 0x09 0xff 0x79 0x05 0xb1 0x03 0x85 0x2b 0x09...

...09 >> bDescriptorType = 0x21 >> bDescriptorSubType = 0x10 >>> RAW dump: >>> 0x00 | 0x09, 0x21, 0x10, 0x01, 0x21, 0x01, 0x22, 0x90, >>> 0x08 | 0x02 >> >> This looks reasonable. >> >> What about this? >> >> usbconfig -u 4 -a 2 do_request 0x81 0x06 0x2200 0 0x100 >> >> One thing I noticed about the report descriptor that NUT returned: it has extra >> zero bytes. >> >> For instance, these lines: >> >> 0.157417 Report Descriptor: (656 bytes) => 05 00 84 00 09 00 04 00 a1 00 01 00 >> 0...

...ion.rb:631:in `connect'' httpclient (2.1.5.2) lib/httpclient/session.rb:522:in `query'' httpclient (2.1.5.2) lib/httpclient/session.rb:147:in `query'' httpclient (2.1.5.2) lib/httpclient.rb:953:in `do_get_block'' httpclient (2.1.5.2) lib/httpclient.rb:765:in `do_request'' httpclient (2.1.5.2) lib/httpclient.rb:848:in `protect_keep_alive_disconnected'' httpclient (2.1.5.2) lib/httpclient.rb:764:in `do_request'' httpclient (2.1.5.2) lib/httpclient.rb:666:in `request'' httpclient (2.1.5.2) lib/httpclient.rb:596:in `post'...

...g here? it ''should try to set the current user from the session'' do controller.session[SessionKeys::USER_ID] = 1 user = mock_model(User) User.stub!(:find).and_return(user) User.should_receive(:find).with(1).and_return(user) controller.should_receive(:set_current_user) do_request end When I watch the spec with my debugger, when it gets to the code, the session is empty, and the spec fails. What would be causing this? Am I setting the session wrong? I have also tried just session, and request.session with the same results. Thanks, Steve

Hi Everyone, I'm having trouble getting TrippLite SMX1500LCDT to work on FreeBSD 11.2, nut 2.7.4 installed from FreeBSD port. The debug output is rather big when I'm starting usbhid-ups initially, Please find that attached (gzipped to comply with message size limit). Subsequently, until I unplug and replug the USB cable, I'm geting a shorter debug output, like this: Network UPS

> What does that revision number correspond to in FreeBSD release numbers? (e.g. 9.3, 10.0) FreeBSD 10.2-RELEASE #0 r286738M the last person probably wasn't able to give the ./configure probably because most people uses the precompiled iso to install NAS4Free.? if you need the ./configure I might have to look for their source on GitHub or something. /usr/local/libexec/nut/usbhid-ups -a

...ndpoint 0 ??????? bLength = 0x0007 ??????? bDescriptorType = 0x0005 ??????? bEndpointAddress = 0x0081? <IN> ??????? bmAttributes = 0x0003? <INTERRUPT> ??????? wMaxPacketSize = 0x0008 ??????? bInterval = 0x000c ??????? bRefresh = 0x0000 ??????? bSynchAddress = 0x0000 usbconfig -u 0 -a 5 do_request 0x81 0x06 0x2200 0 0x100 ?datanas: ~# usbconfig -u 0 -a 5 do_request 0x81 0x06 0x2200 0 0x100 REQUEST = <0x05 0x84 0x09 0x04 0xa1 0x01 0x09 0x24 0xa1 0x00 0x85 0x28 0x09 0xfe 0x79 0x01 0x75 0x08 0x95 0x01 0x15 0x00 0x26 0xff 0x00 0xb1 0x03 0x85 0x29 0x09 0xff 0x79 0x05 0xb1 0x03 0x85 0x2b 0x09...

This is my second attempt at this. The first version (also not working) was here: https://www.redhat.com/archives/libguestfs/2019-October/msg00062.html In part 1/2 I introduce a new .ready_to_serve plugin method which is called after forking and just before accepting any client connection. The idea would be that plugins could start background threads here. However this doesn't work well in

...point 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0081 <IN> bmAttributes = 0x0003 <INTERRUPT> wMaxPacketSize = 0x0008 bInterval = 0x000c bRefresh = 0x0000 bSynchAddress = 0x0000 # usbconfig -u 1 -a 3 do_request 0x81 0x06 0x2200 0 0x100 REQUEST = <0x05 0x84 0x09 0x04 0xa1 0x01 0x09 0x24 0xa1 0x00 0x85 0x28 0x09 0xfe 0x79 0x01 0x75 0x08 0x95 0x01 0x15 0x00 0x26 0xff 0x00 0xb1 0x03 0x85 0x29 0x09 0xff 0x79 0x05 0xb1 0x03 0x85 0x2b 0x09 0xfd 0x79 0x03 0xb1 0x03 0x09 0x1a 0xa1 0x02 0x85 0x30 0x09 0x40 0x67...

...bps) pwr=ON (50mA) > [...] > bLength = 0x09 > bDescriptorType = 0x21 > bDescriptorSubType = 0x10 > RAW dump: > 0x00 | 0x09, 0x21, 0x10, 0x01, 0x21, 0x01, 0x22, 0x90, > 0x08 | 0x02 This looks reasonable. What about this? usbconfig -u 4 -a 2 do_request 0x81 0x06 0x2200 0 0x100 One thing I noticed about the report descriptor that NUT returned: it has extra zero bytes. For instance, these lines: 0.157417 Report Descriptor: (656 bytes) => 05 00 84 00 09 00 04 00 a1 00 01 00 09 00 0.157431 24 00 a1 00 00 00 85 00 01 00 09 00 fe 00 75 00...

...may have better luck using a different system running the NUT driver, such as a Raspberry Pi or Beaglebone Black, as ARM boards seem less affected (but not 100% reliable) with 3016 devices. Can you try the following commands as root? usbconfig -u 1 -a 3 dump_curr_config_desc usbconfig -u 1 -a 3 do_request 0x81 0x06 0x2200 0 0x100 (The "-u" and "-a" options are based on the /dev/ugen1.3 line above - adjust the numbers as appropriate after unplugging and re-plugging the USB cable.) Since usbconfig is part of the base FreeBSD distribution, and not part of NUT, this should identify...

...ptor: Input/output error My other concern is that FreeBSD might not allow the method that we use to retrieve the Report Descriptor. What do the following commands return (need to run them as root)? usbconfig -u 0 -a 5 dump_device_desc usbconfig -u 0 -a 5 dump_curr_config_desc usbconfig -u 0 -a 5 do_request 0x81 0x06 0x2200 0 0x100 (I'm guessing on "-u 0 -a 5" based on .../dev/ugen0.5 -- that might change if the UPS USB cable is unplugged and re-inserted.) > cat /var/etc/ups.conf > [upstl1300] > driver = usbhid-ups > port = auto > pollfreq = 30 &g...

...point 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0081 <IN> bmAttributes = 0x0003 <INTERRUPT> wMaxPacketSize = 0x0008 bInterval = 0x000c bRefresh = 0x0000 bSynchAddress = 0x0000 # usbconfig -u 1 -a 3 do_request 0x81 0x06 0x2200 0 0x100 REQUEST = <ERROR> On Mon, Aug 20, 2018 at 3:39 PM, Charles Lepple <clepple at gmail.com> wrote: > On Aug 20, 2018, at 7:40 AM, Valentin Merkulov <schnobel at ickis.net> wrote: >> >> Attached are config.log and usbhid-ups output with -u root...

...ptor: Input/output error My other concern is that FreeBSD might not allow the method that we use to retrieve the Report Descriptor. What do the following commands return (need to run them as root)? usbconfig -u 0 -a 5 dump_device_desc usbconfig -u 0 -a 5 dump_curr_config_desc usbconfig -u 0 -a 5 do_request 0x81 0x06 0x2200 0 0x100 (I'm guessing on "-u 0 -a 5" based on .../dev/ugen0.5 -- that might change if the UPS USB cable is unplugged and re-inserted.) > cat /var/etc/ups.conf > [upstl1300] >? ? ? ? driver = usbhid-ups >? ? ? ? port = auto >? ? ? ? pollfreq = 30 >?...

...36] :have_baby : forked child: 1938 saslauthd[1936] :have_baby : forked child: 1939 saslauthd[1936] :have_baby : forked child: 1941 saslauthd[1937] :do_auth : auth failure: [user=testomat at mail] [service=smtp] [realm=mail] [mech=shadow] [reason=Unknown] saslauthd[1937] :do_request : response: NO output in /var/log/messages: Aug 26 07:41:31 x02-new saslauthd[1673]: server_exit : master exited: 0 Aug 26 07:41:33 x02-new saslauthd[1936]: detach_tty : master pid is: 0 Aug 26 07:41:33 x02-new saslauthd[1936]: ipc_init : listening on socket: /var/run/saslau...