Regression of GLES2 materials in RC1 3.1.

Godot version:
In version of Godot_v3.1-rc1_win64.exe, compared to Godot_v3.1-beta11_win64.exe
OS/device including version:
Windows 7 Radeon HD 3650
Issue description:
GLES2 materials in RС1 3.1, textures lose clarity, strange stripes are visible.

Minimal reproduction project:
https://www.dropbox.com/s/yb0j0yyfasw459v/3D mat.zip?dl=0

I can't reproduce on linux, Ubuntu 16.04, intel HD graphics

It seems to be due to showing the 3D gizmos, did you try in beta 11 with gizmos disabled maybe?

I can reproduce the blurry reflection with the provided project on Linux (Mageia 7) with Nvidia GTX 670MX.
3.1 beta 11:

3.1 RC1 and 59aa79f2:

I don't have the issue with the gizmos leaking though.

The blurry reflection is a regression from 7141c73ae, a local revert fixes it.

The blurry reflection should be fixed by #26898.
If you can still reproduce the issue with the gizmos appearing on meshes, that would be worth reporting in a new issue.

This is still broken, and deep regression, I tried to run on another computer, here is the result of photos, versions - (Godot_v3.1-beta11_win64.exe, Godot_v3.1-rc1_win64.exe, Godot_v3.1-rc2_win64.exe, Godot_v3. 1-rc3_win64.exe) at the last, additional errors are visible ...

The error is unrelated. It must have been introduced somewhere else.
The results in Beta11 are slightly crisper because they are used a slightly larger radiance map then they should have. To reproduce that level of detail, you should use a larger radiance map. You can set it under environment>sky.
The reason that the radiance is not the same is that it has been updated to match the results of the GLES3 backend.


RHBMS-4188 - Unable to use LATEST as part of the deployment id in RuntimeDataService methods

false negative
jenkins please retest

another.. (succeeds locally.. ).
jenkins please retest

+1 to merge


First draft for the many-fuzzy tool

Design: https://coda.io/d/_df4wCimT68d/Stress-Test-Tool_suhsP
Fixed #1.

It works with ledger.info but I wasn't able to make it work with ledger.send for some reason. Does it work on your side @hansl ?

It does on my side. Here's the example commandline I used:
cargo run --bin many-fuzzy -- fuzz -n 490 http://localhost:8000 --pem ~/Sources/temp/id1.pem ledger.send '{ 1: 10000(h\'01e8acda9634f6f745be872b0e5e9b65b1d3624a3ba91c6432143f60e9\'), 2: 5, 3: "oqbfbahksdwaqeenayy2gxke32hgb7aq4ao4wt745lsfs6wiaaaaqnz" }'

It does on my side. Here's the example commandline I used:
cargo run --bin many-fuzzy -- fuzz -n 490 http://localhost:8000 \
    --pem ~/Sources/temp/id1.pem \
    ledger.send \
    '{ 1: 10000(h\'01e8acda9634f6f745be872b0e5e9b65b1d3624a3ba91c6432143f60e9\'), 2: 5, 3: "oqbfbahksdwaqeenayy2gxke32hgb7aq4ao4wt745lsfs6wiaaaaqnz" }'

The command line you gave didn't parse in bash/zsh, but I got it working with
many-fuzzy fuzz --pem ~/Identities/id1.pem -n 10 \
    http://localhost:8000 \
    'ledger.send' \
    '{1: "oag5x7yiyjektfkwsgok2fnvq4yxnzyvbf5lyi2outfdkkoa6v", 2: 3, 3: "oqbfbahksdwaqeenayy2gxke32hgb7aq4ao4wt745lsfs6wiaaaaqnz"}'

@hansl I'll let you update the spec and merge this. Thanks!


Include simple ORM sample

I'm trying to use the documentation at adonisjs.com to figure out how to create Lucid models in a SQLite database, but it would be much easier if this sample app had an example of, say, a simple one to many relationship model.

It is there already http://adonisjs.com/docs/2.0/lucid-relations#relationships

I'm asking for a sample in the context of this specific "hello world" app.
Also, one of the things that frustrated me about the docs on this specific case is that I got the sense that the Sqlite table would automatically be created for me, but it turns out you have to create it manually with the shape of the ORM object via a DB migration. This is fine, but it just wasn't clear from the docs that you need to do this, so those could stand to be updated, too.
Also, there should be a built-in method on table for specifying that a table should support soft deletes so I don't have to manually call table.timestamp('deleted_at'). Something like table.softDeletes(). The precedent for this is the table.timestamps() method that adds 'created_at' and 'updated_at'.

Agree with soft deletes method in schema creation, will add that.
If you find missing bits in the documentation, than i would appreciate if you can send a pull request with updated docs
I just released 2.0 couple of days back, so need time to gather content and examples apps for community


Add unit tests

This PR includes the following upstream PRs:

https://github.com/openshift-psap/special-resource-operator/pull/121
https://github.com/openshift-psap/special-resource-operator/pull/133
https://github.com/openshift-psap/special-resource-operator/pull/175

/cc @pacevedom @yevgeny-shnaidman @ybettan
/approve
/ok-to-test

I don't see any issue with the PR.
Lets just wait for one more review as I wasn't reviewing https://github.com/openshift-psap/special-resource-operator/pull/133.

Thank you for reviewing. Actually, openshift-psap#133 addresses two bugs, one of which is not included in this repo.
So that PR has been stripped down to just fix assets.go and its unit tests.

/lgtm


Add support for assuming AWS Roles

Anchore (If hosted on AWS EC2) currently assumes the role provided to it (if the config is set to awsauto) This is great to provide the EC2 instance access to the account's ECR. However, if you wanted to have cross account ECR access, this does not work.
After a talk with @nurmi and @zhill , this pull request addresses that issue. It uses the _iam_role as the key on the request to assume the role (sent as the secret) and pull the required image.

Thanks @sonaltr ! I'll give it a review and some testing and if things look good we'll merge it. Before we merge it, you need to sign the contributor agreement at https://github.com/anchore/anchore-engine/blob/master/CONTRIBUTING.rst. You can do that by amending the commit using '-s' for a sign-off line or manually adding it to the commit message.

@zhill just updated the commit message. Please let me know if there are any other issues/concerns.

Test went well. Merged. UX-wise it can be challenging to not see the arn in the cli's 'registry list' or 'registry get' output, but handling viewing credentials is a general issue we need to tackle and not specific to this PR. Thanks @sonaltr!

Hey @zhill. The current implementation of sts.assume_role in anchore doesn't support cross-account ECR access with accounts that require an external_id to be passed (in order to assume the role). Please review the following PR https://github.com/anchore/anchore-engine/pull/225 (If all goes well, I understand the documentation will need to be updated accordingly).

@naman ack, will review and comment in #225


Minor changes on the header page

This image breaks responsiveness ^^. If you can fix it that'll be nice

This image breaks responsiveness ^^. If you can fix it that'll be nice

Fixed


kube proxy userspace docs

This is a Bug Report
Problem:
In general the userspace proxy isnt used much , we should note that in the docs
The userspace for kube proxy has a couple of use cases worth mentioning:

if people want to make their own proxy with custom behaviour (antrea, cilliim, calico?) , they can borrow from it, or look at a minimal reference implementation of a kube proxy
The kube proxy is only configurable by confgimap even though it has several argument options, which can be used for GENERATING a config map.

edit the kube-proxy configmap
restart all kube proxy pods (i.e. delete them, and the ds will bounce em)

The users-space proxy creates a new go routine for every service, this is rarely used, as kernel proxies (which use HNS, IPTables, IPVS, and so on) are much faster and scalable.

..............
I1108 18:11:18.887324       1 server_others.go:186] Using iptables Proxier.
I1108 18:11:18.887599       1 server.go:650] Version: v1.19.1
I1108 18:11:18.887958       1 conntrack.go:52] Setting nf_conntrack_max to 393216

And the userspace proxier:
1108 18:26:29.451576       1 server_others.go:111] kube-proxy node IP is an IPv4 address (<IP_ADDRESS>), assume IPv4 operation
I1108 18:26:29.472040       1 server_others.go:344] Using userspace Proxier.
I1108 18:26:29.489305       1 server.go:650] Version: v1.19.1
I1108 18:26:29.489557       1 conntrack.go:52] Setting nf_conntrack_max to 393216

