Error installing on Mac OS 10.13.6 with Ruby 2.1.10

Hi guys,
I just tried to install mini_racer version 0.1.15 and I am getting the following error:
$ gem install mini_racer -v '0.1.15' --source 'https://rubygems.org/'
Building native extensions. This could take a while...
ERROR:  Error installing mini_racer:
	ERROR: Failed to build gem native extension.

    current directory<EMAIL_ADDRESS>/.rvm/rubies/ruby-2.1.10/bin/ruby -r ./siteconf20181031-72772-n5jquv.rb extconf.rb
checking for main() in -lpthread... yes
checking for main() in -lobjc... yes
creating Makefile

current directory<EMAIL_ADDRESS>make "DESTDIR=" clean

current directory<EMAIL_ADDRESS>make "DESTDIR="
compiling mini_racer_extension.cc
clang: warning: argument unused during compilation: '-rdynamic' [-Wunused-command-line-argument]
In file included from mini_racer_extension.cc:2:
In file included from /.rvm/rubies/ruby-2.1.10/include/ruby-2.1.0/ruby.h:33:
In file included from /.rvm/rubies/ruby-2.1.10/include/ruby-2.1.0/ruby/ruby.h:1702:
/.rvm/rubies/ruby-2.1.10/include/ruby-2.1.0/ruby/intern.h:47:19: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register]
void rb_mem_clear(register VALUE*, register long);
                  ^~~~~~~~~
/.rvm/rubies/ruby-2.1.10/include/ruby-2.1.0/ruby/intern.h:47:36: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register]
void rb_mem_clear(register VALUE*, register long);
                                   ^~~~~~~~~
mini_racer_extension.cc:129:13: error: no type named 'TerminateExecution' in 'v8::V8'
        V8::TerminateExecution(isolate);
        ~~~~^
mini_racer_extension.cc:508:35: error: no member named 'IdleNotification' in 'v8::Isolate'
    return isolate_info->isolate->IdleNotification(NUM2INT(idle_time_in_ms)) ? Qtrue : Qfalse;
           ~~~~~~~~~~~~~~~~~~~~~  ^
mini_racer_extension.cc:737:6: error: no member named 'TerminateExecution' in 'v8::V8'
        V8::TerminateExecution(args->GetIsolate());
        ~~~~^
mini_racer_extension.cc:761:11: error: no type named 'TerminateExecution' in 'v8::V8'
      V8::TerminateExecution(isolate);
      ~~~~^
mini_racer_extension.cc:1036:9: error: no type named 'TerminateExecution' in 'v8::V8'
    V8::TerminateExecution(isolate);
    ~~~~^
2 warnings and 5 errors generated.
make: *** [mini_racer_extension.o] Error 1

make failed, exit code 2

Gem files will remain installed in<EMAIL_ADDRESS>for inspection.
Results logged to<EMAIL_ADDRESS>
I checked out some of the other answers and issues, but those resolutions don't really help me for one reason or another.
How do I fix this or what else can I try to troubleshoot?
Thanks.
Edit 1
I can't upgrade to the latest version because I am stuck on Ruby 2.1.10, and I can't upgrade to 2.3.

explicitly add a dependency in your Gemfile.lock for an earlier libv8 version.

I am having a similar error. Mine is on Ruby 2.4.1 MacOS Moajave, version 10.14.3 (18D109)
$ gem install mini_racer -v '0.1.15'
Building native extensions. This could take a while...
ERROR:  Error installing mini_racer:
	ERROR: Failed to build gem native extension.

    current directory: /Users/adepojuadebayo/.rvm/gems/ruby-2.4.1/gems/mini_racer-0.1.15/ext/mini_racer_extension
/Users/adepojuadebayo/.rvm/rubies/ruby-2.4.1/bin/ruby -r ./siteconf20190220-24857-1ojsc6t.rb extconf.rb
checking for -lpthread... yes
checking for -lobjc... yes
creating Makefile

current directory: /Users/adepojuadebayo/.rvm/gems/ruby-2.4.1/gems/mini_racer-0.1.15/ext/mini_racer_extension
make "DESTDIR=" clean

current directory: /Users/adepojuadebayo/.rvm/gems/ruby-2.4.1/gems/mini_racer-0.1.15/ext/mini_racer_extension
make "DESTDIR="
compiling mini_racer_extension.cc
clang: warning: argument unused during compilation: '-rdynamic' [-Wunused-command-line-argument]
In file included from mini_racer_extension.cc:2:
In file included from /Users/adepojuadebayo/.rvm/rubies/ruby-2.4.1/include/ruby-2.4.0/ruby.h:33:
In file included from /Users/adepojuadebayo/.rvm/rubies/ruby-2.4.1/include/ruby-2.4.0/ruby/ruby.h:2005:
/Users/adepojuadebayo/.rvm/rubies/ruby-2.4.1/include/ruby-2.4.0/ruby/intern.h:47:19: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register]
void rb_mem_clear(register VALUE*, register long);
                  ^~~~~~~~~
/Users/adepojuadebayo/.rvm/rubies/ruby-2.4.1/include/ruby-2.4.0/ruby/intern.h:47:36: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register]
void rb_mem_clear(register VALUE*, register long);
                                   ^~~~~~~~~
2 warnings generated.
linking shared-object mini_racer_extension.bundle
clang: warning: libstdc++ is deprecated; move to libc++ [-Wdeprecated]
ld: library not found for -lstdc++
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [mini_racer_extension.bundle] Error 1

make failed, exit code 2

Gem files will remain installed in /Users/adepojuadebayo/.rvm/gems/ruby-2.4.1/gems/mini_racer-0.1.15 for inspection.
Results logged to /Users/adepojuadebayo/.rvm/gems/ruby-2.4.1/extensions/x86_64-darwin-18/2.4.0/mini_racer-0.1.15/gem_make.out

explicitly add a dependency in your Gemfile.lock for an earlier libv8 version.
Still stands, my recommended fix though is just upgrade mini racer? why do you need the ancient version

note ... I can not keep open issue for EOL Ruby, as I simply do not support Ruby 2.1 or 2.2, you are on your own here.


Failed to bring up Control Plane

Hi deploying a cluster 2 control plane 3 etcd 5 workers, iam policy is created and assigned to the host and the amazon cloud provider it set.  i get the following error
[controlPlane] Failed to bring up Control Plane: Failed to verify healthcheck: Failed to check https://localhost:6443/healthz for service [kube-apiserver] on host [<IP_ADDRESS>]: Get https://localhost:6443/healthz: can not build dialer to c-dgpq5:m-v8ks9, log: I1015 18:25:38.042761 1 controller.go:597] quota admission added evaluator for: {rbac.authorization.k8s.io rolebindings}

Useful
Info

Versions
Rancher v2.1.0 UI: v2.0.77

Route
global-admin.clusters.index

can not build dialer to means the host <IP_ADDRESS> cannot connect back to the configured server-url over HTTPS. This can either be a blocked port, non existing route or wrongly configured certificates. The last option is ruled out when using the default self signed certificates from Rancher. Can you give more info on the setup?

Here is my node template everthing elses is default

Create a cluster

cluster options

I am assigning a IAM group which contains the following policy to the rancher server and using it cluster options
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "VisualEditor0",
            "Effect": "Allow",
            "Action": [
                "ec2:AuthorizeSecurityGroupIngress",
                "ec2:Describe*",
                "ec2:ImportKeyPair",
                "ec2:CreateKeyPair",
                "ec2:CreateSecurityGroup",
                "ec2:CreateTags",
                "ec2:DeleteKeyPair"
            ],
            "Resource": "*"
        },
        {
            "Sid": "VisualEditor1",
            "Effect": "Allow",
            "Action": [
                "ec2:DetachVolume",
                "ec2:AttachVolume",
                "ec2:DeleteVolume",
                "ec2:RunInstances",
                "ec2:CreateVolume"
            ],
            "Resource": [
                "arn:aws:ec2:us-east-1:xxx:instance/*",
                "arn:aws:ec2:us-east-1:xxx:volume/*",
                "arn:aws:ec2:us-east-1:xxx:network-interface/*",
                "arn:aws:ec2:us-east-1:xxx:placement-group/*",
                "arn:aws:ec2:us-east-1::image/ami-*",
                "arn:aws:ec2:us-east-1:xxx:security-group/*",
                "arn:aws:ec2:us-east-1:xxx:subnet/*",
                "arn:aws:ec2:us-east-1:xxx:key-pair/*"
            ]
        },
        {
            "Sid": "VisualEditor2",
            "Effect": "Allow",
            "Action": [
                "ec2:RebootInstances",
                "ec2:TerminateInstances",
                "ec2:StartInstances",
                "ec2:StopInstances"
            ],
            "Resource": "arn:aws:ec2:us-east-1:xxx:instance/*"
        }
    ]
}

Here is the security group breing created

Type
Protocol
Port Range
Source
Description

HTTP | TCP | 80 | <IP_ADDRESS>/0 |
Custom TCP Rule | TCP | 30000 - 32767 | <IP_ADDRESS>/0 |
Custom TCP Rule | TCP | 6443 | <IP_ADDRESS>/0 |
Custom TCP Rule | TCP | 2379 - 2380 | sg-0ae5dd5584d1778f7 (rancher-nodes) |
SSH | TCP | 22 | <IP_ADDRESS>/0 |
Custom UDP Rule | UDP | 8472 | sg-0ae5dd5584d1778f7 (rancher-nodes) |
Custom TCP Rule | TCP | 2376 | <IP_ADDRESS>/0 |
Custom UDP Rule | UDP | 30000 - 32767 | <IP_ADDRESS>/0 |
Custom UDP Rule | UDP | 4789 | sg-0ae5dd5584d1778f7 (rancher-nodes) |
HTTPS | TCP | 443 | <IP_ADDRESS>/0 |
Custom TCP Rule | TCP | 10256 | sg-0ae5dd5584d1778f7 (rancher-nodes) |
Custom TCP Rule | TCP | 10250 - 10252 | sg-0ae5dd5584d1778f7 (rancher-nodes) |

