nokogiri 1.9.1

Hi guys, it's the first time I'm opening an issue on GitHub so I hope I'm doing it correctly.
I was using nokogiri version 1.8.5 without problems. Now I'm having trouble to install nokogiri in my gems since the version 1.9.1 was released.
I tried to create a new app "rails new my_app" and the following message showed up for me:
Gem::Ext::BuildError: ERROR: Failed to build gem native extension.

current directory: /home/kandy/.rvm/gems/ruby-2.5.3/gems/nokogiri-1.9.1/ext/nokogiri
home/kandy/.rvm/rubies/ruby-2.5.3/bin/ruby -r ./siteconf20181225-4018-4uuuhq.rb extconf.rb
undefined method `success?` for nil:NilClass

Gem files will remain installed in /home/kandy/.rvm/gems/ruby-2.5.3/gems/nokogiri-1.9.1 for inspection.
Results logged to /home/kandy/.rvm/gems/ruby-2.5.3/extensions/x86_64-linux/2.5.0/nokogiri-1.9.1/gem_make.out

An error occurred while installing nokogiri (1.9.1), and Bundler cannot continue.
Make sure that `gem install nokogiri -v '1.9.1' --source 'https://rubygems.org/'` succeeds before bundling.

In Gemfile:
  rails was resolved to 5.2.2, which depends on
    actioncable was resolved to 5.2.2, which depends on
      actionpack was resolved to 5.2.2, which depends on
        actionview was resolved to 5.2.2, which depends on
          rails-dom-testing was resolved to 2.0.3, which depends on
            nokogiri

Then following the mentioned tip I executed gem install nokogiri -v '1.9.1' --source 'https://rubygems.org/' which didn't work again.
For now what I'm doing is setting in Gemfile gem 'nokogiri', '~> 1.8.5' to keep working on my apps.
Debian
Ruby on Rails 5.2.2
Ruby 2.5.3
Gem 2.7.8
Thank you very much.

Hi, thank you for asking this question. Unfortunately when you filed this report you ignored the "new issue" template designed to capture the information we need to help you.
Please take a look at https://github.com/sparklemotion/nokogiri/blob/master/.github/ISSUE_TEMPLATE.md and answer those questions and someone will try to help. Thank you!

I'm sorry, I thought the questions were optional. Follow the answers.
Have you tried following the installation tutorial?
Yes
What is the output of gem install?
Building native extensions. This could take a while...
/home/kandy/.rvm/rubies/ruby-2.5.3/lib/ruby/site_ruby/2.5.0/rubygems/ext/builder.rb:76: warning: Insecure world writable dir /home/kandy/.rvm/gems/ruby-2.5.3/bin in PATH, mode 040777
^CERROR: Error installing nokogiri:
        ERROR: Failed to build gem native extension.

        current directory: /home/kandy/.rvm/gems/ruby-2.5.3/gems/nokogiri-1.9.1/ext/nokogiri
