Support running on Python 3

This patch series covers:

initial single-source 2/3 support via python-modernize
subsequent updates to get tests to same state on both 2 & 3

Note: when running redhawk with this patch series on Python 3, it will only work on common subset of Python 2 and Python 3. IOW, it won't work on e.g.
try:
    pass
except Exception, e: # py2 only syntax
    pass

or
async def foo(): # py3 only syntax
    pass

If run on Python 2, it will still analyze Python 2 code correctly. Analyzing Python 3 constructs when running on Python 3 will require some additional work (adding Converters and Nodes for these constructs).

I have three comments:

Adding a ConvertList method will clean up lots of code in the converters due to the list(map(..)) pattern
Dependency on six module can be removed by changing filter in one place
The Try node was added for Issue #2. All the other changes here are for Issue #1. If you are planning on working that in the near future, it would be good to separate that out into another PR?

We will also need a way to separate out if-else pattern when Python 3 support starts. I will think about a way of doing so in the near future.
Change is looking good. Please address the above and I'll accept the Pull request. Thanks for doing this!

So I think I addressed all of your points, but I started testing on Python 3.5 and there seem to be some new test failures, so I'm going to investigate them. Please don't merge yet.

Ok, fixed Python 3.5 compatibility and pushed. Ready to be re-reviewed and merged.

Changes look good - I've merged this to master. Thanks everybody for pitching in and helping fix this issue. Appreciate this! :-)
@bkabrda: Good spot with ConverListOfStatements!

Thanks a lot for the review and for accepting, @spranesh!

Thanks @bkabrda @spranesh @ncoghlan  !