strange thing is this worked over the weekend, I tore it down and tried to rebuild on Monday.

turns out a change was made in our VPC  ..
¯_(ツ)_/¯
thanks


API for per character validator in TextFields

Have an API to have a per character input white/blacklist.

Merging in #9511


RFE: Display/use Business Criticality value

Please add Business Criticality value in Question 1 in the Results screen.  Possibly, add a tooltip as to how it affects scoring.

@noelo I understand from @matallen that this may be complete.  Please close if you concur.

@noelo @kelaird
We appear to be mixing our terms and creating confusion here I think.
In the survey the text states "business criticality" but the field name is BUSPRIORITY.
Priority vs Criticality means different things to the customer, an app can be critical but not their priority to migrate early.
Please could you (@noelo) state what you originally meant to convey with the question?
And also how it differs from the "business priority" and "work priority" in the assessment review screen?
Then after that we can determine what actions need to be taken for this story, and then it can be sized & prioritised ;-)

If it helps, I'll make [A]dd a tooltip as to how [Business Criticality] affects scoring. a separate RFE.  In retrospect it is more important to be able pull out what you put in to Pathfinder.  I imagine Business Criticality will be subjective on a per customer basis.

This field was to be part of the algorithm of how Pathfinder makes its recommendations and the output report. However we haven't defined the report aspect of Pathfinder yet, so the "how it affects scoring" hasn't been decided, but I take your point that there is a need to understand how answering certain questions affects that.
Yes please, do create an "Add a tooltip as to how [Business Criticality] affects scoring". That will force us to consider how we communicate to the end user how those fields affect the recommendations, whatever output we decide upon.


XSLT warning "The parent axis starting at a document node will never select anything"

Hello!

I am on MacOS (latest)

I installed the Oracle JDK (latest)

I installed Maven (latest)

I cloned this repository and checkout'ed the master branch

I invoked the Maven install command (no problems)

I ran EpubCheck from the command line against a few EPUBs (seems to work just fine).

However, the following message is reported over 20 times in the console (just before the actual validation message):

Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything

Validating using EPUB version 3.0.1 rules.
No errors or warnings detected.
Messages: 0 fatal / 0 errors / 0 warnings / 0 info

System:
java --version
java 11 2018-09-25
Java(TM) SE Runtime Environment 18.9 (build 11+28)
Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11+28, mixed mode)

mvn --version
Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe; 2018-06-17T19:33:14+01:00)
Maven home: /Applications/apache-maven
Java version: 11, vendor: Oracle Corporation, runtime: /Library/Java/JavaVirtualMachines/jdk-11.jdk/Contents/Home
Default locale: en_GB, platform encoding: UTF-8
OS name: "mac os x", version: "10.14", arch: "x86_64", family: "mac"

java -jar target/epubcheck.jar --version
EpubCheck v4.0.3-SNAPSHOT
No file specified in the arguments. Exiting.
epubcheck completed

Warning at char 3 in xsl:param/@select on line 459 column 43 SXWN9000: The parent axis starting at a document node will never select anything

Would there be a file associated somewhere in the log with this line and column number?
If not we'll have to do some spelunking :-)

Note that there are no Travis checks for Java 11 yet. We should set those up and check if it’s a Java 11 issue.

I've been looking "everywhere" (EPUBCheck wiki docs, CLI help, known MacOS tmp / app folders, GitHub issue tracker) ... but I am not able to find the full EPUBCheck log. Where should I look for it? Thanks! :)

I also checked the list of system-level file handles opened/closed by the Java process (MacOS / Darwin), I cannot see any low-level log file. Perhaps there isn't one? In which case, all I have is the log excerpt quoted in my original post (above).

I've been looking "everywhere" (EPUBCheck wiki docs, CLI help, known MacOS tmp / app folders, GitHub issue tracker) ... but I am not able to find the full EPUBCheck log. Where should I look for it?

Sorry I wasn't clear: there's no log file, I was asking if there was more context in the console output from your previous message. Apparently not 😄

Note that there are no Travis checks for Java 11 yet. We should set those up and check if it’s a Java 11 issue.

I added a travis check for JDK 11 with PR #860 but it does not throw any errors like these. So it seems to be an issue with your special book.

I'm not sure if is related but I'm on a Windows 10 system with the latest version of the source code, java version 1.8 and Maven 3.5.4 and I'm getting a similar behavior.  I just did a pull from the repo and did get an update to the travis.yaml file, but no other changes.
When I clean and package the code, I get the exact same message that Daniel is getting when I clean and package the code.  It is generated by the "com.adobe.epubcheck.api.Epub20CheckExpandedTest" test suite, and even though there are only 22 tests in the set, I see the error 27 times.
I have tried this in both the "standard" Windows command prompt and using the Git Bash shell as well; both produce the exact same behavior.
I'm just getting started looking at the code base here, and I wasn't sure if this is an expected behavior for that test, but in light of the issue, I wanted to include the information.
java version "1.8.0_181"
Java(TM) SE Runtime Environment (build 1.8.0_181-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode)
mvn -version
Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe; 2018-06-17T12:33:14-06:00)
Maven home: C:\Program Files (x86)\Apache\maven\bin..
Java version: 1.8.0_181, vendor: Oracle Corporation, runtime: C:\Program Files\Java\jdk1.8.0_181\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"

mvn install runs the tests "default-test" and "coverage-test" (all pass), respectively:
Tests run: 1002, Failures: 0, Errors: 0, Skipped: 1

and:
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0

Note that "default-test" reports the warning message:
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything

Full console log:
[INFO] --- maven-surefire-plugin:2.18.1:test (default-test) @ epubcheck ---
[INFO] Surefire report directory: /Users/danielweck/Code/epubcheck/target/surefire-reports

-------------------------------------------------------
 T E S T S
-------------------------------------------------------
Running com.adobe.epubcheck.api.Epub20CheckExpandedTest
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 422 column 41
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 422 column 41
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Tests run: 22, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 14.626 sec - in com.adobe.epubcheck.api.Epub20CheckExpandedTest
Running com.adobe.epubcheck.api.Epub20CheckTest
Spine element not found within package root document ops/manifest.opf
Spine element not found within package root document EPUB/manifest.opf
Spine element not found within package root document OEBPS/content.opf
Tests run: 33, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.681 sec - in com.adobe.epubcheck.api.Epub20CheckTest
Running com.adobe.epubcheck.api.Epub30CheckExpandedTest
Tests run: 148, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 16.55 sec - in com.adobe.epubcheck.api.Epub30CheckExpandedTest
Running com.adobe.epubcheck.api.Epub30CheckTest
Tests run: 48, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 13.984 sec - in com.adobe.epubcheck.api.Epub30CheckTest
Running com.adobe.epubcheck.cli.CLITest
Tests run: 21, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.01 sec - in com.adobe.epubcheck.cli.CLITest
Running com.adobe.epubcheck.nav.NavCheckerTest
Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.175 sec - in com.adobe.epubcheck.nav.NavCheckerTest
Running com.adobe.epubcheck.ocf.OCFCheckerTest
Tests run: 24, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.836 sec - in com.adobe.epubcheck.ocf.OCFCheckerTest
Running com.adobe.epubcheck.ocf.OCFFilenameCheckerTest
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.018 sec - in com.adobe.epubcheck.ocf.OCFFilenameCheckerTest
Running com.adobe.epubcheck.opf.MetadataSetTest
Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.075 sec - in com.adobe.epubcheck.opf.MetadataSetTest
Running com.adobe.epubcheck.opf.OPFCheckerTest
Tests run: 128, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.884 sec - in com.adobe.epubcheck.opf.OPFCheckerTest
Running com.adobe.epubcheck.ops.OPSCheckerTest
Tests run: 100, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.485 sec - in com.adobe.epubcheck.ops.OPSCheckerTest
Running com.adobe.epubcheck.overlay.OverlayCheckerTest
Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.183 sec - in com.adobe.epubcheck.overlay.OverlayCheckerTest
Running com.adobe.epubcheck.test.api_Test
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.297 sec - in com.adobe.epubcheck.test.api_Test
Running com.adobe.epubcheck.test.command_line_Test
Tests run: 19, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 2.809 sec - in com.adobe.epubcheck.test.command_line_Test
Running com.adobe.epubcheck.test.css_Test
Tests run: 17, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.543 sec - in com.adobe.epubcheck.test.css_Test
Running com.adobe.epubcheck.test.dtBook_Test
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.438 sec - in com.adobe.epubcheck.test.dtBook_Test
Running com.adobe.epubcheck.test.encryption_Test
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.919 sec - in com.adobe.epubcheck.test.encryption_Test
Running com.adobe.epubcheck.test.opf_Test
Tests run: 30, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.114 sec - in com.adobe.epubcheck.test.opf_Test
Running com.adobe.epubcheck.test.package_Test
Tests run: 22, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.006 sec - in com.adobe.epubcheck.test.package_Test
Running com.adobe.epubcheck.test.script_Test
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.655 sec - in com.adobe.epubcheck.test.script_Test
Running com.adobe.epubcheck.test.single_file_Test
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.1 sec - in com.adobe.epubcheck.test.single_file_Test
Running com.adobe.epubcheck.test.toc_Test
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.256 sec - in com.adobe.epubcheck.test.toc_Test
Running com.adobe.epubcheck.test.xhtml_Test
Tests run: 17, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.649 sec - in com.adobe.epubcheck.test.xhtml_Test
Running com.adobe.epubcheck.util.OPFPeekerTest
Tests run: 19, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.092 sec - in com.adobe.epubcheck.util.OPFPeekerTest
Running com.adobe.epubcheck.util.PathUtilTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec - in com.adobe.epubcheck.util.PathUtilTest
Running com.adobe.epubcheck.vocab.PrefixParsingTest
Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.068 sec - in com.adobe.epubcheck.vocab.PrefixParsingTest
Running com.adobe.epubcheck.vocab.PropertyTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.007 sec - in com.adobe.epubcheck.vocab.PropertyTest
Running com.adobe.epubcheck.vocab.VocabTest
Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.076 sec - in com.adobe.epubcheck.vocab.VocabTest
Running org.idpf.epubcheck.util.css.CssInputStreamTest
Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.007 sec - in org.idpf.epubcheck.util.css.CssInputStreamTest
Running org.idpf.epubcheck.util.css.CssParserTest
Tests run: 121, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.229 sec - in org.idpf.epubcheck.util.css.CssParserTest
Running org.idpf.epubcheck.util.css.CssScannerTest
Tests run: 127, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.032 sec - in org.idpf.epubcheck.util.css.CssScannerTest

