text:
can't build the tools

I'm trying to build the tools in the 'tools' branch and it seems that cmake builds makefiles that can't find the header files in /usr/local/include
┌─[waboring@airspy] - [~/new/airspyhf-2/tools/src] - [Fri Aug 17, 13:25]
└─[$] <git:(tools*)> mkdir build
┌─[waboring@airspy] - [~/new/airspyhf-2/tools/src] - [Fri Aug 17, 13:25]
└─[$] <git:(tools*)> cd build
┌─[waboring@airspy] - [~/new/airspyhf-2/tools/src/build] - [Fri Aug 17, 13:25]
└─[$] <git:(tools*)> cmake ..
-- The C compiler identification is GNU 6.3.0
-- The CXX compiler identification is GNU 6.3.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Configuring done
-- Generating done
-- Build files have been written to: /home/waboring/new/airspyhf-2/tools/src/build
┌─[waboring@airspy] - [~/new/airspyhf-2/tools/src/build] - [Fri Aug 17, 13:26]
└─[$] <git:(tools*)> make
Scanning dependencies of target airspyhf_lib_version
[ 12%] Building C object CMakeFiles/airspyhf_lib_version.dir/airspyhf_lib_version.c.o
/home/waboring/new/airspyhf-2/tools/src/airspyhf_lib_version.c:26:22: fatal error: airspyhf.h: No such file or directory
 #include <airspyhf.h>
                      ^
compilation terminated.
CMakeFiles/airspyhf_lib_version.dir/build.make:62: recipe for target 'CMakeFiles/airspyhf_lib_version.dir/airspyhf_lib_version.c.o' failed
make[2]: *** [CMakeFiles/airspyhf_lib_version.dir/airspyhf_lib_version.c.o] Error 1
CMakeFiles/Makefile2:67: recipe for target 'CMakeFiles/airspyhf_lib_version.dir/all' failed
make[1]: *** [CMakeFiles/airspyhf_lib_version.dir/all] Error 2
Makefile:127: recipe for target 'all' failed
make: *** [all] Error 2

└─[$] <git:(tools*)> ls -al /usr/local/include
total 36
drwxrwsr-x  4 root staff  4096 Aug 16 16:21 .
drwxrwsr-x 10 root staff  4096 Jun 26 20:03 ..
drwxr-sr-x  2 root staff  4096 Aug 16 16:26 libairspy
drwxr-sr-x  2 root staff  4096 Aug 17 13:03 libairspyhf
-rw-r--r--  1 root staff 12947 Aug 16 15:41 rtl-sdr.h
-rw-r--r--  1 root staff  1436 Aug 16 15:41 rtl-sdr_export.h

└─[$] <git:(tools*)> ls -al /usr/local/include/libairspyhf
total 24
drwxr-sr-x 2 root staff 4096 Aug 17 13:03 .
drwxrwsr-x 4 root staff 4096 Aug 16 16:21 ..
-rw-r--r-- 1 root staff 5967 Aug 17 11:28 airspyhf.h
-rw-r--r-- 1 root staff 2528 Aug 17 11:28 airspyhf_commands.h
-rw-r--r-- 1 root staff 2667 Aug 17 11:28 iqbalancer.h

It should find in the clone.
Delete and uninstall any previously built version of the lib and try that:
git clone https://github.com/IW0HDV/airspyhf.git -b tools
cd airspyhf/
mkdir build
cd build
cmake ../ -DINSTALL_UDEV_RULES=ON
make VERBOSE=1

ok my mistake, I was building from the src/tools/ dir.   that seems to have fixed it.

Anyway, clone again, as in the meantime I updated from the upstream with all the new features and fixed a bug in -a parameter (airspyhf_rx).

authors: amontefusco hemna


text:
[Enhancement] My tablet is not compatible T.T

(i tried using the latest artifact)
Is your feature request related to a problem? Please describe.
PlayStore tells me that is not available for my device and if i download the apk it tells me something like "it look like the package is not valid"
Describe the solution you'd like
Make it compatible with my tablet please.
Additional context
Device: Lenovo Smart Tab M10 HD Wifi
Arq: ARMv8-A 64bits
OS: Android 10

Android 11 is the minimum version required

Can i ask why Android 11?

I'll create a tab in README because this question is already way too asked and answered.
Android 11 is the minimum android version required to keep all features of the Gallery like Trash-bin, most of the API used etc.
Reducing the android version would result in feature loss for under android 11 devices and would require lots of compatibility changes for the MediaStore API

This question must be very frequent because, in my opinion, Android 11 is a very high version for the minimum requirement of an app that is so necessary for everyday use. My phone has Android 13 thanks to a custom ROM, otherwise it would still be on Android 10 and usually, the devices of people I know have Android 9/10.
I feel sad that such a good app didn't get more reach because of this compatibility detail.

source: gharchive/issue

license_type: permissive

license_source: github-api


text:
Question regarding snapshot conflict

Hello, I am currently using this plugin for my game. Is there any direction or sample code for resolving snapshot conflict?
I am currently having a problem that my game save data seem not loading well after some change, or deleting application data. I need to restart the app for it to load well, but there is no way I am going to let this problem slide.
I need your help regarding this matter.

Hi! The plugin is just an interface between the Google API and Godot, so at the end of the day you should be fine following Google's documentation on it, that's what I used to develop the plugin.
For save games specifically you can take a look here, but the docs are quite scarce. This project has a demo app here that you can open and Godot. In theory, if you provide a Game Id of your own, you should be able to run the demo app in an android device and test it there, but I've only tried with my own Game Id, not others.
If you do find a problem in the plugin implementation please let me know, and I'll fix it ASAP, but as mentioned and providing that I didn't mess anything, it's just a bypass between Google and Godot! 😅

Thank you for answering.
What I mean is snapshot_conflict_emitted just provide the snapshot data without public function to resolve the conflict. Meanwhile android sdk of google play games give function to resolve the conflict.
Unity google game sdk also have option to resolve conflict manually or automatically.
I can't even choose what snapshot to be loaded or saved from snapshot_conflict_emitted signal.

Hi! If I understand it correctly, you need to know what action triggered the conflict_emitted signal, either the load or the save methods? I can add a field in the SnapshotConflict object coming in that signal, to indicate the original caller, something like a string with "Save" or "Load", that would be enough for you?
I remember trying to implement the manual flow for resolving conflicts, but I think there was a problem with object types conversion between Java and GDScript. I can try again, too, but if adding the origin field to the SnapshotConflict solves the problem for now, I can quickly try that. What do you think?

Can you try this version of the plugin? I added a origin field to the SnapshotConflinct class in the SnapshotsClient autoload, so now you will know which method originated the conflict. The possible values are either LOAD or SAVE.
If this works, let me know and I will push the new version to the repo.
addons.zip

Okay, I will try it

Hey, it works. It give me "SAVE" and "LOAD" string for each operation in origin.

Nice! In the meantime, what's the manual flow to solve conflicts in other sdks? do you have any examples?

I don't understand either how to do conflict resolution. What I understand from Google's docs is that the designer of the game has to decide depending on every case. I guess there's no correct answer to the question.

Hi @RProduction I'm closing the issue for now, but please feel free to ask any other questions!

authors: Iakobs RProduction

repo: Iakobs/godot-play-game-services

license: MIT


text:
add context-aware function invokations

functions invoked now pass the DialogueManager as well
refactored InvokeFunction code
updated samples to show context-aware invocations

closes #47

source: gharchive/pull-request

repo: Ibralogue/Ibralogue


text:
Sass::SyntaxError in SabisuRails::Explorer#index on rails 4.2.0

