Subclasses being sliced when stored in a vector of ptrs

Having a bit of a problem where my subclasses are getting sliced to the size of their parent. It works fine if you serialise the subclass as is, but as soon as you're storing ptrs to them, it doesn't seem to serialise any further than the base class. I'm assuming this is because it can't identify the type at runtime.
I also tried registering the relationships explicitly but that didn't seem to make a difference either.
Here's some code which replicates the problem I'm having: https://gist.github.com/NotAdam/c72631584e542a51ae4cae71534b3b43
Here's the file that gets produced by the code above:

which has no data after what's defined in the base class.
I'm assuming I'm missing dumb something here, but I haven't had any luck getting it to work yet.

So I've managed to get it working again after reading the documentation properly (lol), working code:
struct SceneObject
{
  SceneObjectType type{ None };

  std::string name;

  virtual ~SceneObject() = default;

  template< class Archive >
  void serialize( Archive& ar )
  {
    ar( type, name );
  }
};

struct TestSceneObject :
  public SceneObject
{
  std::string eventName;
  int test;

  template< class Archive >
  void serialize( Archive& ar )
  {
    ar(
      cereal::base_class< SceneObject >( this ),
      eventName,
      test
    );
  }
};

CEREAL_REGISTER_TYPE( TestSceneObject );

However, the type of the object is set as a member of the object instead as this simplifies how we handle each object type, so I'm curious if we're able to serialise each subclass just using that type field instead. it's also kind of wasteful too because the type name is repeated for each instance in the binary file
I tried doing something like this:
struct SceneGroup
{
  std::string name;
  std::vector< std::shared_ptr< SceneObject > > objects;

  template< class Archive >
  void serialize( Archive& ar )
  {
    ar( name );

    for( auto& obj : objects )
    {
      switch( obj->type )
      {
        default:
          ar( obj );
          break;

        case Test:
          ar( std::reinterpret_pointer_cast< TestSceneObject >( obj ) );
          break;
      }
    }
  }
};

however these are then serialised as isolated instances rather than being a entry in the vector, which then doesn't serialise properly in json either. Subsequently, this then can't deserialise afterwards.

I managed to get this working by pretty much reimplementing the vector serialisation and writing the type before each actual data object and using that to know what to read next which works pretty well.
Hope this is useful for anyone else who wants to do inheritance for objects without RTTI
template< class Archive, class A >
inline
void CEREAL_LOAD_FUNCTION_NAME( Archive& ar, std::vector< std::shared_ptr< SceneObject >, A >& vector )
{
  size_type size;
  ar( make_size_tag( size ) );
  vector.resize( static_cast< std::size_t >( size ) );

  for( size_type i = 0; i < size; ++i )
  {
    SceneObjectType type;
    ar( type );

    switch( type )
    {
      default:
      {
        vector[i] = std::move( readType< Archive, SceneObject >( ar ) );
        break;
      }

      case Test:
      {
        vector[i] = std::move( readType< Archive, TestSceneObject >( ar ) );
        break;
      }
    }
  }
}

Can make it a bit nicer with macros so you don't have to manage each save/load func, but this is pretty nice and then you don't need to have all your save/load code inside your data structures.


Add CONTRIBUTING.md

Looking at https://gist.github.com/PurpleBooth/b24679402957c63ec426 (although most of that is a CoC and I already have a separate CoC already) and https://github.com/django/django/blob/main/CONTRIBUTING.rst (although that links to a lot of other docs about how to contribute to Django).
@mihrab34 Do you have an example CONTRIBUTING file that you seen in the past and liked?

@adamghill I liked this one Async API uses for their projects https://github.com/asyncapi/.github/blob/master/CONTRIBUTING.md

THis got merged in, so closing this.


[Question] How can I consume message again?

I have a system where I don't commit until the consumed message successfully transferred to other service. But consumer locally stores info that I already consumed the message and tries to consume next one.
How can I clear this info and start from the last committed state? Is there some better way than closing current consumer and creating new with same config?

[ 1.0.0 ] Confluent.Kafka nuget version.
[ Windows 10  .NET Framework 4.7.2 ] Operating system.

you can use Consumer.Seek

Can you provide code sample for how I can use Consumer.Seek in already built consumer?
            var config = new ConsumerConfig {
                ClientId = _clientId,
                GroupId = _groupId,
                BootstrapServers = $"{_address}:{_port}",
                AutoOffsetReset = AutoOffsetReset.Earliest,
                EnableAutoCommit = !_waitForTransfer, };

            var _confluentConsumer = new ConsumerBuilder<Ignore, string>(conf).Build();

            _confluentConsumer.Subscribe(_topic);

            var _cancelationToken = new CancellationTokenSource();

            var cr = _confluentConsumer.Consume(_cancelationToken.Token);
                if (!cr.IsPartitionEOF)
                {
                    foreach (var callback in _callbacks)
                    {
                        callback(new CallbackParams(cr));
                    }
                }
            }

For example after callback() I may need to re-consume again.

Also. For some reason when I recreate new consumer the same way I created previous one, assignment is empty. That's definitely not expected behavior, what can be the reason of it?

you can use Consumer.Seek

