!Friendica Support
I had my first-ever server crash of my-place.social. This is in syslog:

2024-11-18T21:34:49.022603-05:00 my-place php: PHP Fatal error: Uncaught mysqli_sql_exception: Too many connections in /var/www/html/src/Database/Database.php:201
2024-11-18T21:34:49.022822-05:00 my-place php: Stack trace:
2024-11-18T21:34:49.022855-05:00 my-place php: #0 /var/www/html/src/Database/Database.php(201): mysqli->__construct()
2024-11-18T21:34:49.022885-05:00 my-place php: #1 /var/www/html/src/Database/Database.php(106): Friendica\Database\Database->connect()
2024-11-18T21:34:49.022911-05:00 my-place php: #2 [internal function]: Friendica\Database\Database->__construct()
2024-11-18T21:34:49.022933-05:00 my-place php: #3 /var/www/html/vendor/level-2/dice/Dice.php(132): ReflectionMethod->invokeArgs()
2024-11-18T21:34:49.022958-05:00 my-place php: #4 /var/www/html/vendor/level-2/dice/Dice.php(96): Dice\Dice->Dice\{closure}()
2024-11-18T21:34:49.022985-05:00 my-place php: #5 /var/www/html/vendor/level-2/dice/Dice.php(247): Dice\Dice->create()
2024-11-18T21:34:49.023014-05:00 my-place php: #6 /var/www/html/vendor/level-2/dice/Dice.php(132): Dice\Dice->Dice\{closure}()
2024-11-18T21:34:49.023049-05:00 my-place php: #7 /var/www/html/vendor/level-2/dice/Dice.php(96): Dice\Dice->Dice\{closure}()
2024-11-18T21:34:49.023074-05:00 my-place php: #8 /var/www/html/vendor/level-2/dice/Dice.php(247): Dice\Dice->create()
2024-11-18T21:34:49.023100-05:00 my-place php: #9 /var/www/html/vendor/level-2/dice/Dice.php(132): Dice\Dice->Dice\{closure}()
2024-11-18T21:34:49.023125-05:00 my-place php: #10 /var/www/html/vendor/level-2/dice/Dice.php(96): Dice\Dice->Dice\{closure}()
2024-11-18T21:34:49.023147-05:00 my-place php: #11 /var/www/html/index.php(34): Dice\Dice->create()
2024-11-18T21:34:49.023172-05:00 my-place php: #12 {main}
2024-11-18T21:34:49.023208-05:00 my-place php: thrown in /var/www/html/src/Database/Database.php on line 201

show variables like 'max_connections'; shows 151 max_connections.

I did: SET GLOBAL max_connections = 200;

I also edited /etc/mysql/mariadb.conf.d/50-server.cnf and set max_connections = 200

Is this too high? Too low? Did I do this the correct way?

Thank you!

Thanks!

Leaving now to go see --

#1882, or #390, 2024's "Juror #2."

But I never saw "Juror #1"!

The Apollo 13 mishap was caused by an explosion in oxygen tank #2 in the service module.

The O2 tanks had been redesigned to use 65V instead of 28V, but the heater thermostatic switches got overlooked.

During ground testing, the switches malfunctioned causing temp to rise and damage the teflon insulation on the wires to the fans.

On April 13, the fans were turned on for a "cryo-stir". The fan wires shorted, the teflon insulation caught fire, the O2 tank exploded.

nssdc.gsfc.nasa.gov/planetary/…
2/n

New error message (of FRIO) about a folder created by the user root.

I haven't found the extensive conversation about this problem with @Hypolite Petovan yet but I'm quite sure that I changed all folders to ownership of user www-data before 28th of November of the smarty folder. Actually there was another conversation about ownership of folders and I changed all folders to be owned by root except storage and view that day on 02:45hs, the new folder owned by root at /view/smarty3/compiled/ like stated below was created on 3:50hs.

As for what I remember of all the conversations this shouldn't have happened.

<?php
/* Smarty version 4.3.1, created on 2023-11-28 03:50:02
  from '7cd2693513597460a71347ba02d3179c5e5ab822' */
