geolocator dependency problem

💬 Questions and Help
FAILURE: Build failed with an exception.

What went wrong:
Could not determine the dependencies of task ':geolocator:compileDebugAidl'.

Could not resolve all task dependencies for configuration ':geolocator:debugCompileClasspath'.
Could not resolve com.google.android.gms:play-services-location:17.0.0.
Required by:
project :geolocator
Could not resolve com.google.android.gms:play-services-location:17.0.0.
Could not get resource 'https://dl.google.com/dl/android/maven2/com/google/android/gms/play-services-location/17.0.0/play-services-location-17.0.0.pom'.
Could not GET 'https://dl.google.com/dl/android/maven2/com/google/android/gms/play-services-location/17.0.0/play-services-location-17.0.0.pom'.
Connection reset
Could not resolve com.google.android.gms:play-services-location:17.0.0.
Could not get resource 'https://dl.google.com/dl/android/maven2/com/google/android/gms/play-services-location/17.0.0/play-services-location-17.0.0.pom'.
Could not GET 'https://dl.google.com/dl/android/maven2/com/google/android/gms/play-services-location/17.0.0/play-services-location-17.0.0.pom'.
Connection reset

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

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

BUILD FAILED in 9m 3s
Exception: Gradle task assembleDebug failed with exit code 1

Could not get resource 'https://dl.google.com/dl/android/maven2/com/google/android/gms/play-services-location/17.0.0/play-services-location-17.0.0.pom'.

That file downloads perfectly fine for me. Maybe you or google had a some downtime? Could you try again with a working internet connection?


Scalapb sparksql does not work with Spark 3 (preview)