If nothing else, at least mentioning that there are 4 different kube proxies, the newer ones are ipvs and iptables, and that some CNI providers are implementing kube proxy on their own, so you may not need to run kube proxy, that would be a good enough start i guess.
Proposed Solution:
Add a quick description of the 4 kube proxy modes, (there are also some good external blog posts like https://rtfm.co.ua/en/kubernetes-service-load-balancing-kube-proxy-and-iptables/  which go over some of this stuff.
Page to Update:
https://kubernetes.io/docs/reference/command-line-tools-reference/kube-proxy/

@distributethe6ix

https://kubernetes.io/docs/reference/command-line-tools-reference/kube-proxy/ is pretty much generated documentation and I'm fine with that.
IMO it'd be good to hyperlink from there to https://kubernetes.io/docs/concepts/cluster-administration/proxies/
(which might actually belong in the Services & Networking grouping anyway).
@jayunit100 how does that sound?

Yeah I guess the issue is that there's very little docs about kube-proxy on the hyperlinked page, only like 4 lines :). So need to flesh that out

/sig network
/language en
/triage accepted

:+1: to expanding https://kubernetes.io/docs/concepts/cluster-administration/proxies/

@distributethe6ix

/remove-lifecycle stale

/remove-lifecycle stale

A different idea would be fixing/splitting the concepts/services-networking/service.md file so that kube-proxy specific contents can be provided in a separate section. Currently the content is embedded in https://kubernetes.io/docs/concepts/services-networking/service/#virtual-ips-and-service-proxies

We could split some of the behind-the-scenes kube-proxy details into the reference section. After all, you could in theory deploy a compliant node (passing all tests) without running any of the existing kube-proxy code.

/remove-lifecycle rotten
/lifecycle frozen

There is no userspace mode in kube-proxy any more.
/close


Multiplatform Swift Support

Multiplatform Swift Support
This adds support for non-Apple (i.e. non-Darwin, non-ObjectiveC) swift installations; broadening the package support to Linux and Server-Side-Swift.
The key changes made:

FoundationNetworking: URLSession & URLRequest are not part of the Foundation module on linux. These are provided by the FoundationNetworking module instead. A compiler canImport was added as needed to import the module if found.

Timer Scheduling: The analytics timer used the ObjectiveC message sending api to handle timer events. Since this api is not available on non-Apple platforms, an alternative is specified.

Also:

Updated actions YML to run unit tests against Linux.
Removed a stray FlagsmithAnalytics.swift file from the root of the repo.

Thanks so much for these PRs @richardpiazza ✊


pillar: Initial support for kvmtool

Add initial kvmtool support
Signed-off-by: Sergey Temerkhanov<EMAIL_ADDRESS>

[the hostess took up a broom]
@eriknordmark we can close this pr. I don't think there is any user for this pr, kvmtool has always been positioned as not a replacement for qemu, maybe for development and testing purposes it can be interesting, but not clear why we need it in eve (also no explicit comments from Sergey on that)


Is peephole optimization done by mrb_load_string or only by mrbc?

What is the true benefit to running a mruby script as compiled bytecode .mrb, I assume it's faster because it doesn't need to parse first like a script .rb, but other than that how is it faster? I see based on presence of the --no-optimize switch on mrbc that peephole optimization is performed. Is peephole optimization done only by mrbc for .mrb files?
In particular I have a function like this for loading the compiled bytecode:
mrb_load_irep_buf(mrb, asset->buf, asset->size);

and this for loading a script:
mrb_load_string(mrb, asset->buf);

Is peephole optimization still performed at when loading the script with mrb_load_string or is it solely done by mrbc when compiling the scripts into bytecode?
Thank you in advance.

This is my answer as I understand it. If there is a wrong answer, I hope someone will correct it.

What is the true benefit to running a mruby script as compiled bytecode .mrb,

I remember that the main reason is to separate the Ruby compiler from the main body.
The background is that mruby targets embedded devices (microcontrollers).
Embedded devices have strong limitations on both ROM and RAM.
Users can choose whether or not to include the compiler itself (mrbgems/mruby-compiler) in their products based on their intended use.

other than that how is it faster?

Perhaps it is not much of a concern.
However, one thing is important.
mruby can cause a SIGSEGV if given corrupt .mrb data.
It is safer not to use untrusted third-party .mrb data in process space it cannot afford to crash.
If an untrusted third party code must be executed, it should be executed through mruby-compiler and mrb_load_string() family of functions.

Is peephole optimization done only by mrbc for .mrb files?
Is peephole optimization still performed at when loading the script with mrb_load_string or is it solely done by mrbc when compiling the scripts into bytecode?

Peephole optimization is enabled by default. Therefore, it is enabled not only by the mrbc command, but also by calls to mrb_load_string().
If optimization is to be disabled, e.g. for debugging purposes, use functions such as mrb_load_string_cxt() with the mrb_ccontext::no_optimize field set to true.
For information, each of the eval family methods provided by mruby-eval has optimization disabled.

For information, each of the eval family methods provided by mruby-eval has optimization disabled.
Is there a reason why optimization is disabled on these eval methods? Just curious.

As far as I can see from commit https://github.com/mruby/mruby/commit/ab724104563d20dbe9428b37cf8b30dfda6cc9ee#diff-ec461c2c849148281fcf1d6a563c8bd5ddd4868d76e4a4f038cebd636003953cR150, I guess the reason for doing so is for debugging purposes.
@matz, can you tell us if you remember why?


[CHANGED] Added nats to the include directory during install [ci skip]

When doing make install, the header files are now copied under
the $CMAKE_INSTALL_PREFIX/include/nats.
Resolves #72

With this changes, a make install with a CMAKE_INSTALL_PREFIX set to /Users/ivan/dev/cnats/install results in this:
Install the project...
-- Install configuration: "Release"
-- Installing: /Users/ivan/dev/cnats/install/lib/libnats.dylib
-- Installing: /Users/ivan/dev/cnats/install/lib/libnats_static.a
-- Up-to-date: /Users/ivan/dev/cnats/install/include/nats/nats.h
-- Up-to-date: /Users/ivan/dev/cnats/install/include/nats/status.h
-- Up-to-date: /Users/ivan/dev/cnats/install/include/nats/version.h
-- Up-to-date: /Users/ivan/dev/cnats/install/include/nats/adapters/libevent.h
-- Up-to-date: /Users/ivan/dev/cnats/install/include/nats/adapters/libuv.h

@pritambaral I believe this change addresses your concerns. @dmpriso Hope this still works for you.
My concern is that users that previously did a make install and used the include directory for their apps will have to update all their apps to pick up the headers. More importantly, they may not know that they are still using the old ones. If I go with this PR, I intend to warn users in the release notes, but not sure if this the right direction. What do you guys think?

@kozlovic Yes, it does. In addition it also adds the adapter headers!
If worried about backwards compatibility, might I suggest a deprecation warning using the preprocessor?:
// include/nats.h
#ifndef __WIN32
#warning "`#include <nats.h>` is deprecated. Please use `#include <nats/nats.h>`"
#else
#pragma message ("`#include <nats.h>` is deprecated. Please use `#include <nats/nats.h>`")
#endif

#include <nats/nats.h>

@pritambaral Glad to know that this would work for you. I am a bit confused in your comment about preprocessor. Where would you want me to put this?
Keep in mind that the examples that I provide pickup the headers directly from the source code, so that would not help putting this in there.

I meant the old include location.
If loading $CMAKE_INSTALL_PREFIX/include/nats.h could automatically load the new $CMAKE_INSTALL_PREFIX/include/nats/nats.h, that would serve to be backwards compatible; but you probably want to move off the former, so you can put that deprecation notice as a compiler warning (where supported).

@kozlovic works for me, thanks!


Make SSL_alloc_buffers() and SSL_free_buffers() work again

The recent record layer refactor left SSL_alloc_buffers() and SSL_free_buffers() as no-ops. We make them work again.
While we are making changes to OSSL_RECORD_METHOD functions, we also remove a couple that were no-ops and never called.

Does this need a test?

24 hours has passed since 'approval: done' was set, but as this PR has been updated in that time the label 'approval: ready to merge' is not being automatically set.  Please review the updates and set the label manually.

If you add new code to fix something and the tests don't already fail, then there was no test :)

24 hours has passed since 'approval: done' was set, but this PR has failing CI tests.  Once the tests pass it will get moved to 'approval: ready to merge' automatically, alternatively please review and set the label manually.

The CI failure appears unrelated to this PR. Setting the "ready-to-merge" label.

Pushed. Thanks.


'asciidoctor-mathematical' could not be loaded

Hello.  everyone.
I want to write equations in my document.
When I executed this command:
$ asciidoctor-pdf --trace -r asciidoctor-mathematical -o test.pdf research.asciidoc

I got this error:
harumo@harumo-X250 ~/Documents/research $ asciidoctor-pdf --trace -r asciidoctor-mathematical -o test.pdf research.asciidoc
/usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- asciidoctor-mathematical (LoadError)
	from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /var/lib/gems/2.3.0/gems/polyglot-0.3.5/lib/polyglot.rb:65:in `require'
	from /usr/lib/ruby/vendor_ruby/asciidoctor/cli/options.rb:219:in `block in parse!'
	from /usr/lib/ruby/vendor_ruby/asciidoctor/cli/options.rb:217:in `each'
	from /usr/lib/ruby/vendor_ruby/asciidoctor/cli/options.rb:217:in `parse!'
	from /var/lib/gems/2.3.0/gems/asciidoctor-pdf-1.5.0.alpha.13/bin/asciidoctor-pdf:25:in `<top (required)>'
	from /usr/local/bin/asciidoctor-pdf:23:in `load'
	from /usr/local/bin/asciidoctor-pdf:23:in `<main>'

I know next to nothing about asciidoc. but I know that it is a great tool for writing.
What am I doing wrong?
Thanks in advance.

What is the result of:
asciidoctor -r asciidoctor-pdf -r asciidoctor-mathematical -b pdf -o test.pdf research.asciidoc

?

Hi. @ProgramFan
Bellow is my result.
harumo@harumo-X250 ~/Documents/research $ asciidoctor -r asciidoctor-pdf -r asciidoctor-mathematical -b pdf -o test.pdf research.asciidoc
asciidoctor: FAILED: 'asciidoctor-mathematical' could not be loaded
  Use --trace for backtrace

And When I use --trace option, I get following result.
harumo@harumo-X250 ~/Documents/research $ asciidoctor --trace -r asciidoctor-pdf -r asciidoctor-mathematical -b pdf -o test.pdf research.asciidoc
/usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- asciidoctor-mathematical (LoadError)
	from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /var/lib/gems/2.3.0/gems/polyglot-0.3.5/lib/polyglot.rb:65:in `require'
	from /var/lib/gems/2.3.0/gems/asciidoctor-1.5.5/lib/asciidoctor/cli/options.rb:219:in `block in parse!'
	from /var/lib/gems/2.3.0/gems/asciidoctor-1.5.5/lib/asciidoctor/cli/options.rb:217:in `each'
	from /var/lib/gems/2.3.0/gems/asciidoctor-1.5.5/lib/asciidoctor/cli/options.rb:217:in `parse!'
	from /var/lib/gems/2.3.0/gems/asciidoctor-1.5.5/lib/asciidoctor/cli/options.rb:33:in `parse!'
	from /var/lib/gems/2.3.0/gems/asciidoctor-1.5.5/lib/asciidoctor/cli/invoker.rb:22:in `initialize'
	from /var/lib/gems/2.3.0/gems/asciidoctor-1.5.5/bin/asciidoctor:12:in `new'
	from /var/lib/gems/2.3.0/gems/asciidoctor-1.5.5/bin/asciidoctor:12:in `<top (required)>'
	from /usr/local/bin/asciidoctor:23:in `load'
	from /usr/local/bin/asciidoctor:23:in `<main>'

My environment is as bellow.

os
ruby version
asciidoctor version

Ubuntu 16.04
2.3.1
1.5.5

I have never met this before. I use asciidoctor-mathematical on macOS and Fedora 24 with rvm, and have no experiences of ruby on ubuntu. So the following are my guesses.
I doubt your installation of asciidoctor-mathematical is not clean. You may have updated your system but asciidoctor-mathematical and its dependencies are not updated, so load errors can occur. Does remove asciidoctor-mathematical and mathematical and reinstall them work?

Please post the output of gem list | grep asciidoctor-mathematical
If you don't get any result from this command try running gem install asciidoctor-mathematical.

@ProgramFan @tstumm
I run gem list | grep asciidoctor-mathematical command, but I get no result.
Then, I run this:gem install asciidoctor-mathematical .
It shows below error message.
harumo@harumo-X250 ~ $ sudo gem install asciidoctor-mathematicalBuilding native extensions.  This could take a while...
ERROR:  Error installing asciidoctor-mathematical:
	ERROR: Failed to build gem native extension.

    current directory: /var/lib/gems/2.3.0/gems/mathematical-1.6.7/ext/mathematical
/usr/bin/ruby2.3 -r ./siteconf20161123-5639-zm8nop.rb extconf.rb
checking for cmake... yes
checking for main() in -lxml2... yes
checking for main() in -lpangocairo-1.0... yes
checking for libxml/tree.h in /include/libxml2,/usr/include/libxml2,/usr/local/include/libxml2... yes
checking for libxml/parser.h in /include/libxml2,/usr/include/libxml2,/usr/local/include/libxml2... yes
checking for libxml/xpath.h in /include/libxml2,/usr/include/libxml2,/usr/local/include/libxml2... yes
checking for libxml/xpathInternals.h in /include/libxml2,/usr/include/libxml2,/usr/local/include/libxml2... yes
-- The C compiler identification is GNU 5.4.0
-- The CXX compiler identification is GNU 5.4.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found BISON: /usr/bin/bison (found version "3.0.4")
-- Found FLEX: /usr/bin/flex (found version "2.6.0")
-- Performing Test COMPILER_HAS_HIDDEN_VISIBILITY
-- Performing Test COMPILER_HAS_HIDDEN_VISIBILITY - Success
-- Performing Test COMPILER_HAS_HIDDEN_INLINE_VISIBILITY
-- Performing Test COMPILER_HAS_HIDDEN_INLINE_VISIBILITY - Success
-- Performing Test COMPILER_HAS_DEPRECATED_ATTR
-- Performing Test COMPILER_HAS_DEPRECATED_ATTR - Success
-- Found PythonInterp: /usr/bin/python (found version "2.7.12")
-- Configuring done
-- Generating done
-- Build files have been written to: /var/lib/gems/2.3.0/gems/mathematical-1.6.7/ext/mathematical/mtex2MML/build
[ 11%] [FLEX][MTEX2MMLSCANNER] Building scanner with flex 2.6.0
[ 22%] [BISON][MTEX2MMLPARSER] Building parser with bison 3.0.4
/var/lib/gems/2.3.0/gems/mathematical-1.6.7/ext/mathematical/mtex2MML/src/parser.y: warning: 5270 shift/reduce conflicts [-Wconflicts-sr]
/var/lib/gems/2.3.0/gems/mathematical-1.6.7/ext/mathematical/mtex2MML/src/parser.y: warning: 613 reduce/reduce conflicts [-Wconflicts-rr]
Scanning dependencies of target libmtex2MML_static
[ 33%] Building C object CMakeFiles/libmtex2MML_static.dir/src/environment.c.o
In file included from /var/lib/gems/2.3.0/gems/mathematical-1.6.7/ext/mathematical/mtex2MML/src/environment.h:5:0,
                 from /var/lib/gems/2.3.0/gems/mathematical-1.6.7/ext/mathematical/mtex2MML/src/environment.c:7:
/var/lib/gems/2.3.0/gems/mathematical-1.6.7/ext/mathematical/mtex2MML/src/environment.c: In function ‘mtex2MML_perform_replacement’:
/var/lib/gems/2.3.0/gems/mathematical-1.6.7/ext/mathematical/mtex2MML/src/../deps/uthash/utarray.h:223:91: warning: signed and unsigned type in conditional expression [-Wsign-compare]
 #define utarray_eltidx(a,e) (((char*)(e) >= (a)->d) ? (((char*)(e) - (a)->d)/(a)->icd.sz) : -1)
                                                                                ^
/var/lib/gems/2.3.0/gems/mathematical-1.6.7/ext/mathematical/mtex2MML/src/../deps/uthash/utarray.h:221:62: note: in expansion of macro ‘utarray_eltidx’
 #define utarray_prev(a,e) (((e)==NULL) ? utarray_back(a) : ((utarray_eltidx(a,e) > 0) ? _utarray_eltptr(a,utarray_eltidx(a,e)-1) : NULL))
                                                              ^
/var/lib/gems/2.3.0/gems/mathematical-1.6.7/ext/mathematical/mtex2MML/src/environment.c:309:22: note: in expansion of macro ‘utarray_prev’
   while ( (o=(char**)utarray_prev(rowlines_stack,o))) {
                      ^
In file included from /var/lib/gems/2.3.0/gems/mathematical-1.6.7/ext/mathematical/mtex2MML/src/environment.h:5:0,
                 from /var/lib/gems/2.3.0/gems/mathematical-1.6.7/ext/mathematical/mtex2MML/src/environment.c:7:
/var/lib/gems/2.3.0/gems/mathematical-1.6.7/ext/mathematical/mtex2MML/src/../deps/uthash/utarray.h:223:91: warning: signed and unsigned type in conditional expression [-Wsign-compare]
 #define utarray_eltidx(a,e) (((char*)(e) >= (a)->d) ? (((char*)(e) - (a)->d)/(a)->icd.sz) : -1)
                                                                                ^
/var/lib/gems/2.3.0/gems/mathematical-1.6.7/ext/mathematical/mtex2MML/src/../deps/uthash/utarray.h:122:56: note: in definition of macro ‘_utarray_eltptr’
 #define _utarray_eltptr(a,j) ((a)->d + ((a)->icd.sz * (j)))
                                                        ^
/var/lib/gems/2.3.0/gems/mathematical-1.6.7/ext/mathematical/mtex2MML/src/../deps/uthash/utarray.h:221:107: note: in expansion of macro ‘utarray_eltidx’
 #define utarray_prev(a,e) (((e)==NULL) ? utarray_back(a) : ((utarray_eltidx(a,e) > 0) ? _utarray_eltptr(a,utarray_eltidx(a,e)-1) : NULL))
                                                                                ^
/var/lib/gems/2.3.0/gems/mathematical-1.6.7/ext/mathematical/mtex2MML/src/environment.c:309:22: note: in expansion of macro ‘utarray_prev’
   while ( (o=(char**)utarray_prev(rowlines_stack,o))) {
                      ^
In file included from /var/lib/gems/2.3.0/gems/mathematical-1.6.7/ext/mathematical/mtex2MML/src/environment.h:5:0,
                 from /var/lib/gems/2.3.0/gems/mathematical-1.6.7/ext/mathematical/mtex2MML/src/environment.c:7:
/var/lib/gems/2.3.0/gems/mathematical-1.6.7/ext/mathematical/mtex2MML/src/../deps/uthash/utarray.h:223:91: warning: signed and unsigned type in conditional expression [-Wsign-compare]
 #define utarray_eltidx(a,e) (((char*)(e) >= (a)->d) ? (((char*)(e) - (a)->d)/(a)->icd.sz) : -1)
                                                                                ^
/var/lib/gems/2.3.0/gems/mathematical-1.6.7/ext/mathematical/mtex2MML/src/../deps/uthash/utarray.h:221:62: note: in expansion of macro ‘utarray_eltidx’
 #define utarray_prev(a,e) (((e)==NULL) ? utarray_back(a) : ((utarray_eltidx(a,e) > 0) ? _utarray_eltptr(a,utarray_eltidx(a,e)-1) : NULL))
                                                              ^
/var/lib/gems/2.3.0/gems/mathematical-1.6.7/ext/mathematical/mtex2MML/src/environment.c:322:22: note: in expansion of macro ‘utarray_prev’
   while ( (p=(char**)utarray_prev(row_spacing_stack,p))) {
                      ^
In file included from /var/lib/gems/2.3.0/gems/mathematical-1.6.7/ext/mathematical/mtex2MML/src/environment.h:5:0,
                 from /var/lib/gems/2.3.0/gems/mathematical-1.6.7/ext/mathematical/mtex2MML/src/environment.c:7:
/var/lib/gems/2.3.0/gems/mathematical-1.6.7/ext/mathematical/mtex2MML/src/../deps/uthash/utarray.h:223:91: warning: signed and unsigned type in conditional expression [-Wsign-compare]
 #define utarray_eltidx(a,e) (((char*)(e) >= (a)->d) ? (((char*)(e) - (a)->d)/(a)->icd.sz) : -1)
                                                                                ^
/var/lib/gems/2.3.0/gems/mathematical-1.6.7/ext/mathematical/mtex2MML/src/../deps/uthash/utarray.h:122:56: note: in definition of macro ‘_utarray_eltptr’
 #define _utarray_eltptr(a,j) ((a)->d + ((a)->icd.sz * (j)))
                                                        ^
/var/lib/gems/2.3.0/gems/mathematical-1.6.7/ext/mathematical/mtex2MML/src/../deps/uthash/utarray.h:221:107: note: in expansion of macro ‘utarray_eltidx’
 #define utarray_prev(a,e) (((e)==NULL) ? utarray_back(a) : ((utarray_eltidx(a,e) > 0) ? _utarray_eltptr(a,utarray_eltidx(a,e)-1) : NULL))
                                                                                ^
/var/lib/gems/2.3.0/gems/mathematical-1.6.7/ext/mathematical/mtex2MML/src/environment.c:322:22: note: in expansion of macro ‘utarray_prev’
   while ( (p=(char**)utarray_prev(row_spacing_stack,p))) {
                      ^
[ 44%] Building C object CMakeFiles/libmtex2MML_static.dir/src/colors.c.o
[ 55%] Building C object CMakeFiles/libmtex2MML_static.dir/src/em.c.o
[ 66%] Building C object CMakeFiles/libmtex2MML_static.dir/src/string_extras.c.o
[ 77%] Building C object CMakeFiles/libmtex2MML_static.dir/parser.c.o
/var/lib/gems/2.3.0/gems/mathematical-1.6.7/ext/mathematical/mtex2MML/src/parser.y: In function ‘mtex2MML_yyerror’:
/var/lib/gems/2.3.0/gems/mathematical-1.6.7/ext/mathematical/mtex2MML/src/parser.y:56:30: warning: unused parameter ‘ret_str’ [-Wunused-parameter]
  static void yyerror (char **ret_str, const char * s)
                              ^
/var/lib/gems/2.3.0/gems/mathematical-1.6.7/ext/mathematical/mtex2MML/src/parser.y: At top level:
/var/lib/gems/2.3.0/gems/mathematical-1.6.7/ext/mathematical/mtex2MML/src/parser.y:68:14: warning: ‘mtex2MML_default_write’ defined but not used [-Wunused-function]
  static void mtex2MML_default_write (const char * buffer, unsigned long length)
              ^
/var/lib/gems/2.3.0/gems/mathematical-1.6.7/ext/mathematical/mtex2MML/src/parser.y:79:14: warning: ‘mtex2MML_default_write_mathml’ defined but not used [-Wunused-function]
  static void mtex2MML_default_write_mathml (const char * mathml)
              ^
[ 88%] Building C object CMakeFiles/libmtex2MML_static.dir/lexer.c.o
/var/lib/gems/2.3.0/gems/mathematical-1.6.7/ext/mathematical/mtex2MML/build/lexer.c: In function ‘yy_get_next_buffer’:
/var/lib/gems/2.3.0/gems/mathematical-1.6.7/ext/mathematical/mtex2MML/build/lexer.c:8042:23: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
   if ( number_to_move == YY_MORE_ADJ )
                       ^
/var/lib/gems/2.3.0/gems/mathematical-1.6.7/ext/mathematical/mtex2MML/build/lexer.c:8059:44: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
  if ((int) ((yy_n_chars) + number_to_move) > YY_CURRENT_BUFFER_LVALUE->yy_buf_size) {
                                            ^
/var/lib/gems/2.3.0/gems/mathematical-1.6.7/ext/mathematical/mtex2MML/src/lexer.l: At top level:
/var/lib/gems/2.3.0/gems/mathematical-1.6.7/ext/mathematical/mtex2MML/build/lexer.c:8178:16: warning: ‘input’ defined but not used [-Wunused-function]
     static int input  (void)
                ^
[100%] Linking C static library libmtex2MML.a
[100%] Built target libmtex2MML_static
-- The C compiler identification is GNU 5.4.0
-- The CXX compiler identification is GNU 5.4.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found PkgConfig: /usr/bin/pkg-config (found version "0.29.1")
-- Checking for module 'glib-2.0'
--   Found glib-2.0, version 2.48.1
-- Checking for module 'cairo'
--   Found cairo, version 1.14.6
-- Checking for module 'pango'
--   Found pango, version 1.38.1
-- Checking for module 'gdk-pixbuf-2.0'
--   Found gdk-pixbuf-2.0, version 2.32.2
-- Checking for module 'libxml-2.0'
--   Found libxml-2.0, version 2.9.3
-- Checking for module 'gio-2.0'
--   Found gio-2.0, version 2.48.1
-- Checking for module 'pangocairo'
--   Found pangocairo, version 1.38.1
-- Configuring done
-- Generating done
-- Build files have been written to: /var/lib/gems/2.3.0/gems/mathematical-1.6.7/ext/mathematical/lasem/build
Scanning dependencies of target lasem
[  0%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmsvglineelement.c.o
[  1%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmsvgfilterconvolvematrix.c.o
[  2%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmdebug.c.o
[  3%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmtraits.c.o
[  4%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmsvglineargradientelement.c.o
[  5%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmmathmlspaceelement.c.o
[  6%] Building C object CMakeFiles/lasem.dir/lasem/src/lsm.c.o
[  7%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmsvggelement.c.o
[  8%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmsvgfiltercomposite.c.o
[  9%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmsvguseelement.c.o
[  9%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmmathmlalignmarkelement.c.o
[ 10%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmsvgfiltercolormatrix.c.o
[ 11%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmsvgpatternelement.c.o
[ 12%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmsvgimageelement.c.o
[ 13%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmsvgtspanelement.c.o
[ 14%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmsvgfilterblend.c.o
[ 15%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmsvgfiltersurface.c.o
[ 16%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmsvggradientelement.c.o
[ 17%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmsvgfilterspecularlighting.c.o
[ 18%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmmathmlattributes.c.o
[ 18%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmdomentities.c.o
[ 19%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmmathmlstyle.c.o
[ 20%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmmathmlpresentationtoken.c.o
[ 21%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmdomelement.c.o
[ 22%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmproperties.c.o
[ 23%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmsvgenums.c.o
[ 24%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmcairo.c.o
[ 25%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmstr.c.o
[ 26%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmsvgstyle.c.o
[ 27%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmmathmllayoututils.c.o
[ 27%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmmathmlerrorelement.c.o
[ 28%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmmathmlview.c.o
[ 29%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmmathmltraits.c.o
[ 30%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmdomtext.c.o
[ 31%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmsvgfilterimage.c.o
[ 32%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmsvgtextelement.c.o
[ 33%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmmathmlfractionelement.c.o
[ 34%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmutils.c.o
[ 35%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmsvgpathelement.c.o
[ 36%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmsvgcircleelement.c.o
[ 36%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmmathmlaligngroupelement.c.o
[ 37%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmmathmlunderoverelement.c.o
[ 38%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmmathmlenums.c.o
[ 39%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmsvgmaskelement.c.o
[ 40%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmsvgfiltermerge.c.o
[ 41%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmsvgmarkerelement.c.o
[ 42%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmsvgfiltergaussianblur.c.o
[ 43%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmsvgmatrix.c.o
[ 44%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmsvgswitchelement.c.o
[ 45%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmmathmlelement.c.o
[ 45%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmsvgrectelement.c.o
[ 46%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmmathmlglyphtableams.c.o
[ 47%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmmathmlrowelement.c.o
[ 48%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmsvgpolygonelement.c.o
[ 49%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmdomparser.c.o
[ 50%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmsvgsvgelement.c.o
[ 51%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmmathmlscriptelement.c.o
[ 52%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmmathmlencloseelement.c.o
[ 53%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmmathmltableelement.c.o
[ 54%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmmathmlutils.c.o
[ 54%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmattributes.c.o
[ 55%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmsvgfiltermergenode.c.o
[ 56%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmsvgfilterelement.c.o
[ 57%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmsvgfiltertile.c.o
[ 58%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmdomnodelist.c.o
[ 59%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmsvgpolylineelement.c.o
[ 60%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmsvgsymbolelement.c.o
[ 61%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmmathmlmathelement.c.o
[ 62%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmmathmlsemanticselement.c.o
[ 63%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmsvgaelement.c.o
[ 63%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmmathmloperatorelement.c.o
[ 64%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmsvgclippathelement.c.o
[ 65%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmsvgfilterturbulence.c.o
[ 66%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmmathmlstringelement.c.o
[ 67%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmdomimplementation.c.o
[ 68%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmdomdocumentfragment.c.o
[ 69%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmmathmlstyleelement.c.o
[ 70%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmmathmloperatordictionary.c.o
[ 71%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmsvgcolors.c.o
[ 72%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmmathmlfencedelement.c.o
[ 72%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmsvgfiltermorphology.c.o
[ 73%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmmathmldocument.c.o
[ 74%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmsvgfilterdisplacementmap.c.o
[ 75%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmsvglength.c.o
[ 76%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmmathmlpaddedelement.c.o
[ 77%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmmathmlradicalelement.c.o
[ 78%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmsvgelement.c.o
[ 79%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmsvgfilterprimitive.c.o
[ 80%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmsvgdefselement.c.o
[ 81%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmmathmltablerowelement.c.o
[ 81%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmsvgellipseelement.c.o
[ 82%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmsvgtraits.c.o
[ 83%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmdomdocument.c.o
[ 84%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmsvgtransformable.c.o
[ 85%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmsvgradialgradientelement.c.o
[ 86%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmmathmlphantomelement.c.o
[ 87%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmmathmlitexelement.c.o
[ 88%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmsvgview.c.o
[ 89%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmmathmlactionelement.c.o
[ 90%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmdomview.c.o
[ 90%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmdomcharacterdata.c.o
[ 91%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmdomnode.c.o
[ 92%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmmathmlpresentationcontainer.c.o
[ 93%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmsvgdocument.c.o
[ 94%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmsvgfilterflood.c.o
[ 95%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmdomnamednodemap.c.o
[ 96%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmsvgfilteroffset.c.o
[ 97%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmsvgstopelement.c.o
[ 98%] Building C object CMakeFiles/lasem.dir/lasem/src/lsmmathmltablecellelement.c.o
[ 99%] Building C object CMakeFiles/lasem.dir/lasem_overrides.c.o
[100%] Linking C shared library liblasem.so
[100%] Built target lasem
checking for mtex2MML.h in /var/lib/gems/2.3.0/gems/mathematical-1.6.7/ext/mathematical/mtex2MML/src... yes
creating Makefile

To see why this extension failed to compile, please check the mkmf.log which can be found here:

  /var/lib/gems/2.3.0/extensions/x86_64-linux/2.3.0/mathematical-1.6.7/mkmf.log

current directory: /var/lib/gems/2.3.0/gems/mathematical-1.6.7/ext/mathematical
make "DESTDIR=" clean

current directory: /var/lib/gems/2.3.0/gems/mathematical-1.6.7/ext/mathematical
make "DESTDIR="
compiling cairo_callbacks.c
compiling lasem_overrides.c
In file included from /usr/include/string.h:630:0,
                 from /var/lib/gems/2.3.0/gems/mathematical-1.6.7/ext/mathematical/mtex2MML/src/../deps/uthash/uthash.h:29,
                 from /var/lib/gems/2.3.0/gems/mathematical-1.6.7/ext/mathematical/mtex2MML/src/environment.h:4,
                 from /var/lib/gems/2.3.0/gems/mathematical-1.6.7/ext/mathematical/mtex2MML/src/mtex2MML.h:12,
                 from lasem_overrides.c:5:
/var/lib/gems/2.3.0/gems/mathematical-1.6.7/ext/mathematical/mtex2MML/src/../deps/uthash/../strdup/strdup.h:24:1: error: expected identifier or ‘(’ before ‘__extension__’
 strdup(const char *str);
 ^
Makefile:239: recipe for target 'lasem_overrides.o' failed
make: *** [lasem_overrides.o] Error 1

make failed, exit code 2

Gem files will remain installed in /var/lib/gems/2.3.0/gems/mathematical-1.6.7 for inspection.
Results logged to /var/lib/gems/2.3.0/extensions/x86_64-linux/2.3.0/mathematical-1.6.7/gem_make.out

I also tried to remove and re-install asciidoctor and asciidoctor-mathematical.
But, I got same result.

See https://github.com/gjtorikian/mathematical/issues/64

Since this is not a problem of asciidoctor-mathematical, I will close this issue, but feel free to ask new questions.

Thank you.
I solved the problem.

Can you please document this in the README?

I can confirm that the fix proposed by Garen works, but it would have saved me time had I seen it in the README first.

This fix does not work on macOS Mojave 10.14, and the gem does not work on it. I've reported this to the mathematical maintainers too.

This shall go to mathematical indeed. I don't understand why someone would override strdup. This type of tricks always introduces nasty bugs and compatibility problems.


re-enable read-only port on kubelet

fixes heapster connection issues

What this PR does / why we need it: Re-enables kubelet read-only-port, which our current heapster configuration needs.
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #2083
Release note:

re-enable read-only port on kubelet to fix heapster

@jackfrancis do we still need this --read-only-port to let heapster collect kubelet info?
cc @leifei87 @feiskyer

Update:
per https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG-1.13.md, heapster is retired in v1.13, let me disable read-only-port in aks-engine.
BTW, here is the background: I am now doing the CIS benchmark conformance work, will bother you @jackfrancis from time to time about some config issue.


reset point when drop the view

How to reset the Point when drop the view?

Hi @anafinotti
I'm not sure I understand the question, can you elaborate a bit?


Swagger UI Doesn't Report Required Fields Correctly

Not sure if this is global or specific to power-feeds status but I also checked devices and status is not required there either in swagger.
Environment

Python version: 3.6
Nautobot version: 1.0b3

Steps to Reproduce

Go to the swagger UI
Look for POST POST /dcim/power-feeds/
Look under parameters in the model view, status is shown as not required

Expected Behavior
Status should have a required * as it is a required field.

Observed Behavior
Swagger shows it as not required

Thanks @nniehoff for reporting this. Interestingly it's marked as non-required field in the serializer mixin, but obviously that's now how it is behaving:
https://github.com/nautobot/nautobot/blob/develop/nautobot/extras/api/serializers.py#L611-L614

It's because of model validation. The field not being required is overridden by the fact that the field is required when the model is validated.

Updating the link: https://github.com/nautobot/nautobot/blob/develop/nautobot/extras/api/serializers.py#L873 (StatusModelSerializerMixin). It probably should be required=True - maybe just change this and test to see what breaks?


Suggestion

First of all thanks and congrats for the innovative project.
Currently the compiled firmware (I mean /build/rp2daq.uf2 file) is placed inside the project files. I would like to suggest you to publish the compiled binary file as a release file. I think this is how usually the binary files are published in github.
also the version control would be easier and files can be visible from release section:
https://github.com/FilipDominec/rp2daq/releases

Thanks, I will do it like yuo describe. Currently, the automatic push of new binary firmware on every ABI change is inefficient.

Done. For the latest current version of the pre-compiled firmware, please always refer to the link:

https://github.com/FilipDominec/rp2daq/releases/latest/download/rp2daq.uf2

I also updated README.md to reflect this.
Thanks for your suggestion.

Wonderful.
I should put a check for firmaware version in scope. Does the returned firmaware version from PICO do change for each individual release?

It should represent the latest date the firmware ABI was updated (breaking binary compatibility), but haven't been overly conscientious about it in previous months.
Anyway, the latest release as well as current git version of rp2daq return human-readable 6-byte string "231005".

ok, thanks


PHX farming should not have Add Liquidity button since it was single token farming

Yes you are right, the mainnet version it will be cCFX/CFX

Yes you are right, the mainnet version it will be cCFX/CFX


bug: switchNetwork not working for BSC mainnet

Is there an existing issue for this?

[X] I have searched the existing issues

Package Version
"@wagmi/core": "^0.8.19",
Current Behavior
Suddenly switchNetwork function is not working when a user changing the network from Ethereum Mainnet to BSC mainnet. It was working fine earlier (5 days ago). It is working fine if a user change the network manually via metamask browser extension.
It is also working fine if a user change his network from BSC mainnet to Ethereum Mainnet.
It is not a coading issue because I am facing the same issue on all my live projects ( approx 5 projects).
Below I am pasting the issue:
Error switching chain     at chunk-YUNHZJBB.js:275:13     at Generator.throw (<anonymous>)     at asyncGeneratorStep (asyncToGenerator.js:3:1)     at _throw (asyncToGenerator.js:29:1)     at _ZoneDelegate.invoke (zone.js:372:26)     at Object.onInvoke (core.mjs:26274:33)     at _ZoneDelegate.invoke (zone.js:371:52)     at Zone.run (zone.js:134:43)     at zone.js:1275:36     at _ZoneDelegate.invokeTask (zone.js:406:31)
Expected Behavior
It should change the network smoothly.
Steps To Reproduce

Open link https://lovehateinu.com/en
Click on BUY NOW button.
Select MEtamask from the opened modal.
Now click on the Buy with BNB button at the bottom of the  center block.
You can check the status on console panel too of inspect element mode.

Link to Minimal Reproducible Example (StackBlitz, CodeSandbox, GitHub repo etc.)
No response
Anything else?
No response

We have the same problem, the network switch does not work properly. Before, everything worked correctly

This is a MetaMask issue. The newest version of MetaMask has the fix. Doesn't seem to be published yet, but hopefully soon.
https://github.com/MetaMask/metamask-extension/releases/tag/v10.28.3


Headless Ghidrathon extension installation

After building the extension, Ghidra's documentation tells us to unzip it in the $GHIDRA_INSTALL_DIR/Extensions diretory; however, putting it in this directory only gives it visibility to perform the actual installation via the gui. To avoid having to configure the extension in the gui, we must extract the zip to ~/.ghidra/.ghidra_<version>/Extensions

note: The Extensions folder will not be present in the hidden directories (.ghidra*), so we must manually create it before/ during the extraction process

Invocation of the headlessAnalyzer should now be using Ghidrathon to process python scripts instead of the default Jython plugin.

perhaps we should discuss this with upstream Ghidra devs to hear their input. the above sounds like it should work and probably won't often be broken; therefore, can we rely on it? can it be documented as part of Ghidra's behavior?
i dont think its really bad if its not documented yet still works - its just something we need to remember and document internally, in case things break later on.

here's a link to the implementation of extension installation, and its just as you said:
https://github.com/NationalSecurityAgency/ghidra/blob/9ec89c37fb30d6228ed82d4cf1441b7a7aa0a3f1/Ghidra/Framework/Project/src/main/java/ghidra/framework/plugintool/dialog/ExtensionUtils.java#L788-L801

I've found extracting to $GHIDRA_INSTALL_DIR/Ghidra/Extensions also works.

I'm not quite sure. I went through the full installation process once a while back, and after upgrading to Ghidra 10.3 tried to do it again. I did open the GUI after that, but found that I didn't need to set anything else up. I can try this again and see if headless mode works without opening the GUI though.

I've found extracting to $GHIDRA_INSTALL_DIR/Ghidra/Extensions also works.

@rchtsang did you find that you could use Ghidrathon in Ghidra headless mode w/out first configuring the extension via Ghidra's UI?

Also, in that case, what about disabling the jython support, should that work fine? I don't have an access to the GUI at all.

That I’m not sure about, it’s possible there are some locally stored
configurations that I’m unaware of, but I removed ~/.ghidra on uninstall
and ghidrathon still worked on reinstall, so if there’s anything beyond
that I should be removing for fresh install let me know and I can try it.
On Sat, Jun 17, 2023 at 4:31 PM Ruturaj Vaidya @.***>
wrote:

I've found extracting to $GHIDRA_INSTALL_DIR/Ghidra/Extensions also works.
@rchtsang https://github.com/rchtsang did you find that you could use
Ghidrathon in Ghidra headless mode w/out first configuring the extension
via Ghidra's UI?
Also, in that case, what about disabling the jython support, should that
work fine? I don't have an access to the GUI at all.
—
Reply to this email directly, view it on GitHub
https://github.com/mandiant/Ghidrathon/issues/47#issuecomment-1595887112,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARLERGFZ6DH3XVLRZK76MIDXLY43ZANCNFSM6AAAAAAY7SGIYE
.
You are receiving this because you were mentioned.Message ID:
@.***>

Btw, I just tested that with my script and it works fine! Thanks for the great project!

I've found extracting to $GHIDRA_INSTALL_DIR/Ghidra/Extensions also works.

Apparently the difference between $GHIDRA_INSTALL_DIR/Extensions and $GHIDRA_INSTALL_DIR/Ghidra/Extensions matters here. The official document refers to the later on.
The  <GhidraInstallDir>/Extensions are "by default uninstalled" according to the same manual a few lines above.

Thanks all - I've update Ghidrathon's README to specify unzip to $GHIDRA_INSTALL_DIR/Ghidra/Extensions as the preferred method for installing Ghidrathon w/out using Ghidra's UI.


File/Print is missing

Issue Type: Feature Request
File/Print is missing
VS Code version: Code 1.49.0 (e790b931385d72cf5669fcefc51cdf65990efa5d, 2020-09-10T13:22:08.892Z)
OS version: Windows_NT x64 10.0.19041

/duplicate of #5953


Include 3MF versions?

3MF is lightweight, portable, and a heck of a lot better than STL ;) @andreasbastian, let me know if I can help generating the files (if you're open to including them)!

That's a great idea!  I haven't worked with 3MF much, want to maybe create a 3MF version of the geometry and then submit a pull request?  I assume 3MF is most useful when you convert from a STEP or other more data-rich format than STL, is the f3d file a reasonable place to start or should I send you a STEP/IGES?

@andreasbastian yeah, starting from CAD would make the most sense. Want to attach one here?

@andreasbastian thanks! So, a question. 3MF has a concept of "objects," described here. Since this is a multi-body part, there are a few ways we can describe it:

As a 6-object part, each of which contains a single-shelled mesh
As a single object part, which contains a 6-shelled mesh

(We could also be fancy and use "components", in which case we would have a 2-object part, one of which is a component which is repeated 5 times with transforms. This would be slick but maybe a little too clever for the intended use.)
I'm attaching screenshots from Element - see the object browser for a sense of how this works. Which do you think is more appropriate for the application? The actual 3MF files (which you can also open in Element, Meshmixer, Netfabb, etc) are attached as well.

3mf options.zip

Nice, I think that the single object 3mf version will be best here to ensure that the cylindrical pins always stay in the exact same positions relative to the main body.  Had I modeled this so that the holes that the pins reside in change diameter, using the component trick would have been slick, but I change the pin diameters, so each has to stay in its respective hole.
Is there anything else that you'd like to change in the "one object.3mf" file or should I rename it "ksr_fdmtest_v4.3mf" and add it to the FDM protocol folder?  Thanks again for making the file!

Ah ah! Sorry I didn't notice the differing sizes.
I'll make the PR in just a minute!


[Slider] Remove unnecessary data-focusvisible attribute

[x] I have followed (at least) the PR section of the contributing guide.

Resolves comment https://github.com/mui/material-ui/pull/35770#discussion_r1096788745. Even I don't see it being used anywhere.
It's not documented, so I guess it's not a breaking change.

It looks OK to me, but let's wait for @mnajdova's opinion.


Adding more memory?

Is it possible to add more memory/disk to cf dev (like it was possible in the old pcfdev were you could pass some options to the 'start' command to create larger VM to run it on)?
I tried cf dev --help, cf dev start --help but no information about this.
I also read the readme here: https://github.com/cloudfoundry-incubator/cfdev/blob/master/README.md

The help commands can be accessed like so:
cf dev help start

You cannot configure the disk size but you can configure the memory with the -m flag, much like before.
cf dev start -m 20000


Pagination Data Format

I am attempting to manually set the data on the table and the pagination data is coming back null here. I was attempting to use the default "links.pagination" path. Here is a sample payload:
{
   "links":{
      "pagination":{
         "total":7982,
         "per_page":20,
         "current_page":1,
         "last_page":400,
         "next_page_url":"...",
         "prev_page_url":"...",
         "from":1,
         "to":20
      }
   },
   "data":[...]
}

I was using this as a guide. You can check the codepen. I will manually override the path for the time being.

@DevinWatson The problem is that your Data Manager function still return the old structure, not the one that you've changed. If you change it as below, it'll work.
// index.js
  //...
  methods: {
    //...
    dataManager (sortOrder, pagination) {
      //...
      return {
        links: { pagination: pagination },
        data: _.slice(data, pagination.from-1, pagination.to)
      }
    }
  }

The process of using the Data mode needs to be look into further as I still feel something doesn't really make sense. Unfortunately, I'm quite occupied with other works at the moment.


HPX_WITH_CUDA corrupts compilation flags

When CUDA is enabled, definitions are added to the compilation regardless of Debug/Release/Other mode and cause incorrect flags to be passed to the compiler.
The lines of code here
https://github.com/STEllAR-GROUP/hpx/blob/master/cmake/HPX_AddCompileFlag.cmake#L33-L35
are the problem.
This results in _DEBUG and DEBUG flags being passed to release builds - which in hpx/config.h trigger HPX_DEBUG to be set and from there, everything is wrong.

NB. the lines https://github.com/STEllAR-GROUP/hpx/blob/master/cmake/HPX_AddCompileFlag.cmake#L88-L90
are also a problem


pip.download cannot be found any more

https://github.com/pypa/setuptools/issues/1080

https://github.com/steenzout/python-object/pull/2

fixed by #28 .


Update peerDependencies to Angular 8+

Hi, could you please update peerDependencies to Angular 8+?
I have no problems running your component with this version, but i just have noisy npm warnings.
Thank you,
Alessandro

Fixed in d7d38fa3f3cf3496a8db68d13a25631c6dd1ae76 👍


To do List

Device type and model (or SN)
To do List
The description of new feature

[x]  1. fork and sync with new code changes   [done]
[x] 2. add github action to auto release midea_ac_lan.zip  [done]
[x] 3. add more Collaborator in current repo   [done]
[ ] 4. remove old midea_ac_lan from HACS default integration
[ ] 5. add new midea_ac_lan repo to HACS default integration
[ ] 6. add github action lint  all the codes in PR, also include old source code linter error fix.
[ ] 7.

Stauts update:
job 4: remove old midea_ac_lan from HACS
I have submit issue and PR：
https://github.com/hacs/integration/issues/3682
https://github.com/hacs/default/pull/2504
it may cost more time to finished job 4 and job 5
once job 4 done ,  I will add new forked repo to HACS default integration later.
Job 6,  in progress, i will fix  some linter erro with all the old source code, once it down , I will deploy to mater branch and used by all PR and future.

Hello, if there is an update from the previous developer, how do I install this version?

Hello, if there is an update from the previous developer, how do I install this version?

I'm not sure with the upate, if he can continue maintain it, he can merge current chagnes in this repo, and we also can merge the new changes from any repo.
Don't need to worry about this issue

The translation was bad. I meant how to install your repo. I noticed that the salaries function to program activation times is missing.

The translation was bad. I meant how to install your repo. I noticed that the appointements function to program activation times is missing.

got it, you mean how to manual install with current repo.
i have submit hacs PR to remove old repo and add current repo, seems it will cost a long time, there is too many PR pending and I'm not sure with the finish time now.
but I will continue to push it to hacs official repo based on the official progress.
in addition, I have upate the README docs in current repo, you can check the detail and confirm with it:
installation
if there is any new issue,  I think we can file new issue to track with it.
then we can use issue to track the bug and quickly fix it via PR.

thank you for the explanations I was able to go to your repository.  do you know how to retrieve the programming like on the Smarthome application?  failing that I did it via the on and off button but if I can leave the water heater on without it heating up that would be a real added value thank you for the work provided

What about using a Discord group for easier communication ?
My contact is : chemelli74#2180

What about using a Discord group for easier communication ?
My contact is : chemelli74#2180

Thank you very much , I have request to add you as friend, my username is wuwentao2000,  and I also create a init discord group: https://discord.com/invite/ZWdd2fXndn
finished init setting and no any more changes, we can have a try.

I've already connected and did request friend.


TypeError: softmax() got an unexpected keyword argument 'axis'

I ran my code ran without any error back to November 2017. This error happened after updated to 2.1.5. Please help. Thank you.
`---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
 in ()
89 model.add(Dropout(0.5))
90 model.add(Dense(num_classes))
---> 91 model.add(Activation('softmax'))
92
93 # -----------------------------------------------------------
/usr/local/lib/python2.7/dist-packages/keras/models.pyc in add(self, layer)
490                           output_shapes=[self.outputs[0]._keras_shape])
491         else:
--> 492             output_tensor = layer(self.outputs[0])
493             if isinstance(output_tensor, list):
494                 raise TypeError('All layers in a Sequential model '
/usr/local/lib/python2.7/dist-packages/keras/engine/topology.pyc in call(self, inputs, **kwargs)
617
618             # Actually call the layer, collecting output(s), mask(s), and shape(s).
--> 619             output = self.call(inputs, **kwargs)
620             output_mask = self.compute_mask(inputs, previous_mask)
621
/usr/local/lib/python2.7/dist-packages/keras/layers/core.pyc in call(self, inputs)
301
302     def call(self, inputs):
--> 303         return self.activation(inputs)
304
305     def get_config(self):
/usr/local/lib/python2.7/dist-packages/keras/activations.pyc in softmax(x, axis)
27     ndim = K.ndim(x)
28     if ndim == 2:
---> 29         return K.softmax(x)
30     elif ndim > 2:
31         e = K.exp(x - K.max(x, axis=axis, keepdims=True))
/usr/local/lib/python2.7/dist-packages/keras/backend/tensorflow_backend.pyc in softmax(x, axis)
2957         A tensor.
2958     """
-> 2959     return tf.nn.softmax(x, axis=axis)
2960
2961
TypeError: softmax() got an unexpected keyword argument 'axis'`

I got exactly the same error by running an example code from your site (https://github.com/keras-team/keras/blob/master/examples/cifar10_resnet.py)
`---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
 in ()
322     model = resnet_v2(input_shape=input_shape, depth=depth)
323 else:
--> 324     model = resnet_v1(input_shape=input_shape, depth=depth)
325
326 model.compile(loss='categorical_crossentropy',
 in resnet_v1(input_shape, depth, num_classes)
219     outputs = Dense(num_classes,
220                     activation='softmax',
--> 221                     kernel_initializer='he_normal')(y)
222
223     # Instantiate model.
/usr/local/lib/python2.7/dist-packages/keras/engine/topology.pyc in call(self, inputs, **kwargs)
617
618             # Actually call the layer, collecting output(s), mask(s), and shape(s).
--> 619             output = self.call(inputs, **kwargs)
620             output_mask = self.compute_mask(inputs, previous_mask)
621
/usr/local/lib/python2.7/dist-packages/keras/layers/core.pyc in call(self, inputs)
857             output = K.bias_add(output, self.bias)
858         if self.activation is not None:
--> 859             output = self.activation(output)
860         return output
861
/usr/local/lib/python2.7/dist-packages/keras/activations.pyc in softmax(x, axis)
27     ndim = K.ndim(x)
28     if ndim == 2:
---> 29         return K.softmax(x)
30     elif ndim > 2:
31         e = K.exp(x - K.max(x, axis=axis, keepdims=True))
/usr/local/lib/python2.7/dist-packages/keras/backend/tensorflow_backend.pyc in softmax(x, axis)
2957         A tensor.
2958     """
-> 2959     return tf.nn.softmax(x, axis=axis)
2960
2961
TypeError: softmax() got an unexpected keyword argument 'axis'`

@Weixing-Zhang Which Tensorflow version are you using?

@srjoglekar246  thanks for your response. I'm using tensorflow-gpu 1.4.0. My keras couldn't load a model when I had the latest version installed. That's why I downgraded it from 1.5.0 to 1.4.0.

Aah. Seems like softmax in TF 1.4 did not support axis as an argument :-/

Seems like I better off upgrading everything. I'll keep my result posted.

srjoglekar246  was right. I upgraded tf-gpu to 1.6, cuda to 9.0, and cudnn to 7.0 and everything worked as normal.

Hi,
I get the same problem but I got a better solution.
Just downgrade the tensorflow and keras.
My previous tensorflow version is 1.4.1 and keras version 2.1.5.
I downgrade to tensorflow version 1.4.0 and keras version 2.0.8.
The error doesn't appear anymore.

@fitrialif - Just curious - why do you think downgrade is a better alternative than upgrade?

It works after upgrading TF:  1.7.0 and Keras: '2.1.5'

I ran into the same issue! But why isn't this handled in the pip package of Keras? Can't it point to specific TF versions as dependencies?

@ambodi
You have to make sure your Keras is up-to-date.
This is what I did: I upgraded tensorflow-gpu to 1.6, cuda to 9.0 (Not 9.0.5 or others), and cudnn to 7.0.
Finally, for python 2.x $ sudo pip install --upgrade keras
for python 3.x $ sudo pip3 install --upgrade keras

hello all!
I am currently working with raspberry pi 3. I have already installed tensorflow version 1.1.0 and keras 2.1.5!But the error TypeError: softmax() got an unexpected keyword argument 'axis'`occurs. I am not able to move further. What should I do? If i have to upgrade my tensorflow version, how do i do it? I need help please

@shouvik10 , can you try updating the TF version using apt-get or something similar?

@srjoglekar246 hey I've tried that too. Its not working :(

pip3 install --upgrade keras==2.1.3
Made it for me. Tensorflow version 1.4

On one hand, it seems like 1.4 shouldn't work since (I thought...) axis wasn't introduced until later. That being said, I've tried all of the versions mentioned in this thread, as well as the latest of both TF and Keras, and still receive this error. I'll look under the hood, but it'd be nice if someone more familiar with the interfacing of the two could jump in on this.

Getting this same error on gcloud using Keras 2.1.6.  Switched to keras==2.1.3 and it seems to work just fine.

I am using tensorflow in anaconda. keras version is 2.1.6 and tensorflow version is 1.1.0. I upgrades tensorflow (1.8.0) through terminal. But in anaconda it is showing that the tensorflow version is 1.1.0.  Could not get rid of the error TypeError: softmax() got an unexpected keyword argument 'axis'

I am working with anaconda. Tensorflow version is 1.1.0 and keras version is 2.1.6. Tried all the options here. But did not work out for me. What else can I do? Thanks in advance!

Hi, I have Mac OS. What I did was uninstall keras version 2.1.6 and installed version 2.1.3 as @JaviFuentes94 suggested and it started working.

just upgrade tensorflow to the latest version.
$ sudo pip3 install --upgrade tensorflow
works without any issues with tensorflow 1.8.0 and keras 2.1.6

My previous tensorflow version is 1.4.2 and keras version is the newest version (with cuda8.0, cudnn 6.0, and python2.7).
I downgrade to tensorflow version 1.4.0 and keras version 2.0.8. It works.

Easiest way to get rid of the error is to directly use softmax function from tensorflow
from keras import backend as K
model.add(Lambda(lambda x: K.tf.nn.softmax(x)))

It works with keras=2.0.8, tensorflow=1.3.0 without upgrade/degrade

@starfleet1702  you are right.
This must be a matrix compat. issue, keras should check the version of tensorflow to use the correct syntax.

Same problem with RaspberryPi 3. I trained the model on my PC using Tensorflow 1.6.0 and Keras 2.1.5 and saved the model using model_from_json.
When I load the model on RaspberryPi3, it shows softmax got unexpected keyword axis.
RaspberryPi3 currently run Tensorflow 1.1.0 and Keras 2.1.5.
Any help is appreciated.

Update: seems like if you downgrade Keras to a version which was used to create the model like in my case I downgraded Keras from 2.1.6 to 2.1.5, it worked! Model was loaded successfully on Raspberry Pi3 created on my PC.
Currently I have:
PC -->TF 1.6.0 and Keras 2.1.5
Pi3 -->TF 1.1.0 and Keras 2.1.5
If this help you please add a comment. I am looking forward for a better solution if anybody has it.

Hello, gents,
I have the similar problem:
Cuda: 8
tf: 1.4 (cause of Cuda, I cant upgrade it)
keras: 2.2
Keras-Applications==1.0.2
Keras-Preprocessing==1.0.1
If I downgrade keras I get errors about keras-application and keras-preprocessing needs more freshly keras:
keras-applications 1.0.2 has requirement keras>=2.1.6, but you'll have keras 2.1.5 which is incompatible.
keras-preprocessing 1.0.1 has requirement keras>=2.1.6, but you'll have keras 2.1.5 which is incompatible.

Is there any table version compatibility between keras+tensorflow?
The example of what I looking for might be such information: https://www.tensorflow.org/install/install_sources#tested_source_configurations

sudo pip install --force-reinstall keras==2.1.3

you can add softmax layer in this fashion and will work:
first:
import tensorflow as tf
then, within you model definition:
model.add(Activation(tf.nn.softmax))

Confirming that @saeeron's solution works on a Raspberry Pi without having to downgrade anything. Bit annoying, though, that the TF version for it is so far behind (at least as far as pip is concerned).

  I've tried 'upgrading' everything and it broke all kinds of other things that were working. It would be nice if the pythonistas added functionality WITHOUT breaking earlier versions (why I love 'go'). I spend way too much time trying to get the 'right' version for all these fantastic Python libraries to play nice together: very frustrating.

@davmaz I feel your pain, for sure. Sometimes I have to set a project aside for a few days until it feels less burdensome. The main reason we run into this so much is that we're working with rapidly developing libraries, right. we could do menial data manipulation all day with the seldom-changing Numpy, but this stuff is way more exciting... and yeah... the update-frustration is the price.  you're not alone! but at least we get to be frustrated while working with such neat stuff!

When I downgrade my tensorflow version to 1.8.0, the problem was solved.

I just edited tensorflow_backend.pyc return tf.nn.softmax(x, axis=axis) to return tf.nn.softmax(x, axis)

The problem is still there. I'm using Keras 2.2.2 and TF 1.2.1. I'll revert. Please fix this :)