Thanks @bkabrda @ncoghlan @jpopelka for your contributions! I've just released a version containing these changes (and some bug fixes). This version will enable redhawk to run via Python3.
However, it may still barf when analyzing some Python3 codebases. This is important, but will take significant development time to fix (Issue #2 and Issue #3).


Is this library is onelogin specific only?

Is this library is onelogin specific only or I can use it for in-common federation as well?

Can be used for any Identity Provide that supports SAML

Thanks for reply. This sentence in readme file makes sense as it would stop
raising such tickets.
On Tue 9 Oct, 2018, 11:12 PM Sixto Martin<EMAIL_ADDRESS>wrote:

Closed #474 https://github.com/onelogin/ruby-saml/issues/474.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/onelogin/ruby-saml/issues/474#event-1893504435, or mute
the thread
https://github.com/notifications/unsubscribe-auth/Am4IPcIVA7cYKhjbZ9JP6a6mZeT3dH2Mks5ujN_qgaJpZM4XTwdV
.


feat: Add SEO Optimization (extended #204)

Add SEO Optimization

Fix Suggested Changes against SEO Optimization

Describe the changes you've made
:link: #204
:link: #209
Type of change
What sort of change have you made:

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Code style update (formatting, local variables)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update.
[ ] This change requires a documentation update

How Has This Been Tested?
Ran builds on gitpod and successful builds ✅
Checklist

[x] My code follows the guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented on my code, particularly wherever it was hard to understand.
[x] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings.
[x] I have added tests that prove my fix is effective or that my feature works.
[x] Any dependent changes have been merged and published in downstream modules.

Code of Conduct

[x] I agree to follow this project's Code of Conduct

Are you still going to work on this or?

Totally forgot about this lying PR, thanks for the reminder @Panquesito7, gonna, create a new one, because the amount of conflicts are no so promising 😂


Deploy SPAccessServiceApp won't connect to database

Details of the scenario you try and problem that is occurring:
Attempting to deploy SPAccessServiceApp but receive this error:
A connection could be established to the Application Database Server but mixed mode authentication isn't enabled.
+ CategoryInfo          : ObjectNotFound: (Access Services Service Application:) [], CimException
+ FullyQualifiedErrorId : Microsoft.Office.Access.Services.PowerShell.NewSPAccessServicesApplication
+ PSComputerName        : SP-APP1
The DSC configuration that is using the resource:
SPAccessServiceApp AccessServices
{
Name                 = "Access Services Service Application"
ApplicationPool      = $serviceAppPoolName
DatabaseServer       = $SqlServerName
PsDscRunAsCredential = $FarmSetupCredential
DependsOn            = "[SPFarm]CreateSPFarm"
Ensure               = "Present"
}
Version of the Operating System and PowerShell the DSC Target Node is running:
Windows Server 2012 R2, PowerShell  5.1
Version of the DSC module you're using:
1.7

Hi @Chiliyago, as the error suggests: You have to enable Mixed Mode authentication on your SQL instance before you can use the Access Service Application. See the properties of your instance in the SQL Management Studio:
https://www.top-password.com/images/server-authentication-mode.png
Can you change that setting, try again and let us know the results?

Yes that did the trick. Does Access Services require Mixed Mode or is that a function of the resource for some reason?

@Chiliyago This is a requirement of Access Services as it uses SQL authentication for each individual database. Have a look at this link for more info:
https://social.technet.microsoft.com/wiki/contents/articles/12514.sharepoint-2013-access-services.aspx#Required_SQL_Server_settings_for_Access_apps


alibabacloud: use NextToken and MaxResults to list tag resources

The cilium operator log looks as follows, the actual vswitches are sufficient.
msg="Unable to maintain ip pool of node" error="no matching vSwitch
available for interface creation (VPC=<VPC> AZ=<AZ> SubnetTags=<TAGS>"
instanceID=<ID> name=<NAME> subsys=ipam

When listing tag resources according to vswitches, the response body may not return all tags, and vswitches without tags cannot be assigned ip. This patch uses NextToken to continue querying tag resources, and sets pagesize through MaxResults.
Alibabacloud API Reference Documentation
[1] https://www.alibabacloud.com/help/en/virtual-private-cloud/latest/listtagresources
Signed-off-by: Hao Zhang<EMAIL_ADDRESS>Fix bug in AlibabaCloud where vSwitches could not be matched

/test

/test

/test

@christarazi You marked this as a bugfix, does it require any backports? If so, can you please tag accordingly?


add minStringLength parameter

this fixes #192

Coverage decreased (-0.4%) to 92.36% when pulling 9f85ebeaa0ebf45bf516b3b2798a4fc7efeac04e on issue-192 into a47c6a3354a1dfcf0f24d37dce2652c24e1ec575 on master.


panicked: capacity overflow

Component
Heimdall (Core)
Have you ensured that you are up to date?

[X] Bifrost
[X] Heimdall

What version of Heimdall are you on?
0.8.2
Operating System
Linux
Describe the bug
mainnet contract: 0xB982741Fa2f6727e6c355E78574212C0d59e6768
code: https://github.com/cdump/evmole/blob/newhm/benchmark/providers/heimdall-rs/src/main.rs#L43
thread '<unnamed>' panicked at library/alloc/src/raw_vec.rs:571:5:
capacity overflow

ty for opening, i will resolve this with #410


/addDef with @ns="http://www.tei-c.org/ns/1.0"

Two attribute definition (xml:lang and curvedir) in MEI basic have a @ns="http://www.tei-c.org/ns/1.0", but no other one.
https://github.com/music-encoding/music-encoding/blob/1a62535e05a74ed781ace12d8f9d7760e4203c36/customizations/mei-basic.xml#L605
https://github.com/music-encoding/music-encoding/blob/1a62535e05a74ed781ace12d8f9d7760e4203c36/customizations/mei-basic.xml#L378
Could somebody explain what their purpose is? Thanks

Seems to be something coming from Oxygen (or another XML editor). It's just a redefinition of the root ns and should be deleted.


Unable to use this Plugin

Launching lib\main.dart on SM J500F in debug mode...
D:\CURRENT\qw\android\app\src\main\AndroidManifest.xml:6:9-27 Error:
Attribute application@label value=(qw) from AndroidManifest.xml:6:9-27
is also present at [com.github.HaarigerHarald:android-youtubeExtractor:master-SNAPSHOT] AndroidManifest.xml:15:9-41 value=(@string/app_name).
Suggestion: add 'tools:replace="android:label"' to  element at AndroidManifest.xml:4:5-23:19 to override.
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:processDebugManifest'.

Manifest merger failed : Attribute application@label value=(testingapproject) from AndroidManifest.xml:6:9-27
is also present at [com.github.HaarigerHarald:android-youtubeExtractor:master-SNAPSHOT] AndroidManifest.xml:15:9-41 value=(@string/app_name).
Suggestion: add 'tools:replace="android:label"' to  element at AndroidManifest.xml:4:5-23:19 to override.

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 3s
Gradle task assembleDebug failed with exit code 1
Exited (sigterm)

@rajeshjeshar Add tools:replace="android:label" to your Manifest file as shown in the screenshot.


.NET 7 Native AOT error: Generic virtual method pointer lookup failure

First, thanks for updating MemoryPack to work with .NET 7 and AOT.
Unfortunately my native AOT test program (latest .NET 7) is crashing with the error below:

(it works OK in debug and release mode in Visual Studio, but crashes only after publishing and running the AOT executable)
Here is the full test code:
using MemoryPack;

namespace Tests
{
    [MemoryPackable]
    public partial class MemPackObject
    {
        public string TestString { get; set; }
    }

    class MemPackTest
    {
        static void Main(string[] args)
        {
            MemPackObject test_object = new MemPackObject();
            test_object.TestString = "ABC";
            Console.WriteLine("Initial value before serializing: " + test_object.TestString);

            byte[] serialized_object = MemoryPackSerializer.Serialize(test_object);
            MemPackObject? deserialized_object = MemoryPackSerializer.Deserialize<MemPackObject>(serialized_object);

            if (deserialized_object != null)
            {
                Console.WriteLine("Final value after deserializing: " + deserialized_object.TestString);
            }

            Console.WriteLine("Test completed. Press any key to exit");
            Console.ReadKey();
        }

    }
}

Thanks.
I suspect it is a bug in the Native AOT compiler, as I reproduced it even with minimized code.
Reported at https://github.com/dotnet/runtime/issues/78882

I received a response.
It seems to be a bug and will not be resolved until .NET 8.

The workaround is to tell the compiler manually that the target needs to be generated. It is not pretty. Pull request https://github.com/dotnet/runtime/pull/78904 adds support for at least telling what needs to be pregenerated and I'm hoping we can service that part in January for 7.0.

It's likely the root cause of the problem will only be fixed in 8.0. Sorry, it's a very risky fix.

I have noted this in the ReadMe.

This has been fixed in https://github.com/dotnet/runtime/pull/80601
It's possible to use the daily build of Microsoft.DotNet.ILCompiler in .NET 7.0.
Note that this is a daily build so it's possible there are other bugs.

Create nuget.config in your solution (where the .sln-file is located) with the following content:<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <packageSources>
    <add key="dotnet8" value="https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet8/nuget/v3/index.json" />
  </packageSources>
</configuration>

Add the following to your .csproj (change win-x64 if you're not using Windows):<PackageReference Include="Microsoft.DotNet.ILCompiler; runtime.win-x64.Microsoft.DotNet.ILCompiler" Version="8.0.0-alpha.1.23067.11" />

After that you can build the project with AOT (e.g. dotnet publish -r win-x64 -c Release -p PublishAot=True). If you run the application it should give the expected result:
Initial value before serializing: ABC
Final value after deserializing: ABC
Test completed. Press any key to exit


Cypress on WSL

Describe the bug
Testing with Cypress errors on Windows for users of the Windows Subsystem for Linux
To Reproduce

Set up this repo
run yarn cy:test

Expected behavior
Cypress opens in the GUI and runs the tests.
Screenshots
See the Hacktoberfest overview video @PaulieScanlon and @spences10 did https://youtu.be/TzWm_tullLo?t=921
Desktop (please complete the following information):

OS: Windows 10 using WSL

Additional context
I ran into this issue and explained how to overcome it in a blogpost at https://nickymeuleman.netlify.app/blog/gui-on-wsl2-cypress
Thanks for mentioning it on Twitter Scott!
https://twitter.com/spences10/status/1312059000817692672
Would you like me to add a mention about what to do in the docs?
(yay for possible Hacktoberfest PRs 🎉 )

@NickyMeuleman Hey mate, this is great! Yeah!! if you're up for creating a PR you could maybe add something in the CONTRIBUTING.md somewhere near the integration-test details. i'll add a Hacktoberfest label on the PR and you might get your hands on a t-shirt!


Design: Figure out how to add attributes/Tags for Models

Description of suggestion or shortcoming:
Similar to Tags for values, it would be useful to add metadata for models.
Some ideas: of things we'd want:

defaultSampleCount
name and doc(). Doc can then be shown in the viewer
version for the version of the model
squiggleVersion (Acts as the default/current version, though you can still preview in other versions)
presentation -> Presentation page. Often used, instead of default.  (Could also be called view or showAs or something.
Maybe version, for the version of the current project.

Some ideas for syntax:

Maybe @@name(), and just add it anywhere.
Maybe we have one variable for the "model as a whole". Like, model -> Tag.name("My Model Name). It's not clear what "value" this should have though.
We could use markdown-style metadata, with --- name: "foobar" --- first.

One challenge is that we might want some of these attributes to be easy to be compared between different files that span many Squiggle versions. So for that, we might want to use some non-Squiggle syntax, like JSON or YAML or something simple. That said, this might be a small concern.

I think I kind of like a different name than "export" to be used for this, like config.
config name = "My great model"
config doc = "This is a long description of my model..."

config views = {"user": doc, "editor": [varA, varB]} // or config.view and config.editorView
config author = "Ozzie Gooen"

Instead of config, we could also use meta, expose, model or other.

@berekuk I'd be curious to get your quick take on the above sometime.

// node_version = 3.30

I guess a different way this could work is something like:
@name("My great model")
@doc("Long doc")
__file__  //Refers to current file.
....

__file__ = __file__ -> Tag.showAs(Calculator)


NameError: uninitialized constant ActionMailer

Checklist

[x] Upgrade Jets: Are you using the latest version of Jets? This allows Jets to fix issues fast. There's a jets upgrade command that makes this a simple task. There's also an Upgrading Guide: http://rubyonjets.com/docs/upgrading/
[x] Reproducibility: Are you reporting a bug others will be able to reproduce and not asking a question. If you're unsure or want to ask a question, do so on https://community.rubyonjets.com
[ ] Code sample: Have you put together a code sample to reproduce the issue and make it available?  Code samples help speed up fixes dramatically. If it's an easily reproducible issue, then code samples are not needed. If you're unsure, please include a code sample.

My Environment

Software
Version

Operating System
OSX 10.13.6

Jets
1.9.12

Ruby
2.5.3

Expected Behaviour

Current Behavior

error occurred when running bundle exec jets console command.
bundler: failed to load command: jets (/Users/NightSwinger/.rbenv/versions/2.5.3/bin/jets)
NameError: uninitialized constant ActionMailer
  /Users/NightSwinger/visionsofblue89/garbages/actionmailer/app/mailers/application_mailer.rb:1:in `<top (required)>'
  /Users/NightSwinger/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/zeitwerk-2.1.6/lib/zeitwerk/kernel.rb:16:in `require'
  /Users/NightSwinger/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/zeitwerk-2.1.6/lib/zeitwerk/kernel.rb:16:in `require'
  /Users/NightSwinger/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/jets-1.9.12/lib/jets/core_ext/kernel.rb:11:in `require'
  /Users/NightSwinger/visionsofblue89/garbages/actionmailer/app/mailers/user_mailer.rb:1:in `<top (required)>'
  /Users/NightSwinger/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/zeitwerk-2.1.6/lib/zeitwerk/kernel.rb:16:in `require'
  /Users/NightSwinger/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/zeitwerk-2.1.6/lib/zeitwerk/kernel.rb:16:in `require'
  /Users/NightSwinger/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/jets-1.9.12/lib/jets/core_ext/kernel.rb:11:in `require'
  /Users/NightSwinger/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/zeitwerk-2.1.6/lib/zeitwerk/loader.rb:369:in `block (2 levels) in eager_load'
  /Users/NightSwinger/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/zeitwerk-2.1.6/lib/zeitwerk/loader.rb:666:in `block in ls'
  /Users/NightSwinger/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/zeitwerk-2.1.6/lib/zeitwerk/loader.rb:663:in `foreach'
  /Users/NightSwinger/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/zeitwerk-2.1.6/lib/zeitwerk/loader.rb:663:in `ls'
  /Users/NightSwinger/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/zeitwerk-2.1.6/lib/zeitwerk/loader.rb:365:in `block in eager_load'
  /Users/NightSwinger/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/zeitwerk-2.1.6/lib/zeitwerk/loader.rb:360:in `synchronize'
  /Users/NightSwinger/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/zeitwerk-2.1.6/lib/zeitwerk/loader.rb:360:in `eager_load'
  /Users/NightSwinger/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/jets-1.9.12/lib/jets/stack.rb:77:in `eager_load_shared_resources!'
  /Users/NightSwinger/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/jets-1.9.12/lib/jets/stack.rb:70:in `has_resources?'
  /Users/NightSwinger/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/jets-1.9.12/lib/jets/application.rb:212:in `default_iam_policy'
  /Users/NightSwinger/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/jets-1.9.12/lib/jets/application.rb:188:in `set_iam_policy'
  /Users/NightSwinger/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/jets-1.9.12/lib/jets/application.rb:23:in `configs!'
  /Users/NightSwinger/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/jets-1.9.12/lib/jets/booter.rb:22:in `boot!'
  /Users/NightSwinger/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/jets-1.9.12/lib/jets/core.rb:18:in `boot'
  /Users/NightSwinger/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/jets-1.9.12/lib/jets/cli.rb:46:in `boot_jets'
  /Users/NightSwinger/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/jets-1.9.12/lib/jets/cli.rb:25:in `start'
  /Users/NightSwinger/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/jets-1.9.12/lib/jets/cli.rb:5:in `start'
  /Users/NightSwinger/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/jets-1.9.12/exe/jets:14:in `<top (required)>'
  /Users/NightSwinger/.rbenv/versions/2.5.3/bin/jets:23:in `load'
  /Users/NightSwinger/.rbenv/versions/2.5.3/bin/jets:23:in `<top (required)>'

Step-by-step reproduction instructions

jets new demo
cd demo
bundle exec jets generate mailer UserMailer new_user
bundle exec jets console

Code Sample

Solution Suggestion

Fixed in #288 Released in v1.9.14


Ripple upgrade required

On the staging infrastructure of our App we are using ripple testnet (started Ripple implementation recently), now when we try to send a TX we get the exception message from RPC "Ripple upgrade required".
I've pulled and built latest master and still have the same issue, what does this mean?

This message indicates that your server does not support an amendment that is enabled. The altnet will, on occasion, operate on code that is ahead of the master branch. You can try building develop instead.

just checked out develop, SConstruct file is missing, I can't build it, any other way to build develop?

With cmake.

any docs on how to compile it?

You can check the platform-specific build instructions in the Builds subfolder of the repo. https://github.com/ripple/rippled/tree/develop/Builds/linux is the linux one.

If you're familiar with docker you can get a testnet node up and running using https://hub.docker.com/r/vhendriks/docker-rippled/ (which is a fork from the gatehub repo, but with a special nightly build (vhendriks/docker-rippled:rippled-nightly)

will probably just docker for now. thanks


provide Bool attribute to check for parents

replaces #144, and closes #140

Coverage remained the same when pulling 5c2e96b21aad974ed0d0cfb1dc4332c4b47d0e04 on yeesian:has-parents into 5b4889aaab4bc1ba355e5ad729b7502ad5b6ce7a on JuliaLang:master.

Coverage remained the same when pulling 5c2e96b21aad974ed0d0cfb1dc4332c4b47d0e04 on yeesian:has-parents into 5b4889aaab4bc1ba355e5ad729b7502ad5b6ce7a on JuliaLang:master.

Hi,
Could I propose a change?
hasparent of the source right now returns true even though technically there's no parent to the source. Could we change this so that it returns false?


Create CODE_OF_CONDUCT.md

Proposal to just use the Contributor Covenant 2.0 as is. We can change the email later.

Considering that this repository is CC0, do we need to add something in the README about third-party files?

That is probably a good idea. We should also include the specific license as a slug in a comment in the top of every file to be really explicit.

Merging as #7 added a notice regarding non-C00 licenses.


Socket mode disconnections with AsyncApp

Hello,
From time to time I experience what I believe are disconnections of the web socket to Slack.
I use slack_bolt.app.async_app.AsyncApp and slack_bolt.adapter.socket_mode.aiohttp.AsyncSocketModeHandler. Every few weeks, the application becomes unresponsive, and slash commands trigger /foo failed with the error "dispatch failed".
Looking at logs, I believe those are relevant:
2021-07-21 05:05:40:slack_bolt.AsyncApp:__init__:INFO:The session seems to be already closed. Going to reconnect...
2021-07-21 05:05:40:slack_bolt.AsyncApp:__init__:INFO:A new session has been established
2021-07-21 05:05:40:slack_bolt.AsyncApp:__init__:INFO:The old session has been abandoned

While the 2nd and 3rd line happen every now and then, the first line ("The session seems to be already closed. Going to reconnect...") doesn't.
Do you have any idea why this happens?
Reproducible in:
The slack_bolt version
slack-bolt==1.5.0
slack-sdk==3.5.0
slackclient==1.3.2

Python runtime version
Python 3.8.10

OS info
This runs in a Docker container based on python:3.8.10-slim-buster
Steps to reproduce:
I sadly can't consistently reproduce it at the moment, this seems to happen transiently.
Expected result:
The web socket stays active.
Actual result:
Connection seems to be lost and the app is not reachable anymore.
Requirements
Please read the Contributing guidelines and Code of Conduct before creating this issue or pull request. By submitting, you are agreeing to those rules.

Hi @matthieucan, thanks for taking the time to report this issue (and we're sorry about the error)!
Considering the given circumstances, this sounds like a race condition issue on the library side. To improve this, the session monitoring logic may need to have better synchronization of shared data in the Socket Mode client (specifically, the code may need asyncio.Lock for safer reconnection internally). We'll take a look at this issue and will try to eliminate this in future versions.

Hi @matthieucan, thanks for taking the time to report this issue (and we're sorry about the error)!
Considering the given circumstances, this sounds like a race condition issue on the library side. To improve this, the session monitoring logic may need to have better synchronization of shared data in the Socket Mode client (specifically, the code may need asyncio.Lock for safer reconnection internally). We'll take a look at this issue and will try to eliminate this in future versions.

Hi @seratch, thank you for your very fast answer!
I'm glad you have it on your radar, I'll be sure to follow future improvements and update my libs as soon as I can :)

After further investigation, I've figured out that this is an issue on the SocketModeClient side. Let me transfer this issue to https://github.com/slackapi/python-slack-sdk


[bug] npm run dev执行失败

<EMAIL_ADDRESS>dev
vite --host

file:///XAgent/XAgentWeb/node_modules/vite/bin/vite.js:7
await import('source-map-support').then((r) => r.default.install())
^^^^^
SyntaxError: Unexpected reserved word
at Loader.moduleStrategy (internal/modules/esm/translators.js:133:18)
at async link (internal/modules/esm/module_job.js:42:21)
npm ERR! code 1
npm ERR! path /home/ys/XAgent/XAgentWeb
npm ERR! command failed
npm ERR! command sh -c vite --host
npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2023-10-18T12_14_44_491Z-debug.log
执行失败log ( /root/.npm/_logs/2023-10-18T12_14_44_491Z-debug.log )
0 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'run', 'dev' ]
1 info using<EMAIL_ADDRESS>2 info using<EMAIL_ADDRESS>3 timing config:load:defaults Completed in 1ms
4 timing config:load:file:/usr/share/nodejs/npm/npmrc Completed in 1ms
5 timing config:load:builtin Completed in 1ms
6 timing config:load:cli Completed in 1ms
7 timing config:load:env Completed in 0ms
8 timing config:load:file:/home/ys/XAgent/XAgentWeb/.npmrc Completed in 0ms
9 timing config:load:project Completed in 1ms
10 timing config:load:file:/root/.npmrc Completed in 0ms
11 timing config:load:user Completed in 0ms
12 timing config:load:file:/etc/npmrc Completed in 0ms
13 timing config:load:global Completed in 0ms
14 timing config:load:cafile Completed in 0ms
15 timing config:load:validate Completed in 0ms
16 timing config:load:setUserAgent Completed in 0ms
17 timing config:load:setEnvs Completed in 0ms
18 timing config:load Completed in 5ms
19 verbose npm-session 8f61d137f4f07a4c
20 timing npm:load Completed in 11ms
21 timing command:run-script Completed in 82ms
22 verbose stack Error: command failed
22 verbose stack     at ChildProcess. (/usr/share/nodejs/@npmcli/promise-spawn/index.js:64:27)
22 verbose stack     at ChildProcess.emit (events.js:314:20)
22 verbose stack     at maybeClose (internal/child_process.js:1022:16)
22 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:287:5)
23 verbose pkgid<EMAIL_ADDRESS>24 verbose cwd /XAgent/XAgentWeb
25 verbose Linux 5.10.0-23-amd64
26 verbose argv "/usr/bin/node" "/usr/bin/npm" "run" "dev"
27 verbose node v12.22.12
28 verbose npm  v7.5.2
29 error code 1
30 error path /home/ys/XAgent/XAgentWeb
31 error command failed
32 error command sh -c vite --host
33 verbose exit 1

在XAgentWeb目录下执行npm install时同样遇到问题
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/vue
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!   peer<EMAIL_ADDRESS>|| ^3.3.0" from<EMAIL_ADDRESS>npm ERR!   node_modules/pinia
npm ERR!     dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer vue@">= 2.5 < 2.7" from<EMAIL_ADDRESS>npm ERR! node_modules/@vue/composition-api
npm ERR!   peerOptional<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/pinia
npm ERR!     dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!


Update to WordPress 4.9.8

I thought of adding this first, but that'd be evil 😄.
Edit: actually, it looks like they've limited the audience for the callout. It doesn't show up in production.

I need to automate this again so I can steal @knowler's commits


[POC?] don't rerender allTheCells allTheTime

⚠ Checkboxtable does not have highlighting for disabled/muted rows in the current state of this PR.
Have a look at ContentCell in the Table-Component. Its sole purpose is to
highlight rows once a CheckboxTable has a disabled or checked row.
To do that it's computing css in a very dynamic way. That dynamic computation
breaks reacts reconciliation - effectively forcing every cell to rerender on
every update (a scroll-event is an update for the MultiGrid we use).
We should get rid of the dynamic nature of ContentCell. Unfortunately i
don't know how to do that, so this is rather a POC that breaks disabled and
checked rows in the CheckboxTable.
Before
Note all the flashing boxes indicating a rerender.

After
A lot less flashing boxes 🎉

@pierrebeitz - I figured out a way we can do this with Context, but I'm wondering if there's a better solution 🤔
If you have time, I'd love to spend a few minutes pairing tomorrow.


tools/format: Minor improvement for err handling

Include error output if the subcommand fails

Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

Merge main can deflake the quic test right now. Thanks!

ill kick it but if it fails again i can probably push it through and save ci cycles


[Enhancement] Support filtering of sub-projects for dependency submission

Loving the new dependency submission feature!
However, I have multi-module projects, where only a subset of the modules publish artefacts, others are used purely for testing within the project.
I'd like to be able to limit which sub-modules/projects publish dependencies to GitHub.  Something like a regex white and/or black-list would be perfect.

Doh, RTFM... DEPENDENCY_GRAPH_INCLUDE_PROJECTS


adds a screenshot

🚀 The docs preview is ready! Check it out here:     https://modal-labs-examples--frontend-preview-e85c66e.modal.run


API: Increase priority of Magma operation, and add coercions between [Magma] and [Mul]

See the discussion in https://leanprover.zulipchat.com/#narrow/stream/458659-Equational/topic/Symbol.20for.20.60Magma.2Eop.60
The two tasks are:

Set the priority for Magma.op higher than for Function.comp so that in the (rare) cases we work with magmas that also have a composition operation, ∘ defaults to the magma operation.
Create coercion API to convert [Magma G] to [Mul G] if needed (but do not make these instances, as usually we would not want to automatically activate these coercions).

claim

propose PR #240

withdraw PR #240


Allow unknowElement and unknownAttribute as a function

Defining unknownElement or unknownAttribute as a function is much more powerful than a static definition.
Instead of the following distributed logic:
var docSpec={
  unknownElement: {
    menu: [{
      caption: function(jsElement) { 'Delete <'+jsElement.name+'>'; },
      action: Xonomy.deleteElement,
      hideIf: function(jsElement) { return jsElement.name === 'root'; }
    }];
  },
  unknownAttribute: {...}
};

... we can make the condition logic centralized as follows:
var docSpec={
  unknownElement: function(elName){
    return (elName !== 'root')
      ? { menu: [{ caption: 'Delete <'+elName+'>', action: Xonomy.deleteElement }]}
      : {};
  },
  unknownAttribute: function(elName, attrName) {
    ...
  },
};

... and for more advanced use-cases it may not be even possible to statically define specification up-front.

Very clever. Now people will want to put everything in these functions and .elements will be empty! :-)


Added a "missing" values prop

It would be nice to have a way to be notified about what values are missing from the data structure

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


"Cannot pause container[uuid]: OCI runtime pause failed: unable to freeze: unknown"

Hi,
I am intermittently getting the above error when trying topologies such as the 5 node leaf-spine. I am using the latest ceos image.
I can run two nodes fine, but it seems once I get to 3-5 it seems to hit an issue. This makes me feel it is hitting a race condition where it tries to pause the container before it has fully been started.
Is this something others have hit before?

From my understanding the container.start() function should be blocking until the container transitions to the running state. This is the docker's source of this error:
https://github.com/moby/moby/blob/7b9275c0da707b030e62c96b679a976f31f929d3/daemon/pause.go#L41
So the container has definitely started since it's gone past this line.
I suspect it could be something to do with timeouts, e.g. not able to pause the init process in X seconds, but it looks like the error comes from several layers deep. Docker makes a call to containerd, which in turn calls runs, which is where it breaks.
Looking at the freeze function, it doesn't look promising:
 The numbers below are empirically chosen to have a decent
 chance to succeed in various scenarios ("runc pause/unpause
 with parallel runc exec" and "bare freeze/unfreeze on a very
 slow system"), tested on RHEL7 and Ubuntu 20.04 kernels.

Can you describe the system you're running on, e.g. CPU, OS version, Docker version?


pylint: 2.13.5 -> 2.13.8

Description of changes

Update pylint from 2.13.5 to 2.13.8
Update astroid from 2.11.2 to 2.11.4 (tested compatibility with pylint)
Add top-level package reference for pylint
Add longDescription with included commands (pyreverse, epylint and symilar)
Disable failing tests on x86_64-darwin. Enable formerly non-working tests.
Add myself as maintainer (totoroot)
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[x] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

@fabaff Could you review please

Should target staging https://github.com/NixOS/nixpkgs/blob/master/CONTRIBUTING.md#rebasing-between-branches-ie-from-master-to-staging

Thanks, @Artturin! I followed the guide and updated the PR.

I'm reluctant to accept another update to pylint/astroid before the branch off, since they can be quite problematic.

Yes, these are totally fine.

Most of the commit messages should start with python3Packages.

@SuperSandro2000 Approving the changes with my veto on the version bumps, not sure what point you're trying to make.

We can merge it as is after the branch off.

We can merge parts of it before the branch off.

#172087

Closing this as newer version was merged with PR #175773 and @SuperSandro2000 is now maintaining the package


Release v1.0.0 requirements 🎯

Only few more steps are left for official v1.0.0 release.
Here's the checklist for releasing v1.0.0:
(Please feel free to add more items)
Features

[ ] Add remaining indicators.
[ ] Update existing indicators.
[ ] Final API check.

Tests

[ ] Update benchmarks.(#)
[ ] Add benchmark result to docs.
[ ] Add return type check.
[ ] Check if there's something more to test.

Documentation

[ ] Write corresponding documentation (# )
[ ] Final review for docs and docstrings.

Release

[ ] Check DLL version.
[ ] Final sanity check and code style.
[ ] Release to PyPI.
[ ] Apply release description to tag.

I think a key element here, before we flip it to v1.0.0 is to ensure that it’s stable.  There’s a couple ways to do this:

dogfood it.  Use the library in your own use case for a while, at least a couple months.
just wait, for more user feedback.  This could take 3-6 months, depending on how much usage

Yeah, the silver lining is that we are gradually getting more users according to Google Analytics.


Expo SDK 39 Button Lag / Delay onPress

🐛 Bug Report

I updated to Expo SDK 39, which updated RN to 63 and also bumped the version of many other dependencies. Now when I press on a Ui Kitten button, there is a noticeable delay after the button is pushed for the button to dim as it should if it was pressed and for the action to happen. The "onPress" animation for that button is also not really happening on iOS at all unless you push and hold for a long time before releasing the button. Web is not effected, have not tested Android.
Could this mean we need to update Ui Kitten with RN's new "Pressable" component over TouchableOpacity?
To Reproduce
Steps to reproduce the behavior:
Update to latestes with "expo update"
Press any  in app and delay is obvious compared to before on iOS
Expected behavior
Buttons to be smooth and buttery like they use to be.

Link to runnable example or repository (highly encouraged)

github repo
snack demo
UI Kitten and Eva version

Package
Version

@eva-design/eva
2.0.0

@ui-kitten/components
5.0.0

Environment information

  System:
    OS: Linux 5.4 Pop!_OS 20.04 LTS
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
  Binaries:
    Node: 14.12.0 - /usr/bin/node
    npm: 6.14.8 - /usr/bin/npm
  npmPackages:
    react: 16.13.1 => 16.13.1
    react-native: 0.63.2 => 0.63.2

could this be related?

So basically what happened is the people over at Facebook thought it would be a good idea to add 130ms of delay to any pressable component. They have been notified that it was a terrible change and I am expecting them to revert this behavior very soon in a release.

Hi @bnussman! Please see the 0.63.3 changelog. That's seems to be fixed


Add failure cases

Move call value to context
Use Failarray helper in mutation selector lib
Add no fill, overfill, and bad signature V failure cases

Codecov Report
Patch and project coverage have no change.

Comparison is base (6fdf0f0) 100.00% compared to head (8122639) 100.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##               1.5     #1138    +/-   ##
==========================================
  Coverage   100.00%   100.00%
==========================================
  Files           46        46
  Lines         2652      2414   -238
  Branches       396       354    -42
==========================================
- Hits          2652      2414   -238

Flag
Coverage Δ

foundry
?

production
100.00% <ø> (ø)

reference
100.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
see 29 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Litle title mistake

In MainActivity.java I suspect :
case 2:
builder.setTicker(getString(R.string.app_name));
builder.setContentTitle(getString(R.string.app_name));
should be
case 2:
builder.setTicker(getString(R.string.app_name));
builder.setContentTitle(getString(R.string.loc_perm));

Thanks man!
I've just updated the repo, do let me know if you found anything else.


Change clef shape and nc head shape no longer working

It seems that a recent change made these stop working.

Changing the headshapes of custos does not work

fixed in cd4ec89


image: p_median3x3: Add function implementation

Targeting memory traffic efficiency.
Signed-off-by: Mateusz Kacprzak<EMAIL_ADDRESS>

Note that some archs like Epiphany is not optimized for function calls, so putting a function in the inner loop is a killer. If the function is simple enough and gets flattened, then it should be ok.


Non functional link in the footer of the website

Description
The link to the "team" under the organization section at the footer of the website is non-responsive.
Screenshots
No response
Additional information
No response

I would be personally working on this

@Abhiram-Gullapalli can you please add a screenshot or gif of the issue?

I hope you understood what I'm trying to convey, the video isn't that clear but hope you got it @kaiwalyakoparkar

@Abhiram-Gullapalli Thank you so much for reporting. We will take a look into the issue

Can you please mention the file location of the bug???


Regenerate datalabeling client

This PR was generated using Autosynth. :rainbow:
Here's the log from Synthtool:
synthtool > Executing /tmpfs/src/git/autosynth/working_repo/google-cloud-clients/google-cloud-datalabeling/synth.py.
synthtool > Ensuring dependencies.
synthtool > Pulling artman image.
latest: Pulling from googleapis/artman
Digest: sha256:9aed6bbde54e26d2fcde7aa86d9f64c0278f741e58808c46573e488cbf6098f0
Status: Image is up to date for googleapis/artman:latest
synthtool > Cloning googleapis.
synthtool > Running generator for google/cloud/datalabeling/artman_datalabeling_v1beta1.yaml.
synthtool > Generated code into /home/kbuilder/.cache/synthtool/googleapis/artman-genfiles/java.
synthtool > Running java formatter on 10 files
synthtool > Running java formatter on 1 files
synthtool > Running java formatter on 284 files
synthtool > Cleaned up 0 temporary directories.
synthtool > Wrote metadata to synth.metadata.

Combined into a single pull request #5880


Allow custom styling for consent banner

Right now the consent banner is styled one-size-fits-all. While we try to keep it low-impact for most designs, this surely hurts adoption in cases where a unified UX is important for operators.
While it's technically trivial to allow operators to inject custom CSS into the iframe element that displays the banner, this also comes with some pitfalls and requirements:

Operators should not be able to alter the content in the banner (i.e. change wording to be misleading or hide certain elements)
The default a11y and privacy standards must be preserved in any case

Approach: allowing operators to define custom CSS per account
Semantic classes are applied to the markup that displays the consent banner. Operators can now add custom CSS for each account which the server will add (in addition to the predefined styles) to each vault response. In order to prevent operators from creating a misleading consent banner the following sanitzation rules are applied to the CSS before saving:

no pseudo content
no hiding of elements
no opacity rules

Pros

Allows operators to apply fine grained styling that matches virtually any site design
Technically simple to implement

Cons

Sanitizing CSS will help, but it will not close all loopholes for malicious use ever (then again, forking Offen is a lot easier and gives you all options)
Does not offer a middle ground for non-technically savvy users that don't want to / cannot write CSS but still want to customize their banner's appearace

As discussed with @hendr-ik in person we would like to start off with the guidelines for sanitizing CSS: we trust the operator who deploys and customizes Offen to keep the consent guarantees intact but aim to prevent attackers (who might hijack a system or similar) from injecting malicious content through CSS.
This means we'll start with the following rules:

no loading of external resources (as this would introduce an external tracking vector)
No use of content. We want to prevent unwanted messages from showing up or attackers changing content.
No use of transparency as this would allow attackers to create an invisible banner and do "clickjacking".

Hi, I don't have the chance to give this much thought from a development point of view.
From a user point of view I really need simple customizations to make Ogden fit in with my designs: border, colors and maybe font family are all I need to touch

I don't have the time to give this much thought from a development point of view in this moment.

Your requirements as a user are super helpful and all we need. Thank you.

@TommasoAmici @whalehub We just merged the PR containing the feature and plan to include it in the next release.
In case you are interested and would like to help us ship a feature that is actually helpful, we'd appreciate any feedback on a test run. To check it out, you can run the development version in demo mode sth like this:
docker pull offen/offen:development
docker run --rm -p 9876:9876  offen/offen:development demo -port 9876

After logging in head to Customize appearance, the documentation link is currently broken because this is not properly released yet, but it would point here https://docs.offen.dev/v/development/running-offen/customizing-consent-banner/
Our primary questions for feedback would be:

can you achieve what you would like to do visually without too much hair pulling?
would you need more/less/different documentation to get up and running?

Any other feedback is welcome too of course. Thank you!

@m90 I love how you implemented this feature, what with the preview function and everything - well done! The documentation was more than sufficient for me personally.
Before

After

This now released in v0.4.2. Thanks for all of your feedback :tophat:


Error: No collateral wallet for DZVJDCDqbmdqVorPS87Jv61YjVFhsvovT3koerNwyPP1

When I run docker-compose up --build
It shows the error
portfinance-liquidator_1  | yarn run v1.22.15
portfinance-liquidator_1  | $ ts-node src/partial.ts
portfinance-liquidator_1  | Port liquidator launched on cluster=https://solana-api.projectserum.com
portfinance-liquidator_1  | Error: No collateral wallet for DZVJDCDqbmdqVorPS87Jv61YjVFhsvovT3koerNwyPP1
portfinance-liquidator_1  |     at /app/src/partial.ts:160:13
portfinance-liquidator_1  | error Command failed with exit code 1.
portfinance-liquidator_1  | info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Could anyone help me to solve this problem, thanks~

Can you send me your public key that you use to run the liquidator?

the public key is : 5fAMqkBNEaqLpZK8Vy63yS4QpiYA943pDMVsAQvA6VGa, may I ask what's the reason for this error? thanks~

Need to have a token account for DZVJDCDqbmdqVorPS87Jv61YjVFhsv
ovT3koerNwyPP1
On Sat, 6 Nov 2021 at 00:35, Jin Kai Yang @.***> wrote:

the public key is : 5fAMqkBNEaqLpZK8Vy63yS4QpiYA943pDMVsAQvA6VGa, may I
ask what's the reason for this error? thanks~
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/port-finance/liquidator/issues/27#issuecomment-962043313,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACMFDUKZ4NCD7P4YJARRZJDUKQBVVANCNFSM5HOEONPA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

--
Wang (Leonard) Ge
Imperial College London 2021
@.***
+44 -<PHONE_NUMBER>4

#28 should fixed it

thank you very much, It's work now!


Zombies elemental resistance from Mon'tregul's Grasp not considered

It's pulling their resistances from passives, ascendancy, and jewels, but not from Mon'tregul's Grasp.
My build:
https://pastebin.com/6xbm0KwN

If you look at Mon'tregul's Grasp, the resistances line is red, which means it hasn't been implemented yet.


Project targeted for .NET Framework 4.5.1 won't build if TaskScheduler NuGet-package 2.5.17 is installed

Steps to reproduce:

Create a new Console Application using .NET Framework 4.5.1
Install TaskScheduler NuGet-package version 2.5.17 (Install-Package TaskScheduler)
Add following line to Main-method:
using (var ts = new TaskService()) {}
Build the solution. Build fails on compiler error:
warning MSB3274: The primary reference "Microsoft.Win32.TaskScheduler, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=0d013ddd5178a2ae, processorArchitecture=MSIL" could not be resolved because it was built against the ".NETFramework,Version=v4.5.2" framework. This is a higher version than the currently targeted framework ".NETFramework,Version=v4.5.1".
error CS0234: The type or namespace name 'TaskScheduler' does not exist in the namespace 'Microsoft.Win32' (are you missing an assembly reference?)

I suspect this is because the binaries in the NuGet-package are located under lib\net45 (instead of lib\net452) and NuGet determines that it's ok to use them in .NET Framework 4.5.1 project. I don't know how  (or if it's even possible) to force NuGet to use binaries targeted for framework 4.0 form example.
Originally posted: 2016-04-11T01:54:46

I believe this is fixed in the 2.5.18 release.
Originally posted: 2016-04-12T18:01:48


Anomaly events

Like STALKER / Metro anomalies should be events, e.g. gravitational anomaly that is just the singulo without the widespread destruction (just the pulling and the shader) that moves through the station.

we have a whole anomaly subdepartment now so i think this is done


allow .cflint as well as .cflintrc to be  used for config

No idea why you need the 'rc' on the config file name, but wondering since you've made that unusual design decisions if you could also allow .cflint to be used for config file as that makes more sense and is easier to understand for other developers.

It's not that unusual. Other linters, such as ESLint, also use the rc ending. What issue are you finding with it?


Can't perfectly center cards on page

I would love to be able to use MTGProxyPrinter but I can't never seem to setup it to make the cards be perfectly centered in the PDF pages. There is always some difference between spacing in the left and right side. This makes printing the back of the cards problematic. I know I can print on a thin paper, cut the cards and put in front of lands or something, but I have 300g/m2 paper at home and a printer capable of printing it. So I can theoretically print proxies/playtest cards that match in thickness the originals, This requires me however, to be able to center front and back perfectly, which I can't do with this app.
Any change to fix this?

#7 might fix the issue but I'm not sure that is the problem you have.
Could you attach a problematic PDF?
Also, are you printing on A4 paper?


Apple Mail 16 empty space between sections

Describe the bug
Apple Mail 16 is showing an empty space between sections when these sections has paddings = 0px.
To Reproduce
Steps to reproduce the behavior:

Create a file with this MJML code: <mjml>...</mjml>
Render it to HTML by doing '...'
Send the HTML to an email address with '...'
See error

Expected behavior
A clear and concise description of what you expected to happen.
MJML environment (please complete the following information):

OS: [e.g. MacOS]
MJML Version [4.9.3]
MJML tool used [try it live]

Email sending environment(for rendering issues):

Platform used to send the email [Litmus]

Affected email clients (for rendering issues):

Email Client [Apple Mail 16]

Screenshots
If applicable, add screenshots to help explain your problem.

Hi.
Hard to say without the MJML to reproduce here. Please past it here : https://mjml.io/try-it-live


Add notification when customer does not add required URLs to exclude from proxy re-encryption as per documentation

In OSD-12147 it was found that a few clusters had misconfigured proxy network requirements which was producing many low alerts. This service log was used to inform them about this. There have been other customer cases where we have found this to be the case too.

The description lgtm. But maybe change the name of file to cluster_wide_proxy_exclusion_url_misconfigured.json? To match with other cluster wide proxy related templates.

/approve


files::tests::test_gzip_is_binary failure in 0.43.0

When updating FreeBSD port of difftastic to 0.43.0:
running 118 tests
test diff::dijkstra::tests::atom_after_empty_list ... ok
test diff::dijkstra::tests::atom_after_novel_list_contiguous ... ok
test diff::dijkstra::tests::mark_syntax_different_atoms ... ok
test diff::dijkstra::tests::mark_syntax_equal_atoms ... ok
test diff::dijkstra::tests::prefer_atoms_same_line ... ok
test diff::dijkstra::tests::prefer_children_same_line ... ok
test diff::dijkstra::tests::repeated_atoms ... ok
test diff::dijkstra::tests::replace_comment_prefer_most_similar ... ok
test diff::dijkstra::tests::replace_similar_comment ... ok
test diff::dijkstra::tests::replace_very_different_comment ... ok
test diff::myers_diff::tests::test_slice_by_hash_different_items ... ok
test diff::myers_diff::tests::test_slice_by_hash_same_items ... ok
test diff::myers_diff::tests::test_slice_different_items ... ok
test diff::myers_diff::tests::test_slice_same_items ... ok
test diff::myers_diff::tests::test_slice_unique_different_items ... ok
test diff::myers_diff::tests::test_slice_unique_same_items ... ok
test diff::sliders::tests::test_slider_at_end ... ok
test diff::sliders::tests::test_slider_at_start ... ok
test diff::sliders::tests::test_slider_partially_unchanged ... ok
test diff::sliders::tests::test_slider_two_steps ... ok
test diff::unchanged::tests::test_count_common_unique ... ok
test diff::unchanged::tests::test_shrink_unchanged_at_end ... ok
test diff::unchanged::tests::test_shrink_unchanged_at_start ... ok
test diff::unchanged::tests::test_shrink_unchanged_nested ... ok
test diff::unchanged::tests::test_similar_ignore_delimiter ... ok
test diff::unchanged::tests::test_similar_with_common_grandchildren ... ok
test diff::unchanged::tests::test_split_mostly_unchanged_toplevel ... ok
test diff::unchanged::tests::test_split_preserves_outer_delimiters ... ok
test diff::unchanged::tests::test_split_unchanged_middle ... ok
test diff::unchanged::tests::test_split_unchanged_multiple ... ok
test diff::dijkstra::tests::extra_atom_lhs ... ok
test diff::unchanged::tests::test_split_unchanged_outer_delimiter ... ok
test diff::unchanged::tests::test_split_unchanged_toplevel_at_end ... ok
test display::context::tests::test_all_lines ... ok
test diff::unchanged::tests::test_split_unchanged_toplevel_at_start ... ok
test display::context::tests::test_all_matched_lines ... ok
test display::context::tests::test_calculate_before_context ... ok
test display::context::tests::test_compact_gaps_with_larger_gap ... ok
test display::context::tests::test_match_blanks_between ... ok
test display::context::tests::test_match_preceding_blanks ... ok
test display::context::tests::test_match_preceding_blanks_first_pair ... ok
test display::context::tests::test_matched_lines_blank_at_ends ... ok
test display::context::tests::test_matched_lines_novel_on_same_line ... ok
test display::context::tests::test_compact_gaps ... ok
test display::context::tests::test_pad_after_when_line_exceeds_max ... ok
test display::hunks::tests::test_matched_lines_for_hunk ... ok
test display::hunks::tests::test_matched_lines_for_hunk_misaligned ... ok
test diff::dijkstra::tests::identical_atoms ... ok
test display::hunks::tests::test_matched_pos_to_hunks ... ok
test display::hunks::tests::test_sorted_novel_positions_simple ... ok
test display::side_by_side::tests::test_display_single_column ... ok
test display::side_by_side::tests::test_format_missing_line_num ... ok
test display::side_by_side::tests::test_format_missing_line_num_at_end ... ok
test display::side_by_side::tests::test_width_calculations ... ok
test display::style::tests::split_string_cjk ... ok
test display::style::tests::split_string_cjk2 ... ok
test display::side_by_side::tests::test_display_hunks ... ok
test display::style::tests::split_string_simple ... ok
test display::style::tests::split_string_unicode ... ok
test display::style::tests::test_split_and_apply ... ok
test display::style::tests::test_split_and_apply_gap_between_styles_on_wrap_boundary ... ok
test display::style::tests::test_split_and_apply_missing ... ok
test display::style::tests::test_split_and_apply_trailing_text ... ok
test display::style::tests::test_split_and_apply_trailing_text_newline ... ok
test display::style::tests::test_combining_char ... ok
test files::tests::test_gzip_is_binary ... FAILED
test files::tests::test_png_bytes_are_binary ... ok
test line_parser::tests::test_novel_lhs_trailing_newlines ... ok
test line_parser::tests::test_positions_no_changes ... ok
test line_parser::tests::test_positions_novel_lhs ... ok
test line_parser::tests::test_positions_whitespace_is_change ... ok
test line_parser::tests::test_split_newlines ... ok
test lines::tests::codepoint_len_non_ascii ... ok
test files::tests::test_plaintext_is_text ... ok
test lines::tests::empty_str_max_line ... ok
test line_parser::tests::test_no_changes_trailing_newlines ... ok
test lines::tests::from_offsets_first_line ... ok
test lines::tests::from_offsets_split_over_multiple_lines ... ok
test lines::tests::str_max_line ... ok
test lines::tests::str_max_line_extra_trailing_newline ... ok
test lines::tests::str_max_line_trailing_newline ... ok
test lines::tests::test_is_all_whiteapce ... ok
test lines::tests::test_split_line_empty ... ok
test lines::tests::test_split_line_single ... ok
test lines::tests::test_split_line_with_crlf ... ok
test lines::tests::test_split_line_with_newline ... ok
test lines::tests::test_split_line_with_trailing_newline ... ok
test lines::tests::from_offsets_first_char ... ok
test options::tests::test_app ... ok
test lines::tests::from_offsets_relative_to ... ok
test parse::guess_language::tests::test_guess_by_emacs_mode ... ok
test parse::guess_language::tests::test_guess_by_emacs_mode_shorthand ... ok
test parse::guess_language::tests::test_guess_by_emacs_mode_shorthand_no_spaces ... ok
test options::tests::test_detect_display_width ... ok
test parse::guess_language::tests::test_guess_by_emacs_mode_second_line ... ok
test parse::guess_language::tests::test_guess_by_extension ... ok
test parse::guess_language::tests::test_guess_by_env_shebang ... ok
test parse::guess_language::tests::test_guess_by_whole_name ... ok
test parse::guess_language::tests::test_guess_unknown ... ok
test parse::syntax::tests::test_atom_equality_ignores_highlighting ... ok
test parse::syntax::tests::test_comment_and_atom_differ ... ok
test parse::syntax::tests::test_flatten_trivial_list ... ok
test parse::syntax::tests::test_ignore_empty_atoms ... ok
test parse::syntax::tests::test_multiline_comment_ignores_leading_whitespace ... ok
test parse::syntax::tests::test_new_atom_truncates_carriage_return ... ok
test parse::syntax::tests::test_split_comment_words_basic ... ok
test parse::syntax::tests::test_split_words ... ok
test parse::syntax::tests::test_split_words_punctuations ... ok
test parse::syntax::tests::test_split_words_single_unicode ... ok
test parse::syntax::tests::test_split_words_single_unicode_not_alphabetic ... ok
test parse::guess_language::tests::test_guess_by_shebang ... ok
test parse::syntax::tests::test_split_words_treats_newline_separately ... ok
test parse::syntax::tests::test_split_words_unicode ... ok
test parse::tree_sitter_parser::tests::test_parse ... ok
test parse::tree_sitter_parser::tests::test_parse_empty_file ... ok
test parse::tree_sitter_parser::tests::test_subtrees ... ok
test display::context::tests::test_merge_in_opposite_lines ... ok
test tests::test_diff_identical_content ... ok

failures:

---- files::tests::test_gzip_is_binary stdout ----
thread 'files::tests::test_gzip_is_binary' panicked at 'assertion failed: `(left == right)`
  left: `Text("謟\u{8}뀺掑\u{300}躋˥䐀棒Ͱ\0")`,
 right: `Binary`', src/files.rs:299:9
stack backtrace:
   0: rust_begin_unwind
   1: core::panicking::panic_fmt
   2: core::panicking::assert_failed_inner
   3: core::panicking::assert_failed
   4: core::ops::function::FnOnce::call_once
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

failures:
    files::tests::test_gzip_is_binary

test result: FAILED. 117 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.05s

Duplicate of #478, thanks for the report!


Add tests for other cable drivers as well

Currently, subctl tests for default cable driver only. Add tests to run against all PRs for other cable drivers as well.

We decided to run a minimal set of tests in subctl. Also submariner-operator doesn't even run cable driver tests. The submariner repo tests all those.

What's the value of having a full e2e matrix?
There's nothing in the e2e tests that actually verifies that any given flag that you set is actually getting deployed (which is a bigger problem but not directly related to this).
You could have simple unit tests to achieve the same goal - see that a flag that you set gets passed down as is to the CR that gets created.
Or if you want you could say that we want to add it to system tests, but since the whole point is to test that a flag gets passed down to a CR I think it's overkill.

You could have simple unit tests to achieve the same goal - see that a flag that you set gets passed down as is to the CR that gets created.

👍

Discussing on the PR scrub, it seems to make sense to have system tests in the operator to verify cable drivers we request are deployed and/or to have unit tests in subctl to verify the submariner object's cable driver flag is set properly.

Unit test part: https://github.com/submariner-io/subctl/issues/408

System tests: https://github.com/submariner-io/submariner-operator/issues/2373


improve memory efficiency and speed of mask plotting in automatic mask generation example

The existing show_anns function creates a separate image for each mask and calls imshow once for each mask. For large images with many masks,  this is very slow and can run out of available RAM.
The function has been modified to create a single img array representing all of the mask overlays combined, greatly improving the memory efficiency and speed when visualizing the masks with matplotlib. Also, I removed unused variables and added an opacity parameter.

@klarrieu I think I did something similar in https://github.com/facebookresearch/segment-anything/pull/73 if you want to take a look.

@calebrob6 Woops, you're totally right. Looks great. Thanks, I'll close this as duplicate of #73


Revert "Eliminate snapshot, depfile opts from bundle cmd"

Fix build
Reverts flutter/flutter#22495

TBR @cbracken


Pagination improvements

Acceptance Criteria (see attached comments for details and videos of the problems):

The pagination should be located at the top right of the screen, at the end of the search page "header" (the component that contains the filters, sort criteria, pagination, number of results, reset button, views, ...).

That header should take the view width and never appear off the page. Even if the table extends.
Currently, the pagination can be out of view when the table is larger: https://github.com/BlueBrain/nexus/issues/2623#issuecomment-906176512

When there are no results, the count should say "No results" and the pagination should be greyed out (inactive) showing only one page

Right now, when the search returns no results, the table jumps because the pagination disappears (see video below).

The text next to the pagination should say "x results" with x the total number of returned documents.

https://user-images.githubusercontent.com/11705901/131097092-d4cb79a7-9608-45b4-81e8-08693cc4a1f5.mp4
Please re-test the acceptance criteria of the following tickets once this is fixed:

https://github.com/BlueBrain/nexus/issues/2623
https://github.com/BlueBrain/nexus/issues/2610

Please add your planning poker estimate with ZenHub @adulbrich


Wrong result of JavaScript code execution

The following code should log 1000000 (1 million) but instead it produces a random number, usually in range 100000 - 160000.
Executing code in my browser's console produces a correct result.
My browser is Chrome 54.0.2840.71 m.
const limit = 1000 * 1000;
let i;
let iterations = 0;

for(i = 0; i < limit; ++i) {
   iterations += 1;
}

console.log(iterations);

Loop protection. Add //noprotect to the JS and it won't kick in.


Fix RHEL subscription deregistration on OpenStack

The deregistration of a RHEL subscription failed if the machines FQDN
did not match its node name. This happened for instance on OpenStack
clusters that add the .novalocal domain suffix.
This change sets the fqdn field in the cloud-init userdata to the hostname to
ensure that the machine name matches the registered name in the
RHSM or Satellite server.
What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number> format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Optional Release Note:

Fix RHEL subscription deregistration on OpenStack

/retest

/assign @moadqassem

/approve
/lgtm


fix typo

Codecov Report

Merging #140 (a2e0793) into main (eda34b4) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #140   +/-   ##
=======================================
  Coverage   92.19%   92.19%
=======================================
  Files          18       18
  Lines        5126     5126
=======================================
  Hits         4726     4726
  Misses        349      349
  Partials       51       51

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update eda34b4...a2e0793. Read the comment docs.

Codecov Report

Merging #140 (a2e0793) into main (eda34b4) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #140   +/-   ##
=======================================
  Coverage   92.19%   92.19%
=======================================
  Files          18       18
  Lines        5126     5126
=======================================
  Hits         4726     4726
  Misses        349      349
  Partials       51       51

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update eda34b4...a2e0793. Read the comment docs.


[AMHACK] Unable to define a blacklisting policy for API calls from a valid IPv6

Description:
Unable to define a blacklisting policy for API calls from a valid IPv6
Suggested Labels:
Bug
APIM Admin console
Affected Product Version:
APIM wum updated - wso2am-<IP_ADDRESS>0928473100.zip
APIM analytics - wso2am-analytics-<IP_ADDRESS>0935606971.zip
OS, DB, other environment details and versions:
Standalone
Ubuntu 15.10
JDK - jdk1.8.0_66
DB - Postgres 9.6.3
Browser - Chrome Version 58.0.3029.96 (64-bit)
Pre -requisites

An API with subscriptions

Steps to reproduce:

Go to Admin console -> Throttling Policies -> Blacklist
Add a blacklisting policy for with valid ipv6
ex: 2001:0db8:85a3:0000:0000:8a2e:0370:7334

Observations

IPv6 is not recognized as a valid input when defining the blacklisting policy

IPv6 is not supported at the moment. Please refer to https://github.com/wso2/product-apim/issues/1515 for this feature.


Challenger Coin - Improve canUse() to avoid using it in more impossible map situations

Done with other commits and issues already.


Column mixin outputs strange behaviour.

Hey,
I am using column mixin with cycle variable in connection with angular js ng-repeat directive. I want to make a projects gallery with 3 gallery elements in row.
HTML file:

                 {{project.name}}
                 {{project.location}}

SCSS file:
.projectGalleryElement {     @include column(1/3, $cycle: 3);     margin-bottom: 20px;     .pictureMockup {         background-color: green;         height: 182px;         width: 100%;         margin-bottom: 6px;     }     a {         text-decoration: none;         line-height: 26px;     } }
In the first row of the gallery, the first element is displayed correctly, but the second element is offseted by 1/3, even though I do not use $offset variable. In each next row gallery elements are placed correctly.

Hey,
I had the same behaviour, but fixed it.
My HTML looked like that :

Projects

Project 1

Project 2

Project 3

Project 4

However, @include column() eventually uses nth-child, like below :
div.project:nth-child(n) {
  margin-right: 3%;
  float: left;
  clear: none;
}

div.project:nth-child(3n) {
  margin-right: 0%;
  float: right;
}

div.project:nth-child(3n + 1) {
  clear: both;
}

In my case, the first div.project was actually the 2nd child of the container.
I'm pretty sure your "Project 1" is also 2nd child of its container.
Maybe the first child is your top bar.
I did something like that :

Projects

Project 1

Project 2

Project 3

Project 4

Also more semantically correct.

Hey,
Thanks for the suggestion. My gallery looks ok right now with HTML code written as follows:

                     {{project.name}}
                     {{project.location}}

SCSS class definition is the same as before.

Thanks for the help @Philoozushi 👍


How to use pykaldi to get phone posterior?

I want to calculate GOP by pykaldi ，and now I need phone-alignment and phone posterior ，I can get the former by aligner，however I don‘t know how to get the latter.

repeat


Print extra line at the end of routes inspection

When multiple applications are present in a Lotus project, the output of lotus routes is cluttered because the lack of extra blank line between groups of routes:
Steps to reproduce:
➜ lotus new bookshelf && cd bookshelf && bundle
➜ bundle exec lotus generate app admin
➜ bundle exec lotus generate action web books#index --url=/books
➜ bundle exec lotus generate action admin users#index --url=/users
➜ bundle exec lotus routes
                Name Method     Path                           Action

                     GET, HEAD  /admin/users                   Admin::Controllers::Users::Index
                Name Method     Path                           Action

                     GET, HEAD  /books                         Web::Controllers::Books::Index

Expected would be:
➜ bundle exec lotus routes
                Name Method     Path                           Action
                     GET, HEAD  /admin/users                   Admin::Controllers::Users::Index

                Name Method     Path                           Action
                     GET, HEAD  /books                         Web::Controllers::Books::Index

Ref #78
/cc @davydovanton

good idea I think :+1:
but may be is better to create smth like this:
                Name Method     Path                           Action
         --------------------------------------------------------------------------------------
                     GET, HEAD  /admin/users                   Admin::Controllers::Users::Index

                Name Method     Path                           Action
         --------------------------------------------------------------------------------------
                     GET, HEAD  /books                         Web::Controllers::Books::Index

@davydovanton With that lines they look grouped like illustrated by the following screenshot:

so, @jodosha may be is better create smth like this?
                Name Method     Path                           Action

                     GET, HEAD  /admin/users                   Admin::Controllers::Users::Index
                     GET, HEAD  /admin/users                   Admin::Controllers::Users::Index

         --------------------------------------------------------------------------------------

                Name Method     Path                           Action

                     GET, HEAD  /books                         Web::Controllers::Books::Index
                     GET, HEAD  /books                         Web::Controllers::Books::Index
                     GET, HEAD  /books                         Web::Controllers::Books::Index

@davydovanton It's way better. It will be probably appear like this instead:
                Name Method     Path                           Action

                     GET, HEAD  /admin/users                   Admin::Controllers::Users::Index
                     GET, HEAD  /admin/users                   Admin::Controllers::Users::Index

         --------------------------------------------------------------------------------------

                Name Method     Path                           Action

                     GET, HEAD  /books                         Web::Controllers::Books::Index
                     GET, HEAD  /books                         Web::Controllers::Books::Index
                     GET, HEAD  /books                         Web::Controllers::Books::Index

         --------------------------------------------------------------------------------------

The last router in a full stack project doesn't know that it's the last one to be inspected, so the last line will probably be there. But I don't mind.

nice, I'm pleased that we have agreed :)
I'll do it today.

@davydovanton thanks ;)

Fixed by #83