text:
Erro na Instalação - Could not create an acl object: Invalid Document

Olá.
Instalei o PagSeguro na versão 2.19 do magento sem nenhum outro modulo ou alteração realizada, e os problemas abaixo foram apresentados.
Versão: Magento 2.1.9 (sem dados de exemplo)
Versão PHP: 7.0.25
Versão MySQL: 5.6
Procedimento utilizado para instalação do modulo PagSeguro (SSH):
php bin/magento deploy:mode:set developer
composer require pagseguro/magento2
php bin/magento setup:upgrade
php bin/magento setup:static-content:deploy pt_BR

Resultado esperado:
Modulo de Pagamento PagSeguro funcionando
Resultado apresentado quando me logo no admin:
1 exception(s):
Exception #0 (LogicException): Could not create an acl object: Invalid Document
Element 'resource': This element is not expected.
Line: 3

Exception #0 (LogicException): Could not create an acl object: Invalid Document
Element 'resource': This element is not expected.
Line: 3

#0 /chroot/home/mestrema/mestremagento.com.br/html/loja/var/generation/Magento/Framework/Acl/Builder/Proxy.php(95): Magento\Framework\Acl\Builder->getAcl()
#1 /chroot/home/mestrema/mestremagento.com.br/html/loja/vendor/magento/module-backend/Model/Auth/Session.php(221): Magento\Framework\Acl\Builder\Proxy->getAcl()
#2 /chroot/home/mestrema/mestremagento.com.br/html/loja/vendor/magento/module-backend/Model/Auth.php(156): Magento\Backend\Model\Auth\Session->processLogin()
#3 /chroot/home/mestrema/mestremagento.com.br/html/loja/vendor/magento/framework/Interception/Interceptor.php(146): Magento\Backend\Model\Auth->login('suporte', 'net12345')
#4 /chroot/home/mestrema/mestremagento.com.br/html/loja/var/generation/Magento/Backend/Model/Auth/Interceptor.php(26): Magento\Backend\Model\Auth\Interceptor->___callPlugins('login', Array, Array)
#5 /chroot/home/mestrema/mestremagento.com.br/html/loja/vendor/magento/module-backend/App/Action/Plugin/Authentication.php(205): Magento\Backend\Model\Auth\Interceptor->login('suporte', 'net12345')
#6 /chroot/home/mestrema/mestremagento.com.br/html/loja/vendor/magento/module-backend/App/Action/Plugin/Authentication.php(157): Magento\Backend\App\Action\Plugin\Authentication->_performLogin(Object(Magento\Framework\App\Request\Http))
#7 /chroot/home/mestrema/mestremagento.com.br/html/loja/vendor/magento/module-backend/App/Action/Plugin/Authentication.php(125): Magento\Backend\App\Action\Plugin\Authentication->_processNotLoggedInUser(Object(Magento\Framework\App\Request\Http))
#8 /chroot/home/mestrema/mestremagento.com.br/html/loja/vendor/magento/framework/Interception/Chain/Chain.php(67): Magento\Backend\App\Action\Plugin\Authentication->aroundDispatch(Object(Magento\Backend\Controller\Adminhtml\Index\Index\Interceptor), Object(Closure), Object(Magento\Framework\App\Request\Http))
#9 /chroot/home/mestrema/mestremagento.com.br/html/loja/vendor/magento/framework/Interception/Interceptor.php(138): Magento\Framework\Interception\Chain\Chain->invokeNext('Magento\\Backend...', 'dispatch', Object(Magento\Backend\Controller\Adminhtml\Index\Index\Interceptor), Array, 'adminMassaction...')
#10 /chroot/home/mestrema/mestremagento.com.br/html/loja/vendor/magento/module-backend/App/Action/Plugin/MassactionKey.php(33): Magento\Backend\Controller\Adminhtml\Index\Index\Interceptor->Magento\Framework\Interception\{closure}(Object(Magento\Framework\App\Request\Http))
#11 /chroot/home/mestrema/mestremagento.com.br/html/loja/vendor/magento/framework/Interception/Interceptor.php(142): Magento\Backend\App\Action\Plugin\MassactionKey->aroundDispatch(Object(Magento\Backend\Controller\Adminhtml\Index\Index\Interceptor), Object(Closure), Object(Magento\Framework\App\Request\Http))
#12 /chroot/home/mestrema/mestremagento.com.br/html/loja/var/generation/Magento/Backend/Controller/Adminhtml/Index/Index/Interceptor.php(26): Magento\Backend\Controller\Adminhtml\Index\Index\Interceptor->___callPlugins('dispatch', Array, Array)
#13 /chroot/home/mestrema/mestremagento.com.br/html/loja/vendor/magento/framework/App/FrontController.php(55): Magento\Backend\Controller\Adminhtml\Index\Index\Interceptor->dispatch(Object(Magento\Framework\App\Request\Http))
#14 /chroot/home/mestrema/mestremagento.com.br/html/loja/vendor/magento/framework/Interception/Interceptor.php(74): Magento\Framework\App\FrontController->dispatch(Object(Magento\Framework\App\Request\Http))
#15 /chroot/home/mestrema/mestremagento.com.br/html/loja/vendor/magento/framework/Interception/Chain/Chain.php(70): Magento\Framework\App\FrontController\Interceptor->___callParent('dispatch', Array)
#16 /chroot/home/mestrema/mestremagento.com.br/html/loja/vendor/magento/framework/Interception/Interceptor.php(138): Magento\Framework\Interception\Chain\Chain->invokeNext('Magento\\Framewo...', 'dispatch', Object(Magento\Framework\App\FrontController\Interceptor), Array, 'install')
#17 /chroot/home/mestrema/mestremagento.com.br/html/loja/vendor/magento/framework/Module/Plugin/DbStatusValidator.php(69): Magento\Framework\App\FrontController\Interceptor->Magento\Framework\Interception\{closure}(Object(Magento\Framework\App\Request\Http))
#18 /chroot/home/mestrema/mestremagento.com.br/html/loja/vendor/magento/framework/Interception/Interceptor.php(142): Magento\Framework\Module\Plugin\DbStatusValidator->aroundDispatch(Object(Magento\Framework\App\FrontController\Interceptor), Object(Closure), Object(Magento\Framework\App\Request\Http))
#19 /chroot/home/mestrema/mestremagento.com.br/html/loja/var/generation/Magento/Framework/App/FrontController/Interceptor.php(26): Magento\Framework\App\FrontController\Interceptor->___callPlugins('dispatch', Array, Array)
#20 /chroot/home/mestrema/mestremagento.com.br/html/loja/vendor/magento/framework/App/Http.php(135): Magento\Framework\App\FrontController\Interceptor->dispatch(Object(Magento\Framework\App\Request\Http))
#21 /chroot/home/mestrema/mestremagento.com.br/html/loja/vendor/magento/framework/App/Bootstrap.php(258): Magento\Framework\App\Http->launch()
#22 /chroot/home/mestrema/mestremagento.com.br/html/loja/index.php(39): Magento\Framework\App\Bootstrap->run(Object(Magento\Framework\App\Http))
#23 {main}

Quando tento compilar:
Errors during compilation:
	UOL\PagSeguro\Model\Transactions\Methods\Refund
		Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Refund in /chroot/home/mestrema/mestremagento.com.br/html/loja/vendor/pagseguro/magento2/Model/Transactions/Methods/Refund.php
\Magento\Framework\App\ResourceConnection already exists in context object
	UOL\PagSeguro\Model\Transactions\Methods\Conciliation
		Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Conciliation in /chroot/home/mestrema/mestremagento.com.br/html/loja/vendor/pagseguro/magento2/Model/Transactions/Methods/Conciliation.php
\Magento\Framework\App\ResourceConnection already exists in context object
	UOL\PagSeguro\Model\Transactions\Methods\Cancellation
		Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Cancellation in /chroot/home/mestrema/mestremagento.com.br/html/loja/vendor/pagseguro/magento2/Model/Transactions/Methods/Cancellation.php
\Magento\Framework\App\ResourceConnection already exists in context object
	UOL\PagSeguro\Model\Transactions\Methods\Abandoned
		Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Abandoned in /chroot/home/mestrema/mestremagento.com.br/html/loja/vendor/pagseguro/magento2/Model/Transactions/Methods/Abandoned.php
\Magento\Framework\App\ResourceConnection already exists in context object
Total Errors Count: 4

Errors during compilation:
	UOL\PagSeguro\Model\Transactions\Methods\Refund
		Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Refund in /chroot/home/mestrema/mestremagento.com.br/html/loja/vendor/pagseguro/magento2/Model/Transactions/Methods/Refund.php
\Magento\Framework\App\ResourceConnection already exists in context object
	UOL\PagSeguro\Model\Transactions\Methods\Conciliation
		Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Conciliation in /chroot/home/mestrema/mestremagento.com.br/html/loja/vendor/pagseguro/magento2/Model/Transactions/Methods/Conciliation.php
\Magento\Framework\App\ResourceConnection already exists in context object
	UOL\PagSeguro\Model\Transactions\Methods\Cancellation
		Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Cancellation in /chroot/home/mestrema/mestremagento.com.br/html/loja/vendor/pagseguro/magento2/Model/Transactions/Methods/Cancellation.php
\Magento\Framework\App\ResourceConnection already exists in context object
	UOL\PagSeguro\Model\Transactions\Methods\Abandoned
		Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Abandoned in /chroot/home/mestrema/mestremagento.com.br/html/loja/vendor/pagseguro/magento2/Model/Transactions/Methods/Abandoned.php
\Magento\Framework\App\ResourceConnection already exists in context object
Total Errors Count: 4

Errors during compilation:
	UOL\PagSeguro\Model\Transactions\Methods\Refund
		Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Refund in /chroot/home/mestrema/mestremagento.com.br/html/loja/vendor/pagseguro/magento2/Model/Transactions/Methods/Refund.php
\Magento\Framework\App\ResourceConnection already exists in context object
	UOL\PagSeguro\Model\Transactions\Methods\Conciliation
		Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Conciliation in /chroot/home/mestrema/mestremagento.com.br/html/loja/vendor/pagseguro/magento2/Model/Transactions/Methods/Conciliation.php
\Magento\Framework\App\ResourceConnection already exists in context object
	UOL\PagSeguro\Model\Transactions\Methods\Cancellation
		Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Cancellation in /chroot/home/mestrema/mestremagento.com.br/html/loja/vendor/pagseguro/magento2/Model/Transactions/Methods/Cancellation.php
\Magento\Framework\App\ResourceConnection already exists in context object
	UOL\PagSeguro\Model\Transactions\Methods\Abandoned
		Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Abandoned in /chroot/home/mestrema/mestremagento.com.br/html/loja/vendor/pagseguro/magento2/Model/Transactions/Methods/Abandoned.php
