Draw pieces

Task consists of next steps:

Choose the pieces assets ( example ).
Extend startup routine. Load pieces as resource.
Extend system for board drawing. For positioning use structure PieceLocations.

The next samples can be helpful:

How to draw sprite from image.
How to draw sprite from part of image.

Useful links:

Bevy entities and components.
Bevy resources.

візму тікет

Taken

Done in: https://github.com/Wandalen/game_chess/pull/188


decode bytes using callback in oneof

I have a protobuf file with a value of type oneof:
        oneof value {
            ...
            bytes    bytes_value                    = 16;       // Bytes, File
            ...
            MetricValueExtension extension_value    = 19;
        }

I am decoding the MetricValueExtension using message level callbacks for oneofs. I am succeeding in doing so. However when I am trying to decode the bytes_value using a callback, I'm facing issues.
The documentation states: "When a field inside oneof contains pb_callback_t fields, the callback values cannot be set before decoding. This is because the different fields share the same storage space in C union. Instead either function name bound callbacks or a separate message level callback can be used. See tests/oneof_callback for an example on this."
For submessages, the callback cb_value is called but when decoding bytes it isn't.
How do I need to solve this?

Hmm, indeed the message level callback is currently only implemented for submessages. I'm not sure I want to extend that, it was a bit cumbersome workaround for the oneof+callback issue in the first place.
Name bound callbacks should work: set (nanopb_msgopt).callback_function = "mydecodecallback" and then implement a function with that name. It will get called for all callback fields inside the message, instead of the normal callback mechanism. It also has the benefit that you can have custom datatypes inside the structure instead of pb_callback_t. See e.g. https://github.com/nanopb/nanopb/blob/master/examples/network_server/client.c#L30 for example.
If that does not suit your usecase, another workaround could be to use generator option (nanopb).no_unions = true, which generates the fields separately and callbacks can be set directly.

Thanks for the reply.
I've solved it now by using FT_POINTER instead of FT_CALLBACK.


Certificate creation script doesn't support directories containing space

This command would lead to bad things.
  ./game_runner/scripts/secure_docker_start_registry.sh localhost

I think it's better if we add some configure script which creates the certificates and configures the scripts to use them (maybe embedding them in the scripts to allow easy transportation of scripts for example make-me-big.sh). This would remove the need to be in the same place as scripts when running them.


compliant and non-compliant code examples documentation

I just started with it. (work in progess)

@vanniktech I think we already had a conversation about this topic somewhere here. In my opinion it's not worth the effort since you need to resolve and annotate the test cases which should be included in the documentation. You also need to build a generator and so on and so forth.
I also think that this information is not likely to change.

I think this can be merged now.


cannot transmute between types of different sizes, or dependently-sized types

I am wrting a crate which I need to use in pallet.
Error details:
error[E0512]: cannot transmute between types of different sizes, or dependently-sized types
  --> /home/vivek/.cargo/git/checkouts/substrate-7e08433d4c370a21/d6c33e7/primitives/runtime-interface/src/impls.rs:44:1
   |
44 | assert_eq_size!(usize, u32);
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |
   = note: source type: `usize` (64 bits)
   = note: target type: `u32` (32 bits)
   = note: this error originates in the macro `assert_eq_size` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0512]: cannot transmute between types of different sizes, or dependently-sized types
  --> /home/vivek/.cargo/git/checkouts/substrate-7e08433d4c370a21/d6c33e7/primitives/runtime-interface/src/impls.rs:46:1
   |
46 | assert_eq_size!(*const u8, u32);
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |
   = note: source type: `*const u8` (64 bits)
   = note: target type: `u32` (32 bits)
   = note: this error originates in the macro `assert_eq_size` (in Nightly builds, run with -Z macro-backtrace for more info)

Content of Cargo.toml
[package]
name = "michelson"
version = "0.1.0"
edition = "2018"

[dependencies.sp-core]
default-features=false
git = 'https://github.com/paritytech/substrate.git'
rev = 'd6c33e7ec313f9bd5e319dc0a5a3ace5543f9617'
version = '3.0.0'

[dependencies.sp-std]
default-features=false
git = 'https://github.com/paritytech/substrate.git'
rev = 'd6c33e7ec313f9bd5e319dc0a5a3ace5543f9617'
version = '3.0.0'

[dependencies.sp-runtime]
default-features=false
git = 'https://github.com/paritytech/substrate.git'
rev = 'd6c33e7ec313f9bd5e319dc0a5a3ace5543f9617'
version = '3.0.0'

[dependencies]
num-bigint = { version = "0.4", default-features = false }
nom = { version = "6.1.2", default-features = false, features = ["alloc"] }
num-traits = { version = "0.2.14", default-features = false }
nom_locate = { version = "3.0.1", default-features = false }
getrandom = { version = "0.2.3", default-features = false, features = ["js"] }
chrono = { version = "0.4.19", default-features = false}

rand_core = { version = "0.6", default-features = false, features = ["getrandom"] }

# Cryptographic dependencies.
bs58 = { version = "0.4.0", default-feature=false, features = ["check", "alloc"] }
# https://github.com/RustCrypto/hashes .
sha2 = { version = "0.9", default-features = false }
sha3 = { version = "0.9", default-features = false }
keccak-hash = { version = "0.7", default-features = false }
blake2b_simd = { version="0.5.11", default-features = false }

ed25519-dalek = { version = "1.0.1", default-features = false, features = ["u64_backend", "rand", "alloc", "batch_deterministic"]}
ed25519 = { version = "1.1.1", default-features = false}
secp256k1 = { version = "0.20.2", default-features = false, features = ["serde", "rand", "recovery"], optional = true }
libsecp256k1 = { version = "0.5.0", default-features = false, features = ["static-context"],  optional = true }
bls12_381 = { version = "0.4.0",  features = ["groups", "pairings"] }

hex = { version = "0.4.3", default-features = false, features = ["alloc"] }

hacl-star = { path = "hacl-star", default-features = false }
hash-db = {version = "0.15.2", default-features = false }

[features]
default = ["libsecp256k1"]
std = [
  'sp-core/std',
  'sp-std/std',
  'sp-runtime/std',
]

Change to:
default = ["libsecp256k1", "std"]

It does not fix the issue.
And I can't reopen the issue.

Do you compile with --no-default-features?
The problem here is that you can not compile sp-io (from where this error is coming from) without std when you not compile it for wasm.


chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-k8s-29-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 4377

Questions ?
Please refer to the Backport tool documentation


add error messages to assert_eq()

[x] Tests added / passed
[x] Passes black dask / flake8 dask

Changes in this PR
This PR proposes adding more informative error messages in dask.array.utils.assert_eq().
How this improves dask
We make heavy use of assert_eq() in LightGBM's Dask tests. I've had the following experience a few times:

make changes
run pytest
tests fail. To figure out how they failed, scroll up to find the assert_eq() information dumped into the console, then try to understand the line in the code that's pointed to.