@mhowlett can you, please, tell if this code sample is the correct way to go? How can I do it for more than 1 assignment? (I don't know if it can ever happen)
var currentTopicPartition = consumer.Assignment.First();
consumer.Seek(new TopicPartitionOffset(currentTopicPartition, consumer.Position(currentTopicPartition) - 1));


Fix: convert content tabs with code blocks into plain text. Closes #3912

Closes #3912

Thanks for the quick PR @dgreuel! We'll review it ASAP.

Hey @dgreuel, looks like a test failed. Could you take a look at it? If it's a bit confusing you can always ask for help 😄

Merged manually. Thank you! 👏


bugfix: filename wrong in error log when get cpuinfo

Filename wrong in error.log in function ngx_getcpuinfo, it should be NGX_CPUINFO_FILE, not NGX_MEMINFO_FILE.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Due to copying the code, the log print uses the wrong file name, thanks for contributing the code.


Update f5_pool monitor_association to support hash

Add stricter attribute value munging to ensure correct input.
Add support for empty {} to simply remove monitoring.
Update documentation to reflect resource changes.

Input of quorum, type, monitor_templates need validation and sane errors.


Error: When choosing a skill from a class, the standard abilities will be replaced with dexterity

When choosing a skill from a class, the standard abilities will be replaced with dexterity.

Can confirm, and add to it.  Any skill chosen during the builder, including from Backgrounds, does this.  See screenshot.
Foundry: 10.291
D&D5E: 2.1.5
Builder: 1.9.2
Midi: 10.0.35

Oops! I will look into it asap!

Any update on this or beta version needing tested?  It's driving me even more bonkers than I already am. :) Thank you!

Hi! Sorry, not yet, unfortunally real life took a reign of my free time these past few weeks, but I will update as soon as I can get a hold on this!

FYI, 1.9.1 does not have this issue.  I cannot figure out why either, I went through the changes github shows and non of them make sense to have caused this.  I just wanted to let you know, in case this helps with your testing to fix it. (When you get time, IRL is a pain some times).

This bug goes all the way back to 1.9.0 (looks like first official v10 release).  All modules disabled except for your module.  I cannot check 1.8.3 as I do not have V9. I have even tried different combinations of dnd5e releases.  Same result. skill proficiency shows dex.

Ok, I just found out this is an issue coming from the system: https://github.com/foundryvtt/dnd5e/issues/2227
In any case, I have found where to work around it, and should be fixing it on the next release too.


Include user-agent for tracking usage

It would be great if the HTTP requests could specify the User-Agent header with something like "ccloud_metrics_source/<commit_version>" so Confluent Cloud can track usage of this connector against the API and help identify any issues with a particular version.

Done


[Bug Report] MacOS - Get permission error, and can't load previous game data after Docker restart. Please help

Have you read the Important information text above

[X] Yes i did

Current behavior
Permission errors occur in the game folder or its subdirectories when restarting Docker after shutdown.
Attempted to apply permissions using chmod 777 -R but received a message that the folder could not be found.
However, ls -l confirms that 777 permissions are in effect. It's unclear if this is the issue, but the server fails to load previous data upon restart.
Desired behavior
Server starts with no permission errors and load previous game play data.
Links to screenshots
No response
To Reproduce

Normal game operation
Stop Docker to terminate execution
Restart Docker and check logs
Permission error occurs
Server terminates abnormally
Copy Docker Compose YAML to another folder
Execute Docker in that folder
New server starts normally
Pause server
Overwrite with previously backed-up data (entire folder)
Resume
New player created on game start (fails to load existing data)
Stop Docker, delete container
Move to the previously used folder, delete all files, and paste the previously backed-up data
Server starts with permission error but fails to load existing data < Current situation

Software setup

OS: macOS 12.7.3 (21H1015)
Docker: 4.26.1 (131620)

Engine: 24.0.7
Compose: v2.23.3-desktop.2
Credential Helper: v0.7.0
Kubernetes: v1.28.2

Hardware setup

vCPU: Dual core Intel Core i5(Mac mini Late 2014)
RAM: 16 GB
Disk: 256GB (SSD)

Additional context
Hello, I'm a React Native developer with limited Docker experience. I understand that it might be difficult to comprehend or answer a question from a developer like me, and I hesitated to ask, but I find myself in a tough situation that I can't resolve on my own. (Note: I'm using software for translation, so the sentences might be a bit off. Please bear with me.)
Here's the issue:
I'm running a server using Docker on a MacMini late2014 (Ram 16GB) with MacOS. Initially, when I ran Docker using the provided Docker file, the server started without any issues, and I played games on it for about two days. Then I remembered that the game client had been updated and thought the server might need updating too.
An hour ago, I stopped Docker using the Stop button in the desktop app to update it. After restarting, I repeatedly received messages like "sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/seddc90fx'". Additionally, a system error occurred, causing the Docker container to shut down automatically.
So, I saved the backup files separately, deleted the Docker app and files on the Mac, and tried a fresh start, which seemed to work fine. However, errors seem to persist when I try to reload the backup files.
Initially, when I ran the "$ sudo chmod 777 -R game" command during setup, I received a message saying the folder couldn't be found. However, when I checked with the ls -l command, I confirmed that the game folder and its subfolders had 777 permissions, so it's hard for me to pinpoint the issue with my skills.
After several attempts, I confirmed that starting fresh with new local files, Docker files, and images seems to work fine. However, when I pasted the backed-up files - the folders created for running the game - back to their original location and restarted, the previous data did not load. I keep receiving permission error logs.
I would appreciate any help. Thank you.
Here is Docker log of current situation.
2024-01-28 14:32:02 palworld-dedicated-server  | >>> Checking for existence of default credentials
2024-01-28 14:32:02 palworld-dedicated-server  | >>> Doing an update of the gameserver
2024-01-28 14:32:03 palworld-dedicated-server  | time="2024-01-28T14:32:03+09:00" level=info msg="read crontab: cronlist"
2024-01-28 14:32:14 palworld-dedicated-server  | tid(13) burning pthread_key_t == 0 so we never use it
2024-01-28 14:32:14 palworld-dedicated-server  | Redirecting stderr to '/home/steam/Steam/logs/stderr.txt'
2024-01-28 14:32:14 palworld-dedicated-server  | Logging directory: '/home/steam/Steam/logs'
2024-01-28 14:32:14 palworld-dedicated-server  | [  0%] Checking for available updates...
2024-01-28 14:32:14 palworld-dedicated-server  | [----] Verifying installation...
2024-01-28 14:32:14 palworld-dedicated-server  | [  0%] Downloading update...
2024-01-28 14:32:14 palworld-dedicated-server  | [  0%] Checking for available updates...
2024-01-28 14:32:14 palworld-dedicated-server  | [----] Download complete.
2024-01-28 14:32:14 palworld-dedicated-server  | [----] Extracting package...
2024-01-28 14:32:14 palworld-dedicated-server  | [----] Extracting package...
2024-01-28 14:32:14 palworld-dedicated-server  | [----] Extracting package...
2024-01-28 14:32:14 palworld-dedicated-server  | [----] Extracting package...
2024-01-28 14:32:14 palworld-dedicated-server  | [----] Installing update...
2024-01-28 14:32:14 palworld-dedicated-server  | [----] Installing update...
2024-01-28 14:32:14 palworld-dedicated-server  | [----] Installing update...
2024-01-28 14:32:14 palworld-dedicated-server  | [----] Installing update...
2024-01-28 14:32:14 palworld-dedicated-server  | [----] Installing update...
2024-01-28 14:32:14 palworld-dedicated-server  | [----] Installing update...
2024-01-28 14:32:14 palworld-dedicated-server  | [----] Installing update...
2024-01-28 14:32:14 palworld-dedicated-server  | [----] Installing update...
2024-01-28 14:32:14 palworld-dedicated-server  | [----] Cleaning up...
2024-01-28 14:32:14 palworld-dedicated-server  | [----] Update complete, launching Steamcmd...
2024-01-28 14:32:15 palworld-dedicated-server  | tid(32) burning pthread_key_t == 0 so we never use it
2024-01-28 14:32:15 palworld-dedicated-server  | Redirecting stderr to '/home/steam/Steam/logs/stderr.txt'
2024-01-28 14:32:15 palworld-dedicated-server  | Logging directory: '/home/steam/Steam/logs'
2024-01-28 14:32:15 palworld-dedicated-server  | [  0%] Checking for available updates...
2024-01-28 14:32:15 palworld-dedicated-server  | [----] Verifying installation...
2024-01-28 14:32:15 palworld-dedicated-server  | Steam Console Client (c) Valve Corporation - version<PHONE_NUMBER>
2024-01-28 14:32:15 palworld-dedicated-server  | -- type 'quit' to exit --
2024-01-28 14:32:16 palworld-dedicated-server  | Loading Steam API...OK
2024-01-28 14:32:16 palworld-dedicated-server  |
2024-01-28 14:32:18 palworld-dedicated-server  | Connecting anonymously to Steam Public...OK
2024-01-28 14:32:18 palworld-dedicated-server  | Waiting for client config...OK
2024-01-28 14:32:35 palworld-dedicated-server  | Waiting for user info...OK
2024-01-28 14:32:35 palworld-dedicated-server  |  Update state (0x3) reconfiguring, progress: 0.00 (0 / 0)
2024-01-28 14:32:35 palworld-dedicated-server  |  Update state (0x5) verifying install, progress: 2.35 (52871648 /<PHONE_NUMBER>)
2024-01-28 14:32:35 palworld-dedicated-server  |  Update state (0x5) verifying install, progress: 17.79 (400014532 /<PHONE_NUMBER>)
2024-01-28 14:32:35 palworld-dedicated-server  |  Update state (0x5) verifying install, progress: 35.86 (806159204 /<PHONE_NUMBER>)
2024-01-28 14:32:35 palworld-dedicated-server  |  Update state (0x5) verifying install, progress: 52.59<PHONE_NUMBER> /<PHONE_NUMBER>)
2024-01-28 14:32:35 palworld-dedicated-server  |  Update state (0x5) verifying install, progress: 70.65<PHONE_NUMBER> /<PHONE_NUMBER>)
2024-01-28 14:32:35 palworld-dedicated-server  |  Update state (0x5) verifying install, progress: 84.27<PHONE_NUMBER> /<PHONE_NUMBER>)
2024-01-28 14:32:35 palworld-dedicated-server  | Success! App '2394010' fully installed.
2024-01-28 14:32:35 palworld-dedicated-server  | Work thread 'CJobMgr::m_WorkThreadPool:1' is marked exited, but we could not immediately join prior to deleting -- proceeding without join
2024-01-28 14:32:35 palworld-dedicated-server  | >>> Starting the gameserver
2024-01-28 14:32:35 palworld-dedicated-server  | >>> Setting up Engine.ini ...
2024-01-28 14:32:35 palworld-dedicated-server  | Found [/Script/OnlineSubsystemUtils.IpNetDriver] section
2024-01-28 14:32:35 palworld-dedicated-server  | Found NetServerMaxTickRate parameter, chaning it to 120
2024-01-28 14:32:35 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedzmPRas': Permission denied
2024-01-28 14:32:35 palworld-dedicated-server  | >>> Finished setting up Engine.ini ...
2024-01-28 14:32:35 palworld-dedicated-server  | >>> Setting up PalWorldSettings.ini ...
2024-01-28 14:32:35 palworld-dedicated-server  | Checking if config exists
2024-01-28 14:32:35 palworld-dedicated-server  | Setting Difficulty to None
2024-01-28 14:32:35 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedDbdFtu': Permission denied
2024-01-28 14:32:35 palworld-dedicated-server  | Setting DayTimeSpeedRate to 1.000000
2024-01-28 14:32:35 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedwyD9IC': Permission denied
2024-01-28 14:32:35 palworld-dedicated-server  | Setting NightTimeSpeedRate to 1.000000
2024-01-28 14:32:35 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sed8IQMsG': Permission denied
2024-01-28 14:32:35 palworld-dedicated-server  | Setting ExpRate to 1.000000
2024-01-28 14:32:35 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedYEo2II': Permission denied
2024-01-28 14:32:35 palworld-dedicated-server  | Setting PalCaptureRate to 1.000000
2024-01-28 14:32:35 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedPM6GqQ': Permission denied
2024-01-28 14:32:35 palworld-dedicated-server  | Setting PalSpawnNumRate to 1.000000
2024-01-28 14:32:35 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedGiJTXU': Permission denied
2024-01-28 14:32:35 palworld-dedicated-server  | Setting PalDamageRateAttack to 1.000000
2024-01-28 14:32:35 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedwYAUFW': Permission denied
2024-01-28 14:32:35 palworld-dedicated-server  | Setting PalDamageRateDefense to 1.000000
2024-01-28 14:32:35 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedHh1D82': Permission denied
2024-01-28 14:32:35 palworld-dedicated-server  | Setting PlayerDamageRateAttack to 1.000000
2024-01-28 14:32:35 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedzZeH86': Permission denied
2024-01-28 14:32:35 palworld-dedicated-server  | Setting PlayerDamageRateDefense to 1.000000
2024-01-28 14:32:35 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedn3UF8b': Permission denied
2024-01-28 14:32:35 palworld-dedicated-server  | Setting PlayerStomachDecreaceRate to 1.000000
2024-01-28 14:32:35 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedfGNyxg': Permission denied
2024-01-28 14:32:35 palworld-dedicated-server  | Setting PlayerStaminaDecreaceRate to 1.000000
2024-01-28 14:32:35 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedwbz7al': Permission denied
2024-01-28 14:32:35 palworld-dedicated-server  | Setting PlayerAutoHPRegeneRate to 1.000000
2024-01-28 14:32:35 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sed7xq0er': Permission denied
2024-01-28 14:32:35 palworld-dedicated-server  | Setting PlayerAutoHpRegeneRateInSleep to 1.000000
2024-01-28 14:32:36 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sed9XeZjw': Permission denied
2024-01-28 14:32:36 palworld-dedicated-server  | Setting PalStomachDecreaceRate to 1.000000
2024-01-28 14:32:36 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedYjeNzy': Permission denied
2024-01-28 14:32:36 palworld-dedicated-server  | Setting PalStaminaDecreaceRate to
2024-01-28 14:32:36 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedZDe8pD': Permission denied
2024-01-28 14:32:36 palworld-dedicated-server  | Setting PalAutoHPRegeneRate to 1.000000
2024-01-28 14:32:36 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedDHDxmI': Permission denied
2024-01-28 14:32:36 palworld-dedicated-server  | Setting PalAutoHpRegeneRateInSleep to 1.000000
2024-01-28 14:32:36 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedZnmIDP': Permission denied
2024-01-28 14:32:36 palworld-dedicated-server  | Setting BuildObjectDamageRate to 1.000000
2024-01-28 14:32:36 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedQCF2tQ': Permission denied
2024-01-28 14:32:36 palworld-dedicated-server  | Setting BuildObjectDeteriorationDamageRate to 1.000000
2024-01-28 14:32:36 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedfaHdkV': Permission denied
2024-01-28 14:32:36 palworld-dedicated-server  | Setting PalAutoHpRegeneRateInSleep to 1.000000
2024-01-28 14:32:36 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedbwLNbZ': Permission denied
2024-01-28 14:32:36 palworld-dedicated-server  | Setting CollectionDropRate to 1.000000
2024-01-28 14:32:36 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedVyypv4': Permission denied
2024-01-28 14:32:36 palworld-dedicated-server  | Setting CollectionObjectHpRate to 1.000000
2024-01-28 14:32:36 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedMDUZoa': Permission denied
2024-01-28 14:32:36 palworld-dedicated-server  | Setting CollectionObjectRespawnSpeedRate to 1.000000
2024-01-28 14:32:36 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedk2ytXd': Permission denied
2024-01-28 14:32:36 palworld-dedicated-server  | Setting EnemyDropItemRate to 1.000000
2024-01-28 14:32:36 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sediZIDCi': Permission denied
2024-01-28 14:32:36 palworld-dedicated-server  | Setting DeathPenalty to All
2024-01-28 14:32:36 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedPBZikn': Permission denied
2024-01-28 14:32:36 palworld-dedicated-server  | Setting bEnablePlayerToPlayerDamage to false
2024-01-28 14:32:36 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedm6NB5u': Permission denied
2024-01-28 14:32:36 palworld-dedicated-server  | Setting bEnableFriendlyFire to false
2024-01-28 14:32:36 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedaJJNRz': Permission denied
2024-01-28 14:32:36 palworld-dedicated-server  | Setting bEnableInvaderEnemy to true
2024-01-28 14:32:36 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/seduL9eYB': Permission denied
2024-01-28 14:32:36 palworld-dedicated-server  | Setting bActiveUNKO to false
2024-01-28 14:32:36 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedQ4KztJ': Permission denied
2024-01-28 14:32:36 palworld-dedicated-server  | Setting bEnableAimAssistPad to true
2024-01-28 14:32:36 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedO0vB5J': Permission denied
2024-01-28 14:32:36 palworld-dedicated-server  | Setting bEnableAimAssistKeyboard to false
2024-01-28 14:32:36 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sed38q3fQ': Permission denied
2024-01-28 14:32:36 palworld-dedicated-server  | Setting DropItemMaxNum to 3000
2024-01-28 14:32:36 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedMpPikV': Permission denied
2024-01-28 14:32:36 palworld-dedicated-server  | Setting DropItemMaxNum_UNKO to 100
2024-01-28 14:32:36 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedYSMaOY': Permission denied
2024-01-28 14:32:36 palworld-dedicated-server  | Setting BaseCampMaxNum to 128
2024-01-28 14:32:36 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sed6jtuQ4': Permission denied
2024-01-28 14:32:36 palworld-dedicated-server  | Setting BaseCampWorkerMaxNum to 15
2024-01-28 14:32:36 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sed6Y6bQ9': Permission denied
2024-01-28 14:32:36 palworld-dedicated-server  | Setting DropItemAliveMaxHours to 1.000000
2024-01-28 14:32:36 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sed3ssjve': Permission denied
2024-01-28 14:32:36 palworld-dedicated-server  | Setting bAutoResetGuildNoOnlinePlayers to false
2024-01-28 14:32:37 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedlp3lJi': Permission denied
2024-01-28 14:32:37 palworld-dedicated-server  | Setting AutoResetGuildTimeNoOnlinePlayers to 72.000000
2024-01-28 14:32:37 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedGuXrBo': Permission denied
2024-01-28 14:32:37 palworld-dedicated-server  | Setting GuildPlayerMaxNum to 20
2024-01-28 14:32:37 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedGwzfFu': Permission denied
2024-01-28 14:32:37 palworld-dedicated-server  | Setting PalEggDefaultHatchingTime to 72.000000
2024-01-28 14:32:37 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedq5Dk9u': Permission denied
2024-01-28 14:32:37 palworld-dedicated-server  | Setting WorkSpeedRate to 1.000000
2024-01-28 14:32:37 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedSfA6Fz': Permission denied
2024-01-28 14:32:37 palworld-dedicated-server  | Setting bIsMultiplay to false
2024-01-28 14:32:37 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedLtCLxI': Permission denied
2024-01-28 14:32:37 palworld-dedicated-server  | Setting bIsPvP to false
2024-01-28 14:32:37 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedPoAocN': Permission denied
2024-01-28 14:32:37 palworld-dedicated-server  | Setting bCanPickupOtherGuildDeathPenaltyDrop to false
2024-01-28 14:32:37 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedNtrrBP': Permission denied
2024-01-28 14:32:37 palworld-dedicated-server  | Setting bEnableNonLoginPenalty to true
2024-01-28 14:32:37 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedh8pqES': Permission denied
2024-01-28 14:32:37 palworld-dedicated-server  | Setting bEnableFastTravel to true
2024-01-28 14:32:37 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sed2S7Kb0': Permission denied
2024-01-28 14:32:37 palworld-dedicated-server  | Setting bIsStartLocationSelectByMap to true
2024-01-28 14:32:37 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedwLpIl5': Permission denied
2024-01-28 14:32:37 palworld-dedicated-server  | Setting bExistPlayerAfterLogout to false
2024-01-28 14:32:37 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedNwcV77': Permission denied
2024-01-28 14:32:37 palworld-dedicated-server  | Setting bEnableDefenseOtherGuildPlayer to false
2024-01-28 14:32:37 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedeTqUqb': Permission denied
2024-01-28 14:32:37 palworld-dedicated-server  | Setting CoopPlayerMaxNum to 4
2024-01-28 14:32:37 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedwMKuah': Permission denied
2024-01-28 14:32:37 palworld-dedicated-server  | Setting max-players to 16
2024-01-28 14:32:37 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedMclwAl': Permission denied
2024-01-28 14:32:37 palworld-dedicated-server  | Setting server name to jammsen-docker-generated-###RANDOM###
2024-01-28 14:32:37 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedsNHlGt': Permission denied
2024-01-28 14:32:37 palworld-dedicated-server  | Found standard template, using random numbers in server name
2024-01-28 14:32:37 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedaVjCKv': Permission denied
2024-01-28 14:32:37 palworld-dedicated-server  | Server name is now jammsen-docker-generated-29517
2024-01-28 14:32:37 palworld-dedicated-server  | Setting server description to Palworld-Dedicated-Server running in Docker by jammsen
2024-01-28 14:32:37 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedfYApnz': Permission denied
2024-01-28 14:32:37 palworld-dedicated-server  | Setting server admin password to "I_Replaced_My_Password"
2024-01-28 14:32:37 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedlK4erH': Permission denied
2024-01-28 14:32:37 palworld-dedicated-server  | Setting server password to "I_Replaced_My_Password"
2024-01-28 14:32:37 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedErUslM': Permission denied
2024-01-28 14:32:37 palworld-dedicated-server  | Setting public port to 8211
2024-01-28 14:32:37 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedRE1kbR': Permission denied
2024-01-28 14:32:37 palworld-dedicated-server  | Setting public ip to "I_Replaced_DDNS_TEXT"
2024-01-28 14:32:37 palworld-dedicated-server  | sed: -e expression #1, char 36: unknown option to `s'
2024-01-28 14:32:37 palworld-dedicated-server  | Setting rcon-enabled to false
2024-01-28 14:32:37 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedGC6H8Y': Permission denied
2024-01-28 14:32:37 palworld-dedicated-server  | Setting RCONPort to 25575
2024-01-28 14:32:37 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedwYAeh2': Permission denied
2024-01-28 14:32:37 palworld-dedicated-server  | Setting bUseAuth to true
2024-01-28 14:32:37 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedFxSy06': Permission denied
2024-01-28 14:32:37 palworld-dedicated-server  | Setting BanListURL to https://api.palworldgame.com/api/banlist.txt
2024-01-28 14:32:37 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedfUUSUa': Permission denied
2024-01-28 14:32:37 palworld-dedicated-server  | >>> Finished setting up PalWorldSettings.ini ...
2024-01-28 14:32:39 palworld-dedicated-server  | [S_API] SteamAPI_Init(): Loaded local 'steamclient.so' OK.
2024-01-28 14:32:39 palworld-dedicated-server  | Shutdown handler: initalize.
2024-01-28 14:32:39 palworld-dedicated-server  | - Existing per-process limit (soft=1048576, hard=1048576) is enough for us (need only 1048576)
2024-01-28 14:32:39 palworld-dedicated-server  | Increasing per-process limit of core file size to infinity.
2024-01-28 14:32:39 palworld-dedicated-server  | CAppInfoCacheReadFromDiskThread took 6 milliseconds to initialize
2024-01-28 14:32:39 palworld-dedicated-server  | Setting breakpad minidump AppID = 2394010
2024-01-28 14:32:39 palworld-dedicated-server  | [S_API FAIL] Tried to access Steam interface SteamUser021 before SteamAPI_Init succeeded.
2024-01-28 14:32:39 palworld-dedicated-server  | [S_API FAIL] Tried to access Steam interface SteamFriends017 before SteamAPI_Init succeeded.
2024-01-28 14:32:41 palworld-dedicated-server  | [S_API FAIL] Tried to access Steam interface STEAMAPPS_INTERFACE_VERSION008 before SteamAPI_Init succeeded.
2024-01-28 14:32:42 palworld-dedicated-server  | [S_API FAIL] Tried to access Steam interface SteamNetworkingUtils004 before SteamAPI_Init succeeded.
2024-01-28 14:35:01 palworld-dedicated-server  | FUnixPlatformMisc::RequestExitWithStatus
2024-01-28 14:35:01 palworld-dedicated-server  | FUnixPlatformMisc::RequestExit
2024-01-28 14:35:03 palworld-dedicated-server  | dlmopen steamservice.so failed: steamservice.so: cannot open shared object file: No such file or directory
2024-01-28 14:35:05 palworld-dedicated-server  | Exiting abnormally (error code: 143)
2024-01-28 14:35:05 palworld-dedicated-server  | Shutdown handler: cleanup.
2024-01-28 14:35:06 palworld-dedicated-server  | >>> Checking for existence of default credentials
2024-01-28 14:35:06 palworld-dedicated-server  | >>> Doing an update of the gameserver
2024-01-28 14:35:06 palworld-dedicated-server  | time="2024-01-28T14:35:06+09:00" level=info msg="read crontab: cronlist"
2024-01-28 14:35:07 palworld-dedicated-server  | tid(20) burning pthread_key_t == 0 so we never use it
2024-01-28 14:35:07 palworld-dedicated-server  | Redirecting stderr to '/home/steam/Steam/logs/stderr.txt'
2024-01-28 14:35:07 palworld-dedicated-server  | Logging directory: '/home/steam/Steam/logs'
2024-01-28 14:35:07 palworld-dedicated-server  | [  0%] Checking for available updates...
2024-01-28 14:35:07 palworld-dedicated-server  | [----] Verifying installation...
2024-01-28 14:35:07 palworld-dedicated-server  | Steam Console Client (c) Valve Corporation - version<PHONE_NUMBER>
2024-01-28 14:35:07 palworld-dedicated-server  | -- type 'quit' to exit --
2024-01-28 14:35:07 palworld-dedicated-server  | Loading Steam API...OK
2024-01-28 14:35:07 palworld-dedicated-server  |
2024-01-28 14:35:09 palworld-dedicated-server  | Connecting anonymously to Steam Public...OK
2024-01-28 14:35:09 palworld-dedicated-server  | Waiting for client config...OK
2024-01-28 14:35:10 palworld-dedicated-server  | Waiting for user info...OK
2024-01-28 14:35:10 palworld-dedicated-server  |  Update state (0x0) unknown, progress: 0.00 (0 / 0)
2024-01-28 14:35:10 palworld-dedicated-server  | Error! App '2394010' state is 0x204 after update job.
2024-01-28 14:35:10 palworld-dedicated-server  | >>> Starting the gameserver
2024-01-28 14:35:10 palworld-dedicated-server  | >>> Setting up Engine.ini ...
2024-01-28 14:35:10 palworld-dedicated-server  | Found no [/Script/OnlineSubsystemUtils.IpNetDriver], adding it
2024-01-28 14:35:10 palworld-dedicated-server  | Found no NetServerMaxTickRate parameter, adding it to 120
2024-01-28 14:35:10 palworld-dedicated-server  | >>> Finished setting up Engine.ini ...
2024-01-28 14:35:10 palworld-dedicated-server  | >>> Setting up PalWorldSettings.ini ...
2024-01-28 14:35:10 palworld-dedicated-server  | Checking if config exists
2024-01-28 14:35:10 palworld-dedicated-server  | Setting Difficulty to None
2024-01-28 14:35:10 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedgb8m2d': Permission denied
2024-01-28 14:35:10 palworld-dedicated-server  | Setting DayTimeSpeedRate to 1.000000
2024-01-28 14:35:10 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedKiTg9j': Permission denied
2024-01-28 14:35:10 palworld-dedicated-server  | Setting NightTimeSpeedRate to 1.000000
2024-01-28 14:35:10 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedftwSIo': Permission denied
2024-01-28 14:35:10 palworld-dedicated-server  | Setting ExpRate to 1.000000
2024-01-28 14:35:10 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sed84dI8q': Permission denied
2024-01-28 14:35:10 palworld-dedicated-server  | Setting PalCaptureRate to 1.000000
2024-01-28 14:35:10 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sed25ygTv': Permission denied
2024-01-28 14:35:10 palworld-dedicated-server  | Setting PalSpawnNumRate to 1.000000
2024-01-28 14:35:10 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedyCkmfz': Permission denied
2024-01-28 14:35:10 palworld-dedicated-server  | Setting PalDamageRateAttack to 1.000000
2024-01-28 14:35:10 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedxkTaOH': Permission denied
2024-01-28 14:35:10 palworld-dedicated-server  | Setting PalDamageRateDefense to 1.000000
2024-01-28 14:35:10 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedBo2hDK': Permission denied
2024-01-28 14:35:10 palworld-dedicated-server  | Setting PlayerDamageRateAttack to 1.000000
2024-01-28 14:35:10 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedn23mqN': Permission denied
2024-01-28 14:35:10 palworld-dedicated-server  | Setting PlayerDamageRateDefense to 1.000000
2024-01-28 14:35:10 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedvyc2sU': Permission denied
2024-01-28 14:35:10 palworld-dedicated-server  | Setting PlayerStomachDecreaceRate to 1.000000
2024-01-28 14:35:10 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedVl661W': Permission denied
2024-01-28 14:35:10 palworld-dedicated-server  | Setting PlayerStaminaDecreaceRate to 1.000000
2024-01-28 14:35:10 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedLsAJP4': Permission denied
2024-01-28 14:35:10 palworld-dedicated-server  | Setting PlayerAutoHPRegeneRate to 1.000000
2024-01-28 14:35:10 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedJCcB29': Permission denied
2024-01-28 14:35:10 palworld-dedicated-server  | Setting PlayerAutoHpRegeneRateInSleep to 1.000000
2024-01-28 14:35:10 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sed87oTUa': Permission denied
2024-01-28 14:35:10 palworld-dedicated-server  | Setting PalStomachDecreaceRate to 1.000000
2024-01-28 14:35:10 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedjNk0dh': Permission denied
2024-01-28 14:35:10 palworld-dedicated-server  | Setting PalStaminaDecreaceRate to
2024-01-28 14:35:10 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedPg9VYm': Permission denied
2024-01-28 14:35:10 palworld-dedicated-server  | Setting PalAutoHPRegeneRate to 1.000000
2024-01-28 14:35:10 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedVoFSsq': Permission denied
2024-01-28 14:35:10 palworld-dedicated-server  | Setting PalAutoHpRegeneRateInSleep to 1.000000
2024-01-28 14:35:10 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sed78T4Sv': Permission denied
2024-01-28 14:35:10 palworld-dedicated-server  | Setting BuildObjectDamageRate to 1.000000
2024-01-28 14:35:10 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedJZriaC': Permission denied
2024-01-28 14:35:10 palworld-dedicated-server  | Setting BuildObjectDeteriorationDamageRate to 1.000000
2024-01-28 14:35:10 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedkPLFyE': Permission denied
2024-01-28 14:35:10 palworld-dedicated-server  | Setting PalAutoHpRegeneRateInSleep to 1.000000
2024-01-28 14:35:10 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedWJnMHH': Permission denied
2024-01-28 14:35:10 palworld-dedicated-server  | Setting CollectionDropRate to 1.000000
2024-01-28 14:35:10 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedwHWLZM': Permission denied
2024-01-28 14:35:10 palworld-dedicated-server  | Setting CollectionObjectHpRate to 1.000000
2024-01-28 14:35:10 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedJKfQuS': Permission denied
2024-01-28 14:35:10 palworld-dedicated-server  | Setting CollectionObjectRespawnSpeedRate to 1.000000
2024-01-28 14:35:10 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedKswfHW': Permission denied
2024-01-28 14:35:10 palworld-dedicated-server  | Setting EnemyDropItemRate to 1.000000
2024-01-28 14:35:10 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedfVM1o2': Permission denied
2024-01-28 14:35:10 palworld-dedicated-server  | Setting DeathPenalty to All
2024-01-28 14:35:10 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedSxO3A6': Permission denied
2024-01-28 14:35:10 palworld-dedicated-server  | Setting bEnablePlayerToPlayerDamage to false
2024-01-28 14:35:10 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedA9OmPd': Permission denied
2024-01-28 14:35:10 palworld-dedicated-server  | Setting bEnableFriendlyFire to false
2024-01-28 14:35:10 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedzDgqgf': Permission denied
2024-01-28 14:35:10 palworld-dedicated-server  | Setting bEnableInvaderEnemy to true
2024-01-28 14:35:10 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sed3Ci4Lj': Permission denied
2024-01-28 14:35:10 palworld-dedicated-server  | Setting bActiveUNKO to false
2024-01-28 14:35:10 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedme2Zcp': Permission denied
2024-01-28 14:35:10 palworld-dedicated-server  | Setting bEnableAimAssistPad to true
2024-01-28 14:35:10 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedv6PsLw': Permission denied
2024-01-28 14:35:10 palworld-dedicated-server  | Setting bEnableAimAssistKeyboard to false
2024-01-28 14:35:10 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sed9RPeHB': Permission denied
2024-01-28 14:35:11 palworld-dedicated-server  | Setting DropItemMaxNum to 3000
2024-01-28 14:35:11 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sed3vbVIB': Permission denied
2024-01-28 14:35:11 palworld-dedicated-server  | Setting DropItemMaxNum_UNKO to 100
2024-01-28 14:35:11 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedhnfTDI': Permission denied
2024-01-28 14:35:11 palworld-dedicated-server  | Setting BaseCampMaxNum to 128
2024-01-28 14:35:11 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedg3KclN': Permission denied
2024-01-28 14:35:11 palworld-dedicated-server  | Setting BaseCampWorkerMaxNum to 15
2024-01-28 14:35:11 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedTY2mUS': Permission denied
2024-01-28 14:35:11 palworld-dedicated-server  | Setting DropItemAliveMaxHours to 1.000000
2024-01-28 14:35:11 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedD0r2ZY': Permission denied
2024-01-28 14:35:11 palworld-dedicated-server  | Setting bAutoResetGuildNoOnlinePlayers to false
2024-01-28 14:35:11 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedsyysH3': Permission denied
2024-01-28 14:35:11 palworld-dedicated-server  | Setting AutoResetGuildTimeNoOnlinePlayers to 72.000000
2024-01-28 14:35:11 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sed20xE67': Permission denied
2024-01-28 14:35:11 palworld-dedicated-server  | Setting GuildPlayerMaxNum to 20
2024-01-28 14:35:11 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedYcVsO8': Permission denied
2024-01-28 14:35:11 palworld-dedicated-server  | Setting PalEggDefaultHatchingTime to 72.000000
2024-01-28 14:35:11 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedfFvPVf': Permission denied
2024-01-28 14:35:11 palworld-dedicated-server  | Setting WorkSpeedRate to 1.000000
2024-01-28 14:35:11 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedy9iDQl': Permission denied
2024-01-28 14:35:11 palworld-dedicated-server  | Setting bIsMultiplay to false
2024-01-28 14:35:11 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sed6ObBuo': Permission denied
2024-01-28 14:35:11 palworld-dedicated-server  | Setting bIsPvP to false
2024-01-28 14:35:11 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedYWZR8t': Permission denied
2024-01-28 14:35:11 palworld-dedicated-server  | Setting bCanPickupOtherGuildDeathPenaltyDrop to false
2024-01-28 14:35:11 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sed2Oe10z': Permission denied
2024-01-28 14:35:11 palworld-dedicated-server  | Setting bEnableNonLoginPenalty to true
2024-01-28 14:35:11 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedArnjJB': Permission denied
2024-01-28 14:35:11 palworld-dedicated-server  | Setting bEnableFastTravel to true
2024-01-28 14:35:11 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sed1UnFiJ': Permission denied
2024-01-28 14:35:11 palworld-dedicated-server  | Setting bIsStartLocationSelectByMap to true
2024-01-28 14:35:11 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedxgQ1iN': Permission denied
2024-01-28 14:35:11 palworld-dedicated-server  | Setting bExistPlayerAfterLogout to false
2024-01-28 14:35:11 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sediHqGhS': Permission denied
2024-01-28 14:35:11 palworld-dedicated-server  | Setting bEnableDefenseOtherGuildPlayer to false
2024-01-28 14:35:11 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedWzhu2W': Permission denied
2024-01-28 14:35:11 palworld-dedicated-server  | Setting CoopPlayerMaxNum to 4
2024-01-28 14:35:11 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedU77di2': Permission denied
2024-01-28 14:35:11 palworld-dedicated-server  | Setting max-players to 16
2024-01-28 14:35:11 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedjCvNh5': Permission denied
2024-01-28 14:35:11 palworld-dedicated-server  | Setting server name to jammsen-docker-generated-###RANDOM###
2024-01-28 14:35:11 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sed2IpiZ8': Permission denied
2024-01-28 14:35:11 palworld-dedicated-server  | Found standard template, using random numbers in server name
2024-01-28 14:35:11 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedl22GKe': Permission denied
2024-01-28 14:35:11 palworld-dedicated-server  | Server name is now jammsen-docker-generated-26608
2024-01-28 14:35:11 palworld-dedicated-server  | Setting server description to Palworld-Dedicated-Server running in Docker by jammsen
2024-01-28 14:35:11 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedO5jiTk': Permission denied
2024-01-28 14:35:11 palworld-dedicated-server  | Setting server admin password to "I_Replaced_My_Password"
2024-01-28 14:35:11 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedeMX4bo': Permission denied
2024-01-28 14:35:11 palworld-dedicated-server  | Setting server password to "I_Replaced_My_Password"
2024-01-28 14:35:11 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sed9Ej02q': Permission denied
2024-01-28 14:35:11 palworld-dedicated-server  | Setting public port to 8211
2024-01-28 14:35:11 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/seddc90fx': Permission denied
2024-01-28 14:35:11 palworld-dedicated-server  | Setting public ip to "I_Replaced_DDNS_TEXT"
2024-01-28 14:35:11 palworld-dedicated-server  | sed: -e expression #1, char 36: unknown option to `s'
2024-01-28 14:35:11 palworld-dedicated-server  | Setting rcon-enabled to false
2024-01-28 14:35:11 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedM6taMI': Permission denied
2024-01-28 14:35:11 palworld-dedicated-server  | Setting RCONPort to 25575
2024-01-28 14:35:11 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedUThzgJ': Permission denied
2024-01-28 14:35:11 palworld-dedicated-server  | Setting bUseAuth to true
2024-01-28 14:35:11 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sed8x7p9P': Permission denied
2024-01-28 14:35:11 palworld-dedicated-server  | Setting BanListURL to https://api.palworldgame.com/api/banlist.txt
2024-01-28 14:35:11 palworld-dedicated-server  | sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedASnYGS': Permission denied
2024-01-28 14:35:11 palworld-dedicated-server  | >>> Finished setting up PalWorldSettings.ini ...
2024-01-28 14:35:11 palworld-dedicated-server  | chmod: changing permissions of '/palworld/Pal/Binaries/Linux/PalServer-Linux-Test': Permission denied
2024-01-28 14:35:13 palworld-dedicated-server  | Shutdown handler: initalize.
2024-01-28 14:35:13 palworld-dedicated-server  | - Existing per-process limit (soft=1048576, hard=1048576) is enough for us (need only 1048576)
2024-01-28 14:35:13 palworld-dedicated-server  | Increasing per-process limit of core file size to infinity.
2024-01-28 14:35:13 palworld-dedicated-server  | [S_API] SteamAPI_Init(): Loaded local 'steamclient.so' OK.
2024-01-28 14:35:13 palworld-dedicated-server  | CAppInfoCacheReadFromDiskThread took 4 milliseconds to initialize
2024-01-28 14:35:13 palworld-dedicated-server  | Setting breakpad minidump AppID = 2394010
2024-01-28 14:35:13 palworld-dedicated-server  | [S_API FAIL] Tried to access Steam interface SteamUser021 before SteamAPI_Init succeeded.
2024-01-28 14:35:13 palworld-dedicated-server  | [S_API FAIL] Tried to access Steam interface SteamFriends017 before SteamAPI_Init succeeded.
2024-01-28 14:35:14 palworld-dedicated-server  | [S_API FAIL] Tried to access Steam interface STEAMAPPS_INTERFACE_VERSION008 before SteamAPI_Init succeeded.
2024-01-28 14:35:15 palworld-dedicated-server  | [S_API FAIL] Tried to access Steam interface SteamNetworkingUtils004 before SteamAPI_Init succeeded.