\Magento\Framework\App\ResourceConnection already exists in context object
Total Errors Count: 4

Errors during compilation:
	UOL\PagSeguro\Model\Transactions\Methods\Refund
		Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Refund in /chroot/home/mestrema/mestremagento.com.br/html/loja/vendor/pagseguro/magento2/Model/Transactions/Methods/Refund.php
\Magento\Framework\App\ResourceConnection already exists in context object
	UOL\PagSeguro\Model\Transactions\Methods\Conciliation
		Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Conciliation in /chroot/home/mestrema/mestremagento.com.br/html/loja/vendor/pagseguro/magento2/Model/Transactions/Methods/Conciliation.php
\Magento\Framework\App\ResourceConnection already exists in context object
	UOL\PagSeguro\Model\Transactions\Methods\Cancellation
		Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Cancellation in /chroot/home/mestrema/mestremagento.com.br/html/loja/vendor/pagseguro/magento2/Model/Transactions/Methods/Cancellation.php
\Magento\Framework\App\ResourceConnection already exists in context object
	UOL\PagSeguro\Model\Transactions\Methods\Abandoned
		Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Abandoned in /chroot/home/mestrema/mestremagento.com.br/html/loja/vendor/pagseguro/magento2/Model/Transactions/Methods/Abandoned.php
\Magento\Framework\App\ResourceConnection already exists in context object
Total Errors Count: 4

Para mim esse erro continua:
Magento 2.1.7
  UOL\PagSeguro\Model\Transactions\Methods\Cancellation
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Cancellation in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Cancellation.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Conciliation
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Conciliation in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Conciliation.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Refund
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Refund in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Refund.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Abandoned
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Abandoned in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Abandoned.php
\Magento\Framework\App\ResourceConnection already exists in context object
Total Errors Count: 4
Errors during compilation:
  UOL\PagSeguro\Model\Transactions\Methods\Cancellation
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Cancellation in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Cancellation.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Conciliation
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Conciliation in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Conciliation.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Refund
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Refund in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Refund.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Abandoned
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Abandoned in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Abandoned.php
\Magento\Framework\App\ResourceConnection already exists in context object
Total Errors Count: 4
Errors during compilation:
  UOL\PagSeguro\Model\Transactions\Methods\Cancellation
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Cancellation in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Cancellation.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Conciliation
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Conciliation in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Conciliation.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Refund
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Refund in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Refund.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Abandoned
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Abandoned in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Abandoned.php
\Magento\Framework\App\ResourceConnection already exists in context object
Total Errors Count: 4
Errors during compilation:
  UOL\PagSeguro\Model\Transactions\Methods\Cancellation
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Cancellation in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Cancellation.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Conciliation
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Conciliation in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Conciliation.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Refund
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Refund in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Refund.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Abandoned
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Abandoned in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Abandoned.php
\Magento\Framework\App\ResourceConnection already exists in context object
Total Errors Count: 4
Errors during compilation:
  UOL\PagSeguro\Model\Transactions\Methods\Cancellation
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Cancellation in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Cancellation.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Conciliation
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Conciliation in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Conciliation.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Refund
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Refund in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Refund.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Abandoned
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Abandoned in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Abandoned.php
\Magento\Framework\App\ResourceConnection already exists in context object
Total Errors Count: 4
Errors during compilation:
  UOL\PagSeguro\Model\Transactions\Methods\Cancellation
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Cancellation in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Cancellation.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Conciliation
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Conciliation in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Conciliation.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Refund
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Refund in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Refund.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Abandoned
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Abandoned in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Abandoned.php
\Magento\Framework\App\ResourceConnection already exists in context object
Total Errors Count: 4
Errors during compilation:
  UOL\PagSeguro\Model\Transactions\Methods\Cancellation
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Cancellation in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Cancellation.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Conciliation
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Conciliation in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Conciliation.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Refund
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Refund in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Refund.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Abandoned
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Abandoned in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Abandoned.php
\Magento\Framework\App\ResourceConnection already exists in context object
Total Errors Count: 4
Errors during compilation:
  UOL\PagSeguro\Model\Transactions\Methods\Cancellation
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Cancellation in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Cancellation.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Conciliation
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Conciliation in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Conciliation.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Refund
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Refund in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Refund.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Abandoned
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Abandoned in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Abandoned.php
\Magento\Framework\App\ResourceConnection already exists in context object
Total Errors Count: 4
Errors during compilation:
  UOL\PagSeguro\Model\Transactions\Methods\Cancellation
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Cancellation in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Cancellation.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Conciliation
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Conciliation in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Conciliation.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Refund
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Refund in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Refund.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Abandoned
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Abandoned in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Abandoned.php
\Magento\Framework\App\ResourceConnection already exists in context object
Total Errors Count: 4
Errors during compilation:
  UOL\PagSeguro\Model\Transactions\Methods\Cancellation
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Cancellation in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Cancellation.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Conciliation
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Conciliation in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Conciliation.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Refund
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Refund in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Refund.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Abandoned
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Abandoned in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Abandoned.php
\Magento\Framework\App\ResourceConnection already exists in context object
Total Errors Count: 4
Errors during compilation:
  UOL\PagSeguro\Model\Transactions\Methods\Cancellation
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Cancellation in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Cancellation.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Conciliation
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Conciliation in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Conciliation.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Refund
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Refund in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Refund.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Abandoned
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Abandoned in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Abandoned.php
\Magento\Framework\App\ResourceConnection already exists in context object
Total Errors Count: 4
Errors during compilation:
  UOL\PagSeguro\Model\Transactions\Methods\Cancellation
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Cancellation in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Cancellation.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Conciliation
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Conciliation in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Conciliation.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Refund
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Refund in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Refund.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Abandoned
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Abandoned in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Abandoned.php
\Magento\Framework\App\ResourceConnection already exists in context object
Total Errors Count: 4
Errors during compilation:
  UOL\PagSeguro\Model\Transactions\Methods\Cancellation
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Cancellation in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Cancellation.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Conciliation
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Conciliation in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Conciliation.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Refund
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Refund in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Refund.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Abandoned
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Abandoned in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Abandoned.php
\Magento\Framework\App\ResourceConnection already exists in context object
Total Errors Count: 4
Errors during compilation:
  UOL\PagSeguro\Model\Transactions\Methods\Cancellation
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Cancellation in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Cancellation.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Conciliation
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Conciliation in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Conciliation.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Refund
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Refund in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Refund.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Abandoned
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Abandoned in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Abandoned.php
\Magento\Framework\App\ResourceConnection already exists in context object
Total Errors Count: 4
Errors during compilation:
  UOL\PagSeguro\Model\Transactions\Methods\Cancellation
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Cancellation in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Cancellation.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Conciliation
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Conciliation in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Conciliation.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Refund
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Refund in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Refund.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Abandoned
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Abandoned in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Abandoned.php
\Magento\Framework\App\ResourceConnection already exists in context object
Total Errors Count: 4
Errors during compilation:
  UOL\PagSeguro\Model\Transactions\Methods\Cancellation
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Cancellation in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Cancellation.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Conciliation
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Conciliation in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Conciliation.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Refund
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Refund in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Refund.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Abandoned
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Abandoned in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Abandoned.php
\Magento\Framework\App\ResourceConnection already exists in context object
Total Errors Count: 4
Errors during compilation:
  UOL\PagSeguro\Model\Transactions\Methods\Cancellation
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Cancellation in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Cancellation.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Conciliation
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Conciliation in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Conciliation.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Refund
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Refund in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Refund.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Abandoned
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Abandoned in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Abandoned.php
\Magento\Framework\App\ResourceConnection already exists in context object
Total Errors Count: 4
Errors during compilation:
  UOL\PagSeguro\Model\Transactions\Methods\Cancellation
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Cancellation in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Cancellation.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Conciliation
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Conciliation in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Conciliation.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Refund
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Refund in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Refund.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Abandoned
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Abandoned in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Abandoned.php
\Magento\Framework\App\ResourceConnection already exists in context object
Total Errors Count: 4
Errors during compilation:
  UOL\PagSeguro\Model\Transactions\Methods\Cancellation
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Cancellation in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Cancellation.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Conciliation
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Conciliation in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Conciliation.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Refund
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Refund in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Refund.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Abandoned
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Abandoned in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Abandoned.php
\Magento\Framework\App\ResourceConnection already exists in context object
Total Errors Count: 4
Errors during compilation:
  UOL\PagSeguro\Model\Transactions\Methods\Cancellation
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Cancellation in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Cancellation.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Conciliation
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Conciliation in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Conciliation.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Refund
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Refund in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Refund.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Abandoned
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Abandoned in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Abandoned.php
\Magento\Framework\App\ResourceConnection already exists in context object
Total Errors Count: 4
Errors during compilation:
  UOL\PagSeguro\Model\Transactions\Methods\Cancellation
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Cancellation in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Cancellation.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Conciliation
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Conciliation in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Conciliation.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Refund
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Refund in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Refund.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Abandoned
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Abandoned in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Abandoned.php
\Magento\Framework\App\ResourceConnection already exists in context object
Total Errors Count: 4
Errors during compilation:
  UOL\PagSeguro\Model\Transactions\Methods\Cancellation
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Cancellation in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Cancellation.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Conciliation
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Conciliation in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Conciliation.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Refund
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Refund in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Refund.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Abandoned
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Abandoned in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Abandoned.php
\Magento\Framework\App\ResourceConnection already exists in context object
Total Errors Count: 4
Errors during compilation:
  UOL\PagSeguro\Model\Transactions\Methods\Cancellation
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Cancellation in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Cancellation.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Conciliation
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Conciliation in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Conciliation.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Refund
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Refund in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Refund.php
\Magento\Framework\App\ResourceConnection already exists in context object
  UOL\PagSeguro\Model\Transactions\Methods\Abandoned
    Incorrect dependency in class UOL\PagSeguro\Model\Transactions\Methods\Abandoned in {dir}vendor/pagseguro/magento2/Model/Transactions/Methods/Abandoned.php
\Magento\Framework\App\ResourceConnection already exists in context object
Total Errors Count: 4
Interception cache generation... 7/7 [============================] 100% 2 mins 198.0 MiB
Generated code and dependency injection configuration successfully.

authors: arielcugenotta nerijunior


text:
Add cli option to print warnings

When I run the CLI it tells me there are 167 warnings in my repo, but I see no way of inspecting those warnings, so a CLI flag would be helpful I think.

If I understand correctly: you can try running with --warning flag, this might give you a basic idea. Using --debug flag will give you a complex debug output, which is very verbose and noisy, but should tell you all there is to log :)

Thanks that works! I don't know how I missed that option 🤦♂

source: gharchive/issue

repo: pahen/madge

license: mit

