Stuck together glass in porcelain

I currently have a glass stuck in a porcelain. I have already setup cold water in top glass and hot (boiling, I'm careful) around lower but still they remain stuck. Plus I added salt in upper (cold) glass. I got this (last) idea from a #youtube video with ID #HOglOnne3As which seems quite straight-forward but still no success here.

Any ideas? I cannot currently upload images, size limit of 780k exceeded but I set $a->config['system']['maximagesize'] = 2*1024*1024; which should be enough, right?

Strange #bug in #Friendica ... So you have to live with a link to my #nextcloud instance: https://cloud.mxchange.org/s/rnFtrpbQqAXx8O1
#youtube #HOglOnne3As #bug #Friendica #nextcloud glass household porcelain problem
It is finally separated, luck with us. :-)
@Steffen K9 ???? das mit dem Hammer brauche ich zum Glueck nicht. Die Glaeser sind gluecklich voneinander getrennt. ;-)

Why I don't like payed support #2

I currently face a #bug in #Payara that doesn't allow TABLE_PER_CLASS and I cannot change the database layout (as then the main program needs to be changed which involves a lot risky work).

I have filled out a bug report ...

... But they don't want to handle it. I guess I'm not alone with this bug. I don't like such "payment model" where paying customers are priotized. I for my projects provide unpriotized support for any one, unpayed and in my free time: My View - Mailer-Project Bug-Tracker
What do you think about such payment models? Good or bad?

2nd submit: better preview before test.
#bug #Payara payara payed support
The case is closed, maybe someone else will pick it up? !java

The class does not have a descriptor, or a descriptor that does not use inheritance or uses a ClassExtractor for inheritance

The mentioned message still comes when you have @Inheritance (strategy = InheritanceType.TABLE_PER_CLASS) in your abstract (not-persisted) with latest version of #Payara / #Glassfish which both contains #EclipseLink by default.

Strange that they did not yet fix it. And unfortunally migrating to e.g. #WilfFly (which uses other #JPA) seems not so easy as you may think.

Currently I have no idea how to fix it and sadly I need the strategy as this #JavaEE application is written for an existing database layout.

Someone may have to raise a support ticket mentioning that the #bug is still there.

Reposted with #public visibility. Sorry for double message.
#Payara #Glassfish #EclipseLink #WilfFly #JPA) #JavaEE #bug #public bug eclipselink javaee jpa payara
Nothing new here so far. Only they asked me to write a test-case for them ... :-(

Local "connect" not working

I think I found a #bug in #friendica, latest develop code. I have rebased my branch to latest changes and revert all of my is_filled_array() changes to dba::is_result().

So what I did was I created an account for my wife and tried to connect to but all I got was a redirect and no entry in table 'intro'. There is also no entry of her account in 'fcontact'.

So what is wrong?
#bug #friendica bug develop friendica
Ah, validate_url() misses to check $h with is_array(). Please try to cherry-pick my latest commits in branch rhaeder-develop (changed develop branch).
Ah, validate_url() misses to check $h with is_array(). Please try to cherry-pick my latest commits in branch rhaeder-develop (changed develop branch).
Later posts Earlier posts