/* @var Smarty_Internal_Template $_smarty_tpl */
if ($_smarty_tpl->_decodeProperties($_smarty_tpl, array (
  'version' => '4.3.1',
  'unifunc' => 'content_6565636a645732_50647552',
  'has_nocache_code' => false,
  'file_dependency' => 
  array (
  ),
  'includes' => 
  array (
  ),
),false)) {
function content_6565636a645732_50647552 (Smarty_Internal_Template $_smarty_tpl) {
?>[url=https://tupambae.org/profile/utopiarte]utopiArte[/url] replied to you on [url=https://tupambae.org/display/0ac89072-1065-6562-6405-8bb240314547]"bugreport - can't answer, like or reshare posts"[/url]<?p>

tupambae.org/admin/themes/frio

Service Unavailable
unable to create directory /var/www/html/view/smarty3/compiled/90/4f/52

Exception thrown in /var/www/html/src/Core/Renderer.php:90
Stack trace:
#0 /var/www/html/view/theme/frio/config.php(199): Friendica\Core\Renderer::replaceMacros()
#1 /var/www/html/view/theme/frio/config.php(141): frio_form()
#2 /var/www/html/src/Module/Admin/Themes/Embed.php(89): theme_admin()
#3 /var/www/html/src/BaseModule.php(244): Friendica\Module\Admin\Themes\Embed->content()
#4 /var/www/html/src/App.php(703): Friendica\BaseModule->run()
#5 /var/www/html/index.php(52): Friendica\App->runFrontend()
#6 {main}

@Hypolite Petovan
Ok fixed that

Executable: /home/anubis2814/mywebsite/bin/console.php
Arguments: array (
0 => 'autoinstall',
)
Options: array (
'v' => 1,
)
Command: autoinstall
Initializing setup...
Complete!

Checking environment...
NOTICE: Not checking .htaccess/URL-Rewrite during CLI installation.

[Error] --------
GNU Multiple Precision PHP module: Error: GNU Multiple Precision PHP module required but not installed.

[Backtrace]:
#0 /home/anubis2814/mywebsite/vendor/asika/simple-console/src/Console.php(108): Friendica\Console\AutomaticInstallation->doExecute()
#1 /home/anubis2814/mywebsite/src/Core/Console.php(163): Asika\SimpleConsole\Console->execute()
#2 /home/anubis2814/mywebsite/vendor/asika/simple-console/src/Console.php(108): Friendica\Core\Console->doExecute()
#3 /home/anubis2814/mywebsite/bin/console.php(41): Asika\SimpleConsole\Console->execute()
#4 {main}
Is this error an issue?

!Friendica Support
wiki.friendi.ca/docs/install
So I am stuck at the create a database point. I can't tell if they just told me, create a database without telling me how or if this helped create a database. I went with B and here were the resutls. Are there peices missing or are these warnings ok for the system we are using?

$ bin/console autoinstall -v
PHP Warning: Module "curl" is already loaded in Unknown on line 0
PHP Warning: Module "gd" is already loaded in Unknown on line 0
PHP Warning: Module "mbstring" is already loaded in Unknown on line 0
Executable: /home/anubis2814/mywebsite/bin/console.php
Arguments: array (
0 => 'autoinstall',
)
Options: array (
'v' => 1,
)
Command: autoinstall
Initializing setup...
PHP Warning: Module "curl" is already loaded in Unknown on line 0
PHP Warning: Module "gd" is already loaded in Unknown on line 0
PHP Warning: Module "mbstring" is already loaded in Unknown on line 0
PHP Warning: Module "curl" is already loaded in Unknown on line 0
PHP Warning: Module "gd" is already loaded in Unknown on line 0
PHP Warning: Module "mbstring" is already loaded in Unknown on line 0
Complete!

Checking environment...
PHP Warning: Module "curl" is already loaded in Unknown on line 0
PHP Warning: Module "gd" is already loaded in Unknown on line 0
PHP Warning: Module "mbstring" is already loaded in Unknown on line 0
PHP Warning: Module "curl" is already loaded in Unknown on line 0
PHP Warning: Module "gd" is already loaded in Unknown on line 0
PHP Warning: Module "mbstring" is already loaded in Unknown on line 0
NOTICE: Not checking .htaccess/URL-Rewrite during CLI installation.

[Error] --------
GNU Multiple Precision PHP module: Error: GNU Multiple Precision PHP module required but not installed.

[Backtrace]:
#0 /home/anubis2814/mywebsite/vendor/asika/simple-console/src/Console.php(108): Friendica\Console\AutomaticInstallation->doExecute()
#1 /home/anubis2814/mywebsite/src/Core/Console.php(163): Asika\SimpleConsole\Console->execute()
#2 /home/anubis2814/mywebsite/vendor/asika/simple-console/src/Console.php(108): Friendica\Core\Console->doExecute()
#3 /home/anubis2814/mywebsite/bin/console.php(41): Asika\SimpleConsole\Console->execute()
#4 {main}

The paper's next move is to link 3 proposals from 2022, 2021, and 2015 about how to use C++ for type and resource safety, and then the C++ Core Guidelines themselves.

• 2022
• 2021
• 2015

Speed-summary.

2022

The 2022 paper lays out a bunch of alternatives and then goes all-in on the Core Guidelines as THE solution. "Just develop the checkers more, slap then on top of existing code and keep using the compatibility story to push what C++ is in more places". It's built around this idea.

It mentions other ways of maintaining type safety, but it boils down to "use the RAII we have and combine it with lots of core guidelines to get what we want". I mean, RAII is wonderful, and that's fair, but you know. Again.

Existence proof of Google's work makes it a little less palatable to think this'll do the trick completely.

2021

This one very explicitly tries to lay out some rules for protecting programmers. But, a lot of the advice is simply just straight up unactionable for the way C++ is written today, meaning it's likely geared towards people doing things today to write new code without lots of refactoring. For example, Rule #2 from this paper is

Every object is accessed according to the type with which it was defined.

The language guarantees this except for preventable pointer misuses (see §4, §5), explicit casts, and type punning using unions. The CG have specific rules to enforce these language rules.

Static analysis can prevent unsafe casting and unsafe uses of unions. Type-safe alternatives to unions, such as std::variant, are available. Casting is essential only for converting untyped data (bytes) into
typed objects.

This is a pretty sensible rule until you start doing things in more complicated code bases or interfacing with C, where the name of the game is committing crimes with pointers -- void* or otherwise -- to get things done. Type-punning is common, and std::variant only showed up in C++17 (much like std::string_view also showing up 10 years late by being introduced in C++17, also with a hamstringed std::optional type -- see here for my usual rant on that).

It also flies in the face of the whole "we take advantage of code that exists", because doing that means you need to interface with C++03, C++11, and C89 to C17 code. All of that is raw pointers and crimes, especially since until C++11 there was no move semantics, so if the whole point -- as these papers and the overarching paper points out -- is to keep compat alive and use old code, then you're going to have to keep working with a grafted up monster.

2015

This is actually the best paper because it uses lots of examples to explain some serious problems with C and C++ code. It walks people through introducing RAII types for safety to prevent use-after-free, double-free, and other large classes of problems. It still shills for the Core Guidelines eventually, but at least it's trying to help. But, again, it offers it in the context if migrating old code to new styles and idioms; but, at the same time, the tension of "you can keep using your old code" keeps rising up. So either we're all using old code or we're rewriting it to use the new stuff, which means that for all the compatibility we have we're still rewriting large chunks of code to defend against bugs instead of just writing the code we want to write to make progress.

This is a consistent theme for this paper and many C++ papers; "compatibility is important", is what they keep saying, while deeply implying that old code needs new tools to be rewritten in and transition paths must happen. At some point, I need to stop fucking with Old and Busted But Occasionally Reliable and start working on the New Hotness, so we end up with a Lovecraftian monstrosity as a matter-of-fact in most long-lived C++ codebases.

Damned if you do, damned if you don't I guess?

To Bind and Loose a Reference

… Let’s talk about something that has haunted me for over a year now.

^{The Pasture}

@Friendica Support I want to delete a post which was accidentially saved to a folder. How to do it? Only thing I see is a pop-up saying that I will be deleting the post, but no button or anything else to be clicked. See screenshots: #1 Firefox on Android, #2 Firefox on Windows.

TIA

@Fabio -- kudos!

Thanks to you, I learned today how to:

1. From my cron table retrieve the username: friendica

2. From /var/www/friendica find out out ownership and mode: friendica:www-data 0750

3. In /var/www/friendica create log/friendica.log

4. Apply details from #2 to the directory I created for media files

And now the storage switch went without any glitches.

root@tepewu:/home/yunohost.multimedia/petroskowo# ls
0c  2a  37  41  4d  61  71  8c  bf  d5  f6
0e  2e  3a  42  57  62  73  93  c8  e3  ff
29  33  3e  4b  60  6d  79  94  c9  e9  index.html

Thank you for your support.

!Friendica Support

Hello!

My system runs on an Raspberry Pi3, Debian 11

Since the upgrade to Friendica 2022.10 adding new contacts in mastodon shows me an error-code.

Exception thrown in /var/www/html/src/ModuleContact/Profile.php:141
Stack trace:
#0 /var/www/html/src/BaseModule.php(244): Friendica\Module\Contact\Profile->con>
#1 /var/www/html/src/App.php(719): Friendica\BaseModule->run()
#2 /var/www/html/index.php(44): Friendica\App->runFrontend()
#3 {main}

I have Friendica debug logs for times around the contact-attempt, but there isn't even shown the contacts-profile-url (but those of many others, i'm not in contact with).

Afterwards, the contact is added as RSS.

--

Adding a new a.gup.pe membership ends up with error messages on screen

Network type can't be detected, contact can't be added.
Profile-url doesn't give proper information, no compatible protocolls for communication oder feeds can be found.

Here i also can't find anything related in the logs.

Does anyone has similar issues?