After much effort, I successfully recovered the play data. The recovery was done by overlaying the save files onto the data created after running the server once. It seems there was an error due to a different checksum in a folder under Saved/SaveGames/0. However, the permission error still persists. For now, I'm continuing to play with the server restarted in this state.

I dont have a Mac to test this, but when i read your errors, i think about chown/chmod permission problems.
Also that config looks very weird. -> sed: preserving permissions for '/palworld/Pal/Saved/Config/LinuxServer/sedU77di2': Permission denied
Here is my code regarding that https://github.com/jammsen/docker-palworld-dedicated-server/blob/master/servermanager.sh#L59

Hello! I was able to reproduce this issue on a Mac. It appears there is a bug in the version of sed deployed in the Debian image that when making temporary files with inline commands (sed -i), it doesn't apply the correct umask. The result is a bunch of permission issues. This gets fixed in sed 4.8.
The workaround for Docker Desktop on Mac that solved it for me was to instead use gRPC FUSE (not VirtioFS)

Hello! I was able to reproduce this issue on a Mac. It appears there is a bug in the version of sed deployed in the Debian image that when making temporary files with inline commands (sed -i), it doesn't apply the correct umask. The result is a bunch of permission issues. This gets fixed in sed 4.8.
The workaround for Docker Desktop on Mac that solved it for me was to instead use gRPC FUSE (not VirtioFS)