Please downgrade your keras to 2.2.0. And upgrade tensorflow version to
1.8.0.
2018년 9월 4일 (화) 오후 11:12, Maj Smerkol<EMAIL_ADDRESS>작성:

The problem is still there. I'm using Keras 2.2.2 and TF 1.2.1. I'll
revert. Please fix this :)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/keras-team/keras/issues/9621#issuecomment-418381671,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APXRVItQ075zHLyOnsOaOTeAQvkfh3hWks5uXopGgaJpZM4Sl-Su
.

@hakex Why should people downgrade their Keras version? This would not be an elegant approach.

I ran my code ran without any error back to November 2017. This error happened after updated to 2.1.5. Please help. Thank you.
`---------------------------------------------------------------------------
TypeError Traceback (most recent call last)
in ()
89 model.add(Dropout(0.5))
90 model.add(Dense(num_classes))
---> 91 model.add(Activation('softmax'))
92
93 # -----------------------------------------------------------
/usr/local/lib/python2.7/dist-packages/keras/models.pyc in add(self, layer)
490 output_shapes=[self.outputs[0]._keras_shape])
491 else:
--> 492 output_tensor = layer(self.outputs[0])
493 if isinstance(output_tensor, list):
494 raise TypeError('All layers in a Sequential model '
/usr/local/lib/python2.7/dist-packages/keras/engine/topology.pyc in call(self, inputs, **kwargs)
617
618 # Actually call the layer, collecting output(s), mask(s), and shape(s).
--> 619 output = self.call(inputs, **kwargs)
620 output_mask = self.compute_mask(inputs, previous_mask)
621
/usr/local/lib/python2.7/dist-packages/keras/layers/core.pyc in call(self, inputs)
301
302 def call(self, inputs):
--> 303 return self.activation(inputs)
304
305 def get_config(self):
/usr/local/lib/python2.7/dist-packages/keras/activations.pyc in softmax(x, axis)
27 ndim = K.ndim(x)
28 if ndim == 2:
---> 29 return K.softmax(x)
30 elif ndim > 2:
31 e = K.exp(x - K.max(x, axis=axis, keepdims=True))
/usr/local/lib/python2.7/dist-packages/keras/backend/tensorflow_backend.pyc in softmax(x, axis)
2957 A tensor.
2958 """
-> 2959 return tf.nn.softmax(x, axis=axis)
2960
2961
TypeError: softmax() got an unexpected keyword argument 'axis'`