I am trying to complete the apionrails tutorial using rails 4.2.0, and for some reason it shows me this error, I am thinking it is due to the fact that I am using rails 4.2.0.
this is where the error is thrown
Extracted source (around line #132):
@include border-radius($form-input-radius);
@include box-shadow($form-input-box-shadow);
@include appearance($ap: none); # line 132
@if($include-input-transition) {
@include single-transition($form-input-transition-property $form-input-transition-duration $form-input-transition-timing-function);

I'm having the same error as well.

Same problem with me

Try locking out the compass version on the Gemfile to something like:
gem 'compass-rails', '1.1.7'

any update on this? the gem 'compass-rails', '1.1.7' doesnt work

The problem comes with furatto and the compass version, this is my Gemfile.lock file, if someone else can share another one, probably I can address the problem in a better way....
GIT
  remote: git://github.com/IcaliaLabs/sabisu-rails.git
  revision: de6340971e70589de2ae2cb0d8170a9a9df84103
  specs:
    sabisu_rails (0.0.2.beta)
      actionpack (~> 4.0)
      activemodel (~> 4.0)
      httparty (~> 0.13)

GEM
  remote: https://rubygems.org/
  specs:
    actionmailer (4.0.2)
      actionpack (= 4.0.2)
      mail (~> 2.5.4)
    actionpack (4.0.2)
      activesupport (= 4.0.2)
      builder (~> 3.1.0)
      erubis (~> 2.7.0)
      rack (~> 1.5.2)
      rack-test (~> 0.6.2)
    active_model_serializers (0.8.1)
      activemodel (>= 3.0)
    activemodel (4.0.2)
      activesupport (= 4.0.2)
      builder (~> 3.1.0)
    activerecord (4.0.2)
      activemodel (= 4.0.2)
      activerecord-deprecated_finders (~> 1.0.2)
      activesupport (= 4.0.2)
      arel (~> 4.0.0)
    activerecord-deprecated_finders (1.0.3)
    activesupport (4.0.2)
      i18n (~> 0.6, >= 0.6.4)
      minitest (~> 4.2)
      multi_json (~> 1.3)
      thread_safe (~> 0.1)
      tzinfo (~> 0.3.37)
    addressable (2.3.6)
    arel (4.0.2)
    bcrypt (3.1.7)
    builder (3.1.4)
    chunky_png (1.3.1)
    coffee-rails (4.0.1)
      coffee-script (>= 2.2.0)
      railties (>= 4.0.0, < 5.0)
    coffee-script (2.2.0)
      coffee-script-source
      execjs
    coffee-script-source (1.7.0)
    compass (0.12.6)
      chunky_png (~> 1.2)
      fssm (>= 0.2.7)
      sass (~> 3.2.19)
    compass-rails (1.1.7)
      compass (>= 0.12.2)
      sprockets (<= 2.11.0)
    delayed_job (4.0.6)
      activesupport (>= 3.0, < 5.0)
    delayed_job_active_record (4.0.3)
      activerecord (>= 3.0, < 5.0)
      delayed_job (>= 3.0, < 4.1)
    devise (3.2.4)
      bcrypt (~> 3.0)
      orm_adapter (~> 0.1)
      railties (>= 3.2.6, < 5)
      thread_safe (~> 0.1)
      warden (~> 1.2.3)
    diff-lcs (1.2.5)
    email_spec (1.6.0)
      launchy (~> 2.1)
      mail (~> 2.2)
    erubis (2.7.0)
    execjs (2.2.0)
    factory_girl (4.4.0)
      activesupport (>= 3.0.0)
    factory_girl_rails (4.4.1)
      factory_girl (~> 4.4.0)
      railties (>= 3.0.0)
    ffaker (1.24.0)
    font-awesome-rails (4.1.0.0)
      railties (>= 3.2, < 5.0)
    fssm (0.2.10)
    furatto (1.3.7)
      actionpack (>= 3.0)
      activemodel (>= 3.0)
      railties (>= 3.0)
    hike (1.2.3)
    httparty (0.13.1)
      json (~> 1.8)
      multi_xml (>= 0.5.2)
    i18n (0.7.0)
    jquery-rails (3.1.0)
      railties (>= 3.0, < 5.0)
      thor (>= 0.14, < 2.0)
    json (1.8.1)
    kaminari (0.16.1)
      actionpack (>= 3.0.0)
      activesupport (>= 3.0.0)
    launchy (2.4.3)
      addressable (~> 2.3)
    mail (2.5.4)
      mime-types (~> 1.16)
      treetop (~> 1.4.8)
    mime-types (1.25.1)
    minitest (4.7.5)
    multi_json (1.10.1)
    multi_xml (0.5.5)
    orm_adapter (0.5.0)
    polyglot (0.3.5)
    rack (1.5.2)
    rack-test (0.6.3)
      rack (>= 1.0)
    rails (4.0.2)
      actionmailer (= 4.0.2)
      actionpack (= 4.0.2)
      activerecord (= 4.0.2)
      activesupport (= 4.0.2)
      bundler (>= 1.3.0, < 2.0)
      railties (= 4.0.2)
      sprockets-rails (~> 2.0.0)
    railties (4.0.2)
      actionpack (= 4.0.2)
      activesupport (= 4.0.2)
      rake (>= 0.8.7)
      thor (>= 0.18.1, < 2.0)
    rake (10.4.2)
    rdoc (4.1.1)
      json (~> 1.4)
    rspec-core (2.14.8)
    rspec-expectations (2.14.5)
      diff-lcs (>= 1.1.3, < 2.0)
    rspec-mocks (2.14.6)
    rspec-rails (2.14.2)
      actionpack (>= 3.0)
      activemodel (>= 3.0)
      activesupport (>= 3.0)
      railties (>= 3.0)
      rspec-core (~> 2.14.0)
      rspec-expectations (~> 2.14.0)
      rspec-mocks (~> 2.14.0)
    sass (3.2.19)
    sass-rails (4.0.3)
      railties (>= 4.0.0, < 5.0)
      sass (~> 3.2.0)
      sprockets (~> 2.8, <= 2.11.0)
      sprockets-rails (~> 2.0)
    sdoc (0.4.0)
      json (~> 1.8)
      rdoc (~> 4.0, < 5.0)
    shoulda-matchers (2.6.1)
      activesupport (>= 3.0.0)
    simple_form (3.0.2)
      actionpack (~> 4.0)
      activemodel (~> 4.0)
    sprockets (2.11.0)
      hike (~> 1.2)
      multi_json (~> 1.0)
      rack (~> 1.0)
      tilt (~> 1.1, != 1.3.0)
    sprockets-rails (2.0.1)
      actionpack (>= 3.0)
      activesupport (>= 3.0)
      sprockets (~> 2.8)
    sqlite3 (1.3.9)
    thor (0.19.1)
    thread_safe (0.3.4)
    tilt (1.4.1)
    treetop (1.4.15)
      polyglot
      polyglot (>= 0.3.1)
    tzinfo (0.3.43)
    uglifier (2.5.1)
      execjs (>= 0.3.0)
      json (>= 1.8.0)
    warden (1.2.3)
      rack (>= 1.0)

PLATFORMS
  ruby

DEPENDENCIES
  active_model_serializers
  coffee-rails (~> 4.0.0)
  compass-rails
  delayed_job_active_record
  devise
  email_spec
  factory_girl_rails
  ffaker
  font-awesome-rails
  furatto
  jquery-rails
  kaminari
  rails (= 4.0.2)
  rspec-rails (~> 2.14)
  sabisu_rails!
  sass-rails (~> 4.0.0)
  sdoc
  shoulda-matchers
  simple_form
  sqlite3
  uglifier (>= 1.3.0)

Thnks! =)

Hi @kurenn
I am seeing the same issue as well. Below is my Gemfile.lock. Hope this helps. The tool looks fantastic and I'd love to get it working.
Also, I am currently going through your rails API tutorial. It is awesome, thank you very much for putting it together.
GIT
  remote: git://github.com/IcaliaLabs/sabisu-rails.git
  revision: de6340971e70589de2ae2cb0d8170a9a9df84103
  specs:
    sabisu_rails (0.0.2.beta)
      actionpack (~> 4.0)
      activemodel (~> 4.0)
      httparty (~> 0.13)

GEM
  remote: https://rubygems.org/
  specs:
    actionmailer (4.2.0)
      actionpack (= 4.2.0)
      actionview (= 4.2.0)
      activejob (= 4.2.0)
      mail (~> 2.5, >= 2.5.4)
      rails-dom-testing (~> 1.0, >= 1.0.5)
    actionpack (4.2.0)
      actionview (= 4.2.0)
      activesupport (= 4.2.0)
      rack (~> 1.6.0)
      rack-test (~> 0.6.2)
      rails-dom-testing (~> 1.0, >= 1.0.5)
      rails-html-sanitizer (~> 1.0, >= 1.0.1)
    actionview (4.2.0)
      activesupport (= 4.2.0)
      builder (~> 3.1)
      erubis (~> 2.7.0)
      rails-dom-testing (~> 1.0, >= 1.0.5)
      rails-html-sanitizer (~> 1.0, >= 1.0.1)
    activejob (4.2.0)
      activesupport (= 4.2.0)
      globalid (>= 0.3.0)
    activemodel (4.2.0)
      activesupport (= 4.2.0)
      builder (~> 3.1)
    activerecord (4.2.0)
      activemodel (= 4.2.0)
      activesupport (= 4.2.0)
      arel (~> 6.0)
    activesupport (4.2.0)
      i18n (~> 0.7)
      json (~> 1.7, >= 1.7.7)
      minitest (~> 5.1)
      thread_safe (~> 0.3, >= 0.3.4)
      tzinfo (~> 1.1)
    arel (6.0.0)
    bcrypt (3.1.10)
    binding_of_caller (0.7.2)
      debug_inspector (>= 0.0.1)
    builder (3.2.2)
    byebug (4.0.1)
      columnize (= 0.9.0)
      rb-readline (= 0.5.2)
    chunky_png (1.3.4)
    coffee-rails (4.1.0)
      coffee-script (>= 2.2.0)
      railties (>= 4.0.0, < 5.0)
    coffee-script (2.3.0)
      coffee-script-source
      execjs
    coffee-script-source (1.9.1)
    columnize (0.9.0)
    compass (1.0.3)
      chunky_png (~> 1.2)
      compass-core (~> 1.0.2)
      compass-import-once (~> 1.0.5)
      rb-fsevent (>= 0.9.3)
      rb-inotify (>= 0.9)
      sass (>= 3.3.13, < 3.5)
    compass-core (1.0.3)
      multi_json (~> 1.0)
      sass (>= 3.3.0, < 3.5)
    compass-import-once (1.0.5)
      sass (>= 3.2, < 3.5)
    compass-rails (2.0.4)
      compass (~> 1.0.0)
      sass-rails (<= 5.0.1)
      sprockets (< 2.13)
    debug_inspector (0.0.2)
    devise (3.4.1)
      bcrypt (~> 3.0)
      orm_adapter (~> 0.1)
      railties (>= 3.2.6, < 5)
      responders
      thread_safe (~> 0.1)
      warden (~> 1.2.3)
    diff-lcs (1.2.5)
    erubis (2.7.0)
    execjs (2.4.0)
    factory_girl (4.5.0)
      activesupport (>= 3.0.0)
    factory_girl_rails (4.5.0)
      factory_girl (~> 4.5.0)
      railties (>= 3.0.0)
    ffaker (1.32.1)
    ffi (1.9.8)
    font-awesome-rails (4.3.0.0)
      railties (>= 3.2, < 5.0)
    furatto (1.3.7)
      actionpack (>= 3.0)
      activemodel (>= 3.0)
      railties (>= 3.0)
    globalid (0.3.3)
      activesupport (>= 4.1.0)
    hike (1.2.3)
    httparty (0.13.3)
      json (~> 1.8)
      multi_xml (>= 0.5.2)
    i18n (0.7.0)
    jbuilder (2.2.11)
      activesupport (>= 3.0.0, < 5)
      multi_json (~> 1.2)
    jquery-rails (4.0.3)
      rails-dom-testing (~> 1.0)
      railties (>= 4.2.0)
      thor (>= 0.14, < 2.0)
    json (1.8.2)
    loofah (2.0.1)
      nokogiri (>= 1.5.9)
    mail (2.6.3)
      mime-types (>= 1.16, < 3)
    mime-types (2.4.3)
    mini_portile (0.6.2)
    minitest (5.5.1)
    multi_json (1.11.0)
    multi_xml (0.5.5)
    nokogiri (1.6.6.2)
      mini_portile (~> 0.6.0)
    orm_adapter (0.5.0)
    rack (1.6.0)
    rack-test (0.6.3)
      rack (>= 1.0)
    rails (4.2.0)
      actionmailer (= 4.2.0)
      actionpack (= 4.2.0)
      actionview (= 4.2.0)
      activejob (= 4.2.0)
      activemodel (= 4.2.0)
      activerecord (= 4.2.0)
      activesupport (= 4.2.0)
      bundler (>= 1.3.0, < 2.0)
      railties (= 4.2.0)
      sprockets-rails
    rails-deprecated_sanitizer (1.0.3)
      activesupport (>= 4.2.0.alpha)
    rails-dom-testing (1.0.5)
      activesupport (>= 4.2.0.beta, < 5.0)
      nokogiri (~> 1.6.0)
      rails-deprecated_sanitizer (>= 1.0.1)
    rails-html-sanitizer (1.0.2)
      loofah (~> 2.0)
    railties (4.2.0)
      actionpack (= 4.2.0)
      activesupport (= 4.2.0)
      rake (>= 0.8.7)
      thor (>= 0.18.1, < 2.0)
    rake (10.4.2)
    rb-fsevent (0.9.4)
    rb-inotify (0.9.5)
      ffi (>= 0.5.0)
    rb-readline (0.5.2)
    rdoc (4.2.0)
      json (~> 1.4)
    responders (2.1.0)
      railties (>= 4.2.0, < 5)
    rspec-core (3.2.2)
      rspec-support (~> 3.2.0)
    rspec-expectations (3.2.0)
      diff-lcs (>= 1.2.0, < 2.0)
      rspec-support (~> 3.2.0)
    rspec-mocks (3.2.1)
      diff-lcs (>= 1.2.0, < 2.0)
      rspec-support (~> 3.2.0)
    rspec-rails (3.2.1)
      actionpack (>= 3.0, < 4.3)
      activesupport (>= 3.0, < 4.3)
      railties (>= 3.0, < 4.3)
      rspec-core (~> 3.2.0)
      rspec-expectations (~> 3.2.0)
      rspec-mocks (~> 3.2.0)
      rspec-support (~> 3.2.0)
    rspec-support (3.2.2)
    sass (3.4.13)
    sass-rails (5.0.1)
      railties (>= 4.0.0, < 5.0)
      sass (~> 3.1)
      sprockets (>= 2.8, < 4.0)
      sprockets-rails (>= 2.0, < 4.0)
      tilt (~> 1.1)
    sdoc (0.4.1)
      json (~> 1.7, >= 1.7.7)
      rdoc (~> 4.0)
    shoulda-matchers (2.8.0)
      activesupport (>= 3.0.0)
    simple_form (3.1.0)
      actionpack (~> 4.0)
      activemodel (~> 4.0)
    spring (1.3.3)
    sprockets (2.12.3)
      hike (~> 1.2)
      multi_json (~> 1.0)
      rack (~> 1.0)
      tilt (~> 1.1, != 1.3.0)
    sprockets-rails (2.2.4)
      actionpack (>= 3.0)
      activesupport (>= 3.0)
      sprockets (>= 2.8, < 4.0)
    sqlite3 (1.3.10)
    thor (0.19.1)
    thread_safe (0.3.5)
    tilt (1.4.1)
    turbolinks (2.5.3)
      coffee-rails
    tzinfo (1.2.2)
      thread_safe (~> 0.1)
    uglifier (2.7.1)
      execjs (>= 0.3.0)
      json (>= 1.8.0)
    warden (1.2.3)
      rack (>= 1.0)
    web-console (2.1.2)
      activemodel (>= 4.0)
      binding_of_caller (>= 0.7.2)
      railties (>= 4.0)
      sprockets-rails (>= 2.0, < 4.0)

PLATFORMS
  ruby

DEPENDENCIES
  byebug
  coffee-rails (~> 4.1.0)
  compass-rails
  devise
  factory_girl_rails
  ffaker
  font-awesome-rails
  furatto
  jbuilder (~> 2.0)
  jquery-rails
  rails (= 4.2.0)
  rspec-rails
  sabisu_rails!
  sass-rails (~> 5.0)
  sdoc (~> 0.4.0)
  shoulda-matchers
  simple_form
  spring
  sqlite3
  turbolinks
  uglifier (>= 1.3.0)
  web-console (~> 2.0)

changing the version of furatto to 1.3.7 solve the problem. thanks

1.3.7 Furatto did not solve the issue, I want to use that gem of yours, seems very useful. Thanks for the tutorial by the way!
ERR;
NameError in SabisuRails::Explorer#index

Try to get the latest version from sabisu, that is from github:
Your Gemfile
source 'https://rubygems.org'
.
.
.
gem 'furatto', github: "IcaliaLabs/furatto-rails"
gem 'sabisu_rails', github: "IcaliaLabs/sabisu-rails"
.
.

Let me know if that works, I currently have one project with that configuration

Still not working; the error is as follows:

Sass::SyntaxError in SabisuRails::Explorer#index
Showing /Users/ardacicek/.rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/bundler/gems/sabisu-rails-f9c9f2c41d84/app/views/layouts/sabisu_rails.html.erb where line #13 raised:
File to import not found or unreadable: compass/css3.

Using furatto 1.4.0 (was 1.3.7) from git://github.com/IcaliaLabs/furatto-rails.git (at master)
Using sabisu_rails 0.0.2.beta from git://github.com/IcaliaLabs/sabisu-rails.git (at master)

Update the version of compass-rails to at least 2.0:
gem 'compass-rails', '~> 2.0'

Could not track what I really have done but finally I manage to use the sabisu, thanks a lot.

Can you share what you did in order to close this issue?

Gemfile: solved my issue
.
.
gem 'sabisu_rails', github: "IcaliaLabs/sabisu-rails"
gem 'furatto', github: "IcaliaLabs/furatto-rails"
gem 'compass-rails', github: "Compass/compass-rails", branch: "master"
.
.

Sweet!

I had this problem and found that the only way that I could get it to work was to remove the gem 'compass-rails' altogether.
The compass-rails was causing me to have dependency issues, but once I had removed compass-rails I got the Saibisu working all together.

Gemfile: solve this issue
.
.
gem 'furatto', github: "IcaliaLabs/furatto-rails"
gem 'sabisu_rails', github: "IcaliaLabs/sabisu-rails"
gem 'compass-rails', '~> 2.0'
.
.

authors: adinsley archagy ardarda clondono danielmoralesp gilmishal kchens kcoleman731 kurenn tenaz3

repo: IcaliaLabs/sabisu-rails

license: mit

license_source: bigquery


text:
numpy (np) import  missing

Hi,
I believe you're missing an import statement -> in your 'define_date' function you refer to np, but it isn't imported as far as I can see.
see -> return float(np.nan)
Best regards,
Mike

Fixed by latest release

authors: HurinHu MBKraus

repo: Iceloof/GoogleNews


text:
Using OIDC client for OAUTH

From OidcClient.js and OidcClientSettings.js, looks like this library supports OpenId. Is there a way to configure this for OAUTH, where I can provide authorizationEndpoint, tokenEndpoint etc separately (not the openId way).

This is a question. I am not able to add the appropriate label to this issue.

Yes, you can use it just for OAuth2. Just request "token" instead of "id_token token" for the response type.

authors: anandvnath brockallen

repo: IdentityModel/oidc-client-js


text:
Added link Platform scenario sample

I created a .NET Core and ASP.NET Core "Platform scenario" sample and have added a link to it in the Community Quickstarts document.
It has "internal" and "external" clients to show what an interaction of consent could/should look alike.

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

I added this manually since merge conflict up here aren't working. Thanks!

Did you have a look at the sample at all?

authors: BenjaminAbt brockallen dnfclas leastprivilege


text:
🛑 Swila is down

In eedfd70, Swila (https://swila.waithakasam.com) was down:

HTTP code: 530
Response time: 93 ms

Resolved: Swila is back up in eef1b3b after 1 hour, 58 minutes.

repo: IdrisFallout/upptime


text:
List only .md files

Question
I have for various reasons (poor organisation in the main on my part)  a mixed set of files in my vault, including images, pdfs etc mixed among my .md files.
Is it possible to only show the markdown files, when for example executing ObsNvimFindNote or ObsNvimFindInNote etc

Yeah, sure it's possible.
I guess I might be able to add ObsNvimFindFile and make ObsNvimFindNote/ObsNvimFindInNote searching only through MD files.
I'll try to think of the solution 🤔
PS. As s work around you might use https://github.com/nvim-telescope/telescope-fzf-native.nvim .md$ should work.

Many Thanks. And Doh - I should have thought of that work around as well - will give that a go.

Also you might want to check for alternative plugins. There is a https://github.com/epwalsh/obsidian.nvim
It supports attachments, so it may be more comfortable to use for you.

authors: IlyasYOY solarider


text:
Some typos and small corrections

Hey Gene!
There were some small typos and one little suggested re-write.  You definitely don't need to accept this PR, but I hope it will at least help with these little things.
Overall I find the message very clear and well presented. The examples you gave along side each explanation helped to round out what you were saying with a more concrete example.
I think there are a few things that might be a bit more complex in a real world example with a large scale app.  Things like code splitting can make it challenging if the code is not being served from the same origin as the sites root domain.  This will require advanced configuration if your code splitting setup.  It may be worth mentioning this information.
Thanks for letting me take a pass over this.  I really like the way this reads and is presented.
Good luck with it, and let me know if there's some way I can contribute!
-Andy

@terodox thanks for giving it a read. I'm going to merge the PR, and I will catch up with you about your thoughts about code-splitting... I have a couple ideas on the matter. Thank you!

authors: gconnolly terodox


text:
Consider caching process data

#89 will update the main process table to poll the server for process data. This in turn will poll the Process Manager for changes to process information. We've been told to expect on the order of 10 simultaneous users. If we assume refreshes every 0.5 seconds that gives 20 calls/second to the server and consequently the Process Manager (assuming users only have one copy of the page open).
Whilst I'm confident that we can handle 20 calls/second by deploying with a capable application server and potentially by using asynchronous views we should check whether that sort of load on the process manager is going to be a problem for them.
If we need to reduce the number of calls to the Process Manager we could create a standalone process that polls the Process Manger and stores the results in the application database. Refresh requests from the UI then only need to hit the database rather than making a gRPC call to the Process Manager. This would reduce the polling rate of the Process Manager to around 2 /second.
A couple of tradeoffs we'd make:

calls to the Process Manager would not be directly related to a user and may require some sort of dedicated role account authenticated for this purpose.
in the event that the visibility of different processes would need to vary for different end users, this logic would need to be implemented on our server. Our current steer on this is that it wouldn't be required.

Will consider this later as part of the deployment phase of the work where we will have the opportunity to do some load testing and figure out if this is needed.

Your latter comments means that the filtering (see #94) might need to be setup without models at hand to work with, right?

For the time being we're not going to consider this. May review on the basis of deployment load testing or user feedback.

authors: cc-a dalonsoa


text:
Python V3 version

So with the latest release of Indigo, this plugin won't work with the next version of Indigo, as they won't support plugins that don't work in Python 3.
I'm not a coder, but am hoping someone will take a look at this and hopefully get it upgraded to work with Python 3.

I have downloaded the plugin and modified it to run under Python 3.
However, as I don't have a Yamaha receiver, I can't test it.
I will work out how to do a pull request to set it up as a pre-relaese for testing.
Once the Pthon 3 version is tested as OK in its current state, we can then look at enhancements.

authors: autolog jltnol

repo: IndigoDomotics/indigo-yamaharx


text:
Allow user to manage workspace

My Workspace is currently very large (~5 GB is space), so it would be nice if we could have single work space on a Build Master server instead of constantly deleting / creating temporary one.

Good idea, we will have this implemented in v4.7 (due out end of May).

Included as part of BuildMaster v4.7

authors: jrasch mcjacek

repo: Inedo/bmx-tfs


text:
[1.16.5] Mod interaction problem with Direwolf20-MC / BuildingGadgets

When this mod is loaded, Direwolf20-MC /
BuildingGadgets stops working.

I can confirm that Dungeons Libraries also interferes with Building Gadgets in 1.18.2
Expected behavior: (Only Building Gadgets installed)

What happens: (Building Gadgets, GeckoLib, Dungeons Libraries, Curios)

Building Gadgets works in creative mode but not in survival mode so it seems to be an issue with the blocks not registering as in the inventory.

Since the issue is still open, just throwing out I'm having the same issue with BG in my 1.19.2 modpack.

Since the issue is still open, just throwing out I'm having the same issue with BG in my 1.19.2 modpack.

Should be fixed with #43 in next version, but only for 1.19.2.
1.16.5 will not be receiving fixes by me, so I am closing the issue for now as "won't fix" for that version.


text:
XCCL support

Add findXCCL.cmake to find xccl lib and headers
Add AllGather AllReduce Broadcast
Support llama2 gpt2 (single / distributed)
Add launch_kunlun.py to Start distributed inference
Support test in InfiniTest
Fix bugs

通过单测，但是需要在Makefile中手动设置编译器，因为.210 昆仑server上默认gcc版本落后了

GPT2 单卡结果与onnxruntime对比

python3 launch_kunlun.py --nproc_per_node=2 --model gpt2/gpt2_bs16.onnx --batch_size 16 --length 1024
分布式结果和单卡结果对比

修改后结果无变动：

repo: InfiniTensor/InfiniTensor


text:
feat: move to dotnet 8.0.2

BREAKING CHANGE: move to dotnet 8.0.2

see #63

authors: ArneD emalfroy


text:
Bug on query bound

For single predicate x < 10 with RTree index, the IndexedRelationScan will transfer the predicate to a MBR with equality bound, which cause the x = 10 will be the final result.

Resolved, pls refer to PR #51.

repo: InitialDLab/Simba


text:
ENH: allowing filename to be specified instead of providing images

Closes #48.

Build has warnings:
In file included from /ITKMontage/test/itkMontageTestHelper.hxx:22:0,
                 from /ITKMontage/test/itkMontageTestTiles.cxx:20:
/ITKMontage/include/itkTileMontage.h: In instantiation of 'class itk::TileMontage, float>':
/ITKMontage/test/itkMontageTestHelper.hxx:102:35:   required from 'int montageTest(const PositionTableType&, const PositionTableType&, const FilenameTableType&, const string&, bool) [with PixelType = short unsigned int; unsigned int xMontageSize = 10u; unsigned int yMontageSize = 10u; PositionTableType = std::array, 10ul>, 10ul>; FilenameTableType = std::array, 10ul>, 10ul>; std::__cxx11::string = std::__cxx11::basic_string]'
/ITKMontage/test/itkMontageTestTiles.cxx:75:120:   required from here
[CTest: warning matched] /ITKMontage/include/itkTileMontage.h:40:27: warning: 'itk::TileMontage, float>' declared with greater visibility than the type of its field 'itk::TileMontage, float>::m_Reader' [-Wattributes]
 class ITK_TEMPLATE_EXPORT TileMontage: public ProcessObject
                           ^~~~~~~~~~~

ImageFileReader should be using ITK_TEMPLATE_EXPORT.

ImageFileReader should be using ITK_TEMPLATE_EXPORT -> this needs to be changed in ITK, so this PR can be merged.

authors: dzenanz thewtex

repo: InsightSoftwareConsortium/ITKMontage


text:
Update sweeps README

@cliffckerr

@hamelsmu, you have merge conflicts since the file was renamed to README.rst. Please update when you get a chance!

@lgeorge-idm done 👍

I’ll go ahead and close this PR, I’m not familiar with RST and I might have have time to touch this for about a week.  If someone is familiar with RST feel free to port these instructions

authors: hamelsmu lgeorge-idm

repo: InstituteforDiseaseModeling/covasim


text:
Final mechanic design + assembling

We've been improving the mechanical design because we've noticed some issues on our 'Utopia' design.
Jordi has printed-us the new design and tomorrow morning we will proceed with the assembling. The idea is to show some prototype in the tomorrow class.

Also to comment, we changed the idea of having as a 'wristwatch' with the electronics and all te wiring to the glove, to place the electronics in the same 3d structure (housing) but we will stick it on top of the glove, since we have opted for a long glove that covers the first arm stretch

Bugs fixed #1
The holes for passing the nuts of the screws are too small, we believe that the 3D slicer program does not compensate the size of the extruder head and therefore it comes out too small (we're talking about milimeters)

Bugs fixed 2:
After deciding that we would place the wrist case above the glove, we will use the holes of where the wrist strap would pass to screw it to the glove so, we'll update it to make upgrade it's resistance to break

Bugs fixed 3:
We created a functional design and, once assembled, we observed that the serial pin was too short so, we made a new design with a hole to let the serial plug in

Bugs fixed 4:
As the 'bugs fixed 1' our printer isn't good with the size of the holes and was too small. we made some changes to the hole to let the serial wire well pluged

Bugs fixed 5:
After a long week thinking the best way to make the pcb a simpler and more compact pcb, we turn the design around, turning the arduino nano, so we must turn the serial hole, as well as the lid wing.


text:
IGAPP-18: Extend and use rtl array from locales

Instead of extending the array I went an other route and made sure we only use set the direction for language we know which script the people use.
That means:

on Android we use what the operating system tells us
in the browser we only set the direction flag if we know whether it is rtl or not
I also removed ui direction form the state

Instead of extending the array I went an other route and made sure we only use set the direction for language we know which script the people use.
That means:
* on Android we use what the operating system tells us

* in the browser we only set the direction flag if we know whether it is rtl or not

* I also removed ui direction form the state

Why did you chose this solution? Because there are languages which have a rtl and a ltr script?
What about iOS?

Instead of extending the array I went an other route and made sure we only use set the direction for language we know which script the people use.
That means:
* on Android we use what the operating system tells us

* in the browser we only set the direction flag if we know whether it is rtl or not

* I also removed ui direction form the state

Why did you chose this solution? Because there are languages which have a rtl and a ltr script?
What about iOS?

authors: klinzo maxammann

repo: Integreat/integreat-app


text:
Build failed in test cases

Use command "mvn package -Pdist" to build trunk, see the following errors constantly,
[INFO]
[INFO] --- maven-surefire-plugin:2.20:test (default-test) @ smart-server ---
[INFO]
[INFO] -------------------------------------------------------
[INFO]  T E S T S
[INFO] -------------------------------------------------------
[INFO] Running org.smartdata.server.engine.cmdlet.TestCmdlet
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.405 s <<< FAILURE! - in org.smartdata.server.engine.cmdlet.TestCmdlet
[ERROR] testRunCmdlet(org.smartdata.server.engine.cmdlet.TestCmdlet)  Time elapsed: 1.289 s  <<< ERROR!
java.lang.NoSuchMethodError: org.apache.hadoop.util.JvmPauseMonitor: method ()V not found
at org.smartdata.server.engine.cmdlet.TestCmdlet.createCluster(TestCmdlet.java:57)
[INFO] Running org.smartdata.server.engine.rule.TestGetRuleInfo
[ERROR] Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.127 s <<< FAILURE! - in org.smartdata.server.engine.rule.TestGetRuleInfo
[ERROR] testGetSingleRuleInfo(org.smartdata.server.engine.rule.TestGetRuleInfo)  Time elapsed: 0.058 s  <<< ERROR!
java.lang.NoSuchMethodError: org.apache.hadoop.util.JvmPauseMonitor: method ()V not found
[ERROR] testMultiRules(org.smartdata.server.engine.rule.TestGetRuleInfo)  Time elapsed: 0.058 s  <<< ERROR!
java.lang.NoSuchMethodError: org.apache.hadoop.util.JvmPauseMonitor: method ()V not found
[INFO] Running org.smartdata.server.engine.rule.TestRuleManager
[INFO] Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 41.565 s - in org.smartdata.server.engine.rule.TestRuleManager
[INFO] Running org.smartdata.server.engine.rule.TestSubmitRule
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.036 s <<< FAILURE! - in org.smartdata.server.engine.rule.TestSubmitRule
[ERROR] testSubmitRule(org.smartdata.server.engine.rule.TestSubmitRule)  Time elapsed: 0.036 s  <<< ERROR!
java.lang.NoSuchMethodError: org.apache.hadoop.util.JvmPauseMonitor: method ()V not found
[INFO] Running org.smartdata.server.engine.TestCmdletManager
[ERROR] Tests run: 6, Failures: 0, Errors: 6, Skipped: 0, Time elapsed: 0.219 s <<< FAILURE! - in org.smartdata.server.engine.TestCmdletManager
[ERROR] testGetListDeleteCmdlet(org.smartdata.server.engine.TestCmdletManager)  Time elapsed: 0.035 s  <<< ERROR!
java.lang.NoSuchMethodError: org.apache.hadoop.util.JvmPauseMonitor: method ()V not found
[ERROR] testCreateFromDescriptor(org.smartdata.server.engine.TestCmdletManager)  Time elapsed: 0.055 s  <<< ERROR!
java.lang.NoSuchMethodError: org.apache.hadoop.util.JvmPauseMonitor: method ()V not found
[ERROR] testAPI(org.smartdata.server.engine.TestCmdletManager)  Time elapsed: 0.033 s  <<< ERROR!
java.lang.NoSuchMethodError: org.apache.hadoop.util.JvmPauseMonitor: method ()V not found
[ERROR] wrongCmdlet(org.smartdata.server.engine.TestCmdletManager)  Time elapsed: 0.033 s  <<< ERROR!
java.lang.NoSuchMethodError: org.apache.hadoop.util.JvmPauseMonitor: method ()V not found
[ERROR] testWithoutCluster(org.smartdata.server.engine.TestCmdletManager)  Time elapsed: 0.03 s  <<< ERROR!
java.lang.NoSuchMethodError: org.apache.hadoop.util.JvmPauseMonitor: method ()V not found
[ERROR] testFileLock(org.smartdata.server.engine.TestCmdletManager)  Time elapsed: 0.029 s  <<< ERROR!
java.lang.NoSuchMethodError: org.apache.hadoop.util.JvmPauseMonitor: method ()V not found
[INFO] Running org.smartdata.server.TestSmartAdmin
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.028 s <<< FAILURE! - in org.smartdata.server.TestSmartAdmin
[ERROR] test(org.smartdata.server.TestSmartAdmin)  Time elapsed: 0.028 s  <<< ERROR!
java.lang.NoSuchMethodError: org.apache.hadoop.util.JvmPauseMonitor: method ()V not found
[INFO] Running org.smartdata.server.TestSmartServer
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.079 s <<< FAILURE! - in org.smartdata.server.TestSmartServer
[ERROR] test(org.smartdata.server.TestSmartServer)  Time elapsed: 1.079 s  <<< ERROR!
java.net.BindException: Problem binding to [0.0.0.0:7042] java.net.BindException: Address already in use; For more details see:  http://wiki.apache.org/hadoop/BindException
at org.smartdata.server.TestSmartServer.setUp(TestSmartServer.java:53)
Caused by: java.net.BindException: Address already in use
at org.smartdata.server.TestSmartServer.setUp(TestSmartServer.java:53)
[INFO] Running org.smartdata.server.TestSmartServerCli
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.028 s <<< FAILURE! - in org.smartdata.server.TestSmartServerCli
[ERROR] testConfNameNodeRPCAddr(org.smartdata.server.TestSmartServerCli)  Time elapsed: 0.028 s  <<< ERROR!
java.lang.NoSuchMethodError: org.apache.hadoop.util.JvmPauseMonitor: method ()V not found
at org.smartdata.server.TestSmartServerCli.testConfNameNodeRPCAddr(TestSmartServerCli.java:40)
[INFO] Running org.smartdata.server.TestSmartServerLogin
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.213 s <<< FAILURE! - in org.smartdata.server.TestSmartServerLogin
[ERROR] loginSmartServerUsingKeytab(org.smartdata.server.TestSmartServerLogin)  Time elapsed: 0.211 s  <<< ERROR!
java.lang.NoSuchMethodError: org.apache.hadoop.util.JvmPauseMonitor: method ()V not found
at org.smartdata.server.TestSmartServerLogin.initConf(TestSmartServerLogin.java:54)
at org.smartdata.server.TestSmartServerLogin.loginSmartServerUsingKeytab(TestSmartServerLogin.java:84)
[INFO] Running org.smartdata.server.TestSmartServerReConfig
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.051 s <<< FAILURE! - in org.smartdata.server.TestSmartServerReConfig
[ERROR] setUp(org.smartdata.server.TestSmartServerReConfig)  Time elapsed: 0.051 s  <<< ERROR!
java.lang.NoSuchMethodError: org.apache.hadoop.util.JvmPauseMonitor: method ()V not found
at org.smartdata.server.TestSmartServerReConfig.setUp(TestSmartServerReConfig.java:54)
[INFO] Running org.smartdata.server.tools.TestSmartShell
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.02 s - in org.smartdata.server.tools.TestSmartShell
[INFO] Running org.smartdata.server.tools.TestSubmitRuleThroughCli
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.042 s <<< FAILURE! - in org.smartdata.server.tools.TestSubmitRuleThroughCli
[ERROR] test(org.smartdata.server.tools.TestSubmitRuleThroughCli)  Time elapsed: 0.042 s  <<< ERROR!
java.lang.NoSuchMethodError: org.apache.hadoop.util.JvmPauseMonitor: method ()V not found
[INFO] Running org.smartdata.server.util.TestJsonUtil
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.075 s - in org.smartdata.server.util.TestJsonUtil
[INFO]
[INFO] Results:
[INFO]

Can someone look into this issue?  The unit test fails every time. If we cannot fix it because of some reason, please comments them out, so the remaining unit test can got the change to run.

Can you try mvn install package -Pdist?

With latest source code, the unit test failed at Zeppelin server module which has no problem previously on Mac.
Zeppelin: Server ................................... FAILURE [01:00 min]
org.openqa.selenium.firefox.NotConnectedException: Unable to connect to host 127.0.0.1 on port 7055 after 45000 ms. Firefox console output:
":false,"hasBinaryComponents":false,"strictCompatibility":true,"locales":[],"targetApplications":[{"id":"{ec8030f7-c20a-464f-9b0e-13a3a9e97384}","minVersion":"53.0","maxVersion":"53.0"}],"targetPlatforms":[],"seen":true,"dependencies":[],"hasEmbeddedWebExtension":false,"userPermissions":null}
1499926153976	addons.xpi	DEBUG	getModTime: Recursive scan of {972ce4c6-7e08-4474-a285-3208198ce6fd}
1499926153977	DeferredSave.extensions.json	DEBUG	Save changes
1499926153977	addons.xpi	DEBUG	Updating database with changes to installed add-ons
1499926153977	addons.xpi-utils	DEBUG	Updating add-on states
1499926153978	addons.xpi-utils	DEBUG	Writing add-ons list
1499926153979	addons.xpi	DEBUG	Registering manifest for /Applications/Firefox.app/Contents/Resources/browser/features/aushelper@mozilla.org.xpi
1499926153979	addons.xpi	DEBUG	Calling bootstrap method startup on aushelper@mozilla.org version 2.0
1499926153980	addons.xpi	DEBUG	Registering manifest for /Applications/Firefox.app/Contents/Resources/browser/features/e10srollout@mozilla.org.xpi
1499926153980	addons.xpi	DEBUG	Calling bootstrap method startup on e10srollout@mozilla.org version 1.14
1499926153981	addons.xpi	DEBUG	Registering manifest for /Applications/Firefox.app/Contents/Resources/browser/features/firefox@getpocket.com.xpi
1499926153981	addons.xpi	DEBUG	Calling bootstrap method startup on firefox@getpocket.com version 1.0.5
1499926153982	addons.xpi	DEBUG	Registering manifest for /Applications/Firefox.app/Contents/Resources/browser/features/webcompat@mozilla.org.xpi
1499926153982	addons.xpi	DEBUG	Calling bootstrap method startup on webcompat@mozilla.org version 1.0
1499926153984	addons.manager	DEBUG	Registering shutdown blocker for XPIProvider
1499926153984	addons.manager	DEBUG	Provider finished startup: XPIProvider
1499926153985	addons.manager	DEBUG	Starting provider: LightweightThemeManager
1499926153985	addons.manager	DEBUG	Registering shutdown blocker for LightweightThemeManager
1499926153985	addons.manager	DEBUG	Provider finished startup: LightweightThemeManager
1499926153986	addons.manager	DEBUG	Starting provider: GMPProvider
1499926153989	addons.manager	DEBUG	Registering shutdown blocker for GMPProvider
1499926153989	addons.manager	DEBUG	Provider finished startup: GMPProvider
1499926153989	addons.manager	DEBUG	Starting provider: PluginProvider
1499926153989	addons.manager	DEBUG	Registering shutdown blocker for PluginProvider
1499926153990	addons.manager	DEBUG	Provider finished startup: PluginProvider
1499926153990	addons.manager	DEBUG	Completed startup sequence
1499926154280	addons.manager	DEBUG	Starting provider:
1499926154280	addons.manager	DEBUG	Registering shutdown blocker for
1499926154281	addons.manager	DEBUG	Provider finished startup:
1499926154285	DeferredSave.extensions.json	DEBUG	Starting write
1499926154374	addons.repository	DEBUG	No addons.json found.
1499926154375	DeferredSave.addons.json	DEBUG	Save changes
1499926154379	DeferredSave.addons.json	DEBUG	Starting timer
1499926154400	addons.manager	DEBUG	Starting provider: PreviousExperimentProvider
1499926154400	addons.manager	DEBUG	Registering shutdown blocker for PreviousExperimentProvider
1499926154401	addons.manager	DEBUG	Provider finished startup: PreviousExperimentProvider
1499926154423	DeferredSave.extensions.json	DEBUG	Write succeeded
1499926154424	addons.xpi-utils	DEBUG	XPI Database saved, setting schema version preference to 19
1499926154434	DeferredSave.addons.json	DEBUG	Starting write
1499926154452	DeferredSave.addons.json	DEBUG	Write succeeded
2017-07-12 23:09:15.603 plugin-container[30915:830247] *** CFMessagePort: bootstrap_register(): failed 1100 (0x44c) 'Permission denied', port = 0x983b, name = 'com.apple.tsm.portname'
See /usr/include/servers/bootstrap_defs.h for the error codes.
2017-07-12 23:09:15.605 plugin-container[30915:830247] *** CFMessagePort: bootstrap_register(): failed 1100 (0x44c) 'Permission denied', port = 0x9b03, name = 'com.apple.CFPasteboardClient'
See /usr/include/servers/bootstrap_defs.h for the error codes.
at org.openqa.selenium.firefox.internal.NewProfileExtensionConnection.start(NewProfileExtensionConnection.java:123)
at org.openqa.selenium.firefox.FirefoxDriver.startClient(FirefoxDriver.java:271)
at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:117)
at org.openqa.selenium.firefox.FirefoxDriver.<init>(FirefoxDriver.java:216)
at org.openqa.selenium.firefox.FirefoxDriver.<init>(FirefoxDriver.java:211)
at org.openqa.selenium.firefox.FirefoxDriver.<init>(FirefoxDriver.java:207)
at org.apache.zeppelin.AbstractFunctionalSuite.firefox(AbstractFunctionalSuite.scala:82)
at org.apache.zeppelin.AbstractFunctionalSuite$$anonfun$3.apply(AbstractFunctionalSuite.scala:60)
at org.apache.zeppelin.AbstractFunctionalSuite$$anonfun$3.apply(AbstractFunctionalSuite.scala:60)
at scala.util.Try$.apply(Try.scala:192)
at org.apache.zeppelin.AbstractFunctionalSuite$$anonfun$4.apply(AbstractFunctionalSuite.scala:61)
at org.apache.zeppelin.AbstractFunctionalSuite$$anonfun$4.apply(AbstractFunctionalSuite.scala:61)
at scala.collection.immutable.List.map(List.scala:277)
at org.apache.zeppelin.AbstractFunctionalSuite.getDriver(AbstractFunctionalSuite.scala:61)
at org.apache.zeppelin.AbstractFunctionalSuite.<init>(AbstractFunctionalSuite.scala:39)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
at java.lang.Class.newInstance(Class.java:383)
at org.scalatest.tools.DiscoverySuite$.getSuiteInstance(DiscoverySuite.scala:69)
at org.scalatest.tools.DiscoverySuite$$anonfun$1.apply(DiscoverySuite.scala:38)
at org.scalatest.tools.DiscoverySuite$$anonfun$1.apply(DiscoverySuite.scala:37)
at scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:234)
at scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:234)
at scala.collection.Iterator$class.foreach(Iterator.scala:893)
at scala.collection.AbstractIterator.foreach(Iterator.scala:1336)
at scala.collection.IterableLike$class.foreach(IterableLike.scala:72)
at scala.collection.AbstractIterable.foreach(Iterable.scala:54)
at scala.collection.TraversableLike$class.map(TraversableLike.scala:234)
at scala.collection.AbstractTraversable.map(Traversable.scala:104)
at org.scalatest.tools.DiscoverySuite.<init>(DiscoverySuite.scala:37)
at org.scalatest.tools.Runner$.genDiscoSuites$1(Runner.scala:2390)
at org.scalatest.tools.Runner$.doRunRunRunDaDoRunRun(Runner.scala:2475)
at org.scalatest.tools.Runner$$anonfun$runOptionallyWithPassFailReporter$2.apply(Runner.scala:1044)
at org.scalatest.tools.Runner$$anonfun$runOptionallyWithPassFailReporter$2.apply(Runner.scala:1043)
at org.scalatest.tools.Runner$.withClassLoaderAndDispatchReporter(Runner.scala:2722)
at org.scalatest.tools.Runner$.runOptionallyWithPassFailReporter(Runner.scala:1043)
at org.scalatest.tools.Runner$.main(Runner.scala:860)
at org.scalatest.tools.Runner.main(Runner.scala)

*** RUN ABORTED ***
java.lang.RuntimeException: Unable to load a Suite class that was discovered in the runpath: org.apache.zeppelin.AbstractFunctionalSuite
at org.scalatest.tools.DiscoverySuite$.getSuiteInstance(DiscoverySuite.scala:84)
at org.scalatest.tools.DiscoverySuite$$anonfun$1.apply(DiscoverySuite.scala:38)
at org.scalatest.tools.DiscoverySuite$$anonfun$1.apply(DiscoverySuite.scala:37)
at scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:234)
at scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:234)
at scala.collection.Iterator$class.foreach(Iterator.scala:893)
at scala.collection.AbstractIterator.foreach(Iterator.scala:1336)
at scala.collection.IterableLike$class.foreach(IterableLike.scala:72)
at scala.collection.AbstractIterable.foreach(Iterable.scala:54)
at scala.collection.TraversableLike$class.map(TraversableLike.scala:234)
...
Cause: java.lang.RuntimeException: Could not initialize any driver
at org.apache.zeppelin.AbstractFunctionalSuite.getDriver(AbstractFunctionalSuite.scala:64)
at org.apache.zeppelin.AbstractFunctionalSuite.(AbstractFunctionalSuite.scala:39)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
at java.lang.Class.newInstance(Class.java:383)
at org.scalatest.tools.DiscoverySuite$.getSuiteInstance(DiscoverySuite.scala:69)
at org.scalatest.tools.DiscoverySuite$$anonfun$1.apply(DiscoverySuite.scala:38)
at org.scalatest.tools.DiscoverySuite$$anonfun$1.apply(DiscoverySuite.scala:37)
...