/home/kandy/.rvm/rubies/ruby-2.5.3/bin/ruby -r ./siteconf20181226-1578-1kcecs3.rb extconf.rb
undefined method `success?' for nil:NilClass

Gem files will remain installed in /home/kandy/.rvm/gems/ruby-2.5.3/gems/nokogiri-1.9.1 for inspection.
Results logged to /home/kandy/.rvm/gems/ruby-2.5.3/extensions/x86_64-linux/2.5.0/nokogiri-1.9.1/gem_make.out

What are the contents of the mkmf.log file?
This file wasn't generated. I looked for it using find ~/.rvm -name mkmf.log, but I didn't find anything in nokogiri-1.9.1
What operating system are you using?
Debian
Thank you very much.


Source Plugin for Kafka Connect

Explore options for building this - particularly for Aura.
Exposed TransactionEventHandlers not yet available- may have to be polling approach of some sort

Hi
we are looking exactly for this source connector for the neo4j.
may i know when this functionality will release?

@vishnu2497 we are actively discussing this as a team, how/when to prioritize it.  It hasn't been built yet.  You could really help us by describing your use case & desire for this feature.  Which systems do you want to produce data out to?  In which format?  And so on.

Actually we are looking similar thing like Kafka Connectors to pull the
data from neo4j and store into Kafka topic.
We can have a control while using connector kind of stuff but that is not
achievable in current neo4j streams
We need the following functionality
1)Use connector to pull data from neo4j
2)That connect has to be configurable at any time
3)Able to capture the CDC (CHANGE DATA CAPTURE)
4)Able to use query mode also to get the data based on query..
5)Able to pause/resume the connectors.
In a short point Neo4j sink connector for kafka is available already like
that source connector is there means it will be great.
On Fri, Dec 11, 2020, 21:26 David Allen<EMAIL_ADDRESS>wrote:

@vishnu2497 https://github.com/vishnu2497 we are actively discussing
this as a team, how/when to prioritize it. It hasn't been built yet. You
could really help us by describing your use case & desire for this feature.
Which systems do you want to produce data out to? In which format? And so
on.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/neo4j-contrib/neo4j-streams/issues/375#issuecomment-743275537,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHG3DYODFYCQYX2J2AKTKVTSUI6L3ANCNFSM4T44DTUQ
.

This is already available, refer to https://neo4j.com/docs/kafka for more information.


Configuring authentication steps in the Console app breaks authentication

Describe the issue:
Configuring authentication steps using the Console app renders authenticating impossible.
How to reproduce:

Create an app through the Console.
Go to the Sign-on Method tab and add an additional step or add another authenticator to the existing tab and update.
Try signing in using the created app.
The SSO page throws an error.

Move on to the management console and check out the adaptive script.

Updating the authentication steps through the console messes up the adaptive script.

Could recreate the issues. The issue is related to script generation.
 "var onLoginRequest = function(context) {\n    executeStep(0);\n};\n"
The same flow works when using the Management console. Still there is an issue in the UI. It shows null values as follows.


Revisit animation for MD sidemenu

Short description of the problem:
Currently our sidemenu feels much faster than the native sidemenu on Android. It opens a good bit faster than the native sidemenu and closes a little faster than the native sidemenu.
What behavior are you expecting?
Our sidemenu to feel equivalent to the native sidemenu on an Ionic 2 app.
Steps to reproduce:

open the conference app on an android device and open / close the sidemenu
open the Google Play app on an android device and open / close the sidemenu
notice the difference

Which Ionic Version? 2.x

I think this is already fixed, please @jgw96 reopen it if you feel this issues is not fixed completely.


File Version pattern checking

We want to implement version checking in a similar way OA Works does.
OA Works uses this spreadsheet of regex patterns to help them make a determination if a file is an accepted version (post-print) or published version.  They apply these patterns to check the first 500 words of a document and the filename.  The spreadsheet indicates what pattern to look for and what version it indicates.  The spreadsheet can be found here: https://docs.google.com/spreadsheets/d/10DNDmOG19shNnuw6cwtCpK-sBnexRCCtD4WnxJx_DPQ/edit#gid=0 .
Their code basically looks for the patterns and adds a point if a published version pattern is found and removes a point if an accepted manuscript pattern is found.  If the end score is greater than 0, it is a published version, if it is less than 0 it is an accepted manuscript.  When talking with someone from OA Works it sounded like they weighed published version patterns a little more heavily.  We'll have to take a look at some of these patterns and see if that's what we want to do.  OA Work's code can be found here: https://github.com/oaworks/api/blob/master/worker/src/deposit.coffee#L260-L297 .
OA Works indicated that this processing takes 15-30 seconds, so we may want to add a loading animation to the submit files button so users know it is processing.

Also, if we can get this working with the current metadata checks, that would be great.  There may be some parts we want to change or remove though.

This will be used in the ScholarSphere upload process and the Activity Insight upload process, so it should be usable in both.


Upgrade to Debian 10 Buster

:exclamation:  Current sticking points

[ ]  Zeyple : pygpgme is no longer supported by upstream for years and has a successor (python-gpg), python-gpgme package is no longer available with Buster. Zeyple needs to be updated.

[X] Zeyple has been temporarily disabled in mailserver 1.1-latest. Open issue : https://github.com/infertux/zeyple/issues/60

:information_source: Changes

[X] Dovecot https://wiki2.dovecot.org/Upgrading/2.3

[X] ssl_protocols has been replaced by ssl_min_protocol.
[X] Since 2.3.3+ DH parameter usage is optional and can be omitted. Amend ciphers to disallow non-ECC based DH algorithms, new ssl_cipher_list = EECDH+AES:EDH+AES+aRSA:!DH
[X] ssl_dh_parameters_length removed.
[X] ssl-parameters.dat file is now obsolete and has been removed.
[X] Database password can now contain a '#' character.

[X] Postfix Postfix 3.4, Postfix 3.3, Postfix 3.2

[X] Since Postfix 3.3, the master daemon can be started in the foreground ! Finally :tada: :cake:

[X] clamav-unofficial-sigs

[X] Yara rules are broken with clamav ≥ 0.100. Yara rules are now disabled in default configuration. Open issue : link

:warning: Warnings

[X] postfix/postfix-script: warning: symlink leaves directory: /etc/postfix/./makedefs.out. Open issue : link (This warning is harmless)

:beetle:  Bugs

No bug found yet, only zeyple unit tests fail.

Softwares version

Software
Stretch
Buster

Postfix
3.1.12
3.4.5

Dovecot
2.2.27
2.3.4

Fetchmail
6.3.26
6.4.0

ClamAV
0.100.3
0.101.2

Unbound
1.6.0
1.9.0

Rsyslog
8.24.0
8.1901.0

Upgrade state : Complete (testing)

For all volunteers, you can begin to test this new version unless if you are currently using Zeyple. Your feedback will be appreciated.

Shouldn't we update Python from Python 2 to Python 3 as well? I think Debian 10 support would be a great place to do it. Are there any parts that still depend on Python 2?

DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 won't be maintained after that date. A future version of pip will drop support for Python 2.7. More details about Python 2 support in pip, can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support

@neuffer done.

Thanks!

Everything is ok after upgrade on my two servers. What if we add zeyple.py into rootfs, can we then use it?

@dguttierrez nope because zeyple.py use pygpgme and the maintainers of Debian Project dropped the old python-gpgme  with pygpgme module inside.
You can install pygpgme with pip directly, it should works, but this package was last released in 2012 and I don't want to use an unmaintained GPG module for security reason.

I'm seeing this on startup.
mailserver      | 2019-08-12T23:54:19.721747+00:00 mail dovecot: master: Fatal: service(dict) User doesn't exist: vmail (See service dict { unix_listener /var/run/dovecot/dict { user } } setting)
mailserver      | 2019-08-12T23:54:19.739876+00:00 mail root: s6-supervise : spawning unbound process
mailserver      | [1565654059] unbound[1184:0] warning: did not exit gracefully last time (1157)
mailserver      | 2019-08-12T23:54:19.755257+00:00 mail root: s6-supervise : spawning dovecot process
mailserver      | 2019-08-12T23:54:19.764876+00:00 mail root: s6-supervise : spawning rspamd process
mailserver      | 2019-08-12T23:54:19.782181+00:00 mail root: s6-supervise : spawning freshclam process
mailserver      | ./run: line 13: /var/run/clamav/freshclam.pid: No such file or directory
mailserver      | 2019-08-12 23:54:19 #1198(main) <fb8165>; main; detect_priv: user specified does not exists (Success), aborting
mailserver      | 2019-08-12T23:54:19.808271+00:00 mail root: s6-supervise : virus database downloaded, spawning clamd process
mailserver      | ./run: line 4: /var/run/clamav/clamd.pid: No such file or directory

Temporarily downgraded to mail-server:1.1-stable for the above problem. Will look into it. Would appreciate any ideas, @hardware

In mailserver container, from the prior images, I see:
$ docker-compose exec mailserver  bash
root@mail:/# grep vmail /etc/passwd
vmail:x:1024:1024::/var/mail:

but in mailserver:1.1-latest, there is no vmail user.

Upload your entire logs please.

mailserver.log

Upload your entire logs please.

mailserver.log
@hardware

Ok, got it. So the issue is : you've actived Zeyple and the mail server should have stopped right after this warning :
[WARNING] Zeyple support has been temporarily disabled in the master branch following the Debian 10 update. Please, use the stable docker tag (1.1-stable) until the issue fixed. More information here : https://github.com/hardware/mailserver/issues/393

But my exit procedure doesn't works as expected, I forgot about the changes made by @Matchlighter.
Disable Zeyple or stay with 1.1-stable.

I actually don't need Zeyple. I can disable it. Thank you.

Can I use this version? I can install one of my mail servers.

So far so good, you can use it.

Zeyple' author wants to rewrite his program starting from scratch with Golang : https://github.com/infertux/zeyple/issues/52#issuecomment-431650033
As a temporary solution for Buster, I can install python-gpgme deb package from debian.pkgs.org. This is not ideal but why not.


Integration of lsb2rcconf to OpenRC

Hello.
I just want to know, what do you think about integration of lsb2rcconf to OpenRC?

some more background for folks unfamiliar with this stuff:
https://wiki.debian.org/LSBInitScripts
i'm inclined to pass.  LSB adoption seems to be too low to bother.


Input ndarrays or bytes instead of files.

Hi,
Has anyone tried modifying the code so that it supports numpy arrays or images bytes for processing instead of the current approach of .png files.
I tried looking into it but I do not have the necessary experience in cpp to modify the code to my will.

why not https://github.com/media2x/rife-ncnn-vulkan-python?

Seems to only support up to Python 3.10, I've tried building it for Python 3.11 but with no success. I am sure it's a me issue but I just couldn't motivate myself to look too deep into it. + It would be nice to have newer version of Rife but I am sure that's as easy as adding the wanted models folders after reading quickly through it.

This is so wired, because I am currently using it with the exactly python 3.11. How about raise an issue on my project with the error logs attached so that I can assist with addressing the problems?

Sure will do later today.


Add supported features matrix

For each model. Like this.

There is https://github.com/YosysHQ/yosys/wiki/FPGA-family-feature-matrix/ and there is no difference per model. Supported models are listed in the readme. Although I've just been informed that Tang Nano 9k is missing, which I'll fix.

Hard core

I mean Cortex-M hard core not listed there


Define cREAL bucket size

I think a good approach for this would be to emulate the bucket sizes we had for cUSD at time of launching it for the first time. The reasoning would be that this is the first time Celo creates a "local" stablecoin and we need to start small, although it has significant more liquidity than it had back then already with only a CELO/BTC -> BTC/BRL implicit pair.


[BUG] Simplefog still allows players to see doors on the hidden portion of map

Module Version: v0.3.4
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Enable Simplefog for scene with doors
See error

Expected behavior
The door icons in the hidden area should not be displayed to the players
Screenshots
Simplefog layer in grey, players can see the two door icons

Browser:
Chrome
Foundry Version:
11.350
Game System:
Savage Worlds Adventure Edition 3.0.6
Additional context
None

Unfortunately, this is not something that can be fixed.  Doors are on the "interface" layer which is above the simplefog layer, and lowering it would lower many other necessary controls.

Ah ha ... bummer  :-(
Thanks for response


Updated requirements to remove seqeval version

It seems that ExplainaBoard works with the most recent version of seqeval, so just removed the version specification.
Fixes https://github.com/neulab/ExplainaBoard/issues/12
Also makes a few small additions to .gitignore.

Closing this in favor of a follow-up PR that will build upon the new naming of interpret_eval -> explainaboard


add torch.script tests to convert_image_dtype

Addresses https://github.com/pytorch/vision/pull/2078#issuecomment-642783406

Test failure seems related. @fmassa Could you have a look if I misunderstood the usage of torch.jit.script?

I think the test failures are because torch.jit.script expects a function, but you are passing the output of the function (which is a tensor)

I think the test failures are because torch.jit.script expects a function, but you are passing the output of the function (which is a tensor)

Oh dang, that should have been obvious. Sorry, I was tired when I wrote it.

I think test failures might be either due to a breakage in PyTorch (cc @eellison does it ring a bell for the Faster R-CNN and Mask R-CNN tests?) or you need to rebase on top of master (which I think it's the case, just confirming)

Will try the rebase.
I've seen errors such as this:
RuntimeError:
Tried to access nonexistent attribute or method 'is_floating_point' of type 'int'.:

I don't think this will be fixed by a rebase. Is it possible that I'm not allowed to use that attribute in torch.script?

@pmeier I see, it's an issue with torchscript (it currently doesn't have dtype mapped to torchscript internally).
For now, the workaround would probably be to do
img.dtype in [torch.float16, torch.float32, torch.float64]

until torchscript supports it.
But then, we will have another issue afterwards, which is that torchscript doesn't support finfo and iinfo
I think for now it's better to wait until torchscript adds better support for dtype, so let's hold on with this PR for now. :-/
cc @eellison

I've pushed the last commit before I saw your comment. You can ignore it for noe and I will revert it when we move forward with this PR.

Superseded by #2485.


feat(pm_auth): add payment method auth flows

Type of Change

[ ] Bugfix
[x] New feature
[ ] Enhancement
[ ] Refactoring
[ ] Dependency updates
[ ] Documentation
[ ] CI/CD

Description

This PR includes 2 main flows in payment method auth: PmAuthLinkTokenCreate and PmAuthExchangeToken
Additional Changes

[ ] This PR modifies the API contract
[ ] This PR modifies the database schema
[ ] This PR modifies application configuration/environment variables

Motivation and Context

How did you test it?

Checklist

[x] I formatted the code cargo +nightly fmt --all
[x] I addressed lints thrown by cargo clippy
[x] I reviewed the submitted code
[ ] I added unit tests for my changes where possible
[ ] I added a CHANGELOG entry if applicable

Not required.


[JetNews] Fix pull-to-refresh indicator

It's just weird.

Should be better now, using Accompanist default swipe refresh component.


Fixed alignment of annotation boxes.

This patch addresses the misaligned boxes for in-manifest annotations.
See: Issue #918

Coverage decreased (-4.9%) to 35.502% when pulling ef3f61835b4b0fad7f7ca23db31bfc406dcfb70c on dicksonlaw583:annotation_box_fix into 6cf7f91b97e2afe943b898aa04391bba46e12a22 on IIIF:release2.1.

Coverage increased (+0.09%) to 40.469% when pulling 91845789b5b39c9003c072cc7c0634a45e3f5d4c on dicksonlaw583:annotation_box_fix into 6cf7f91b97e2afe943b898aa04391bba46e12a22 on IIIF:release2.1.

Thanks @dicksonlaw583. Merging.


[Type checker] Fix multi-file crasher for property wrapper backing storage

Fixes rdar://problem/51810057

@swift-ci please smoke test and merge

@swift-ci please smoke test and merge

Dropped in favor of https://github.com/apple/swift/pull/25743


Support for importing non-area relations as MultiLineString

It can be convenient to be able to import non-area relations as MultiLineString geometries into linestring table.
This PR adds this capability. Only relations specified in relation_types will be imported. No relations are imported by default.

Hi. Thanks for your PR.
The timing is a bit unfortunate as I just made a larger refactoring. Parsing and some basic stuff is moved into a separate library (https://github.com/omniscale/go-osm). The changes are the go-osm branch (https://github.com/omniscale/imposm3/tree/go-osm).
Can you base your patch on this branch and see if you need to make any changes?
For tests:  It's great that you included a new system test. But can your use short and commented dummy OSM files like  https://github.com/omniscale/imposm3/blob/go-osm/test/route_relation.osm and https://github.com/omniscale/imposm3/blob/go-osm/test/route_relation.osc

Hi @olt. I've rebased it on top of go-osm branch. There were just minor conflicts. The OSM files should be more comprehensible now.

@olt Any chance of this being merged? Would be super-useful for me.

I've rebased it on top of master and changed the base branch to master. Surprisingly, there was no conflict after those two years.

@olt I am in the need for that PR. Any reason why it is left unmerged?

Sorry for the long silence.
Is my understanding correct, that this change is backward incompatible with older imports? (It will try to import multipolygons into linestring tables?)
Can someone who used this patch comment on that?


audiovisual-0.0 does not compile

Citing from http://hydra.cryp.to/build/657629/log/raw:
src/Data/Graphics/Sight.hs:89:53: Not in scope: ‘eye4'
src/Data/Graphics/Sight.hs:126:88: Not in scope: ‘eye4’

Please wait a bit more for next release.

My life would be easier if you'd keep this issue open until that release is available from Hackage. Now, I have to remember to regularly check for that update and to re-enable the build in NixOS once it appears.

Will you make that new release?

Sorry, perhaps I'm going to deprecate this package.

What about the packages that depend on this, i.e. call?


Bar chart does not render all bars in firefox when using a scrollable div

Expected behavior
Rendering all the bars in the bar plot:

Current behavior
Bars are not rendered after bar no. 682:

Reproducible sample
https://codepen.io/FilomenoSanchez/pen/gOzErZW
Optional extra steps/info to reproduce
This is only an issue when the following conditions are met:

Bar chart inside a large scrollable div
Using Firefox

Something which I find interesting is that when hovering over the "invisible" bars the tooltip is displayed...
Context
I need to plot a barplot with over a thousand bars, each having a value between 0 and 1. Due to the large amount of data, the only way this data can be displayed in a meaningful way is by fitting the plot inside a scrollable div so that the bars can be bigger and the user scrolls along the horizontal axis. As mentioned, this is not an issue when loading the page in Chrome or Safari but some users may want to use the app in Firefox.
chart.js version
v3.9.1
Browser name and version
Firefox 105
Link to your project
No response

Duplicate of #4909, #8309, #10777
Setting borderwidth to 0 and clip to false will resolve the issue

Yes that solves it, thanks!

Out of curiosity @LeeLenaleee, is there any way the bar borders could be kept (i.e. borderwidth above 0)?

Only thing I can think off is creating a custom plugin and drawing it yourself

Thanks for the suggestion @LeeLenaleee. I got something working now with a plugin: https://codepen.io/FilomenoSanchez/pen/VwxNZJe . However I have found another issue: because I am using the plugin beforeDraw the tooltip gets obscured by the bar borders:

I have tried using afterDraw instead but then the boundary between the stacked bars is not as visible:

Do you have any tips? If not that's fine, thanks anyway for all the help so far!

I think I just figured out that instead of afterDraw it should have been afterDatasetsDraw... Thanks anyway!


[COMMUNITY][RFC] Transition to Apache

Thanks to everyone's participation, TVM Joins Apache as an incubator project. This is a public thread to list some of the things we should know about the transition to Apache and possible discussions.
What to Anticipate
Here are transition steps what will happen next

PMC move to<EMAIL_ADDRESS>(already done)
PMC invite all existing committers to apache and ask committers to sign iCLA(we will follow up in the next few weeks)
Transition the dmlc/tvm repo to apache/incubator-tvm

Double check apache/tvm-committers to make sure correct membership
We will send out notice and RFC beforehand and everything should work smoothly.

Community
Everything should stay the same if there are any further updates we will still resolve publically as per Apache way.  We will continue bringing in new people following the community guideline. There are some delays recently due to PMC list transition, and we will resume now that the list transition is done:)
Development
One of the Apache's requirements of development is the Public Archive Principle. This is a way to ensure everyone can participate at any time.
<EMAIL_ADDRESS>is now the archive and development mail-list for TVM. You can subscribe by sending an email to<EMAIL_ADDRESS>The community is using the github issue for technical RFC and a discourse forum for development discussions. We would like to continue doing so while obeying the principle that "everything happens (also) happen in dev@".
We have set up the automatic forwarding so that any thread in github that has the prefix([VOTE], [COMMUNITY], [RFC], [DEV]) will be automatically mirrored to the dev@, we also mirror the thread under the development categories to<EMAIL_ADDRESS>This way, the community can still enjoy the modern infrastructure from github and discourse for development while under the Apache framework. Please be mindful about the Public Archive Principle so that we make sure all important decisions appears in<EMAIL_ADDRESS>This is a short summary of what we need to know. One thing that worth discussing is whether we want to continue to use github for VOTE, given that issue is mirrored to dev@, it makes the vote through github also possible, we would like to hear the community's opinion on this. Please also feel free to ask questions and share other thoughts.

https://github.com/dmlc/tvm/pull/2906


Add document timeline example

Merged, but compare with the datatracker page for RFC 8280

Fixed in PR #51


Use correct versioning for alpha release

There was a mistake in the version bumping replacement (commit here), so -ccs was removed from the version when bumping for 6.0.x-alpha1, resulting in packaging builds to fail. This commit fixes the version in kafka to include ccs in the versioning.

Please get someone from the Kafka team to approve the change.


Create .pullapprove.yml

@Shredder121 Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.


hcxdumptool  not filter right mac address

heres  what my my capture looks like and the first two captures are from my  router the second two are not is this normal? anyway when i turn the  pmkid into hash and try to crack it.. hashcat gives me password from  wrong access point.
hcxdumptool -o hashingit -i wlan0 --filterlist=tvfp2filer.txt --filtermode=2 --enable_status=1
the mac address that is suppose to filter is:  009fa9073914
the filter works seems like for a short period then starts grabbing from all access points in area
still havent been able to capture pmkid from 009fa9073914
the pmkid captureed belongs to 2c56dc54e238 using awus036nha. i have a awus036nh on the way to my house for testing.
capturing (stop with ctrl+c)
INTERFACE:...............: wlan0
FILTERLIST...............: 1 entries
MAC CLIENT...............: fcc233dadfba
MAC ACCESS POINT.........: b025aa99a8f8 (incremented on every new client) EAPOL TIMEOUT............: 150000
REPLAYCOUNT..............: 63156
ANONCE...................: 1f963f900448da8c1182e40ba288928877f40543759cd5e6425deb3548407868 [16:26:17 - 001] 009fa9073914 -> 5c93a20b3897 [FOUND AUTHORIZED HANDSHAKE, EAPOL TIMEOUT 2516]
[16:40:15 - 001] 009fa9073914 -> ccfb65942f7e [FOUND AUTHORIZED HANDSHAKE, EAPOL TIMEOUT 2651] [17:19:39 - 001] b44bd20fd6ba -> 5c8fe0bf2984 [EAPOL 4/4 - M4 RETRY ATTACK] [17:39:53 - 011] 2c56dc54e238 -> 5ccf7f48a404 [FOUND PMKID] INFO: cha=11, rx=145350, rx(dropped)=3145, tx=2453, powned=3, err=0^C terminated...
the filter is working somewhat atleast cuz i tried without filter and got slammed with tons more

https://github.com/ZerBea/hcxdumptool/commit/f57338faca30bec31bee509cf99104a471286816#diff-56f0554ece9939c694f65b93a8468553R4435

so am i doing it wrong by running: echo "009FA9073914">filter.txt
then running hcxdumptool -o hash -i wlan0mon --filterlist=filter.txt --filtermode=2 --enable_status 3

not sure what that strasharo but im trying to capture traffic from the ap in the filter list

hcxpcaptool will convert handshakes and PMKIDs to hccapx and/or 16800 hashfiles.
Now you must delete the unwanted PMKIDs from your 16800 hashfiles.
Or you can retrieve the wanted handshakes from your hccapx file, by wlanhcx2ssid.

009fa9073914 is your filter list entry.
You got 2 handshakes from this ssid:
[16:26:17 - 001] 009fa9073914 -> 5c93a20b3897 [FOUND AUTHORIZED HANDSHAKE, EAPOL TIMEOUT 2516]
[16:40:15 - 001] 009fa9073914 -> ccfb65942f7e [FOUND AUTHORIZED HANDSHAKE, EAPOL TIMEOUT 2651]
But the AP doesn't transmit a PMKID!!!!

How much time does it takes to fetch the PMKID because I tried a lot but could not get the PMKID even after waiting for 30 minutes or more.

If AP has enabled PMKID less than a minute running this options:
hcxdumptool -i INTERACE -o output.pcapng -t 5 --enable_status=1
To check if AP is in range run:
hcxdumptool -i INTERACE --do_rcascan
Driver of your interface must support monitor mode and packet injection.

If AP is not in range what should I do?
On Sun, 14 Apr 2019, 1:38 am ZerBea<EMAIL_ADDRESS>wrote:

If AP has enabled PMKID less than a minute running this options:
hcxdumptool -i INTERACE -o output.pcapng -t 5 --enable_status=1
To check if AP is in range run:
hcxdumptool -i INTERACE --do_rcascan
Driver of your interface must support monitor mode and packet injection.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ZerBea/hcxdumptool/issues/37#issuecomment-482876835,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AvTJ4nKig2P-GP6ldCi_zIiOZFHOv_jcks5vgjlEgaJpZM4YRJly
.

To answer this question we need an information about your equipment (WLAN device), because:

case: device doesn't support full packet injection (get a supported device)
case: AP is far away (you need a better antenna or get closer to the AP)
case: hardware is broken (antenna connector)

If you receive PMKIDs from other APs, but not from your target, target hasn't active this feature
I assume there are now warnings if you start hcxdumptool. In that case please add output of
$ hcxdumptool -I
$ lsusb if you have an USB device)
or
$ lspci if you have an internal device)
BTW:
Not all drivers support monitor mode.
Not all drivers that support monitor mode, support packet injection, too. Intel drivers are well known for this.

That mean using only laptop without wireless adapter cannot do PMKID
cracking? What wireless adapter would you recommend me for PMKID cracking
to buy which would support both monitor mode and packet injection?
On Sun, 14 Apr 2019, 1:11 pm ZerBea<EMAIL_ADDRESS>wrote:

To answer this question we need an information about your equipment (WLAN
device), because:

case: device doesn't support full packet injection (get a supported
device)
case: AP is far away (you need a better antenna or get closer to
the AP)
case: hardware is broken (antenna connector)

If you receive PMKIDs from other APs, but not from your target, target
hasn't active this feature
I assume there are now warnings if you start hcxdumptool. In that case
please add output of
$ hcxdumptool -I
$ lsusb if you have an USB device)
or
$ lspci if you have an internal device)
BTW:
Not all drivers support monitor mode.
Not all drivers that support monitor mode, support packet injection, too.
Intel drivers are well known for this.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ZerBea/hcxdumptool/issues/37#issuecomment-482927541,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AvTJ4nTN-rgORCy4iWpMR-omcJKEbl8aks5vgtuZgaJpZM4YRJly
.

As I wrote, it depends on several factors.  If the AP doesn't run PMKID features, this attack vector will not work.
But you can improve your equipment:
USB WLAN device with external antenna connector and a high gain antenna
Driver must support monitor mode and full packet injection. Read more here:
https://wikidevi.com
This drivers are known as working out ouf the box:
kernel driver mt7601ut:
ID 7392:7710 Edimax Technology Co., Ltd
ID 148f:7601 Ralink Technology, Corp. MT7601U Wireless Adapter
kernel driver rt2800usb:
ID 148f:3070 Ralink Technology, Corp. RT2870/RT3070 Wireless Adapter
ID 148f:5370 Ralink Technology, Corp. RT5370 Wireless Adapter
They are part of the kernel. Do not buy a device that require to install a third party driver!
I do not recommend a special device by name, because VENDORs very often change the chipset, So a device V1 will work, while V2 dosn't work.

Can you recommend me a wireless adapter V1 with vendor name from amazon
please. With that how can we check out whether our target mac's AP has
PMKID enabled or not from our machine?
On Mon, 15 Apr 2019, 1:51 am ZerBea<EMAIL_ADDRESS>wrote:

As I wrote, it depends on several factors. If the AP doesn't run PMKID
features, this attack vector will not work.
But you can improve your equipment:
USB WLAN device with external antenna connector and a high gain antenna
Driver must support monitor mode and full packet injection. Read more here:
https://wikidevi.com
This drivers are known as working out ouf the box:
kernel driver mt7601ut:
ID 7392:7710 Edimax Technology Co., Ltd
ID 148f:7601 Ralink Technology, Corp. MT7601U Wireless Adapter
kernel driver rt2800usb:
ID 148f:3070 Ralink Technology, Corp. RT2870/RT3070 Wireless Adapter
ID 148f:5370 Ralink Technology, Corp. RT5370 Wireless Adapter
They are part of the kernel. Do not buy a device that require to install a
third party driver!
I do not recommend a special device by name, because VENDORs very often
change the chipset, So a device V1 will work, while V2 dosn't work.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ZerBea/hcxdumptool/issues/37#issuecomment-483055000,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AvTJ4s2sBvCUcdfxhwGWdt3J09I_ppwuks5vg43bgaJpZM4YRJly
.

If you run
$ hcxdumptool -i INTERFACE --do_rcascan
and you get a message AP IN RANGE, you know, that the AP receive our request and respond to it.
if you run
$ hcxdumptool -i INTERFACE --enable_status=1
and you receive a PMKID, you know that the AP is vulnerable against this attack.
My favorite adapters are:
EDIMAX EW-7711UAN (ID 7392:7710 Edimax Technology Co., Ltd)
ALLNET ALLNET ALL-WA0150N (ID 148f:7601 Ralink Technology, Corp. MT7601U Wireless Adapter)
TENDA W311U+ (ID 148f:3070 Ralink Technology, Corp. RT2870/RT3070 Wireless Adapter)

Thank you for your wonderful responses clearing my doubts.
On Tue, 16 Apr 2019, 3:22 am ZerBea<EMAIL_ADDRESS>wrote:

If you run
$ hcxdumptool -i INTERFACE --do_rcascan
and you get a message AP IN RANGE, you know, that the AP receive our
request and respond to it.
if you run
$ hcxdumptool -i INTERFACE --enable_status=1
and you receive a PMKID, you know that the AP is vulnerable against this
attack.
My favorite adapters are:
EDIMAX EW-7711UAN (ID 7392:7710 Edimax Technology Co., Ltd)
ALLNET ALLNET ALL-WA0150N (ID 148f:7601 Ralink Technology, Corp. MT7601U
Wireless Adapter)
TENDA W311U+ (ID 148f:3070 Ralink Technology, Corp. RT2870/RT3070 Wireless
Adapter)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ZerBea/hcxdumptool/issues/37#issuecomment-483432461,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AvTJ4gu8FK4BVigzwQFWMxUskw81de-Xks5vhPSDgaJpZM4YRJly
.

Updated hcxdumptool device wiki and README.md.
The listed devices are (still) working on latest kernel. They are not affected by xhci bug.

This is the only adapter available for shipment to India. Would it serve
the purpose?
On Tue, 16 Apr 2019, 12:18 pm ZerBea<EMAIL_ADDRESS>wrote:

Updated hcxdumptool device wiki and README.md.
The listed devices are (still) working on latest kernel. They are not
affected by xhci bug.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ZerBea/hcxdumptool/issues/37#issuecomment-483533332,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AvTJ4tnBHte8p00ToKj4nXsBg0ifP8aXks5vhXJLgaJpZM4YRJly
.

I found this adaptor, TP-Link TL-WN722N 150Mbps Wireless USB Adapter whose
Version is V1.X. Would it work for Monitor mode and packet injection?
On Tue, 23 Apr 2019, 2:42 pm red ghost<EMAIL_ADDRESS>wrote:

This is the only adapter available for shipment to India. Would it serve
the purpose?
On Tue, 16 Apr 2019, 12:18 pm ZerBea<EMAIL_ADDRESS>wrote:

Updated hcxdumptool device wiki and README.md.
The listed devices are (still) working on latest kernel. They are not
affected by xhci bug.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ZerBea/hcxdumptool/issues/37#issuecomment-483533332,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AvTJ4tnBHte8p00ToKj4nXsBg0ifP8aXks5vhXJLgaJpZM4YRJly
.

Yes, 1.x has Atheros chipset and works fine with hcxdumptool.

Unfortunately what I received wireless adapter is of version 3.0. Sir,
would version 3.0 support the minister mode and packet injections.
On Tue, 23 Apr 2019, 11:26 pm strasharo<EMAIL_ADDRESS>wrote:

Yes, 1.x has Atheros chipset and works fine with hcxdumptool.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ZerBea/hcxdumptool/issues/37#issuecomment-485909214,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AL2MTYWHENEVDKDAW6BXVBTPR5EU3ANCNFSM4GCETFZA
.

No. Only v1 of this device is working.
Manufacturers do change chipsets without changing model numbers. Sometimes they add (v)ersion or (rev)vision.

Panda Wireless PAU09 N600 Dual Band (2.4GHz and 5GHz) Wireless N USB
Adapter W/Dual 5dBi Antennas - Windows XP/Vista/7/8/8.1/10, Mint, Ubuntu,
openSUSE, Fedora, Centos, Kali Linux and Raspbian. Will this wireless
adapter support monitor mode and packets injection?
On Sat, 27 Apr 2019, 7:20 pm ZerBea<EMAIL_ADDRESS>wrote:

No. Only v1 of this device is working.
Manufacturers do change chipsets without changing model numbers. Sometimes
they add (v)ersion or (rev)vision.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ZerBea/hcxdumptool/issues/37#issuecomment-487287643,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AL2MTYTNRJSBKP67GMIJPDDPSRK2NANCNFSM4GCETFZA
.

That depends on the chipset. It looks like there are different versions.
https://www.wirelesshack.org/review-panda-wireless-pau09-n600-dual-band-wifi-dongle.html
https://www.phoronix.com/scan.php?page=article&item=panda-pau09-linux&num=1

Will Alfa AWUS036NHA support monitor mode and packet injection. I have
already bought one and tried but could not get the PMKID.
On Mon, 20 May 2019, 1:55 am ZerBea<EMAIL_ADDRESS>wrote:

That depends on the chipset. It looks like there are different versions.
https://www.wirelesshack.org/review-panda-wireless-pau09-n600-dual-band-wifi-dongle.html
https://www.phoronix.com/scan.php?page=article&item=panda-pau09-linux&num=1
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ZerBea/hcxdumptool/issues/37?email_source=notifications&email_token=AL2MTYWMMESVR4LHCTGYD3DPWGZVLA5CNFSM4GCETFZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVXJ4UQ#issuecomment-493788754,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AL2MTYUIWSXTTTRKBLFEN7DPWGZVLANCNFSM4GCETFZA
.

$ hcxdumptool -i interface --enable_status=1 -o capture.pcapng

To find out if AP's are in range:
$ hcxdumptool -i interface --do_rcascan

I have tried to crack my android phone's hotspot password by using PMKID
capture method but am not able to capture the PMKID. Will this method not
work in android hotspot password cracking?
On Fri, 24 May 2019, 6:58 pm ZerBea<EMAIL_ADDRESS>wrote:

To find out if AP's are in range:
$ hcxdumptool -i interface --do_rcascan
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ZerBea/hcxdumptool/issues/37?email_source=notifications&email_token=AL2MTYVLH3D7O63PJXKULQ3PW7UO5A5CNFSM4GCETFZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWFK6GA#issuecomment-495628056,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AL2MTYWVXEPV2UGEWLBWFHLPW7UO5ANCNFSM4GCETFZA
.

Not all access points use this method. On some access points this feature is activated by default - on others not, because it absolutely make no sense for a single hotspot (like your Android phone) to run roaming features.
https://mrncciew.com/2014/09/11/cwsp-pmk-caching-preauthentication/
https://documentation.meraki.com/MR/WiFi_Basics_and_Best_Practices/Pairwise_Master_Key_and_Opportunistic_Key_Caching_-_PMK_and_OKC

After getting the PMKID found, I have tried to crack it using hashcat but
comes with an error saying failed to get magic number from .pcapng . What
is it? Please help me
On Sat, 25 May 2019, 1:18 pm ZerBea<EMAIL_ADDRESS>wrote:

Not all access points use this method. On some access points this feature
is activated by default - on others not, because it absolutely make no
sense for a single hotspot (like your Android phone) to run roaming
features.
https://mrncciew.com/2014/09/11/cwsp-pmk-caching-preauthentication/
https://documentation.meraki.com/MR/WiFi_Basics_and_Best_Practices/Pairwise_Master_Key_and_Opportunistic_Key_Caching_-_PMK_and_OKC
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ZerBea/hcxdumptool/issues/37?email_source=notifications&email_token=AL2MTYQWOBUSG7PXAZ2GFQ3PXDVMZA5CNFSM4GCETFZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWHINXY#issuecomment-495879903,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AL2MTYVOCWHZEYNWZYFU3O3PXDVMZANCNFSM4GCETFZA
.

Which command lin did you use?
Correct is for older hashcat:
$ haxpcaptool -z pmkids.16800 capture.pcapng
or for latest hashcat git:
$ haxpcaptool -k pmkids.16800 capture.pcapng
If you get an error like "failed to get magic number", your pcapng file is destroyed.
Please attach that pcapng file, to see what went wrong

Would be grateful if sir would help me out with commands to bypass public
wifi login portal in Kali Linux using Alfa adapter.
On Mon, 27 May 2019, 8:04 pm ZerBea<EMAIL_ADDRESS>wrote:

Which command lin did you use?
Correct is for older hashcat:
$ haxpcaptool -z pmkids.16800 capture.pcapng
or for latest hashcat git:
$ haxpcaptool -k pmkids.16800 capture.pcapng
If you get an error like "failed to get magic number", your pcapng file is
destroyed.
Please attach that pcapng file, to see what went wrong
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ZerBea/hcxdumptool/issues/37?email_source=notifications&email_token=AL2MTYXCQV4TKEQDF66Z7DTPXPWNVA5CNFSM4GCETFZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWJ6QSQ#issuecomment-496232522,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AL2MTYVBKBN7OIMKWCD2OY3PXPWNVANCNFSM4GCETFZA
.

That is neither part of hcxdumptool, hcxtools, hashcat nor part of john. Also I do not use KALI Linux.
So you can't expect an answer here. I suggest you, to ask this question in KALI forum.


Various documentation improvements.

For example, mention the icon used for the drawer menu in the docs (this helps people writing unit tests); add DefaultAssetBundle sample code.

cc @gspencergoog

thanks for the review. will land on green.


Multiple reducers using the same action type constant

Maybe I missed this, but given the way this set up defines constants:
const INCREMENT = 'redux-example/counter/INCREMENT';
what happens, or how would you handle, a case where multiple reducers look for the same action type. A simple example is a todo app where there there is a stats component that displays a variety of statistics. Adding a todo (hypothetically a ADD_TODO) would want to trigger both a literal addition, and a recalculation of the stats, so it seems to me that both the todos and the stats reducer would listen for ADD_TODO. Would I define the constant in the file its closest tied to and export it for others? The goal here looks to be to compartmentalize var exposure so is it ok for one reducer to provide constants to others?

You could just export this const and then import it right into the other reducer(s). Use it into your switch statements as done with the other ones. Be careful to not forget to remove its imported ref when deleted from its source reducer.

@Doubl3 my biggest concern with that was that if the reducers aren't all in the same place, you'd have a ton of import statements cross referencing files all over the place.
Since the question though I've come up with a new strategy that's been working well. I export a reducer and all of it's associated files (constants, action types, selectors) as a single default which lets me import it as a 'bundle' into another file and then destruct the constants from there. If a bundle is only used by one Component, i keep it there directory wise. If its used by more than one, it goes to a top level directory where components have quick access to it.

I didn't exactly catch your pain. Thx for your explanations. Indeed, it's a good way to go.


Revert "Remove kvass"

Reverts space-wizards/space-station-14#15939
Considering this has pissed off the majority of the Russian community (who make up a sizable number of contributors), I don’t think “well I’ve never seen this in the game”, “sprite bad”, and “regional stuff is cringe” were valid reasons for removing this.

considering the brigading: haha no


TUX out leaves the terminal color in orange

When you run the script on an OS that isn't supported and it shows the TUX logo, it leaves the terminal color to orange instead of it its default color.
I have NO Idea what distro you are using but here is Tux.

fixed.


After configuring, WIFI AP still visible and accessible

I have flashed this firmware to a nodeMCU and did the initial configuration to connect it to my wifi network. OTGW data is now accessible over port 25238 (using openHab BTW). Only issue I have is that the NodeMCU is still showing as open access point, which could be a security breach for my wireless network (hacking into it by connecting via phone near my house one might find the network password).
Even better: a configuration page where one could set static IP and reconfigure wifi details afterwards.
Krgds
Cor

Once the device is connected to a WiFi network as a station, it switches off the OTGW-MCU network. I have no idea why you believe there is still an open access point. You must either be looking at a different network, or a list of saved networks.
Your suggestion to set a static IP and access the device that way to configure the WiFi details won't work. The device needs to be connected to a WiFi network to be able to access it. It doesn't matter whether the IP address is static, or obtained via DHCP.

Mmmm, well I have the same.  Although my nodemcu is connected to my wifi there still is an insecure AP active with the name ESP-5E3xxxxx. When I connect to that I can access the webpage of otgwmcu at <IP_ADDRESS> and I can see a living message log, so no cache.
I am on 0.7.

Can you indicate step by step how you arrived at that situation? Because when I follow the instructions on the web site with a blank esp8266, I get a working device, connected to my WiFi network and no open AP. The part that is most baffling is the SSID of the AP. If the firmware ever creates an AP, it sets it up with an SSID of OTGW-MCU.

I found the issue. Apparently if you don't take a blank esp8266 (NodeMCU v1.0 in my case) but one that was used in other projects previous wifi settings (can?) stay active.
Solved it by applying:
esptool.py --port /dev/ttyUSB0 erase_flash
first and then
esptool -cp /dev/ttyUSB0 -cd nodemcu -cb 921600 -cf otgwmcu-fw.bin -ca 0x300000 -cf otgwmcu-fs.bin
Now all issues are gone.
Thanks.

Sounds like https://github.com/tzapu/WiFiManager/issues/1220 could be related. Although I would have expected erase_flash to wipe the old mode/credentials.

Yes, this did the trick for me. Thanks. No more insecure AP visible or available.


Composer PSR-4 Deprecation warning

Hello,
I am rather new to submitting these issues. If I have made an error or missed something I am sorry. Please let me know so I can fix it.
Thank you in advance.
Issue Summary
I receive Deprecation Notice when pulling the package down with composer
Deprecation Notice: Class SendGrid\Mail\Substitution located in ./vendor/sendgrid/sendgrid/lib/mail/Substitution.php does not comply with psr-4 autoloading standard. It will not autoload anymore in Composer v1.11+. in phar:///usr/local/bin/composer/src/Composer/Autoload/ClassMapGenerator.php:185
Deprecation Notice: Class SendGrid\Mail\Bcc located in ./vendor/sendgrid/sendgrid/lib/mail/Bcc.php does not comply with psr-4 autoloading standard. It will not autoload anymore in Composer v1.11+. in phar:///usr/local/bin/composer/src/Composer/Autoload/ClassMapGenerator.php:185
Deprecation Notice: Class SendGrid\Mail\Mail located in ./vendor/sendgrid/sendgrid/lib/mail/Mail.php does not comply with psr-4 autoloading standard. It will not autoload anymore in Composer v1.11+. in phar:///usr/local/bin/composer/src/Composer/Autoload/ClassMapGenerator.php:185
Deprecation Notice: Class SendGrid\Mail\TypeException located in ./vendor/sendgrid/sendgrid/lib/mail/TypeException.php does not comply with psr-4 autoloading standard. It will not autoload anymore in Composer v1.11+. in phar:///usr/local/bin/composer/src/Composer/Autoload/ClassMapGenerator.php:185
Deprecation Notice: Class SendGrid\Mail\IpPoolName located in ./vendor/sendgrid/sendgrid/lib/mail/IpPoolName.php does not comply with psr-4 autoloading standard. It will not autoload anymore in Composer v1.11+. in phar:///usr/local/bin/composer/src/Composer/Autoload/ClassMapGenerator.php:185
Deprecation Notice: Class SendGrid\Mail\Category located in ./vendor/sendgrid/sendgrid/lib/mail/Category.php does not comply with psr-4 autoloading standard. It will not autoload anymore in Composer v1.11+. in phar:///usr/local/bin/composer/src/Composer/Autoload/ClassMapGenerator.php:185
Deprecation Notice: Class SendGrid\Mail\ReplyTo located in ./vendor/sendgrid/sendgrid/lib/mail/ReplyTo.php does not comply with psr-4 autoloading standard. It will not autoload anymore in Composer v1.11+. in phar:///usr/local/bin/composer/src/Composer/Autoload/ClassMapGenerator.php:185
Deprecation Notice: Class SendGrid\Mail\Header located in ./vendor/sendgrid/sendgrid/lib/mail/Header.php does not comply with psr-4 autoloading standard. It will not autoload anymore in Composer v1.11+. in phar:///usr/local/bin/composer/src/Composer/Autoload/ClassMapGenerator.php:185
Deprecation Notice: Class SendGrid\Mail\HtmlContent located in ./vendor/sendgrid/sendgrid/lib/mail/HtmlContent.php does not comply with psr-4 autoloading standard. It will not autoload anymore in Composer v1.11+. in phar:///usr/local/bin/composer/src/Composer/Autoload/ClassMapGenerator.php:185
Deprecation Notice: Class SendGrid\Mail\OpenTracking located in ./vendor/sendgrid/sendgrid/lib/mail/OpenTracking.php does not comply with psr-4 autoloading standard. It will not autoload anymore in Composer v1.11+. in phar:///usr/local/bin/composer/src/Composer/Autoload/ClassMapGenerator.php:185
Deprecation Notice: Class SendGrid\Mail\Asm located in ./vendor/sendgrid/sendgrid/lib/mail/Asm.php does not comply with psr-4 autoloading standard. It will not autoload anymore in Composer v1.11+. in phar:///usr/local/bin/composer/src/Composer/Autoload/ClassMapGenerator.php:185
Deprecation Notice: Class SendGrid\Mail\SpamCheck located in ./vendor/sendgrid/sendgrid/lib/mail/SpamCheck.php does not comply with psr-4 autoloading standard. It will not autoload anymore in Composer v1.11+. in phar:///usr/local/bin/composer/src/Composer/Autoload/ClassMapGenerator.php:185
Deprecation Notice: Class SendGrid\Mail\Content located in ./vendor/sendgrid/sendgrid/lib/mail/Content.php does not comply with psr-4 autoloading standard. It will not autoload anymore in Composer v1.11+. in phar:///usr/local/bin/composer/src/Composer/Autoload/ClassMapGenerator.php:185
Deprecation Notice: Class SendGrid\Mail\TrackingSettings located in ./vendor/sendgrid/sendgrid/lib/mail/TrackingSettings.php does not comply with psr-4 autoloading standard. It will not autoload anymore in Composer v1.11+. in phar:///usr/local/bin/composer/src/Composer/Autoload/ClassMapGenerator.php:185
Deprecation Notice: Class SendGrid\Mail\Personalization located in ./vendor/sendgrid/sendgrid/lib/mail/Personalization.php does not comply with psr-4 autoloading standard. It will not autoload anymore in Composer v1.11+. in phar:///usr/local/bin/composer/src/Composer/Autoload/ClassMapGenerator.php:185
Deprecation Notice: Class SendGrid\Mail\ClickTracking located in ./vendor/sendgrid/sendgrid/lib/mail/ClickTracking.php does not comply with psr-4 autoloading standard. It will not autoload anymore in Composer v1.11+. in phar:///usr/local/bin/composer/src/Composer/Autoload/ClassMapGenerator.php:185
Deprecation Notice: Class SendGrid\Mail\BypassListManagement located in ./vendor/sendgrid/sendgrid/lib/mail/BypassListManagement.php does not comply with psr-4 autoloading standard. It will not autoload anymore in Composer v1.11+. in phar:///usr/local/bin/composer/src/Composer/Autoload/ClassMapGenerator.php:185
Deprecation Notice: Class SendGrid\Mail\To located in ./vendor/sendgrid/sendgrid/lib/mail/To.php does not comply with psr-4 autoloading standard. It will not autoload anymore in Composer v1.11+. in phar:///usr/local/bin/composer/src/Composer/Autoload/ClassMapGenerator.php:185
Deprecation Notice: Class SendGrid\Mail\EmailAddress located in ./vendor/sendgrid/sendgrid/lib/mail/EmailAddress.php does not comply with psr-4 autoloading standard. It will not autoload anymore in Composer v1.11+. in phar:///usr/local/bin/composer/src/Composer/Autoload/ClassMapGenerator.php:185
Deprecation Notice: Class SendGrid\Mail\Footer located in ./vendor/sendgrid/sendgrid/lib/mail/Footer.php does not comply with psr-4 autoloading standard. It will not autoload anymore in Composer v1.11+. in phar:///usr/local/bin/composer/src/Composer/Autoload/ClassMapGenerator.php:185
Deprecation Notice: Class SendGrid\Mail\GroupsToDisplay located in ./vendor/sendgrid/sendgrid/lib/mail/GroupsToDisplay.php does not comply with psr-4 autoloading standard. It will not autoload anymore in Composer v1.11+. in phar:///usr/local/bin/composer/src/Composer/Autoload/ClassMapGenerator.php:185
Deprecation Notice: Class SendGrid\Mail\CustomArg located in ./vendor/sendgrid/sendgrid/lib/mail/CustomArg.php does not comply with psr-4 autoloading standard. It will not autoload anymore in Composer v1.11+. in phar:///usr/local/bin/composer/src/Composer/Autoload/ClassMapGenerator.php:185
Deprecation Notice: Class SendGrid\Mail\PlainTextContent located in ./vendor/sendgrid/sendgrid/lib/mail/PlainTextContent.php does not comply with psr-4 autoloading standard. It will not autoload anymore in Composer v1.11+. in phar:///usr/local/bin/composer/src/Composer/Autoload/ClassMapGenerator.php:185
Deprecation Notice: Class SendGrid\Mail\BccSettings located in ./vendor/sendgrid/sendgrid/lib/mail/BccSettings.php does not comply with psr-4 autoloading standard. It will not autoload anymore in Composer v1.11+. in phar:///usr/local/bin/composer/src/Composer/Autoload/ClassMapGenerator.php:185
Deprecation Notice: Class SendGrid\Mail\TemplateId located in ./vendor/sendgrid/sendgrid/lib/mail/TemplateId.php does not comply with psr-4 autoloading standard. It will not autoload anymore in Composer v1.11+. in phar:///usr/local/bin/composer/src/Composer/Autoload/ClassMapGenerator.php:185
Deprecation Notice: Class SendGrid\Mail\MimeType located in ./vendor/sendgrid/sendgrid/lib/mail/MimeType.php does not comply with psr-4 autoloading standard. It will not autoload anymore in Composer v1.11+. in phar:///usr/local/bin/composer/src/Composer/Autoload/ClassMapGenerator.php:185
Deprecation Notice: Class SendGrid\Mail\Cc located in ./vendor/sendgrid/sendgrid/lib/mail/Cc.php does not comply with psr-4 autoloading standard. It will not autoload anymore in Composer v1.11+. in phar:///usr/local/bin/composer/src/Composer/Autoload/ClassMapGenerator.php:185
Deprecation Notice: Class SendGrid\Mail\GroupId located in ./vendor/sendgrid/sendgrid/lib/mail/GroupId.php does not comply with psr-4 autoloading standard. It will not autoload anymore in Composer v1.11+. in phar:///usr/local/bin/composer/src/Composer/Autoload/ClassMapGenerator.php:185
Deprecation Notice: Class SendGrid\Mail\SendAt located in ./vendor/sendgrid/sendgrid/lib/mail/SendAt.php does not comply with psr-4 autoloading standard. It will not autoload anymore in Composer v1.11+. in phar:///usr/local/bin/composer/src/Composer/Autoload/ClassMapGenerator.php:185
Deprecation Notice: Class SendGrid\Mail\Subject located in ./vendor/sendgrid/sendgrid/lib/mail/Subject.php does not comply with psr-4 autoloading standard. It will not autoload anymore in Composer v1.11+. in phar:///usr/local/bin/composer/src/Composer/Autoload/ClassMapGenerator.php:185
Deprecation Notice: Class SendGrid\Mail\SubscriptionTracking located in ./vendor/sendgrid/sendgrid/lib/mail/SubscriptionTracking.php does not comply with psr-4 autoloading standard. It will not autoload anymore in Composer v1.11+. in phar:///usr/local/bin/composer/src/Composer/Autoload/ClassMapGenerator.php:185
Deprecation Notice: Class SendGrid\Mail\From located in ./vendor/sendgrid/sendgrid/lib/mail/From.php does not comply with psr-4 autoloading standard. It will not autoload anymore in Composer v1.11+. in phar:///usr/local/bin/composer/src/Composer/Autoload/ClassMapGenerator.php:185
Deprecation Notice: Class SendGrid\Mail\MailSettings located in ./vendor/sendgrid/sendgrid/lib/mail/MailSettings.php does not comply with psr-4 autoloading standard. It will not autoload anymore in Composer v1.11+. in phar:///usr/local/bin/composer/src/Composer/Autoload/ClassMapGenerator.php:185
Deprecation Notice: Class SendGrid\Mail\Ganalytics located in ./vendor/sendgrid/sendgrid/lib/mail/Ganalytics.php does not comply with psr-4 autoloading standard. It will not autoload anymore in Composer v1.11+. in phar:///usr/local/bin/composer/src/Composer/Autoload/ClassMapGenerator.php:185
Deprecation Notice: Class SendGrid\Mail\BatchId located in ./vendor/sendgrid/sendgrid/lib/mail/BatchId.php does not comply with psr-4 autoloading standard. It will not autoload anymore in Composer v1.11+. in phar:///usr/local/bin/composer/src/Composer/Autoload/ClassMapGenerator.php:185
Deprecation Notice: Class SendGrid\Mail\SandBoxMode located in ./vendor/sendgrid/sendgrid/lib/mail/SandBoxMode.php does not comply with psr-4 autoloading standard. It will not autoload anymore in Composer v1.11+. in phar:///usr/local/bin/composer/src/Composer/Autoload/ClassMapGenerator.php:185
Deprecation Notice: Class SendGrid\Mail\Attachment located in ./vendor/sendgrid/sendgrid/lib/mail/Attachment.php does not comply with psr-4 autoloading standard. It will not autoload anymore in Composer v1.11+. in phar:///usr/local/bin/composer/src/Composer/Autoload/ClassMapGenerator.php:185
Deprecation Notice: Class SendGrid\Mail\Section located in ./vendor/sendgrid/sendgrid/lib/mail/Section.php does not comply with psr-4 autoloading standard. It will not autoload anymore in Composer v1.11+. in phar:///usr/local/bin/composer/src/Composer/Autoload/ClassMapGenerator.php:185
Deprecation Notice: Class SendGrid\Contacts\RecipientForm located in ./vendor/sendgrid/sendgrid/lib/contacts/RecipientForm.php does not comply with psr-4 autoloading standard. It will not autoload anymore in Composer v1.11+. in phar:///usr/local/bin/composer/src/Composer/Autoload/ClassMapGenerator.php:185
Deprecation Notice: Class SendGrid\Contacts\Recipient located in ./vendor/sendgrid/sendgrid/lib/contacts/Recipient.php does not comply with psr-4 autoloading standard. It will not autoload anymore in Composer v1.11+. in phar:///usr/local/bin/composer/src/Composer/Autoload/ClassMapGenerator.php:185
Deprecation Notice: Class SendGrid\Stats\Stats located in ./vendor/sendgrid/sendgrid/lib/stats/Stats.php does not comply with psr-4 autoloading standard. It will not autoload anymore in Composer v1.11+. in phar:///usr/local/bin/composer/src/Composer/Autoload/ClassMapGenerator.php:185

Steps to Reproduce

Install Composer version Composer version 1.10-dev
pull package "sendgrid/sendgrid": "~7",
run composer install

Any other information you want to share that is relevant to the issue being reported. Especially, why do you consider this to be a bug? What do you expect to happen instead?
I expect no warnings or errors.
Technical details:

PHP Version: 7.3.3

This chunk of code - in composer.json - must be responsible for this:
  "autoload": {
    "psr-4": {
      "SendGrid\\": "lib/",               <<< Remove this line
      "SendGrid\\Mail\\": "lib/mail/",
      "SendGrid\\Contacts\\": "lib/contacts/",
      "SendGrid\\Stats\\": "lib/stats/"
    },
    "files": ["lib/SendGrid.php"]
  },

I think it's better to remove the mentioned line. Composer complains about the lowercase folder name the php files are in. But because every subfolder is entered below, the line is unnecessary.
The SendGrid.php file in this folder is loaded separately in 'files' section and isn't in namespace.

Any updates?

My PR is still pending for 'code review' - like many other PRs :(

Approved and merged. Next release scheduled for 2020-02-19.


i need a really sick cozy client

title

not relevant to the project

omfg. what's wrong with these people...


Fixed compilation

Implementation of some methods in TestDataProvider lacks of correct interface declaration

No problem vicent! Your work is awesome. We are here to help :) Thanks!


Added linking instruction to Install.md

The first time I tried setting up Liblava, I got confused by this due to generally lacking CMake knowledge.

I appreciate that, it helps others as well.


aug

Coverage remained the same at 92.857% when pulling eb1e275529308fbcac9c04baec391e132e57d648 on aug into 72322e22526aa2e67f060c0187064e84674bc3c8 on master.


feat: GuardGoalNums tactic

What did I do wrong? :smile:

Also this is actually guardNumGoals, I shouldn't try to do this and listen to Mario at the same time

Okay, so this wasn't the tactic I was supposed to implement but I think it works? (Feel free to close if this is useless, hah.)


Camera_windows changing resolution selection does not affect file size

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce
Select Medium resolution from your example app and a photo shows on my filesystem as 1920x1280 and 331kb jpeg, 10 seconds of MP4 video is 28.8Mb...changing resolution to Max gives new files with the same sizes and resolutions despite the resolution being correctly set in createCamera with _serializeResolutionPreset(resolutionPreset)
Checking with the windows camera app gives 134kb and 2.37Mb when set on Medium (also jpeg and MP4) so it seems that the resolutionpreset isn't working correctly
Expected results
resolutionPreset should actually change the resolution and give broadly similar results to the default windows camera.
Actual results
Select Medium resolution from your example app and a photo shows on my filesystem as 1920x1280 and 331kb jpeg, 10 seconds of MP4 video is 28.8Mb...changing resolution to Max gives new files with the same sizes and resolutions despite the resolution being correctly set in createCamera with _serializeResolutionPreset(resolutionPreset)
Checking with the windows camera app gives 134kb and 2.37Mb when set on Medium (also jpeg and MP4) so it seems that the resolutionpreset isn't working correctly...whether that is just by accident or not I don't know since as you will see from the screenshots Microsoft can't get the resolutions in order.  The photo resolution does not correlate to the resolutionPresets whilst the video does (albeit with no Low resolution mode available and the rear camera mirrored-but I have a code to correct that)
Code sample
Code sample
Select Medium resolution from your example app and a photo shows on my filesystem as 1920x1280 and 331kb jpeg, 10 seconds of MP4 video is 28.8Mb...changing resolution to max gives new files with the same sizes and resolutions despite the resolution being correctly set in createCamera with _serializeResolutionPreset(resolutionPreset)

Checking with the windows camera app gives 134kb and 2.37Mb when set on Medium (also jpeg and MP4) so it seems that the resolutionpreset isn't working correctly

//use your own example code!
Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

![photoset2](https://github.com/flutter/flutter/assets/70710178/896369d0-a009-4f25-8e25-5165b0e1f68f)
![video](https://github.com/flutter/flutter/assets/70710178/c34eb5d2-b463-4035-b197-6d4f5e00d312)
Logs
Logs
[Paste your logs here]

Flutter Doctor output
Doctor output
There is no output because the code produces images and video as expected just not at the  resolution expected

Hi @Jsnt1004
This looks similar to a known issue being tracked at https://github.com/flutter/flutter/issues/122966.
Closing this issue in favor of #122966, so please follow up on it for further updates. You can leave there your comment and react an upvote to the original comment will help to raise the issue. Thank you!


added maven central version badge

Thanks!

Adding this manually instead since there are merge conflicts.

Closing this since I solver the problem manually. Thanks again, looking good!


Make isort venv, or other environment, independent

This ticket represents the work to make isort work the same, by default independent to what environments are loaded or installed. This is increasingly important as isort is being utilized widely within CI/CD systems, where the likely hood that a build system will have a different venv than a developers machine becomes very high.
Suggested approach:
Default finding should do the following on a per import basis:

CUSTOM: import name exists in any custom specified import sections.
FUTURE: import starts with from __future__
STDLIB: import name exists in comprehensive built in definition of stdlib imports
FIRSTPARTY: import name starts with .
FIRSTPARTY: import code exists within the files isort is told to sort.
FIRSTPARTY: import code exists in same directory as any files isort is told to sort.
THIRDPARTY: Everything else.

In this way, by default isort will not use any magic and will be fully repeatable :crossed_fingers:. The older approach should be made available via a flag, such as --environment-identifcation-magic and corresponding config option. No optional dependencies (such as toml, setup.py requirements etc) should be used by default, as using these optional dependencies by default is a recipe for non-repeatable runs and user confusion.
Related:
https://github.com/timothycrosley/isort/issues/1058
https://github.com/timothycrosley/isort/pull/1071
https://github.com/timothycrosley/isort/issues/1104
https://github.com/timothycrosley/isort/issues/1098
https://github.com/timothycrosley/isort/issues/1048
https://github.com/timothycrosley/isort/issues/1007
https://github.com/timothycrosley/isort/issues/952
https://github.com/timothycrosley/isort/issues/910
And more that have been closed from previous magic improvement work, though this is the first magic removal attempt.

I just discovered this testing the master branch on our code sorted with 4.3.21 with everything mixing into first-party (within isolated pre-commit hooks is out direct use case here). Good to see it's known.
The change to third-by-default sounds sane; for our use case I'd be happy with that and explicitly specifying first-party, though appreciate some level of heuristic magic might make it more flexible.
Doing so based on where it's run sounds to me like maybe a risk of getting different behaviour based on where it's run from (e.g. along with pre-commit we have weekly jobs that run inside and over whole multi-project trees, in case people haven't been installing the hooks....). Perhaps "FIRSTPARTY is anything above in the current package"?, though I imagine namespace packages make this hard to determine heuristically also.
From these rules It looks like local/relative (.) imports are proposed to be counted as FIRSTPARTY - these are currently LOCAL, I believe? Planning to remove this distinction, or just not specifying here?

fwiw, you may find some prior art in https://github.com/asottile/aspy.refactor_imports (which powers reorder-python-imports) -- notably you'll likely run into the issue of src layouts where you'll want some sort of argument to indicate where the source roots are -- the tool above uses --application-directories
as a workaround, and what's been suggested for usage with pre-commit at least, is to utilize seed-isort-config which leverages aspy.refactor_imports to populate known_third_party and then isort "just works"
I suggested something similar way back in #184 ;)

Is there any interest in/plan for allowing the [tool.poetry.dependencies] and [tool.poetry.dev-dependencies] to seed the isort THIRDPARTY list?

When does this fix is about to be merged? This is making a lot of false-positive errors in my CI/CD process.

This is now merged into development branch and ready for release with 5.0.0. @beneisner, no - that's the exact kind of magic I'm aiming to remove. The good news, is with this latest version you shouldn't need it.


Roadmap Question

First off, this is a fantastic project!  Thank you for building it.
How deep down the wallet features past wallet generation and importing do you plan on going?  I imagine wagyu would be a useful component in an offline signing solution for instance.

Thanks! We should definitely add a roadmap on here. There are subsequent repos in the works currently to complement wagyu. One repo (codename unagi) will enable API queries for the supported coins (so one can pull UTXOs/balances/state), and the other repo (codenamed bento) will be a stateful wallet (ingesting unagi + wagyu to enable importing/exporting of keys, lookup of past transactions, and sending of new transactions).
The original plan was to build all of this into wagyu, however it was becoming a monolith that needed some proper abstraction barriers. This way, wagyu can be used solely for stateless operations (e.g. offline operations), while bento can be used as a stateful client (which is more high-level/user-friendly).

Great question, we've gone back and forth on this, and are open to your thoughts (as well as the community's).
For now, we're taking it case by case. For example, Bitcoin, Ethereum, and Monero are currently built as independent implementations. Zcash includes a partial port of the algebraic components and Sapling crypto primitives, which we then map to the Standard and HD wallet models in wagyu.
In some cases it may be difficult to build an independent implementation. For example, most (if not all) Monero transaction builders query a Monero full node to discover the other inputs in crafting a full Monero TX. In this case, it might be overly complicated to implement an independent version.

In the case of Zcash, we could transition it to a fully independent implementation. For example, I implemented the BLS12-381 and JubJub infra in zexe, and we could in theory port this out (which already has a full array of arithmetic operations, including tests) to build an independent Sapling crypto stack. However, for the time being, we felt doing that would only make sense once the base protocol itself has stabilized (likely over the years).

Interesting, it seems more straightforward for parallel implementations for the wagyu side of things to keep it lightweight and minimal on the dependencies.  It optimizes for "it just works".
Unagi and Bento (or anything stateful) seem tougher especially as you support more wallet operations and currency types.  I could imagine a plugin interface that declares dependencies and the operations they support that could then be surfaced to the UI or API of Unagi/Bento.
For instance for Monero, in order to provide operations you would need a monero full node running or an address of one to query as well as a monero cli executable to shell out to (kinda clunky).  You could also make it a shared library dependency in the case where a project exposes a nice library api.
One other way to encapsulate and limit the scope of this might be drawing the line at just tx signing and do all tx crafting in the native clients for a particular currency.

The plan is to try and funnel all network queries (external requests) to unagi, and have implementations for requests with different service providers (using whatever connection protocol needed - REST, RPC, etc). This way fetching state from the outside world is unagi's responsibility, and with implementations for multiple service providers, we can traitify the service provider and build-in automatic fallbacks (e.g. if one service provider goes down for maintenance) for each functionality in unagi.
This way, for transactions, wagyu will remain strictly a transaction builder. Then unagi, will be an external state fetcher. And then, bento will be a stateful wallet by ingesting wagyu and unagi.

The architecture makes a ton of sense.  I like the encapsulation of external data fetching to a single library as that can get messy.  Thank you for outlining a bit more of the roadmap here.  Feel free to close out the issue.

No problem and always open to suggestions. The goal is to design a framework that be useful for the community and be robust enough to stand the test of time. Thanks for the kind words


.trigger('change')

v1.2.0 line 1117 doesn't contain 'model &&'
When setting value (using "silent:true") and then chaining & triggering a "change"  event, it throws an error
model.set({'some':'data'}, {'silent':true}).trigger('change');
I know it says "not" to use silent...

I'm not sure this needs to be fixed. The change event always passes model as the first argument, and an options object as the second. Anything else is breaking the contract.
model.trigger('change', model, options).

Hi Justin,
It's odd that it only happens when the model is in a collection.
I guess it's in my code somewhere.
Regards,
John Schroeder
<EMAIL_ADDRESS>480-948-0009

On Jun 3, 2015, at 3:54 PM, Justin Ridgewell<EMAIL_ADDRESS>wrote:
I'm not sure this needs to be fixed. The change event always passes model as the first argument, and an options object as the second. Anything else is breaking the contract.
model.trigger('change', model, options).
—
Reply to this email directly or view it on GitHub.


Adding SDK Generation related implementation

Purpose
Fix for: https://github.com/wso2/apk/issues/440

Codecov Report
Base: 15.55% // Head: 15.91% // Increases project coverage by +0.35% :tada:

Coverage data is based on head (49f0707) compared to base (bb01472).
Patch coverage: 7.09% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #460      +/-   ##
==========================================
+ Coverage   15.55%   15.91%   +0.35%
==========================================
  Files          76       76
  Lines        5662     5541     -121
  Branches     3130     3077      -53
==========================================
+ Hits          881      882       +1
+ Misses       4781     4659     -122

Impacted Files
Coverage Δ

...tal/devportal-domain-service/ballerina/apiImpl.bal
24.00% <0.00%> (-68.31%)
:arrow_down:

...apk.devportal.sdk/APIClientGenerationException.bal
0.00% <0.00%> (ø)

...2.apk.devportal.sdk/APIClientGenerationManager.bal
2.73% <2.73%> (ø)

...domain-service/ballerina/devportal-api_service.bal
9.47% <6.25%> (-0.30%)
:arrow_down:

...allerina/modules/java.util.function/BiConsumer.bal
28.57% <28.57%> (ø)

...allerina/modules/java.util.function/BiFunction.bal
28.57% <28.57%> (ø)

.../ballerina/modules/java.util.function/Function.bal
28.57% <28.57%> (ø)

...main-service/ballerina/modules/java.util/Entry.bal
28.57% <28.57%> (ø)

...domain-service/ballerina/modules/java.util/Set.bal

...main-service/ballerina/modules/java.lang/Class.bal

... and 4 more

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 at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Adding comment to flare provider to prevent people from adding more

What does this PR do?
Adding comment to flare provider to prevent people from adding more

/merge


Problem with equivalence axiom for 'abnormal pterygoid muscle morphology'

'has part' some
(morphology and ('inheres in' some 'medial pterygoid muscle') and ('inheres in' some 'lateral pterygoid muscle') and ('has modifier' some abnormal))

the abnormality can't be in both places at the same time (the latest version of uberon makes these two classes spatially distinct, so we're catching it)

Same for absent:
'has part' some
('lacks all parts of type' and ('inheres in' some mouth) and (towards some 'medial pterygoid muscle') and (towards some 'lateral pterygoid muscle') and ('has modifier' some abnormal))

just use UBERON:0006720 ! pterygoid muscle

Very odd.  I thought you can't make a double 'inheres in' ...
Fixed axiom for 'abnormal...' and also revised axiom for 'absent....', which had additional problems as well.


How to add a private a private registry say on loalhost:50000 to anchore-client?

Is this a request for help?:
YES
Is this a BUG REPORT or a FEATURE REQUEST? (choose one):
NONE

Version of Anchore Engine and Anchore CLI if applicable:
anchore-cli --version anchore-cli, version 0.4.0
What happened:
I am unable to add a private registry for scanning.
What did you expect to happen:
Registry was deployed using the following commands:
mkdir Infrastructure
cd Infrastructure/
mkdir Registry
cd Registry/

vim docker-compose.yml
version: '3.0'

services:
  my-registry:
    image: registry:latest
    container_name: my-registry
    volumes:
      - registry:/var/lib/registry
    ports:
      - "50000:5000"
    restart: unless-stopped
volumes:
  registry:

docker-compose up -d
docker login localhost:50000
docker tag nmap-dist:latest localhost:50000/nmap-dist:latest && docker push localhost:50000/nmap-dist:latest

Any relevant log output from /var/log/anchore:
anchore-cli registry add <IP_ADDRESS>:50000/v2/_catalog nehajainiitbhilai iitbhilai1234

Error: cannot ping supplied registry with supplied credentials - exception: failed check to access registry (https://<IP_ADDRESS>:50000,nehajainiitbhilai) - exception: HTTPSConnectionPool(host='<IP_ADDRESS>', port=50000): Max retries exceeded with url: /v2/ (Caused by SSLError(SSLError("bad handshake: Error([('SSL routines', 'ssl3_get_record', 'wrong version number')],)",),))
HTTP Code: 406
Detail: {u'error_codes': []}
What docker images are you using:
nmap-dist, nmap image built on distroless.
How to reproduce the issue:
Anything else we need to know:

hi @nehaj27
By default, the docker registry image doesn't deploy with SSL enabled (or with any default users/credentials in place) - a couple of options!

you don't have to add the registry at all (or log in/create credentials), in order to add an image:

# docker-compose up -d
# docker tag docker.io/alpine:latest localhost:50000/alpine:latest
# docker push localhost:50000/alpine:latest
The push refers to a repository [localhost:50000/alpine]
f1b5933fe4b5: Layer already exists
latest: digest: sha256:bf1684a6e3676389ec861c602e97f27b03f14178e5bc3f70dce198f9f160cce9 size: 528

from there, you can add an image to anchore (skipping the step of adding the registry, since there are no creds by default):
# anchore-cli image add <ip>:50000/alpine:latest
Image Digest: sha256:bf1684a6e3676389ec861c602e97f27b03f14178e5bc3f70dce198f9f160cce9
Parent Digest: sha256:769fddc7cc2f0a1c35abb2f91432e8beecf83916c421420e6a6da9f8975464b6
Analysis Status: not_analyzed
...
...

if you do enable TLS and add credentials to your registry (see https://docs.docker.com/registry/deploying/), then you can add the registry/credentials as you were working through in your report.  note that, if you decide to use a self-signed certificate, you would also need to supply the '--insecure' flag to 'anchore-cli registry add ...' to allow the system to interact with a registry endpoint with a self-signed cert.

Let us know if this helps to clarify!

Closing this out due to inactivity, @nehaj27  Please re-open if more questions or issues remain. Thanks!


Create update-contributors.yml

Auto updating contributors to README.md

There's a error in the file


Add support for SIMD vector comparison intrinsics

Description of changes:

Changes the vector type to contain a VectorData struct with type information (this allows us to re-define type equality for vector types).
Declares Vector* expressions which generate vector-* ireps, as regular operators (e.g., == or <=) aren't picked up by CBMC. This also makes our own type-checking code cleaner.
Re-enables SIMD intrinsics.
Adds some utilities functions for vector types.
Moves the SIMD tests folder to Intrinsics.
Splits our test case into unsigned integers, signed integers, and floats.

Resolved issues:
Towards #1148
Call-outs:

Testing:

How is this change tested? Existing regression + more cases.

Is this a refactor change? No.

Checklist

[x] Each commit message has a non-empty body, explaining why the change was made
[x] Methods or procedures are documented
[x] Regression or unit tests are included, or existing tests cover the modified code
[x] My PR is restricted to a single feature or bugfix

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses.

Ready for review again!
Typecheck errors are now triggered in codegen_intrinsic_simd_cmp and they are very similar to the ones produced by rustc. I've also included the (redundant) typechecks in a new associated function typecheck_vector_cmp_expr.
I've also undone the VectorData wrapper change. It isn't needed anymore because we're passing down the place type as the return type, which we use to generate the vector comparison expression. Previously, I wasn't doing this so I need to bypass the typecheck for assign statements somehow.
I've also moved/edited/added some comments.

BTW this is ready for review again, all comments above have been addressed.


feat(W293): blank line contains whitespaces

Added W293 from pycodestyle
https://www.flake8rules.com/rules/W293.html

Ok there's a PR recently with this rule already https://github.com/charliermarsh/ruff/pull/3122/files

Oh yeah that's funny timing! Thank you for this.

I could definitely use help with the remaining pycodestyle rules, FWIW.

I could definitely use help with the remaining pycodestyle rules, FWIW.

@charliermarsh sure, I will try to add the missing ones!


Firefox 69: user-select unprefixed

https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/69:

The user-select property---which specifies whether or not the user is able to select text in the affected element---has been unprefixed in Firefox 69 (bug 1492739).

I've checked https://tests.caniuse.com/?feat=user-select-none using Firefox 69.0b13 (64-Bit).

Thanks!


Clean up restrictive placeholders

Right now you have to declare restrictive placeholders with every route that uses them.
my $r = $app->routes;
$r->get('/users/:id' => [id => qr/[0-9]+/])->to('Users#show');
$r->get('/groups/:id' => [id => qr/[0-9]+/])->to('Groups#show');
$r->get('/rooms/:name' => [name => ['red', 'blue']])->to('Rooms#show');
...

This can be quite tedious, and doesn't look all that nice. What we could do instead is to allow for reusable named restrictions (needs a better name...) to be declared once on the router. And then use them with a new placeholder notation.
my $r = $app->routes;
$r->add_restriction(int => qr/[0-9]+/);
$r->add_restriction(room_name => ['red', 'blue']);

$r->get('/users/(id:int)')->to('Users#show');
$r->get('/groups/(id:int)')->to('Groups#show');
$r->get('/rooms/(name:room_name)')->to('Rooms#show');
...

Some restrictions like int could be built-in. The old way of declaring restrictive placeholders could be preserved or deprecated, i'm not sure which is better. Thoughts?

I love this idea!. I would call it placeholder types or placeholder definition instead of placeholder restriction. On the other hand, I would vote to keep the old way as I think it still fits better for small/lite apps.

I like the new syntax. I am neutral about what happens to the old syntax.

@jhthorsen What you think about incorporating this into the OpenAPI plugin? And/or being able to use this to generate an OpenAPI spec from existing route-specs?

@mohawk2: I can't use it in m::p::openapi and keep the existing functionality: I want to return 400 and not 404 when a placeholder gets "invalid" data.

I've made a branch with an implementation of the feature. https://github.com/kraih/mojo/compare/placeholder_types

This makes some aspects of routing much more clear, and it makes perfect sense to 404 unmatched routes. On the other hand, like @jhthorsen's comment above, most of my applications use liberal route placeholders and then post-routing type validation in the controller to return a 400, rather than a 404. I think I would use this feature, but not as often as I would if it were a post-routing type check.

It appears we have a strong argument against this feature. Which is the lack of type validation error handling, and inability to respond with a 400 response instead of the usual 404. I guess that could be a blocker.

So, i think this feature is blocked until we find a solution for handling validation errors for normal restrictive placeholders, or decide that we never want to do that. Otherwise we risk making routing internals too complicated for proper validation error handling.

Shouldn't a route with a non-matching placeholder just be ignored and not trigger the route at all (like with the current implementation with regex matching)?
That way by adding another route with an unrestricted type you could still allow to handle the "bad input" case like in the example below.
my $r = $app->routes;
$r->add_restriction(int => qr/[0-9]+/, catch => 0);
$r->get('/users/(id:int)')->to('Users#show'); # Should match /users/646
$r->get('/users/:id')->to('Users#handlebad); # Should match all other users /users/frosty and invalid chars

To avoid having to define the route twice for the fallback, I tried to come up with a syntax to integrate the check into the placeholder type, but only came up with a syntax that I'm not happy with:
my $r = $app->routes;
# Route to controller Generic#badinput in case placeholder is found but invalid
$r->add_placeholder_type(int => qr/[0-9]+/, route_invalid => 'Generic#badinput');
# No invalid route defined, just skip the route if "int" is not matched
$r->add_placeholder_type(int => qr/[0-9]+/); # same as below
$r->add_placeholder_type(int => qr/[0-9]+/, route_invalid => undef);

This will always trigger the same controller on invalid input, which reduces the reusability of the placeholder again. Not sure if that is what I want.

How can you tell which route failed inside route_invalid? I was thinking about something similar:
$app->hook(after_partial_route_match => sub { my ($c) = @_ ... });

But it also suffers from knowing what didn't match. I mean, it can be a list of routes:
$r->get('/users/(id:int)')->to('user#get_by_id');
$r->get('/users/(id:str)')->to('user#get_by_username');

You cannot really tell them apart unless you check the request path again of course, but that is not a very modular approach. That is exactly why I am not really happy with that approach.
So the only way would be to add additional information to the route itself (e.g. overriding the proposed route_invalid):
$r->get('/users/(id:int)' => route_invalid => 'user#failed')->to('user#get_by_id'); #or
$r->get('/users/(id:int)')->to('user#get_by_id')->invalid_to('user#badid'); #or

Again here, if no route_invalid is specified the route would be silently ignored.
I kind of like the second syntax, it seems quite natural to Mojo.
Without the invalid_to handling it would be more verbose:
$r->get('/users/(id:int)')->to('user#get_by_id');
$r->get('/users/:id')->to('user#badid');

So far this seems like the only sensible solution to me.
$r->get('/users/(id:int)')->to('user#get_by_id');
$r->get('/users/:id')->to('user#badid');

How do you propose we differentiate between a request not matching on the /users part from a route not matching on the /(id:int) part? Wouldn't that require a total rewrite of the router? Is that even possible without breaking lots of other things?

The intention would be to match only on the placeholder parts, but as soon as multiple placeholders are used you would again need to map them.
$r->get('/users/(id:int)/link/(friendid:int')->to('user#get_by_id')->invalid_to(id => 'user#badid', friendid => 'user#badfriendid');

This would then reroute for a bad friendid to user#badfriendid and on a bad id to user#badid. Otherwise it would just skip the route. But I'm not convinced yet either.

I think this proposal has failed. There seems to be a lot of interest in differentiating between a route not matching at all and a placeholder type not matching. With the current router that seems almost impossible to implement.


Improve test coverage of special methods with type conversions

https://github.com/cython/cython/issues/4163
if old_type.is_pyobject:
    if arg.default:  # 4325 ↛ 4326
        code.putln("if (%s) {" % arg.hdr_cname)
    else:
        code.putln("assert(%s); {" % arg.hdr_cname)
        self.generate_arg_conversion_from_pyobject(arg, code)
        code.putln("}")
    elif new_type.is_pyobject:  # 4331 ↛ 4334
        self.generate_arg_conversion_to_pyobject(arg, code)
    else:
        if new_type.assignable_from(old_type):
            code.putln("%s = %s;" % (arg.entry.cname, arg.hdr_cname))
        else:
            error(arg.pos, "Cannot convert 1 argument from '%s' to '%s'" % (old_type, new_type))

It doesn't cover the arg.default case (since I don't think any
of these methods accept a default argument), or the failed conversion
case. But does cover the pyobject->C, C->pyobject and C->C cases

(and fills in a hole in coverage of the Cython source)

Adding a test ALWAYS intends to improve the coverage, so this line isn't needed. It's good as part of a commit comment, explaining the reason for the change, but it shouldn't remain in the code. It's actually outdated the moment it gets committed.


[BUG] Add or change language

Ver: eb7c605
描述问题
How to change the language or add one
I want to add another language or if it's possible change the current language(bot commands language)

Please response in english, Thanks

You can add an environment variable configuration to cloudflare, set LANGUAGE to en. then re-invoke the init excuse


Remove version: Outertech.GetDiz version <IP_ADDRESS>

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

URL: https://www.outertech.com/downloads/getdiz491.exe
Response status code does not indicate success: 523 ().
(Automated message - build 897)

Hi @Exorcism0666,
This manifest has the highest version number for this package. Is it available from another location? (This might be in error if the version is switching from semantic to string, or string to semantic.)
(Automated response - build 897.)


Internet Explorer support

I am opening this issue for discussing ways to overcome or workaround IE's (lack of) ES6 support.
FYI: https://caniuse.com/#feat=es6

Microsoft is making changes that might move more users from IE to Edge.
Windows 7 support ends January 14th, 2020. This is pushing enterprise customers to move to Windows 10. More Windows 10 users means the availability of Edge to more users.
An upcoming Edge feature will let people view IE compatible pages rendered by IE directly in the Edge browser. This will be available and helpful to enterprise and home Windows users.

https://arstechnica.com/gadgets/2019/05/coming-soon-to-chromium-edge-ie-tabs-more-privacy-control/

Enterprises that have completely moved to Windows 10 can use group policies that are available now to force Edge usage while supporting falling back to IE for sites that need it.

https://docs.microsoft.com/en-us/microsoft-edge/deploy/emie-to-improve-compatibility
https://support.microsoft.com/en-us/help/4019877/windows-10-open-internet-explorer-11-for-webpages-that-required-enterp

But what if they move to Linux instead?

I haven't heard anything about IE11 adding ESM support, did I miss that? @pika/web exists to let you install dependencies that can be imported natively in the browser. Unfortunately, that's impossible without ESM support.
We did just add transpilation to target older browser, but that is still restricted to "browsers that support ESM".

Closing since I don't believe this is actionable


Syntax error in matching/model/rnn_encoder.py.

Dear authors,
There are several Syntax Errors stemming from wrong variable names within the forward function of the Entity Maching model, inside
matching/model/rnn_encoder.py.  I am not sure how to fix it, because due to the naming conventions it is non-trivial.
It is only 24 lines, so I am sending the code snippet below that contains the errors:
def forward(self, alias1, alias1_word_mask, alias1_char_mask, alias2, alias2_word_mask, is_sample=False):
device = torch.device("cuda")
batch_size, word_max_len1, char_max_len1 = alias1.size(0)
alias = alias.view(batch_size * word_max_len, char_max_len)

alias_rep = self.embeddings(alias)

alias_char_len = alias_char_mask.view(batch_size * word_max_len, char_max_len).data.eq(0).long().sum(1).cpu().numpy().tolist()
alias_char_idx = [i for i in range(len(alias_char_len)) if alias_char_len[i] > 0]
alias_char_mask = alias_char_mask.view(batch_size * word_max_len, char_max_len)[alias_char_idx]
alias_char_len = [i for i in alias_char_len if i > 0]
alias_rep = alias_rep[alias_char_idx]
alias_rep = self.char_encoder(alias_rep, alias_char_len)

alias_rep = self.char_self_attn(alias_rep, alias_char_mask)
del alias_char_mask

alias_word_rep = torch.FloatTensor(batch_size * word_max_len, 2 * self.args.hidden_size).zero_().to(device)
alias_word_rep[alias_char_idx] = alias_rep
#del alias_rep

alias_word_rep = alias_word_rep.view(batch_size, word_max_len, -1)
alias_word_len = alias_word_mask.data.cpu().eq(0).long().sum(1).cpu().numpy().tolist()

return self.word_encoder(alias_word_rep, alias_word_len, is_sample)

As you can see, alias1_word_mask, alias1_char_mask, alias2, alias2_word_mask are all in the arguments of the function, but they are in fact never used (properly) which leaves the subsequent expressions with undefined variables.

Thanks for your interest, sorry about the confusion. Could you help check which code fragment uses this module (Hybrid_Alias_Rep), as I could not find it. If none of the code used this module, it might be fine to just ignore this function.

You are right. It is not used, but since it seems like a simplified version of Hybrid_Alias_Sim. I thought it was/is perhaps for the sake of calculating feature representations of words for analytical purposes (which might be useful to know before the attention gets applied).
Is it completely redundant then, in case I would only like to pass the data through the pipeline described in the paper?


Improved bootstrapping

This patch comes up because the directory structure of http.kali.org has changed. There is no directory called stable anymore. It is substituted by kali/. However I think this can be a universal improvement as the implementation of bootstrapping kali we have currently only works for kali, not for other derived distros.
This fix has been part of my effort to add the Trisquel distro and it has been sleeping in my fork for quite a long time now. :P
Fixed according to #1868

I think this makes sense, but needs some style fixes :)

@dnschneid fixed

Staging?

Thanks for fixing this!