It is because the current tensorflow version you used is not matching to your code. Just modify the tf.nn.softmax(x, axis=axis) to tf.nn.softmax(x, dim=axis).

This error is still / again occuring with tensorflow 1.12.0 and keras 2.2.4 on python3.7.

The error is again occuring with tensorflow 1.12.0 and keras 2.2.4, most likely because axis got renamed to dim in TF.

@Zahlii confirmer! I also have the same error with keras 2.2.4 and tensorflow 1.2.1
$ python -c "import keras; print( keras.__version__ );"
Using TensorFlow backend.
2.2.4
$ python -c "import tensorflow as tf; print( tf.__version__ );"
1.2.1

cc @ghostplant

please upgrade tensorflow to 1.8.0 and check it out again.
If this doesn't work. please downgrade keras to 2.2.0.
2018년 11월 27일 (화) 오전 12:25, Loreto Parisi<EMAIL_ADDRESS>작성:

@Zahlii https://github.com/Zahlii confirmer! I also have the same error
with keras 2.2.4 and tensorflow 1.2.1
$ python -c "import keras; print( keras.version );"
Using TensorFlow backend.
2.2.4
$ python -c "import tensorflow as tf; print( tf.version );"
1.2.1
cc @ghostplant https://github.com/ghostplant
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/keras-team/keras/issues/9621#issuecomment-441677072,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APXRVKU9rjUR-Rsw6ASHKPXvLMQl2gkJks5uzAfRgaJpZM4Sl-Su
.

