similar to: Prescription Fedex Tracking Number

I''ve been using the Business::FedEx::DirectConnect perl module to track and ship packages via FedEx for awhile now. I''m wanting to convert some of this functionality over to ROR, mostly just the package tracking part. Has anyone successfully tracked a package using the Shipping API out on RubyForge? It seems like the functionality is there since it''s just another

I working on an existing code base for a client. The app is built in rails 2.3 and uses the fedex plugin. Now i have develop a functionality for shipping the goods using *international priority* service type, the problem i''m facing is when ever i make a call to the fedex api for a shipping label it returns an error "Fedex::FedexError: Unable to get label from Fedex: Customs

Dear klibc at zytor.com, We attempted to deliver your package on March 29th, 2016, 09:00 AM. The delivery attempt failed because the address was business closed or nobody could sign for it. To pick up the package,please, print the receipt that is attached to this email and visit Fedex office indicated in the receipt. If the package is not picked up within 24 hours, it will be returned to

--k1lZvvs/B4yU6o8G Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi! It is my duty to inform you about this very unfortunate security issue in the IRC DCC connection tracking code. The following mail has just been sent to bugtraq, Linux Vendors have been informed two weeks in advance in order to prepare their advisories.

There has been a TODO waiting for quite a long time in drm_dp_mst_topology.c: /* We cannot rely on port->vcpi.num_slots to update * topology_state->avail_slots as the port may not exist if the parent * branch device was unplugged. This should be fixed by tracking * per-port slot allocation in drm_dp_mst_topology_state instead of * depending on the caller to tell us how many slots

On Wed, 2018-11-07 at 21:59 +0100, Daniel Vetter wrote: > On Tue, Nov 06, 2018 at 08:21:14PM -0500, Lyude Paul wrote: > > There has been a TODO waiting for quite a long time in > > drm_dp_mst_topology.c: > > > > /* We cannot rely on port->vcpi.num_slots to update > > * topology_state->avail_slots as the port may not exist if the parent > > *

There has been a TODO waiting for quite a long time in drm_dp_mst_topology.c: /* We cannot rely on port->vcpi.num_slots to update * topology_state->avail_slots as the port may not exist if the parent * branch device was unplugged. This should be fixed by tracking * per-port slot allocation in drm_dp_mst_topology_state instead of * depending on the caller to tell us how many slots

There has been a TODO waiting for quite a long time in drm_dp_mst_topology.c: /* We cannot rely on port->vcpi.num_slots to update * topology_state->avail_slots as the port may not exist if the parent * branch device was unplugged. This should be fixed by tracking * per-port slot allocation in drm_dp_mst_topology_state instead of * depending on the caller to tell us how many slots

On Wed, Nov 07, 2018 at 04:39:57PM -0500, Lyude Paul wrote: > On Wed, 2018-11-07 at 16:23 -0500, Lyude Paul wrote: > > On Wed, 2018-11-07 at 21:59 +0100, Daniel Vetter wrote: > > > On Tue, Nov 06, 2018 at 08:21:14PM -0500, Lyude Paul wrote: > > > > There has been a TODO waiting for quite a long time in > > > > drm_dp_mst_topology.c: > > > >

Hi Adrian, > quite a lot of work Large amounts of credit should go to llvm-reduce, which was fundamental to getting any of this done, > I've skimmed your implementation and it looks nice and well-documented. The thing that worries me is the over-complicated lattices -- I didn't anticipate the problem, and there's a risk that it's more complex than it needs to be. As it

Hi, This is a summary of what was discussed at the Performance Tracking and Benchmarking Infrastructure BoF session last week at the LLVM dev meeting. At the same time it contains a proposal on a few next steps to improve the setup and use of buildbots to track performance changes in code generated by LLVM. The buildbots currently are very valuable in detecting correctness

Hello, I''m interested in learning what folks in the Rails community do when they need to generate permanent unique numbers for tracking objects such as packing slips, inventory items, customers, employees, etc. It''s tempting to use the autogenerated id, but they''re not pretty enough for human consumption and it can be problematic having assigned ids if tables ever need

There has been a TODO waiting for quite a long time in drm_dp_mst_topology.c: /* We cannot rely on port->vcpi.num_slots to update * topology_state->avail_slots as the port may not exist if the parent * branch device was unplugged. This should be fixed by tracking * per-port slot allocation in drm_dp_mst_topology_state instead of * depending on the caller to tell us how many slots

There has been a TODO waiting for quite a long time in drm_dp_mst_topology.c: /* We cannot rely on port->vcpi.num_slots to update * topology_state->avail_slots as the port may not exist if the parent * branch device was unplugged. This should be fixed by tracking * per-port slot allocation in drm_dp_mst_topology_state instead of * depending on the caller to tell us how many slots

Hello, This is a more detailed overview of my progress than the weekly reports, which can also be found on the mailing list. Over the past two weeks I have been learning a lot more about capture tracking. From this I was able to instrument the current implementation in order to identify some of the false positives in it. I was hoping to have more definitive results by now than what I

There has been a TODO waiting for quite a long time in drm_dp_mst_topology.c: /* We cannot rely on port->vcpi.num_slots to update * topology_state->avail_slots as the port may not exist if the parent * branch device was unplugged. This should be fixed by tracking * per-port slot allocation in drm_dp_mst_topology_state instead of * depending on the caller to tell us how many slots

--yrj/dFKFPuw6o+aM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi! Today the netfilter core team announces the new bug-tracking system for netfilter/iptables. This step really was necessarry, because I started to get the feeling that I'm losing track of all the concurrent issues. So if you are aware of any bugs in the

Thank you, I tried to compile it with llvm 3.4 through these commands: petsas at shinigami:~/software/poolalloc$ ./configure --with-llvmsrc=/home/petsas/software/llvm --with-llvmobj=/home/petsas/software/llvm petsas at shinigami:~/software/poolalloc$ make but I'm getting get this error: make[1]: Entering directory `/home/petsas/software/poolalloc/lib' make[2]: Entering directory

Somebody please forward this, if this is not an appropiate place to ask the OpenSSH developers for a new feature. As many of us have seen, any sshd left open on the internet eventually becomes the target of password guessing attacks. I am aware of tools for scanning the security logs, and manipulating iptables to block ongoing attacks, but I am not aware of a way to configure sshd itself to

I'm trying to configure the dovecot statistics tracking option with Dovecot 2.1.12 on FreeBSD 9.1-RELEASE. I've seen on the wiki page the configuration settings needed for this but it does not say which configuration file these settings should be added to. http://wiki2.dovecot.org/Statistics I was hoping someone could tell me which file these settings should be added to? Do they all