Failed to update/install with composer

After fetching last changes from https://github.com/symfony/symfony-standard, I installed composer and tried to update/install vendors. Here are results/errors
php composer.phar update
...
[RuntimeException]
  Failed to execute git clone 'https://github.com/symfony/SwiftmailerBridge' '/home/umpirsky/Projects/PHP/symfony-standard.loc/vendor/symfony/swiftmailer-bridge/Symfony/Bridge/Swiftmailer' && cd '/home/umpirsky/Projects/PHP/symfony-standard.loc/vendor/symfony/swiftmailer-bridge/Symfony/Bridge/Swiftmailer' && git checkout '23b8d5c049bb3dfb67ec04bbea09464da27c4ec7' && git reset --hard '23b8d5c049bb3dfb67ec04bbea09464da27c4ec7'

php composer.phar install
...
 [RuntimeException]
  Failed to execute git clone 'https://github.com/fabpot/Twig-extensions' '/home/umpirsky/Projects/PHP/symfony-standard.loc/vendor/twig/extensions' && cd '/home/umpirsky/Projects/PHP/symfony-standard.loc/vendor/twig/extensions' && git checkout '1dfff8e793f50f651c4f74f796c2c68a4aee3147' && git reset --hard '1dfff8e793f50f651c4f74f796c2c68a4aee3147'

Update: here is a complete trace:
Exception trace:
 () at phar:///home/umpirsky/Projects/PHP/symfony-standard.loc/composer.phar/src/Composer/Downloader/GitDownloader.php:2
 Composer\Downloader\GitDownloader->doDownload() at phar:///home/umpirsky/Projects/PHP/symfony-standard.loc/composer.phar/src/Composer/Downloader/VcsDownloader.php:2
 Composer\Downloader\VcsDownloader->download() at phar:///home/umpirsky/Projects/PHP/symfony-standard.loc/composer.phar/src/Composer/Downloader/DownloadManager.php:2
 Composer\Downloader\DownloadManager->download() at phar:///home/umpirsky/Projects/PHP/symfony-standard.loc/composer.phar/src/Composer/Installer/LibraryInstaller.php:2
 Composer\Installer\LibraryInstaller->install() at phar:///home/umpirsky/Projects/PHP/symfony-standard.loc/composer.phar/src/Composer/Installer/InstallationManager.php:2
 Composer\Installer\InstallationManager->install() at phar:///home/umpirsky/Projects/PHP/symfony-standard.loc/composer.phar/src/Composer/Installer/InstallationManager.php:2
 Composer\Installer\InstallationManager->execute() at phar:///home/umpirsky/Projects/PHP/symfony-standard.loc/composer.phar/src/Composer/Command/InstallCommand.php:10
 Composer\Command\InstallCommand->install() at phar:///home/umpirsky/Projects/PHP/symfony-standard.loc/composer.phar/src/Composer/Command/UpdateCommand.php:10
 Composer\Command\UpdateCommand->execute() at phar:///home/umpirsky/Projects/PHP/symfony-standard.loc/composer.phar/vendor/symfony/console/Symfony/Component/Console/Command/Command.php:2
 Symfony\Component\Console\Command\Command->run() at phar:///home/umpirsky/Projects/PHP/symfony-standard.loc/composer.phar/vendor/symfony/console/Symfony/Component/Console/Application.php:2
 Symfony\Component\Console\Application->doRun() at phar:///home/umpirsky/Projects/PHP/symfony-standard.loc/composer.phar/src/Composer/Console/Application.php:2
 Composer\Console\Application->doRun() at phar:///home/umpirsky/Projects/PHP/symfony-standard.loc/composer.phar/vendor/symfony/console/Symfony/Component/Console/Application.php:2
 Symfony\Component\Console\Application->run() at phar:///home/umpirsky/Projects/PHP/symfony-standard.loc/composer.phar/src/Composer/Console/Application.php:2
 Composer\Console\Application->run() at phar:///home/umpirsky/Projects/PHP/symfony-standard.loc/composer.phar/bin/composer:13
 require() at /home/umpirsky/Projects/PHP/symfony-standard.loc/composer.phar:15
...

$ rm -fr vendor && composer.phar install -v
Installing from lock file
Your lock file is out of sync with your composer.json, run "composer.phar update" to update dependencies
Installing twig/twig (1.6.0)
  - Package twig/twig (1.6.0)
    Downloading
    Unpacking archive
    Cleaning up

Installing twig/extensions (dev-master)
  - Package twig/extensions (dev-master)
    Cloning 1dfff8e793f50f651c4f74f796c2c68a4aee3147

Installing symfony/symfony (2.1-dev)
  - Package symfony/symfony (dev-master)
    Cloning 3de31c62d6d695477803d797177fbfe2a2fa3ef5

  [RuntimeException]
  Failed to execute git clone "git://github.com/symfony/symfony.git" "C:\wamp\www\scpsf\vendor/symfony/symfony" && cd "C:\wamp\www\scpsf\vendor/symfony/symfony" && git checkout "3de31c62d6d695477803d797177fbfe2a2fa3ef5" && git reset --hard "3de31c62d6d695477803d797177fbfe2a2fa3ef5"

Exception trace:
 () at phar://C:/wamp/www/scpsf/composer.phar/src/Composer/Downloader/GitDownloader.php:2
 Composer\Downloader\GitDownloader->doDownload() at phar://C:/wamp/www/scpsf/composer.phar/src/Composer/Downloader/VcsDownloader.php:2
 Composer\Downloader\VcsDownloader->download() at phar://C:/wamp/www/scpsf/composer.phar/src/Composer/Downloader/DownloadManager.php:2
 Composer\Downloader\DownloadManager->download() at phar://C:/wamp/www/scpsf/composer.phar/src/Composer/Installer/LibraryInstaller.php:2
 Composer\Installer\LibraryInstaller->install() at phar://C:/wamp/www/scpsf/composer.phar/src/Composer/Installer/InstallationManager.php:2
 Composer\Installer\InstallationManager->install() at phar://C:/wamp/www/scpsf/composer.phar/src/Composer/Installer/InstallationManager.php:2
 Composer\Installer\InstallationManager->execute() at phar://C:/wamp/www/scpsf/composer.phar/src/Composer/Command/InstallCommand.php:10
 Composer\Command\InstallCommand->install() at phar://C:/wamp/www/scpsf/composer.phar/src/Composer/Command/InstallCommand.php:10
 Composer\Command\InstallCommand->execute() at phar://C:/wamp/www/scpsf/composer.phar/vendor/symfony/console/Symfony/Component/Console/Command/Command.php:2
 Symfony\Component\Console\Command\Command->run() at phar://C:/wamp/www/scpsf/composer.phar/vendor/symfony/console/Symfony/Component/Console/Application.php:2
 Symfony\Component\Console\Application->doRun() at phar://C:/wamp/www/scpsf/composer.phar/src/Composer/Console/Application.php:2
 Composer\Console\Application->doRun() at phar://C:/wamp/www/scpsf/composer.phar/vendor/symfony/console/Symfony/Component/Console/Application.php:2
 Symfony\Component\Console\Application->run() at phar://C:/wamp/www/scpsf/composer.phar/src/Composer/Console/Application.php:2
 Composer\Console\Application->run() at phar://C:/wamp/www/scpsf/composer.phar/bin/composer:13
 require() at C:\wamp\www\scpsf\composer.phar:15

install [--prefer-source] [--dry-run] [--no-install-recommends] [--install-suggests]

I'm resetting to 32a0f51d57ffce342e67b4e501ae155e4732adbe .
Please tell us when you find a solution :D

@Dentxinho I actually managed to install vendors with composer, but after zillion retries and failures. I guess I was just lucky enough.

I cant stand with 32a0f51d57ffce342e67b4e501ae155e4732adbe. Sensio/SensioDistributionBundle tree follows symfony/symfony-standard tree, and doesn't have build_bootstrap anymore.
I'll wait for a solution.