--
윤학림 드림
세종대학교 컴퓨터공학과
05006 서울특별시 광진구 능동로 209 세종대학교
전 화 02)465-5266
Mobile 010-2396-3278
E-mail<EMAIL_ADDRESS>

@hakex it does not work. I had to downgrade.
This is my configuration that it works for sure:
tensorflow==1.8.0
keras==2.2.0
PyHyphen==0.10
google==2.0.1
protobuf==3.4.0

liliarizona's suggestion worked for me (delete: axis=axis)

After trying some of the above suggestions, I ended up trying this change:
From:
model.add(Dense(133, activation='softmax'))
To:
model.add(Dense(133, activation = (tf.nn.softmax)))
and that did the trick. No change in versions or downgrade.
I am on tensorflow==1.12.0 and Keras==2.2.4

After trying some of the above suggestions, I ended up trying this change:
From:
model.add(Dense(133, activation='softmax'))
To:
model.add(Dense(133, activation = (tf.nn.softmax)))
and that did the trick. No change in versions or downgrade.
I am on tensorflow==1.12.0 and Keras==2.2.4

Lambda

Both seems good way without changing versions. Thanks!!

Hi NamePickAxe,
New to R and Keras -- so I have a couple of questions:

With tensorflow 1.10 and keras 2.2.4 I run into the same problem with softmax and axis argument.
How do I implement your solution?? If I type
"from keras import backend as K" in R or in python, it does not work. I tried K <-backend which works but how to implement the second line of your command??  --
Where to implement the change model command??? (if I understand you are changing the "old" softmax model to one that will ignore the axis parameter??)
How did you get tensorflow==1.12.0?? I downloaded from CRAN and got 1.10