I also met with this problem. Currently all the tests passed on travis. So if you want to verify your code change, you can submit a pull request to see whether all the tests passed.

authors: ChenSammi huafengw

repo: Intel-bigdata/SSM


text:
Add CommandRPC support

submitCommand for command submit.
getCommandInfo for getting commandinfo with given commandID.
listCommandinfs for getting all commands executing.
activateCommand for activating(insert it to queue) an given command.
deleteCommand for delete a command from queue, if this command is running, then kill it.

@littlezhou Please check if these API satisfy our Demo.


text:
Black color image in current Master

Hi
With the current software on the master branch, I received all black color images. This is both using the Realsense viewer and my custom c++ script. And both using camera firmware 5.10.3 and 5.9.
Edit: I am running Ubuntu 16.04, and using the D415.
Can someone please fix this?

[Realsense Customer Engineering Team Comment]
Hi @BGA3,
Which platform/board do you use? What's your librealsense version?
I previously saw the similar issue on Odroid XU4 board.

Hi,
I am working on a Firefly roc-rk3328-cc board running Ubuntu 16.04. The librealsense version is the current master.

Yes, we are working on it - #2306
The issue is limited to non-Intel boards

Thank you!
Should be resolved in 2.16.1

Thanks for the support. It seems to be fixed, at least it works on my setup.