Hello @beardenj - According to this https://packages.debian.org/bullseye/sed Sed 4.7.1 is used in oldstable.
Bookworm uses 4.9.1 - https://packages.debian.org/search?keywords=sed&searchon=names&suite=bookworm&section=all
Not sure if @CM2Walki will deliver a "steamcmd image for Bookworm though. As far as i can see on master its Bullseye so Debian 11 only. You might want to consider a Feature Request over there.

See https://github.com/CM2Walki/steamcmd/issues/54

@beardenj Debian 12 support was added, i can look into upgrading the base-image in a few days.


server.py is adding 'trainer' instead of removing it at the end of training.

in File server.py, line 131:
while self.trainers:
self.add_trainer()
Should it be self.remove_trainer() ?

Fixed as suggested.


Swift 2

Updates DKChainableAnimationKit to the new Swift 2 using Xcode 7 beta1.
I suggest to keep this around as a separate branch feature/swift-2 and not merge it into master, as it breaks compatibility with Xcode 6 and can only be build using beta software. However, to use DKChainableAnimationKit with the new Xcode and iOS 9 this change is required. Once Xcode 7 leaves beta stage, the branch can then be merged.

:+1:

Will you open up a new branch swift-2so that we can merge this pull request into there?

Yes I will. But I will do that when Xcode7 leaves beta. Cuz it will happen
months later. And I will add more features to this library.
If I create a new branch and merge it now, and add more features to master
branch. And I cannot merge swift-2 branch from master. So I will do that later.
From Draveness
On 周四, 6月 11, 2015 at 17:48, Draveness/DKChainableAnimationKit
<EMAIL_ADDRESS>wrote:
Will you open up a new branch swift-2 so that we can merge this pull request into there?
—
Reply to this email directly or view it on GitHub
[https://github.com/Draveness/DKChainableAnimationKit/pull/8#issuecomment-111070055] .[https://github.com/notifications/beacon/AGMUR7Ab9aIMRpE4-gWIE9yKApxJbWiIks5oSVDtgaJpZM4E-mkL.gif]

Could you open up a new branch swift-2, so that we can benefit your work ? :-) Thx