As of this PR, assert_eq() would raise an AssertionError with enough information to understand how the inputs a and b differ. For example:

AssertionError: a and b have different shapes (a: (100,), b: (100, 2))

Notes for Reviewers
I wasn't sure where it would be appropriate to add tests on these changes. tests/test_array_utils.py doesn't currently contain tests on assert_eq() directly. If you're open to the change proposed in this PR, please let me know if you'd like me to add some tests on the specific messages as well.
Thanks for your time and consideration.

FWIW there's an open issue for adding tests around out assert_eq testing utilities. Any additions on that front are certainly welcome, though no obligation

FWIW there's an open issue for adding tests around out assert_eq testing utilities. Any additions on that front are certainly welcome, though no obligation

Linking to the issue https://github.com/dask/dask/issues/2682

Linking to the issue https://github.com/dask/dask/issues/2682

thanks, I'll take a look!

thanks, I'll take a look!


Porting Chalk to default Jekyll project or not?

I am getting a lot of issues with people not understanding how Chalk works (deploying). I could do 2 things:

Ditch jekyll-assets and work with a default Jekyll installation. This would mean the following:

Have to get autoprefixer from somewhere else
No proper asset pipeline
No support for unsupported github pages jekyll plugins
Ability to host the Jekyll site on the master branch instead of the output files with the deploy script

So in short option 1 would make Chalk more dummy proof but would decrease it's technical performance.

Keep working the same way and potentially creating a lite version without jekyll-assets and eventually create a Jekyll Theme.

What does everyone think? Would love to get some feedback.

Deploying Chalk took me a few hours mostly because I couldn't understand the instructions on the README. My case was a little different and this is only the second time I've been working with Jekyll so I expected everything to work as all the default Jekyll installations. Perhaps option 2 with maybe an FAQ or something more expansive on the original so users who don't really understand anything can know what to do?

Static file hosting is extremely cheap or even free. Better docs are the way to go, imo.

Hi,
I struggled to deploy Chalk, and ended up having to rearrange how I was doing things in a way that's not mentioned in your README.
I have my repository name 'WendyBeth.github.io'. In order to deploy to your user page, you have to use the master branch. I struggled with this quite a bit, because running the deploy script forced the deploy to gh-pages. I could change my repo's name and then see my blog, but it a) didn't port in any assets, and b) kept linking to posts as if the namespace of my blog's repo did not exist. So if I clicked on a post title from 'WendyBeth.github.io/blog', it redirected me to 'WendyBeth.github.io/posts/post-title', which of course did not exist.
What I ended up having to do was create a different default branch - I called it develop - and then change the deploy script to write everything post-processing to master. See here.
I don't think you need to get rid of jekyll-assets - that's actually a really cool addition to this theme and is one of the reasons (other than the beautiful font choices) I chose it. Fleshing out the deploy section of the README to make it explicit what to do if 1) I want to host this blog as my user page (at username.github.io) or 2) I want to host this blog on it's own page (at username.github.io/blogname) so that the posts and all internal links are aware of the namespace, would help. If there's something I completely missed, adding that to the README would be ideal.
All that said, I love this theme and couldn't be happier with it. 💯

You could use Gulp to achieve something similar to the Jekyll-Assets plugin, @nielsenramon.

Folks, I have been working on something alike (haven't published it yet), to be foolproof but make it easier to start with comes at an expense of flexibility (as @nielsenramin mentioned).
It could be an option to maintain two flavors - starter (get started in no time) and expert (can be bent to your will but you need to be familiar with its internals).
Humans aren't good at maintaining in the long run but automation actually excels at that, so automating it could be a way to go.

UPD: Looks like I have published that work already. Here: https://rubygems.org/gems/jekyll-theme-chalk

Decided not to port this theme to a default Jekyll project. Jekyll-assets comes with too many benefits right now. People are using Chalk because of all the custom stuff we've added anyway!

Could you create a port to a default Pages theme, without the jekyll-assets? I like how clean it looks, and there is plenty of customization without the assets, don't you think?


chore(derive): Error Exports

📚 $\text{Stack Overview}$
Pulls submitted in this stack:

#758 👈
#757
main

This comment was automatically generated by st.


updated stuff

:+1: :zap:

Not really needed to change one line which already exists. Also beaks the ordering of variables which is sorted by name ;)

Any ordering of keys in JSON objects is not meaningful. Regardless, it does happen to reflect how the API currently encodes things and fixes oredering, so may as well merge it...


Added Like Effect Button

Fixes Issue🛠

Closes #
Description👨💻
Added Like effect Button
closes #1104
Type of Change📄

[ ] Bug fix (non-breaking change which fixes a bug)
[x] New feature (non-breaking change which adds functionality)
[ ] Style (non-breaking change which improves website style or formatting)
[ ] Documentation (non-breaking change which updates or adds documentation)
[ ] Responsiveness (non-breaking change which improves UI/UX on different screen sizes)

Checklist✅

[x] I am an Open Source contributor
[x] I have performed a self-review of my code
[x] My code follows the style guidelines of this project
[x] I have commented on my code, particularly in hard-to-understand areas

Screenshots/GIF📷

@Rakesh9100  please review it soon

@Rakesh9100 Please Review it soon


Update azure.core to have reference type on ResponseError

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check for Azure.Core
API changes are not detected in this pull request for Azure.Core


Need to have a way to show newly added requested claims to consent page

Need to consider the $subject because if the identity admin add new requested claims currently there is no way to show the consents for the new requested claims to the user.

Currently, without this improvement, we could achieve the use case using [1]
[1] https://github.com/wso2/product-is/issues/2985#issuecomment-374506227

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


[WIP] People Picker

Hey @timbl - just making my efforts public here. Right now the picker can render a list of people dragged in via WebId URIs. I'm currently working on using the kb to keep track of the dynamic vcard group as we discussed last week.

Heads up that this change includes two refactors (which are currently causing conflicts which I can resolve):

Introduce babel
Begin to split apart the widgets module


How to register adapters with jest-circus

Hey; we've been using setup-polly-jest for awhile and it's working great, so thanks for the project!
We're trying to upgrade to jest 27 / jest-circus, and for some reason our adapters are no longer being registered, i.e. we have code like:
Polly.register(require("@pollyjs/adapter-node-http"));
Polly.register(require("@pollyjs/persister-fs"));

But our tests are now failing with:
    PollyError: [Polly] Adapter matching the name `node-http` was not registered.