I tried building sparksql-scalapb with spark version 3.0.0-preview2 and it built successfully, but there are runtime errors, mainly missing spark encoders.
I have constructed a minimal example and test here:
https://github.com/SaiKiranBurle/sparksql-scalapb-test
The test can be done using sbt test
The specific error that I got from the above test is:
[error] java.lang.NoSuchMethodError: org.apache.spark.sql.catalyst.encoders.ExpressionEncoder.<init>(Lorg/apache/spark/sql/types/StructType;ZLscala/collection/Seq;Lorg/apache/spark/sql/catalyst/expressions/Expression;Lscala/reflect/ClassTag;)V
[error]         at frameless.TypedExpressionEncoder$.apply(TypedExpressionEncoder.scala:45)
[error]         at scalapb.spark.Implicits.typedEncoderToEncoder(TypedEncoders.scala:130)
[error]         at scalapb.spark.Implicits.typedEncoderToEncoder$(TypedEncoders.scala:127)
[error]         at scalapb.spark.Implicits$.typedEncoderToEncoder(TypedEncoders.scala:133)
[error]         at ProtoTest.$anonfun$new$1(ProtoTest.scala:26)
[error]         at org.scalatest.OutcomeOf.outcomeOf(OutcomeOf.scala:85)
[error]         at org.scalatest.OutcomeOf.outcomeOf$(OutcomeOf.scala:83)
[error]         at org.scalatest.OutcomeOf$.outcomeOf(OutcomeOf.scala:104)
[error]         at org.scalatest.Transformer.apply(Transformer.scala:22)
[error]         at org.scalatest.Transformer.apply(Transformer.scala:20)
[error]         at org.scalatest.funsuite.AnyFunSuiteLike$$anon$1.apply(AnyFunSuiteLike.scala:189)
[error]         at org.scalatest.TestSuite.withFixture(TestSuite.scala:196)
[error]         at org.scalatest.TestSuite.withFixture$(TestSuite.scala:195)
[error]         at org.scalatest.funsuite.AnyFunSuite.withFixture(AnyFunSuite.scala:1562)
[error]         at org.scalatest.funsuite.AnyFunSuiteLike.invokeWithFixture$1(AnyFunSuiteLike.scala:187)
[error]         at org.scalatest.funsuite.AnyFunSuiteLike.$anonfun$runTest$1(AnyFunSuiteLike.scala:199)
[error]         at org.scalatest.SuperEngine.runTestImpl(Engine.scala:306)
[error]         at org.scalatest.funsuite.AnyFunSuiteLike.runTest(AnyFunSuiteLike.scala:199)
[error]         at org.scalatest.funsuite.AnyFunSuiteLike.runTest$(AnyFunSuiteLike.scala:181)
[error]         at org.scalatest.funsuite.AnyFunSuite.runTest(AnyFunSuite.scala:1562)
[error]         at org.scalatest.funsuite.AnyFunSuiteLike.$anonfun$runTests$1(AnyFunSuiteLike.scala:232)
[error]         at org.scalatest.SuperEngine.$anonfun$runTestsInBranch$1(Engine.scala:413)
[error]         at scala.collection.immutable.List.foreach(List.scala:392)
[error]         at org.scalatest.SuperEngine.traverseSubNodes$1(Engine.scala:401)
[error]         at org.scalatest.SuperEngine.runTestsInBranch(Engine.scala:396)
[error]         at org.scalatest.SuperEngine.runTestsImpl(Engine.scala:475)
[error]         at org.scalatest.funsuite.AnyFunSuiteLike.runTests(AnyFunSuiteLike.scala:232)
[error]         at org.scalatest.funsuite.AnyFunSuiteLike.runTests$(AnyFunSuiteLike.scala:231)
[error]         at org.scalatest.funsuite.AnyFunSuite.runTests(AnyFunSuite.scala:1562)
[error]         at org.scalatest.Suite.run(Suite.scala:1112)
[error]         at org.scalatest.Suite.run$(Suite.scala:1094)
[error]         at org.scalatest.funsuite.AnyFunSuite.org$scalatest$funsuite$AnyFunSuiteLike$$super$run(AnyFunSuite.scala:1562)
[error]         at org.scalatest.funsuite.AnyFunSuiteLike.$anonfun$run$1(AnyFunSuiteLike.scala:236)
[error]         at org.scalatest.SuperEngine.runImpl(Engine.scala:535)
[error]         at org.scalatest.funsuite.AnyFunSuiteLike.run(AnyFunSuiteLike.scala:236)
[error]         at org.scalatest.funsuite.AnyFunSuiteLike.run$(AnyFunSuiteLike.scala:235)
[error]         at org.scalatest.funsuite.AnyFunSuite.run(AnyFunSuite.scala:1562)
[error]         at org.scalatest.tools.Framework.org$scalatest$tools$Framework$$runSuite(Framework.scala:318)
[error]         at org.scalatest.tools.Framework$ScalaTestTask.execute(Framework.scala:513)
[error]         at sbt.TestRunner.runTest$1(TestFramework.scala:139)
[error]         at sbt.TestRunner.run(TestFramework.scala:154)
[error]         at sbt.TestFramework$$anon$3$$anonfun$$lessinit$greater$1.$anonfun$apply$1(TestFramework.scala:317)
[error]         at sbt.TestFramework$.sbt$TestFramework$$withContextLoader(TestFramework.scala:277)
[error]         at sbt.TestFramework$$anon$3$$anonfun$$lessinit$greater$1.apply(TestFramework.scala:317)
[error]         at sbt.TestFramework$$anon$3$$anonfun$$lessinit$greater$1.apply(TestFramework.scala:317)
[error]         at sbt.TestFunction.apply(TestFramework.scala:329)
[error]         at sbt.Tests$.$anonfun$toTask$1(Tests.scala:311)
[error]         at sbt.std.Transform$$anon$3.$anonfun$apply$2(Transform.scala:46)
[error]         at sbt.std.Transform$$anon$4.work(Transform.scala:67)
[error]         at sbt.Execute.$anonfun$submit$2(Execute.scala:281)
[error]         at sbt.internal.util.ErrorHandling$.wideConvert(ErrorHandling.scala:19)
[error]         at sbt.Execute.work(Execute.scala:290)
[error]         at sbt.Execute.$anonfun$submit$1(Execute.scala:281)
[error]         at sbt.ConcurrentRestrictions$$anon$4.$anonfun$submitValid$1(ConcurrentRestrictions.scala:178)
[error]         at sbt.CompletionService$$anon$2.call(CompletionService.scala:37)
[error]         at java.util.concurrent.FutureTask.run(FutureTask.java:266)
[error]         at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
[error]         at java.util.concurrent.FutureTask.run(FutureTask.java:266)
[error]         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
[error]         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
[error]         at java.lang.Thread.run(Thread.java:748)

