topic Re: [8.3.1] Managed library import failed in EAGLE Forum

[8.3.1] Managed library import failed

Anonymous — Fri, 18 Aug 2017 00:39:28 GMT

I converted a local library to a managed library, added some 3d models, synced everything back and forth to circuits.io and fusion, that all went great. (this was under 8.3.0)

Then I imported a device from a different (unmanaged) library into the managed one, and tried making a new version by selecting `create new version` (in eagle). Opens a process bar window and then hangs quite some time at `Processing library...` and then fails with `managed library import failed`. This happened under 8.3.0 and 8.3.1. After removing the imported device the situation stays the same.

Any way around this?

Re: [8.3.1] Managed library import failed

jorge_garcia — Tue, 29 Aug 2017 22:49:50 GMT

Hello Jelmer,

I'm looking into this one, sorry for the delay. A few fixes have been made to the circuits.io and EAGLE/Fusion workflow in the last few days so I would suggest trying again.

Please let me know if there's anything else I can do for you.

Best Regards,

Re: [8.3.1] Managed library import failed

colin_taylor — Wed, 30 Aug 2017 17:10:14 GMT

Hi Jelmer,

As Jorge said we have implemented quite a few fixes for the process of managing libraries. If you have the URN of your library I can explicitly take a look at to make sure your library is being managed correctly. If you haven't tried in a few days I would retry the library to see if the problem was fixed, hopefully it is!

Thanks for your patience.

Re: [8.3.1] Managed library import failed

Anonymous — Wed, 30 Aug 2017 17:37:49 GMT

Hi Colin,

Tried again today, but still having the exact same problem. urn:adsk:eagle:library:183461

Re: [8.3.1] Managed library import failed

colin_taylor — Wed, 30 Aug 2017 21:10:52 GMT

Hi Jelmer,

Is it possible to separate your logos into a different library? These logos can sometimes be broken down into thousands of rectangles which is not a very efficient for the web side of things, but its how Eagle works. To check to see if a new version of a certain asset, like a footprint, needs a new version we must compare the old footprint to the new one being uploaded. This can become costly with thousands of rectangles, which is causing it to take longer then our timeout is set for so the library fails. This explains why it succeeded the first time, and not any other times. I know moving your logos is not ideal, but I'm not sure when we'll have an ideal solution available. I was able to successfully get your import to work by extending the timeout, but its not safe on a larger scale. So if you check the library on the site it should be accessible again. Sorry for the inconvenience.

Re: [8.3.1] Managed library import failed

Anonymous — Thu, 31 Aug 2017 02:46:24 GMT

Thanks for looking into this Colin, this explains a lot. I'll move out the logos.

Storing (silkscreen) graphics as a footprint, which results in a very high number of rectangles, is indeed not great for file size and (CAM) processing time. Not only on web, but I also have the feeling this doesn't work great in Eagle itself.

So, together with this error can I put in a feature request: native support for (importing, exporting and basic editing of) svg, dxf, png, ... 😉

Thanks again