Sorry -- I am not new to computers but totally new to Keras (and R..)
Running on a mac:
version  R version 3.5.2 (2018-12-20)
os       macOS Sierra 10.12.6
system   x86_64, darwin15.6.0
ui       X11
collate  en_US.UTF-8
ctype    en_US.UTF-8
Many thanks --

Hi,
I get the same problem but I got a better solution.
Just downgrade the tensorflow and keras.
My previous tensorflow version is 1.4.1 and keras version 2.1.5.
I downgrade to tensorflow version 1.4.0 and keras version 2.0.8.
The error doesn't appear anymore.

This really works.

pip3 install --upgrade keras==2.1.3
Made it for me. Tensorflow version 1.4
Works for me

The solution that worked for me was to use activation = (tf.nn.softmax) as opposed to just activation = 'softmax'

upgrade tensorflow and keras to below version solved my issue
pip install keras==2.1.6
pip install tensorflow==1.7.0

The reason why assert this error is version of tensorflow and keras is mismatch. I have slove this problem:
 pip install tensorflow==1.5.0
If you donot want to downdegree keras, tf 1.5.0 is the first version that support softmax(axis=axis).

@fitrialif - Just curious - why do you think downgrade is a better alternative than upgrade?

because upgrading affects other dependents

Happened to me while loading a saved model, downgraded tensorflow to version 1.14.0 and keras to 2.2.4 and it works now (I may have installed another library requiring tf 2.0 so that caused the problem to me)