I've put the new jest env at the top of our test files:
/** @jest-environment setup-polly-jest/jest-environment-node */
...
import "src/setupPolly";
...
describe("...", () => {

Where the src/setupPolly file is what has our common Polly.register code in it.
By adding some console.logs inside of polly itself, it looks like there are two versions of Polly's internal event emitter floating around, i.e. from a test run:
CREATED EventEmitter {
  madeAt:<PHONE_NUMBER>545,
  [Symbol()]: Map { _c: Map(0) {} },
  [Symbol()]: Set { _c: Set(3) { 'register', 'create', 'stop' } }
}
  console.log
    CREATED EventEmitter {
      madeAt:<PHONE_NUMBER>580,
      [Symbol()]: Map { _c: Map(0) {} },
      [Symbol()]: Set { _c: Set(3) { 'register', 'create', 'stop' } }
    }

      at Object.<anonymous> (node_modules/@pollyjs/core/dist/cjs/pollyjs-core.js:6195:9)

  console.log
    REGISTERING adapters

      at Object.<anonymous> (src/setupPolly.ts:10:9)

  console.log
    REGISTERING ON1 EventEmitter {
      madeAt:<PHONE_NUMBER>580,
      [Symbol()]: Map { _c: Map(0) {} },
      [Symbol()]: Set { _c: Set(3) { 'register', 'create', 'stop' } }
    }

      at Function.on (node_modules/@pollyjs/core/src/polly.js:113:12)

  console.log
    REGISTERING ON1 EventEmitter {
      madeAt:<PHONE_NUMBER>580,
      [Symbol()]: Map { _c: Map(1) { 'register' => [Set] } },
      [Symbol()]: Set { _c: Set(3) { 'register', 'create', 'stop' } }
    }

      at Function.on (node_modules/@pollyjs/core/src/polly.js:113:12)

EMITTING ON1 EventEmitter {
  madeAt:<PHONE_NUMBER>545,
  [Symbol()]: Map { _c: Map(0) {} },
  [Symbol()]: Set { _c: Set(3) { 'register', 'create', 'stop' } }
}
INSIDE emitSync
INSIDE emitSync

  ● Test suite failed to run

    PollyError: [Polly] Adapter matching the name `node-http` was not registered.

      at Object.assert (node_modules/@pollyjs/utils/src/utils/assert.js:5:11)
      at Polly.connectTo (node_modules/@pollyjs/core/dist/cjs/pollyjs-core.js:6433:11)
      at node_modules/@pollyjs/core/src/polly.js:170:20
          at Array.forEach (<anonymous>)
      at Polly.configure (node_modules/@pollyjs/core/src/polly.js:170:20)
      at new Polly (node_modules/@pollyjs/core/dist/cjs/pollyjs-core.js:6221:10)
      at PollyEnvironmentNode.handleTestEvent (node_modules/setup-polly-jest/lib/jest-environment-polly.js:85:48)

What seems to be happening is:

The<PHONE_NUMBER>545 event emitter is created immediately when the test starts (I assume from the jest-environment-node)
However a second<PHONE_NUMBER>580 event emitter is also created (I assume this is due to Jest's sandboxing, like b/c our src/setupPolly.ts is imported from within our test, it is getting it's own separate require/vm context)
Our Polly.register(node-adapter) call is putting the adapter into the 2nd /<PHONE_NUMBER>580 emitter

You can see the 2nd event emitter's map is empty, but then starts to get populated i.e.  'register' => [Set]

But when handleTestEvent runs and tries to create a polly instance for the test, the Polly.configure is using the first event emitter,<PHONE_NUMBER>545 to look for adapters, and not finding any

So, that is what happening. I really don't know why though. :-)
Is there a different way to Polly.register in the new jest-circus setup?
I've looked through the readme and the commit that added jest-circus support and didn't see anything obvious, but maybe I'm missing something.
Thanks!

Hey @stephenh, thanks for reporting the issue! I can confirm that it exists and I think that you probably have the right idea about the root cause. I don't have time to immediately look into it, but will try to see if anything can be done to make global Polly.register calls work with the new jest runtime, I never used this way of registering adapters with polly, so when adding circus support I kinda missed that it's not working anymore. In the meantime as a workaround you can use the approach of directly passing adapters in the config as it is done in this tests in this repo:
https://github.com/gribnoysup/setup-polly-jest/blob/13db62ea1503b4ff61215f5a3c4d1bbd8de0d03d/test/integration/jest/index.test.js#L18-L26

Ah great! We can definitely do that, and I confirmed that works for us as well.
Thanks for the quick reply!


nvim-treesitter breaking changes on highlight

See related discussions:

https://www.reddit.com/r/neovim/comments/19aratu/psa_nvimtreesitter_breaking_changes_on_highlight/
https://github.com/nvim-treesitter/nvim-treesitter/issues/2293

Already been done 3 days ago


update repositories to https and use melpa.org

I was having weird issues without this, not sure they are reproducible. In any case, this is a no-brainer and I would like to get it merged as quickly as possible.

We should be using HTTPS only by default anyways, and if the url has changed then we should use it.


Add automation to add form.js to a tag

Add automation to build the form.js to a tag when a tag is created.

Completed in #153


pio build fails with 0.10.0

Guys, I'm trying to use recommender with PIO 0.10.0 and get following error
[INFO] [Console$] sbt.ResolveException: unresolved dependency: io.prediction#core_2.10;0.9.7-aml: not found

on pio build --verbose
Is there 0.9.7 hardcoded somewhere ? I can't' find it.
Here is how I install PIO: https://github.com/unoexperto/docker-predictionio/blob/master/0.10.0/Dockerfile
Here is fill log:
[info] Loading project definition from /opt/ArticleRecommender/project
[info] Set current project to template-scala-parallel-universal-recommendation (in build file:/opt/ArticleRecommender/)
[info] Updating {file:/opt/ArticleRecommender/}articlerecommender...
[info] Resolving org.scala-lang#scala-library;2.10.4 ...
M[info] Resolving org.xerial.snappy#snappy-java;<IP_ADDRESS> ...
M[info] Resolving org.apache.mahout#mahout-math-scala_2.10;0.13.0-SNAPSHOT ...
M[info] Resolving org.apache.mahout#mahout-math-scala_2.10;0.13.0-SNAPSHOT ...
M[info] Resolving org.apache.mahout#mahout-math;0.13.0-SNAPSHOT ...
M[info] Resolving org.apache.mahout#mahout-math;0.13.0-SNAPSHOT ...
M[info] Resolving org.apache.commons#commons-math3;3.2 ...
M[info] Resolving com.google.guava#guava;14.0.1 ...
M[info] Resolving it.unimi.dsi#fastutil;7.0.12 ...
M[info] Resolving org.slf4j#slf4j-api;1.7.21 ...
M[info] Resolving com.tdunning#t-digest;3.1 ...
M[info] Resolving com.esotericsoftware.kryo#kryo;2.24.0 ...
M[info] Resolving com.esotericsoftware.minlog#minlog;1.2 ...
M[info] Resolving org.objenesis#objenesis;2.1 ...
M[info] Resolving log4j#log4j;1.2.17 ...
M[info] Resolving com.github.scopt#scopt_2.10;3.3.0 ...
M[info] Resolving org.apache.mahout#mahout-spark_2.10;0.13.0-SNAPSHOT ...
M[info] Resolving org.apache.mahout#mahout-spark_2.10;0.13.0-SNAPSHOT ...
M[info] Resolving org.apache.mahout#mahout-hdfs;0.13.0-SNAPSHOT ...
M[info] Resolving org.apache.mahout#mahout-hdfs;0.13.0-SNAPSHOT ...
M[info] Resolving com.fasterxml.jackson.core#jackson-core;2.7.4 ...
M[info] Resolving org.apache.commons#commons-lang3;3.1 ...
M[info] Resolving commons-cli#commons-cli;1.2 ...
M[info] Resolving org.apache.mahout.commons#commons-cli;2.0-mahout ...
M[info] Resolving org.apache.solr#solr-commons-csv;3.5.0 ...
M[info] Resolving com.thoughtworks.xstream#xstream;1.4.4 ...
M[info] Resolving xpp3#xpp3_min;1.1.4c ...
M[info] Resolving org.elasticsearch#elasticsearch-spark_2.10;2.1.2 ...
M[info] Resolving org.json4s#json4s-native_2.10;3.2.10 ...
M[info] Resolving org.json4s#json4s-core_2.10;3.2.10 ...
M[info] Resolving org.json4s#json4s-ast_2.10;3.2.10 ...
M[info] Resolving com.thoughtworks.paranamer#paranamer;2.6 ...
M[info] Resolving org.scala-lang#scalap;2.10.0 ...
M[info] Resolving org.scala-lang#scala-compiler;2.10.0 ...
M[info] Resolving org.scala-lang#scala-reflect;2.10.0 ...
M[info] Resolving io.prediction#core_2.10;0.9.7-aml ...
M[info] Resolving io.prediction#core_2.10;0.9.7-aml ...
[warn] 	module not found: io.prediction#core_2.10;0.9.7-aml
[warn] ==== local: tried
[warn]   /root/.ivy2/local/io.prediction/core_2.10/0.9.7-aml/ivys/ivy.xml
[warn] ==== public: tried
[warn]   https://repo1.maven.org/maven2/io/prediction/core_2.10/0.9.7-aml/core_2.10-0.9.7-aml.pom
[warn] ==== Maven2 Local: tried
[warn]   file:/root/.m2/repository/io/prediction/core_2.10/0.9.7-aml/core_2.10-0.9.7-aml.pom
[info] Resolving org.apache.spark#spark-core_2.10;1.4.0 ...
M[info] Resolving com.twitter#chill_2.10;0.5.0 ...
M[info] Resolving com.twitter#chill-java;0.5.0 ...
M[info] Resolving com.esotericsoftware.kryo#kryo;2.21 ...
M[info] Resolving com.esotericsoftware.reflectasm#reflectasm;1.07 ...
M[info] Resolving org.objenesis#objenesis;1.2 ...
M[info] Resolving org.apache.hadoop#hadoop-client;2.2.0 ...
M[info] Resolving org.apache.hadoop#hadoop-common;2.2.0 ...
M[info] Resolving org.apache.hadoop#hadoop-annotations;2.2.0 ...
M[info] Resolving com.google.guava#guava;11.0.2 ...
M[info] Resolving com.google.code.findbugs#jsr305;1.3.9 ...
M[info] Resolving org.apache.commons#commons-math;2.1 ...
M[info] Resolving xmlenc#xmlenc;0.52 ...
M[info] Resolving commons-httpclient#commons-httpclient;3.1 ...
M[info] Resolving commons-codec#commons-codec;1.4 ...
M[info] Resolving commons-io#commons-io;2.1 ...
M[info] Resolving commons-logging#commons-logging;1.1.1 ...
M[info] Resolving commons-lang#commons-lang;2.5 ...
M[info] Resolving commons-configuration#commons-configuration;1.6 ...
M[info] Resolving commons-collections#commons-collections;3.2.1 ...
M[info] Resolving commons-digester#commons-digester;1.8 ...
M[info] Resolving commons-beanutils#commons-beanutils;1.7.0 ...
M[info] Resolving commons-beanutils#commons-beanutils-core;1.8.0 ...
M[info] Resolving org.codehaus.jackson#jackson-core-asl;1.8.8 ...
M[info] Resolving org.apache.avro#avro;1.7.4 ...
M[info] Resolving com.thoughtworks.paranamer#paranamer;2.3 ...
M[info] Resolving org.xerial.snappy#snappy-java;<IP_ADDRESS> ...
M[info] Resolving org.apache.commons#commons-compress;1.4.1 ...
M[info] Resolving org.tukaani#xz;1.0 ...
M[info] Resolving com.google.protobuf#protobuf-java;2.5.0 ...
M[info] Resolving org.apache.hadoop#hadoop-auth;2.2.0 ...
M[info] Resolving org.apache.hadoop#hadoop-hdfs;2.2.0 ...
M[info] Resolving org.mortbay.jetty#jetty-util;6.1.26 ...
M[info] Resolving org.apache.hadoop#hadoop-mapreduce-client-app;2.2.0 ...
M[info] Resolving org.apache.hadoop#hadoop-mapreduce-client-app;2.2.0 ...
M[info] Resolving org.apache.hadoop#hadoop-mapreduce-client;2.2.0 ...
M[info] Resolving org.apache.hadoop#hadoop-mapreduce-client-common;2.2.0 ...
M[info] Resolving org.apache.hadoop#hadoop-mapreduce-client-common;2.2.0 ...
M[info] Resolving org.apache.hadoop#hadoop-mapreduce-client;2.2.0 ...
M[info] Resolving org.apache.hadoop#hadoop-yarn-common;2.2.0 ...
M[info] Resolving org.apache.hadoop#hadoop-yarn-common;2.2.0 ...
M[info] Resolving org.apache.hadoop#hadoop-yarn;2.2.0 ...
M[info] Resolving org.apache.hadoop#hadoop-yarn-api;2.2.0 ...
M[info] Resolving org.apache.hadoop#hadoop-yarn-api;2.2.0 ...
M[info] Resolving org.apache.hadoop#hadoop-yarn;2.2.0 ...
M[info] Resolving org.slf4j#slf4j-log4j12;1.7.5 ...
M[info] Resolving com.google.inject#guice;3.0 ...
M[info] Resolving javax.inject#javax.inject;1 ...
M[info] Resolving aopalliance#aopalliance;1.0 ...
M[info] Resolving org.sonatype.sisu.inject#cglib;2.2.1-v20090111 ...
M[info] Resolving asm#asm;3.2 ...
M[info] Resolving com.sun.jersey.jersey-test-framework#jersey-test-framework-grizzly2;1.9 ...
M[info] Resolving com.sun.jersey#jersey-server;1.9 ...
M[info] Resolving com.sun.jersey#jersey-json;1.9 ...
M[info] Resolving org.codehaus.jettison#jettison;1.1 ...
M[info] Resolving stax#stax-api;1.0.1 ...
M[info] Resolving com.sun.xml.bind#jaxb-impl;2.2.3-1 ...
M[info] Resolving javax.xml.bind#jaxb-api;2.2.2 ...
M[info] Resolving javax.activation#activation;1.1 ...
M[info] Resolving org.codehaus.jackson#jackson-jaxrs;1.8.8 ...
M[info] Resolving org.codehaus.jackson#jackson-xc;1.8.8 ...
M[info] Resolving com.sun.jersey.contribs#jersey-guice;1.9 ...
M[info] Resolving org.apache.hadoop#hadoop-yarn-client;2.2.0 ...
M[info] Resolving org.apache.hadoop#hadoop-yarn-client;2.2.0 ...
M[info] Resolving org.apache.hadoop#hadoop-yarn;2.2.0 ...
M[info] Resolving org.apache.hadoop#hadoop-mapreduce-client-core;2.2.0 ...
M[info] Resolving org.apache.hadoop#hadoop-mapreduce-client-core;2.2.0 ...
M[info] Resolving org.apache.hadoop#hadoop-mapreduce-client;2.2.0 ...
M[info] Resolving org.apache.hadoop#hadoop-yarn-server-common;2.2.0 ...
M[info] Resolving org.apache.hadoop#hadoop-yarn-server-common;2.2.0 ...
M[info] Resolving org.apache.hadoop#hadoop-yarn-server;2.2.0 ...
M[info] Resolving org.apache.hadoop#hadoop-yarn-server;2.2.0 ...
M[info] Resolving org.apache.hadoop#hadoop-yarn;2.2.0 ...
M[info] Resolving org.apache.hadoop#hadoop-mapreduce-client-shuffle;2.2.0 ...
M[info] Resolving org.apache.hadoop#hadoop-mapreduce-client-shuffle;2.2.0 ...
M[info] Resolving org.apache.hadoop#hadoop-mapreduce-client;2.2.0 ...
M[info] Resolving org.apache.hadoop#hadoop-mapreduce-client-jobclient;2.2.0 ...
M[info] Resolving org.apache.hadoop#hadoop-mapreduce-client-jobclient;2.2.0 ...
M[info] Resolving org.apache.hadoop#hadoop-mapreduce-client;2.2.0 ...
M[info] Resolving org.apache.hadoop#hadoop-yarn-server-nodemanager;2.2.0 ...
M[info] Resolving org.apache.hadoop#hadoop-yarn-server-nodemanager;2.2.0 ...
M[info] Resolving org.apache.hadoop#hadoop-yarn-server;2.2.0 ...
M[info] Resolving org.apache.spark#spark-launcher_2.10;1.4.0 ...
M[info] Resolving org.spark-project.spark#unused;1.0.0 ...
M[info] Resolving org.apache.spark#spark-network-common_2.10;1.4.0 ...
M[info] Resolving io.netty#netty-all;4.0.23.Final ...
M[info] Resolving org.apache.spark#spark-network-shuffle_2.10;1.4.0 ...
M[info] Resolving org.apache.spark#spark-unsafe_2.10;1.4.0 ...
M[info] Resolving net.java.dev.jets3t#jets3t;0.7.1 ...
M[info] Resolving org.apache.curator#curator-recipes;2.4.0 ...
M[info] Resolving org.apache.curator#curator-framework;2.4.0 ...
M[info] Resolving org.apache.curator#curator-client;2.4.0 ...
M[info] Resolving org.slf4j#slf4j-api;1.6.4 ...
M[info] Resolving org.apache.zookeeper#zookeeper;3.4.5 ...
M[info] Resolving jline#jline;0.9.94 ...
M[info] Resolving org.eclipse.jetty.orbit#javax.servlet;3.0.0.v201112011016 ...
M[info] Resolving org.apache.commons#commons-lang3;3.3.2 ...
M[info] Resolving org.apache.commons#commons-math3;3.4.1 ...
M[info] Resolving org.slf4j#jul-to-slf4j;1.7.10 ...
M[info] Resolving org.slf4j#jcl-over-slf4j;1.7.10 ...
M[info] Resolving org.slf4j#slf4j-log4j12;1.7.10 ...
M[info] Resolving com.ning#compress-lzf;1.0.3 ...
M[info] Resolving net.jpountz.lz4#lz4;1.2.0 ...
M[info] Resolving org.roaringbitmap#RoaringBitmap;0.4.5 ...
M[info] Resolving commons-net#commons-net;2.2 ...
M[info] Resolving org.spark-project.akka#akka-remote_2.10;2.3.4-spark ...
M[info] Resolving org.spark-project.akka#akka-actor_2.10;2.3.4-spark ...
M[info] Resolving com.typesafe#config;1.2.1 ...
M[info] Resolving io.netty#netty;3.8.0.Final ...
M[info] Resolving org.spark-project.protobuf#protobuf-java;2.5.0-spark ...
M[info] Resolving org.uncommons.maths#uncommons-maths;1.2.2a ...
M[info] Resolving org.spark-project.akka#akka-slf4j_2.10;2.3.4-spark ...
M[info] Resolving org.json4s#json4s-jackson_2.10;3.2.10 ...
M[info] Resolving com.sun.jersey#jersey-core;1.9 ...
M[info] Resolving org.apache.mesos#mesos;0.21.1 ...
M[info] Resolving com.clearspring.analytics#stream;2.7.0 ...
M[info] Resolving io.dropwizard.metrics#metrics-core;3.1.0 ...
M[info] Resolving io.dropwizard.metrics#metrics-jvm;3.1.0 ...
M[info] Resolving io.dropwizard.metrics#metrics-json;3.1.0 ...
M[info] Resolving io.dropwizard.metrics#metrics-graphite;3.1.0 ...
M[info] Resolving com.fasterxml.jackson.core#jackson-databind;2.4.4 ...
M[info] Resolving com.fasterxml.jackson.core#jackson-annotations;2.4.0 ...
M[info] Resolving com.fasterxml.jackson.core#jackson-core;2.4.4 ...
M[info] Resolving com.fasterxml.jackson.module#jackson-module-scala_2.10;2.4.4 ...
M[info] Resolving org.scala-lang#scala-reflect;2.10.4 ...
M[info] Resolving com.fasterxml.jackson.core#jackson-annotations;2.4.4 ...
M[info] Resolving org.apache.ivy#ivy;2.4.0 ...
M[info] Resolving oro#oro;2.0.8 ...
M[info] Resolving org.tachyonproject#tachyon-client;0.6.4 ...
M[info] Resolving org.tachyonproject#tachyon;0.6.4 ...
M[info] Resolving commons-codec#commons-codec;1.5 ...
M[info] Resolving commons-io#commons-io;2.4 ...
M[info] Resolving net.razorvine#pyrolite;4.4 ...
M[info] Resolving net.sf.py4j#py4j;<IP_ADDRESS> ...
M[info] Resolving org.apache.spark#spark-mllib_2.10;1.4.0 ...
M[info] Resolving org.apache.spark#spark-streaming_2.10;1.4.0 ...
M[info] Resolving org.apache.spark#spark-sql_2.10;1.4.0 ...
M[info] Resolving org.apache.spark#spark-catalyst_2.10;1.4.0 ...
M[info] Resolving org.scala-lang#scala-compiler;2.10.4 ...
M[info] Resolving org.scalamacros#quasiquotes_2.10;2.0.1 ...
M[info] Resolving com.twitter#parquet-column;1.6.0rc3 ...
M[info] Resolving com.twitter#parquet-common;1.6.0rc3 ...
M[info] Resolving com.twitter#parquet-encoding;1.6.0rc3 ...
M[info] Resolving com.twitter#parquet-generator;1.6.0rc3 ...
M[info] Resolving com.twitter#parquet-hadoop;1.6.0rc3 ...
M[info] Resolving com.twitter#parquet-format;2.2.0-rc1 ...
M[info] Resolving com.twitter#parquet-jackson;1.6.0rc3 ...
M[info] Resolving org.codehaus.jackson#jackson-mapper-asl;1.9.11 ...
M[info] Resolving org.codehaus.jackson#jackson-core-asl;1.9.11 ...
M[info] Resolving org.jodd#jodd-core;3.6.3 ...
M[info] Resolving org.apache.spark#spark-graphx_2.10;1.4.0 ...
M[info] Resolving com.github.fommil.netlib#core;1.1.2 ...
M[info] Resolving net.sourceforge.f2j#arpack_combined_all;0.1 ...
M[info] Resolving org.scalanlp#breeze_2.10;0.11.2 ...
M[info] Resolving org.scalanlp#breeze-macros_2.10;0.11.2 ...
M[info] Resolving net.sf.opencsv#opencsv;2.3 ...
M[info] Resolving com.github.rwl#jtransforms;2.4.0 ...
M[info] Resolving org.spire-math#spire_2.10;0.7.4 ...
M[info] Resolving org.spire-math#spire-macros_2.10;0.7.4 ...
M[info] Resolving org.jpmml#pmml-model;1.1.15 ...
M[info] Resolving org.jpmml#pmml-agent;1.1.15 ...
M[info] Resolving org.jpmml#pmml-schema;1.1.15 ...
M[info] Resolving com.sun.xml.bind#jaxb-impl;2.2.7 ...
M[info] Resolving com.sun.xml.bind#jaxb-core;2.2.7 ...
M[info] Resolving javax.xml.bind#jaxb-api;2.2.7 ...
M[info] Resolving com.sun.istack#istack-commons-runtime;2.16 ...
M[info] Resolving com.sun.xml.fastinfoset#FastInfoset;1.2.12 ...
M[info] Resolving javax.xml.bind#jsr173_api;1.0 ...
M[info] Resolving commons-net#commons-net;3.1 ...
M[info] Resolving org.scala-lang#jline;2.10.4 ...
M[info] Resolving org.fusesource.jansi#jansi;1.4 ...
[warn] 	::::::::::::::::::::::::::::::::::::::::::::::
[warn] 	::          UNRESOLVED DEPENDENCIES         ::
[warn] 	::::::::::::::::::::::::::::::::::::::::::::::
[warn] 	:: io.prediction#core_2.10;0.9.7-aml: not found
[warn] 	::::::::::::::::::::::::::::::::::::::::::::::
[info] Done updating.
[info] io.prediction:template-scala-parallel-universal-recommendation_2.10:0.4.2 [S]
[info]   +-com.thoughtworks.xstream:xstream:1.4.4
[info]   | +-xpp3:xpp3_min:1.1.4c
[info]   |
[info]   +-org.apache.mahout:mahout-hdfs:0.13.0-SNAPSHOT
[info]   | +-com.fasterxml.jackson.core:jackson-core:2.7.4
[info]   | +-com.google.guava:guava:14.0.1
[info]   | +-commons-cli:commons-cli:1.2
[info]   | +-org.apache.commons:commons-lang3:3.1
[info]   | +-org.apache.commons:commons-math3:3.2
[info]   | +-org.apache.mahout.commons:commons-cli:2.0-mahout
[info]   | +-org.apache.mahout:mahout-math:0.13.0-SNAPSHOT
[info]   | | +-com.google.guava:guava:14.0.1
[info]   | | +-com.tdunning:t-digest:3.1
[info]   | | +-it.unimi.dsi:fastutil:7.0.12
[info]   | | +-org.apache.commons:commons-math3:3.2
[info]   | | +-org.slf4j:slf4j-api:1.7.21
[info]   | |
[info]   | +-org.apache.solr:solr-commons-csv:3.5.0
[info]   | | +-org.slf4j:slf4j-api:1.6.1 (evicted by: 1.7.21)
[info]   | | +-org.slf4j:slf4j-api:1.7.21
[info]   | |
[info]   | +-org.slf4j:slf4j-api:1.7.21
[info]   |
[info]   +-org.apache.mahout:mahout-math-scala_2.10:0.13.0-SNAPSHOT
[info]   | +-com.esotericsoftware.kryo:kryo:2.24.0
[info]   | | +-com.esotericsoftware.minlog:minlog:1.2
[info]   | | +-org.objenesis:objenesis:2.1
[info]   | |
[info]   | +-com.github.scopt:scopt_2.10:3.3.0 [S]
[info]   | +-log4j:log4j:1.2.17
[info]   | +-org.apache.mahout:mahout-math:0.13.0-SNAPSHOT
[info]   |   +-com.google.guava:guava:14.0.1
[info]   |   +-com.tdunning:t-digest:3.1
[info]   |   +-it.unimi.dsi:fastutil:7.0.12
[info]   |   +-org.apache.commons:commons-math3:3.2
[info]   |   +-org.slf4j:slf4j-api:1.7.21
[info]   |
[info]   +-org.apache.mahout:mahout-math:0.13.0-SNAPSHOT
[info]   | +-com.google.guava:guava:14.0.1
[info]   | +-com.tdunning:t-digest:3.1
[info]   | +-it.unimi.dsi:fastutil:7.0.12
[info]   | +-org.apache.commons:commons-math3:3.2
[info]   | +-org.slf4j:slf4j-api:1.7.21
[info]   |
[info]   +-org.apache.mahout:mahout-spark_2.10:0.13.0-SNAPSHOT
[info]   | +-org.apache.mahout:mahout-math-scala_2.10:0.13.0-SNAPSHOT
[info]   |   +-com.esotericsoftware.kryo:kryo:2.24.0
[info]   |   | +-com.esotericsoftware.minlog:minlog:1.2
[info]   |   | +-org.objenesis:objenesis:2.1
[info]   |   |
[info]   |   +-com.github.scopt:scopt_2.10:3.3.0 [S]
[info]   |   +-log4j:log4j:1.2.17
[info]   |   +-org.apache.mahout:mahout-math:0.13.0-SNAPSHOT
[info]   |     +-com.google.guava:guava:14.0.1
[info]   |     +-com.tdunning:t-digest:3.1
[info]   |     +-it.unimi.dsi:fastutil:7.0.12
[info]   |     +-org.apache.commons:commons-math3:3.2
[info]   |     +-org.slf4j:slf4j-api:1.7.21
[info]   |
[info]   +-org.elasticsearch:elasticsearch-spark_2.10:2.1.2 [S]
[info]   +-org.json4s:json4s-native_2.10:3.2.10 [S]
[info]   | +-org.json4s:json4s-core_2.10:3.2.10 [S]
[info]   |   +-com.thoughtworks.paranamer:paranamer:2.6
[info]   |   +-org.json4s:json4s-ast_2.10:3.2.10 [S]
[info]   |   +-org.scala-lang:scalap:2.10.0
[info]   |     +-org.scala-lang:scala-compiler:2.10.0 [S]
[info]   |       +-org.scala-lang:scala-reflect:2.10.0 [S]
[info]   |
[info]   +-org.xerial.snappy:snappy-java:<IP_ADDRESS>
[info]
[info] Note: The graph was estimated to be too big to display (> 15 nodes). Use `sbt 'dependency-graph --force'` (with the single quotes) to force graph display.
[success] Total time: 6 s, completed Nov 10, 2016 6:46:46 PM

Where did you get the recommender from?

@tom-chan From your (I assume) git.

Can I have the URL for that? Things might be a little messy during transition so just want to make sure.

Sure. I'm getting it from https://github.com/actionml/template-scala-parallel-universal-recommendation.git and using tag v0.4.2.
 You have to install 0.9.7-aml using instructions here: http://actionml.com/docs/install
The Universal Recommender is an ActionML template and supported on this Google group: https://groups.google.com/forum/#!forum/actionml-user
The template is being moved to Apache-PIO as we speak and will be released as v0.5.0 from the same repo you got 0.4.2. Expect an update next week of after Thanksgiving.

I'm using PredcitionIO-0.9.7-aml but when i try to build i've got this error message:
[Console$] [error] (*:update) sbt.ResolveException: unresolved dependency: org.apache.mahout#mahout-math-scala_2.10;0.13.0-SNAPSHOT: not found
[ERROR] [Console$] [error] unresolved dependency: org.apache.mahout#mahout-spark_2.10;0.13.0-SNAPSHOT: not found
[ERROR] [Console$] [error] unresolved dependency: org.apache.mahout#mahout-math;0.13.0-SNAPSHOT: not found
[ERROR] [Console$] [error] unresolved dependency: org.apache.mahout#mahout-hdfs;0.13.0-SNAPSHOT: not found
[ERROR] [Console$] [error] unresolved dependency: io.prediction#core_2.10;0.9.7-aml: not found
[ERROR] [Console$] [error] Total time: 64 s, completed Dec 8, 2016 12:42:52 PM
[ERROR] [Console$] Return code of previous step is 1. Aborting.

What should i do? PLease help me! Thank you!

Folks, since the Universal Recommender is not able to work with the apache version of pio, I suggest removing it from the template gallery, at least until we have compatibility.


Benchmark

update benchmark

Codecov Report

Merging #7 (ff625c9) into master (fa644af) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master       #7   +/-   ##
=======================================
  Coverage   96.32%   96.32%
=======================================
  Files          11       11
  Lines         381      381
=======================================
  Hits          367      367
  Misses          7        7
  Partials        7        7

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 fa644af...ff625c9. Read the comment docs.


Question:

Hi Andreas,
after looking into serial terminal i saw that the device searches for wifi's again and again even if its conected to one.
Only for my understanding: Is that necessary? e.g. for keeping the wifi alife?
Wouldn't it be nice to search the Wifi only when not connected? or when the settings page gets opened?
Have a nice Evening
Lukas

Yes, that's right ;-)
Since 1.5.0034_develop that function will called only in background to update the environment, so it not consumes cpu time. That's currently the easiest thing to meet different (not known) use cases for the usabilty.
And also yes, could be updated only with some wait time, when the settings page is opened - with some extra effort on dev side...
We can put it on the backlog.


DCR: .bot file seems unnecessary

The docs tell us to put he appid and password in the application settings of the web service, so what purpose is the .bot file serving?  It's confusing to have values in app settings of Azure, yet in my source code (.bot file) locally.  It seems like all we've done is move app settings - a concept that works for web apps and v3 bots perfectly - to a new paradigm with no gain.  I was never able to figure out securing this file (encrypt/decrypt) as any time i tried things became out of sync w/ what was deployed to Azure and my bot ceased to work.  This is not what we should expect of a real-world deployment story for a bot on the Microsoft Bot Framework and Azure Bot Service.
Furthermore this file complicates the devops story.  Instead of different environments deploying the exact same code and altering environment vars (app settings), we now have to search/replace tokens within a file.  Customary procedure for something like this has always been to have ".settings" or ".settings" files which are then easily usable in a devops pipeline.
Still in other Azure services where there may be "encrypted" configuration available, there is a "download profile" link to supply the developer w/ the necessary credentials; this would be more preferable, with there being a UI in Azure to edit the .bot file (where saving then encrypts it)

We are about a week away from merging a set of changes into master that will address these issues.  You can see the coming changes by looking at the samples found in in the samples-work-in-progress branch.  We've removed the reliance on .bot files and .recipe files.  .bot file configuration settings are not stored in platform specific configuration files (appsettings.json for .net and .env for Node.js).  recipe files and their usage by msbot clone services has been replaced by the usage of Azure ARM templates and Az CLI commands.  When this branch is merged we will also be publishing update documentation to account for these changes.


Unable to enumerate bluetooth devices

This is one is a major. Once it has happened, you have to restart OH to get rid of it.
This happens after I enable "connection control" for a device (particularly to Xiaomi mi flora).
It tries to connect to that device, I can see that it also tries to do authentication (via setting a pin code) and then Bluez reports infamous Software caused connection abort error and then it starts failing with this:
14:07:06.022 [WARN ] [oth.manager.impl.BluetoothManagerImpl] - Device discovery job error
cz.organovabanka.bluetooth.manager.transport.dbus.BluezException: Unable to enumerate bluetooth objects when processing /org/bluez/hci0
	at cz.organovabanka.bluetooth.manager.transport.dbus.BluezAdapter.getDevices(BluezAdapter.java:253) ~[?:?]
	at cz.organovabanka.bluetooth.manager.transport.dbus.BluezFactory.lambda$getDiscoveredDevices$5(BluezFactory.java:301) ~[?:?]
	at java.util.concurrent.ConcurrentHashMap$ValueSpliterator.forEachRemaining(ConcurrentHashMap.java:3566) [?:?]
	at java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:580) [?:?]
	at cz.organovabanka.bluetooth.manager.transport.dbus.BluezFactory.getDiscoveredDevices(BluezFactory.java:301) [219:organovabanka.org.eclipse.smarthome.binding.bluetooth.transport.dbus:1.0.0.SNAPSHOT]
	at org.sputnikdev.bluetooth.manager.impl.BluetoothManagerImpl$DeviceDiscoveryJob.discoverDevices(BluetoothManagerImpl.java:690) [214:org.sputnikdev.org.eclipse.smarthome.binding.bluetooth:1.1.5]
	at org.sputnikdev.bluetooth.manager.impl.BluetoothManagerImpl$DeviceDiscoveryJob.run(BluetoothManagerImpl.java:683) [214:org.sputnikdev.org.eclipse.smarthome.binding.bluetooth:1.1.5]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [?:?]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [?:?]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [?:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?]
	at java.lang.Thread.run(Thread.java:748) [?:?]
Caused by: org.freedesktop.dbus.exceptions.NotConnected: Disconnected
	at sun.reflect.GeneratedConstructorAccessor247.newInstance(Unknown Source) ~[?:?]
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) ~[?:?]
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423) ~[?:?]
	at org.freedesktop.dbus.Error.getException(Error.java:143) ~[?:?]
	at org.freedesktop.dbus.Error.throwException(Error.java:175) ~[?:?]
	at org.freedesktop.dbus.RemoteInvocationHandler.executeRemoteMethod(RemoteInvocationHandler.java:168) ~[?:?]
	at org.freedesktop.dbus.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:234) ~[?:?]
	at com.sun.proxy.$Proxy154.GetManagedObjects(Unknown Source) ~[?:?]
	at cz.organovabanka.bluetooth.manager.transport.dbus.BluezAdapter.getDevices(BluezAdapter.java:249) ~[?:?]
	... 13 more