Results :

Tests run: 1002, Failures: 0, Errors: 0, Skipped: 1

With childrens-literature.epub downloaded from http://idpf.github.io/epub3-samples/30/samples.html
java -jar target/epubcheck.jar childrens-literature.epub
=>
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 422 column 41
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 422 column 41
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Validating using EPUB version 3.0.1 rules.
No errors or warnings detected.
Messages: 0 fatal / 0 errors / 0 warnings / 0 info

epubcheck completed

With accessible_epub_3.epub downloaded from http://idpf.github.io/epub3-samples/30/samples.html
java -jar target/epubcheck.jar accessible_epub_3.epub
=>
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 422 column 41
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 422 column 41
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything
Validating using EPUB version 3.0.1 rules.
ERROR(CSS-020): /Users/danielweck/Downloads/accessible_epub_3.epub/EPUB/css/epub.css(130,3): CSS font selector declaration uses unexpected font-size value 'bold'.

Check finished with errors
Messages: 0 fatal / 1 errors / 0 warnings / 0 info

epubcheck completed

So, instead of Oracle JDK v11.0.1 from https://www.oracle.com/technetwork/java/javase/downloads/jdk11-downloads-5066655.html , I have tried with OpenJDK v11.0.1 from https://jdk.java.net/11/
/usr/libexec/java_home -V
Matching Java Virtual Machines (2):
    11.0.1, x86_64:	"OpenJDK 11.0.1"	/Library/Java/JavaVirtualMachines/jdk-11.0.1.jdk/Contents/Home
    11, x86_64:	"Java SE 11"	/Library/Java/JavaVirtualMachines/jdk-11.jdk/Contents/Home

/Library/Java/JavaVirtualMachines/jdk-11.0.1.jdk/Contents/Home

/usr/libexec/java_home -v 11
/Library/Java/JavaVirtualMachines/jdk-11.0.1.jdk/Contents/Home

java --version
openjdk 11.0.1 2018-10-16
OpenJDK Runtime Environment 18.9 (build 11.0.1+13)
OpenJDK 64-Bit Server VM 18.9 (build 11.0.1+13, mixed mode)

I get the exact same console messages (as detailed above), so I won't repeat them here. Excerpt:
Warning at char 3 in xsl:param/@select on line 459 column 43
  SXWN9000: The parent axis starting at a document node will never select anything

I had a fresh look at this issue and I can reproduce it locally too (on macOS 10.13.6 running OpenJDK 11.0.1+13).
The issue comes from the schematron XSLT bundled with Jing, which has the /.. XPath expression which will always evaluate to the empty sequence.
Apparently Saxon 9.8 raises a SXWN9000 warning for this construct, when Saxon 9.7 stayed silent. I ran the tests before #830 was applied and the warning didn't show up.
It puzzles me however why the warning doesn't happen on the Travis build… to be further investigated.
As for making this warning disappear, we have several options:

revert to Saxon 9.7
try to configure the Saxon instance run by Jing to stay silent
try to override the XSLT bundled with Jing by a patched XSLT where we remove this selector

I will also file a bug to Jing.


Switch to use pyright

It's on the roadmap.

Something may be useful:
Pyright playground server: https://github.com/erictraut/pyright-playground
--mypy ++pyright

Mypy: !!!!!

I've been using pyright-playground during development tool, it's very handy. I also plan to add a link to it for every challenge, with code automatically populated, so people can use pyright-playground's language server & autocomplete (which we are not likely to provide here )

I'm starting to work on it, and hopefully to get it done this weekend

Have switched to pyright, closed.


Group Only Table results in table querying all records

Package
filament/filament
Package Version
v3.2.40
Laravel Version
v11.17.0
Livewire Version
v3.5.4
PHP Version
PHP 8.3.9
Problem description
The app timeout when accessing Orders menu
Expected behavior
It should not query all records, at least not without limit
Steps to reproduce
git clone https://github.com/sawirricardo/filafun
cd filafun
composer install
cp .env.example .env
php artisan migrate:fresh --seed
php artisan serve

Go to https://<IP_ADDRESS>:8000/admin
login as<EMAIL_ADDRESS>password
access menu orders

Reproduction repository (issue will be closed if this is not valid)
https://github.com/sawirricardo/filafun
Relevant log output
No response

Donate 💰 to fund this issue

You can donate funding to this issue. We receive the money once the issue is completed & confirmed by you.
100% of the funding will be distributed between the Filament core team to run all aspects of the project.
Thank you in advance for helping us make maintenance sustainable!

This is required to calculate summaries across records, we need to know what groups are available. The reason there is no limit is because it's impossible to get reliable numbers of groups when paginating, as some pages may only return 1 group.


[Doc] The logo file in the lower left corner of the page is 404

Search before asking

[X] I had searched in the issues and found no similar issues.

Documentation Related
I found that the logo file in the lower left corner of the page is not loaded correctly：

After opening the browser console, I found that the file is 404：

Was this file renamed or moved to another directory? I thought I might be able to try to fix this. :)
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

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

Quite detailed observation. You can find the website code at https://github.com/apache/eventmesh-dashboard repo.
The problem is because the logo file uses a relative path reference. Just replace it with an absolute path.

eventmesh-dashboard

Sorry for the late reply. I don't seem to find the develop branch in the eventmesh-dashboard, and I can't find the /docs directory in the main branch. Which branch should I deal with this problem?

Quite detailed observation. You can find the website code at https://github.com/apache/eventmesh-dashboard repo.
The problem is because the logo file uses a relative path reference. Just replace it with an absolute path.

Sorry for the late reply. I don't seem to find the develop branch in the eventmesh-dashboard, and I can't find the /docs directory in the main branch. Which branch should I deal with this problem?

Correct, the logo file is stored in https://github.com/apache/eventmesh-site repo.

@qqeasonchen ，@Pil0tXia Thanks for the guidance, I think I fixed the problem.
But should I close the issue and reopen it in the https://github.com/apache/eventmesh-site repo before submitting the PR?


Complete documentation

The README and generated docs should give the user enough information to fully understand how Telephonist works.

@danielberkompas I've looked at this and your other work with ex_twiml
**I'm wondering, can use this state machine with the SMS verb or are there call specific things in here?`

@cloudbring You could use this with the SMS verb, yes. Do you have a specific use case in mind?

I'm trying to tie SMS messages to an in-browser chat session with JS.
Basically allow the users of the app I'm building to chat with people over
SMS. I was thinking that Elixir and Phoenix's support for channels would be
a good choice for my usecase. Do you agree and would telephonist be up to
the job?
On Sun, May 31, 2015 at 9:35 PM Daniel Berkompas<EMAIL_ADDRESS>wrote:

@cloudbring https://github.com/cloudbring You could use this with the
SMS verb, yes. Do you have a specific use case in mind?
—
Reply to this email directly or view it on GitHub
https://github.com/danielberkompas/telephonist/issues/1#issuecomment-107302606
.

I think Elixir, Phoenix and Twilio would be a good fit for what you're building, but I don't think you need Telephonist for that. Telephonist is primarily intended to help manage inbound phone calls, for example, for a help desk. It's not really needed to handle inbound/outbound SMS.
It sounds like your app would have two main transactions:
1. User sends message from JS chat

Message is sent over websockets to Phoenix channel
App decides what phone number needs to be sent an SMS
Contact Twilio REST API to send an SMS message to that phone number

2. User sends SMS from phone

Message is sent to a Twilio phone number
Twilio posts information about the SMS message, including the number it was sent to, to an endpoint on your Phoenix app
Your app interprets what JS chat this message belongs to, and broadcasts the message on the appropriate Phoenix channel.
Message comes through websockets to JS client
Display to user

Telephonist doesn't fit into this picture. However, another library I wrote, ExTwilio might be useful for the Twilio API calls you'd need to make.

Thanks for the advice! I'm gonna take that to heart and try and build it
out over the next couple of weekends.
I saw ExTwillio. Looks good, can't wait to jump in and start playing
around.
So, I wrote up a little Gist kinda outlining what's in the Phoenix
Ecosystem as of June 2015 (in the context of writing this app) and I list
your Twilio packages (among other things).  Take a look and let me know
what you think and if there's anything that's missing.
j.mp/phoenix_ecosystem_June2015 http://j.mp/phoenix_ecosystem_June2015
Best,
Emmanuel
On Mon, Jun 1, 2015 at 1:29 PM Daniel Berkompas<EMAIL_ADDRESS>wrote:

I think Elixir, Phoenix and Twilio would be a good fit for what you're
building, but I don't think you need Telephonist for that. Telephonist is
primarily intended to help manage inbound phone calls, for example, for a
help desk. It's not really needed to handle inbound/outbound SMS.
It sounds like your app would have two main transactions:

User sends message from JS chat

Message is sent over websockets to Phoenix channel
App decides what phone number needs to be sent an SMS
Contact Twilio REST API to send an SMS message to that phone number

User sends SMS from phone

Message is sent to a Twilio phone number
Twilio posts information about the SMS message, including the number
it was sent to, to an endpoint on your Phoenix app
Your app interprets what JS chat this message belongs to, and
broadcasts the message on the appropriate Phoenix channel.
Message comes through websockets to JS client
Display to user