There is a binary incompatibility between the current version of Frameless (which sparksql-scalapb) is using, and Spark 3. I have filed this ticket upstream (typelevel/frameless#427). At this point we are blocked until the above issue is resolved.

It looks like both https://github.com/typelevel/frameless/issues/427 and https://github.com/typelevel/frameless/pull/433 have been resolved+merged now. Are there any other blockers?

The next step would be to try and update the dependencies and see if this project's test suite passes. Will you be able to look into this and report?

@thesamet Sure thing. I'll test against their 0.9.0 release. I'll look into it shortly.

So frameless 0.9.x isn't published anywhere, raised https://github.com/typelevel/frameless/issues/440 for that.
On a build of frameless-dataset off master, dropped into a fresh sparksql-scalapb w/ spark-sql @ 0.3.0, I'm seeing a series of errors: https://gist.github.com/paulfryzel/1462eb3b2fae5e3abdb80f4ef0b86f75. I'll see what I can step through later on.

@paulfryzel frameless 0.9 seems to be published now.
Did you manage to resolve the aforementioned errors?

@rsi2m Thanks for the heads up! I've updated my fork accordingly and reproduced the test output for review.
Currently, I'm at 20/36 tests passed but haven't had any real time to work on it since. While I may be able to free up some time soon, I'd certainly welcome an additional set of eyes, or I'd be happy to bring others up to speed with my findings.

Thanks so much for your help with this @paulfryzel !  I was planning to check out your work on this as well soon and see what's needed to take it to the finishing line.

I was able to fix the rest of the tests and we now have Spark 3 fully supported. :tada:
Big thanks to @paulfryzel for the initial commit. The rest was just working through some obscure change in Spark behavior (possibly a bug?) that has something to do about input null-checks next to StaticInvoke. Most code I found does these null checks around NewInstance calls, so rewriting how we constructs messages from PMessages did the trick: https://github.com/scalapb/sparksql-scalapb/commit/a468d34f8bef1e3413a8e70372ebcc4cd10865bd#diff-22a116f322ad6eb9e0dbb1a884aa906bR50-R62

I released 0.11.0-RC1 - please check it out and report any issues.

@thesamet Thanks a lot for bringing this all together! Very much appreciated.
Will bring into our development codebases this week and get some feedback.

@paulfryzel @thesamet Thank you guys! Awesome work!


Revisions to the Getting Started guide

Issue, if available:
Description of changes:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

I have read through these changes and approve.


Fanspeed doesn't work on zhimi.airpurifier.v6

All advertised features work on zhimi.airpurifier.v6 except Fan Speed. which gives this error in HomeBridge log:
[12/25/2021, 6:17:12 PM] [homebridge-xiaomi-mi-air-purifier] This plugin threw an error from the characteristic 'Rotation Speed': Unhandled error thrown inside write handler for characteristic: device.changeFanSpeed is not a function. See https://git.io/JtMGR for more info.
MiioDevice {
model=zhimi.airpurifier.v6,
types=miio:air-purifier, sensor, miio, air-purifier,
capabilities=fan-speed, miio:buzzer, miio:led-brightness, miio:switchable-led, pm2.5, relative-humidity, temperature, switchable-mode, mode, switchable-power, restorable-state, power, state
}

Using the fanspeed slider in Homekit gives above error in HomeBridge and Homekit says "No Response"

Expected behavior:
Simple fan slider
Logs:
Show the Homebridge logs here, remove any sensitive information.

[12/25/2021, 6:17:12 PM] [homebridge-xiaomi-mi-air-purifier] This plugin threw an error from the characteristic 'Rotation Speed': Unhandled error thrown inside write handler for characteristic: device.changeFanSpeed is not a function. See https://git.io/JtMGR for more info.
MiioDevice {
model=zhimi.airpurifier.v6,
types=miio:air-purifier, sensor, miio, air-purifier,
capabilities=fan-speed, miio:buzzer, miio:led-brightness, miio:switchable-led, pm2.5, relative-humidity, temperature, switchable-mode, mode, switchable-power, restorable-state, power, state
}
Show your Homebridge config.json here, remove any sensitive information.

Screenshots:

Environment:

Plugin Version: homebridge-xiaomi-mi-air-purifier v2.0.2
Homebridge Version: homebridge -v1.3.8
Node.js Version:
NPM Version:
Device:  zhimi.airpurifier.v6 (as stated in token extractor
Operating System: Docker

same issue with 2S

same for 1

After some trial and error, got it working with https://github.com/merdok/homebridge-miot.
All controls including fan speed, mode, led/buzzer control, humidity/temp sensors are working fine. I was finally able to get rid of xiaomi app.
Be aware, that your mi purifier may not be registered on a server in China, so it may get the wrong token from your login/password. Also, I've had to switch to config json, because miot config WebUI was unstable for me.
I've used https://github.com/PiotrMachowski/Xiaomi-cloud-tokens-extractor to get token for de server.
Here's my config:
{
    "platforms": [
        {
            "name": "Config",
            "port": 8581,
            "platform": "config"
        },
        {
            "devices": [
                {
                    "name": "Air Purifier 2",
                    "ip": "secret",
                    "token": "secret",
                    "deviceId": "secret",
                    "model": "zhimi.airpurifier.m1",
                    "pollingInterval": 7,
                    "deepDebugLog": false,
                    "micloud": {
                        "timeout": 10000,
                        "username": "secret",
                        "password": "secret",
                        "forceMiCloud": false,
                        "country": "de"
                    },
                    "buzzerControl": true,
                    "ledControl": true,
                    "showTemperature": true,
                    "screenControl": true,
                    "fanLevelControl": true,
                    "modeControl": true
                }
            ],
            "platform": "miot"
        }
    ]
}


Syslog?

If you're operating fakenet as a sinkhole, the ability to write to syslog, so it could be sent to a SIEM would be a great capability.

FakeNet-NG uses the Python logging module, so perhaps the SysLogHandler under logging.handlers could make short work of this? If it isn't a no-code solution, then it still seems like it should be pretty quick to integrate that.
https://docs.python.org/2/library/logging.handlers.html

Boerio,
See pull request https://github.com/fireeye/flare-fakenet-ng/pull/69. It should address your local and remote syslog needs.

Closed via #91 with -s argument in version 1.4.1.


upgrade lib to support ocp4.14

issue: https://issues.redhat.com/browse/ACM-6878

/lgtm

/cherry-pick backplane-2.3


feat: Merge branch 'master' into develop

Issue: FAIL tests/admin/product.js

FAIL tests/admin/product.js


Lighting issue when showing edges on a textured .gltf

Describe the bug
Lighting is wrong when showing edges of a textured .gltf
f3d -e file.gltf

No problem with a non-textured gltf:

Nor with a textured obj or fbx:

Regression between 2.0 and 2.1, should be bisected

Looks related to the PBR shader. Should not be too hard to fix. Do you want me to take a look before the final release?

That can wait 2.3 tbh, nobody found it in the last three months.

VTK fix: https://gitlab.kitware.com/vtk/vtk/-/merge_requests/10705


co19/LibTest/core/Symbol/Symbol_A06_t01 test fails on dartdevk

The test below works on all platforms, including dart2js, but fails on
import "../../../Utils/expect.dart";

class C {
  bool called = false;

  @override
  noSuchMethod(Invocation invocation) {
    called = true;
    Expect.equals(invocation.memberName, new Symbol("foo"));
    Expect.isFalse(identical(invocation.memberName, const Symbol("foo"))); // Fails here, isFalse argument is true
  }
}

main() {
  dynamic c = new C();
  c.foo();
  Expect.isTrue(c.called);
  c.called = false;

  c.foo;
  Expect.isTrue(c.called);
  c.called = false;
}

Tested on the edge version of DSK

I think we'd need to change the test in this case: We generally don't want to prevent optimizations where certain objects provided by the runtime are canonicalized, even in the case where we do not require this canonicalization.
An instance creation using new (explicitly or implicitly) that invokes a generative constructor must yield an object that isn't identical to any existing object, but objects provided by the runtime (that is "built-in objects" like reified types and function tearoffs) are not guaranteed to have been created by new, so it's OK to canonicalize them, even at run time, if that's helpful.
Consequently, we should test for identical(v1, v2) whenever that is specified, but we should not jump to the conclusion that we must have !identical(v1, v2) for all other cases. In particular, we shouldn't have Expect.isFalse(identical(...)).
The 'Symbols' section in the language specification is currently being updated (https://github.com/dart-lang/language/pull/1782) such that it includes equality and identity of symbols obtained from invocations of the Symbol(_) constructor.

Closing, I believe there is no need to change any tools, and the change to the test is handled in https://github.com/dart-lang/co19/issues/1128.


core/Normal: replace From with TryFrom and rename Normal::new and Normal::set

The implementations of Normal::new and (the From<f32> trait) clips the provided float to the normal range. While this ensures the Normal is valid, it prevents the user from handling out of range errors whithout checking the value first and then calling the clipping constructor or setter.
This commit adds the TryFrom<f32> implementation which fails if the provided value is out of range.
Previous behaviour is still applicable in most cases, but the clipping should be made explicite IMO. I removed the From<f32> implementation which would conflict with TryFrom<f32> anyway and renamed Normal::new as Normal::from_clipped.
For the same reasons, I also renamed Normal::set as Normal::set_clipped and added the faillible Normal::try_set.
Normal::set_clipped is now used wherever I found it to be useful in the code base.
In order to avoid the need to explicitely use std::convert::TryFrom, I lifted the crate's edition to "2021". Note that iced uses edition "2021" anyway and the minimum Rust supported version is at least 1.65.0 since iced uses GATs in at least one place.
Added unit tests for the renamed and added functions.
First commit is a pass on a few statics and functions that can be made const. Also fixes a constant.

Nice, thanks.


Suggestion to include "git add" for delete operations

It will be great to include something on the command "add" because in git it does not have the exact same meaning as the English word, it actually means adding an operation. Like if we remove a file locally, and want to remove it from the "staging area" and remote repo, we still do "git add file"

Added this to git.md