As of Yesterday, XCode 7 is officially out of beta. It would be great to figure out a path forward for Swift 2.0.

Updated


Include URL to data sources

Include some URLs to reference data used in this project

All is looking good

All changes have been accounted and ready to proceed with the merge


Auto-fill only parts of a transaction and let the rest get entered manually

I have some use-cases for auto-filling i.e. only the payee, but I still want to enter the purpose manually.
To my knowledge this is not possible now, right ?
If I add a match rule it will override the fill: keys and leave those as the original values, but don't give me the opportunity to manual enter anz value. Or am i wrong ? Hope it gets clear what I want.

This is not too well documented but is mentioned here and in the Changelog, if I understand you correctly.
Example:
    - match:
        payee: "MUSIC COMPANY 123"
      fill:
        credit_account: "expenses:monthly:musiccompany"
        purpose:

will auto fill credit_account and prompt for purpose

Works like a charm!


Refactored packages

As a whole this pr is about #71 it doesn't resolve all of the issues but it gets us closer to modularity/optionality. Now the core backend doesn't know anything about sublime packages for using them in the frontend we just need to add
import _ "github.com/limetext/lime/backend/sublime"

closes #64
As there are a lot of commits and changes I'll address the main changes:

packages package which most of the code and the package is documented

sublime package the code is now much cleaner also we have separate tests

removed lime-packages dependency from backend we dont need this submodule for lime-backend anymore

I tested the frontends against this pr they won't crash but they don't load any packages currently because i need to work a bit on lime-packages repo.

closes #85

Coverage decreased (-1.3%) to 58.421% when pulling 02d187f9e940a464f41a5f42e1b276fdee3933c7 on packages into 1f446ac54d08be96b16bda78c4c5ed167f45a052 on master.

Coverage decreased (-1.3%) to 58.396% when pulling cb459ef64edd9d2e5b41ddbad902b0bd0c28001b on packages into 1f446ac54d08be96b16bda78c4c5ed167f45a052 on master.

Coverage decreased (-1.0%) to 58.726% when pulling c3f7f27887e66183971933a2efb7b154177e06e9 on packages into 1f446ac54d08be96b16bda78c4c5ed167f45a052 on master.

All mentioned problems are resolved.


Add codecov upload step

this needs the codecov secret, which I don't have permissions to add to the repo


Since 1.45, this doesn't happen anymore, instead the word is replaced by `. It's the same with auto-closing.
This was very useful to type markdown-like commit messages. If this is not a bug/intended, is there a way to reenable this behavior?
v1.44.2 :