license_type: permissive

license_source: bigquery


text:
Suspending inside a FOR-Loop breaks the loop

Hi, I am implementing a simple WAIT function which waits a few seconds (non-blocking since I do it inside Unreal Engine 4), and it works great with mb_schedule_suspend(s, MB_FUNC_SUSPEND) and mb_run(s, false);
However I stumbled across a bug, suspending inside a FOR-Loop will not resume when calling mb_run. Here is my implementation of WAIT:
int wait(struct mb_interpreter_t* s, void** l)
{
	// Will return OK
	int result = MB_FUNC_OK;

	// Holds the delay to wait (in milliseconds)
	int delay = 0;

	// Needed otherwise we can't return values!
	mb_check(mb_attempt_func_begin(s, l));
	mb_check(mb_attempt_func_end(s, l));

	// Check if an argument was passed
	if (mb_has_arg(s, l))
	{
		// Try to read an int argument into &delay
		mb_check(mb_pop_int(s, l, &delay));
	}

	// Suspend the BASIC execution until we start it again using mb_run
	mb_schedule_suspend(s, MB_FUNC_SUSPEND);
	UE_LOG(LogTemp, Log, TEXT("Suspended"));

	// Set up a timer to wait for the specified time
	float DelayTime = delay / 1000.f;
	FTimerHandle ResumeTimer;
	BasicWorldRef->GetTimerManager().SetTimer(ResumeTimer, [=]() {
		// After the UE4 timer triggered, call mb_run to resume the execution where it left of
		UE_LOG(LogTemp, Log, TEXT("Resumed"));
		mb_run(s, false);
	}, DelayTime, false);

	return result;
}

And here's my BASIC code to test with:
PRINT "Waiting in a loop"
FOR a=1 TO 5
  PRINT "In the loop!",a
  WAIT 1000
  NEXT a

PRINT "Finished"

It is printing the first "In the loop!" and "1", but then nothing happens, so it won't reach the next iteration (probably NEXT lost the reference to the for loop?)

Bumping this, as I want to start implementing this feature shortly. I couldn't make sense out of the my_basic source code myself, otherwise I would have tried to fix it myself. @paladin-t

@paladin-t

The suspending feature was reserved from a very early version (almost a decade ago) of MY-BASIC. it is obsolete, and not suggested now.
Sorry this doesn't answer the question, but consider using other fiber/setcontext/coroutine lib for a workaround.

Ah, thanks! For me, I solved the issue by not using suspend / pause at all, but make the Basic execution completely sync and blocking, and then let it run in its own thread. Might not be the optimal solution for anyone, but for me it works!

closing for now.

authors: iUltimateLP paladin-t sa-tasche


text:
Plugin upgrades do not require the user to restart there IDE

Before this PR
Whenever we upgraded the plugin users were required to do a full restart of there IDE
After this PR
Now the plugin should be able to upgrade without forcing the user to restart there IDE as we have set requires-restart=false
All checks have been ran to ensure dynamic upgrading works see https://plugins.jetbrains.com/docs/intellij/dynamic-plugins.html?from=jetbrains.org

==COMMIT_MSG==
Plugin upgrades do not require the user to restart there IDE
==COMMIT_MSG==
Possible downsides?
There is no easy way to run this as part of gradle, previously https://github.com/JetBrains/inspection-plugin would have worked but the project has now been deprecated in favour of https://www.jetbrains.com/qodana/ which is too heavy handed for this plugin. This means we have no automated ways of ensuring that the checks are ran in the future

:+1:

source: gharchive/pull-request

authors: CRogers FinlayRJW

license_source: github-api


text:
Publish docker images

Fixes #164