I'll do some more experiments to get some more details.

I also got this in the logs:
14:06:56.935 [WARN ] [.impl.AbstractBluetoothObjectGovernor] - Error occurred while interacting (setAlias) with native object: /B8:27:EB:60:0C:43/4C:65:A8:D0:7A:EE : Disconnected
14:06:57.006 [WARN ] [.impl.AbstractBluetoothObjectGovernor] - Error occurred while interacting (setAlias) with native object: /B8:27:EB:60:0C:43/C0:7E:98:8F:F4:28 : Disconnected
14:06:57.026 [ERROR] [h.manager.transport.dbus.BluezAdapter] - /org/bluez/hci2: Failed to remove device /org/bluez/hci2/dev_4C_65_A8_D0_7A_EE, reason: Disconnected
14:06:57.078 [ERROR] [h.manager.transport.dbus.BluezAdapter] - /org/bluez/hci2: Failed to remove device /org/bluez/hci2/dev_C0_7E_98_8F_F4_28, reason: Disconnected
14:06:57.110 [WARN ] [manager.impl.CompletableFutureService] - Bluetooth error happened while competing a future: /B8:27:EB:60:0C:43/4C:65:A8:D0:7A:EE : Error occurred while interacting (setAlias) with native object: /B8:27:EB:60:0C:43/4C:65:A8:D0:7A:EE : Disconnected
14:06:57.189 [WARN ] [.impl.AbstractBluetoothObjectGovernor] - Error occurred while interacting (setAlias) with native object: /B8:27:EB:60:0C:43/E7:AC:07:C9:F7:3F : Disconnected