Pronunciation of English words on screen

Do another round of adding missing English words and app names to the dictionary. For example "Talkback" is missing. Go systematically through the UI and transcribe missing words.

Did a round on this, re-open if we come across more missing words


[e2e]: generic tag main goreleaser-assets-multi-subjects slsa3

Repo: https://github.com/slsa-framework/example-package/tree/v38.0.47
Run: https://github.com/slsa-framework/example-package/actions/runs/5262445797
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.tag.main.goreleaser-assets-multi-subjects.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.tag.main.goreleaser-assets-multi-subjects.slsa3.yml
Trigger: push
Branch: v38.0.47
Date: Wed Jun 14 03:12:02 UTC 2023

Repo: https://github.com/slsa-framework/example-package/tree/v38.0.47
Run: https://github.com/slsa-framework/example-package/actions/runs/5262445797
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.tag.main.goreleaser-assets-multi-subjects.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.tag.main.goreleaser-assets-multi-subjects.slsa3.yml
Trigger: push
Branch: v38.0.47
Date: Wed Jun 14 05:23:51 UTC 2023

Repo: https://github.com/slsa-framework/example-package/tree/v38.0.54
Run: https://github.com/slsa-framework/example-package/actions/runs/5352369183
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.tag.main.goreleaser-assets-multi-subjects.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.tag.main.goreleaser-assets-multi-subjects.slsa3.yml
Trigger: push
Branch: v38.0.54
Date: Fri Jun 23 03:28:37 UTC 2023
Tests are passing now. Closing this issue.


fix a couple of clippy findings.

Thanks for your contribution! I'd assume that you've found the clippy warnings by running cargo clippy inside of the font subcrate, but how did you find the issue in the main.rs? Clippy doesn't seem to lint that for me.
Also looking at this it might make sense to handle the testing of the font subcrate differently. Currently none of the tests inside of font are run when something inside of font is changed and clippy doesn't run on the code change either. Would be interesting to see if Github/Travis-CI support subdirectories more properly for CI purposes.

Right, I was playing around with some additional warnings, the main.rs one is a clippy needless_borrow which is silent be default.

Oh it seems like there's a false positive currently present in the needless_borrow lint in combination with derive macros, which is why it's temporarily disabled. That explains why clippy did not warn about this anymore.