v1.54.3 (1.51.1 for the capture but it's the same since 1.45) :

Does this issue occur when all extensions are disabled?: Yes

@joaomoreno do you have any pointers on this one? What was allowing this before?

I really don't know... pinging @alexdima and @rebornix in case there was refactorings in this area of auto surrounding characters.

@joaomoreno This commit defines the language of the SCM input to be scminput. The language scminput does not have any surrounding pairs defined. Here is as an example the language configuration for plaintext.

I see that the git-commit language is affected too (but probably was since the beginning, not like this issue), I don't know what is possible in VSCode (nor what you would accept), what could be working to fix this:

(scminput only) create a /extensions/git-base/languages/scminput.language-configuration.json file with the plaintext configuration? (Not the way to go I think)
(scminput only) edit https://github.com/microsoft/vscode/blob/1.72.2/src/vs/workbench/contrib/scm/browser/scm.contribution.ts#L34 to add a copy of the plaintext configuration? Would you accept a PR?
configure the language myself using the settings? Is that possible at all? This would be the best option IMO: allowing each user to configure the editor as wanted, but it seems unsupported (https://old.reddit.com/r/vscode/comments/qo28jx/change_some_language_settings/)
create an extensions that would add/configure the surroundingPairs in theses 2 languages (scminput, git-commit)? How hard would that be?

Note that this is really an issue because on AZERTY layout, ` is a dead key requiring to press AltGr+7 followed by Space to get one, or double press AltGr+7 to get two but then you must put the text inside or delete one ; so the ability to select text + AltGr+7, Space to put backticks is really useful.
Current annexes:

the plaintext configuration : https://github.com/microsoft/vscode/blob/1.72.2/src/vs/editor/common/languages/languageConfigurationRegistry.ts#L298
the git-commit language configuration https://github.com/microsoft/vscode/blob/1.72.2/extensions/git-base/languages/git-commit.language-configuration.json
the plaintext language registration https://github.com/microsoft/vscode/blob/1.72.2/src/vs/editor/common/languages/modesRegistry.ts#L56
the plaintext language config registration https://github.com/microsoft/vscode/blob/1.72.2/src/vs/editor/common/languages/languageConfigurationRegistry.ts#L298

So idea n°3 seems to be discussed in https://github.com/microsoft/vscode/issues/102574 (2020) and https://github.com/microsoft/vscode/issues/38352 is even older (2017), any chance it'll be available? Are you aware of extensions allowing this?

(scminput only) create a /extensions/git-base/languages/scminput.language-configuration.json file with the plaintext configuration? (Not the way to go I think)
(scminput only) edit https://github.com/microsoft/vscode/blob/1.72.2/src/vs/workbench/contrib/scm/browser/scm.contribution.ts#L34 to add a copy of the plaintext configuration? Would you accept a PR?
configure the language myself using the settings? Is that possible at all? This would be the best option IMO: allowing each user to configure the editor as wanted, but it seems unsupported (https://old.reddit.com/r/vscode/comments/qo28jx/change_some_language_settings/)
create an extensions that would add/configure the surroundingPairs in theses 2 languages (scminput, git-commit)? How hard would that be?

Option No2 seems reasonable to me. @joaomoreno, @alexdima what do you think?

We did a bunch of refactorings since last year, one of which was to eliminate the LanguageConfigurationRegistry, so adding a language configuration statically in ambient code is not possible anymore. I think the recommended way is to use the ILanguageConfigurationService. cc @hediet to double check this.


container error after upgrade to containerd.io 1.4.6-1

System: docker-ce version 20.10.6 on Debian buster 10.9
Bug: After last update of conainerd.io from version 1.4.4-1 to 1.4.6-1 docker container immediately stop working.
Error messages from docker status:

cleanup: failed to delete container from containerd: no such container
failed to start container ... task 64c... already exists: unk

Restarting docker did not solved the problem.
Workaround: Downgrade containerd.io to previous version (sudo apt-get install containerd.io:amd64=1.4.4-1) and container immediately worked again.

I also have problems after upgrading from 1.4.4-1 to 1.4.6-1.
I get the following error:

docker: Error response from daemon: OCI runtime create failed: invalid mount {Destination:[...] Type:bind Source:/var/lib/docker/volumes/ ... /_data Options:[rbind]}: mount destination [...] not absolute: unknown.

Downgrading to 1.4.4-1 also helped me immediately.

Same here, needed to downgrade from 1.4.6 to 1.4.4.

Same thing!
FROM ubuntu:18.04

RUN echo asd

docker build -t asd .
Sending build context to Docker daemon  2.048kB
Step 1/2 : FROM ubuntu:18.04
 ---> 81bcf752ac3d
Step 2/2 : RUN echo asd
 ---> Running in 71fc8a0abb62
OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: rootfs_linux.go:76: mounting "proc" to rootfs at "/proc" caused: mount through procfd: no such file or directory: unknown

docker version
Client: Docker Engine - Community
 Version:           20.10.7
 API version:       1.41
 Go version:        go1.13.15
 Git commit:        f0df350
 Built:             Wed Jun  2 11:56:40 2021
 OS/Arch:           linux/amd64
 Context:           default
 Experimental:      true

Server: Docker Engine - Community
 Engine:
  Version:          20.10.7
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.13.15
  Git commit:       b0f5bc3
  Built:            Wed Jun  2 11:54:48 2021
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.4.6
  GitCommit:        d71fcd7d8303cbf684402823e425e9dd2e99285d
 runc:
  Version:          1.0.0-rc93
  GitCommit:        12644e614e25b05da6fd08a38ffa0cfe1903fdec
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

On Ubuntu 18:04

I was getting:
docker: Error response from daemon: OCI runtime create failed: invalid mount {Destination:: Type:bind Source:/var/lib/docker/volumes/9e1805936631f35e4895a18840a0f56c21669099b5967954b176585e9af7a2da/_data Options:[rbind]}: mount destination : not absolute: unknown.
Downgrading as pointed out by @KeyserSoeze worked.

@KeyserSoeze not sure what happened in your case; do you happen to be using the "live restore" option on Docker?
I tried reproducing by:

installing docker 20.10.6 and containerd v1.4.4 + runc v1.0.0-rc93
start some containers
upgrade containerd to 1.4.6 + runc v1.0.0-rc95
start some containers

wget -q -O- "https://download.docker.com/linux/debian/gpg" | apt-key add -qq -
echo "deb [arch=amd64] https://download.docker.com/linux/debian buster stable" > /etc/apt/sources.list.d/docker.list

# install docker 20.10.6 and containerd v1.4.4 + runc v1.0.0-rc93
apt-get update && apt-get install -y -qq --no-install-recommends \
    docker-ce-cli=5:20.10.6~3-0~debian-buster \
    docker-ce=5:20.10.6~3-0~debian-buster \
    containerd.io=1.4.4-1

# run some containers
docker run -d --name web nginx:alpine
docker run -it ubuntu:18.04

# upgrade containerd
apt-get install -y containerd.io=1.4.6-1

# try starting the "web" container
docker start web

# try running an ubuntu container
docker run -it --rm ubuntu

Does upgrading docker to 20.10.7 solve your issue?
w.r.t. https://github.com/containerd/containerd/issues/5547#issuecomment-851354441 and https://github.com/containerd/containerd/issues/5547#issuecomment-854549074
@nilsglow @mesquita
That looks related to a breaking change in runc (see https://github.com/opencontainers/runc/issues/2928). We applied changes in Docker 20.10.7 to work around that change (see https://github.com/moby/moby/pull/42370), as well as changes in BuildKit (https://github.com/moby/buildkit/pull/2123) but it's possible that (e.g. in situations where you're running a swarm service which was already created) that this is causing issues.
I'm not sure if the runc maintainers want to revert that change for v1.0.0 (but I can try)
@goodspark I tried reproducing your issue (which looks to be separate from the above), but wasn't able to: what distro are you running on? (perhaps you can edit your comment and add the output of docker info ?)

I'm having this same issue with Github workflows using ubuntu-latest:
Current runner version: '2.278.0'
- Operating System
  Ubuntu
  20.04.2
  LTS
- Virtual Environment
  Environment: ubuntu-20.04
  Version: 20210531.0
  Included Software: https://github.com/actions/virtual-environments/blob/ubuntu20/20210531.0/images/linux/Ubuntu2004-README.md
  Image Release: https://github.com/actions/virtual-environments/releases/tag/ubuntu20%2F20210531.0

docker version
- Client:
  Version:           20.10.6+azure
  API version:       1.41
  Go version:        go1.13.15
  Git commit:        370c28948e3c12dce3d1df60b6f184990618553f
  Built:             Fri Apr  9 17:01:36 2021
  OS/Arch:           linux/amd64
  Context:           default
  Experimental:      true

- Server:
  Engine:
    Version:          20.10.6+azure
    API version:      1.41 (minimum version 1.12)
    Go version:       go1.13.15
    Git commit:       8728dd246c3ab53105434eef8ffe997b6fd14dc6
    Built:            Fri Apr  9 22:06:18 2021
    OS/Arch:          linux/amd64
    Experimental:     false
  containerd:
    Version:          1.4.6+azure
    GitCommit:        d71fcd7d8303cbf684402823e425e9dd2e99285d
  runc:
    Version:          1.0.0-rc95
    GitCommit:        b9ee9c6314599f1b4a7f497e1f1f856fe433d3b7
  docker-init:
    Version:          0.19.0
    GitCommit:

(I have already tried downgrading to moby-containerd=1.4.4+azure-1, but the error persists)
This is the error output:
docker: Error response from daemon: OCI runtime create failed: invalid mount {Destination:[ Type:bind Source:/var/lib/docker/volumes/361b5350807ea92c892fdc87e911040d484c24db5b72b74bf5a865374e416224/_data Options:[rbind]}: mount destination [ not absolute: unknown.
Error: Process completed with exit code 125.

The error is reproducible by running the following command in a GitHub workflow:
# Create configuration files
mkdir -p /tmp/config/
cat > /tmp/config/salt-api.conf <<EOF
external_auth:
  pam:
    salt_api:
      - .*
      - '@runner'
      - '@wheel'
      - '@jobs'
EOF

# Run test instance
docker run --rm --detach --name saltstack_master \
  --publish 4505:4505 --publish 4506:4506 --publish 8000:8000 \
  --env 'SALT_API_SERVICE_ENABLED=true' \
  --env 'SALT_API_USER_PASS=4wesome-Pass0rd' \
  --platform linux/amd64 \
  --volume /tmp/config:/home/salt/data/config:ro \
  cdalvaro/docker-salt-master:latest

# Wait for salt-master bootup
sleep 60

Hm... in your case, I wonder if you made a typo somewhere, or if some script produced an incorrect output;
mount destination [ not absolute

Seems to indicate you're attempting to mount to [ inside the container.

Hm... in your case, I wonder if you made a typo somewhere, or if some script produced an incorrect output;
mount destination [ not absolute

Seems to indicate you're attempting to mount to [ inside the container.

Thank you for your reply, @thaJeztah!
Initially, that was my first thought. But then I realized that these same settings were running well until a dependabot PR where checks began to fail. I haven't approved that PR yet, but checks are failing now in the main branch.

Yeah, it's definitely odd. The "source" of that mount (/var/lib/docker/volumes/361b5350807ea92c892fdc87e911040d484c24db5b72b74bf5a865374e416224/_data) looks like it's an "anonymous" volume (which would be if the container's image has a VOLUME specified). The error message is weird though, as it would mean that somehow the VOLUME definition in the image that's used has [ as target.
That could be if (e.g.) it was built from a Dockerfile that uses the JSON notation for volumes, something like:
VOLUME ["/some/path/", "/some-other/path/", "/yet/another/path/"]

If that JSON was invalid (e.g., using single quotes instead of double quotes, or a missing comma) during building the image, Docker will fallback to treating that JSON as a literal string (which would explain the error message).
Are you able to do a docker inspect of the cdalvaro/docker-salt-master:latest image and the container that was started?

I ran into the same mounting error after upgrading from 1.4.4-1 to 1.4.6-1.
Mine was indeed caused by an incorrect VOLUME declaration which worked before.
Before it was:
VOLUME [ ${DATA_DIR} ]

As the quotation marks are missing, this is an incorrect declaration of a JSON array. Changing it to the following (and removing stopped containers beofre running build) solved it:
VOLUME [ "${DATA_DIR}" ]

You are my hero @thaJeztah 🎉
By doing docker inspect cdalvaro/docker-salt-master:latest if seen two wrong volumes:
"Volumes": {
  "/home/salt/data/3pfs": {},
  "/home/salt/data/config": {},
  "/home/salt/data/keys": {},
  "/home/salt/data/logs": {},
  "/home/salt/data/srv": {},
  "[": {},
  "]": {}
},

I had a multiple directories VOLUME command without commas. I have separated those directories with commas and it has worked like a charm! (https://github.com/cdalvaro/docker-salt-master/pull/78/commits/7a03130ff544501cc04db967b2fb1060b2822425)
Thank you again for your help!

Looks like this is really a common problem with the mount volume while  using docker image by nginx
$docker run --name spa-web -v $(pwd):/usr/share/nginx/html:ro -d nginx
I have have similar issue with OCI runtime create failed: invalid mount while mounting  my mount file. I observed a new folder was created which is totally different from my current directory where my html files are..This is absolutely strange to me.

the spa was what i specified in my code while spa;C kept popping up after i run my command.
any  help would be greatly appreciated

Okay so i figured out a workaround. I changed my terminal and stopped using bash script in interi,m. So i tried powershell instead because of windows os. However, something changed. in my code, () now {}
$docker run --name spa-web -v ${pwd}:/usr/share/nginx/html:ro -d nginx

Downgrading worked for me, too.
That said, I wanted to elaborate on my specific scenario.
In my case I was reviving a script from 2019 that worked perfectly back then.
The first time the script worked fine. Then, when forcefully removing the container and re-creating it with the exact same script, I encountered the same error as @mesquita:
docker: Error response from daemon: OCI runtime create failed: invalid mount {Destination:: Type:bind Source:/var/lib/docker/volumes/9e1805936631f35e4895a18840a0f56c21669099b5967954b176585e9af7a2da/_data Options:[rbind]}: mount destination : not absolute: unknown.

It just wouldn't budge.
Downgrading "solved" it, for now.
Why did it work the first time, though?
That's another question that will hopefully be  answered when the real fix will have been implemented.

Why did it work the first time, though?

Hard to tell. If you have a link to the script, perhaps that provides more info as to what the script is doing (and why it failed)

@thaJeztah
The entire script consists of setting bash variables to passwords and paths for a docker run command. Once they are set, there is the docker run command.
So, there is absolutely nothing else in the script, besides the action of running a single Docker container.

@theAkito
I had the same issue
For some reason its got to do with the volume mount paths the docker-compose.yml, at least in my case. Either specify a volume or have a relative mount. Changing these paths fixed it for me and I did not need to downgrade the containerd, I couldn't figure out how to downgrade it on windows running docker desktop.  Perhaps this helps someone out.
services:
  frontend:
    build:
     context: ./frontend
     dockerfile: ./Docker/Dockerfile
    image: react_frontend_service
    container_name: frontend
    restart: always
   command: npm start
    volumes:
      - ./frontend/:/usr/src/app/ # it wants this
     - usr/src/app/ # it does not want this
    ports:
      - "8000:3000"
    env_file:
      - frontend/environments/.develpment.env
    depends_on:
      - postgres_database

 - usr/src/app/ # it does not want this

That line only has a single path, in which case it's considered the path inside the container to create a volume for.  When using the shorthand (-v <host-path or volume name>:<container-path>) syntax, if no host-path is specified, then an anonymous volume is created and mounted at <container-path> inside the container.
However, it looks like you specify two volumes/mounts for the same container path;

a bind-mount to mount your local ./frontend/ directory at /usr/src/app/ inside the container
an anonymous volume to also mount at /usr/src/app/ inside the container

I think this could potentially lead to a race-condition, where (depending on which mount gets mounted first), the bind-mount masking the content of the anonymous volume, or vice-versa.
Was is  intentional to have to mounts? I have a feeling only the first one is needed?

I've run into a similar problem with the latest version.
In my Dockerfile I have the following
VOLUME /path/to/dir # My Comment
When I try to start a container using that image, I get the following error:
OCI runtime create failed: invalid mount {
Destination:My
Type:bind
Source:/var/lib/docker/volumes/<long_hash_here>/_data Options:[rbind]
}: mount destination My not absolute: unknown

Note that it appears to be grabbing the first word of the comment "My" as part of the volume definition. This was not the case before the update. Moving the comment above the VOLUME line as depicted below resolved the error, but requiring such formatting contradicts my understanding of the documentation regarding Dockerfile comments https://docs.docker.com/engine/reference/builder/#format.
# My Comment
VOLUME /path/to/dir

Yes, The Dockerfile syntax only supports comments on their own line, and does not support trailing comments.

Docker treats lines that begin with # as a comment, unless the line is a valid parser directive.
A # marker anywhere else in a line is treated as an argument (...)

In case of VOLUME, the Dockerfile syntax allows multiple volumes to be defined in a single VOLUME instruction;
VOLUME /one /two /three

So what happens if you add the trailing comment;
VOLUME /path/to/dir # My Comment

Is that it defines four volumes: /path/to/dir, #, My, and Comment; # is a valid name for a Directory on Linux, so it's valid as a mount-point as well for a volume.
You can see this when building an image;
FROM busybox
VOLUME /path/to/dir # My Comment

Then, inspecting the image, you can see the 4 volumes in the configuration:
DOCKER_BUILDKIT=1 docker build -t myimage .
docker image inspect --format '{{json .Config.Volumes}}' myimage
{"#":{},"/path/to/dir":{},"Comment":{},"My":{}}

Just to add to the fray, the update also affected me. I don't doubt that the error is on my part, but so far I just haven't had the time to spend more time than I already have troubleshooting this particular minor app. It worked fine until one day my dev server crashed with about 10 apps on it (unattended upgrades had updated containderd.io which broke the app and caused nginx to panic since it could no longer find the crashed app) but it sounds like the upgrade isn't to blame... just that it now enforces proper syntax, which should have probably failed before.

This issue should be fixed by https://github.com/opencontainers/runc/pull/3004, which relaxed the validation in runc, and is part of runc v1.0.0, which is included in containerd v1.5.3 (and up) and containerd v1.4.7 (and up).

Building this Dockerfile on the latest Docker 3.5.2 mac Os also shows the problem. Is this fixed on mac ?

ARG IMAGE_TAG="undefined"

RUN apt-get update && apt-get install -y jq vim

VOLUME [ /usr/src ]
WORKDIR /usr/src
CMD [ "bash" ]

#COPY content /opt/
RUN { \
  set -vx; \
  echo "done"; \
}

build command
docker build -t test-docker .
result
...
Removing intermediate container 8ac750f81f58
 ---> f35985ea2242
Step 4/7 : VOLUME [ /usr/src ]
 ---> Running in a7f9b7cfdd1f
Removing intermediate container a7f9b7cfdd1f
 ---> 884b15bc5c03
Step 5/7 : WORKDIR /usr/src
 ---> Running in 9a499880fb40
Removing intermediate container 9a499880fb40
 ---> d85cdfeb5a16
Step 6/7 : CMD [ "bash" ]
 ---> Running in 2145cb2fb967
Removing intermediate container 2145cb2fb967
 ---> ef3b45f40dee
Step 7/7 : RUN {   set -vx;   echo "done"; }
 ---> Running in ca93d27d5241
OCI runtime create failed: invalid mount {Destination:[ Type:bind Source:/var/lib/docker/volumes/77f6f42bf4284e2ad943b57cc4d6abd87ea8fb91b0e58f97df2e27b733c4cc4c/_data Options:[rbind]}: mount destination [ not absolute: unknown```

Upcoming patch release of Docker Desktop will include runc v1.0.0
But in your case looks like there's a mistake in your Dockerfile;
VOLUME [ /usr/src ]

Is not valid JSON, so will create 3 volumes: [, /usr/src, and ]
Change it to:
VOLUME ["/usr/src"]

(with quotes)
or
VOLUME /usr/src

Tested and it works

Downgrading worked for me, too.
That said, I wanted to elaborate on my specific scenario.
In my case I was reviving a script from 2019 that worked perfectly back then.
The first time the script worked fine. Then, when forcefully removing the container and re-creating it with the exact same script, I encountered the same error as @mesquita:
docker: Error response from daemon: OCI runtime create failed: invalid mount {Destination:: Type:bind Source:/var/lib/docker/volumes/9e1805936631f35e4895a18840a0f56c21669099b5967954b176585e9af7a2da/_data Options:[rbind]}: mount destination : not absolute: unknown.

It just wouldn't budge.
Downgrading "solved" it, for now.
Why did it work the first time, though?
That's another question that will hopefully be answered when the real fix will have been implemented.

Hi @theAkito, did you figure out why it worked at the first time. I also faced the same issue. I could run a container without any issue at the first time. After a while I tried to restart the container, then it showed the invalid mount error. The error is expected since I use the 1.4.6-1 containerd. But I couldn't figure out why it worked at the first time.

@yanjunli76
I'm sorry, didn't figure it out and I doubt I will be able to.


Optimise allowance storage slots

Store allowances in slot sha3(from, to) to save gas on 2D mapping calculations.

Completed in commit 3dbc066
allowance(address from, address to) is now stored at storage slot keccak256(to . from) where . is concatenation.


Counters have absurd values

When using this library, I've noticed a problem.
When I start a counter, I get a _total and a _sum object. The sum always seems to end up at some absurdly high value.
(Note - code taken from my bot, which is functionally the same as this)
ON_INTERACTION_COUNTER = Counter(
    METRIC_PREFIX + 'event_on_interaction',
    'Amount of interactions called by users',
    ['shard', 'interaction', 'command'],
)

In this example, the counter always starts at something crazy like<PHONE_NUMBER>.937016.
To counter this, I get the rate :
sum by (command) (increase(max_over_time(prod_storybot_event_on_interaction_total{job="$job",command!="None"}[$__range])[$__range:]))

But this causes the query to go slow and time out.
I think this might be a bug in the client library, but I just wanted to check

Can you show the result of this promql query? I'm wondering which interaction type is influencing this counter the most.
sum(discord_event_on_interaction_total) by (interaction)

Odd... since last boot, it seems like I'm getting normal values:
sum(prod_storybot_event_on_interaction_total) by (interaction)

I'm not sure why - usually, the counters will have crazy values. I'm not sure why it seems to be working now.
I guess I'll close this for now, but reopen when I see this issue again?


crate-private trait FloatLike in public interface (v0.2.0)

Me again! The 0.2.0 release introduces a bug:
error[E0445]: crate-private trait `FloatLike` in public interface
  --> /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pco-0.2.0/src/float_mult_utils.rs:9:1
   |
9  |   pub fn join_latents<F: FloatLike>(base: F, primary: &mut [F::L], secondary: &[F::L]) {
   |   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ can't leak crate-private trait
   |
  ::: /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pco-0.2.0/src/data_types/mod.rs:20:1
   |
20 | / pub(crate) trait FloatLike:
21 | |   Add<Output = Self>
22 | |   + AddAssign
23 | |   + Copy
...  |
33 | |   + SubAssign
34 | |   + Div<Output = Self>
   | |______________________- `FloatLike` declared as crate-private

Relevant CI run triggering this issue:
https://github.com/LDeakin/zarrs/actions/runs/8367021385/job/22908525341?pr=15

I think this is actually a bug in older versions of cargo - the join_latents function is crate-private. Are you able to rustup to a newer version?

Yeah, looks like the minimum Rust version should really be 1.74. I suppose it wasn't a bug per se, but a change in the language: https://rust-lang.github.io/rfcs/2145-type-privacy.html

Well that's annoying, but I just published another version (0.2.1) that should work in 1.73.


[stable/jenkins] How to create new users

Is this a request for help?: Yes
Version of Helm and Kubernetes:
$ helm version
Client: &version.Version{SemVer:"v2.11.0", GitCommit:"2e55dbe1fdb5fdb96b75ff144a339489417b146b", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.11.0", GitCommit:"2e55dbe1fdb5fdb96b75ff144a339489417b146b", GitTreeState:"clean"}
$ kubectl version
Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.11", GitCommit:"637c7e288581ee40ab4ca210618a89a555b6e7e9", GitTreeState:"clean", BuildDate:"2018-11-26T14:38:32Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"10+", GitVersion:"v1.10.13-eks-g484b8", GitCommit:"484b857e3134d55ac6373fea2f51798fefa0533f", GitTreeState:"clean", BuildDate:"2019-03-08T05:32:36Z", GoVersion:"go1.10.8", Compiler:"gc", Platform:"linux/amd64"}
Which chart:
[stable/jenkins]
Chart version reported by helm list: jenkins-0.36.0
What happened:
I am able to log in to jenkins as user admin (I get get the password via kubectl get secret).
I would like to configure new, non-admin users in order to then apply Role-Based Strategy security.
The Security realm option is set to Delegate to servlet container
How do I add users when this setting is active?
PS: I have tried selecting "Jenkins' own user database" but that kicks me out of the server and I can't log in any more.

That is a good question. I don't think that the chart currently supports this use case.
Will you not prefer (if possible of course) to delegate authentication to github/gitlab/other where you manage your code?

At the moment it says "delegate to servlet container" so I was wondering if that "fetched" users from the underlying Kubernetes cluster.
The gitlab/github option is interesting.

I encourage you to go ahead and submit a PR if you like ;)
And that it a super cool plugin, didn't know it!

Were you able to find a solution for this? I'm looking for the same

I am testing the GitLab authentication plugin.

At the moment it says "delegate to servlet container" so I was wondering if that "fetched" users from the underlying Kubernetes cluster.
On second look it seems this plugin is a good answer to that question: https://jenkinsci.github.io/kubernetes-credentials-provider-plugin/
For gitlab there's the gitLab authentication plugin.
I am starting to see an answer to my own question: the chart is only responsible for bootstrapping the Jenkins server with an admin account.
Auth/Authz is down to user preferences by using available plugins to integrate with auth providers.
The only thing I would document is that if you switch to "Jenkins's own internal database" you lock yourself out because by default that db is not initialised.

@marcelloromani how did manage to manage your users auth using the kubernetes-credentials-provider-plugin? I am running Jenkins on GKE (using the stable/jenkins chart).  I couldn't find the plugin, I am running Jenkins 2.176.2.  Feedback is appreciated!

Hi @leonyi
we eventually installed the GitLab plugin and configured it to delegate authentication to GitLab.
I have not had time to work with the k8s credentials plugin since, sorry :)

You can install Role-based Authorization Strategy plugin and activate jenkins db users (realms) + Role-Based Strategy (authentication).
This steps allowed me to create new admin user and other users.


docs/Homebrew-Governance: Schultz Condorcet aka Beatpath

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.
[ ] Have you successfully run brew style with your changes locally?
[ ] Have you successfully run brew typecheck with your changes locally?
[ ] Have you successfully run brew tests with your changes locally?

I tried to set up the Project Leader election in OpaVote and couldn't find "Schultz Condorcet" in the list of methods. Let's save the next person who does this a click by specifying its alternative name that is in OpaVote, "beatpath".

Review period will end on 2022-03-23 at 22:24:03 UTC.

Review period ended.


pam_python.so missing on Fedora

I'm using howdy from copr from @luyatshimbalanga and I was able to get it running with some minor patches but I've now discovered that fedora is simply missing pam_python.so
I would appreciate if you could provide the missing pam_python library in the copr repo.
Linux distribution (if applicable): Fedora 32
Howdy version: 2.6.0

pam_python is already packaged on https://copr.fedorainfracloud.org/coprs/anaumov/pam-python/.
What will be great is pam_python.so getting ported to python 3 instead. See the review process on https://bugzilla.redhat.com/show_bug.cgi?id=1641386

Thanks for your response. It would probably be wise to add that info to the fedora install instructions. Unfortunately, I struggle to enable that package. Do you know any workarounds?
sudo dnf copr enable anaumov/pam-python
[...]
Error: This repository does not have any builds yet so you cannot enable it now.

I ran into the same issue, but managed to get pam_python on fedora using the rpm sphere repo, however now instead I get an error about the dlib module not being found... despite installing manually / with pip2 / pip3, etc., which is strange considering it loads correctly from a python shell (both 2 and 3).

dlib is packaged with the copr repo. try installing python3-dlib from the repo instead of pip. when you do install dlib via pip from as your user, it will only be available for that user but howdy is run as root so it won't be able to find that version of dlib.

Tried installing python3-dlib from the repo, but now i get the error
No module named '_dlib_pybind11'

Can't import the dlib module, check the output of
pip3 show dlib

and they can't be found by the python shells despite being reported working by pip and being installed in the correct locations, /usr/lib64/python3.8/site-packages that is.
Having dlib installed using sudo pip3 install dlib is the way I had it set up before and results in howdy working however whenever a sign in is initiated I get the error
Traceback (most recent call last):
  File "/lib64/security/howdy/compare.py", line 18, in <module>
    import dlib
ModuleNotFoundError: No module named 'dlib'
Unknown error: 1

And again, it works in the python shell.

@LukaJankovic I've created my own builds because of this (and other problems). Maybe it'll will solve your problems https://copr.fedorainfracloud.org/coprs/principis/howdy/

@principis Thanks for your copr repo; do you plan to update it for Fedora 33? It's not installing for me on Fedora 33. I also tried compiling myself, and while howdy works for me, pam_python does not (I get a segmentation fault when trying to run it after compiling it myself). Any clues?

@dbdorman I'll look into it

@principis Thanks, I was able to install from your copr build, but still getting a segmentation fault when executing pam_python, so must be something with my system. I'll try debugging

So what is the result  of everything that ?

So what is the result of everything that ?

Could you please elaborate?

@principis
https://github.com/rpmsphere/spec/pull/4
But I don't know how to add .patch there. I managed to compile it for Fedora39, but did not test yet.

@principis rpmsphere/spec#4 But I don't know how to add .patch there. I managed to compile it for Fedora39 (i.e. Python 3.12), but did not test yet.

I have no idea what you are trying to accomplish. I have packaged howdy here, which should work fine.


Unable to read variant when default initialized to different variant index

The following code:
#include <iostream>
#include <variant>
#include <glaze/glaze.hpp>

using var = std::variant<std::string, int, double>;

struct my_struct {
  var val{1};
};

int main() {
  my_struct st1{"hello world"};

  std::string buffer = glz::write_json(st1);
  buffer = glz::prettify(buffer);
  std::cout << buffer << std::endl;

  my_struct st2;
  auto pe = glz::read_json(st2, buffer);
  std::string descriptive_error = glz::format_error(pe, buffer);
  std::cout << descriptive_error << std::endl;
}

gives an error on read_json; it prints
{
   "val": "hello world"
}
2:11: parse_number_failure
      "val": "hello world"
             ^

It seems that it fails whenever val is default-initialized to a different type than st1 is initialized to later.
Also, when the variant no longer includes double (i.e. using var = std::variant<std::string, int>), then val can be safely reassigned from an int to a string and vice versa without issue.

Yes, this is a known limitation to automatic variant deduction, because the JSON specification treats all numeric values as the same. So, by including both int and double you are making your variant not auto-deducible. See documentation
We could add support for partial automatic deduction for your string type in this case, but it makes things more confusing for users if only some types will be deduced.
You could only include double in your variant and then cast this to an int when you want an int. Or, you can use tags for your variants (see documentation.
If automatic deduction is not possible for your type combination then the variant will attempt a load into the active state, which in your example is an integer, which is why you get a parse_number_failure error.
I hope this makes sense. And, please add your thoughts if you think there's a good solution to this.


Implement state control for the program

Implement the state control for the program to navigate Employee, Member, Menu, Order functionalities. The command word for these states can be changed to be easier to understand.

Close due to conflict with another issue


Restrict d keybinding to queue list

Block ability to delete items from  downloading and done list

Fix in https://github.com/jim-at-jibba/telecharger/releases/tag/v0.0.4


SRV-I-9: checkClaimKeyBan()/deleteOld* doesn't work outside UTC

Analysis of the Issue
During code review of ../covid-shield-server/blob/deploy_tf/pkg/persistence/queries.go#L346.
checkClaimKeyBan() gets the time of the last failure from the DB and subtracts it from the remaining ban duration. However, this only works if the local time is set to UTC.
The value is previously stored in the DB via mysql NOW(), which stores the time in local time. When it is read back, because the timestamp does not contain timezone info, q.Scan() assumes UTC. This causes the elapsed duration to be very large (if negative offset timezone), never causing a ban, or very negative (positive offset timezone), causing a much longer ban than expected.
I suspect other functions using stored timestamps behave similarly.
This behavior may be expected if setting clocks to UTC is a requirement of the running environment, but it's not documented anywhere.
Recommendation
Provide clarification on expected behaviour and requirement on setting clocks to UTC.

Working as expected, could not repro


Publishing MSIX SDK 1.6

Add IAppx*Utf8 variants for AppxPackaging APIs. Allow overriding language package selection via IMsixApplicabilityLanguagesEnumerator. Support paths and packages with international characters. Update OpenSSL to 1.0.2q. Bugs fixes.

looks good.


Remove unwanted String.prototype extensions

closes https://github.com/TryGhost/Ghost/issues/8958

markdown-it-named-headers pulled in string.js despite it not being used which added a lot of String.prototype extensions and caused Ember deprecation notices
moves the short markdown-it-named-headers functionality directly into our app code without using String.js

Coverage decreased (-0.1%) to 72.288% when pulling 2f26512b3188adceb28b04c4b4ac70519294f576 on kevinansfield:custom-markdown-it-named-headers into 87449ebb803b436db4042ebd896ff208d2675f5a on TryGhost:master.

LGTM 👍


chore: Remove NOT NULL constraint for github_id in user table

I made changes in the other examples as well, removing the NOT NULL

#41

Thank you!


'unavailable' event never called

First, thank's for your work.
With the miio.devices() example, the 'unavailable' event is never called for a xiaomi philips bulb.
The 'unavailable' event is correctly raised by tinkerhub-discovery/lib/basic.js(105)...

Fixed in the last release.  I don't know how...

@thunderace, @aholstenson - please. reopen this one. I'm having same problem with Air Purifier 2. Tinkerhub emits event, but it does not go up to the miio.devices().


updated linker

Notified by johnboy14 in public chat that this has changed

I think it's the wrong place to change the settings. The updated variable is using partials, which are pulled from config/dictionaries. There it needs to be updated at the applicable devices.

LGTM


rate limits with websockets?

Will rate limits also work when using websockets?

Let's move this discussion to discuss.istio.io, as that is a more appropriate forum for questions.
/cc @gargnupur


OpenType SVG fonts open slowly in Fedora 39 Linux

I downloaded the Noto Color Emoji fonts from Google website.
URL: https://fonts.google.com/noto/specimen/Noto+Color+Emoji?query=emoji
I check this font with ttx, it contains the SVG table inside the font.
SVG   0x8EA0F1D5  19252109   4763880
It seems this is an OpenType SVG font.
It takes several minutes to open this font with gnome-font-viewer.
I rebuilt ftview with librsvg, ftview also takes several minutes to open this font.
Why does it take several minutes to open the OpenType SVG font?

Well, quite simply because it's huge and the font viewer is probably trying to load all the thousands of emoji glyphs all at once. I'm not sure there is much we can do.

Ideally use the COLRv1 font (present in this repo under /fonts, see https://developer.chrome.com/blog/colrv1-fonts for context). That require that gnome-font-viewer and ftview support COLRv1; I'm not sure whether they do.
I don't think there is anything to be changed in this repo so closing.