Telephonist doesn't fit into this picture. However, another library I
wrote, ExTwilio https://github.com/danielberkompas/ex_twilio might be
useful for the Twilio API calls you'd need to make.
—
Reply to this email directly or view it on GitHub
https://github.com/danielberkompas/telephonist/issues/1#issuecomment-107697271
.


terminate called after throwing an instance of 'std::runtime_error'

What i do:
> g++ Test.cpp -o Test && ./Test

What i get:
terminate called after throwing an instance of 'std::runtime_error'
  what():  flf2a not found !
[1]    5288 abort (core dumped)  ./Test

Code:
#include <iostream>
#include "srilakshmikanthanp/Figlet.hpp"

using namespace srilakshmikanthanp;

int main()
{
    Figlet figlet(FigletFont::make("Fonts/Standard.flf"), Smushed::make());
    std::cout << figlet("Hello, C++");
    return 0;
}

Hey, thanks for raising issue now I added the file not found error could you please run the same program but with also with the Fonts folder available,
#include <iostream>
#include "./Figlet.hpp"

using namespace srilakshmikanthanp;

int main()
{
    Figlet figlet(FigletFont::make("./Fonts/Standard.flf"), Smushed::make());
    std::cout << figlet("Hello, C++");
    return 0;
}

Assuming the Fonts folder will present in current working directory

1. When Fonts folder is not in current working directory;
2. When Fonts folder is in current working directory.
I think everything is working as it should now.
Thanks!

Yeah! Just pass the path to font or stringstream to FigletFont::make


Improve extension recommendations (August milestone)

Currently the extension recommendations come from 2 sources

a curated list of extensions mapped to filetypes maintained by the VS Code team.
the extension list inside the .vscode/extensions.json file in a workspace which is maintained by the workspace owners

A framework that can help explain to the user why and how these recommendations are made is missing
This issue tracks work in improving the extension recommendation system and will span over several iterations.
Things to achieve

Users should understand why a recommendation is being made. A recommendation can be

based on current file type
based on current workspace
history of types of files opened

[x] Recommendations should be relevant. For example: User opens a php file long time ago, gets recommendation for a php extension, never again opens a php file. The recommendation continues to show up today. Files/workspaces used more often should influence recommendations than files/workspaces rarely used
Recommendations list should be short and well sorted as per relevance. For example: the recommendation for current file type and workspace can show up before the ones based on historical usage (moved to September milestone)

We need telemetry in place to

[x] determine whether recommendations are successful
[x] assess the success of different ways of presenting recommendations
associate extensions with features like format/lint/completion/outline etc This can in the future help in recommending by category (moved to September milestone)

Sounds great, because personally I have disabled that view, because I don't need those extensions that are suggested.
How do you want to improve the algorithm?

Adding a way to calculate relevance of an extension recommendation can help in pruning the list.
Currently extensions recommended by file type gets stored in the local storage and they appear in the recommended view.
The simplest way to go about this is storing a timestamp along with the recommendation. If that date is more than a week old, the extension is removed from the list.
cc @sandy081 @kieferrm @seanmcbreen

@ramya-rao-a would it be possible to add an entry onto the list of extensions mapped to filetypes maintained by the VS Code team.?
Ideally, if there is a .cake file in the current workspace, it would be great if the user were recommended to add the Cake Extension:
https://marketplace.visualstudio.com/items?itemName=cake-build.cake-vscode
Thanks

@gep13 That's a valid request. I have created an issue to track this. See #38543
Once we have a good list there and few of us from the team verify the extensions, we will update the recommendations

@ramya-rao-a that is great, thank you!


Wallets: increase timeouts

Codecov Report

Merging #787 (2b7c73b) into main (ea76995) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #787   +/-   ##
=======================================
  Coverage   41.25%   41.25%
=======================================
  Files         206      206
  Lines       10906    10906
=======================================
  Hits         4499     4499
  Misses       6407     6407

Impacted Files
Coverage Δ

lnbits/wallets/eclair.py
21.29% <ø> (ø)

lnbits/wallets/lnbits.py
18.75% <ø> (ø)

lnbits/wallets/lndrest.py
17.75% <ø> (ø)

lnbits/wallets/lnpay.py
21.95% <ø> (ø)

lnbits/wallets/lntxbot.py
17.24% <ø> (ø)

lnbits/wallets/opennode.py
24.35% <ø> (ø)

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


Update text vol 2

Task description
There are three screens that needs to have their texts updated again. Two of the screens are in the introductory delegation carousel, and the third one is the one where the user can decide between a specific baker pool or passive delegation.
The new text is highlighted in blue, in the box called "Renaming of L-pool to passive delegation VOL 2 in Figma. It can be seen on to the right of the first renaming box.

Verified with the Android MW version 3.0.11 (95)


npm ERR! notarget No matching version found for<EMAIL_ADDRESS>

Hi,
while running  or trying to build the core-node module we are getting the following error message.
(DIBuild) npm ERR! code ETARGETnpm
ERR! notarget No matching version found for<EMAIL_ADDRESS>ERR! notarget In most cases you or one of your dependencies are requesting npm
ERR! notarget a package version that doesn't exist.
We were not able to locate where sax package is being referred in the core-node module. The error still persists even if we include it in the package.json file.
Rest all modules are getting built and running fine.
We tried using HANA 2.0 SPS05 and SPS07 versions.

@pradeep87gupta
Please Check the Npm registry once, issue occur because of npm registry is not been set properly. https://www.npmjs.com/package/sax/v/1.1.4
Regards,
Lalith. S

Hi @LalithManokar,
thanks for coming back on this.
We checked our system and our admin team says that this npm package exists in the registry.
We have also setup the UPSTREAMLINK and SAPUPSTREAM_LINK as below
UPSTREAM_LINK: "http://registry.npmjs.org/"
SAPUPSTREAM_LINK: "https://registry.npmjs.org"
All other modules like core-xsjs and user-xsjs are getting built and running fine.
Only in the core-node project its prompting this error even though we if we include it in the package.json file as a dependency
"sax" : "1.2.4"
Could please let us know where exactly should we be checking this npm registry whether it has been setup properly or not?

Please Check the documentation
https://help.sap.com/docs/SAP_HANA_PLATFORM/4505d0bdaf4948449b7f7379d24d0f0d/726e5d41462c4eb29eaa6cc83ff41e84.html?q=UPSTREAM_LINK
Regards,
Lalith. S

Hi @LalithManokar,
Thanks a lot. Your solution worked for us and now we dont have the npm error anymore.
I have run into other issue now. Could you also please check that. Thank you!
https://github.com/SAP-samples/hana-shine-xsa/issues/97


Add socket support and other options

Hi :)
This PR adds the filesPath option to the frontend module, which i use to host the frontend with a different web server.
Also i changed the piped-proxy to use systemd sockets and added the listenPath option which allows setting a path to a unix socket for the proxy to listen on.
Another change is the extra sed in the frontend postPatch to change the opensearch url. Upstream doesn't do this in the docker container setup, but i think there is no reason to not do it.

Thanks for the contributions. I merged the filesPath and opensearch changes. Can you open a new PR for the socket change (or update this one?)
I'll be happy to merge unix socket support, but I'll need to do some research to understand how you're doing it with systemd-socket and piped-proxy. This is using systemd socket activation?

Socket activation imposes a performance penalty because a new process must be launched for each connection. piped-proxy supports natively setting up its own TCP connection, but not its own UNIX socket. So I'd like to use socket activation only in the case of UNIX sockets, not TCP connections. Let me know if I'm wrong about any of these statements. And I'm open to be convinced in using activation for all cases if there's an argument for it.

OK, I'm wrong about the performance penalty. It doesn't work by creating a new process per connection. I'll do some testing on your solution.

Socket activation means that the service is automatically started when a connection is made to the socket. But since the piped-proxy.service is started by the multi-user.target anyways this is not happening. I am only using systemd sockets because of permission issues when using the builtin unix socket listener.
I've changed the module to use systemd sockets only when listenPath is set.
If you have any more questions I'd be happy to answer :)

I'm still using this without any issues.
Just a friendly ping :)


Q: how to run test cases?

Apologies if I missed something.
I am about to create a pull request and wanted to run the test cases in advance, but grunt test gives me this output:
Running "karma:unit" (karma) task
19 04 2017 10:27:22.699:WARN [watcher]: Pattern "/home/sapient/angular-recaptcha/bower_components/angular/angular.js" does not match any file.
19 04 2017 10:27:22.701:WARN [watcher]: Pattern "/home/sapient/angular-recaptcha/bower_components/angular-mocks/angular-mocks.js" does not match any file.
19 04 2017 10:27:22.781:INFO [karma]: Karma v1.6.0 server started at http://<IP_ADDRESS>:9876/
19 04 2017 10:27:22.781:INFO [launcher]: Launching browser Chrome with unlimited concurrency
19 04 2017 10:27:22.787:INFO [launcher]: Starting browser Chrome
19 04 2017 10:27:23.361:INFO [Chrome 57.0.2987 (Linux 0.0.0)]: Connected on socket Ki8CrYvAsy6qL70mAAAA with id 66299035
Chrome 57.0.2987 (Linux 0.0.0) ERROR
  Uncaught ReferenceError: angular is not defined
  at src/module.js:9

Warning: Task "karma:unit" failed. Use --force to continue.

In other words, the module.js file expects a global object named angular which is not available in Chrome at runtime.

This is a sample config I've got:
Might it be that Karma is expecting that angular and angular-mocks are loaded with commonJS or so? and that the bower_components are not standalone scripts?

PS: what else do you suggest to test before opening a PR? I mean, given that reCaptcha does not work on localhost, the options seem quite limited ...

reCaptcha does work on localhost, you just need to provide your own reCaptcha key which has localhost defined as a domain.
Also, did you run npm install and bower install?


TestPointer changes