I'll dig further and let you know how it goes. It might be that BM needs some changes as well.

Got that again after roughly a day of observation:
13:57:48.475 [WARN ] [oth.manager.impl.BluetoothManagerImpl] - Device discovery job error
cz.organovabanka.bluetooth.manager.transport.dbus.BluezException: Unable to enumerate bluetooth objects when processing /org/bluez/hci0
	at cz.organovabanka.bluetooth.manager.transport.dbus.BluezAdapter.getDevices(BluezAdapter.java:253) ~[?:?]
	at cz.organovabanka.bluetooth.manager.transport.dbus.BluezFactory.lambda$getDiscoveredDevices$5(BluezFactory.java:301) ~[?:?]
	at java.util.concurrent.ConcurrentHashMap$ValueSpliterator.forEachRemaining(ConcurrentHashMap.java:3566) [?:?]
	at java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:580) [?:?]
	at cz.organovabanka.bluetooth.manager.transport.dbus.BluezFactory.getDiscoveredDevices(BluezFactory.java:301) [219:organovabanka.org.eclipse.smarthome.binding.bluetooth.transport.dbus:1.0.0.SNAPSHOT]
	at org.sputnikdev.bluetooth.manager.impl.BluetoothManagerImpl$DeviceDiscoveryJob.discoverDevices(BluetoothManagerImpl.java:690) [214:org.sputnikdev.org.eclipse.smarthome.binding.bluetooth:1.1.5]
	at org.sputnikdev.bluetooth.manager.impl.BluetoothManagerImpl$DeviceDiscoveryJob.run(BluetoothManagerImpl.java:683) [214:org.sputnikdev.org.eclipse.smarthome.binding.bluetooth:1.1.5]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [?:?]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [?:?]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [?:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?]
	at java.lang.Thread.run(Thread.java:748) [?:?]