Also it seems like clippy does properly lint the subcrates (even though I wasn't able to reproduce locally).
See https://travis-ci.org/jwilm/alacritty/jobs/408024826.

I think it might only lint the subcrates due to --all-targets --all-features https://github.com/jwilm/alacritty/blob/master/.travis.yml#L32
I'll remove the needless_borrow change from the pr.

I added another commit which runs the tests of the two subcrates on travis as well.
It seems to me that cargo test --all should actually achieve this but as well but I couldn't see any of the subcrate tests being run so I called the tests one by one.

I don't think removing the needless_borrow fix is necessary. It's just that this is the reason why it's currently disabled. When there are no false positives, the lint should still be followed.

Ok I think the copypasta tests fail because travis is headless and thus there is no x11 clipboard. :/
test x11::tests::clipboard_works ... FAILED
failures:
---- x11::tests::clipboard_works stdout ----
	thread 'x11::tests::clipboard_works' panicked at 'store selection: Io(Os { code: 2, kind: NotFound, message: "No such file or directory" })', libcore/result.rs:945:5
note: Run with `RUST_BACKTRACE=1` for a backtrace.
failures:
    x11::tests::clipboard_works

@matthiaskrgr I wonder if xvfb would also give a clipboard... https://docs.travis-ci.com/user/gui-and-headless-browsers/#Using-xvfb-to-Run-Tests-That-Require-a-GUI

@jedahan ah, that's a great suggestion, thanks, I'll try that! :)

I don't think using xvfb to run tests would be a great plan. I've used it for benchmarking before, so I have a travis config which would make this work, however it seems quite unclean to me.
Keeping in mind that the copypasta crate is going to be replaced long-term anyways, I'd be fine with skipping the test for CI for that. Since it's unlikely that this subcrate is going to change.


Build from 'builder.dockerfile' if exists

This change allows to track the used Builder tag in a Dockerfile. This is useful for using Dependabot to keep the builder version up to date.
Users of the Builder who wish to use Dependabot will need to create a builder.dockerfile next to their build script with the following contents:
FROM ghcr.io/gardenlinux/builder:SHA

Where SHA will be updated by dependabot if configured correctly.
also users will need to set the container_image value in build to localhost/builder

I know it looks weird that I don't have quotes in $containerfile but as far as I understand word splitting is what we want here..

Could we add documentation?
For example:
Updating Builder Tag in Dockerfile with Dependabot
Purpose
Enable Dependabot to automatically update the Builder tag in Dockerfiles.
Steps

Create builder.dockerfile:

Place next to your build script.
Add the content: FROM ghcr.io/gardenlinux/builder:SHA.
SHA is the Builder version, updated by Dependabot.

Configure build Script:

Set container_image to localhost/builder.

Dependabot Setup
Ensure Dependabot monitors builder.dockerfile for automatic Builder version updates.

Could we add documentation?

Yes. I'm not sure if we are there yet because (as far as I understand) Dependabot needs releases on github to actually detect new versions, so we will need to push releases of the builder which we don't do yet. My approach here was to implement the requirements 1 by 1 and document it once we can verify it works.
To my understanding what is missing for this is merging this PR, and push proper tags/releases in this repo which I'd to in another PR (have not yet looked into how the images are published in detail).


[5.1] Fix possible key overlap in cache of Str::snake

Not a very practical example, but this PR avoids such a collision:
Str::snake('foo', '--');
Str::snake('foo-', '-');

Mmmm, a bit unsure, is it okay for 5.1?

I think this was changed in a later version? Also, we defintely need tests with this please.

Oh, right I see. Just read this again. We've not fixed this in a later version.

Added tests.


Add support for imagePullSecrets to Vault chart

What this PR does / why we need it:
This PR adds support for imagePullSecrets to the Vault chart so that images can be pulled from private registries, such as mirrors.
Which issue this PR fixes
N/A
Special notes for your reviewer:
This is my first PR. Please let me know if there's anything I can do better.

/assign @mattfarina

/assign

/ok-to-test

/lgtm


Update README.md

Added link for Python solution for Bigger is Greater problem

Please add the Readme and solution in the same PR

Please add the Readme and solution in the same PR

Surely, will keep this in  mind


remotePathResolve not working for every path

Describe the bug
The resolveRemotePaths cannot resolve every path correctly.
To Reproduce
Steps to reproduce the behaviour:

I have a python application, which generated a corbuleta xml report, which was successfully parsed and imported by the extension
The application runs on a docker container, and is copied to an absolute path '/app'
I set the 'resolveRemotePath' setting to ['/app', '']
I am trying to display the coverage

Expected behaviour
The coverage is rendered.
Outcome
The extensions fails to resolve any path, but does not give a warning or error.
I actually found the cause of the bug. The path is resolved with the following function:

sectionfinder.ts:81

private resolveFileName(fileName: string): string {
        let potentialFileName = fileName;
        const remoteLocalPaths = this.configStore.remotePathResolve;
        if (remoteLocalPaths) {
            const remoteFragment = remoteLocalPaths[0];
            const localFragment = remoteLocalPaths[1];
            const paths = fileName.split(remoteFragment);

            // If we have a length of two we have a match and can swap the paths
            // Note: this is because split will give us an array of two with the first element
            // being an empty string and the second being the project path.
            if (paths.length === 2) {
                potentialFileName = localFragment + paths[1];
            }
        }
        return potentialFileName;
    }

In my case, i had a path /app/src/app/my_module.py which should be resolved to src/app/my_module.py.
With remotePathResolve set to ['/app', ''], the '/app' substring is matched two times by .split, causing the
file name resolution to fail.
I could fix the issue by changing the setting to ' ['/app'/src, 'src']', but i had to go through the source code to figure this one out.
Desktop (please complete the following information):

OS: Ubuntu 20.04 64bit
Extension Version v2.9.1
VSCode Version 1.66.2 x64

Additional context
Add any other context about the problem here.

@der-schick96 Thanks for the ticket and the investigation!
Very interesting bug, I agree with your thinking around the issue living in the resolveFileName as well.
I will try to put in some time to make a failing test for this function, that uses the scenario you mentioned above, but in the meantime you can use the workaround you found.


FileNotFoundError when adding credentials (dephell self auth)

Short description
Hi, I was trying to set my credentials for pypi using the following command on Windows 10:
dephell self auth test.pypi.org my_username my_password

Output
It raised a FileNotFoundError:
dephell self auth test.pypi.org my_username my_password
>>> ERROR FileNotFoundError: [Errno 2] No such file or directory: 'C:\\Users\\Stef\\AppData\\Local\\dephell\\dephell\\config.toml'

Steps to reproduce
When I then create the folder/file myself it works fine, when I delete it, it raises the error again.
Versions
{
  "cache": "8.25Mb",
  "path": "c:\\users\\stef\\programs\\miniconda3\\lib\\site-packages\\dephell",
  "python": "c:\\users\\stef\\programs\\miniconda3\\python.exe",
  "version": "0.8.2",
  "versions": {
    "dephell-archive": "0.1.6",
    "dephell-argparse": "0.1.2",
    "dephell-changelogs": "0.0.1",
    "dephell-discover": "0.2.10",
    "dephell-licenses": "0.1.6",
    "dephell-links": "0.1.5",
    "dephell-markers": "1.0.3",
    "dephell-pythons": "0.1.14",
    "dephell-setuptools": "0.2.3",
    "dephell-shells": "0.1.4",
    "dephell-specifier": "0.2.1",
    "dephell-venvs": "0.1.17",
    "dephell-versioning": "0.1.1"
  }
}

Please, fill in all sections from the issue template.


Halimand-Norfolk

why has Halimand-Norfolk region not reported any new cases in weeks? I know there is a testing shortage but they should be reporting something?

Thanks for the message. It looked like H-N archived most of their COVID data on January 7, but since it didn't break our data pipeline, I didn't notice until you pointed it out.
https://hnhu.org/additional-daily-statistics/
Their dashboard is now useless for our purposes, since there is no way to continue reporting cases, mortality and recovered in the same format as before. A few PHUs have done this in response to testing limitations in 2022. I'm going to have to swap out their dataset for the Ministry of Health dataset. Stay tuned for that after tonight's update---you'll see a full time series for this PHU again.


Revert 1 a kubik patch 1

Codecov Report

Merging #2150 into master will increase coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #2150      +/-   ##
==========================================
+ Coverage   73.94%   73.94%   +<.01%
==========================================
  Files          90       90
  Lines      131906   131907       +1
  Branches    28964    28964
==========================================
+ Hits        97536    97540       +4
- Misses      34347    34348       +1
+ Partials       23       19       -4

Impacted Files
Coverage Δ

src/if_xcmdsrv.c
83.63% <0%> (-2.52%)
:arrow_down:

src/gui.c
46.34% <0%> (ø)
:arrow_up:

src/os_unix.c
53.36% <0%> (+0.04%)
:arrow_up:

src/window.c
81.09% <0%> (+0.06%)
:arrow_up:

src/channel.c
82.67% <0%> (+0.08%)
:arrow_up:

src/if_py_both.h
76.23% <0%> (+0.14%)
:arrow_up:

src/ex_cmds.c
77.94% <0%> (+0.22%)
:arrow_up:

Continue to review full report at Codecov.

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


Getting the json content of the request in the filter

Hello!
I'm trying to get json from a request in the filter for further analysis of this data by the filter. But I get a null pointer
Is there any way to get json from a request in a filter? Thanks for the answers!
void InSomnia::Filter::Login::doFilter(
    const drogon::HttpRequestPtr &req,
    drogon::FilterCallback &&fcb,
    drogon::FilterChainCallback &&fccb)
{
    const std::shared_ptr < Json::Value > jsonPtr = req->jsonObject();
    if(!jsonPtr)
    {
        // Gets here
    }
}

The problem is solved! The request consists of two parts - Option and Post. Option comes first - it does not contain JSON. That is, I added the following code to the beginning of the filter and everything worked fine
if (req->getMethod() == drogon::HttpMethod::Options)
{
    return fccb();
}


CastError: Cast to ObjectId failed when duplicating content with a relationship field

Link to reproduction
No response
Describe the Bug
When duplicating a document which contains a RelationshipField, the duplication is successful but it does throw an error which is confusing to the user.
Checking the logs it shows a "ERROR (payload): CastError: Cast to ObjectId failed for value ..." where you get "(type Object) at path "_id" for model"
To Reproduce
Create a collection with a RelationshipField field
Create a document and link it to a document via the relationship
Duplicate the document
Payload Version
2.24.2
Adapters and Plugins
No response

The field config I used to get the error:
{
name: 'fieldname',
label: 'Related to',
type: 'relationship',
index: true,
hasMany: true,
relationTo: ['collectionslug'],
admin: {}
}
And just to clarify, yes the document has to have at least one document linked for the error to occur. If the field is empty there is no issue.

Hey @frederico-taramaschi - I'm unable to reproduce this on latest v2 (2.30.1). Can you give this another shot on latest v2 and let me know if you're still experiencing this?

Sorry I have not yet been able to make time to test it out on latest, hoping to do it soon

Hey @frederico-taramaschi - I'm going to close this issue for now - if you are still experiencing the above behavior on latest v2, please send me a reproduction repo and I'll be happy to re-open this issue and take another look.