repo: IntelRealSense/librealsense


text:
overdue a lot after using 2 d435 for a  long time on Android

Before opening a new issue, we wanted to provide you with some useful suggestions (Click "Preview" above for a better view):

Consider checking out SDK examples.
Have you looked in our documentations?
Is you question a frequently asked one?
Try searching our GitHub Issues (open and closed) for a similar issue.

All users are welcomed to report bugs, ask questions, suggest or request enhancements and generally feel free to open new issue, even if they haven't followed any of the suggestions above :)

Required Info

Camera Model
D435

Firmware Version
05.11.01.100

Operating System & Version
Android

Kernel Version (Linux Only)

Platform
RK3399

SDK Version
2.18.1

Language
c++

Segment
Robot

Issue Description###
<Describe your issue / question / feature request / etc..>
Hi. Our team using 2 d435 on RK3399.
1.We build librealsense2.so from Android Studios.
2.And use it in a binary(name: RGBD_Server) which only  get the streams from the  2 RGBD and send out through socket.
3.adb connect to the RK3399. Push the binary and the libs to it. And run the binary through cmd.
./RGBD_Server
Configs of 2 d435:
W  x  H     = 848 x 480
fps            = 15
preset       = HIGH_ACCURACY
streams    = depth   &    left IR

TEST:
At first 2 RGBD works fine. But we notice that after about 4 hours(more or less),  one of the RGBD become very unstable.
So we change the log level to DEBUG and open the Android kernal log test it again.
RESULT:
kernal log:  libuvc show no ERROR
librealsense log:

From the first frame,  every frame will come out a " overdue " log.
Repeat receiving frame 0 of every stream. And will come with a overdue log.
the frequency will be very high!
3.After about 6 hours, one of the RGBD becomes unstable. And soon(maybe about 10 mins later) even lsusb cant find it.

the following logs contains the 3 phenomenon above.
23/05 11:49:53,527 DEBUG [516574672112] (F:\Code\third_part\realsense-app\app\src\main\cpp\librealsense\src\sync.cpp:516) fps 15 Infrared 109482 3012241.778000 Depth 109482 3012241.778000
23/05 11:49:53,527 DEBUG [516574672112] (F:\Code\third_part\realsense-app\app\src\main\cpp\librealsense\src\sync.cpp:529) (TS: )Infrared 109482 3012241.778000 Depth 109482 3012241.778000 fps 15 gap 66.666664 next_expected: 3012308.444664
23/05 11:49:53,527 DEBUG [516574672112] (F:\Code\third_part\realsense-app\app\src\main\cpp\librealsense\src\archive.cpp:288) CallbackFinished,Infrared,0,DispatchedAt,1558612193527.291016
23/05 11:49:53,527 DEBUG [516574672112] (F:\Code\third_part\realsense-app\app\src\main\cpp\librealsense\src\archive.cpp:295) Frame Callback [Infrared#0] overdue. (Duration: 1558612193527.291016ms, FPS: 15, Max Duration: 62ms)
23/05 11:49:53,527 DEBUG [516574672112] (F:\Code\third_part\realsense-app\app\src\main\cpp\librealsense\src\proc\syncer-processing-block.cpp:28) SYNCED: Infrared 109482, 3012241.778000 Depth 109482, 3012241.778000
23/05 11:49:53,527 DEBUG [516574672112] (F:\Code\third_part\realsense-app\app\src\main\cpp\librealsense\src\archive.cpp:502) CallbackStarted,Infrared,109482,DispatchedAt,1558612193527.592041
23/05 11:49:53,527 DEBUG [516574672112] (F:\Code\third_part\realsense-app\app\src\main\cpp\librealsense\src\archive.cpp:288) CallbackFinished,Infrared,109481,DispatchedAt,1558612193527.679932
23/05 11:49:53,527 DEBUG [516574672112] (F:\Code\third_part\realsense-app\app\src\main\cpp\librealsense\src\archive.cpp:295) Frame Callback [Infrared#109481] overdue. (Duration: 77.159912ms, FPS: 15, Max Duration: 62ms)
23/05 11:49:53,527 DEBUG [516574672112] (F:\Code\third_part\realsense-app\app\src\main\cpp\librealsense\src\archive.cpp:288) CallbackFinished,Depth,109481,DispatchedAt,1558612193527.866943
23/05 11:49:53,527 DEBUG [516574672112] (F:\Code\third_part\realsense-app\app\src\main\cpp\librealsense\src\archive.cpp:295) Frame Callback [Depth#109481] overdue. (Duration: 69.266846ms, FPS: 15, Max Duration: 62ms)
23/05 11:49:53,528 DEBUG [516574672112] (F:\Code\third_part\realsense-app\app\src\main\cpp\librealsense\src\archive.cpp:502) CallbackStarted,Depth,109482,DispatchedAt,1558612193528.048096
23/05 11:49:53,528 DEBUG [516574672112] (F:\Code\third_part\realsense-app\app\src\main\cpp\librealsense\src\archive.cpp:288) CallbackFinished,Depth,0,DispatchedAt,1558612193528.102051
23/05 11:49:53,529 DEBUG [516574672112] (F:\Code\third_part\realsense-app\app\src\main\cpp\librealsense\src\archive.cpp:288) CallbackFinished,Infrared,0,DispatchedAt,1558612193528.159912
23/05 11:49:53,533 DEBUG [516695270640] (F:\Code\third_part\realsense-app\app\src\main\cpp\librealsense\src\sensor.cpp:453) FrameAccepted,Depth,Counter,0,Index,0,BackEndTS,0.000000,SystemTime,1558612193533.135010 ,diff_ts[Sys-BE],1558612193533.135010,TS,3021743.526000,TS_Domain,Hardware Clock,last_frame_number,0,last_timestamp,0.000000
23/05 11:49:53,536 DEBUG [516695270640] (F:\Code\third_part\realsense-app\app\src\main\cpp\librealsense\src\archive.cpp:502) CallbackStarted,Depth,0,DispatchedAt,1558612193536.345947
23/05 11:49:53,537 DEBUG [516695270640] (F:\Code\third_part\realsense-app\app\src\main\cpp\librealsense\src\sync.cpp:143) DISPATCH (TS: )--> Depth 0 3021743.526000
23/05 11:49:53,537 DEBUG [516695270640] (F:\Code\third_part\realsense-app\app\src\main\cpp\librealsense\src\sync.cpp:551) clean inactive stream in (TS: )Depth Infrared Infrared Color
23/05 11:49:53,537 DEBUG [516695270640] (F:\Code\third_part\realsense-app\app\src\main\cpp\librealsense\src\sync.cpp:551) clean inactive stream in (TS: )Depth Infrared Infrared Color
23/05 11:49:53,537 DEBUG [516695270640] (F:\Code\third_part\realsense-app\app\src\main\cpp\librealsense\src\sync.cpp:551) clean inactive stream in (TS: )Depth Infrared Infrared Color
23/05 11:49:53,537 DEBUG [516695270640] (F:\Code\third_part\realsense-app\app\src\main\cpp\librealsense\src\sync.cpp:551) clean inactive stream in (TS: )Depth Infrared Infrared Color
23/05 11:49:53,538 DEBUG [516695270640] (F:\Code\third_part\realsense-app\app\src\main\cpp\librealsense\src\sync.cpp:143) DISPATCH (TS: (FN: I Depth I Infrared I Infrared ) I Color )--> Depth 0 3021743.526000
23/05 11:49:53,538 DEBUG [516695270640] (F:\Code\third_part\realsense-app\app\src\main\cpp\librealsense\src\sync.cpp:551) clean inactive stream in (TS: (FN: I Depth I Infrared I Infrared ) I Color )Depth Infrared Infrared
23/05 11:49:53,538 DEBUG [516695270640] (F:\Code\third_part\realsense-app\app\src\main\cpp\librealsense\src\sync.cpp:551) clean inactive stream in (TS: (FN: I Depth I Infrared I Infrared ) I Color )Depth Infrared Infrared
23/05 11:49:53,538 DEBUG [516695270640] (F:\Code\third_part\realsense-app\app\src\main\cpp\librealsense\src\sync.cpp:551) clean inactive stream in (TS: (FN: I Depth I Infrared I Infrared ) I Color )Depth Infrared Infrared
23/05 11:49:53,538 DEBUG [516695270640] (F:\Code\third_part\realsense-app\app\src\main\cpp\librealsense\src\sync.cpp:143) DISPATCH (FN: I Depth I Infrared I Infrared )--> Depth 0 3021743.526000
23/05 11:49:53,538 DEBUG [516695270640] (F:\Code\third_part\realsense-app\app\src\main\cpp\librealsense\src\sync.cpp:422) clean inactive stream in (FN: I Depth I Infrared I Infrared )Depth
23/05 11:49:53,538 DEBUG [516695270640] (F:\Code\third_part\realsense-app\app\src\main\cpp\librealsense\src\sync.cpp:422) clean inactive stream in (FN: I Depth I Infrared I Infrared )Infrared
23/05 11:49:53,539 DEBUG [516695270640] (F:\Code\third_part\realsense-app\app\src\main\cpp\librealsense\src\archive.cpp:288) CallbackFinished,Depth,109575,DispatchedAt,1558612193539.012939
23/05 11:49:53,539 DEBUG [516695270640] (F:\Code\third_part\realsense-app\app\src\main\cpp\librealsense\src\archive.cpp:295) Frame Callback [Depth#109575] overdue. (Duration: 2885.302002ms, FPS: 15, Max Duration: 62ms)
23/05 11:49:53,539 DEBUG [516695270640] (F:\Code\third_part\realsense-app\app\src\main\cpp\librealsense\src\archive.cpp:288) CallbackFinished,Depth,109575,DispatchedAt,1558612193539.459961
23/05 11:49:53,539 DEBUG [516695270640] (F:\Code\third_part\realsense-app\app\src\main\cpp\librealsense\src\archive.cpp:295) Frame Callback [Depth#109575] overdue. (Duration: 2819.269043ms, FPS: 15, Max Duration: 62ms)
23/05 11:49:53,539 DEBUG [516695270640] (F:\Code\third_part\realsense-app\app\src\main\cpp\librealsense\src\archive.cpp:288) CallbackFinished,Depth,109575,DispatchedAt,1558612193539.768066
23/05 11:49:53,539 DEBUG [516695270640] (F:\Code\third_part\realsense-app\app\src\main\cpp\librealsense\src\archive.cpp:295) Frame Callback [Depth#109575] overdue. (Duration: 2752.756104ms, FPS: 15, Max Duration: 62ms)
23/05 11:49:53,540 DEBUG [516695270640] (F:\Code\third_part\realsense-app\app\src\main\cpp\librealsense\src\archive.cpp:288) CallbackFinished,Depth,109575,DispatchedAt,1558612193540.008057
23/05 11:49:53,540 DEBUG [516695270640] (F:\Code\third_part\realsense-app\app\src\main\cpp\librealsense\src\archive.cpp:295) Frame Callback [Depth#109575] overdue. (Duration: 2686.362061ms, FPS: 15, Max Duration: 62ms)
23/05 11:49:53,540 DEBUG [516695270640] (F:\Code\third_part\realsense-app\app\src\main\cpp\librealsense\src\archive.cpp:288) CallbackFinished,Depth,109575,DispatchedAt,1558612193540.247070
23/05 11:49:53,540 DEBUG [516695270640] (F:\Code\third_part\realsense-app\app\src\main\cpp\librealsense\src\archive.cpp:295) Frame Callback [Depth#109575] overdue. (Duration: 2618.258057ms, FPS: 15, Max Duration: 62ms)
23/05 11:49:53,540 DEBUG [516695270640] (F:\Code\third_part\realsense-app\app\src\main\cpp\librealsense\src\archive.cpp:288) CallbackFinished,Depth,109575,DispatchedAt,1558612193540.547119
23/05 11:49:53,540 DEBUG [516695270640] (F:\Code\third_part\realsense-app\app\src\main\cpp\librealsense\src\archive.cpp:295) Frame Callback [Depth#109575] overdue. (Duration: 2552.906006ms, FPS: 15, Max Duration: 62ms)
23/05 11:49:53,541 DEBUG [516695270640] (F:\Code\third_part\realsense-app\app\src\main\cpp\librealsense\src\archive.cpp:288) CallbackFinished,Depth,109575,DispatchedAt,1558612193540.950928
23/05 11:49:53,541 DEBUG [516695270640] (F:\Code\third_part\realsense-app\app\src\main\cpp\librealsense\src\archive.cpp:295) Frame Callback [Depth#109575] overdue. (Duration: 2486.604004ms, FPS: 15, Max Duration: 62ms)
23/05 11:49:53,541 DEBUG [516695270640] (F:\Code\third_part\realsense-app\app\src\main\cpp\librealsense\src\archive.cpp:288) CallbackFinished,Depth,109575,DispatchedAt,1558612193541.164062
23/05 11:49:53,541 DEBUG [516695270640] (F:\Code\third_part\realsense-app\app\src\main\cpp\librealsense\src\archive.cpp:295) Frame Callback [Depth#109575] overdue. (Duration: 2420.248047ms, FPS: 15, Max Duration: 62ms)
23/05 11:49:53,541 DEBUG [516695270640] (F:\Code\third_part\realsense-app\app\src\main\cpp\librealsense\src\archive.cpp:288) CallbackFinished,Depth,109575,DispatchedAt,1558612193541.375000
23/05 11:49:53,541 DEBUG [516695270640] (F:\Code\third_part\realsense-app\app\src\main\cpp\librealsense\src\archive.cpp:295) Frame Callback [Depth#109575] overdue. (Duration: 2353.334961ms, FPS: 15, Max Duration: 62ms)
23/05 11:49:53,541 DEBUG [516695270640] (F:\Code\third_part\realsense-app\app\src\main\cpp\librealsense\src\archive.cpp:288) CallbackFinished,Depth,109575,DispatchedAt,1558612193541.733887
23/05 11:49:53,541 DEBUG [516695270640] (F:\Code\third_part\realsense-app\app\src\main\cpp\librealsense\src\archive.cpp:295) Frame Callback [Depth#109575] overdue. (Duration: 2286.659912ms, FPS: 15, Max Duration: 62ms)
23/05 11:49:53,542 DEBUG [516695270640] (F:\Code\third_part\realsense-app\app\src\main\cpp\librealsense\src\sync.cpp:99) I Depth--> Depth 0, 3021743.526000
23/05 11:49:53,542 DEBUG [516695270640] (F:\Code\third_part\realsense-app\app\src\main\cpp\librealsense\src\sync.cpp:258) SYNC (FN: I Depth I Infrared I Infrared )--> Depth 0 3021743.526000

Please let me know if there's anything I can try to make this work.
Thanks in advance.

we update the librealsense sdk to 2.22.0.
It really increase the rate of success of opening the RGBD at first time.
But the unstable phenomenon is still showing.
1.Still can't see much different from the kernal log.
2.One strange thing is that after the freq of the frame become unstable.
The ls /dev/video only show video0 & video1
which the right result shoule be 6 videos.
Than we kill the process with out pulling out USB.
And we restart the programe. The programe can still run ! All stream are working fine.
The ls /dev/video still only show video0 & video1

Hi @guokiddo1
Are you using the android solution for unrooted devices
or the previous solution?
I have a possible solution for the frequency issue that seems to improve it- #4032 (more tests are required)
As for the USB disconnect, I also see this issue on my RK3399 setup and I steel don't have a root-cause/ solution for that.

We do a lot of work to fix this.
Here are some result.
1.we open the devices not from Java(Android) but from JNI. We use libuvc to open the D435.
So I afaird the #4032 cant solve our problem.
2. Now time, the biggest problem is that the D435 may suddenly send no data randomly after 1~5hours.
First we dont know whether this is the hardware problem or software problem or sdk problem.
We print logs from Apk, SDK, BUS, kernel and we locate the bug.
We use tcpdump to get all the USB BUS data when running the process.
And when the bug shows, the devices return NULL!

We are pretty sure the hardware is still connected.
the lsusb result is correct  and  we use API:     dev.hardware_reset() the devices can re-open.
But the problem is that if everytime we use hardware_reset(), it will cost about 30s to open 2 RGBD.
It could be fix only by reset one of the error endpoints. And could cost less time.(Just like#4032 do)
Now we are trying to fix the problem by logging the transfer->status from libuvc/stream.cpp first.
Check if libuvc could recognize the error-endpoint.
Than we will try to only reset the error endpoints through libuvc.
Do you have any more advices for this ?

By the way， we are using sdk 2.23.0 now.

We add logs (print transfer->status) in src/libuvc/stream.cpp when get  _uvc_stream_callback
When one rgbd return nothing
the log shows:
21/06 07:20:12,779 DEBUG [535557055728] (stream.cpp:836) uvc_stream_callback; status: 1
status:1 refer LIBUSB_TRANSFER_ERROR
so we check src/libuvc/stream.cpp _uvc_stream_callback
the origion code like this:
  case LIBUSB_TRANSFER_ERROR:
    UVC_DEBUG("retrying transfer, status = %d", transfer->status);
    break;   }
when get LIBUSB_TRANSFER_ERROR; the origin code will do notiong.
We will try libusb_clear_halt to reset the end-point
  case LIBUSB_TRANSFER_ERROR:
    libusb_clear_halt
    UVC_DEBUG("retrying transfer, status = %d", transfer->status);
    break;   }

Reset the endpoint (clear halt) might do the work.
Currently, on the usbhost backend, I'm resting the end point in two cases, overflow error and protocol error.
I didn't see transfer error yet but I'm not sure if libusb and usbhost are completely aligned.

@guokiddo1  Any luck with libusb_clear_halt?

for our new binary version.

we add "libusb_clear_halt" when recieve LIBUSB_TRANSFER_ERROR

for SDK build config:
BUILD_WITH_OPENMP = false
CMAKE_BUILD_TYPE = Release
ENABLE_ZERO_COPY = true
to reduce the CPU utilization

And some very strange things happends.
After open D435 3~5 hours. The USB 3.0 host of  RK3399 is halt !!
All the devices connect to USB 3.0 disappear.(  we see from  lsusb)
We found this on several RK3399.
We are not sure it is a bug of D435 or SDK or our RK3399.
But we guess maybe it is a bug of SDK because the bug shows very high frequency
only after we update the SDK .
But it's also hard to imagine how a USB devices would crash the USB host.

So we are now very conflusing about our next step and
could only try some solution to locate the bug more accurately.

I also see this issue on my FIreFly boards  (3399 and 3328)  with the solution for un-rooted devices.
This issue was reproduced also on earlier versions of librealsense.
Configure more streams at higher resolutions accelerates the reproduction.
For example with [depth 1280x720x30 | color 1280x720x30] I was able to run more than 10 hours with no issues (until I needed to stop the test), while configuring [depth 1280x720x30 | color 1920x1080x30 | IR1 1280x720x30 | IR2 1280x720x30] ran for less than a minute before the device was disconnected.
When checking the dmesg log this is what is get:
[  116.651896] xhci-hcd xhci-hcd.12.auto: xHCI host not responding to stop endpoint command.
[  116.651921] xhci-hcd xhci-hcd.12.auto: Assuming host is dying, halting host.
[  116.665990] usb 4-1: usbfs: USBDEVFS_CONTROL failed cmd ealsense.camera rqt 33 rq 1 len 1024 ret -110
[  116.666922] xhci-hcd xhci-hcd.12.auto: HC died; cleaning up
[  116.670018] usb 4-1: USB disconnect, device number 2
I was not able to reproduce it on pixel 2 or Samsung S8.
Will update once I have any progress with this problem.

We run it as root devices
and use SDK 2.23.0

Tracked by DSO-13154. No progress yet.


text:
Not able to play rosbag with ros command

librealsense
2.22.0 RELEASE

OS
Linux

Name
Intel RealSense D435

Serial Number
745412070314

Firmware Version
05.10.03.00

Advanced Mode
YES

Usb Type Descriptor
3.2

Hi,
Want to record data from real sense and generate a video file for further processing. I am able to save the recording in the bag format and play it back with the realsense viewer, but when I try to play it with the command rosbag play  I get the below error -
[ INFO] [1561133313.635821050]: Opening 20190621_170754.bag
[FATAL] [1561133313.653045811]: Character [ ] at element [32] is not valid in Graph Resource Name [/device_0/sensor_0/option/Enable Auto Exposure/value].  Valid characters are a-z, A-Z, 0-9, / and _.
How can I reslove this, I want to extract video from the RGB camera (at the cameras resloution).

realsense-ros node has a parameter that would play SDK .bag file.

@ShettyHarapanahalli Did you get it through? Looking forward to your update. Thanks!

The problem is related to the fact that, as shown in the error, some of the topics include the space character, which is not allowed in a topic name. I did not check the code in librealsense, however, a quick workaround using ROS is just to use the filter tool in rosbag to get only the images (here more information http://wiki.ros.org/rosbag/Commandline#rosbag_filter). For example, to get the IMU data and the image data (properly replacing the elements in <>):
rosbag filter <input.bag> <output.bag> "topic == '/device_<device_id>/sensor_<sensor_id>/<stream_type>_<stream_id>/imu/data' or topic == '/device_<device_id>/sensor_<sensor_id>/<stream_type>_<stream_id>/image/data'"

@quattrinili Thanks for the good point!  @ShettyHarapanahalli  Could you please have a try with quattrinili's workaround? Thanks!

I used the python wrapper, the example below helped me do the job for me -
https://github.com/IntelRealSense/librealsense/blob/master/wrappers/python/examples/read_bag_example.py
@quattrinili thanks for the command.

Just sharing for reference, the below tool helps extract data from ROS bag file -
https://github.com/IntelRealSense/librealsense/tree/master/tools/convert

The problem is related to the fact that, as shown in the error, some of the topics include the space character, which is not allowed in a topic name. I did not check the code in librealsense, however, a quick workaround using ROS is just to use the filter tool in rosbag to get only the images (here more information http://wiki.ros.org/rosbag/Commandline#rosbag_filter). For example, to get the IMU data and the image data (properly replacing the elements in <>):
rosbag filter <input.bag> <output.bag> "topic == '/device_<device_id>/sensor_<sensor_id>/<stream_type>_<stream_id>/imu/data' or topic == '/device_<device_id>/sensor_<sensor_id>/<stream_type>_<stream_id>/image/data'"

I am using ros1 bridge to read the rosbag file. Unfortunately i am unable to play the rosbag file using ros2 bag play command.
It gave error like bellow:
what():  Invalid topic name: topic name token must not start with a number:
  '/device_0/sensor_1/Color_0/tf/0'

Then i tried with filter option, but i got below error message. II must play the rosbag files to be able to publish image topics.
rosbag filter ./Inputs/realsense_video/20210615_134517.bag ./Inputs/realsense_video/20210615_134517=out.bag "topic == '/device_0/sensor_1/Color_0/image/data' or topic == '/device_0/sensor_0/Depth_0/image/data'"

Traceback (most recent call last):
  File "/opt/ros/noetic/bin/rosbag", line 34, in <module>
    import rosbag
  File "/opt/ros/noetic/lib/python3/dist-packages/rosbag/__init__.py", line 33, in <module>
    from .bag import Bag, Compression, ROSBagException, ROSBagFormatException, ROSBagUnindexedException
  File "/opt/ros/noetic/lib/python3/dist-packages/rosbag/bag.py", line 69, in <module>
    import rospy
  File "/opt/ros/noetic/lib/python3/dist-packages/rospy/__init__.py", line 49, in <module>
    from .client import spin, myargv, init_node, \
  File "/opt/ros/noetic/lib/python3/dist-packages/rospy/client.py", line 54, in <module>
    import rospy.core
  File "/opt/ros/noetic/lib/python3/dist-packages/rospy/core.py", line 75, in <module>
    from rosgraph_msgs.msg import Log
ImportError: cannot import name 'Log' from 'rosgraph_msgs.msg' (/opt/ros/foxy/lib/python3.8/site-packages/rosgraph_msgs/msg/__init__.py)

Can any one suggest what to do?

authors: RealSenseCustomerSupport ShettyHarapanahalli Udaykiran87 dorodnic quattrinili


text:
Segfault in align with a debug build

Required Info

Camera Model
D435

Firmware Version
05.11.01.100

Operating System & Version
Linux (Ubuntu 18)

Kernel Version (Linux Only)
4.15.0-54

Platform
PC

SDK Version
2.24.0

Language
C++

Segment
AR

Issue Description
When using a debug build with -D_DEBUG, align frames to depth (or colour) results in a segmentation fault whilst performing an atomic operation inside a shared pointer of a stream profile. The relevant file is rs_frame.hpp line 376 (profile = other.profile;). In release mode there are no problems.

@knicos I tried the latest SDK v2.28 and FW 5.11.11.100 and didn't get the issue. Could you please try the latest SDK and FW to see if any luck? Thanks!

@knicos Could you please update if you still get issue with the latest SDK and FW? Thanks!

I updated to 2.28.1 and the latest FW update but I do still have the segfault in the debug build. It does not appear to be resolved for me.

@knicos , is this reproducible with the SDK tools/examples, such as rs-align ?
If not -  can you share the reproduction snippet?

The examples do work correctly. We are using it as a part of a much larger application that has a lot of threading with no guarantee that it is the same thread calling align.process for each frame. The application also uses OpenCV and CUDA extensively in case this matters. Unfortunately I don't have time to construct an example to reproduce it and can't provide our full source.
In a class constructor:
rs2::config cfg;
cfg.enable_stream(RS2_STREAM_DEPTH, 1280, 720, RS2_FORMAT_Z16, 30);
cfg.enable_stream(RS2_STREAM_COLOR, 1280, 720, RS2_FORMAT_BGRA8, 30);

rs2::pipeline_profile profile = pipe_.start(cfg);
rs2::device dev = profile.get_device();
rs2_intrinsics intrin = profile.get_stream(rs2_stream::RS2_STREAM_DEPTH).as<rs2::video_stream_profile>().get_intrinsics();

rs2::depth_sensor ds = dev.query_sensors().front().as<rs2::depth_sensor>();
scale_ = ds.get_depth_scale();

And in a process frame method:
rs2::frameset frames;
if (!pipe_.poll_for_frames(&frames)) return false;
frames = align_to_depth_.process(frames);

The last line is the problem in debug mode.

Ok, please ignore my previous comment. The examples DO NOT WORK if -D_DEBUG is passed to compiler. rs-align then segfaults.

Did you append a cmake generated makefile to add the -D_DEBUG flag? I want to reproduce the segfault you're seeing

@knicos If you're thinking to build debug version, -D_DEBUG flag is not the right one. I think you should build with **-DCMAKE_BUILD_TYPE=Debug  **
Could you please have a try and update? Thanks!

I do use -DCMAKE_BUILD_TYPE=Debug, and that alone seems ok. However, other code we have, in libraries that are not our own, uses _DEBUG and we need to enable it.

#2567

@knicos Could you please try gdb to get the core dump information about the Segfault? Thanks!

@knicos Did you get chance to try gdb to get the core dump information? Looking forward to your update. Thanks!

@RealSenseCustomerSupport Have you checked my gdb log or try to combine Realsense with OpenVINO on Raspberry Pi 3/4?
I am still stuck with the Segmentation fault problem of the Alignment API. As a result, I cannot use for  Intel device for my project.

@whatisor Your issue seems closed on github. Please create another new issue if it's not resolved. Thanks!

@knicos  Any update from your side? Thanks!

Any idea how to compile rs-align? Don't remember what I did last time but 2.31.1 doesn't compile on my machine, it fails to find libusb (it is installed), attempts to compile an internal version which also fails (missing config.h). I can't spend time on this so if it doesn't work I can't help further.
I can give you this from our own application which still crashes in debug (with _DEBUG) but the error is different (stack smashing detected).
#0  0x00007fffda6f1e97 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#1  0x00007fffda6f3801 in __GI_abort () at abort.c:79
#2  0x00007fffda73c897 in __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7fffda869988 "*** %s **: %s terminated\n") at ../sysdeps/posix/libc_fatal.c:181
#3  0x00007fffda7e7cd1 in __GI___fortify_fail_abort (need_backtrace=need_backtrace@entry=false, msg=msg@entry=0x7fffda869966 "stack smashing detected") at fortify_fail.c:33
#4  0x00007fffda7e7c92 in __stack_chk_fail () at stack_chk_fail.c:29
#5  0x00007ffff5ab8608 in librealsense::stream_filter_processing_block::should_process(rs2::frame const&) (this=, frame=...) at /home/jenkins/workspace/LRS_SDK_CI_Debian/src/src/proc/synthetic-stream.cpp:308
#6  0x00007ffff5ab94dc in librealsense::generic_processing_block::<lambda(rs2::frame, const rs2::frame_source&)>::operator() (source=..., f=..., __closure=0x55555712bc78)
at /home/jenkins/workspace/LRS_SDK_CI_Debian/src/src/proc/synthetic-stream.cpp:69
#7  0x00007ffff5ab94dc in rs2::frame_processor_callback<librealsense::generic_processing_block::generic_processing_block(char const)::<lambda(rs2::frame, const rs2::frame_source&)> >::on_frame(rs2_frame *, rs2_source *) (this=0x55555712bc70, f=, source=)
at /home/jenkins/workspace/LRS_SDK_CI_Debian/src/obj-x86_64-linux-gnu/../include/librealsense2/hpp/rs_processing.hpp:128
#8  0x00007ffff5ab60a7 in librealsense::processing_block::invoke(librealsense::frame_holder) (this=0x555556853f80, f=...) at /home/jenkins/workspace/LRS_SDK_CI_Debian/src/src/proc/synthetic-stream.cpp:43
#9  0x00007ffff5c223f1 in librealsense::synthetic_sensor::<lambda(librealsense::frame_holder)>::operator() (__closure=, f=...) at /home/jenkins/workspace/LRS_SDK_CI_Debian/src/src/sensor.cpp:1473
#10 0x00007ffff5c223f1 in librealsense::internal_frame_callback<librealsense::synthetic_sensor::start(librealsense::frame_callback_ptr)::<lambda(librealsense::frame_holder)> >::on_frame(rs2_frame *) (this=, fref=) at /home/jenkins/workspace/LRS_SDK_CI_Debian/src/src/types.h:935
#11 0x00007ffff5c3331b in librealsense::frame_source::invoke_callback(librealsense::frame_holder) const (this=0x555557095bc0, frame=...) at /home/jenkins/workspace/LRS_SDK_CI_Debian/src/src/source.cpp:125
#12 0x00007ffff5c187bb in librealsense::uvc_sensor::<lambda(librealsense::platform::stream_profile, librealsense::platform::frame_object, std::function<void()>)>::operator()(librealsense::platform::frame_object, std::function<void()>) (__closure=, f=..., continuation=..., p=...)
at /home/jenkins/workspace/LRS_SDK_CI_Debian/src/src/sensor.cpp:377
#13 0x00007ffff5c18f27 in std::_Function_handler<void(librealsense::platform::stream_profile, librealsense::platform::frame_object, std::function<void()>), librealsense::uvc_sensor::open(const stream_profiles&):---Type  to continue, or q  to quit---
td::_Any_data &, librealsense::platform::stream_profile &&, librealsense::platform::frame_object &&, std::function<void()> &&) (__functor=..., __args#0=..., __args#1=..., __args#2=...)
at /usr/include/c++/7/bits/std_function.h:316
#14 0x00007ffff5b437ee in std::function<void (librealsense::platform::stream_profile, librealsense::platform::frame_object, std::function<void ()>)>::operator()(librealsense::platform::stream_profile, librealsense::platform::frame_object, std::function<void ()>) const (__args#2=..., __args#1=..., __args#0=..., this=0x555557104890) at /usr/include/c++/7/bits/std_function.h:706
#15 0x00007ffff5b437ee in librealsense::platform::v4l_uvc_device::poll() (this=this@entry=0x555557104730) at /home/jenkins/workspace/LRS_SDK_CI_Debian/src/src/linux/backend-v4l2.cpp:954
#16 0x00007ffff5b44058 in librealsense::platform::v4l_uvc_device::capture_loop() (this=0x555557104730) at /home/jenkins/workspace/LRS_SDK_CI_Debian/src/src/linux/backend-v4l2.cpp:1290
#17 0x00007fffdb11766f in  () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#18 0x00007ffff6ddb6db in start_thread (arg=0x7fff2cff9700) at pthread_create.c:463
#19 0x00007fffda7d488f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Just taking another look. Is this not the problem?
Lines 623 in rs_frame.hpp (release 2.31.1)
#ifdef _DEBUG
        stream_profile profile;
        unsigned long long frame_number = 0;
#endif

If your debug build is without _DEBUG but I have _DEBUG then the rs_frame class is of a different size and hence will corrupt the stack as I'm seeing.

@knicos  Did you install "libusb-1.0-0-dev" for libusb? And did you build SDK from source code or use the DKMS binary? What's CPU of your setup?

@RealSenseCustomerSupport Have you checked my gdb log or try to combine Realsense with OpenVINO on Raspberry Pi 3/4?
I am still stuck with the Segmentation fault problem of the Alignment API. As a result, I cannot use for Intel device for my project.

@whatisor have you tried wrapping the C API in your C++ program? I've run into the same segfaults everyone else has but I've found success in wrapping the C API align functions in my C++ application

@ThomasBrandonD thanks for response.
I think Realsense is C++, isn't it?
I used rs2::align

... don't know (can't check atm, probably the wrong one)
No, always the DKMS binary.
Intel Core i7

I was adding _DEBUG to my own cmake for my own purposes, not rebuilding realsense SDK with it. Hence the conflict.

@whatisor
It is, but you can still use C in your C++ app, check out https://stackoverflow.com/questions/1041866/what-is-the-effect-of-extern-c-in-c
I'm assuming you're using some API to modify your the image frames you're getting from the realsense (like OpenCV). You can just use the Realsense C API to get the data into a cv::Mat
If that makes sense give it a shot or I can make a small example

@ThomasBrandonD , Do you mean issue only occurs for C++ API of realsense?

@whatisfor Yep, it doesn't exactly "solve" the issue of this ticket but if you need a solution, using the C API is one work-around you might try which worked for me

Hi,
Will you be needing further help with this?
If we don’t hear from you in 7 days, this issue will be closed.
Thanks

authors: RealSenseCustomerSupport RealSenseSupport ThomasBrandonD ev-mp knicos whatisor


text:
SR300 support in ROS + Distorted Pointcloud

could you precise the format for RGB and depth data for SR300 ? I use the following formats (as in examples) together  with the ROS wrapper from https://github.com/intel-ros/realsense, and I get weird colors and weird depth distances:
DEPTH_FORMAT = RS_FORMAT_Z16;
COLOR_FORMAT = RS_FORMAT_RGB8;
IR1_FORMAT = RS_FORMAT_Y16;
What is the correct format?

Required Info

Camera Model
SR300

Firmware Version
3.10.10.0

Operating System & Version
Linux

Kernel Version (Linux Only)
4.4.0-040400-generic

Build System
VS2013, XCode or Makefile

Hi. The Intel ROS node you linked doesn't support the SR300 yet (despite being based on librealsense). That ROS team will need to modify their node to deal with the correct depth scale and formats. I could possibly point you in the right direction if you send a screenshot of exactly what colors are wrong in the color or IR image. The depth scale between cameras is usually explained in other people's code by a missing multiply in the pointcloud projection code (https://github.com/IntelRealSense/librealsense/blob/master/examples/cpp-tutorial-3-pointcloud.cpp#L101). I would also recommend using one of the librealsense sample applications to double check that the camera isn't fundamentally giving weird data.

Thank you, @ddiakopoulos, now it works! the problem was in pointcloud processing disabled by default. Once enabled, the values are correct!

When we run examples, the RGB image looks good but in the depth data there is some distortion (like in screenshots, where a planar surface placed in front of the camera (just behind the cola) looks like a curved surface with its distortion increasing with a distance from the plane. Could you suggest how to correct this distortion? In intrinsic parameters, the Distortion matrix is empty, could you give approximate values?

@nlyubova we've seen this same thing on a couple different GitHub issues now. Could you print out all members of both depth and color intrinsic structs, and the extrinsics between depth=>color?

This is the camera info that I get with the ROS wrapper and librealsense (after few modifications in the wrapper's code, we can get the Distortion as well). Since we have two SR300 sensors (the same model and the same Firmware version: 3.10.10.0), here is the camera info from each of them (and there is small difference in numbers):
**1st SR300 sensor:  Depth intrinsic: **
height: 480
width: 640
distortion_model: plumb_bob
D: [0.14829276502132416, 0.06511270254850388, 0.004560006316751242, 0.0025975550524890423, 0.08284061402082443]
K: [475.53765869140625, 0.0, 309.2130126953125, 0.0, 475.5375061035156, 245.9634552001953, 0.0, 0.0, 1.0]
R: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
P: [475.53765869140625, 0.0, 309.2130126953125, 0.0, 0.0, 475.5375061035156, 245.9634552001953, 0.0, 0.0, 0.0, 1.0, 0.0]
**1st SR300 sensor: Color intrinsic: **
height: 480
width: 640
distortion_model: plumb_bob
D: [0.0, 0.0, 0.0, 0.0, 0.0]
K: [616.5604248046875, 0.0, 304.9191589355469, 0.0, 616.560546875, 241.67813110351562, 0.0, 0.0, 1.0]
R: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
P: [616.5604248046875, 0.0, 304.9191589355469, 0.0, 0.0, 616.560546875, 241.67813110351562, 0.0, 0.0, 0.0, 1.0, 0.0]
**1st SR300 sensor: depth -> color extrinsic: **

Translation: [0.001, 0.004, -0.026]
Rotation: in Quaternion [0.000, 0.000, 0.000, 1.000]
in RPY (radian) [0.000, -0.000, 0.000]
in RPY (degree) [0.000, -0.000, 0.000]

**2nd SR300 sensor: Depth intrinsic: **
height: 480
width: 640
distortion_model: plumb_bob
D: [0.13900761306285858, 0.08196153491735458, 0.003836501855403185, -8.22131842141971e-05, 0.06141791120171547]
K: [475.8931884765625, 0.0, 321.28350830078125, 0.0, 475.89306640625, 245.9639434814453, 0.0, 0.0, 1.0]
R: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
P: [475.8931884765625, 0.0, 321.28350830078125, 0.0, 0.0, 475.89306640625, 245.9639434814453, 0.0, 0.0, 0.0, 1.0, 0.0]
**2nd SR300 sensor: Color intrinsic: **
height: 480
width: 640
distortion_model: plumb_bob
D: [0.0, 0.0, 0.0, 0.0, 0.0]
K: [617.5955200195312, 0.0, 314.9975280761719, 0.0, 617.5956420898438, 238.17877197265625, 0.0, 0.0, 1.0]
R: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
P: [617.5955200195312, 0.0, 314.9975280761719, 0.0, 0.0, 617.5956420898438, 238.17877197265625, 0.0, 0.0, 0.0, 1.0, 0.0]
**2nd SR300 sensor: depth -> color extrinsic: **

Translation: [0.001, 0.004, -0.025]
Rotation: in Quaternion [0.000, 0.000, 0.000, 1.000]
in RPY (radian) [0.000, -0.000, 0.000]
in RPY (degree) [0.000, -0.000, 0.000]

@nlyubova unfortunately I'm not very familiar with the ROS-ian way of performing projection. The best guidance I can offer is that you must use the projection methods in rsutil.h because of the SR300's somewhat confusing inverse model.
All those coefficients look OK to me. I encountered similar pincushion distortion + warped sides in an internal validation tool used for the SR300. I have an open question to the camera hardware team to see if this is the quality of data expected. My own internal team primarily focuses on the R200+ series of devices, so we are not intimately familiar with the depth properties of the SR300.

Per private email communication, this is the result of known calibration issues in pre-release ("non-PRQ") SR300 modules.

@nlyubova Hey, I wonder could you please tell me how to run the example code? I have qtcreator installed but I just don't know how to use it.

Hi. The Intel ROS node you linked doesn't support the SR300 yet (despite being based on librealsense). That ROS team will need to modify their node to deal with the correct depth scale and formats. I could possibly point you in the right direction if you send a screenshot of exactly what colors are wrong in the color or IR image. The depth scale between cameras is usually explained in other people's code by a missing multiply in the pointcloud projection code (https://github.com/IntelRealSense/librealsense/blob/master/examples/cpp-tutorial-3-pointcloud.cpp#L101). I would also recommend using one of the librealsense sample applications to double check that the camera isn't fundamentally giving weird data.

Updated link? https://github.com/IntelRealSense/librealsense/tree/master/examples/pointcloud

authors: Thompson104 ddiakopoulos nlyubova tispratik


text:
Cannot start pipeline of T265 after using command context.query_all_sensors() or context.query_devices()

Required Info

Camera Model
{ T265 }

Firmware Version
(0.2.0.926)

Operating System & Version
{ Ubuntu 18.04

Kernel Version (Linux Only)
( 5.3.0-51-generic )

Platform
x86_64 Desktop

SDK Version
{ v2.34.0 }

Language
{ C++ }

Issue Description
When calling the function rs2::context().query_devices() or rs2::context().query_sensors(), I am unable to start the T265 pipeline.
rs2::context  ctx;
for (auto &&dev : ctx.query_devices())
        {
            rs2::pipeline pipe(ctx);
            rs2::config cfg;
            cfg.enable_device(dev.get_info(RS2_CAMERA_INFO_SERIAL_NUMBER));
            pipe.start(cfg);
        }

I too have the same problem running SDK v2.34.0 but on Windows 10 (firmware 0.2.0.926). An unhandled exception is thrown using the above code.
I came across this error first trying to run the rs-multicam example which uses the same method to start pipelines as above. I have been able to replicate this issue on two separate Windows computers. It is worth noting that realsense-viewer works fine, without any problems streaming from the T265.
Currently, the only way I can get the T265 to work is by enabling the streams desired without querying devices beforehand:
rs2::pipeline pipe;
rs2::config cfg;
cfg.enable_stream(RS2_STREAM_POSE, RS2_FORMAT_6DOF);
cfg.enable_stream(RS2_STREAM_FISHEYE, 1);
cfg.enable_stream(RS2_STREAM_FISHEYE, 2);
pipe.start(cfg);

This is the same method as per rs-ar-basic. Next, I will try to find a previous SDK version which works with ctx.query_devices(), and if that does not work, reverting the T265 firmware to a previous version.

After going back and compiling the previous releases of the SDK, the most recent version that still works with rs-multicam and ctx.query_devices() is v2.31.0.

After going back and compiling the previous releases of the SDK, the most recent release that still works with rs-multicam and ctx.query_devices() is v2.31.0.
Each SDK was built using Windows 10 (1903), CMake GUI 3.17.0 and Visual Studio 2019. The CMake configuration was left as default EXCEPT for checking ENFORCE_METADATA.

@ev-mp, Any update on this?

@ev-mp ping on this issue.

Last release included update to rs-multicam showing how to use query_devices together with pipeline

authors: MoBaT dorodnic jfa1 joshuafavetti


text:
Wrong timestamp for last recorded frame

Required Info

Camera Model
D435 / L515

Firmware Version
05.12.08.200 / 01.05.02.00

Operating System & Version
Linux (Ubuntu 18.04) / MacOS 10.15.7

Kernel Version (Linux Only)
5.4.0.58

Platform
PC

SDK Version
2.40.0

Language
C++

Segment

I'm recording to a bag file with the rs2::pipeline API. The last frame gets recorded with a wrong  timestamp and this creates an incorrect duration. While reading the bag file, the reader code (including realsense-viewer) waits for ever or crashes. This happens on both platforms listed above (macOS with L515 and Ubuntu 18.04 with D435).

The debug logs created with LRS_LOG_LEVEL=DEBUG are attached. There is a big jump in the timestamp for the last frame in the recording logs.
Playback_2020-12-18-15_19_17.log.zip
Recording_2020-12-18-15_11_26.log.zip
Is there any way to mitigate this, such as not writing the last frame, or fixing the last frame timestamp? Here is what hasn't worked:

Pausing recording some time before stopping the pipeline.
Re-starting and re-stopping the pipeline after stopping it.

This error happens if pause() recording is called very soon after pipeline::start().

Hi @ssheorey
In looking at this further, I think what is happening is the pause function is pausing the recording but not stopping the streams from continuing which could lead to a change in timestamp when recording is resumed.
Took a look at recording via the rs-recorder as well as the recording function inside realsense-viewer and I don't see this issue.
*If we don’t hear from you in 7 days, this issue will be closed.

Hi @ssheorey
In looking at this further, I think what is happening is the pause function is pausing the recording but not stopping the streams from continuing which could lead to a change in timestamp when recording is resumed.
Took a look at recording via the rs-recorder as well as the recording function inside realsense-viewer and I don't see this issue.
*If we don’t hear from you in 7 days, this issue will be closed.

Thanks for looking into this. My earlier code called pipeline::start() immediately followed by pause() to wait for the user to request start recording. I wanted to retrieve frames for display while recording was paused. The timestamp issue only affects the last frame recorded, which is strange, and the last timestamp actually looks to be a junk value (e.g. 5 years in the future), not what you would get if the clock had just continued running. This pattern isn't used in rs-recorder so the issues doesn't appear.
After a lot of trial and error, my work around was to create a new pipeline when I needed to start recording, instead of keeping recording paused().

Thanks for looking into this. My earlier code called pipeline::start() immediately followed by pause() to wait for the user to request start recording. I wanted to retrieve frames for display while recording was paused. The timestamp issue only affects the last frame recorded, which is strange, and the last timestamp actually looks to be a junk value (e.g. 5 years in the future), not what you would get if the clock had just continued running. This pattern isn't used in rs-recorder so the issues doesn't appear.
After a lot of trial and error, my work around was to create a new pipeline when I needed to start recording, instead of keeping recording paused().

Thanks and glad that you were able to determine a workaround for this.
Is there anything else you need here?
*If we don’t hear from you in 7 days, this issue will be closed.

Thanks and glad that you were able to determine a workaround for this.
Is there anything else you need here?
*If we don’t hear from you in 7 days, this issue will be closed.

hello @ssheorey
I tried to reproduce the issue with the flow you described without success , can you please attach a code snippet from your application that reproduce this issue?

authors: RealSenseSupport aangerma ssheorey


text:
feat(loss)/add different operator types for cross_entropy

Motivation

support different operator types for cross_entropy

add op_type config
loss = dict(  label_smoothing=0,  op_type="flash_vocab_parallel", )

reference this https://github.com/pjlab-sys4nlp/InternTrain/pull/148
Use cases (Optional)
If this PR introduces a new feature, it is better to list some use cases here and update the documentation.
Checklist
Before PR:

[x] Pre-commit or other linting tools are used to fix the potential lint issues.

@yingtongxiong merge下develop分支过CI吧

@yingtongxiong merge下develop分支过CI吧

好的

@yingtongxiong merge下develop分支过CI吧

@sunpengsdu 已经好了

authors: sunpengsdu yingtongxiong

repo: InternLM/InternEvo


text:
Result of a sonarqube analysis on the code

Describe the bug
I've run the sonarqube software to scan the code of the dataspace connector. It came up with some faults and some possible bugs. I attach the result od the analyse with a couple of photos. If it's needed any further infromation don't hesitate on contacting.
Additional context

Hi,
thank you very much for your interest in the DSC and sharing information with us.
FYI: When you run mvn verify site -Prelease our build system will also perform code and security analysis and generate a project report!

authors: brianjahnke jmartinezsqs


text:
Handling Participant Ids in the Contract Agreement

Currently, the ContractAgreementMessage does not contain properties for the participant ids. Two properties should be defined of type xsd:string:

dspace:consumerId
dspace:providerId

The contents of these properties are a dataspace-specific unique identifier of the contract agreement parties. Note that these identifiers are not necessarily the same as the identifiers of the participant agents negotiating the contract (i.e. the "connectors").

Should be added to the odrl:Agreement, not dspace:ContractAgreementMessage.

authors: jimmarino juliapampus