Driving a pointer in a test right now requires pumping, continually giving the original location, etc.
Instead the API should look something like:
TestGesture gesture = tester.startGesture(downLocation);
gesture.moveTo(newPoint1);
gesture.moveTo(newPoint2);
gesture.moveTo(newPoint3);
gesture.up(); // or gesture.cancel();

moveTo would dispatch a pointer move event with the new point, at downLocation, then pump.
gesture would also expose the TestPointer.
moveTo() would take optional argument "pump: false" or maybe "duration" which is how long to pump (and null would mean don't pump).

Sounds good.  Note that we should keep the hit test from the start and re-use it throughout.  Many tests perform new hit tests for move and up, which isn't what happens in real life.

/cc @apwilson


[IoT] IoT Operations Extension v0.1.0b1

Release notes for this extension can be found here:
https://github.com/Azure/azure-iot-ops-cli-extension/releases/tag/v0.1.0b1

This checklist is used to make sure that common guidelines for a pull request are followed.
Related command

General Guidelines

[ ] Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
[ ] Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

IoT


Provide inheritance through hierarchy

Idea

Create a page with icon:

Create a page that inherits an icon (my inheritance look at the tags property):

Check the icon rendering on sub page:

Expected behaviour:

All sub pages can inherit whole icon configuration from root page
All sub pages can inherit whole icon configuration from the rightmost parent page (in case of root page config overrided in one of the sub pages)

if you check the code - there are a lot of icon search attempts alreqady. adding more can do perf issues...
at least searching through all hierarchy. what if just add 1 level (most left) checking?


Add a transit feed: step 2/Add operators suggestions

This experience will change based on ongoing design work for loading states, but here are a few suggestions based on the current text.
Intro paragraph: "Your feed contains the following operators. Review the information below and provide additional details about each operator and location it serves." (I'd like to say metadata here, but not sure that is a known term?)
I think we could put the text "For operators that spread..." could be either in pop-up help if it's that important or in the help.

Let's keep the number generator. Rewrite to
All fields are required, other than municipality/region. (but no validations)
Rename State to State or Province


First attempt at integrating Facenet

Not intended to be approved, just to try running the CI (Replaces chestnut_dec_may test to be of Facenet).

Closed because: poetry build after merge fails.


[#29] setup repo for recipe installation

Describe the Pull Request
A clear and concise description of what the Pull Request is and link to existing issue.

[x] 👩🎓 I read contribution guidelines
[ ] 🐞 Pull request introduces a BC-Break
[ ] ✅ Pull request is covered by tests
[ ] 📒 Pull request is properly documented in docs

Codecov Report
Base: 76.88% // Head: 76.88% // No change to project coverage :thumbsup:

Coverage data is based on head (f941340) compared to base (da1b560).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff            @@
##               main      #33   +/-   ##
=========================================
  Coverage     76.88%   76.88%
  Complexity       86       86
=========================================
  Files            24       24
  Lines           359      359
=========================================
  Hits            276      276
  Misses           83       83

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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


Rails/FilePath autocorrect shouldn't remove important trailing slash in dynamic string containing Rails.root

I'm trying to use Rails.root to remove it from an absolute filepath to result in a filepath relative to Rails.root.
my_abs_path              = "/Users/me/rails_app/config/locales/text_en.yml"
expected_relative_result = "config/locales/text_en.yml"

my_abs_path.delete_prefix("#{Rails.root}/") == expected_relative_result
# => true

Expected behavior
# this should be allowed by Rails/FilePath cop because the last / in /Users/me/rails_app/ must be deleted, not just /Users/me/rails_app
my_abs_path.delete_prefix("#{Rails.root}/")

Actual behavior
my_abs_path.delete_prefix("#{Rails.root}/")
# raises Rails/FilePath, and is autocorrected to
my_abs_path.delete_prefix("#{Rails.root.join('')}")
# which raises Style/RedundantInterpolation, so we manually correct to
my_abs_path.delete_prefix(Rails.root.join('').to_s)
# which is wrong:
actual = my_abs_path.delete_prefix(Rails.root.join('').to_s)
actual == expected_relative_result
# => false
puts actual
# => "/config/locales/text_en.yml"

# so we try giving an argument to join, but still wrong because Rails.root.join never adds a trailing slash:
actual = my_abs_path.delete_prefix(Rails.root.join('./').to_s)
actual == expected_relative_result
# => false
puts actual
# => "/config/locales/text_en.yml"

Steps to reproduce the problem
Copy the below into a file, run RuboCop with autocorrect enabled and manually fix any other cops that are raised, then assert that the result is true.
rubocop-rails-filepath-test.rb
# where Rails.root is /Users/me/rails_app
my_abs_path = "/Users/me/rails_app/config/locales/text_en.yml"
expected_relative_result = "config/locales/text_en.yml"

actual = my_abs_path.delete_prefix("#{Rails.root}/")
if actual != expected_relative_result
  raise "Invalid autocorrection: #{actual.inspect} != #{expected_relative_result.inspect}"
end

rubocop -a rubocop-rails-filepath-test.rb
rubocop -A rubocop-rails-filepath-test.rb # autofix Style/RedundantInterpolation
bin/rails c < rubocop-rails-filepath-test.rb

RuboCop version
1.57.2 (using Parser <IP_ADDRESS>, rubocop-ast 1.30.0, running on ruby 3.0.6) [arm64-darwin21]
  - rubocop-rails 2.22.1
  - rubocop-rspec 2.18.1

I can see autocorrection was added in #991 so is this considered a bug of that? If so, then I can submit a fix that allows "#{Rails.root}/" if that's acceptable?
I also saw #1071 which might get fixed at the same time; I can check.
Also theres https://github.com/rubocop/rubocop-rails/issues/434 which includes the exact same case as this.


Add test for 400 Bad Request

Go fmt update, and test/functionality for 400 Bad Request.

Thanks for the PR. Mind rebasing off the latest master? I updated the source files with gofmt.

Thanks - I'll rebase and resubmit. Glad to see this project still getting work.


API Keys page raises Errors when sorting

Add a quick filter to the API Keys page
click on various column headings to sort

Fixed in > beta.199


Add the ability to configure soulbound further

This adds further options for users to customize their own version of soulbound, in particular it controls the various options of the enchanted book.
To make it neater, i moved soulbound into its own category for the configs, and match a similar format as with the other enchantment.
By default, soulbound is set to treasure enchant true, and villager trading true, as per your previous default configuration.
It's my first attempt at modding something here, so do correct me if i did something wrong.

Yeah I have gone past this thinking to myself "why didn't I include that?". I think this would do the trick, there's just the issue what happens when someone updates, and the config system is changed. Most likely, they will get an error about the config file containing the wrong information.
I will take an extra look to see if I can fix this in some way though. Will probably move some stuff around, to fit more with namings and such if I find a way to implement this, but thank you anyway for taking the time to write this. I will look over the PR again when I have time, probably next weekend

I've added this in commit 5676a19b3070b42e00d750ffb91ca055744d4e54. Changed a few things from this PR, but only config names and such, to keep it in style with the rest of the config. I was able to avoid the config error by just renaming customSoulboundEnchant to soulboundEnchant in the configs. I also added the same configurability for the deathsight enchantment, although that enchantment is disabled by default.
I'm closing this PR without merging because I already implemented it. That's what I found easiest so that's what I did. I will make sure to release the update within the next few days


I think there has a problem

https://falco.org/docs/rules/
I tried this ,but didn't work, I think the value of evt.typeshould be openat

hello?

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle rotten

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://github.com/falcosecurity/community.
/close

@poiana: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://github.com/falcosecurity/community.
/close

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.


deis pull registry returns error "Tag not found" on 1.8.0

I just set up a new 1.8.0 cluster on AWS but am unable to migrate my apps. deis pull is throwing the "Tag not found" error described in #3218 and others.
deis pull registry.<deis domain>:5000/<app>:<version number>
deis pull registry.<deis domain>:5000/<app>:v<version number>
deis pull <public IP of registry>:5000/<app>:<version number>
deis pull <public IP of registry>:5000/<app>:v<version number>
return an error:
Creating build... 503 SERVICE UNAVAILABLE
Detail:
GET Image Error (404: {"error": "Tag not found"})

The only deviation from a default install of deis is that I have disabled proxy protocol per the documentation.
I have tried opening up TCP 5000 on both clusters' ELB security group, and ELB but that did not seem to make a difference.
I have tried opening up TCP 5000 on the VPC security group that the instances use but that didn't seem to make a difference either.
The output of /opt/bin/deis-debug-logs and deisctl journal registry for both clusters can be found here.
Has anyone else been experiencing this on 1.8.0?
Thank you in advance for your help, cheers! :beers:

@clayzermk1 Can you also confirm the Docker version on both old and new hosts?

From the logs, it looks like your internal registry can't connect to your external registry: https://gist.github.com/clayzermk1/c363ee6293a580431cfe#file-deisctl-journal-registry_on_180-L19

@carmstrong The old stack is 1.4.1 and the new one is 1.8.0.
@bacongobbler Thank you. I wonder why. Is the only port used for this operation TCP 5000?

@clayzermk1 yep! deis pull essentially emulates a "docker pull" from the old docker v1 API. The code which is invoked on a deis pull can be seen here, for reference.
To oversimplify things, the registry is pulling the layers directly from your remote registry and tagging it as myapp:vn. The error is confusing on the client's end, but that's mostly been because we're looking to EOL deis pull in favour of deis push.

ping @clayzermk1, were you able to resolve this issue?

Just got back around to this now actually. Will let you know before EOD.

@bacongobbler I took another look at my EC2 SG/ELB configuration and made sure TCP 5000 was on everything just for giggles - no dice, still getting timeouts. At this point unless you would like me to help debug this issue, I'm content just re-creating the apps on the new cluster.

I tore down my 1.8.0 cluster.


[HIVEMALL-28] Set HIVEMALL_HOME to absolute path

Set HIVEMALL_HOME to absolute path.

Coverage remained the same at 35.842% when pulling 0d6cafbf819c6d09a2e6ba2e135c166bd2910d4d on wangyum:HIVEMALL-28 into 38224bb23bd64ebc5187a1fd506d2031b6d0f446 on apache:master.

@wangyum Thank you for the contribution.
@maropu Could you review this one?

@wangyum Thanks for your work! What does this pr solve? Any issue in the current script?

@wangyum oh, I found you've already described that in the JIRA ticket. Could you write "what does this pr solve?" in this description? If you update that , LGTM. cc: @myui

@maropu I have updated the description.

LGTM cc: @myui

@wangyum merged. Thank you for the contribution!


Registry: function to return current version

return latest active gif version

addressed in https://github.com/etherisc/gif-next/pull/189
release manager provides getLatestVersion(), while registry::getMajorVersion points to it


(backport) SEC-592:  Customize Jetty request queue and threadpool size (#172)

Ability to customize the thread pool and size of request queue.

@confluentinc It looks like @srpanwar-confluent just signed our Contributor License Agreement. :+1:
Always at your service,
clabot


Adds next and previous buttons to the handbook

Adds next/prev buttons to the bottom of the handbook when pages are chonologically sorted

For non-chronologically ordered - we could consider re-listing the sections below

Looks good to me 👍


Directives Tracking

I think we need to develop some directives to tie/hook into Intercom. If anyone has other ideas about what to put here, please add it as a comment below.
Current Plan:

[x] Show Intercom: show a new message window
[x] Show Intercom with Message: Show a new message window prepopulated with content
[ ] Track event: Track an event by name
[ ] Log Out/Shutdown: shut down intercom, for use on a log out button

@scott-wyatt I'm going to make some changes shortly, I'll let you know. Can you put them in an beta channel on NPM (not the primary channel so we don't screw up people's deps yet)

@scott-wyatt if you just want to add me to the NPM page, that should also work. I'm also @wbhob on NPM

@wbhob you are now an owner of ng-intercom on npm

Yay I published alpha 1.


Fix Rancher healthcheck doesn't work as expected

Fixes #2279
Here is the small change I did to fix the issue. I tested locally and it works.
It is my first go changes so I am sure this could be better

We would love to merge your Pull Request to fix the problem but unfortunately, we cannot find information on this "upgrading" state in the official documentation.
Excerpt :

The current state of the instance. The options are creating, error, erroring, migrating, purged, purging, removed, removing, requested, restarting, restoring, running, starting, stopped, stopping, updating-running, updating-stopped.

Could you provide us with more information on the matter?

We are using Rancher and Traefik in prod and I developed an app that is integrated with our CICD to deploy automatically our application on Rancher.
Here are examples of different states I am getting from Rancher when an update is executed.
2018-03-02 12:42:13.400  INFO 1 [ XNIO-2 task-48] c.e.w.c.r.d.service.ApplicationService    serviceName=cs-ch-trover-adapter; health state=initializing and service's state=upgrading
2018-03-02 12:42:13.423  INFO 1 [ XNIO-2 task-23] c.e.w.c.r.d.service.ApplicationService    serviceName=cs-ch-trover-adapter; health state=healthy and service's state=upgraded
2018-03-02 12:42:08.398  INFO 1 [ XNIO-2 task-23] c.e.w.c.r.d.service.ApplicationService    serviceName=cs-ch-trover-adapter; health state=healthy and service's state=upgrading
2018-03-02 12:42:03.373  INFO 1 [ XNIO-2 task-23] c.e.w.c.r.d.service.ApplicationService    serviceName=cs-ch-trover-adapter; health state=degraded and service's state=upgrading

Best
Jerome

@jmirc could you rebase on the v1.5 branch.

close this issue based on master in favor of #2962 which is based on v1.5

@jmirc for the next time, I recommend to you to use a dedicated branch when you do a PR (e.g. not master or v1.5).

@ldez Sorry about that. I will do it.

@jmirc don't change anything for now :wink:
And also next time, please try to respect PR description template.


FIxing ophaned code block error

FIx mistake in leaving a code block, which messed up formating for readme.

Codecov Report

Merging #18 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master    #18   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           3      3
  Lines         430    430
=====================================
  Hits          430    430

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 8183053...5db81dd. Read the comment docs.


Vaadin 8.0beta1 - Vaadin7 components from compatibility module not available

Since not all vaadin components are available on beta1 (most notably Tree, planned for Vaadin 8.1), there's a compatibility module available (vaadin-compatibility-server, vaadin-compatibility-client), but It is not used by this project.

Fixed in pull request #2

Pull-Request integrated. Created a new branch to keep origin/master as clean as possible.
Intention of the project was to show how easy you can get started with Vaddin8 :)
Thanks anyways


✨ Automatically add negative values for number config.values

Description
Input:
export default {
    values: {
        '1x': 16
    }
}

Instead of 1x you can also use -1x:

...

The principle of how it works is straightforward - it automatically creates the '-1x': -16 configuration value for you:
export default {
    values: {
        '1x': 16,
+       '-1x': -16
    }
}

typeof values[x] === 'number'

Naming conventions
🟢 Mathematical expression.

key: {number}x

export default {
    values: {
        '1x': 16,
    }
}

🔴 Collides with default unit conversions and native property values.
export default {
    values: {
        '1': 16,
    }
}

In the syntax of the Master CSS standard, font:1 is equal to font-size: 0.0625rem, but now you override it to font-size: 1rem.
You can change the preset syntax behavior, but this is not recommended; try to keep Master CSS syntax consistent throughout.
🟠 The markup is not readable enough.
export default {
    values: {
        foo: 16,
    }
}

Since the value of font:foo does not start with a number, in addition to being less readable, Master CSS cannot treat it as font-size, you can only use font-size:foo explicitly:

 🧐

🎉 Released at v2.0.0-beta.148


sth. wrong when use "resolve.alias" with cdn url

Describe the bug
It can't work when use "resolve.alias" with "vue" and "vue-router" cdn.
And the browser showed error message is "Uncaught TypeError: Failed to resolve module specifier "vue". Relative references must start with either "/", "./", or "../"."
Reproduction
in my vite.config.js
import { defineConfig } from 'vite'
import vue from '@vitejs/plugin-vue'

// https://vitejs.dev/config/
export default defineConfig({
  server: {
    port: 8080
  },
  resolve: {
    alias: {
      'vue': 'https://cdnjs.cloudflare.com/ajax/libs/vue/3.0.5/vue.esm-browser.js',
      'vue-router': 'https://cdnjs.cloudflare.com/ajax/libs/vue-router/4.0.4/vue-router.esm-browser.js',
    }
  },
  optimizeDeps: {
    exclude: [
      'vue',
      'vue-router'
    ]
  },
  plugins: [vue()],
})

System Info
in my package.json
{
  "name": "vite-project",
  "version": "0.0.0",
  "scripts": {
    "dev": "vite",
    "build": "vite build",
    "serve": "vite preview"
  },
  "dependencies": {
    "vue": "^3.0.5",
    "vue-router": "^4.0.4"
  },
  "devDependencies": {
    "@vitejs/plugin-vue": "^1.1.4",
    "@vue/compiler-sfc": "^3.0.5",
    "vite": "^2.0.1"
  }
}

Logs (Optional if provided reproduction)
the log is right
  vite v2.0.2 dev server running at:

  > Local:    http://localhost:8080/

  ready in 376ms.

The ESM build of vue-router at https://cdnjs.cloudflare.com/ajax/libs/vue-router/4.0.4/vue-router.esm-browser.js contains non-rewritten import * from 'vue'. Vite doesn't rewrite imports from external files.
You need to use a ESM-compiled CDN like https://www.skypack.dev/ or https://www.jsdelivr.com/esm.


Add an option for appending trailing slash

Django will redirect if missing trailing slashes, but this will only work for GET.  Redirects will also not work if doing a cross origin request while developing (eg localhost:4000 -> localhost:8000)

Some more info: I tried removing the trailing slashes from my DRF router, however there are assumptions in amygdala that the urls specified in the schema config will always have a trailing slash: https://github.com/lincolnloop/amygdala/blob/master/amygdala.js#L130


Time out after last "pooling" update

Hi ! i got timeout after last update:
[6/3/2020, 9:43:03 PM] [Bed Room Air Purifier] getCurrentAirPurifierState Failed: MIOTDevice is not responding
[6/3/2020, 9:43:03 PM] [Bed Room Air Purifier] getActive
[6/3/2020, 9:43:03 PM] [Bed Room Air Purifier] getActive Failed: MIOTDevice is not responding
[6/3/2020, 9:43:03 PM] [Bed Room Air Purifier] getTargetAirPurifierState
[6/3/2020, 9:43:03 PM] [Bed Room Air Purifier] getTargetAirPurifierState Failed: MIOTDevice is not responding
[6/3/2020, 9:43:03 PM] [Bed Room Air Purifier] getFilterChangeIndication
[6/3/2020, 9:43:03 PM] [Bed Room Air Purifier] getFilterChangeIndication Failed: MIOTDevice is not responding
[6/3/2020, 9:43:03 PM] [Bed Room Air Purifier] getBuzzer
[6/3/2020, 9:43:03 PM] [Bed Room Air Purifier] getBuzzer Failed: MIOTDevice is not responding
[6/3/2020, 9:43:03 PM] [Bed Room Air Purifier] getHumidity
[6/3/2020, 9:43:03 PM] [Bed Room Air Purifier] getHumidity Failed: MIOTDevice is not responding
[6/3/2020, 9:43:03 PM] [Bed Room Air Purifier] getLED
[6/3/2020, 9:43:03 PM] [Bed Room Air Purifier] getLED Failed: MIOTDevice is not responding
[6/3/2020, 9:43:03 PM] [Bed Room Air Purifier] getTemperature
[6/3/2020, 9:43:03 PM] [Bed Room Air Purifier] getTemperature Failed: MIOTDevice is not responding

I got similar issue, but after using the mi home app, to change few settings. e.g. switch modes. the device seemed to have connected fine.
I will keep an eye out on the issue.
for the time beng, ensure you have updated the config file to the latest spec.
{
"accessory": "MiAirPurifier3",
"name": "Bed Room Air Purifier",
"ip": "192.168.1.x",
"token": "xxxxxxxxxxxxxxxxxxx",
"did": "xxxxxxxxx",
"enableLED": true,
"enableBuzzer": true,
"pm25_breakpoints" = [5, 12, 35, 55],
"polling_interval": 60000
}

@github9984 i changed some settings in mi app and that was not help me, i have this config:

hmm, i remove:
"showTemperature": true,
"showHumidity": true,
"showAirQuality": true,
in my config, and this helped me...


Possibility to disable blue ripple effects

using the setting "scroll sync" on "selection change", the preview document scrolls nicely, however, every keystroke there is a blue ripple effect, would an option to disable this behavior be possible?

I thought it might be a nice QOL improvement if there was a toggle.

the ripple effect is used to indicate the target src2preview jump. in this case this can be improved


Add Http Forwarder

trap2json supports Kafka integration and others except HTTP Is it possible to add HTTP forwarder

Our first request on our first open source project!
Yes it is possible and I think it's trivial to implement. We still don't know when to add http support, since internally we don't use it. However, feel free to submit PR!

Well since I had free time, I implemented what you asked. It should be available soon in v0.5.0. Let me know what you think!


Removing deleted and private submissions from collection

Purpose
Deleted and private nodes should not appear in a collection
Changes
Making management command to fix this
QA Notes
Please make verification statements inspired by your code and what your code touches.

Verify
Verify

What are the areas of risk?
Any concerns/considerations/questions that development raised?
Documentation

Side Effects

Ticket

Closing in favor of #9635


[default] Problem with "about us" static page

Current behavior
We can enter empty "Aubout us" page from sidebar links but after refresh we get "We can't find the page"

Expected behavior
"About us" page link sould render static page or it should be removed
Steps to reproduce the issue
Visit: demo.storefrontcloud.io as a guest
Click on menu
Select "Track my order"
Click on "About us" sidebar link
Refresh page

I'm gonna do this one! 🙋

PR here: https://github.com/DivanteLtd/vue-storefront/pull/2325


Rule shorthand-property-no-redundant-values not working when have variables for value in sass

When I use variables in the value, shorthand-property-no-redundant-values rule is not working.
For example following code will not get alert:
$baseline: 8px; .foo {   padding: $baseline 0 0 0; }
Any fix for this will be added?

That rule is part of stylelint and not this project. Most of the stylelint rules are meant to use with CSS, so they don't work with SCSS syntax.
You might want to report this to https://github.com/stylelint/stylelint and see what they respond. It might be that it won't get fixed unless we implement a similar rule for stylelint-scss that supports your code example.

I created this issue their, but they asked me to report here...
https://github.com/stylelint/stylelint/issues/2790

It might be that it won't get fixed unless we implement a similar rule for stylelint-scss that supports your code example.

That's correct. The built-in rules simply ignore non-standard constructs. As such, a new scss/shorthand-property-no-redundant-values rule within this plugin pack is the way forward. Unlike the built-in rule, this new rule wouldn't ignore SCSS variables. @copiali Please consider contributing the rule to stylelint-scss if you think it'll be useful to you and others.


MSID: 88837 Version: 2 DOI: 10.1101/2<IP_ADDRESS>6635

MSID: 88837
Version: 2
Preprint DOI: https://doi.org/10.1101/2<IP_ADDRESS>6635
Step 1. Awaiting reviews
Editorial to post reviews via hypothesis
Useful links:

DocMap: https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=88837
New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
Reviews on sciety: https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>6635

For trouble shooting (e.g. no Docmaps available):

DocMap issue addressing: https://miro.com/app/board/uXjVNCwK6EI=/
Explore DataHub DocMaps API: https://lookerstudio.google.com/reporting/4c2f0368-babb-4beb-b5b3-497e7e7b0f08/page/ejphD
Unmatched submissions and preprints: https://lookerstudio.google.com/u/0/reporting/9f86204f-3bf7-477c-9b18-5c5ef141bf69/page/p_gxi57ha93c
Unmatched manuscripts spreadsheet: https://docs.google.com/spreadsheets/d/15QcK8w-ssB7109RQEDtFpJPZ0J5HTGxoHa_2TtpMBbg/edit#gid=1336081641

Step 2. Preview reviewed preprint
Production QC content ahead of publication
Instructions:

QC preview: https://prod--epp.elifesciences.org/previews/88837v2
Update ticket with any problems (add blocked label)
When QC OK, add QC OK label to ticket and add publication date and time to https://docs.google.com/spreadsheets/d/1amAlKvdLcaDp5W8Z8g77NmkwbMF5n_u89ArSqPMO8jg
Move card to next column
(At end of the day post link in #enhanced-preprint and ask for PDF to be generated)

Useful links:

Preprint DOI :  https://doi.org/10.1101/2<IP_ADDRESS>6635
Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/88837/v2/reviews
To update the MECA path in the docmap: https://docs.google.com/spreadsheets/d/1mctCQuNFBjSn97Lihy7_vBO6z7-N-oqyLv4clyi6zHg

Step 3: Awaiting search reindex
This step adds the reviewed preprint to the homepage: https://elifesciences.org
The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.
Useful links:

Jenkins pipeline to reindex search can be triggered sooner or monitored here: https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 4: Published! PDF requested
Waiting for PDF to be generated
Useful links:

PDF tracking: https://docs.google.com/spreadsheets/d/106_XeDjmuBae7gexOTNzg60lapeqjl2aRn9DzupGyS8/

Step 5: Introduce PDF to data folder and git repo
Upload PDF to relevent folder in git repo https://github.com/elifesciences/enhanced-preprints-data/
Step 6: Done!

[ ] Kettle is on!

Schematron:
error: This journal reference (id c50) has no article-title element.

@fred-atherden Reviewer 1's comments include this - can we format it better?

Thanks for flagging @naushinthomson.
@acollings, could you assist with the above please? Presumably the presence of hashtags at the start of the line mean that this is being treated as a header as per markdown formatting. If we were maybe to add a space before the hashtags, I think it would  no longer be treated as headers?:

Thanks @acollings, I'm still not seeing a space in the hypothesis comment though, maybe leading spaces are stripped by default by hypothesis? If that were the case I think we'd still run into the issue unfortunately.
Could we try adding a no break space -   - instead?

Wow, @fred-atherden I never knew there was a "no break space"! This is what it looked like before so I think something is getting stripped:

I've now tried the no break space...

Thanks Andy - let's see what it looks like on Monday! (Aren't you supposed to be on holiday!?)

Ha, yes, I am, honest :-)

Unfortunately, it looks like the space has still been stripped out of Hypothesis:

Hi @JGilbert-eLife I've just tried something else. Take a look and see if it'll work?!

Looks good to me! I'll need to pull this across again tomorrow.


Minor correction regarding brew instructions

The argument --HEAD should have been after install.

Thank you,
FYI I will update and clean the homebrew formula after the next release (~ end of april).

Sounds good.


webhooks headers (feature request)

Hi, thank you for this nice alarmserver.
I was wondering if you could add the parameter of an "Authorization: Bearer" header in the webhooks (or a generic header parameter).
Many services require some headers and in this way, one may directly call Home Assistant REST APIs without calling MQTT, if needed.
You may have a look here on the REST API page.
From the go http client page it seems pretty straightforward (just use webhooks.client.Header.Add,() but it would need to change the configuration package and the SendMessage func... and I'm not very confortable with GO.
Thank you.

I'm definitely interested in implementing this feature and to make webhooks more usable in general and I'm glad you brought that up. Thank you!
I have recently moved and all my cameras are not connected yet so there is going to be some delay with me implementing it. However, I have started writing some code already; just warning against expecting it being merged into main any time soon 😄

That's great news!
I started myself trying to build the code to be able to change it and test it, but it seems some dependencies have changed and I get the following messages:
~/go/src/github.com/toxuin/alarmserver$ go build ../../spf13/viper/internal/encoding/hcl/codec.go:8:2: cannot find package "github.com/hashicorp/hcl/hcl/printer" in any of:         /usr/src/github.com/hashicorp/hcl/hcl/printer (from $GOROOT)         /home/marco/go/src/github.com/hashicorp/hcl/hcl/printer (from $GOPATH) ../../../goftp.io/server/v2/compat.go:17:2: cannot find package "goftp.io/server/core" in any of:         /usr/src/goftp.io/server/core (from $GOROOT)         /home/marco/go/src/goftp.io/server/core (from $GOPATH) ../../../goftp.io/server/v2/compat.go:18:2: cannot find package "goftp.io/server/driver/file" in any of:         /usr/src/goftp.io/server/driver/file (from $GOROOT)         /home/marco/go/src/goftp.io/server/driver/file (from $GOPATH) ../../../goftp.io/server/v2/compat.go:19:2: cannot find package "goftp.io/server/driver/minio" in any of:         /usr/src/goftp.io/server/driver/minio (from $GOROOT)         /home/marco/go/src/goftp.io/server/driver/minio (from $GOPATH)
Any suggestions?

You can see the way it's built in the Dockerfile:
go get -d ./... && CGO_ENABLED=0 go build -ldflags="-w -s" -o ./out/alarmserver
I hope that helps!

Yep, thank you!
I had to:
export GO111MODULE="on"

and then run:
go get -d ./... && CGO_ENABLED=1 go build -gccgoflags="-w -s" -o ./out/alarmserver

with CGO_ENABLED=1, or I would get errors like:
/go/pkg/mod/golang.org/x/sys@v0.0.0-20200323222414-85ca7c5b95cd/unix/gccgo.go:50: undefined reference to `gccgoRealSyscallNoError'

Now it's building and running as expected.
Will post here any news...

I've worked a bit on this and it seems to work fine in my synthetic setup.
@alitaker are you able to test this new implementation? All my cameras are still in boxes somewhere -__-
You have to either build the branch webhook-headers or use docker image tagged toxuin/alarmserver:webhook-headers.
Please be my QA for this! 🙏  I'm hopeful you can test it at least a little so I can make a new release with this feature.
I appreciate your help! ^_^

Yes, I have a couple of cameras I can test it on.
Will let you know as soon as the setup is up and running.

Hi @toxuin , just to report... I still have to debug it, but I keep getting:
Got no response from https://<my_ha_server>:<my_ha_port>/api/states/binary_sensor.dev001

Maybe it's a docker thing, will check when I have more time
BTW, my config now is:
hisilicon:
  enabled: true
  port: 15003

webhooks:
  enabled: true
  urls:
    - "https://<my_ha_server>:<my_ha_port>/api/states/binary_sensor.dev001"
  headers:
    - "Authorization: Bearer <my_ha_token>"

Most likely this is due to connectivity within docker and its ports (container/host ports, etc).
However, this exact use case would not work currently, as this particular endpoint expects a certain schema of the request that alarmserver definitely does not conform to. Here's the link to Home Assistant API docs and it requires there to be a state field which does not exist on the JSON that Alarmserver sends.
There are infinite use cases with webhooks, so just outputting Alarmservers own internal JSON schema would be the most versatile way as it would not require me to write a wrapper for every API in existence, nor would it require users to write some kind of templated config to send webhooks in a specific format.
For your specific use case though - would MQTT integration be not sufficient? Do you run a home assistant without MQTT broker?

Yes, I am aware of the HA APIs requirements.
Actually I started using HA without MQTT and before starting with Alarmserver in GO, I made some modifications to the PHP implementation PhpCameraAlarmGateway (forked here).
My fork rewrites the JSON with device_class=motion, state=on|off, custom icon and friendly_name (ready for HA UI)
Indeed that would be a very specific webhook implementation, but I guess it's one of the most used, so for me it's worth it.

Do you use nodered by any chance? You could expose the webhook endpoint and transform the payload in nodered - maybe that would be an option?

Oops, I've also found a small mistake in your config:
webhooks:
  enabled: true
  urls:
    - "https://<my_ha_server>:<my_ha_port>/api/states/binary_sensor.dev001"
  headers:
    - "Authorization: Bearer <my_ha_token>"

shoud be
webhooks:
  enabled: true
  items:
    - url: "https://<my_ha_server>:<my_ha_port>/api/states/binary_sensor.dev001"
      headers:
        - "Authorization: Bearer <my_ha_token>"

webhooks.urls config key is the "old" implementation and is basically just a shorthand with all the default options for a webhook (POST method, no headers).

I was today years old when I discovered there's Webhook trigger in Home Assistant 🤦
I am just mentioning here in case it would be advantageous for your use case @alitaker .
In combination with binary_switch it could be an easy solution to the above problem - no node-red required.

Yes Webhook triggers seem very useful.
I'm currently using the states API to alter a virtual binary sensor in HA, so I can check in the history and see what happened to that sensor (I have other non-virtual binary sensors and this way seems more linear as every detector has its sensor).
The webhook would be a quicker implementation though, because you skip the binary sensor (definition+state change).
I'll probably test both ways... as soon as I find some spare time! :sweat_smile:
Thanx!


Double monitor, double layout usage

I am using two monitors and the main monitor is vertical and side monitor is horizontal. I have tried to move the mouse around the corners to obtain the boundaries of the monitors. However it does not seem correct. See the image.

Do you handle the multiple monitor case?

I'm sorry, I have no idea how I managed to not notice for so long that there are open issues on this project.
No, multiple monitors are currently totally unsupported. Is this something you're still interested in?

I would be interested in that.
The setup i'm using has three monitors where each of them has a different size and iirc in my testing a few months back it seemed like as if the mouse movements on all screens are overlayed on top of each other.
Screens from left to right: 1920x1080, 2560x1080, 1600x900
It's a weird setup and i can fully understand if it won't get full support.

it seemed like as if the mouse movements on all screens are overlayed on top of each other

Yep, as the program currently assumes a single display, all mouse movement is mapped onto a single target in program statistics.
I think that if multiple monitor support can be added, it will work also if there are more than 2 monitors.
But just to check, can you do the following on your three-monitor system:

run InputScope
right-click on the tray icon and choose "Show Python console"
in the console window, execute for i in range(wx.Display.GetCount()): print i, wx.Display(i).Geometry

What is the result?

The Output is:
0 (0, 0, 2560, 1080)
1 (-1920, 0, 1920, 1080)
2 (2560, 237, 1600, 900)

The new v1.3 release has support for multiple displays.
Can you confirm it works on your setup?

The new v1.3 release has support for multiple displays.
Can you confirm it works on your setup?

On 1.3 and 1.4 multi monitor seems to work great.
The only "problems" i found so far is that the heatmap preview is stretched to 16:9 and on my rightmost monitor the capture speed seems to be lower than on the other screens (though that screen is the oldest and the only one connected via DVI)

Excellent, glad to hear it's working as intended.
Yes, mouse heatmap is always scaled to 16:9 - because a display can have any number of resolutions applied on it over time. But perhaps in a next release I will use the scale of the first recorded screen size, as anyway most people do not change the resolution much.
Your rightmost monitor is the largest one, right? The seemingly lower capture speed is probably because InputScope reduces mouse movement events, first by scaling them to heatmap size and skipping those in the same location, and then by merging linear movement events that are close enough in time and space.
If you like, there are some configuration directives you can add to inputscope.ini to tweak the linear reduction:

MouseMoveJoinInterval is maximum seconds between linear movement events to merge
MouseMoveJoinRadius is maximum pixels between linear movement events to merge, in heatmap scale

Setting either to 0 will effectively disable the reduction of linear movement. Just add the directives to inputscope.ini when InputScope is not running. But be advised that there can be very many mouse movement events per second if they're not being reduced.


Children of  must have a path or default prop

I see this has been discussed before, but still seems to be an issue ( #248 )
Here is a codesandbox (nav to either one or two):
https://codesandbox.io/s/reach-router-children-bug-pqei6
This sandbox is a very narrow example, in my case I have a real use case for wanting my "Route" to have children and use those children rather than using a prop.

Hi,
You are right. Actually using prop children doesn't work.
If you pass the children through another props, it works : https://codesandbox.io/s/reach-router-children-bug-uhk64?fontsize=14&hidenavigation=1&theme=dark.
I encountered this problem before, I thought I had posted an issue but didn't. Thanks for bringing that up ;)

thanks!
yes, for now, i am using a render prop rather than using children.
children prop, however, is easier to iterate / clone.
i think the issue stems from the RouteComponents ability to have a nested structure, as seen here:
https://reach.tech/router/api/RouteComponent
(section: Children elements, Route Prop)


scope $container var to support different containers

scoped window and container vars to allow different elements to use different containers.
The bug occurred if you tried to do something like:
$('li').children('img').lazyload({
container: $(element).parent()
});
$('body').children('img').lazyload();
The first set would have their container reset to window.

Thanks for the feedback ssorallen. You're keeping me honest!
I $-prefixed $container, and instead of passing it into the convenience functions, used the value in settings. The minified version is now a bit smaller, and the convenience functions will also not suffer from the bug I set out to fix with this patch.

Awesome. I will merge this for 1.8.0. Hopefully release it during this weekend.


Switch to supported version of docker image

That would enable stackdriver logging for example.

Closing this due to lack of response.
Please reopen if/when you sign the CLA.


[MSAL with REACT] loading configuration from json

Core Library
MSAL.js v2 (@azure/msal-browser)
Core Library Version
"@types/react": "^17.0.16",

Wrapper Library
MSAL React (@azure/msal-react)
Wrapper Library Version
"@azure/msal-browser": "^2.16.1",
Description
Configuration:
"@azure/msal-browser": "^2.16.1",
"@azure/msal-react": "^1.0.1",
"@types/node": "^12.20.19",
"@types/react": "^17.0.16",
"@types/react-dom": "^17.0.9",
I have added config.json file in public folder. in App.tsx file   we have to use   . here the pcs should be initialized with config.json values . any example reading values from json and initialize authentication
MSAL Configuration
auth: {
        clientId: "clientid",
        authority: "https://login.microsoftonline.com/b2c_tententid",
        redirectUri: "http://localhost:3001/",
        navigateToLoginRequestUrl: true,

    },

Relevant Code Snippets
No response
Identity Provider
Azure B2C Custom Policy
Source
Internal (Microsoft)

hey @Shyam268 sorry for late response. We recommend initializing msal instance outside of your React component tree, for example in your index.js file:
import React from "react";
import ReactDOM from "react-dom";

import { MsalProvider } from "@azure/msal-react";
import { Configuration,  PublicClientApplication } from "@azure/msal-browser";

import App from "./app.jsx";

// MSAL configuration
const configuration: Configuration = {
    auth: {
        clientId: "client-id"
    }
};

const pca = new PublicClientApplication(configuration);

// Component
const AppProvider = () => (
    <MsalProvider instance={pca}>
        <App />
    </MsalProvider>
);

ReactDOM.render(<AppProvider />, document.getElementById("root"));

As such, you can simply delay rendering your app until the json file is fetched. For example:
import React from "react";
import ReactDOM from "react-dom";

import { MsalProvider } from "@azure/msal-react";
import { Configuration,  PublicClientApplication } from "@azure/msal-browser";

import App from "./app.jsx";

fetch(window.location.origin + '/config.json') // from your "public" folder
  .then((response) => response.json())
  .then((config) => {
      const pca = new PublicClientApplication(config);

      // Component
      const AppProvider = () => (
          <MsalProvider instance={pca}>
              <App />
          </MsalProvider>
      );

      ReactDOM.render(<AppProvider />, document.getElementById("root"));
  });

Let me know if that's not what you had in mind.