I have a similar problem(

Same problem here as well.
While Composer is a good idea it could have been introduced in 2.1 then promoted in 2.2 as the only upgrade way.

@dlsniper Composer has always been meant to be used for Symfony. The only reason we have the deps file in 2.0 is that it was not ready.

@stof I do understand this but then again, if Composer becomes mainstream, it should first work. Right now, I can't install anything from my computer because I'm getting:

florin@monzi7:/var/www/ss$ php composer.phar install
Installing from lock file
Your lock file is out of sync with your composer.json, run "composer.phar update" to update dependencies
  - Package twig/twig (1.6.0)
    Downloading
    Unpacking archive
    Cleaning up

  - Package twig/extensions (dev-master)
    Cloning 1dfff8e793f50f651c4f74f796c2c68a4aee3147

  [RuntimeException]
  Failed to execute git clone 'https://github.com/fabpot/Twig-extensions' '/var/www/ss/vendor/twig/extensions' && cd '/var/www/ss/vendor/twig/extensions' && git checkout '1dfff8e793f50f651c4f74f796c2c68a4aee3147' && git reset --hard '1dfff8e793f50f651c4f74f796c2c68a4aee3147'
                                                                                ```

I do acknowledge that it would be nice for people to do more work on it but right now you've forced me to revert a commit in order to be able to start any type of development for the 2.1 branch. I have no issue in using it as long as I have a backup that I can use in case I want to install/update symfony2.1.

Thanks

well, first, you should follow the advice of the method and run the update command as you changed your composer.json since the last time you used it.

I've did:
composer.phar self-update
composer.phar update
composer.phar install
cloned the symfony-standard repository again
The thing is that I can't just make it work and do a complete install from top to bottom using Composer. Is there any way to use git:// instead of http:// or https:// ?
Thanks

I'm also seeing issues with composer. I just tried again with a 100% fresh install.

Clone symfony
Install composer.phar
Attempt to install vendors, get a failure:

Other info:
[bsd mbadolato ~ master]$ php --version
PHP 5.3.10 with Suhosin-Patch (cli) (built: Feb 14 2012 16:46:36)
Copyright (c) 1997-2012 The PHP Group
Zend Engine v2.3.0, Copyright (c) 1998-2012 Zend Technologies
with Xdebug v2.1.3, Copyright (c) 2002-2012, by Derick Rethans
[bsd mbadolato ~ master]$ uname -a
FreeBSD home 9.0-RELEASE FreeBSD 9.0-RELEASE #8: Sat Jan 14 22:27:39 MST 2012     root@home:/usr/obj/usr/src/sys/BSD  amd64
print_r(get_loaded_extensions());
Array
(
[0] => Core
[1] => date
[2] => ereg
[3] => libxml
[4] => pcre
[5] => Reflection
[6] => SPL
[7] => hash
[8] => session
[9] => apc
[10] => intl
[11] => json
[12] => xml
[13] => zlib
[14] => PDO
[15] => iconv
[16] => tokenizer
[17] => pdo_sqlite
[18] => pdo_pgsql
[19] => dom
[20] => posix
[21] => standard
[22] => mysqlnd
[23] => curl
[24] => pgsql
[25] => SimpleXML
[26] => mbstring
[27] => ctype
[28] => memcache
[29] => Phar
[30] => mhash
[31] => xdebug
)

@fabpot Wouldn't it be a better idea to ask all the people using Symfony2.1 to start using Composer more that until now but also revert and keep the old ways of installing/updating? You could post a message on the blog, make a better and a 'call to use' or something, but this is rather annoying and you can only imagine who a new user feels after experiencing this.
I was trying to find a bug in the caching mechanism of Symfony2.1 and Doctrine2.2 but then again, I can't install neither of them with composer so that I can have a clean instance and work at least on reproducing the issue and creating a report in the right place but I gave up 3 days already as I'd expect things to just work when I'm installing a framework.

I'd have to agree with @dlsniper in that we should probably have both deps and composer solutions in place for the time being, until any kinks are worked out.
The issue I posted above appears to be more of a composer issue (I have not attempted to resolve yet), but still. It's the most rudimentary of commands that I did (literally the main/basic path through the use case), and if those are failing for me, then surely others will run into issues as well.
cc: @fabpot

@mbadolato seems like you don't have the filter_var function in your code. Are you using a custom build of PHP ? this function is available by default

@stof Nope, standard install (from source) on FreeBSD. It's possible that filter_var is part of a php module that's not compiled in by default. I can check.

Found a security port: /usr/ports/security/php5-filter
Installing gave me the filter.so extension.  That indeed was the issue.
I noticed this similar issues when initially setting up this box, i.e., I had to install various php modules that aren't necessarily part of the Symfony requirements check. I had all of the modules that Symfony appeared to require, yet the check.php would fail until I got other modules in, like dom and one of the XML classes beyond what was being checked for (I can't recall off the top of my head). I guess the base install on FreeBSD does not have certain modules by default, as opposed to what the packages for some of the Linux distos have.
I think what I need to do is start with a clean box and determine exactly which modules were needed and submit a patch to the check scripts to encompass the full gamut of requirements.
Thanks for the suggestion of where to look, @stof.  I'm still receiving a Runtime Exception when trying to get at some of the vendors, but I'll troubleshoot that when I'm home tonight.

Here's a log of what I'm doing right after a git pull in the symfony-standard directory:  http://pastebin.com/kL3gpnbc
How can I debug this?

I'm going to throw my two cents in right now... I haven't tried composer, but I've followed other people's problems and they all seem to be close to the same.
Currently, in production I rely on github (which is actually a terrible move especially after the DDoS attacks).  I was in need of booting another app server and I couldn't get my application to work until I switched the deps file to use the git protocol... it seems as if composer relies on whatever the repository owner specified the repo url (which can bite someone in the ass if SF2 is to rely on github for a lot of things)
So far, it looks cool and everything... but just scary.
Github even emailed me to ask me what IPs I'm using to get them whitelisted, but on AWS, app server ips always change...  so i'll probably be going back to compressing my app then syncing them to app servers.
Anyway, I hope composer starts to look up if it's the future.
Also, I utilize many private repositories... does composer even allow for that?

@dlsniper That's the same Runtime error I saw. I deleted the partial Vendors directory I had, deleted the composer.lock file out of my Symfony root, ran the install command again and it worked

@dlsniper, yep, i agree with you.  i was just explaining that github isn't fullproof... and currently their http(s) protocols are buggy.  They literally physically emailed me for my ips to whitelist me so I was able to clone all repos necessary for my production application servers...
for example, travisci was blacklisted which caused FOSUserBundle to change their protocol: https://github.com/FriendsOfSymfony/FOSUserBundle/blob/master/vendor/vendors.php which will work until they block git also.
Moral of the storyremote code hosting isn't really a complete fullproof way.
I just know that currently, git protocol is working on my app servers whereas http was giving me the same errors you're getting.

@jstout24 the command working when running it directly, the issue is when using the composer.phar install command.

I have some random composer errors too.

@nostrzak some of the github servers are down currently

I ran into this problem and fixed by running the install command after running
composer update
which allowed my composer install  to finally complete successfully.
Smooth ride from there, finally.

FYI if you are running PHP7, then try running composer.phar with PHP56
php56 composer.phar update


RuntimeError: Error(s) in loading state_dict for LatentDiffusion

dear guys:
when i change model to sdxl, i got error below
raise RuntimeError('Error(s) in loading state_dict for {}:\n\t{}'.format(
RuntimeError: Error(s) in loading state_dict for LatentDiffusion:
size mismatch for model.diffusion_model.time_embed.0.weight: copying a param with shape torch.Size([1536, 384]) from checkpoint, the shape in current model is torch.Size([1280, 320])
………………………………………………………………
how can I resolve this problem?

same

same

Yo! Same error and I've copied the latest YAML files for Base & Refiner. Using RunPod. Thoughts?

same

same

Anyone here solved it yet? Thank you!


Rails 5.2 support

Just curious where there's any progress on Rails 5.2 support, maybe a branch I can try?
I tried out neo4jrb + 5.2 briefly when rc1 came out, and again for rc2, but it is sadly still unusable. I tried cloning this repo and running the specs to see if there might be some kind of quick and easy fix, but I get thousands of spec failures, most of which are either NoMethodError: undefined method 'changed?' for nil:NilClass or Neo.ClientError.Transaction.TransactionNotFound: Unrecognized transaction id. Transaction may have timed out and been rolled back. It seems like something is amiss with constraints, but it doesn't seem to be something obvious enough for me to be able to fix on my own...

@anamba Thanks for the report!
I've not been trying the Neo4j.rb gems with Rails 5.2 and haven't seen any reports yet, so any information that you can provide would be helpful.  Could you provide a full backtrace for the error(s) you are getting and perhaps some sample code for an example of where it's occurring?
If you don't want to post your code publicly you could share a private gist URL with me via the form on the Neo4j.rb homepage
Thanks again

Here's what I did yesterday to check for Rails 5.2 support (if I did it today it would be different, since 5.2.0 is out now).
First, I cloned this repo, did a bundle install and rspec. Bundler installed activemodel/activesupport/railties 5.1.6 and all specs passed. (If I did this now, it would install 5.2.0).
Next, I updated neo4j.gemspec to specify 5.2.0.rc2 for activemodel/activesupport/railties and ran bundle update, then ran rspec again. This time, most of the specs failed (1601 examples, 1224 failures, 2 pending).

Hrmm, you shouldn't need to check out the repo and change the gemspec.  Do you mean that you ran the tests inside of the neo4j gem repo, or the tests inside of your project pointing to your checked out repo?
The neo4j.gemspec file is what helps build the gem for people to use.  So the activemodel and activesupport dependencies inside of the neo4j.gemspec should stay as '>= 4.0' because that means that the neo4j gem will require at least version 4.0.0 of those gems but it will also support version 5.x.y, 6.x.y, etc... (though, of course, we don't know if there will be problems with Rails 6.0 until it comes out).
If you're trying to run the tests in this repo locally (and I'll try to do this now), the neo4j.gemspec should stay the same and you should do bundle update activemodel activerecord to see if the gem is compatible with the latest versions of those gems (the Gemfile has a gemspec declaration which causes it to use the dependencies from the neo4j.gemspec file and the Gemfile.lock will hold whatever specific version of the gem you're trying to use right now)

Oh, also, if you're running the neo4j repo specs, you'll need to have a version of Neo4j running and a NEO4J_URL environment variable set to point to it (beware that it will wipe the database, including indexes and constraints)

Looks like you need to run bundle update activemodel activesupport railties because railties is tied up in there too

Wow, ok, after all that I can confirm that it's working for me in 5.1.x but not 5.2.x.  I'll take a look, thanks ;)

Yup, failing on CI too.  I just re-ran one of the tasks now that 5.2.0 is out (CI will automatically pull in the latest):
https://travis-ci.org/neo4jrb/neo4j/jobs/360924370

😞 it looks like activemodel 5.2 refactors attributes, either to use something new or to use something that was already there.  But I think that some of the creakier parts of the ActiveNode code are breaking with the change.  I made a branch with some of the fixes that I've made so far.  Currently the problem is that it doesn't seem to like it when you assign things to the underlying @attributes instance variable that aren't objects like ActiveModel::Attribute::FromUser or ActiveModel::Attribute::FromDatabase and the code is just assigning a string for the uuid.  This also goes to the fact that there have been various requests to make the default uuid id_property just an attribute like everything else, so now might be a good time.  But it would probably take some time and some refactoring.  I need to cut out for now, though.

Happy to help test once you've got something semi-working. Would love to help fix things as well, but I am still relatively new to neo4jrb and neo4j in general. (One of these days, though, you can look forward to getting a pull request from me.)

As Rails 5.2 is now out, would be great to get this fixed. 🙇

@aledalgrande This is certainly my highest priority, but it's probably not going to be simple and I can can only work on it in my spare time.  I've updated the README to warn people in the meantime, though

@anamba Thanks very much!  Normally I'd suggest jumping in, but this bit of code is kind of hairy.  Just got back from holiday, but I'll hopefully soon see if I can scope it

I’ve got a branch with passing specs. The changes were pretty simple,
though I’d appreciate careful review. We will probably need to implement
some methods to fill in gaps for compatibility with old Rails, too. I have
no internet other than email but I’ll push it up tonight and you guys can
kick the tires.
On Mon, Apr 16, 2018 at 7:39 AM Brian Underwood<EMAIL_ADDRESS>wrote:

@anamba https://github.com/anamba Thanks very much! Normally I'd
suggest jumping in, but this bit of code is kind of hairy. Just got back
from holiday, but I'll hopefully soon see if I can scope it
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/neo4jrb/neo4j/issues/1496#issuecomment-381584711, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AD6E910jFh5FqXthQCmvfU51c6H_wNHoks5tpJDzgaJpZM4TMIPc
.

Yeah, I know there's definitely some things that seemed like they might not be backwards compatible, but I'm looking forward to seeing the changes!  Thanks!

FYI for anybody following, check out this PR:
https://github.com/neo4jrb/neo4j/pull/1499
I think it's most of the way there, but CI is taking a long time to run every time we make changes.  I think it's mostly working for ActiveModel 5.2, but the tests are failing for Ruby 2.1 (which may be because newer versions of Rails require Ruby 2.4, IIRC, though I'm not sure).  Also, I added a build on CI for ActiveModel 5.1 (since CI uses the most recent version by default), so we need to see how that runs.  When I ran it locally I think I saw problems

Rails requires Ruby 2.2.2 since 5.1 https://rubygems.org/gems/rails/versions/5.1.4

The fix from #1499 has been released as version 9.2.2 of the gem.  Give it a try!

9.2.2 is doing everything I need it to so far. Thanks!

🎉 Thanks for the feedback!

🎉🤘🎉


Blobs under unnamed folders are not shown

Storage Explorer Version: 1.12.0
Build Number: 20200116.10
Platform/OS: Windows 10
Architecture: x64
Regression From:  N/A
Bug Description
If a blob resides in a named folder that's under an unnamed folder, the blob isn't accessible from Storage Explorer.
Steps to Reproduce

Upload a blob with path "///folder/blob.txt"
In storage explorer, open the unnamed folders until "folder" is shown
Open "folder"

Expected Experience
blob.txt is shown
Actual Experience
no blobs are shown
Additional Context
Originally reported from https://icm.ad.msft.net/imp/v3/incidents/details/180985613/home

Duplicate of https://github.com/microsoft/AzureStorageExplorer/issues/1512


Community Meeting Meta Issue

Let's discuss the breaking changes coming on Dynaconf 3.0.0 https://doodle.com/poll/ke2g4kc6mzwgtavh
There are some issues still opened for 3.0 https://github.com/rochacbruno/dynaconf/milestone/9
The highlights to be discussed are:

Global settings object is going to be deprecated
Users must create their own instance of dynaconf
Deprecate
from dynaconf import settings

New recommended way
 # yourprogram/config.py
 settings = Dynaconf(**options)`

reason
Most users are confused about importing direct from dynaconf a singleton config object and when
customizations via **options are needed they have to change the whole codebase.

No more default file paths
Right now Dynaconf loads all files named settings.*
idea is making it explicit only via option
settings_files=[list of paths or globs]
e.g:
from dynaconf import Dynaconf
settings = Dynaconf(settings_files=["main.toml", "other.toml", "path/*.toml"])

reason
Debugging file loading is hard, permissions and other I/O problems may happen
idea is to make explicit and raise earlier for errors.

Envless mode will be default
Now dynaconf has an envless_mode, which means it can load
all variables direct from the main level of a file.
server = 'bar.com'
port = 5050

This will be the default and if needed users will provide the
list of environments.
settings = Dynaconf(envs=["development", "production"])

then
[default]
server = 'bar.com'
port = 5050
[development]
server = 'dev.com'
[production]
server = 'prod.com'
port = 80

Allow parser to be changed or disabled
Right now toml is the only parser for every variable,
idea is to make it configurable (and allow users to opt-out)
reason
Some users reported that wanted raw values instead of parsed
by toml.

dotenv will be disabled by default
No more loading of .env unless users explicitly enables it.
reason
In some environments dotenv is already loaded by the shell tool

Validators will fire by default if passed to the settings object
No need to explicity call settings.validators.validate()
if Dynaconf(validators=[...]) is passed it will be called
right after the initialization.

Remove logging completely
reason
It is easier to debug using pdb/ipdb, logging right now is
useless.

Hi Bruno
Let me comment first bullet: right now it is very simple: you simply adding 'import dynaconf' in each module where you want to use settings, and then, referring to parameters through settings.SOMETHING. With this change, will I have to declare settings object.. in every module? every function?
It seems difficult, especially because my app changing values of parameters sometimes - then an object declared somewhere will miss these changes.. Or am I wrong?

@And2Devel hi, the idea is that somewhere in your project you create your own main settings object.
program/config.py
from dynaconf import Dynaconf
settings = Dynaconf(**options)

then in other parts of your program you just import from program.config import settings

OK, I see.
What about changing value of a parameter?
Will I have to use "global" in every function, like below?
def example_function():
    global settings
    settings.SOMETHING = 'value'`

@And2Devel no, you don't need to use global the only change is that instead of importing the settings from dynaconf directly you will start importing from yourprogram.config the usage remains the same.

in insights-qe we pretty much completely try to avoid the global variable and try to set up multiple own instances per "application object"  - we collect settings files from a number of python package data folders and want to grow the ability to easyly create views to a specifiv settings instance with overrides layered on top

Dynaconf COmmunity meeting is recorded here: Available for 60 days: https://www.twitch.tv/videos/647819477

the version 3.0.0 is implementing the main changes:

[ ] envless by default
[ ] no more global settings object (you need to instantiate one yourself)
[ ] no more loading of .env files unless user specifies load_dotenv=True
[ ] first level variables can now be accessed using lowercase settings.server.hostname for exemple (before upper was mandatory settings.SERVER.hostname) #272
[ ] settings path or glob should be provided by user, dynaconf will not try to load settings.* by default #310
[ ] Logging to be completelly removed #352

"Explicit is better than implicit"

All the changes discussed on this issue has been implemented!
Details on https://github.com/rochacbruno/dynaconf/blob/master/3.x-release-notes.md
Pre release rc2 is coming tomorrow and I can use some help for testing.


babel the api with require('babel-register')

Thoughts?

only issue is this: https://github.com/flatiron/cradle/pull/306


Clear input text on AddFeeling when user saves

This has been mentioned by a couple of people now

Closed by dc0b141bb214e183047bb013dd48790ff24f3856


Remove Courier New from font-family of REPL editor

I work on Ubuntu on Laptop with 1920x1080. It doesn't come with Monaco or Menlo or Consolas. So Courier New ends up being the font for ace-editor. And it looks like this.

It really hard to read and understand anything.

Do you know what is the preferred monospace code font that comes preinstalled on ubuntu?

Ubuntu Mono. It looks nice too. Also the font size can be a bit better.

Made https://github.com/babel/babel.github.io/issues/970


Update feeder tests to match with new implementation

Goal of this PR
This PR fixes the feeder unit tests which got broken because the feeder no longer takes the given commit hash into account. It now only returns the deltas for the next hash, regardless of its input.
How to test it
Make sure the logic makes sense and that the tests are passing on the CI.

Closing in favor of a PR that will fix the feeder's logic


Arbitrage

Will this crate support Arbitrage and Triangular arbitrage?

@sarmel Well, I guess this will never be supported directly inside the crate, because this crate does not want to expose any specific trading strategy but rather provide an interface to define your own strategies, hence it won’t try to automatically detect arbitrage opportunities.
However, my dream goal would be that users wanting to design an algorithm exploiting such arbitrage opportunities would be able to easily implement their algo on top of this crate.

OK. Thanks for creating and making this crate open source.


Handling Function Errors

I have added type errors to function so when the user enter an string to a function that only accept number it should throw errors
You can check out the changes.
I have also found a typo in server.js file and I have fixed it.

I also found that there was a function that was using another function without importing it, I fixed in this pull request

Good work I love it!


Enable strict xfail in pytest

pytest does not fail when XFAIL tests passes unexpectedly, unless strict mode is set.
Currently the following XFAIL is passing unexpectedly:
XPASS cupy_tests\core_tests\test_raw.py::TestRawJitify_param_0_{jitify=False}::test_jitify1 macro preprocessing in NVRTC is likely buggy

pfnCI, test this please.

Failed as expected:
______________ TestRawJitify_param_0_{jitify=False}.test_jitify1 ______________
[XPASS(strict)] macro preprocessing in NVRTC is likely buggy

Jenkins CI test (for commit 7cfcc6cd80b90bfeeed2eefbd9ffadfed7048648, target branch master) succeeded!

/test

pfnCI, test this please.

Question: Would this have any impact to the ROCm CI? Maybe the impact is expected?

@leofang Thanks, that's a good point. The following XPASS will become FAIL after this PR.
https://kmaehashi.github.io/cupy-rocm-ci-report/master/output_test.log
XPASS tests/cupy_tests/core_tests/test_ndarray_unary_op.py::TestArrayBoolOp::test_bool_one_element ROCm/HIP may have a bug
XPASS tests/cupy_tests/indexing_tests/test_generate.py::TestIX_::test_ix_ndarray HIP may have a bug
XPASS tests/cupy_tests/math_tests/test_misc.py::TestConvolve_param_0_{mode='valid'}::test_convolve_diff_types HIP/ROCm may have a bug with larger `b`
XPASS tests/cupy_tests/math_tests/test_misc.py::TestConvolve_param_1_{mode='same'}::test_convolve_diff_types HIP/ROCm may have a bug with larger `b`
XPASS tests/cupy_tests/math_tests/test_misc.py::TestConvolve_param_2_{mode='full'}::test_convolve_diff_types HIP/ROCm may have a bug with larger `b`
XPASS tests/cupy_tests/statistics_tests/test_correlation.py::TestCorrelate_param_0_{mode='valid'}::test_correlate_diff_types ROCm/HIP may have a bug
XPASS tests/cupy_tests/statistics_tests/test_correlation.py::TestCorrelate_param_1_{mode='full'}::test_correlate_diff_types ROCm/HIP may have a bug
XPASS tests/cupy_tests/statistics_tests/test_correlation.py::TestCorrelate_param_2_{mode='same'}::test_correlate_diff_types ROCm/HIP may have a bug

I think we can work on fixing them in separate PR.

Jenkins CI test (for commit 7cfcc6cd80b90bfeeed2eefbd9ffadfed7048648, target branch master) failed with status FAILURE.

pfnCI, test this please.

Jenkins CI test (for commit 7cfcc6cd80b90bfeeed2eefbd9ffadfed7048648, target branch master) succeeded!


Move the change to fPhysicsState.fPstep to only update for the winning process

@pcanal can you checkout these two files from the master and try to merge again?


Remove namespace

Fixes https://github.com/apache-spark-on-k8s/kubernetes-HDFS/issues/6

@kimoonkim ok to merge this?

@foxish This change is pretty much ready. Any chance we can fix the README.md and merge soon? FYI, I don't think I have the push privilege for this repo in case you were waiting for me to do the merge.

Done, merging. Will add the push privilege for you in this repo. Thanks!

Cool. Thanks for taking care of this! And happy to have the push privilege :)


Netherite Sockets

mythicdrops sends a "you cannot use that gem on that type of item!" Message when trying to socket the gem on a netherite item.

Fixed by adding netherite to the itemGroups.yml.


init local storage

Some problems with this version:

The helper text is long and unnecessary: Just put: Please enter your name (I.e: Elon)
The first message needs to re-send after user enter input

Add a space between user name and message


warning raised for version eol

Closes #233879
WIP
Currently, a warning header is added to all admin and storefront APIs that are using a version that expires within 30 days or is expired already.
This pull request is raised to add warning message within the Shopify API gem in case of API Version EOL.

cc: @Shopify/api-patterns-team


Calculator using GUI (PYTHON)

Hey, Greeting's of the day !!
(A clear and concise description of what the feature is.)
I want to add Calculator to your repository made using GUI (Python) i.e ..     Project-Guidance/Web Development/Basic/Calulator
It can do basic arithmetic operation .
Yeas i read all the contributing Guidelines ..
I would like to work on this under GSSOC'22
Please assign this to me .
Thank's regard .. :crossed_fingers:
(Write your answer here.)

@Vikash-8090-Yadav Proceed 👍

I am GGSoc Contributor
I would also like to contribute on this.


Add assets functionality to txwrapper-substrate

Add the following functions from the Assets pallet:

transfer
transfer_keep_alive
approve_transfer
cancel_approval
transfer_approved

Eventually we should have a txwrapper instance for Statemint that includes these methods plus Proxy and Multisig.

Ideally we can this in by ~ April 2nd

Sounds good! Will get it done.


Grind for low R signatures

(This issue originated at https://github.com/sparrowwallet/sparrow/issues/144 - transferring it here)
SeedSigner does not appear to be currently grinding for low R signatures, resulting in a larger transaction size than is necessary. In particular, look at the signatures for Input #2 of the PSBT attached - when encoded to DER, both signatures are 71 bytes in length. Signatures with low R are less than 71 bytes in length. It's strongly recommended to grind for low R signatures - this is done by adding additional data to the deterministic nonce as described by section 3.6 of RFC 6979, and signing until a signature with low R has been calculated. Bitcoin Core, Electrum, Sparrow and other wallets do this.
Further, it's also important to calculate this nonce the same way as Bitcoin Core/libsecp256k1 (which results in the same signature). Since we can't easily prove that the nonce is random, it is strongly advantageous to use the same nonce as everyone else. Here are some notes that may be helpful:

The initial attempt to sign uses no additional data as per RFC 6979 3.6. If that attempt results in high R, the second attempt uses a value of 1 (and further attempts increment).
The additional data is encoded to little endian.
The additional data is applied in both RFC 6979 steps 3.2d and 3.2f (RFC 6979 3.6 does not clarify this well).

It looks like actually signing is being done by the embit library here - but posting this as a SeedSigner issue because I think it's an important one to address given the focus of this project.
test.consolidation.fee.error.if.left.on.lowest.range.psbt.txt

A relevant change has been made in embit that should resolve this (https://github.com/diybitcoinhardware/embit/issues/12).

I've done testing with embit 0.4.3 release and can not replicate the issue found before. This appears to be resolved.

Going to leave this open until we get the updated version of embit into a release, thank you for testing the fix.

Was able to circle back and test this, have done several transactions with a large number of inputs, haven't encountered the fee issue again, considering this closed.


Icon auto-change based on profile

Could be very useful adding a features that autoswitch icon image based on what profile is applide. I notice that sometime I forget pc on "energys saver" than goin through some game and get very low performance, sometimes forgetting that I0m on "energy saver profile"

I concur, It would be very useful to see at a glance which plan is activated. Perhaps a different color for each plan.


ModuleNotFoundError: No module named 'geemap.eefolium' - geemap_app.py

OS: Linux-Ubuntu 22.04.2
Steps followed:

Installed dependencies with Pipenv using the requirements.txt file:
$ pipenv install -r requirements.txt
Entered the Pipenv environment:
$ pipenv shell
Executed the Streamlit app:
$ streamlit run geemap_app.py

Error encountered:
You can now view your Streamlit app in your browser.

  Local URL: http://localhost:9999
  Network URL: http://999.999.0.999:9999

2024-07-16 11:50:16.662 Uncaught app exception
Traceback (most recent call last):
  File "/home/dude/.local/share/virtualenvs/geemap-streamlit-ZjOHIH0S/lib/python3.10/site-packages/streamlit/runtime/scriptrunner/script_runner.py", line 589, in _run_script
    exec(code, module.__dict__)
  File "/home/dude//Programming/geemap.streamlit/geemap-streamlit/geemap_app.py", line 3, in <module>
    import geemap.eefolium as geemap
ModuleNotFoundError: No module named 'geemap.eefolium'

The same error was when I run:
$ streamlit run app.py


Kak-Bundle Design Discussion

It seems bundle is adding a %val{runtime}/autoload symlink to bundle's dir, which is in turn under user's autoload — this will result in nasty, hard to debug errors in most setups, as people usually already have that symlink directly under their autoload.
So you should decide whether you want bundle to

remain in autoload: then drop the symlink, and also the bundle command becomes kindof meaningless — subdirs get loaded anyway and bundle cannot control what's loaded and what not. Once you place something under autoload, that's it — all subdirs will be searched recursively for .kak files.
go above autoload / elsewhere (then you need to load files manually like plug using find — see plug.sh)

Also, there are also shell quoting problems (use "$var" consistently, unless you really mean to word-split, but beware that a naked $var also expands globs), and perhaps bundle_plugins should be a str-list option.

As for your overall point, although I agree about the symlink thing (I could include an option to do it or not), I think the rest of that first bullet point betrays a misunderstanding of the purpose of the bundle command.
We are using autoload precisely so that we don't have to handle the actual loading of plugins, which makes this significantly faster on load than the OG plug.kak. This was also the aim of alexherbo2's plug.kak. What the bundle command actually does is tell kak-bundle which plugins to install when the bundle-install command is run. Admittedly, I probably didn't make that very clear in the README.
You do have a point about the shell variable expansion and using a str-list instead of a space delimited string for the list of plugins, though - I will certainly look into that.

OK, so you want bundle to stay in autoload (and not call find), that's good to clear up.
In this case, to remove a plugin, the user not only has to remove the corresponding bundle command in their kakrc, but also manually remove the git repo from under bundle/. This needs to be mentioned in the README.
There's another option that doesn't require find: move the actual git repos out of autoload (e.g. into %val{config}/bundle-repos, and add symlinks to the "enabled" plugins (actual git repos) under a "thin" directory autoload/bundle. You get to manage what gets loaded (via the bundle command) without slowing down to find / source.
If you like this last option, I can help with that (it sounds like something I might want to use). If you prefer to keep it as it is, that's also great, but I'd suggest not adding the runtime/autoload symlink by default, as it breaks most existing setups. I've struggled to debug a stray duplicate runtime/autoload link for a day recently (added by my own testing scripts for a plugin, long story).

I really like the way you're going with this, I have another option that would avoid having to deal with symlinks: add a bundle-load command that takes a set of plugins as parameters. For example, if you wanted to load mru-files.kak (great plugin, by the way) and kak-lsp, you would run bundle-load mru-files.kak kak-lsp. This command would go into the bundle plugins directory and load all the .kak files found in the repos of the specified plugins. This would allow the user to pick and choose what plugins to load, and I don't have to deal with cleaning up symlinks to plugins the user no longer wants loaded in a future Kakoune session. This could look like the following in someone's kakrc:
bundle https://github.com/kak-lsp/kak-lsp
bundle https://gitlab.com/kstr0k/mru-files.kak
bundle https://github.com/andreyorst/powerline.kak

bundle-load kak-lsp mru-files.kak # Note that only kak-lsp and mru-files get loaded, not powerline.kak

# Now plugins are loaded. Set options and hooks and run commands here.

The main slowdown with the OG plug.kak that I wanted to avoid is actually the fact that each invocation of the plug command spawns an sh process, with all the os-level processing that entails. The main goal with this plugin manager is to avoid creating sh processes as much as possible, not necessarily to avoid calling find (Kakoune actually uses find to load the autoload directory - see https://github.com/mawww/kakoune/blob/master/share/kak/kakrc) - hence why the bundle command does no more than simply update the plugin list.  Placing all the plugins in autoload was my initial plan on accomplishing this goal, as Kakoune would spawn a single sh process to load them all. However, loading the plugins with a bundle-load command would require creating only one sh process on my part, and allows the user to populate their autoload directory as they see fit, avoiding the symlink collision issues you mentioned earlier.
I hope I don't come across as too callous regarding your input - I really do appreciate your willingness to give input and get involved in making this plugin manager work.

Thanks, and no problem at all. Hey, we're on the same page — as you may have noticed I've also been working on reducing %sh{} calls (or if not possible, at least the number of subshells / external calls in shell code).
bundle-load sounds like a good design.
Another thing: for some git repos, I need to switch to a non-default branch (or a tag). I'm OK with doing that manually, once after bundle-install, but if I clean and re-install, the branches / tags get lost; it gets unworkable. What do you think about this? One way I can think of to handle it would be to optionally provide the bundle command with a full git command (bundle 'git clone -b BRANCH ... $URL. Then bundle-install and bundle-update could tell if each plugin (from the str-list) is a simple URL or a full git command ending in a URL (it has spaces). This would be backwards compatible.

Sorry for the delay - I was busy all morning. I've taken the liberty of renaming this issue to "Kak-Gradle Design Discussion", as that is essentially what this has turned into (not that that's a bad thing).
I really like that idea of potentially passing a git command to the bundle command as a means of specifying a certain branch or tag to switch to. Essentially, it would just require the bundle-install command checking if the string starts with 'git ', and deciding what git command to run based on that. I don't really have time to work on that right now, but I think that's a good way to move forward.

The bundle-load command has been added, and it works exactly like we discussed. It seems to work for me, so let me know if you have any issues with it. I don't have time to implement the bundle command enhancement tonight, though.

Let me look at it and maybe PR some changes. Some quick remarks:

you don't need to backslash \. within find -name patterns — these are shell patterns, not regexes. I don't think it's actively harmful but I'd have to fire up a FreeBSD VM
I'll replace sed with shell builtin read's
to make it easier for the user, bundle-load with no args should default to all registered plugins. I think this just means running find on bundle_path.

I'll implement the bundle 'command args... URL' extension also. A further enhancement:

the command given via bundle could be arbitrary, not just git ... URL. For example, a ln -s /src/awesome ./awesome (bundle-install already cd's to bundle_path). This would be useful for emulating plug's load-path (note that this is not the same as git clone file:///...)
bundle-update should ignore anything within bundle_path that's not a subdir
not required right now, but good to have in mind, maybe document: the rule was (and remains)

everything after the final / in the bundle ... command becomes the install subdir under bundle_path. E.g.
bundle http://.../name
bundle 'git clone ... http://.../name'
bundle 'ln -s /src/name ./name'

Note: with bundle 'git clone URL ./renamed', the user can also handle multiple repos with the same name (but different URLs).

OK, I rewrote the README to hopefully better reflect all the new things kak-bundle is now capable of. If anything was omitted or is unclear, don't hesitate to let me know.

Will do, I'm a little busy with sel-editor right now.
But since I'm here, I was thinking about a few more things (briefly explained, let me know if anything sounds confusing):

bundle can keep track of loaded plugins and, well, not load twice. This is so that separate bundle-load this-plugin; bundle-load that-plugin do not prevent a final bundle-load # no args from loading all remaining ones
loading some plugins individually (with the associated cost... of course) is useful because it allows the user to require and use the plugin right away, in the middle of their kakrc. For example, my k9s0ke-dbg.kak plugin has defp, which defines a self-docstring-ed function (which will soon include optionally-trace-able functions). Also, alias-args to alias command + arguments. The user might want to immediately load meta-programming plugins in the middle of their kakrc, without breaking load # no args
the easiest way to do this would be to send back to kakoune a str-list of files, which can be diff-ed (set -add / set -remove) against the currently loaded plugins, then the new ones can be sourced, then the loaded-plugins list can be the union of the two.

There are some missing capabilities; maybe we should document, maybe sit on them:

bundle 'ln -s ~/src/myplugin' — similar to plug's load-path. Also, bundle ln -s ~/src/myplugin ./renamed, git clone ... ./renamed. This is because different plugins can have equal basename's, but different URL's, and otherwise they are non-installable
document the requirement that the last /* in the command / URL should be the actual dir in bundle-path where the command installs the plugin. E.g. a command can be any shell code, possibly multiple commands separated with ; — bundle, doesn't care, it just needs the last /* component to be the destination subdir in bundle_path. It's not required for now, but otherwise, later bundle won't be able to locate install-paths for registered plugins, and it may want to (e.g. re-install or update a specified list of plugins, not all)

I.e. this simply means sending back a list of
set -add global bundle_new %<source %<XXX>>;
set -add global bundle_new %<source %<YYY>>;

instead of the plain source commands. Since <> are already excluded from filenames, and since they balance, it makes no difference (otherwise we'd have to add a quoter, quote-quote the filenames etc)
In Kakoune, after eval -- %sh{},
# set-difference: don't load again
set -remove global bundle_new bundle_loaded
eval "%opt{bundle_loaded}"  # concatenate statements

# remove, then re-add to get set-union
set -remove global bundle_loaded bundle_new
set -add global bundle_loaded bundle_new

Other solutions are possible (like a command_fifo to have sh compute some things etc)

So, OK, this worked quite nicely it seems (PR #5 ).
Now, I'd like to write a bundle-plug emulator, which I would release separately; it would help adoption, and also keep kakrc configs more-or-less compatible. It would provide a bundle-plug command, which people can optionally alias to ... plug if they wish to keep their configs.
I would need a command that both registers the plugin and calls bundle-load with the final /* component (basename), for all args. This approach would be slower, but the tradeoff might be worth it to some. This should be quite easy. But what do you think?
Note that I've already implemented plug-many for plug.kak, which loads multiple plugins with a single sh call (see the PR's there). It's fate is not quite decided (apparently there will be a new plug version at some point anyway), but it works.

So, something like this, perhaps (sorry if this is suboptimal; my bash-fu is weak)?
def bundle-plug -params 1 %{
    bundle %arg{1}
    eval %sh{
        plugin="$1"
        repo="${plugin#*/}"
        echo "bundle-load $repo"
    }
}
alias global plug bundle-plug

Obviously that example would need some tweaks, as it only works with passing a URL to it, and it doesn't support any of plug's switches, but I agree that including something like this would make migrating from plug.kak to kak-bundle substantially easier.

Yeah, except more like https://github.com/andreyorst/plug.kak/pull/100 :
bundle-plug https://github.com/gustavo-hms/peneira demand peneira %{
} plug https://github.com/jbomanson/search-doc.kak demand search-doc %{
  alias global doc-search search-doc
} plug https://gitlab.com/FlyingWombat/case.kak

... so that there can be a single command and sh call.
From plug, I would take config, demand and defer (make config mandatory — the goal is to make compatibility possible and not split the community; not to emulate perfectly).
So, I would probably need something like
bundle-load-and-register %{ prelude1 } URL1 %{ postlude1 } \
 %{ prelude2 } 'cmd .. ./myplug' %{ postlude2 } \
 %{ prelude3 } URL3 {postlude3 } # etc

... from bundle. As a first (and probably uncontroversial) step. Then I could implement a simple plug emulator. In kak, first bundle-source is executed, then the postlude is eval'd. The post-lude (to be generated by bundle-plug) would be: plug's config + register a ModuleLoaded hook + require-module # if demanded
The preludes could be sh code. I'm not sure yet. I just put them as placeholders for now.
There are other designs (as in that plug PR); for instance
bundle-block-start
bundle-block-one %{ prelude1 } URL-or-cmd1 %{ postlude1 }
bundle-block-one %{ prelude2 } URL-or-cmd2 %{ postlude2 }
bundle-block-end

This could accumulate args in a str-list, and (bundle-block-end) finally send them to %sh{}.
What do you think (as far as architecture, naming etc)?

OK, let me see if I understand you. If we were to go with your first suggestion (which is the one I'm leaning towards, in all honesty):
bundle-load-and-register %{ prelude1 } URL1 %{ postlude1 } \
%{ prelude2 } 'cmd .. ./myplug' %{ postlude2 } \
%{ prelude3 } URL3 {postlude3 } # etc

Then this hypothetical bundle-load-and-register command would need to do the following (I'm ignoring the preludes for now, because I don't think we need them):

Run bundle on the argument representing the plugin
Load the plugin with bundle-load
Execute the postlude, which would be any config or demand hooks defined by bundle-plug
Repeat the above three steps until we run out of arguments

If that is correct, then this should be doable. Again, I'm no shell shogun, but I should be able to cobble up something that does the above.

PR #6 . Actually, it was a little tricky to get right. To avoid adding a quoter, I'm passing back kakoune %arg{} references that only make sense to the calling function. But, this is %sh{} code that is supposed to be bound to a kak command anyway.
Feel free to amend as you see fit. I've called it *-register-and-load, since that's the actual order.
BTW, do you have any local tests? Are you using bundle with a reasonably complex config yourself? Mine includes only a converted portion of the plug configs, but this will change as soon as I write the bundle-plug emulator.

... and, at some point, we should probably split the prelude into a separate *.sh file. Let me know when you think it's a good time (since again, this breaks git diff viewability)

You're too quick, dude. Leave me something to do 😄

Sorry about that... I realized it might be a problem. I happen to have a quite a bit of "OSS time" at this point, I guess, and I also want to get things "just right".
I really appreciate your design decisions / input (as I've said, without it I might have over-engineered things even worse). So, what do you see next in bundle / what would you like to implement? Just so we don't step on each other's toes, I'm planning to do this:

add a *bundle-status* scratch for install / update feedback. This is rather tricky to get right, due to (of course) the background jobs I introduced in the parallel update (which you advised against). See plug.kak's shell wait / jobs-file hack — I really don't want to do that, and I think there are better ways, but it's not simple.
write a kak-bundle-plug emulator. I've already written a plug wrapper for the plug-many enhancement I mentioned above. This also involves shell tricks in order to iterate over an array of arguments while building another (or maybe it will be easier — I'll have to see)

Oh, no worries. That was meant in jest 😉. It's just that, during weekdays, I have maybe an hour or two at most to work on side projects, due to my job and other priorities, and I have kak-dap to work on as well.
As for your suggestion to work on viewing the install/update process in a buffer, that was going to be my next step. I don't think we need a fancy interface like the OG plug.kak for this - outputting the stdout of the git commands (or whatever we're running) into the buffer should be enough. We could even give it the grep filetype for some highlighting. I believe that's how alexherbo2's plug.kak did it, before he discontinued it. I'm not even entirely convinced the parallel processing will make this that much harder, although the option still exists to nix the buffer if $kak_opt_bundle_parallel is set to true, should things get dicy.

Hang on - I have a better idea for the bundle-pickyload command. Instead of passing the plugin name and scripts separately, define them in the same argument. Something like this:
bundle-pickyload kakoune-extra/autosplit.kak kakoune-extra/fzf.kak

This also makes supporting multiple plugins with this command trivial, as basically all we're doing is cd'ing into the plugins directory and sourcing each of the arguments.

Hey, kak-dap looks like a really cool project.
pickyload also seems like a worthy extension. What do you think about adding a filter option bundle, which the user can manipulate at their convenience, to... filter out sources? This would allow all -load-related commands (load-and-register, bundle-plug) be able to use it. Then, bundle-pickyload itself could be a wrapper.

bundle-pickyload kakoune-extra/autosplit.kak kakoune-extra/fzf.kak

This also makes supporting multiple plugins with this command trivial, as basically all we're doing is cd'ing into the plugins directory and sourcing each of the arguments.

Ah. I see what you're saying, that would be much simpler. But then how would you exclude those picky-ed plugins from the general bundle-load  # no args at the end of kakrc?

I would probably solve that by having bundle-pickyload update a list of plugins it's handled, so bundle-load knows not to touch them.

I would probably solve that by having bundle-pickyload update a list of plugins it's handled, so bundle-load knows not to touch them.

I see, so something like
printf '%s\n' \
  "set -remove global bundle_loaded_sources %<${file%%/*}>"
  "set -add global bundle_loaded_sources %<${file%%/*}>"

This is a really nice addition.

https://github.com/kstr0k/kak-bundle-plug
It works with my entire setup. Pure kakscript, for better and worse.

As for your suggestion to work on viewing the install/update process in a buffer, that was going to be my next step. I don't think we need a fancy interface like the OG plug.kak for this - outputting the stdout of the git commands (or whatever we're running) into the buffer should be enough.

The problem with multiple jobs is that if all jobs output to the same stdout, their output gets mixed up. Even producing mixed-up line fragments from different jobs.
The cleanest output can be obtained by redirecting the stdout of each job to a separate log (which is what I did). Now, to get that output, either the shell has to pipe back to kak (FIFO or command-fifo), or kak has to read these logs.
If the shell is to concatenate the logs (either by looping over them once a second, or with tail -f file1 file2 etc, which is not even POSIX for multiple files), then it also has to wait for all jobs to terminate. So it has to wait for all jobs except the one that polls the file. This is tricky. The POSIX wait command doesn't take a timeout. There's kill -0 to check the existence of a PID, but I'm still not sure it's completely safe. It may be possible to wait for all jobs to finish in a job-owner subshell, and in the main process poll (with kill -0) that job-owner, while concatenating the logs on each iteration and sending them to kak.
If, OTOH, Kakoune is to collect the logs, then the shell can still wait for all jobs to finish as it's doing now. However we need to implement a periodic hook in Kakoune, e.g. by chaining -once NormalIdle hooks and increasing a counter which wraps around to 0 when the periodic limit is hit (at which point the periodic code executes). This is also tricky, especially since the NormalIdle timeout is not fixed (from what I recall). And NormalIdle doesn't occur without user activity...

OK, bundle-lazyload is in the latest master. It not only selects specific scripts to load from a plugin, but it also marks that plugin as "loaded" so future bundle-load calls don't try to load the rest of the plugin. From my testing, this seems to work fairly well. I also removed the bundle_new_sources and bundle_loaded_sources options, since these seemed to me to be overcomplicating things, and a single bundle_loaded_plugins option seemed to do the trick. Let me know if this command works for you.
I think I'm going to need to take a break from kak-bundle for a bit - I only have limited time right now and need to get kak-dap done at some point.

Well first of all there is no POSIX [[ .. ]] or =~ operator. Are you using bash as the KAKOUNE_POXIX_SHELL instead of dash?

OK, I understand -- it's better to focus on the things you like.
But I'm not sure how to proceed if you want to take a break. The simplest option for me would be to develop my fork independently. I have yet to implement a number of things (e.g. noload support).
Another option would be for me to take over bundle as well for a while, until you want to work on it again, if you'd like to proceed that way.
What do you think?

I just pushed up a change that should address the POSIX compliance issue.
About how to proceed from here - I would say just work on your fork, and then I'll have you submit a pull request when I'm ready to get back in the saddle. This is basically what andreyorst did when he had to take a break from developing powerline.kak and I was maintaining it for him.

OK;

let me finish my kak-bundle-plug emulation
including any PR's I may need to kak-bundle
then let's make a joint announcement on

And then you can take a break :) Does that sound reasonable?

Sounds good.

I'll be sure to mention kak-bundle-plug in the Tips and Tricks section, under a plug.kak Compatibility header or something. Having an easy way to transition from plug.kak to kak-bundle would be very appealing.
That said, for a while now I've been in the process of migrating my repositories to Codeberg, due to recent (as in the last couple years) business decisions on Github's part that I'm not really much of a fan of. I've already migrated kak-dap over, and this plugin is next in line. If you want to keep contributing to this plugin (and I'm assuming you do), then I believe Codeberg lets you log in with your Github account, so the barrier to entry shouldn't be too high. We can continue this discussion over there.
If you need me to delay for a bit, I can do that, but I would like to get moved over eventually.

It depends on what you want to announce on http://discuss.kakoune.com; I've been saying we're nearing completion for a while, but this time I think it's for real :)
I presume Codeberg? I've managed to sign-up and link accounts (whatever that means — you still need to create a CB account in the first place).
I'm mostly on gitlab myself (https://gitlab.com/kstr0k).
Now: are you going to delete this GH repo? Abandon it? Mirror Codeberg?

I've been mentioning the URL of your repo in several discussions, including ongoing bug reports for https://github.com/mawww/kakoune — it would be a pity if those links broke.

I wouldn't get rid of the github repo entirely - I would just replace the README with a statement that development has moved to Codeberg and archive the repo, like what I did with kak-dap: https://github.com/jdugan6240/kak-dap.
In other words, linking to it wouldn't yield a 404, but there wouldn't be any updates to that repo.

I see. Well, copy it over to begin with, and let me see how it works.

OK, the new repo can be found here: https://codeberg.org/jdugan6240/kak-bundle.
This design discussion issue was even copied over, so should the need arise, we can continue in there.

Given the recent kak-bundle redesign, I think this issue can be closed.


[vcpkg docs][ES] Sync with English readme (#21952)

Update the Spanish readme with the latest changes of English readme PR (#21127)
What does your PR fix?

It keeps in sync the Spanish readme with the mainstream readme, also corrects some false friends for library translation
Fixes some untranslated links

Which triplets are supported/not supported? Have you updated the [CI baseline]
N/A [L10N][Documentation]
Does your PR follow the maintainer guide?
Yes

Thanks!


Keep navigation within the RHP when navigating from a report to an expense on the Search page

Background: Users often utilize the Search page to find and access reports through the Right-Hand Pane (RHP). The RHP allows them to view reports without leaving the Search page, providing a seamless and efficient experience.
Problem: When users attempt to view an expense from a report opened in the RHP, they are redirected to the Inbox, disrupting their workflow and preventing them from maintaining their original context.
Solution: Adjust the RHP navigation stack in Search so that any content accessed from within the RHP remains within it. This change will enable users to navigate from a report to its associated expenses entirely within the RHP, allowing for smooth, uninterrupted exploration of report details without leaving the Search page.
https://github.com/user-attachments/assets/59dcdbb9-1835-47d4-aefd-82b2e43a6d43

This is being actively worked on

Not overdue, SWM is working on it.

Good question, thoughts @luacmartins ?

They are the same. I'll close the other issue in favor of this one, since it has a more structured P/S

Coupla' things:

We are going to keep this moving forward, yes?
I'm moving this project into #migrate to track along with this next wave of changes.

@trjExpensify @shawnborton can you share what the new navigation flows should be in the Search page? That'd give us a better idea if this is still needed or not

What do you mean by new navigation flows?

The redesign, report in the main pane etc.

Basically what navigating from an expense/report row to a report in the main pane to an expense in the RHP then clicking any link in the RHP, etc

Native stack PR merged and getting through the follow up bugs, this will unblock the bottom tab refactor and these changes too

That being said, I do think it makes sense to keep the user in the RHP if they are navigating into a thread inside of an expense or something like that.

So we'd keep the user in the RHP if they clicked any link in the RHP chat?

I wouldn't say "any link" but we'd want to keep them in the RHP if they were drilling down into a thread or something.
It gets a bit tricky though because in theory, you could first open up an expense in the RHP from the Search > All page. But then from the expense, you could go up a level and view the report. Maybe it's okay to keep that report in the RHP, but then we have a consistency where sometimes the report can be opened in the main content pane and sometimes it can be opened up in the RHP.
I think the best path forward might just be to try to keep the user in the RHP if they are navigating around within the RHP in relation to workspace chat/report/expense views.

Going to throw a HOLD on this one while we sort out some of the high-level discussions around Search V3. Sorry for the change of plans, but let's make sure we attack this one with alignment.

Still holding

Still holding


[BUG] - BlueprintTweaks and BuildToolOpt option incompatibility

When using BlueprintTweaks 1.6.3 and Starfi5h's BuildToolOpt 1.0.2, with UIBlueprintOpt enabled, the following error is consistently reported as soon as you select any blueprint. (That is, opening the blueprint selections, and single left clicking any non-folder blueprint. Pasting is not required, only viewing.)
I presume this is a low priority bug. However, this did not occur with BlueprintTweaks 1.6.2, and the previously stated mods and options. Thus, i thought it useful to be made aware of. Simply disabling the noted option fixes the issue, and thus is not a major issue. For reference, I have BepInEx 5.4.22.
[Error  : Unity Log] System.MissingMethodException: void UIBlueprintInspector.Refresh(bool,bool,bool)
at UIBlueprintInspector._OnOpen () [0x00005] in <098005bb1c5d4804a3d5e3ad4799301a>:0
at ManualBehaviour._Open () [0x00031] in <098005bb1c5d4804a3d5e3ad4799301a>:0

aww dang this 2 are good combo, hoping this can/will be fix

btw, i disabled the UIBlueprintOpt and tried putting new blueprint, when double clicking the blueprint, error shows

This issue isn't a compatibility issue. It was fixed in v1.6.3

I don't have BuildToolOpt and I also have this error message.

reinstalled this mod,
disabled all mods except this mod and related to this mod.
created new game with this only mod running, new issue


Exposing too many API that should be private

Since the current nutsdb package structure is flat, all internal methods and variables can be changed to private, and only part of the user API should be exposed.
For example, The method SubmitBucket in tx.go should rename to submitBucket.

Hey, I would like to work on this issue.

Hey, I would like to work on this issue.

Assigned to you. Thanks.😁

Hey @bigboss2063 PR is ready, should I also have changed the internal types e.g Event, Record to be unexported ? I left them as is but I changed the creator methods to newEvent and newRecord

Hey @bigboss2063 PR is ready, should I also have changed the internal types e.g Event, Record to be unexported ? I left them as is but I changed the creator methods to newEvent and newRecord

yeap. I think we should change them all.

@bigboss2063 I think PR is ready now with the extra changes

Wow! It's a very big change. I need some time to review🤣.


Removes botimize because it's discontinued and keep erroring

Fixes #90
The env var is already removed from production & staging LINE bot server.

Pull Request Test Coverage Report for Build 384

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 90.909%

Totals

Change from base Build 378:
0.0%

Covered Lines:
167

Relevant Lines:
182

💛  - Coveralls


Backslash escapes and literal backslashes in links must be supported according to the spec

Steps to reproduce the problem (provide example input):
See http://spec.commonmark.org/0.28/#example-167
Expected behavior:
URL is /url%5Cbar*baz
Actual behavior:
URL is /url\bar*baz

Disregard that


How to load two different tables into two different indices of elasticsearch?

I have two different tables, for example, user and event. And there are two indices in elasticsearch, index_user and index_event, how to do configuration in .sh files in folder elasticsearch-jdbc/bin?
Could we just leverage only one .sh file?

We could do it by two different .sh files, just change the configuration item "statefile" in the .sh file, e.g.
in user.sh:  "statefile" : "user_statefile.json" ;
and in event.sh: "statefile" : "event_statefile.json"

I think you can leverage one .sh file by specifying the index in the SQL under the "_index" column


show just recent invoices but provide a link to full list

currently full invoice list isn't linked to a aspnet route, so that should be done once routes are updated to allow for persistent links.

Oooooops

From: Spruce Weber-Milne @.>
Sent: Tuesday, June 29, 2021 10:12:14 AM
To: ucdavis/Harvest @.>
Cc: Scott Kirkland @.>; Author @.>
Subject: Re: [ucdavis/Harvest] show just recent invoices but provide a link to full list (#272)
@sprucely commented on this pull request.

In Harvest.Web/ClientApp/src/Invoices/InvoiceListContainer.tsxhttps://github.com/ucdavis/Harvest/pull/272#discussion_r660811022:

if (projectId) {

 cb();

}
cb();

if projectId, callback, else callback?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/ucdavis/Harvest/pull/272#pullrequestreview-695294809, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AABRQAPMDTP4UVPYZE3UJSLTVH5G5ANCNFSM47QU2B4Q.


Split Prism::Loader#load_node in one lambda per node type

Otherwise load_node is too big to compile and is forced to run in interpreter: https://github.com/oracle/truffleruby/issues/3293#issuecomment-1759730996
For the benchmark at https://github.com/oracle/truffleruby/issues/3293#issuecomment-1759790280
TruffleRuby Native 23.1.0: Before: 10.574041 After: 5.592436
JRuby <IP_ADDRESS>: Before: 7.037780 After: 3.995317
JRuby <IP_ADDRESS> -Xcompile.invokedynamic=true: Before: 7.047832 After: 2.269294

I did not measure on CRuby since the FFI backend is not default there.
EDIT:
I measured on CRuby 3.2 too and it's a little bit slower but almost the same:
Without YJIT: Before: 5.284203 After: 5.357027
With YJIT: Before: 3.333703 After: 3.516235
I think that's fine, given that on CRuby it's using the C extension for YARP.parse and that's faster (2s, 1.75s with YJIT).
cc @enebo

@eregon I half wonder how naming methods for each type with a send would work?  Not just because it may be more expensive for us to run blocks but because it would make debugging the gem give a much nicer backtrace when there is a problem.

That would be a megamorphic send (megamorphic in lookup since the method name is one of many, impossible to inline cache that lookup), which is a lot more expensive than a block call with a non-constant block "call target" (which has no lookup).

I'm seeing about a 10% slow-down on CRuby for this. I'd rather not impose that penalty unless we have to.

That's more than I saw in my measurements in the description.

Could you check the platform that you're on when you're templating out the file? That would allow both implementations to still be quick.

Unfortunately that cannot work since the same templates/lib/prism/serialize.rb in a .gem is used on both CRuby and TruffleRuby.
I can however emit both code paths and do if RUBY_ENGINE == checks.
I'm not sure it's worth it given Prism.load is anyway much slower on CRuby than Prism.parse, but it's easy enough, I'll do it.

@enebo One thing that is worth a try is to have an array of Method objects, then the megamorphic lookup would be avoided and it would be Method#call instead of Proc#call. Not sure if that's better.

Rebased and now the exact same code as before is used on CRuby.


Bugfix bracket disambiguation

Fixes an issue where maybeDisambiguateBracket could return a variant not found in allowedVariants.

Credential issue with the 1loc pipeline?


Add QEMU mode for some AFL++ secondary fuzzers

QEMU mode (-Q) could be used for certain secondary fuzzers.

I tried it, it does not much sense because of the huge targets. also tried with frida etc.
it is just very slow, difficult coverage gathering.
I recommend closing this.

Yep this was our feeling too. Thank you for checking it out.


force rename of native-named functions in non-native objects?

Is it possible to have ADVANCED_OPTIMIZATIONS rename functions such as .pushState() when not invoked on a native history object or rename .push() when not invoked on an array? What would be the correct way to annotate these cases so they get renamed?
For instance:
/**
 * @constructor
 */
function Moo() {}

Moo.prototype = {
  pushState: function(foo) {
    console.log(foo);
  }
};

var moo = new Moo();
var y = moo.pushState("123");

If the function is not named pushState, the whole thing optimizes to console.log("123");. I would like this behavior, but without having to physically rename all functions to appease the compiler.
thanks!

If you have type checking enabled for your project, you should be able to get type-based optimizations in advanced mode.
Here is an example where Foo#push is renamed but Array#push is not.
http://closure-compiler-debugger.appspot.com/#input0%3Dfunction%2520f(%252F**%2520!Array%253Cnumber%253E%2520*%252F%2520a)%2520%257B%250A%2520%2520a.push(123)%253B%250A%2520%2520console.log(a%255B0%255D)%253B%250A%257D%250A%250Af(%255B%255D)%253B%250A%250A%252F**%2520%2540constructor%2520*%252F%250Afunction%2520Foo()%2520%257B%250A%2520%2520this.prop%2520%253D%2520123%253B%250A%257D%250A%250AFoo.prototype.push%2520%253D%2520function%2520(x)%2520%257B%250A%2520%2520this.prop%2520%253D%2520x%253B%250A%257D%253B%250A%250Afunction%2520g(%252F**%2520!Foo%2520*%252F%2520x)%2520%257B%250A%2520%2520x.push(1)%253B%250A%2520%2520console.log(x.prop)%253B%250A%257D%250A%250Ag(new%2520Foo)%253B%26input1%26conformanceConfig%26externs%26refasterjs-template%26includeDefaultExterns%3D1%26CHECK_SYMBOLS%3D1%26CHECK_TYPES%3D1%26DISAMBIGUATE_PROPERTIES%3D1%26MISSING_PROPERTIES%3D1%26PRETTY_PRINT%3D1%26PROPERTY_RENAMING%3D1
I can't get this behavior on http://closure-compiler.appspot.com/home, probably because it's running an older version of the compiler.

thanks for looking at it. you're right, in that case it does work, but try this one out:
/** @constructor */
function Foo() {
	this.x = 0;
	this.y = 0;
};

Foo.prototype = {
	blah: function() {
		console.log("blah");
		return this;
	},
	kitteh: function() {
		console.log("kitteh");
		return this;
	},
	push: function() {
		console.log("push");
		return this;
	},
	pop: function() {
		console.log("pop");
		return this;
	},
	moveTo: function(x, y) {
		this.x = x;
		this.y = y;
		console.log("moveTo");
		return this;
	},
	moveBy: function(x, y) {
		console.log("moveBy");
		return this.moveTo(this.x + x, this.y + y);
	},
};

var myFoo = new Foo();

myFoo
	.moveTo(123,456)
	.moveTo(999,888)
	.moveTo(666,555)
	.kitteh()
	.kitteh()
	.kitteh()
	.push()
	.push()
	.push()
	.moveBy(4,6)
	.moveBy(4,6)
	.moveBy(4,6)
	.moveBy(4,6)
	.pop()
	.pop()
	.pop()
	.pop()
	.blah()
	.blah()
	.blah()
	.blah();

compiles to this for me (beautified):
function b() {
    this.b = this.a = 0
}
b.prototype = {
    push: function() {
        console.log("push");
        return this
    },
    pop: function() {
        console.log("pop");
        return this
    },
    moveTo: function(a, c) {
        this.a = a;
        this.b = c;
        console.log("moveTo");
        return this
    },
    moveBy: function(a, c) {
        console.log("moveBy");
        return this.moveTo(this.a + a, this.b + c)
    }
};

function d(a) {
    console.log("kitteh");
    return a
}

function e(a) {
    console.log("blah");
    return a
}
e(e(e(e(d(d(d((new b).moveTo(123, 456).moveTo(999, 888).moveTo(666, 555)))).push().push().push().moveBy(4, 6).moveBy(4, 6).moveBy(4, 6).moveBy(4, 6).pop().pop().pop().pop()))));

Try individually assigning the prototype methods instead of using an object literal. That may be the real bug here.

no luck :(
/** @constructor */
function Foo() {
	this.x = 0;
	this.y = 0;
};

Foo.prototype.blah = function() {
	console.log("blah");
	return this;
};

Foo.prototype.kitteh = function() {
	console.log("kitteh");
	return this;
};

Foo.prototype.push = function() {
	console.log("push");
	return this;
};

Foo.prototype.pop = function() {
	console.log("pop");
	return this;
};

Foo.prototype.moveTo = function(x, y) {
	this.x = x;
	this.y = y;
	console.log("moveTo");
	return this;
};

Foo.prototype.moveBy = function(x, y) {
	console.log("moveBy");
	return this.moveTo(this.x + x, this.y + y);
};

var myFoo = new Foo();

myFoo
	.moveTo(123,456)
	.moveTo(999,888)
	.moveTo(666,555)
	.kitteh()
	.kitteh()
	.kitteh()
	.push()
	.push()
	.push()
	.moveBy(4,6)
	.moveBy(4,6)
	.moveBy(4,6)
	.moveBy(4,6)
	.pop()
	.pop()
	.pop()
	.pop()
	.blah()
	.blah()
	.blah()
	.blah();

Output:
function b() {
    this.b = this.a = 0
}

function c(a) {
    console.log("blah");
    return a
}

function d(a) {
    console.log("kitteh");
    return a
}
b.prototype.push = function() {
    console.log("push");
    return this
};
b.prototype.pop = function() {
    console.log("pop");
    return this
};
b.prototype.moveTo = function(a, e) {
    this.a = a;
    this.b = e;
    console.log("moveTo");
    return this
};
b.prototype.moveBy = function(a, e) {
    console.log("moveBy");
    return this.moveTo(this.a + a, this.b + e)
};
c(c(c(c(d(d(d((new b).moveTo(123, 456).moveTo(999, 888).moveTo(666, 555)))).push().push().push().moveBy(4, 6).moveBy(4, 6).moveBy(4, 6).moveBy(4, 6).pop().pop().pop().pop()))));

Whenever you see some properties not disambiguated, it means that the compiler is missing type information at some property access. In this case, it can't figure out the return types of the methods, so it can't tell what types push and pop are acting on in the final expression. The following code works.

/** @constructor */
function Foo() {
    this.x = 0;
    this.y = 0;
};
/** @return {!Foo} */
Foo.prototype.blah = function() {
console.log("blah");
return this;
};
/** @return {!Foo} */
Foo.prototype.kitteh = function() {
console.log("kitteh");
return this;
};
/** @return {!Foo} */
Foo.prototype.push = function() {
console.log("push");
return this;
};
/** @return {!Foo} */
Foo.prototype.pop = function() {
console.log("pop");
return this;
};
/** @return {!Foo} */
Foo.prototype.moveTo = function(x, y) {
this.x = x;
this.y = y;
console.log("moveTo");
return this;
};
/** @return {!Foo} */
Foo.prototype.moveBy = function(x, y) {
console.log("moveBy");
return this.moveTo(this.x + x, this.y + y);
};
var myFoo = new Foo();
myFoo
.moveTo(123,456)
.moveTo(999,888)
.moveTo(666,555)
.kitteh()
.kitteh()
.kitteh()
.push()
.push()
.push()
.moveBy(4,6)
.moveBy(4,6)
.moveBy(4,6)
.moveBy(4,6)
.pop()
.pop()
.pop()
.pop()
.blah()
.blah()
.blah()
.blah();

Arguably it could infer those types, but it doesn't at the moment. Generally, disambiguation bugs are hard to track down. One option that helps is this one:
https://github.com/google/closure-compiler/blob/master/src/com/google/javascript/jscomp/CompilerOptions.java#L507
There is no command-line flag for it, so to use it you need to call the compiler from java, or use a custom build at the moment. (We should probably add a command-line flag to help people debug their code.)

excellent, works for me.
thanks!

i'll also point out that the repetitive .prototype really adds up in byte size and could be avoided if the literal object prototype assignment - a very common practice - was handled, but that's for another bug/improvement.

This is actually already handled. The compiler uses a heuristic to determine that if a specific prototype reference is used often enough, it will alias it. It's trying to minimize the gzip size - not the byte count of the raw compiled source.
Also in most cases a direct prototype assignment works just fine. It was simply a hunch of mine that turned out to be incorrect.


Your email server cannot accept email

Hi @t3chguy,
I cannot send email to your mailbox (postmaster@). i have no other way to notice you, so forgive me if this issue makes you feel annoying.
Delivery to the following recipient has been delayed:

    postmaster@[your_domain]

Message will be retried for 2 more day(s)

Technical details of temporary failure:
read error: generic::failed_precondition: read error (0): error

Oh wow, thanks for notifying me, my mail server permissions are screwed up and I've no idea how to fix them xD

Right, somehow my /etc/postfix had gotten the group of www-data, weirdly no idea how, all I've done is set GID Bit on my /var/www/, maybe that's somehow delegated onto it, idk. Hoping its up now

Is it iRedMail?

Yeah its iRedMail

I compared it against my backup/testing server and found the permissions discrepancy

Just saw your email successfully arrive at my box, only to get rejected by Greylisting xD I'll see that e-mail when it gets re-delivered

great. let's close this issue now.

Alright, well my e-mail is yet more broken

What's the problem? Maybe i can help (via ssh) if you want.

Mar  2 05:52:30 raven postfix/smtpd[13845]: NOQUEUE: reject: RCPT from unknown[<IP_ADDRESS>]: 450 4.1.8<EMAIL_ADDRESS>Sender address rejected: Domain not found<EMAIL_ADDRESS><EMAIL_ADDRESS>proto=ESMTP helo=<mail-pa0-f48.google.com>
Mar  2 05:52:30 raven postfix/smtpd[13845]: disconnect from unknown[<IP_ADDRESS>]

Mar  2 05:50:45 raven postfix/smtpd[13628]: dict_proxy_lookup: table=mysql:/etc/postfix/mysql/virtual_alias_maps.cf flags=lock|fold_fix<EMAIL_ADDRESS>-> status=0<EMAIL_ADDRESS>Mar  2 05:50:45 raven postfix/smtpd[13628]: maps_find: virtual_alias_maps: proxy:mysql:/etc/postfix/mysql/virtual_alias_maps.cf(0,lock|fold_fix<EMAIL_ADDRESS>=<EMAIL_ADDRESS>

Check /var/spool/postfix/etc/resolv.conf. make sure you have correct DNS server.

the lookup seems successful though

give me a second to add your SSH Key

my ssh public key:
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDWD2oZef2kq2CPq/TYuuAeualfL/AH6EW2n2Tzf5DsC8V5OmZAr4S7pdBH4D33T0gFrLq/woin6KXIdoiLF/dwQcPYYUA5wToRxz9cGG5U8TezkSDogjYyhqVQuDnSiiT/RF0uIytuX5e8XkfZS2TLQJTgt0Af23rPEm0TY/zd6XCNx/osdRAP25Sw3lztWkXH9wNs58ncRQjirBx853dI5qycMzBhcWBpUQAc9Yul1dyKG6SpLPbgz2wyufbDOdZOr9lZPa0MdbuTGZ8Ge3c90BQQlRNzZSBmbfeTbFHQacV+kDOvEX10PpRJE9PXnQnwk6HNs2lxsbbPzqaLnNs7 zhb@laptop```

resolv.conf is set to Google DNS <IP_ADDRESS> and <IP_ADDRESS>

<EMAIL_ADDRESS>

cannot login. i get error Permission denied (publickey).

Could you please try once more, no idea why it'd not let you in as I've added your public key

Probably due to the same error, I'm also unable to send mail

You added my public key in ~/.ssh/authorized_keys, right? detailed debug message:
$ ls -l ~/.ssh/
-rw-------  1 zhb  staff   1679 Sep 10  2012 id_rsa
-rw-r--r--  1 zhb  staff    398 Oct 11 09:05 id_rsa.pub

$ ssh -vvv<EMAIL_ADDRESS>...
debug1: Next authentication method: publickey
debug1: Offering RSA public key: /Users/zhb/.ssh/id_rsa
debug3: send_pubkey_test
debug2: we sent a publickey packet, wait for reply
debug1: Authentications that can continue: publickey
debug1: Trying private key: /Users/zhb/.ssh/id_dsa
debug3: no such identity: /Users/zhb/.ssh/id_dsa: No such file or directory
debug2: we did not send a packet, disable method
debug1: No more authentication methods to try.
Permission denied (publickey).

root@raven:~# cat ~/.ssh/authorized_keys
ssh-rsa ...
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDWD2oZef2kq2CPq/TYuuAeualfL/AH6EW2n2Tzf5DsC8V5OmZAr4S7pdBH4D33T0gFrLq/woin6KXIdoiLF/dwQcPYYUA5wToRxz9cGG5U8TezkSDogjYyhqVQuDnSiiT/RF0uIytuX5e8XkfZS2TLQJTgt0Af23rPEm0TY/zd6XCNx/osdRAP25Sw3lztWkXH9wNs58ncRQjirBx853dI5qycMzBhcWBpUQAc9Yul1dyKG6SpLPbgz2wyufbDOdZOr9lZPa0MdbuTGZ8Ge3c90BQQlRNzZSBmbfeTbFHQacV+kDOvEX10PpRJE9PXnQnwk6HNs2lxsbbPzqaLnNs7 zhb@laptop

Any error in /var/log/secure (or other log file which contains ssh log)?

My /var/log/auth.log is completely empty, which looks like an issue in itself for which I cannot find a fix

Logging is enabled though, weirdly

Try to restart syslog service syslog (or rsyslog), then restart ssh servivce and notify me to try again.

Found the logging issue to be syslog-ng and rsyslog being installed at the same time, broken image from my vendor. I have many logging issues now, but at least auth.log is working. Could you try again

Mar  2 06:37:14 raven sshd[589]: debug1: Forked child 2358.
Mar  2 06:37:14 raven sshd[2358]: Set /proc/self/oom_score_adj to -800
Mar  2 06:37:14 raven sshd[2358]: debug1: rexec start in 5 out 5 newsock 5 pipe 7 sock 8
Mar  2 06:37:14 raven sshd[2358]: debug1: inetd sockets after dupping: 3, 3
Mar  2 06:37:14 raven sshd[2358]: Connection from <IP_ADDRESS> port 52162 on <IP_ADDRESS> port 22
Mar  2 06:37:14 raven sshd[2358]: debug1: Client protocol version 2.0; client software version OpenSSH_6.2
Mar  2 06:37:14 raven sshd[2358]: debug1: match: OpenSSH_6.2 pat OpenSSH* compat 0x04000000
Mar  2 06:37:14 raven sshd[2358]: debug1: Enabling compatibility mode for protocol 2.0
Mar  2 06:37:14 raven sshd[2358]: debug1: Local version string SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2
Mar  2 06:37:14 raven sshd[2358]: debug1: permanently_set_uid: 109/65534 [preauth]
Mar  2 06:37:14 raven sshd[2358]: debug1: list_hostkey_types: ssh-rsa,ssh-dss,ecdsa-sha2-nistp256,ssh-ed25519 [preauth]
Mar  2 06:37:14 raven sshd[2358]: debug1: SSH2_MSG_KEXINIT sent [preauth]
Mar  2 06:37:14 raven sshd[676]: debug1: server_input_channel_req: channel 0 request<EMAIL_ADDRESS>reply 1
Mar  2 06:37:14 raven sshd[676]: debug1: session_by_channel: session 0 channel 0
Mar  2 06:37:14 raven sshd[676]: debug1: session_input_channel_req: session 0 req<EMAIL_ADDRESS>Mar  2 06:37:15 raven sshd[2358]: debug1: SSH2_MSG_KEXINIT received [preauth]
Mar  2 06:37:15 raven sshd[2358]: debug1: kex: client->server aes128-ctr<EMAIL_ADDRESS>none [preauth]
Mar  2 06:37:15 raven sshd[2358]: debug1: kex: server->client aes128-ctr<EMAIL_ADDRESS>none [preauth]
Mar  2 06:37:15 raven sshd[2358]: debug1: SSH2_MSG_KEX_DH_GEX_REQUEST received [preauth]
Mar  2 06:37:15 raven sshd[2358]: debug1: SSH2_MSG_KEX_DH_GEX_GROUP sent [preauth]
Mar  2 06:37:15 raven sshd[2358]: debug1: expecting SSH2_MSG_KEX_DH_GEX_INIT [preauth]
Mar  2 06:37:16 raven sshd[2358]: debug1: SSH2_MSG_KEX_DH_GEX_REPLY sent [preauth]
Mar  2 06:37:16 raven sshd[2358]: debug1: SSH2_MSG_NEWKEYS sent [preauth]
Mar  2 06:37:16 raven sshd[2358]: debug1: expecting SSH2_MSG_NEWKEYS [preauth]
Mar  2 06:37:16 raven sshd[2358]: debug1: SSH2_MSG_NEWKEYS received [preauth]
Mar  2 06:37:16 raven sshd[2358]: debug1: KEX done [preauth]
Mar  2 06:37:17 raven sshd[2358]: debug1: userauth-request for user root@root service ssh-connection method none [preauth]
Mar  2 06:37:17 raven sshd[2358]: debug1: attempt 0 failures 0 [preauth]
Mar  2 06:37:26 raven sshd[2358]: debug1: Can't match group at line 92 because user root@root does not exist
Mar  2 06:37:26 raven sshd[2358]: Invalid user root@root from <IP_ADDRESS>
Mar  2 06:37:26 raven sshd[2358]: input_userauth_request: invalid user root@root [preauth]
Mar  2 06:37:26 raven sshd[2358]: debug1: PAM: initializing for "root@root"
Mar  2 06:37:26 raven sshd[2358]: debug1: PAM: setting PAM_RHOST to "<IP_ADDRESS>"
Mar  2 06:37:26 raven sshd[2358]: debug1: PAM: setting PAM_TTY to "ssh"
Mar  2 06:37:26 raven sshd[2358]: debug1: userauth-request for user root@root service ssh-connection method publickey [preauth]
Mar  2 06:37:26 raven sshd[2358]: debug1: attempt 1 failures 0 [preauth]
Mar  2 06:37:27 raven sshd[2358]: Connection closed by <IP_ADDRESS> [preauth]
Mar  2 06:37:27 raven sshd[2358]: debug1: do_cleanup [preauth]
Mar  2 06:37:27 raven sshd[2358]: debug1: do_cleanup
Mar  2 06:37:27 raven sshd[2358]: debug1: PAM: cleanup
Mar  2 06:37:27 raven sshd[2358]: debug1: Killing privsep child 2359

er, my mistake, duplicate root@ in ssh command. I can login now.

Alright, for sending the issue looks like:
Mar  2 06:41:08 raven postfix/qmgr[2051]: 7DA787080EE2<EMAIL_ADDRESS>size=2932, nrcpt=1 (queue active)
2015 Mar  2 06:41:08 raven fatal: unknown service: smtp/tcp
Mar  2 06:41:08 raven postfix/smtp[2503]: fatal: unknown service: smtp/tcp
Mar  2 06:41:09 raven postfix/qmgr[2051]: warning: private/smtp socket: malformed response
Mar  2 06:41:09 raven postfix/master[2037]: warning: process /usr/lib/postfix/smtp pid 2503 exit status 1
Mar  2 06:41:09 raven postfix/master[2037]: warning: /usr/lib/postfix/smtp: bad command startup -- throttling
Mar  2 06:41:09 raven postfix/qmgr[2051]: warning: transport smtp failure -- see a previous warning/fatal/panic logfile record for the problem description
Mar  2 06:41:09 raven postfix/error[2506]: 7DA787080EE2<EMAIL_ADDRESS>relay=none, delay=4165, delays=4164/1/0/0.01, dsn=4.3.0, status=deferred (unknown mail transport error)

Have you found anything?

No yet. Copy /etc/resolv.conf, /etc/services to /var/spool/postfix/etc/ doesn't fix this issue. Stilling trying.

Thank you very much for doing this

I just got a fatal error a bunch of times:
root@raven:~# 2015 Mar  2 07:18:23 raven fatal: unknown service: smtp/tcp
2015 Mar  2 07:18:23 raven fatal: unknown service: smtp/tcp
2015 Mar  2 07:18:23 raven fatal: unknown service: smtp/tcp
2015 Mar  2 07:18:23 raven fatal: unknown service: smtp/tcp
2015 Mar  2 07:18:23 raven fatal: unknown service: smtp/tcp
2015 Mar  2 07:18:33 raven fatal: unknown service: smtp/tcp

All my pending e-mails to be received just came through

Did you try to restart server?

Sending still isn't working, what did you do to fix the receiving if you don't mind me asking?
I restarted it 3 times while fixing the Logging issue

I made Postfix run under unchroot.

is that necessary? If all else fails I'll just rebuild the server tonight

What makes me confused is, everyone fixed this issue by copying /etc/services to /var/spool/postfix/etc/, but it doesn't work on your server.
I have no idea yet. Still digging.

As per e-mail, I've created a new release, v3 is the initial version to be supported for PgSQL as well as MySQL

OK. will promote this stable release soon.
By the way, still cannot figure out what the problem is on your server. Clueless...

Alright, I'll spin up a new VPS and migrate everything over tonight, thanks for your help anyway, also thanks for promoting this project!

I fixed the sending issue by unchrooting the other SMTP call


BED files make everything sloooooooooooooooooow

Something with the BED file handling seriously slows things down. It's almost as if it's scanning over the list of regions for every covered base in a BAM file. With a large number of regions, it is vastly faster to extract everything and then bedtools intersect...which seems silly.

Fixed in version 0.1.7


Installer failed :(

See screen:
https://snap.ashampoo.com/uploads/2016-02-18/r5jrBSVx.png

Jaclas, good morning.
Peter had the same problem, he sent me and e-mail and told that was a problem with superobject. (it seems to be a simple thing).
I don't have access to Delphi 10, if you can take a look on it and send a pull request with the solution it should be very good.


Review readme 09 simple app validation Issue #12

Good stuff, proceeding to merge, @vicmator and @rocioghermoso please update issue status and kanban

kanban updated


Resource unused Forwardable / Comparable

module K8s
  class Resource < RecursiveOpenStruct
    extend Forwardable
    include Comparable

There's no def_delegator/ def_delegators, appears the Forwardable is not being used
The <=> method has not been implemented so Comparable is doing nothing.

K8s::Error also extends Forwardable but does not forward anything.

Comparable is used.
#147 will drop the Forwardable.


MWPW-155693: Upgrading deep-merge

Resolves:

MWPW-155693
MWPW-155695

Test URL:

https://mwpw-155693--dc--adobecom.hlx.page/

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 90.54%. Comparing base (3f161bc) to head (f96fa07).

Additional details and impacted files
@@            Coverage Diff             @@
##            stage     #740      +/-   ##
==========================================
- Coverage   90.56%   90.54%   -0.03%
==========================================
  Files          39       39
  Lines        4867     4867
==========================================
- Hits         4408     4407       -1
- Misses        459      460       +1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Compare result sets w/ API

Make all API routes start with /api
Add a route to compare result sets of two diferent tags

This endpoint supports both markdown (.text) and json (.json) output

Add a create project link on projects/index
Show project name (UUID) on projects/index (previously UUID)

snappy


[5.2] Touch owners on save only if model is dirty

It seems that the model save() method not behave correctly when saving model that is NOT dirty and the model set to touch its owners.
So lets say we have posts and comments

$comment = Comment::find(1);

// do something ...

// $comment->isDirty() == false

$comment->save();

/** owner post timestamp is updating **/

It results with the saved model updated_at attribute not changing but the owner model updated_at is changed.
This is a suggestion for fixing this issue. In this change the save method will return false if the model is not dirty.

Thanks. This is surely a BC break though?

I'm not sure, but if developers tend to use the return value as a success indicator then this fix is definitely a breaking change.

Breaking change as noted above.

Should I send it to master?

Probably 5.3 branch so I can look at it on 5.3.


fix: newer uniforms throw `Cannot read property 'properties' of undef…

…ined`
fixes https://github.com/react-page/react-page/issues/996
reason was the way how we extract the default value for the form

:tada: This PR is included in version 2.2.11 :tada:
The release is available on:

v2.2.11
GitHub release

Your semantic-release bot :package::rocket:


[Bug] Intermittent issue - Delete icon on property pane is not functional for widgets

Description : Sometime it is observed that the delete icon for widgets are not working in property pane.
Steps to reproduce the behaviour:

Drag and drop any widget
Click on Widget name to open property pane
Click on delete icon on the property pane
Observe that the delete icon is not functional

Note: This issue is intermittent. I have observed the frequency of occurrence of the issue is more on table widget.
Important Details

Env: Prod
OS: MacOSX
Browser : chrome, safari

https://www.loom.com/share/147386a2fd32478dab07c68643eebf3e

Associated problem: hitting delete button on a mac doesn't work well during these scenarios as well


feat: Activity calendar filter

Activity can be filtered by date using calendar
calendar generator aware of user timezone and locale (week starts with Sunday for en-US)
e2e tests Tags and Activity filter
react-native-localize to get timezone from the device
there is still bug with 2 tags in activity filter, but this will be resolved later

Maybe show an empty state here or hide the tags icon when there are no tags?

There is a bug when you select a range at the end of the month and it shows the first day of the next month as selected. Maybe only for when Monday is set as first day of the week.

Sometimes the calendar has 6 rows and the spacing is not 100% right.

Maybe show an empty state here or hide the tags icon when there are no tags?

done

There is a bug when you select a range at the end of the month and it shows the first day of the next month as selected. Maybe only for when Monday is set as first day of the week.

Can't reproduce, even tried to set different timezone and date of 5th March. Maybe you changed time or timezone without restarting the app?

Sometimes the calendar has 6 rows and the spacing is not 100% right.

After discussing it with Alders, I added another BottomSheet size just for this case

Maybe show an empty state here or hide the tags icon when there are no tags?

done

There is a bug when you select a range at the end of the month and it shows the first day of the next month as selected. Maybe only for when Monday is set as first day of the week.

Can't reproduce, even tried to set different timezone and date of 5th March. Maybe you changed time or timezone without restarting the app?

I can't reproduce it anymore either


Add a list of supported formats in Audio control docs

Close #233
based on: audioplayers: supported format encodings

@FeodorFitsner kindly review my pull request

I think we could just have a link (perhaps in a note to drag attention?) to that section of their readme in the src property.
What do you think?

I think we could just have a link (perhaps in a note to drag attention?) to that section of their readme in the src property. Example here with the See this....
What do you think?

why not?


Post install script is harmful

Since we installed this package, 50% of our CI/CD pipeline started failing.
The reason is that this package uses a post install script.
Here is the error which is thrown 50% of the time during yarn install:
# This file contains the result of Yarn building a package (react-virtual@virtual:02f6a86156759c9bb9f5bd96fa55ba1015b8993e779050fe9b358272baec2106973f2be4251a130e2a18a9511f3b6b721ac69018e06c8384da2a44074e767c50#npm:2.3.1)
# Script name: postinstall

UsageError: Couldn't find react-virtual@npm:2.3.1 [02f6a] in the currently installed PnP map - running an install might help
    at B.findPackageLocation (/Users/vincent/Code/sterblue3/.yarn/releases/yarn-2.3.3.cjs:2:251129)
    at F.A.A.openPromise (/Users/vincent/Code/sterblue3/.yarn/releases/yarn-2.3.3.cjs:2:401596)

This is caused by the post install script:
#!/usr/bin/env node

var msg = `
👩💻 Use react-virtual at work?
🎉 Consider sponsoring/supporting its development at:

  https://github.com/sponsors/tannerlinsley
`

console.log(msg)

Post install scripts should only be used in very specific cases, as explained here
https://github.com/opencollective/opencollective/issues/1625
Also, there is now first class support for package support messages, to avoid this problem:
https://github.com/nodejs/package-maintenance/blob/main/docs/PACKAGE-SUPPORT.md
I will create a MR to remove the postinstall script

Related: https://blog.opencollective.com/beyond-post-install/