Most recent failure looked like it hung on the dist publish:
[INFO] Spark Integration for Kafka 0.10 ................... SUCCESS [ 31.655 s]
[INFO] Spark Integration for Kafka 0.10 Assembly .......... SUCCESS [ 13.120 s]
[INFO] Kafka 0.10 Source for Structured Streaming ......... SUCCESS [ 35.614 s]
[INFO] Spark Project Dist Provided Hadoop ................. SUCCESS [  4.667 s]
[INFO] Spark Project Dist Palantir Hadoop ................. SUCCESS [  6.766 s]
[INFO] Spark Project Kinesis Assembly ..................... SUCCESS [  8.061 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 33:42 min
[INFO] Finished at: 2017-05-23T22:15:48Z
[INFO] Final Memory: 120M/1353M
[INFO] ------------------------------------------------------------------------
Publishing dist hadoop-2.8.0-palantir3 -Phadoop-cloud -Phadoop-palantir -Pkinesis-asl -Pkubernetes -Phive -Pyarn -Psparkr ...

Moving to publish this internally from the Spark dists

repo: palantir/spark


text:
@deprecated should be associated to a specific overload.

Bug Report

TSLint version: 5.4.2
TypeScript version: 2.3.4
Running TSLint via: CLI, VSCode

TypeScript code being linted
function foo<T>(): T;
/** @deprecated */
function foo(bar: any): any;
function foo() { }

foo<number>();

with tslint.json configuration:
{
  "extends": "vts"
}

Actual behavior
foo is deprecated. (deprecation)

Expected behavior
No error.

Running into this with Angular Injector: https://github.com/angular/angular/blob/d9d00bd/packages/core/src/di/injector.ts#L53

For the reference: I have the same problem as @buu700
#2883 will fix this. It's only waiting for a reviewer.

authors: ajafff buu700 vilic

repo: palantir/tslint


text:
Django 4.2+ compatible setup_query

This PR should fix the incompatibility described in the issue https://github.com/palewire/django-postgres-copy/issues/160

I apologize for starting a new PR. I did notice the https://github.com/palewire/django-postgres-copy/pull/166 right after I submitted this one (as usual :sweat_smile: ).
I do however believe that this PR's solution is faster, simpler, less error-prone, and more future-proof than inspecting super().setup_query and deciding which kwargs to use. And since this is an inherited method, we do not need to re-declare the defaults, we can just pass whatever the callee passed in and let the parent's implementation handle it.

@bbajuzik would be cool if fix is this simple, probably less error prone than PR mentioned.
Anyway happy if this incompatibility would get solved for this great tool.

authors: bbajuzik jykae

repo: palewire/django-postgres-copy

license: MIT


text:
Preventing prompts without tty from echoing their outputs

fixes #906

Thanks for working on this. However, after looking at the issue again, I'm not clear why we want to hide the error. This fix just hides the error but enables the same insecure echoing. I'm going to close this as I don't think it needs to be fixed. See my comment in the linked issue.

authors: davidism icreatedanaccount

repo: pallets/click


text:
Why secure_filename() returns only ASCII string?

Can you please explain meaning of 'maximum portability' in 'The filename returned is an ASCII only string for maximum portability'?
I can find encoding way for utf-8 from 'http://www.voidcn.com/article/p-cxjdqemb-bpc.html'

Storing non-ascii filenames is a great way to end up with broken paths when moving between systems.

authors: LeeInHaeng ThiefMaster

repo: pallets/werkzeug


text:
SharedDataMiddleware does not support unicode paths

The static file serving currently does not support unicode paths on either 2.x or 3.x but it fails in different ways.  On Python 3 it lacks the WSGI encoding dance and on 2.x it hopes the URL encoding is the FS encoding.

I can't reproduce this issue. I created a file called 実験.txt and used the following app:
from werkzeug.exceptions import NotFound
from werkzeug.middleware.shared_data import SharedDataMiddleware

@Request.application
def app(request):
    return NotFound()

app = SharedDataMiddleware(app, {"/static": ""})

python -m werkzeug.serving example:app

Navigating to https://127.0.0.1:5000/static/実験.txt correctly served the file with Python 2 and Python 3.

authors: davidism mitsuhiko


text:
pandas.DataFrame.from_dict : issue with dtype and columns arguments types

Describe the bug
issue with types for pandas.DataFrame.from_dict method:

dtype is restricted to str in the stub file when pands allows for str, type and None
columns is restricted to list of strings when pandas allows for much more (at least: str, int, float, datetime)

To Reproduce

minimal exemple:

import pandas as pd
import datetime

data = {'l1': [1, 2, 3],
        'l2': [4, 5, 6]}

# all of the following are accepted by pandas
# however mypy complains with the last 3
pd.DataFrame.from_dict(data, orient='index')  # OK
pd.DataFrame.from_dict(data, orient='index', dtype='float')  # OK
pd.DataFrame.from_dict(data, orient='index', columns=['a', 'b', 'c'])  # OK
pd.DataFrame.from_dict(data, orient='index', dtype=float)  # NOK
pd.DataFrame.from_dict(data, orient='index', dtype=None)  # NOK
pd.DataFrame.from_dict(data, orient='index',
                       columns=[1.0, 2, datetime.datetime.now()])  # NOK

type checker :  mypy
typing errors:

from_dict_test.py:12: error: Argument "dtype" to "from_dict" of "DataFrame" has incompatible type "type[float]"; expected "str"  [arg-type]
from_dict_test.py:13: error: Argument "dtype" to "from_dict" of "DataFrame" has incompatible type "None"; expected "str"  [arg-type]
from_dict_test.py:15: error: List item 0 has incompatible type "float"; expected "str"  [list-item]
from_dict_test.py:15: error: List item 1 has incompatible type "int"; expected "str"  [list-item]
from_dict_test.py:15: error: List item 2 has incompatible type "datetime"; expected "str"  [list-item]

Please complete the following information:

OS: Windows
Windows 10 22H2   build: 19045.4170
Python 3.12.2 | packaged by Anaconda, Inc. | (main, Feb 27 2024, 17:28:07) [MSC v.1916 64 bit (AMD64)] on win32
mypy                          1.9.0
pandas-stubs                  2.2.0.240218

Thanks for the report.
There are multiple issues with the stub for DataFrame.from_dict().

Argument dtype should be AsTypeArg | None
Argument columns should be Axes | None, but only if orient==Literal["index"]

So those updates could be done to the stubs, with an appropriate overload to handle the columns argument only being accepted for orient=="index" .
PR with tests welcome.

I think I can handle that, I'll give it a try anyway. Thanks for the tips

authors: Dr-Irv mutricyl

repo: pandas-dev/pandas-stubs


text:
Release 2.1.117

Backlog:

[ ] Allow system_site_packages=True in Virtualenv.create() #1973
[ ] Cleanup sys.path after pex is imported #1959
[ ] importing a pex leaks bootstrap vendored code #1954
[ ] The --compile option is only useful for Python 2.7 #1939
[ ] Universal lock creation failure for disjoint IC and Requires-Python is correct but the error message from Pip / Pex is confusing. #1927
[ ] The __pex__ import hook does not handle registering top level PEP-420 packages #1910
[ ] The --resolve-local-platforms option does not work with --complete-platforms #1899
[ ] Expose setuptools and wheel version flags for use with non-vendored Pips. #1895
[ ] Plumb --pip-version to Platform tag calculation. #1894

[ ] PEX_INHERIT_PATH+default shebangs don't interact well with virtualenvs #1344
[ ] Pex interpreter cache is not upgrade / downgrade safe. #1176
[ ] Provide a better resolve error message for a Platform DistributionTarget when --resolve-local-platforms. #1070
[ ] Remove PEX_PYTHON_PATH from build time interpreter selection. #1075

Moved from "Release 2.1.111 #1993" to make way for #1991.

repo: pantsbuild/pex


text:
似乎是找不到二维码图片?

[2024-10-31 21:19:44][ERROR]: 启动时发生错误: [WinError 2] 系统找不到指定的文件。
[2024-10-31 21:19:44][ERROR]: 错误详情：
Traceback (most recent call last):
File "D:\CODE\WECHAT2\agent_chat_wechat\main.py", line 162, in main_task
await core.auto_login(hot_reload=False)
File "D:\ProgramData\anaconda3\envs\WeCHART\lib\site-packages\vchat\core\register.py", line 51, in auto_login
await self._login(
File "D:\ProgramData\anaconda3\envs\WeCHART\lib\site-packages\vchat\core\login.py", line 43, in _login
resp_text = await self._get_uuid_and_wait_for_scan(
File "D:\ProgramData\anaconda3\envs\WeCHART\lib\site-packages\vchat\core\login.py", line 107, in _get_uuid_and_wait_for_scan
await self.get_qr(self.uuid, enable_cmd_qr, pic_path, qr_callback)
File "D:\ProgramData\anaconda3\envs\WeCHART\lib\site-packages\vchat\core\login.py", line 81, in get_qr
utils.print_qr(pic_path)
File "D:\ProgramData\anaconda3\envs\WeCHART\lib\site-packages\vchat\utils.py", line 85, in print_qr
subprocess.call(["start", file_path])
File "D:\ProgramData\anaconda3\envs\WeCHART\lib\subprocess.py", line 345, in call
with Popen(*popenargs, **kwargs) as p:
File "D:\ProgramData\anaconda3\envs\WeCHART\lib\subprocess.py", line 971, in init
self._execute_child(args, executable, preexec_fn, close_fds,
File "D:\ProgramData\anaconda3\envs\WeCHART\lib\subprocess.py", line 1456, in _execute_child
hp, ht, pid, tid = _winapi.CreateProcess(executable, args,
FileNotFoundError: [WinError 2] 系统找不到指定的文件。
[2024-10-31 21:19:44][INFO]: 程序退出。

我的猜测是系统环境的问题，这个是VChat框架的问题，我在部署到我朋友的电脑发现了这个问题，在我自己笔记本，主机目前是没有这个问题

我的猜测是电脑系统环境的问题，我在部署到我朋友的电脑也发现了这个问题，在我自己笔记本/主机和其他朋友的电脑，目前是没有出现这个问题，我后面有时间整一下这个问题

我后续有时间，解决一下这个问题，在我其中的一个朋友电脑上有出现这个问题，其他朋友的电脑是都没问题的

解决问题的办法就是：
根据你的路径设置，打开D:\ProgramData\anaconda3\envs\WeCHART\lib\site-packages\vchat\utils.py这个文件，
找到：print_qr函数
替换下列代码：
def print_qr(file_path):
if config.OS == "linux":
subprocess.call(["xdg-open", file_path])
elif config.OS == "win32":
subprocess.call(["explorer", file_path])
elif config.OS == "darwin":
subprocess.call(["open", file_path])
else:
raise NotImplementedError

如果二维码没有打开，在项目文件夹下会有一个svg的文件，打开以后扫码即可，登录的微信号一定要实名认证过的账号

authors: mixosense-zhihaozhou panxingfeng


text:
Typing Hono for createOpenApiDocument

Currently if you pass a hono object that is typed with it's own type variables, not created passing a new Hono(), there are type errors. Given we are no longer passing a Hono object of type BlankEnv.
For example:
  const AppBindings = {
    Variables: {
      //
    }
  }

  const app = new Hono<AppBindings>({ strict: false }).basePath('/api');

  createOpenApiDocument(app, {
    info: {
      title: 'Example API',
      version: '1.0.0',
    },
  });

This results in createOpenApiDocument stating:
Type Hono<AppBindings, BlankSchema, '/'> is not assignable to type Hono<BlankEnv, BlankSchema, '/'>
Any idea how to correctly type this?

I haven't handled this case in the function's signature, I will have to update it. I should have a moment to do it this weekend. You can temporarily just cast the parameter to unknown as Hono or even any and remove it after the update.

@paolostyle, sounds good. Thank you! Look forward to the update.

Working for me now! Thank you @paolostyle!

authors: BradNut paolostyle

repo: paolostyle/hono-zod-openapi


text:
Wrong colors of 4g/LTE, upload/download indicators in light theme

Description:
The 4G/LTE indicators are black when using light theme, this should be white and the upload/download on both wifi and 4G are misplaced and in the wrong color too (black).
Steps to reproduce:

Use light theme
Pull down QS

ROM info:
Lineage OS 15.1 on Oneplus 5
Module version (build version):
Android P-ify version 0.1.0 alpha #26
Screenshot:

Xposedlog:
xposed_error_20180320_095827.log

I have the same problem (OnePlus One Fabulous Oreo 8.1). Also the media Off status is not displayed properly (it shows a black cross next to the icon, but the background stays blue).

authors: Jpkovas RouNNdeL

repo: paphonb/AndroidP-ify


text:
The corners of the quick settings panel is not rounded enough

Hey,
I am running on AEX 5.3 on my Xiaomi Redmi Note 4 and I am on Android P-ify version 0.2.0_40 build.
I noticed that the the corners of the quick settings panel are not rounded enough like Android P, so please take a look on that 😊

It is already rounded in build 41.

Sir, I can't find build #41 any where, I am on #40, will you please send
link ?
On Mon, Apr 2, 2018, 5:03 AM paphonb notifications@github.com wrote:

Closed #28 https://github.com/paphonb/AndroidP-ify/issues/28.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/paphonb/AndroidP-ify/issues/28#event-1551284396, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AkOIshH-0CynIjRBz5lL_R11C83VLjXBks5tkWO3gaJpZM4TC2qK
.

https://github.com/paphonb/AndroidP-ify/releases/download/0.2.0_41/AndroidPify-0.2.0_41.apk

authors: paphonb rishikeshbeura sumeshmeena


text:
hive: reth does not respond to eth/TestMaliciousHandshake properly

Describe the bug
The hive simulator for the eth/TestMaliciousHandshake test does cause reth to fail the handshake, but not in the right way. The simulator outputs the following logs:
skipping suite "discv4" because it doesn't match test pattern eth/TestMaliciousHandshake
1..1
not ok 1 TestMaliciousHandshake
# Testing malicious handshake 0
# dial failed: read tcp 172.17.0.3:35620->172.17.0.4:30303: read: connection reset by peer
exit status 1
skipping suite "snap" because it doesn't match test pattern eth/TestMaliciousHandshake

This is how reth terminates the connection:
2023-02-22T20:32:08.611565Z TRACE Sending disconnect message during the handshake reason=Useless peer
2023-02-22T20:32:08.614217Z TRACE disconnected pending session session_id=SessionId(0) remote_addr=172.17.0.3:35606 error=Some(P2PStreamError(HandshakeError(NoSharedCapabilities)))
2023-02-22T20:32:08.614258Z  WARN Incoming pending session failed remote_addr=172.17.0.3:35606 error=Some(Eth(P2PStreamError(HandshakeError(NoSharedCapabilities))))
2023-02-22T20:32:08.614297Z TRACE The incoming ip address is in the ban list remote_addr=172.17.0.3:35620

This places the IP in the ban list, which causes problems for all succeeding hive tests, because the IP is the same for the rest of the tests.
The other issue is that because of this, the test cannot establish a connection for its other malicious handshakes, since TestMaliciousHandshake actually tests sending multiple malicious handshakes that should not succeed.
Steps to reproduce
Follow instructions in #851 for running hive, and run the devp2p tests.
This was run with reth logs set to:
RUST_LOG=net=trace,reth_eth_wire=trace

Node logs
No response
Platform(s)
No response
What version/commit are you on?
No response
Code of Conduct

[X] I agree to follow the Code of Conduct

The other issue is that because of this, the test cannot establish a connection for its other malicious handshakes, since TestMaliciousHandshake actually tests sending multiple malicious handshakes that should not succeed.

this is in the same test with same PeerId?
can you please link that here.

Update:
This happens because we ban the hive simulator container's IP after it sends the first malicious handshake. These containers have non-routable IPs however, so we do not necessarily need to IP ban them. To fix this, we should create a helper is_global method that determines whether or not the IP is globally routable, similar to the nightly IpAddr::is_global method. We should not ban non-routable peers.
Geth also implements this functionality, which is why it does not throttle hive test peers.

authors: Rjected mattsse

repo: paradigmxyz/reth


text:
Complete optimism mainnet forkid tests

We have a comprehensive set of tests for the mainnet and testnet forkids, including some optimism network tests:
https://github.com/paradigmxyz/reth/blob/3d28a69134daa4f7ea1de004692f2630db152774/crates/primitives/src/chain/spec.rs#L2443-L2472
We should also add these for optimism mainnet, so we have forkid tests for all of the optimism networks covered.

Note: I just added a very basic, non-comprehensive test for this. The test now just needs to be completed with the other forks!

I'd like to work on this

Where can I find the block numbers for the forks? Found timestamps here:
https://specs.optimism.io/protocol/superchain-upgrades.html#activation-timestamps
By knowing the block number I can find the Bedrock upgrade
https://optimistic.etherscan.io/block/105235063

Where can I find the block numbers for the forks? Found timestamps here: https://specs.optimism.io/protocol/superchain-upgrades.html#activation-timestamps
By knowing the block number I can find the Bedrock upgrade https://optimistic.etherscan.io/block/105235063

yes, those should be correct, also take a look at the OP_MAINNET chainspec for the proper block and timestamp values. Just assigned!

I can only see the timestamps and not the blocks in the chainspec
https://github.com/paradigmxyz/reth/blob/3d28a69134daa4f7ea1de004692f2630db152774/crates/primitives/src/chain/spec.rs#L297-L300
Also, do you want forkid tests for all hardforks or just Canyon, Delta and Ecotone?

some hardforks are only conditioned on the timestamp and not the block number which is why some of them do not have a block number:)

I've added the forks as test cases, but I'm stuck on computing ForkHash and next for Canyon and Delta
https://github.com/paradigmxyz/reth/pull/8114
Computed fork ID is not computed correctly for Canyon and Delta:
assertion `left == right` failed: Expected fork ID ForkId { hash: ForkHash("00000000"), next: 1708560000 }, computed fork ID ForkId { hash: ForkHash("caf517ed"), next: 3950000 } at block 0
  left: ForkId { hash: ForkHash("00000000"), next: 1708560000 }
 right: ForkId { hash: ForkHash("caf517ed"), next: 3950000 }

Is the forkhash supposed to be 00000000? That sounds incorrect

left some comments in reviews, let's move there

authors: Rjected estensen onbjerg


text:
feat: ChainSpec associated type

First step for https://github.com/paradigmxyz/reth/issues/10272
Adds ChainSpec trait and assoc type to ChainSpecProvider and NodeTypes, for now most of the logic is hardcoded to use the default ChainSpec

pending @mattsse or @joshieDo

authors: emhane klkvr


text:
ci: update runners for apple builds

macos-14 runner is on M1, which means apple-arm64 will be native, making them faster
macos-13 runner has an extra core, which means apple-x86_64 builds will be slightly faster, also macos-latest uses an older MacOS version (12.0) for builds

We have to also consider that I believe these would increase the minimum macos version requirement. This is the same reason we use ubuntu-20.04 for the linux builds (for glibc version)

cc @rswanson

(woops misclicked the close instead of comment)

@DaniPopes aren't we aren't de-facto using macos-14 in the release workflow as macos-latest should give you a macos-14 build (ref: https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners/about-github-hosted-runners#standard-github-hosted-runners-for-public-repositories)? Just want to make sure I understand the concern here. My initial read is that the x86 change is probably a good one, the arm64 change should probably stay pinned to macos-latest because it is net the same and keeps us in line with the latest runner enhancements

ah it seems to have been updated sometime after opening this PR, I agree yes, we should use macos-13 runner for x64 and macos-latest for Apple Silicon.

authors: DaniPopes QEDK onbjerg rswanson


text:
Elixir/Erlang VM support

The Erlang VM has support for perf maps via the ERL_FLAGS="+S 1 +JPperf true" flags. However, even when setting those flags, profiling an Erlang process does not consistently work (occasionally individual addresses are symbolized).
Working theory: Erlang has a multi-process model, which could be a problem in this case if a process is short-lived (in the sense that a profiling loop of 10 seconds passed while the process was created and ended).
Ultimately even if the perf-map support works, it would be great for erlang users not to have to change anything about their deployment to reap the benefits, but it's a good intermediate step.

It took me some time to get to this but it seems like Erlang support works just fine now. :)
All that's needed is +JPperf map in Erlang flags. Documentation suggests setting it to true, which also works. The difference is that when set to true, Erlang generates the mappings in two formats I mentioned above - setting it to map generates only one format and is sufficient.
I still see some unresolved symbols here and there but, these probably come from some libraries in our Docker image. A vast majority of symbols on this screenshot come from the JIT for sure:

That is amazing!!!

Hi, I'm the OpenTelemetry Erlang/Elixir maintainer and I'm interested in toying with this example and parca in sort of preparation for what the Otel Profiling SIG comes up with.
It isn't clear from the example how to actually use this with parca. I've played with using parca UI, have it installed locally via snap, and I've tried perf with Erlang, but how this demo and the parca agent are meant to work together I'm not seeing :)

Hey @tsloughter, maybe this repo and examples could help better https://github.com/parca-dev/parca-demo/tree/main/erlang
The idea behind the agent is to profile the whole system using eBPF. You need to drop the agent on the host and it will do the rest. If you configure it to send data to a Parca server you can see the collected profiles (you can see all this in the example above). For now, you need to set some flags for BEAM so that the agent can symbolize the collected stack traces.
I hope this helps. Let me know if it's not clear enough.

@kakkoyun oh, you mean run the agent locally on my machine which will collect from the Erlang process running in docker?
I expected a sidecar or something (so a docker-compose instead of a single dockerfile) :)

@tsloughter  Yes, that approach should work. If the process is not in a VM on your local machine the agent can discover it. You might want to use relabelling support to drop all the process' profiles except the erlang one. PTAL
https://www.parca.dev/docs/parca-agent-labelling#configuration
If you're looking for a pre-baked solution, in the example, we run it in the k8s cluster. And you pick which demo you'd like to run.

I believe we can close this issue. In the last versions (agent 0.13 + server 0.15/0.16), I have no problem resolving Erlang JIT symbols. Some issues I still have are related to symbols from binary files, but nothing Erlang specific.

Our ambition is to not even have to enable the +JPperf true flag. It's really awesome that if people put a small amount of work into it that we can support it, but ultimately we want people to have to do absolutely nothing to their deployments. Zero-instrumentation all the way.
That said I agree it's important to recognize this milestone and on a support matrix we could probably already say we support Erlang.

I didn't know that was even possible :D

It'll probably be a while until we take these measures, but essentially it's reading the same data as +JPperf true exposes via the jitdump/perf-map interface directly from the Erlang VM. The information is there, we just need to find it. We'll first do that for languages where we have no other option though, such as Python and Ruby.

That'd be awesome.
Side note, curious if you have had any involved with OpenTelemetry profiling?

At least one person from the Parca project attends every OpenTelemetry Profiling working group call. If you have any more specific questions I think it would be best to continue that conversation on Parca Discord, so we can keep this issue on the topic of zero-instrumentation Erlang support.

authors: brancz kakkoyun mkuratczyk tsloughter

repo: parca-dev/parca-agent


text:
build failed with compiling librocksdb-sys v6.11.4 failed on macOS 10.15.7

Compiling librocksdb-sys v6.11.4
The following warnings were emitted during compilation
Compiling librocksdb-sys v6.11.4
Compiling frame-executive v2.0.0
Compiling pallet-sudo v2.0.0
Compiling pallet-template v2.0.0 (/Users/houfa.zhou/dev/src/github.com/substrate-developer-hub/substrate-node-template/pallets/template)
Compiling pallet-timestamp v2.0.0
Compiling pallet-transaction-payment v2.0.0
Compiling pallet-balances v2.0.0
Compiling sc-client-api v2.0.0
Compiling sc-rpc-api v0.8.0
Compiling sc-transaction-graph v2.0.0
Compiling pallet-session v2.0.0
Compiling sc-block-builder v0.8.0
Compiling sc-state-db v0.8.0
Compiling sc-transaction-pool v2.0.0
Compiling sc-light v2.0.0
Compiling sc-consensus-slots v0.8.0
Compiling sc-consensus v0.8.0
Compiling substrate-frame-rpc-system v2.0.0
Compiling sc-network v0.8.0
Compiling sc-rpc v2.0.0
Compiling sc-basic-authorship v0.8.0
Compiling sc-consensus-aura v0.8.0
The following warnings were emitted during compilation:
。。。。。。。
warning: In file included from
warning: 13 errors generated.
warning: 13 errors generated.
warning: 13 errors generated.
warning: 177 warnings and 13 errors generated.
warning: 13 errors generated.
warning: 13 errors generated.
warning: 13 errors generated.
error: failed to run custom build command for librocksdb-sys v6.11.4
Caused by:
process didn't exit successfully: /Users/houfa.zhou/dev/src/github.com/substrate-developer-hub/substrate-node-template/target/release/build/librocksdb-sys-958b8483ede74939/build-script-build (exit code: 1)
--- stdout
cargo:rerun-if-changed=rocksdb/
TARGET = Some("x86_64-apple-darwin")
OPT_LEVEL = Some("3")
HOST = Some("x86_64-apple-darwin")
CXX_x86_64-apple-darwin = None
CXX_x86_64_apple_darwin = None
HOST_CXX = None
CXX = None
CXXFLAGS_x86_64-apple-darwin = None
CXXFLAGS_x86_64_apple_darwin = None
HOST_CXXFLAGS = None
CXXFLAGS = None
CRATE_CC_NO_DEFAULTS = None
DEBUG = Some("false")
CARGO_CFG_TARGET_FEATURE = Some("cmpxchg16b,fxsr,sse,sse2,sse3,ssse3")
CXX_x86_64-apple-darwin = None
CXX_x86_64_apple_darwin = None
HOST_CXX = None
CXX = None
CXXFLAGS_x86_64-apple-darwin = None
CXXFLAGS_x86_64_apple_darwin = None
HOST_CXXFLAGS = None
CXXFLAGS = None
CRATE_CC_NO_DEFAULTS = None
CARGO_CFG_TARGET_FEATURE = Some("cmpxchg16b,fxsr,sse,sse2,sse3,ssse3")
CXX_x86_64-apple-darwin = None
CXX_x86_64_apple_darwin = None
HOST_CXX = None
CXX = None
CXXFLAGS_x86_64-apple-darwin = None
CXXFLAGS_x86_64_apple_darwin = None
HOST_CXXFLAGS = None
CXXFLAGS = None
CRATE_CC_NO_DEFAULTS = None
CARGO_CFG_TARGET_FEATURE = Some("cmpxchg16b,fxsr,sse,sse2,sse3,ssse3")
CXX_x86_64-apple-darwin = None
CXX_x86_64_apple_darwin = None
HOST_CXX = None
CXX = None
CXXFLAGS_x86_64-apple-darwin = None
CXXFLAGS_x86_64_apple_darwin = None
HOST_CXXFLAGS = None
CXXFLAGS = None
CRATE_CC_NO_DEFAULTS = None
CARGO_CFG_TARGET_FEATURE = Some("cmpxchg16b,fxsr,sse,sse2,sse3,ssse3")
CXX_x86_64-apple-darwin = None
CXX_x86_64_apple_darwin = None
HOST_CXX = None
CXX = None
CXXFLAGS_x86_64-apple-darwin = None
CXXFLAGS_x86_64_apple_darwin = None
HOST_CXXFLAGS = None
CXXFLAGS = None
CRATE_CC_NO_DEFAULTS = None
CARGO_CFG_TARGET_FEATURE = Some("cmpxchg16b,fxsr,sse,sse2,sse3,ssse3")
running: "c++" "-O3" "-ffunction-sections" "-fdata-sections" "-fPIC" "-m64" "-arch" "x86_64" "-I" "rocksdb/include/" "-I" "rocksdb/" "-I" "rocksdb/third-party/gtest-1.8.1/fused-src/" "-I" "snappy/" "-I" "." "-Wall" "-Wextra" "-std=c++11" "-Wno-unused-parameter" "-msse2" "-msse4.1" "-msse4.2" "-mpclmul" "-DSNAPPY=1" "-DNDEBUG=1" "-DHAVE_SSE42=1" "-DHAVE_PCLMUL=1" "-DOS_MACOSX=1" "-DROCKSDB_PLATFORM_POSIX=1" "-DROCKSDB_LIB_IO_POSIX=1" "-o" "/Users/houfa.zhou/dev/src/github.com/substrate-developer-hub/substrate-node-template/target/release/build/librocksdb-sys-9a985f5ad15d9840/out/rocksdb/db/blob/blob_file_addition.o" "-c" "rocksdb/db/blob/blob_file_addition.cc"
running: "c++" "-O3" "-ffunction-sections" "-fdata-sections" "-fPIC" "-m64" "-arch" "x86_64" "-I" "rocksdb/include/" "-I" "rocksdb/" "-I" "rocksdb/third-party/gtest-1.8.1/fused-src/" "-I" "snappy/" "-I" "." "-Wall" "-Wextra" "-std=c++11" "-Wno-unused-parameter" "-msse2" "-msse4.1" "-msse4.2" "-mpclmul" "-DSNAPPY=1" "-DNDEBUG=1" "-DHAVE_SSE42=1" "-DHAVE_PCLMUL=1" "-DOS_MACOSX=1" "-DROCKSDB_PLATFORM_POSIX=1" "-DROCKSDB_LIB_IO_POSIX=1" "-o" "/Users/houfa.zhou/dev/src/github.com/substrate-developer-hub/substrate-node-template/target/release/build/librocksdb-sys-9a985f5ad15d9840/out/rocksdb/db/blob/blob_log_writer.o" "-c" "rocksdb/db/blob/blob_log_writer.cc"
running: "c++" "-O3" "-ffunction-sections" "-fdata-sections" "-fPIC" "-m64" "-arch" "x86_64" "-I" "rocksdb/include/" "-I" "rocksdb/" "-I" "rocksdb/third-party/gtest-1.8.1/fused-src/" "-I" "snappy/" "-I" "." "-Wall" "-Wextra" "-std=c++11" "-Wno-unused-parameter" "-msse2" "-msse4.1" "-msse4.2" "-mpclmul" "-DSNAPPY=1" "-DNDEBUG=1" "-DHAVE_SSE42=1" "-DHAVE_PCLMUL=1" "-DOS_MACOSX=1" "-DROCKSDB_PLATFORM_POSIX=1" "-DROCKSDB_LIB_IO_POSIX=1" "-o" "/Users/houfa.zhou/dev/src/github.com/substrate-developer-hub/substrate-node-template/target/release/build/librocksdb-sys-9a985f5ad15d9840/out/rocksdb/db/blob/blob_log_format.o" "-c" "rocksdb/db/blob/blob_log_format.cc"
running: "c++" "-O3" "-ffunction-sections" "-fdata-sections" "-fPIC" "-m64" "-arch" "x86_64" "-I" "rocksdb/include/" "-I" "rocksdb/" "-I" "rocksdb/third-party/gtest-1.8.1/fused-src/" "-I" "snappy/" "-I" "." "-Wall" "-Wextra" "-std=c++11" "-Wno-unused-parameter" "-msse2" "-msse4.1" "-msse4.2" "-mpclmul" "-DSNAPPY=1" "-DNDEBUG=1" "-DHAVE_SSE42=1" "-DHAVE_PCLMUL=1" "-DOS_MACOSX=1" "-DROCKSDB_PLATFORM_POSIX=1" "-DROCKSDB_LIB_IO_POSIX=1" "-o" "/Users/houfa.zhou/dev/src/github.com/substrate-developer-hub/substrate-node-template/target/release/build/librocksdb-sys-9a985f5ad15d9840/out/rocksdb/db/blob/blob_file_garbage.o" "-c" "rocksdb/db/blob/blob_file_garbage.cc"
running: "c++" "-O3" "-ffunction-sections" "-fdata-sections" "-fPIC" "-m64" "-arch" "x86_64" "-I" "rocksdb/include/" "-I" "rocksdb/" "-I" "rocksdb/third-party/gtest-1.8.1/fused-src/" "-I" "snappy/" "-I" "." "-Wall" "-Wextra" "-std=c++11" "-Wno-unused-parameter" "-msse2" "-msse4.1" "-msse4.2" "-mpclmul" "-DSNAPPY=1" "-DNDEBUG=1" "-DHAVE_SSE42=1" "-DHAVE_PCLMUL=1" "-DOS_MACOSX=1" "-DROCKSDB_PLATFORM_POSIX=1" "-DROCKSDB_LIB_IO_POSIX=1" "-o" "/Users/houfa.zhou/dev/src/github.com/substrate-developer-hub/substrate-node-template/target/release/build/librocksdb-sys-9a985f5ad15d9840/out/rocksdb/db/builder.o" "-c" "rocksdb/db/builder.cc"
running: "c++" "-O3" "-ffunction-sections" "-fdata-sections" "-fPIC" "-m64" "-arch" "x86_64" "-I" "rocksdb/include/" "-I" "rocksdb/" "-I" "rocksdb/third-party/gtest-1.8.1/fused-src/" "-I" "snappy/" "-I" "." "-Wall" "-Wextra" "-std=c++11" "-Wno-unused-parameter" "-msse2" "-msse4.1" "-msse4.2" "-mpclmul" "-DSNAPPY=1" "-DNDEBUG=1" "-DHAVE_SSE42=1" "-DHAVE_PCLMUL=1" "-DOS_MACOSX=1" "-DROCKSDB_PLATFORM_POSIX=1" "-DROCKSDB_LIB_IO_POSIX=1" "-o" "/Users/houfa.zhou/dev/src/github.com/substrate-developer-hub/substrate-node-template/target/release/build/librocksdb-sys-9a985f5ad15d9840/out/rocksdb/cache/cache.o" "-c" "rocksdb/cache/cache.cc"
running: "c++" "-O3" "-ffunction-sections" "-fdata-sections" "-fPIC" "-m64" "-arch" "x86_64" "-I" "rocksdb/include/" "-I" "rocksdb/" "-I" "rocksdb/third-party/gtest-1.8.1/fused-src/" "-I" "snappy/" "-I" "." "-Wall" "-Wextra" "-std=c++11" "-Wno-unused-parameter" "-msse2" "-msse4.1" "-msse4.2" "-mpclmul" "-DSNAPPY=1" "-DNDEBUG=1" "-DHAVE_SSE42=1" "-DHAVE_PCLMUL=1" "-DOS_MACOSX=1" "-DROCKSDB_PLATFORM_POSIX=1" "-DROCKSDB_LIB_IO_POSIX=1" "-o" "/Users/houfa.zhou/dev/src/github.com/substrate-developer-hub/substrate-node-template/target/release/build/librocksdb-sys-9a985f5ad15d9840/out/rocksdb/db/arena_wrapped_db_iter.o" "-c" "rocksdb/db/arena_wrapped_db_iter.cc"
running: "c++" "-O3" "-ffunction-sections" "-fdata-sections" "-fPIC" "-m64" "-arch" "x86_64" "-I" "rocksdb/include/" "-I" "rocksdb/" "-I" "rocksdb/third-party/gtest-1.8.1/fused-src/" "-I" "snappy/" "-I" "." "-Wall" "-Wextra" "-std=c++11" "-Wno-unused-parameter" "-msse2" "-msse4.1" "-msse4.2" "-mpclmul" "-DSNAPPY=1" "-DNDEBUG=1" "-DHAVE_SSE42=1" "-DHAVE_PCLMUL=1" "-DOS_MACOSX=1" "-DROCKSDB_PLATFORM_POSIX=1" "-DROCKSDB_LIB_IO_POSIX=1" "-o" "/Users/houfa.zhou/dev/src/github.com/substrate-developer-hub/substrate-node-template/target/release/build/librocksdb-sys-9a985f5ad15d9840/out/rocksdb/db/blob/blob_log_reader.o" "-c" "rocksdb/db/blob/blob_log_reader.cc"
running: "c++" "-O3" "-ffunction-sections" "-fdata-sections" "-fPIC" "-m64" "-arch" "x86_64" "-I" "rocksdb/include/" "-I" "rocksdb/" "-I" "rocksdb/third-party/gtest-1.8.1/fused-src/" "-I" "snappy/" "-I" "." "-Wall" "-Wextra" "-std=c++11" "-Wno-unused-parameter" "-msse2" "-msse4.1" "-msse4.2" "-mpclmul" "-DSNAPPY=1" "-DNDEBUG=1" "-DHAVE_SSE42=1" "-DHAVE_PCLMUL=1" "-DOS_MACOSX=1" "-DROCKSDB_PLATFORM_POSIX=1" "-DROCKSDB_LIB_IO_POSIX=1" "-o" "/Users/houfa.zhou/dev/src/github.com/substrate-developer-hub/substrate-node-template/target/release/build/librocksdb-sys-9a985f5ad15d9840/out/rocksdb/cache/lru_cache.o" "-c" "rocksdb/cache/lru_cache.cc"
running: "c++" "-O3" "-ffunction-sections" "-fdata-sections" "-fPIC" "-m64" "-arch" "x86_64" "-I" "rocksdb/include/" "-I" "rocksdb/" "-I" "rocksdb/third-party/gtest-1.8.1/fused-src/" "-I" "snappy/" "-I" "." "-Wall" "-Wextra" "-std=c++11" "-Wno-unused-parameter" "-msse2" "-msse4.1" "-msse4.2" "-mpclmul" "-DSNAPPY=1" "-DNDEBUG=1" "-DHAVE_SSE42=1" "-DHAVE_PCLMUL=1" "-DOS_MACOSX=1" "-DROCKSDB_PLATFORM_POSIX=1" "-DROCKSDB_LIB_IO_POSIX=1" "-o" "/Users/houfa.zhou/dev/src/github.com/substrate-developer-hub/substrate-node-template/target/release/build/librocksdb-sys-9a985f5ad15d9840/out/rocksdb/db/blob/blob_file_meta.o" "-c" "rocksdb/db/blob/blob_file_meta.cc"
running: "c++" "-O3" "-ffunction-sections" "-fdata-sections" "-fPIC" "-m64" "-arch" "x86_64" "-I" "rocksdb/include/" "-I" "rocksdb/" "-I" "rocksdb/third-party/gtest-1.8.1/fused-src/" "-I" "snappy/" "-I" "." "-Wall" "-Wextra" "-std=c++11" "-Wno-unused-parameter" "-msse2" "-msse4.1" "-msse4.2" "-mpclmul" "-DSNAPPY=1" "-DNDEBUG=1" "-DHAVE_SSE42=1" "-DHAVE_PCLMUL=1" "-DOS_MACOSX=1" "-DROCKSDB_PLATFORM_POSIX=1" "-DROCKSDB_LIB_IO_POSIX=1" "-o" "/Users/houfa.zhou/dev/src/github.com/substrate-developer-hub/substrate-node-template/target/release/build/librocksdb-sys-9a985f5ad15d9840/out/rocksdb/cache/sharded_cache.o" "-c" "rocksdb/cache/sharded_cache.cc"
running: "c++" "-O3" "-ffunction-sections" "-fdata-sections" "-fPIC" "-m64" "-arch" "x86_64" "-I" "rocksdb/include/" "-I" "rocksdb/" "-I" "rocksdb/third-party/gtest-1.8.1/fused-src/" "-I" "snappy/" "-I" "." "-Wall" "-Wextra" "-std=c++11" "-Wno-unused-parameter" "-msse2" "-msse4.1" "-msse4.2" "-mpclmul" "-DSNAPPY=1" "-DNDEBUG=1" "-DHAVE_SSE42=1" "-DHAVE_PCLMUL=1" "-DOS_MACOSX=1" "-DROCKSDB_PLATFORM_POSIX=1" "-DROCKSDB_LIB_IO_POSIX=1" "-o" "/Users/houfa.zhou/dev/src/github.com/substrate-developer-hub/substrate-node-template/target/release/build/librocksdb-sys-9a985f5ad15d9840/out/rocksdb/cache/clock_cache.o" "-c" "rocksdb/cache/clock_cache.cc"
。。。。。。
cargo:warning=using ::isunordered;
cargo:warning=      ~~^
cargo:warning=13 errors generated.
exit code: 1
cargo:warning=13 errors generated.
exit code: 1
cargo:warning=13 errors generated.
exit code: 1
cargo:warning=177 warnings and 13 errors generated.
exit code: 1
cargo:warning=13 errors generated.
exit code: 1
cargo:warning=13 errors generated.
exit code: 1
cargo:warning=13 errors generated.
exit code: 1
--- stderr
error occurred: Command "c++" "-O3" "-ffunction-sections" "-fdata-sections" "-fPIC" "-m64" "-arch" "x86_64" "-I" "rocksdb/include/" "-I" "rocksdb/" "-I" "rocksdb/third-party/gtest-1.8.1/fused-src/" "-I" "snappy/" "-I" "." "-Wall" "-Wextra" "-std=c++11" "-Wno-unused-parameter" "-msse2" "-msse4.1" "-msse4.2" "-mpclmul" "-DSNAPPY=1" "-DNDEBUG=1" "-DHAVE_SSE42=1" "-DHAVE_PCLMUL=1" "-DOS_MACOSX=1" "-DROCKSDB_PLATFORM_POSIX=1" "-DROCKSDB_LIB_IO_POSIX=1" "-o" "/Users/houfa.zhou/dev/src/github.com/substrate-developer-hub/substrate-node-template/target/release/build/librocksdb-sys-9a985f5ad15d9840/out/rocksdb/cache/cache.o" "-c" "rocksdb/cache/cache.cc" with args "c++" did not execute successfully (status code exit code: 1).
warning: build failed, waiting for other jobs to finish...
error: build failed
detail log:
err.log

This is a rocksdb compilation error, not related to Substrate. It is only an external dependency. The best would be that you check that all dependencies are installed and if yes, go to the rust rocksdb github.

authors: bkchr yiyanwannian

repo: paritytech/substrate


text:
Exclude big changes from file annotations

You can now easily exclude big automated code changes by running
git config blame.ignoreRevsFile .git-blame-ignore-revs
in your local repository. It will work also in IDE integrations.
You should add new commit hashes to this file when you create or find such big automated refactorings while reading code history. If you only know the short hash, use git rev-parse eeccbf39 to expand it to the full hash needed in this file.
On versions of Git 2.20 and later comments (#), empty lines, and any leading and trailing whitespace is ignored. Everything but a SHA-1 per line will error out on older versions.

bot merge

authors: bkchr wigy-opensource-developer


text:
Updated docs for method set_payee & set_controller

Description
This PR is related to this issue. It updates the docs for the method set_payee so that they reflect correctly when the changes from this function start to apply.
Further Notes
The same comment can also be found in the following methods :
validate
nominate
chill
set_controller
kick
chill_other
I was wondering if we need to update these comments too since I do not see an era check in these functions either but maybe I am wrong.
Thank you so much for your feedback.

Out of the other functions, set_controller also appears to take effect immediately. The others relate to the election though, which only takes place one per era, so those docs are correct.

bot merge


text:
Fix BoundedSlice bound

Changes:

Use <= instead of < for the bound check in the constructor.
Add test

Thanks @koute for finding it!

FYI, I've already put up a PR for this here: https://github.com/paritytech/substrate/pull/11600
Sorry, I should have added you as a reviewer... (:

authors: ggwpez koute


text:
Add PoV Tracking to Benchmarking Pipeline

This PR introduces the PoV Tracking / Proof Recorder into the Runtime Benchmarking Pipeline.
In summary, when a parachain presents a new block for the relay chain to validate, it must also provide a minimal PoV block which contains all the necessary storage items which can be used to prove the validity of the state transition.
This means if you are trying to transfer a balance between two accounts on a parachain, you need to provide some subsection of the full state trie to the relay chain which contains those two account balances.
Due to the base-16 Patricia-Merkle trie used in Substrate, this can end up being a lot of extra data. We need to not only confirm that a block of extrinsics would execute in time, but also that the PoV block needed for all those extrinsics would fit within the limits of the relay chain.
When benchmarking for PoV block size, you need to ensure to follow the path of any extrinsic logic which touches the most storage items, especially those that are large, as this is likely to create the largest PoV block. Furthermore, you must populate the storage to have all of those storage items as full as they can be. Always benchmark the worst case scenario.
Initial tests from this PR show:
Pallet: "pallet_balances", Extrinsic: "transfer",
extrinsic_time,storage_root_time,reads,repeat_reads,writes,repeat_writes,proof_size
65000,13000,1,18,1,4,1806

Pallet: "pallet_balances", Extrinsic: "transfer_keep_alive",
extrinsic_time,storage_root_time,reads,repeat_reads,writes,repeat_writes,proof_size
48000,4000,1,12,1,3,1571

So a balance transfer on an empty chain is around 1.6 - 1.8 kB.
Another benchmark which populates more data into the state:
Pallet: "pallet_collective", Extrinsic: "close_approved",
b,m,p,extrinsic_time,storage_root_time,reads,repeat_reads,writes,repeat_writes,proof_size
1,100,100,126000,3000,5,10,3,2,12554
103,100,100,148000,4000,5,10,3,2,12801
205,100,100,144000,4000,5,10,3,2,12761
307,100,100,113000,2000,5,10,3,2,12863
409,100,100,121000,3000,5,10,3,2,12965
511,100,100,121000,3000,5,10,3,2,12935
613,100,100,119000,3000,5,10,3,2,13103
715,100,100,124000,3000,5,10,3,2,13073
817,100,100,125000,4000,5,10,3,2,13713
919,100,100,125000,3000,5,10,3,2,13551
1021,100,100,126000,3000,5,10,3,2,13709
1024,4,100,83000,3000,5,10,3,2,7368
1024,13,100,88000,3000,5,10,3,2,7944
1024,22,100,214000,3000,5,10,3,2,8520
1024,31,100,106000,17000,5,10,3,2,9096
1024,40,100,96000,3000,5,10,3,2,9672
1024,49,100,99000,3000,5,10,3,2,10248
1024,58,100,100000,3000,5,10,3,2,10824
1024,67,100,106000,3000,5,10,3,2,11402
1024,76,100,111000,3000,5,10,3,2,11978
1024,85,100,113000,3000,5,10,3,2,12554
1024,94,100,115000,3000,5,10,3,2,13130
1024,100,1,88000,3000,5,10,3,2,8941
1024,100,10,108000,3000,5,10,3,2,9835
1024,100,19,97000,3000,5,10,3,2,10453
1024,100,28,110000,3000,5,10,3,2,10945
1024,100,37,104000,3000,5,10,3,2,11299
1024,100,46,113000,4000,5,10,3,2,11653
1024,100,55,115000,3000,5,10,3,2,12281
1024,100,64,117000,3000,5,10,3,2,12296
1024,100,73,153000,3000,5,10,3,2,12782
1024,100,82,115000,3000,5,10,3,2,12872
1024,100,91,119000,3000,5,10,3,2,13226
1024,100,100,122000,3000,5,10,3,2,13514

Here we see the PoV size of a closed_approve where we change the number of:

b: bytes in the proposal
m: members in the collective
p: number of proposals in the system

Here we can see the proof size increases as the values of these things increases. Up to nearly 14 kB.
More analysis will be done to verify all of this benchmarking process is sane, and we will introduce processes in future PRs that will fill up the state for worst case PoV benchmarking.

bot merge

So we can benchmark PoV impact but we don't have any way to track and limit it within FRAME akin to weight, right?

authors: athei shawntabrizi


text:
[Trappist on Rococo] Add pallet for maintenance mode

Add a pallet to Trappist's runtime to allow for a maintenance (aka emergency) mode.
Moonbeam and Acala, among others, have a similar feature.

I have analyzed both pallets and my vote goes for Moonbeam since seems to be more generic and better structured.
It also contains XCMP handles.

Maintenance mode pallet spec
The pallet logic itself will be very basic and it will just expose two extrinsics that will handle the on/off property for the maintenance mode. But the specific part goes in the impls exposed from the pallet. The traits implementations frame_support::traits::Contains and cumulus_primitives_core::DmpMessageHandler will help to a list of defined runtime calls and XCM messages respectively:
Runtime Call Filtering (Contains<RuntimeCall>)
The Contains<RuntimeCall> trait implementation twill be set to be used by the the BaseCallFilter feature of the frame_system pallet. The logic is not hard to follow:
	impl<T: Config> Contains<T::RuntimeCall> for Pallet<T> {
		fn contains(call: &T::RuntimeCall) -> bool {
			if MaintenanceMode::<T>::get() {
				T::FilteredCalls::contains(call)
			}  else {
                             return false;
                         }
		}
	}

From the runtime the FilteredCalls type will be provided to the pallet so we can filter which calls we want:
pub struct RuntimeFilteredCalls;
impl Contains<RuntimeCall> for RuntimeFilteredCalls {
	fn contains(call: &RuntimeCall) -> bool {
		match call {
			RuntimeCall::Assets(method) => match method {
				pallet_assets::Call::transfer { .. } => true,
				pallet_assets::Call::transfer_keep_alive { .. } => true,
                                  ...
				_ => false,
			},
	                ....
		}
	}
}

XCM messages (cumulus_primitives_core::DmpMessageHandler)
From the XCM messages perspective, the DMP Queue messages will be filtered by relying on the cumulus_primitives_core::DmpMessageHandler::handle_dmp_messages(iter, limit). By providing Weight::zero() to the second argument, basically the  messages are queued for next iteration.
From the runtime perspective, the struct MaintenanceDmpHandler will be a wrapper of the DmpQueue::handle_dmp_messages and it will be provided as a type to the pallet:
pub struct MaintenanceDmpHandler;
impl DmpMessageHandler for MaintenanceDmpHandler {
	fn handle_dmp_messages(
		iter: impl Iterator<Item = (RelayBlockNumber, Vec<u8>)>,
		limit: Weight,
	) -> Weight {
		DmpQueue::handle_dmp_messages(iter,limit)
	}
}

Then from the pallet side, the DmpMessageHandler will use the MaintenanceDmpHandler in the following way:
	impl<T: Config> DmpMessageHandler for Pallet<T> {
		fn handle_dmp_messages(
			iter: impl Iterator<Item = (RelayBlockNumber, Vec<u8>)>,
			limit: Weight,
		) -> Weight {
			if MaintenanceMode::<T>::get() {
				T::MaintenanceDmpHandler::handle_dmp_messages(iter, Weight::zero())
			} else {
				T::MaintenanceDmpHandler::handle_dmp_messages(iter, limit)
			}
		}
	}

Pallet adjustments over the runtime

construct_runtime! {
	pub enum Runtime where
		Block = Block,
		NodeBlock = opaque::Block,
		UncheckedExtrinsic = UncheckedExtrinsic
	{
                	MaintenanceMode: pallet_maintenance_mode::{Pallet, Call, Config, Storage, Event} = 50,
         }
}

impl frame_system::Config for Runtime {
        ...
	type BaseCallFilter = MaintenanceMode;
        ...
}

impl cumulus_pallet_parachain_system::Config for Runtime {
	...
	type DmpMessageHandler = MaintenanceMode;
        ...
}

Transaction pool
Finally we should filter as well the calls in the transaction pool so they are not included during the maintenance:
	impl sp_transaction_pool::runtime_api::TaggedTransactionQueue<Block> for Runtime {
		fn validate_transaction(
			source: TransactionSource,
			tx: <Block as BlockT>::Extrinsic,
			block_hash: <Block as BlockT>::Hash,
		) -> TransactionValidity {
			if !<Runtime as frame_system::Config>::BaseCallFilter::contains(&xt.0.function) {
				return InvalidTransaction::Call.into();
			}
			Executive::validate_transaction(source, tx, block_hash)

		}
	}

CC: @stiiifff

@hbulgarini Looks good, thanks for spec-ing this out before.

	impl<T: Config> Contains<T::RuntimeCall> for Pallet<T> {
		fn contains(call: &T::RuntimeCall) -> bool {
			if MaintenanceMode::<T>::get() {
				T::FilteredCalls::contains(call)
			}  else {
                             return false; // <-- should be true here if you are whitelisting
                         }
		}
	}

Would it be useful to be able to select which pallets/calls are whitelisted when the Lockdown mode is active? This feature would enable us to gradually enable pallets during testing and isolate any problematic pallets for individual testing purposes.
By selectively choosing which pallets are allowed in the whitelist, we can thoroughly test the node as we progressively enable more pallets.
I was just thinking about it, but I'm not fully sure how much extra value it would provide to the pallet.

authors: hbulgarini kalaninja stiiifff valentinfernandez1

repo: paritytech/trappist


text:
Upload the legend from source wms server for external wms layer

Refine the logic to get the target crs for ows resource

This change is

Comments from Reviewable

Coverage decreased (-0.06%) to 51.923% when pulling b3dc470362a096238480466b104eedd2f45a12ee on rockychen-dpaw:master into 3dfa3c306fca93697b42cf1c9b560cedaaf390cd on parksandwildlife:master.

Reviewed 2 of 4 files at r1.
Review status: 2 of 4 files reviewed at latest revision, all discussions resolved, some commit checks failed.

Comments from Reviewable

Reviewed 2 of 4 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved, some commit checks failed.

Comments from Reviewable

authors: coveralls rockychen-dpaw ropable

repo: parksandwildlife/oim-cms


text:
Online Decoding

I wrote simple python bindings for online decoding

Hello @SeanNaren , can you please review and approve pr, Thanks!

hey @stas6626 thanks for making this! I should have time in the rest of the week to have a look, apologies on the delay :)

@SeanNaren No problem!
I get bug report from @stevenhillis about seq_len growing, thank you for this!
Also, what to say thanks to @nikolsky for help with tricky shape bug!

Thanks so much @stas6626, @nikolsky for your work on this, this is a fantastic feature!

repo: parlance/ctcdecode


text:
Replaced wysiwyg bodyeditor

Takes care of jumping issues when typing inside the wysiwyg editor, reported during user testing.
Covers #632

@dethe done!

repo: participedia/frontend


text:
Dockerize  go-swagger3

Make sure  DOCKER_USERNAME and DOCKER_PASSWORD are added in github secrets.
A workflow will run whenever a new tag is created and push these images:

parvez3019/go-swagger3:latest
parvez3019/go-swagger3:specific version

@parvez3019 ready

I have added the secrets, will merge once reviewed by @qequ as well.


text:
Can you specify a timeout for a connection?

If the connection cannot be established after a period of specified time, I need the connection to timeout.
Where and what is the property that I need to set, and is that in milliseconds?

Please, see this section in the docs: https://github.com/patriksimek/node-mssql#cfg-basic

authors: patriksimek quackerjeff

repo: patriksimek/node-mssql


text:
Add create_attribute()

create_attribute() is a new twig function in Drupal core 8.3.x https://www.drupal.org/node/2818293
The Attribute class contains a lot of logic, i am not sure if we should copy it, trim it down or maybe add drupal/core as a composer dependency and use it directly?

Hmm aleksip/plugin-data-transform has the necessary classes already.

Ideally these issues will land some day:

Move Attribute classes under Drupal\Component
[Meta] Expose Drupal Components outside of Drupal

Meanwhile Data Transform Plugin has the required classes and is already a dependency of Pattern Lab Twig Standard Edition for Drupal, so maybe it could be added as a dependency here too.

are there any news on this one?

Looks like #8 fixes this

just added a create_attribute function in #10

authors: aleksip romanovma waako webflo


text:
IE11: pfe-health-index colors

Description of the issue
IE11 bug in rendering the colors for the health-index.
Impacted component(s)

pfe-health-index

Branch: fix-issue-992-pfe-health-index-colors

repo: patternfly/patternfly-elements


text:
Adds initial documentation.

Makes progress on #21 and GH documentation.

FYI - I don't currently have edit access to Sketch, which is required to add the pink annotation tags to the images. I'm working on getting that granted

repo: patternfly/react-user-feedback


text:
Encoding fails when stdout is piped or redirected to file on Windows

Issue
tl;dr infamous character encoding error happens with --encoding --no-pretty when redirecting stdout on Windows pwsh.
To save costs, I'm capturing the contents of the repo-map in various situations to understand how it's generated, how to optimize it, etc.  To do that, I'm using a fairly common pattern: running a shell command and piping the output somewhere.
# Pwsh (PowerShell Core) 7.4.5
aider --show-repo-map --encoding utf-8 --no-pretty > repomap.txt
# Also happens when redirecting to `echo` which is a more convenient reproduction
aider --show-repo-map --encoding utf-8 --no-pretty | echo

Unfortunately, when stdout is redirected, print() fails to encode one of the braille characters used for aider's spinner.  My prompt also never appears until I hit Ctrl+C; I suspect this because python doesn't close the redirected file descriptor.  Notably:

I've passed --encoding utf-8
I've passed --no-pretty which ideally would disable the spinner
I'm piping to a file, so ideally aider would disable terminal-specific drawing commands such as spinners
--show-repo-map tells us we are not in an interactive mode, because it always outputs and exits
encoding issue aside, terminal prompt does not return till Ctrl+C

A simpler reproduction is:
# This one has the same encoding error but *does* return terminal prompt without Ctrl+C
python -c 'print("\u280b")' | echo

Full log:
PS C:\...> aider --show-repo-map --encoding utf-8 --no-pretty | echo

Aider v0.58.2.dev7+g9789668c
Main model: claude-3-5-sonnet-20240620 with diff edit format, infinite output
Weak model: claude-3-haiku-20240307
Git repo: .git with 7,638 files
Warning: For large repos, consider using --subtree-only and .aiderignore
See: https://aider.chat/docs/faq.html#can-i-use-aider-in-a-large-mono-repo
Repo-map: using 1024 tokens, auto refresh

# Uncaught UnicodeEncodeError in cp1252.py line 19

Aider version: 0.58.2.dev7+g9789668c
Python version: 3.12.6
Platform: Windows-11-10.0.22631-SP0
Python implementation: CPython
Virtual environment: Yes
OS: Windows 11 (64bit)
Git version: git version 2.40.1.windows.1

An uncaught exception occurred:

`` `
Traceback (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "__main__.py", line 8, in <module>
    sys.exit(main())
             ^^^^^^
  File "main.py", line 672, in main
    repo_map = coder.get_repo_map()
               ^^^^^^^^^^^^^^^^^^^^
  File "base_coder.py", line 599, in get_repo_map
    repo_content = self.repo_map.get_repo_map(
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "repomap.py", line 127, in get_repo_map
    files_listing = self.get_ranked_tags_map(
                    ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "repomap.py", line 482, in get_ranked_tags_map
    result = self.get_ranked_tags_map_uncached(
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "repomap.py", line 513, in get_ranked_tags_map_uncached
    ranked_tags = self.get_ranked_tags(
                  ^^^^^^^^^^^^^^^^^^^^^
  File "repomap.py", line 316, in get_ranked_tags
    progress()
  File "utils.py", line 283, in step
    self._step()
  File "utils.py", line 292, in _step
    print(f"\r{self.text} {next(self.spinner_chars)}\r{self.text} ", end="", flush=True)
  File "cp1252.py", line 19, in encode
    return codecs.charmap_encode(input,self.errors,encoding_table)[0]
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
UnicodeEncodeError: 'charmap' codec can't encode character '\u280b' in position 19: character maps to <undefined>

Version and model info
No response

I'm using env var PYTHONIOENCODING=utf-8 as a workaround.
It still prints the spinner, which comes out looking corrupted.  Ideally that'd be disabled for non-terminal output.  But it's not a big deal.

Thanks for trying aider and filing this issue.
The fix is available in the main branch. You can get it by installing the latest version from github:
aider --install-main-branch

# or...

python -m pip install --upgrade --upgrade-strategy only-if-needed git+https://github.com/Aider-AI/aider.git

If you have a chance to try it, let me know if it works better for you. I'm going to close this issue for now, but feel free to add a comment here and I will re-open. Or feel free to file a new issue any time.

authors: cspotcode paul-gauthier

repo: paul-gauthier/aider