Caused by: org.freedesktop.dbus.exceptions.NotConnected: Not Connected
	at org.freedesktop.dbus.RemoteInvocationHandler.executeRemoteMethod(RemoteInvocationHandler.java:137) ~[?:?]
	at org.freedesktop.dbus.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:234) ~[?:?]
	at com.sun.proxy.$Proxy137.GetManagedObjects(Unknown Source) ~[?:?]
	at cz.organovabanka.bluetooth.manager.transport.dbus.BluezAdapter.getDevices(BluezAdapter.java:249) ~[?:?]
	... 13 more
13:57:48.743 [WARN ] [.impl.AbstractBluetoothObjectGovernor] - Error occurred while interacting (setAlias) with native object: /00:1A:7D:DA:71:05/E7:AC:07:C9:F7:3F : Not Connected
13:57:48.827 [WARN ] [.impl.AbstractBluetoothObjectGovernor] - Error occurred while interacting (setAlias) with native object: /00:1A:7D:DA:71:04/E7:AC:07:C9:F7:3F : Not Connected

Slightly different message though.

Ok, I was able to replicate the issue in the end; it should be solved upon migration to dbus-java-3.0.0. However, I got a different issue - what are the error policies upon failing connections? Generaly, following can occur when connect() is invoked:

no reply ... - generic failed connect, should I throw in BluetoothInteractionException, or NotReadyYet?
allready pending
connection caused by software abort (which can mean pretty much anything, but usualy a new attempt to connect is required).

Sorry @xrucka , just noticed this. I'll think aand reply in the morning.

Great, thanks :-)