chennes wrote: ↑Tue Mar 02, 2021 4:06 pm
Well, things continue to proceed with my ticket - they had some more (simple) changes to request, but on their end have been proactively working on getting the patch to pass their regression tests.
Good news! Looks like the ticket has changed to 'verified'. In the OCCT bugtracker that means it's ready to be in the next release (7.6.0).
chennes wrote: ↑Wed Mar 17, 2021 5:43 pm
Excellent, that's one less patch to maintain -- they also made a good change to it that will allow some currently-failing fillets to work again.
Yes! This is a great achievement. Would you be willing to take aim at any other upstream tickets (listed in the OP) so we can set those in motion?
It's hard for me to find time to do these because I can't do OpenCASCADE stuff at work (due to the CLA). Also, the reality is that I don't know enough to be useful -- this patch was purely C++/error handling, with no OCCT knowledge required.
Hi @greyltc, I'm pinging you to find out if you'd be interested in helping move some of these tickets (reported upstream and unreported) tickets. Since you've had some success recently with https://tracker.dev.opencascade.org/view.php?id=32264 (issue #4610)
I see that the OCCT bug for our issue #1840 is still open, but I just tested on OCCT 7.5.1 (with the blobfish patches) and could not reproduce any longer. Can someone else double-check this one as well?